5.1.2 Bearer level CDR parameters

32.2983GPPCharging Data Record (CDR) parameter descriptionCharging managementRelease 18Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1.2.0 General

This clause contains the description of the CDR parameters that are specific to the bearer level CDR types.
This comprises the CDR types from the Circuit Switched (CS) domain (TS 32.250 [10]), the Packet Switched (PS) domain, i.e. GPRS (TS 32.251 [11]).

5.1.2.1 CS domain CDR parameters

5.1.2.1.0 Introduction

This clause contains the description of the CDR parameters that are specific to the CS domain CDR types as specified in TS 32.250 [10].

5.1.2.1.1 Additional Charging Information

This field consists of two parts, a charge indicator and additional charging parameters. The charge indicator is derived from the information contained within the ISUP "backward call indicator" and may be used to store a charge indicator (charge/no charge) received from another network node. The additional charging parameters are non-standard and intended to permit the inclusion of further charging information received from Intelligent Network and/or Value Added Service nodes.

5.1.2.1.2 AoC parameters/change of AoC parameters

The AoC parameter field contains the set of charge advice (AoC) parameters sent to the MS on call set-up. If further sets of parameters are sent during the call, as a result of a tariff switch-over for example, then this may be recorded in the Change of AoC Parameter field including the time at which the change occurred.

It should be noted that the Change of AoC Parms. field is optional and not required if partial records are generated on tariff switch-over.

The AoC parameters are defined in TS 22.024 [104].

5.1.2.1.3 Basic Service/change of service/ISDN Basic Service

The basic service field contains the code of the basic service employed on call set-up. Any alteration to the basic service during the connection may be recorded in the change of service field including the time at which the change took place.

The change of service field is optional and may be omitted if partial records are created whenever the basic service is changed.

The coding of basic services is defined in detail in TS 29.002 [214].

In the case of the transit record the GSM basic service employed is generally not available. However, if the device on which the call originates/terminates is connected via ISDN digital subscriber signalling then the appropriate ISDN basic service code may be recorded in the record. One possible example includes the direct connection of an ISDN PABX to an MSC/VLR.

5.1.2.1.4 Call duration

This field contains the relevant call duration in seconds. For incomplete calls (call attempts) the relevant duration is the call holding time from the seizure to the release of the traffic channel. For complete (answered) calls this is the chargeable duration from answer to release of the traffic channel. For partial records this is the duration of the individual partial record and not the cumulative duration of the call.

It should be noted that the time stamps may be expressed in terms of tenths of seconds or even milliseconds and, as a result, the calculation of the call 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 call duration of zero seconds shall not be accepted.

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

If CAMEL is invoked for the call and a control relationship is existing, the call might continue after a RELEASE or a DISCONNECT from the called party side received by the gsmSSF. The call duration of the incoming leg is stored in the main body of the call record. For each outgoing leg the call duration is stored in the respective ‘CAMELInformation’ module. If a call leg does not reach answer status and attempt charging is enabled a ‘CAMELInformation’ module containing the holding time is generated.

An example of how to use the call duration and the timestamps is given in figure 5.1.2.1.4.1. It shows a CAMEL controlled mobile originated follow-on scenario. The uppermost arrow  marks the overall duration of the call that is to be measured and stored in the main body of the respective MOC record. The duration before t₅ (incoming leg) or t₄ (outgoing leg) needs not to be stored since the call is answered later on. The call duration in the first outgoing leg module contains the time interval from t₄ to t₆ (period ). The call duration measurement of the second outleg is started with t₉and ended with t₁₀ (interval ).

Since the last outgoing leg is not answered, the respective module contains the holding time starting with t₁₁and ending with t₁₃ (period ).

(The timestamps t₁, t₂, t₃,t₇,t₈ and t₁₂ are mentioned for completion reasons only.)

Point in time	Signalling message sent/received trigger detection point encountered	Duration logging
t₁	SETUP; TDP(control)
t₂	IAM	seizure of outg. leg 1
t₃	ACM
t₄	ANSWER	start of call duration (outg. leg 1)
t₅	CONNECT	start of call duration (inc. leg)
t₆	RELEASE; EDP(control)	stop of call duration (outg. leg 1)
t₇	IAM	seizure of outg. leg 2
t₈	ACM
t₉	ANSWER	start of call duration (outg. leg 2)
t₁₀	RELEASE; EDP(control)	stop of call duration (outg. leg 2)
t₁₁	IAM	seizure of outg. leg 3 start of holding time (outg. leg 3)
t₁₂	ACM
t₁₃	RELEASE; EDP(control)	stop of holding time (outg. leg 3)

Figure 5.1.2.1.4.1: Call duration measurement in follow-on scenarios

5.1.2.1.5 Call reference

This field uniquely identifies a call or transaction on one side of the interface (i.e. ‘A’ or ‘B’ side) and is derived from the transaction identifier of TS 24.008 [208]. It is also used to identify all partial records and transactions belonging to the same connection.

For the avoidance of doubt, there is no global call reference defined within GSM and the call reference field cannot be used to combine, for example, the MOC and MTC records of a mobile‑to‑mobile connection.

5.1.2.1.6 Calling/called/connected/translated number

In general an Recommendation E.164 [308] number but may also include other numbering plans e.g. ITU-T Recommendation X.121 [315]. Each of these fields includes the type of number and number plan as specified in detail in TS 24.008 [208]. Where appropriate, these fields may also contain the presentation and screening information also specified in TS 24.008 [208].

The called number is the number received from the mobile station on mobile originated call set-up as defined in TS 24.008 [208]. Similarly, the calling number is the number received from the network on mobile terminated call set-up. In case of CAMEL initiated Call Forward (CF), the called (forwarded-to) number is returned by CAMEL.

The translated number is the result of any digit translation performed by the MSC on the called number received from the mobile station on mobile originated call set-up. This parameter is not included in the CDR if no digit translation has taken place.

The connected number is the number of the actual party reached as defined in TS 24.008 [208]. Although this is normally identical to the called number it may differ. This parameter is not included if identical to the called number.

The following examples are intended to explain the use of these fields:

EXAMPLE 1: Called Number = Connected Number

Normal call from a mobile subscriber to a mobile subscriber or to a PSTN subscriber.

EXAMPLE 2: Called Number != Connected Number

In case of routing to a PABX with Automatic Call Distribution or to an ISDN Basic Access with several devices attached. The connected number is that of the party actually reached. N.B. The recording of the actual number connected may be limited by the capability of intermediate signalling connections.

EXAMPLE 3: MTC record for Call Forwarding ("A" -> "B" -> "C")

In case of call forwarding, the connected number recorded in the MTC record of the "B" subscriber is that of the forwarded-to party or "C" subscriber. The calling party field contains the number of the "A" subscriber.

EXAMPLE 4: Translated Number

This field is only present if digit translation is applied by the MSC to the called number received from the mobile station. Examples include abbreviated dialling codes and service numbers.

5.1.2.1.7 Calling Party Number

This field contains Calling Party Number modified by CAMEL service.

5.1.2.1.8 CAMEL call leg information

This field contains a set of CAMEL information IEs according to the number of outgoing CAMEL call legs.

5.1.2.1.9 CAMEL information

This field contains a list of parameters with information related to one CAMEL outgoing call leg. This parameter list is an Information Element (IE) used in the CAMEL Call Leg Information field.

As a network option, parameters that are identical to the corresponding values in the top level structure of the record are not recorded again. That means whenever a value is not mentioned in this set the value provided in the basic record is valid instead. This might lead to an empty or even absent structure, if no parameter was modified.

5.1.2.1.10 CAMEL initiated CF indicator

The purpose of this field is to distinguish CAMEL call forwarding service scenarios from standard GSM call forwarding scenarios.

From the Basic Call State Model (BCSM)’s point of view this field is set to ‘CF’ whenever the Originating CAMEL Subscription Information (O_CSI) was applied after terminating CAMEL call processing had been taken place changing the call destination. For the avoidance of doubt: this flag does not depend on other modified call parameter(s) (e.g.: redirection information, etc.) received in the CAP_CONNECT message of the Terminating CAMEL Subscription Information (T_CSI) service.

This flag also indicates that another record might be generated, one containing the charging information related to the terminating CAMEL service and one containing the charging information related to the originating CAMEL service.

5.1.2.1.11 CAMEL modified Service Centre

This field contains SMS-C address modified by CAMEL service. If this field is present the field Service Centre contain SMS-C address before CAMEL modification.

5.1.2.1.12 CAMEL SMS Information

This field contains following CAMEL information for mobile originated and terminated SMS:

– Default SMS handling:

This field indicates whether or not a CAMEL encounters default SMS handling. This field shall be present only if default SMS handling has been applied.

– Free format data:

See clause 5.1.2.1.26.

– Calling Party Number:

This field contains Calling Party Number modified by CAMEL service.

– CAMEL modified Service Centre:

This field contains SMS-C address modified by CAMEL service.

NOTE 1: This field is only applicable for originated SMS.

– CAMEL Destination Subscriber Number

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

NOTE 2: This field is only applicable for originated SMS.

– SMS Reference Number:

This field contains the SMS Reference Number assigned to the Short Message by the MSC.

5.1.2.1.13 Cause for termination

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

– normal release;

– CAMEL initiated call release;

– partial record generation;

– partial record call re-establishment;

– unsuccessful call attempt;

– abnormal termination during the stable phase;

– unauthorized network originating a location service request;

– unauthorized client requesting a location service;

– position method failure at a location service execution;

– unknown or unreachable LCS client at a location service request.

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

5.1.2.1.14 Channel Coding Accepted/Channel Coding Used

A list of traffic channel codings for HSCSD connections accepted/negotiated by the MS.

These parameters are only present in the CDRs for HSCSD connections.

5.1.2.1.15 Data volume

This field includes the number of 64 octet segments transmitted during the use of data services if known.

5.1.2.1.16 Default call/SMS handling

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

5.1.2.1.17 Destination Subscriber Number

This field contains Destination/Called Subscriber Number modified by CAMEL service. If not modified then this field may contain original Destination Number also when CAMEL is not active.

5.1.2.1.18 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 TS 29.002 [214];

– a Cause from TS 24.008 [208];

– a Cause from TS 29.078 [217];

– a Cause from ITU-T Recommendation Q.767 [309];

– a LCS diagnostics according TS 29.002 [214].

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

5.1.2.1.19 EMS-Digits

This parameter only applies to location for an emergency services call in North America and gives the North American Emergency Services Routing Digits as defined in TS 29.002 [214].

5.1.2.1.20 EMS-Key

This parameter only applies to location for an emergency services call in North America and gives the North American Emergency Services Routing Key as defined in TS 29.002 [214].

5.1.2.1.21 Entity number

This field contains the Recommendation E.164 [308] number assigned to the entity (MSC, VLR, HLR etc.) that produced the record. For further details concerning the structure of MSC and location register numbers see TS 23.003 [200].

5.1.2.1.22 Equipment id

This field contains a local identifier used to distinguish between equipment of the same equipment type e.g. the number of the conference circuit employed if more than one is available.

5.1.2.1.23 Equipment type

This field contains the type of common equipment employed e.g. conference circuit for multi-party service.

5.1.2.1.24 Event time stamps

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

The call records may contain three significant call handling time stamps:

– the time at which the resource in question was seized (Seizure time);

– the time at which the call was answered or at which charging commences (Answer time);

– the time at which the resource was released (Release time).

For both Mobile Originated and Mobile Terminated calls, the Seizure time is the time at which the traffic channel is allocated i.e. the time at which the ASSIGN COMMAND message is sent to the MS.

For Mobile Originated calls the Answer time is the time at which the CONNECT message is sent to the calling party. For Mobile Terminated calls the time at which the CONNECT message is received from the called party. However, if the subscriber has subscribed to the advice of charge charging level service, then the answer time shall be derived from the time at which the FACILITY message is received from the MS containing the acknowledgement of receipt of the AOC parameters. Similarly, if the AOC parameters are changed during the call then the change time recorded for a subscriber with AOC charging level is the receipt of the FACILITY message from the MS. For a subscriber with AOC information level the change time recorded is the time at which the FACILITY is sent to the MS. Finally, in case of call re-establishment the answer time is the time at which the new traffic channel is allocated by the MSC i.e. when the ASSIGN COMMAND is sent to the MS.

