Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.502  Word version:  19.2.0

Top   Top   Up   Prev   Next
1…   5…   5.2.2…   5.2.2.2.4…   5.2.2.3…   5.2.2.3.2…   5.2.2.3.3…   5.2.2.3.6…   5.2.2.3.8…   5.2.2.3.10…   5.2.2.3.17…   5.2.2.3.23…   5.2.2.4…   5.2.2.8…   5.2.2.8.2…   5.2.2.8.2.7…   5.2.2.8.2.12…   5.2.2.8.2.20…   5.2.2.8.3…   5.2.2.8.3.6…   5.2.2.9…   5.2.3…   6…   6.1.2…   6.1.3…   6.1.3.3…   6.1.3.5…   6.1.3.6…   6.1.3.7…   6.1.4…   6.1.6…   6.1.6.2…   6.1.6.2.5…   6.1.6.2.11…   6.1.6.2.18…   6.1.6.2.27…   6.1.6.2.40…   6.1.6.2.54…   6.1.6.2.65…   6.1.6.3…   6.1.6.4…   6.1.7…   A…   B…   C… 
5.2.2.2.4 I-SMF Insertion, Change or Removal during Xn based Handover  5.2.2.2.5 I-SMF Insertion, Change or Removal during N2 based Handover  5.2.2.2.6 Service Request with I-SMF insertion/change/removal or with V-SMF change  5.2.2.2.7 Registration procedure for a UE with a PDU session with I-SMF or V-SMF insertion, change and removal  5.2.2.2.8 SMF Context Transfer procedure, LBO or no Roaming, no I-SMF  5.2.2.2.9 I-SMF Context Transfer procedure  5.2.2.2.10 Handover between 3GPP and non-3GPP accesses with I-SMF insertion/removal or V-SMF change  5.2.2.2.12 SMF triggered I-SMF selection/removal or V-SMF selection 
...

 

5.2.2.2.4  I-SMF Insertion, Change or Removal during Xn based Handover |R16|  p. 24
The NF Service Consumer (e.g. AMF) shall request the I-SMF (for I-SMF insertion or change) or the SMF (for I-SMF removal) to create a SM context during Xn based handover, as follows.
Step 1.
The NF Service Consumer shall send a POST request, with the following additional information:
  • N2 SM information received from the target 5G-AN (see Path Switch Request Transfer IE in clause 9.3.4.8 of TS 38.413);
  • additional N2 SM information received from the source 5G-AN (see Secondary RAT Data Usage Report Transfer IE in clause 9.3.4.23 of TS 38.413), if any;
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF during I-SMF insertion, or the SM Context resource in the source I-SMF during I-SMF change or removal, and optionally the NF instance identifier of the SMF hosting the SM Context resource;
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF during I-SMF insertion or change, and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF and I-SMF.
Step 2a.
On success, the SMF shall return a 201 Created response.
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
If the Path Swith Request Transfer IE is included within the N2 SM Information in the request message but the path switch failed, the message body shall contain an SmContextCreateError structure, including:
  • N2 SM information (Path Swith Request Unsuccessful Transfer).
Up
5.2.2.2.5  I-SMF Insertion, Change or Removal during N2 based Handover |R16|  p. 25
The NF Service Consumer (e.g. AMF) shall request the I-SMF (for I-SMF insertion or change) or the SMF (for I-SMF removal) to create a SM context during N2 based handover, as follows.
Step 1.
The NF Service Consumer shall send a POST request, with the following additional information:
  • N2 SM information received from the source NG-RAN (see Handover Required Transfer IE in clause 9.3.4.14 of TS 38.413);
  • the hoState attribute set to PREPARING (see clause 5.2.2.3.4.1);
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF during I-SMF insertion,,or the SM Context resource in the source I-SMF during I-SMF change or removal, and optionally the NF instance identifier of the SMF hosting the SM Context resource;
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF during I-SMF insertion or change, and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF and I-SMF.
Step 2a.
On success, the SMF shall return a 201 Created response including the following information:
  • hoState attribute set to PREPARING and N2 SM information to request the target 5G-AN to assign resources to the PDU session, as specified in step 2 of Figure 5.2.2.3.4.2-1;
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
Up
5.2.2.2.6  Service Request with I-SMF insertion/change/removal or with V-SMF change |R16|  p. 25
The NF Service Consumer (e.g. AMF) shall request the new I-SMF or new V-SMF to create a SM context during a Service Request with I-SMF insertion/change or with V-SMF change, or shall request the SMF to create a SM context during a Service Request with I-SMF removal, as follows.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.2.6-1: Service Request with I-SMF insertion/change/removal or with V-SMF change
Figure 5.2.2.2.6-1: Service Request with I-SMF insertion/change/removal or with V-SMF change
Up
Step 1.
The NF Service Consumer shall send a POST request as specified in clause 5.2.2.2.1, with the following additional information:
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF (for a Service Request with an I-SMF insertion) or in the old I-SMF (for a Service Request with an I-SMF change or removal) or in the old V-SMF (for a Service Request with a V-SMF change), and optionally the NF instance identifier of the SMF hosting the SM Context resource.
  • the upCnxState attribute set to ACTIVATING (see clause 5.2.2.3.2.1) to indicate the establishment of N3 tunnel User Plane resources for the PDU Session;
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF (for a Service Request with an I-SMF insertion or change), and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF and I-SMF;
  • the hSmfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the H-SMF (for a Service Request with an V-SMF change), and optionally the NF instance identifier of the H-SMF, if the "ACSCR" feature is not supported by the AMF and V-SMF.
