GTPP Interface Overview
CDR Transport by GTPP
CDR Push Functionality
IMPORTANT:
Path Protocol
GTPP Message Types
|
Message Type value (Decimal)
|
GTPP Message
|
|---|---|
|
1
|
Echo Request
|
|
2
|
Echo Response
|
|
3
|
Version Not Supported
|
|
4
|
Node Alive Request
|
|
5
|
Node Alive Response
|
|
6
|
Redirection Request
|
|
7
|
Redirection Response
|
|
240
|
Data Record Transfer Request
|
|
241
|
Data Record Transfer Response
|
|
Others
|
Reserved for future
use
|
IMPORTANT:
|
TLV Information Element
Types
|
|
|
254
|
Address of Recommended
Node
|
|
253
|
Requests Responded
|
|
252
|
Data Record Packet
|
|
251
|
Charging Gateway Address
(this IE is also used in TS 29.060 [200])
|
|
250
|
Sequence Numbers of
Canceled Packets
|
|
249
|
Sequence Numbers of
Released Packets
|
|
TV Information Element
Types
|
|
|
127
|
Charging ID
|
|
126
|
Packet Transfer Command
|
Usage of GTPP Header in Charging
Information Elements
GTPP Messages
Node Alive Request
IMPORTANT:
|
Information Element
|
Presence Requirement
|
|---|---|
|
Node Address
|
Mandatory
|
|
Alternative Node Address
|
Optional
|
|
Private Extension
|
Optional
|
Node Alive Response
|
Information Element
|
Presence Requirement
|
|---|---|
|
Private Extension
|
Optional
|
Redirection Request
|
Information Element
|
Presence Requirement
|
|---|---|
|
Cause
|
Mandatory
|
|
Address of Recommended
Node
|
Optional
|
|
Alternative Address
of Recommended Node
|
Optional
|
|
Private Extension
|
Optional
|
Redirection Response
|
Information Element
|
Presence Requirement
|
|---|---|
|
Cause
|
Mandatory
|
|
Private Extension
|
Optional
|
Data Record Transfer Request
Information Elements in Data Record Transfer Request
Packet Transfer Command IE
Data Record Packet IE
Sequence Numbers of Canceled Packets IE
Data Record Transfer Response
Handling Error Response Cause
Charging Characteristics
|
CLI command configured
on GGSN
|
Sent by SGSN
|
Sent by AAA
|
CC used
|
chargingCharSelMode
|
|---|---|---|---|---|
|
no cc-sgsn
|
no cc
|
no cc
|
Default
|
Home/Visiting/Roaming
Default
|
|
cc
|
Default
|
Home/Visiting/Roaming
Default
|
||
|
cc
|
no cc
|
SGSN
|
SGSN Supplied
|
|
|
cc
|
SGSN
|
SGSN Supplied
|
||
|
cc-sgsn use-ggsn
|
no cc
|
no cc
|
GGSN
|
GGSN Override
|
|
cc
|
GGSN
|
GGSN Override
|
||
|
cc
|
no cc
|
GGSN
|
GGSN Override
|
|
|
cc
|
GGSN
|
GGSN Override
|
||
|
cc-sgsn radius-returned
|
no cc
|
no cc
|
Default
|
Home/Visiting/Roaming
Default
|
|
cc
|
AAA
|
AAA Supplied
|
||
|
cc
|
no cc
|
SGSN
|
SGSN Supplied
|
|
|
cc
|
AAA
|
AAA Supplied
|
||
|
cc-sgsn radius-returned
use-ggsn
|
no cc
|
no cc
|
GGSN
|
GGSN Override
|
|
cc
|
AAA
|
AAA Supplied
|
||
|
cc
|
no cc
|
GGSN
|
GGSN Override
|
|
|
cc
|
AAA
|
AAA Supplied
|
Charging Records
IMPORTANT:
IMPORTANT:
Zero Volume CDR Suppression
IMPORTANT:
File Format for CDRs
| Field | Description | Value |
|---|---|---|
| 0x00 - 0x03 | Offset | Offset from EoH to first Unread CDR (4 Bytes) |
| 0x04 - 0x07 | Encoding | Basic Encoding Rule (BER) i.e. 1 (4 Bytes) |
| 0x08 - 0x0b | Number of CDRs | Total number of CDRs in the file (4 Bytes) |
| 0x0c - 0x0f | Number of read CDRs | Total number of read CDRs in the file (4 Bytes) |
| 0x10 - 0x13 | File size | Size of CDR file in bytes (4 Bytes) |
| 0x14 - 0x17 | Abstract Syntax Notation One (ASN.1) format definition version | ASN.1 definition version information (4 Bytes) |
IMPORTANT:
IMPORTANT:
IMPORTANT:
Enhanced G-CDRs
Triggers for Generation of Charging Records
GGSN CDR Triggers
G-CDR Triggers
eG-CDR Triggers
|
Cause
|
Scenarios
|
Partial/Final
|
Value
|
Supported
|
|---|---|---|---|---|
|
normalRelease
|
– Delete PDP from
SGSN
– Manual call clearing
on GGSN
– Radius disconnect
– Idle and absolute
timeout
|
Final
|
0
|
Yes
|
|
abnormalRelease
|
– Path failure
– 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
|
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
| Cause | Scenarios | Partial/Final | Value | Supported |
|---|---|---|---|---|
| normalRelease | IP-CAN bearer release or detach | Final | 0 | Yes |
| abnormalRelease | Any other abnormal release | Final | 4 | Yes |
| volumeLimit | Configured volume threshold has been exceeded | Partial | 16 | Yes |
| timeLimit | Configured interval has been reached | Partial | 17 | Yes |
| servingNodeChange | Serving node Address list overflow | Partial | 18 | Yes |
| maxChangeCondition | Maximum number of changes in charging conditions | Partial | 19 | Yes |
| managementIntervention | For example, using the command gtpp interim now active-charging egcdr | Partial | 20 | Yes |
| RAT Change | Change of radio interface from (for example, EUTRAN to GSM to UMTS) | Partial | 22 | Yes |
| mSTimeZoneChange | MS changes time zone | Partial | 23 | Yes |
| PLMN Change | Change of PLMN-ID | Partial | 24 | Yes |
PGW-CDR Charging Information Addition
|
Trigger Conditions
|
Description/Behavior
|
|---|---|
|
IP-CAN bearer modification
|
A change of IP-CAN bearer
conditions (QoS change, SGSN/S-GW change, PLMN Id change,
RAT change, user location change) results in a set of “List
of Service Data” containers, such as all active service
data flow containers, being added to the CDR.
|
|
Tariff Time Change
|
On reaching the Tariff
Time Change, a set of “List of Service Data” containers,
such as all active service data flow containers, is added to the CDR.
|
|
DCCA Failure-Handling
procedure triggering
|
When the Diameter Credit-Control-Failure-Handling
mechanism is triggered a “List of Service Data”,
such as all active service data flow containers, is added to the
CDR.
The causes are only
relevant due to simultaneous usage of an active DCCA session.
|
|
Service data flow report
|
For independent online
and offline charging, a “List of Service Data” container
for the service data flow is added at:
For tight interworking
of online and offline charging, a “List of Service Data” container
for the service data flow is added when:
|
S-CDR Triggers
Triggers for S-CDR Closure
|
Cause For Record Closure
|
||||
|---|---|---|---|---|
| Cause | Scenarios | Partial/Final | Value | Configurable |
| normalRelease | Final | 0 | No | |
| abnormalRelease | Final | 4 | No | |
| SGSN Change |
PDP Release in old
SGSN due to ISRAU scenario.
|
Final | 18 | No |
| volumeLimit |
configured volume threshold has
been exceeded
|
Partial | 16 | Yes |
| timeLimit |
configured interval
has been reached
|
Partial | 17 | Yes |
| maxChangeCondition |
limit for the LOTV
containers was exceeded
|
Partial | 19 | Yes |
| managementIntervention |
e.g. using the command "gtpp interim now"
and also "clear subscribers all"
|
Partial | 20 | No |
| managementIntervention | i.e. using the command "clear subscribers all" | Final | 20 | No |
| intraSGSNIntersystemChange | change of radio interface from GSM to UMTS or vice-versa | Partial | 21 | No |
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. | Partial | 0 | Yes |
| tariffTime | On reaching the Tariff Time Change a "List of Traffic Data Volumes" container will be added to the CDR. | Partial | 1 | Yes |
| Direct Tunnel 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. | Partial | 8 | Yes |
| Direct Tunnel Removal | When the SGSN establishes or removes a Direct Tunnel a “List of 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. | - | 2 | No |
SGW-CDR Triggers
| Cause | Scenarios | Partial/Final | Value | Supported |
|---|---|---|---|---|
| normalRelease | IP-CAN bearer release or detach | Final | 0 | Yes |
| abnormalRelease | Any other abnormal release | Final | 4 | Yes |
| volumeLimit | Configured volume threshold has been exceeded | Partial | 16 | Yes |
| timeLimit | Configured interval has been reached | Partial | 17 | Yes |
| servingNodeChange | Serving node Address list overflow | Partial | 18 | Yes |
| maxChangeCondition | Limit for the LOTV containers was exceeded | Partial | 19 | Yes |
| managementIntervention | For example, using the command gtpp interim now | Partial | 20 | Yes |
| RAT Change | Change of radio interface from (for example, EUTRAN to GSM to UMTS) | Partial | 22 | No |
| mSTimeZoneChange | MS changes time zone | Partial | 23 | Yes |
IMPORTANT:
IMPORTANT:
SGW-CDR Charging Information Addition
|
Trigger Conditions
|
Description/Behavior
|
|---|---|
|
QoS Change
|
A change in the QoS
will occur when the open “List of Traffic Data Volumes” containers
are closed and added to the CDR, and a new IP-CAN bearer specific
container is opened.
|
|
Tariff Time Change
|
After reaching the Tariff
Time Change, open “List of Traffic Data Volumes” containers
are closed and added to the CDR.
|
|
User Location Change
|
A change in the User
Location Info (for example, ECGI, TAI, RAI, SAI or CGI) will close
open “List of Traffic Data Volumes” containers.
They are then added to the CDR if location reporting is required
and a report of User Location Change is received.
|
|
ULI Change
|
When the ULI changes,
then a data volume container is added to the field "List of Service
Data Volumes".
|
|
CDR Closure
|
Open “List
of Traffic Data Volumes” containers are closed and added
to the SGW-CDR.
|
WLAN-CDR Triggers
| Cause | Scenarios | Partial/Final | Value | Configurable |
|---|---|---|---|---|
| normalRelease | UE is terminating the call | Final | 0 | No |
| abnormalRelease | Failure within the chassis (due to multiple software failures) | Final | 4 | No |
| volumeLimit | Configured volume threshold has been exceeded | Partial | 16 | Yes |
| timeLimit | Configured interval has been reached | Partial | 17 | Yes |
| maxChangeCondition | Limit for the LOTV containers was exceeded | Partial | 19 | Yes |
| managementIntervention | For example, using the command gtpp interim now | Partial | 20 | No |
| managementIntervention | For example, using the command clear subscribers all | Final | 20 | No |
WLAN-CDR Charging Information Addition
| Cause | Scenarios | Partial/Final | Value | Configurable |
|---|---|---|---|---|
| QoS Change | A change in the QoS shall result that open “List of Traffic Data Volumes” containers being closed and added to the CDR and new bearer specific container is opened. | Partial | 0 | Yes |
| tariffTime | On reaching the Tariff Time Change a “List of Traffic Data Volumes” container will be added to the CDR. | Partial | 1 | Yes |
| recordClosure | A list of “List of Traffic Data Volumes” container will be added to the WLAN-CDR. | - | 2 | No |