Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
▀ Triggers for Generation of Charging Records
▄ GTPP Interface Administration and Reference, StarOS Release 17
40
Table 10. Cause for Record Closing
Cause
Scenarios
Partial/Final
Value
Supported
normalRelease
IP-CAN bearer release or detach
Final
0
Yes
abnormalRelease
Any other abnormal release
Final
4
Yes
volumeLimit
Configured volume threshold has been exceeded
Partial
16
Yes
timeLimit
Configured interval has been reached
Partial
17
Yes
servingNodeChange
Serving node Address list overflow
Partial
18
Yes
maxChangeCondition
Maximum number of changes in charging conditions
Partial
19
Yes
managementIntervention
For example, using the command
gtpp interim now active-
charging egcdr
Partial
20
Yes
RAT Change
Change of radio interface from (for example, EUTRAN to GSM to
UMTS)
UMTS)
Partial
22
Yes
mSTimeZoneChange
MS changes time zone
Partial
23
Yes
PLMN Change
Change of PLMN-ID
Partial
24
Yes
PGW-CDR Charging Information Addition
The “List of Service Data” attribute in the PGW-CDR consists of a set of containers that are added when specific trigger
conditions are met. Each container identifies the configured counts (volume separated for uplink and downlink, elapsed
time, or number of events) per rating group or combination of the rating group and service id within the same IP-CAN
bearer, on encountering that trigger condition.
conditions are met. Each container identifies the configured counts (volume separated for uplink and downlink, elapsed
time, or number of events) per rating group or combination of the rating group and service id within the same IP-CAN
bearer, on encountering that trigger condition.
Table 11. Triggers for PGW-CDR Charging Information Addition
Trigger Conditions
Description/Behavior
IP-CAN bearer
modification
modification
A change of IP-CAN bearer conditions (QoS change, SGSN/S-GW change, PLMN Id change, RAT
change, user location change) results in a set of “List of Service Data” containers, such as all active
service data flow containers, being added to the CDR.
change, user location change) results in a set of “List of Service Data” containers, such as all active
service data flow containers, being added to the CDR.
Tariff Time Change
On reaching the Tariff Time Change, a set of “List of Service Data” containers, such as all active
service data flow containers, is added to the CDR.
service data flow containers, is added to the CDR.
DCCA Failure-
Handling procedure
triggering
Handling procedure
triggering
When the Diameter Credit-Control-Failure-Handling mechanism is triggered a “List of Service Data”,
such as all active service data flow containers, is added to the CDR.
The causes are only relevant due to simultaneous usage of an active DCCA session.
such as all active service data flow containers, is added to the CDR.
The causes are only relevant due to simultaneous usage of an active DCCA session.