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
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
In 19.3 and later releases, this feature is extended to support
non-ADC based rules (ECS protocols) in addition to existing P2P protocols, and
also detection of application flows for Group of Ruledefs. The following
enhancements are supported:
support combination of P2P and non-P2P rule lines in the same ruledef.
application flows based on group of ruledefs.
START/STOP event reporting at instance level, that is, per flow basis. This was
supported per Application ID basis in previous releases.
dynamic routes to analyzers for installed ADC rules. Dynamic routes will be
supported only for these protocols - HTTP, HTTPS, FTP, RTP, RTCP and SIP.
multi-line AND logic for rulelines when configuring ADC ruledefs.
Removal of all
PCC rules will result in termination of Application Detection for that
application. In previous releases, if more than one PCC rule with same
Application ID is installed, then removal of any of the PCC rules will
terminate Application Detection for that application.
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 ASR 5500. This ruledef contains application
filters that define the application supported by P2P protocols and
In releases prior to release 19.3: 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 can be enabled or
disabled by PCRF for dynamic rules, and configured on ASR 5500 for pre-defined
In 19.3 and later releases:
When a subscriber attaches to the network, PCRF will install ADC
rule/Group of Ruledefs towards PCEF to detect Application flow. The Install ADC
rules will additionally enable default routes to HTTP, HTTPS, FTP, RTSP, RTCP
or SIP analyzer based on the rule-definition. The default routes use the
standard ports associated with the respective protocol. When a new flow comes,
the route matching happens for dynamic routes first, then static routes and
finally default routes. When a flow matches that ADC rule, an APP-START
notification is sent to PCRF with Application ID, Instance ID and flow
information. Instance ID is a unique identifier for a particular ADC flow. PCRF
then takes necessary action for the detected application. When ADC flow
terminates, an APP-STOP notification is sent to PCRF with Application ID and
The following types
of ADC ruledefs can be configured.
p2p protocol = <name>
p2p protocol-group = <name>
p2p behavioral = <name>
multiline-or all-lines is optional if rule
contains only one line.
p2p protocol = <name>
p2p traffic-type = <sub_type_name>
p2p anymatch = TRUE
p2p any-match =
TRUE is configured, only one rule containing this rule line can
be installed. This rule line must not be used with any other P2P rule line.
In 19.3 and later
releases, the ADC functionality is extended to identify applications and
distinguish bearer traffic based on TOS/DSCP. DSCP/TOS based ADC dynamic rules
over Gx will be supported for default and dedicated bearers. Bearer mapping and
rule matching will be done based on DSCP/TOS value. Filters can be created for
PCC rules based on TOS-Traffic-Class AVP under flow information.
When a subscriber
attaches to the network, PCRF will install PCC rule with TOS/DSCP filter
towards PCEF. PCEF will create a dedicated bearer and send the packet filters
to UE as well. When a new flow comes with first packet as Uplink, UE does
bearer matching based on the TOS/DSCP value, and sends flow on the correct
dedicated bearer. For downlink packet, ECS does bearer lookup and assigns
correct bearer to the flow based on the TOS/DSCP value.
ADC Event reporting
will contain flow template with outer IP 3 tuples (Source IP, Destination IP,
Port). L4-L7 rule match will also work for PMIP service.