Cisco Cisco Packet Data Gateway (PDG) Guida Dell'Amministratore
GTPP Accounting Overview
▀ Triggers for Generation of Charging Records
▄ Cisco ASR 5x00 GTPP Interface Administration and Reference
34
Table 9. Cause for Record Closing
Cause
Scenarios
Partial/Final Value Supported
normalRelease
– Delete PDP from SGSN
– Manual call clearing on GGSN
– Radius disconnect
– Idle and absolute timeout
– Manual call clearing on GGSN
– Radius disconnect
– Idle and absolute timeout
Final
0
Yes
abnormalRelease
– Path failure
– Context replacement
– Context replacement
Final
4
Yes
volumeLimit
Configured volume threshold has been exceeded
Partial
16
Yes
timeLimit
Configured interval has been reached
Partial
17
Yes
sGSNChange
– Configured limit of SGSN changes has been reached
– inter-PLMN SGSN change
– inter-PLMN SGSN change
Partial
18
Yes
maxChangeCond
Configured limit of change conditions has been reached Partial
19
Yes
managementIntervention For example, using the command
gtpp interim now
Partial
20
Yes
rATChange
Radio access technology change
Partial
22
Yes
mSTimeZoneChange
MS changes time zone
Partial
23
Yes
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.