In compliance with 3GPP TS 29.244 V15.0.0, ADC over Gx feature supports the following functionalities in CUPS environment:

• Application START/STOP event reporting at the instance level, over the Sx Interface, as part of the session usage report request.

• Application START/STOP is sent for Group of Ruledef when a flow matches the Group of Ruledef.

• Supports AND logic for rulelines while matching ADC ruledefs.

• Supports new Information Elements (IEs) for Packet Forwarding Control Protocol (PFCP) messages that are used for ADC application detection notifications.

Important

In this release, the ADC Over Gx feature is applicable for ADC L3/L4 rules.

Important

For supplemental information about ADC Over Gx feature in non-CUPS environment, refer to: ADC Support over Gx section in the Application Detection and Control Overview chapter of the ADC Administration Guide. Support ADC Rules over Gx Interface section in the Gx Interface Support chapter of the P-GW Administration Guide.

For ADC over Gx feature in the CUPS environment, support is added for the following:

• The Application ID/TDF Application Identifier is part of the PDI of PDR, either in Sx Establishment Request or Sx Session Modify Request.

• Handling of the ADC rule match on U-Plane.

• To generate a session usage report request when the Application START/STOP event occurs on U-Plane.

• New IEs as part of the Usage report request:

  • Application ID

  • Application Instance ID

  • Flow Information

• Monitor Protocol to decode the new IEs.

• To handle the usage report request that is received, and trigger the CCR-U to PCRF on C-Plane.

The functionality of ADC Over Gx feature consists of the following components, and each are described in this section.

ADC Rule Match

The ADC rule match is invoked after the traditional rule match. After the L3/L4 filters are being matched, the rule match engine checks for any ADC rules being configured on the bearer. If ADC rules are present, then the ADC rule match occurs.

If the bearer has ADC rule which does not have the L3/L4 filters, and it’s a non-GBR bearer, then the ADC rule match is done across all the non-GBR bearers. The charging is done against the charging and action policy of the rule match.

For ADC dynamic rules, if the L3/L4 filter matches but the ADC rule match fails, then the rule is considered as not matched.

Session Usage Report Request Generation

Once the ADC rule matches on the U-Plane and an application has been detected, the U-Plane triggers the Application START notification over the Sx interface as a session usage report:

• With the measurement method set to Event

• Usage Report Trigger set to “Start of Traffic”

• The Application Detection Info, such as Application ID, Application Instance ID, and Application Flow Information along with the direction.

When the application teardown gracefully, the application gets timed out, or the rule match changes, the application STOP is triggered from U-Plane to C-Plane as a session usage report:

• With the measurement method set to “Event”

• Usage Report Trigger set to “Stop of Traffic”

• Application ID

• Application Instance ID

The application STOP is not triggered when:

• “mute” is enabled.

• The call is going down.

• The rule/PDR is deleted.

• The bearer/tunnel deletion occurs.

Handling Session Usage Report on C-Plane

After receiving the session usage report on C-Plane, it detects the event and CCR-U is triggered toward PCRF, along with the required attributes to be sent.

The CLI commands available for ADC Over Gx in non-CUPS environment can be used in CUPS environment.

Following are the sample configurations to:

• Enable the feature under Policy Control Configuration mode:

  diameter encode-supported-features adc-rules

• Configure ADC predefined rule under ACS Rulebase Configuration mode:

  action priority 55 dynamic-only adc ruledef qci5 charging-action charge-action-qci5
  action priority 56 dynamic-only adc mute group-of-ruledefs qci5_gor charging-action charge-action-qci5

Important

Application START/STOP will not be sent to PCRF if the Application START/STOP event trigger is not registered while enabling the ADC Over Gx feature.

Important

For additional information about the CLI commands, refer the Command Line Interface Reference.

This section describes the CLI commands available to monitor and/or troubleshoot the feature.