Volume Reporting on S5 Trigger Call Flow
This section describes the Volume Reporting on S5 Trigger call flow.
|
Step |
Description |
|---|---|
|
1 |
Established a PDN session with the default and dedicated bearers. The PGW sends the Update Bearer Request to the GTPC-EP. |
|
2 |
The GTPC-EP forwards S5 Update Bearer Request to the SGW-service pod. |
|
3 |
The SGW sends the Update Bearer request S11 to the GTPC-EP. |
|
4 |
The GTPC-EP forwards the Update Bearer request to the MME. |
|
5 |
The MME sends the Update Bearer Response to the GTPC-EP with the cause as Request-Accepted. |
|
6 |
The GTPC-EP sends the S11 Update Bearer Response to the SGW-service pod with the cause as Request-Accepted. |
|
7 |
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. |
|
8 |
The SGW-service pod receives the Sx Session Modification Response from the PFCP proto with the cause as Request-Accepted. |
|
9 |
The SGW-service pod triggers the CDR generation. |
|
10 |
The SGW-service pod sends the CDR report to the GTPP-EP. |
|
11 |
The GTPC-EP receives the Update Bearer response from the SGW-service pod with the cause as Request-Accepted. |
|
12 |
The PGW forwards the S5 the Update Bearer response from the GTPC-EP with the cause as Request-Accepted. |
|
13 |
The GTPP-EP sends the CDR ACK to the SGW-service pod. |