Cisco Cisco ASR 5700
Application Detection and Control Overview
How ADC Works ▀
ADC Administration Guide, StarOS Release 18 ▄
17
How ADC Works
As part of traffic analysis, packets will be first passed through the ADC analyzers when “p2p dynamic-flow-detection”
is enabled. If it is not detected as P2P by any of the ADC analyzers, then it will follow the rule matching to find an
application analyzer.
is enabled. If it is not detected as P2P by any of the ADC analyzers, then it will follow the rule matching to find an
application analyzer.
ADC analyzers examine uplink and downlink traffic and use rules that define what packet content to take action on and
what action to take when the rule is true. The analyzers also generate usage records for the billing system. The rules are
configured/defined in the same way as ECS in-line service ruledefs and rulebases.
what action to take when the rule is true. The analyzers also generate usage records for the billing system. The rules are
configured/defined in the same way as ECS in-line service ruledefs and rulebases.
For a few specific protocols, packets will be sent to non-ADC analyzers even after marking the flow as P2P. If the flow
is marked as P2P and also analyzed by other analyzers, the statistics for display and debug purposes reflect in both
analyzers. The EDR also displays the ADC application/protocol names if configured.
is marked as P2P and also analyzed by other analyzers, the statistics for display and debug purposes reflect in both
analyzers. The EDR also displays the ADC application/protocol names if configured.
ADC also interfaces to a PCRF Diameter Gx interface to accept policy ACLs and rulebases from a PDF. ADC supports
real-time dynamic policy updates during a subscriber session. This includes modifying the subscriber's policy rules
during an active session by means of ACL name and Rulebase name.
real-time dynamic policy updates during a subscriber session. This includes modifying the subscriber's policy rules
during an active session by means of ACL name and Rulebase name.
In Gx interface, a Charging Rulebase will be treated as a group of ruledefs. A group of ruledefs enables grouping rules
into categories, so that charging systems can base the charging policy on the category. When a request contains names
of several Charging Rulebases, groups of ruledefs of the corresponding names are activated. For ADC rules to work in
the group of ruledefs, P2P detection has to be enabled in the rulebase statically.
into categories, so that charging systems can base the charging policy on the category. When a request contains names
of several Charging Rulebases, groups of ruledefs of the corresponding names are activated. For ADC rules to work in
the group of ruledefs, P2P detection has to be enabled in the rulebase statically.
Static policy is supported initially. A default subscriber profile is assumed and can be overwritten on the gateway. Per-
subscriber static policy is pulled by the gateway from the AAA service at subscriber authentication.
subscriber static policy is pulled by the gateway from the AAA service at subscriber authentication.
The following figure illustrates how packets travel through the system using ADC. The packets are investigated and
then handled appropriately using ruledefs for charging.
then handled appropriately using ruledefs for charging.
Figure 1.
Overview of Packet Processing in ECSv2
Limitations
This section lists the limitations for the ADC protocols that support audio and video sub-classification.