Volume Reporting on S11 Trigger Call Flow
This section describes Volume Reporting on S11 Trigger call flow.

Step |
Description |
---|---|
1 |
Established a PDN session with the default and dedicated bearers. The MME sends Modify Bearer Request to the GTPC-EP. |
2 |
The GTPC-EP forwards the S11 Modify Bearer Request to the SGW-service pod. |
3 |
The SGW-service pod requests the 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. |
6 |
The SGW-service pod sends the generated CDR request to the GTPP-EP. |
7 |
The SGW-service pod sends the S5 Sx Modify Bearer Request to the GTPC-EP. |
8 |
The GTPC-EP sends the Modify Bearer Request to the PGW. |
9 |
The GTPC-EP receives the Modify Bearer Response from the PGW with the cause as Request-Accepted. |
10 |
The GTPC-EP forwards the S5 Modify Bearer Response to the SGW-service pod with the cause as Request-Accepted. |
11 |
The SGW-service pod sends the S11 Modify Bearer Response to the PGW with the cause as Request-Accepted. |
12 |
The GTPC-EP sends the Modify Bearer Response to the MME with the cause as Request-Accepted. |
13 |
The GTPP-EP sends the CDR ACK to the SGW-service pod. |