Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
▀ Charging Records
▄ GTPP Interface Administration and Reference, StarOS Release 19
30
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.
In StarOS release 16.0, S2a Mobility Over GTP (SaMOG) Gateway supports generation of CDR files for offline
charging. In Offline Charging, charging information is collected concurrently with resource usage. The charging
information is then passed through a chain of logical charging functions, and the CDR files are generated by the
network, which are then transferred to the network operator's Billing Domain.
charging. In Offline Charging, charging information is collected concurrently with resource usage. The charging
information is then passed through a chain of logical charging functions, and the CDR files are generated by the
network, which are then transferred to the network operator's Billing Domain.
As 3GPP specifications does not define a CDR format for SaMOG, the S-GW CDR and SGSN CDR record formats are
used to define the CDR format for SaMOG 4G/3G subscribers. The record format can be selected using a CLI command
under the GTPP Group Configuration Mode. By default, for an SaMOG license, the S-GW record type is used, and for
an SaMOG 3G license, the SGSN record type is used.
used to define the CDR format for SaMOG 4G/3G subscribers. The record format can be selected using a CLI command
under the GTPP Group Configuration Mode. By default, for an SaMOG license, the S-GW record type is used, and for
an SaMOG 3G license, the SGSN record type is used.
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.