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.

Usage Report with SoT – CCR-I Message Not Sent During Initial Attach or Bearer Creation
Usage Report with SoT – CCR-I Message Not Sent During Initial Attach or Bearer Creation Call Flow Description

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.

Note
  • The SMF receives the details to add PCC rules for the default or dedicated bearer from PCRF.

  • If you have configured the send charging-initial traffic-start value, then the PCRF doesn't send the Gy Credit Control Request-Initial (CCR-I) message to SMF.

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.

Note

In case of traffic detection at CnPGW-U, the CnPGW-U prepares the usage report with the SoT.

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.