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 23.256  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   4.4…   4.5…   5…   5.2.3…   5.2.4…   5.2.5…   5.2.5.3…   5.2.5.4…   5.2.7   5.2.8…   5.2.9…   5.3…   5.4…   5.5…   6…   6.2…   6.3…   6.3.4… 
5.2.5.4 USS initiated C2 pairing policy configuration  5.2.5.4.1 USS initiated C2 pairing policy configuration in 5GS  5.2.5.4.2 USS initiated C2 pairing policy configuration in EPS 
...

 

5.2.5.4  USS initiated C2 pairing policy configuration  p. 51

5.2.5.4.1  USS initiated C2 pairing policy configuration in 5GS  p. 51
The USS initiated C2 pairing policy configuration Figure 5.2.5.4.1-1.
Copy of original 3GPP image for 3GPP TS 23.256, Fig. 5.2.5.4.1-1: USS initiated C2 pairing policy configuration in 5GS
Figure 5.2.5.4.1-1: USS initiated C2 pairing policy configuration in 5GS
(⇒ copy of original 3GPP image)
Up
Step 0.
The UAV is registered in the network and a PDU session is established as specified in clause 5.2.3.2.
Step 1.
The USS initiates the PDU Session modification by invoking the Nnef_AFSessionWithQoS_Create request including USS Identity/AF Identifier, UAV-UAVC Pairing info/Flow description(s), QoS reference. The UAV-UAVC Pairing info/Flow description(s) includes the UAV-C IP address. See step 1 in clause 4.15.6.6 of TS 23.502: Setting up an AF session with required QoS.
Step 2.
UAS NF/NEF authorizes the request from the USS followed by interacting with PCF triggering a Npcf_PolicyAuthorization_Create request and provides relevant parameters to the PCF.
PCF determines whether the request is authorized and if the requested QoS is allowed. PCF informs UAS NF/NEF if the request is accepted by invoking Npcf_PolicyAuthorization_Create response. See steps 2 - 4 in Figure 4.15.6.6-1 of TS 23.502.
Step 3.
UAS NF/NEF sends a Nnef_AFsessionWithQoS_Create response message (Transaction Reference ID, Result) to the USS. Result indicates whether the request is granted or not. See step 5 in Figure 4.15.6.6-1 of TS 23.502.
Step 4.
If the PCF determines that the SMF needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information. The updated policy information includes the UAV-C IP address. See steps 3 - 5 in Figure 4.16.5.2-1 of TS 23.502.
Step 5.
The PDU Session Modification continues and completes as in steps 2a - 13 in Figure 4.3.3.2-1 of TS 23.502, UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout). Based on the updated policy information received, the SMF determines and provides N4 rules to enable communication between UAV and UAV-C, e.g. Packet Detection Rules, Forwarding Action Rules.
Step 6-7.
[Optional] The PCF sends Npcf_PolicyAuthorization_Notify message to the UAS NF/NEF when the modification of the transmission resources corresponding to the QoS update succeeded or failed. The UAS NF/NEF transfers this information to the USS by sending Nnef_AFSessionWithQoS_Notify message. See steps 6 and 7 in Figure 4.15.6.6-1 of TS 23.502.
Up
5.2.5.4.2  USS initiated C2 pairing policy configuration in EPS  p. 52
The USS initiated C2 pairing policy configuration in EPS Figure 5.2.5.4.2-1.
Copy of original 3GPP image for 3GPP TS 23.256, Fig. 5.2.5.4.2-1: USS initiated C2 pairing policy configuration in EPS
Figure 5.2.5.4.2-1: USS initiated C2 pairing policy configuration in EPS
(⇒ copy of original 3GPP image)
Up
Step 0.
The UAV is registered in the network and a PDN Connection is established as specified in clause 5.2.3.3.
Step 1.
The USS initiates the PDN Connection modification by invoking the Nnef_AFSessionWithQoS_Create request including USS Identity/AF Identifier, Transaction Reference ID, UAV-UAVC Pairing info/Flow description(s), QoS reference. The UAV-UAVC Pairing info/Flow description(s) includes the UAV-C IP address. See step 1 in clause 4.15.6.6 of TS 23.502: Setting up an AF session with required QoS.
Step 2.
UAS NF/NEF authorizes the request from the USS followed by interacting with PCF triggering a Npcf_PolicyAuthorization_Create request and provides relevant parameters to the PCF.
PCF determines whether the request is authorized and if the requested QoS is allowed. PCF informs UAS NF/NEF if the request is accepted by invoking Npcf_PolicyAuthorization_Create response. See steps 2 - 4 in Figure 4.15.6.6-1 of TS 23.502.
Step 3.
UAS NF/NEF sends a Nnef_AFsessionWithQoS_Create response message (Transaction Reference ID, Result) to the USS. Result indicates whether the request is granted or not. See step 5 in Figure 4.15.6.6-1 of TS 23.502.
Step 4.
If the PCF determines that the SMF+PGW-C needs updated policy information, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with updated policy information. The updated policy information includes the UAV-C IP address. See steps 3 - 5 in Figure 4.16.5.2-1 of TS 23.502.
Step 5.
Based on the updated policy information received, the SMF+PGW-C determines and provides N4 rules to enable communication between UAV and UAV-C, e.g. Packet Detection Rules, Forwarding Action Rules.
Step 6.
[Conditional] If QoS needs to be updated: Based on the updated policy information received, the SMF+PGW-C determines N4 rules for QoS update and provides to the PGW-U.
Based on the updated policy information received, the SMF+PGW-C invokes the PDN GW initiated bearer modification with bearer QoS update procedure (clause 5.4.2.1 of TS 23.401) by sending Update Bearer Request message to the SGW. Steps 2 - 11 in Figure 5.4.2.1-1 of TS 23.401 are executed to update QoS in the UE and the RAN.
Step 7-8.
[Optional] The PCF sends Npcf_PolicyAuthorization_Notify message to the UAS NF/NEF when the modification of the transmission resources corresponding to the QoS update succeeded or failed. The UAS NF/NEF transfers this information to the USS by sending Nnef_AFSessionWithQoS_Notify message. See steps 6 and 7 in Figure 4.15.6.6-1 of TS 23.502.
Up

5.2.6  Void

Up   Top   ToC