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.8.3.6 Addition of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.3.7 Removal of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.3.8 Change of PSA for IPv6 multi-homing or UL CL controlled by I-SMF   5.2.2.8.3.9 Policy update procedures with an I-SMF   5.2.2.8.3.10 Simultaneous change of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.3.11 Network (e.g. AMF) triggered network slice replacement with PDU session retained  
...

 

5.2.2.8.3.6  Addition of PSA and BP or UL CL controlled by I-SMF   p. 86
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request shall contain:
  • N4 information for the handling of the local traffic that is offloaded at the PSA (see Annex D of TS 29.244);
  • N4 information for the local offload rules at the UL CL/BP (see Annex D of TS 29.244);
  • the DNAI related to N4 information targeting the local PSA;
  • the indication that the DNAI shall not change, if applicable;
  • the indication that the local PSA shall not change, if applicable.
For the Simultaneous change of Branching Points or UL CLs controlled by different I-SMFs (see clause 4.23.9.5 of TS 23.502), the POST request may also contain:
  • n9DataForwardingInd set to true, if the N9 Forwarding Tunnel establishment between Branching Points or UL CLs to support the EAS session continuity is required;
  • n9UlPdrIdList pointing to the UL PDR(s) included in the N4 information for UL N9 forwarding in the target Branching Point or UL CL to support the EAS session continuity;
  • n9InactivityTimer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity.
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1, with the following modifications.
The content of the POST response shall contain:
  • N4 response information;
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Step 2b.
Same as step 2b of Figure 5.2.2.8.3.1-1, with the following modifications.
For a 4xx/5xx response, the message body shall contain a VsmfUpdateError structure, including N4 response information if available (e.g. PFCP Session Establishment Response with a rejection cause).
Up
5.2.2.8.3.7  Removal of PSA and BP or UL CL controlled by I-SMF   p. 87
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request shall contain:
  • N4 information for the removal of the local offload rules at the UL CL/BP and PSA (see Annex D of TS 29.244);
  • the DNAI related to N4 information targeting the local PSA.
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1, with the following modifications.
The content of the POST response shall contain:
  • N4 response information;
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Step 2b.
Same as step 2b of Figure 5.2.2.8.3.1-1, with the following modifications.
For a 4xx/5xx response, the message body shall contain a VsmfUpdateError structure, including N4 response information if available (e.g. PFCP Session Deletion Response with a rejection cause).
Up
5.2.2.8.3.8  Change of PSA for IPv6 multi-homing or UL CL controlled by I-SMF   p. 87
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request shall contain:
  • N4 information for the removal of the local offload rules at the removed PSA (see Annex D of TS 29.244);
  • N4 information for the handling of the local traffic that is offloaded at the inserted PSA (see Annex D of TS 29.244);
  • N4 information for the updating of the local offload rules at the UL CL/BP (see Annex D of TS 29.244);
  • the DNAIs related to N4 information targeting the removed or inserted PSA.
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1, with the following modifications.
The content of the POST response shall contain:
  • N4 response information;
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Step 2b.
Same as step 2b of Figure 5.2.2.8.3.1-1, with the following modifications.
For a 4xx/5xx response, the message body shall contain a VsmfUpdateError structure, including N4 response information if available (e.g. PFCP Session Establishment Response with a rejection cause).
Up
5.2.2.8.3.9  Policy update procedures with an I-SMF   p. 88
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request may contain:
  • N4 information updating local offload rules at the I-SMF (see Annex D of TS 29.244);
  • the DNAI related to the N4 information if the latter relates to a local PSA;
  • an updated list of DNAI(s) of interest for the PDU Session.
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1, with the following modifications.
The content of the POST response shall contain:
  • N4 response information, if N4 information was received in the request;
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Step 2b.
Same as step 2b of Figure 5.2.2.8.3.1-1, with the following modifications.
For a 4xx/5xx response, the message body shall contain a VsmfUpdateError structure, including N4 response information if available (e.g. PFCP Session Modification Response with a rejection cause).
Up
5.2.2.8.3.10  Simultaneous change of PSA and BP or UL CL controlled by I-SMF   p. 88
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request shall contain:
  • N4 information for the removal of the local offload rules at the removed PSA (see Annex D of TS 29.244);
  • N4 information for the handling of the local traffic that is offloaded at the inserted PSA (see Annex D of TS 29.244);
  • N4 information for the removal of the local offload rules at the removed UL CL/BP (see Annex D of TS 29.244);
  • N4 information for the creation of the local offload rules at the inserted UL CL/BP (see Annex D of TS 29.244);
  • the DNAIs related to N4 information targeting the removed or inserted PSA.
The content of the POST request may contain:
  • n9DataForwardingInd set to true, if the N9 Forwarding Tunnel establishment between Branching Points or UL CLs to support the EAS session continuity is required;
  • n9UlPdrIdList pointing to the UL PDR(s) included in the N4 information for UL N9 forwarding in the target Branching Point or UL CL to support the EAS session continuity;
  • n9InactivityTimer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity.
The SMF may only include the N4 information for the inserted PSA and the inserted UL CL/BP as specified in clause D.2.7 of TS 29.244, if the I-SMF only includes the PsaInformation corresponding to the new PSA and the UlclBpInformation corresponding to the new UL CL or BP during simultaneous change of PSA and BP or UL CL and data forwarding between the new and old UL CL/BPs for EAS session continuity is required.
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1, with the following modifications.
The content of the POST response shall contain:
  • N4 response information;
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Step 2b.
Same as step 2b of Figure 5.2.2.8.3.1-1, with the following modifications.
For a 4xx/5xx response, the message body shall contain a VsmfUpdateError structure, including N4 response information if available (e.g. PFCP Session Establishment Response with a rejection cause).
Up
5.2.2.8.3.11  Network (e.g. AMF) triggered network slice replacement with PDU session retained   p. 89
During network slice replacement procedure, for HR PDU session, if the H-SMF determines to retain the PDU session for the alternative HPLMN S-NSSAI, the H-SMF shall use this procedure to instruct the V-SMF that the PDU session is retained for the alternative HPLMN S-NSSAI (see clause 4.3.3.3 of TS 23.502).
The requirements specified in clause 5.2.2.8.3.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.3.1-1, with the following modifications.
The requestIndication shall be set to NW_REQ_PDU_SES_MOD.
The content of the POST request shall contain:
  • an altHplmnSnssai IE to indicate the alternative HPLMN S-NSSAI applied to the PDU session;
  • a pduSessionRetainInd IE to indicate the PDU session is retained;
Step 2a.
Same as step 2a of Figure 5.2.2.8.3.1-1.
Up

Up   Top   ToC