PGW-requested Disconnection Call Flow
This section describes the PGW-requested disconnection call flow.

Step |
Description |
---|---|
1 |
The PGW sends the Delete Bearer Request to the S11-GTP-EP for other PDN disconnection. |
2 |
The GTP-EP decodes the received UDP message and converts the message into the gRPC message. Based on the TEID value, the gRPC message is forwarded to the SGW-service pod which can handle the UE session. |
3 |
The SGW-service pod finds the subscriber context information as per the local ingress TEID. The SGW-service pod validates the Delete Bearer Request content. The SGW-service pod sends the Sx Modify Request to the PFCP-EP with apply action as DROP to drop the uplink or downlink packets at the SGW-U. |
4 |
The PFCP-EP sends the Sx Modify Response to the SGW-service pod. |
5 |
The SGW-service pod forwards the Delete Bearer Request to the S5-SGW-EGRESS-GTP-EP. |
6 |
The S5-SGW-EGRESS-GTP-EP forwards the Delete Bearer Request to the PGW through the UDP proxy. |
7 |
The PGW sends the Delete Bearer Response to the S5-SGW-EGRESS-GTP-EP. |
8 |
The S5-SGW-EGRESS-GTP-EP forwards the Delete Bearer Response to the SGW-service pod. |
9 |
The SGW-service pod validates the Delete Bearer Response, and sends the Sx Delete Request to the PFCP-EP. |
10 |
The SGW-service pod receives the Sx Delete Bearer Response from the PFCP-EP. |
11 |
For the last PDN, the SGW-service pod sends the NodeMgrResourceManager Request for the ID release to the NodeManager. |
12 |
The Node Manager releasees the ID and sends the acknowledgment to the SGW-service pod. |
13 |
The SGW-service pod sends the Delete Bearer Response to the S11-GTP-EP. |
14 |
The S11-GTP-EP forwards the Delete Bearer Response to the MME. |
15 |
The SGW-service pod
|