DBC Failure Handling Call Flow
This section describes the DBC Failure Handling call flow.

Step |
Description |
---|---|
1 |
The MME sends the Delete Bearer Command to the S11-GTP-EP pod. |
2 |
The S11-GTP-EP pod sends the ASYNC Delete Bearer Command to the SGW-SVC pod. |
3 |
The SGW-SVC pod forwards Delete Bearer Command to the PGW. Save DBC_info in PDN for response. The EP pod performs retransmission. If there is no response, the pod sends the Delete Bearer Command Failure Indication (DBCFI) to the SGW-SVC pod. |
4 |
The S5-GTP-EP sends the Delete Bearer Command to the UDP Proxy. |
5 |
The UDP Proxy forwards the Delete Bearer Command to the PGW. |
6 |
The PGW sends the Delete Bearer Command Failure to the UDP Proxy. DBCFI is received on S5 GTPC-EP pod and is forwarded to the SGW-SVC pod. |
7 |
The UDP Proxy forwards the Delete Bearer Command Failure to the S5-GTP-EP. |
8 |
The S5-GTP-EP sends the GRPC Delete Bearer Command Response to the SGW-SVC. |
9 |
The SGW-SVC pod sends the GRPC-DBCmd-Failure-Ind-Notif to the S11-GTP-EP. |
10 |
The S11-GTP-EP pod processes the DBCFI and forwards the response to MME with the saved DBC_Info. |