Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
Triggers for Generation of Charging Records ▀
GTPP Interface Administration and Reference, StarOS Release 19 ▄
39
Table 10. Triggers for ePDG-CDR Closure
Closure
Conditions
Conditions
Description/Behavior
End of bearer
within the ePDG
within the ePDG
Deactivation of the bearer (either default or dedicated) in the ePDG will result in the CDR being closed. The
trigger condition covers:
trigger condition covers:
termination of bearer;
any abnormal release (as listed below):
GTP-C/GTP-U path failures in S2b interface
Dead Peer Detection in SWu interface.
IKESA/IPSESA rekey failure
Partial Record
Reason
Reason
OAM&P reasons permit the closure of the CDR for internal reasons.
The trigger condition covers:
The trigger condition covers:
data volume limit; CDR generated based on every uplink/downlink/total volume limit.
time (duration) limit; CDR generated for every configured "x" seconds time
maximum number of charging condition changes (QoS/tariff time change); CDR generated when the
max bucket limit is reached. By default its 4.Please check "cc profile <> buckets <>" CLI under
accouting-policy configuration mode.
max bucket limit is reached. By default its 4.Please check "cc profile <> buckets <>" CLI under
accouting-policy configuration mode.
management intervention; (clear subscriber <>)
The Partial Record generation trigger thresholds are those associated with the Charging Characteristics. The Partial
Record generation trigger thresholds are ePDG configuration parameters defined per Charging Characteristics profile by
the operator through configuration options. In the event that the ePDG-CDR is closed and the bearer remains active, a
further ePDG-CDR is opened with an incremented Sequence Number in the ePDG.
Record generation trigger thresholds are ePDG configuration parameters defined per Charging Characteristics profile by
the operator through configuration options. In the event that the ePDG-CDR is closed and the bearer remains active, a
further ePDG-CDR is opened with an incremented Sequence Number in the ePDG.
When Charging Event is triggered by the above listed conditions, the Change-Condition (at PS information level)
associated to the CDR closure, indicating the appropriate condition will be present, and it will be omitted otherwise.
associated to the CDR closure, indicating the appropriate condition will be present, and it will be omitted otherwise.
GGSN CDR Triggers
The following sections describe the triggers for the generation of partial and final G-CDRs and eG-CDRs.
G-CDR Triggers
G-CDRs are updated (not closed) for any of the following conditions:
SGSN IP address change
When the SGSN IP address changes, i.e. an Update PDP Context Request is received with a new SGSN IP
address, the old address (if not already added) and the new address are added to the field “List of SGSN
Addresses”.
address, the old address (if not already added) and the new address are added to the field “List of SGSN
Addresses”.
QoS change