Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.502  Word version:  17.6.0

Top   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.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.3.2.5…   4.15.4…   4.15.6.7…   4.15.7…   4.16…   4.16.4…   4.16.8…   4.16.11…   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…   5.2.18…   A…   E…   F…

 

4.3.5  Session continuity, service continuity and UP path managementp. 152

4.3.5.1  Change of SSC mode 2 PDU Session Anchor with different PDU Sessionsp. 152

The following procedure is triggered by SMF in order to change the PDU Session Anchor serving a PDU Session of SSC mode 2 for a UE when neither multi-homing nor UL CL applies to the PDU Session. This procedure releases the existing PDU Session associated with an old PDU Session Anchor (i.e. UPF1 in Figure 4.3.5.1-1) and immediately establishes a new PDU Session with a new PDU Session Anchor (i.e. UPF2 in Figure 4.3.5.1-1) to the same DN.
Reproduction of 3GPP TS 23.502, Fig. 4.3.5.1-1: Change of SSC mode 2 PSA for a PDU Session
Up
Step 1.
The SMF determines that the serving UPF needs to be changed due to events that may benefit from such change.
Step 1a.
If the UPF (PSA) cannot connect to the target DNAI that SMF received from SM-PCF, the SMF invokes Nsmf_PDUSession_SMContextStatusNotify Request (target DNAI information) service operation to the AMF. The SMF also indicates the SMF selection is expected.
The target DNAI information is used for SMF selection which can control UPF connecting to that DNAI at next PDU session establishment towards the same DNN and S-NSSAI. Due to it is for SMF selection, the AMF stores the target DNAI information received from SMF. The target DNAI information is not transferred outside, e.g. to support the UE context transfer between AMFs for AMF relocation.
Step 2.
The PDU Session Release procedure is initiated as described in clause 4.3.4. The SMF sends an N1 SM Information to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer as described in Step 3b of clause 4.3.4.2. The PDU Session Release Command message in N1 SM Information contains the PDU Session ID and Cause indicating that a PDU Session re-establishment to the same DN is required.
Step 3.
Upon reception of PDU Session Release Command with Cause indicating that a PDU Session re-establishment to the same DN is required as sent in step 2, the UE generates a new PDU Session ID and initiates PDU Session Establishment procedure as described in clause 4.3.2.2.
Then, the AMF selects an SMF as described in clause 6.3.2 of TS 23.501 and the SMF can select a new UPF (i.e. UPF2) for the re-established PDU Session of SSC mode 2.
If the AMF has received target DNAI information from old SMF (i.e. SMF1), for the PDU Session toward same DNN and S-NSSAI the AMF selects the SMF using the stored target DNAI information. The AMF includes the target DNAI in the Nsmf_PDUSession_CreateSMContext Request and deletes the stored target DNAI information. The SMF selects the new PDU Session Anchor using the target DNAI.
Up

Up   Top   ToC