Content for TS 38.413 Word version: 18.2.0

1… 4… 8… 8.2… 8.2.3… 8.3… 8.3.4… 8.4… 8.4.3… 8.5… 8.7… 8.8… 8.10… 8.12… 8.17… 9… 9.2… 9.2.2… 9.2.3… 9.2.4… 9.2.6… 9.2.7… 9.2.9… 9.2.11… 9.2.16… 9.2.17… 9.3… 9.3.1.21… 9.3.1.41… 9.3.1.61… 9.3.1.81… 9.3.1.101… 9.3.1.121… 9.3.1.141… 9.3.1.161… 9.3.1.181… 9.3.1.205… 9.3.1.222… 9.3.1.245… 9.3.2… 9.3.3… 9.3.3.21… 9.3.3.42… 9.3.4… 9.3.4.10… 9.3.5… 9.4… 9.4.4 9.4.5 9.4.6… 9.5… 10…

9.3 Information Element Definitions p. 203

9.3.1 Radio Network Layer Related IEs p. 203

9.3.1.1 Message Type p. 203

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.3.1.2 Cause p. 204

The purpose of the Cause IE is to indicate the reason for a particular event for the NGAP protocol.

IE/Group Name	Presence	IE type and reference
CHOICE Cause Group	M
>Radio Network Layer
>>Radio Network Layer Cause	M	ENUMERATED ( Unspecified, TXnRELOCOverall expiry, Successful handover, Release due to NG-RAN generated reason, Release due to 5GC generated reason, Handover cancelled, Partial handover, Handover failure in target 5GC/NG-RAN node or target system, Handover target not allowed, TNGRELOCoverall expiry, TNG_RELOCprep expiry, Cell not available, Unknown target ID, No radio resources available in target cell, Unknown local UE NGAP ID, Inconsistent remote UE NGAP ID, Handover desirable for radio reasons, Time critical handover, Resource optimisation handover, Reduce load in serving cell, User inactivity, Radio connection with UE lost, Radio resources not available, Invalid QoS combination, Failure in the radio interface procedure, Interaction with other procedure, Unknown PDU Session ID, Unknown QoS Flow ID, Multiple PDU Session ID Instances, Multiple QoS Flow ID Instances, Encryption and/or integrity protection algorithms not supported, NG intra-system handover triggered, NG inter-system handover triggered, Xn handover triggered, Not supported 5QI value, UE context transfer, IMS voice EPS fallback or RAT fallback triggered, UP integrity protection not possible, UP confidentiality protection not possible, Slice(s) not supported, UE in RRC_INACTIVE state not reachable, Redirection, Resources not available for the slice(s), UE maximum integrity protected data rate reason, Release due to CN-detected mobility, N26 interface not available, Release due to pre-emption, Multiple Location Reporting Reference ID Instances, RSN not available for the UP, NPN access denied, CAG only access denied, Insufficient UE Capabilities, RedCap UE not supported, Unknown MBS Session ID, Indicated MBS Session Area Information not served by the gNB, Inconsistent slice info for the session, Misaligned association for the multicast and unicast sessions or flows, eRedCap UE not supported, 2Rx XR UE not supported )
>Transport Layer
>>Transport Layer Cause	M	ENUMERATED ( Transport resource unavailable, Unspecified, …)
>NAS
>>NAS Cause	M	ENUMERATED ( Normal release, Authentication failure, Deregister, Unspecified, …, UE not in PLMN serving area, Mobile IAB not authorized, IAB not authorized )
>Protocol
>>Protocol Cause	M	ENUMERATED ( Transfer syntax error, Abstract syntax error (reject), Abstract syntax error (ignore and notify), Message not compatible with receiver state, Semantic error, Abstract syntax error (falsely constructed message), Unspecified, …)
>Miscellaneous
>>Miscellaneous Cause	M	ENUMERATED ( Control processing overload, Not enough user plane processing resources, Hardware failure, O&M intervention, Unknown PLMN or SNPN, Unspecified, …)

