6 Charging Data Collection

32.0153G call and event data for the Packet Switched (PS) domain3GPPCharging managementRelease 1999Telecommunications managementTS

6.1 Record contents

Tables 5, 6, 7, 8 and 9 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 (M), 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 (NE). Equipment manufacturers shall be capable of providing all of these fields in order to claim conformance with the present document.

The Mandatory (M), Conditional (C) and Optional (O) 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 (BS) 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. "Network Initiated PDP Context". 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), GGSN Address, 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 CDR data is enabled then the following GSM or 3G 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.

System Type

C

Indicates the type of air interface used, e.g. UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface.

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.

Served MSISDN

O

The primary MSISDN of the subscriber.

SGSN Address

M

The IP address of the current SGSN.

MS Network Capability

O

The mobile station Network Capability.

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 Identifier

O

Cell identity or Service Area Code (SAC) 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 Network Identifier

M

The logical name of the connected access point to the external packet data network (network identifier part of APN).

APN Selection Mode

O

An index indicating how the APN was selected.

PDP Type

M

PDP type, i.e. IP, PPP, IHOSS:OSP

Served PDP Address

C

PDP address of the served IMSI, i.e. IPv4 or IPv6

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.

In GSM, data volumes are in Octets above the SNDCP layer and are separated for uplink and downlink traffic.

In 3G, data volumes are in octets above the GTP-U 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.

Local Record Sequence Number

O

Consecutive record number created by this node. The number is allocated sequentially including all CDR types.

Access Point Name Operator Identifier

M

The Operator Identifier part of the APN.

RNC Unsent Downlink Volume

C

The downlink data volume which the RNC has not sent to MS.

CAMEL Information

C

Set of CAMEL information related to PDP context. For more information see Description of Record Fields.

Charging Characteristics

C

The Charging Characteristics flag retrieved from subscriber’s data as described in subclause 6.1.6.5.

6.1.2 GPRS charging data in GGSN (G-CDR)

If the collection of CDR data is enabled then the following GSM or 3G 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.

Served IMSI

M

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

Served MSISDN

O

The primary MSISDN of the subscriber.

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 Network Identifier

M

The logical name of the connected access point to the external packet data network (network identifier part of APN).

APN Selection Mode

O

An index indicating how the APN was selected.

PDP Type

M

PDP type, i.e. IP, PPP, or IHOSS:OSP

Served PDP Address

C

PDP address, i.e. IPv4 or IPv6

Dynamic Address Flag

C

Indicates whether served PDP address is dynamic, which 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.

In GSM, data volumes are in octets above the GTP layer and are separated for uplink and downlink traffic.

In 3G, data volumes are in octets above the GTP-U 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.

Local Record Sequence Number

O

Consecutive record number created by this node. The number is allocated sequentially including all CDR types.

Charging Characteristics

C

The Charging Characteristics flag retrieved from subscriber’s data as described in subclause 6.1.6.5.

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 GSM or 3G 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.

Served MSISDN

O

The primary MSISDN of the subscriber.

SGSN Address

M

The IP address of the current SGSN.

MS Network Capability

O

The mobile station network capability.

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 Identifier

O

The Cell Identity or Service Area Code (SAC) 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.

Local Record Sequence Number

O

Consecutive record number created by this node. The number is allocated sequentially including all CDR types.

Charging Characteristics

C

The Charging Characteristics flag set used by the SGSN.

System Type

C

Indicates the type of air interface used, e.g. UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface.

CAMEL Information

C

Set of CAMEL related to Attach/Detach session. For more information see Description of Record Fields.

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 the 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 Network Capability

M

The mobile station network capability.

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 Identifier

O

The Cell Identity or Service Area Code (SAC) 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.

Node ID

O

Name of the recording entity.

Local Record Sequence Number

O

Consecutive record number created by this node. The number is allocated sequentially including all CDR types.

Charging Characteristics

C

The Charging Characteristics flag set used by the SGSN.

System Type

C

Indicates the type of air interface used, e.g. UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface.

Destination Number

O

The destination short message subscriber number.

