Cisco Cisco Packet Data Interworking Function (PDIF) Notas De La Versión
ECS Changes in Release 15.0
ECS Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
159
Previous Behavior: In earlier releases, the HTTP analyzer parses all the fields in the HTTP header even when any rule
matching fields or ECS feature does not use the value parsed from the HTTP header, thus impacting the Deep Packet
Inspection (DPI) performance.
matching fields or ECS feature does not use the value parsed from the HTTP header, thus impacting the Deep Packet
Inspection (DPI) performance.
New Behavior: With this release, selective parsing of the HTTP header fields is introduced based on the configured
features and rule matching fields using the HTTP header fields. The HTTP header field is parsed only during the
following conditions:
features and rule matching fields using the HTTP header fields. The HTTP header field is parsed only during the
following conditions:
A rulebase configuration refers to a ruledef that requires an HTTP header field for rule matching.
A charging action that uses an HTTP header field for flow action that uses an HTTP header field information.
An ECS feature defined at a rulebase level requires an HTTP header field information.
ECS Command Changes as of September 30, 2013
This section provides information on ECS command changes in release 15.0.
Important:
For more information regarding commands in this section, refer to the Command Line Interface
Reference for this release.
New ECS Commands
This section identifies new ECS commands available in release 15.0.
http referer
This command allows you to define rule expressions to match the value in the HTTP Referer request-header field. With
this release, the
this release, the
regex
keyword is added to match the HTRF fields using regular expressions.
config
active-charging service service_name
ruledef ruledef_name
http referer [ case-sensitive ] regex string
end
ip dscp
This command enables you to configure a charging ruledef with the DSCP value and match it with the DSCP value in
the incoming IP packets.
the incoming IP packets.
config
active-charging service service_name
ruledef ruledef_name
[ no ] ip dscp { != | = }IPv4_ToS | IPv6_TC_value [ mask mask_value ]