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.2.7 Addition of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.2.8 Removal of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.2.9 Change of PSA for IPv6 multi-homing or UL CL controlled by I-SMF   5.2.2.8.2.10 PDU Session modification with I-SMF or V-SMF change   5.2.2.8.2.11 Sending by I-SMF of N4 notifications related with traffic usage reporting  
...

 

5.2.2.8.2.7  Addition of PSA and BP or UL CL controlled by I-SMF   p. 75
This clause applies only in case of non-roaming or LBO roaming as control of an UL CL or BP in VPLMN is not supported in HR roaming case (see clause 5.34.4 of TS 23.501).
An I-SMF and I-UPF have already been inserted for the PDU session.
The requirements specified in clause 5.2.2.8.2.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.2-1, with the following modifications:
The POST request shall contain:
  • the requestIndication IE set to NW_REQ_PDU_SES_MOD;
  • the indication that an UL CL or BP has been inserted into the data path of the PDU session;
  • the list of DNAIs supported by the inserted PSA;
  • the new UE IPv6 prefix at the PSA, assigned by the I-SMF or by the UPF supporting the PSA, if IPv6 multi-homing applies to the PDU session;
  • the icnTunnelInfo with the N9 tunnel information of the UL CL or BP for the downlink traffic, if a UPF different from the earlier I-UPF is selected for the UL CL or BP.
Step 2a.
Same as step 2a of Figure 5.2.2.8.2-1.
Up
5.2.2.8.2.8  Removal of PSA and BP or UL CL controlled by I-SMF   p. 76
This clause applies only in case of non-roaming or LBO roaming as control of an UL CL or BP in VPLMN is not supported in HR roaming case (see clause 5.34.4 of TS 23.501).
The requirements specified in clause 5.2.2.8.2.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.2-1, with the following modifications:
The POST request shall contain:
  • the requestIndication IE set to NW_REQ_PDU_SES_MOD;
  • the indication that an UL CL or BP has been removed from the data path of the PDU session;
  • the removed UE IPv6 prefix at the PSA, if IPv6 multi-homing applies to the PDU session;
  • the list of DNAIs supported by the removed PSA;
  • the icnTunnelInfo with the N9 tunnel information of the I-UPF for the downlink traffic.
Step 2a.
Same as step 2a of Figure 5.2.2.8.2-1.
Up
5.2.2.8.2.9  Change of PSA for IPv6 multi-homing or UL CL controlled by I-SMF   p. 76
This clause applies only in case of non-roaming or LBO roaming as control of an UL CL or BP in VPLMN is not supported in HR roaming case (see clause 5.34.4 of TS 23.501).
The requirements specified in clause 5.2.2.8.2.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.2-1, with the following modifications:
The POST request shall contain:
  • the requestIndication IE set to NW_REQ_PDU_SES_MOD;
  • the indication that a PSA is removed and another PSA is inserted;
  • the list of DNAIs supported by the inserted PSA;
  • the new UE IPv6 prefix at the inserted PSA, assigned by the I-SMF or by the UPF supporting the PSA, if IPv6 multi-homing applies to the PDU session;
  • the removed UE IPv6 prefix at the removed PSA, if IPv6 multi-homing applies to the PDU session;
  • the list of DNAIs supported by the removed PSA.
Step 2a.
Same as step 2a of Figure 5.2.2.8.2-1.
Up
5.2.2.8.2.10  PDU Session modification with I-SMF or V-SMF change   p. 76
During PDU Session modification with I-SMF or V-SMF change, the NF Service Consumer (i.e. the new V-SMF for a HR PDU session, or the new I-SMF for a PDU session with an I-SMF) shall update the PDU session in the H-SMF or SMF and provide the information of the new I-SMF or V-SMF.
The requirements specified in clause 5.2.2.8.2.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.2-1, with the following additions:
The POST request shall contain:
  • the requestIndication set to NW_REQ_PDU_SES_MOD or UE_REQ_PDU_SES_MOD for network requested or UE requested PDU session modification respectively;
  • the ismfPduSessionUri or vsmfPduSessionUri IE containing the callback URI ({vsmfPduSessionUri} or {ismfPduSessionUri}) representing the PDU session in the new I-SMF or new V-SMF. The H-SMF or SMF shall construct the callback URIs based on the received {vsmfPduSessionUri} or {ismfPduSessionUri} as defined in clause 6.1, e.g. the callback URI "{vsmfPduSessionUri}/modify" to modify a PDU session in the V-SMF;
  • the ismfId or vsmfId IE containing the identifier of the new I-SMF or new V-SMF;
  • optionally the iSmfServiceInstanceId or vSmfServiceInstanceId IE containing the serviceInstanceId of the new I-SMF or new V-SMF service instance serving the PDU session;
  • the disasterRoamingInd IE set to true if the V-SMF is indicated by the AMF that the UE is registered for Disaster Roaming service;
  • the supportedFeatures IE indicating the features the NF Service Consumer supports, if at least one feature defined in clause 6.1.8 is supported.
Step 2.
Same as step 1 of Figure 5.2.2.8.2-1, the SMF shall replace the corresponding information for the old I-SMF or old V-SMF stored locally with the received information. 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 feature defined in clause 6.1.8 is supported by the updated PDU session resource.
Up
5.2.2.8.2.11  Sending by I-SMF of N4 notifications related with traffic usage reporting   p. 77
This clause applies only in case of non-roaming or LBO roaming as control of an UL CL or BP in VPLMN is not supported in HR roaming case (see clause 5.34.4 of TS 23.501).
The requirements specified in clause 5.2.2.8.2.1 shall apply with the following modifications.
Step 1.
Same as step 1 of Figure 5.2.2.8.2-1, with the following modifications:
The POST request shall contain:
  • the requestIndication IE set to NW_REQ_PDU_SES_MOD;
  • N4 information related with traffic usage reporting (i.e. PFCP Session Report Request, see Annex D of TS 29.244);
  • the DNAI related to the N4 information if the latter relates to a local PSA;
Step 2a.
Same as step 2a of Figure 5.2.2.8.2-1, with the following modifications:
The content of the POST response shall contain:
  • N4 response information (i.e. PFCP Session Report Response);
  • the DNAI related to the N4 information if the latter relates to a local PSA.
Up

Up   Top   ToC