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.12 N2 Handover Execution with I-SMF Insertion   5.2.2.8.2.13 N2 Handover Cancellation with I-SMF Insertion   5.2.2.8.2.14 EPS to 5GS Handover Cancellation   5.2.2.8.2.15 5G-AN requested PDU session resource release   5.2.2.8.2.16 Xn Handover with or without I-SMF or V-SMF Change   5.2.2.8.2.17 EPS to 5GS Handover Failure   5.2.2.8.2.18 EPS Bearer ID revocation   5.2.2.8.2.19 Network requested PDU session release  
...

 

5.2.2.8.2.12  N2 Handover Execution with I-SMF Insertion   p. 77
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 set to NW_REQ_PDU_SES_MOD;
  • the hoPreparationIndication IE set to "false", to indicate that there is no handover preparation in progress anymore and that the SMF shall switch the DL user plane of the PDU session;
  • the qosFlowsRelNotifyList IE indicating the failed QoS flow(s), if one or more QoS flow(s) cannot be established at the target RAN.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
The SMF shall return a 200 OK response. The SMF shall switch the DL user plane of the PDU session using the N9 tunnel information that has been received in the icnTunnelInfo, if the hoPreparationIndication IE was set to "false" in the request.
If the handover preparation failed (e.g. the target 5G-AN failed to establish resources 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 set to NW_REQ_PDU_SES_MOD;
  • the cause attribute set to "HO_FAILURE";
  • the NotifyList IE with the cause set to "UP_SEC_NOT_FULFILLED", if the PDU Session was rejected by the Target NG-RAN because the User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates "Required"; and
  • the hoPreparationIndication IE set to "false", to indicate that there is no handover preparation in progress anymore.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
The SMF shall return a 200 OK response. If the SMF decides to keep the PDU session, the SMF shall switch the DL user plane of the PDU session using the N9 tunnel information that has been received in the icnTunnelInfo during the handover preparation; otherwise the SMF should trigger the PDU session release as specified in clause 5.2.2.8.3.3.
Up
5.2.2.8.2.13  N2 Handover Cancellation with I-SMF Insertion   p. 78
For handover cancellation, 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 set to NW_REQ_PDU_SES_MOD;
  • the cause attribute set to "HO_CANCEL";
  • the hoPreparationIndication IE set to "false", to indicate that there is no handover preparation in progress anymore.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
The SMF shall return a 200 OK response. The SMF shall release the resources prepared for the handover.
Up
5.2.2.8.2.14  EPS to 5GS Handover Cancellation   p. 78
If the handover cancellation, 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 set to PDU_SES_MOB;
  • the cause attribute set to "HO_CANCEL";
  • an empty list of EPS Bearer Ids;
  • the hoPreparationIndication IE set to "false", to indicate that there is no handover preparation in progress anymore.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
The H-SMF or SMF shall return a 200 OK response. The H-SMF or SMF shall release the resources prepared for the handover. The combined PGW-C+SMF shall not release the PDN connection that was attempted to be handed over.
Up
5.2.2.8.2.15  5G-AN requested PDU session resource release   p. 79
This clause applies only in case of 5G-AN requested PDU session resource release by sending the NGAP PDU SESSION RESOURCE NOTIFY to the AMF case (see step 1d in clause 4.3.4.3 of TS 23.502).
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 set to REL_DUE_TO_5G_AN_REQUEST to indicate that the PDU session resource has been released by the 5G-AN.
After receving the request, the SMF may decide to keep the PDU Session (with user plane connection deactivated) or release the PDU Session. If the SMF decides to keep the PDU Session, it shall return "200 OK" not including n1SmInfoToUe. If the SMF decides to release the PDU Session, it shall return "200 OK" including n1SmInfoToUe binary data containing the Message Type "PDU Session Release Command" and possibly PCO and cause information.
Up
5.2.2.8.2.16  Xn Handover 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 upSecurityInfo IE, if received from the NG-RAN;
  • 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 Xn 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.
The SMF shall verify that the upSecurity IE included in the received upSecurityInfo IE is same as the security policy for integrity protection and encryption that the SMF has locally stored. If there is a mismatch, the SMF shall send its locally stored security policy for integrity protection and encryption in upSecurity IE to NG-RAN as specified in clause 6.6.1 of TS 33.501.
For an Xn 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.17  EPS to 5GS Handover Failure   p. 79
If the handover to 5GS failed, e.g. rejected by the target NG-RAN, 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 set to PDU_SES_MOB;
  • the cause attribute set to "HO_FAILURE";
  • an empty list of EPS Bearer Ids;
  • the hoPreparationIndication IE set to "false", to indicate that there is no handover preparation in progress anymore.
Step 2.
Same as step 2 of Figure 5.2.2.8.2-1, with the following modifications.
The H-SMF or SMF shall return a 200 OK response. The H-SMF or SMF shall release the resources prepared for the handover. The combined PGW-C+SMF shall not release the PDN connection that was attempted to be handed over.
Up
5.2.2.8.2.18  EPS Bearer ID revocation   p. 80
When the AMF decides to revoke some EBI(s) and the I-SMF or V-SMF receives the request from AMF, 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 shall be set to EBI_ASSIGNMENT_REQ.
The NF Service Consumer shall include the revokeEbiList IE to request the SMF to release some EBI(s). The SMF shall disassociate the EBI(s) with the QFI(s) with which they are associated.
Up
5.2.2.8.2.19  Network requested PDU session release   p. 80
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 set to NW_REQ_PDU_SES_REL.

Up   Top   ToC