6 Charging Data Collection

12.153GPPGeneral Packet Radio Service (GPRS)GPRS ChargingRelease 1997TS

6.1 Record contents

The following tables describe the contents of each of the call and event records generated by the GSNs. Each table contains the name of the field, a key indicating whether or not the field is mandatory, and a description of the contents.

The key field has the following meaning:

M This field is mandatory and always present. Any exceptions to this rule are explicitly described.

C This field is only available under certain conditions. If available the field is present.

The conditions under which the field is available are individually described.

O This field is optional and configurable either via additional TMN management functions or manufacturer specific means. For the avoidance of doubt, optional does not mean that the parameter is not supported by the network element. Equipment manufacturers shall be capable of providing all of these fields in order to claim conformance with the present document.

The mandatory, conditional, and optional designations are described at the GSN / CGF interface (see exceptions below) and may be available at the CGF / BS interface to meet the Billing System requirement.

All the mandatory or conditional fields are not required in all CDRs at the GSN / CGF interface in the following cases:

– Each information element is included at least in one record. This applies for situations where partial records are produced between the GSN and CGF, and the information has not changed, e.g. "GGSN Address Used". The following primary identifier fields are however needed in all records: Record Type, Served IMSI, and if the CDR is related to a PDP context (G-CDR and S-CDR), then also the Charging ID.

– GSNs are configured to produce only part of the described information. This applies for situations where record types are not produced or some functional component is excluded from the records such as whole M-CDR or time based charging in G-CDR.

In the case of a distributed CGF the following charging data records are not applicable at the GSN / CGF interface and proprietary solutions or variations to the present document are allowed. However, the described information content needs to be supported to be able to conform to the requirements towards the BS.

6.1.1 GPRS charging data in SGSN (S-CDR)

If the collection of SGSN data is enabled then the following GPRS SGSN data shall be available for each PDP context.

Table 5: GPRS SGSN PDP context data

Field

Description

Record Type

M

GPRS SGSN PDP context record.

Network initiated PDP context

C

Present if this is a network initiated PDP context.

Anonymous Access Indicator

C

Set to true to indicate anonymous access (and that the Served IMSI is not supplied)

Served IMSI

M

IMSI of the served party (if Anonymous Access Indicator is FALSE or not supplied).

Served IMEI

C

The IMEI of the ME, if available.

SGSN Address

M

The IP address of the current SGSN.

MS Classmark

O

The mobile station classmark employed.

Routing area

O

Routing area at the time of the record creation.

Local Area Code

O

Location area code at the time of the record creation.

Cell Identity

O

Cell id at the time of the record creation.

Charging ID

M

PDP context identifier used to identify this PDP context in different records created by GSNs

GGSN Address Used

M

The IP address of the GGSN currently used. The GGSN address is always the same for an activated PDP.

Access Point Name

M

The logical name of the connected access point to the external packet data network.

PDP Type

M

PDP type, e.g. X.25 or IP

Served PDP address

M

PDP address of the served IMSI, e.g. an IPv4, IPv6 or X.121.

List of traffic data volumes

M

A list of changes in charging conditions for this PDP context, each time stamped. Charging conditions are used to categorise traffic volumes, such as per QoS/tariff period. Initial and subsequently changed QoS and corresponding data values are listed. Data volumes are in Octets above the SNDCP layer and are separated for uplink and downlink traffic.

Record opening time

M

Time stamp when PDP context activation is created in this SGSN

or record opening time on following partial records

Duration

M

Duration of this record in the SGSN.

SGSN change

C

Present if this is first record after SGSN change.

Cause for record closing

M

The reason for the release of record from this SGSN.

Diagnostics

O

A more detailed reason for the release of the connection.

Record Sequence number

C

Partial record sequence number in this SGSN. Only present in case of partial records.

Node ID

O

Name of the recording entity

Record extensions

O

A set of network/ manufacturer specific extensions to the record.

6.1.2 GPRS charging data in GGSN (G-CDR)

If the collection of GGSN data is enabled then the following GPRS GGSN data shall be available for each PDP context.

Table 6: GPRS GGSN PDP context data

Field

Description

Record Type

M

GPRS GGSN PDP context record.

Network initiated PDP context

C

Present if this is a network initiated PDP context.

