Cisco Cisco Packet Data Gateway (PDG) Wartungshandbuch
New Feature Summary
Generally Available 06-30-2010
1-18
Number of TCP Connections for Optimized Mode
The number of TCP connections established to the Diameter server has changed:
●
In the non-optimized mode, it is a maximum of 12 PSC x 6 ACSMgrs.
●
In the optimized mode, the number of connections will be
<number of PSC>
x 7
SessMgrs.
ASR in Rel. 7 Gx Implementation Not Supported
In the Rel. 7 Gx implementation, any Abort-Session-Request (ASR) received by the
PCEF/BBERF will be treated as an unsupported command. In response, an
Abort-Session-Answer (ASA) is sent with DIAMETER_COMMAND_UNSUPPORTED
(3001).
PCEF/BBERF will be treated as an unsupported command. In response, an
Abort-Session-Answer (ASA) is sent with DIAMETER_COMMAND_UNSUPPORTED
(3001).
Charging Rule Definition Rejection if Precedence AVP Missing in
Create Case
Create Case
In the v8.0 Rel. 7 Gx implementation, when a charging rule definition is sent from PCRF
without the Precedence AVP, the default precedence value (255) is populated. Existing
precedence of the rule definition changes to the default value (255) even when there is no
Precedence AVP in the update.
without the Precedence AVP, the default precedence value (255) is populated. Existing
precedence of the rule definition changes to the default value (255) even when there is no
Precedence AVP in the update.
Now, if the Precedence AVP is missing in the new charging rule definition sent from the
PCRF, the default precedence value (255) is not populated, and the charging rule definition
is rejected. In the update case, if the Precedence AVP is missing, it is not updated with the
default precedence value (255), and the charging rule definition is not rejected. The existing
precedence is used.
PCRF, the default precedence value (255) is not populated, and the charging rule definition
is rejected. In the update case, if the Precedence AVP is missing, it is not updated with the
default precedence value (255), and the charging rule definition is not rejected. The existing
precedence is used.
Pipelining of HTTP Requests
ECS now supports pipelining of up to 32 HTTP requests on the same TCP connection.
Pipeline overflow requests are not analyzed. Such overflow requests are treated as
http-error. The billing system, based on this information, decides to charge or not charge, or
refund the subscriber accordingly.
Pipeline overflow requests are not analyzed. Such overflow requests are treated as
http-error. The billing system, based on this information, decides to charge or not charge, or
refund the subscriber accordingly.
Default IP for Unsupported Protocol
Unsupported protocol in the flow description is considered as failure and is no longer set
with IP as default protocol. In the create case, the rule definition is rejected when this failure
happens. In the update case, the existing rule definition is removed when the failure
happens.
with IP as default protocol. In the create case, the rule definition is rejected when this failure
happens. In the update case, the existing rule definition is removed when the failure
happens.