Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
▀ Triggers for Generation of Charging Records
▄ GTPP Interface Administration and Reference, StarOS Release 19
42
PGW-CDR Triggers
The following events trigger closure and the sending of a partial PGW-CDR:
When the number of QoS changes or tariff time changes has reached the configured maximum number of
charging condition changes. Before this, service containers are added to the CDR for every change.
Every x seconds configured using “interval x”
Every x octets configured using “volume x” (up/down/total)
Command
gtpp interim now active-charging egcdr
Transferring the context to a new SGW/SGSN (serving Node Change).
Changing the access type within the same P-GW (RAT Change)
A PGW-CDR is closed as the final record of a subscriber session for the following events:
Detach Request received from UE
Delete bearer context request received from SGW.
Manual subscriber clearing
Abnormal Releases such as path failures
The following table lists the values for the “CauseForRecordClosing” field based on trigger scenarios.
Table 12. 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
conditions are met. Each container identifies the configured counts (volume separated for uplink and downlink, elapsed