Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 38.413  Word version:  16.3.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…   9…   9.2.5…   9.3…   9.3.2…   10…

 

8.3.4  UE Context Modification

8.3.4.1  General

The purpose of the UE Context Modification procedure is to partly modify the established UE context. The procedure uses UE-associated signalling.

8.3.4.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.4.2-1: UE context modification: successful operation
Up
Upon receipt of the UE CONTEXT MODIFICATION REQUEST message the NG-RAN node shall
  • if supported, store the received IAB Authorization information in the UE context.
If the Security Key IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall store it and perform AS key re-keying according to TS 33.501.
If the UE Security Capabilities IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall store them and take them into use together with the received keys according to TS 33.501.
If the Index to RAT/Frequency Selection Priority IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.501.
If the RAN Paging Priority IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may use it to determine a priority for paging the UE in RRC_INACTIVE state.
If the UE Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall
  • replace the previously provided UE Aggregate Maximum Bit Rate by the received UE Aggregate Maximum Bit Rate in the UE context;
  • use the received UE Aggregate Maximum Bit Rate for all Non-GBR QoS flows for the concerned UE as specified in TS 23.501.
If the Core Network Assistance Information for RRC INACTIVE IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and use it for e.g. 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 CN Assisted RAN Parameters Tuning IE is included in the UE CONTEXT MODIFICATION 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 UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store this information in the UE context and report to the AMF the User Location Information IE and the RRC State IE in the UE CONTEXT MODIFICATION RESPONSE message.
If the RRC Inactive Transition Report Request IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "cancel report", the NG-RAN node shall, if supported, stop reporting to the AMF the RRC state of the UE.
The NG-RAN node shall report, in the UE CONTEXT MODIFICATION RESPONSE message to the AMF, the successful update of the UE context.
If the Emergency Fallback Indicator IE is included in the UE CONTEXT MODIFICATION REQUEST message, it indicates that the concerned UE context 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 taking into account the Emergency Service Target CN IE if provided.
If the New AMF UE NGAP ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall use the received value for future signalling with the AMF.
If the New GUAMI IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall replace the previously stored GUAMI as specified in TS 23.501.
If the SRVCC Operation Possible IE is included in UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, store the content of the received SRVCC Operation Possible IE in the UE context and use it as defined in TS 23.216.
If the NR V2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, update its V2X services authorization information for the UE accordingly. If the NR V2X Services Authorized IE includes one or more IEs set to "not authorized", the NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).
If the LTE V2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, update its V2X services authorization information for the UE accordingly. If the LTE V2X Services Authorized IE includes one or more IEs set to "not authorized", the NG-RAN node shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).
If the NR UE Sidelink Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported:
  • replace the previously provided NR UE Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value;
  • use the received value for the concerned UE's sidelink communication in network scheduled mode for NR V2X services.
If the LTE UE Sidelink Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported:
  • replace the previously provided LTE UE Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value;
  • use the received value for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services.
If the PC5 QoS Parameters IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node shall, if supported, use it as defined in TS 23.287.
If the UE CONTEXT MODIFICATION 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.
Interactions with RRC Inactive Transition Report procedure:
If the RRC Inactive Transition Report Request IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "single RRC connected state report", the NG-RAN node shall, if supported and if the UE is in RRC_INACTIVE state, send one subsequent RRC INACTIVE TRANSITION REPORT message to the AMF when the RRC state transitions to RRC_CONNECTED state.
If the RRC Inactive Transition Report Request IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to "subsequent state transition report", the NG-RAN node shall, if supported, send the RRC INACTIVE TRANSITION REPORT message to the AMF to report the RRC state of the UE when the UE enters or leaves RRC_INACTIVE state.
Up

8.3.4.3  Unsuccessful OperationWord‑p. 44
Reproduction of 3GPP TS 38.413, Figure 8.3.4.3-1: UE context modification: unsuccessful operation
Up
In case the UE context update cannot be performed successfully, the NG-RAN node shall respond with the UE CONTEXT MODIFICATION FAILURE message to the AMF with an appropriate cause value in the Cause IE.
If the New AMF UE NGAP ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the NG-RAN node may use the received New AMF UE NGAP ID IE or Old AMF UE NGAP ID IE in the UE CONTEXT MODIFICATION FAILURE message.