The meaning of the different cause values is described in the following tables. 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
Unspecified	Sent for radio network layer cause when none of the specified cause values applies.
TXnRELOCOverall expiry	The timer guarding the handover that takes place over Xn has abnormally expired.
Successful handover	Successful handover.
Release due to NG-RAN generated reason	Release is initiated due to NG-RAN generated reason.
Release due to 5GC generated reason	Release is initiated due to 5GC generated reason.
Handover cancelled	The reason for the action is cancellation of Handover.
Partial handover	Provides a reason for the handover cancellation. The HANDOVER COMMAND message from AMF contained PDU Session Resource to Release List IE or QoS flow to Release List 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.
Handover failure in target 5GC/ NG-RAN node or target system	The handover failed due to a failure in target 5GC/NG-RAN node or target system.
Handover target not allowed	Handover to the indicated target cell is not allowed for the UE in question.
TNGRELOCoverall expiry	The reason for the action is expiry of timer TNGRELOCoverall.
TNG_RELOCprep expiry	Handover Preparation procedure is cancelled when timer TNG_RELOCprep expires.
Cell not available	The concerned cell is not available.
Unknown target ID	Handover rejected because the target ID is not known to the AMF.
No radio resources available in target cell	Load on target cell is too high.
Unknown local UE NGAP ID	The action failed because the receiving node does not recognise the local UE NGAP ID.
Inconsistent remote UE NGAP ID	The action failed because the receiving node considers that the received remote UE NGAP ID is inconsistent.
Handover desirable for radio reasons	The reason for requesting handover is radio related.
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.
Resource optimisation handover	The reason for requesting handover is to improve the load distribution with the neighbour cells.
Reduce load in serving cell	Load on serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing.
User inactivity	The action is requested due to inactivity on all user data radio bearers (i.e., DRBs and, if applicable, MRBs as per clause 16.10.5.2 of TS 38.300), e.g., NG is requested to be released in order to optimise the radio resources. For L2 U2N Relay UE, this action is requested due to user inactivity on all PDU sessions of L2 U2N Relay UE and its served remote UE(s).
Radio connection with UE lost	The action is requested due to losing the radio connection to the UE.
Radio resources not available	No requested radio resources are available.
Invalid QoS combination	The action was failed because of invalid QoS combination.
Failure in the radio interface procedure	Radio interface procedure has failed.
Interaction with other procedure	The action is due to an ongoing interaction with another procedure.
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 PDU Session ID instances	The action failed because multiple instances of the same PDU Session had been provided to/from 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.
Encryption and/or integrity protection algorithms not supported	The NG-RAN node is unable to support any of the encryption and/or integrity protection algorithms supported by the UE.
NG intra-system handover triggered	The action is due to a NG intra-system handover that has been triggered.
NG inter-system handover triggered	The action is due to a NG inter-system handover that has been triggered.
Xn handover triggered	The action is due to an Xn handover that has been triggered.
Not supported 5QI value	The QoS flow setup failed because the requested 5QI is not supported.
UE context transfer	The action is due to a UE resumes from the NG-RAN node different from the one which sent the UE into RRC_INACTIVE state.
IMS voice EPS fallback or RAT fallback triggered	The setup of QoS flow is failed due to EPS fallback or RAT fallback for IMS voice using handover or redirection.
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.
Slice(s) not supported	Slice(s) not supported.
UE in RRC_INACTIVE state not reachable	The action is requested due to RAN paging failure.
Redirection	The release is requested due to inter-system redirection or intra-system redirection.
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.
Release due to CN-detected mobility	The context release is requested by the AMF because the UE is already served by another CN node (same or different system), or another NG interface of the same CN node.
N26 interface not available	The action failed due to a temporary failure of the N26 interface.
Release due to pre-emption	Release is initiated due to pre-emption.
Multiple Location Reporting Reference ID Instances	The action failed because multiple areas of interest are set with the same Location Reporting Reference ID.
RSN not available for the UP	The redundant user plane resources indicated by RSN are not available.
NPN access denied	Access was denied, or release is requested, for NPN reasons.
CAG only access denied	Access was denied because the cell is a non-CAG cell and UE is only allowed to access CAG cells.
Insufficient UE Capabilities	The procedure can't proceed due to insufficient UE capabilities.
RedCap UE not supported	The action failed because target NG-RAN node does not support RedCap UE.
Unknown MBS Session ID	The action failed because the MBS Session ID is unknown.
Indicated MBS Service Area Information not served by the gNB	The action failed because none of the cells in the indicated MBS Service Area Information are served by the NG-RAN node.
Inconsistent slice info for the session	The action failed because the slice info of the multicast session is inconsistent.
Misaligned association for the multicast and unicast sessions or flows	The action failed because the Associated Unicast QoS Flow ID has already been used, or the Associated Unicast QoS Flow ID is not defined, or the Associated Unicast QoS Flow ID is not released, or multiple MBS QoS flows associated to the same unicast QoS flow, or same multicast session associated to multiple PDU Sessions.
eRedCap UE not supported	The action failed because target NG-RAN node does not support eRedCap UE.
2Rx XR UE not supported	The action failed because target NG-RAN node does not support 2Rx XR UE.

