Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   Up   Prev   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   4.11.2   4.11.3…   4.12…   4.12.6…   4.12a   4.12b   4.13…   4.13.4…   4.13.6…   4.14…   4.15…   4.15.4…   4.16…   4.16.4…   4.16.8…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24   4.25   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   A…   E…   F…

 

4.2.3  Service Request proceduresWord-p. 46
4.2.3.1  General
The Service Request procedure is used by a UE in CM IDLE state or the 5GC to request the establishment of a secure connection to an AMF. The Service Request procedure is also used both when the UE is in CM-IDLE and in CM-CONNECTED to activate a User Plane connection for an established PDU Session.
The UE shall not initiate a Service Request procedure if there is an ongoing Service Request procedure.
4.2.3.2  UE Triggered Service Request
The UE in CM IDLE state initiates the Service Request procedure in order to send uplink signalling messages, user data, to request emergency services fallback, or as a response to a network paging request. The UE shall not initiate UE Triggered Service Request from CM-IDLE if there is a Service Gap timer running. After receiving the Service Request message, the AMF may perform authentication. After the establishment of the signalling connection to an AMF, the UE or network may send signalling messages, e.g. PDU Session establishment from UE to the SMF, via the AMF.
The Service Request procedure is used by a UE in CM-CONNECTED to request activatation of a User Plane connection for PDU Sessions and to respond to a NAS Notification message from the AMF. When a User Plane connection for a PDU Session is activated, the AS layer in the UE indicates it to the NAS layer.
For any Service Request, the AMF responds with a Service Accept message to synchronize PDU Session status between UE and network, if necessary. The AMF responds with a Service Reject message to UE, if the Service Request cannot be accepted by network. The Service Reject message may include an indication or cause code requesting the UE to perform Registration procedure.
For this procedure, the impacted SMF and UPF, if any, are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved if V-SMF relocation is not triggered.
For Service Request due to user data, network may take further actions if User Plane connection activation is not successful.
The procedure in this clause 4.2.3.2 is applicable to the scenarios with or without intermediate UPF, and with or without intermediate UPF reselection.
If the UE initiates Service Request procedures via non-3GPP Access, functions defined in the clause 4.12.4.1 are applied.
The User Plane of all PDU Sessions with redundant I-UPFs or with redundant N3/N9 tunnels for URLLC shall be activated during the Service Request procedure if the UE in CM-IDLE state initiates the Service Request procedure from 3GPP access. If the redundant I-UPFs are to be added/replaced/removed, the N4 Session procedure to manage the I-UPF is done for each I-UPF in steps 6c, 6d,7a, 7b, 8a, 8b, 9, 10, 17a,17b, 20a, 20b, 21a,21b, 22a and 22b of the figure 4.2.3.2-1. If the redundant N3/N9 tunnels are used for URLLC and the I-UPF is to be added/replaced/removed, the N4 Session procedure to update the tunnel is done for each N3/N9 tunnel in steps 6c, 6d,7a, 7b, 8a, 8b, 9, 10, 17a, 17b. 20a, 20b, 21a, and 21b of the figure 4.2.3.2-1.
Up
Step 1.
UE to (R)AN: AN message (AN parameters, Service Request (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, 5G-S-TMSI, [NAS message container], Exempt Indication)).
The NAS message container shall be included if the UE is sending a Service Request message as an Initial NAS message and the UE needs to send non-cleartext IEs, see clause 4.4.6 in TS 24.501.
The List Of PDU Sessions To Be Activated is provided by UE when the UE wants to re-activate the PDU Session(s). The List Of Allowed PDU Sessions is provided by the UE when the Service Request is a response of a Paging or a NAS Notification for a PDU Session associated with non-3GPP access, and identifies the PDU Sessions that can be transferred to 3GPP access.
In the case of NG-RAN:
  • The AN parameters include 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see TS 23.501, clause 5.30) and Establishment cause. The Establishment cause provides the reason for requesting the establishment of an RRC connection.
  • The UE sends Service Request message towards the AMF encapsulated in an RRC message to the NG-RAN. The RRC message(s) that can be used to carry the 5G-S-TMSI and this NAS message are described in TS 38.331 and TS 36.331.