The Release time is the time at which the connection is released by either party i.e. a DISCONNECT or RELEASE is sent by the network or a DISCONNECT is received from the MS. In the case of a radio link failure, the release time is the time at which the failure was detected by the MSC.

For unsuccessful call attempts the Seizure time is mandatory. The Release time is optional and the call duration recorded is the call holding time i.e. the difference between the two.

For successful calls the Answer time is mandatory and both the Seizure and Release times are optional. The call duration recorded is the chargeable duration i.e. the difference between the Answer and Release time stamps.

The event records include the following time stamps:

– HLR-int time: The receipt of a MAP_SEND_ROUTING_INFO request by the HLR;

– Loc.Upd. time: The receipt of a MAP_UPDATE_LOCATION_AREA request by the VLR or the receipt of a MAP_UPDATE_LOCATION request by the HLR;

– SS-Action: The receipt of a supplementary service request by the VLR;

e.g. MAP_REGISTER_SS, MAP_INVOKE_SS

– SMS-MO: The receipt of an RP_DATA message from the MS containing an SMS_SUBMIT PDU;

– SMS-MT: The transmission of an RP_DATA message to the MS containing an SMS_DELIVER PDU;

– LCS: The time the LR was processed.

It should be noted that the events listed above are only examples in order to demonstrate the principles and that the list is by no means exhaustive.

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

5.1.2.1.25 Fixed Network User Rate

This field indicates the user data rate applied for the connection in the fixed network. In UMTS, it shall be present for all bearer services as specified in TS 22.002 [102]. In GSM, this parameter is part of the HSCSD connection parameters, see clause 5.1.2.1.30.

5.1.2.1.26 Free format data

This field contains charging information sent by the gsmSCF in the Furnish Charging Information (FCI) messages as defined in TS 29.078 [217]. 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 clauses of the relevant call records. ‘Free format data’ sent to the legID=1 is always stored in the top level of the respective record. ‘Free format data’ sent to the legID >1 is stored in the appropriate CAMEL call leg information field.

If the FCI is received more than once during one continuing incoming/outgoing CAMEL call leg, 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.

5.1.2.1.27 Free format data append indicator

This field contains an indicator whether 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 ofpartial 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.

5.1.2.1.28 GsmSCF address

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

5.1.2.1.29 Guaranteed Bit Rate

This field contains the Guaranteed Bit Rate based on the FNUR for transparent and Wanted AIUR for non-transparent CS data services based on the described mapping in TS 27.001 [213]. The Guaranteed Bit Rate may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. The bit-rate of the UMTS bearer service shall guarantee to the user or applications refer TS 22.002 [102].

Operator may choose any of the possible values less or equal to wanted AIUR (Air Interface User Rate).
(If WAIUR is less or equal to 14,4 kbit/s then Guaranteed Bit Rate and Maximum Bit Rate shall be set to 14,4 kbit/s).

5.1.2.1.30 HSCSD parameters/Change of HSCSD parameters

The basic HSCSD parameters are negotiated between the MS and the network at call set-up time. They comprise ofthe following parameters:

– the FNUR (Fixed Network User Rate) (optionally);

– the total AIUR (Air Interface User Rate) requested by the MS (for non-transparent HSCSD connections only);

– a list of the channel codings accepted by the MS;

– the maximum number of traffic channels accepted by the MS (this is noted in the channels requested field);

– the channel coding and the number of traffic channels actually used for the call.

In case the network or user initiated modification procedure takes place during the call, the AIUR requested, the channel coding used and the number of traffic channel requested/used might be recorded in the Change of HSCSD parameters field including the time at which the change occurred and which entity requested the change.

It should be noted that the Change of HSCSD Parameters field is optional and not required if partial records are generated when a Change of HSCSD Parameters takes place.

5.1.2.1.31 Incoming/outgoing trunk group

The incoming trunk group describes the trunk on which the call originates as seen from the MSC. For mobile originated calls this will generally be a BSS trunk. Similarly, the outgoing trunk group describes the trunk on which the call leaves the MSC.

For 3G, this parameter may not be available. When available, this parameter shall be supplied in the CDRs.

5.1.2.1.32 Interrogation result

This field contains the result of the HLR interrogation attempt as defined in the MAP (TS 29.002 [214]).

NOTE: This field is only provided if the attempted interrogation was unsuccessful.

5.1.2.1.33 IMEI Check Event

This field identifies the type of event that caused the IMEI check to take place:

– Mobile originating call attempt;

– Mobile terminating call attempt;

– Mobile originating SMS;

– Mobile terminating SMS;

– Supplementary service actions performed by the subscriber;

– Location update.

5.1.2.1.34 IMEI Status

This field contains the result of the IMEI checking procedure:

– Tracklisted;

– Blocklisted;

– Non-allowlisted.

5.1.2.1.35 JIP Parameter

This Jurisdiction Information Parameter (JIP) is populated if received via one of the methods listed as JIP Source. The field shall identify the actual originating exchange and may be equal to 6 or 10 digits for North America Region (NAR). Note that this field may not apply for international areas, as it is not currently used. Additionally, it is also possible to use the LRN as the JIP if it properly identifies the originating switch.

5.1.2.1.36 JIP Query Status Indicator

This field indicates the status of Location Routing Number (LRN) query as follows:

1. Number Portability Data Base (NPDB) returns LRN or NULL response (free of any error).

2. No response was received to the query; the query timed out.

4. Protocol error in received response message.

5. Error detected in response data.

6. Query rejected

9. No query performed

99. Query unsuccessful, reason unknown

If the JIP is equal to the LRN, then the JIP query status shall be the same as the LRN query status. If not, this field shall be set to one of the values listed above.

5.1.2.1.37 JIP Source Indicator

This indicator shall be populated if the Jurisdiction Information Parameter is derived. Identifies the method in which the value was derived. Shall be set to the values listed in the LRN Source Indicator.

5.1.2.1.38 LCS Cause

The LCS Cause parameter provides the reason for an unsuccessful location request according TS 49.031 [227].

5.1.2.1.39 LCS Client Identity

This field contains further information on the LCS Client identity:

– Client External ID;

– Client Dialled by MS ID;

– Client Internal ID.

5.1.2.1.40 LCS Client Type

This field contains the type of the LCS Client as defined in TS 29.002 [214].

5.1.2.1.41 LCS Priority

This parameter gives the priority of the location request as defined in TS 49.031 [227]

5.1.2.1.42 LCS QoS

This information element defines the Quality of Service for a location request as defined in TS 49.031 [227].

5.1.2.1.43 Level of CAMEL service

This field describes briefly the complexity of CAMEL invocation:

– ‘Basic’ means that CAMEL feature is invoked during the set-up phase (e.g. to modify the destination) of the call only;

– ‘Online charging’ means that CAMEL supported AoC parameter were sent to the mobile station (the Send Charging Information message, SCI, is received from the gsmSCF);

– The flag ‘call duration supervision’ is set whenever the call duration supervision is applied in the gsmSSF of the VPLMN (apply charging message is received from the gsmSCF).

5.1.2.1.44 Location/change of location

The location field contains a combination of the Location Area Code (LAC), Cell Identity (CI) and MCC+MNC of the cell in which the served party is currently located. Any change of location 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 LAC and CI are both 2 octet quantities and coded according to TS 24.008 [208].

For SMS over SGs (defined in TS 36.413 [226]), the LAC field contains the Tracking Area Code and the Cell Identity contains the 16 least significant bits.

5.1.2.1.45 Location Estimate

The Location Estimate field is providing an estimate of a geographic location of a target MS according to TS 29.002 [214].

5.1.2.1.46 Location Extension

The Location Extension field contains the 12 most significant bits from the Cell Identity field. This is used when SMS over SGs (defined in TS 36.413 [226]) is applied and the access is E-UTRAN.

5.1.2.1.47 Location Routing Number (LRN)

This field contains Ten-digit Location Routing Number (LRN) for the Number Portability feature. It is populated if received via one of the methods listed as "LRN Source". It identifies the new location of a ported subscriber. For North America Region (NAR) this may be a 10-digit E.164 number. For Europe, other formats may apply.

If more than 10 digits are received, the first ten digits received are recorded. If fewer than 10 digits are received, the information is left justified in the field and padded with 0xF.

5.1.2.1.48 Location Type

This field contains the type of the location as defined in TS 29.002 [214].

5.1.2.1.49 LRN Query Status Indicator

This field indicates the status of Location Routing Number (LRN) query as follows:

1. Number Portability Data Base (NPDB) returns LRN or NULL response (free of any error);

2. No response was received to the query; the query timed out;

4. Protocol error in received response message;

5. Error detected in response data;

5. Query rejected;

9. No query performed;

99. Query unsuccessful, reason unknown.

It is populated if an NP query was performed.

5.1.2.1.50 LRN Source Indicator

This field indicates whether the Location Routing Number is obtained from LRN NP database or it came in incoming signalling or switching system data.

It is populated if routing information for a ported subscriber is received from one of the methods listed below.
It shall be equal to one of the following enumerated values:

1. LRN NP Database;

2. SwitchingSystemData;

3. Incomingsignaling;

9. Unknown.

5.1.2.1.51 Maximum Bit Rate

This field contains the Maximum Bit Rate based on the FNUR (Fixed Network User Rate) for transparent and WAIUR(Wanted Air Interface User Rate) for non-transparent CS data services based on the described mapping in TS 27.001 [213]. The parameter can be used to make code reservations in the downlink of the radio interface for the UMTS bearer service (BS20 and BS30) refer TS 22.002 [102]. Its purpose is:

to limit the delivered bit-rate to applications or external networks with such limitations,
to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs).]

Maximum bit rate is set to the highest value  WAIUR (If WAIUR is less or equal to 14.4 kbit/s then Guaranteed Bit Rate and Maximum Bit Rate shall be set to 14.4 kbit/s).

5.1.2.1.52 Measure Duration

This field contains the duration for the section of the location measurement corresponding to the location request and the location report messages.

5.1.2.1.53 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 TS 23.040 [201].

5.1.2.1.54 MLC Number

This parameter refers to the ISDN (E.164[308]) number of an MLC.

5.1.2.1.55 Mobile station classmark/change of classmark

This MS classmark field contains the mobile station classmark employed by the served MS on call set-up as defined in TS 24.008 [208] (see mobile station classmark 2, mobile station classmark 3). Any alteration in the classmark during the connection may be recorded in the change of classmark field and will include the time at which the change took place.

It should be noted that the change of classmark field is optional and not required if partial records are created when the classmark is altered.

5.1.2.1.56 MOLR Type

The MOLR-Type identifier refers to the type of MO-LR that was invoked as defined in TS 24.080 [209].

5.1.2.1.57 MSC Address

This field contains the Recommendation E.164 [308] number assigned to the MSC that produced the record. For further details concerning the structure of MSC numbers see TS 23.003 [200].

5.1.2.1.58 MSC Server Indication

This field contains an indicator whether the CAMEL subscription information is active. The parameter is present for the VT-CSI in the VMSC and not present for the T-CSI in the GMSC.

This indication should be used for differentiation between the validity of the record content for T-CSI in the GMSC and VT-CSI in the VMSC.

5.1.2.1.59 Network Call Reference

Whenever CAMEL is applied, this field is used for correlation of call records outputted from the originating MSC (when applicable), the GMSC and the terminating MSC, and a network optional call record from the gsmSCF.

5.1.2.1.60 Notification to MS user

This field contains the privacy notification to MS user that was applicable when the LR was invoked as defined in TS 29.002 [214].

5.1.2.1.61 Number of DP encountered

This field indicates how often CAMEL armed detection points (TDP and EDP) were encountered and is a measure of signalling between serving network and CAMEL service and complements ‘Level of CAMEL service’ field. Detection points from all applied CAMEL services for a single call leg and processed in the same gsmSSF shall be counted together.

