Content for  TS 38.413  Word version:  18.2.0

The purpose of the Initial Context Setup procedure is to establish the necessary overall initial UE context at the NG-RAN node, when required, including PDU session context, the Security Key, Mobility Restriction List, UE Radio Capability and UE Security Capabilities, etc. The AMF may initiate the Initial Context Setup procedure if a UE-associated logical NG-connection exists for the UE or if the AMF has received the RAN UE NGAP ID IE in an INITIAL UE MESSAGE message or if the NG-RAN node has already initiated a UE-associated logical NG-connection by sending an INITIAL UE MESSAGE message via another NG interface instance. The procedure uses UE-associated signalling. For signalling only connections and if the UE Context Request IE is not received in the Initial UE Message, the AMF may be configured to trigger the procedure for all NAS procedures or on a per NAS procedure basis depending on operator's configuration.

In case of the establishment of a PDU session the 5GC shall be prepared to receive user data before the INITIAL CONTEXT SETUP RESPONSE message has been received by the AMF. If no UE-associated logical NG-connection exists, the UE-associated logical NG-connection shall be established at reception of the INITIAL CONTEXT SETUP REQUEST message. The INITIAL CONTEXT SETUP REQUEST message shall contain the Index to RAT/Frequency Selection Priority IE, if available in the AMF. If the NAS-PDU IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall pass it transparently towards the UE. If the Masked IMEISV IE is contained in the INITIAL CONTEXT SETUP REQUEST message the target NG-RAN node shall, if supported, use it to determine the characteristics of the UE for subsequent handling. Upon receipt of the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall

• attempt to execute the requested PDU session configuration;
• store the received UE Aggregate Maximum Bit Rate in the UE context, and use the received UE Aggregate Maximum Bit Rate for Non-GBR QoS flows for the concerned UE as specified in TS 23.501;
• store the received Mobility Restriction List in the UE context;
• store the received UE Radio Capability in the UE context;
• store the received Index to RAT/Frequency Selection Priority in the UE context and use it as defined in TS 23.501;
• store the received UE Security Capabilities in the UE context;
• store the received Security Key in the UE context and, if the NG-RAN node is required to activate security for the UE, take this security key into use;
• if supported, store the received SRVCC Operation Possible in the UE context and use it as defined in TS 23.216;
• store the received NR V2X Services Authorization information, if supported, in the UE context;
• store the received LTE V2X Services Authorization information, if supported, in the UE context;
• store the received NR A2X Services Authorization information, if supported, in the UE context;
• store the received LTE A2X Services Authorization information, if supported, in the UE context;
• store the received NR UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services;
• store the received LTE UE Sidelink Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services;
• store the received NR A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for NR A2X services;
• store the received LTE A2X UE PC5 Aggregate Maximum Bit Rate, if supported, in the UE context, and use it for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services;
• store the received PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.287;
• store the received A2X PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.256.
• store the received Management Based MDT PLMN List information, if supported, in the UE context;
• if supported, store the received IAB Authorization information in the UE context, and use it accordingly for the IAB-MT as specified in TS 38.401;
• store the received 5G ProSe Authorization information in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services;
• store the received 5G ProSe UE PC5 Aggregate Maximum Bit Rate in the UE context, if supported, and use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services;
• store the received 5G ProSe PC5 QoS Parameters, if supported, in the UE context and use it as defined in TS 23.304;
• store the received Ranging and Sidelink Positioning service information, if supported, in the UE context;
• store the received Network Controlled Repeater Authorization, if supported, in the UE context;
• if supported, store the received Mobile IAB Authorization information in the UE context, and use it accordingly for the mobile IAB-MT;
• store the received PDU Set QoS parameters, if supported, in the UE context and use it as specified in TS 23.501.