8.3.4.4  Abnormal Conditions

If the UE CONTEXT MODIFICATION REQUEST message including the New AMF UE NGAP ID IE is received after the NG-RAN node has initiated another class 1 NGAP EP, the NG-RAN node shall be prepared to receive the response message containing an AMF UE NGAP ID with the value received in the New AMF UE NGAP ID IE.

8.3.5  RRC Inactive Transition ReportWord‑p. 45

8.3.5.1  General

The purpose of the RRC Inactive Transition Report procedure is to notify the AMF when the UE enters or leaves RRC_INACTIVE state. The procedure uses UE-associated signalling.

8.3.5.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.5.2-1: RRC Inactive transition report
Up
The NG-RAN node initiates the procedure by sending an RRC INACTIVE TRANSITION REPORT message to the AMF. Upon reception of the RRC INACTIVE TRANSITION REPORT message, the AMF shall take appropriate actions based on the information indicated by the RRC State IE.

8.3.5.3  Abnormal Conditions

Void.

8.3.6  Connection Establishment Indication |R16|

8.3.6.1  General

The purpose of the Connection Establishment Indication procedure is to enable the AMF to complete the establishment of the UE-associated logical NG-connection, The procedure uses UE-associated signalling. This procedure applies only if the NG-RAN node is an ng-eNB.

8.3.6.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.6.2-1: Connection Establishment Indication procedure. Successful operation.
Up
The AMF initiates the procedure by sending a CONNECTION ESTABLISHMENT INDICATION message to the NG-RAN node.
If the UE-associated logical NG-connection is not established, the AMF shall allocate a unique AMF UE NGAP ID to be used for the UE and include it in the CONNECTION ESTABLISHMENT INDICATION message.
If the UE Radio Capability IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as defined in TS 38.300.
If the End Indication IE is included in the CONNECTION ESTABLISHMENT INDICATION message and set to "no further data", the NG-RAN node shall consider that there are no further NAS PDUs to be transmitted for this UE.
If the S-NSSAI IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the Allowed NSSAI IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the UE Differentiation Information IE is included in the CONNECTION ESTABLISHMENT INDICATION 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 DL CP Security Information IE is included in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall forward this information to the UE as described in TS 36.300.
If the NB-IoT UE Priority IE is contained in the CONNECTION ESTABLISHMENT INDICATION message, the NG-RAN node shall, if supported, store this information in the UE context, and use it as specified in TS 23.501.
Up

8.3.6.3  Abnormal ConditionsWord‑p. 46
Void.

8.3.7  AMF CP Relocation Indication |R16|

8.3.7.1  General

The purpose of the AMF CP Relocation Indication procedure is to inform the NG-RAN node that the UE's connection is to be relocated to another NG-RAN node as described in TS 38.300, for a UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB.
The procedure uses UE-associated signalling.

8.3.7.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.7.2-1: AMF CP Relocation Indication. Successful operation.
Up
The AMF initiates the procedure by sending an AMF CP RELOCATION INDICATION message to the NG-RAN node.
Upon reception of the AMF CP RELOCATION INDICATION message, the NG-RAN node shall terminate the delivery of NAS messages that have been received from the AMF.
If the S-NSSAI IE is contained in the AMF CP RELOCATION INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the Allowed NSSAI IE is contained in the AMF CP RELOCATION INDICATION message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
Interactions with NAS Non Delivery Indication procedure:
On reception of the AMF CP RELOCATION INDICATION message, the NG-RAN node may initiate NAS Non Delivery Indication procedure(s) to report the non-delivery of any NAS PDUs previously received from the AMF.
Up

8.3.7.3  Abnormal ConditionsWord‑p. 47
Void.

8.3.8  RAN CP Relocation Indication |R16|