5.1.2.1.62 Number of forwarding

This field, if provided via ISUP signalling, contains the number of times a call has been forwarded prior to the interrogation of the HLR and is defined in TS 29.002 [214].

5.1.2.1.63 Old /new location

These fields contain the location of a mobile subscriber before and after a location update. In case of VLR location update the location information consists of a VMSC number and location area code and MCC+MNC, with identity of the cell or the SAC for new location. In case of HLR location update the field contains the VMSC number and the VLR number.

5.1.2.1.64 Partial Record Type

This field indicates the event that caused the generation of a partial record.

5.1.2.1.65 Positioning Data

This information element is providing positioning data associated with a successful or unsuccessful location attempt for a target MS according TS 49.031 [227].

5.1.2.1.66 Positioning Data

This information element is providing positioning data associated with a successful or unsuccessful location attempt for a target MS according TS 49.031 [227].

5.1.2.1.67 Privacy Override

This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN for an MT‑LR are in the same country as defined in TS 29.002 [214].

5.1.2.1.68 Radio channel requested/radio channel used/change of radio channel

The radio channel requested field contains the type of channel requested by the user. The following values are permitted:

– full rate;

– half rate;

– dual mode half rate preferred;

– dual mode full rate preferred.

The radio channel used field indicates the type of traffic channel actually employed for the connection i.e. either full rate (Bm) or half rate (Lm) as described in GSM 05.01 via CR change to 45.001 [312]. Any change in the type of channel used may be recorded in the change of radio channel used field including the time at which the change occurred and the speech version used after the change of radio channel.

5.1.2.1.69 Rate Indication

This parameter specifies the rate adaptation that was used for the connection. The field is constructed from the information in the parameters "rate adaptation" and "other rate adaptation" signalled between the MS/UE and the network, see TS 24.008 [208].

The format of this field is a single octet with the following format:

– Bits 0-1: the Rate Adaptation field as defined in TS 24.008 [208];

Bits 2-3: the Other Rate Adaptation field as defined in TS 24.008 [208];

– Bits 4-7: not used.

5.1.2.1.70 Reason for Service Change

This field contains the type of service change requested by the subscriber or performed by the network. Possible values include:

– subscriber initiated;

– network initiated;

– call setup fallback;

– call setup change order.

For further details see TS 23.172 [207].

5.1.2.1.71 Record extensions

The field enables network operators and/ or manufacturers to add their own extensions to the standard record definitions.

5.1.2.1.72 Record type

The field identifies the type of the record e.g. mobile originated, mobile terminated etc.

5.1.2.1.73 Recording Entity

This field contains the E.164 [308] number assigned to the entity (MSC, VLR, HLR etc.) that produced the record. For further details concerning the structure of MSC and location register numbers see TS 23.003 [200].

5.1.2.1.74 Redial attempt

This field indicates that a call is the result of a redial attempt to switch from speech to multimedia or vice-versa.

5.1.2.1.74A Related ICID

This field contains the related IMS Charging ID for the IMS call leg in case of SRVCC as received from IMS domain.

5.1.2.1.75 Roaming number

The roaming number field contains the mobile station roaming number as defined in TS 23.003 [200] and coded according to TS 29.002 [214].

5.1.2.1.76 Routing number

The routing number field of the HLR interrogation record contains either a mobile station roaming number or, in case of call forwarding, a forwarded-to number.

5.1.2.1.77 Sequence number

This field contains a running sequence number employed to link the partial records generated for a particular connection.

5.1.2.1.78 Served IMEI

This fields contains the international mobile equipment identity (IMEI) or IMEISV 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 case of an MTC record.

The structure of the IMEI, IMEISV is specified in TS 23.003 [200] and the encoding defined in TS 29.274 [223].

5.1.2.1.79 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 an MOC record.

The structure of the IMSI is defined in TS 23.003 [200].

5.1.2.1.80 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 TS 23.003 [200].

5.1.2.1.81 Service centre address

This field contains a Recommendation E.164 [308] number identifying a particular service centre e.g. short message service centre (see TS 23.040 [201]).

5.1.2.1.82 Service Change Initiator

This field indicates that the owner of this CDR is the initiator of the service change.

5.1.2.1.83 Service key

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

5.1.2.1.84 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 TS 29.002 [214]). Note that this field is only provided if the attempted delivery was unsuccessful.

5.1.2.1.85 Speech version supported/Speech version used

The speech version supported field contains the speech version supported by the MS with the highest priority.
The speech version used field contains the speech codec version assigned for that call. The coding is according GSM 08.08 [313] speech version identifier with the extension bit 8 set to 0.

It should be noted that the change of radio channel field is optional and not required if partial records are generated.

5.1.2.1.86 Supplementary service(s)

The supplementary service field in the Supplementary Service record type contains the code of the supplementary service on which the action was performed.

The supplementary services field in the MOC/MTC records contains the codes of the supplementary services invoked as a result of, or during, a connection.

The coding of supplementary service is described in detail in TS 29.002 [214].

5.1.2.1.87 Supplementary service action

This field contains the type of supplementary service action requested by the subscriber or performed by the network. Possible values include:

– registration;

– erasure;

– activation;

– deactivation;

– interrogation;

– invocation.

For further details see TS 22.004 [103].

5.1.2.1.88 Supplementary service action result

This field contains the result of an attempted supplementary service action (see TS 29.002 [214]). Note that this field is only provided if the SS-action was at least partially unsuccessful.

5.1.2.1.89 Supplementary service parameters

This field contains the parameters associated with a supplementary service action requested by the subscriber. For further details of the parameters involved see the GSM 02.8n series of documents.

5.1.2.1.90 Supplementary service(s)

The supplementary service field in the Supplementary Service record type contains the code of the supplementary service on which the action was performed.

The supplementary services field in the MOC/MTC records contains the codes of the supplementary services invoked as a result of, or during, a connection.

The coding of supplementary service is described in detail in TS 29.002 [214].

5.1.2.1.91 System type

This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call set-up. For an open CDR in a 2G NE (responsible for the CDR), the field is not present (even if the call is handed off to a 3G air interface). For a CDR in a 3G NE (responsible for the CDR), the value unknown shall be used after handover.

5.1.2.1.92 Transparency indicator

This field indicates whether the basic service was employed in transparent or non-transparent mode. It should also be noted that this field is only relevant for those services which may be operated in both transparent and non-transparent modes.

5.1.2.1.93 Update result

This field contains the result of the location update request as defined in the MAP (TS 29.002 [214]). Note that this field is only provided if the attempted update was unsuccessful.

5.1.2.2 PS domain CDR parameters

5.1.2.2.A Introduction

This subclause contains the description of the CDR parameters that are specific to the PS domain CDR types as specified in TS 32.251 [11].

5.1.2.2.B Void

5.1.2.2.0 3GPP2 User Location Information

This field holds the 3GPP2 User Location Information. It contains the 3GPP2-BSID as described in TS 29.212 [220].

The parameter is provided to the PGW/TDF during IP-CAN/TDF session establishment/modification, through PCC procedures for non-3GPP Accesses, as defined in the TS 23.203 [203].

5.1.2.2.0aA Access Availability Change Reason

This field indicates the reason why the availability of an access is changed by the PCEF, i.e. RAN rule indication or Access usable/unusable as defined in TS 29.212 [220].

5.1.2.2.0A Access Line Identifier

This field contains the Access line id (physical and logical circuit ID) serving the 3GPP UE or fixed user (i.e. Fixed device or RG).

This field contains the Access line id (physical and logical circuit ID):

– serving the 3GPP UE or fixed device, behind the RG when in bridge mode or in routed mode without NAT, or

– of the RG when in routed mode with NAT;

– of the access point to which the UE is attached, in trusted or untrusted WLAN.

5.1.2.2.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/MME or modified by CAMEL service. An APN can also be a wildcard, in which case the SGSN/MME selects the access point address.

Following TS 23.003 [200], the APN field is specified in the CDR by two variable strings. The first is the APN Network Identifier (NI portion) and the second is the APN Operator Identifier (OI portion). The APN NI may contain one or more label as described in TS 23.003 [200]. The APN OI is composed of three labels. The first and second labels together shall uniquely identify the PLMN operator (e.g. "mnc<operator mnc>.mcc<operator mcc>.gprs").

To represent the APN NI and OI in the PCN CDRs, the "dot" notation shall be used.

See TS 23.003 [200] and TS 23.060 [202] for more information about APN format and access point decision rules.

5.1.2.2.1A APN Rate Control

This field contains the APN Rate Control as specified in TS 23.401 [245], which is used during the record for the PDN connection to the PGW.

5.1.2.2.2 APN Selection Mode

This field indicates how the SGSN/MME selected the APN to be used. The values and their meaning are as specified in TS 29.060 [215] for GTP case and in TS 29.274 [223] for eGTP case.

5.1.2.2.3 CAMEL Charging Information

This field contains the CAMEL Information as defined for the PDP context from the SGSN as the copy including Tag and Length from the SGSN’s CDR (S‑CDR).

5.1.2.2.4 CAMEL Information

