6.3.4 Updates to procedures specified in TS 23.060 [5]

23.2143GPPArchitecture enhancements for control and user plane separation of EPC nodesRelease 17TS

6.3.4.1 Procedures with PDN connection deactivation

6.3.4.1.1 Procedures with SGSN terminating S4 interface

This clause defines interactions between the CP and UP function during the following procedures related to the deactivation of a PDN connection:

Group 1:

– Combined GPRS / IMSI Attach procedure:

– Including steps specific for S4 SGSN: Combined GPRS / IMSI Attach procedure, Delete Bearer by the new SGSN, using S4, and Combined GPRS / IMSI Attach procedure, Delete Bearer by the old SGSN, using S4.

– MS-Initiated Combined GPRS / IMSI Detach Procedure.

– SGSN-Initiated GPRS Detach Procedure.

– HLR-Initiated GPRS Detach Procedure:

– Including steps specific for S4 SGSN: SGSN interaction during Detach Procedure when using S4.

– MS Initiated Bearer Deactivation Procedure for A/Gb mode (with Teardown Ind).

– MS Initiated Bearer Deactivation Procedure for Iu mode (with Teardown Ind).

– SGSN-initiated Bearer Deactivation Procedure (with Teardown Ind):

– Including steps specific for S4 SGSN: MS-and SGSN Initiated PDN connection Deactivation Procedure using S4.

Group 2:

– GGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind):

– Including steps specific for S4 SGSN: PDN GW-initiated Bearer Deactivation Procedure using S4, part 1 and part 2.

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

– The SGW-C releases the existing Sx session from SGW-U.

– The PGW-C releases the existing Sx session from PGW-U.

– The SGW-C modifies the existing Sx session for SGW-U.

– The PGW-C modifies the existing Sx session for PGW-U.

Figure 6.3.4.1.1-1: Interaction between CP and UP function with PDN connection deactivation Group 1

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.

2a. The SGW-C sends an Sx Session Modification Request to the SGW-U to modify the Sx session. SGW-C shall request SGW-U to stop counting uplink packets for the affected bearers. SGW-C shall also request the SGW-U to discard uplink packets received from eNodeB for the affected bearers.

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

2c. The relevant steps of the procedure as specified in the figure above are executed.

3a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.

3b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

3c. The relevant steps of the procedure as specified in the figure above are executed.

3d. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session.

3e. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session.

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

5a. The SGW-C may send an Sx Session Modification Request to the SGW-U in detach and Bearer Deactivation procedures. 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.

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

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

7a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.

7b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

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

9a. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session.

9b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session.

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

Figure 6.3.4.1.1-2: Interaction between CP and UP function with PDN connection deactivation Group 2

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.

2a. The PGW-C sends an Sx Session Modification Request to the PGW-U when it initiates bearer deactivation procedure. PGW-C shall indicate PGW-U to stop counting downlink packets for the affected bearers. PGW-C shall also indicate the PGW-U to discard downlink packets received for the affected bearers.

2b. The PGW-U sends an Sx Session Modification Response to the PGW-C.

3a. Void.

3b. Void.

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

5a. The SGW-C sends an Sx Session Termination Request to the SGW-U to release the Sx session.

5b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session.

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

7a. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session.

7b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

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

6.3.4.1.2 Procedures with SGSN terminating Gn/Gp interface

This clause defines interactions between the CP and UP function during the following procedures related to the deactivation of a PDN connection:

Group 1:

– Combined GPRS / IMSI Attach procedure.

– MS-Initiated Combined GPRS / IMSI Detach Procedure.

– SGSN-Initiated GPRS Detach Procedure.

– HLR-Initiated GPRS Detach Procedure.

– MS Initiated PDP Context Deactivation Procedure for A/Gb mode (with Teardown Ind).

– MS Initiated PDP Context Deactivation Procedure for Iu mode (with Teardown Ind).

– SGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind).

Group 2:

– GGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind).

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

Figure 6.3.4.1.2-1: Interaction between CP and UP function with PDN connection deactivation Group 1

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.

2a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.

2b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

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

4a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session.

4b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

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

Figure 6.3.4.1.2-2: Interaction between CP and UP function with PDN connection deactivation Group 2

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.

2a. The PGW-C sends an Sx Session Modification Request to the PGW-U when it initiates bearer deactivation procedure. PGW-C shall indicate PGW-U to stop counting downlink packets for the affected bearers. PGW-C shall also indicate the PGW-U to discard downlink packets received for the affected bearers.

2b. The PGW-U sends an Sx Session Modification Response to the PGW-C.

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

4a. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session.

4b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session.

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

