9.2.3 General IE definitions
38.4233GPPNG-RANRelease 17TSXn Application Protocol (XnAP)
9.2.3.1 Message Type
The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Procedure Code |
M |
INTEGER (0..255) |
||
Type of Message |
M |
CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, …) |
9.2.3.2 Cause
The purpose of the Cause IE is to indicate the reason for a particular event for the XnAP protocol.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
CHOICE Cause Group |
M |
|||
>Radio Network Layer |
||||
>>Radio Network Layer Cause |
M |
ENUMERATED Cell not Available, Handover Desirable for Radio Reasons, Handover Target not Allowed, Invalid AMF Set ID, No Radio Resources Available in Target Cell, Partial Handover, Reduce Load in Serving Cell, Resource Optimisation Handover, Time Critical Handover, TXnRELOCoverall Expiry, TXnRELOCprep Expiry, Unknown GUAMI ID, Unknown Local NG-RAN node UE XnAP ID, Inconsistent Remote NG-RAN node UE XnAP ID, Encryption And/Or Integrity Protection Algorithms Not Supported, Multiple PDU Session ID Instances, Unknown PDU Session ID, Unknown QoS Flow ID, Multiple QoS Flow ID Instances, Switch Off Ongoing, Not supported 5QI value, TXnDCoverall Expiry, TXnDCprep Expiry, Action Desirable for Radio Reasons, Reduce Load, Resource Optimisation, Time Critical action, Target not Allowed, No Radio Resources Available, Invalid QoS combination, Encryption Algorithms Not Supported, Procedure cancelled, RRM purpose, Improve User Bit Rate, User Inactivity, Radio Connection With UE Lost, Failure in the Radio Interface Procedure, Bearer Option not Supported, UP integrity protection not possible, UP confidentiality protection not possible, Resources not available for the slice(s), UE Maximum integrity protected data rate reason, CP Integrity Protection Failure, UP Integrity Protection Failure, Slice(s) not supported by NG-RAN, MN Mobility, SN Mobility, Count reaches max value, Unknown Old NG-RAN node UE XnAP ID, PDCP Overload, DRB ID not available, Unspecified, …, UE Context ID not known, Non-relocation of context, CHO-CPC resources to be changed, RSN not available for the UP, NPN access denied, Report Characteristics Empty, Existing Measurement ID, Measurement Temporarily not Available, Measurement not Supported For The Object, UE Power Saving, Not existing NG-RAN node2 Measurement ID, Insufficient UE Capabilities, Normal Release, Value out of allowed range, SCG activation deactivation failure, SCG deactivation failure due to data transmission) |
||
>Transport Layer |
||||
>>Transport Layer Cause |
M |
ENUMERATED Unspecified, |
||
>Protocol |
||||
>>Protocol Cause |
M |
ENUMERATED Semantic Error, Abstract Syntax Error (Falsely Constructed Message), Unspecified, …) |
||
>Misc |
||||
>>Miscellaneous Cause |
M |
ENUMERATED O&M Intervention, Not enough User Plane Processing Resources, Unspecified, …) |
The meaning of the different cause values is specified in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action.
Radio Network Layer cause |
Meaning |
Cell not Available |
The concerned cell is not available. |
Handover Desirable for Radio Reasons |
The reason for requesting handover is radio related. |
Handover Target not Allowed |
Handover to the indicated target cell is not allowed for the UE in question. |
Invalid AMF Set ID |
The target NG-RAN node doesn’t belong to the same AMF Set of the source NG-RAN node, i.e. NG handovers should be attempted instead. |
No Radio Resources Available in Target Cell |
The target cell doesn’t have sufficient radio resources available. |
Partial Handover |
Provides a reason for the handover cancellation. The target NG-RAN node did not admit all PDU Sessions included in the HANDOVER REQUEST and the source NG-RAN node estimated service continuity for the UE would be better by not proceeding with handover towards this particular target NG-RAN node. |
Reduce Load in Serving Cell |
Load in serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing. |
Resource Optimisation Handover |
The reason for requesting handover is to improve the load distribution with the neighbour cells. |
Value out of allowed range |
The action failed because the proposed Handover Trigger parameter change in the NG-RAN node2 Proposed Mobility Parameters IE is too low or too high. |
Time Critical Handover |
Handover is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where the connection is likely to be dropped if handover is not performed. |
TXnRELOCoverall Expiry |
The reason for the action is expiry of timer TXnRELOCoverall. |
TXnRELOCprep Expiry |
Handover Preparation procedure is cancelled when timer TXnRELOCprep expires. |
Unknown GUAMI ID |
The target NG-RAN node belongs to the same AMF Set of the source NG-RAN node and recognizes the AMF Set ID. However, the GUAMI value is unknown to the target NG-RAN node. |
Unknown Local NG-RAN node UE XnAP ID |
The action failed because the receiving NG-RAN node does not recognise the local NG-RAN node UE XnAP ID. |
Inconsistent Remote NG-RAN node UE XnAP ID |
The action failed because the receiving NG-RAN node considers that the received remote NG-RAN node UE XnAP ID is inconsistent.. |
Encryption And/Or Integrity Protection Algorithms Not Supported |
The target NG-RAN node is unable to support any of the encryption and/or integrity protection algorithms supported by the UE. |
Multiple PDU Session ID Instances |
The action failed because multiple instances of the same PDU Session had been provided to the NG-RAN node. |
Unknown PDU Session ID |
The action failed because the PDU Session ID is unknown in the NG-RAN node. |
Unknown QoS Flow ID |
The action failed because the QoS Flow ID is unknown in the NG-RAN node. |
Multiple QoS Flow ID Instances |
The action failed because multiple instances of the same QoS flow had been provided to the NG-RAN node. |
Switch Off Ongoing |
The reason for the action is an ongoing switch off i.e. the concerned cell will be switched off after offloading and not be available. It aides the receiving NG-RAN node in taking subsequent actions, e.g. selecting the target cell for subsequent handovers. |
Not supported 5QI value |
The action failed because the requested 5QI is not supported. |
TXnDCoverall Expiry |
The reason for the action is expiry of timer TXnDCoverall. |
TXnDCprep Expiry |
The reason for the action is expiry of timer TXnDCprep |
Action Desirable for Radio Reasons |
The reason for requesting the action is radio related. |
Reduce Load |
Load in the cell(group) served by the requesting node needs to be reduced. |
Resource Optimisation |
The reason for requesting this action is to improve the load distribution with the neighbour cells. |
Time Critical action |
The action is requested for time critical reason i.e. this cause value is reserved to represent all critical cases where radio resources are likely to be dropped if the requested action is not performed. |
Target not Allowed |
Requested action towards the indicated target cell is not allowed for the UE in question. In the current version of this specification applicable for Dual Connectivity only. |
No Radio Resources Available |
The cell(s) in the requested node don’t have sufficient radio resources available. In the current version of this specification applicable for Dual Connectivity only. |
Invalid QoS combination |
The action was failed because of invalid QoS combination. In the current version of this specification applicable for Dual Connectivity only. |
Encryption Algorithms Not Supported |
The requested NG-RAN node is unable to support any of the encryption algorithms supported by the UE. |
Procedure cancelled |
The sending node cancelled the procedure due to other urgent actions to be performed. In the current version of this specification applicable for Dual Connectivity only. |
RRM purpose |
The procedure is initiated due to node internal RRM purposes. In the current version of this specification applicable for Dual Connectivity only. |
Improve User Bit Rate |
The reason for requesting this action is to improve the user bit rate. In the current version of this specification applicable for Dual Connectivity only. |
User Inactivity |
The action is requested due to user inactivity on all PDU Sessions. The action may be performed on several levels: – on UE Context level, if NG is requested to be released in order to optimise the radio resources; or S-NG-RAN node didn’t see activity on the PDU session recently. – on PDU Session Resource or DRB or QoS flow level, e.g. if Activity Notification indicate lack of activity In the current version of this specification applicable for Dual Connectivity only. |
Radio Connection With UE Lost |
The action is requested due to losing the radio connection to the UE. In the current version of this specification applicable for Dual Connectivity only. |
Failure in the Radio Interface Procedure |
Radio interface procedure has failed. In the current version of this specification applicable for Dual Connectivity only. |
Bearer Option not Supported |
The requested bearer option is not supported by the sending node. In the current version of this specification applicable for Dual Connectivity only. |
UP integrity protection not possible |
The PDU session cannot be accepted according to the required user plane integrity protection policy. |
UP confidentiality protection not possible |
The PDU session cannot be accepted according to the required user plane confidentiality protection policy. |
Resources not available for the slice(s) |
The requested resources are not available for the slice(s). |
UE Maximum integrity protected data rate reason |
The request is not accepted in order to comply with the maximum data rate for integrity protection supported by the UE. |
CP Integrity Protection Failure |
The request is not accepted due to failed control plane integrity protection. |
UP Integrity Protection Failure |
The procedure is initiated because the SN (hosting node) detected an Integrity Protection failure in the UL PDU coming from the MN. |
Slice(s) not supported by NG-RAN |
The failure is due to slice(s) not supported by the NG-RAN node. |
MN Mobility |
The procedure is initiated due to relocation of the M-NG-RAN node UE context. |
SN Mobility |
The procedure is initiated due to relocation of the S-NG-RAN node UE context. |
Count reaches max value, |
Indicates the PDCP COUNT for UL or DL reached the max value and the bearer may be released. |
Unknown Old NG-RAN node UE XnAP ID |
The action failed because the Old NG-RAN node UE XnAP ID or the S-NG-RAN node UE XnAP ID is unknown. |
PDCP Overload |
The procedure is initiated due to PDCP resource limitation. |
DRB ID not available |
The action failed because the M-NG-RAN node is not able to provide additional DRB IDs to the S-NG-RAN node. |
Unspecified |
Sent for radio network layer cause when none of the specified cause values applies. |
UE Context ID not known |
The context retrieval procedure cannot be performed because the UE context cannot be identified. |
Non-relocation of context |
The context retrieval procedure is not performed because the old RAN node has decided not to relocate the UE context. |
CHO-CPC resources to be changed |
The prepared resources for CHO or CPC for a UE are to be changed. |
RSN not available for the UP |
The redundant user plane resources are not available. |
NPN Access denied |
Access denied, or release is required, due to NPN reasons. |
Report Characteristics Empty |
The action failed because there is no measurement object in the report characteristics. |
Existing Measurement ID |
The action failed because the measurement ID is already used. |
Measurement Temporarily not Available |
The NG-RAN node can temporarily not provide the requested measurement object. |
Measurement not Supported For The Object |
At least one of the concerned object(s) does not support the requested measurement. |
UE Power Saving |
The procedure is initiated to accommodate the preference indicated by UE to release the S-NG-RAN node for UE power saving purpose. |
Not existing NG-RAN node2 Measurement ID |
The action failed because the NG-RAN node2 Measurement ID is not used. |
Insufficient UE Capabilities |
The procedure can’t proceed due to insufficient UE capabilities. |
Normal Release |
The release is due to normal reasons. |
SCG activation deactivation failure |
The action failed due to rejection of the SCG activation deactivation request. |
SCG deactivation failure due to data transmission |
The SCG deactivation failure due to ongoing or arriving data transmission. |
Transport Layer cause |
Meaning |
Transport resource unavailable |
The required transport resources are not available. |
Unspecified |
Sent when none of the above cause values applies but still the cause is Transport Network Layer related. |
Protocol cause |
Meaning |
Transfer Syntax Error |
The received message included a transfer syntax error. |
Abstract Syntax Error (Reject) |
The received message included an abstract syntax error and the concerning criticality indicated "reject". |
Abstract Syntax Error (Ignore And Notify) |
The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". |
Message Not Compatible With Receiver State |
The received message was not compatible with the receiver state. |
Semantic Error |
The received message included a semantic error. |
Abstract Syntax Error (Falsely Constructed Message) |
The received message contained IEs or IE groups in wrong order or with too many occurrences. |
Unspecified |
Sent when none of the above cause values applies but still the cause is Protocol related. |
Miscellaneous cause |
Meaning |
Control Processing Overload |
NG-RAN node control processing overload. |
Hardware Failure |
NG-RAN node hardware failure. |
Not enough User Plane Processing Resources |
NG-RAN node has insufficient user plane processing resources available. |
O&M Intervention |
Operation and Maintenance intervention related to NG-RAN node equipment. |
Unspecified |
Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer or Protocol. |
9.2.3.3 Criticality Diagnostics
The Criticality Diagnostics IE is sent by the NG-RAN node when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Procedure Code |
O |
INTEGER (0..255) |
Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. |
|
Triggering Message |
O |
ENUMERATED (initiating message, successful outcome, unsuccessful outcome) |
The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. |
|
Procedure Criticality |
O |
ENUMERATED (reject, ignore, notify) |
This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). |
|
Information Element Criticality Diagnostics |
0..<maxNrOfErrors> |
|||
>IE Criticality |
M |
ENUMERATED (reject, ignore, notify) |
The IE Criticality is used for reporting the criticality of the triggering IE. The value "ignore" is not applicable. |
|
>IE ID |
M |
INTEGER (0..65535) |
The IE ID of the not understood or missing IE |
|
>Type Of Error |
M |
ENUMERATED(not understood, missing, …) |
Range bound |
Explanation |
maxNrOfErrors |
Maximum no. of IE errors allowed to be reported with a single message. The Value is 256. |
9.2.3.4 Bit Rate
This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL or by the UE in sidelink within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a GBR QoS flow, or an aggregate maximum bit rate.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Bit Rate |
M |
INTEGER (0..4,000,000,000,000,…) |
The unit is: bit/s |
9.2.3.5 QoS Flow Level QoS Parameters
This IE defines the QoS Parameters to be applied to a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
CHOICE QoS Characteristics |
M |
– |
||||
>Non Dynamic 5QI |
||||||
>>Non dynamic 5QI Descriptor |
M |
9.2.3.8 |
– |
|||
>Dynamic 5QI |
||||||
>>Dynamic 5QI Descriptor |
M |
9.2.3.9 |
– |
|||
Allocation and Retention Priority |
M |
9.2.3.7 |
– |
|||
GBR QoS Flow Information |
O |
9.2.3.6 |
This IE shall be present for GBR QoS flows and is ignored otherwise. |
– |
||
Reflective QoS Attribute |
O |
ENUMERATED (subject to, …) |
Reflective QoS is specified in TS 23.501 [7]. This IE applies to Non-GBR bearers only and is ignored otherwise. |
– |
||
Additional QoS flow Information |
O |
ENUMERATED (more likely, …) |
If this IE is set to "more likely", this indicates that traffic for this QoS flow is likely to appear more often than traffic for other flows established for the PDU session. This IE may be present in case of Non-GBR flows only and is ignored otherwise. |
– |
||
QoS Monitoring Request |
O |
ENUMERATED (UL, DL, Both, …) |
Indicates to measure UL, or DL, or both UL/DL delays for the associated QoS flow. |
YES |
ignore |
|
QoS Monitoring Reporting Frequency |
O |
INTEGER (1.. 1800, …) |
Indicates the Reporting Frequency for RAN part delay for Qos monitoring. Unit: second |
YES |
ignore |
|
QoS Monitoring Disabled |
O |
ENUMERATED(true, …) |
Indicates to stop the QoS monitoring. |
YES |
ignore |
9.2.3.6 GBR QoS Flow Information
This IE indicates QoS Parameters for a GBR QoS Flow for downlink and uplink.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Maximum Flow Bit Rate Downlink |
M |
Bit Rate 9.2.3.4 |
Maximum Bit Rate in DL. Flow Bit Rates are specified in TS 23.501 [7]. |
– |
||
Maximum Flow Bit Rate Uplink |
M |
Bit Rate 9.2.3.4 |
Maximum Bit Rate in UL. Flow Bit Rates are specified in TS 23.501 [7]. |
– |
||
Guaranteed Flow Bit Rate Downlink |
M |
Bit Rate 9.2.3.4 |
Guaranteed Bit Rate (provided that there is data to deliver) in DL. Flow Bit Rates are specified in TS 23.501 [7]. |
– |
||
Guaranteed Flow Bit Rate Uplink |
M |
Bit Rate 9.2.3.4 |
Guaranteed Bit Rate (provided that there is data to deliver). Flow Bit Rates are specified in TS 23.501 [7]. |
– |
||
Notification Control |
O |
ENUMERATED (notification requested, …) |
Notification control is specified in TS 23.501 [7] |
– |
||
Maximum Packet Loss Rate Downlink |
O |
Packet Loss Rate 9.2.3.11 |
Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Maximum Packet Loss Rate is specified in TS 23.501 [7]. |
– |
||
Maximum Packet Loss Rate Uplink |
O |
Packet Loss Rate 9.2.3.11 |
Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Maximum Packet Loss Rate is specified in TS 23.501 [7]. |
– |
||
Alternative QoS Parameters Set List |
O |
9.2.3.102 |
Indicates alternative sets of QoS Parameters for the QoS flow. |
YES |
ignore |
9.2.3.7 Allocation and Retention Priority
This IE specifies the relative importance compared to other QoS flows for allocation and retention of the NR RAN resource.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Allocation/Retention Priority |
1 |
|||
>Priority Level |
M |
INTEGER (0..15, …) |
Desc.: This defines the relative importance of a resource request. (see TS 23.501 [7]). Usage: Values between 1 and 15 are ordered in decreasing order of priority, i.e., 1 is the highest and 15 is the lowest. |
|
>Pre-emption Capability |
M |
ENUMERATED (shall not trigger pre-emption, may trigger pre-emption, …) |
Desc.: This IE indicates the pre-emption capability of the request on other QoS flows (see TS 23.501 [7]). Usage: The QoS flow shall not pre-empt other QoS flow or, the QoS flow may pre-empt other QoS flows. NOTE: The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the gNB. |
|
>Pre-emption Vulnerability |
M |
ENUMERATED (not pre-emptable, pre-emptable, …) |
Desc.: This IE indicates the vulnerability of the QoS flow to preemption of other QoS flows (see TS 23.501 [7]). Usage: The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows. NOTE: Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the gNB. |
9.2.3.8 Non dynamic 5QI Descriptor
This IE defines QoS characteristics for a standardized or pre-configured 5QI for downlink and uplink.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
5QI |
M |
INTEGER (0..255, …) |
This IE contains the standardized or pre-configured 5QI as specified in TS 23.501 [7} |
– |
||
Priority Level |
O |
9.2.3.62 |
Priority level is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. |
– |
||
Averaging Window |
O |
9.2.3.14 |
Averaging window is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. |
– |
||
Maximum Data Burst Volume |
O |
9.2.3.15 |
Maximum Data Burst Volume is specified in TS 23.501 [7]. When included, it overrides standardized or pre-configured value. |
– |
||
CN Packet Delay Budget Downlink |
O |
Extended Packet Delay Budget 9.2.3.113 |
Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. |
YES |
ignore |
|
CN Packet Delay Budget Uplink |
O |
Extended Packet Delay Budget 9.2.3.113 |
Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. |
YES |
ignore |
9.2.3.9 Dynamic 5QI Descriptor
This IE defines the QoS characteristics for a non-standardized or not pre-configured 5QI for downlink and uplink.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Priority Level |
M |
9.2.3.62 |
Priority level is specified in TS 23.501 [7]. |
– |
||
Packet Delay Budget |
M |
9.2.3.12 |
Packet Delay Budget is specified in TS 23.501 [7]. This IE is ignored if the Extended Packet Delay Budget IE is present. |
– |
||
Packet Error Rate |
M |
9.2.3.13 |
Packet Error Rate is specified in TS 23.501 [7]. |
– |
||
5QI |
O |
INTEGER (0..255, …) |
This IE contains the dynamically assigned 5QI as specified in TS 23.501 [7]. |
– |
||
Delay Critical |
C-ifGBRflow |
ENUMERATED (Delay critical, Non-delay critical, …) |
This IE indicates whether the GBR QoS flow is delay critical as specified in TS 23.501 [7]. |
– |
||
Averaging Window |
C-ifGBRflow |
9.2.3.14 |
Averaging window is specified in TS 23.501 [7]. |
– |
||
Maximum Data Burst Volume |
O |
9.2.3.15 |
Maximum Data Burst Volume is specified in TS 23.501 [7]. This IE shall be included if the Delay Critical IE is set to "delay critical" and is be ignored otherwise. |
– |
||
Extended Packet Delay Budget |
O |
9.2.3.113 |
Packet Delay Budget is specified in TS 23.501 [7]. |
YES |
ignore |
|
CN Packet Delay Budget Downlink |
O |
Extended Packet Delay Budget 9.2.3.113 |
Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. |
YES |
ignore |
|
CN Packet Delay Budget Uplink |
O |
Extended Packet Delay Budget 9.2.3.113 |
Core Network Packet Delay Budget is specified in TS 23.501 [7]. This IE may be present in case of GBR QoS flows and is ignored otherwise. |
YES |
ignore |
Condition |
Explanation |
ifGBRflow |
This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. |
9.2.3.10 QoS Flow Identifier
This IE identifies either a QoS Flow within a PDU Session or an MBS QoS flow within an MBS Session. Definition and use of the QoS Flow Identifier is specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
QoS Flow Identifier |
M |
INTEGER (0 ..63, …) |
9.2.3.11 Packet Loss Rate
This IE indicates the Packet Loss Rate for a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Packet Loss Rate |
M |
INTEGER (0..1000, …) |
Ratio of lost packets per number of packets sent, expressed in tenth of percent. |
9.2.3.12 Packet Delay Budget
This IE indicates the Packet Delay Budget for a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Packet Delay Budget |
M |
INTEGER (0..1023, …) |
Upper bound value for the delay that a packet may experience expressed in units of 0.5ms. |
9.2.3.13 Packet Error Rate
This IE indicates the Packet Error Rate for a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Scalar |
M |
INTEGER (0..9,…) |
The packet error rate is expressed as Scalar * 10-k, whereas k is the Exponent. |
|
Exponent |
M |
INTEGER (0..9, …) |
9.2.3.14 Averaging Window
This IE indicates the Averaging Window for a QoS flow and applies to GBR QoS flows only.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Averaging Window |
M |
INTEGER (0..4095, …) |
Unit: ms. |
9.2.3.15 Maximum Data Burst Volume
This IE indicates the Maximum Data Burst Volume for a QoS flow and applies to delay critical GBR QoS flows only.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Maximum Data Burst Volume |
M |
INTEGER (0..4095, …, 4096.. 2000000) |
Unit: byte, |
9.2.3.16 NG-RAN node UE XnAP ID
The NG-RAN node UE XnAP ID uniquely identifies a UE over the Xn interface within the NG-RAN node.
The use of this IE is defined in TS 38.401 [2].
NOTE: If Xn-C signalling transport is shared among multiple interface instances, the value of the NG-RAN node UE XnAP ID is allocated so that it can be associated with the corresponding Xn-C interface instance.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NG-RAN node UE XnAP ID |
M |
INTEGER (0 .. 232 -1) |
9.2.3.17 UE Aggregate Maximum Bit Rate
The UE Aggregate Maximum Bitrate is applicable for all Non-GBR QoS flows per UE which is defined for the Downlink and the Uplink direction and a subscription parameter provided by the AMF to the NG-RAN.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Aggregate Maximum Bit Rate |
1 |
Applicable for Non-GBR QoS flows. |
||
>UE Aggregate Maximum Bit Rate Downlink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
|
>UE Aggregate Maximum Bit Rate Uplink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the UE Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
9.2.3.18 PDU Session ID
This IE identifies a PDU Session for a UE. Definition and use of the PDU Session ID is specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDU Session ID |
M |
INTEGER (0 ..255) |
9.2.3.19 PDU Session Type
This IE defines the PDU Session Type as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDU Session Type |
M |
ENUMERATED (IPv4, IPv6, IPv4v6, Ethernet, Unstructured, …) |
9.2.3.20 TAI Support List
This IE indicates the list of TAIs supported by NG-RAN node and associated characteristics e.g. supported slices.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
TAI Support Item |
1..<maxnoofsupportedTACs> |
– |
||||
>TAC |
M |
9.2.2.5 |
Broadcast TAC |
– |
||
>Broadcast PLMNs |
1..<maxnoofsupportedPLMNs> |
– |
||||
>>PLMN Identity |
M |
9.2.2.4 |
Broadcast PLMN |
– |
||
>>TAI Slice Support List |
M |
Slice Support List |
Supported S-NSSAIs per TAC, per PLMN or per SNPN. |
– |
||
>>NPN Support |
O |
9.2.2.72 |
YES |
reject |
||
>>Extended TAI Slice Support List |
O |
Extended Slice Support List |
Additional Supported S-NSSAIs per TAC, per PLMN or per SNPN. |
YES |
reject |
|
>>TAI NSAG Support List |
O |
9.2.3.170 |
NSAG information associated with the slices per TAC, per PLMN or per SNPN. |
YES |
ignore |
Range bound |
Explanation |
maxnoofsupportedTACs |
Maximum no. of TACs supported by an NG-RAN node. Value is 256. |
maxnoofsupportedPLMNs |
Maximum no. of PLMNs supported by an NG-RAN node. Value is 12. |
9.2.3.21 S-NSSAI
This IE indicates the S-NSSAI as defined in TS 23.003 [22].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
SST |
M |
OCTET STRING (SIZE(1)) |
||
SD |
O |
OCTET STRING (SIZE(3)) |
9.2.3.22 Slice Support List
This IE indicates the list of supported slices.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Slice Support Item |
1..<maxnoofSliceItems> |
|||
>S-NSSAI |
M |
9.2.3.21 |
Range bound |
Explanation |
maxnoofSliceItems |
Maximum no. of signalled slice support items. Value is 1024. |
9.2.3.23 Index to RAT/Frequency Selection Priority
The Index to RAT/Frequency Selection Priority IE is used to define local configuration for RRM strategies such as camp priorities and control of inter-RAT/inter-frequency mobility in RRC_CONNECTED, as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Index to RAT/Frequency Selection Priority |
M |
INTEGER (1..256) |
9.2.3.24 GUAMI
This IE contains the Globally Unique AMF Identifier (GUAMI) as defined in TS 23.003 [22].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN Identity |
M |
9.2.2.4 |
||
AMF Identifier |
1 |
|||
>AMF Region ID |
M |
BIT STRING (SIZE (8)) |
||
>AMF Set ID |
M |
BIT STRING (SIZE (10)) |
||
>AMF Pointer |
M |
BIT STRING (SIZE (6)) |
9.2.3.25 Target Cell Global ID
This IE contains either an NR CGI or an E-UTRA CGI.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE Target Cell |
M |
|||
>NR |
||||
>>NR CGI |
M |
9.2.2.7 |
||
>E-UTRA |
||||
>>E-UTRA CGI |
M |
9.2.2.8 |
9.2.3.26 AMF UE NGAP ID
This IE is defined in TS 38.413 [5] and used to uniquely identify the UE association over the source side NG interface instance.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
AMF UE NGAP ID |
M |
INTEGER (0 .. 240 -1) |
9.2.3.27 SCG Configuration Query
The SCG Configuration Query IE is used to request the S-NG-RAN node to provide current SCG configuration.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
SCG Configuration Query |
M |
ENUMERATED (True, …) |
9.2.3.28 RLC Mode
The RLC Mode IE indicates the RLC Mode used for a DRB.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
RLC Mode |
M |
ENUMERATED ( RLC-AM, RLC-UM-Bidirectional, |
9.2.3.29 Transport Layer Address
This IE is defined to contain an IP address.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Transport Layer Address |
M |
BIT STRING (1..160, …) |
9.2.3.30 UP Transport Layer Information
This element is used to provide the transport layer information associated with NG or Xn user plane transport. In this release it corresponds to an IP adress and a GTP Tunnel Endpoint Identifier. When the NR-DC UE is connected with an IAB, the QoS Mapping Information is used to set the IP header of packets in case that the S-NG-RAN node serves the IAB and the packets belonging to MN-terminated split bearer/SCG bearer are transmitted from M-NG-RAN node to S-NG-RAN node, and in case that the M-NG-RAN node serves the IAB and the packets belonging to SN-terminated split bearer/MCG bearer are transmitted from S-NG-RAN node to M-NG-RAN node.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
CHOICE UP Transport Layer Information |
M |
|||||
>GTP tunnel |
– |
|||||
>>Transport Layer Address |
M |
9.2.3.29 |
The Transport Layer Address is specified in TS 38.424 [19] and TS 38.414 [20]. |
– |
||
>>GTP-TEID |
M |
OCTET STRING (4) |
The Tunnel Endpoint Identifier (TEID) is specified in TS 29.281 [18] |
– |
||
>>QoS Mapping Information |
O |
9.2.3.144 |
YES |
reject |
9.2.3.31 CP Transport Layer Information
This element is used to provide the transport layer information associated with NG or Xn control plane transport.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
CHOICE CP Transport Layer Information |
||||||
>Endpoint-IP-address |
– |
|||||
>>Endpoint IP Address |
M |
Transport Layer Address 9.2.3.29 |
– |
|||
>Endpoint-IP-address-and-port |
YES |
reject |
||||
>>Endpoint IP Address |
M |
Transport Layer Address 9.2.3.29 |
– |
|||
>>Port Number |
M |
BIT STRING (16) |
– |
9.2.3.32 Masked IMEISV
This information element contains the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Masked IMEISV |
M |
BIT STRING (SIZE(64)) |
Coded as the International Mobile station Equipment Identity and Software Version Number (IMEISV) defined in TS 23.003 [22] with the last 4 digits of the SNR masked by setting the corresponding bits to 1. |
9.2.3.33 DRB ID
This IE contains the DRB ID.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
DRB ID |
M |
INTEGER (1..32, …) |
9.2.3.34 DL Forwarding
This element indicates a proposal for forwarding of downlink packets.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
DL Forwarding |
M |
ENUMERATED (DL forwarding proposed, …) |
9.2.3.35 Data Forwarding Accepted
This element indicates that data forwarding was accepted.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Data Forwarding Accepted |
M |
ENUMERATED (data forwarding accepted, …) |
9.2.3.36 COUNT Value for PDCP SN Length 12
This information element indicates the 12-bit long PDCP sequence number and the corresponding 20 bits long Hyper Frame Number.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDCP-SN Length 12 |
M |
INTEGER (0..4095) |
||
HFN for PDCP-SN Length 12 |
M |
INTEGER (0..1048575) |
9.2.3.37 COUNT Value for PDCP SN Length 18
This information element indicates the 18-bit long PDCP sequence number and the corresponding 14 bits long Hyper Frame Number.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDCP-SN Length 18 |
M |
INTEGER (0..262143) |
||
HFN for PDCP-SN Length 18 |
M |
INTEGER (0..16383) |
9.2.3.38 RAN Paging Area
The RAN Paging Area IE defines the paging area within a PLMN for RAN paging a UE in RRC_INACTIVE state.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN Identity |
M |
9.2.2.4 |
||
CHOICE RAN Paging Area Choice |
M |
|||
>Cell List |
||||
>>Cell List Item |
1 .. < maxnoofCellsinRNA> |
|||
>>>NG-RAN Cell Identity |
M |
9.2.2.9 |
In this version of the specification, the RAN paging area should contain NG-RAN cells of the same RAT type. |
|
>RAN Area ID List |
||||
>>RAN Area ID List Item |
1 .. <maxnoofRanAreasinRNA> |
|||
>>>RAN Area ID |
M |
9.2.3.39 |
Range bound |
Explanation |
maxnoofCellsinRNA |
Maximum no. of cells in a RAN notification area. Value is 32. |
maxnoofRanAreasinRNA |
Maximum no. of RAN area IDs in a RAN notification area. Value is 16. |
9.2.3.39 RAN Area ID
This IE defines the RAN Area ID.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
TAC |
M |
9.2.2.5 |
Tracking Area Code |
|
RANAC |
O |
RAN Area Code 9.2.2.6 |
9.2.3.40 UE Context ID
This IE is used to address a UE Context within an NG-RAN node.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE UE Context ID |
M |
|||
>RRC Resume |
||||
>>I-RNTI |
M |
9.2.3.46 |
||
>>Allocated C-RNTI |
M |
BIT STRING (SIZE (16)) |
Temporary C-RNTI or C-RNTI allocated to the UE by the cell where the RRC connection has been requested to be resumed, contained in the MAC RAR or MAC MSGB as defined in TS 38.321 [35] or in TS 36.321 [36]. |
|
>>Access PCI |
M |
NG-RAN Cell PCI 9.2.2.10 |
The cell PCI where the RRC connection has been requested to be resumed. |
|
>RRC Reestablishment |
||||
>>C-RNTI |
M |
BIT STRING (SIZE (16)) |
C-RNTI contained in the RRCReestablishmentRequest message (TS 38.331 [10]) or RRCConnectionReestablishmentRequest message (TS 36.331 [14]). |
|
>>Failure Cell PCI |
M |
NG-RAN Cell PCI 9.2.2.10 |
9.2.3.41 Assistance Data for RAN Paging
This IE provides assistance information for RAN paging.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
RAN Paging Attempt Information |
O |
9.2.3.42 |
– |
|||
NPN Paging Assistance Information |
O |
9.2.3.121 |
YES |
ignore |
9.2.3.42 RAN Paging Attempt Information
This IE includes information related to the RAN paging attempt over Xn.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Paging Attempt Count |
M |
INTEGER (1..16,…) |
Number of the RAN paging attempt. |
|
Intended Number of Paging Attempts |
M |
INTEGER (1..16,…) |
Intended number of RAN paging attempts. |
|
Next Paging Area Scope |
O |
ENUMERATED (same, changed, …) |
Indicates whether the RAN paging area scope will change at next RAN paging attempt. |
9.2.3.43 UE RAN Paging Identity
The IE defines the UE Identity for RAN paging a UE in RRC_INACTIVE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE UE RAN Paging Identity |
M |
|||
>I-RNTI full |
||||
>>I-RNTI full |
M |
BIT STRING (SIZE (40)) |
9.2.3.44 Paging Priority
This information element contains an indication of the priority to be considered for the paging request.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Paging Priority |
M |
ENUMERATED (PrioLevel1, PrioLevel2, PrioLevel3, PrioLevel4, PrioLevel5, PrioLevel6, PrioLevel7, PrioLevel8, …) |
Lower value codepoint indicates higher priority. |
9.2.3.45 Delivery Status
This IE provides the delivery status of RRC PDUs provided by RRC Transfer message.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Delivery Status |
M |
INTEGER (0..212-1) |
Highest successfully delivered NR PDCP SN, as defined in TS 38.323 [11]. |
9.2.3.46 I-RNTI
The I-RNTI is defined for allocation in an NR or E-UTRA serving cell as a reference to a UE Context within an NG-RAN node. The I-RNTI is partitioned into two parts, the first part identifies the NG-RAN node that allocated the I-RNTI and the second part identifies the UE context stored in this NG-RAN node, refer to Annex C in TS 38.300 [9], or the I-RNTI is partitioned into three parts, the first part indicates the length of NG-RAN Node ID part of the NG-RAN Node that allocated the I-RNTI, the second part identifies the NG-RAN node that allocated the I-RNTI and the third part identifies the UE context stored in this NG-RAN node, refer to Annex F in TS 38.300[9].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE I-RNTI |
||||
>I-RNTI full |
||||
>>I-RNTI full |
M |
BIT STRING (SIZE (40)) |
This IE is used to identify the suspended UE context of a UE in RRC_INACTIVE using 40 bits (refer to I-RNTI-Value IE in TS 38.331 [10] and I-RNTI IE in TS 36.331 [14]). |
|
>I-RNTI short |
||||
>>I-RNTI short |
M |
BIT STRING (SIZE (24)) |
This IE is used to identify the suspended UE context of a UE in RRC_INACTIVE using 24 bits (refer to ShortI-RNTI-Value IE in TS 38.331 [10] and ShortI-RNTI IE in TS 36.331 [14]). |
9.2.3.47 Location Reporting Information
This information element indicates how the location information should be reported.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Event Type |
M |
ENUMERATED ( report upon change of serving cell, report UE moving presence into or out of the Area of Interest, …, report upon change of serving cell and Area of Interest) |
– |
|||
Report Area |
M |
ENUMERATED (Cell, …) |
– |
|||
Area of Interest Information |
O |
9.2.3.48 |
– |
|||
Additional Location Information |
O |
ENUMERATED (Include PSCell, …) |
YES |
ignore |
9.2.3.48 Area of Interest Information
This IE contains indicates the Area of Interest information, which may contain multiple Areas of Interest, as specified in TS 23.502 [13].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Area of Interest Item |
1.. <maxnoofAoIs> |
|||
>List of TAIs in Area of Interest |
0..1 |
|||
>>TAI in Area of Interest Item |
1..< maxnoofTAIsinAoI > |
|||
>>>PLMN Identity |
M |
9.2.2.4 |
||
>>>TAC |
M |
9.2.2.5 |
||
>List of Cells in Area of Interest |
0..1 |
This IE may need to be refined with SA2. |
||
>>Cell Item |
1..<maxnoofcellsinAoI> |
|||
>>>PLMN Identity |
M |
9.2.2.4 |
||
>>>NG-RAN Cell Identity |
M |
9.2.2.9 |
||
>List of Global NG-RAN Nodes in Area of Interest |
0..1 |
|||
>>Global NG-RAN Node in Area of Interest Item |
1..<maxnoofRANNodesinAoI> |
|||
>>>Global NG-RAN Node ID |
M |
9.2.2.3 |
||
>Request Reporting Reference ID |
M |
9.2.3.58 |
Range bound |
Explanation |
maxnoofAOIs |
Maximum no. of Areas of Interest. Value is 64. |
maxnoofTAIsinAoI |
Maximum no. of tracking areas in an Area of Interest. Value is 16. |
maxnoofcellsinAoI |
Maximum no. of cells in an Area of Interest. Value is 256. |
maxnoofRANNodesinAoI |
Maximum no. of global NG-RAN nodes in an Area of Interest. Value is 64. |
9.2.3.49 UE Security Capabilities
The UE Security Capabilities IE defines the supported algorithms for encryption and integrity protection in the UE. Except as noted below, the NG-RAN nodes store and send the complete bitmaps without modification or truncation as specified in TS 38.300 [9].
NOTE: There is a 1-bit circular shift between the bitmaps of the IE in this specification and the corresponding bitmaps in TS 38.413 [5].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
NR Encryption Algorithms |
M |
BIT STRING {nea1-128(1), nea2-128(2), nea3-128(3)} (SIZE(16, …)) |
Each position in the bitmap represents an encryption algorithm: "all bits equal to 0" – UE supports no other NR algorithm than NEA0, "second bit" – 128-NEA1, "third bit" – 128-NEA2, "fourth bit" – 128-NEA3, “fifth to eighth bit” correspond to bit 4 to bit 1 of octet 3 in the UE Security Capability IE defined in TS 24.501 [30], other bits reserved for future use. Value ‘1’ indicates support and value ‘0’ indicates no support of the algorithm. Algorithms are defined in TS 33.501 [28]. |
|
NR Integrity Protection Algorithms |
M |
BIT STRING {nia1-128(1), nia2-128(2), nia3-128(3)} (SIZE(16, …)) |
Each position in the bitmap represents an integrity protection algorithm: "all bits equal to 0" – UE supports no other NR algorithm than NIA0, "second bit" – 128-NIA1, "third bit" – 128-NIA2, "fourth bit" – 128-NIA3, “fifth to eighth bit” correspond to bit 4 to bit 1 of octet 4 in the UE Security Capability IE defined in TS 24.501 [30], other bits reserved for future use. Value ‘1’ indicates support and value ‘0’ indicates no support of the algorithm. Algorithms are defined in TS 33.501 [28]. |
|
E-UTRA Encryption Algorithms |
M |
BIT STRING {eea1-128(1), eea2-128(2), eea3-128(3)} (SIZE(16, …)) |
Each position in the bitmap represents an encryption algorithm: "all bits equal to 0" – UE supports no other algorithm than EEA0, "second bit" – 128-EEA1, "third bit" – 128-EEA2, "fourth bit" – 128-EEA3, “fifth to eighth bit” correspond to bit 4 to bit 1 of octet 5 in the UE Security Capability IE defined in TS 24.501 [30], other bits reserved for future use. Value ‘1’ indicates support and value ‘0’ indicates no support of the algorithm. Algorithms are defined in TS 33.401 [29]. |
|
E-UTRA Integrity Protection Algorithms |
M |
BIT STRING {eia1-128(1), eia2-128(2), eia3-128(3)} (SIZE(16, …)) |
Each position in the bitmap represents an integrity protection algorithm: "all bits equal to 0" – UE supports no other algorithm than EIA0, "second bit" – 128-EIA1, "third bit" – 128-EIA2, "fourth bit" – 128-EIA3, “fifth to eighth bit” correspond to bit 4 to bit 1 of octet 6 in the UE Security Capability IE defined in TS 24.501 [30], other bits reserved for future use. Value ‘1’ indicates support and value ‘0’ indicates no support of the algorithm. Algorithms are defined in TS 33.401 [29]. |
9.2.3.50 AS Security Information
The AS Security Information IE is used to generate the key material to be used for AS security with the UE.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Key NG-RAN Star |
M |
BIT STRING (256) |
KNG-RAN* defined in TS 33.501 [28]. |
|
Next Hop Chaining Count |
M |
INTEGER (0..7) |
Next Hop Chaining Count (NCC) defined in TS 33.501 [28] |
9.2.3.51 S-NG-RAN node Security Key
The S-NG-RAN node Security Key IE is used to apply security in the S-NG-RAN node as defined in TS 33.501 [28].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
S-NG-RAN node Security Key |
M |
BIT STRING (SIZE(256)) |
The S-KSN which is provided by the M-NG-RAN node, see TS 33.501 [28]. |
9.2.3.52 Security Indication
This IE contains the user plane integrity protection indication and confidentiality protection indication which indicates the requirements on UP integrity protection and ciphering for the corresponding PDU session, respectively. Additionally, this IE contains the maximum integrity protected data rate values (UL and DL) per UE for integrity protected DRBs.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Integrity Protection Indication |
M |
ENUMERATED (required, preferred, not needed,…) |
Indicates whether UP integrity protection shall apply, should apply, or shall not apply for the concerned PDU session. |
|
Confidentiality Protection Indication |
M |
ENUMERATED (required, preferred, not needed, …) |
Indicates whether UP ciphering shall apply, should apply, or shall not apply for the concerned PDU session. |
|
Maximum Integrity Protected Data Rate |
C-ifIntegrityProtectionrequiredorpreferred |
9.2.3.73 |
If present, this IE contains the values received from the CN for the overall UE capability. This IE may be ignored by the SN in the case of dual connectivity. |
Condition |
Explanation |
ifIntegrityProtectionrequiredorpreferred |
This IE shall be present if the Integrity Protection IE within the Security Indication IE is present and set to “required” or “preferred”. |
9.2.3.53 Mobility Restriction List
This IE defines roaming or access restrictions for subsequent mobility actions for which the NG-RAN provides information about the target of the mobility action towards the UE, e.g., handover, or for SCG selection during dual connectivity operation or for assigning proper RNAs. If the NG-RAN receives the Mobility Restriction List IE, it shall overwrite previously received restriction information. NG-RAN behaviour upon receiving this IE is specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Serving PLMN |
M |
PLMN Identity 9.2.2.4 |
– |
|||
Equivalent PLMNs |
0..<maxnoofEPLMNs> |
Allowed PLMNs in addition to Serving PLMN. This list corresponds to the list of "equivalent PLMNs" as defined in TS 24.501 [30]. This list is part of the roaming restriction information. Roaming restrictions apply to PLMNs other than the Serving PLMN and Equivalent PLMNs. |
– |
|||
>PLMN Identity |
M |
9.2.2.4 |
– |
|||
RAT Restrictions |
0..<maxnoofPLMNs> |
This IE contains RAT restriction related information as specified in TS 23.501 [7]. |
– |
|||
>PLMN Identity |
M |
9.2.2.4 |
– |
|||
>RAT Restriction Information |
M |
BIT STRING { e-UTRA (0), nR (1), nR-unlicensed (2), nR-LEO (3), nR-MEO (4), nR-GEO (5), nR-OTHERSAT (6)} (SIZE(8, …)) |
Each position in the bitmap represents a RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 is reserved for future use. |
– |
||
>Extended RAT Restriction Information |
O |
9.2.3.99 |
If this IE is included, the RAT Restriction Information IE is ignored. |
YES |
ignore |
|
Forbidden Area Information |
0..<maxnoofPLMNs> |
This IE contains Forbidden Area information as specified in TS 23.501 [7]. |
– |
|||
>PLMN Identity |
M |
9.2.2.4 |
– |
|||
>Forbidden TACs |
1..<maxnoofForbiddenTACs> |
– |
||||
>>TAC |
M |
9.2.2.5 |
The TAC of the forbidden TAI. |
– |
||
Service Area Information |
0..<maxnoofPLMNs> |
This IE contains Service Area Restriction information as specified in TS 23.501 [7]. |
– |
|||
>PLMN Identity |
M |
9.2.2.4 |
– |
|||
>Allowed TACs |
0..<maxnooAllowedAreas> |
– |
||||
>>TAC |
M |
9.2.2.5 |
The TAC of the allowed TAI. |
– |
||
>Not Allowed TACs |
0..<maxnooAllowedAreas> |
– |
||||
>>TAC |
M |
9.2.2.5 |
The TAC of the not-allowed TAI. |
– |
||
Last E-UTRAN PLMN Identity |
O |
9.2.2.4 |
Indicates the E-UTRAN PLMN ID from where the UE formerly handed over to 5GS and which is preferred in case of subsequent mobility to EPS. |
YES |
ignore |
|
Core Network Type Restriction for serving PLMN |
O |
ENUMERATED (EPCForbidden, …) |
Indicates whether the UE is restricted to connect to EPC for the Serving PLMN as specified in TS 23.501 [7]. |
YES |
ignore |
|
Core Network Type Restriction for Equivalent PLMNs |
0..<maxnoofEPLMNs> |
YES |
ignore |
|||
>PLMN Identity |
M |
9.2.2.4 |
Includes any of the Equivalent PLMNs listed in the Mobility Restriction List IE for which CN Type restriction applies as specified in TS 23.501 [7]. |
– |
||
>Core Network Type Restriction |
M |
ENUMERATED (EPCForbidden, 5GCForbidden, …) |
Indicates whether the UE is restricted to connect to EPC or to 5GC for this PLMN. |
– |
||
NPN Mobility Information |
O |
9.2.3.119 |
YES |
reject |
Range bound |
Explanation |
maxnoofEPLMNs |
Maximum no. of equivalent PLMNs. Value is 15. |
maxnoofPLMNs |
Maximum no. of allowed PLMNs. Value is 16. |
maxnoofForbiddenTACs |
Maximum no. of forbidden Tracking Area Codes. Value is 4096. |
maxnoofAllowedAreas |
Maximum no. of allowed or not allowed Tracking Areas. Value is 16. |
9.2.3.54 Xn Benefit Value
The Xn Benefit Value IE indicates the quantified benefit of the signalling connection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Xn Benefit Value |
M |
INTEGER (1..8, …) |
Value 1 indicates lowest benefit, and 8 indicates highest benefit. |
9.2.3.55 Trace Activation
This IE defines parameters related to a trace activation.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
NG-RAN Trace ID |
M |
9.2.3.97 |
– |
|||
Interfaces To Trace |
M |
BIT STRING (SIZE(8)) |
Each position in the bitmap represents an NG-RAN node interface: first bit = NG-C, second bit = Xn-C, third bit = Uu, fourth bit = F1-C, fifth bit = E1: other bits reserved for future use. Value ‘1’ indicates ‘should be traced’. Value ‘0’ indicates ‘should not be traced’. |
– |
||
Trace Depth |
M |
ENUMERATED (minimum, medium, maximum, MinimumWithoutVendorSpecificExtension, MediumWithoutVendorSpecificExtension, MaximumWithoutVendorSpecificExtension, …) |
Defined in TS 32.422 [23]. |
– |
||
Trace Collection Entity IP Address |
M |
Transport Layer Address 9.2.3.29 |
For File based Reporting. Defined in TS 32.422 [23] Should be ignored if the Trace Collection Entity URI IE is present. |
– |
||
Trace Collection Entity URI |
O |
URI 9.2.3.124 |
For Streaming based Reporting. Defined in TS 32.422 [23] Replaces Trace Collection Entity IP Address if present |
YES |
ignore |
|
MDT Configuration |
O |
9.2.3.125 |
This IE defines the MDT configuration parameters. |
YES |
ignore |
9.2.3.56 Time To Wait
This IE defines the minimum allowed waiting times.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Time To Wait |
M |
ENUMERATED (1s, 2s, 5s, 10s, 20s, 60s, …) |
9.2.3.57 QoS Flow Notification Control Indication Info
This IE provides information about QoS flows of a PDU Session Resource for which notification control has been requested.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
QoS Flow Notification Indication Info |
1 |
– |
||||
>QoS Flows Notify Item |
1..<maxnoofQoSFlows> |
– |
||||
>>QoS Flow Identifier |
M |
9.2.3.10 |
– |
|||
>>Notification Information |
M |
ENUMERATED (fulfilled, not fulfilled, …) |
– |
|||
>>Current QoS Parameters Set Index |
O |
Alternative QoS Parameters Set Notify Index 9.2.3.104 |
Index to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative parameter set. |
YES |
ignore |
Range bound |
Explanation |
maxnoofQoSFlows |
Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
9.2.3.58 Request Reporting Reference ID
This IE contains the Request Reporting Reference ID and is used for UE presence in Area of Interest reporting as specified in TS 23.502 [13].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Request Reporting Reference ID |
M |
INTEGER (1..64, …) |
9.2.3.59 User plane traffic activity report
This IE is used to indicate user plane traffic activity.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
User plane traffic activity report |
M |
ENUMERATED (inactive, re-activated, …) |
"re-activated" is only set after "inactive" has been reported for the concerned reporting object |
9.2.3.60 Lower Layer presence status change
This IE is used to indicate that lower layer resources’ presence status shall be changed. If the presence status is set to "release lower layers" or "suspend lower layers", SDAP entities, PDCP entities, Xn-U bearer resources, NG-U bearer resources and UE context information shall be kept.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Lower Layer presence status change |
M |
ENUMERATED (release lower layers, re-establish lower layers, …, suspend lower layers, resume lower layers) |
"re-establish lower layers" is only set after "release lower layers" has been indicated. "resume lower layers" shall restore SCG. "resume lower layers" shall be only set after "suspend lower layers" has been indicated. |
9.2.3.61 RRC Resume Cause
The purpose of the RRC Resume Cause IE is to indicate to the old NG-RAN node the reason for the RRC Connection Resume as received from the UE in the ResumeCause defined in TS 36.331 [14] and TS 38.331 [10]. In this version of the specification, this is limited to the case of RNA update.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
RRC Resume Cause |
M |
ENUMERATED (rna-Update, …) |
9.2.3.62 Priority Level
This IE indicates the Priority Level for a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Priority Level |
M |
INTEGER (1..127, …) |
Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 127 as the lowest priority. |
9.2.3.63 PDCP SN Length
The PDCP SN Length IE is used to indicate the PDCP SN length configuration of the bearer.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
UL PDCP SN Length |
M |
ENUMERATED (12bits, 18bits, …) |
This IE indicates the PDCP sequence number size for UL. |
|
DL PDCP SN Length |
M |
ENUMERATED (12bits, 18bits, …) |
This IE indicates the PDCP sequence number size for DL. |
9.2.3.64 UE History Information
The UE History Information IE contains information about cells that a UE has been served by in active state prior to the target cell. The overall mechanism is described in TS 36.300 [12].
NOTE: The definition of this IE is aligned with the definition of the UE History Information IE in TS 38.413 [5].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Last Visited Cell List |
1..<maxnoofCellsinUEHistoryInfo> |
Most recent information is added to the top of this list |
||
>Last Visited Cell Information |
M |
9.2.3.65 |
Range bound |
Explanation |
maxnoofCellsinUEHistoryInfo |
Maximum number of last visited cell information records that can be reported in the IE. Value is 16. |
9.2.3.65 Last Visited Cell Information
The Last Visited Cell Information may contain cell specific information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE Last Visited Cell Information |
M |
|||
>NG-RAN Cell |
||||
>>Last Visited NG-RAN Cell Information |
M |
OCTET STRING |
Defined in TS 38.413 [5]. |
|
>E-UTRAN Cell |
||||
>>Last Visited E-UTRAN Cell Information |
M |
OCTET STRING |
Defined in TS 36.413 [31]. |
|
>UTRAN Cell |
||||
>>Last Visited UTRAN Cell Information |
M |
OCTET STRING |
Defined in TS 25.413 [32]. |
|
>GERAN Cell |
||||
>>Last Visited GERAN Cell Information |
M |
OCTET STRING |
Defined in TS 36.413 [31]. |
9.2.3.66 Paging DRX
This IE indicates the RAN paging cycle as defined in TS 38.304 [33] and TS 36.304 [34].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Paging DRX |
M |
ENUMERATED (32, 64, 128, 256, … , 512, 1024) |
Unit is radio frame. |
9.2.3.67 Security Result
This IE indicates whether the security policy indicated as "preferred" in the Security Indication IE is performed or not.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Integrity Protection Result |
M |
ENUMERATED (performed, not performed, …) |
Indicates whether UP integrity protection is performed or not for the concerned PDU session. |
|
Confidentiality Protection Result |
M |
ENUMERATED (performed, not performed, …) |
Indicates whether UP ciphering is performed or not for the concerned PDU session. |
9.2.3.68 UE Context Kept Indicator
This IE indicates whether the UE Context is kept at the S-NG-RAN node in case of an M-NG-RAN node handover without S-NG-RAN node change or inter-M-NG-RAN node RRC resume without S-NG-RAN node change.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
UE Context Kept Indicator |
M |
ENUMERATED (true, …) |
9.2.3.69 PDU Session Aggregate Maximum Bit Rate
This IE is applicable for all Non-GBR QoS flows per PDU session which is defined for the downlink and the uplink direction and is provided at the Handover Preparation procedure to the target NG-RAN node and at the Retrieve UE Context procedure to the new NG-RAN node as received by the 5GC, during dual connectivity related procedures to the to the S-NG-RAN node as decided by the M-NG-RAN node, as specified in TS 37.340 [8].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDU session Aggregate Maximum Bit Rate |
1 |
Applicable for Non-GBR QoS flows. |
||
>PDU session Aggregate Maximum Bit Rate Downlink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
|
>PDU session Aggregate Maximum Bit Rate Uplink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the PDU session Aggregate Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
9.2.3.70 LCID
This IE uniquely identifies a logical channel ID for the associated DRB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
LCID |
M |
INTEGER (1..32, …) |
Corresponds to the LogicalChannelIdentity defined in TS 38.331 [10]. |
9.2.3.71 Duplication Activation
The Duplication Activation IE indicates the initial status of UL PDCP duplication, i.e., whether UL PDCP Duplication is activated or not.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Duplication Activation |
M |
ENUMERATED ( Active, Inactive, …) |
9.2.3.72 RRC Config Indication
This IE indicates the type of RRC configuration used at the S-NG-RAN node.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
RRC Config Indication |
M |
ENUMERATED (full config, delta config, …) |
9.2.3.73 Maximum Integrity Protected Data Rate
This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [9].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Maximum IP Rate Uplink |
M |
Maximum IP Rate 9.2.3.89 |
Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in UL. If the Maximum IP Rate Downlink IE is absent, this IE applies to both UL and DL. |
– |
||
Maximum IP Rate Downlink |
O |
Maximum IP Rate 9.2.3.89 |
Indicates the maximum aggregate rate for integrity protected DRBs supported by the UE in the DL. |
YES |
ignore |
9.2.3.74 PDCP Change Indication
The PDCP Change Indication IE is used for S-NG-RAN node to either initiate the security key update or to request PDCP data recovery in M-NG-RAN node. The PDCP Change Indication IE is also used for M-NG-RAN node to request PDCP data recovery in S-NG-RAN node.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE PDCP Change Indication |
M |
|||
>From S-NG-RAN node |
||||
>>Indication from S-NG-RAN node to M-NG-RAN node |
M |
ENUMERATED |
S-NG-RAN node key update required indicates that the security key in S-NG-RAN node needs to be updated. The value of PDCP data recovery required indicates that the M-NG-RAN node needs to perform PDCP data recovery. |
|
>From M-NG-RAN node |
||||
>>Indication from M-NG-RAN node to S-NG-RAN node |
M |
ENUMERATED |
The value of PDCP data recovery required indicates that the S-NG-RAN node needs to perform PDCP data recovery. |
9.2.3.75 UL Configuration
This IE indicates how the UL PDCP is configured for the corresponding node.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UL UE Configuration |
M |
ENUMERATED (no-data, shared, only, …) |
Indicates how the UE uses the UL at the corresponding node. |
9.2.3.76 UP Transport Parameters
This IE contains Xn-U related information related to a DRB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UP Transport Parameters |
1 |
|||
>UP Transport Item |
1..<maxnoofSCellGroupsplus1> |
|||
>>UP Transport Layer Information |
M |
9.2.3.30 |
||
>>Cell Group ID |
M |
INTEGER (0..maxnoofSCellGroups, …) |
This IE corresponds to the CellGroupId as defined in TS 38.331 [10] (0=MCG, 1=SCG). In this version of the specification, values "2" and "3" shall not be set by the sender and ignored by the receiver. For E-UTRA Cell Groups, the same encoding is used as for NR Cell Groups. NOTE: There is no corresponding IE defined in TS 36.331 [14]. |
Range bound |
Explanation |
maxnoofSCellGroups |
Maximum no of Secondary Cell Groups. Value is 3. |
9.2.3.77 Desired Activity Notification Level
This IE contains information on which level activity notification shall be performed.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Desired Activity Notification Level |
O |
ENUMERATED (None, QoS Flow, PDU session, UE, …) |
9.2.3.78 Number of DRB IDs
This IE indicates the number of DRB IDs.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Number of DRB IDs |
M |
INTEGER (1..32, …) |
9.2.3.79 QoS Flow Mapping Indication
This IE is used to indicate whether only the uplink or the downlink of a QoS flow is mapped to a DRB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
QoS Flow Mapping Indication |
M |
ENUMERATED (ul, dl, …) |
This IE indicates whether only the uplink or the downlink QoS flow is mapped to the DRB |
9.2.3.80 RLC Status
The RLC Status IE indicates about the RLC configuration change included in the container towards the UE.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Reestablishment Indication |
M |
ENUMERATED (reestablished, …) |
Indicates that following the change of the radio status, the RLC has been re-established. |
9.2.3.81 Expected UE Behaviour
This IE indicates the behaviour of a UE with predictable activity and/or mobility behaviour, to assist the NG-RAN node in determining the optimum RRC connection time and to help with the RRC_INACTIVE state transition and RNA configuration (e.g. size and shape of the RNA).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Expected UE Activity Behaviour |
O |
9.2.3.82 |
||
Expected HO Interval |
O |
ENUMERATED (sec15, sec30, sec60, sec90, sec120, sec180, long-time, …) |
Indicates the expected time interval between inter NG-RAN node handovers. If "long-time" is included, the interval between inter NG-RAN node handovers is expected to be longer than 180 seconds. |
|
Expected UE Mobility |
O |
ENUMERATED (stationary, mobile, …) |
Indicates whether the UE is expected to be stationary or mobile. |
|
Expected UE Moving Trajectory |
0..1 |
Indicates the UE’s expected geographical movement. |
||
>Expected UE Moving Trajectory Item |
1..<maxnoofCellsUEMovingTrajectory> |
Includes list of visited and non-visited cells, where visited cells are listed in the order the UE visited them with the most recent cell being the first in the list. Non-visited cells are included immediately after the visited cell they are associated with. |
||
>>Global NG-RAN Cell Identity |
M |
9.2.2.27 |
||
>>Time Stayed in Cell |
O |
INTEGER (0..4095) |
Included for visited cells and indicates the time a UE stayed in a cell in seconds. If the UE stays in a cell more than 4095 seconds, this IE is set to 4095. |
Range bound |
Explanation |
maxnoofCellsUEMovingTrajectory |
Maximum no. of cells of UE moving trajectory. Value is 16. |
9.2.3.82 Expected UE Activity Behaviour
This IE indicates information about the expected "UE activity behaviour" of the UE or the PDU session as defined in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Expected Activity Period |
O |
INTEGER (1..30|40|50|60|80| 100|120|150|180| 181, …) |
If set to "181" the expected activity time is longer than 180 seconds. The remaining values indicate the expected activity time in [seconds]. |
|
Expected Idle Period |
O |
INTEGER (1..30|40|50|60|80| 100|120|150|180| 181, …) |
If set to "181" the expected idle time is longer than 180 seconds. The remaining values indicate the expected idle time in [seconds]. |
|
Source of UE Activity Behaviour Information |
O |
ENUMERATED (subscription information, statistics, …) |
If "subscription information" is indicated, the information contained in the Expected Activity Period IE and the Expected Idle Period IE, if present, is derived from subscription information. If "statistics" is indicated, the information contained in the Expected Activity Period IE and the Expected Idle Period IE, if present, is derived from statistical information. |
9.2.3.83 AMF Region Information
This IE indicates the Global AMF Region IDs of the AMF Regions to which the NG-RAN node belongs.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
AMF Region Information |
1 |
|||
>Global AMF Region Information Item |
1..<maxnoofAMFRegions> |
|||
>>PLMN Identity |
M |
9.2.2.4 |
||
>>AMF Region Identifier |
1 |
|||
>>>AMF Region ID |
M |
BIT STRING (SIZE (8)) |
Range bound |
Explanation |
maxnoofAMFRegions |
Maximum no. of AMF Regions an NG-RAN node can be connected to. Value is 16. |
9.2.3.84 TNL Association Usage
This IE indicates the usage of the TNL association.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
TNL Association Usage |
O |
ENUMERATED (ue, non-ue, both, …) |
Indicates whether the TNL association is only used for UE associated signalling, or non-UE associated signalling, or both. |
9.2.3.85 Network Instance
This IE provides the network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Network Instance |
M |
INTEGER (1..256, …) |
9.2.3.86 PDCP Duplication Configuration
The PDCP Duplication Configuration IE indicates whether PDCP Duplication is configured or de-configured.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
PDCP Duplication Configuration |
M |
ENUMERATED ( configured, de-configured, …) |
9.2.3.87 Secondary RAT Usage Information
This IE provides information on the Secondary RAT resources used by a PDU Session with MR-DC as specified in TS 37.340 [8].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PDU Session Usage Report |
0..1 |
|||
>RAT Type |
M |
ENUMERATED (nR, e-UTRA, …, nR-unlicensed, eUTRA-unlicensed) |
||
>PDU Session Timed Report List |
M |
Volume Timed Report List 9.2.3.88 |
||
QoS Flows Usage Report List |
0..1 |
|||
>QoS Flows Usage Report Item |
1..<maxnoofQoSflows> |
|||
>>QoS Flow Indicator |
M |
9.2.3.10 |
||
>>RAT Type |
M |
ENUMERATED (nR, eutra, …, nR-unlicensed, eUTRA-unlicensed) |
||
>>QoS Flows Timed Report List |
M |
Volume Timed Report List 9.2.3.88 |
Range bound |
Explanation |
maxnoofQoSFlows |
Maximum no. of QoS flows allowed within one PDU session. Value is 64. |
9.2.3.88 Volume Timed Report List
This IE provides information on the data usage.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Volume Timed Report Item |
1.. <maxnoofTimePeriods> |
|||
>Start Timestamp |
M |
OCTET STRING (SIZE(4)) |
UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [37]. It indicates the start time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. |
|
>End Timestamp |
M |
OCTET STRING (SIZE(4)) |
UTC time encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [37]. It indicates the end time of the collecting period of the included Usage Count UL IE and Usage Count DL IE. |
|
>Usage Count UL |
M |
INTEGER (0..264-1) |
The unit is: octets. |
|
>Usage Count DL |
M |
INTEGER (0..264-1) |
The unit is: octets. |
Range bound |
Explanation |
maxnoofTimePeriods |
Maximum no. of time reporting periods. Value is 2. |
9.2.3.89 Maximum IP Rate
This IE indicates the maximum aggregate data rate for integrity protected DRBs for a UE as defined in TS 38.300 [9].
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Maximum Integrity Protected Data Rate |
M |
ENUMERATED (64kbps, max UE rate, …) |
Defines the upper bound of the aggregate data rate of user plane integrity protected data. |
9.2.3.90 UL Forwarding
This element indicates a proposal for forwarding of uplink packets.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UL Forwarding |
M |
ENUMERATED (UL forwarding proposed, …) |
9.2.3.91 UE Radio Capability for Paging
This IE contains paging specific UE Radio Capability information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Radio Capability for Paging of NR |
O |
OCTET STRING |
Includes the RRC UERadioPagingInformation message as defined in TS 38.331 [10]. |
|
UE Radio Capability for Paging of E-UTRA |
O |
OCTET STRING |
Includes the RRC UERadioPagingInformation message as defined in TS 36.331 [14]. |
9.2.3.92 Common Network Instance
This IE provides the common network instance to be used by the NG-RAN node when selecting a particular transport network resource as described in TS 23.501 [7] in a format common with 5GC.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Common Network Instance |
M |
OCTET STRING |
The octets of OCTET STRING are encoded as the Network Instance field of the Network Instance IE specified in TS 29.244 [45] |
9.2.3.93 Default DRB Allowed
This IE is used to indicate whether the SN is allowed to configure the default DRB for a PDU session or not.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Default DRB Allowed |
M |
ENUMERATED (true, false, …) |
9.2.3.94 Split Session Indicator
This IE indicates whether admitting the requested resources results in a split PDU session.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Split Session Indicator |
M |
ENUMERATED (split, …) |
9.2.3.95 UL Forwarding Proposal
This IE indicates a proposal for forwarding of uplink packets.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UL Forwarding Proposal |
M |
ENUMERATED (UL data forwarding proposed, …) |
9.2.3.96 TNL Configuration Info
This IE is used for signalling IP addresses of IPSEc endpoints used for establishment of IPSec tunnels.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Extended UP Transport Layer Addresses To Add List |
0..1 |
|||
>Extended UP Transport Layer Addresses To Add Item |
1..<maxnoofExtTLAs> |
|||
>>IP-Sec Transport Layer Address |
M |
Transport Layer Address 9.2.3.29 |
Transport Layer Addresses for IP-Sec endpoint. |
|
>>GTP Transport Layer Addresses To Add List |
0..1 |
|||
>>>GTP Transport Layer Addresses To Add Item |
1..<maxnoofGTPTLAs> |
|||
>>>>GTP Transport Layer Address Info |
M |
Transport Layer Address 9.3.2.29 |
GTP Transport Layer Addresses for GTP end-points. |
|
Extended UP Transport Layer Addresses To Remove List |
0..1 |
|||
>Extended UP Transport Layer Addresses To Remove Item |
0..<maxnoofExtTLAs> |
|||
>>IP-Sec Transport Layer Address |
O |
Transport Layer Address 9.2.3.29 |
Transport Layer Addresses for IP-Sec endpoint. |
|
>>GTP Transport Layer Addresses To Remove List |
0..1 |
|||
>>>GTP Transport Layer Addresses To Remove Item |
1..<maxnoofGTPTLAs> |
|||
>>>>GTP Transport Layer Address Info |
M |
Transport Layer Address 9.2.3.2 |
GTP Transport Layer Addresses for GTP end-points. |
Range bound |
Explanation |
maxnoofExtTLAs |
Maximum no. of Extended Transport Layer Addresses in the message. Value is 16. |
maxnoofGTPTLAs |
Maximum no. of GTP Transport Layer Addresses for a GTP end-point in the message. Value is 16. |
9.2.3.97 NG-RAN Trace ID
This IE defines the NG-RAN Trace ID.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NG-RAN Trace ID |
M |
OCTET STRING (SIZE(8)) |
This IE is composed of the following: Trace Reference defined in TS 32.422 [23] (leftmost 6 octets, with PLMN information encoded as in 9.2.2.4), and Trace Recording Session Reference defined in TS 32.422 [23] (last 2 octets). |
9.2.3.98 Non-GBR Resources Offered
This IE indicates whether the MCG offers non-GBR resources for non-GBR QoS flows of the PDU Session Resource.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Non-GBR Resources Offered |
M |
ENUMERATED (true, …) |
9.2.3.99 Extended RAT Restriction Information
This element provides RAT restrictions as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Primary RAT Restriction |
M |
BIT STRING { e-UTRA (0), nR (1), nR-unlicensed (2), nR-LEO (3), nR-MEO (4), nR-GEO (5), nR-OTHERSAT (6)} (SIZE(8, …)) |
Each position in the bitmap represents a Primary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bit 7 reserved for future use. The Primary RAT is the RAT used in the access cell, or target cell. |
|
Secondary RAT Restriction |
M |
BIT STRING { e-UTRA (0), nR (1), e-UTRA-unlicensed (2), nR-unlicensed (3)} (SIZE(8, …)) |
Each position in the bitmap represents a Secondary RAT. If a bit is set to "1", the respective RAT is restricted for the UE. If a bit is set to "0", the respective RAT is not restricted for the UE. Bits 4-7 reserved for future use. A Secondary RAT is a RAT, distinct from the UE’s primary RAT, used in any cell serving the UE excluding the PCell. |
9.2.3.100 5GC Mobility Restriction List Container
This IE contains the Mobility Restriction List IE specified in TS 38.413 [5] as received by the NG-RAN from the 5GC.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
5GC Mobility Restriction List Container |
M |
OCTET STRING |
The octets of the OCTET STRING are encoded according to the specifications of the Mobility Restriction List IE specified in TS 38.413 [5]. |
9.2.3.101 Maximum Number of CHO Preparations
This IE indicates the maximum number of concurrently prepared CHO candidate cells for a UE at a candidate target NG-RAN node.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Maximum Number of CHO Preparations |
M |
INTEGER (1..8, …) |
9.2.3.102 Alternative QoS Parameters Set List
This IE contains alternative sets of QoS parameters which the NG-RAN node can indicate to be fulfilled when notification control is enabled and it cannot fulfil the requested list of QoS parameters.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Alternative QoS Parameters Set Item |
1..<maxnoofQoSparaSets> |
|||
>Alternative QoS Parameters Set Index |
M |
9.2.3.103 |
||
>Guaranteed Flow Bit Rate Downlink |
O |
Bit Rate 9.2.3.4 |
||
>Guaranteed Flow Bit Rate Uplink |
O |
Bit Rate 9.2.3.4 |
||
>Packet Delay Budget |
O |
9.2.3.12 |
||
>Packet Error Rate |
O |
9.2.3.13 |
Range bound |
Explanation |
maxnoofQoSparaSets |
Maximum no. of alternative sets of QoS Parameters allowed for the QoS profile. Value is 8. |
9.2.3.103 Alternative QoS Parameters Set Index
This IE indicates the QoS parameters set which can currently be fulfilled.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Alternative QoS Parameters Set Index |
M |
INTEGER (1..8, …) |
Indicates the index of the item within the Alternative QoS Parameters Set List IE corresponding to the currently fulfilled alternative QoS parameters set. |
9.2.3.104 Alternative QoS Parameters Set Notify Index
This IE indicates the QoS parameters set which can currently be fulfilled.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Alternative QoS Parameters Set Notify Index |
M |
INTEGER (0..8, …) |
Indicates the index of the item within the Alternative QoS Parameters Set List IE corresponding to the currently fulfilled alternative QoS parameters set. Value 0 indicates that NG-RAN cannot even fulfil the lowest alternative QoS parameters set. |
9.2.3.105 NR V2X Services Authorized
This IE provides information on the authorization status of the UE to use the NR sidelink for V2X services.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Vehicle UE |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized as Vehicle UE |
|
Pedestrian UE |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized as Pedestrian UE |
9.2.3.106 LTE V2X Services Authorized
This IE provides information on the authorization status of the UE to use the LTE sidelink for V2X services.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Vehicle UE |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized as Vehicle UE |
|
Pedestrian UE |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized as Pedestrian UE |
9.2.3.107 NR UE Sidelink Aggregate Maximum Bit Rate
This IE provides information on the Aggregate Maximum Bitrate of the UE’s sidelink communication.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NR UE Sidelink Aggregate Maximum Bit Rate |
M |
Bit Rate 9.2.3.4 |
Value 0 shall be considered as a logical error by the receiving NG-RAN node. |
9.2.3.108 LTE UE Sidelink Aggregate Maximum Bit Rate
This IE provides information on the Aggregate Maximum Bitrate of the UE’s sidelink communication for LTE V2X services.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
LTE UE Sidelink Aggregate Maximum Bit Rate |
M |
Bit Rate 9.2.3.4 |
Value 0 shall be considered as a logical error by the receiving NG-RAN node. |
9.2.3.109 PC5 QoS Parameters
This IE provides information on the PC5 QoS parameters of the UE’s sidelink communication for NR PC5.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PC5 QoS Flow List |
1 |
|||
>PC5 QoS Flow Item |
1..<maxnoofPC5QoSFlows> |
|||
>>PQI |
M |
INTEGER (0..255, …) |
PQI is a special 5QI as specified in TS 23.501 [7]. |
|
>>PC5 Flow Bit Rates |
O |
Only applies for GBR QoS Flows. |
||
>>>Guaranteed Flow Bit Rate |
M |
Bit Rate 9.2.3.4 |
Guaranteed Bit Rate for the PC5 QoS flow. Details in TS 23.501 [7]. |
|
>>>Maximum Flow Bit Rate |
M |
Bit Rate 9.2.3.4 |
Maximum Bit Rate for the PC5 QoS flow. Details in TS 23.501 [7]. |
|
>>Range |
O |
ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, …) |
Only applies for groupcast. |
|
PC5 Link Aggregate Bit Rates |
O |
Bit Rate 9.2.3.4 |
Only applies for non-GBR QoS Flows. |
Range bound |
Explanation |
maxnoofPC5QoSFlows |
Maximum no. of PC5 QoS flows allowed towards one UE. Value is 2048. NOTE: ASN.1 value definition of the maxnoofPC5QoSFlows is 2064. The size of the PC5 QoS Flow List shall not exceed 2048 items. |
9.2.3.110 UE History Information from the UE
This IE contains information about mobility history report for a UE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE UE History Information from the UE |
M |
|||
>NR |
||||
>>NR Mobility History Report |
M |
OCTET STRING |
VisitedCellInfoList contained in the UEInformationResponse message (TS 38.331 [10]). |
9.2.3.111 RLC Duplication Information
This IE indicates the RLC duplication configuration in case that the indicated DRB is configured with more than two RLC entities as specified in TS 38.331 [10].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
RLC Activation State List |
1 |
|||
>RLC Activation State Items |
1 .. < maxnoofRLCDuplicationstate > |
This IE indicates information on the initial secondary RLC activation state of UL PDCP duplication. Each position in the list represents a secondary RLC entity in ascending order by the LCH ID in the order of MCG and SCG. |
||
>>Duplication State |
M |
ENUMERATED (Active, Inactive, …) |
||
Primary RLC Indication |
O |
ENUMERATED ( True, False, …) |
This IE is present when DC based PDCP duplication is configured. This IE indicates whether the primary RLC entity located at the assisting node. |
Range bound |
Explanation |
maxnoofRLCDuplicationstate |
Maximum no of Secondary RLC entities. Value is 3. |
9.2.3.112 Redundant PDU Session Information
This IE provides Redundancy information to be applied to a PDU Session.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
RSN |
M |
ENUMERATED (v1, v2, …) |
– |
|||
PDU Session Pair ID |
O |
INTEGER (0..255, …) |
as defined in TS 23.501 [9]. This IE is not used in the response message. If received, the M-NG-RAN node shall ignore it. |
YES |
ignore |
9.2.3.113 Extended Packet Delay Budget
This IE indicates the Packet Delay Budget for a QoS flow.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Extended Packet Delay Budget |
M |
INTEGER (0..65535, …) |
Upper bound value for the delay that a packet may experience expressed in unit of 0.01ms. |
9.2.3.114 TSC Traffic Characteristics
This IE provides the traffic characteristics of TSC QoS flows.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
TSC Assistance Information Downlink |
O |
TSC Assistance Information 9.2.3.115 |
||
TSC Assistance Information Uplink |
O |
TSC Assistance Information 9.2.3.115 |
9.2.3.115 TSC Assistance Information
This IE provides the TSC assistance information for a TSC QoS flow in the uplink or downlink (see TS 23.501 [7]).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Periodicity |
M |
9.2.3.116 |
Periodicity as specified in TS 23.501 [7]. |
– |
||
Burst Arrival Time |
O |
9.2.3.117 |
Burst Arrival Time as specified in TS 23.501 [7]. |
– |
||
Survival Time |
O |
9.2.3.152 |
YES |
ignore |
9.2.3.116 Periodicity
This IE indicates the Periodicity of the TSC QoS flow as defined in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Periodicity |
M |
INTEGER (0..640000, …) |
Periodicity expressed in units of 1 us. |
9.2.3.117 Burst Arrival Time
This IE indicates the Burst Arrival Time of the TSC QoS flow as defined in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Burst Arrival Time |
M |
OCTET STRING |
Encoded in the same format as the ReferenceTime IE as defined in TS 38.331 [10]. The value is truncated to 1 us granularity. |
9.2.3.118 Redundant QoS Flow Indicator
This IE provides the Redundant QoS Flow Indicator for a QoS flows as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Redundant QoS Flow Indicator |
M |
ENUMERATED (true, false) |
This IE indicates if this QoS flow is requested for the redundant transmission. Value "true" indicates that redundant transmission is requested for this QoS flow. Value "false" indicates that redundant transmission is requested to be stopped if started. |
9.2.3.119 NPN Mobility Information
This information element indicates the access restrictions related to an NPN.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE NPN Mobility Information |
M |
|||
>SNPN Mobility Information |
||||
>>Serving NID |
M |
NID 9.2.2.65 |
||
>PNI-NPN Mobility Information |
||||
>>Allowed PNI-NPN ID List |
M |
9.2.3.120 |
9.2.3.120 Allowed PNI-NPN ID List
This IE contains information on allowed UE mobility in PNI-NPN including allowed PNI-NPNs and whether the UE is allowed to access non-CAG cells for each PLMN.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Allowed PNI-NPN ID List |
1..<maxnoofEPLMNs+1> |
|||
>PLMN Identity |
M |
9.2.2.4 |
||
>PNI-NPN Restricted Information |
M |
9.2.3.123 |
||
>Allowed CAG-Identifier List per PLMN |
1..<maxnoofCAGsperPLMN> |
|||
>>CAG-Identifier |
M |
9.2.2.66 |
Range bound |
Explanation |
maxnoofEPLMNs+1 |
Maximum no. of equivalent PLMNs plus one serving PLMN. Value is 16. |
maxnoofCAGsperPLMN |
Maximum number of CAGs per PLMN in UE’s Allowed PNI-NPN ID List. Value is 256. |
9.2.3.121 NPN Paging Assistance Information
This IE contains NPN Paging Assistance Information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE NPN Mobility Information |
M |
|||
>PNI-NPN Information |
||||
>>Allowed PNI-NPN ID List |
M |
9.2.3.120 |
9.2.3.122 Void
Void.
9.2.3.123 PNI-NPN Restricted Information
This IE indicates whether the UE is allowed to access cells that support PNI-NPNs for a PLMN.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PNI-NPN Restricted Information |
M |
ENUMERATED (restricted, not-restricted, …) |
If set to "restricted", the IE indicates that the UE is not allowed to access non-CAG cells for a PLMN. |
9.2.3.124 URI
This IE is defined to contain a URI address.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
URI |
M |
VisibleString |
String representing URI (Uniform Resource Identifier) |
9.2.3.125 MDT Configuration
The IE defines the MDT configuration parameters.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MDT Configuration-NR |
O |
9.2.3.126 |
||
MDT Configuration-EUTRA |
O |
9.2.3.127 |
9.2.3.126 MDT Configuration-NR
The IE defines the MDT configuration parameters of NR.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MDT Activation |
M |
ENUMERATED (Immediate MDT only, Logged MDT only, Immediate MDT and Trace,…) |
||
CHOICE Area Scope of MDT-NR |
O |
|||
>Cell based |
||||
>>Cell ID List for MDT-NR |
1 .. <maxnoofCellIDforMDT> |
|||
>>>NR CGI |
M |
9.2.2.7 |
||
>TA based |
||||
>>TA List for MDT |
1 .. <maxnoofTAforMDT> |
|||
>>>TAC |
M |
OCTET STRING (SIZE (3)) |
The TAI is derived using the current serving PLMN. |
|
>TAI based |
||||
>>TAI List for MDT |
1 .. <maxnoofTAforMDT> |
|||
>>>TAI |
M |
9.2.3.20 |
||
CHOICE MDT Mode |
M |
|||
>Immediate MDT-NR |
||||
>>Measurements to Activate |
M |
BITSTRING (SIZE(8)) |
Each position in the bitmap indicates a MDT measurement, as defined in TS 37.320 [43]. First Bit = M1, Second Bit= M2, Fourth Bit = M4, Fifth Bit = M5, Sixth Bit = logging of M1 from event triggered measurement reports according to existing RRM configuration, Seventh Bit = M6, Eighth Bit = M7. Value "1" indicates "activate" and value "0" indicates "do not activate". This version of the specification does not use bits 3. |
|
>>M1 Configuration |
C-ifM1 |
9.2.3.128 |
||
>>M4 Configuration |
C-ifM4 |
9.2.3.129 |
||
>>M5 Configuration |
C-ifM5 |
9.2.3.130 |
||
>>MDT Location Information |
O |
BITSTRING(SIZE(8)) |
Each position in the bitmap represents requested location information as defined in TS 37.320 [43]. First Bit = GNSS Other bits are reserved for future use and are ignored if received. Value "1" indicates "activate" and value "0" indicates "do not activate". The eNB shall ignore the first bit unless the Measurements to Activate IE has the first bit or the sixth bit set to "1". |
|
>>M6 Configuration |
C-ifM6 |
9.2.3.131 |
||
>>M7 Configuration |
C-ifM7 |
9.2.3.132 |
||
>>Bluetooth Measurement Configuration |
O |
9.2.3.11 |
||
>>WLAN Measurement Configuration |
O |
9.2.3.12 |
||
>>Sensor Measurement Configuration |
O |
9.2.3.136 |
||
>Logged MDT-NR |
||||
>>Logging interval |
M |
ENUMERATED (ms320, ms640, ms1280, ms2560, ms5120, ms10240, ms20480, ms30720, ms40960 and ms61440, infinity) |
This IE is defined in TS 38.331 [10]. The value "infinity" represents one shot logging, i.e., only one log per event in the logged MDT report. |
|
>>Logging duration |
M |
ENUMERATED (10, 20, 40, 60, 90, 120) |
This IE is defined in TS 38.331 [10]. Unit: [minute]. |
|
>>CHOICE Report Type |
M |
|||
>>>Periodical |
||||
>>>Event Triggered |
||||
>>>>Logged Event Trigger Config |
M |
9.2.3.137 |
||
>>Bluetooth Measurement Configuration |
O |
9.2.3.134 |
||
>>WLAN Measurement Configuration |
O |
9.2.3.135 |
||
>>Sensor Measurement Configuration |
O |
9.2.3.136 |
||
>>Area Scope of Neighbour Cells |
O |
9.2.3.140 |
||
>>Early Measurement |
O |
ENUMERATED (true, …) |
This IE indicates whether the UE is allowed to log measurements on early measurement related frequencies in logged MDT as specified in TS 38.331 [10]. |
|
Signalling based MDT PLMN List |
O |
MDT PLMN List 9.2.3.133 |
Range bound |
Explanation |
maxnoofCellIDforMDT |
Maximum no. of Cell ID subject for MDT scope. Value is 32. |
maxnoofTAforMDT |
Maximum no. of TA subject for MDT scope. Value is 8. |
Condition |
Explanation |
ifM1 |
This IE shall be present if the Measurements to Activate IE has the first bit set to "1". |
ifM4 |
This IE shall be present if the Measurements to Activate IE has the fourth bit set to "1". |
ifM5 |
This IE shall be present if the Measurements to Activate IE has the fifth bit set to "1". |
ifM6 |
This IE shall be present if the Measurements to Activate IE has the seventh bit set to "1". |
ifM7 |
This IE shall be present if the Measurements to Activate IE has the eighth bit set to "1". |
9.2.3.127 MDT Configuration-EUTRA
The IE defines the MDT configuration parameters of EUTRA.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MDT Activation |
M |
ENUMERATED(Immediate MDT only, Logged MDT only, Immediate MDT and Trace,…) |
||
CHOICE Area Scope of MDT-E-UTRA |
O |
|||
>Cell based |
||||
>>Cell ID List for MDT |
1 .. <maxnoofCellIDforMDT> |
|||
>>>NR CGI |
M |
9.2.2.7 |
||
>TA based |
||||
>>TA List for MDT |
1 .. <maxnoofTAforMDT> |
|||
>>>TAC |
M |
OCTET STRING (SIZE (3)) |
The TAI is derived using the current serving PLMN. |
|
>TAI based |
||||
>>TAI List for MDT |
1 .. <maxnoofTAforMDT> |
|||
>>>TAI |
M |
9.2.3.20 |
||
MDT Mode E-UTRA |
M |
OCTET STRING |
MDTMode IE defined in TS 36.413 [31]. |
|
Signalling based MDT PLMN List |
O |
MDT PLMN List 9.2.3.133 |
Range bound |
Explanation |
maxnoofCellIDforMDT |
Maximum no. of Cell ID subject for MDT scope. Value is 32. |
maxnoofTAforMDT |
Maximum no. of TA subject for MDT scope. Value is 8. |
9.2.3.128 M1 Configuration
This IE defines the parameters for M1 measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
M1 Reporting Trigger |
M |
ENUMERATED (periodic, A2event-triggered, A2event-triggered periodic, …) |
– |
|||
M1 Threshold Event A2 |
C-ifM1A2trigger |
Included in case of event-triggered or event-triggered periodic reporting for measurement M1. |
– |
|||
>CHOICE Threshold |
M |
– |
||||
>>RSRP |
||||||
>>>Threshold RSRP |
M |
INTEGER (0..127) |
This IE is defined in TS 38.331 [10]. |
– |
||
>>RSRQ |
||||||
>>>Threshold RSRQ |
M |
INTEGER (0..127) |
This IE is defined in TS 38.331 [10]. |
– |
||
>>SINR |
||||||
>>>Threshold SINR |
M |
INTEGER (0..127) |
This IE is defined in TS 38.331 [10]. |
– |
||
M1 Periodic reporting |
C-ifperiodicMDT |
Included in case of periodic or event-triggered periodic reporting for measurement M1. |
– |
|||
>Report interval |
M |
ENUMERATED (ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, min1, min6, min12, min30, min60) |
This IE is defined in TS 38.331 [10]. The value min60 is not used in the specification. |
– |
||
>Report amount |
M |
ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity) |
Number of reports. |
– |
||
>Extended Report interval |
O |
ENUMERATED (ms20480, ms40960,…) |
This IE is the extension of Report interval IE. If this IE is present, the Report interval IE is ignored. |
YES |
ignore |
|
Include Beam Measurements Indication |
O |
ENUMERATED (true, …) |
To configure whether the UE should include beam level measurements. |
YES |
ignore |
|
Beam Measurements Report Configuration |
C-ifM1BeamMeasInd |
YES |
ignore |
|||
>Beam Measurements Report Quantity |
O |
This IE indicates the beam measurement quantity as defined in TS 38.331 [10]. |
– |
|||
>>RSRP |
M |
ENUMERATED (true, …) |
– |
|||
>>RSRQ |
M |
ENUMERATED (true, …) |
– |
|||
>>SINR |
M |
ENUMERATED (true, …) |
– |
|||
>MaxNrofRS-IndexesTo Report |
O |
INTEGER (1..64, …) |
Indicates the max number of beam measurements to be reported as defined in TS 38.331 [10]. |
– |
Condition |
Explanation |
ifM1A2trigger |
This IE shall be present if the Measurements to Activate IE has the first bit set to "1" and the M1 Reporting Trigger IE is set to "A2event-triggered" or to "A2event-triggered periodic". |
ifperiodicMDT |
This IE shall be present if the M1 Reporting Trigger IE is set to "periodic", or to "A2event-triggered periodic". |
ifM1BeamMeasInd |
This IE shall be present if the Include Beam Measurements Indication IE is set to “true”. |
9.2.3.129 M4 Configuration
This IE defines the parameters for M4 measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
M4 Collection Period |
M |
ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, …) |
– |
|||
M4 Links to log |
M |
ENUMERATED(uplink, downlink, both-uplink-and-downlink, …) |
– |
|||
M4 Report Amount |
O |
ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity …) |
Number of reports. |
YES |
ignore |
9.2.3.130 M5 Configuration
This IE defines the parameters for M5 measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
M5 Collection Period |
M |
ENUMERATED (ms1024, ms2048, ms5120, ms10240, min1, …) |
– |
|||
M5 Links to log |
M |
ENUMERATED(uplink, downlink, both-uplink-and-downlink, …) |
– |
|||
M5 Report Amount |
O |
ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity …) |
Number of reports. |
YES |
ignore |
9.2.3.131 M6 Configuration
This IE defines the parameters for M6 measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
M6 Report Interval |
M |
ENUMERATED (ms120,ms240,ms480,ms640,ms1024, ms2048, ms5120, ms10240, ms20480,ms40960,min1,min6,min12,min30, …) |
– |
|||
M6 Links to log |
M |
ENUMERATED(uplink, downlink, both-uplink-and-downlink, …) |
– |
|||
M6 Report Amount |
O |
ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity …) |
Number of reports. |
YES |
ignore |
9.2.3.132 M7 Configuration
This IE defines the parameters for M7 measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
M7 Collection Period |
M |
INTEGER (1..60, …) |
Unit: minutes |
– |
||
M7 Links to log |
M |
ENUMERATED(uplink, downlink, both-uplink-and-downlink, …) |
– |
|||
M7 Report Amount |
O |
ENUMERATED (1, 2, 4, 8, 16, 32, 64, infinity …) |
Number of reports. |
YES |
ignore |
9.2.3.133 MDT PLMN List
The purpose of the MDT PLMN List IE is to provide the list of PLMN allowed for MDT.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MDT PLMN List |
1..<maxnoofMDTPLMNs> |
|||
>PLMN Identity |
M |
9.2.2.4 |
Range bound |
Explanation |
maxnoofMDTPLMNs |
Maximum no. of PLMNs in the MDT PLMN list. Value is 16. |
9.2.3.134 Bluetooth Measurement Configuration
This IE defines the parameters for Bluetooth measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Bluetooth Measurement Configuration |
M |
ENUMERATED (Setup, …) |
||
Bluetooth Measurement Configuration Name List |
0..1 |
This IE is present if the Bluetooth Measurement Configuration IE is set to "Setup". |
||
>Bluetooth Measurement Configuration Name Item IEs |
1 .. <maxnoofBluetoothName> |
|||
>>Bluetooth Measurement Configuration Name |
M |
OCTET STRING (SIZE (1..248)) |
||
BT RSSI |
O |
ENUMERATED (True, …) |
In case of Immediate MDT, it corresponds to M8 measurement as defined in 37.320 [43]. |
Range bound |
Explanation |
maxnoofBluetoothName |
Maximum no. of Bluetooth local name used for Bluetooth measurement collection. Value is 4. |
9.2.3.135 WLAN Measurement Configuration
This IE defines the parameters for WLAN measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
WLAN Measurement Configuration |
M |
ENUMERATED (Setup, …) |
||
WLAN Measurement Configuration Name List |
0..1 |
This IE is present if the WLAN Measurement Configuration IE is set to "Setup". |
||
>WLAN Measurement Configuration Name Item IEs |
1 .. <maxnoofWLANName> |
|||
>>WLAN Measurement Configuration Name |
M |
OCTET STRING (SIZE (1..32)) |
||
WLAN RSSI |
O |
ENUMERATED (True, …) |
In case of Immediate MDT, it corresponds to M8 as defined in 37.320 [43]. |
|
WLAN RTT |
O |
ENUMERATED (True, …) |
In case of Immediate MDT, it corresponds to M9 as defined in 37.320 [43]. |
Range bound |
Explanation |
maxnoofWLANName |
Maximum no. of WLAN SSID used for WLAN measurement collection. Value is 4. |
9.2.3.136 Sensor Measurement Configuration
This IE defines the parameters for Sensor measurement collection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Sensor Measurement Configuration |
M |
ENUMERATED (Setup, …) |
||
Sensor Measurement Configuration Name List |
0..1 |
|||
>Sensor Measurement Configuration Name Item IEs |
1 .. <maxnoofSensorName> |
|||
>>Uncompensated Barometric Configuration |
O |
ENUMERATED (True, …) |
||
>>UE Speed Configuration |
O |
ENUMERATED (True, …) |
||
>>UE Orientation Configuration |
O |
ENUMERATED (True, …) |
Range bound |
Explanation |
maxnoofSensorName |
Maximum no. of Sensor local name used for Sensor measurement collection. Value is 3 |
9.2.3.137 Logged Event Trigger Config
This IE configures with UE with specific events for triggering MDT configuration. Current specified event is based on out of coverage (OOC) detection.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE Event Type Trigger |
M |
|||
>Out of Coverage |
||||
>>Out of Coverage Indication |
ENUMERATED (true, …) |
|||
>L1 Event |
||||
>>CHOICE L1 Event Threshold |
M |
|||
>>>RSRP |
||||
>>>>Threshold RSRP |
M |
INTEGER (0..127) |
This IE is defined in TS 38.331 [10]. |
|
>>>RSRQ |
||||
>>>>Threshold RSRQ |
M |
INTEGER (0..127) |
This IE is defined in TS 38.331 [10]. |
|
>>Hysteresis |
INTEGER (0..30) |
This parameter is used within the entry and leave condition of an event triggered reporting condition. |
||
>>Time to trigger |
ENUMERATED (ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120) |
Time during which specific criteria for the event needs to be met in order to trigger a measurement report. |
9.2.3.138 UE Radio Capability ID
This IE contains UE Capability ID as defined in TS 23.003 [22].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Radio Capability ID |
M |
OCTET STRING |
9.2.3.139 Extended Slice Support List
This IE indicates a list of supported slices.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Slice Support Item |
1..<maxnoofExtSliceItems> |
|||
>S-NSSAI |
M |
9.2.3.21 |
Range bound |
Explanation |
maxnoofExtSliceItems |
Maximum no. of signalled slice support items. Value is 65535. |
9.2.3.140 Area Scope of Neighbour Cells
This IE defines the area scope of neighbour cells for logged MDT.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Area Scope of Neighbour Cells |
M |
1 .. <maxnoofFreqforMDT> |
||
>NR FreqInfo |
M |
9.2.2.19 |
||
>PCI List for MDT |
O |
1 .. <maxnoofNeighPCIforMDT> |
||
>> NRPCI |
M |
INTEGER (0..1007) |
NR Physical Cell ID |
Range bound |
Explanation |
maxnoofFreqforMDT |
Maximum no. of Frequency Information subject for MDT scope. Value is 8. |
maxnoofNeighPCIforMDT |
Maximum no. of Neighbour cells subject for MDT scope. Value is 32. |
9.2.3.141 Extended UE Identity Index Value
This IE is used by the target NG-RAN node to calculate the Paging Frame as specified in TS 36.304[34].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Extended UE Identity Index Value |
M |
BIT STRING (SIZE(16)) |
9.2.3.142 E-UTRA Paging eDRX Information
This IE indicates the E-UTRA Paging eDRX parameters for RRC_IDLE as defined in TS 36.304 [34], if configured by higher layers.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
E-UTRA Paging eDRX Cycle |
M |
ENUMERATED (hfhalf, hf1, hf2, hf4, hf6, hf8, hf10, hf12, hf14, hf16, hf32, hf64, hf128, hf256, …) |
The DRX defined in TS 36.304 [34]. Unit: [number of hyperframes]. |
|
E-UTRA Paging Time Window |
O |
ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, …) |
Unit: [1.28 second]. |
9.2.3.143 UE Specific DRX
This IE indicates the UE specific paging cycle as defined in TS 36.304 [34] and 38.304 [33].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Specific DRX |
M |
ENUMERATED (32, 64, 128, 256, …) |
Unit is radio frame. |
9.2.3.144 QoS Mapping Information
This IE indicates the DSCP and/or IPv6 Flow Label field(s) of IP packets sent in the corresponding GTP-U tunnel.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
DSCP |
O |
BIT STRING (SIZE(6)) |
||
Flow label |
O |
BIT STRING (SIZE(20)) |
9.2.3.145 MRB ID
This IE contains the MRB ID as specified in TS 38.401 [2].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MRB ID |
M |
INTEGER (1..512, …) |
9.2.3.146 MBS Session ID
This IE indicates the MBS Session ID uniquely identifies an MBS session.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
TMGI |
M |
OCTET STRING (SIZE (6)) |
Encoded as defined in TS 23.003 [22]. |
|
NID |
O |
9.2.2.65 |
9.2.3.147 MRB Progress Information
This IE contains the MRB progress Information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE PDCP SN Status |
M |
|||
>12bits |
||||
>>PDCP SN Length 12 |
M |
INTEGER (0..4095) |
||
>18bits |
||||
>>PDCP SN Length 18 |
M |
INTEGER (0..262143) |
9.2.3.148 MBS Area Session ID
This IE indicates the Area Session ID for MBS Session with location dependent context.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBS Area Session ID |
M |
INTEGER (0 .. 65535, …) |
9.2.3.149 MBS Service Area information
This IE contains the MBS service area information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBS Service Area Cell List |
0..<maxnoofCellsforMBS> |
|||
>NR CGI |
M |
9.2.2.7 |
||
MBS Service Area TAI List |
0..<maxnoofTAIforMBS> |
|||
>PLMN Identity |
M |
9.2.2.4 |
||
>TAC |
M |
9.2.2.5 |
Range bound |
Explanation |
maxnoofCellsforMBS |
Maximum no. of cells allowed within one MBS Service Area. Value is 8192. |
maxnoofTAIforMBS |
Maximum no. of TAs allowed within one MBS Service Area. Value is 1024. |
9.2.3.150 MBS Service Area
This IE contains the MBS service area.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CHOICE MBS Service Area |
M |
|||
>location independent |
||||
>>MBS Service Area Information |
M |
9.2.3.149 |
||
>location dependent |
||||
>>MBS Service Area Information Location Dependent List |
1..<maxnoofMBSServiceAreaInformation> |
|||
>>>MBS Area Session ID |
M |
9.2.3.148 |
||
>>>MBS Service Area Information |
M |
9.2.3.149 |
Range bound |
Explanation |
maxnoofMBSServiceAreaInformation |
Maximum no. of MBS Service Area Information elements in the MBS Service Area Information LocationDependent List IE. Value is 256. |
9.2.3.151 SCG UE History Information
This IE contains information about the PSCells served by the secondary node in an active state.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
Last Visited PSCell List |
0..<maxnoofPSCellsPerSN> |
List of cells configured as PSCells. Most recent PSCell related information is added to the top of the list. |
||
>Last Visited PSCell Information |
M |
OCTET STRING |
Defined in TS 38.413 [5] |
Range bound |
Explanation |
maxnoofPSCellsPerSN |
Maximum number of last visited PSCell information records that can be reported in the IE. Value is 8. |
9.2.3.152 Survival Time
This IE provides the Survival Time for a TSC QoS flow (see TS 23.501 [7]).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Survival Time |
M |
INTEGER (0..1920000, …) |
Expressed in units of 1 us. |
9.2.3.153 Time Synchronisation Assistance Information
This IE indicates the 5G access stratum time distribution parameters as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Time Distribution indication |
M |
ENUMERATED (enabled, disabled, …) |
||
Uu Time Synchronization Error Budget |
C-ifEnabled |
INTEGER (0..1000000, …) |
Expressed in units of 1 ns. |
Condition |
Explanation |
ifEnabled |
This IE shall be present if the Time Distribution Indication IE is set to “enabled”. |
9.2.3.154 SCG Activation Request
This IE indicates whether the SCG resources are required to be activated or deactivated.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
SCG Activation Request |
M |
ENUMERATED (Activate SCG, Deactivate SCG, …) |
9.2.3.155 SCG Activation Status
This IE indicates the status of the SCG resources.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
SCG Activation Status |
M |
ENUMERATED (SCG activated, SCG deactivated, …) |
9.2.3.156 QMC Configuration Information
This IE contains the information about the QoE Measurement Collection (QMC) configuration.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Application Layer Measurement Information List |
||||
>UE Application Layer Measurement Information Item |
1..<maxnoofUEAppLayerMeas> |
|||
>>UE Application Layer Measurement Configuration Information |
M |
9.2.3.157 |
Range bound |
Explanation |
maxnoofUEAppLayerMeas |
Maximum no. of simultaneous QoE measurement configurations at a UE. In this version of the specification, the value is 16. |
9.2.3.157 UE Application Layer Measurement Configuration Information
This IE defines the information about the QoE Measurement Collection (QMC) configuration.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
QoE Reference |
M |
OCTET STRING (SIZE(6)) |
QoE Reference, as defined in clause 5.2 of TS 28.405 [55]. It consists of MCC+MNC+QMC ID, where the MCC and MNC are coming with the QMC activation request from the management system to identify one PLMN containing the management system, and QMC ID is a 3 bytes Octet String. |
|
Measurement Configuration Application Layer ID |
O |
INTEGER |
This IE indicates the identity of the application layer measurement configuration, as defined in TS 38.331 [10]. |
|
Service Type |
M |
ENUMERATED (QMC for DASH streaming, QMC for MTSI, QMC for VR, …) |
This IE indicates the service type of QoE measurements. |
|
QoE Measurement Status |
O |
ENUMERATED (ongoing, …) |
Indicates whether the QoE measurement has started. |
|
Container for Application Layer Measurement Configuration |
O |
OCTET STRING (SIZE(1..8000)) |
Contains the signalling based QoE measurement configuration, see Annex L in TS 26.247 [47], clause 16.5 in TS 26.114 [53] and clause 9 in TS 26.118 [54]. |
|
CHOICE MDT Alignment Information |
O |
Indicates the MDT measurements with which alignment is required. |
||
>S-based MDT |
||||
>>NG-RAN Trace ID |
M |
9.2.3.97 |
Indicates the signalling-based MDT measurements with which alignment is required. |
|
Measurement Collection Entity IP Address |
O |
Transport Layer Address 9.2.3.29 |
The IP address of the entity receiving the QoE measurement report. |
|
CHOICE Area Scope of QMC |
O |
|||
>Cell based |
||||
>>Cell ID List for QMC |
1 .. <maxnoofCellIDforQMC> |
|||
>>>Global NG-RAN Cell Identity |
M |
9.2.2.27 |
The included NG-RAN Cell Identity IE can only indicate the NR Cell Identity. |
|
>TA based |
||||
>>TA List for QMC |
1 .. <maxnoofTAforQMC> |
|||
>>>TAC |
M |
9.2.2.5 |
The TAI is derived using the current serving PLMN. |
|
>TAI based |
||||
>>TAI List for QMC |
1 .. <maxnoofTAforQMC> |
|||
>>>TAI |
M |
9.2.3.20 |
||
>PLMN based |
||||
>>PLMN List for QMC |
1 .. <maxnoofPLMNforQMC> |
|||
>>>PLMN Identity |
M |
9.2.2.4 |
||
S-NSSAI List |
O |
0..1 |
||
>S-NSSAI Item |
1 .. <maxnoofSNSSAIforQMC> |
|||
>>S-NSSAI |
M |
S-NSSAI 9.2.3.21 |
||
Available RAN Visible QoE Metrics |
O |
9.2.3.158 |
Present in case of signalling-based QoE. |
Range bound |
Explanation |
maxnoofCellIDforQMC |
Maximum no. of Cell IDs comprising the QMC scope. Value is 32. |
maxnoofTAforQMC |
Maximum no. of TA comprising the QMC scope. Value is 8. |
maxnoofPLMNforQMC |
Maximum no. of PLMNs in the PLMN list for QMC scope. Value is 16. |
maxnoofSNSSAIforQMC |
Maximum no. of S-NSSAIs comprising the QMC scope. Value is 16. |
9.2.3.158 Available RAN Visible QoE Metrics
This IE indicates which RAN visible QoE metrics can be configured by the NG-RAN for the RAN visible QoE measurement.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Buffer Level |
O |
ENUMERATED (true, …) |
This IE defines whether the Buffer Level can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. |
|
Playout Delay for Media Startup |
O |
ENUMERATED (true, …) |
This IE defines whether the Playout delay can be collected as a RAN visible QoE metric by NG-RAN from UE, for DASH streaming and VR service types. |
9.2.3.159 5G ProSe Authorized
This IE provides information on the authorization status of the UE to use the 5G ProSe services.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
5G ProSe Direct Discovery |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized for 5G ProSe Direct Discovery. |
|
5G ProSe Direct Communication |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized for 5G ProSe Direct Communication. |
|
5G ProSe Layer-2 UE-to-Network Relay |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized for 5G ProSe Layer-2 UE-to-Network Relay. |
|
5G ProSe Layer-3 UE-to-Network Relay |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized for 5G ProSe Layer-3 UE-to-Network Relay. |
|
5G ProSe Layer-2 Remote UE |
O |
ENUMERATED (authorized, not authorized, …) |
Indicates whether the UE is authorized for 5G ProSe Layer-2 Remote UE. |
9.2.3.160 5G ProSe PC5 QoS Parameters
This IE provides information on the 5G ProSe PC5 QoS parameters of the UE’s sidelink communication for 5G ProSe services.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
5G ProSe PC5 QoS Flow List |
1 |
|||
>5G ProSe PC5 QoS Flow Item |
1..<maxnoofPC5QoSFlows> |
|||
>>PQI |
M |
INTEGER (0..255, …) |
PQI is a special 5QI as specified in TS 23.501 [7]. |
|
>>5G ProSe PC5 Flow Bit Rates |
O |
Only applies for GBR QoS Flows. |
||
>>>Guaranteed Flow Bit Rate |
M |
Bit Rate 9.2.3.4 |
Guaranteed Bit Rate for the 5G ProSe PC5 QoS flow. Details in TS 23.501 [7]. |
|
>>>Maximum Flow Bit Rate |
M |
Bit Rate 9.2.3.4 |
Maximum Bit Rate for the 5G ProSe PC5 QoS flow. Details in TS 23.501 [7]. |
|
>>Range |
O |
ENUMERATED (m50, m80, m180, m200, m350, m400, m500, m700, m1000, …) |
Only applies for groupcast. |
|
5G ProSe PC5 Link Aggregate Bit Rates |
O |
Bit Rate 9.2.3.4 |
Only applies for non-GBR QoS Flows. |
Range bound |
Explanation |
maxnoofPC5QoSFlows |
Maximum no. of 5G ProSe PC5 QoS flows allowed towards one UE. Value is 2048. |
9.2.3.161 NR Paging eDRX Information
This IE indicates the NR Paging eDRX parameters as defined in TS 38.304 [33].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NR Paging eDRX Cycle |
M |
ENUMERATED (hfquarter, hfhalf, hf1, hf2, hf4, hf8, hf16, hf32, hf64, hf128, hf256, hf512, hf1024, …) |
TeDRX, CN defined in TS 38.304 [33]. Unit: [number of hyperframes]. |
|
NR Paging Time Window |
O |
ENUMERATED (s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s11, s12, s13, s14, s15, s16, …, s17, s18, s19, s20, s21, s22, s23, s24, s25, s26, s27, s28, s29, s30, s31, s32) |
Unit: [1.28 seconds] |
9.2.3.162 NR Paging eDRX Information for RRC INACTIVE
This IE indicates the NR Paging eDRX parameters for RRC_INACTIVE as defined in TS 38.304 [33].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NR Paging eDRX Cycle Inactive |
M |
ENUMERATED (hfquarter, hfhalf, hf1, …) |
TeDRX, RAN defined in TS 38.304 [33]. Unit: [number of hyperframes]. |
9.2.3.163 SDT Support Request
This IE indicates that the UE requested for SDT and may include additional assistance information.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
SDT Indicator |
M |
ENUMERATED (true,…) |
||
SDT assistant information |
O |
ENUMERATED (single packet, multiple packets, …) |
“Single packet” indicates no subsequent SDT transmission is expected; “Multiple packets” indicates subsequent SDT transmission is expected. |
9.2.3.164 Partial UE Context Information for SDT
This IE contains the UE context information within the PARTIAL UE CONTEXT TRANSFER message for NR SDT.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
SDT DRBs To Be Setup List |
0..1 |
YES |
ignore |
|||
>SDT DRBs to Be Setup Item |
1 .. <maxnoofDRBs> |
– |
||||
>>DRB ID |
M |
9.2.3.33 |
– |
|||
>>UL TNL Information |
M |
UP Transport Parameters 9.2.3. 76 |
– |
|||
>>DRB RLC Bearer Configuration |
M |
OCTET STRING |
RLC-BearerConfig IE defined in subclause 6.3.2 of TS 38.331 [10] |
– |
||
>>DRB QoS |
M |
QoS Flow Level QoS Parameters 9.2.3.5 |
– |
|||
>>RLC Mode |
M |
9.2.3.28 |
– |
|||
>>S-NSSAI |
M |
9.2.3.21 |
– |
|||
>>PDCP SN Length |
M |
9.2.3.63 |
– |
|||
>>Flows Mapped to DRB List |
1 |
– |
||||
>>>Flows Mapped to DRB Item |
1 .. <maxnoofQoSFlows> |
– |
||||
>>>>QoS Flow Identifier |
M |
9.2.3.10 |
– |
|||
>>>>QoS Flow Level QoS Parameters |
M |
9.2.3.5 |
– |
|||
>>>>QoS Flow Mapping Indication |
O |
9.2.3.79 |
– |
|||
SDT SRBs to Be Setup List |
1 |
SRB1 is always included. |
YES |
ignore |
||
>SDT SRBs to Be Setup Item |
1 .. <maxnoofSRBs> |
– |
||||
>>SRB ID |
M |
9.2.3.165 |
In this version of the specification, values "0", "3", and "4" are not set by the sender and ignored by the receiver. |
– |
||
>>SRB RLC Bearer Configuration |
M |
OCTET STRING |
RLC-BearerConfig IE defined in subclause 6.3.2 of TS 38.331 [10]. |
– |
Range bound |
Explanation |
maxnoofDRBs |
Maximum no. of DRB allowed towards one UE, the maximum value is 32. |
maxnoofSRBs |
Maximum no. of SRB allowed towards one UE, the maximum value is 5. |
9.2.3.165 SRB ID
This IE uniquely identifies a SRB for a UE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
SRB ID |
M |
INTEGER (0..4, …) |
Corresponds to the identities of SRB as defined in TS 38.331 [10]. |
9.2.3.166 PEIPS Assistance Information
This IE provides the information related to CN paging subgrouping for a particular UE, as specified in TS 38.304 [33].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
CN Subgroup ID |
M |
INTEGER (0..7, …) |
9.2.3.167 UE Slice Maximum Bit Rate List
The UE Slice Maximum Bit Rate List includes a list of UE Slice Maximum Bit Rate, each UE Slice Maximum Bit Rate is applicable for all PDU Sessions associated with a specific S-NSSAI of that UE, which is defined for the Downlink and the Uplink direction as specified in TS 23.501 [7].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
UE Slice Maximum Bit Rate |
1..<maxnoofSMBR> |
|||
>S-NSSAI |
M |
9.3.1.24 |
||
>UE Slice Maximum Bit Rate Downlink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the UE Slice Maximum Bit Rate as specified in TS 23.501 [7] in the downlink direction. |
|
>UE Slice Maximum Bit Rate Uplink |
M |
Bit Rate 9.2.3.4 |
This IE indicates the UE Slice Maximum Bit Rate as specified in TS 23.501 [7] in the uplink direction. |
Range bound |
Explanation |
maxnoofSMBR |
Maximum no. of SLICE MAXIMUM BIT RATE for a UE. Value is 8. |
9.2.3.168 Positioning Information
This IE contains positioning information that assists in the SRS configuration of the UE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Requested SRS Transmission Characteristics |
M |
OCTET STRING |
Requested SRS Transmission Characteristics, as defined in TS 38.455 [49]. |
|
Routing ID |
M |
OCTET STRING |
The maximum length corresponds to NfInstanceId defined in TS 29.571 [50]. |
|
NRPPa Transaction ID |
M |
INTEGER (0..32767) |
NRPPa Transaction ID, as defined in TS 38.455 [49] |
9.2.3.169 MDT PLMN Modification List
The purpose of the MDT PLMN List Modification IE is to provide the modified list of PLMN allowed for MDT.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MDT PLMN Modification List |
0..<maxnoofMDTPLMNs> |
An empty list indicates there is no PLMN allowed for MDT. |
||
>PLMN Identity |
M |
9.2.2.4 |
Range bound |
Explanation |
maxnoofMDTPLMNs |
Maximum no. of PLMNs in the MDT PLMN list. Value is 16. |
9.2.3.170 TAI NSAG Support List
This IE indicates the slice group mapping for all groups supported at the NG-RAN node per TAI.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
NSAG Support Item |
1..<maxnoofNSAGs> |
|||
>NSAG ID |
M |
INTEGER (0.. 255, …) |
||
>NSAG Slice Support List |
M |
Extended Slice Support List 9.2.3.139 |
Indicates the list of slices which belong to the NSAG. |
Range bound |
Explanation |
maxnoofNSAGs |
Maximum no. of Slice Groups for the TAI. Value is 256. |