If the Service Request is triggered by the UE for user data, the UE identifies, using the List Of PDU Sessions To Be Activated, the PDU Session(s) for which the UP connections are to be activated in Service Request message. When the UE includes the List Of PDU Sessions To Be Activated, the UE shall indicate PDU Sessions only associated with the access the Service Request is related to. If the Service Request is triggered by the UE for signalling only, the UE doesn't identify any List Of PDU Sessions To Be Activated. If this procedure is triggered for paging response, and the UE has at the same time some user data to be transferred, the UE identifies the PDU Session(s) whose UP connections are to be activated in Service Request message, by the List Of PDU Sessions To Be Activated. Otherwise the UE does not identify any PDU Session(s) in the Service Request message for paging response. As defined in TS 24.501 the UE shall include always-on PDU Sessions which are accepted by the network in the List Of PDU Sessions To Be Activated even if there are no pending uplink data for those PDU Sessions or when the Service Request is triggered for signalling only or when the Service Request is triggered for paging response.
If the Service Request over 3GPP access is triggered in response to the paging or NAS Notification indicating non-3GPP access, the Service Request message shall identify the list of PDU Sessions associated with the non-3GPP access that can be re-activated over 3GPP in the List Of Allowed PDU Sessions, as described in clause 4.2.3.3 (step 6) of this specification and in clause 5.6.8 of TS 23.501.
If the Service Request is triggered to report PS Data Off status change and the UE is in Non-Allowed Area, the UE shall send Service Request message with an indication that the message is exempted from restriction (e.g. Non-Allowed Area). In this case, if the UE is in Non-Allowed Area, the UE shall not include the List Of PDU Sessions To Be Activated and as a result the always-on PDU Session is not re-activated during the Service Request procedure.
The PDU Session status indicates the PDU Sessions available in the UE.
The UE shall not trigger a Service Request procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN.
NOTE 1:
A PDU Session corresponding to a LADN is not included in the List Of PDU Sessions To Be Activated when the UE is outside the area of availability of the LADN.
For UE in CM-CONNECTED state, only the List Of PDU Sessions To Be Activated and List Of Allowed PDU Sessions need to be included in the Service Request.
Up

Step 2.
(R)AN to AMF: N2 Message (N2 parameters, Service Request).
Details of this step are described in TS 38.413. If the AMF can't handle the Service Request it will reject it.
When NG-RAN is used, the N2 parameters include the 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see TS 23.501, clause 5.30), Location information and Establishment cause, UE Context Request.
If the UE is in CM-IDLE state, the NG-RAN obtains the 5G-S-TMSI in RRC procedure. NG-RAN selects the AMF according to 5G-S-TMSI. The Location Information relates to the cell in which the UE is camping.
Based on the PDU Session status, the AMF may initiate PDU Session Release procedure in the network for the PDU Sessions whose PDU Session ID(s) were indicated by the UE as not available.
When the Establishment cause is associated with priority services (e.g. MPS, MCS), the AMF includes a Message Priority header to indicate priority information. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500.
The AMF enforces the Mobility Restrictions as specified in TS 23.501, clause 5.3.4.1.1.
If there is a Service Gap timer running in AMF for the UE and the AMF is not waiting for a MT paging response from the UE and the Service Request is not for regulatory prioritized services like Emergency services or not for exception reporting, the AMF rejects the Service Request with an appropriate cause. In addition, AMF may also provide a UE with a Mobility Management Back-off timer set to the remaining value of the Service Gap timer.
Up

Step 3a.
AMF to (R)AN: N2 Request (security context, Mobility Restriction List, list of recommended cells / TAs / NG-RAN node identifiers).
If the 5G-AN had requested for UE Context or there is a requirement for AMF to provide this e.g. the AMF needs to initiate fallback procedure as in clause 4.13.4.2 for Emergency services, AMF initiates NGAP procedure as specified in TS 38.413. For UE in CM-IDLE state, 5G-AN stores the Security Context in the UE AN context. Mobility Restriction List is described in TS 23.501, clause 5.3.4.1 "Mobility Restrictions".
The 5G-AN uses the Security Context to protect the messages exchanged with the UE as described in TS 33.501.
If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The RAN may use this information to allocate the RAN Notification Area when the RAN decides to enable RRC Inactive state for the UE.
Up

Step 3.
If the Service Request was not sent integrity protected or integrity protection verification failed, the AMF shall reject the Service Request as stated in TS 24.501.
If the UE in CM-IDLE state triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the UE and the network can exchange NAS signalling and steps 4 to 11 and 15 to 22 are skipped.
If the UE in Non-Allowed Area triggered the Service Request with an indication that the message is exempted from restriction (e.g. Non-Allowed Area), the AMF should accept the Service Request. In this case, if the UE is in Non-Allowed Area, the AMF rejects user plane setup request from the SMF except for emergency services.
If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access, and the AMF received N1 SM Container only from the SMF in step 3a of clause 4.2.3.3, the AMF sends the NAS signalling including the N1 SM Container to the UE in step 7 of clause 4.2.3.3 without updating the access associated to the PDU Session.
Up

