Gy Multiple MSCC and FUI-Redirection

Revision History


Note

Revision history details are not provided for features introduced before release 21.24.


Revision Details

Release

First introduced

Pre 21.24

Feature Description

FUI Redirection is supported in the CUPS architecture. The Final-Unit-Indication AVP can be present in the CCA from the server to indicate that the given quota is the final quota from the server and the corresponding action as specified in the AVP needs to be taken.

If the Final-Unit-Indication AVP is present at MSCC level, and if the Final-Unit-Action AVP is set to TERMINATE, a CCR-Update is sent at the expiry of the allotted quota and report the usage of the category that is terminated.

In the Final-Unit-Indication AVP, if the Final-Unit-Action is REDIRECT or Redirect-Server AVP is present at command level, redirection is performed.

The redirection takes place at the end of consumption of quota of the specified category. The Gy sends a CCR-Update without any RSU or Rating-Group AVP so that the server does not give any more quotas. If the Final-Unit-Action AVP is RESTRICT_ACCESS, then according to the settings in Restriction-Filter-Rule AVP or Filter-Id AVP. Gy sends CCR-Update to the server with used quota.

With this release, the following functionalities are supported:

  • The FUI-Redirection with HTTP URL.

  • The FUI-Redirection is done for the HTTP GET request.

  • Only the following CLI: diameter redirect-validity-timer immediate , is supported

  • As per the 3GPP specification, Redirected-Traffic will also get redirected if the rule is executed from FUI-Redirect. However, provision to allow redirected-traffic to pass through is not present but the CLI behavior with respect to no diameter fui-redirected-flow allow behavior is implemented.

Limitations

  • The FUI-Redirection along with Filter-Ids/Filter-Rules are not supported.

  • Appending the Original URL is not supported.

  • Token based mechanism to exit Redirection is not supported.

  • The default option traffic-start in the CLI: diameter redirect-validity-timer , is not supported.

  • The WSP protocol is not supported in CUPS.

  • The CLI: redirect-require-user-agent , is not supported. Even if the user-agent is not configured, redirection is functional.