How it Works

The SMF processes the Tariff-Time-Change AVP in Granted-Service-Unit (GSU) level from Gy interface in CCAI and CCAU messages. The SMF includes the Tariff-Change-Usage AVP inside Used-Service-Unit (USU) in CCRU and CCRT messages when the usage report is received from UPF.

Following scenarios are supported:

  • Tariff-Time-Change with Quota-Holding-Time Expired Trigger

  • Tariff-Time-Change with Validity-Time Expired Trigger

  • Tariff-Time-Change with Volume/Time-Quota Exhausted Trigger

  • Tariff-Time-Change with Volume/Time-Quota-Threshold Trigger

  • Tariff-Time-Change with Immediate Reporting Trigger

  • Tariff-Time-Change with Terminate Reporting Trigger

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

  • The OCS provides "Tariff-Time-Change" AVP in CCAI/CCAU messages. After processing, SMF sends this information towards the UPF in PFCP Session Establishment Request and PFCP Session Modification Request using PFCP_IE_MONITORING_TIME IE.

  • The SMF receives two usage reports for each URR:

    • one with “Usage Report Trigger” as 'MONIT' and “ PFCP_IE_USAGE_INFORMATION” as ‘bef’ with "PFCP_IE_VOLUME_MEASUREMENT" and "PFCP_IE_DURATION_MEASUREMENT".

    • other usage report with “Usage Report Trigger” as 'TIMQU' and “ PFCP_IE_USAGE_INFORMATION” as ‘aft’ with "PFCP_IE_VOLUME_MEASUREMENT" and "PFCP_IE_DURATION_MEASUREMENT".

  • The SMF uses different USU to forward both the usage reports within MSCC towards OCS in CCRU/CCRT messages.

    .

    • first usage report, one with "MONIT" trigger is forwarded in USU1 with "Tariff-Change-Usage: UNIT_BEFORE_TARIFF_CHANGE" and

    • second usage report, one with "TIMQU" tigger is forwarded in USU2 with "Tariff-Change-Usage: UNIT_AFTER_TARIFF_CHANGE ".