6.3.4.2 Procedures with PDN connection modification

6.3.4.2.1 Procedures with SGSN terminating S4 interface

This clause defines interactions between the CP and UP function during the following procedures related to the modification of a PDN connection.

Group 1 Procedures for Location Management, Handover, Service Request and Inter-System Change:

– Inter SGSN Routeing Area Update Procedure:

– Including steps specific for S4 SGSN: Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4.

– Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure:

– Including steps specific for S4 SGSN: Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4.

– Iu mode RA Update Procedure:

– Including steps specific for S4 SGSN: Routeing Area Update Procedure using S4.

– SRNS Relocation Procedure.

– Combined Hard Handover and SRNS Relocation Procedure.

– Combined Cell / URA Update and SRNS Relocation Procedure:

– Including steps specific for S4 SGSN: Serving RNS Relocation Procedure, Combined Hard Handover and SRNS Relocation Procedure, and Combined Cell / URA Update and SRNS Relocation Procedure Using S4.

– Enhanced Serving RNS Relocation:

– Including steps specific for S4 SGSN: Enhanced Serving RNS Relocation Procedure using S4.

– MS Initiated Service Request Procedure.

– Network Initiated Service Request Procedure:

– Including steps specific for S4 SGSN: UE Initiated Service Request Procedure Using S4.

– Iu mode to A/Gb mode Intra SGSN Change:

– Including steps specific for S4 SGSN: Iu mode to A/Gb mode Intra SGSN Change using S4.

– A/Gb mode to Iu mode Intra SGSN Change:

– Including steps specific for S4 SGSN: A/Gb mode to Iu mode Intra-SGSN Change using S4.

– Iu mode to A/Gb mode Inter-SGSN Change:

– Including steps specific for S4 SGSN: Iu mode to A/Gb mode Inter-SGSN Change using S4.

– A/Gb mode to Iu mode Inter SGSN Change:

– Including steps specific for S4 SGSN: A/Gb mode to Iu mode Inter-SGSN Change using S4.

– GPRS Paging Procedure (A/Gb mode):

– S4 specific handling in Paging response for GPRS Downlink Transfer with no established user plane on S4.

Group 2 UE/SGSN initiated PDN connection modification:

– Secondary PDP Context Activation Procedure for A/Gb mode.

– Secondary PDP Context Activation Procedure for Iu mode:

– Including steps specific for S4 SGSN: Secondary PDP Context Activation Procedure, PDP Creation part, using S4.

– MS-Initiated PDP Context Modification Procedure, A/Gb mode.

– MS-Initiated PDP Context Modification Procedure, Iu mode.

– SGSN-Initiated PDP Context Modification Procedure, A/Gb mode.

– SGSN-Initiated PDP Context Modification Procedure, Iu mode:

– Including steps specific for S4 SGSN: Request part of SGSN-Initiated EPS Bearer Modification Procedure using S4, and Update part of SGSN-Initiated EPS Bearer Modification Procedure using S4.

– MS Initiated PDP Context Deactivation Procedure for A/Gb mode (without Teardown Ind).

– MS Initiated PDP Context Deactivation Procedure for Iu mode (without Teardown Ind).

– SGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind):

– Steps specific for S4 SGSN: MS-and SGSN Initiated Bearer Deactivation Procedure.

Group 3 PGW initiated PDN connection modification:

– Network Requested Secondary PDP Context Activation Procedure using S4.

– GGSN-Initiated PDP Context Modification Procedure:

– Including steps specific for S4 SGSN: PGW-Initiated Bearer Modification Procedure, A/Gb mode.

– GGSN-Initiated PDP Context Modification Procedure:

– Including steps specific for S4 SGSN: PGW-Initiated Bearer Modification Procedure, Iu mode.

– GGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind):

– Including steps specific for S4 SGSN: PGW-initiated Bearer Deactivation Procedure.

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

– The SGW-C informs the SGW-U to modify the Sx session.

– The PGW-C informs the PGW-U to modify the Sx session.

Figure 6.3.4.2.1-1: Interaction between CP and UP function with PDN connection modification, Group 1

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.

2a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session.

2b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session.

2c. The relevant steps of the procedure as specified in the figure above are executed.

3a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session.

3b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session.

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

NOTE 1: Step 2a/2b happens when SGW-C receives request message from S4 SGSN, and step 3a/3b happens when PGW-C receives request message from SGW-C.

Figure 6.3.4.2.1-2: Interaction between CP and UP function with PDN connection modification, Group 2

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.

2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", PGW-C may request PGW-U to allocate F-TEID for the dedicated bearer. For "MS- or SGSN- Initiated PDP Context Deactivation Procedure", PGW-C shall request PGW-U to stop counting and stop forwarding packets for the affected bearers.

