Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
▀ Charging Records
▄ GTPP Interface Administration and Reference, StarOS Release 19
34
By default, the G-CDR does not support the traffic and vendor specific records. To support a traffic and vendor specific
record, the ECS must be configured to generate eG-CDRs. eG-CDRs are useful to implement Time Based Charging
(TBC) and Flow Based bearer Charging (FBC) to ECS.
record, the ECS must be configured to generate eG-CDRs. eG-CDRs are useful to implement Time Based Charging
(TBC) and Flow Based bearer Charging (FBC) to ECS.
eG-CDR supports customer specific formats configured in Ga context in a GGSN service with standard or custom
specific GTPP dictionaries.
specific GTPP dictionaries.
eG-CDR Format
The eG-CDRs can be in ASN.1 Format.
For more information on G-CDR and eG-CDR attributes and definitions, refer to the G-CDR and Enhanced G-CDR
Field Descriptions chapter in this reference guide.
Field Descriptions chapter in this reference guide.
PDN Gateway Call Detail Records (PGW-CDRs)
PGW-CDRs are generated according to 3GPP TS 32.298 V8.5.0.
PGW-CDR Format
The PGW-CDRs can be in ASN.1 Format.
Serving Gateway Call Detail Records (SGW-CDRs)
SGW-CDRs are generated according to 3GPP TS 32.298 V8.7.0.
SGW-CDR Format
The SGW-CDRs can be in ASN.1 Format.
Standard SGSN CDRs
S-CDRs are generated according to 3GPP TS 32.215 V4.5.0 for Release 4 dictionaries, and 3GPP TS 32.298 V6.4.1 for
Release 6 dictionaries.
Release 6 dictionaries.
S-CDR Format
The S-CDRs can be in ASN.1 Format.
Wireless LAN Call Detail Records (WLAN-CDRs)
WLAN-CDRs are generated according to 3GPP TS 32.298 V6.4.1.