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.4  Procedures with GTP based S2a releasep. 57

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 releases the existing Sx session from the PGW-U.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.4-1: Interaction between CP and UP function with release of GTP based S2a
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 sends an Sx Session Termination Request to the PGW-U to release the Sx session.
Step 3.
The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed.

6.3.3.5  Procedures with dedicated bearer activation by PGWp. 58

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 activating new dedicated bearer.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.5-1: Interaction between CP and UP function with dedicated bearer activation by PGW
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 activation procedure based on the PCC decision provision (QoS policy) message received from the PCRF. It uses received QoS policy to assign the EPS Bearer QoS, i.e., it assigns the values to the bearer level QoS parameters QCI, ARP, GBR and MBR. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for activating new dedicated bearer for the UE.
Step 3.
The PGW-U shall allocate TEIDs for the new bearer(s). The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. It shall include the TEIDs it has allocated for the new bearer(s).
Step 4.
The relevant steps of the procedure as specified in the Figure above are executed.
Up

6.3.3.6  Procedures with bearer deactivation by PGWp. 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 deactivating the dedicated bearer.
Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.3.6-1: Interaction between CP and UP function with bearer deactivation by PGW-C
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 bearer deactivation procedure based on IP-CAN modifications encountered by the PCRF when the dynamic PCC is deployed. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for deactivating the dedicated bearer for the UE.
Step 3.
The PGW-U de-allocates the TEIDs for the dedicated bearer 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

Up   Top   ToC