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
156
When the UE is connected to eHRPD, the PCO value of 0 is sent except for Self Activation. When the UE
connection returns to P-GW, the last known PCO is sent to the UE and becomes active.
Regular Expression Support for HTTP Referer Field
With this release, regular expressions can be configured for the HTTP Referer (HTRF) field in ruledefs.
Transactional Rule Matching Feature
The Transactional Rule Matching (TRM) feature enables the Enhanced Charging Service (ECS) to bypass per-packet
rule matching on a transaction once the transaction is fully classified. This enables ECS to better utilize CPU resources
and accomodate additional throughput for the system, thus improving the overall performance.
rule matching on a transaction once the transaction is fully classified. This enables ECS to better utilize CPU resources
and accomodate additional throughput for the system, thus improving the overall performance.
A transaction for TRM can be defined as the entire UDP flow, the ACK of the 3-way handshake to the FIN/RST of a
TCP flow, or the HTTP request to the next HTTP request, or HTTP request to the FIN/RST for the final request of the
flow. The TRM feature can perform rule matching on IP L4 rules (UDP, TCP), HTTP, and HTTPS.
TCP flow, or the HTTP request to the next HTTP request, or HTTP request to the FIN/RST for the final request of the
flow. The TRM feature can perform rule matching on IP L4 rules (UDP, TCP), HTTP, and HTTPS.
Limitations and Dependencies:
TRM is supported only on the ASR5500 platform.
TRM is limited to flows with no protocol routing rules with the exception of HTTP and HTTPS flows. All other
flows are not supported and TRM does not have any impact on other flows.
When TRM is enabled, the following functionalities are affected:
Per direction rule matching.
TCP state rules for the duration of the TRM transaction.
Configuring delay charging when the TRM feature is enabled impacts only packets outside transaction
boundaries. All packets within the transaction boundary will be applied to the application (i.e. HTTP).
Once a flow is classified to a ruledef (first packet in flow for UDP, or the first data packet after the 3-way
handshake for a TCP flow), TRM will attempt to use that matched rule for the duration of the transaction. This
might result in the ruledefs such as those with mid-transaction TCP states or packet direction to be ignored for
the flow.
might result in the ruledefs such as those with mid-transaction TCP states or packet direction to be ignored for
the flow.
Configuring TRM and P2P in the same rulebase is not supported. Any attempt in configuring TRM and P2P in
the same rulebase will result in an error message and configuration failure.
Modified ECS Features
This section identifies ECS features modified in release 15.0.
ECS Performance Optimization for IP Fragmentation
Previous Behavior: Rule matching and identification of bearer occurs only after all the fragments of an IP packet are
reassembled. The IP fragment-related data structures are maintained at a sub session level. After reassembly, if the
packet belongs to another bearer, all the fragment related information is moved to the correct bearer. This leads to
performance impact and possibilities for issues.
reassembled. The IP fragment-related data structures are maintained at a sub session level. After reassembly, if the
packet belongs to another bearer, all the fragment related information is moved to the correct bearer. This leads to
performance impact and possibilities for issues.
New Behavior: With this release, handling of IP fragment related structure has been changed to improve performance
and reduce the occurance of issues.
and reduce the occurance of issues.
ECS Ruledef Information Enhancements to Monitor Protocol and Monitor Subscriber