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
154
(Fastpath) with limited supported features. By limiting the supported features, Fastpath eliminates the overhead of
packets being subjected to the large number of feature-based conditional checks in ECS.
packets being subjected to the large number of feature-based conditional checks in ECS.
Fastpath does not replace the existing data path, and works in parallel with the existing ECS data path. The Fastpath
feature is part of the Transactional Rule Matching (TRM) feature and requires TRM to be enabled.
feature is part of the Transactional Rule Matching (TRM) feature and requires TRM to be enabled.
For information on ECS features supported by fastpath, refer the Enhanced Charging Services Administration Guide.
Handling/Prioritizing from multiple flow actions for same packet
Flow Actions-related Changes
In this release, the following flow action changes are introduced:
Multiple flow actions from more than one charging action can be taken on a single packet.
The flow actions Flow-Kill, Redirection and content-Insertion will interwork with Next Hop and VLAN ID
configurations.
Flow actions are divided into the following broad categories:
Buffer
Session kill
Injections actions
Modification actions
Common actions
If a flow action from a particular category cannot be taken on the packet under consideration, then the next flow
action from the same category (if set during rule matching) would be considered for application.
Only one Injection action would be taken on the packet and it would interwork with any or all of the common
actions.
All modification actions will interwork with each other as well as with Common actions.
Post-processing—Charging hierarchy no longer exists as far as the flow actions are concerned except in those
cases concerning the post-processing actions set from the OCS and that in the limit-reached quota state.
All flow actions can now fall in any of the category (Charging/ Post-processing). That is, no barrier exists in
configuring a particular flow action as a charging or post-processing action.
The charging action/sub session level statistics will get incremented only if the action is taken.
The injection actions taken on WAP packets will also support the Next Hop and VLAN ID configurations for
injected packets.
The ICAP connection failure actions will not get any special prioritization. They obey the prioritization rules
which are laid down.
In case when the same flow action is configured inside a normal charging action as well as inside the post-
processing charging action, the post-processing flow action will take priority.
Post-processing Rule Matching-related Changes
The following post-processing rule matching changes are introduced:
Post-processing rule matching occurs when post-processing rules are configured and/or the FUI rules are
enabled. Post-processing rule matching is ignored only if the packet is buffered by DCCA or ACF.