9.2 Message Functional Definition and Content
38.4633GPPE1 Application Protocol (E1AP)NG-RANRelease 16TS
9.2.1 Interface Management messages
9.2.1.1 RESET
This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to request that the E1 interface, or parts of the E1 interface, to be reset.
Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
CHOICE Reset Type |
M |
YES |
reject |
|||
>E1 interface |
||||||
>>Reset All |
M |
ENUMERATED (Reset all,…) |
– |
|||
>Part of E1 interface |
||||||
>>UE-associated logical E1-connection list |
1 |
– |
||||
>>>UE-associated logical E1-connection Item |
1 .. <maxnoofIndividualE1ConnectionsToReset> |
EACH |
reject |
|||
>>>>gNB-CU-CP UE E1AP ID |
O |
9.3.1.4 |
– |
|||
>>>>gNB-CU-UP UE E1AP ID |
O |
9.3.1.5 |
– |
Range bound |
Explanation |
maxnoofIndividualE1ConnectionsToReset |
Maximum no. of UE-associated logical E1-connections allowed to reset in one message. Value is 65536. |
9.2.1.2 RESET ACKNOWLEDGE
This message is sent by both the gNB-CU-CP and the gNB-CU-UP as a response to a RESET message.
Direction: gNB-CU-UP → gNB-CU-CP and gNB-CU-CP → gNB-CU-UP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
UE-associated logical E1-connection list |
0..1 |
YES |
ignore |
|||
>UE-associated logical E1-connection Item |
1 .. <maxnoofIndividualE1ConnectionsToReset> |
EACH |
ignore |
|||
>>gNB-CU-CP UE E1AP ID |
O |
9.3.1.4 |
– |
|||
>>gNB-CU-UP UE E1AP ID |
O |
9.3.1.5 |
– |
|||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Range bound |
Explanation |
maxnoofIndividualE1ConnectionsToReset |
Maximum no. of UE-associated logical E1-connections allowed to reset in one message. Value is 65536. |
9.2.1.3 ERROR INDICATION
This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to indicate that some error has been detected in the node.
Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
ignore |
||
Transaction ID |
M |
9.3.1.53 |
This IE is ignored if received in UE associated signalling message. |
YES |
reject |
|
gNB-CU-CP UE E1AP ID |
O |
9.3.1.4 |
YES |
ignore |
||
gNB-CU-UP UE E1AP ID |
O |
9.3.1.5 |
YES |
ignore |
||
Cause |
O |
9.3.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.4 GNB-CU-UP E1 SETUP REQUEST
This message is sent by the gNB-CU-UP to transfer information for a TNL association.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-UP ID |
M |
9.3.1.15 |
YES |
reject |
||
gNB-CU-UP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-UP. |
YES |
ignore |
|
CN Support |
M |
ENUMERATED (EPC. 5GC, both, …) |
YES |
reject |
||
Supported PLMNs |
1..<maxnoofSPLMNs> |
Supported PLMNs |
YES |
reject |
||
>PLMN Identity |
M |
9.3.1.7 |
– |
– |
||
>Slice Support List |
O |
9.3.1.8 |
Supported S-NSSAIs per PLMN. |
– |
– |
|
>Extended Slice Support List |
O |
9.3.1.94 |
Additional Supported S-NSSAIs per PLMN. |
YES |
reject |
|
>NR CGI Support List |
O |
9.3.1.36 |
Supported cells. |
– |
– |
|
>QoS Parameters Support List |
O |
9.3.1.37 |
Supported QoS parameters per PLMN. |
– |
– |
|
>NPN Support Information |
O |
9.3.1.83 |
YES |
reject |
||
>Extended NR CGI Support List |
O |
9.3.1.97 |
Additional supported cells per PLMN. |
YES |
ignore |
|
gNB-CU-UP Capacity |
O |
9.3.1.56 |
YES |
ignore |
||
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-UP Name |
O |
9.3.1.95 |
YES |
ignore |
Range bound |
Explanation |
maxnoofSPLMNs |
Maximum no. of Supported PLMN Ids. Value is 12. |
9.2.1.5 GNB-CU-UP E1 SETUP RESPONSE
This message is sent by the gNB-CU-CP to transfer information for a TNL association.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-CP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-CP. |
YES |
ignore |
|
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-CP Name |
O |
9.3.1.96 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.6 GNB-CU-UP E1 SETUP FAILURE
This message is sent by the gNB-CU-CP to indicate E1 Setup failure.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Time To wait |
O |
9.3.1.6 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.7 GNB-CU-CP E1 SETUP REQUEST
This message is sent by the gNB-CU-CP to transfer information for a TNL association.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-CP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-CP. |
YES |
ignore |
|
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-CP Name |
O |
9.3.1.95 |
YES |
ignore |
9.2.1.8 GNB-CU-CP E1 SETUP RESPONSE
This message is sent by the gNB-CU-UP to transfer information for a TNL association.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-UP ID |
M |
9.3.1.15 |
YES |
reject |
||
gNB-CU-UP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-UP. |
YES |
ignore |
|
CN Support |
M |
ENUMERATED (EPC. 5GC, both, …) |
YES |
reject |
||
Supported PLMNs |
1..<maxnoofSPLMNs> |
Supported PLMNs |
YES |
reject |
||
>PLMN Identity |
M |
9.3.1.7 |
– |
– |
||
>Slice Support List |
O |
9.3.1.8 |
Supported S-NSSAIs per PLMN. |
– |
– |
|
>Extended Slice Support List |
O |
9.3.1.94 |
Additional Supported S-NSSAIs per PLMN. |
YES |
reject |
|
>NR CGI Support List |
O |
9.3.1.36 |
Supported cells. |
– |
– |
|
>QoS Parameters Support List |
O |
9.3.1.37 |
Supported QoS parameters per PLMN. |
– |
– |
|
>NPN Support Information |
O |
9.3.1.83 |
YES |
reject |
||
>Extended NR CGI Support List |
O |
9.3.1.97 |
Additional supported cells per PLMN. |
YES |
ignore |
|
gNB-CU-UP Capacity |
O |
9.3.1.56 |
YES |
ignore |
||
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-UP Name |
O |
9.3.1.95 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Range bound |
Explanation |
maxnoofSPLMNs |
Maximum no. of Supported PLMN Ids. Value is 12. |
9.2.1.9 GNB-CU-CP E1 SETUP FAILURE
This message is sent by the gNB-CU-UP to indicate E1 Setup failure.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Time To wait |
O |
9.3.1.6 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.10 GNB-CU-UP CONFIGURATION UPDATE
This message is sent by the gNB-CU-UP to transfer updated information for a TNL association.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-UP ID |
O |
9.3.1.15 |
YES |
reject |
||
gNB-CU-UP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-UP. |
YES |
ignore |
|
Supported PLMNs |
0..<maxnoofSPLMNs> |
Supported PLMNs |
YES |
reject |
||
>PLMN Identity |
M |
9.3.1.7 |
– |
– |
||
>Slice Support List |
O |
9.3.1.8 |
Supported S-NSSAIs per PLMN. |
– |
– |
|
>Extended Slice Support List |
O |
9.3.1.94 |
Additional Supported S-NSSAIs per PLMN. |
YES |
reject |
|
>NR CGI Support List |
O |
9.3.1.36 |
Supported cells. |
– |
– |
|
>QoS Parameters Support List |
O |
9.3.1.37 |
Supported QoS parameters per PLMN. |
– |
– |
|
>NPN Support Information |
O |
9.3.1.83 |
YES |
reject |
||
>Extended NR CGI Support List |
O |
9.3.1.97 |
Additional supported cells per PLMN. |
YES |
ignore |
|
gNB-CU-UP Capacity |
O |
9.3.1.56 |
YES |
ignore |
||
gNB-CU-UP TNLA To Remove List |
0..1 |
YES |
reject |
|||
>gNB-CU-UP TNLA To Remove Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-UP. |
– |
– |
|
>>TNLA Transport Layer Address gNB-CU-CP |
O |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP. |
– |
– |
|
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-UP Name |
O |
9.3.1.96 |
YES |
ignore |
Range bound |
Explanation |
maxnoofSPLMNs |
Maximum no. of Supported PLMN Ids. Value is 12. |
maxnoofTNLAssociations |
Maximum numbers of TNL Associations between the gNB-CU-UP and the gNB-CU-CP. Value is 32. |
9.2.1.11 GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE
This message is sent by a gNB-CU-CP to a gNB-CU-UP to acknowledge update of information for a TNL association.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
||
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
9.2.1.12 GNB-CU-UP CONFIGURATION UPDATE FAILURE
This message is sent by the gNB-CU-CP to indicate gNB-CU-UP Configuration Update failure.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Time To wait |
O |
9.3.1.6 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.13 GNB-CU-CP CONFIGURATION UPDATE
This message is sent by the gNB-CU-CP to transfer updated information for a TNL association.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-CP Name |
O |
PrintableString(SIZE(1..150,…)) |
Human readable name of the gNB-CU-CP |
YES |
ignore |
|
gNB-CU-CP TNLA To Add List |
0..1 |
YES |
ignore |
|||
>gNB-CU-CP TNLA To Add Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Information |
M |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP. |
– |
– |
|
>>TNLA Usage |
M |
ENUMERATED (ue, non-ue, both, …) |
Indicates whether the TNLA is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.462 [18]. |
– |
– |
|
gNB-CU-CP TNLA To Remove List |
0..1 |
YES |
ignore |
|||
>gNB-CU-CP TNLA To Remove Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP. |
– |
– |
|
>>TNLA Transport Layer Address gNB-CU-UP |
O |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-UP. |
YES |
reject |
|
gNB-CU-CP TNLA To Update List |
0..1 |
YES |
ignore |
|||
>gNB-CU-CP TNLA To Update Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Address 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP. |
– |
– |
|
>>TNLA Usage |
O |
ENUMERATED (ue, non-ue, both, …) |
Indicates whether the TNLA is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.462 [18]. |
– |
– |
|
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
||
Extended gNB-CU-CP Name |
O |
9.3.1.95 |
YES |
ignore |
Range bound |
Explanation |
maxnoofTNLAssociations |
Maximum numbers of TNL Associations between the gNB-CU-CP and the gNB-CU-UP. Value is 32. |
9.2.1.14 GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE
This message is sent by a gNB-CU-UP to a gNB-CU-CP to acknowledge update of information for a TNL association.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-CP TNLA Setup List |
0..1 |
YES |
ignore |
|||
>gNB-CU-CP TNLA Setup Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP |
– |
– |
|
gNB-CU-CP TNLA Failed to Setup List |
0..1 |
YES |
ignore |
|||
>gNB-CU-CP TNLA Failed To Setup Item IEs |
1..<maxnoofTNLAssociations> |
– |
– |
|||
>>TNLA Transport Layer Address |
M |
CP Transport Layer Information 9.3.2.2 |
Transport Layer Address of the gNB-CU-CP |
– |
– |
|
>>Cause |
M |
9.3.1.2 |
||||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
||
Transport Network Layer Address Info |
O |
9.3.2.7 |
YES |
ignore |
Range bound |
Explanation |
maxnoofTNLAssociations |
Maximum numbers of TNL Associations between the gNB-CU-CP and the gNB-CU-UP. Value is 32. |
9.2.1.15 GNB-CU-CP CONFIGURATION UPDATE FAILURE
This message is sent by the gNB-CU-UP to indicate gNB-CU-CP Configuration Update failure.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Time To wait |
O |
9.3.1.6 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.16 E1 RELEASE REQUEST
This message is sent by both the gNB-CU-CP and the gNB-CU-UP and is used to request the release of the E1 interface.
Direction: gNB-CU-CP → gNB-CU-UP and gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
9.2.1.17 E1 RELEASE RESPONSE
This message is sent by both the gNB-CU-CP and the gNB-CU-UP as a response to an E1 RELEASE REQUEST message.
Direction: gNB-CU-UP → gNB-CU-CP and gNB-CU-CP → gNB-CU-UP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.18 GNB-CU-UP STATUS INDICATION
This message is sent by the gNB-CU-UP to indicate to the gNB-CU-CP its status of overload.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-UP Overload Information |
M |
ENUMERATED (overloaded, not-overloaded) |
YES |
reject |
9.2.1.19 RESOURCE STATUS REQUEST
This message is sent by an gNB-CU-CP to gNB-CU-UP to initiate the requested measurement according to the parameters given in the message.
Direction: gNB-CU-CP → gNB-CU-UP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
9.3.1.1 |
YES |
reject |
|||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
|||
gNB-CU-CP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-CP |
YES |
reject |
||
gNB-CU-UP Measurement ID |
C-ifRegistrationRequestStop |
INTEGER (1..4095,…) |
Allocated by gNB-CU-UP |
YES |
ignore |
||
Registration Request |
M |
ENUMERATED(start, stop, …) |
Type of request for which the resource status is required. |
YES |
ignore |
||
Report Characteristics |
C-ifRegistrationRequestStart |
BITSTRING (SIZE(32)) |
Each position in the bitmap indicates measurement object the gNB-CU-UP is requested to report. First Bit = TNL Available Capacity Ind Periodic, Second Bit = HW Capacity Ind Periodic. Other bits shall be ignored by the gNB-CU-UP. |
YES |
reject |
||
Reporting Periodicity |
O |
ENUMERATED (500ms, 1000ms, 2000ms, 5000ms, 10000ms, 20000ms, 30000ms, 40000ms, 50000ms, 60000ms, 70000ms, 80000ms, 90000ms, 100000ms, 110000ms, 120000ms, …) |
Periodicity that can be used for reporting. Also used as the averaging window length for all measurement object if supported. |
YES |
ignore |
Condition |
Explanation |
ifRegistrationRequestStop |
This IE shall be present if the Registration Request IE is set to the value “stop” |
ifRegistrationRequestStart |
This IE shall be present if the Registration Request IE is set to the value "start". |
9.2.1.20 RESOURCE STATUS RESPONSE
This message is sent by the gNB-CU-UP to indicate that the requested measurement, for all the measurement objects included in the measurement is successfully initiated.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
gNB-CU-CP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-CP |
YES |
reject |
|
gNB-CU-UP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-UP |
YES |
ignore |
|
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.1.21 RESOURCE STATUS FAILURE
This message is sent by the gNB-CU-UP to indicate that for any of the requested measurement objects the measurement cannot be initiated.
Direction: gNB-CU-UP → gNB-CU-CP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
9.3.1.1 |
YES |
reject |
|||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
|||
gNB-CU-CP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-CP |
YES |
reject |
||
gNB-CU-UP Measurement ID |
C-ifRegistrationRequestStop |
INTEGER (1..4095,…) |
Allocated by gNB-CU-UP |
YES |
ignore |
||
Cause |
M |
9.3.1.2 |
Ignored by the receiver when the Complete Failure Cause Information IE is included |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Condition |
Explanation |
ifRegistrationRequestStop |
This IE shall be present if the Registration Request IE is set to the value “stop” |
9.2.1.22 RESOURCE STATUS UPDATE
This message is sent by gNB-CU-UP to gNB-CU-CP to report the results of the requested measurements.
Direction: gNB-CU-UP → gNB-CU-CP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
|
Message Type |
M |
9.3.1.1 |
YES |
Ignore |
|||
Transaction ID |
M |
9.3.1.53 |
YES |
Reject |
|||
gNB-CU-CP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-CP |
YES |
Reject |
||
gNB-CU-UP Measurement ID |
M |
INTEGER (1..4095,…) |
Allocated by gNB-CU-UP |
YES |
Reject |
||
TNL Available Capacity Indicator |
O |
9.3.1.72 |
|||||
HW Capacity Indicator |
O |
9.3.1.73 |
Range bound |
Explanation |
maxnoofSPLMNs |
Maximum no. of Supported PLMN Ids. Value is 12. |
maxnoofSliceItems |
Maximum no. of signalled slice support items. Value is 1024. |
9.2.2 Bearer Context Management messages
9.2.2.1 BEARER CONTEXT SETUP REQUEST
This message is sent by the gNB-CU-CP to request the gNB-CU-UP to setup a bearer context.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
Security Information |
M |
9.3.1.10 |
YES |
reject |
||
UE DL Aggregate Maximum Bit Rate |
M |
Bit Rate 9.3.1.20 |
YES |
reject |
||
UE DL Maximum Integrity Protected Data Rate |
O |
Bit Rate 9.3.1.20 |
The Bit Rate is a portion of the UE’s Maximum Integrity Protected Data Rate, and is enforced by the gNB-CU-UP node. |
YES |
reject |
|
Serving PLMN |
M |
PLMN Identity 9.3.1.7 |
YES |
ignore |
||
Activity Notification Level |
M |
9.3.1.67 |
YES |
reject |
||
UE Inactivity Timer |
O |
Inactivity Timer 9.3.1.54 |
Included if the Activity Notification Level is set to UE. |
– |
– |
|
Bearer Context Status Change |
O |
ENUMERATED (Suspend, Resume, …) |
Indicates the status of the Bearer Context |
YES |
reject |
|
CHOICE System |
M |
YES |
reject |
|||
>E-UTRAN |
||||||
>>DRB To Setup List |
M |
DRB To Setup List E-UTRAN 9.3.3.1 |
YES |
reject |
||
>>Subscriber Profile ID for RAT/Frequency priority |
O |
9.3.1.69 |
YES |
ignore |
||
>>Additional RRM Policy Index |
O |
9.3.1.70 |
YES |
Ignore |
||
>NG-RAN |
||||||
>>PDU Session Resource To Setup List |
M |
9.3.3.2 |
YES |
reject |
||
RAN UE ID |
O |
OCTET STRING (SIZE(8)) |
YES |
ignore |
||
gNB-DU ID |
O |
9.3.1.65 |
Included whenever it is known by the gNB-CU-CP |
YES |
ignore |
|
Trace Activation |
O |
9.3.1.68 |
YES |
ignore |
||
NPN Context Information |
O |
9.3.1.84 |
YES |
reject |
||
Management Based MDT PLMN List |
O |
MDT PLMN List 9.3.1.89 |
YES |
ignore |
||
CHO Initiation |
O |
ENUMERATED (True, …) |
YES |
reject |
||
Additional Handover Information |
O |
ENUMERATED(Discard PDCP SN, …) |
If set to “Discard PDCP SN”, indicates that the forwarded PDCP SNs have to be removed |
YES |
ignore |
|
Direct Forwarding Path Availability |
O |
9.3.1.98 |
YES |
ignore |
||
gNB-CU-UP UE E1AP ID |
O |
9.3.1.5 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.2 BEARER CONTEXT SETUP RESPONSE
This message is sent by the gNB-CU-UP to confirm the setup of the requested bearer context.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE System |
M |
YES |
reject |
|||
>E-UTRAN |
||||||
>>DRB Setup List |
M |
DRB Setup List E-UTRAN 9.3.3.3 |
YES |
reject |
||
>>DRB Failed List |
O |
DRB Failed List E-UTRAN 9.3.3.4 |
YES |
reject |
||
>NG-RAN |
||||||
>>PDU Session Resource Setup List |
M |
9.3.3.5 |
YES |
reject |
||
>>PDU Session Resource Failed List |
O |
9.3.3.6 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.3 BEARER CONTEXT SETUP FAILURE
This message is sent by the gNB-CU-UP to indicate that the setup of the bearer context was unsuccessful.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
O |
9.3.1.5 |
YES |
ignore |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.2.4 BEARER CONTEXT MODIFICATION REQUEST
This message is sent by the gNB-CU-CP to request the gNB-CU-UP to modify a bearer context.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Security Information |
O |
9.3.1.10 |
YES |
reject |
||
UE DL Aggregate Maximum Bit Rate |
O |
Bit Rate 9.3.1.20 |
YES |
reject |
||
UE DL Maximum Integrity Protected Data Rate |
O |
Bit Rate 9.3.1.20 |
The Bit Rate is a portion of the UE’s Maximum Integrity Protected Data Rate, and is enforced by the gNB-CU-UP node. |
YES |
reject |
|
Bearer Context Status Change |
O |
ENUMERATED (Suspend, Resume, …) |
Indicates the status of the Bearer Context |
YES |
reject |
|
New UL TNL Information Required |
O |
ENUMERATED (required, …) |
Indicates that new UL TNL information has been requested to be provided. |
YES |
reject |
|
UE Inactivity Timer |
O |
Inactivity Timer 9.3.1.54 |
Included if the Activity Notification Level is set to UE. |
– |
– |
|
Data Discard Required |
O |
ENUMERATED (required, …) |
Indicate to discard the DL user data in case of RAN paging failure. |
YES |
ignore |
|
CHOICE System |
O |
YES |
reject |
|||
>E-UTRAN |
||||||
>>DRB To Setup List |
O |
DRB To Setup Modification List E-UTRAN 9.3.3.7 |
YES |
reject |
||
>>DRB To Modify List |
O |
DRB To Modify List E-UTRAN 9.3.3.8 |
YES |
reject |
||
>>DRB To Remove List |
O |
DRB To Remove List E-UTRAN 9.3.3.9 |
YES |
reject |
||
>>Subscriber Profile ID for RAT/Frequency priority |
O |
9.3.1.69 |
YES |
ignore |
||
>>Additional RRM Policy Index |
O |
9.3.1.70 |
YES |
ignore |
||
>NG-RAN |
||||||
>>PDU Session Resource To Setup List |
O |
PDU Session Resource To Setup Modification List 9.3.3.10 |
YES |
reject |
||
>>PDU Session Resource To Modify List |
O |
9.3.3.11 |
YES |
reject |
||
>>PDU Session Resource To Remove List |
O |
9.3.3.12 |
YES |
reject |
||
RAN UE ID |
O |
OCTET STRING (SIZE(8)) |
YES |
ignore |
||
gNB-DU ID |
O |
9.3.1.65 |
YES |
ignore |
||
Activity Notification Level |
O |
9.3.1.67 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.5 BEARER CONTEXT MODIFICATION RESPONSE
This message is sent by the gNB-CU-UP to confirm the modification of the requested bearer context.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE System |
O |
YES |
ignore |
|||
>E-UTRAN |
||||||
>>DRB Setup List |
O |
DRB Setup Modification List E-UTRAN 9.3.3.13 |
YES |
ignore |
||
>>DRB Failed List |
O |
DRB Failed Modification List E-UTRAN 9.3.3.14 |
YES |
ignore |
||
>>DRB Modified List |
O |
DRB Modified List E-UTRAN 9.3.3.15 |
YES |
ignore |
||
>>DRB Failed To Modify List |
O |
DRB Failed To Modify List E-UTRAN 9.3.3.16 |
YES |
ignore |
||
>>Retainability Measurements Information |
O |
9.3.1.71 |
Provides information on all the removed DRB(s), needed for retainability measurements in the gNB-CU-CP |
YES |
ignore |
|
>NG-RAN |
||||||
>>PDU Session Resource Setup List |
O |
PDU Session Resource Setup Modification List 9.3.3.17 |
YES |
reject |
||
>>PDU Session Resource Failed List |
O |
PDU Session Resource Failed Modification List 9.3.3.18 |
YES |
reject |
||
>>PDU Session Resource Modified List |
O |
9.3.3.19 |
YES |
reject |
||
>>PDU Session Resource Failed To Modify List |
O |
9.3.3.20 |
YES |
reject |
||
>>Retainability Measurements Information |
O |
9.3.1.71 |
Provides information on all the removed DRB(s), needed for retainability measurements in the gNB-CU-CP |
YES |
ignore |
|
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.6 BEARER CONTEXT MODIFICATION FAILURE
This message is sent by the gNB-CU-UP to indicate that the modification of the bearer context was unsuccessful.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.2.7 BEARER CONTEXT MODIFICATION REQUIRED
This message is sent by the gNB-CU-UP to inform the gNB-CU-CP that a modification of a bearer context is required (e.g., due to local problems at the gNB-CU-UP).
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE System |
M |
YES |
reject |
|||
>E-UTRAN |
||||||
>>DRB To Modify List |
O |
DRB Required To Modify List E-UTRAN 9.3.3.21 |
YES |
reject |
||
>>DRB To Remove List |
O |
DRB Required To Remove List 9.3.3.22 |
YES |
reject |
||
>NG-RAN |
||||||
>>PDU Session Resource Required To Modify List |
O |
PDU Session Resource Required To Modify List 9.3.3.23 |
YES |
reject |
||
>>PDU Session Resource To Remove List |
O |
9.3.3.12 |
YES |
reject |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.8 BEARER CONTEXT MODIFICATION CONFIRM
This message is sent by the gNB-CU-CP to confirm the modification of the requested bearer context.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE System |
O |
YES |
ignore |
|||
>E-UTRAN |
||||||
>>DRB Modified List |
O |
DRB Confirm Modified List E-UTRAN 9.3.3.24 |
YES |
ignore |
||
>NG-RAN |
||||||
>>PDU Session Resource Modified List |
O |
PDU Session Resource Confirm Modified List 9.3.3.25 |
YES |
Ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.9 BEARER CONTEXT RELEASE COMMAND
This message is sent by the gNB-CU-CP to command the gNB-CU-UP to release an UE-associated logical E1 connection.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
9.2.2.10 BEARER CONTEXT RELEASE COMPLETE
This message is sent by the gNB-CU-UP to confirm the release of the UE-associated logical E1 connection.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
||
Retainability Measurements Information |
O |
9.3.1.71 |
Provides information on all the removed DRB(s) and QoS Flow(s), needed for retainability measurements in the gNB-CU-CP |
YES |
ignore |
9.2.2.11 BEARER CONTEXT RELEASE REQUEST
This message is sent by the gNB-CU-UP to request the release of an UE-associated logical E1 connection.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
DRB Status List |
0.. 1 |
YES |
ignore |
|||
>DRB Status Item |
1..<maxnoofDRBs> |
– |
– |
|||
>>DRB ID |
M |
9.3.1.16 |
– |
– |
||
>>PDCP DL Count |
O |
PDCP Count 9.3.1.35 |
PDCP count for next DL packet to be assigned. |
– |
– |
|
>>PDCP UL Count |
O |
PDCP Count 9.3.1.35 |
PDCP count for first un-acknowledged UL packet. |
– |
– |
|
Cause |
M |
9.3.1.2 |
YES |
ignore |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
9.2.2.12 BEARER CONTEXT INACTIVITY NOTIFICATION
This message is sent by the gNB-CU-UP to provide information about the UE activity to the gNB-CU-CP.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE Activity Information |
M |
YES |
reject |
|||
>DRB Activity List |
1 |
Used if the Activity Notification Level IE is set as “DRB” in BEARER CONTEXT SETUP Request message |
YES |
reject |
||
>>DRB Activity Item |
1 .. <maxnoofDRBs> |
– |
– |
|||
>>>DRB ID |
M |
9.3.1.16 |
– |
– |
||
>>>DRB Activity |
M |
ENUMERATED (Active, Not active, …) |
– |
– |
||
>PDU Session Resource Activity List |
1 |
Used if the Activity Notification Level IE is set as “PDU Session” in the BEARER CONTEXT SETUP Request message |
YES |
reject |
||
>>PDU Session Resource Activity Item |
1 .. <maxnoofPDUSessionResource> |
– |
– |
|||
>>>PDU Session ID |
M |
9.3.1.21 |
– |
– |
||
>>>PDU Session Resource Activity |
M |
ENUMERATED (Active, Not active, …) |
– |
– |
||
>UE Activity |
M |
ENUMERATED (Active, Not active, …) |
Used if the Activity Notification Level IE is set as “UE” in the BEARER CONTEXT SETUP Request message |
YES |
reject |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRB for a UE, the maximum value is 32. |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.13 DL DATA NOTIFICATION
This message is sent by the gNB-CU-UP to provide information about the DL data detection to the gNB-CU-CP.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Paging Priority Indicator (PPI) |
O |
9.3.1.55 |
YES |
ignore |
||
PDU Session To Notify List |
O |
YES |
ignore |
|||
>PDU Session To Notify Item |
1..<maxnoofPDUSessionResource> |
– |
– |
|||
>>PDU Session ID |
M |
9.3.1.21 |
– |
– |
||
>>QoS Flow List |
M |
9.3.1.12 |
– |
– |
Range bound |
Explanation |
maxnoofPDUSessionResource |
Maximum no. of PDU Sessions for a UE. Value is 256. |
9.2.2.14 DATA USAGE REPORT
This message is sent by the gNB-CU-UP to report data volumes.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Data Usage Report List |
M |
9.3.1.44 |
YES |
ignore |
9.2.2.15 GNB-CU-UP COUNTER CHECK REQUEST
This message is sent by the gNB-CU-UP to request the verification of the value of the PDCP COUNTs associated with the DRBs established in the gNB-CU-UP.
Direction: gNB-CU-UP → gNB-CU-CP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
CHOICE System |
M |
YES |
reject |
|||
>E-UTRAN |
||||||
>>DRBs Subject to Counter Check List |
1 |
YES |
ignore |
|||
>>>DRBs Subject to Counter Check Item |
1 .. <maxnoof DRBs> |
– |
– |
|||
>>>>DRB ID |
M |
9.3.1.16 |
– |
– |
||
>>>>PDCP UL Count |
M |
PDCP Count 9.3.1.35 |
Indicates the value of uplink COUNT associated to this DRB, as specified in TS 38.331 [8]. |
– |
– |
|
>>>>PDCP DL Count |
M |
PDCP Count 9.3.1.35 |
Indicates the value of downlink COUNT associated to this DRB, as specified in TS 38.331 [8]. |
– |
– |
|
>NG-RAN |
||||||
>>DRBs Subject to Counter Check List |
1 |
YES |
ignore |
|||
>>>DRBs Subject to Counter Check Item |
1 .. <maxnoof DRBs> |
– |
– |
|||
>>>>PDU Session ID |
M |
9.3.1.21 |
– |
– |
||
>>>>DRB ID |
M |
9.3.1.16 |
– |
– |
||
>>>>PDCP UL Count |
M |
PDCP Count 9.3.1.35 |
Indicates the value of uplink COUNT associated to this DRB, as specified in TS 38.331 [8]. |
– |
– |
|
>>>>PDCP DL Count |
M |
PDCP Count 9.3.1.35 |
Indicates the value of downlink COUNT associated to this DRB, as specified in TS 38.331 [8]. |
– |
– |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRBs for a UE. Value is 32. |
9.2.2.16 UL DATA NOTIFICATION
This message is sent by the gNB-CU-UP to provide information about the UL data detection to the gNB-CU-CP.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
PDU Session To Notify List |
1 |
YES |
reject |
|||
>PDU Session To Notify Item |
1..<maxnoofPDUSessionResource> |
– |
– |
|||
>>PDU Session ID |
M |
9.3.1.21 |
– |
– |
||
>>QoS Flow List |
M |
9.3.1.12 |
– |
– |
9.2.2.17 MR-DC DATA USAGE REPORT
This message is sent by the gNB-CU-UP to report data volumes when the UE is connected to the 5GC.
Direction: gNB-CU-UP → gNB-CU-CP.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
PDU Session Resource Data Usage List |
1 |
YES |
ignore |
|||
>PDU Session Resource Data Usage Item |
1 .. <maxnoof PDUsessions> |
– |
||||
>>PDU Session ID |
M |
9.3.1.21 |
– |
|||
>>MR-DC Usage Information |
M |
9.3.1.63 |
– |
Range bound |
Explanation |
maxnoofPDUsessions |
Maximum no. of PDU sessions. Value is 256 |
9.2.2.18 EARLY FORWARDING SN TRANSFER
This message is sent by the source gNB-CU-UP to the source gNB-CU-CP to transfer the COUNT value(s) related to early forwarded downlink PDCP SDUs during Conditional Handover or conditional PSCell change.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
DRBs Subject To Early Forwarding List |
M |
1 |
YES |
reject |
||
>DRBs Subject To Early Forwarding Item |
1 .. <maxnoofDRBs> |
– |
– |
|||
>>DRB ID |
M |
9.3.1.16 |
– |
– |
||
>>DL COUNT Value |
M |
PDCP Count 9.3.1.35 |
PDCP-SN and Hyper frame number of the last DL SDU successfully delivered in sequence to the UE, if RLC-AM, and successfully transmitted, if RLC-UM. |
– |
– |
9.2.2.19 GNB-CU-CP MEASUREMENT RESULTS INFORMATION
This message is sent to the gNB-CU-UP to provide the measurement result received by the gNB-CU-CP.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
DRB Measurement Results Information List |
1 |
YES |
reject |
|||
>DRB Measurement Results Information Item |
1 .. <maxnoofDRBs> |
EACH |
reject |
|||
>>DRB ID |
M |
9.3.1.16 |
– |
|||
>>UL D1 Result |
O |
INTEGER (0 .. 10000,…) |
The unit is: 0.1ms |
– |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRB allowed towards one UE, the maximum value is 64. |
9.2.3 Trace Messages
9.2.3.1 TRACE START
This message is sent by the gNB-CU-CP to initiate a trace session for a UE.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
ignore |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Trace Activation |
M |
9.3.1.68 |
YES |
ignore |
9.2.3.2 DEACTIVATE TRACE
This message is sent by the gNB-CU-CP to deactivate a trace session.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
ignore |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Trace ID |
M |
OCTET STRING (SIZE(8)) |
As per Trace ID in Trace Activation IE |
YES |
ignore |
9.2.3.3 CELL TRAFFIC TRACE
This message is sent by the gNB-CU-UP to initiate a trace session for a UE.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
ignore |
||
gNB-CU-CP UE E1AP ID |
M |
9.3.1.4 |
YES |
reject |
||
gNB-CU-UP UE E1AP ID |
M |
9.3.1.5 |
YES |
reject |
||
Trace ID |
M |
OCTET STRING (SIZE(8)) |
The Trace ID IE is composed of the following: Trace Reference defined in TS 32.422 [24] (leftmost 6 octets, with PLMN information coded as in 9.2.3.8), and Trace Recording Session Reference defined in TS 32.422 [24] (last 2 octets). |
YES |
ignore |
|
Trace Collection Entity IP Address |
M |
Transport Layer Address 9.2.2.1 |
For File based Reporting. Defined in TS 32.422 [24]. Should be ignored if URI is present. |
YES |
ignore |
|
Privacy Indicator |
O |
ENUMERATED (Immediate MDT, Logged MDT, …) |
YES |
ignore |
||
Trace Collection Entity URI |
O |
9.3.2.8 |
For Streaming based Reporting. Defined in TS 32.422 [24] Replaces Trace Collection Entity IP Address if present. |
YES |
ignore |
9.2.4 IAB Messages
9.2.4.1 IAB UP TNL ADDRESS UPDATE
This message is sent by the gNB-CU-CP to request the gNB-CU-UP to update the TNL address(es) of the DL F1-U GTP tunnel information.
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
DL UP TNL Address To Update List |
0..1 |
YES |
reject |
|||
> DL UP TNL Address To Update Item IEs |
1..<maxnoofTNLAddresses> |
– |
– |
|||
>>Old TNL Address |
M |
9.3.2.4 |
The old Transport Layer Address of IAB-DU for DL F1-U GTP tunnel. |
– |
– |
|
>>New TNL Address |
M |
9.3.2.4 |
The new Transport Layer Address of IAB-DU for DL F1-U GTP tunnel. |
– |
– |
Range bound |
Explanation |
maxnoofTNLAddresses |
Maximum no. of TNL addresses to be updated in one E1AP procedure. Value is 8. |
9.2.4.2 IAB UP TNL ADDRESS UPDATE ACKNOWLEDGE
This message is sent by the gNB-CU-UP to the gNB-CU-CP to acknowledge the update of TNL address in DL F1-U GTP tunnel information, or provide the updated TNL address(es) of the UL F1-U GTP tunnel information.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
||
UL UP TNL Address to Update List |
0..1 |
YES |
ignore |
|||
> UL UP TNL Address Updated Item IEs |
1..<maxnoofTNLAddresses> |
– |
– |
|||
>>Old TNL Address |
M |
9.3.2.4 |
The old Transport Layer Address of CU-UP for UL F1-U GTP tunnel. |
– |
– |
|
>>New TNL Address |
M |
9.3.2.4 |
The new Transport Layer Address of CU-UP for UL F1-U GTP tunnel. |
– |
– |
Range bound |
Explanation |
maxnoofTNLAddresses |
Maximum no. of TNL addresses updated in one E1AP procedure. Value is 8. |
9.2.4.3 IAB UP TNL ADDRESS UPDATE FAILURE
This message is sent by the gNB-CU-UP to indicate IAB UP TNL address Update failure.
Direction: gNB-CU-UP → gNB-CU-CP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.53 |
YES |
reject |
||
Cause |
M |
9.3.1.2 |
YES |
ignore |
||
Time To wait |
O |
9.3.1.6 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.3.1.3 |
YES |
ignore |
9.2.4.4 IAB PSK NOTIFICATION
This message is sent by the gNB-CU-CP to the gNB-CU-UP to transfer the security key info to be used for the IKEv2 Pre-shared Secret Key (PSK) authentication to protect the F1-U interface of the IAB-node(s).
Direction: gNB-CU-CP → gNB-CU-UP
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Message Type |
M |
9.3.1.1 |
YES |
reject |
||
Transaction ID |
M |
9.3.1.23 |
YES |
reject |
||
IAB-donor-CU-UP PSK Info |
M |
9.3.1.99 |
YES |
reject |