Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.413  Word version:  18.2.0

Top   Top   Up   Prev   Next
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 Definitionsp. 203

9.3.1  Radio Network Layer Related IEsp. 203

9.3.1.1  Message Typep. 203

The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.
IE/Group Name Pre­sence Range IE type and reference Semantics description
Procedure CodeMINTEGER (0..255)
Type of MessageM CHOICE (
Initiating Message,
Successful Outcome,
Unsuccessful Outcome,
…)
Up

9.3.1.2  Causep. 204

The purpose of the Cause IE is to indicate the reason for a particular event for the NGAP protocol.
IE/Group Name Pre­sence Range IE type and reference Semantics description
CHOICE Cause GroupM
>Radio Network Layer
>>Radio Network Layer Cause MENUMERATED (
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,
TNGRELOCprep 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 CauseMENUMERATED (
Transport resource unavailable,
Unspecified,
…)
>NAS
>>NAS CauseMENUMERATED (
Normal release,
Authentication failure,
Deregister,
Unspecified,
…,
UE not in PLMN serving area,
Mobile IAB not authorized,
IAB not authorized
)
>Protocol
>>Protocol CauseMENUMERATED (
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 CauseMENUMERATED (
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
UnspecifiedSent for radio network layer cause when none of the specified cause values applies.
TXnRELOCOverall expiryThe timer guarding the handover that takes place over Xn has abnormally expired.
Successful handoverSuccessful handover.
Release due to NG-RAN generated reasonRelease is initiated due to NG-RAN generated reason.
Release due to 5GC generated reasonRelease is initiated due to 5GC generated reason.
Handover cancelledThe reason for the action is cancellation of Handover.
Partial handoverProvides 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 systemThe handover failed due to a failure in target 5GC/NG-RAN node or target system.
Handover target not allowedHandover to the indicated target cell is not allowed for the UE in question.
TNGRELOCoverall expiryThe reason for the action is expiry of timer TNGRELOCoverall.
TNGRELOCprep expiryHandover Preparation procedure is cancelled when timer TNGRELOCprep expires.
Cell not availableThe concerned cell is not available.
Unknown target IDHandover rejected because the target ID is not known to the AMF.
No radio resources available in target cellLoad on target cell is too high.
Unknown local UE NGAP IDThe action failed because the receiving node does not recognise the local UE NGAP ID.
Inconsistent remote UE NGAP IDThe action failed because the receiving node considers that the received remote UE NGAP ID is inconsistent.
Handover desirable for radio reasonsThe reason for requesting handover is radio related.
Time critical handoverHandover 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 handoverThe reason for requesting handover is to improve the load distribution with the neighbour cells.
Reduce load in serving cellLoad on serving cell needs to be reduced. When applied to handover preparation, it indicates the handover is triggered due to load balancing.
User inactivityThe 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 lostThe action is requested due to losing the radio connection to the UE.
Radio resources not availableNo requested radio resources are available.
Invalid QoS combinationThe action was failed because of invalid QoS combination.
Failure in the radio interface procedureRadio interface procedure has failed.
Interaction with other procedureThe action is due to an ongoing interaction with another procedure.
Unknown PDU Session IDThe action failed because the PDU Session ID is unknown in the NG-RAN node.
Unknown QoS Flow IDThe action failed because the QoS Flow ID is unknown in the NG-RAN node.
Multiple PDU Session ID instancesThe action failed because multiple instances of the same PDU Session had been provided to/from the NG-RAN node.
Multiple QoS Flow ID instancesThe 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 supportedThe NG-RAN node is unable to support any of the encryption and/or integrity protection algorithms supported by the UE.
NG intra-system handover triggeredThe action is due to a NG intra-system handover that has been triggered.
NG inter-system handover triggeredThe action is due to a NG inter-system handover that has been triggered.
Xn handover triggeredThe action is due to an Xn handover that has been triggered.
Not supported 5QI valueThe QoS flow setup failed because the requested 5QI is not supported.
UE context transferThe 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 triggeredThe setup of QoS flow is failed due to EPS fallback or RAT fallback for IMS voice using handover or redirection.
UP integrity protection not possibleThe PDU session cannot be accepted according to the required user plane integrity protection policy.
UP confidentiality protection not possibleThe PDU session cannot be accepted according to the required user plane confidentiality protection policy.
Slice(s) not supportedSlice(s) not supported.
UE in RRC_INACTIVE state not reachableThe action is requested due to RAN paging failure.
RedirectionThe 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 reasonThe 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 mobilityThe 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 availableThe action failed due to a temporary failure of the N26 interface.
Release due to pre-emptionRelease is initiated due to pre-emption.
Multiple Location Reporting Reference ID InstancesThe action failed because multiple areas of interest are set with the same Location Reporting Reference ID.
RSN not available for the UPThe redundant user plane resources indicated by RSN are not available.
NPN access deniedAccess was denied, or release is requested, for NPN reasons.
CAG only access deniedAccess was denied because the cell is a non-CAG cell and UE is only allowed to access CAG cells.
Insufficient UE CapabilitiesThe procedure can't proceed due to insufficient UE capabilities.
RedCap UE not supportedThe action failed because target NG-RAN node does not support RedCap UE.
Unknown MBS Session IDThe action failed because the MBS Session ID is unknown.
Indicated MBS Service Area Information not served by the gNBThe 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 sessionThe action failed because the slice info of the multicast session is inconsistent.
Misaligned association for the multicast and unicast sessions or flowsThe 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 supportedThe action failed because target NG-RAN node does not support eRedCap UE.
2Rx XR UE not supportedThe action failed because target NG-RAN node does not support 2Rx XR UE.
Transport Layer cause Meaning
Transport resource unavailableThe required transport resources are not available.
UnspecifiedSent when none of the specified cause values applies but still the cause is Transport Network Layer related.
NAS cause Meaning
Normal releaseThe release is normal.
Authentication failureThe action is due to authentication failure.
DeregisterThe action is due to deregister.
UnspecifiedSent when none of the specified cause values applies but still the cause is NAS related.
UE not in PLMN serving areaThe release is due to the UE not being within the serving area of its current PLMN (for NTN).
Mobile IAB not authorizedThe release is due to the NG-RAN node having completed the operation for a non-authorized mobile IAB-node.
IAB not authorizedThe action is requested due to the NG-RAN node having completed the operation for a non-authorized IAB-node.
Protocol cause Meaning
Transfer syntax errorThe 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 stateThe received message was not compatible with the receiver state.
Semantic errorThe 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.
UnspecifiedSent when none of the specified cause values applies but still the cause is Protocol related.
Miscellaneous cause Meaning
Control processing overloadControl processing overload.
Not enough user plane processing resourcesNot enough resources are available related to user plane processing.
Hardware failureAction related to hardware failure.
O&M interventionThe action is due to O&M intervention.
Unknown PLMN or SNPNThe AMF does not identify any PLMN or SNPN provided by the NG-RAN node.
Unspecified failureSent 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.
Up

9.3.1.3  Criticality Diagnosticsp. 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 Pre­sence Range IE type and reference Semantics description
Procedure CodeOINTEGER (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 MessageOENUMERATED (initiating message, successful outcome, unsuccessful outcome)Used only if the Criticality Diagnostics is part of Error Indication procedure.
Procedure CriticalityOENUMERATED (reject, ignore, notify)Used for reporting the Criticality of the Triggering message (Procedure).
Information Element Criticality Diagnostics0..<maxnoofErrors>
>IE CriticalityMENUMERATED (reject, ignore, notify)Used for reporting the criticality of the triggering IE. The value 'ignore' is not applicable.
>IE IDMINTEGER (0..65535)The IE ID of the not understood or missing IE.
>Type of ErrorMENUMERATED (not understood, missing, …)
Range bound Explanation
maxnoofErrorsMaximum no. of IE errors allowed to be reported with a single message. Value is 256.
Up

9.3.1.4  Bit Ratep. 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 Pre­sence Range IE type and reference Semantics description
Bit RateMINTEGER (0..4,000,000,000,000, …)The unit is: bit/s
Up

9.3.1.5  Global RAN Node IDp. 211

This IE is used to globally identify an NG-RAN node (see TS 38.300).
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
CHOICE NG-RAN nodeM-
>gNB
>>Global gNB IDM 9.3.1.6-
>ng-eNB
>>Global ng-eNB IDM 9.3.1.8-
>N3IWF
>>Global N3IWF IDM 9.3.1.57-
>TNGF
>>Global TNGF IDM 9.3.1.161YESreject
>TWIF
>>Global TWIF IDM 9.3.1.163YESreject
>W-AGF
>>Global W-AGF IDM 9.3.1.162YESreject
Up

9.3.1.6  Global gNB IDp. 211

This IE is used to globally identify a gNB (see TS 38.300).
IE/Group Name Pre­sence Range IE type and reference Semantics description
PLMN IdentityM 9.3.3.5
CHOICE gNB IDM
>gNB ID
>>gNB IDMBIT 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.
Up

9.3.1.7  NR CGIp. 211

This IE is used to globally identify an NR cell (see TS 38.300).
IE/Group Name Pre­sence Range IE type and reference Semantics description
PLMN IdentityM 9.3.3.5
NR Cell IdentityMBIT STRING (SIZE(36))The leftmost bits of the NR Cell Identity IE correspond to the gNB ID (defined in subclause 9.3.1.6).
Up

9.3.1.8  Global ng-eNB IDp. 212

This IE is used to globally identify an ng-eNB (see TS 38.300).
IE/Group Name Pre­sence Range IE type and reference Semantics description
PLMN IdentityM 9.3.3.5
CHOICE ng-eNB IDM
>Macro ng-eNB ID
>>Macro ng-eNB IDMBIT 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 IDMBIT 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 IDMBIT 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.
Up

9.3.1.9  E-UTRA CGIp. 212

This IE is used to globally identify an E-UTRA cell (see TS 36.300).
IE/Group Name Pre­sence Range IE type and reference Semantics description
PLMN IdentityM 9.3.3.5
E-UTRA Cell IdentityMBIT 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).
Up

9.3.1.10  GBR QoS Flow Informationp. 212

This IE indicates QoS parameters for a GBR QoS flow for downlink and uplink.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Maximum Flow Bit Rate DownlinkMBit Rate
9.3.1.4
Maximum Bit Rate in DL. Details in TS 23.501.-
Maximum Flow Bit Rate UplinkMBit Rate
9.3.1.4
Maximum Bit Rate in UL. Details in TS 23.501.-
Guaranteed Flow Bit Rate DownlinkMBit 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 UplinkMBit Rate
9.3.1.4
Guaranteed Bit Rate (provided there is data to deliver) in UL. Details in TS 23.501.-
Notification ControlOENUMERATED (notification requested, ...) Details in TS 23.501.-
Maximum Packet Loss Rate DownlinkOPacket 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 UplinkOPacket 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 ListO 9.3.1.151Indicates alternative sets of QoS parameters for the QoS flow.YESignore
Up

9.3.1.11Void

9.3.1.12  QoS Flow Level QoS Parametersp. 213

This IE defines the QoS parameters to be applied to a QoS flow.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
CHOICE QoS CharacteristicsM-
>Non-dynamic 5QI
>>Non Dynamic 5QI DescriptorM 9.3.1.28-
>Dynamic 5QI
>>Dynamic 5QI DescriptorM 9.3.1.18-
Allocation and Retention PriorityM 9.3.1.19-
GBR QoS Flow InformationO 9.3.1.10This IE shall be present for GBR QoS flows and is ignored otherwise.-
Reflective QoS AttributeOENUMERATED (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 InformationOENUMERATED (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 RequestOENUMERATED (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.YESignore
QoS Monitoring Reporting FrequencyOINTEGER (1.. 1800, …)Indicates the reporting frequency for RAN part delay for QoS monitoring.
Units: second
YESignore
PDU Set QoS Parameters0..1YESignore
>UL PDU Set QoS InformationOPDU Set QoS Information
9.3.1.264
-
>DL PDU Set QoS InformationOPDU Set QoS Information
9.3.1.264
-
Up

9.3.1.13  QoS Flow List with Causep. 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 Pre­sence Range IE type and reference Semantics description
QoS Flow Item1..<maxnoofQoSFlows>
>QoS Flow IdentifierM 9.3.1.51
>CauseM 9.3.1.2
Range bound Explanation
maxnoofQoSFlowsMaximum no. of QoS flows allowed within one PDU session. Value is 64.
Up

9.3.1.14  Trace Activationp. 215

This IE defines parameters related to a trace session activation.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
NG-RAN Trace IDMOCTET 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 TraceMBIT 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 DepthMENUMERATED (
minimum,
medium,
maximum,
minimumWithoutVendorSpecificExtension,
mediumWithoutVendorSpecificExtension,
maximumWithoutVendorSpecificExtension, …)
Defined in TS 32.422.-
Trace Collection Entity IP AddressMTransport 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 ConfigurationO 9.3.1.167YESignore
Trace Collection Entity URIOURI
9.3.2.14
For Streaming based Reporting.
Defined in TS 32.422.
YESignore
Up

9.3.1.15  Core Network Assistance Information for RRC INACTIVEp. 216

This IE provides assistance information for RRC_INACTIVE configuration.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
UE Identity Index ValueM 9.3.3.23-
UE Specific DRXOPaging DRX
9.3.1.90
-
Periodic Registration Update TimerM 9.3.3.24-
MICO Mode IndicationO 9.3.1.23-
TAI List for RRC Inactive1-
>TAI List for RRC Inactive Item1..<maxnoofTAIforInactive>-
>>TAIM 9.3.3.11-
Expected UE BehaviourO 9.3.1.93-
E-UTRA Paging eDRX InformationO 9.3.1.154YESignore
Extended UE Identity Index ValueO 9.3.3.52YESignore
UE Radio Capability for PagingO 9.3.1.68YESignore
MICO All PLMNO 9.3.1.194YESignore
NR Paging eDRX InformationO 9.3.1.227YESignore
Paging Cause Indication for Voice ServiceOENUMERATED (supported, …) This IE indicates whether the UE supports the feature of indication of paging cause for voice service.YESignore
PEIPS Assistance InformationO 9.3.1.232YESignore
Hashed UE Identity Index ValueO 9.3.3.62YESignore
CN MT Communication HandlingOENUMERATED (supported, …)This IE indicates the CN support of CN based MT communication handling.YESignore
Range bound Explanation
maxnoofTAIforInactiveMaximum no. of TAIs for RRC Inactive. Value is 16.
Up

9.3.1.16  User Location Informationp. 217

This IE is used to provide location information of the UE.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
CHOICE User Location InformationM-
>E-UTRA user location information
>>E-UTRA CGIM 9.3.1.9-
>>TAIM 9.3.3.11-
>>Age of LocationOTime Stamp
9.3.1.75
Indicates the UTC time when the location information was generated.-
>>PSCell InformationONG-RAN CGI
9.3.1.73
YESignore
>NR user location information
>>NR CGIM 9.3.1.7-
>>TAIM 9.3.3.11This IE is ignored if the NR NTN TAI Information IE is present.-
>>Age of LocationOTime Stamp
9.3.1.75
Indicates the UTC time when the location information was generated.-
>>PSCell InformationONG-RAN CGI
9.3.1.73
YESignore
>>NIDO 9.3.3.42YESreject
>>NR NTN TAI InformationO 9.3.3.53YESignore
>>Mobile IAB-MT User Location InformationO 9.3.1.260Indicates the user location information of a mobile IAB-MT, which is co-located with the mobile IAB-DU which serves the UE.YESignore
>N3IWF user location information
>>IP AddressMTransport Layer Address
9.3.2.4
UE's local IP address used to reach the N3IWF-
>>Port NumberOOCTET STRING (SIZE(2))UDP or TCP source port number if NAT is detected.-
>>TAIO 9.3.3.11YESignore
>TNGF user location informationYESignore
>>TNAP IDM OCTET STRING TNAP Identifier used to identify the TNAP. Details in TS 29.571.-
>>IP AddressMTransport Layer Address
9.3.2.4
UE's local IP address used to reach the TNGF.-
>>Port NumberOOCTET STRING (SIZE(2))UDP or TCP source port number if NAT is detected.-
>>TAIO 9.3.3.11YESignore
>TWIF user location informationYESignore
>>TWAP IDMOCTET STRING TWAP Identifier used to identify the TWAP. Details in TS 29.571.-
>>IP AddressMTransport Layer Address
9.3.2.4
Non-5G-Capable over WLAN device's local IP address used to reach the TWIF.-
>>Port NumberOOCTET STRING (SIZE(2))UDP or TCP source port number if NAT is detected.-
>>TAIO 9.3.3.11YESignore
>W-AGF user location informationIndicates the location information via wireline access as specified in TS 23.316.YESignore
>>W-AGF user location informationM 9.3.1.164-
Up

9.3.1.17  Slice Support Listp. 219

This IE indicates the list of supported slices.
IE/Group Name Pre­sence Range IE type and reference Semantics description
Slice Support Item1..<maxnoofSliceItems>
>S-NSSAIM 9.3.1.24
Range bound Explanation
maxnoofSliceItemsMaximum no. of signalled slice support items. Value is 1024.
Up

9.3.1.18  Dynamic 5QI Descriptorp. 219

This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink.
IE/Group Name Pre­sence Range IE type and refe­rence Semantics description Criti­cality Assi­gned Criti­cality
Priority LevelM 9.3.1.84Priority Level is specified in TS 23.501.-
Packet Delay BudgetM 9.3.1.80Packet Delay Budget is specified in TS 23.501. This IE is ignored if the Extended Packet Delay Budget IE is present.-
Packet Error RateM 9.3.1.81Packet Error Rate is specified in TS 23.501.-
5QIOINTEGER (0..255, …)Indicates the dynamically assigned 5QI as specified in TS 23.501.-
Delay CriticalC-ifGBRflowENUMERATED (delay critical, non-delay critical, …)Indicates whether the GBR QoS flow is delay critical as specified in TS 23.501.-
Averaging WindowC-ifGBRflow 9.3.1.82Averaging Window is specified in TS 23.501.-
Maximum Data Burst VolumeO 9.3.1.83Maximum 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 BudgetO 9.3.1.135Packet Delay Budget is specified in TS 23.501.YESignore
CN Packet Delay Budget DownlinkOExtended 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.
YESignore
CN Packet Delay Budget UplinkOExtended 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.
YESignore
Condition Explanation
ifGBRflowThis IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE.
Up

9.3.1.19  Allocation and Retention Priorityp. 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 Pre­sence Range IE type and reference Semantics description
Priority LevelMINTEGER (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 CapabilityM 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 VulnerabilityM 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.
Up

9.3.1.20  Source to Target Transparent Containerp. 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 Pre­sence Range IE type and reference Semantics description
Source to Target Transparent ContainerMOCTET STRINGThis 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.
Up

Up   Top   ToC