Feature Description

The following capabilities are added to the SMF as a part of this feature:

  • The SMF is capable to receive Quota Validity time from Gy interface in CCAI and CCAU messages. After processing, SMF sends this information towards UPF in the following messages PFCP_SESSION_ESTABLISHMENT_REQUEST and PFCP_SESSION_MODIFICATION_REQUEST with trigger as “timqu”.

    If PFCP_SESSION_REPORT_REQUEST message receives usage report with “timqu” trigger, The SMF sends CCRU message with USU with time quota information and adds TGPPReportingReason as “VALIDITY_TIME”.

  • The SMF is capable to receive Quota Holding time from Gy interface in CCAI and CCAU messages. After processing SMF sends this information towads UPF in the following messages PFCP_SESSION_ESTABLISHMENT_REQUEST and PFCP_SESSION_MODIFICATION_REQUEST with trigger as “quhti”.

    PFCP_SESSION_ESTABLISHMENT_REQUEST PFCP_SESSION_MODIFICATION_REQUEST

    If PFCP_SESSION_REPORT_REQUEST message receives usage report with “quhti” trigger. The SMF sends CCRU message with USU with time quota information and adds TGPPReportingReason as “QHT”.

Quota-Validity-Time

This is an optional AVP and may only occur in a CCA command. It is contained in the Multiple-Services-Credit-Control AVP. This field defines the time in order to limit the validity of the granted quota for a given category instance.

The following requirements are supported by SMF:

  • Validity-Time” received in Gy CCAI/CCAU messages establishment or modification

  • The SMF process received validity time, if it is eligible to send the information towards UPF

    SMF Sends validity time as “tm_quta” in PFCP_IE_TIME_QUOTA and set the trigger as timqu with in PFCP_IE_REPORTING_TRIGGERS in: PFCP_SESSION_ESTABLISHMENT_REQUEST and PFCP_SESSION_MODIFICATION_REQUEST

  • SMF can receive PFCP_IE_USAGE_REPORT_REP_REQ with timqu as trigger and duration in “durton_msrt” in PFCP_SESSION_REPORT_REQUEST message

  • SMF process usage report sends received “durton_msrt” as “CC-Time” inside Used-Service-Unit and 3GPP-Reporting-Reason added as VALIDITY_TIME with in Multiple-Services-Credit-Control AVP in CCRU.

  • If SMF received “volume_msrmt” along with “durton_msrt”, then “CC-Total-Octets“, “CC-Input-Octets“, “CC-Output-Octets“ filled along with “CC-Time” inside Used-Service-Unit and 3GPP-Reporting-Reason added as VALIDITY_TIME with in Multiple-Services-Credit-Control AVP in CCRU.

  • If cnPGW not “Validity-Time” receives in Gy CCAI/CCAU messages then it read from charging profile configuration and apply it.

Quota-Holding-Time

This is an optional AVP and may only occur in a CCA command. It is contained in the Multiple-Services-Credit-Control AVP. It applies equally to the granted time quota and to the granted volume quota.

The following requirements are supported by the SMF:

  • 3GPP-Quota-Holding-Time” received in Gy CCAI/CCAU messages establishment or modification

  • SMF Sends holding time as “quta_hldg_tm” in PFCP_IE_QUOTA_HOLDING_TIME and set the trigger as quhti with in PFCP_IE_REPORTING_TRIGGERS in PFCP_SESSION_ESTABLISHMENT_REQUEST and PFCP_SESSION_MODIFICATION_REQUEST

  • SMF can receive PFCP_IE_USAGE_REPORT_REP_REQ with quhti as trigger

  • SMF process usage report 3GPP-Reporting-Reason added as QHT with in Multiple-Services-Credit-Control AVP in CCRU.

Volume-Quota-Threshold

This is an optional AVP and may only occur in a CCA command. It is contained in the Multiple-Services-Credit-Control AVP. If cnPGW and not the “3GPP-Volume-Quota-Threshold” is received in the Gy CCAI/CCAU messages, then it reads the information from the charging profile configuration and applies it.