Content for  TS 23.502  Word version:  18.0.0

UE is registered in 5GS and established PDU sessions. The FQDN for the S5/S8 interface of the SMF+PGW-C is also stored in the UDM by the SMF+PGW-C during PDU Session setup in addition to what is specified in clause 4.3.2.2.1 and clause 4.3.2.2.2.

Step 1 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401.

Step 2 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401 with the following modifications: The UE shall provide a EPS-GUTI that is mapped from the 5G-GUTI following the mapping rules specified in TS 23.501. The UE indicates that it is moving from 5GC.

Step 3 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401.

If the MME determined that the old node is an AMF based on UE's GUTI mapped from 5G-GUTI and the MME is configured to support 5GS-EPS interworking without N26 procedure, the MME sends a TAU Reject to the UE.

Step 1 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401 with the modifications captured in clause 4.11.2.4.1.

Step 2 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401.

Steps 4-7 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401, with the modifications captured in clause 4.11.2.4.1.

Step 8 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401, with the modifications captured in clause 4.11.2.4.1.

Step 11 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401, with the following modifications: The subscription profile the MME receives from HSS+UDM includes per DNN/APN at most one SMF+PGW-C FQDN as described in in clause 5.17.2.1 in TS 23.501.

Steps 12-24 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401, with the modifications as described in clause 4.11.2.4.1.

Step 25 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401.

Step 26 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401.

If the UE has remaining PDU Sessions in 5GS which it wants to transfer to EPS and maintain the same IP address/prefix, the UE performs the UE requested PDN Connectivity Procedure as specified in clause 5.10.2 of TS 23.401 and sets the Request Type to "handover" or "handover of emergency bearer services" in Step 1 of the procedure with modification captured in clause 4.11.2.4.2. UE provides an APN and the PDU Session ID corresponding to the PDU Session it wants to transfer to EPS. The UE provides the PDU Session ID in PCO as described in clause 4.11.1.1. UEs in single-registration mode performs this step for each PDU Session immediately after completing the E-UTRAN Initial Attach procedure. UEs in dual-registration mode may perform this step any time after the completing of E-UTRAN Initial Attach procedure. Also, UEs in dual-registration mode may perform this step only for a subset of PDU Sessions. The MME determines the SMF+PGW-C address for the Create Session Request based on the APN if received from the UE, local Emergency Configuration Data (as in clause 4.11.0a.4) and the subscription profile which may include the Emergency Information received from the HSS+UDM in Step 9 or when the HSS+UDM notifies the MME for the new SMF+PGW-C ID in the updated subscription profile. The SMF+PGW-C uses the PDU Session ID to correlate the transferred PDN connection with the PDU Session in 5GC. As a result of the procedure the PGW-U+UPF starts routing DL data packets to the Serving GW for the default and any dedicated EPS bearers established for this PDN connection.

For Non-Roaming case and Roaming with Local Breakout, the SMF+PGW-C initiates release of the PDU Session(s) in 5GS transferred to EPS as specified in clause 4.3.4.2 with the following clarification:

• In step 2, the SMF+PGW-C shall not release IP address/prefix(es) allocated for the PDU Session;
• If UP connection of the PDU Session is not active, step 3b is not executed, thus the steps triggered by step 3b are not executed;
  If UP connection of the PDU Session is active, the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation in step 3b without including N1 SM container (PDU Session Release Command);
• In step 11, Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the SMF to notify AMF that the SM context for this PDU Session is released due to handover to EPS.

The UE is attached in EPC as specified in clause 4.11.2.4.1.

Step 1 in clause 4.2.2.2.2 (General Registration) with the following clarifications: The UE indicates that it is moving from EPC. The UE in single registration mode provides the Registration type set to "mobility registration update", a 5G-GUTI mapped from the 4G-GUTI and a native 5G-GUTI (if available) as an Additional GUTI. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. The UE shall select the 5G-GUTI for the additional GUTI as follows, listed in decreasing order of preference:

• a native 5G-GUTI assigned by the PLMN to which the UE is attempting to register, if available;
• a native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register, if available;
• a native 5G-GUTI assigned by any other PLMN, if available.

The UE in dual registration mode provides the Registration type set to "initial registration" and a native 5G-GUTI or SUCI. In single registration mode, the UE also includes at least the S-NSSAIs (with values for the Serving PLMN) associated with the established PDN connections in the Requested NSSAI in RRC Connection Establishment.

Step 2 as in clause 4.2.2.2.

