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.8.2.20 N2 Handover Execution with or without I-SMF or V-SMF Change   5.2.2.8.2.21 Reporting of satellite backhaul change to (H-)SMF   5.2.2.8.2.22 Simultaneous change of PSA and BP or UL CL controlled by I-SMF   5.2.2.8.2.23 Service Request without I-SMF/V-SMF Change or with I-SMF/V-SMF Change or with I-SMF Insertion   5.2.2.8.2.24 Remote UE Report during 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF  
...

 

5.2.2.8.2.20  N2 Handover Execution with or without I-SMF or V-SMF Change   p. 79
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 qosFlowsRelNotifyList IE indicating the failed QoS flow(s), if one or more QoS flow(s) cannot be established at the target RAN.
For an N2 handover with an I-SMF or V-SMF change, the requirements specified in step 1 of clause 5.2.2.8.2.10, other than how to set the requestIndication, shall also apply.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
For an N2 handover with an I-SMF or V-SMF change, the requirements specified in step 2 of clause 5.2.2.8.2.10 shall also apply.
Up
5.2.2.8.2.21  Reporting of satellite backhaul change to (H-)SMF   p. 79
If the V-SMF/I-SMF and the anchor SMF support the 5GSAT feature (see clause 6.1.8), the V-SMF/I-SMF shall report a change of the satellite backhaul category used towards the 5G AN currently serving the UE if:
  • the satelliteBackhaulCat IE has been received from the AMF and there is a change of the satelliteBackhaulCat IE compared to what has been signalled earlier to the (H-)SMF (as determined from the SmContext); or
  • upon inter-AMF mobility (when a target AMF is taking over the control of the PDU session), the new AMF does not include the satelliteBackhaulCat IE and a satellite backhaul category had been signalled to the SMF (as determined from the SmContext).
To report a change of the satellite backhaul category, 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, unless specified otherwise in clause 5.2.2.8. if the change of the satelliteBackhaulCat IE is detected during a procedure for which it is requested to report a different requestIndication value; and
  • the satelliteBackhaulCat IE set to the value received from the AMF or, in the latter case, set to the value "NON_SATELLITE" to indicate that there is no longer any satellite backhaul towards the new 5G AN serving the UE.
Up
5.2.2.8.2.22  Simultaneous change of PSA and BP or UL CL controlled by I-SMF   p. 79
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;
  • a PsaInformation corresponding to the new PSA:
    • a PsaIndication set to "PSA_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 NF Instance Id of the inserted PSA;
  • a UlclBpInformation corresponding to the new UL CL or BP if it separate from the new PSA:
    • the NF Instance Id of the inserted UL CL or BP;
  • a PsaInformation corresponding to the removed PSA, if either the I-SMF or the SMF does not support the "N9FSC" feature:
    • a PsaIndication set to "PSA_REMOVED";
    • 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.23  Service Request without I-SMF/V-SMF Change or with I-SMF/V-SMF Change or with I-SMF Insertion   p. 80
During a Service Request without I-SMF/V-SMF Change or with I-SMF/V-SMF Change or with I-SMF Insertion, the NF Service Consumer (i.e. the V-SMF for a HR PDU session, or the I-SMF for a PDU session with an I-SMF) shall update the PDU session in the H-SMF or SMF as follows:
Reproduction of 3GPP TS 29.502, Fig. 5.2.2.8.2.23-1: PDU session update towards H-SMF or SMF during Service Request
Figure 5.2.2.8.2.23-1: PDU session update towards H-SMF or SMF during Service Request
Up
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 additionally contain:
  • the upCnxState IE set to ACTIVATING if the User Plane resource for the PDU Session is going to be established by the I-SMF/V-SMF.
Step 2a.
Same as step 2a of Figure 5.2.2.8.2-1, with the following modifications.
The SMF shall behave as specified in clause as specified in clause 4.23.4.2 (step 7a) and clause 4.23.4.3 (step 8a) of TS 23.502.
Step 2b.
Same as step 2b of Figure 5.2.2.8.2-1.
Step 3.
Same as step 1 of Figure 5.2.2.8.2-1, with the following modifications.
The POST request shall additionally contain:
  • the upCnxState IE set to ACTIVATED when User Plane resource has been established, if the upCnxState IE with the value ACTIVATING was previously provided to the SMF in the procedure, via a previous Update operation (step 1) or via Create operation for I-SMF/V-SMF insertion (see clause 5.2.2.7.6).
Step 4a.
Same as step 2a of Figure 5.2.2.8.2-1, with the following modifications.
The SMF shall behave as specified in clause as specified in clause 4.23.4.2 (step 16) and clause 4.23.4.3 (step 20a) of TS 23.502.
Step 4b.
Same as step 2b of Figure 5.2.2.8.2-1.
Up
5.2.2.8.2.24  Remote UE Report during 5G ProSe Communication via 5G ProSe Layer-3 UE-to-Network Relay without N3IWF   p. 81
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 n1SmInfoFromUe IE containing "Remote UE context connected" and/or "Remote UE context disconnected" NAS IE.
    • Up

    Up   Top   ToC