Record Type
|
0
|
M
|
The field identifies
the type of the record:- S-CDR(sgsnPDPRecord) 18 (0x12)
- G-CDR(ggsnPDPRecord)
19 (0x13)
- eG-CDR(egsnPDPRecord)
70 (0x46)
|
Integer
|
1
|
80
|
Network initiated PDP context
|
1
|
O
|
This field indicates
that the PDP context was network initiated. The field is missing
in case of mobile activated PDP context. Set to TRUE (0xFF) if PDP
context was initiated from network side.
This field is not yet supported
by the SGSN.
|
Boolean
|
1
|
81
|
Served IMSI
|
3
|
M
|
This field contains
the International Mobile Subscriber Identity (IMSI) of the served
party.
The IMSI is formatted
in accordance with 3GPP TS 23.003.
|
BCD encoded octet string
|
3-8
|
83
|
GGSN Address
|
4
|
M
|
This field provides
the current serving GGSN IP Address for the Control Plane, which is
equivalent to the configured ggsn-service address on the GGSN. The standard
3GPP 32.298 offers a choice for the encoding of the address to be
either in binary or text format.
The GGSN encodes the address
in binary format and includes the octet string.
|
Choice
|
6
|
a4
|
GGSN IPv4 Binary Address
|
4-0
|
M
|
The octet string included in
the field described above includes the Gn address of the GGSN service
in binary coding.
|
Octet string
|
4
|
80
|
Charging ID
|
5
|
M
|
This field is a charging identifier, which
can be used together with the GGSN address to identify all records produced
in the GGSN involved in a single PDP context. The Charging ID is generated
by the GGSN at PDP context activation and is transferred to the
context requesting SGSN. At an inter-SGSN routing area update the charging
ID is transferred to the new SGSN as part of each active PDP context.
The possible values
for the charging ID, which are defined in TS 29.060 are 1-4,294,967,295 and
those values are encapsulated in following scheme in the CDR-field:
1 - 127 850101-85017F
128 – 32,767 85020080-85027FFF
32,768 – 8,388,607 8503008000-85037FFFFF
8,388,608 – 2,147,483,647 850400800000-85047FFFFFF
2,147,483,648 – 4,294,967,295 85050080000000- 850500FFFFFFFF
|
Integer
|
1-5
|
85
|
SGSN Address
|
6
|
M
|
This field contains
one or several SGSN IP addresses.
For an S-CDR, the SGSN
address contains the control plane or user plane address of the current
SGSN serving the PDP context.
For a G-CDR and eG-CDR,
in addition to the current SGSN being used, the field may contain additional SGSN addresses where
the PDP context was located before and where it has moved away
using the Inter-SGSN Routing Area Update Procedure. The maximum number
of addresses in the list is 5.
|
Sequence
|
6-30
|
a6
|
SGSN IPv4 Binary Address
|
6-0
|
M
|
The octet string included in
the field described above includes either control plane or user plane
address of the SGSN in binary coding.
|
Octet String
|
4
|
80
|
Access Point Name Network Identifier
|
7
|
M
|
This field contains
the Network Identifier part of the Access Point Name (APN). It is provided
by the SGSN in the Create PDP Context Request message.
For GGSN generated records,
in case of a configured virtual APN, the virtual APN is included instead,
unless this is overridden by the option gcdr apn-name-to-be-included {gn | virtual}
|
IA5string
|
1-63
|
87
|
PDP Type
|
8
|
M
|
This field defines
the PDP type, e.g. IP or PPP, as received in the PDP context request
from the SGSN.
Supported values:
|
Octet string
|
2
|
88
|
Served PDP Address
|
9
|
O
|
This field contains
the PDP address of the served IMSI for which the standard 3GPP TS
32.298 allows a choice of either IPAddress or ETSIAddress.
|
Choice
|
8
|
a9
|
PDP IP Address
|
9-0
|
M
|
This field contains
the IP address for the PDP context.
|
Choice
|
6
|
a0
|
PDP IPv4 Binary Address
|
9-0-0
|
M
|
The octet string included in
the field described above includes the IPv4 address assigned to
the subscriber by the GGSN in binary coding.
|
Octet String
|
4
|
80
|
Dynamic Address Flag
|
11
|
O
|
This field indicates
that the PDP address has been dynamically allocated for that particular PDP
context. In this case, the value is set to TRUE and encoded as "FF".
This field is missing if the address allocation method was "static",
i.e. part of PDP context subscription.
|
Boolean
|
1
|
8b
|
List of Traffic Volumes
|
12
|
M
|
This list includes
one or more Traffic Volume containers related to a "Change of Charging Condition"
as described in the next field. The maximum number of containers
is configurable.
|
Sequence
|
Variable length
|
ac
|
ChangeOfCharCondition
|
12-0
|
M
|
Each traffic volume container contains details
related to a charging condition as described in the following subsections.
A new container is usually created for a QoS change and for tariff changes.
|
Sequence
|
Variable length
|
30
|
QoS Requested
|
12-0-1
|
O
|
This field contains
the QoS desired by the MS at PDP context activation.
|
Octet String
|
4-15
|
81
|
QoS Negotiated
|
12-0-2
|
O
|
This field indicates
the applied QoS accepted by the network.
The QoS values may only
be included in the first container, in later containers the presence depends
upon what was changed.
|
Octet String
|
4-15
|
82
|
GPRS Uplink data volume
|
12-0-3
|
M
|
This field includes
the number of octets transmitted during the use of the packet data
services in the uplink direction.
The amount of data counted
in the GGSN is the payload of the GTP-U protocol at the Gn interface. The
data counted already includes the IP PDP bearer protocols i.e. IP
or PPP.
Note that a maximum
of 2^32 bytes can be counted in this field. A volume trigger should
be defined at least for this value to avoid an overflow, if not
done already for a smaller amount of traffic.
|
Integer
|
1-5
|
83
|
GPRS Downlink data volume
|
12-0-4
|
M
|
This field includes
the number of octets transmitted during the use of the packet data
services in the downlink direction.
The amount of data counted
in the GGSN is the payload of the GTP-U protocol at the Gn interface. The
data counted already includes the IP PDP bearer protocols i.e. IP
or PPP.
Note that a maximum
of 2^32 bytes can be counted in this field. A volume trigger should
be defined at least for this value to avoid an overflow, if not
done already for a smaller amount of traffic.
|
Integer
|
1-5
|
84
|
Change Condition
|
12-0-5
|
M
|
This field defines
the reason for closing the container such as tariff time change,
QoS change or closing of the CDR.
Supported values:
- qoSChange: 0
- tariffTime: 1
- recordClosure: 2
- failureHandlingContinueOngoing:
3
- failureHandlingRetryandTerminateOngoing:
4
- failureHandlingTerminateOngoing: 5
FailureHandling is a standard
AVP element in DCCA.
- Terminate: The online session is finished. The associated PDP Context is released (ongoing sessions) or not established (new sessions). Failover for ongoing sessions is not supported. Failover for new sessions is always supported.
- Retry&Terminate;: The online session is finished. The associated PDP Context is released (ongoing sessions) or not established (new sessions). Failover for ongoing sessions is supported. Failover for new sessions is always supported.
- Continue: The online session is finished. The associated PDP Context is established (new sessions) or not released (ongoing sessions). Failover for ongoing sessions is supported. Failover for new sessions is always supported.
|
Enumerated (Integer)
|
1
|
85
|
Change time
|
12-0-6
|
M
|
This field is a time stamp,
which defines the moment when the volume container is closed or
the CDR is closed.
|
BCD encoded octet string
|
9
|
86
|
Failurehandling Continue
|
12-0-7
|
O
|
Failure handling continue element
is present if failure handling procedure is executed by GGSN
|
Boolean
|
1
|
87
|
User Location Information
|
12-0-8
|
O
|
The User Location Information for
the MS if provided by the SGSN to the GGSN during the PDP context activation/modification procedure.
Transparently copied from
the GTP message.
|
Octet string
|
8
|
88
|
Record Opening Time
|
13
|
M
|
This field contains
the time stamp when PDP context is activated in GGSN or when a subsequent record
is opened after a partial record.
The timestamp is determined based
on the internal timer which has an accuracy of 10ms. Depending on the
configured mechanism (ceiling, floor, round-off) this is translated into
the timestamp which only shows the full seconds.
|
BCD encoded octet string
|
9
|
8d
|
Duration
|
14
|
M
|
This field contains
the relevant duration in seconds for PDP contexts with range of 0..4294967295 (2^32-1).
It is the duration from Record Opening
Time to the Change Time. This value is converted from the internal representation in milliseconds to
an integer value representing only seconds. The mechanism for this conversion (ceiling,
floor, round-off) can be configured. It is also possible to configure
to use milliseconds in this field instead of seconds.
|
Integer
|
1-5
|
8e
|
Cause for Record Closing
|
15
|
M
|
This field contains
a reason for the closure of the CDR.
Supported values:
- normalRelease: 0
- abnormalRelease: 4
- volumeLimit: 16
- timeLimit: 17
- sGSNChange: 18
- maxChangeCond: 19
- managementIntervention: 20
- rATChange: 22
- mSTimeZoneChange: 23
|
Integer
|
1
|
8f
|
Diagnostics
|
16
|
O
|
This field is included
in the CDR when the PDP context is released and when the option gtpp attribute diagnostics is
configured.
Only the choice of gsm0408Value is
used.
This field is supported for
G-CDRs only (not eG-CDRs).
|
Choice
|
3
|
b0
|
gsm0408Cause
|
16-0
|
M
|
This cause is used in
the Diagnostics field and contains one of the following values:- 36: If the SGSN sends Delete PDP context request
- 38: If GGSN sends delete PDP context request due
to GTP-C/U echo timeout with SGSN
- 40: If the GGSN sends delete PDP context request due
to receiving a RADIUS Disconnect request message.
- 26: If the GGSN sends delete PDP context request for
any other reason
|
Integer
|
1
|
80
|
Record Sequence Number
|
17
|
O
|
A running sequence number
with range 1 through 4294967295 used to link partial records generated
by the GGSN for a specific PDP context (characterized with the same Charging
ID and GGSN address pair). This field is not present if the first
record is also the final record.
|
Integer
|
1-5
|
91
|
Node ID
|
18
|
M
|
This field contains
an identifier string for the node that had generated the CDR.
On the ASR5K GGSN,
this NodeID field is a printable string of the ndddSTRING format:
n: The first digit
is the Sessmgr restart counter having a value between 0 and 7.
ddd: The number of
the sessmgr instance generating the CDR
STRING: This is a configured Node-ID-Suffix
having any string between 1 to16 characters, defined using the gtpp attribute node-id command.
If this node-id-suffix is
not configured, the GGSN uses the GTPP context name as the Node-id-suffix (truncated
to 16 characters).
For G-CDRs, this field
is only included when the option gtpp attribute local-record-sequence-number is configured.
|
IA5string
|
5-20
|
92
|
Local Record Sequence Number
|
20
|
M
|
For each Node ID, this number
with range 1..4294967295 is allocated sequentially for each CDR. This
along with a Node ID uniquely identifies a CDR.
For G-CDRs, this field
is only included when the option gtpp attribute local-record-sequence-number is configured.
|
Integer
|
1-5
|
94
|
APN Selection Mode
|
21
|
M
|
An index indicating
how the APN was selected. The following APN selection mode indexes are
possible:- 0: MS or network provided APN, subscribed verified
- 1: MS provided APN, subscription
not verified
- 2: Network provided APN, subscription
not verified
|
Enumerated (Integer)
|
1
|
95
|
Served MSISDN
|
22
|
M
|
The field tracks the Mobile
Station (MS) ISDN number (MSISDN) of the subscriber which is transparently copied
from the Create PDP Context Request message and is TBCD encoded.
|
BCD encoded octet string
|
1-9
|
96
|
Charging Characteristics
|
23
|
M
|
Lists the charging characteristics applied
to the PDP context.
The GGSN can accept charging characteristics from
the SGSN or AAA or use its own configured value. GGSN configured charging characteristics are
specified as part of the GGSN Service and are applied for G-CDRs
to subscriber PDP contexts through APN templates.
|
Hex value octet string
|
2
|
97
|
Charging Characteristics Selection Mode
|
24
|
O
|
The charging characteristic type
that the GGSN applied to the CDR. The following values for this field
are defined in 3GPP TS 32.298:
- sGSNSupplied (0) - For GGSN only
- subscriptionSpecific
(1) -For SGSN only
- aPNSpecific (2) -
For SGSN only
- homeDefault (3) -
For SGSN and GGSN
- roamingDefault (4)
- For SGSN and GGSN
- visitingDefault (5)
- For SGSN and GGSN
- SGSN supplied: The GGSN is using the charging characteristics supplied by the SGSN.
- Home default: GGSN configured charging characteristics
for home subscribers are used. Home subscribers are those that belong
to the same PLMN as the one on which the GGSN is located.
- Visiting default: GGSN configured charging characteristics
for visiting subscribers are used. Visiting subscribers are those
that belong to a different PLMN than the one on which the GGSN is located.
- Roaming default: GGSN configured charging characteristics
for roaming subscribers are used. Roaming subscribers are those
that are serviced by an SGSN belonging to a different PLMN than
the one on which the GGSN is located.
|
Enumerated (Integer)
|
1
|
98
|
SGSN PLMN Identifier
|
27
|
O
|
RAI (optionally supplied
by SGSN in the GTP create PDP context request) is used as SGSN PLMN Identifier value.
It is omitted if the SGSN does not supply the RAI and is not identified
as a "home" SGSN. For home SGSNs without the RAI a locally configured PLMN-ID
can be sent instead.
|
Octet string
|
3
|
9b
|
Served IMEISV
|
29
|
O
|
This field contains software version
in addition to the IMEI defined before. This software version is encoded
in the last byte replacing the spare digit and filler.
The structure of the
IMEISV is defined in TS 23.003.
|
BCD encoded octet string
|
8
|
9d
|
RAT Type
|
30
|
O
|
This field indicates
the Radio Access Technology (RAT) type currently used by the Mobile Station.
This field is present in the CDR if provided by SGSN.
RAT Type values:
- Reserved: 0
- UTRAN: 1
- GERAN: 2
- WLAN: 3
- Spare: 4-255
|
Integer
|
1
|
9e
|
MS Time Zone
|
31
|
O
|
This field contains
the "Time Zone" IE that the SGSN may provide to the GGSN during the
PDP context activation/modification procedure.
It is transparently copied
from the message into the CDR. The Time Zone is used to indicate
the offset between universal time and local time in steps of 15 minutes
of where the MS current resides. It is coded as specified in 3GPP
TS 29.060 (which refers to 24.008 for the time zone, which again refers
to the TP Service Centre Time Stamp field in 23.040).
|
Octet string
|
2
|
9f1f
|
User Location Information
|
32
|
O
|
The User Location Information for
the MS if provided by the SGSN to the GGSN during the PDP context activation/modification procedure.
Transparently copied from
the PDP context request.
|
Octet string
|
8
|
9f20
|
List of Service Data Volumes
|
34
|
O
|
A list of the changes that
occurred in charging conditions for all service data flows for the PDP context.
|
Sequence
|
Variable length
|
bf22
|
Service Data Volume Block
|
34-0
|
O
|
|
Sequence
|
Variable length
|
30
|
Rating group
|
34-0-1
|
M
|
This is the service flow
identity and has to be used for differentiated evaluation of user's
traffic. This is also known as content-id.
|
Integer
|
1-5
|
81
|
Charging Rulebase name
|
34-0-2
|
M
|
The name of the Rulebase
used for charging. This is the group name of charging rules.
|
IA5string
|
1-63
|
82
|
Result Code
|
34-0-3
|
O
|
The Diameter server
sends result-codes for each of the content-id for which quota is requested.
The GGSN use this to populate the eG-CDR bucket. This is a Mandatory AVP
that comes in response for every quota request for a category.
|
Integer
|
1-5
|
83
|
Local Sequence number
|
34-0-4
|
M
|
A per service data container sequence number.
It starts from 1 for each service, increasing by 1 for each service
date container generated for that service within the lifetime of
this PDP session.
|
Integer
|
1-5
|
84
|
Time of first usage
|
34-0-5
|
M
|
The time stamp for the first
IP packet to be transmitted for the service data flow referred to
the current instance of Service Condition Change.
|
BCD encoded octet string
|
9
|
85
|
Time of last usage
|
34-0-6
|
M
|
The time stamp for the last
IP packet to be transmitted for the service data flow referred to
the current instance of Service Condition Change.
|
BCD encoded octet string
|
9
|
86
|
Usage time
|
34-0-7
|
M
|
The difference between
"time of first usage" and "time of last usage".
|
Integer
|
1-5
|
87
|
Service condition change
|
34-0-8
|
M
|
The reason for closing
the service data container for triggers like SGSN change, QoS change, Rat
change, time and volume triggers, etc.
|
Bit string
|
5
|
88
|
QoS negotiated
|
34-0-9
|
O
|
The negotiated QoS applied for
the service data flow.
In
16.0 and earlier releases, if in the CDRs there are multiple LOSDVs
with same content-id and different service-identifiers, then the
QOS-Info Information Element (IE) is included only in the very first LOSDV
and not in the subsequent LOSDVs unless its previous LOSDV is closed
for QoS change.
In
17.0 and later releases, this implementation has been modified to include
QOS-Info in all LOSDVs having different combination of service-id and
content-id. Thus if there are multiple LOSDVs with same content-id
but different service-id, QOS-Info will be present in every such LOSDV.
|
Octet string
|
4-15
|
89
|
sgsn-Address
|
34-0-10
|
M
|
The valid SGSN IP address
during the service data recording interval.
|
Choice
|
6
|
aa
|
SGSN-IPv4-Binary Address
|
34-0-10-0
|
M
|
The octet string included in
the field "sgsn-Address" includes either control
plane or user plane address of the SGSN in binary coding.
|
Octet string
|
4
|
80
|
SGSN PLMN identifier
|
34-0-11
|
O
|
RAI (optionally supplied
by SGSN in the GTP create PDP context request) is used as SGSN PLMN Identifier value.
It is omitted if the SGSN does not supply the RAI and is not identified
as a "home" SGSN. For home SGSNs without the RAI a locally configured PLMN-ID
can be sent instead.
|
Octet string
|
3
|
8b
|
FBC Data volume uplink
|
34-0-12
|
M
|
The number of octets transmitted during
the use of the packet data services in the uplink direction.
|
Integer
|
1-5
|
8c
|
FBC data volume downlink
|
34-0-13
|
M
|
The number of octets transmitted during
the use of the packet data services in the downlink direction.
|
Integer
|
1-5
|
8d
|
Time of report
|
34-0-14
|
M
|
A time stamp defining the
moment when the service data container is closed.
|
BCD encoded octet string
|
9
|
8e
|
RAT Type
|
34-0-15
|
O
|
The valid radio access technology type
during the service data recording interval.
|
Integer
|
1
|
8f
|
Failurehandling Continue
|
34-0-16
|
O
|
A Boolean expression included
if the failure handling condition has been executed.
This can be either configured
on the GGSN using failure-handling CLI
inside "credit-control" mode or can be received from the server
in the "Credit-Control-Failure-Handling" AVP. Whatever is received
from the server will have higher precedence. There is no negotiation with
the Diameter server in this regard and the GGSN will use whatever the
server provides.
|
Boolean
|
1
|
90
|
Service Identifier
|
34-0-17
|
O
|
The service identifier
may designate an end user service, a part of an end user service,
or an arbitrarily formed group thereof. This field is only included
if reporting is per combination of the rating group and service
id
|
Integer
|
1-5
|
91
|
User Location Information
|
34-0-20
|
O
|
The User Location Information for
the MS if provided by the SGSN to the GGSN during the PDP context activation/modification procedure.
Transparently copied from
the GTP message
|
Octet string
|
8
|
94
|
Time Quota Mechanism
|
34-0-22
|
O
|
Time Quota Mechanism contains
two further subfields and is included if envelope reporting is required:
Time Quota Type identifies the mechanism by which time-based usage should be reported - as defined in TS 32.299.
Base Time Interval identifies the length of the base time interval, for controlling the reporting of time based usage, in seconds
|
Sequence
|
Variable length
|
96
|