Cisco Cisco Packet Data Interworking Function (PDIF)
GTPP Accounting Overview
Charging Records ▀
GTPP Interface Administration and Reference, StarOS Release 18 ▄
33
Example:
default3_07_15_2009_08_09_25_4_file000003.u
custom6 Format: This file format is similar to custom4 file format except CDRs will be written in 8Kbyte
blocks in a file.
Header: No Header
Contents: CDR1|CDR2FFFFFF|CDR3FFFFF..|..CDRnFFFF|
where | represents the end of a 8K block
EoF marker: No EoF marker
File name format:
<node-id-suffix+vpn-id>_<date>+<time>_<total-cdrs>_file<fileseqnum>.u
The
<fileseqnum>
denotes the file sequence number ranging from 1 through 4294967295.
Example:
default3_07_15_2009_07_59_32_5_file2.u
Important:
These file formats are customer-specific. For more information on the file formats, contact your
Cisco account representative.
Evolved Packet Data Gateway Call Detail Records (ePDG-CDRs)
ePDG-CDRs are generated according to 3GPP TS 32.298 V12.6.0.
ePDG-CDR Format
The ePDG-CDRs can be in ASN.1 format.
Standard G-CDRs
G-CDRs are generated according to 3GPP TS 32.251 V6.6.0. Currently ECS supports generation of CDRs using
AAAMgrs only.
AAAMgrs only.
G-CDR Format
The G-CDRs can be in ASN.1 Format.
Enhanced G-CDRs
The ECS also supports enhanced G-CDRs, which is an enhanced format of standard G-CDRs to provide greater
portability of charging information. eG-CDRs are compliant with 3GPP TS 32.298 v6.5.0 for Rel. 6 based dictionaries,
and with 3GPP TS 32.298 v7.4.0 for Rel. 7 based dictionaries.
portability of charging information. eG-CDRs are compliant with 3GPP TS 32.298 v6.5.0 for Rel. 6 based dictionaries,
and with 3GPP TS 32.298 v7.4.0 for Rel. 7 based dictionaries.