Step 4.
[Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID(s), Operation Type, UE location information, Access Type, RAT Type, UE presence in LADN service area, Indication of Access Type can be changed, [MO Exception Data Counter]).
The Nsmf_PDUSession_UpdateSMContext Request is invoked:
  • If the UE identifies List Of PDU Sessions To Be Activated in the Service Request message;
  • This procedure is triggered by the SMF but the PDU Session(s) identified by the UE correlates to other PDU Session ID(s) than the one triggering the procedure; or
  • If this procedure is triggered by the SMF in response to paging or NAS notification indicating 3GPP access, and the current UE location is outside the "Area of validity for the N2 SM information" provided by the SMF in step 3a of clause 4.2.3.3 or the "Area of validity for the N2 SM information" was not provided by the SMF in step 3a of clause 4.2.3.3, the AMF shall not send the N2 information provided by the SMF in step 3a of clause 4.2.3.3. Otherwise, if the current UE location is in the "Area of validity for the N2 SM information", steps 4 to 11 are skipped; or
  • If this procedure is triggered by the SMF in response to paging or NAS notification indicating non-3GPP access, and the AMF received N2 SM Information only, or both N1 SM Container and N2 SM Information in step 3a of clause 4.2.3.3.
If the DNN corresponds to an LADN then the "UE presence in LADN service area" indicates if the UE is IN or OUT of the LADN service area. If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area.
The AMF determines the PDU Session(s) for which the UP connection(s) shall be activated and sends an Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the PDU Session(s) with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s). The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1. If the RAT type is NB-IoT, the AMF shall ensure that the number of PDU session(s) for which UP connection(s) are active does not exceed 2.
If the procedure was triggered in response to paging or NAS Notification indicating non-3GPP access, the AMF received N2 SM Information in step 3a of clause 4.2.3.3 and the PDU Session for which the UE was paged or notified is not in the List Of Allowed PDU Sessions provided by the UE, the AMF notifies the SMF that the UE is not reachable. For other PDU Sessions in the List Of Allowed PDU Sessions the Service Request Procedure succeeds without re-activating the User Plane of any PDU Sessions, unless they have also been included by the UE in the List Of PDU Sessions To Be Activated.
If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access, and the PDU Session for which the UE was paged or notified is in the List Of Allowed PDU Sessions provided by the UE, and the AMF received N2 SM Information only or N1 SM Container and N2 SM Information from the SMF in step 3a of clause 4.2.3.3, the AMF notifies the SMF that the access type of the PDU session can be changed. The AMF discards any already received N1 SM Container and N2 SM Information. In Home Routed roaming case, the V-SMF triggers Nsmf_PDUSession_Update service operation towards the H-SMF to notify the access type of the PDU Session can be changed and the procedure continues as specified in clause 4.3.3.3 from step 1a to step 10.
If the UE is accessing via the NB-IoT RAT, the AMF may update all (H-)SMFs, and the (H-)SMFs may then update UPF(PSA)s and NEFs with whether the RRC establishment cause is set to "MO exception data" or not for Small Data Rate Control purposes, as described in TS 23.501, clause 5.31.14.3. The AMF may immediately send the MO Exception Data Counter to the (H-)SMF. The update may be provided by the N4 Session Modification Request in step 6a or step 7a or an N4 Session Modification Request may be triggered if step 6a and step 7a are skipped.
The AMF may receive a Service Request to establish another NAS signalling connection via a NG-RAN while it has maintained an old NAS signalling connection for UE still via NG-RAN. In this case, AMF shall trigger the AN release procedure toward the old NG-RAN to release the old NAS signalling connection as defined in clause 4.2.6 with following logic:
  • For the PDU Sessions indicated in the List Of PDU Sessions To Be Activated, the AMF requests the SMF to activate the PDU Session(s) immediately by performing this step 4.
  • For the PDU Sessions indicated in the "List of PDU Session ID(s) with active N3 user plane" but not in the List Of PDU Sessions To Be Activated, the AMF requests the SMF to deactivate the PDU Session(s).
Up

Step 5a.
[Conditional] SMF to PCF: If the AMF notified the SMF that the access type of the PDU session can be changed in step 4, and if PCC is deployed, the SMF perform an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1 if Policy Control Request Trigger condition(s) have been met (i.e. change of Access Type). The PCF may provide updated PCC Rule(s).
Up

