Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
Triggers for Generation of Charging Records ▀
GTPP Interface Administration and Reference, StarOS Release 17 ▄
43
Triggers for S-CDR Charging Information Addition
The "List of Traffic Volumes" attribute of the S-CDR consists of a set of containers, which are added when specific
trigger conditions are met, and identify the volume count per PDP context, separated for uplink and downlink traffic, on
encountering that trigger condition.
trigger conditions are met, and identify the volume count per PDP context, separated for uplink and downlink traffic, on
encountering that trigger condition.
Table 13. Triggers for S-CDR Charging Information Addition
Change Condition
Cause
Scenario
Partial/Final
Value
Configurable
qoSChange
A change in the QoS will result in a "List of Traffic Data Volumes"
container being added to the CDR.
container being added to the CDR.
Partial
0
Yes
tariffTime
On reaching the Tariff Time Change a "List of Traffic Data Volumes"
container will be added to the CDR.
container will be added to the CDR.
Partial
1
Yes
Direct Tunnel
establishment
establishment
When the SGSN establishes or removes a Direct Tunnel a “List of
Traffic Data Volumes” container will be added to the CDR. When a
direct tunnel is established, the SGSN will no longer be able to count
data volumes associated with the IP-CAN bearer for which the direct
tunnel is established.
Traffic Data Volumes” container will be added to the CDR. When a
direct tunnel is established, the SGSN will no longer be able to count
data volumes associated with the IP-CAN bearer for which the direct
tunnel is established.
Partial
8
Yes
Direct Tunnel
Removal
Removal
When the SGSN establishes or removes a Direct Tunnel a “List of
Traffic Data Volumes” container will be added to the CDR.
Traffic Data Volumes” container will be added to the CDR.
Partial
9
Yes
recordClosure
A list of "List of Traffic Data Volumes" container will be added to the
S-CDR.
S-CDR.
-
2
No
SGW-CDR Triggers
The following events trigger closure and sending of a partial SGW-CDR.
When the number of QoS changes or tariff time changes or number of user location changes have reached the
configured number of “buckets”. Prior to this, another traffic data volume container is added to the CDR for
every change.
every change.
Every x seconds configured using “interval x”
Every x octets configured using “volume x” (up/down/total)
Command
gtpp interim now
Transferring the context to a new S-GW
Changing the access type within the same S-GW (RAT Change)
An SGW-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 MME
Delete bearer context request received from P-GW