Transport Layer cause	Meaning
Transport resource unavailable	The required transport resources are not available.
Unspecified	Sent when none of the specified cause values applies but still the cause is Transport Network Layer related.

NAS cause	Meaning
Normal release	The release is normal.
Authentication failure	The action is due to authentication failure.
Deregister	The action is due to deregister.
Unspecified	Sent when none of the specified cause values applies but still the cause is NAS related.
UE not in PLMN serving area	The release is due to the UE not being within the serving area of its current PLMN (for NTN).
Mobile IAB not authorized	The release is due to the NG-RAN node having completed the operation for a non-authorized mobile IAB-node.
IAB not authorized	The action is requested due to the NG-RAN node having completed the operation for a non-authorized IAB-node.

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 specified cause values applies but still the cause is Protocol related.

Miscellaneous cause	Meaning
Control processing overload	Control processing overload.
Not enough user plane processing resources	Not enough resources are available related to user plane processing.
Hardware failure	Action related to hardware failure.
O&M intervention	The action is due to O&M intervention.
Unknown PLMN or SNPN	The AMF does not identify any PLMN or SNPN provided by the NG-RAN node.
Unspecified failure	Sent when none of the specified cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer, NAS or Protocol.

9.3.1.3 Criticality Diagnostics p. 210

The Criticality Diagnostics IE is sent by the NG-RAN node or the AMF 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.

For further details on how to use the Criticality Diagnostics IE, see clause 10.

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Procedure Code	O		INTEGER (0..255)	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)	Used only if the Criticality Diagnostics is part of Error Indication procedure.
Procedure Criticality	O		ENUMERATED (reject, ignore, notify)	Used for reporting the Criticality of the Triggering message (Procedure).
Information Element Criticality Diagnostics		0..<maxnoofErrors>
>IE Criticality	M		ENUMERATED (reject, ignore, notify)	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
maxnoofErrors	Maximum no. of IE errors allowed to be reported with a single message. Value is 256.

9.3.1.4 Bit Rate p. 211

This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL or by 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.3.1.5 Global RAN Node ID p. 211

This IE is used to globally identify an NG-RAN node (see TS 38.300).

IE/Group Name	Presence	IE type and reference	Criticality	Assigned Criticality
CHOICE NG-RAN node	M		-
>gNB
>>Global gNB ID	M	9.3.1.6	-
>ng-eNB
>>Global ng-eNB ID	M	9.3.1.8	-
>N3IWF
>>Global N3IWF ID	M	9.3.1.57	-
>TNGF
>>Global TNGF ID	M	9.3.1.161	YES	reject
>TWIF
>>Global TWIF ID	M	9.3.1.163	YES	reject
>W-AGF
>>Global W-AGF ID	M	9.3.1.162	YES	reject

9.3.1.6 Global gNB ID p. 211

This IE is used to globally identify a gNB (see TS 38.300).

IE/Group Name	Presence	IE type and reference	Semantics description
PLMN Identity	M	9.3.3.5
CHOICE gNB ID	M
>gNB ID
>>gNB ID	M	BIT STRING (SIZE(22..32))	Equal to the leftmost bits of the NR Cell Identity IE contained in the NR CGI IE of each cell served by the gNB.

9.3.1.7 NR CGI p. 211

This IE is used to globally identify an NR cell (see TS 38.300).

IE/Group Name	Presence	Range	IE type and reference	Semantics description
PLMN Identity	M		9.3.3.5
NR Cell Identity	M		BIT STRING (SIZE(36))	The leftmost bits of the NR Cell Identity IE correspond to the gNB ID (defined in subclause 9.3.1.6).

9.3.1.8 Global ng-eNB ID p. 212