8.3.8.1  General

The purpose of the RAN CP Relocation Indication procedure is to request the AMF to authenticate the UE's re-establishment request, and trigger the establishment of the respective UE-associated logical NG-connection, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB.
The procedure uses UE-associated signalling.

8.3.8.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.8.2-1: RAN CP Relocation Indication.
Up
The NG-RAN node initiates the procedure by sending a RAN CP RELOCATION INDICATION message to the AMF.
The NG-RAN node shall allocate a unique RAN UE NGAP ID to be used for the UE and the NG-RAN node shall include this identity in the RAN CP RELOCATION INDICATION message.
When the NG-RAN node receives the RRCConnectionReestablishmentRequest message, it triggers the RAN CP Relocation Indication procedure including NAS-level security information received from the UE. If the AMF authenticates the request, it initiates the Connection Establishment Indication procedure including NAS-level security information to be sent to the UE in the RRCConnectionReestablishment message.
In case the AMF cannot authenticate the UE's request, the CONNECTION ESTABLISHMENT INDICATION message does not contain security information, and the NG-RAN node shall fail the RRC Re-establishment.
In case of authentication failure, the NG-RAN node and the AMF should locally release the allocated NG resources, if any.
Interactions with the AMF CP Relocation and UE Context Release procedures:
In case of successful UE authentication, the AMF initiates the UE Context Release procedure to release the UE's NG-connection in the old NG-RAN node. The AMF may initiate the AMF CP Relocation procedure before the release procedure in order to trigger the old NG-RAN node to return non-delivered NAS PDUs to the AMF.
Up

8.3.8.3  Abnormal Conditions

Void.

8.3.9  Retrieve UE Information |R16|Word‑p. 48

8.3.9.1  General

The purpose of the Retrieve UE Information procedure is for the NG-RAN node to request the UE information including NB-IoT UE Priority and UE Radio Capability from the AMF, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB.

8.3.9.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.9.2-1: Retrieve UE Information
Up
The NG-RAN node initiates the procedure by sending the RETRIEVE UE INFORMATION message to the AMF.

8.3.9.3  Abnormal Conditions

Void.

8.3.10  UE Information Transfer |R16|

8.3.10.1  General

The purpose of the UE Information Transfer procedure is for the AMF to send the UE information including NB-IoT UE Priority and UE Radio Capability to the NG-RAN node, for a NB-IoT UE using Control Plane CIoT 5GS Optimisation. This procedure applies only if the NG-RAN node is an ng-eNB.

8.3.10.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.10.2-1: UE Information Transfer
Up
The AMF initiates the procedure by sending the UE INFORMATION TRANSFER message to the NG-RAN node.
If the NB-IoT UE Priority IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the UE Radio Capability IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the S-NSSAI IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the Allowed NSSAI IE is contained in the UE INFORMATION TRANSFER message, the NG-RAN node shall store this information in the UE context, and use it as specified in TS 23.501.
If the UE Differentiation Information IE is included in the UE INFORMATION TRANSFER message, the NG-RAN node shall, if supported, store this information in the UE context for further use according to TS 23.501.
Up

8.3.10.3  Abnormal ConditionsWord‑p. 49
Void.

8.3.11  UE Context Suspend |R16|

8.3.11.1  General

The purpose of the UE Context Suspend procedure is to suspend the UE-associated logical NG-connection and the NG-U transport bearer with the 5GC while keeping the UE context in the NG-RAN node.
In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB.