Anonymous Access Indicator

C

Set to true to indicate anonymous access (and that the Served IMSI is not supplied).

Served IMSI

M

IMSI of the served party (if Anonymous Access Indicator is FALSE or not supplied).

GGSN Address

M

The IP address of the GGSN used.

Charging ID

M

PDP context identifier used to identify this PDP context in different records created by GSNs

SGSN Address

M

List of SGSN addresses used during this record.

Access Point Name

M

The logical name of the connected access point to the external packet data network.

PDP Type

M

PDP type, e.g. X.25 or IP

Served PDP Address

M

PDP address, e.g. an IPv4, IPv6 or X.121.

Remote PDP Address

O

List of PDP addresses of the remote host or DTE e.g. an IPv4, IPv6, or X.121 (Included if the PDP type is X.25)

Dynamic Address Flag

C

Indicates whether served PDP address is dynamic, that is allocated during PDP context activation.

List of traffic data volumes

M

A list of changes in charging conditions for this PDP context, each time stamped. Charging conditions are used to categorise traffic volumes, such as per tariff period. Initial and subsequently changed QoS and corresponding data values are listed. Data volumes are in octets above the GTP layer and are separated for uplink and downlink traffic.

Record opening time

M

Time stamp when this record was opened.

Duration

M

Duration of this record in the GGSN .

Cause for record closing

M

The reason for the release of record from this GGSN .

Diagnostics

O

A more detailed reason for the release of the connection.

Record Sequence number

C

Partial record sequence number, only present in case of partial records.

Node ID

O

Name of the recording entity.

Record extensions

O

A set of network/ manufacturer specific extensions to the record.

SGSN PLMN Identifier

O

SGSN PLMN Identifier (MCC and MNC) used during this record.

6.1.3 GPRS mobile station mobility management data in SGSN (M-CDR)

If the collection of MS mobility management data is enabled then GPRS SGSN shall start collecting information each time the mobile is attached to the SGSN.

Table 7: GPRS SGSN mobile station mobility management data

Field

Description

Record Type

M

GPRS SGSN mobility management record.

Served IMSI

M

IMSI of the MS.

Served IMEI

C

The IMEI of the ME, if available.

SGSN Address

M

The IP address of the current SGSN.

MS Classmark

O

The mobile station classmark employed.

Routing area

O

Routing area at the time of the record creation..

Local Area Code

O

Location area code at the time of record creation.

Cell Identity

O

Cell id at the time of the record creation.

Change of Location

O

A list of changes in Routing Area Identity, each time stamped.

Record opening time

M

Timestamp when this record was opened.

Duration

O

Duration of this record.

SGSN change

C

Present if this is first record after SGSN change.

Cause for record closing

M

The reason for the release of the record in this SGSN.

Diagnostics

O

A more detailed reason for the release of the connection.

Record Sequence number

C

Partial record sequence number in this SGSN, only present in case of partial records.

Node ID

O

Name of the recording entity.

Record extensions

O

A set of network/ manufacturer specific extensions to the record.

6.1.4 GPRS MO SMS data in SGSN (S-SMO-CDR)

If enabled, an S-SMO-CDR SGSN Mobile originated SMS record shall be produced for each short message sent by a mobile subscriber via SGSN.

Table 8: SGSN Mobile originated SMS record

Field

Description

Record Type

M

SGSN Mobile originated SMS.

Served IMSI

M

The IMSI of the subscriber.

Served IMEI

O

The IMEI of the ME, if available.

Served MSISDN

O

The primary MSISDN of the subscriber.

MS Classmark

M

The mobile station classmark.

Service Centre

M

The address (E.164) of the SMS-service centre.

Recording Entity

M

The E.164 number of the SGSN.

Location Area Code

O

The Location Area Code from which the message originated.

Routing Area Code

O

The Routing Area Code from which the message originated.

Cell Identity

O

The Cell Identity from which the message originated.

Event Time stamp

M

The time at which the message was received by the SGSN from the subscriber.

Message Reference

M

A reference, provided by the MS uniquely identifying this message.

SMS Result

C

The result of the attempted delivery if unsuccessful.

Record extensions

O

A set of network/ manufacturer specific extensions to the record.

6.1.5 GPRS MT SMS data in SGSN (S-SMT-CDR)