CAMEL Information

C

Set of CAMEL information related to SMS session. For more information see Description of Record Fields.

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 the 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 Network Capability

M

The mobile station network capability

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 Identifier

O

The Cell Identity or Service Area Code (SAC) 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.

Node ID

O

Name of the recording entity.

Local Record Sequence Number

O

Consecutive record number created by this node. The number is allocated sequentially including all CDR types.

Charging Characteristics

C

The Charging Characteristics flag set used by the SGSN.

System Type

C

Indicates the type of air interface used, e.g. UTRAN. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface.

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 (APN) Network/Operator Identifier

These fields contain the actual connected Access Point Name Network/Operator Identifier determined either by MS, SGSN or modified by CAMEL service. An APN can also be a wildcard, in which case the SGSN selects the access point address.

The APN Network Identifier containing more than one label corresponds to an Internet domain name. The APN Operator Identifier is composed of three labels. The first and second labels together shall uniquely identify the GPRS PLMN (e.g. "operator name>.<operator group>.gprs").

See 3GPP TS 23.003 [4] and 3GPP TS 23.060 [8] for more information about APN format and access point decision rules.

6.1.6.2 APN Selection Mode

This field indicates how the SGSN selected the APN to be used. The values and their meaning are as specified in 3GPP TS 29.060 [22] subclause 7.9 ‘Information elements’.

6.1.6.3 CAMEL Information

This field includes following CAMEL information elements for PDP context (S-CDR), Attach/Detach session (M-CDR) and Mobile originated SMS (S-SMO-CDR) if corresponding CAMEL service is activated.

  • CAMEL Access Point Name NI (S-CDR)

This field contains the network identifier part of APN before modification by the SCF.

  • CAMEL Access Point Name OI (S-CDR)

This field contains the operator identifier part of APN before modification by the SCF.

  • CAMEL Calling Party Number (S-SMO-CDR)

This field contains the Calling Party Number modified by the CAMEL service.

  • CAMEL Destination Subscriber Number (S-SMO-CDR)

This field contains the short message Destination Number modified by the CAMEL service.

  • CAMEL SMSC Address (S-SMO-CDR)

This field contains the SMSC address modified by the CAMEL service.

  • SCF address (S-CDR, M-CDR, S-SMO-CDR)

This field identifies the CAMEL server serving the subscriber. Address is defined in HLR as part of CAMEL subscription information

  • Service key (S-CDR, M-CDR, S-SMO-CDR)

This field identifies the CAMEL service logic applied. Service key is defined in HLR as part of CAMEL subscription information.

  • Default Transaction/SMS Handling (S-CDR, M-CDR, S-SMO-CDR)

This field indicates whether or not a CAMEL encountered default GPRS- or SMS-handling. This field shall be present only if default call handling has been applied. Parameter is defined in HLR as part of CAMEL subscription information.

  • Free Format Data (S-CDR, M-CDR, S-SMO-CDR)

This field contains charging information sent by the gsmSCF in the Furnish Charging Information GPRS messages as defined in 3GPP TS 29.078 [20]. The data can be sent either in one FCI message or several FCI messages with append indicator. This data is transferred transparently in the CAMEL sections of the relevant call records.

If the FCI is received more then once during one CAMEL call, the append indicator defines whether the FCI information is appended to previous FCI and stored in the relevant record or the information of the last FCI received is stored in the relevant record (the previous FCI information shall be overwritten).

In the event of partial output the currently valid ‘Free format data’ is stored in the partial record.

  • FFD Append Indicator (S-CDR, M-CDR)

This field contains an indicator whether CAMEL free format data is to be appended to free format data stored in previous partial CDR. This field is needed in CDR post processing to sort out valid free format data for that call leg from sequence of partial records. Creation of partial records is independent on received FCIs and thus valid free format data may be divided to different partial records.

If field is missing then free format data in this CDR replaces all received free format data in previous CDRs. Append indicator is not needed in the first partial record. In following partial records indicator shall get value true if all FCIs received during that partial record have append indicator. If one or more of the received FCIs for that call leg during the partial record do not have append indicator then this field shall be missing.

  • Level of CAMEL services (S-CDR, M-CDR)

