Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 17
ECS Enhancements for 17.3 ▀
Release Change Reference, StarOS Release 17 ▄
125
[ no ] attribute { sn-rating-group | sn-service-id | sn-charging-action }
priority priority
priority priority
end
Performance Indicator Changes
show active-charging edr-format all
With this feature enabled, the output of
show active-charging edr-format all
command will display these
newly configured EDR attributes.
CSCur91211 - Quota not requested in CCR-I when preemptively in CA set
(dynamic-only)
Applicable Products: GGSN
Feature Changes
Processing of Predefined Rules with Default Bearer QoS Change
Previous Behavior: In the case of default bearer QoS change, the predefined rules were buffered for processing later.
As a result, the CCR-I message sent over Gy does not contain the rating-group of predefined rule.
As a result, the CCR-I message sent over Gy does not contain the rating-group of predefined rule.
New Behavior: Predefined rules on default bearer will now be processed along with the default bearer QoS change.
Customer Impact: Customers will be able to see CCR-I with predefined rule charging-action rating group if
configured.
configured.
CSCus80666 - Dis-engage TRM when a flow moves from one bearer to another
Applicable Products: GGSN, P-GW, PDSN
Feature Changes
TRM Flows
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. With this enhancement, TRM/Accel path gets
disengaged in case of any bearer movement for a particular flow.
rule matching on a transaction once the transaction is fully classified. With this enhancement, TRM/Accel path gets
disengaged in case of any bearer movement for a particular flow.
Previous Behavior: When TRM/Accel path gets enabled for a flow on a particular bearer and if flow moves from one
bearer to another, TRM would not get disengaged. As a result, packets were being matched to rules present on the
previous bearer, and not on the current bearer.
bearer to another, TRM would not get disengaged. As a result, packets were being matched to rules present on the
previous bearer, and not on the current bearer.
New Behavior: When TRM/Accel path gets enabled for a flow on a particular bearer and if flow moves from one
bearer to another, TRM will get disengaged. Packets will now be matched to rules present on the new bearer.
bearer to another, TRM will get disengaged. Packets will now be matched to rules present on the new bearer.