If enabled, an SGSN Mobile terminated SMS record shall be produced for each short message received by a mobile subscriber via SGSN.

Table 9: SGSN Mobile terminated SMS record

Field

Description

Record Type

M

SGSN Mobile terminated SMS.

Served IMSI

M

The IMSI of the subscriber.

Served IMEI

O

The IMEI of the ME, if available.

Served MSISDN

O

The primary MSISDN of the subscriber.

MS Classmark

M

The mobile station classmark.

Service Centre

M

The address (E.164) of the SMS-service centre.

Recording Entity

M

The E.164 number of the SGSN.

Location Area Code

O

The Location Area Code to which the message was delivered.

Routing Area Code

O

The Routing Area Code to which the message was delivered.

Cell Identity

O

The Cell Identity to which the message was delivered.

Event Time stamp

M

Delivery time stamp, time at which message was sent to the MS by the SGSN.

SMS Result

C

The result of the attempted delivery if unsuccessful.

Record extensions

O

A set of network/ manufacturer specific extensions to the record.

6.1.6 Description of Record Fields

This subclause contains a brief description of each field of the CDRs described in the previous subclause.

6.1.6.1 Access Point Name

This field contains the logical Access Point Name used to determine the actual connected access point. APN comprises of mandatory network identifier and optional operator identifier. APN can also be a wildcard, in which case SGSN selects the access point address. See GSM 09.60 [22] and GSM 03.60 [8] for more information about APN format and access point decision rules.

6.1.6.2 Cause for record closing

This field contains a reason for the release of the CDR including the following:

– normal release: PDP context release or GPRS detach;

– partial record generation: data volume limit, time (duration) limit, SGSN change of maximum number of changes in charging conditions;

– abnormal termination (PDP or MM context);

management intervention (request due to O&M reasons).

A more detailed reason may be found in the diagnostics field.

6.1.6.3 Charging ID

This field is a charging identifier which can be used together with GGSN address to identify all records produced in SGSN(s) and GGSN involved in a single PDP context. Charging ID is generated by GGSN at PDP context activation and transferred to context requesting SGSN. At inter-SGSN routing area update charging ID is transferred to the new SGSN as part of each active PDP context.

Different GGSNs allocate the charging ID independently of each other and may allocate the same numbers. The CGF and/or BS may check the uniqueness of each charging ID together with the GGSN address and optionally (if still unambiguous) with the record opening time stamp.

6.1.6.4 Diagnostics

This field includes a more detailed technical reason for the release of the connection and may contain one of the following:

– a MAP error from GSM 09.02 [17];

– a Cause from GSM 04.08 [16];

The diagnostics may also be extended to include manufacturer and network specific information.

6.1.6.5 Duration

This field contains the relevant duration in seconds for PDP contexts (S-CDR, G-CDR, and attachment (M-CDR)). For partial records this is the duration of the individual partial record and not the cumulative duration.

It should be noted that the internal time measurements may be expressed in terms of tenths of seconds or even milliseconds and, as a result, the calculation of the duration may result in the rounding or truncation of the measured duration to a whole number of seconds.

Whether or not rounding or truncation is to be used is considered to be outside the scope of the present document subject to the following restrictions:

1) A duration of zero seconds shall be accepted providing that the transferred data volume is greater than zero.

2) The same method of truncation/rounding shall be applied to both single and partial records.

6.1.6.6 Dynamic Address Flag

This field indicates that PDP address has been dynamically allocated for that particular PDP context. Field is missing if address is static i.e. part of PDP context subscription. Dynamic address allocation might be relevant for charging e.g. the duration of PDP context as one resource offered and possible owned by network operator.

6.1.6.7 Event time stamps

These fields contain the event time stamps relevant for each of the individual record types.

All time-stamps include a minimum of date, hour, minute, and second.

6.1.6.8 GGSN address/GGSN address used

These fields contain one IP address of GGSN.

The S-CDR fields contain a single address of current GGSN used.

The G-CDR fields contain an address of current GGSN.

6.1.6.9 List of traffic data volumes

This list includes one or more containers, which each include the following fields:

Data volume uplink, data volume downlink, change condition and change time.

Data volume includes the number of octets transmitted during the use of packet data services.