This field includes following CAMEL information elements for PDP context (S-CDR), Attach/Detach session
(M-CDR), Mobile originated SMS (S-SMO-CDR) and Mobile terminated SMS (S-SMT-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 CSE.

CAMEL Access Point Name OI (S-CDR):

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

CAMEL Calling Party Number (S-SMO-CDR, S-SMT-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, S-SMT-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, S-SMT-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, S-SMT-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, S-SMT-CDR):

This field contains charging information sent by the gsmSCF in the Furnish Charging Information GPRS messages as defined in TS 29.078 [217]. 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 clauses of the relevant call records.

If the FCI is received more than 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 of received FCIs and thus valid free format data may be divided to different partial records.

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

This field describes briefly the complexity of CAMEL invocation. Categories are the same as 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 DPs encountered (S-CDR, M-CDR):

This field indicates how many armed CAMEL detection points (TDP and EDP) were encountered and complements "Level of CAMEL service" field.

smsReferenceNumber (S-SMO-CDR, S-SMT-CDR)

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

5.1.2.2.5 Cause for Record Closing

This field contains a reason for the release of the CDR. In case of Rf interface is used, it is derived from Change-Condition AVP at PS-information AVP level defined in TS 32.299 [40], when received. The following is included:

– normal release: IP-CAN bearer release or detach, TDF session release, IP-CAN session release for IP-Edge; It corresponds to "Normal Release" in Change-Condition AVP.

– data volume limit; It corresponds to "Volume Limit" in Change-Condition AVP.

– time (duration) limit; It corresponds to "Time Limit" in Change-Condition AVP.

– maximum number of changes in charging conditions; It corresponds to "Max Number of Changes in Charging conditions " in Change-Condition AVP.

– For SGSN: intra SGSN intersystem change (change of radio interface from GSM to UMTS or vice versa);

– For P-GW, TDF and S-GW: Radio Access Technology (RAT) change; It corresponds to "RAT Change" in Change-Condition AVP.

– abnormal termination (IP-CAN bearer or MM context or TDF session, or IP-CAN session); It corresponds to "Abnormal Release" in Change-Condition AVP.

– For SGSN: SGSN change;

– For S-GW, ePDG, TWAG: S-GW change; It corresponds to "S-GW Change" in Change-Condition AVP and is used for inter serving node change of all types.

– Timezone change; It corresponds to "UE TimeZone Change" in Change-Condition AVP.

– SGSN or S-GW PLMN change; It corresponds to "Serving Node PLMN Change" in Change-Condition AVP.

– For P-GW: APN-AMBR change: It corresponds to "Qos Change" in Change-Condition AVP.

– For S-GW, P-GW: MO exception data counter receipt: It corresponds to " MO exception data counter receipt" in Change-Condition AVP.

– unauthorized network originating a location service request;

– unauthorized client requesting a location service;

– position method failure at a location service execution;

– unknown or unreachable LCS client at a location service request;

– management intervention (request due to O&M reasons); It corresponds to "Management Intervention" in Change-Condition AVP;

– VoLTE bearer normal release: It corresponds to "VoLTE Bearer Normal Release" in Change-Condition AVP.

– VoLTE bearer abnormal release: It corresponds to "VoLTE Bearer Abnormal Release" in Change-Condition AVP.A more detailed reason may be found in the diagnostics field or Enhanced Diagnostics field.

5.1.2.2.6 Cell Identifier

For GSM, the Cell Identifier is defined as the Cell Id, reference 24.008 [208], and for UMTS it is defined as the Service Area Code in TS 25.413 [212].

5.1.2.2.7 Charging Characteristics

The Charging Characteristics field allows the operator to apply different kind of charging methods in the CDRs.
A subscriber may have Charging Characteristics assigned to his subscription. These characteristics can be supplied by the HLR/HSS according to the rules specified in Annex A of TS 32.251 [11].

Charging Characteristics used by IP-Edge [PCEF] or TDF in Convergent Fixed-Mobile Operator scenario are always configured in IP-Edge [PCEF] or TDF respectively, as described in annex D of TS 32.251 [11].

This information can be used by the PCNs/ IP-Edge [PCEF] to activate charging generation and e.g. control the closure of the CDR or the traffic volume containers (see clause 5.1.2.2.25) and applied charging characteristics is included in CDRs transmitted to nodes handling the CDRs via the Ga reference point. It can also be used in nodes handling the CDRs (e.g., the CGF or the billing system) to influence the CDR processing priority and routing. These functions are accomplished by specifying the charging characteristics as sets of charging profiles and the expected behaviour associated with each profile.
The interpretations of the profiles and their associated behaviours can be different for each PLMN operator and are not subject to standardisation. In the present document only the charging characteristic formats and selection modes are specified.

The functional requirements for the Charging Characteristics are further defined in normative Annex A of
TS 32.251 [11], including an example for the definitions of the trigger profiles associated with each CDR type.

The format of charging characteristics field is depicted in Figure 4. Each Bx (x =0..15) refers to a specific behaviour defined on a per-Operator basis, indicated as active when set to "1" value. See Annex A of
TS 32.251 [11] for guidance on how behaviours could be defined.

Figure 5.1.2.2.7.1: Charging Characteristics flags

5.1.2.2.8 Charging Characteristics selection mode

This field indicates the charging characteristic type that the PCNs applied to the CDR. In the SGSN the allowed values are:

– Home default;

– Visiting default;

– Roaming default;

– APN specific;

– Subscription specific.

In the S-GW/P-GW/TDF the allowed values are:

– Home default;

– Visiting default;

– Roaming default;

– Serving node supplied.

NOTE: The value ‘Serving Node Supplied’ is used if the CC what was received from e.g. S-GW is used i.e. the one what comes during bearer activation.

Further details are provided in TS 32.251 [11] Annex A.

In the IP-Edge [PCEF] and TDF in Convergent Fixed-Mobile Operator scenario, the allowed values are:

– Home default;

– Visiting default;

– Fixed default;

Further details are provided in TS 32.251 [11] Annex D.

5.1.2.2.9 Charging ID

This field is a charging identifier, which can be used together with P-GW address to identify all records produced in SGSN(s), S-GW and P-GW involved in a single IP-CAN bearer. Charging ID is generated by P-GW at IP-CAN bearer activation and transferred to bearer requesting SGSN/S-GW. At inter-SGSN/S-GW change the charging ID is transferred to the new SGSN/S-GW as part of each active IP-CAN bearer.

In case of PMIP-based connectivity, the Charging Id is generated per PDN connection.

Different P-GWs 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 P-GWs address and optionally (if still ambiguous) with the record opening time stamp.

5.1.2.2.9A CN Operator Selection Entity

This field defines which entity (UE or Network) has selected the Serving Core Network in Network Sharing situations.

5.1.2.2.9Aa CP CIoT EPS Optimisation Indicator

This field contains the indication on whether Control Plane CIoT EPS optimisation is used by the PDN connection during data transfer with the UE (i.e. Control Plane NAS PDU viaS11-U between SGW andMME) or not (i.e. User Plane via S1-U between SGW and eNB).

5.1.2.2.9B Charging per IP-CAN Session Indicator

This field indicates whether charging per IP-CAN session is active or not.

5.1.2.2.10 Destination Number

This field contains short message Destination Number requested by the user. See TS 32.250 [10].

5.1.2.2.11 Diagnostics

This field includes a more detailed technical reason for the releases of the connection.
The diagnostics may also be extended to include manufacturer and network specific information.

5.1.2.2.12 Duration

This field contains the relevant duration in seconds for IP-CAN bearer (S-CDR, SGW-CDR, PGW-CDR),
IP-CAN session (IPE-CDR), and attachment (M-CDR). In case of TDF-CDR, this field contains the relevant duration in seconds for TDF session.

It is the duration from Record Opening Time to record closure. 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.

5.1.2.2.13 Dynamic Address Flag

This field indicates that PDN address has been dynamically allocated for that particular IP-CAN bearer (PDN connection). This field is missing if address is static. Dynamic address allocation might be relevant for charging e.g. as one resource offered and possible owned by network operator.

5.1.2.2.13A Dynamic Address Flag Extension

This field indicates that the IPv4 address has been dynamically allocated for that particular IP-CAN bearer (PDN connection) of PDN type IPv4v6, and the dynamic IPv6 prefix is indicated in Dynamic Address Flag. This field is missing if IPv4 address is static. Dynamic address allocation might be relevant for charging e.g. as one resource offered and possible owned by network operator.

5.1.2.2.13Aa Enhanced Diagnostics

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

– RAN/NAS cause from TS 29.274 [223];

NOTE: The Enhanced Diagnostics is defined to allow extensions to other types of release causes in the future.

5.1.2.2.13B EPC QoS Information

This field contains the APN-AMBR for the IP-CAN session. It is used in the PGW-CDR only when charging per IP-CAN session is active.

5.1.2.2.13C ePDG Address Used

This field is the serving ePDG IP Address for the Control Plane. If both an IPv4 and an IPv6 address of the ePDG is available, the ePDG shall include the IPv4 address in the CDR.

5.1.2.2.13D ePDG IPv6 Address

This field is the serving ePDG IPv6 Address for the Control Plane, when both IPv4 and IPv6 addresses of the ePDG are available.

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

5.1.2.2.15 Void

5.1.2.2.15A Fixed User Location Information

This field contains the UE location in a fixed broadband access network. The location of the subscriber may include Access line id (physical and logical circuit ID) defined in ETSI TS 283 034 [314], SSID and BSSID of the Access Point, defined in IEEE Std 802.11-2012 [408].

5.1.2.2.16 GGSN Address Used

This field is the current serving GGSN/P-GW IP Address for the Control Plane. If both an IPv4 and an IPv6 address of the GGSN/P-GW are available, the SGSN shall include the IPv4 address in the CDR.

5.1.2.2.16A Void

(Void)

5.1.2.2.17 IMS Signalling Context

Indicates if the IP-CAN bearer is used for IMS signalling. It is only present if the IP-CAN bearer is an IMS signalling bearer. A IP-CAN bearer for IMS signalling is determined via the "IM CN Subsystem Signalling Flag" conveyed via the "Activate PDP context request" message from the MS to the network (refer to TS 24.008 ).

5.1.2.2.18 IMSI Unauthenticated Flag

This field indicates that provided "Served IMSI" is not authenticated, and relates to an emergency bearer established with IMSI as identifier (refer to TS 23.060 [202] and TS 29.274 [223]). This field is missing if IMSI is authenticated, or if IMSI is not provided as identifier.

5.1.2.2.18A IP-CAN session Type

This field defines the IP-CAN session type, e.g. IP, or PPP. PDP type format is used: See TS 29.060 [215].

5.1.2.2.18B IP-Edge Address IPv6

This field is the IP-Edge IPv6 Address used for the Control Plane, when both IPv4 and IPv6 addresses of the IP-Edge are available.

5.1.2.2.18C IP-Edge Address Used

This field is the IP-Edge IP Address used for the Control Plane. If both an IPv4 and an IPv6 addresses of the IP-Edge are available, the field shall include the IPv4 address.

5.1.2.2.18D IP-Edge Operator Identifier

This field is the PMLN Identifier (Mobile Country Code and Mobile Network Code) of the Convergent Fixed-Mobile Operator owning the IP-Edge located in Fixed Broadband Access.

The MCC and MNC are coded as described for "User Location Info" in TS 29.274 [223].

5.1.2.2.18E Last MS Time Zone

This field contains the "Time Zone" provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer deactivation. It is derived from 3GPP-MS-TimeZone AVP provided within PS-Information AVP, both defined in TS 32.299 [50], when received on Rf closure.

5.1.2.2.18F Last User Location Information

This field contains the User Location Information as described in clause in 5.1.2.2.75.

The field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer deactivation. It is derived from 3GPP-User-Location-Info AVP provided at PS-Information AVP level, both defined in TS 32.299 [50], when received on Rf closure.

5.1.2.2.19 LCS Cause

The LCS Cause parameter provides the reason for an unsuccessful location request according TS 49.031 [227].

5.1.2.2.20 LCS Client Identity

This field contains further information on the LCS Client identity:

Client External ID;
Client Dialled by MS ID;

– Client Internal ID.

5.1.2.2.21 LCS Client Type

This field contains the type of the LCS Client as defined in TS 29.002 [214].

5.1.2.2.22 LCS Priority

This parameter gives the priority of the location request as defined in TS 49.031 [227].

5.1.2.2.23 LCS QoS

This information element defines the Quality of Service for a location request as defined in TS 49.031 [227].

5.1.2.2.23A List of RAN Secondary RAT Usage Reports

This list applicable in SGW-CDR and PGW-CDR, includes one or more containers reported from the RAN for a secondary RAT.

Each container includes the following fields:

– Data Volume Uplink, Data Volume Downlink, Start Time, End Time and Secondary RAT Type.

– Data Volume Uplink includes the number of octets transmitted during the use of the packet data services in the uplink direction reported from RAN. The counting and reporting from RAN of uplink data volumes is optional.

– Data Volume Downlink includes the number of octets transmitted during the use of the packet data services in the downlink direction reported from RAN. The counting and reporting from RAN of downlink data volumes is optional.

– RAN Start Time is a time stamp, which defines the moment when the volume container is opened by the RAN.

– RAN End Time is a time stamp, which defines the moment when the volume container is closed by the RAN.

– Secondary RAT Type This field contains the RAT type for the secondary RAT.

– Charging ID This field contains the Charging ID of the bearer corresponding to the reported usage. Only needed if IP-CAN session level charging is applied.

5.1.2.2.24 List of Service Data

This list includes one or more service data containers. Depending on the reporting level of PCC/ADC rules, one service data container either includes charging data for one rating group or for one rating group and service id combination. Each service data container may include the following fields:

– AF-Record-Information.

– Charging Rule Base Name.

– ADC Rule Base Name.

– Data Volume Downlink.

– Data Volume Uplink.

– Event Based Charging Information.

– Local Sequence Number.

– PS Furnish Charging Information.

– EPC Qos Information.

– Rating Group.

– Report Time.

– Result Code.

– Service Condition Change.

– Service Identifier.

– Service Specific Info.

– Serving Node Address.

– Time of First Usage.

– Time of Last Usage.

– Time Quota Mechanism.

– Time Usage.

– user location information.

– 3GPP2 User Location Information.

– UWAN User Location Information.

– TWAN User Location Information.

– Sponsor Identity.

– Application Service Provider Identity.

– Presence Reporting Area Status.

– List of Presence Reporting Area Information.

– User CSG Information.

– RAT Type.

– Serving PLMN Rate Control.

– APN Rate Control.

– Related Change of Service Condition.

– Traffic Steering Policy Identifier Downlink.

– Traffic Steering Policy Identifier Uplink.

– VoLTE Information.

– Rating Group is the identifier of rating group. This field is mandatory. The parameter corresponds to the Charging Key as specified in TS 23.203 [203].

– Charging Rule Base Name is the reference to group of PCC rules predefined at the PCEF. This field is included if any of the PCC rules, which usage is reported within this service data container, was activated by using the Charging Rule Base Name as specified in TS 29.212 [220]. In case multiple Charging Rule Base Names activate PCC rules, which usage is reported within this service data container, the P-GW/IPE-CDR shall include only one occurrence to the service data container.

– ADC Rule Base Name is the reference to group of ADC rules predefined at the TDF. This field is included if any of the ADC rules, which usage is reported within this service data container, was activated by using the ADC Rule Base Name as specified in TS 29.212 [220]. In case multiple ADC Rule Base Names activate ADC rules, which usage is reported within this service data container, the TDF shall include only one occurrence to the service data container.

– Result Code contains the result code after the interconnection with the OCS. This field may be added to the service data container if online and offline charging are both used for same rating group. The result code in service data container is the value of the Result-Code AVP received within last CCA message in corresponding MSCC AVP to this service data container.

– Local Sequence Number is a service data container sequence number. It starts from 1 and is increased by 1 for each service date container generated within the lifetime of this IP-CAN bearer/TDF session.

– Time of First Usage is the time stamp for the first IP packet to be transmitted and mapped to the current service data container. For envelope reporting controlled by the Time Quota Mechanism, this indicates the time stamp for the first IP packet to be transmitted that causes an envelope to be opened – see TS 32.299 [50].

– Time of Last Usage is the time stamp for the last IP packet to be transmitted and mapped to the current service data container. For envelope reporting, controlled by the Time Quota Mechanism, this indicates the time stamp for an envelope to be closed – see TS 32.299 [50] for conditions for envelope closure.

– Time Usage contains the effective used time within the service data container recording interval.

– Service Condition Change defines the reason for closing the service data container (see TS 32.251 [11]), such as tariff time change, IP-CAN bearer modification (e.g. QoS change, S-GW change, user location change, user CSG information change), access change of service data flow, indirect service condition change, service usage thresholds, service idled out, termination or failure handling procedure. When one of the "CGI/SAI, ECGI or TAI or RAI Change" are reported as user location change, the dedicated value in service Condition Change is set instead of the generic "user location change" value. This field is specified as bitmask for support of multiple change trigger (e.g. S-GW and QoS change). This field is derived from Change-Condition AVP at Service-Data-Container AVP level defined in TS 32.299 [50] when received on Rf. Each value is mapped to the corresponding value in "ServiceConditionChange" field. When simultaneous change triggers are met, multiple Change-Condition values are set in field bitmask. When no Change-Condition AVP is provided, the "recordClosure" value is set for the service data container. For envelope reporting, the Service Condition Change value shall always take the value "envelopeClosure". The mechanism for creating the envelope is identified within the Time Quota Mechanism field.

– EPC Qos Information in service specific service data containers contains the QoS applied for the service. This is included in the first service data container. In following container EPC QoS information is present if previous change condition is "QoS change". The P-GW/TDF/IPE-CDR shall include only one EPC QoS Information occurrence to one service data container.

– Serving Node Address contains the valid serving node (e.g. SGSN/S-GW) control plane IP address during the service data container recording interval.

– Data Volume Uplink and Downlink, includes the number of octets transmitted during the service data container recording interval in the uplink and/or downlink direction, respectively. The amount of data counted in P-GW shall be as specified in clauses 5.2.1.10.1, 5.3.1.1 and 5.3.1.6.1 of TS 32.251 [11]. The amount of data counted in TDF shall be based on full payload of the data transferred. The amount of data counted in IP-Edge shall be based on full payload of the data transferred.

– Report Time is a time stamp, which defines the moment when the service data container is closed.

– Service Identifier is an identifier for a service. 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.

– PS Furnish Charging Information includes charging information per rating group in case it is sent by OCS.

– User location information contains the user location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE was located during the service data container recording interval. This is included in the service data container only if previous container’s change condition is "user location change" or one of the "CGI/SAI, ECGI or TAI or RAI Change". Note the user location information in PGW-CDR/TDF-CDR main level contains the location where the UE was when PGW-CDR/TDF-CDR was opened, and the "Last user location information" in PGW-CDR main level contains the location where the UE was when PGW-CDR is closed.

– Presence Reporting Area Status contains the status of the UE presence (i.e. indication on whether the UE is inside or outside) in the Presence Reporting Area(s) identified by "Presence Reporting Area identifier(s)" contained in PGW-CDR main level. This is included in the service data container when the initial status is reported after opening of PGW-CDR, or if previous container’s change condition is "Presence in Presence Reporting Area Change". This field is not applicable in multiple PRA(s).

– List of Presence Reporting Area Information contains the list of Presence Reporting Area Information. Each Presence Reporting Area Information includes the "Presence Reporting Area identifier", the status of the UE presence (i.e. indication on whether the UE is inside or outside the Presence Reporting Area or Presence Reporting Area(s) inactive), and the Node (PCRF, OCS) which subscribed-to the PRA.

– 3GPP2 User Location Information contains the 3GPP2 user location (i.e. 3GPP2-BSID: Cell-Id, SID, NID) where the UE was located during the service data container recording interval. This is included in the service data container only if previous container’s change condition is "user location change". Note the "3GPP2 user location information" in PGW-CDR/TDF-CDR main level contains the location where the UE was when PGW-CDR/TDF-CDR was opened.

– UWAN User Location Information contains the Untrusted Wireless Access Network (UWAN) user location during the service data container recording interval. This is included in the service data container only if previous container’s change condition is "user location change". Note the user location information in PGW-CDR main level contains the location where the UE was when PGW-CDR was opened.

– TWAN User Location Information contains the user location in a Trusted WLAN Access Network during the service data container recording interval. This is included in the service data container only if previous container’s change condition is "user location change". Note the user location information in PGW-CDR/TDF-CDR main level contains the location where the UE was when PGW-CDR/TDF-CDR was opened.

– User CSG information contains the status of the user accessing a CSG cell (CSG ID within the PLMN, Access mode and indication on CSG membership) during the service data container recording interval. This is included in the service data container only if previous container’s change condition is "user CSG information change". Note the "user CSG information" in PGW-CDR main level contains the "user CSG information" when PGW-CDR was opened.

– AF-Record-Information includes the "AF Charging Identifier" (ICID for IMS) and associated flow identifiers generated by the AF and received by the P-GW over Gx interfaces as defined in TS 29.212 [220]. In case usage of PCC rules, which usage is reported within the container, has different AF-Record-Information then the P-GW shall include all occurrences to the service data container.

– Event Based Charging Information includes the number of events and associated timeStamps (each event is timestamped) during the service data container recording interval.

– 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 [50].

– Base Time Interval identifies the length of the base time interval, for controlling the reporting of time based usage, in seconds.

– Service Specific Info holds service specific data for a pre-defined PCC or a predefined ADC rule that is used for enhanced packet filtering.

– Sponsor Identity identifies the sponsor willing to pay for the operator’s charge for connectivity.

– Application Service Provider Identity identifies application service provider that is delivering a service to an end user.

– RAT Type contains the RAT type for the IP-CAN bearer that is first reported for the Rating Group or Rating Group / Service Identifier in the container. If traffic from multiple bearers is included in the report for the container, only one field is included.

NOTE: Sponsor Identity and Application Service Provider Identity are not used together with Service Identification reporting. Furthermore, neither the Sponsor Identity nor Application Service Provider Identity is applicable to the TDF.

– Related Change of Service Condition indicates the reason a related container was closed when the current container is indirectly closed and the supplemental information for the event. This information is applicable when charging per IP-CAN session is active for a multi-access PDN connection.

– Serving PLMN Rate Control This field contains the Serving PLMN Rate Control applied by MME during the transfer of the data volume captured by the container (applicable only to the PGW-CDR). This is included in the service data container only if previous container’s change condition is "Serving PLMN Rate Control change ". Note the Serving PLMN Rate Control field in PGW-CDR main level contains the Serving PLMN Rate Control when PGW-CDR was opened.

– APN Rate Control This field contains the APN Rate Control applied by PGW during the transfer of the data volume captured by the container (applicable only to the PGW-CDR). This is included in the service data container only if previous container’s change condition is "APN Rate Control change ". Note the APN Rate Control field in PGW-CDR main level contains the APN Rate Control when PGW-CDR was opened.

– Traffic Steering Policy Identifier Downlink This field contains the Traffic Steering Policy Identifier Downlink applied by PGW/ TDF during the service data container recording interval.

– Traffic Steering Policy Identifier Uplink This field contains the Traffic Steering Policy Identifier Uplink applied by PGW/TDF during the service data container recording interval.

– VoLTE Information This field contains the caller and callee Information of VoLTE. Caller Information of VoLTE is described in clause 5.1.3.1.24. Callee Information contains:

– Called Party Address (described in clause 5.1.3.1.9).

– Requested Party Address (described in clause 5.1.3.1.43).

– List of Called Asserted Identity (described in clause 5.1.3.1.23).

5.1.2.2.25 List of Traffic Data Volumes

This list applicable in S-CDR, SGW-CDR, IPE-CDR, ePDG-CDR and TWAG-CDR, includes one or more containers.

This list applicable in PGW-CDR when charging per IP-CAN session is active and IP-CAN bearer charging is being performed for the session.

In SGW-CDR, PGW-CDR, IPE-CDR, ePDG-CDR and TWAG-CDR, containers are per QCI/ARP pair. This means that if QoS control within one IP-CAN bearer is applicable in S-GW, P-GW, ePDG and TWAG, there can be several containers open at same time one per each applied QCI/ARP pair.

Each container includes the following fields:

– Data Volume Uplink, Data Volume Downlink, Change Condition and Change Time.

– Data Volume Uplink includes the number of octets transmitted during the use of the packet data services in the uplink direction. In MBMS charging, this field is normally to be set to zero, because MBMS charging is based on the volume of the downlink data. The counting of uplink data volumes is optional. In S-CDR this field is not present when the SGSN has successfully established Direct Tunnel between the RNC and the GGSN.

– Data Volume Downlink includes the number of octets transmitted during the use of the packet data services in the downlink direction. In S-CDR this field is not present when the SGSN has successfully established Direct Tunnel between the RNC and the GGSN.

– Change Condition defines the reason for closing the container (see TS 32.251 [11]), such as tariff time change, QoS change or closing of the CDR. This field is derived from Change-Condition AVP Traffic-Data-Volumes AVP level defined in TS 32.299 [40] when received on Rf. Each value is mapped to the corresponding value in "ChangeCondition" field. When no Change-Condition AVP is provided, the "recordClosure" value is set for the container. For User Location Change, when one of the "CGI/SAI, ECGI or TAI or RAI Change" are reported as user location change, the dedicated value in service Condition Change is set instead of the generic "user location change" value.

– Change Time is a time stamp, which defines the moment when the volume container is closed or the CDR is closed. All the active IP-CAN bearers 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).