This IE is used to globally identify an ng-eNB (see TS 38.300).

IE/Group Name	Presence	IE type and reference	Semantics description
PLMN Identity	M	9.3.3.5
CHOICE ng-eNB ID	M
>Macro ng-eNB ID
>>Macro ng-eNB ID	M	BIT STRING (SIZE(20))	Equal to the 20 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB.
>Short Macro ng-eNB ID
>>Short Macro ng-eNB ID	M	BIT STRING (SIZE(18))	Equal to the 18 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB.
>Long Macro ng-eNB ID
>>Long Macro ng-eNB ID	M	BIT STRING (SIZE(21))	Equal to the 21 leftmost bits of the E-UTRA Cell Identity IE contained in the E-UTRA CGI IE of each cell served by the ng-eNB.

9.3.1.9 E-UTRA CGI p. 212

This IE is used to globally identify an E-UTRA cell (see TS 36.300).

IE/Group Name	Presence	Range	IE type and reference	Semantics description
PLMN Identity	M		9.3.3.5
E-UTRA Cell Identity	M		BIT STRING (SIZE(28))	The leftmost bits of the E-UTRA Cell Identity IE correspond to the ng-eNB ID (defined in subclause 9.3.1.8) and to the eNB ID (defined in subclause 9.3.1.165).

9.3.1.10 GBR QoS Flow Information p. 212

This IE indicates QoS parameters for a GBR QoS flow for downlink and uplink.

IE/Group Name	Presence	IE type and reference	Semantics description	Criticality	Assigned Criticality
Maximum Flow Bit Rate Downlink	M	Bit Rate 9.3.1.4	Maximum Bit Rate in DL. Details in TS 23.501.	-
Maximum Flow Bit Rate Uplink	M	Bit Rate 9.3.1.4	Maximum Bit Rate in UL. Details in TS 23.501.	-
Guaranteed Flow Bit Rate Downlink	M	Bit Rate 9.3.1.4	Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501.	-
Guaranteed Flow Bit Rate Uplink	M	Bit Rate 9.3.1.4	Guaranteed Bit Rate (provided there is data to deliver) in UL. Details in TS 23.501.	-
Notification Control	O	ENUMERATED (notification requested, ...)	Details in TS 23.501.	-
Maximum Packet Loss Rate Downlink	O	Packet Loss Rate 9.3.1.79	Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501.	-
Maximum Packet Loss Rate Uplink	O	Packet Loss Rate 9.3.1.79	Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501.	-
Alternative QoS Parameters Set List	O	9.3.1.151	Indicates alternative sets of QoS parameters for the QoS flow.	YES	ignore

9.3.1.11 Void

9.3.1.12 QoS Flow Level QoS Parameters p. 213

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.3.1.28		-
>Dynamic 5QI
>>Dynamic 5QI Descriptor	M		9.3.1.18		-
Allocation and Retention Priority	M		9.3.1.19		-
GBR QoS Flow Information	O		9.3.1.10	This IE shall be present for GBR QoS flows and is ignored otherwise.	-
Reflective QoS Attribute	O		ENUMERATED (subject to, …)	Details in TS 23.501. This IE may be present in case of Non-GBR QoS flows and is ignored otherwise.	-
Additional QoS Flow Information	O		ENUMERATED (more likely, …)	This IE 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 QoS flows and is ignored otherwise.	-
QoS Monitoring Request	O		ENUMERATED (UL, DL, Both, …, stop)	Indicates to measure UL, or DL, or both UL/DL delays for the associated QoS flow or stop the corresponding QoS monitoring.	YES	ignore
QoS Monitoring Reporting Frequency	O		INTEGER (1.. 1800, …)	Indicates the reporting frequency for RAN part delay for QoS monitoring. Units: second	YES	ignore
PDU Set QoS Parameters		0..1			YES	ignore
>UL PDU Set QoS Information	O		PDU Set QoS Information 9.3.1.264		-
>DL PDU Set QoS Information	O		PDU Set QoS Information 9.3.1.264		-

9.3.1.13 QoS Flow List with Cause p. 214

This IE contains a list of QoS flows with a cause value. It is used for example to indicate failed QoS flow(s) or QoS flow(s) to be released.

