Enhanced Charging Service Configuration
The following type of configuration is suitable when operators want to apply differentiated charging to various
flows that are found to be tethered. In this case, traffic that requires different charging action or content ID
when it is tethered will be identified using two ruledefs, one with "flow-is-tethered = TRUE" option and
another without this option. This configuration provides finer granularity of control but results in higher
performance degradation because the rule matching tree size increases.
billing-action egcdr
exit
rulebase consumer
tethering-detection
action priority 10 ruledef tethered-traffic charging-action
premium
action priority 20 ruledef ftp-pkts charging-action standard
action priority 30 ruledef http-pkts charging-action standard
action priority 40 ruledef tcp-pkts charging-action standard
action priority 50 ruledef ip-pkts charging-action standard
route priority 80 ruledef http-port analyzer http
exit
rulebase default
end
configure
active-charging service ecs_service
tethering-database
ruledef ftp-pkts
ftp any-match = TRUE
exit
ruledef ftp-pkts-tethered
ftp any-match = TRUE
tethering-detection flow-tethered
exit
ruledef http-pkts
http any-match = TRUE
Cisco ASR 5x00 Enhanced Charging Services Administration Guide ▄
Configuring Enhanced Features ▀
111