For the Initial Context Setup an initial value for the Next Hop Chaining Count is stored in the UE context. If the PDU Session Resource Setup Request List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall behave the same as defined in the PDU Session Resource Setup procedure. The NG-RAN node shall report to the AMF in the INITIAL CONTEXT SETUP RESPONSE message the result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure. Upon reception of the INITIAL CONTEXT SETUP RESPONSE message the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Setup Response Transfer IE or PDU Session Resource Setup Unsuccessful Transfer IE to the SMF associated with the concerned PDU session. In case the splitting PDU session is not used by the NG-RAN node, the SMF should remove the Additional Transport Layer Information, if any. The NG-RAN node shall use the information in the Mobility Restriction List IE if present in the INITIAL CONTEXT SETUP REQUEST message to

• determine a target for subsequent mobility action for which the NG-RAN node provides information about the target of the mobility action towards the UE;
• select a proper SCG during dual connectivity operation;
• assign proper RNA(s) for the UE when moving the UE to RRC_INACTIVE state.

If the Mobility Restriction List IE is not contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall consider that no roaming and no access restriction apply to the UE except for the PNI NPN mobility as described in TS 23.501. The NG-RAN node shall also consider that no roaming and no access restriction apply to the UE when:

• one of the QoS flows includes a particular ARP value (TS 23.501).

The NG-RAN node shall consider that roaming or access to CAG cells is only allowed if the Allowed PNI-NPN List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, as described in TS 23.501. If the Trace Activation IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, initiate the requested trace function as described in TS 32.422. In particular, the NG-RAN node shall, if supported:

• if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422;
• if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", "Logged MDT only", initiate the requested MDT session as described in TS 32.422 and the NG-RAN node shall ignore the Interfaces To Trace IE and the Trace Depth IE;
• if the Trace Activation IE includes the MDT Location Information IE within the MDT Configuration IE, store this information and take it into account in the requested MDT session;
• if the Trace Activation IE includes the Signalling Based MDT PLMN List IE within the MDT Configuration IE, the NG-RAN node may use it to propagate the MDT Configuration as described in TS 37.320.
• if the Trace Activation IE includes the Bluetooth Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320.
• if the Trace Activation IE includes the WLAN Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320.
• if the Trace Activation IE includes the Sensor Measurement Configuration IE within the MDT Configuration IE, take it into account for MDT Configuration as described in TS 37.320.
• if the Trace Activation IE includes the MDT Configuration IE and if the NG-RAN node is a gNB at least the MDT Configuration-NR IE shall be present, while if the NG-RAN node is an ng-eNB at least the MDT Configuration-EUTRA IE shall be present.
• if the Trace Activation IE includes the MN Only MDT Collection IE and the MN Only MDT Collection IE is set to "MN only", consider that the MDT Configuration-NR IE or the MDT Configuration-EUTRA IE is only applicable for the MN if the UE is configured with MR-DC.