Step 5b.
If the PDU Session ID corresponds to a LADN and the SMF determines that the UE is outside the area of availability of the LADN based on the "UE presence in LADN service area" from the AMF, the SMF decides to (based on local policies) either:
  • keep the PDU Session, but reject the activation of User Plane connection for the PDU Session and inform the AMF about it. If the procedure has been triggered by a Network Triggered Service Request as described in clause 4.3.2.3, the SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages; or
  • to release the PDU Session: the SMF releases the PDU Session and informs the AMF that the PDU Session is released.
In any case of the two cases above the SMF answers to the AMF (step10) with an appropriate reject cause and the User Plane Activation of PDU Session is stopped.
Otherwise, based on the location info received from the AMF, the SMF checks the UPF Selection Criteria according to clause 6.3.3 of TS 23.501, and determines to perform one of the following:
  • accepts the activation of UP connection and continue using the current UPF(s);
  • accepts the activation of UP connection and selects a new intermediate UPF (or add/remove an intermediate UPF), if the UE has moved out of the service area of the UPF that was previously connecting to the AN, while maintaining the UPF(s) acting as PDU Session Anchor. The steps to perform I-UPF addition/change/removal are described as conditional steps in the following of the current procedure; or
  • NOTE 2:
    If the old and/or new I-UPF implements an UL CL or BP functionality and a PDU Session Anchor for connectivity to the local access to the Data Network as described in TS 23.501, clause 5.6.4.2, the signalling described in the current clause is intended as the signalling to add, remove or change the PDU Session Anchor, and must be complemented by the signalling to add, release or change the UL CL or BP as described respectively in clauses 4.3.5.4, 4.3.5.5 and 4.3.5.7.
  • rejects the activation of UP connection of a PDU Session of SSC mode 2, and trigger re-establishment of the PDU Session after Service Request procedure to perform the allocation of a new UPF to act as PDU Session Anchor, e.g. the UE has moved out of the service area of the anchor UPF which is connecting to NG-RAN.
In the case that the SMF fails to find suitable I-UPF, the SMF decides to (based on local policies) either:
  • trigger re-establishment of PDU Session. After Service Request procedure, SMF sends N1 SM message to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer containing the cause indicating PDU Session re-establishment is required for the UE; or
  • keep the PDU Session, but reject the activation request of User Plane connection for the PDU Session and inform the AMF about it; or
  • release the PDU Session after Service Request procedure.
If the SMF has determined that the UE is performing Inter-RAT mobility to or from the NB-IoT RAT then the SMF uses the "PDU Session continuity at inter RAT mobility" to determine how to handle the PDU Session.
Up

Step 6a.
[Conditional] SMF to UPF (PSA): N4 Session Modification Request.
Depending on the network deployment, the CN Tunnel Info of UPF (PSA) allocated for N3 or N9 interface may be changed during the Service Request procedure, e.g. UPF connected to different IP domains. If different CN Tunnel Info need be used, the SMF sends N4 Session Modification Request message to UPF (PSA) and requests CN Tunnel Info providing the target Network Instance.
If "MO exception data" is indicated in N4 Session Modification Request, the UPF shall consider all subsequent MO and MT data as "Exception Data" until it receives non "MO exception data" indication.
Up

Step 6b.
[Conditional] UPF (PSA) to SMF: N4 Session Modification Response.
The UPF (PSA) sends an N4 Session Establishment Response message to the SMF. The UPF provides CN Tunnel Info to the SMF. The UPF (PSA) associate the CN Tunnel Info with UL Packet detection rules provided by the SMF.
If the redundant I-UPFs are used for URLLC, each I-UPF provides UL CN Tunnel Info for N3 interface to the SMF in the N4 Session Establishment Response message.
If the redundant N3 tunnels are used for URLLC, the UPF (PSA) provides redundant UL CN Tunnel Info for N3 interface to the SMF in N4 Session Establishment Response message.
Up

Step 6c.
[Conditional] SMF to new UPF (intermediate): N4 Session Establishment Request.
If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, or if the SMF selects to insert an intermediate UPF for a PDU Session which did not have an intermediate UPF, an N4 Session Establishment Request message is sent to the new UPF, providing Packet detection, Data forwarding, enforcement and reporting rules to be installed on the intermediate UPF. The CN Tunnel Info (on N9) of PSA, i.e. which is used to establish the N9 tunnel, for this PDU Session is also provided to the intermediate UPF.
If the Service Request is triggered by the network and a new UPF is selected by the SMF to replace the old (intermediate) UPF, the SMF may also include a request for the UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF. In this case, the UPF begins to buffer the DL data it may receive at the same time from the UPF (PSA) and start a timer.
Up