Step 3 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the Registration type is "mobility registration update" and the UE indicates that it is moving from EPC in step 1 and the AMF is configured to support 5GS-EPS interworking procedure without N26 interface, the AMF treats this registration request as "initial Registration" and the AMF skips the PDU Session status synchronization. If the UE has provided a 5G-GUTI mapped from 4G-GUTI in step 1 and the AMF is configured to support 5GS-EPS interworking procedure without N26 interface, the AMF does not perform steps 4 and 5 in clause 4.2.2.2 (UE context transfer from the MME).

Steps 4-13 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the UE has included an additional GUTI in the Registration Request, then the new AMF attempts to retrieve the UE's security context from the old AMF in steps 4 and 5. If the UE's security context is not available in the old AMF or if the UE has not provided an additional GUTI then the AMF retrieves the SUCI from the UE in steps 6 and 7.

Step 14 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the UE indicates that it is moving from EPC and the Registration type is set to "initial registration" or "mobility registration update" in step 1 and AMF is configured to support 5GS-EPS interworking without N26 procedure, the AMF sends an Nudm_UECM_Registration Request message to the HSS+UDM indicating that registration of an MME at the HSS+UDM, if any, shall not be cancelled. The HSS+UDM does not send cancel location to the old MME. The subscription profile the AMF receives from HSS+UDM includes the DNN/APN and SMF+PGW-C FQDN for S5/S8 interface for each PDN connection established in EPC. For emergency PDU Session, the AMF receives Emergency Information containing SMF+PGW-C FQDN from HSS+UDM.

Steps 15-19c as in clause 4.2.2.2.2 (General Registration).

Step 21 as in clause 4.2.2.2.2 (General Registration) with the following modifications: The AMF includes an "Interworking without N26" indicator to the UE. If the UE had provided PDU Session Status information in step 1, the AMF Sets the PDU Session Status to not synchronized.

Step 22 as in clause 4.2.2.2.2 (General Registration)

UE requested PDU Session Establishment procedure as in clause 4.3.2.2.1. If the UE had setup PDN Connections in EPC which it wants to transfer to 5GS and maintain the same IP address/prefix and the UE received "Interworking without N26" indicator in step 7, the UE performs the UE requested PDU Session Establishment Procedure as in clause 4.3.2.2 and sets the Request Type to "Existing PDU Session" or "Existing Emergency PDU Session" in step 1 of the procedure. The UE provides a DNN for non-emergency PDU Session, the PDU Session ID and S-NSSAI corresponding to the existing PDN connection it wants to transfer from EPS to 5GS. The S-NSSAI is set as described in clause 5.15.7.2 of TS 23.501. If the Request Type indicates "Existing Emergency PDU Session", the AMF shall use the Emergency Information received from the HSS+UDM which contains SMF+PGW-C FQDN for S5/S8 interface for the emergency PDN connection established in EPS and the AMF shall use the S-NSSAI locally configured in Emergency Configuration Data. UEs in single-registration mode performs this step for each PDN connection immediately after the step 8. UEs in dual-registration mode may perform this step any time after step 8. Also, UEs in dual-registration mode may perform this step only for a subset of PDU Sessions. The AMF determines the S5/S8 interface of the SMF+PGW-C for the PDU Session based on the DNN received from the UE and the SMF+PGW-C ID in the subscription profile received from the HSS+UDM in step 5 or when the HSS+UDM notifies the AMF for the new SMF+PGW-C ID in the updated subscription profile. The AMF queries the NRF in serving PLMN by issuing the Nnrf_NFDiscovery_Request including the FQDN for the S5/S8 interface of the SMF+PGW-C and the NRF provides the IP address or FQDN of the N11/N16 interface of the SMF+PGW-C. The AMF invokes the Nsmf_PDUSession_CreateSMContext service with the SMF address provided by the NRF. The AMF includes the PDU Session ID to the request sent to the SMF+PGW-C. The SMF+PGW-C uses the PDU Session ID to determine the correct PDU Session. After step 16a of Figure 4.3.2.2.1-1 in clause 4.3.2.2.1, user plane is switched from EPS to 5GS. As specified clause 4.3.2.2, if the SMF has not yet registered for the PDU Session ID, then the SMF registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, PDU Session ID) and if Session Management Subscription data for corresponding SUPI, DNN and S-NSSAI is not available, then SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, DNN, S-NSSAI) and subscribes to be notified when this subscription data is modified using Nudm_SDM_Subscribe (SUPI, Session Management Subscription data, DNN, S-NSSAI).

The SMF+PGW-C performs release of the resources in EPC for the PDN connections(s) transferred to 5GS by performing the PDN GW initiated bearer deactivation procedure as defined in clause 5.4.4.1 of TS 23.401, except the steps 4-7.