9.1.3 Messages for Global Procedures
38.4233GPPNG-RANRelease 17TSXn Application Protocol (XnAP)
9.1.3.1 XN SETUP REQUEST
This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Global NG-RAN Node ID |
M |
9.2.2.3 |
YES |
reject |
||
TAI Support List |
M |
9.2.3.20 |
List of supported TAs and associated characteristics. |
YES |
reject |
|
AMF Region Information |
M |
9.2.3.83 |
Contains a list of all the AMF Regions to which the NG-RAN node belongs. |
YES |
reject |
|
List of Served Cells NR |
0 .. <maxnoofCellsinNG-RAN node> |
Contains a list of cells served by the gNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the gNB |
YES |
reject |
||
>Served Cell Information NR |
M |
9.2.2.11 |
– |
|||
>Neighbour Information NR |
O |
9.2.2.13 |
– |
|||
>Neighbour Information E-UTRA |
O |
9.2.2.14 |
– |
|||
>Served Cell Specific Info Request |
O |
9.2.2.102 |
YES |
ignore |
||
List of Served Cells E-UTRA |
0 .. <maxnoofCellsinNG-RAN node> |
Contains a list of cells served by the ng-eNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the ng-eNB |
YES |
reject |
||
>Served Cell Information E-UTRA |
M |
9.2.2.12 |
– |
|||
>Neighbour Information NR |
O |
9.2.2.13 |
– |
|||
>Neighbour Information E-UTRA |
O |
9.2.2.14 |
– |
|||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
||
TNL Configuration Info |
O |
9.2.3.96 |
YES |
ignore |
||
Partial List Indicator NR |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the List of Served Cells NR IE. |
YES |
ignore |
|
Cell and Capacity Assistance Information NR |
O |
9.2.2.41 |
Contains NR cell related assistance information. |
YES |
ignore |
|
Partial List Indicator E-UTRA |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the List of Served Cells E-UTRA. |
YES |
ignore |
|
Cell and Capacity Assistance Information E-UTRA |
O |
9.2.2.42 |
Contains E-UTRA cell related assistance information. |
YES |
ignore |
|
Local NG-RAN Node Identifier |
O |
9.2.2.101 |
YES |
ignore |
||
Neighbour NG-RAN Node List |
0..<maxnoofNeighbourNG-RAN nodes> |
YES |
ignore |
|||
>Global NG-RAN Node ID |
M |
9.2.2.3 |
– |
|||
>Local NG-RAN Node Identifier |
M |
9.2.2.101 |
– |
Range bound |
Explanation |
maxnoofCellsinNG-RAN node |
Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
maxnoofNeighbourNG-RAN nodes |
Maximum no. of neighbour NG-RAN nodes. Value is 256. |
9.1.3.2 XN SETUP RESPONSE
This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Global NG-RAN Node ID |
M |
9.2.2.3 |
YES |
reject |
||
TAI Support List |
M |
9.2.3.20 |
List of supported TAs and associated characteristics. |
YES |
reject |
|
List of Served Cells NR |
0 .. <maxnoofCellsinNG-RAN node> |
Contains a list of cells served by the gNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the gNB |
YES |
reject |
||
>Served Cell Information NR |
M |
9.2.2.11 |
– |
|||
>Neighbour Information NR |
O |
9.2.2.13 |
– |
|||
>Neighbour Information E-UTRA |
O |
9.2.2.14 |
– |
|||
List of Served Cells E-UTRA |
0 .. <maxnoofCellsinNG-RAN node> |
Contains a list of cells served by the ng-eNB. If a partial list of cells is signalled, it contains at least one cell per carrier configured at the gNB |
YES |
reject |
||
>Served Cell Information E-UTRA |
M |
9.2.2.12 |
– |
|||
>Neighbour Information NR |
O |
9.2.2.13 |
– |
|||
>Neighbour Information E-UTRA |
O |
9.2.2.14 |
– |
|||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
AMF Region Information |
O |
9.2.3.83 |
Contains a list of all the AMF Regions to which the NG-RAN node belongs. |
YES |
reject |
|
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
||
TNL Configuration Info |
O |
9.2.3.96 |
YES |
ignore |
||
Partial List Indicator NR |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the List of Served Cells NR IE. |
YES |
ignore |
|
Cell and Capacity Assistance Information NR |
O |
9.2.2.41 |
Contains NR cell related assistance information. |
YES |
ignore |
|
Partial List Indicator E-UTRA |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the List of Served Cells E-UTRA. |
YES |
ignore |
|
Cell and Capacity Assistance Information E-UTRA |
O |
9.2.2.42 |
Contains E-UTRA cell related assistance information. |
YES |
ignore |
|
Local NG-RAN Node Identifier |
O |
9.2.2.101 |
YES |
ignore |
||
Neighbour NG-RAN Node List |
0..<maxnoofNeighbourNG-RAN nodes> |
YES |
ignore |
|||
>Global NG-RAN Node ID |
M |
9.2.2.3 |
– |
|||
>Local NG-RAN Node Identifier |
M |
9.2.2.101 |
– |
Range bound |
Explanation |
maxnoofCellsinNG-RAN node |
Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
maxnoofNeighbourNG-RAN nodes |
Maximum no. of neighbour NG-RAN nodes. Value is 256. |
9.1.3.3 XN SETUP FAILURE
This message is sent by the neighbouring NG-RAN node to indicate Xn Setup failure.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Time To Wait |
O |
9.2.3.56 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
||
Message Oversize Notification |
O |
9.2.2.45 |
YES |
ignore |
9.1.3.4 NG-RAN NODE CONFIGURATION UPDATE
This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer updated information for an Xn-C interface instance.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
9.2.3.1 |
YES |
reject |
|||
TAI Support List |
O |
9.2.3.20 |
List of supported TAs and associated characteristics. |
GLOBAL |
reject |
||
CHOICE Initiating NodeType |
M |
YES |
ignore |
||||
>gNB |
|||||||
>>Served Cells To Update NR |
O |
9.2.2.15 |
YES |
ignore |
|||
>>Cell Assistance Information NR |
O |
9.2.2.17 |
YES |
ignore |
|||
>>Cell Assistance Information E-UTRA |
O |
9.2.2.43 |
YES |
ignore |
|||
>>Served Cell Specific Info Request |
O |
9.2.2.102 |
YES |
ignore |
|||
>ng-eNB |
|||||||
>>Served Cells to Update E-UTRA |
O |
9.2.2.16 |
YES |
ignore |
|||
>>Cell Assistance Information NR |
O |
9.2.2.17 |
YES |
ignore |
|||
>>Cell Assistance Information E-UTRA |
O |
9.2.2.43 |
YES |
ignore |
|||
TNLA To Add List |
0..1 |
YES |
ignore |
||||
>TNLA To Add Item |
1..<maxnoofTNLAssociations> |
– |
|||||
>>TNLA Transport Layer Information |
M |
CP Transport Layer Information 9.2.3.31 |
CP Transport Layer Information of NG-RAN node1 |
– |
|||
>> TNL Association Usage |
M |
9.2.3.84 |
– |
||||
TNLA To Update List |
0..1 |
YES |
ignore |
||||
>TNLA To Update Item |
1..<maxnoofTNLAssociations> |
– |
|||||
>>TNLA Transport Layer Information |
M |
CP Transport Layer Information 9.2.3.31 |
CP Transport Layer Information of NG-RAN node1 |
– |
|||
>> TNL Association Usage |
O |
9.2.3.84 |
– |
||||
TNLA To Remove List |
0..1 |
YES |
ignore |
||||
>TNLA To Remove Item |
1..<maxnoofTNLAssociations> |
– |
|||||
>>TNLA Transport Layer Information |
M |
CP Transport Layer Information 9.2.3.31 |
CP Transport Layer Information of NG-RAN node1 |
– |
|||
Global NG-RAN Node ID |
O |
9.2.2.3 |
YES |
reject |
|||
AMF Region Information To Add |
O |
AMF Region Information 9.2.3.83 |
List of all added AMF Regions to which the NG-RAN node belongs. |
YES |
reject |
||
AMF Region Information To Delete |
O |
AMF Region Information 9.2.3.83 |
List of all deleted AMF Regions to which the NG-RAN node belongs. |
YES |
reject |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
|||
TNL Configuration Info |
O |
9.2.3.96 |
YES |
ignore |
|||
Coverage Modification List |
0 .. 1 |
List of cells with modified coverage. |
GLOBAL |
reject |
|||
>Coverage Modification Item |
0 .. <maxnoofCellsinNG-RAN node> |
– |
|||||
>>Global NG-RAN Cell Identity |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
NG-RAN Cell Global Identifier of the cell to be modified. |
– |
|||
>>Cell Coverage State |
M |
INTEGER (0..63, …) |
Value ‘0’ indicates that the cell is inactive. Other values Indicates that the cell is active and also indicates the coverage configuration of the concerned cell. |
– |
|||
>>Cell Deployment Status Indicator |
O |
ENUMERATED(pre-change-notification, …) |
Indicates the Cell Coverage State is planned to be used at the next reconfiguration. |
– |
|||
>>Cell Replacing Info |
C-ifCellDeploymentStatusIndicatorPresent |
– |
|||||
>>>Replacing Cells |
0 .. <maxnoofCellsinNG-RAN node> |
– |
|||||
>>>>Global NG-RAN Cell Identity |
Global NG-RAN Cell Identity 9.2.2.27 |
NG-RAN Cell Global Identifier of a cell that may replace all or part of the coverage of the cell to be modified. |
– |
||||
>>SSB Coverage Modification List |
0.. 1 |
List of SSB beams with modified coverage. |
– |
||||
>>>SSB Coverage Modification Item |
0..<maxnoofSSBAreas> |
– |
|||||
>>>>SSB Index |
M |
INTEGER (0..63) |
Identifier of the SSB beam to be modified. |
– |
|||
>>>>SSB Coverage State |
M |
INTEGER (0..15, …) |
Value ‘0’ indicates that the SSB beam is inactive. Other values Indicates that the SSB beam is active and also indicates the coverage configuration of the concerned SSB beam. |
– |
|||
Local NG-RAN Node Identifier |
O |
9.2.2.101 |
YES |
ignore |
|||
Neighbour NG-RAN Node List |
0..<maxnoofNeighbourNG-RAN nodes> |
YES |
ignore |
||||
>Global NG-RAN Node ID |
M |
9.2.2.3 |
– |
||||
>Local NG-RAN Node Identifier |
M |
9.2.2.101 |
– |
||||
Local NG-RAN Node Identifier Removal |
O |
Local NG-RAN Node Identifier 9.2.2.101 |
YES |
ignore |
Range bound |
Explanation |
maxnoofTNLAssociations |
Maximum numbers of TNL Associations between the NG RAN nodes. Value is 32. |
maxnoofCellsinNG-RAN node |
Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
maxnoofSSBAreas |
Maximum no. SSB Areas that can be served by a cell. Value is 64. |
maxnoofNeighbourNG-RAN nodes |
Maximum no. of neighbour NG-RAN nodes. Value is 256. |
Condition |
Explanation |
ifCellDeploymentStatusIndicatorPresent |
This IE shall be present if the Cell Deployment Status Indicator IE is present. |
9.1.3.5 NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE
This message is sent by a neighbouring NG-RAN node to a peer node to acknowledge update of information for a TNL association.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
CHOICE Responding NodeType |
M |
YES |
ignore |
|||
>ng-eNB |
||||||
>>Served E-UTRA Cells |
0 .. < maxnoofCellsinNG-RANnode> |
Complete or limited list of cells served by an ng-eNB, if requested by NG-RAN node1. |
YES |
ignore |
||
>>>Served Cell Information E-UTRA |
M |
9.2.2.12 |
– |
|||
>>>Neighbour Information NR |
O |
9.2.2.13 |
NR neighbours. |
– |
||
>>>Neighbour Information E-UTRA |
O |
9.2.2.14 |
E-UTRA neighbours |
– |
||
>>Partial List Indicator E-UTRA |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the Served E-UTRA Cells IE |
YES |
ignore |
|
>>Cell and Capacity Assistance Information E-UTRA |
O |
9.2.2.42 |
Contains E-UTRA cell related assistance information. |
YES |
ignore |
|
>gNB |
||||||
>>Served NR Cells |
0 .. < maxnoofCellsinNG-RANnode> |
Complete or limited list of cells served by a gNB, if requested by NG-RAN node1. |
– |
|||
>>>Served Cell Information NR |
M |
9.2.2.11 |
– |
|||
>>>Neighbour Information NR |
O |
9.2.2.13 |
NR neighbours. |
– |
||
>>>Neighbour Information E-UTRA |
O |
9.2.2.14 |
E-UTRA neighbours |
– |
||
>>Partial List Indicator NR |
O |
Partial List Indicator 9.2.2.46 |
Value "partial" indicates that a partial list of cells is included in the Served NR Cells IE |
YES |
ignore |
|
>>Cell and Capacity Assistance Information NR |
O |
9.2.2.41 |
Contains NR cell related assistance information. |
YES |
ignore |
|
TNLA Setup List |
0..1 |
YES |
ignore |
|||
>TNLA Setup Item |
1..<maxnoofTNLAssociations> |
– |
||||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.2.3.31 |
CP Transport Layer Information as received from NG-RAN node1 |
– |
||
TNLA Failed to Setup Lis |
0..1 |
YES |
ignore |
|||
>TNLA Failed To Setup Item |
1..<maxnoofTNLAssociations> |
– |
||||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.2.3.31 |
CP Transport Layer Information as received from NG-RAN node1 |
– |
||
>>Cause |
M |
9.2.3.2 |
– |
|||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
||
TNL Configuration Info |
O |
9.2.3.96 |
YES |
ignore |
||
Local NG-RAN Node Identifier |
O |
9.2.2.101 |
YES |
ignore |
||
Neighbour NG-RAN Node List |
0..<maxnoofNeighbourNG-RAN nodes> |
YES |
ignore |
|||
>Global NG-RAN Node ID |
M |
9.2.2.3 |
– |
|||
>Local NG-RAN Node Identifier |
M |
9.2.2.101 |
– |
|||
Local NG-RAN Node Identifier Removal |
Local NG-RAN Node Identifier 9.2.2.101 |
YES |
ignore |
Range bound |
Explanation |
maxnoofCellsinNGRANnode |
Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
maxnoofTNLAssociations |
Maximum numbers of TNL Associations between NG-RAN nodes. Value is 32. |
maxnoofNeighbourNG-RAN nodes |
Maximum no. of neighbour NG-RAN nodes. Value is 256. |
9.1.3.6 NG-RAN NODE CONFIGURATION UPDATE FAILURE
This message is sent by the neighbouring NG-RAN node to indicate NG-RAN node Configuration Update failure.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Time To Wait |
O |
9.2.3.56 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.7 CELL ACTIVATION REQUEST
This message is sent by the NG-RAN node1 to the peer NG-RAN node2 to request a previously switched-off cell/s to be re-activated.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
CHOICE Served Cells To Activate |
M |
YES |
reject |
|||
>NR Cells |
||||||
>>NR Cells List |
1 |
– |
||||
>>>NR Cells item |
1 .. < maxnoofCellsinNG-RANnode> |
– |
||||
>>>>NR CGI |
M |
9.2.2.7 |
– |
|||
>E-UTRA Cells |
||||||
>>E-UTRA Cells List |
1 |
– |
||||
>>>E-UTRA Cells item |
1 .. < maxnoofCellsinNG-RANnode> |
– |
||||
>>>>E-UTRA CGI |
M |
9.2.2.8 |
– |
|||
Activation ID |
M |
INTEGER (0..255) |
Allocated by the NG-RAN node1 |
YES |
reject |
|
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
Range bound |
Explanation |
maxnoofCellsinNG-RANnode |
Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
9.1.3.8 CELL ACTIVATION RESPONSE
This message is sent by an NG-RAN node2 to a peer NG-RAN node1 to indicate that one or more cell(s) previously switched-off has (have) been activated.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
CHOICE Activated Served Cells |
M |
YES |
reject |
|||
>NR Cells |
||||||
>>NR Cells List |
1 |
– |
||||
>>>NR Cells Item |
1 .. < maxnoffCellsinNG-RANnode> |
– |
||||
>>>>NR CGI |
M |
9.2.2.7 |
– |
|||
>E-UTRA Cells |
||||||
>>E-UTRA Cells List |
1 |
– |
||||
>>>E-UTRA Cells Item |
1 .. < maxnoofCellsinNG-RANnode> |
– |
||||
>>>>E-UTRA CGI |
M |
9.2.2.8 |
– |
|||
Activation ID |
M |
INTEGER (0..255) |
Allocated by the NG-RAN node1 |
YES |
reject |
|
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
Range bound |
Explanation |
maxnoofCellsinNG-RANnode |
Maximum no. cells that can be served by an NG-RAN node. Value is 16384. |
9.1.3.9 CELL ACTIVATION FAILURE
This message is sent by an NG-RAN node2 to a peer NG-RAN node1 to indicate cell activation failure.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Activation ID |
M |
INTEGER (0..255) |
Allocated by the NG-RAN node1 |
YES |
reject |
|
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.10 RESET REQUEST
This message is sent from one NG-RAN node to another NG-RAN node and is used to request the Xn interface to be reset.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
CHOICE Reset Request TypeInfo |
M |
YES |
reject |
|||
>Full Reset |
||||||
>Partial Reset |
||||||
>>UE contexts to be released List |
1 |
– |
||||
>>>UE Contexts to be released Item |
1 .. <maxnoof UEcontexts> |
– |
||||
>>>>NG-RAN node1 UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated at the NG-RAN node1 |
– |
||
>>>>NG-RAN node2 UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated at the NG-RAN node2 |
– |
||
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
Range bound |
Explanation |
maxnoofUEContexts |
Maximum no. of UE Contexts. Value is 8192. |
9.1.3.11 RESET RESPONSE
This message is sent by an NG-RAN node as a response to a RESET REQUEST message.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
CHOICE Reset Response Type Info |
M |
YES |
ignore |
|||
>Full Reset |
||||||
>Partial Reset |
||||||
>>Admitted UE contexts to be released List |
1 |
– |
||||
>>>Admitted UE Contexts to be released Item |
1 .. <maxnoof UEcontexts> |
– |
||||
>>>>NG-RAN node1 UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated at the NG-RAN node1 |
– |
||
>>>>NG-RAN node2 UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated at the NG-RAN node2 |
– |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
Range bound |
Explanation |
maxnoofUEContexts |
Maximum no. of UE Contexts. Value is 8192. |
9.1.3.12 ERROR INDICATION
This message is used to indicate that some error has been detected in the NG-RAN node.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
ignore |
||
Old NG-RAN node UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated for handover at the source NG-RAN node and for dual connectivity at the S-NG-RAN node or for an SN Status Transfer procedure at the NG-RAN node from which a DRB is offloaded. |
YES |
ignore |
|
New NG-RAN node UE XnAP ID |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
Allocated for handover at the target NG-RAN node and for dual connectivity at the M-NG-RAN node or for an SN Status Transfer procedure at the NG-RAN node to which a DRB is offloaded. |
YES |
ignore |
|
Cause |
O |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.13 XN REMOVAL REQUEST
This message is sent by a NG-RAN node to a neighbouring NG-RAN node to initiate the removal of the interface instance.
Direction: NG-RAN node 1 NG-RAN node 2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Global NG-RAN Node ID |
M |
9.2.2.3 |
YES |
reject |
||
Xn Removal Threshold |
O |
Xn Benefit Value 9.2.3.54 |
YES |
reject |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.14 XN REMOVAL RESPONSE
This message is sent by a NG-RAN node to a neighbouring NG-RAN node to acknowledge the initiation of removal of the interface instance.
Direction: NG-RAN node 2 NG-RAN node 1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Global NG-RAN Node ID |
M |
9.2.2.3 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.15 XN REMOVAL FAILURE
This message is sent by the NG-RAN node to indicate that removing the interface instance cannot be accepted.
Direction: NG-RAN node 2 NG-RAN node 1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
||
Interface Instance Indication |
O |
9.2.2.39 |
YES |
reject |
9.1.3.16 FAILURE INDICATION
This message is sent by NG-RAN node2 to indicate an RRC re-establishment attempt or a reception of an RLF Report from a UE that suffered a connection failure at NG-RAN node1.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
ignore |
||
CHOICE Initiating condition |
M |
YES |
reject |
|||
>RRC Reestab |
||||||
>>CHOICE RRC Reestab Initiated Reporting |
M |
– |
||||
>>>RRC Reestab Reporting without RLF Report |
||||||
>>>>Failure cell PCI |
M |
9.2.2.10 |
Physical Cell Identifier |
– |
||
>>>>Re-establishment cell CGI |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
– |
|||
>>>>C-RNTI |
M |
BIT STRING (SIZE (16)) |
C-RNTI contained in the RRCRe-establishment Request message (TS 38.331 [10]) or in the RRCConnectionReestablishmentRequest message (TS 36.331 [14]) |
– |
||
>>>>ShortMAC-I |
M |
BIT STRING (SIZE (16)) |
ShortMAC-I contained in the RRCRe-establishment Request message (TS 38.331 [10]) or in the RRCConnectionReestablishmentRequest message (TS 36.331 [14]) |
– |
||
>>>>RRC Conn Reestab Indicator |
O |
ENUMERATED (reconfigurationFailure, handoverFailure, otherFailure, …) |
YES |
ignore |
||
>>>RRC Reestab Reporting with RLF Report |
||||||
>>>>UE RLF Report Container |
M |
9.2.2.59 |
nr-RLF-Report-r16 IE contained in the UEInformationResponse message (TS 38.331 [10]) or RLF-Report-r9 IE contained in the UEInformationResponse message (TS 36.331 [14]) |
– |
||
>RRC Setup |
||||||
>>CHOICE RRC Setup Initiated Reporting |
M |
– |
||||
>>>RRC Setup Reporting with RLF Report |
||||||
>>>>UE RLF Report Container |
M |
9.2.2.59 |
nr-RLF-Report-r16 IE contained in the UEInformationResponse message (TS 38.331 [10]) or RLF-Report-r9 IE contained in the UEInformationResponse message (TS 36.331 [14]) |
– |
9.1.3.17 HANDOVER REPORT
This message is sent by NG-RAN node1 to NG-RAN node2 to report a handover failure event, or other critical mobility problem.
Direction: NG-RAN node 1 NG-RAN node 2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
ignore |
||
Handover Report Type |
M |
ENUMERATED (HO too early, HO to wrong cell, Inter-system ping-pong. …) |
YES |
ignore |
||
Handover Cause |
M |
Cause 9.2.3.2 |
Indicates handover cause employed for handover from NG-RAN node 2 |
YES |
ignore |
|
Source cell CGI |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
NG-RAN CGI of source cell for handover procedure (in NG-RAN node 2) |
YES |
ignore |
|
Target cell CGI |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
NG-RAN CGI of target cell for handover procedure (in NG-RAN node 1). If the Handover Report Type is set to "Inter-system ping-pong", it contains the target cell of the inter system handover from the other system to NG-RAN node 1 cell |
YES |
ignore |
|
Re-establishment cell CGI |
C- ifHandoverReportType HoToWrongCell |
Global Cell Identity 9.2.2.73 |
CGI of cell where UE attempted re-establishment or where UE successfully re- connected after the failure |
YES |
ignore |
|
Target cell in E-UTRAN |
C- ifHandoverReportType Intersystempingpong |
OCTET STRING |
Encoded according to Global Cell ID in the Last Visited E-UTRAN Cell Information IE, as defined in in TS 36.413 [31] |
YES |
ignore |
|
Source cell C-RNTI |
O |
BIT STRING (SIZE (16)) |
C-RNTI allocated at the source NG-RAN node (in NG-RAN node 2) |
YES |
ignore |
|
Mobility Information |
O |
BIT STRING (SIZE (32)) |
Information provided in the HANDOVER REQUEST message or in the SN STATUS TRANSFER message from NG-RAN node 2. |
YES |
ignore |
|
UE RLF Report Container |
O |
9.2.2.59 |
The UE RLF Report Container IE received in the FAILURE INDICATION message. |
YES |
ignore |
|
CHO Configuration |
O |
9.2.2.76 |
YES |
ignore |
Condition |
Explanation |
ifHandoverReportType HoToWrongCell |
This IE shall be present if the Handover Report Type IE is set to the value "HO to wrong cell" |
ifHandoverReportType Intersystempingpong |
This IE shall be present if the Handover Report Type IE is set to the value "Inter-system ping-pong" |
9.1.3.18 RESOURCE STATUS REQUEST
This message is sent by NG-RAN node1 to NG-RAN node2 to initiate the requested measurement according to the parameters given in the message.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node1 |
YES |
reject |
|
NG-RAN node2 Measurement ID |
C-ifRegistrationRequestStoporAdd |
INTEGER (1..4095,…) |
Allocated by NG-RAN node2 |
YES |
ignore |
|
Registration Request |
M |
ENUMERATED(start, stop, add, …) |
Type of request for which the resource status is required. |
YES |
reject |
|
Report Characteristics |
C-ifRegistrationRequestStart |
BITSTRING (SIZE(32)) |
Each position in the bitmap indicates measurement object the NG-RAN node2 is requested to report. First Bit = PRB Periodic, Second Bit = TNL Capacity Ind Periodic, Third Bit = Composite Available Capacity Periodic, Fourth Bit =Number of Active UEs Periodic, Fifth Bit =RRC connections Periodic, Sixth Bit = NR-U Channel List Periodic. Other bits shall be ignored by the NG-RAN node2. |
YES |
reject |
|
Cell To Report List |
0..1 |
Cell ID list to which the request applies. |
YES |
ignore |
||
>Cell To Report Item |
1 .. <maxnoofCellsinNG-RANnode> |
– |
||||
>>Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
– |
|||
>>SSB To Report List |
0..1 |
SSB list to which the request applies. |
– |
|||
>>>SSB To Report Item |
1 .. < maxnoofSSBAreas> |
– |
||||
>>>>SSB-Index |
M |
INTEGER (0..,63..) |
– |
|||
>>Slice To Report List |
0..1 |
S-NSSAI list to which the request applies. |
– |
|||
>>>Slice To Report Item |
1 .. < maxnoofBPLMNs > |
– |
||||
>>>>PLMN Identity |
M |
9.2.2.4 |
Broadcast PLMN |
– |
||
>>>>S-NSSAI List |
1 |
– |
||||
>>>>>S-NSSAI Item |
1 .. < maxnoofSliceItems> |
– |
||||
>>>>>>S-NSSAI |
M |
S-NSSAI 9.2.3.21 |
– |
|||
Reporting Periodicity |
O |
ENUMERATED(500ms, 1000ms, 2000ms, 5000ms, 10000ms, …) |
Periodicity that can be used for reporting ofindicated measurements. Also used as the averaging window length for all measurement object if supported. |
YES |
ignore |
Condition |
Explanation |
ifRegistrationRequestStoporAdd |
This IE shall be present if the Registration Request IE is set to the value "stop" or "add". |
ifRegistrationRequestStart |
This IE shall be present if the Registration Request IE is set to the value "start". |
Range bound |
Explanation |
maxnoofCellsinNG-RANnode |
Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
maxnoofSSBAreas |
Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
maxnoofSliceItems |
Maximum no. of signalled slice support items. Value is 1024. |
9.1.3.19 RESOURCE STATUS RESPONSE
This message is sent by NG-RAN node2 to NG-RAN node1 to indicate that the requested measurement, for all of the measurement objects included in the measurement is successfully initiated.
Direction: NG-RAN node2 NG-RAN node1
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node1 |
YES |
reject |
|
NG-RAN node2 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node2 |
YES |
reject |
|
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
9.1.3.20 RESOURCE STATUS FAILURE
This message is sent by the NG-RAN node2 to NG-RAN node1 to indicate that for any of the requested measurement objects the measurement cannot be initiated.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node1 |
YES |
reject |
|
NG-RAN node2 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node2 |
YES |
reject |
|
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.3 |
YES |
ignore |
9.1.3.21 RESOURCE STATUS UPDATE
This message is sent by NG-RAN node2 to NG-RAN node1 to report the results of the requested measurements.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
ignore |
||
NG-RAN node1 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node1 |
YES |
reject |
|
NG-RAN node2 Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by NG-RAN node2 |
YES |
reject |
|
Cell Measurement Result |
1 |
YES |
ignore |
|||
>Cell Measurement Result Item |
1 .. < maxnoofCellsinNG-RANnode > |
YES |
ignore |
|||
>>Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
– |
|||
>>Radio Resource Status |
O |
9.2.2.50 |
– |
|||
>>TNL Capacity Indicator |
O |
9.2.2.49 |
– |
|||
>>Composite Available Capacity Group |
O |
9.2.2.51 |
– |
|||
>>Slice Available Capacity |
O |
9.2.2.55 |
– |
|||
>>Number of Active UEs |
O |
9.2.2.62 |
–- |
|||
>>RRC Connections |
O |
9.2.2.56 |
– |
|||
>>NR-U Channel List |
0..1 |
YES |
ignore |
|||
>>>NR-U Channel Item |
1..<maxnoofNR-UChannelIDs> |
– |
||||
>>>>NR-U Channel ID |
M |
INTEGER (1.. maxnoofNR-UChannelIDs, …) |
The NR-U channel utilised in the last reporting period |
– |
||
>>>>Channel occupancy time percentage DL |
M |
INTEGER (0..100) |
The percentage of time for which the channel resources have been utilised for DL traffic served by the corresponding NR-U Channel of the serving cell. Value 100 corresponds to the duration between consecutive reporting. |
– |
||
>>>>Energy Detection Threshold DL |
M |
INTEGER (-100..-50,…) |
Average ED Threshold used for DL channel sensing at the gNB. Value is in dBm. |
– |
Range bound |
Explanation |
maxnoofCellsinNG-RANnode |
Maximum no. cells that can be served by a NG-RAN node. Value is 16384. |
maxnoofNR-UChannelIDs |
Maximum no. NR-U channel IDs in a cell. Value is 16. |
9.1.3.22 MOBILITY CHANGE REQUEST
This message is sent by NG-RAN node1 to NG-RAN node2 to initiate adaptation of mobility parameters.
Direction: NG-RAN node1 NG-RAN node2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
reject |
||
NG-RAN node2 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
reject |
||
NG-RAN node1 Mobility Parameters |
O |
Mobility Parameters Information 9.2.2.60 |
Configuration change in NG-RAN node1 cell |
YES |
ignore |
|
NG-RAN node2 Proposed Mobility Parameters |
M |
Mobility Parameters Information 9.2.2.60 |
Proposed configuration change in NG-RAN node2 cell |
YES |
reject |
|
Cause |
M |
9.2.3.2 |
YES |
reject |
||
SSB Offsets List |
0..1 |
YES |
ignore |
|||
>SSB Offsets Item |
1 .. < maxnoofSSBAreas> |
– |
||||
>>NG-RAN node1 SSB Offset Information |
O |
SSB Offset Information 9.2.2.77 |
Configuration change in NG-RAN node 1 SSB |
– |
||
>>NG-RAN node2 SSB Offset Information |
M |
SSB Offset Information 9.2.2.77 |
Proposed configuration change in NG-RAN node2 SSB |
– |
Range bound |
Explanation |
maxnoofSSBAreas |
Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
9.1.3.23 MOBILITY CHANGE ACKNOWLEDGE
This message is sent by NG-RAN node2 to indicate to NG-RAN node1 that Proposed Mobility Parameters proposed by NG-RAN node1 were accepted.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
reject |
||
NG-RAN node2 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.2.3.2 |
YES |
ignore |
9.1.3.24 MOBILITY CHANGE FAILURE
This message is sent by the NG-RAN node2 to indicate to NG-RAN node1 that Proposed Mobility Parameters proposed by NG-RAN node1 were refused.
Direction: NG-RAN node2 NG-RAN node1.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
reject |
||
NG-RAN node1 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
ignore |
||
NG-RAN node2 Cell ID |
M |
Global NG-RAN Cell Identity 9.2.2.27 |
YES |
ignore |
||
Cause |
M |
9.2.3.2 |
YES |
ignore |
||
Mobility Parameters Modification Range |
O |
9.2.2.61 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.3.2 |
YES |
ignore |
||
NG-RAN node2 SSB Offsets Modification Range |
0 .. < maxnoofSSBAreas> |
YES |
ignore |
|||
>SSB Offset Modification Range |
M |
9.2.2.78 |
– |
Range bound |
Explanation |
maxnoofSSBAreas |
Maximum no. SSB Areas that can be served by a NG-RAN node cell. Value is 64. |
9.1.3.25 ACCESS AND MOBILITY INDICATION
This message is sent by NG-RAN node1 to transfer access and mobility related information to NG-RAN node2.
Direction: NG-RAN node 1 NG-RAN node 2.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.2.3.1 |
YES |
ignore |
||
RACH Report List |
0..1 |
YES |
ignore |
|||
>RACH Report List Item |
1 .. <maxnoofRACHReports> |
EACH |
ignore |
|||
>>RACH Report Container |
O |
OCTET STRING |
RA-ReportList-r16 IE as defined in subclause 6.2.2 in TS 38.331 [10]. |
YES |
ignore |
|
>>UE Assistant Identifier |
O |
NG-RAN node UE XnAP ID 9.2.3.16 |
YES |
ignore |
||
Successful HO Report List |
0..1 |
YES |
ignore |
|||
>Successful HO Report List Item |
1 .. <maxnoofSuccessfulHOReports> |
– |
||||
>>Successful HO Report Container |
O |
OCTET STRING |
SuccessHO-Report-r17 IE as defined in subclause 6.2.2 in TS 38.331 [10]. |
– |
Range bound |
Explanation |
maxnoofRACHReports |
Maximum no. of RACH Reports, the maximum value is 64. |
maxnoofSuccessfulHOReports |
Maximum no. of Successful HO Reports, the maximum value is 64. |