IE/Group Name	Presence	Range	IE type and reference
QoS Flow Item		1..<maxnoofQoSFlows>
>QoS Flow Identifier	M		9.3.1.51
>Cause	M		9.3.1.2

Range bound	Explanation
maxnoofQoSFlows	Maximum no. of QoS flows allowed within one PDU session. Value is 64.

9.3.1.14 Trace Activation p. 215

This IE defines parameters related to a trace session activation.

IE/Group Name	Presence	IE type and reference	Semantics description	Criticality	Assigned Criticality
NG-RAN Trace ID	M	OCTET STRING (SIZE(8))	This IE is composed of the following: Trace Reference defined in TS 32.422 (leftmost 6 octets, with PLMN information encoded as in clause 9.3.3.5), and Trace Recording Session Reference defined in TS 32.422 (last 2 octets).	-
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.	-
Trace Collection Entity IP Address	M	Transport Layer Address 9.3.2.4	For File based Reporting. Defined in TS 32.422. This IE is ignored if the Trace Collection Entity URI IE is present.	-
MDT Configuration	O	9.3.1.167		YES	ignore
Trace Collection Entity URI	O	URI 9.3.2.14	For Streaming based Reporting. Defined in TS 32.422.	YES	ignore

9.3.1.15 Core Network Assistance Information for RRC INACTIVE p. 216

This IE provides assistance information for RRC_INACTIVE configuration.

IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
UE Identity Index Value	M		9.3.3.23		-
UE Specific DRX	O		Paging DRX 9.3.1.90		-
Periodic Registration Update Timer	M		9.3.3.24		-
MICO Mode Indication	O		9.3.1.23		-
TAI List for RRC Inactive		1			-
>TAI List for RRC Inactive Item		1..<maxnoofTAIforInactive>			-
>>TAI	M		9.3.3.11		-
Expected UE Behaviour	O		9.3.1.93		-
E-UTRA Paging eDRX Information	O		9.3.1.154		YES	ignore
Extended UE Identity Index Value	O		9.3.3.52		YES	ignore
UE Radio Capability for Paging	O		9.3.1.68		YES	ignore
MICO All PLMN	O		9.3.1.194		YES	ignore
NR Paging eDRX Information	O		9.3.1.227		YES	ignore
Paging Cause Indication for Voice Service	O		ENUMERATED (supported, …)	This IE indicates whether the UE supports the feature of indication of paging cause for voice service.	YES	ignore
PEIPS Assistance Information	O		9.3.1.232		YES	ignore
Hashed UE Identity Index Value	O		9.3.3.62		YES	ignore
CN MT Communication Handling	O		ENUMERATED (supported, …)	This IE indicates the CN support of CN based MT communication handling.	YES	ignore

Range bound	Explanation
maxnoofTAIforInactive	Maximum no. of TAIs for RRC Inactive. Value is 16.

9.3.1.16 User Location Information p. 217

This IE is used to provide location information of the UE.

IE/Group Name	Presence	IE type and reference	Semantics description	Criticality	Assigned Criticality
CHOICE User Location Information	M			-
>E-UTRA user location information
>>E-UTRA CGI	M	9.3.1.9		-
>>TAI	M	9.3.3.11		-
>>Age of Location	O	Time Stamp 9.3.1.75	Indicates the UTC time when the location information was generated.	-
>>PSCell Information	O	NG-RAN CGI 9.3.1.73		YES	ignore
>NR user location information
>>NR CGI	M	9.3.1.7		-
>>TAI	M	9.3.3.11	This IE is ignored if the NR NTN TAI Information IE is present.	-
>>Age of Location	O	Time Stamp 9.3.1.75	Indicates the UTC time when the location information was generated.	-
>>PSCell Information	O	NG-RAN CGI 9.3.1.73		YES	ignore
>>NID	O	9.3.3.42		YES	reject
>>NR NTN TAI Information	O	9.3.3.53		YES	ignore
>>Mobile IAB-MT User Location Information	O	9.3.1.260	Indicates the user location information of a mobile IAB-MT, which is co-located with the mobile IAB-DU which serves the UE.	YES	ignore
>N3IWF user location information
>>IP Address	M	Transport Layer Address 9.3.2.4	UE's local IP address used to reach the N3IWF	-
>>Port Number	O	OCTET STRING (SIZE(2))	UDP or TCP source port number if NAT is detected.	-
>>TAI	O	9.3.3.11		YES	ignore
>TNGF user location information				YES	ignore
>>TNAP ID	M	OCTET STRING	TNAP Identifier used to identify the TNAP. Details in TS 29.571.	-
>>IP Address	M	Transport Layer Address 9.3.2.4	UE's local IP address used to reach the TNGF.	-
>>Port Number	O	OCTET STRING (SIZE(2))	UDP or TCP source port number if NAT is detected.	-
>>TAI	O	9.3.3.11		YES	ignore
>TWIF user location information				YES	ignore
>>TWAP ID	M	OCTET STRING	TWAP Identifier used to identify the TWAP. Details in TS 29.571.	-
>>IP Address	M	Transport Layer Address 9.3.2.4	Non-5G-Capable over WLAN device's local IP address used to reach the TWIF.	-
>>Port Number	O	OCTET STRING (SIZE(2))	UDP or TCP source port number if NAT is detected.	-
>>TAI	O	9.3.3.11		YES	ignore
>W-AGF user location information			Indicates the location information via wireline access as specified in TS 23.316.	YES	ignore
>>W-AGF user location information	M	9.3.1.164		-