Change condition defines the reason for closing the container (see subclauses 5.7.1 and 5.7.3), such as tariff time change, QoS change or closing the CDR. Change time is a time stamp which defines the moment when the new volume counts are started or CDR is closed. All the active PDP contexts do not need to have exactly the same time stamp e.g. due to same tariff time change (variance of the time stamps is implementation and traffic load dependent and is out of the scope of standardisation).

First container includes following optional fields: QoS Requested (not in G-CDR) and QoS Negotiated. In following containers QoS Negotiated is present if previous change condition is QoS change.

Following is an example of a list, which has three containers (sets of volume counts) caused by one QoS change and one tariff time change.

Table 10: Example list of traffic data volumes

QoS Requested = QoS1

QoS Negotiated = QoS1

Data Volume Uplink = 1

Data Volume Downlink = 2

Change Condition = QoS change

Time Stamp = TIME1

QoS Negotiated = QoS2

Data Volume Uplink = 5

Data Volume Downlink = 6

Change Condition = Tariff change

Time Stamp = TIME2

Data Volume Uplink = 3

Data Volume Downlink = 4

Change Condition = Record closed

Time Stamp = TIME3

First container includes initial QoS values and corresponding volume counts. Second container includes new QoS values and corresponding volume counts before tariff time change. Last container includes volume counts after the tariff time change. Following total volume counts can be itemised (tariff1 is used before and tariff2 after the tariff time change):

Container

QoS1+Tariff1

uplink = 1, downlink = 2

1

QoS2+Tariff1

uplink = 5, downlink = 6

2

QoS2+Tariff2

uplink = 3, downlink = 4

3

QoS1

uplink = 1, downlink = 2

1

QoS2

uplink = 8, downlink = 10

2+3

Tariff1

uplink = 6, downlink = 8

1+2

Tariff2

uplink = 3, downlink = 4

1

The amount of data counted in the GGSN shall be the data volume sent over the GTP layer. Therefore the data countedalready includes the IP/X.25 PDP bearer protocols.

The data volume counted in the SGSN covers the amount of data transferred in the SNDCP PDUs. Therefore the data counted already includes the IP/X.25 PDP bearer protocols.

In order to avoid that downstream packets transmitted from the old SGSN to the new SGSN at inter SGSN RA update induce the increase of the PDP CDR downstream volume counters in both SGSN the following rule is followed:

– for PDP contexts using LLC in unacknowledged mode: an SGSN shall update the PDP CDR when the packet has been sent by the SGSN towards the MS.

– for PDP contexts using LLC in acknowledged mode : an SGSN shall only update the PDP CDR at the reception of the acknowledgement of the correct reception of a downstream packet by the MS. This implies that for downstream packets under transmission at inter SGSN RA update a packet sent by the old SGSN actually received by the MS and acknowledged by the MS towards the new SGSN through the RA update complete message induces the update of the PDP CDR record by the new SGSN.

Data volumes retransmitted (by RLC or LLC) due to poor radio link conditions shall not be counted.

6.1.6.10 Message reference

This field contains a unique message reference number allocated by the mobile station when transmitting a short message to the service centre. This field corresponds to the TP-Message-Reference element of the SMS_SUBMIT PDU defined in GSM 03.40.

6.1.6.11 Mobile station classmark

This MS classmark field contains the mobile station classmark 4 employed by the served MS on PDP context activation or on GPRS attachment as defined in GSM 04.08 [16].

6.1.6.12 Network initiated PDP context

This field indicates that PDP context is network initiated. The field is missing in case of mobile activated PDP context.

6.1.6.13 Node ID

This field contains an optional operator configurable identifier string for the node which generated the CDR.

6.1.6.14 PDP Type

This field defines the PDP type, e.g. X.25 or IP (see GSM 09.60 for exact format).

6.1.6.15 QoS Requested/QoS Negotiated

Quality of Service Requested contains the QoS wanted by MS at PDP context activation. QoS Negotiated indicates the applied QoS accepted by the network.

The QoS profile consists of 5 attributes: reliability, delay, precedence, peak throughput and mean throughput. See GSM 03.60 [8] for more details.

6.1.6.16 Record extensions

The field enables network operators and/or manufacturers to add their own extensions to the standard record definitions. This field contains a set of "management extensions" as defined in CCITT X.721 [5].

