Supported Functionality and Limitations

Basic call flow with Volume-Quota mechanism is supported with the following limitations:
  • Dynamic Rules with Online Enabled is supported; both at Session-Setup and Mid-Session.

  • Predefined Rules (dynamic-only) is supported; both at Session-Setup and Mid-Session. No restriction on configuring the "preemptively request".

  • Static-rules with Online Charging are supported.

  • Ignore-service-id is supported.

  • Volume-Quota/Volume-Threshold mechanisms are supported.

  • Event-Triggers (through which the Query URR occurs), and sending of usage information to the OCS is supported.

  • The "updateURR" procedure, through the Sx/N4-Session-Modification procedure where the OCS grants a fresh Quota, is supported.

  • Pending-Traffic-Treatment (PTT) Drop/Pass is supported with following limitations:

    • The scenarios currently supported are no-quota and quota-exhausted.

    • The trigger or re-authorization scenarios are not supported.

    • The PTT action (Forward/Drop) is considered after the quota-get is exhausted.

  • Wall-Clock time-quota mechanism is supported.

  • Other Time Quota Mechanisms (Discrete Time Period and Continuous-Time-Period) are not supported.

  • Final-Unit-Indication Terminate mechanism is supported.

  • FUI-Restrict is not supported.

  • Server-Unreachable (SU) mechanism is now supported with minor change in behavior compared to non- 5G UPF P-GW.

    • When an URR needs quota at UPF, the usage-report is generated to SMF and until the SMF responds with the linked SU_URR, the packets matching this URR are treated with Pending-Traffic-Treatment configuration.

    • When the SU Time Quota is used and it's reported to SMF for the Quota Exhaust, and if the session goes into Server-Unreachable state again, the time elapsed from the last Usage-Report is accounted in the usage.

  • Pending-Traffic-Treatment Buffer mechanism is not supported.

  • Quota-Hold-Time is supported.

  • Quota-Consumption-Time mechanism is not supported.

  • Quota-Validity-Time is supported.

  • Configuring different "rating-group" value other than the "content-id" is supported.

    • The RG 0 is not supported.

  • Trigger to PCF for the Out-of-Credit, Reallocation-of-Credit events are not qualified.

    Important

    Event-trigger Out-of-Credit toward PCF is validated with a limitation of having only one time Grant-Quota (Keeping Total Volume and Granted Volume at same value).

  • Service-Specific-Units are not supported.

  • Tariff-Time change is supported as per 3GPP specification.

  • FUI-Redirect is supported with following limitations:

    • Redirection for HTTPs is not supported.

    • The FUI-Redirect with Filter-IDs/Filter-Rules are not supported.

    • The WSP Protocol is not supported.

    • The redirect-require-user-agent CLI command is not supported; the redirection continues to work even if the user-agent is not present.

    • Appending the original URL is not supported.

    • Token-based mechanism, to come out of Redirection, is not supported. To end the redirection in 5G UPF, OCS sends Redirect Validity-Time or RAR.

    • FUI-Redirection is supported only for the URL, similar to the behavior in non-5G UPF architecture.

    • Check pointing of FUI Redirection URL is not supported.