9.3.1.17 Slice Support List p. 219

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.3.1.24

Range bound	Explanation
maxnoofSliceItems	Maximum no. of signalled slice support items. Value is 1024.

9.3.1.18 Dynamic 5QI Descriptor p. 219

This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink.

IE/Group Name	Presence	IE type and reference	Semantics description	Criticality	Assigned Criticality
Priority Level	M	9.3.1.84	Priority Level is specified in TS 23.501.	-
Packet Delay Budget	M	9.3.1.80	Packet Delay Budget is specified in TS 23.501. This IE is ignored if the Extended Packet Delay Budget IE is present.	-
Packet Error Rate	M	9.3.1.81	Packet Error Rate is specified in TS 23.501.	-
5QI	O	INTEGER (0..255, …)	Indicates the dynamically assigned 5QI as specified in TS 23.501.	-
Delay Critical	C-ifGBRflow	ENUMERATED (delay critical, non-delay critical, …)	Indicates whether the GBR QoS flow is delay critical as specified in TS 23.501.	-
Averaging Window	C-ifGBRflow	9.3.1.82	Averaging Window is specified in TS 23.501.	-
Maximum Data Burst Volume	O	9.3.1.83	Maximum Data Burst Volume is specified in TS 23.501. This IE shall be included if the Delay Critical IE is set to "delay critical" and is ignored otherwise.	-
Extended Packet Delay Budget	O	9.3.1.135	Packet Delay Budget is specified in TS 23.501.	YES	ignore
CN Packet Delay Budget Downlink	O	Extended Packet Delay Budget 9.3.1.135	Core Network Packet Delay Budget is specified in TS 23.501. 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.3.1.135	Core Network Packet Delay Budget is specified in TS 23.501. 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.3.1.19 Allocation and Retention Priority p. 221

This IE specifies the relative importance of a QoS flow compared to other QoS flows for allocation and retention of NG-RAN resources.

IE/Group Name	Presence	IE type and reference	Semantics description
Priority Level	M	INTEGER (1..15)	Desc.: This IE defines the relative importance of a resource request (see TS 23.501). Usage: Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority.
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). Usage: The QoS flow shall not pre-empt other QoS flows 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 NG-RAN node.
Pre-emption Vulnerability	M	ENUMERATED ( not pre-emptable, pre-emptable, …)	Desc.: This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows (see TS 23.501). 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: The 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 NG-RAN node.

9.3.1.20 Source to Target Transparent Container p. 221

This IE is used to transparently pass radio related information from the handover source to the handover target through the core network; it is produced by the source RAN node and is transmitted to the target RAN node.

IE/Group Name	Presence	Range	IE type and reference	Semantics description
Source to Target Transparent Container	M		OCTET STRING	This IE includes a transparent container from the source RAN node to the target RAN node. The octets of the OCTET STRING are encoded according to the specifications of the target system. NOTE: In the current version of the specification, this IE may carry either the Source NG-RAN Node to Target NG-RAN Node Transparent Container IE or the Source eNB to Target eNB Transparent Container IE as defined in TS 36.413 or the Source RNC to Target RNC Transparent Container IE as defined in TS 25.413.