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.7.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.17 AMF requested PDU Session Release due to Network Slice-Specific Authentication and Authorization failure or revocation  5.2.2.3.18 5GS to EPS Idle mode mobility using N26 interface with data forwarding  5.2.2.3.19 AMF requested PDU Session Release due to Control Plane Only indication associated with PDU Session is not applicable any longer  5.2.2.3.20 AMF requested PDU Session Release due to ODB changes  5.2.2.3.21 N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs  5.2.2.3.22 Remote UE Report during 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF procedure 
...

 

5.2.2.3.17  AMF requested PDU Session Release due to Network Slice-Specific Authentication and Authorization failure or revocation |R16|  p. 50
The requirements specified in clause 5.2.2.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.3.1-1, with the following modifications.
The POST request shall contain:
  • the release IE set to true;
  • the cause IE set to REL_DUE_TO_SLICE_NOT_AUTHORIZED.
5.2.2.3.18  5GS to EPS Idle mode mobility using N26 interface with data forwarding |R16|  p. 50
The NF Service Consumer (e.g. AMF) shall request the SMF to forward buffered DL data towards the EPS during a 5GS to EPS Idle mode mobility using N26 interface with data forwarding (see clause 4.11.1.3.2A of TS 23.502), as follows.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.3.18-1: 5GS to EPS Idle mode mobility using N26 interface with data forwarding
Figure 5.2.2.3.18-1: 5GS to EPS Idle mode mobility using N26 interface with data forwarding
Up
Step 1.
The NF Service Consumer shall send a POST request, as specified in clause 5.2.2.3.1, with the following information:
  • forwardingFTeid received from the MME in the Context Acknowdge, if any; or
  • forwarding bearer contexts received from the MME in Context Acknowdge, if any.
Step 2a.
Upon receipt of such a request, the SMF shall forward the buffered DL data on the forwarding tunnel(s).
Step 2b.
If the SMF cannot proceed with the request, the SMF shall return an error response, as specified for step 2b of Figure 5.2.2.3.1-1.
Up
5.2.2.3.19  AMF requested PDU Session Release due to Control Plane Only indication associated with PDU Session is not applicable any longer |R16|  p. 51
The requirements specified in clause 5.2.2.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.3.1-1, with the following modifications.
The POST request shall contain:
  • the release IE set to true;
  • the cause IE set to REL_DUE_TO_CP_ONLY_NOT_APPLICABLE.
5.2.2.3.20  AMF requested PDU Session Release due to ODB changes |R17|  p. 51
The requirements specified in clause 5.2.2.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.3.1-1, with the following modifications.
The POST request shall contain:
  • the release IE set to true;
  • the cause IE set to REL_DUE_TO_SUBSCRIPTION_CHANGE.
5.2.2.3.21  N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs |R17|  p. 51
During simultaneous change of Branching Points or UL CLs controlled by different I-SMFs, the NF Service Consumer (e.g. target I-SMF) shall use this procedure to exchange N9 forwarding tunnel information with the NF Service Producer (e.g. source I-SMF).
The NF Service Consumer (e.g. target I-SMF) shall request the source I-SMF to establish one downlink and/or one uplink N9 data forwarding tunnels, as follows.
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.3.21-1: N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs
Figure 5.2.2.3.21-1: N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs
Up
Step 1.
The NF Service Consumer shall send a POST request, as specified in clause 5.2.2.3.1, with the following information:
  • dataForwarding attribute set to true, for the N9 Forwarding Tunnel establishment between Branching Points or UL CLs controlled by different I-SMFs;
  • n9DlForwardingTunnel attribute carrying the N9 downlink data forwarding tunnel info of target Branching Point or UL CL;
  • other information, if necessary.
Step 2a.
Same as step 2a of Figure 5.2.2.3.1-1, with the following information:
  • n9UlForwardingTunnel attribute carrying the N9 uplink data forwarding tunnel info of source Branching Point or UL CL;
  • other information, if necessary.
Step 2b.
If the source I-SMF cannot proceed with the request, the source I-SMF shall return an error response, as specified for step 2b of Figure 5.2.2.3.1-1.
Up
5.2.2.3.22  Remote UE Report during 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF procedure |R17|  p. 52
The requirements specified in clause 5.2.2.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.3.1-1, with the following modifications.
The POST request shall contain:
  • the n1SmMsg IE containing the Remote UE Report NAS Message.
For Home-Routed PDU Session or PDU session with I-SMF, the V-SMF or I-SMF shall invoke the Update service operation on the (H-)SMF, as specified in clause 5.2.2.8.2.24.
Step 2.
Same as step 2 of Figure 5.2.2.3.1-1, with the following modifications.
The POST response shall contain:
  • the n1SmMsg IE containing the Remote UE Report Response NAS Message.
Up

Up   Top   ToC