Enhanced Charging Service Overview
â–„ Cisco ASR 5000 Series Product Overview
The following figure illustrates how ruledefs interact with the Protocol Analyzer Stack and Action Engine to produce
charging records.
Figure 179. ECS In-line Service Processing
ECS In-Line Service
Protocol
Analyzer Stack
ruledefs
(rule-application routing)
ruledefs
(rule-application charging)
Charging Engine
block
Xmit
redirect
string, =, >, !, etc.
Call
detail
records
Incoming
packets
(directed to
ECS by CSS)
Packet
inspection
output
string, =, >, !, etc.
Packets entering the ECS subsystem must first pass through the Protocol Analyzer Stack where routing ruledefs apply to
determine which packets to inspect. Then output from this inspection is passed to the Charging Engine, where charging
ruledefs apply to perform actions on the output.
Routing Ruledefs and Packet Inspection
The following figure and the steps that follow describe the details of routing ruledef application during packet
inspection.