Clear PDN Call Flow
This section describes the Clear PDN call flow.

Step |
Description |
---|---|
1 |
The OAM pod calls the CDL API with the filters. CDL sends the notification message to REST EP. |
2 |
The REST-EP converts this message to Clear Subscriber Request with a cause and sends Clear Subscriber to the SGW-Service pod. Transaction-T1 started. |
3-6 |
The SGW-Service pod sends Sx Modification Request to UPF through PFCP-EP. The SGW-Service pod receives Sx Modification Response from UPF through PFCP-EP. |
7 |
The SGW-Service pod sends the Delete Bearer Request to the S11-GTP-EP. |
8 |
The SGW-Service pod sends the Delete Session Request to the S5-SGW-EGRESS-GTP-EP. |
9 |
The S11-GTP-EP sends the Delete Bearer Request to MME. |
10-12 |
The S5-SGW-EGRESS-GTP-EP sends the Delete Session Request to PGW. The PGW sends the Delete Session Response to S5-SGW-EGRESS-GTP-EP. The S5-SGW-EGRESS-GTP-EP forwards this request to the SGW-Service pod. |
13-16 |
MME sends the Delete Bearer Response to S11-GTP-EP. S11-GTP-EP forwards to the SGW-Service pod. |
17, 18 |
PGW sends the Delete Session Response to S5-SGW-EGRESS-GTP-EP. S5-SGW-EGRESS-GTP-EP forwards this request to the SGW-Service pod. |
19-22 |
The SGW-Service pod sends the Sx Delete Request to PFCP-EP. The PFCP-EP forwards the request to UPF. UPF sends the Sx Delete Response to PFCP-EP, which it forwards it to the SGW-Service pod. |