Step 2a.
On success, the SMF shall return a 201 Created response as specified in clause 5.2.2.2.1 with the following additional information:
  • the upCnxState attribute set to ACTIVATING;
  • N2 SM information to request the 5G-AN to assign resources to the PDU session (see PDU Session Resource Setup Request Transfer IE in clause 9.3.4.1 of TS 38.413), including the transport layer address and tunnel endpoint of the uplink termination point for the user plane data for this PDU session (i.e. UPF's GTP-U F-TEID for uplink traffic).
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1. Steps 3 to 4 of Figure 5.2.2.3.2.2-1 are skipped in this case.
Up
5.2.2.2.7  Registration procedure for a UE with a PDU session with I-SMF or V-SMF insertion, change and removal |R16|  p. 26
The NF Service Consumer (e.g. AMF) shall request the SMF to create a SM context during UE Registration procedure for a PDU session with I-SMF or V-SMF insertion, change and removal, as follows.
Step 1.
Same as step 1 of Figure 5.2.2.2.1-1, the NF Service Consumer shall send a POST request, with the following additional information:
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF during I-SMF or V-SMF insertion or the SM Context resource in the I-SMF or V-SMF during I-SMF or V-SMF removal or the SM Context resource in the old I-SMF or old V-SMF during I-SMF or V-SMF change, and optionally the NF instance identifier of the SMF hosting the SM Context resource;
  • the upCnxState attribute set to ACTIVATING (see clause 5.2.2.3.2.1) to indicate the establishment of N3 tunnel User Plane resources for the PDU Session, if the UE requested to activate the PDU session;
  • if the UE is in CM-CONNECTED state during the registration procedure after an EPS to 5GS handover (see clause 4.11.1.3.3 of TS 23.502), the ranUnchangedInd attribute shall be set to indicate that NG-RAN is not changed for the PDU Session (i.e. for this case, the NG-RAN tunnel info shall be included in SM context retrieved from old I-SMF, or old V-SMF or SMF);
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF during I-SMF insertion or change, and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF and I-SMF.
Step 2a.
On success, the SMF shall return a 201 Created response.
If the SMF establishes N3 tunnel User Plane resources for the PDU Session, e.g. due to the NF Service Consumer requesting so or due to buffered DL data in the old I-SMF/I-UPF or old V-SMF/V-UPF (see clause 4.23.3 of TS 23.502), the 201 Created response shall contain the following additional information:
  • the upCnxState attribute set to ACTIVATING;
  • N2 SM information to request the 5G-AN to assign resources to the PDU session (see PDU Session Resource Setup Request Transfer IE in clause 9.3.4.1 of TS 38.413), including the transport layer address and tunnel endpoint of the uplink termination point for the user plane data for this PDU session (i.e. UPF's GTP-U F-TEID for uplink traffic).
If the SMF receives the ranUnchangedInd attribute set to indicate that NG-RAN is not changed for the PDU Session, the SMF shall respond with a 201 Created with the following additional information:
  • N2 SM information to request the 5G-AN to update UPF tunnel info of the PDU session (see PDU Session Resource Modify Request Transfer IE in clause 9.3.4.3 of TS 38.413), including the transport layer address and tunnel endpoint of the uplink termination point for the user plane data for this PDU session (i.e. UPF's GTP-U F-TEID for uplink traffic and NG-RAN's GTP-U F-TEID for downlink traffic).
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
Up
5.2.2.2.8  SMF Context Transfer procedure, LBO or no Roaming, no I-SMF |R16|  p. 27
The NF Service Consumer (e.g. AMF) shall request the SMF to create a SM context during an SMF Context Transfer procedure, LBO or no Roaming, no I-SMF, as follows.
Step 1.
Same as step 1 of Figure 5.2.2.2.1-1, the NF Service Consumer shall send a POST request, with the following additional information:
  • SMF transfer indication, Old SMF ID, the identifier of the SM Context resource in old SMF.
Step 2a.
On success, the SMF shall return a 201 Created response.
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
Up
5.2.2.2.9  I-SMF Context Transfer procedure |R16|  p. 27
The NF Service Consumer (e.g. AMF) shall request the SMF to create a SM context during I-SMF Context Transfer procedure, as follows.
Step 1.
Same as step 1 of Figure 5.2.2.2.1-1, the NF Service Consumer shall send a POST request, with the following additional information:
  • SMF transfer indication, Old SMF ID, the identifier of the SM Context resource in old SMF.
Step 2a.
On success, the SMF shall return a 201 Created response.
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
Up
5.2.2.2.10  Handover between 3GPP and non-3GPP accesses with I-SMF insertion/removal or V-SMF change |R16|  p. 28
The NF Service Consumer (e.g. AMF) shall request the I-SMF (for I-SMF insertion during a handover from non-3GPP to 3GPP access), the V-SMF (for V-SMF change during a handover from non-3GPP to 3GPP access) or the SMF (for I-SMF removal during a handover from 3GPP to non-3GPP access) to create a SM context as follows.
Step 1.
The NF Service Consumer shall send a POST request as specified in clause 5.2.2.2.1, with the following additional information:
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF (during I-SMF insertion), the SM Context resource in the source I-SMF during I-SMF removal, or the SM Context resource in the source V-SMF during V-SMF change, and optionally the NF instance identifier of the SMF hosting the SM Context resource;
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF (during I-SMF insertion), and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF and I-SMF;
  • the hSmfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the H-SMF (during V-SMF change), and optionally the NF instance identifier of the H-SMF, if the "ACSCR" feature is not supported by the AMF and V-SMF.
Step 2a.
Same as step 2a of Figure 5.2.2.2.1-1.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
The SMF (for I-SMF removal during a handover from 3GPP to non-3GPP access) may perform Network Slice Admission Control before the PDU Session is moved to the target access (i.e., before the N3 tunnel for the PDU Session is established).
Up
5.2.2.2.11  Void
5.2.2.2.12  SMF triggered I-SMF selection/removal or V-SMF selection |R17|  p. 28
The NF Service Consumer (e.g. AMF) shall invoke the following procedure to request:
  • the new I-SMF to create a SM context if the SMF (or the associated old I-SMF) cannot serve the target DNAI; or
  • the SMF to create the SM context if an I-SMF is used for the PDU Session and the SMF itself can serve the target DNAI hence the existing I-SMF is no longer needed; or
  • the SMF to create the SM context if an I-SMF is used for the PDU Session and the DNAI currently served by I-SMF is not used for the PDU Session anymore, hence the existing I-SMF is not needed; or
  • the new V-SMF to create a SM context if the associated old V-SMF cannot serve the target DNAI.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.2.12-1: I-SMF selection/removal or V-SMF selection per DNAI
Figure 5.2.2.2.12-1: I-SMF selection/removal or V-SMF selection per DNAI
Up
Step 1.
The NF Service Consumer shall send a POST request as defined in step 1 of Figure 5.2.2.2.6-1, with the following additional information:
  • the smContextRef attribute set to the identifier of the SM Context resource in the SMF during I-SMF insertion, or the SM Context resource in the source I-SMF during I-SMF change/removal, or the SM Context resource in the source V-SMF during V-SMF change, and optionally the NF instance identifier of the SMF hosting the SM Context resource;
  • the target DNAI, if it is received in the targetDnaiInfo attribute of the SM context status notification;
  • if the UE is in CM-CONNECTED state, the ranUnchangedInd attribute shall be set to indicate that NG-RAN is not changed for the PDU Session (i.e. for this case, the NG-RAN tunnel info shall be included in SM context retrieved from old I-SMF, old V-SMF or SMF) as specified in clause 4.23.5.4 of TS 23.502 and clause 6.7.3.2 of TS 23.548;
  • the smfUri IE attribute set to the API URI of the Nsmf_PDUSession service of the SMF (during I-SMF insertion/change, or V-SMF change), and optionally the NF instance identifier of the SMF, if the "ACSCR" feature is not supported by the AMF, I-SMF or V-SMF.
Step 2a.
On success, the SMF shall return a 201 Created response, with the following additional information:
If the SMF receives the ranUnchangedInd attribute set to indicate that NG-RAN is not changed for the PDU Session, the SMF shall include the N2 SM information to request the 5G-AN to update UPF tunnel info of the PDU session (see PDU Session Resource Modify Request Transfer IE in clause 9.3.4.3 of TS 38.413), including the transport layer address and tunnel endpoint of the uplink termination point for the user plane data for this PDU session (i.e. UPF's GTP-U F-TEID for uplink traffic and NG-RAN's GTP-U F-TEID for downlink traffic).
The "Location" header shall be present in the POST response and shall contain the URI of the created SM context resource.
The NF Service Consumer (e.g. AMF) shall store the association of the PDU Session ID and the SMF ID.
Step 2b.
Same as step 2b of Figure 5.2.2.2.1-1.
Up

Up   Top   ToC