– User Location Information contains the location (e.g. CGI/SAI, ECGI/TAI or RAI) where the UE is located and used during the transfer of the data volume captured by the container (applicable only to the SGW-CDR). This is included in the Traffic data container only if previous container’s change condition is "user location change". Note the user location information in SGW-CDR main level contains the location where the UE was when SGW-CDR was opened, and the "Last user location information" in SGW-CDR main level contains the location where the UE was when SGW-CDR is closed.

– UWAN User Location Information contains the Untrusted Wireless Access Network (UWAN) user location during the transfer of the data volume captured by the container. This is included in the Traffic data container only if previous container’s change condition is "user location change". Note the user location information in ePDG-CDR main level contains the location where the UE was when ePDG-CDR was opened.

– TWAN User Location Information contains the user location in a Trusted WLAN Access Network during the transfer of the data volume captured by the container. This is included in the Traffic data container only if previous container’s change condition is "user location change". Note the user location information in TWAG-CDR main level contains the location where the UE was when TWAG-CDR was opened.

– Presence Reporting Area Status contains the status of the UE presence (i.e. indication on whether the UE is inside or outside) in the Presence Reporting Area(s) identified by "Presence Reporting Area identifier(s)" contained in SGW-CDR main level. This is included in the Traffic data container when the initial status is reported after opening of SGW-CDR, or if previous container’s change condition is "Presence in Presence Reporting Area Change". This field is not applicable in multiple PRA(s).