Step 6d.
New UPF (intermediate) to SMF: N4 Session Establishment Response.
The new intermediate UPF sends an N4 Session Establishment Response message to the SMF. The UPF provides DL CN Tunnel Info as requested by SMF in step 6a. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one.
Up

Step 7a.
[Conditional] SMF to UPF (PSA): N4 Session Modification Request.
If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, the SMF sends N4 Session Modification Request message to PDU Session Anchor UPF, providing DL Tunnel Info from new intermediate UPF. If the new intermediate UPF was added for the PDU Session, the UPF (PSA) begins to send the DL data to the new I-UPF as indicated in the DL CN Tunnel Info. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF.
If the Service Request is triggered by the network, and the SMF removes the old I-UPF but does not replace it with a new I-UPF, the SMF may also include a request for the UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF. In this case, the UPF (PSA) begins to buffer the DL data it may receive at the same time from the N6 interface and start a timer. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to (R)AN.
Up

Step 7b.
The UPF (PSA) sends N4 Session Modification Response message to SMF.
If requested by SMF, the UPF (PSA) sends DL CN tunnel info for the old (intermediate) UPF to the SMF. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one.
If the UPF that connects to RAN is the UPF (PSA), and if the SMF finds that the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF.
Up

Step 8a.
[Conditional] SMF to old UPF (intermediate): N4 Session Modification Request (New UPF address, New UPF DL Tunnel ID)
If the service request is triggered by the network, and the SMF removes the old (intermediate) UPF, the SMF sends the N4 Session Modification Request message to the old (intermediate) UPF, providing the DL Tunnel Info for the buffered DL data. If the SMF allocated new I-UPF, the DL Tunnel Info is from the new (intermediate) UPF acting as N3 terminating point. If the SMF did not allocate a new I-UPF, the DL Tunnel Info is from the new UPF (PSA) acting as N3 terminating point. The SMF starts a timer to monitor the forwarding tunnel as step 6b or 7b.
If the SMF find the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF.
Up

Step 8b.
old UPF (intermediate) to SMF: N4 Session Modification Response
The old (intermediate) UPF sends N4 Session Modification Response message to SMF.
Up

Step 9.
[Conditional] old UPF (intermediate) to new UPF (intermediate): buffered downlink data forwarding
If the I-UPF is changed and forwarding tunnel was established to the new I-UPF, the old (intermediate) UPF forwards its buffered data to the new (intermediate) UPF acting as N3 terminating point. The new UPF should not send the buffered downlink packet(s) received from the UPF (PSA) until end marker packets were received from the old I-UPF or the timer started at step 6c is expired.
Up

Step 10.
[Conditional] old UPF (intermediate) to UPF (PSA): buffered downlink data forwarding
If the old I-UPF is removed and no new I-UPF is assigned for the PDU Session and forwarding tunnel was established to the UPF (PSA), the old (intermediate) UPF forwards its buffered data to the UPF (PSA) acting as N3 Terminating Point. The UPF (PSA) should not send the buffered DL data received from the N6 interface until it receives end marker packets from the old I-UPF or the timer started at step 7a is expired.
Up

Step 11.
[Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM information (PDU Session ID, QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI, User Plane Security Enforcement, UE Integrity Protection Maximum Data Rate, RSN), N1 SM Container, Cause) to the AMF. If the UPF that connects to RAN is the UPF (PSA), the N3 CN Tunnel Info is the UL CN Tunnel Info of the UPF (PSA). If the UPF that connects to RAN is the new intermediate UPF, the CN N3 Tunnel Info is the UL Tunnel Info of the intermediate UPF.
For the PDU Session with redundant I-UPFs or with redundant N3 tunnels for URLLC, the two UL N3 CN Tunnel Infos are included, the SMF also indicates the NG-RAN that one of the CN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501.
The SMF shall send N1 SM Container and/or N2 SM Information to the AMF when applicable. (e.g. when the SMF was notified from the AMF that the access type of the PDU Session can be changed in step 4).
For a PDU Session that the SMF has determined to accept the activation of UP connection in step 5a or 5b, the SMF generates only N2 SM information and sends Nsmf_PDUSession_UpdateSMContext Response to the AMF to establish the User Plane(s). The N2 SM information contains information that the AMF shall provide to the NG-RAN. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decided to change the PSA UPF for the SSC mode 3 PDU Session, the SMF triggers the change of SSC mode 3 PDU Session anchor as an independent procedure described in clause 4.3.5.2 or clause 4.3.5.3 after accepting the activation of UP of the PDU Session.
The SMF can reject the activation of UP of the PDU Session by including a cause in the Nsmf_PDUSession_UpdateSMContext Response. Following are some of the cases:
  • If the PDU Session corresponds to a LADN and the UE is outside the area of availability of the LADN as described in step 5b;
  • If the AMF notified the SMF that the UE is reachable only for regulatory prioritized service, and the PDU Session to be activated is not for a regulatory prioritized service; or
  • If the SMF decided to change the PSA UPF for the requested PDU Session as described in step 5b. In this case, after sending Nsmf_PDUSession_UpdateSMContext Response, the SMF triggers another procedure to instruct UE to re-establish the PDU Session as described in clause 4.3.5.1 for SSC mode 2.
  • If the SMF received negative response in Step 6b due to UPF resource unavailability.
