Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.214  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4.3…   5…   5.6…   5.10…   6…   6.3…   6.3.1.2   6.3.1.3…   6.3.1.6…   6.3.2…   6.3.3…   6.3.3.4…   6.3.3.7…   6.3.4…   6.3.4.2…   6.3.4.2.2   6.3.4.3   6.4…   7…

 

6.3.3.7  Procedures with bearer modificationp. 59

This clause defines interactions between the CP and UP function during the following procedures:
During the above procedures following is the nature of interactions between the CP and UP function:
  • The PGW-C modifies the existing Sx session for modification of the existing bearer.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.7-1: Interaction between CP and UP function with bearer modification
Up
Step 1.
Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.
Step 2.
The PGW-C initiates dedicated bearer modification procedure based on the PCC decision provision (QoS policy) message received from the PCRF. It uses this QoS policy to determine that a service data flow shall be aggregated to or removed from an active bearer or that the authorized QoS of a service data flow has changed. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for modification of the existing bearer for the UE.
Step 3.
The PGW-U updates the Sx parameters and sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session.
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed.
Up

6.3.3.8  Procedures with handover from non-3GPP accessp. 60

This clause defines interactions between the CP and UP function during the following procedures:
During the above procedures following is the nature of interactions between the CP and UP function:
  • The SGW-C selects a SGW-U and creates an Sx session.
  • The SGW-C modifies the existing Sx session for modification of the bearer.
  • The PGW-C selects a PGW-U and creates an Sx session.
  • The PGW-C modifies the existing Sx session for modification of the bearer.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.8-1: Interaction between CP and UP function with handover from non-3GPP access
Up
Step 1.
Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.
Step 2.
The SGW-C shall select SGW-U as specified in clause 5.12 when the request with a Handover Indication information. The SGW-C sends Sx Session Establishment Request to the selected SGW-U for creating Sx session for the UE.
Step 3.
The SGW-U allocates F-TEIDu for all received bearers. The SGW-U sends Sx Session Establishment Response to the SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer.
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed. Since Handover Indication is included, the PGW-C may execute a PCEF-Initiated IP CAN Session Modification Procedure with the PCRF.
Step 5.
The PGW-C sends an Sx Session Modification Request to the PGW-U for modifying the Sx session for the UE.
Step 6.
The PGW-U allocates F-TEIDu for all received bearers. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer.
Step 7.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 8.
The SGW-C sends an Sx Session Modification Request after Radio and Access bearers are established at the SGW-C.
Step 9.
The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session.
Step 10.
The relevant steps of the procedure as specified in the Figure above are executed.
Step 11.
The PGW-C sends an Sx Session Modification Request to prompt the PGW-U to tunnel packets from non 3GPP IP access to 3GPP access system and immediately start routing packets to the SGW-U for the default and any dedicated EPS bearers established.
Step 12.
The PGW-U sends an Sx Session Modification Response to the PGW-C.
Step 13.
The relevant steps of the procedure as specified in the Figure above are executed.
Up

6.3.3.9  Procedures with handover from 3GPP accessp. 62

This clause defines interactions between the CP and UP function during the following procedures:
During the above procedures following is the nature of interactions between the CP and UP function:
  • The new PGW-C selects a new PGW-U and creates an Sx session.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.9-1: Interaction between CP and UP function with handover from 3GPP access
Up
Step 1.
Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the Figure above are executed.
Step 2.
The PGW-C allocates F-TEIDu for each and every bearer. Then the PGW-C sends an Sx Session Establishment Request to the selected PGW-U for modifying the Sx session for the UE.
Step 3.
The PGW-U allocates F-TEIDu for all received bearers. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful modification of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer.
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed.
Up

Up   Top   ToC