DBC Success Handling Call Flow

This section describes the DBC Success Handling call flow.

DBC Success Handling Call Flow
DBC Success Handling Call Flow Description

Step

Description

1

The MME sends a Delete Bearer Command to the S11-UDP-Proxy.

2

The S11-UDP-Proxy forwards the Delete Bearer Command to the S11-GTP-EP.

3

The S11-UDP-Proxy sends the ASYNC Delete Bearer Command to the SGW-SVC pod.

4

The SGW-SVC pod sends the BGIPC Delete Bearer Command to the S5-GTP-EP. Save DBC_info in the PDN for response.

5

The EP pod performs the retransmission and reports a failure if there is no response. The pod sends the Delete Bearer Command Failure Indication (DBCFI) to the SGW-SVC pod.

The S5-GTP-EP sends the Delete Bearer Command to the S5-UDP-Proxy.

6

The S5-UDP-Proxy send the Delete Bearer Command to the PGW.

7

The PGW sends the Delete Bearer Request to the S5-UDP-Proxy pod.

8

The S5-UDP-Proxy pod forwards the Delete Bearer Request to the S5-GTP-EP.

9

The S5-GTP-EP pod sends the DBCFI (with Request as ACCEPTED) to the SGW-SVC pod to end the transaction. The SGW-SVC pod ends the transaction and consumes this DBCFI.

The post internal transaction sends the GRPCE_DBReq to SGW-SVC pod.

10

After the ET1 transaction is completed, the S5-GTP-EP starts.

11

The S5-GTP-EP pod sends the GRPC-DBRequest to the SGW-SVC.

12

The SGW-SVC pod processes the Delete Bearer Request and used saved DBC_Info to send the Updated Bearer Request to the MME.

13

The S11-GTP-EP pod sends the Delete Bearer Request to the S11-UDP-Proxy pod.

14

The S11-UDP-Proxy forwards the Delete Bearer Request to the MME.

15

The MME sends the Delete Bearer Response to the S11-UDP-Proxy pod.

16

The S11-UDP-Proxy processes the Delete Bearer Response to the SGW-SVC.

17

The SGW-SVC forwards the Delete Bearer Response to the S5-GTP-EP.

18

The S5-GTP-EP pod sends the Delete Bearer Response to the S5-UDP-Proxy.

19

The S5-UDP-Proxy sends the Delete Bearer Response to the PGW.