Double Delete Optimization Call Flow

This section describes the Double Delete Optimization call flow.

Double Delete Optimization Call Flow
Double Delete Optimization Call Flow Description

Step

Description

1

Initial Attach procedure is completed.

The PDN1(ebi 5) and PDN2(ebi 6,7,8) is established.

The Delete Bearer Request (ebi 6) and Sx Modify Request is pending and the Delete Session Request is received from the MME.

The PGW sends the Delete Bearer Request (ebi 6) for PDN2 to the S5-GTP-EP.

2

The S5-GTP-EP forwards the Delete Bearer Request (ebi 6) for PDN2 to the cnSGW.

3

The cnSGW sends the Sx Modify Request to the PFCP-EP.

4

Waits for the Sx Modify Response for the Delete Bearer Request (ebi 6) default.

The MME sends the Delete Session Request for PDN2 to the S11-GTP-EP.

5

The S11-GTP-EP forwards the Delete Session Request for PDN2 to the cnSGW.

6

Collision detected at PDN2.

Deletion process running at PDN2.

New procedure aborted and old procedure continue.

The S11 Delete Bearer Request isn't send after an Sx Modify Response of the Delete Bearer Request.

The cnSGW sends Delete Session Response (Accepted) for PDN2 to the S11-GTP-EP.

7

The S11-GTP-EP forwards the Delete Session Response (Accepted) for PDN2 to the MME.

8

While the Delete Bearer Request handling continues, the PFCP-EP sends Sx Modify Response 1 for PDN2 to the cnSGW.

9

The cnSGW sends the Sx Delete Request for PDN2 to the PFCP-EP.

10

The PFCP-EP sends the Sx Delete Response for PDN2 to the cnSGW.

11

The cnSGW sends Delete Bearer Response for PDN2 to the S5-GTP-EP.

12

The S5-GTP-EP forwards the Delete Bearer Response for PDN2 to the PGW.