Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
Triggers for Generation of Charging Records ▀
GTPP Interface Administration and Reference, StarOS Release 18 ▄
41
When the ULI changes, then a data volume container is added to the field "List of Service Data Volumes".
The eG-CDRs will be closed and sent as a partial record for any of the following triggers:
Data volume limit
Time duration limit
Maximum number of charging condition changes (QoS/tariff time change)
Maximum number of service data containers
Management intervention
MS/Subscriber time zone change
Inter PLMN SGSN change
Radio Access Technology (RAT) change
When an eG-CDR partial is written, all open LOSDVs will be closed as well with a matching change condition.
The eG-CDRs will be closed and sent as a final record upon the deactivation of the PDP context in the GGSN, both for
normal termination and for any abnormal release.
normal termination and for any abnormal release.
All LOSDV which have been reported in previous partials but did not have a final change condition in the container are
repeated in the final eG-CDR with a final change condition (e.g. pDPContextRelease). In case no volume has been
transferred for this container since the last eG-CDR, then the timestamps for first and last usage will be set to the default
value of "000101000000-0200".
repeated in the final eG-CDR with a final change condition (e.g. pDPContextRelease). In case no volume has been
transferred for this container since the last eG-CDR, then the timestamps for first and last usage will be set to the default
value of "000101000000-0200".
The following table lists the values for the “CauseForRecordClosing” field based on trigger scenarios.
Table 11. 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