Content for TS 23.214 Word version: 18.0.0

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.1.6 Procedures with release of PDN connection 6.3.1.7 Procedures with modification of bearer
...

6.3.1.6 Procedures with release of PDN connection p. 48

This clause defines interactions between the CP and UP function during the following procedures:

UE-initiated Detach procedure for E-UTRAN (clause 5.3.8.2.1 of TS 23.401).
UE-initiated Detach procedure for GERAN/UTRAN with ISR activated (clause 5.3.8.2.2 of TS 23.401).
MME-initiated Detach procedure (clause 5.3.8.3 of TS 23.401).
SGSN-initiated Detach procedure with ISR activated (clause 5.3.8.3A of TS 23.401).
HSS-initiated Detach procedure (clause 5.3.8.4 of TS 23.401).
UE or MME requested PDN disconnection (clause 5.10.3 of TS 23.401).

During the above procedures following is the nature of interactions between the CP and UP function:

The SGW-C terminates the Sx session at the SGW-U.
The PGW-C terminates the Sx session at the PGW-U.

Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.6-1: Interaction between CP and UP function during release of PDN connection

Figure 6.3.1.6-1: Interaction between CP and UP function during release of PDN connection
(⇒ copy of original 3GPP image)

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 sends an Sx Session Modification Request to the SGW-U. SGW-C shall indicate SGW-U to stop counting uplink packets for the affected bearers. SGW-C shall also indicate the SGW-U to discard uplink packets received from eNodeB for the affected bearers.

Step 3.

The SGW-U sends an Sx Session Modification Response to the SGW-C.

Step 4.

The relevant steps of the procedure as specified in the Figure above are executed.

Step 5.

The PGW-C sends an Sx Session Termination Request to the PGW-U.

Step 6.

The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the successful termination of the Sx session. Additionally, if the usage reporting is configured by the PGW-C (as specified in clause 5.3.2) the PGW-U shall provide the usage report(s) for the PDN connection (as specified in clause 5.3.3) to the PGW-C.

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 Termination Request to the SGW-U.

Step 9.

The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the successful termination of the Sx session. Additionally, if the usage reporting is configured by the SGW-C (as specified in clause 5.3.2) the SGW-U shall provide the usage report(s) for the PDN connection (as specified in clause 5.3.3) to the SGW-C.

6.3.1.7 Procedures with modification of bearer p. 50

This clause defines interactions between the CP and UP function during the following procedures:

Dedicated bearer activation (clause 5.4.1 of TS 23.401).
PDN GW initiated bearer modification with bearer QoS update (clause 5.4.2.1 of TS 23.401).
PDN GW initiated bearer modification without bearer QoS update (clause 5.4.3 of TS 23.401).
PDN GW initiated bearer deactivation (clause 5.4.4.1 of TS 23.401).
HSS Initiated Subscribed QoS Modification (clause 5.4.2.2 of TS 23.401).
MME Initiated Dedicated Bearer Deactivation (clause 5.4.4.2 of TS 23.401).

During the above procedures following is the nature of interactions between the CP and UP function:

The PGW-C modifies the Sx session at the PGW-U.
The SGW-C modifies the Sx session at the SGW-U.

Copy of original 3GPP image for 3GPP TS 23.214, Fig. 6.3.1.7-1: Interaction between CP and UP function during modification of bearer

Figure 6.3.1.7-1: Interaction between CP and UP function during modification of bearer
(⇒ copy of original 3GPP image)

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 Modification Request to the PGW-U. For "Dedicated bearer activation", PGW-C indicates PGW-U to allocate F-TEID for the new dedicated bearer. For "PGW/MME initiated bearer deactivation procedure", PGW-C shall indicate PGW-U to stop counting and stop forwarding downlink packets for the affected bearer(s).

Step 3.

The PGW-U 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.

Step 5.

The SGW-C may send an Sx Session Modification Request to the SGW-U. For "Dedicated bearer activation", SGW-C indicates SGW-U to allocate F-TEID for the new dedicated bearer.

Step 6.

The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session.

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 to the SGW-U. For dedicated bearer activation procedure, the SGW-C shall include the F-TEIDu of the activated bearer received from the eNodeB. For PDN GW/HSS initiated bearer modification with bearer QoS update procedure, SGW-C provides updated QoS parameters to SGW-U. For PDN GW/MME initiated bearer deactivation procedure, SGW-C shall indicate SGW-U to remove the PDR(s) for the affected bearer(s).

If the default bearer belonging to a PDN connection is deactivated, the SGW-C sends an Sx Session Termination Request to the SGW-U.

Step 9.

The SGW-U sends an Sx Session Modification Response or an Sx Session Termination Response to the SGW-C confirming the successful modification or termination 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 the PGW-U. For dedicated bearer activation procedure, the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For PDN GW/HSS initiated bearer modification with bearer QoS update procedure, PGW-C provides updates according to the changed QoS parameters and TFT (if applicable) to PGW-U. For "PDN GW initiated bearer modification without bearer QoS update" procedure, PGW-C provides updates according to the changed APN-AMBR and/or TFT to PGW-U. For PDN GW/MME initiated bearer deactivation procedure, PGW-C shall indicate PGW-U to remove the PDR(s) for the affected bearer(s).

If the default bearer belonging to a PDN connection is deactivated, the PGW-C sends an Sx Session Termination Request to the PGW-U.

Step 12.

The PGW-U sends an Sx Session Modification Response or an Sx Session Termination Response to the PGW-C confirming the successful modification or termination of the Sx session.

Step 13.

The relevant steps of the procedure as specified in the Figure above are executed.