Cisco Cisco Packet Data Gateway (PDG) Guía De Administador
GTPP Accounting Overview
Charging Records ▀
Cisco ASR 5x00 GTPP Interface Administration and Reference ▄
27
Charging Records
Charging records support details of the termination such as which end initiated the termination, termination type e.g.
RST, FIN, etc. and in case of HTTP 1.1, whether or not the connection is still open. It is possible to pipeline up to 15
HTTP requests on the same TCP connection. The billing system, based on this information, decides upon the success or
failure of the connection and charge or refund accordingly.
RST, FIN, etc. and in case of HTTP 1.1, whether or not the connection is still open. It is possible to pipeline up to 15
HTTP requests on the same TCP connection. The billing system, based on this information, decides upon the success or
failure of the connection and charge or refund accordingly.
To cover the requirements of standard solutions and at the same time, provide flexible and detailed information on
service usage, the following types of usage records are provided:
service usage, the following types of usage records are provided:
Standard G-CDRs
eG-CDRs
PGW-CDRs
SGW-CDRs
S-CDRs
WLAN-CDRs
The Multimedia Core Platform supports multiple fields for use in these CDRs. The CDRs are encoded using the ASN.1
format and are sent to the CGF using the GTPP.
format and are sent to the CGF using the GTPP.
Important:
The behavior for several of the fields supported in CDRs can be modified. For more information,
refer to the Command Line Interface Reference.
Important:
SGW-CDRs are suppressed and only PGW-CDRs are generated for a session hosted by the
associated S-GW and P-GW service. SGW-CDRs are generated when the S-GW connects to an external P-GW.
Zero Volume CDR Suppression
Important:
The Zero Volume CDR Suppression is a license-controlled feature applicable to all types of CDRs –
GGSN CDRs, PGW-CDRs, SGW-CDRs, and SGSN CDRs. For more information, contact your Cisco account
representative.
representative.
This feature is developed to suppress the CDRs with zero byte data count, so that the OCG node is not overloaded with
a flood of CDRs. The CDRs can be categorized as follows:
a flood of CDRs. The CDRs can be categorized as follows:
Final-cdrs: These CDRs are generated at the end of a context.
Internal-trigger-cdrs: These CDRs are generated due to internal triggers such as volume limit, time limit, tariff
change or user generated interims through the CLI commands.
External-trigger-cdrs: These CDRs are generated due to external triggers such as QoS Change, RAT change and
so on. All triggers which are not considered as final-cdrs or internal-trigger-cdrs are considered as external-
trigger-cdrs.
trigger-cdrs.
The customers can select the CDRs they want to suppress. A new CLI command
[ default | no ] gtpp
suppress-cdrs zero-volume { external-trigger-cdr | final-cdr | internal-trigger-cdr }
is