8.3.11.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.11.2-1: UE Context Suspend: Successful operation.
Up
The NG-RAN node initiates the procedure by sending the UE CONTEXT SUSPEND REQUEST message to the AMF.
Upon receipt of the UE CONTEXT SUSPEND REQUEST message the AMF shall act as defined in TS 23.502.
Upon receipt of the UE CONTEXT SUSPEND RESPONSE message the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and send the UE to RRC_IDLE.
If the Information on Recommended Cells and RAN Nodes for Paging IE is included in the UE CONTEXT SUSPEND REQUEST message, the AMF shall, if supported, store it and may use it for subsequent paging.
If the Paging Assistance Data for CE Capable UE IE is included in the UE CONTEXT SUSPEND REQUEST message, the AMF shall, if supported, store it and use it for subsequent paging, as specified in TS 23.502.
If the Security Context IE is included in the UE CONTEXT SUSPEND RESPONSE message, the NG-RAN node shall store the received Security Context IE in the UE context and remove any existing unused stored {NH, NCC} as specified in TS 33.501.
If the Suspend Indicator IE is included in the UE CONTEXT SUSPEND REQUEST message, the SMF shall, if supported, consider the associated PDU session as suspended.
Up

8.3.11.3  Unsuccessful OperationWord‑p. 50
Reproduction of 3GPP TS 38.413, Figure 8.3.11.3-1: UE Context Suspend: unsuccessful operation.
Up
If the AMF decides to not suspend the connection e.g. due to pending downlink data to be sent, it shall send the UE CONTEXT SUSPEND FAILURE message to the NG-RAN node.

8.3.11.4  Abnormal Conditions

Void.

8.3.12  UE Context Resume |R16|

8.3.12.1  General

The purpose of the UE Context Resume procedure is to resume the UE context, the suspended UE-associated logical NG-connection and the related NG-U transport bearer in the 5GC for this UE.
In this version of the specification, this procedure applies only if the NG-RAN node is an ng-eNB.

8.3.12.2  Successful Operation

Reproduction of 3GPP TS 38.413, Figure 8.3.12.2-1: UE Context Resume procedure. Successful operation.
Up
The NG-RAN node initiates the procedure by sending the UE CONTEXT RESUME REQUEST message to the AMF. If the NG-RAN node is not able to admit any suspended PDU sessions, the NG-RAN node shall indicate this in the PDU Session Resource Failed to Resume List IE. If the NG-RAN node is not able to admit certain QoS flows for a PDU session, the NG-RAN node shall indicate this in the QoS Flow Failed to Resume List IE included in the UE Context Resume Request Transfer IE for that PDU session.
Upon receipt of the UE CONTEXT RESUME REQUEST message the AMF shall act as defined in TS 23.502 and respond with the UE CONTEXT RESUME RESPONSE message. If the AMF is not able to admit any suspended PDU sessions, the AMF shall indicate this in the PDU Session Resource Failed to Resume List IE. If the SMF is not able to admit certain QoS flows for a PDU session, the SMF shall indicate this in the QoS Flow Failed to Resume List IE included in the UE Context Resume Response Transfer IE for that PDU session.
The NG-RAN node shall release resources for each PDU session or QoS flow failed to resume and shall assume that the 5GC has released respective resources as well.
If the Security Context IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall store the received Security Context IE in the UE context and the NG-RAN node shall use it for the next suspend/resume or Xn handover or Intra NG-RAN node handovers as specified in TS 33.501.
If the Suspend Request Indication IE is included in the UE CONTEXT RESUME REQUEST message, the AMF shall, if supported, consider that the NG-RAN node is requesting immediate transition to RRC IDLE with Suspend as specified in TS 23.502. If the Suspend Response Indication IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall suspend the UE context, the UE-associated logical NG-connection and the related PDU session contexts and send the UE to RRC_IDLE.
If the Extended Connected Time IE is included in the UE CONTEXT RESUME RESPONSE message, the NG-RAN node shall, if supported, use it as described in TS 23.501.
Up

8.3.12.3  Unsuccessful OperationWord‑p. 51
Reproduction of 3GPP TS 38.413, Figure 8.3.12.3-1: UE Context resume: unsuccessful operation.
Up
If the AMF is not able to resume a single PDU session, it releases the UE-associated logical NG-connection by sending the UE CONTEXT RESUME FAILURE message to the NG-RAN node. Upon reception of the UE CONTEXT RESUME FAILURE message the NG-RAN node shall release the RRC connection as specified in TS 36.331 and release all related signalling and user data transport resources.


Up   Top   ToC