If the UE Security Capabilities IE included in the INITIAL CONTEXT SETUP REQUEST message only contains the EIA0 or NIA0 algorithm as defined in TS 33.501 and if the EIA0 or NIA0 algorithm is defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501), the NG-RAN node shall take it into use and ignore the keys received in the Security Key IE. If the QMC Configuration Information IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it for QoE management, as described in TS 38.300. If the Assistance Information for QoE Measurement IE is included in the UE Application Layer Measurement Configuration Information IE within the QMC Configuration Information IE, the NG-RAN node may take it into account for controlling the reporting of application layer measurement when the NG-RAN node is overloaded, as described in TS 38.300. If the Core Network Assistance Information for RRC INACTIVE IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it for the RRC_INACTIVE state decision and RNA configuration for the UE and RAN paging if any for a UE in RRC_INACTIVE state, as specified in TS 38.300. If the MICO All PLMN IE is included in the Core Network Assistance Information for RRC INACTIVE IE the NG-RAN node shall, if supported, consider that the registration area for the UE is the full PLMN and ignore the TAI List for RRC Inactive IE. If the Paging Cause Indication for Voice Service IE is included in the Core Network Assistance Information for RRC INACTIVE IE, the NG-RAN node shall, if supported, store and use it as specified in TS 38.300. If the PEIPS Assistance Information IE is included in the Core Network Assistance Information for RRC INACTIVE IE, the NG-RAN node shall, if supported, store it and use it for paging subgrouping the UE in RRC_INACTIVE state, as specified in TS 38.300. If the CN MT Communication Handling IE is included in the Core Network Assistance Information for RRC INACTIVE IE, the NG-RAN node shall, if supported, store it and may subsequently request, based on implementation, the CN for MT communication handling as described in TS 23.502. If the CN Assisted RAN Parameters Tuning IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node may use it as described in TS 23.501. If the RRC Inactive Transition Report Request IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context. If the Emergency Fallback Indicator IE is included in the INITIAL CONTEXT SETUP REQUEST message, it indicates that the UE context to be set up is subject to emergency service fallback as described in TS 23.501 and the NG-RAN node may, if supported, take the appropriate mobility actions. If the Old AMF IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall consider that this UE-associated logical NG-connection was redirected to this AMF from another AMF identified by the Old AMF IE. If the Redirection for Voice EPS Fallback IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store it and use it in a subsequent decision of EPS fallback for voice as specified in TS 23.502. If the Location Reporting Request Type IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node should perform the requested location reporting functionality for the UE as described in subclause 8.12. If the Enhanced Coverage Restriction IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501. If the Extended Connected Time IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it as described in TS 23.501. If the UE Differentiation Information IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501. If the CE-mode-B Restricted IE is included in the INITIAL CONTEXT SETUP REQUEST message and the Enhanced Coverage Restriction IE is not set to "restricted" and the Enhanced Coverage Restriction information stored in the UE context is not set to "restricted", the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 23.501. If the UE User Plane CIoT Support Indicator IE is included in the INITIAL CONTEXT SETUP REQUEST message the NG-RAN node shall, if supported, store this information in the UE context and consider that User Plane CIoT 5GS Optimisation as specified in TS 23.501 is supported for the UE. If the Management Based MDT PLMN List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it to allow subsequent selection of the UE for management based MDT defined in TS 32.422. If the INITIAL CONTEXT SETUP REQUEST message contains the UE Radio Capability ID IE, the NG-RAN node shall, if supported, use it as specified in TS 23.501 and TS 23.502. For each PDU session, if the PDU Session Expected UE Activity Behaviour IE is included in the INTIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, handle this information as specified in TS 23.501. If the Time Synchronisation Assistance Information IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store the information in the UE context and use it as defined in TS 23.501. If the Target NSSAI Information IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node may use this information as specified in TS 23.501. If the Partially Allowed NSSAI IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, deduce from it the partially allowed network slices for the UE, store and replace any previously received Partially Allowed NSSAI and use it as specified in TS 23.501. If the UE Slice Maximum Bit Rate List IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store the received UE Slice Maximum Bit Rate List in the UE context, and use it for each S-NSSAI for the concerned UE as specified in TS 23.501. If the Aerial UE Subscription Information IE is included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it as defined in TS 38.300. If the PNI-NPN Area Scope of MDT IE is included in the MDT Configuration-NR IE included in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall, if supported, use it to derive the MDT area scope for MDT measurement collection in PNI-NPN areas. Upon reception of the PNI-NPN Area Scope of MDT IE, the NG-RAN node shall consider that the area scope for MDT measurement collection in PNI-NPN areas is defined only by the areas included in the PNI-NPN Area Scope of MDT IE. Interactions with Initial UE Message procedure: Interactions with RRC Inactive Transition Report procedure:

If the NG-RAN node is not able to establish an NG UE context, it shall consider the procedure as failed and reply with the INITIAL CONTEXT SETUP FAILURE message. If the PDU Session Resource Setup Request List IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the NG-RAN node shall report to the AMF, in the INITIAL CONTEXT SETUP FAILURE message, the unsuccessful establishment result for each PDU session resource requested to be setup as defined in the PDU Session Resource Setup procedure. Upon reception of the INITIAL CONTEXT SETUP FAILURE message the AMF shall, for each PDU session indicated in the PDU Session ID IE, transfer transparently the PDU Session Resource Setup Unsuccessful Transfer IE to the SMF associated with the concerned PDU session and may consider that the NAS PDU included in the INITIAL CONTEXT SETUP REQUEST message was not delivered.

