Cisco Cisco Packet Data Gateway (PDG)
GTPP Accounting Overview
▀ Triggers for Generation of Charging Records
▄ GTPP Interface Administration and Reference, StarOS Release 19
40
When a QoS change is detected, i.e. an Update PDP Context Request is received with a new QoS value) and
the maximum number of configured “buckets” has not been reached, then a traffic data volume container for
the previous QoS and volume is added to the field “List of Traffic Data Volumes”.
the maximum number of configured “buckets” has not been reached, then a traffic data volume container for
the previous QoS and volume is added to the field “List of Traffic Data Volumes”.
Tariff Time Change
When the tariff time changes and the maximum number of configured “buckets” has not been reached, then a
traffic data volume container is added to the field “List of Traffic Data Volumes” for the volume before the
tariff time.
traffic data volume container is added to the field “List of Traffic Data Volumes” for the volume before the
tariff time.
The following events trigger closure and sending of a partial G-CDR:
When the number of SGSN changes has reached the configured number of “sgsns”. Before this, the new SGSN
address is added to the list of SGSN IP addresses in the CDR. If “sgsns 4” is configured, this means that after 4
handovers the record is closed and the G-CDR will contain 5 SGSN IP addresses. The parameter can be set to 1
to 4 with a default of 4.
handovers the record is closed and the G-CDR will contain 5 SGSN IP addresses. The parameter can be set to 1
to 4 with a default of 4.
When the number of QoS changes or tariff time changes, with up to 4 timestamps which can be configured using
the tariff statement, has reached the configured number of “buckets” (1 to 4 with default of 4). Before this,
another traffic data volume container is added to the CDR for every change.
another traffic data volume container is added to the CDR for every change.
Every x seconds configured using “interval x”
Every x octets configured using “volume x” (up/down/total)
A G-CDR is closed as the final record of a subscriber session for the following events:
Delete PDP context received from SGSN
Delete PDP context initiated by GGSN (e.g. expiry of idle or absolute timer)
Abnormal Releases such as PDP context replacements
eG-CDR Triggers
eG-CDRs are updated (not closed) for any of the following conditions:
PDP context modification
When a change of PDP context conditions occurs (QoS change, SGSN change, PLMN Id change, RAT
change) the List of Service Data (LOSDV) and the List of Traffic Volume (LOTV) containers are updated.
change) the List of Service Data (LOSDV) and the List of Traffic Volume (LOTV) containers are updated.
In case of SGSN change condition only LOSDV containers are updated and also the List of SGSN addresses is
updated.
updated.
Tariff time change
When a change of tariff time occurs a set of LOSDV and LOTV containers, i.e. all active service data flow
containers, will be added to eG-CDR.
containers, will be added to eG-CDR.
Failure handling procedure triggering
When the failure handling mechanism is triggered and the failure action is set to “continue” a set of LOSDV
and LOTV containers, i.e. all active service data flow containers, will be added to eG-CDR.
and LOTV containers, i.e. all active service data flow containers, will be added to eG-CDR.
Service data flow report
When an expiry of time limit, volume limit or termination is detected for a service data flow a set of LOSDV
container is added to eG-CDR.
container is added to eG-CDR.
CDR closure
When a CDR closure occurs all active LOSDV containers are added to eG-CDR.
ULI change