If the PDU Session has been assigned any EPS bearer ID, the SMF also includes the mapping between EPS bearer ID(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN.
The User Plane Security Enforcement information is determined by the SMF upon PDU session establishment as described in clause 5.10.3 of TS 23.501. If the User Plane Security Enforcement information indicates that Integrity Protection is "Preferred" or "Required", the SMF also includes the UE Integrity Protection Maximum Data Rate.
The RSN is included when applicable, as determined by the SMF during PDU Session establishment as described in clause 5.33.2.1 of TS 23.501.
Up

Step 12.
AMF to (R)AN: N2 Request (N2 SM information received from SMF, security context, Mobility Restriction List, UE-AMBR, MM NAS Service Accept, list of recommended cells / TAs / NG-RAN node identifiers, UE Radio Capability, Core Network Assistance Information, Tracing Requirements, UE Radio Capability ID). The Allowed NSSAI for the Access Type for the UE is included in the N2 message. If the subscription information includes Tracing Requirements, the AMF includes Tracing Requirements in the N2 Request.
If the UE triggered the Service Request while in CM-CONNECTED state, only N2 SM information received from SMF and MM NAS Service Accept are included in the N2 Request.
If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-CONNECTED state, only N2 SM information received from SMF is included in the N2 Request.
If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-IDLE state, only N2 SM information received from SMF and MM NAS Service Accept is included in the N2 Request.
For a UE that was in CM-IDLE state when the Service Request was triggered, the NG-RAN stores the Security Context. If the Service Request is not triggered by UE for a signalling connection only, RAN also stores QoS Information for the QoS Flows of the PDU Sessions that are activated and N3 Tunnel IDs in the UE RAN context and Mobility Restriction List (as described in TS 23.501, clause 5.3.4.1).
MM NAS Service Accept includes PDU Session status in AMF. Any local PDU Session Release during the Session Request procedure is indicated to the UE via the Session Status. PDU Session Reactivation Result is provided in Service Accept for the PDU sessions in the List Of PDU Sessions To Be Activated, and the PDU Session in the List of Allowed PDU Sessions which has caused paging or NAS notification. If the PDU Session Reactivation Result of a PDU Session is failure, the cause of the failure is also provided.
If there are multiple PDU Sessions that involves multiple SMFs, AMF does not need to wait for responses from all SMFs in step 11 before it sends N2 SM information to the RAN. However, the AMF shall wait for all responses from the SMFs before it sends MM NAS Service Accept message to the UE.
AMF shall include at least one N2 SM information from SMF if this step is triggered for PDU Session User Plane activation. AMF may send additional N2 SM information from SMFs in separate N2 message(s) (e.g. N2 tunnel setup request), if there is any. Alternatively, if multiple SMFs are involved, the AMF may send one N2 Request message to (R)AN after all the Nsmf_PDUSession_UpdateSMContext Response service operations from all the SMFs associated with the UE are received.
If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The NG-RAN may use this information to allocate the RAN Notification Area when the NG-RAN decides to enable RRC Inactive state for the UE.
The AMF includes the UE's "RRC Inactive Assistance Information" as defined in TS 23.501, clause 5.3.3.2.5.
If the NG-RAN node does not support RACS and the AMF have UE Radio Capability ID but not the UE Radio Capability information, then AMF will use Nucmf_UECapabilityManagement_Resolve to try to retrieve the corresponding UE Radio Capability information.
If the NG-RAN node does not support RACS, or the AMF does not have UE Radio Capability ID in UE context, the AMF shall include the UE Radio Capability information, if available, to the NG-RAN node as described in TS 23.501. If the RAT Type is NB-IoT then NB-IoT specific UE Radio Access Capability Information is included instead, if available.
If AMF has UE Radio Capability ID in UE context and the NG-RAN supports RACS, the AMF signals the UE Radio Capability ID. If the NG-RAN node does not have mapping between the UE Radio Capability ID and the corresponding UE radio capabilities, it shall use the non-UE associated procedure described in TS 38.413 to retrieve the mapping from the AMF.
The AMF may include the Core Network Assistance Information which includes Core Network assisted RAN parameters tuning and Core Network assisted RAN paging information as defined in TS 23.501.
If the UE included support for restriction of use of Enhanced Coverage, the AMF sends Enhanced Coverage Restricted information to the (R)AN in the N2 message.
If the UE and the AMF have negotiated to enable MICO mode and the AMF uses the Extended connected timer, then the AMF provides the Extended Connected time value to NG-RAN (see clause 5.31.7.3 of TS 23.501) in this step. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC-CONNECTED state regardless of inactivity.
If the AMF accepted MICO mode in the last registration procedure and knows there may be mobile terminated data or signalling pending, the AMF maintains the N2 connection for at least the Extended Connected Time as described in clause 5.31.7.3 of TS 23.501, and provides the Extended Connected Time value to the RAN in N2 message with Service Accept message. The RAN should keep the UE in RRC-CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivered to the UE.
If the RAN receives two CN Tunnel Info for a PDU session in step 11 for redundant transmission, RAN also allocates two AN Tunnel Info correspondingly, and indicate to SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501.
Up

Step 13.
(R)AN to UE: The NG-RAN performs RRC Connection Reconfiguration with the UE depending on the QoS Information for all the QoS Flows of the PDU Sessions whose UP connections are activated and Data Radio Bearers. For a UE that was in CM-IDLE state, if the Service Request is not triggered by UE for a signalling connection only, the User Plane security is established at this step, which is described in detail in TS 38.331 and TS 36.331. For a UE that was in CM-IDLE state, if the Service Request is triggered by UE for a signalling connection only, AS security context may be established in this step, which is described in detail in TS 38.331 and TS 36.331.
If the N2 Request includes a NAS message, the NG-RAN forwards the NAS message to the UE. The UE locally deletes context of PDU Sessions that are not available in 5GC.
NOTE 3:
The reception of the Service Accept message does not imply the successful activation of the User Plane radio resources.
NOTE 4:
If not all the requested User Plane AN resources are successfully activated, see TS 38.413.
After the User Plane radio resources are setup, the uplink data from the UE can now be forwarded to NG-RAN. The NG-RAN sends the uplink data to the UPF address and Tunnel ID provided in the step 11.
If the NG-RAN can not establish redundant user plane for the PDU Session as indicated by the RSN parameter, the NG-RAN takes the decision on how to proceed with the PDU Session as described in TS 23.501.
Up

Step 14.
[Conditional] (R)AN to AMF: N2 Request Ack (List of PDU Sessions To Be Established with N2 SM information (AN Tunnel Info, List of accepted QoS Flows for the PDU Sessions whose UP connections are activated, List of rejected QoS Flows for the PDU Sessions whose UP connections are activated), List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element).
The message may include N2 SM information(s), e.g. AN Tunnel Info. NG-RAN may respond N2 SM information with separate N2 message (e.g. N2 tunnel setup response) if AMF sends separate N2 message in step 11.
If multiple N2 SM information are included in the N2 Request message in step 12, the N2 Request Ack includes multiple N2 SM information and information to enable the AMF to associate the responses to relevant SMF.
Up

Step 15.
[Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, RAT Type, Access Type) per PDU Session to the SMF. The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1.
If the AMF received N2 SM information (one or multiple) in step 14, then the AMF shall forward the N2 SM information to the relevant SMF per PDU Session ID. If the UE Time Zone has changed compared to the last reported UE Time Zone then the AMF shall include the UE Time Zone IE in this message.
If the PDU Session is moved from the non-3GPP access to 3GPP access (i.e. N3 tunnel for the PDU Session is established successfully), the SMF and AMF update associated access of the PDU Session. The UE updates associated access of the PDU Session when the user plane resource for the PDU Session is successfully established.
Procedure for unpausing a charging pause initiated earlier is specified in clause 4.4.4.
If a PDU Session is rejected by the serving NG-RAN with an indication that the PDU Session was rejected because User Plane Security Enforcement is not supported in the serving NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501, the SMF shall trigger the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session.
If some of the QoS Flows of a PDU Session are not accepted by the serving NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session after this procedure is completed.
Up

Step 16.
[Optional] SMF to PCF: If dynamic PCC is deployed, SMF may initiate notification about new location information to the PCF (if subscribed) by performing an SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1. The PCF may provide updated policies.
Up

Step 17a.
[Conditional] SMF to new intermediate UPF: N4 Session Modification Request (AN Tunnel Info and List of accepted QFI(s)).
If the SMF selected a new UPF to act as intermediate UPF for the PDU Session in step 5b, the SMF initiates a N4 Session Modification procedure to the new I-UPF and provides AN Tunnel Info. The Downlink Data from the new I-UPF can now be forwarded to NG-RAN and UE.
Up

Step 17b.
[Conditional] UPF to SMF: N4 Session Modification Response.
Up

Step 18a.
[Conditional] SMF to UPF (PSA): N4 Session Modification Request (AN Tunnel Info, List of rejected QoS Flows).
If a User Plane is to be setup or modified and after the modification there is no I-UPF, the SMF initiates a N4 Session Modification procedure to UPF (PSA) and provides AN Tunnel Info. The Downlink Data from the UPF (PSA) can now be forwarded to NG-RAN and UE.
For QoS Flows in the List of rejected QoS Flows, the SMF shall instruct the UPF to remove the rules (e.g., Packet Detection Rules etc.) which are associated with the QoS Flows.
If SMF decides to perform redundant transmission for one or more QoS Flows of the PDU, the SMF also indicates the UPF (PSA) to perform packet duplication for the QoS Flow(s) in downlink direction by forwarding rules.
Up

Step 18b.
[Conditional] UPF to SMF: N4 Session Modification Response.
Up

Step 19.
[Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response.
Up

Step 20a.
[Conditional] SMF to new UPF (intermediate): N4 Session Modification Request.
If forwarding tunnel has been established to the new I-UPF and if the timer SMF set for forwarding tunnel at step 8a has expired, SMF sends N4 Session modification request to new (intermediate) UPF acting as N3 terminating point to release the forwarding tunnel.
Up

Step 20b.
[Conditional] new UPF (intermediate) to SMF: N4 Session modification response.
New (intermediate) UPF acting as N3 terminating point sends N4 Session Modification response to SMF.
Up

Step 21a.
[Conditional] SMF to UPF (PSA): N4 Session Modification Request.
If forwarding tunnel has been established to the UPF (PSA) and if the timer SMF set for forwarding tunnel at step 7b has expired, SMF sends N4 Session modification request to UPF (PSA) acting as N3 Terminating Point to release the forwarding tunnel.
Up

Step 21b.
[Conditional] UPF (PSA) to SMF: N4 Session Modification Response.
UPF (PSA) acting as N3 Terminating Point sends N4 Session Modification Response to SMF.
Up

Step 22a.
[Conditional] SMF to old UPF: N4 Session Modification Request or N4 Session Release Request.
If the SMF decided to continue using the old UPF in step 5b, the SMF sends an N4 Session Modification Request, providing AN Tunnel Info.
If the SMF decided to select a new UPF to act as intermediate UPF in step 5b, and the old UPF is not PSA UPF, the SMF initiates resource release, after timer in step 6b or 7b expires, by sending an N4 Session Release Request (Release Cause) to the old intermediate UPF.
Up

Step 22b.
Old intermediate UPF to SMF: N4 Session Modification Response or N4 Session Release Response.
The old UPF acknowledges with an N4 Session Modification Response or N4 Session Release Response message to confirm the modification or release of resources.
Up

For the mobility related events described in clause 4.15.4, the AMF invokes the Namf_EventExposure_Notify service operation after step 4.
Upon reception of the Namf_EventExposure_Notify with an indication that the UE is reachable, if the SMF has pending DL data the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to establish the User Plane(s) for the PDU Sessions, otherwise the SMF resumes sending DL data notifications to the AMF in the case of DL data.
Upon reception of the Namf_EventExposure_Notify with an indication that UE is reachable only for regulatory prioritized service, the SMF deactivates the PDU Session if the service of the PDU Session is not regulatory prioritized. For home routed roaming case, the V-SMF triggers the deactivation of the PDU Session, in addition, the H-SMF refrains from sending downlink signalling if the signalling is not related to regulatory prioritized service upon receiving the notification.
Up

Up   Top   ToC