Usage Report with SoT – CCR-I Message Not Sent During Initial Attach or Bearer Creation
This section provides details about the usage report with SoT when the CCR-I message is not sent during the initial attach or bearer creation.

Step |
Description |
||
---|---|---|---|
1 |
Both the PCRF and SMF send and receive the Gx Credit Control Request (CCR) and Credit Control Answer (CCA) messages to each other.
|
||
2 and 3 |
The PFCP and GTPP message exchange happens. The SMF sends the PCFP messages to CnPGW-U and GTPP messages to S-GW.
|
||
4 |
The CnPGW-U F sends the N4 Session Report Request to SMF with the SoT details. The SMF sends the N4 Session Report Response to CnPGW-U. |
||
5 |
The SMF sends the CCR-I message with quota request for each bearer in different Gy Diameter sessions to OCS. These sessions can have one or multiple MSCCs with Requested-Service-Unit (RSU) AVPs, which is one for each Rating Group and service ID. |
||
6 |
The OCS sends the CCA-I message from the corresponding Gy Diameter session to SMF. The Diameter session includes details, such as quota and triggers for each Rating Group and Service ID. |
||
7 |
The SMF sends the N4 Session Modification Request to CnPGW-U. This request includes details on the required URRs with quota. |
||
8 |
The CnPGW-U sends the N4 Session Modification Response to SMF. |