– List of Presence Reporting Area Information contains the list of Presence Reporting Area Information. Each Presence Reporting Area Information includes the "Presence Reporting Area identifier", the status of the UE presence (i.e. indication on whether the UE is inside or outside the Presence Reporting Area or Presence Reporting Area(s) inactive). In the PGW it contains the Node (PCRF, OCS) which subscribed-to the PRA.

– User CSG information contains the status of the user accessing a CSG cell (CSG ID within the PLMN, Access mode and indication on CSG membership) during the transfer of the data volume captured by the container. This is included in the Traffic data container only if previous container’s change condition is "user CSG information change". Note the "user CSG information" in S-CDR/SGW-CDR main level contains the "user CSG information" when S-CDR/SGW-CDR was opened.

– EPC QoS Information In case of IP-CAN bearer specific container this contains authorized QoS for the IP-CAN bearer. First container for each QCI/ARP pair includes this field. In following containers this field is present if previous change condition is "QoS change". This field is applicable only in SGW-CDR, PGW-CDR, IPE-CDR, ePDG-CDR, and TWAG-CDR.

In S-CDR first container includes following optional fields: QoS Requested 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 IP-CAN bearer modification procedure.

Table 5.1.2.2.25.1 illustrates an example for S-CDR but same principles are applicable also for SGW-CDR, PGW-CDR, IPE-CDR, ePDG-CDR and TWAG-CDR. There are five containers (sets of volume counts) caused by one QoS change, one location change, one tariff time change and one Direct Tunnel establishment (direct tunnel change applicable in S-CDR only). When CDR is opened the subscriber is in CGI1.

Table 5.1.2.2.25.1: 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 = 10

Data Volume Downlink = 3

Change Condition = CGI/SAI Change

Time Stamp = TIME3

Data Volume Uplink = 3

Data Volume Downlink = 4

User Location Info = CGI2

Change Condition = Direct Tunnel establishment Occurrence

Time Stamp = TIME4

Change Condition = Record closed

Time Stamp = TIME5

First container includes initial QoS values and corresponding volume counts. Second container includes new QoS values and corresponding volume counts before tariff time change. Third container includes the indication of location change and corresponding volume counts before the location change and after the tariff time change. Fourth container includes volume counts after the location change and contains the indication of Direct Tunnel establishment. Last container includes no volume count as it refers to Direct Tunnel establishment. The total volume counts can be itemised as shown in Table 5.1.2.2.25.2 (tariff1 is used before and tariff2 after the tariff time change):

Table 5.1.2.2.25.2: Itemised list of total volume count corresponding to table 5.1.2.2.25.1

		Container
QoS1+Tariff1	uplink = 1, downlink = 2	1
QoS2+Tariff1	uplink = 5, downlink = 6	2
QoS2+Tariff2	uplink = 13, downlink = 7	3+4
QoS1	uplink = 1, downlink = 2	1
QoS2	uplink = 18, downlink = 13	2+3+4
Tariff1	uplink = 6, downlink = 8	1+2
Tariff2	uplink = 13, downlink = 7	3+4
CGI1	uplink = 16, downlink = 11	1+2+3
CGI2	uplink = 3, downlink = 4	4
No Direct Tunnel	uplink = 19, downlink = 15	1+2+3+4
Direct Tunnel	-, –	5

The amount of data counted in the S-GW shall be the payload of the user plane at the S1-U/S4/S2interface. Therefore the data counted already includes the IP PDP bearer protocols i.e. IP or PPP.

The data volume counted in the SGSN is dependent on the system. For GSM SGSN the data volume is the payload of the SNDCP PDUs at the Gb interface. For UMTS-SGSN it is the GTP-U PDUs at the Iu-PS interface. Therefore, in both systems, 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 rules shall be 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, a GSM-SGSN shall only update the PDP CDR at the reception of the acknowledgement by the MS of the correct reception of a downstream packet. In other worlds, for inter SGSN RA update, the new SGSN shall update the PDP CDR record when a downstream packet sent by the old SGSN is received by the MS and acknowledged by the MS towards the new SGSN through the RA update complete message.

In UMTS, the not transferred downlink data can be accounted for in the S-CDR with "RNC Unsent Downlink Volume" field, which is the 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.

The following additional fields are applicable in the P-GW CDR when charging per IP-CAN session is active and IP-CAN bearer charging is being performed for the session:

– Charging Id In case of IP-CAN bearer specific container this contains the charging Id assigned to the bearer.

– RAT Type This field contains the RAT type for the current IP-CAN bearer.

– Access Availability Change Reason indicates the reason why the availability of an access is changed by the PCEF, i.e. RAN rule indication or Access usable/unusable as defined in TS 29.212 [220].

– Related Change of Charging Condition indicates the reason a related container was closed when the current container is indirectly closed and the supplemental information for the event. This information is applicable when charging per IP-CAN session is active for a multi-access PDN connection.

– Diagnostics In case of IP-CAN bearer specific container this contains the Diagnostics as per clause 5.1.2.2.11 associated to the bearer.

– Enhanced Diagnostics In case of IP-CAN bearer specific container this contains the Enhanced Diagnostics as per clause 5.1.2.2.13Aa associated to the bearer.

– CP CIoT EPS optimisation indicator This field contains the indication on whether Control Plane CIoT EPS optimisation is used for the transfer of the data volume captured by the container. This is included in the Traffic data container only if previous container’s change condition is "change in user plane to UE". Note the CP CIoT EPS Optimisation indicator field in SGW-CDR main level contains the CP CIoT EPS optimisation indicator value when SGW-CDR was opened.

– Serving PLMN Rate Control This field contains the Serving PLMN Rate Control applied by MME during the transfer of the data volume captured by the container (applicable to the SGW-CDR and PGW-CDR). For the SGW-CDR this is included in the Traffic data container only if previous container’s change condition is " Serving PLMN Rate Control change ". Note the Serving PLMN Rate Control field in SGW-CDR main level contains the Serving PLMN Rate Control when SGW-CDR was opened. For the PGW-CDR this is included when List of Traffic Data Volumes is present, charging per IP-CAN session is active and IP-CAN bearer charging is being performed for the session.

– APN Rate Control This field contains the APN Rate Control applied by PGW during the transfer of the data volume captured by the container (applicable only to the PGW-CDR). This is included in the Traffic data container only if previous container’s change condition is "APN Rate Control change ". Note the APN Rate Control field in PGW-CDR main level contains the APN Rate Control when PGW-CDR was opened.

5.1.2.2.26 Local Record Sequence Number

This field includes a unique record number created by this node. The number is allocated sequentially for each partial CDR (or whole CDR) 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, S-/P-GW address, TDF address, IP-Edge Address, Recording Entity).

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

5.1.2.2.27 Location Estimate

The Location Estimate field is providing an estimate of a geographic location of a target MS according to TS 29.002 [214].

5.1.2.2.28 Location Method

The Location Method identifier refers to the argument of LCS-MOLR that was invoked as defined in TS 24.080 [209].

5.1.2.2.29 Location Type

This field contains the type of the location as defined in TS 29.002 [214].

5.1.2.2.29A Low Priority Indicator

This field indicates if the PDN connection has a low priority, i.e. for Machine Type Communication.

5.1.2.2.29B NBIFOM Mode

This field indicates the NBIFOM mode selected by PCRF for a multi-access PDN connection, i.e. UE initiated or Network initiated as defined in TS 29.212 [220].

5.1.2.2.29C NBIFOM Support

This field indicates that NBIFOM was requested by the UE, supported and accepted by the network for the IP-CAN session or if NBIFOM is not supported for the IP-CAN session as defined in TS 29.212 [220].

5.1.2.2.30 Measurement Duration

This field contains the duration for the section of the location measurement corresponding to the Perform_Location_Request and Perform_Location_Response by the SGSN.

5.1.2.2.31 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 TS 23.040 [201].

5.1.2.2.32 MLC Number

This parameter refers to the ISDN (ITU-T Rec. E.164 [308]) number of a GMLC.

5.1.2.2.32A MME Name

This field contains the Diameter Identity of the serving MME.

5.1.2.2.32B MME Realm

This field contains the Diameter Realm Identity of the serving MME.

5.1.2.2.33 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 TS 24.008 [208].

5.1.2.2.34 MS Time Zone

This field contains the ‘Time Zone’ IE provided by the SGSN/MME and transferred to the S-GW/P-GW/TDF during the IP-CAN bearer activation/modification procedure as specified in TS 29.060 [215] and in TS 29.212 [220].

5.1.2.2.35 Network Initiated PDP Context

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

5.1.2.2.36 Node ID

This field contains an optional, operator configurable, identifier string for the node that had generated the CDR.
The Node ID may or may not be the DNS host name of the node.

5.1.2.2.37 Notification to MS user

This field contains the privacy notification to MS user that was applicable when the LR was invoked as defined in TS 29.002 [214].

5.1.2.2.37A Originating Address

This field is the Originating Address of the SME as defined in TS 23.040 [201].

5.1.2.2.37B P-GW Address IPv6

This field is the P-GW IPv6 Address used for the Control Plane, when both IPv4 and IPv6 addresses of the P-GW are available.

5.1.2.2.38 P-GW Address Used

These field is the serving P-GW IP Address for the Control Plane. If both an IPv4 and an IPv6 address of the P-GW is available, the P-GW shall include the IPv4 address in the CDR.

5.1.2.2.39 P-GW PLMN Identifier

This field is the P-GW PMLN Identifier (Mobile Country Code and Mobile Network Code).

The MCC and MNC are coded as described for "User Location Info" in TS 29.274 [223].

5.1.2.2.40 PDN Connection Charging ID

This field defines the PDN connection (IP-CAN session) Charging identifier to identify different records belonging to same PDN connection. For a PDN connection that is limited to use one single access at a time this field includes Charging Id of first IP-CAN bearer activated. Together with P-GW address this uniquely identifies the PDN connection.

For application based charging by the TDF:

– In case of GTP based connectivity, an "EPS default bearer Charging Identifier"

– In case of PMIP based connectivity, an "unique Charging Id"

is assigned by the P-GW and transferred to the TDF via the PCRF for the TDF session.

5.1.2.2.41 PDP Type

This field defines the PDP type, e.g. IP, or PPP as per TS 29.060 [215] .

5.1.2.2.42 PDP/PDN Type

This field defines the bearer type, e.g. IP, or PPP as per TS 29.060 [215] .

5.1.2.2.42A PDP/PDN Type Extension

This field defines the PDN type as per TS 29.061 [216] for Non-IP PDN Type.

5.1.2.2.43 Positioning Data

This information element is providing positioning data associated with a successful or unsuccessful location attempt for a target MS according TS 49.031 [227].

5.1.2.2.43A Presence Reporting Area Information

This field contains the Presence Reporting Area Information: Presence Reporting Area identifier(s) and the indication on whether the UE is inside or outside the Presence Reporting Area(s), as described in TS 29.274 [223].

5.1.2.2.44 Privacy Override

This parameter indicates if the LCS client overrides MS privacy when the GMLC and VMSC/SGSN for an MT-LR are in the same country as defined in TS 29.002 [214].

5.1.2.2.45 PS Furnish Charging Information

This field includes following information elements for IP-CAN bearer (PGW-CDR) , for TDF session (TDF-CDR) , or for the IP-CAN session (IPE-CDR):

PS Free Format Data

This field contains charging information sent by the OCS in the Diameter Credit-Control Credit-Control-Answer messages as defined in TS 32.251 [11]. The data can be sent either in one Diameter Credit-Control Credit-Control-Answer message or several Diameter Credit-Control Credit-Control-Answer messages with append indicator. This data is transferred transparently in the PS Furnish Charging Information field of the relevant call records.