2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session.

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

4a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", SGW-C requests SGW-U to allocate F-TEID for the dedicate bearer. For "MS- or SGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to stop counting and stop forwarding packets for the affected bearers.

4b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session.

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

6a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", the SGW-C shall include the F-TEIDu of the activated bearer received from the S4 SGSN or RNC. For "MS- or SGSN- initiated PDP Context Modification" with bearer QoS update procedure, SGW-C provides updated QoS parameters to SGW-U. For "MS- or SGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to remove the PDR for the affected bearers.

6b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session.

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

8a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For "MS- or SGSN- Initiated PDP Context Deactivation Procedure, the PGW-C shall request PGW-U to remove the PDR for the affected bearers.

8b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session.

NOTE 2: Step 2a/2b happens before PGW-C sends request message to SGW-C, and step 8a/8b happens when PGW-C receives response message from SGW-C.

NOTE 3: Step 4a/4b happens when SGW-C receives request message from PGW-C, and step 6a/6b happens when SGW-C receives response message from S4 SGSN.

Figure 6.3.4.2.1-3: Interaction between CP and UP function with PDN connection modification, Group 3

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.

2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", PGW-C may request PGW-U to allocate F-TEID for the dedicated bearer. For "GGSN Initiated PDP Context Deactivation Procedure", PGW-C shall request PGW-U to stop counting and stop forwarding packets for the affected bearers.

2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session.

3a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", SGW-C requests SGW-U to allocate F-TEID for the dedicated bearer. For "GGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to stop counting and stop forwarding packets for the affected bearers.

3b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session.

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

5a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", the SGW-C shall include the F-TEIDu of the activated bearer received from the S4 SGSN or RNC. For "GGSN initiated PDP Context Modification" with bearer QoS update, SGW-C provides updated QoS parameters to SGW-U. For "GGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to remove the PDR for the affected bearers.

5b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session.

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

7a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For "GGSN initiated PDP Context Modification" with bearer QoS update, PGW-C provides updated QoS parameters to PGW-U. For "GGSN Initiated PDP Context Deactivation Procedure, the PGW-C shall request PGW-U to remove the PDR for the affected bearers.

7b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session.

NOTE 4: Step 2a/2b happens before PGW-C sends request message to SGW-C, and step 7a/7b happens when PGW-C receives response message from SGW-C.

NOTE 5: Step 3a/3b happens when SGW-C receives request message from PGW-C, and step 5a/5b happens when SGW-C receives response message from S4 SGSN.

6.3.4.2.2 Procedures with SGSN terminating Gn/Gp interface

This clause defines interactions between the CP and UP function during the following procedures related to the modification of a PDN connection.

Group 1 Procedures for Location Management, Handover, Service Request and Inter-System Change:

– Inter SGSN Routeing Area Update Procedure.

– Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure.

– Iu mode RA Update Procedure.

– SRNS Relocation Procedure.

– Combined Hard Handover and SRNS Relocation Procedure.

– Combined Cell / URA Update and SRNS Relocation Procedure.

– Enhanced Serving RNS Relocation.

– MS Initiated Service Request Procedure.

– Network Initiated Service Request Procedure.

– Iu mode to A/Gb mode Intra SGSN Change.

– A/Gb mode to Iu mode Intra SGSN Change.

– Iu mode to A/Gb mode Inter-SGSN Change.

– A/Gb mode to Iu mode Inter SGSN Change.

– GPRS Paging Procedure (A/Gb mode).

Group 2 UE/SGSN initiated PDN connection modification:

– Secondary PDP Context Activation Procedure for A/Gb mode.

– Secondary PDP Context Activation Procedure for Iu mode.

– SGSN-Initiated PDP Context Modification Procedure, A/Gb mode.

– SGSN-Initiated PDP Context Modification Procedure, Iu mode.

– MS-Initiated PDP Context Modification Procedure, A/Gb mode.

– MS-Initiated PDP Context Modification Procedure, Iu mode.

– MS Initiated PDP Context Deactivation Procedure for A/Gb mode (without Teardown Ind).

– MS Initiated PDP Context Deactivation Procedure for Iu mode (without Teardown Ind).

– SGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind).

Group 3 PGW initiated PDN connection modification:

– Network Requested Secondary PDP Context Activation Procedure using Gn

– GGSN-Initiated PDP Context Modification Procedure for A/Gb mode

– GGSN-Initiated PDP Context Modification Procedure for Iu mode

– GGSN-initiated PDP Context Deactivation Procedure

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

– The PGW-C informs the PGW-U to modify the Sx session.