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:  18.5.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.3.6 Inter-AMF change or mobility  5.2.2.3.7 RAN Initiated QoS Flow Mobility 
...

 

5.2.2.3.6  Inter-AMF change or mobility  p. 41
The NF Service Consumer (e.g. new AMF) shall inform the SMF that it has taken over the role of serving the UE (e.g. it has taken the responsibility of the signalling towards the UE), when so required by TS 23.501 and TS 23.502, as follows.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.3.6-1: Inter-AMF change or mobility
Figure 5.2.2.3.6-1: Inter-AMF change or mobility
Up
Step 1.
The NF Service Consumer shall update the SMF with the new serving AMF, by sending a POST request, as specified in clause 5.2.2.3.1, with the following information:
  • servingNfId set to the new serving AMF Id;
  • the supportedFeatures IE indicating the optional features it supports, if at least one optional feature defined in clause 6.1.8 is supported;
  • other information, if necessary, e.g. to activate the user plane connection of the PDU session (see clause 5.2.2.3.2.2).
Step 2a.
Same as step 2a of Figure 5.2.2.3.1-1. In addition, the SMF shall include the supportedFeatures IE in the response, if the supportedFeatures IE was received in the request and at least one optional feature defined in clause 6.1.8 is supported by the updated SM context resource.
Step 2b.
Same as step 2b of Figure 5.2.2.3.1-1.
Up
5.2.2.3.7  RAN Initiated QoS Flow Mobility  p. 42
The NF Service Consumer (e.g. AMF) shall request the SMF to transfer QoS flows to and from Secondary RAN node, or more generally, handle a NG-RAN PDU Session Resource Modify Indication, as follows.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.3.7-1: RAN Initiated QoS Flow Mobility
Figure 5.2.2.3.7-1: RAN Initiated QoS Flow Mobility
Up
Step 1.
The NF Service Consumer shall request the SMF to modify the PDU session, as requested by the NG-RAN, by sending a POST request, as specified in clause 5.2.2.3.1, with the following information:
  • N2 SM information received from the 5G-AN (see PDU Session Resource Modify Indication Transfer IE in clause 9.3.4.6 of TS 38.413), including the transport layer information for the QoS flows of this PDU session (i.e. 5G-AN's GTP-U F-TEIDs for downlink traffic);
  • other information, if necessary.
Step 2a.
Upon receipt of such a request, if the SMF can proceed with switching the QoS flows of the PDU session, the SMF shall return a 200 OK response including the following information:
  • N2 SM information (see PDU Session Resource Modify Confirm Transfer IE in clause 9.3.4.7 of TS 38.413), including the list of QoS flows which were modified successfully and the list of QoS flows which failed to be modified if available.
Step 2b.
If the SMF cannot proceed with switching the QoS flows of the PDU session, the SMF shall return an error response, as specified for step 2b of Figure 5.2.2.3.1-1, including:
Up

Up   Top   ToC