Cisco ASR 5000 Series, Обзор продукта

Страница: 755 / 992

Enhanced Charging Service Overview
Accounting Interfaces ▀
Cisco ASR 5000 Series Product Overview ▄
OL-22938-02
Standard GGSN Call Detail Records (G-CDRs)
Important:
G-CDRs are only available in GGSN networks.
G-CDRs are generated according to 3GPP TS 32.251 V6.6.0.
Currently ECS supports generation of CDRs using AAAMgrs only.
G-CDR Format
The G-CDRs can be in ASN.1 format.
Important:
For more information on G-CDR fields, refer to the AAA Interface Administration and Reference
Guide .
Enhanced GGSN Call Detail Records (eG-CDRs)
Important:
eG-CDRs are only available in GGSN networks.
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.
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 TBC and FBC to ECS.
eG-CDR supports customer specific formats configured in Ga context in a GGSN service with standard or custom
specific GTPP dictionaries.
eG-CDR Format
The eG-CDRs can be in ASN.1 format.
Triggers to Update eG-CDRs
The following table lists the trigger conditions to update charging information in an eG-CDR.
Table 91. Triggers for charging information update in eG-CDR
Triggers Description and Action