Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 17
ECS Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
153
Feature Changes
Rf Accounting Support for FAPA
Rf is supported for Flow Aware Packet Acceleration (FAPA) feature and it provides improved performance for HTTP
traffic if the traffic flow is FAPA eligible.
traffic if the traffic flow is FAPA eligible.
CSCum88705 - FDR/EDR should be supported in A-ECS
Applicable Products: GGSN, P-GW
Feature Changes
FDR/EDR Support for FAPA
FDR/EDR is supported for Flow Aware Packet Acceleration (FAPA) feature and it provides improved performance for
HTTP traffic if the traffic flow is FAPA eligible.
HTTP traffic if the traffic flow is FAPA eligible.
CSCun17417 - Discontinue support for charge-volume variants except ip,
constant
Applicable Products: P-GW
Feature Changes
Discontinuation of CLI Configuration Options in Charging Action
The other charge-volume protocol variants except IP and constant, in charging-action configuration has been removed
and would no longer be available. For example, if you have a HTTP GET request with total packet length 100 bytes, out
of which 20 bytes is the IP header, 20 bytes is the TCP header, and 60 bytes are the HTTP headers, ECSv2 provided a
mechanism to charge for total 100 bytes (IP-and-above) or just 80 bytes (TCP-and-above) or just 60 bytes (HTTP-and-
above), which of these three applied to a given packet was decided by the charge-volume protocol variant in the
charging-action CLI config. With this feature, only IP packet is being charged and the granularity has been removed.
and would no longer be available. For example, if you have a HTTP GET request with total packet length 100 bytes, out
of which 20 bytes is the IP header, 20 bytes is the TCP header, and 60 bytes are the HTTP headers, ECSv2 provided a
mechanism to charge for total 100 bytes (IP-and-above) or just 80 bytes (TCP-and-above) or just 60 bytes (HTTP-and-
above), which of these three applied to a given packet was decided by the charge-volume protocol variant in the
charging-action CLI config. With this feature, only IP packet is being charged and the granularity has been removed.
Previous Behavior: Earlier, bytes could be charged according to protocol specified in
charging-action
CLI.
New Behavior: Currently, only entire IP packet is charged and the granularity has been removed. All other charge-
volume protocol variants except IP and constant have been removed.
volume protocol variants except IP and constant have been removed.
Command Changes
charge-volume
All options in
charge-volume
command under
charging-action
have been removed except
IP
and
constant
.
charge-volume ip
The option
packet-length
has been removed from the command
charge-volume ip
under
charging-action
.