6.1.6.17 Record opening time

This field contains the time stamp when the record is opened (see GSM 12.05 for exact format).

Record opening reason does not have a separate field. For G-CDR and M-CDR it can be derived from the field "Sequence number" i.e. missing field or value one means activation of PDP context and GPRS attachment. For S-CDR also field "SGSN change" need to be taken into account.

6.1.6.18 Record Sequence number

This field contains a running sequence number employed to link the partial records generated in the SGSN/GGSN for a particular PDP context (characterised with same the Charging ID and GGSN address pair). In the S-CDR the sequence number is always started from one after inter-SGSN routing area update, see field "SGSN change". Sequence number is missing if record is the only one produced in the SGSN/GGSN for the PDP context (e.g. inter-SGSN routing area update can result to two S-CDRs without sequence number and field "SGSN update" present in the second record).

6.1.6.19 Record type

The field identifies the type of the record e.g. S-CDR, G-CDR, M-CDR, S-SMO-CDR and S-SMT-CDR.

6.1.6.20 Recording entity number

This field contains the ITU-T Recommendation E.164 number assigned to the entity that produced the record. For further details see GSM 03.03 [14].

6.1.6.21 Remote PDP address

Remote PDP address may be used if PDP type is ITU-T Recommendation X.25. This parameter is not used if the PDP type is IP. Itemised volume billing is available per Access Point Name. This field contains a list of connected remote PDP addresses.

6.1.6.22 Routing Area Code/Cell Identity/Change of location

The location information contains a combination of the Routing Area Code (RAC) and optionally Cell Identity (CI) of the routing area and cell in which the served party is currently located. Any change of location (i.e. Routing area change) may be recorded in the change of location field including the time at which the change took place.

The change of location field is optional and not required if partial records are generated when the location changes.

The RAC and (optionally) CI are coded according to GSM 04.08 [16].

6.1.6.23 Served IMEI

This field contains the international mobile equipment identity (IMEI) of the equipment served. The term "served" equipment is used to describe the ME involved in the transaction recorded e.g. the called ME in the case of a network initiated PDP context.

The structure of the IMEI is defined in GSM 03.03 [14].

6.1.6.24 Served IMSI

This fields contains the international mobile subscriber identity (IMSI) of the served party. The term "served" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the calling subscriber in case of a mobile initiated PDP context.

The structure of the IMSI is defined in GSM 03.03 [14].

6.1.6.25 Served MSISDN

This fields contains the mobile station ISDN number (MSISDN) of the served party. The term "served" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the called subscriber in case of an MTC record. In case of multi-numbering the MSISDN stored in a MOC record will be the primary MSISDN of the calling party.

The structure of the MSISDN is defined in GSM 03.03 [14].

6.1.6.26 Served PDP address

This field contains the PDP address of the served IMSI. This is a network layer address e.g. of type IP version 4, IP version 6 or X.121. The address for each PDP type is allocated either temporarily or permanently, see field "Dynamic Address Flag".

6.1.6.27 Service centre address

This field contains a CCITT E.164 number identifying a particular service centre e.g. short message service centre (see GSM 03.40).

6.1.6.28 SGSN address

These fields contain one or several IP addresses of SGSN.

The S-CDR fields contain single address of current SGSN and GGSN used.

The G-CDR fields contains the address of the current GGSN and a list of SGSNs, which have been connected during the record (SGSN change due to inter SGSN routing area update).

The M-CDR only contains the address of the current SGSN. The M-CDR does not identify any information related to active PDP context(s) and thus does not know connected (used) GGSN(s).

6.1.6.29 SGSN change

This field is present only in the S-CDR to indicate that this is the first record after an inter-SGSN routing area update.

SGSN PLMN Identifier

This field contains a SGSN PLMN Identifier (Mobile Country Code and Mobile Network Code), for the SGSNs which have been connected during the record. This implies that when the MS moves to another PLMN, the G-CDR has to be closed.

The MCC and MNC are coded as described for ‘Routing Area Identity’ in [22].

6.1.6.31 Short message service result

This field contains the result of an attempt to deliver a short message either to a service centre or to a mobile subscriber (see GSM 09.02). Note that this field is only provided if the attempted delivery was unsuccessful.