Dedicated Bearer Deletion Procedure Call Flow
This section describes the Dedicated Bearer Delete Procedure call flow.

Step |
Description |
---|---|
1 |
The PGW sends the S5 Delete Bearer Request with EBI list containing one or more dedicated bearer EBIs, to the GTPC-EP pod. |
2 |
The GTPC-EP pod forwards the S5 Delete Bearer Request to the SGW-SVC pod. |
3 |
The SGW-SVC pod receives the S5 Delete Bearer request and performs the following:
|
4 |
The PFCP-EP pod forwards the Sx Modification Request to the UP. |
5 |
The UP sends the Sx Modification Response to the PFCP-EP pod. |
6 |
The PFCP-EP pod forwards the Sx Modification Response to the SGW-SVC pod. |
7 |
The SGW-SVC pod receives the Sx Modification Response and triggers the S11 Delete Bearer Request to the GTPC-EP pod. |
8 |
The GTPC-EP pod forwards the S11 Delete Bearer Request to the MME. |
9 |
The MME sends the S11 Delete Bearer Response to the GTPC-EP pod. |
10 |
The GTPC-EP pod forwards the S11 Delete Bearer Response to the SGW-SVC pod. |
11 |
The SGW-SVC receives the S11 Delete Bearer Response and triggers the Sx Modification Request to the PFCP-EP pod, to remove traffic endpoints for removal of the GTPU tunnels for the requested dedicated bearers. |
12 |
The PFCP-EP pod forwards the Sx Modification Request to the UP to remove GTP tunnels for the requested dedicated bearers. |
13 |
The UP sends the Sx Modification Response to the PFCP-EP pod. |
14 |
The PFCP-EP forwards the Sx Modification Response to the SGW-SVC pod. |
15 |
The SGW-SVC receives the Sx Modification Response and performs the following:
|
16 |
The GTP-EP pod forwards the S5 Delete Bearer Response to the PGW. |