Cisco Cisco ASR 5700
Application Detection and Control Overview
ADC Overview ▀
ADC Administration Guide, StarOS Release 18 ▄
15
Rynga
Skype
Smartvoip
Talkatone
Tango
Viber
Voipdiscount
Vopium
Vtok
Yahoo
For more information on the A-ECS feature, refer to the ECS Administration Guide.
ADC Support over Gx
The ADC Rule feature will support detection of application level flows as described in Release-11 of 3GPP standard.
ADC Rules are certain extensions to dynamic and predefined PCC Rules in order to support specification, detection and
reporting of an application flow. These rules are installed (modified/removed) by PCRF via CCA-I/CCA-U/RAR
events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing attributes of dynamic and
predefined rules will be applicable.
ADC Rules are certain extensions to dynamic and predefined PCC Rules in order to support specification, detection and
reporting of an application flow. These rules are installed (modified/removed) by PCRF via CCA-I/CCA-U/RAR
events. ADC rules can be either dynamic PCC or predefined PCC rules, and the existing attributes of dynamic and
predefined rules will be applicable.
Dynamic PCC rule contains either traffic flow filters or Application ID. When Application ID is present, the rule is
treated as ADC Rule. Application ID is the name of the ruledef which is pre-defined in the boxer configuration. This
ruledef contains application filters that define the application supported by P2P protocols.
treated as ADC Rule. Application ID is the name of the ruledef which is pre-defined in the boxer configuration. This
ruledef contains application filters that define the application supported by P2P protocols.
PCEF will process and install ADC rules that are received from PCRF interface, and will detect the specified
application(s) and report detection of application traffic to the PCRF. Reporting of application traffic are controlled by
PCRF and generates Application Start/Stop events along with the Application ID. Application mute status can be
enabled or disabled on both dynamic and predefined ADC rules. When mute is disabled, Application Start/Stop event
trigger will be generated by PCEF for that specific Application ID. Mute status for dynamic rule can be enabled or
disabled by PCRF, in case of pre-defined rule it is configure either on boxer configuration or CLI.
application(s) and report detection of application traffic to the PCRF. Reporting of application traffic are controlled by
PCRF and generates Application Start/Stop events along with the Application ID. Application mute status can be
enabled or disabled on both dynamic and predefined ADC rules. When mute is disabled, Application Start/Stop event
trigger will be generated by PCEF for that specific Application ID. Mute status for dynamic rule can be enabled or
disabled by PCRF, in case of pre-defined rule it is configure either on boxer configuration or CLI.
Important:
ADC Rule support is a licensed-controlled feature. Contact your Cisco account representative for
detailed information on specific licensing requirements.
When the license is not enabled, P2P continues to function as per its original behavior, that is, it monitors the traffic at
the entire rulebase level. When the license is enabled, the P2P behavior changes such as to monitor traffic at per
subscriber level.
the entire rulebase level. When the license is enabled, the P2P behavior changes such as to monitor traffic at per
subscriber level.
The following types of ADC ruledefs can be configured.
Limitations
The limitations for the ADC over Gx feature are:
ADC does not support group of ruledefs.
Registration of the duplicate application IDs are not supported.