If the PS Free Format Data is received more than once during one IP-CAN bearer for which an offline session is established, the append indicator defines whether the PS Free Format Data is appended to previous received PS Free Format Data and stored in the relevant record or the information of the last PS Free Format Data received is stored in the relevant record (the previous PS Free Format Data information shall be overwritten).

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

PS FFD Append Indicator:

This field contains an indicator whether PS free format data is to be appended to the PS free format data stored in previous partial CDR. This field is needed in CDR post processing to sort out valid PS free format data for that IP-CAN bearer from sequence of partial records. Creation of partial records is independent of received PS Free Format Data and thus valid PS free format data may be divided to different partial records.

If field is missing then the PS free format data in this CDR replaces all received PS 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 PS Free Format Data received during that partial record have append indicator. If one or more of the received PS Free Format Data for that PDP Context during the partial record do not have append indicator then this field shall be missing.

5.1.2.2.46 QoS Requested/QoS Negotiated

Quality of Service Requested contains the QoS desired by MS at IP-CAN bearer activation. QoS Negotiated indicates the applied QoS accepted by the network.

If a pre-Release ’99 only capable terminal is served, the applicable QoS parameters and their encoding in the CDRs are specified in TS 32.015 [228].

In all other cases, the applicable QoS attributes are defined in the "Quality of Service profile" in TS 23.060 [202], and their encoding in the CDR corresponds to the "Quality of Service profile" specified in TS 29.060 [215].

5.1.2.2.46A RAN End Time

This field contains the time when the RAN closes the volume container, and is available in the CDR for the secondary RAT.

5.1.2.2.46B RAN Start Time

This field contains the time when the RAN opens the volume container, and is available in the CDR for the secondary RAT.

5.1.2.2.47 RAT Type

Holds the value of RAT Type, as provided to S-GW and P-GW, specified in TS 29.061 [216] and also provided to the TDF as specified in TS 29.212 [220].

The field is provided by the SGSN/MME and transferred to the S-GW/P-GW during the IP-CAN bearer activation/modification and transferred to the TDF during the TDF session establishment/modification.

5.1.2.2.48 Record Extensions

This field enables network operators and/or manufacturers to add their own recommended extensions to the standard record definitions. This field contains a set of "management extensions" as defined in X.721 [305].
This is conditioned upon the existence of an extension.

5.1.2.2.49 Record Opening Time

This field contains the time stamp when the MS is attached to a SGSN (M-CDR) or IP-CAN bearer is activated in SGSN/S-GW/P-GW (S-CDR, SGW-CDR, PGW-CDR) or TDF session is established, or IP-CAN session is established (IPE-CDR), or record opening time on subsequent partial records (see TS 32.250 [4] for exact format).

Record opening reason does not have a separate field. For SGW/PGW/TDF/IPE -CDRs and M-CDR it can be derived from the field "Sequence number"; i.e. either a missing field or a value one (1) means activation of IP-CAN bearer (SGW/PGW-CDR) or GPRS attachment (M-CDR) or TDF session establishment (TDF-CDR) , or IP-CAN session establishment (IPE-CDR). For the S-CDR the field "SGSN change" also needs to be taken into account.

5.1.2.2.50 Record Sequence Number

This field contains a running sequence number employed to link the partial records generated in the SGSN/SGW/PGW for a particular MM context or IP-CAN bearer, or IP-CAN session, or TDF session (characterised with the same Charging ID and PGW address pair). For M-CDR or S-CDR the sequence number always restarts from one (1) after an 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/SGW/PGW/TDF/IP-Edge (e.g. inter-SGSN routing area update can result to two M-CDR or two S-CDRs without sequence number and field "SGSN change" present in the second record).

5.1.2.2.51 Record Type

The field identifies the type of the record e.g. S-CDR, SGW-CDR, PGW-CDR, M-CDR, S-SMO-CDR, TDF-CDR, IPE-CDR and S-SMT-CDR.

5.1.2.2.52 Recording Entity Number

This field contains the E.164 number assigned to the entity that produced the record. For further details see TS 23.003 [200].

5.1.2.2.52A Retransmission

This parameter, when present, indicates that information from retransmitted Diameter ACRs has been used in this CDR.

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

5.1.2.2.54 Routing Area Code/Location/Cell Identifier/Change of location

These fields can occur only in SGSN generated CDRs. 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 GSM the Cell Identifier is defined by the Cell Identity (CI) and in UMTS 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 location field contains a combination of the location area code (LAC), cell identity (CI) and MCC+MNC of the cell in which the served party is currently located.

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 [208] and the SAC according TS 25.413 [212].

5.1.2.2.54A S-GW Address IPv6

This field is the S-GW IPv6 Address used for the Control Plane, when both IPv4 and IPv6 addresses of the S-GW are available.

5.1.2.2.55 S-GW Address Used

These field is the serving S-GW IP Address for the Control Plane. If both an IPv4 and an IPv6 address of the S-GW is available, the S-GW shall include the IPv4 address in the CDR.

5.1.2.2.56 S-GW Change

This field is present only in the SGW-CDR ,ePDG-CDR or TWAG-CDR to indicate that this is the first record after an inter serving node change (change from SGW, ePDG, TWAG, HSGW).

5.1.2.2.56A Secondary RAT Type

Holds the value of Secondary RAT Type, as provided by the RAN.

The field is provided by the RAN and transferred to the S-GW/P-GW in the RAN Traffic Volume element.

5.1.2.2.57 Served 3GPP2 MEID

This field contains the Mobile Equipment Identity of the user’s terminal in 3GPP2 access, and the content is defined in TS 29.272 [222].

5.1.2.2.57A Served Fixed Subscriber Id

This field contains the subscriber identity, as defined in Broadband Forum TR 134 [601], used by the Fixed User (i.e. Fixed Device or RG) for Subscriber IP session in fixed broadband access network.

5.1.2.2.58 Served IMEI

This field contains the International Mobile Equipment Identity (IMEI) of the equipment served, if available. 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 specified in TS 23.003 [200] and the encoding defined in TS 29.274 [223].

5.1.2.2.58A SCS/AS Address

This field contains the Address of SCS/AS.

5.1.2.2.59 void

5.1.2.2.60 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 TS 23.003 [200].

5.1.2.2.60A Served IP-CAN session Address

This field contains the IP address for the IP-CAN session. This is a network layer address i.e. of type IPv4 address or IPv6 prefix. The address for each IP-CAN session type is allocated either temporarily or permanently (see "Dynamic Address Flag"). This parameter shall be present except when both the IP-CAN session type is PPP and dynamic address assignment is used.

5.1.2.2.60B Served IP-CAN session Address Extension

This field contains the IPv4 address for the IP-CAN session when dual-stack IPv4 IPv6 is used, and the IPv6 prefix is included in Served IP-CAN session Address or Served IP-CAN Address.

5.1.2.2.61 Served MN NAI

This field contains the Mobile identifier of the served user, in NAI format based on IMSI, as defined TS 23.003 [200].

5.1.2.2.62 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. In case of multi-numbering the MSISDN stored in a CDR will be the primary MSISDN of the calling party.

The structure of the MSISDN is defined in TS 23.003 [200].

5.1.2.2.63 Served PDP Address

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

5.1.2.2.64 Served PDP/PDN Address

This field contains the IP address for the PDN connection (PDP context, IP-CAN bearer). This is a network layer address i.e. of type IPv4 address or IPv6 prefix. The address for each Bearer type is allocated either temporarily or permanently (see "Dynamic Address Flag"). This parameter shall be present except when both the Bearer type is PPP and dynamic address assignment is used.

5.1.2.2.64A Served PDP/PDN Address Extension

This field contains the IPv4 address for the PDN connection (PDP context, IP-CAN bearer) when dual-stack IPv4 IPv6 is used, and the IPv6 prefix is included in Served PDP Address or Served PDP/PDN Address.

5.1.2.2.64B Served PDP/PDN Address prefix length

This field contains the prefix length of an IPv6 typed Served PDP/PDN Address. The field needs not available for prefix length of 64 bits, as in this case the 64 bit prefix length default shall be assumed.

5.1.2.2.65 Service Centre Address

This field contains a E.164 number identifying a particular service centre e.g. Short Message Service (SMS) centre (see TS 23.040 [201]).

5.1.2.2.66 Serving Node Address

These fields contain one or several control plane IP addresses of SGSN, MME, ePDG, HSGW, TWAG or S-GW, which have been connected during the record.

If both an IPv4 and an IPv6 address of the SGSN/S-GW/MME/ePDG/HSGW/TWAG are available, the S-GW/P-GW/TDF shall include the IPv4 address in the CDR.

5.1.2.2.66A Serving Node IPv6 Address

These fields contain one or several control plane IPv6 addresses, in case of IPv4v6 dual stack, of SGSN, MME, ePDG, HSGW, TWAG or S-GW, which have been connected during the record, when both IPv4 and IPv6 addresses of the node are available.

5.1.2.2.67 Serving Node PLMN Identifier

This field contains the PLMN Identifier (Mobile Country Code and Mobile Network Code) serving the UE.

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

5.1.2.2.68 Serving Node Type

These fields contain one or several serving node types in control plane of S-GW or P-GW, which have been connected during the record. The serving node types listed here map to the serving node addresses listed in the field "Serving node Address" in sequence.

For Originated and Terminated SMS CDRs, this field contains the Node Type which generates the CDRs, i.e. SGSN or MME.

5.1.2.2.68A Serving PLMN Rate Control

This field contains the Serving PLMN Rate Control as specified in TS 23.401 [245], which is used during the record for the PDN connection to the PGW.

5.1.2.2.68B SGi PtP Tunnelling Method

This field indicates whether SGi PtP tunnelling method is based on UDP/IP or other methods for a non-IP PDN type PDN connection.

5.1.2.2.69 SGSN Address

These fields contain one or several IP addresses of SGSN. The IP address of the SGSN can be either control plane address or user plane address.

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

The M-CDR fields only contain the address of the current SGSN.

If both an IPv4 and an IPv6 address of the SGSN are available, the SGSNs shall include the IPv4 address in the CDR.

5.1.2.2.69A Void

(Void).

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

5.1.2.2.71 Short Message Service (SMS) Result

5.1.2.2.72 Start Time

This field contains the time when the IP-CAN session starts at the S-GW/P-GW/IP-Edge or TDF session starts at TDF, available in the CDR for the first bearer in an IP-CAN session in case of S-GW/P-GW/IP-Edge or, alternatively, available in the CDR for the TDF session start.

5.1.2.2.73 Stop Time

This field contains the time when the IP-CAN session is terminated at the S-GW/P-GW/IP-Edge or TDF session terminated at the TDF, available in the CDR for the last bearer in an IP-CAN session in case of S-GW/P-GW/IP-Edge or, alternatively, available in the CDR for the TDF session stop.

5.1.2.2.73aA TDF Address Used

This field is the serving TDF IP Address for the Control Plane. If both an IPv4 and an IPv6 addresses of the TDF are available, the TDF shall include the IPv4 address in the CDR. It contains the TDF-IP-Address as described in TS 29.212 [220].

5.1.2.2.73bA TDF IPv6 Address Used

This field is the serving TDF IPv6 Address for the Control Plane, when both IPv4 and IPv6 addresses of the TDF are available.

5.1.2.2.73cA TDF PLMN Identifier

This field is the TDF PMLN Identifier (Mobile Country Code and Mobile Network Code).

5.1.2.2.73cAa Traffic Steering Policy Identifier Uplink

This field contains traffic steering policy identifier in the uplink direction as specified in TS 23.203[203].

5.1.2.2.73cAb Traffic Steering Policy Identifier Downlink

This field contains traffic steering policy identifier in the downlink direction as specified in TS 23.203[203].

5.1.2.2.73dA TWAG Address Used

This field is the serving TWAG IP Address for the Control Plane. If both an IPv4 and an IPv6 address of the TWAG is available, the TWAG shall include the IPv4 address in the CDR.

5.1.2.2.73eA TWAG IPv6 Address

