URR Removal and CDR Generation on Deletion of Dedicated Bearer Call Flow
This section describes the URR Removal and CDR Generation on Deletion of Dedicated Bearer call flow.

Step |
Description |
---|---|
1 |
Established a PDN session with the default and dedicated bearer. The PGW sends the Delete Bearer Request to the GTPC-EP. |
2 |
The GTPC-EP forwards the S5 Delete Bearer Request to the SGW-service pod. |
3 |
The SGW-service pod requests a usage report query when charging enabled with QoS trigger and QoS change detected. The SGW-service pod sends the Sx Session Modification Request to the PFCP-Proto. |
4 |
The PFCP proto sends the Sx Session Modification Response to the SGW-service pod with the cause as Request-Accepted. |
5 |
The SGW-service pod triggers the CDR generation and sends CDR request to the GTPP-EP. |
6 |
The SGW-service pod sends the S5 Sx Modify Bearer Request to the GTPP-EP. |
7 |
The SGW-service pod sends the S11 Delete Bearer Request to the GTPC-EP. |
8 |
The GTPC-EP forwards the Delete Bearer Request to the MME. |
9 |
The GTPC-EP receives the Delete Barer Response from the MME with the cause as Request-Accepted. |
10 |
The GTPC-EP forwards the S11 Delete Bearer Response to the SGW-service pod with the cause as Request-Accepted. |
11 |
The SGW-service pod sends the Sx Session Modification Request to the PFCP proto. |
12 |
The SGW-service pod receives the Sx Session Modification Response from the PFCP proto with the cause as Request-Accepted. |
13 |
The SGW-service pod sends the S5 Delete Bearer Response to the GTPC-EP with the cause as Request-Accepted. |
14 |
The GTPC-EP sends the Delete Bearer Response to the PGW with the cause as Request-Accepted. |
15 |
The PFCP proto sends the CDR ACK to the SGW-service pod. |