Cisco Cisco Packet Data Gateway (PDG) Manual De Manutenção
New Feature Summary
Generally Available 06-30-2010
1-14
ECS Features in Release 8.0
This section provides information for new features in the Enhanced Charging Service in
Release 8.0.
Release 8.0.
Group of Ruledefs Configuration Mode
In support for grouped rule categories, a Group of Ruledefs Configuration Mode has been
included within the Active Charging Service Mode. This enables grouping rules into
categories, so that charging systems can base the charging policy on the category. A group
of ruledefs may contain optimizable ruledefs. If all the ruledefs in a group of ruledefs can be
optimized, and if the group is included in a rulebase that has optimization turned on, then
the group will be optimized.
included within the Active Charging Service Mode. This enables grouping rules into
categories, so that charging systems can base the charging policy on the category. A group
of ruledefs may contain optimizable ruledefs. If all the ruledefs in a group of ruledefs can be
optimized, and if the group is included in a rulebase that has optimization turned on, then
the group will be optimized.
IP Readdressing
Readdressing of packets based on the destination IP address of the packets is now
supported. This enables redirecting unknown gateway traffic to known/trusted gateways.
supported. This enables redirecting unknown gateway traffic to known/trusted gateways.
The IP Readdressing is configured in the flow action defined in a charging action. IP
readdressing works for traffic that matches particular ruledef and hence the charging action.
IP readdressing is applicable to both uplink and downlink traffic. In the Active Charging
Subsystem, uplink packets are modified after packet inspection, rule matching, etc., where
the destination IP/port is determined, and replaced with the readdress IP/port just before
they are sent out. Downlink packets (containing the readdressed IP/port) are modified as
soon as they are received, before the packet inspection, where the source IP/port is replaced
with the original server IP/port number.
readdressing works for traffic that matches particular ruledef and hence the charging action.
IP readdressing is applicable to both uplink and downlink traffic. In the Active Charging
Subsystem, uplink packets are modified after packet inspection, rule matching, etc., where
the destination IP/port is determined, and replaced with the readdress IP/port just before
they are sent out. Downlink packets (containing the readdressed IP/port) are modified as
soon as they are received, before the packet inspection, where the source IP/port is replaced
with the original server IP/port number.
For one flow from an MS, if one packet is re-addressed, then all the packets in that flow will
be re-addressed to the same server. Features like DPI, rule-matching, etc. remain
unaffected. Each IP address + port combination will be defined as a ruledef.
be re-addressed to the same server. Features like DPI, rule-matching, etc. remain
unaffected. Each IP address + port combination will be defined as a ruledef.
In case of IP fragmentation, packets with successful IP reassembly will be readdressed.
However, IP fragmentation failure packets will not be re-addressed.
However, IP fragmentation failure packets will not be re-addressed.
Packet Filter Configuration Mode
In support for the Network Controlled QoS (NCQoS) feature providing control of QoS for
subscriber from network element side; i.e. GGSN, a Packet Filter Configuration Mode has
been included within the Active Charging Service mode. This mode enables configuring a
packet filter’s parameters.
subscriber from network element side; i.e. GGSN, a Packet Filter Configuration Mode has
been included within the Active Charging Service mode. This mode enables configuring a
packet filter’s parameters.
Corrected DCCA Behavior upon Receipt of
Charging-Rule-Base-Name AVP
Charging-Rule-Base-Name AVP
The “Charging-Rule-Base-Name” AVP (code: 1004) is sent in CCA messages from the Gy
server to set the rulebase. The rulebase that comes in this AVP must already be configured
in the system. In v7.0, ACSMgr checks for the rulebase, and if it is not present discards the
message, a CCR-T is not sent. In v7.1 and later, if the rulebase is not present the message is
rejected, and a CCR-T is sent with DIAMETER_BAD_ANSWER as the termination cause.
server to set the rulebase. The rulebase that comes in this AVP must already be configured
in the system. In v7.0, ACSMgr checks for the rulebase, and if it is not present discards the
message, a CCR-T is not sent. In v7.1 and later, if the rulebase is not present the message is
rejected, and a CCR-T is sent with DIAMETER_BAD_ANSWER as the termination cause.