Cisco Cisco Packet Data Gateway (PDG) Notas De La Versión
ECS Changes in Release 15.0
ECS Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
157
In earlier releases, the functionality of the
monitor protocol
and
monitor subscriber
commands was limited to
displaying only the packet information that goes in and comes out of ECS. With this release, these commands support
tracing rule matches per packet for single subscribers. This information can be used for debugging, and enables better
utilization of system resources.
tracing rule matches per packet for single subscribers. This information can be used for debugging, and enables better
utilization of system resources.
For normal static, predefined or dynamic rule matching, if there is no delay charging or if the data is not segmented
(HTTP segmented GET request), rule match is logged as soon as the rule match condition is met.
(HTTP segmented GET request), rule match is logged as soon as the rule match condition is met.
For HTTP packets with partial header, the packet which contains the end of the header will be rule matched and the
previous packet with the partial header will be matched to the rule that the last packet has been matched to.
previous packet with the partial header will be matched to the rule that the last packet has been matched to.
ECSv2-DCCA Enhancements
DCCA Charging of HTTP/WAP Concatenated Packet Buffered at DCCA
Previous Behavior: In earlier releases, when an HTTP packet (or WAP) containing multiple requests/responses gets
buffered at DCCA waiting for a response from OCS regarding the quota for any of these requests, the requests that
follow are not forwarded for rule matching. Hence the correct charging action is not applied for these. Additionally,
when the quota response is received, the request that caused buffering gets charged against the correct Content ID, while
requests that follow are charged against the Content ID of the next packet.
buffered at DCCA waiting for a response from OCS regarding the quota for any of these requests, the requests that
follow are not forwarded for rule matching. Hence the correct charging action is not applied for these. Additionally,
when the quota response is received, the request that caused buffering gets charged against the correct Content ID, while
requests that follow are charged against the Content ID of the next packet.
New Behavior: With this release, correct rule matching and charging action is taken for subsequent request/response
(WAP / HTTP) in a concatenated packet, when the packet is buffered at DCCA waiting for quota response for the
earlier request/response. Additionally, all the requests/responses in the buffered concatenated packet are charged for the
correct byte count against the correct Content IDs.
(WAP / HTTP) in a concatenated packet, when the packet is buffered at DCCA waiting for quota response for the
earlier request/response. Additionally, all the requests/responses in the buffered concatenated packet are charged for the
correct byte count against the correct Content IDs.
Flow Action Prioritization of Concatenated Packet
Previous Behavior: In earlier releases, when a concatenated (HTTP/WAP) packet is being processed, rule matching
and charging occurs per request/response, and the corresponding flow-action is taken on the whole packet per
request/response immediately.
and charging occurs per request/response, and the corresponding flow-action is taken on the whole packet per
request/response immediately.
New Behavior: With this release, when a concatenated (HTTP/WAP) packet is processed, rule matching and charging
occurs per request/response. However, the corresponding flow-action will not be taken immediately. The flow action
prioritization module marks the flow actions of all the requests/responses and when the whole packet gets processed, a
prioritized flow action (from the ones that are marked) will be taken on the whole packet.
occurs per request/response. However, the corresponding flow-action will not be taken immediately. The flow action
prioritization module marks the flow actions of all the requests/responses and when the whole packet gets processed, a
prioritized flow action (from the ones that are marked) will be taken on the whole packet.
Enhancements to Static, Dynamic, and Predef Rules
The static rule, dynamic rule, and charging action (billing policy) mapped to a packet after a rule match can deactivate
when the packet is buffered at one of the deferal paths, waiting for a service response (For example DCCA buffering,
ICAP buffering etc). After the response is received and the packet gets post processed, it has the dangling references to
deactivated objects. Also if they are dereferenced somewhere, it results in a segmentation fault.
when the packet is buffered at one of the deferal paths, waiting for a service response (For example DCCA buffering,
ICAP buffering etc). After the response is received and the packet gets post processed, it has the dangling references to
deactivated objects. Also if they are dereferenced somewhere, it results in a segmentation fault.
Dynamic Rule (Defined and Pushed by PCRF over Gx)
Previous Behavior: Matched dynamic-rule/billing policy of the DCCA buffered packet was not validated after a quota
response is received. In cases where the dynamic rule gets deleted before the quota response is received, the packet was
being sent to charging and post processing with reference to a non-existent dynamic rule/billing policy. This might lead
to a system crash.
response is received. In cases where the dynamic rule gets deleted before the quota response is received, the packet was
being sent to charging and post processing with reference to a non-existent dynamic rule/billing policy. This might lead
to a system crash.
New Behavior: On dynamic rule deletion, the references to the dynamic rule/ billing policy mapped to the packet after
rule match are cleared for the DCCA buffered packets. After the quota response is received, such packets will not be
sent for charging or post processing, and will be dropped.
rule match are cleared for the DCCA buffered packets. After the quota response is received, such packets will not be
sent for charging or post processing, and will be dropped.