This field describes briefly the complexity of CAMEL invocation. Categories are same than in circuit switched services and measure of resource usage in VPLMN requested by HPLMN.

– ‘Basic’ means that CAMEL feature is invoked during the PDP context activation phase only (e.g. to modify APN_NI / APN_OI).

– ‘Call duration supervision’ means that PDP context duration or volume supervision is applied in the gprsSSF of the VPLMN (Apply Charging message is received from the gsmSCF)

  • Number of DP encountered (S-CDR, M-CDR)

This field indicates how often armed CAMEL detection points (TDP and EDP) were encountered and is a measure of signalling between VPLMN and CAMEL service and complements ‘Level of CAMEL service’ field.

  • SMSReferenceNumber (S-SMO-CDR)

This parameter contains the SMS Reference Number assigned to the Short Message by the SGSN.

6.1.6.4 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 or 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.5 Charging Characteristics

The Charging Characteristics field as defined in Figure 8a allows the operator to apply different kind of charging methods for the CDRs. The N flag in the Charging Characteristics indicates normal charging, the P flag indicates prepaid charging, the F flag indicates flat rate charging and the H flag indicates charging by hot billing. The 2nd octet is reserved for future use. One or more of the flags shall be set according to the charging characteristics received from the HLR and transmitted by the CDR generating node over the Ga interface.

Figure 8a: Charging Characteristics flags

Charging Characteristics in S-CDR is determined by the SGSN as follows:

  • If a "PDP context Charging Characteristics" is present in the subscriber’s data for this PDP context, than it shall be used,
  • If there is no "PDP context Charging Characteristics" but a "Subscribed Charging Characteristics" is present in the subscriber’s data, the "Subscribed Charging Characteristics" shall be used.

Charging Characteristics in G-CDR corresponds to the "Charging characteristics" information of the PDP context data in the GGSN.

6.1.6.6 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.7 Destination Number

This field contains short message Destination Number requested by the user.

6.1.6.8 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 3GPP TS 29.002 [21];

– a Cause from 3GPP TS 24.008 [13].

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

6.1.6.9 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.10 Dynamic Address Flag

This field indicates that PDP address has been dynamically allocated for that particular PDP context. This 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.11 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.12 GGSN Address/GGSN Address Used

These fields are the current serving GGSN IP address for the control plane.

6.1.6.13 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 Time Stamp.

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 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". In addition to the QoS Negotiated parameter the QoS Requested parameter is present in following containers if the change condition is "QoS change" and the QoS change was initiated by the MS via a PDP context modification procedure.

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 Requested = QoS2 (if requested by the MS)

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):

Table :

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 counted already includes the IP PDP bearer protocols i.e. IP, TCP or UDP Headers.

The data volume counted in the SGSN covers the amount of data transferred in the SNDCP PDUs. Therefore the data counted already includes the overheads of any PDP bearer protocols.

The amount of data counted in the 3G-GGSN shall be the data volume sent over the GTP-U layer. Therefore the data counted already includes the overheads of any PDP bearer protocols.

The data volume counted in the 3G-SGSN covers the amount of data transferred in the GTP-U PDUs. Therefore the data counted already includes the overheads of any PDP bearer protocols.

In GSM, 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;

  • In GSM, for PDP contexts using LLC in acknowledged mode a 2G-SGSN shall only update the PDP CDR at the reception of the acknowledgement by the MS of the correct reception of a downstream packet. 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. In UMTS, the not transferred downlink data ‘RNC Unsent Downlink Volume’ can be accounted for in the S-CDR, i.e. data that the RNC has either discarded or forwarded during handover.
  • In UMTS, The not transferred downlink data ‘RNC Unsent Downlink Volume’ can be accounted for in the S‑CDR , i.e. data that the RNC has either discarded or forwarded during handover.

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

6.1.6.14 Local Record Sequence Number

This field includes a unique record number created by this node. The number is allocated sequentially including all CDR types. The number is unique within one node, which is identified either by field Node ID or by record-dependent node address (SGSN address, GGSN address, Recording Entity).