This field is the serving TWAG IPv6 Address for the Control Plane, when both IPv4 and IPv6 addresses of the TWAG are available.

5.1.2.2.73A TWAN User Location Information

This field holds the UE location in a Trusted WLAN Access Network (defined as TWAN Identifier in TS 29.274 [223]).

5.1.2.2.73B UNI PDU CP Only Flag

This field contains an indication on whether this PDN connection is applied with "Control Plane Only flag", i.e. transfer using Control Plane NAS PDUs only, when Control Plane CIoT EPS Optimisation is enabled. This field is missing if both, user plane and control plane UNI for PDU transfer (i.e. S1-U and S11-U from S-GW) are allowed, when Control Plane CIoT EPS Optimisation is enabled.

5.1.2.2.74 User CSG Information

This field contains the "User CSG Information" status of the user accessing a CSG cell: it comprises CSG ID within the PLMN, Access mode and indication on CSG membership for the user when hybrid access applies, as defined in TS 29.060 [215] for GPRS case, and in TS 29.274 [223] for EPC case.

5.1.2.2.75 User Location Information

This field contains the User Location Information as described in

– TS 29.060 [215] for GTP case (e.g. CGI, SAI, RAI),

– TS 29.274 [223] for eGTP case (e.g. CGI, SAI, RAI TAI and ECGI) and

– TS 29.275 [224] for PMIP case.

The field is provided by the SGSN/MME and transferred to the S-GW/P-GW/TDF during the IP-CAN bearer activation/modification and/or TDF session establishment/modification.

5.1.2.2.75A User Location Information Time

This field contains the time at which the UE was last known to be in the location which is reported during bearer deactivation or UE detach procedure.

5.1.2.2.76 Void

5.1.2.2.77 UWAN User Location Information

This field contains the UE location in an Untrusted Wireless Access Network (UWAN) which includes the UE local IP address and optionally either UDP source port number (if NAT is detected) or TCP source port number. It may also include WLAN location information the ePDG may have received from the 3GPP AAA server about the UE, as TWAN Identifier defined in TS 29.274 [223].

5.1.2.3 Void

5.1.2.4 CP data transfer domain CDR parameters

5.1.2.4.1 Introduction

This subclause contains the description of the CDR parameters that are specific to the CP data transfer domain CDR types as specified in TS 32.253 [13].

5.1.2.4.2 Access Point Name (APN) Network Identifier

These fields contain the actual connected Access Point Name Network Identifier. APN selection by the MME for SCEF based delivery mechanism selection for non-IP data delivery is specified in TS 23.682 [243]

The APN Network Identifier (NI portion) is part of APN, which format is specified in TS 23.003 [200]. To represent the APN NI in the CPCN CDRs, the "dot" notation shall be used.

5.1.2.4.3 APN Rate Control

This field contains the APN Rate Control as specified in TS 29.128 [244], which is used during the record for the PDN connection to the SCEF.

5.1.2.4.4 Cause for Record Closing

This field contains a reason for the release of the CDR. In case of Rf interface is used, it is derived, when received, from Change-Condition AVP at PS-information AVP level defined in TS 32.299 [50] used for CP data transfer. The following is included:

– normal release: PDN connection to SCEF release; It corresponds to "Normal Release" in Change-Condition AVP.

– abnormal termination (PDN connection to SCEF); It corresponds to "Abnormal Release" in Change-Condition AVP.

– data volume limit; It corresponds to "Volume Limit" in Change-Condition AVP.

– time (duration) limit; It corresponds to "Time Limit" in Change-Condition AVP.

– maximum number of NIDD submissions. It corresponds to "Maximum number of NIDD submissions" in Change-Condition AVP.

– Serving Node change; It corresponds to "Serving Node Change" in Change-Condition AVP and is used for MME change.

– For SCEF, PLMN change; It corresponds to "PLMN Change" in Change-Condition AVP.

– For SCEF: APN Rate Control Change: It corresponds to "APN Rate Control Change" in Change-Condition AVP.

– Serving PLMN Rate Control Change: It corresponds to "Serving PLMN Rate Control Change" in Change-Condition AVP.

– RAT type Change: It corresponds to "RAT Change " in Change-Condition AVP.

– management intervention (request due to O&M reasons); It corresponds to "Management Intervention" in Change-Condition AVP.

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

5.1.2.4.5 Charging Characteristics

The Charging Characteristics field allows the operator to apply different kind of charging methods in the CDRs.
A subscriber may have Charging Characteristics assigned to his subscription. These characteristics can be supplied by the HSS and selected according to the rules specified in Annex X of TS 32.253 [13].

This information can be used by the CPCNs (SCEF, IWK-SCEF, MME) to activate charging generation and e.g. control the closure of the CDR or the traffic volume containers, and applied charging characteristics is included in CDRs transmitted via the Ga/Rf reference point. It can also be used in nodes handling the CDRs (e.g., the CGF or the billing system) to influence the CDR processing priority and routing. These functions are accomplished by specifying the charging characteristics as sets of charging profiles and the expected behaviour associated with each profile.
The interpretations of the profiles and their associated behaviours can be different for each PLMN operator and are not subject to standardisation. In the present document only the charging characteristic formats and selection modes are specified.

The format of charging characteristics field is depicted in Figure 5.1.2.4.5.1. Each Bx (x =0..15) refers to a specific behaviour defined on a per-Operator basis, indicated as active when set to "1" value. See Annex X of TS 32.253 [13]. for guidance on how behaviours could be defined.

Figure 5.1.2.4.5.1: Charging Characteristics flags

5.1.2.4.6 Charging Characteristics selection mode

This field indicates the charging characteristic type that the CPCNs (SCEF, IWK-SCEF, MME) applied to the CDR. In the MME the allowed values are:

– Home default;

– Roaming default;

– APN specific;

– Subscription specific.

In the IWK-SCEF/SCEF the allowed values are:

– Home default;

– Roaming default;

– Serving node supplied.

Further details are provided in TS 32.253 [13] Annex X.

5.1.2.4.7 Charging ID

This field is a charging identifier, which can be used together with SCEF Identity to identify all records produced in CPCN Nodes involved in a single PDN connection to a SCEF. Charging ID is generated by SCEF at PDN connection establishment and transferred to IWK-SCEF/MME., The charging ID is transferred to the new MME, at MME change during the lifetime of the PDN connection.

Different SCEFs 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 SCEFs address and optionally (if still ambiguous) with the record opening time stamp.

5.1.2.4.8 Diagnostics

This field includes a more detailed technical reason for the releases of the connection.
The diagnostics may also be extended to include manufacturer and network specific information.

5.1.2.4.9 Duration

This field contains the relevant duration in seconds for PDN connection to SCEF in CPCN Node CDRs.

It is the duration from Record Opening Time to record closure. For partial records this is the duration of the individual partial record and not the cumulative duration.

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.

5.1.2.4.10 External-Identifier

This field contains the external identifier of the UE, which identifies a subscription associated to an IMSI, as specified in TS 23.003 [200].

5.1.2.4.11 List of NIDD Submissions

This list applicable in CPDT-SCE-CDR and CPDT-SNN-CDR, includes one or more containers.

Each container includes the following fields:

– Submission Timestamp;

– Event Timestamp;

– Data Volume Uplink.

– Data Volume Downlink.

– Service Change Condition.

– Submission Result Code.

SubmissionTimestamp is a time stamp, which defines the moment when the data transfer request NIDD submission was submitted to the CPCN Node.

Event Timestamp is a time stamp, which defines the moment when the event triggered the generation of charging information from the CPCN Node, for the NIDD submission.

Data Volume Uplink and Downlink includes the number of octets transmitted during the NIDD submission.

Service Change Condition contains the reason for the NIDD submission container, e.g. NIDD submission response receipt, NIDD submission response sending, NIDD delivery to the UE, NIDD submission timeout, NIDD delivery from the UE error.

Submission Result Code defines the result of NIDD submission.

5.1.2.4.12 Local Record Sequence Number

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

5.1.2.4.13 Node ID

This field contains an optional, operator configurable, identifier string for the node that had generated the CDR.
The Node ID may or may not be the DNS host name of the node.

5.1.2.4.14 RAT Type

This field contains the Radio Access Technology (RAT) type used for the NIDD submissions.

5.1.2.4.15 Record Extensions

5.1.2.4.16 Record Opening Time

This field contains the time stamp when the PDN connection to SCEF is activated in CPDT-SCE-CDR, CPDT-IWK-CDR, CPDT-MME-CDR, or record opening time on subsequent partial records.

Record opening reason does not have a separate field. For CPDT-SCE-CDR, CPDT-IWK-CDR and CPDT-MME-CDR, it can be derived from the field "Sequence number"; i.e. either a missing field or a value one (1) means activation of PDN connection to SCEF.

5.1.2.4.17 Record Sequence Number

This field contains a running sequence number employed to link the partial records generated in the SCEF/IWK-SCEF/MME for a particular PDN connection to SCEF (characterised with the same Charging ID and SCEF ID pair). The Record Sequence Number starts from one (1). The Record Sequence Number is missing if the record is the only one produced in the SCEF/IWK-SCEF/MME.

5.1.2.4.18 Record Type

The field identifies the type of the record i.e. CPCN-SCE-CDR and CPCN-SNN-CDR.

5.1.2.4.19 Retransmission

This parameter, when present, indicates that information from retransmitted Diameter ACRs has been used in this CDR.

5.1.2.4.20 SCEF ID

This field contains the Diameter Identity of the SCEF serving the PDN connection.

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

The structure of the IMSI is defined in TS 23.003 [200].

5.1.2.4.22 Served MSISDN

The structure of the MSISDN is defined in TS 23.003 [200].

5.1.2.4.23 Serving Node Identity

This field contains the Diameter Identity of the serving node (i.e. MME) connected during the record for the PDN connection to the SCEF.

5.1.2.4.24 Serving Node PLMN Identifier

This field contains the PLMN Identifier (Mobile Country Code and Mobile Network Code) serving the UE.

5.1.2.4.25 Serving PLMN Rate Control

This field contains the Serving PLMN Rate Control as specified in TS 29.128 [244], which is used during the record for the PDN connection to the SCEF.

5.1.2.5 Exposure Function API CDR parameters

5.1.2.5.1 Introduction

This clause contains the description of each field of the Exposure Function API CDRs specified in TS 32.254 [14].

5.1.2.5.2 API Content

This field holds the API content (e.g. location, Monitoring Type) used in the T8 transaction for the API invocation request, if available.

5.1.2.5.3 API Direction

This field holds the direction to indicate the API invocation or API notification.

5.1.2.5.4 API Identifier

This field holds the identity of API for each API invocation.

5.1.2.5.5 API Invocation Timestamp

This field holds the time stamp when the API invocation request is submitted to the SCEF.

5.1.2.5.6 API Network Service Node

This field holds the identifier of the network element as defined in TS 23.682[243] that triggers the API notification.

5.1.2.5.7 API Result Code

This field holds the result of API Invocation.

5.1.2.5.8 API Size

This field holds the size of API payload.

5.1.2.5.9 Event Timestamp

This field holds the time stamp of the event reported for the generation of charging information from the SCEF, for the northbound exposure function API.

5.1.2.5.10 External Identifier

This field holds the external Identifier identifying the served party associated to the IMSI or MSISDN or External Group ID, if available.

5.1.2.5.11 Local Record Sequence Number

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

5.1.2.5.12 Node Id

Name of the recording entity.

5.1.2.5.13 Record Extensions

A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension.

5.1.2.5.14 Record Type

SCEF exposure function API record.

5.1.2.5.15 Retransmission

This parameter, when present, indicates that information from retransmitted Diameter ACRs has been used in this CDR.

5.1.2.5.16 SCEF Address

This parameter holds the IP address of SCEF.

5.1.2.5.17 SCEF ID

This parameter holds the Diameter identity of the SCEF used for this API invocation.

5.1.2.5.18 SCS AS Address

This field holds the IP address of SCS/AS

5.1.2.5.19 TLTRI

This field holds the T8 Long Term Transaction Reference ID.