If the supported algorithms for encryption defined in the Encryption Algorithms IE in the UE Security Capabilities IE, plus the mandated support of EEA0 and NEA0 in all UEs (TS 33.501), do not match any allowed algorithms defined in the configured list of allowed encryption algorithms in the NG-RAN node (TS 33.501), the NG-RAN node shall reject the procedure using the INITIAL CONTEXT SETUP FAILURE message. If the Partially Allowed NSSAI IE is received in the INITIAL CONTEXT SETUP REQUEST message and the total number of S-NSSAIs included in the Allowed NSSAI and Partially Allowed NSSAI exceeds eight, the NG-RAN node shall consider the procedure as failed. If any of the S-NSSAI which is present in the Partially Allowed NSSAI IE is also present in the Allowed NSSAI IE, the NG-RAN node shall consider the procedure as failed. If the supported algorithms for integrity defined in the Integrity Protection Algorithms IE in the UE Security Capabilities IE, plus the mandated support of the EIA0 and NIA0 algorithm in all UEs (TS 33.501), do not match any allowed algorithms defined in the configured list of allowed integrity protection algorithms in the NG-RAN node (TS 33.501), the NG-RAN node shall reject the procedure using the INITIAL CONTEXT SETUP FAILURE message. If the PNI-NPN Area Scope of MDT IE is included in the MDT Configuration-NR IE in the INITIAL CONTEXT SETUP REQUEST message, and the Area Scope of MDT IE is set to "PNI-NPN Based MDT", the NG-RAN node shall, if supported, use the Area Scope of MDT IE to derive the MDT area scope for MDT measurement collection in PNI-NPN areas, and ignore the PNI-NPN Area Scope of MDT.

The purpose of the UE Context Release Request procedure is to enable the NG-RAN node to request the AMF to release the UE-associated logical NG-connection due to NG-RAN node generated reasons. The procedure uses UE-associated signalling.

The NG-RAN node controlling a UE-associated logical NG-connection initiates the procedure by sending a UE CONTEXT RELEASE REQUEST message towards the affected AMF. The UE CONTEXT RELEASE REQUEST message shall indicate the appropriate cause value, e.g., "TXnRELOCOverall Expiry", "Redirection", for the requested UE-associated logical NG-connection release. If the PDU Session Resource List IE is included in the UE CONTEXT RELEASE REQUEST message, the AMF shall handle this information as specified in TS 23.502. Interactions with UE Context Release procedure:

Void.

The purpose of the UE Context Release procedure is to enable the AMF to order the release of the UE-associated logical NG-connection due to various reasons, e.g., completion of a transaction between the UE and the 5GC, or release of the old UE-associated logical NG-connection when the UE has initiated the establishment of a new UE-associated logical NG-connection, etc. The procedure uses UE-associated signalling.

The AMF initiates the procedure by sending the UE CONTEXT RELEASE COMMAND message to the NG-RAN node. The UE CONTEXT RELEASE COMMAND message shall contain both the AMF UE NGAP ID IE and the RAN UE NGAP ID IE if available, otherwise the message shall contain the AMF UE NGAP ID IE. Upon reception of the UE CONTEXT RELEASE COMMAND message, the NG-RAN node shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message. If the PDU Session Resource List IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall handle this information as specified in TS 23.502. If the User Location Information IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall handle this information as specified in TS 23.502. If the Information on Recommended Cells and RAN Nodes for Paging IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall, if supported, store it and may use it for subsequent paging. For each PDU session for which the Secondary RAT Usage Information IE is included in the PDU Session Resource Release Response Transfer IE, the SMF shall handle this information as specified in TS 23.502. If the Paging Assistance Data for CE Capable UE IE is included in the UE CONTEXT RELEASE COMPLETE message, the AMF shall, if supported, store it and use it for subsequent paging, as specified in TS 23.502.

Not applicable.

If the UE Context Release procedure is not initiated towards the NG-RAN node before the expiry of the timer TNG_RELOCOverall, the NG-RAN node shall request the AMF to release the UE context. If the UE returns to the NG-RAN node before the reception of the UE CONTEXT RELEASE COMMAND message or the expiry of the timer TNG_RELOCOverall, the NG-RAN node shall stop the timer TNG_RELOCOverall and continue to serve the UE.