The field can be used e.g. to identify missing records in post processing system.

6.1.6.15 Message reference

This field contains a unique message reference number allocated by the Mobile Station (MS) 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 3GPP TS 23.040 [7].

6.1.6.16 MS Network Capability

This MS Network Capability field contains the MS network capability value of the MS network capability information element of the served MS on PDP context activation or on GPRS attachment as defined in 3GPP TS 24.008 [13].

6.1.6.17 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.18 Node ID

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

6.1.6.19 PDP Type

This field defines the PDP type, e.g. IP, PPP, or IHOSS:OSP (see 3GPP TS 29.060 [22] for exact format).

6.1.6.20 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.

If a pre-Release ’99 only capable terminal is served, the QoS profile consists of five (5) attributes as follows: reliability, delay, precedence, peak throughput and mean throughput. The encoding of this QoS profile shall be in accordance with GSM 12.15.

In Release 99, the QoS profile consists of the above 2G parameters plus the following UMTS attributes: Traffic class (‘conversational’, ‘streaming’, ‘interactive’, ‘background’), Maximum bit-rate (kbps), Delivery order (y/n), Maximum SDU size (octets), SDU error ratio, Residual bit error ratio, Delivery of erroneous SDUs (y/n/-), Transfer delay (ms), Traffic handling priority, Allocation/Retention Priority. This QoS profile shall be encoded according to the "Quality of Service (QoS) Profile" parameter specified in 3GPP TS 29.060 [22].

6.1.6.21 Record Extensions

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

6.1.6.22 Record Opening Time

This field contains the time stamp when the record is opened (see 3GPP TS 32.005 [23] 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.23 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". The Record Sequence Number is missing if the 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.24 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.25 Recording Entity Number

This field contains the ITU-T E.164 number assigned to the entity that produced the record. For further details see 3GPP TS 23.003 [4].

6.1.6.26 RNC Unsent Downlink Volume

This field contains the unsent downlink volume that the RNC has either discarded or forwarded to 2G-SGSN and already included in S-CDR. This field is present when RNC has provided unsent downlink volume count at RAB release and can be used by a downstream system to apply proper charging for this PDP context.

6.1.6.27 Routing Area Code/Cell Identifier/Change of location

The location information contains a combination of the Routing Area Code (RAC) and an optional Cell Identifier of the routing area and cell in which the served party is currently located. In 2G domain the Cell Identifier is defined by the Cell Identity (CI) and in 3G domain by the Service Area Code (SAC). 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 3G TS 24.008 [13] and the SAC according 3GPP TS 25.413 [15].

6.1.6.28 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 3GPP TS 23.003 [4].

6.1.6.29 Served IMSI

This field 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 3GPP TS 23.003 [4].

6.1.6.30 Served MSISDN

This field contains the Mobile Station (MS) 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 an MOC record will be the primary MSISDN of the calling party.

The structure of the MSISDN is defined in 3GPP TS 23.003 [4].

6.1.6.31 Served PDP Address

This field contains the PDP address of the served IMSI. This is a network layer address i.e. of type IP version 4, IP version 6. The address for each PDP type is allocated either temporarily or permanently (see "Dynamic Address Flag" field in subclause 6.1.6.10 ). This parameter shall be present except when both the PDP type is PPP and dynamic PDP address assignment is used.

6.1.6.32 Service Centre Address

This field contains a ITU-T E.164 number identifying a particular service centre e.g. Short Message Service (SMS) centre (see 3GPP TS 23.040 [7]).

6.1.6.33 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.34 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.

6.1.6.35 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.36 Short Message Service (SMS) 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 3GPP TS 29.002). Note that this field is only provided if the attempted delivery was unsuccessful.

6.1.6.37 System Type

This field is present conditionally, indicating the use of the UTRAN or GERAN air-interface for the provision of service recorded by this CDR. In the case of service provided by a GSM air interface, this field is not present.

NOTE: The ASN.1 contains a value of "unknown" which may be used in other domains but not in the PS domain.