6 Definition of charging information
32.2503GPPCharging managementCircuit Switched (CS) domain chargingRelease 17Telecommunication managementTS
6.0 General
This clause provides Stage 3 specifications of the CDR type and content for the 3GPP CS domain. For each of the CDR types listed in clause 5.2.3, a parameter table, which gives a short description of the parameters, is provided. The detailed specification of the CDR parameters and their encoding is contained in TS 32.298 [51], while annex A and TS 32.297 [52] specify the details of the CDR file transfer to the BD.
6.1 Data description for CS domain offline charging
6.1.1 Diameter message contents
Not applicable. Refer to clause 5.2.2 for further information.
6.1.2 GTP’ message contents
Not applicable. Refer to clause 5.2.4 for further information.
6.1.3 CDR description on the Bc reference point
6.1.3.0 Introduction
Dedicated types of CDRs can be generated in the CS domain, as specified in clause 5.2.3. The content of each CDR type is defined in one of the tables that are part of this clause. For each CDR type the parameter definition includes the parameter name, description and category.
The CS nodes shall be able to provide the CDRs at the Billing System interface in the format and content described in the present document. Additional CDR formats and contents, generated by the CS nodes, may be available at the interface to the billing system to meet the requirements of the billing system, these are outside of the scope of 3GPP standardization.
The following tables provide a brief description of each CDR parameter and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. Full definitions of the parameters, sorted by the parameter name in alphabetical order, are provided in TS 32.298 [51]. TS 32.298 [51] also specifies the encoding of the CDRs and their parameters on the Bc reference point, while the CDR files transferred on Bc are specified in TS 32.297 [52].
6.1.3.1 Mobile originated call attempt
If the generation of these records is enabled then an MOC record shall be created for each outgoing call attempt made by a mobile station. These MOC records shall be produced in the originating MSC.
Table 6.1.3.1: MOC record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
M |
M |
IMSI of the calling party. |
Served IMEI |
C |
C |
IMEI of the calling ME, if available. |
Served MSISDN |
OM |
OM |
The primary MSISDN of the calling party. |
Called Number |
M |
M |
The address of the called party i.e. the number dialled by the calling subscriber. |
Translated Number |
OC |
OC |
The called number after digit translation within the MSC (if applicable) |
Connected Number |
OC |
OC |
The number of the connected party if different to the Called Number |
Roaming Number |
OC |
OC |
The Mobile Station Roaming Number employed to route this connection, if applicable. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
Incoming TKGP |
OM |
OC |
The MSC trunk group on which the call originated , usually from the BSS. If available in 3G, this parameter shall be supplied. |
Outgoing TKGP |
OM |
OC |
The trunk group on which the call left the MSC. If available in 3G, this parameter shall be supplied. |
Location |
M |
M |
The identity of the cell or the SAC at the time of CDR creation, including the location area code and MCC+MNC. |
Change of Location |
OC |
OC |
A list of changes in Location Area Code / Service Area Code / Cell Id and MCC+MNC. Each time-stamped. |
Basic service |
M |
M |
Bearer or teleservice employed. |
Rate Indication |
OC |
OC |
Present if "rate adaption" parameters for the basic service were signalled between the MS/UE and the network, see 3GPP TS 24.008 [208]. |
Transparency Indicator |
C |
C |
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode. |
Change Of Service |
OC |
OC |
A list of changes of basic service during a connection each time-stamped. |
Supp. Services |
C |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
AOC Parameters |
OC |
OC |
The charge advice parameters sent to the MS on call set-up. This field shall be supplied only when AoC parameters have been sent. |
Change of AOC Parameters |
OC |
OC |
New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. This field shall be supplied only when AoC parameters have been sent. |
MS Classmark |
M |
M |
The mobile station classmark employed on call set-up. |
Change of Classmark |
OC |
OC |
A list of changes to the classmark during the connection each time-stamped |
Event time stamps: |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer: time of answer (for successful calls) Release time: time of traffic channel release This field contains the MS Time Zone. |
Call duration |
M |
M |
The chargeable duration of the connection for successful calls, the holding time for call attempts. |
Data volume |
C |
– |
The number of data segments transmitted if available at the MSC |
Radio Channel Requested |
OM |
– |
The type of radio traffic channel (full / half etc.) requested by the MS. |
Radio Channel Used |
M |
– |
The type of radio channel actually used (full or half rate). |
Change of Radio Channel |
OC |
– |
A list of changes each time stamped |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Additional Chg. Info |
OC |
OC |
Charge/no charge indicator and additional charging parameters, when available. |
ICS I2 active Flag |
C |
C |
This field indicates that the MSC is IMS registered on the UE’s behalf during the session for service centralization in the IMS. |
IMS Charging Identifier |
OM |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the enhanced MSC server with SIP interface. |
IMS Private user Identity |
OM |
OM |
This field contains the IMS Private User Identity and Public User Identity specifically reserved for IMS registrations. |
GsmSCF address |
C |
C |
Identifies the CAMEL server serving the subscriber. Shall be present only if CAMEL is applied. |
Service key |
C |
C |
The CAMEL service logic to be applied. Shall be present only if CAMEL is applied. |
Network call reference |
C |
C |
An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. |
MSC Address |
C |
C |
This field contains the E.164 number assigned to the MSC that generated the network call reference. Shall be present only if CAMEL is applied. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Number of HSCSD Channels Requested |
C |
– |
The maximum number of HSCSD channels requested as received from the MS at call set-up. Shall only be present for HSCSD connections. |
Number of HSCSD Channels Allocated |
C |
– |
The number of HSCSD channels allocated to the MS at call set-up. Shall only be present for HSCSD connections. |
Change of HSCSD Parameters |
C |
– |
A list of network or user initiated changes of number of HSCSD channels during a connection each time-stamped. Shall only be present in case of an HSCSD call, if the basic HSCSD parameters are modified due the user or network initiated modification procedure. |
Fixed Network User Rate |
OC |
OC |
Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. |
Air Interface User Rate Requested |
C |
– |
The total Air Interface User Rate Requested by the MS at call set-up. Shall only be present for non-transparent HSCSD connections. |
Channel Coding Accepted |
C |
– |
A list of the traffic channels codings accepted by the MS. Shall only be present for HSCSD connections. |
Channel Coding Used |
C |
– |
The traffic channels codings negotiated between the MS and the network at call set-up. Shall only be present for HSCSD connections. |
Guaranteed bit rate |
– |
OC |
Describes the bit-rate the UMTS bearer service shall guarantee to the user or application. Guaranteed Bit Rate may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. Shall only be present for UMTS data connections. |
Maximum bit rate |
– |
OC |
Maximum Bit Rate can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations, 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections. |
Speech Version Supported |
OM |
– |
Speech version supported by the MS with highest priority indicated by MS |
Speech Version Used |
OM |
– |
Speech version used for that call |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied. |
Level of CAMEL service |
OC |
OC |
Indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied. |
Free format data append indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied. |
Default call handling 2 |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling for 2nd service such as dialled service. This field shall be present only if default call handling has been applied. |
GsmSCF address 2 |
C |
C |
Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Service key 2 |
C |
C |
The CAMEL service logic to be applied for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Free format Data 2 |
C |
C |
This field contains data sent by the gsmSCF in the FCI message(s) for 2nd service such as dialled service. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for 2nd service. |
Free format data append indicator 2 |
C |
C |
Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for 2nd service. |
System Type |
– |
M |
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. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
OC |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
Reason for service change |
– |
OC |
Indicates the type of service change and fallback. |
Service change initiator |
– |
OC |
Indicates the service change initiator. |
Redial Attempt |
OC |
OC |
Indicates to the network that a call is the result of a redial attempt to switch from speech to multimedia or vice-versa |
Record extensions |
OC |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
6.1.3.2 Mobile originated emergency call attempt
If the generation of MOC records is enabled then an MOC emergency record shall be created for each outgoing emergency call attempt made by a mobile station. These records shall be produced in the originating MSC.
Table 6.1.3.2: MOC emergency record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
C |
C |
IMSI of the calling party in case of an emergency call with a SIM card. |
Served IMEI |
C |
C |
IMEI of the calling mobile equipment if available. |
Served MSISDN |
OC |
OC |
The primary MSISDN of the calling party, if supplied by the UE. |
Translated Number |
OC |
OC |
The called number after digit translation within the MSC (if applicable) |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
Incoming TKGP |
OM |
OC |
The MSC trunk group on which the call originated, usually from the BSS. If available in 3G, this parameter shall be supplied. |
Outgoing TKGP |
OM |
OC |
The trunk group on which the call left the MSC. If available in 3G, this parameter shall be supplied. |
Location |
M |
M |
The identity of the cell or the SAC in which the call originated including the location area code and MCC+MNC. |
Change of Location |
OC |
OC |
A list of changes in Location Area Code / Service Area Code / Cell Id and MCC+MNC. Each time-stamped. |
Basic service |
M |
M |
Teleservice ’emergency call’. |
AOC Parameters |
OC |
OC |
The charge advice parameters sent to the MS on call set-up. This field shall be supplied only when AoC parameters have been sent. |
Change of AOC Parameters |
OC |
OC |
New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. This field shall be supplied only when AoC parameters have been sent. |
MS Classmark |
M |
M |
The mobile station classmark employed on call set-up. |
Change of classmark |
OC |
OC |
A list of changes to the classmark during the connection each time-stamped |
Event time stamps |
C |
C |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) |
C |
C |
Answer time: time of answer (for successful calls) |
|
OM |
OM |
Release time: time of traffic channel release |
|
Call duration |
M |
M |
The chargeable duration of the connection for successful calls, the holding time for call attempts. |
Radio Channel Requested |
OM |
– |
The type of radio traffic channel (full / half etc.) requested by the MS. |
Radio Channel Used |
M |
– |
The type of radio channel used (full or half rate). |
Change of Radio Channel |
OC |
– |
A list of changes each time stamped |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
System Type |
– |
M |
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. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.3 Mobile originated call forwarding attempt
If the generation of MOC records is enabled in the forwarding MSC then the forwarding MSC shall produce an MOC record for the forwarded-leg of the call.
Table 6.1.3.3: MOC, call forwarding record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
M |
M |
IMSI of the forwarding party. |
Served MSISDN |
OM |
OM |
The MSISDN of the forwarding party. |
Calling Number |
Oc |
Oc |
The address of the calling party. |
Called Number |
M |
M |
The address of the "forwarded-to" party. |
Translated Number |
OC |
OC |
The called number after digit translation within the MSC (if applicable) |
Connected Number |
OC |
OC |
The number of the connected party if different to the Called Number |
Roaming Number |
OC |
OC |
The Mobile Station Roaming Number employed to route this connection, if applicable. |
Recording Entity |
M |
M |
The E.164 number of the forwarding MSC |
Incoming TKGP |
OM |
OM |
The MSC trunk group on which the call originated at the forwarding MSC. |
Outgoing TKGP |
OM |
OM |
The trunk group on which the call left the forwarding MSC |
Basic service |
C |
C |
Bearer or teleservice employed, not always available e.g. in case of call forwarding unconditional. |
Rate Adaptation |
OC |
OC |
Present if "rate adaption" parameters for the basic service were signalled between the MS/UE and the network, see 3GPP TS 24.008 [208]. May not always be available in this CDR type. |
Transparency Indicator |
C |
C |
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode. |
Fixed Network User Rate |
OC |
OC |
Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. |
ChangeOfService |
OC |
OC |
A list of changes of basic service during a connection each time-stamped. |
Supplementary Services |
C |
C |
Supplementary services invoked as a result of this connection, if this information is available to the forwarding node. This field shall be present when one or more supplementary services have been invoked. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer time: time of answer (for successful calls) Release time: time of traffic channel release |
Call duration |
M |
M |
The chargeable duration of the connection for successful calls, the holding time of call attempts. |
Data volume |
C |
– |
The number of data segments transmitted if available at the MSC |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Additional Charging Info |
OC |
O |
Charge/no charge indicator and additional charging parameters, when available. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
GsmSCF address |
C |
C |
Identifies the CAMEL server serving the subscriber. Shall be present only if CAMEL is applied. |
Service key |
C |
C |
The CAMEL service logic to be applied. Shall be present only if CAMEL is applied. |
Network call reference |
C |
C |
An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. |
MSC Address |
C |
C |
This field contains the E.164 number assigned to the MSC that generated the network call reference. Shall be present only if CAMEL is applied. |
CAMEL initiated CF indicator |
C |
C |
Indicates that the CAMEL server initiated call forwarding. Shall be present only if CAMEL is applied. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied. |
Level of CAMEL service |
OC |
OC |
Indicator of the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied. |
Free format data append indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied. |
Default call handling 2 |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling for 2nd service such as dialled service. This field shall be present only if default call handling has been applied. |
GsmSCF address 2 |
C |
C |
Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Service key 2 |
C |
C |
The CAMEL service logic to be applied for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Free format Data 2 |
C |
C |
This field contains data sent by the gsmSCF in the FCI message(s) for 2nd service such as dialled service. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for 2nd service. |
Free format data append indicator 2 |
C |
C |
Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for 2nd service. |
Location Routing Number |
– |
Oc |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.4 Mobile terminated call attempt
If the generation of these records is enabled, then an MTC record shall be created for each incoming call attempt made for a mobile station. The MTC records shall be produced in the terminating MSC.
Table 6.1.3.4: MTC record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile Terminated. |
Served IMSI |
M |
M |
IMSI of the called party. |
Served IMEI |
C |
C |
IMEI of the called ME, if available. |
Served MSISDN |
OM |
OM |
The MSISDN of the called party. |
Calling Number |
C |
C |
The number of the calling party if available. |
Connected Number |
OC |
OC |
Only relevant in case of call forwarding where the "forwarded-to" number is recorded. |
Recording Entity |
M |
M |
The E.164 number of the visited (terminating) MSC |
Incoming TKGP |
OM |
OM |
The MSC trunk group on which the call originated. |
Outgoing TKGP |
OM |
OC |
The trunk group on which the call left the MSC, usually to the BSS. If available in 3G, this parameter shall be supplied. |
Location |
C |
C |
The identity of the cell or the SAC occupied by the called party when the call was set up, including the location area code and MCC+MNC. |
Change of Location |
OC |
OC |
A list of changes in Location Area Code / Service Area Code / Cell Id and MCC+MNC. Each time-stamped. |
Basic Service |
M |
M |
Bearer or teleservice employed |
Rate Adaptation |
OC |
OC |
Present if "rate adaption" parameters for the basic service were signalled between the MS/UE and the network, see 3GPP TS 24.008 [208]. |
Transparency Indicator |
C |
C |
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode. |
Change of Service |
OC |
OC |
A list of changes of basic service during a connection each time-stamped. |
Supplementary services |
C |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
AOC Parameters |
OC |
OC |
The charge advice parameters sent to the MS on call set-up. This field shall be supplied only when AoC parameters have been sent. |
Change of AOC Parameters |
OC |
OC |
New AOC parameters sent to the MS e.g. as a result of a tariff switch-over, including the time at which the new set was applied. This field shall be supplied only when AoC parameters have been sent. |
MS Classmark |
M |
M |
The mobile station class mark. |
Change of Classmark |
OC |
OC |
A list of changes to the classmark during the connection each time-stamped |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of traffic channel seizure for unsuccessful call attempts Answer time: time of answer for successful calls Release time: time of traffic channel release |
Call duration |
M |
M |
The chargeable duration of the connection if successful, the holding time of the call if unsuccessful. |
Data volume |
C |
– |
The number of data segments transmitted, if available at the MSC |
Radio Channel Requested |
OM |
– |
The type of radio traffic channel (full / half etc.) requested by the MS. |
Radio Channel Used |
M |
– |
The type of radio channel used (full or half rate). |
Change of Raddio Channel |
OC |
– |
A list of changes each time stamped |
Cause for Termination |
M |
M |
The reason for the release of the call. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions at the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Additional Chg. Info |
OC |
OC |
Charge/no charge indicator and additional charging parameters, when available. |
ICS I2 active Flag |
C |
C |
This field indicates that the MSC is IMS registered on the UE’s behalf during the session for service centralization in the IMS. |
IMS Charging Identifier |
OM |
OM |
This parameter holds the IMS charging identifier (ICID) as recieved by the enhanced MSC server with SIP interface. |
IMS Private user Identity |
OM |
OM |
This field contains the IMS Private User Identity and Public User Identity specifically reserved for IMS registrations. |
Network call reference |
C |
C |
An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. |
MSC Address |
C |
C |
This field contains the E.164 number assigned to the MSC that generated the network call reference. Shall be present only if CAMEL is applied. |
Number of HSCSD Channels Requested |
OC |
– |
The maximum number of HSCSD channels requested as received from the MS at call set-up. Shall only be present for HSCSD connections. |
Number of HSCSD Channels Allocated |
OC |
– |
The number of HSCSD channels allocated to the MS at call set-up. Shall only be present for HSCSD connections. |
Change of HSCSD Parameters |
OC |
– |
A list of network or user initiated changes of number of HSCSD channels during a connection each time-stamped. Shall only be present in case of an HSCSD call, if the basic HSCSD parameters are modified due the user or network initiated modification procedure. |
Fixed Network User Rate |
OC |
– |
Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. |
Air Interface User Rate Requested |
C |
C |
The total Air Interface User Rate Requested by the MS at call set-up. Shall only be present for non-transparent HSCSD connections. |
Channel Coding Accepted |
C |
– |
A list of the traffic channels codings accepted by the MS. Shall only be present for HSCSD connections. |
Channel Coding Used |
C |
– |
The traffic channels codings negotiated between the MS and the network at call set-up. Shall only be present for HSCSD connections. |
Guaranteed bit rate |
– |
OC |
Describes the bit-rate the UMTS bearer service shall guarantee to the user or application. Guaranteed Bit Rate may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. Shall only be present for UMTS data connections. |
Maximum bit rate |
– |
OC |
Maximum Bit Rate can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations; 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections. |
Speech Version Used |
OM |
– |
Speech version used for that call |
Speech Version Supported |
OM |
– |
Speech version supported by the MS with highest priority indicated by MS. |
System Type |
– |
M |
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. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature. |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN. |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP. |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
OC |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
Reason for service change |
– |
OC |
Indicates the type of service change and fallback. |
Service change initiator |
– |
OC |
Indicates the service change initiator. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.5 Roaming call attempt
If the generation of these records is enabled then, a roaming record shall be created for each call redirected to a mobile subscriber roaming outside the HPLMN. These roaming records shall be produced in the GMSC of the roaming subscriber’s HPLMN. These roaming records shall be produced by the “Old MSC/VLR” during Mobile Terminating Roaming Forwarding (MTRF) procedure, when the call is re-routed towards a new MSC/VLR located in a different PLMN.
Table 6.1.3.5: Roaming record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Roaming record. |
Served IMSI |
M |
M |
IMSI of the called (roaming) party. |
Served MSISDN |
OM |
OM |
The MSISDN of the called (roaming) party. |
Calling Number |
C |
C |
The address of the calling party, if available. |
Roaming Number |
M |
M |
The Mobile Station Roaming Number employed to route this connection. |
Recording Entity |
M |
M |
The E.164 number of the GMSC |
Incoming TKGP |
OM |
OM |
The GMSC/VMSC trunk group on which the call originated. |
Outgoing TKGP |
OM |
OM |
The trunk group on which the call left the GMSC/VMSC |
Basic service |
M |
M |
Bearer or teleservice employed. |
Transparency Indicator |
C |
C |
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode. |
ChangeOfService |
OC |
OC |
A list of changes of basic service during a connection each time-stamped. |
Supplementary Services |
C |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer time: time of answer (for successful calls) Release time: time of traffic channel release |
Call duration |
M |
M |
The chargeable duration of the connection for successful calls, the holding time of call attempts. |
Data volume |
C |
C |
The number of data segments transmitted if available at the GMSC |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Network call reference |
C |
C |
An identifier to correlate transactions on the same call taking place in different network nodes, shall be present if CAMEL is applied. |
MSC Address |
C |
C |
This field contains the E.164 number assigned to the MSC that generated the network call reference. Shall be present only if CAMEL is applied. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
– |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
6.1.3.6 Incoming gateway call attempt
If generation of these records is enabled, an incoming gateway record shall be created for each incoming call attempt received by a gateway MSC from another network. These records, produced in the gateway MSC, may be used to settle accounts with other networks. The generation of gateway records shall not be influenced by the production of MTC records i.e. even if the GMSC and terminating MSC are co-located a gateway record shall still be produced.
Table 6.1.3.6: Incoming gateway record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
Incoming gateway record |
Calling Number |
C |
C |
The number of the calling party if available at this node. |
Called Number |
M |
M |
The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing. |
Recording Entity |
M |
M |
The E.164 number of the GMSC |
Incoming TKGP |
M |
M |
The incoming GMSC trunk group on which the call originated. |
Outgoing TKGP |
OM |
OC |
The trunk group on which the call left the GMSC. If available in 3G, this parameter shall be supplied. |
Event time stamps: |
M C OM |
M C OM |
Seizure time: time of incoming trunk seizure Answer time: time of answer (successful calls only) Release time: time of incoming trunk release |
Call duration |
M |
M |
The accountable duration (answer -> release of incoming trunk) of the connection if successful, the call holding time of the incoming trunk for call attempts. |
Data Volume |
C |
– |
If applicable and known at the GMSC |
ISDN Bearer Capability |
OC |
OC |
Present if this parameter is signalled back from the VMSC to the GMSC in the access transport parameter of the Answer Message (ANM), see 3GPP TS 29.007 [213]. |
Low Layer Compatibility |
OC |
OC |
Present if this parameter is signalled back from the VMSC to the GMSC in the access transport parameter of the Answer Message (ANM), see 3GPP TS 29.007 [213]. |
High Layer Compatibility |
OC |
OC |
Present if this parameter is signalled back from the VMSC to the GMSC in the access transport parameter of the Answer Message (ANM), see 3GPP TS 29.007 [213]. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call Reference |
M |
M |
A local identifier distinguishing between transactions. |
Reason for service change |
– |
OC |
Indicates the type of service change and fallback. |
Service change initiator |
– |
OC |
Indicates the service change initiator. |
Sequence number |
C |
C |
Partial record sequence number, if applicable. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
– |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
6.1.3.7 Outgoing gateway call attempt
If generation of these records is enabled, an outgoing gateway record shall be created for each outgoing call attempt from a gateway MSC to another network. These records, produced in the gateway MSC, may be used to settle accounts with other networks. The generation of gateway records shall not be influenced by the production of MOC records i.e. even if the GMSC and originating MSC are co-located a gateway record shall still be produced.
Table 6.1.3.7: Outgoing gateway record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Outgoing gateway record |
Calling Number |
C |
C |
The number of the calling party if available at this node. |
Called Number |
M |
M |
The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing. |
Recording Entity |
M |
M |
The E.164 number of the GMSC |
Incoming TKGP |
OM |
OC |
The incoming GMSC trunk group on which the call originated. If available in 3G, this parameter shall be supplied. |
Outgoing TKGP |
M |
M |
The trunk group on which the call left the GMSC. |
Event time stamps: |
M C OM |
M C OM |
Seizure time: time of outgoing trunk seizure Answer time: time of answer (successful calls only) Release time: time of outgoing trunk release |
Call duration |
M |
M |
The accountable duration (answer -> release of outgoing trunk) of the connection if successful, the call holding time of the outgoing trunk for call attempts. |
Data Volume |
C |
– |
If applicable and known at the GMSC |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call Reference |
M |
M |
A local identifier distinguishing between transactions. |
Sequence number |
C |
C |
Partial record sequence number, if applicable. |
Reason for service change |
– |
OC |
Indicates the type of service change and fallback. |
Service change initiator |
– |
OC |
Indicates the service change initiator. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
– |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
6.1.3.8 Transit call attempt
If generation of these records is enabled then a transit record may be generated for each incoming call attempt received by a Transit MSC i.e. neither originating nor terminating. For the avoidance of doubt, a transit record shall only be produced if no MOC or MTC record is produced for this call attempt by this MSC. The transit records, produced in the TMSC, may be used to record traffic from particular origins or to particular destinations.
Table 6.1.3.8: Transit record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Transit. |
Recording Entity |
M |
M |
The E.164 number of the transit MSC |
Incoming TKGP |
M |
M |
The TMSC trunk group on which the call originated. |
Outgoing TKGP |
M |
M |
The trunk group on which the call left the TMSC. |
Calling Number |
C |
C |
The number of the calling party if available at this node. |
Called Number |
M |
M |
The address of the called party as seen by the TMSC. |
ISDN Basic Service |
OM |
OM |
The ISDN basic service employed |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming trunk seizure for unsuccessful call attempts Answer time: time of answer (successful calls only) Release time: time of traffic channel release |
Call duration |
M |
M |
The chargeable duration of the connection if successful, the call holding time for call attempts. |
Data Volume |
C |
– |
If applicable and known at the transit MSC |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call Reference |
M |
M |
A local identifier distinguishing between transactions. |
Sequence number |
C |
C |
Partial record sequence number, if applicable. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
– |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
6.1.3.9 Supplementary service actions
A supplementary service record may be produced in the NEF of the appropriate MSC or HLR for each supplementary service action (activation, deactivation, invocation etc.) performed or initiated by the subscriber.
– There are two fundamental types of SS-actions: Call related i.e. as a result of a connection,
e.g. Invocation of CLIP / CLIR / AoC, etc.
– Non-call related i.e. as a result of Subscriber Controlled Input (SCI) e.g. Registration of call forwarding.
Each supplementary service action shall be performed on one or more basic service groups. If the action applies to all teleservices and all bearer services (i.e. to all basic services) then the basic services field shall be omitted.
SCI actions may be recorded in individual SS-action records. Call related actions may be recorded in either the appropriate call record (MOC/MTC) or in separate SS-action records.
Additional non-standard supplementary service actions may be made available within some networks in the form of Unstructured Supplementary Service Data (USSD). These actions may also be recorded in SS-action records. However, as these actions are non-standard they may not include an appropriate action type, supplementary service code or basic service code.
Table 6.1.3.9: SS-action record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Supplementary service action. |
Served IMSI |
M |
M |
The IMSI of the MS performing the action. |
Served IMEI |
OC |
OC |
The IMEI of the ME performing the action. |
Served MSISDN |
OM |
OM |
The primary MSISDN of the party performing the action. |
MS Classmark |
M |
M |
The mobile station classmark. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC / HLR. |
Location |
OM |
OM |
The identity of the cell or the SAC, including the location area code and MCC+MNC, from which the request originated. |
Basic Services |
C |
C |
The basic service group(s) to which the supplementary service applies. This field is not provided if the action applies to all basic services. |
Supplementary Service |
C |
C |
The supplementary service or group of supplementary services for which the request was made. May not be available in case of USSD. |
SS Action |
C |
C |
Activation, deactivation, interrogation etc. May not be available in case of USSD. |
SS Action time stamp |
M |
M |
The time at which the action was requested. |
SS Parameters |
C |
C |
Service dependent parameters or unstructured supplementary service data, if defined for the SS action recorded in this CDR. |
SS Action Result |
C |
C |
Result of the requested transaction if unsuccessful. |
Call Reference |
M |
M |
A local identifier distinguishing between transactions at the same MS. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
System Type |
– |
M |
This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface |
6.1.3.10 HLR interrogation
If enabled, a HLR interrogation record shall be created for each interrogation performed for a mobile subscriber. These records may be produced in either the HLR itself or the interrogating MSC.
Table 6.1.3.10: HLR interrogation record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
HLR interrogation. |
Served IMSI |
C |
C |
The IMSI of the party being interrogated, if successful |
Served MSISDN |
M |
M |
The MSISDN of the subscriber being interrogated. |
Recording Entity |
M |
M |
The E.164 Number of the HLR / MSC. |
Basic Service |
OC |
OC |
Only for teleservice 21 (SMS-MT). |
Routing Number |
C |
C |
Routing number (MSRN, forwarding number) provided by the HLR if the interrogation was successful. |
Interrogation time stamp |
M |
M |
Time at which the interrogation was invoked. |
Number of Forwarding |
C |
C |
The number of times the call has been forwarded if provided by ISUP. |
Interrogation Result |
C |
C |
The result of the interrogation request if unsuccessful. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.11 Location update (VLR)
If enabled, a VLR location update record shall be produced in the VLR for each location registration or location update received by the VLR for a mobile subscriber.
Table 6.1.3.11: Location update (VLR) record
Field |
2G |
3G |
Loc Upd over SGs |
Description |
Record Type |
M |
M |
M |
Location update. |
Served IMSI |
M |
M |
M |
IMSI of the served MS. |
Served MSISDN |
OM |
OM |
OM |
The primary MSISDN of the party performing the location update |
Recording Entity |
M |
M |
M |
The E.164 number of the entity (VLR or MSC/VLR) generating the record. |
Old location |
C C |
C C |
– C |
Not present for registration: VMSC E.164 Number Location Area Code and MCC+MNC |
New location |
M M OM |
M M OM |
M M OM |
VMSC E.164 Number . When E-UTRAN location update over SG, this field contains the E.164 number of the entity (VLR or MSC/VLR) generating the record (i.e Recording entity). Location Area Code Cell Identification or Service Area Code and MCC+MNC The Cell Identity contains the 16 least significant bits and the Tracking Area Code is placed in the Location Area Code field if E-UTRAN location update. |
Location Extension |
– |
– |
OM |
The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN location update. |
MS Classmark |
M |
M |
M |
The mobile station classmark. When E-UTRAN location update over SG, this field contains Default classmark 1” 0x7F value”. |
Update time stamp |
M |
M |
M |
Time at which the update was invoked. |
Update Result |
C |
C |
C |
The result of the location update if unsuccessful. |
Record extensions |
OC |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.12 Location update (HLR)
If enabled, an HLR location update record shall be produced in the HLR for each location registration or location update received by the HLR for a mobile subscriber including location updates received from subscribers roaming in foreign PLMNs.
Table 6.1.3.12: Location Update (HLR) record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
Location update. |
Served IMSI |
M |
M |
IMSI of the served MS. |
Recording Entity |
M |
M |
The E.164 Number of the HLR. |
Old location |
OC OC |
OC OC |
VMSC E.164 Number VLR E.164 Number |
New location |
M M |
M M |
VMSC E.164 Number VLR E.164 Number |
Update time stamp |
M |
M |
Time at which the update was invoked. |
Update Result |
C |
C |
The result of the location update if unsuccessful. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.13 Short message service, mobile originated
If enabled, an SMS-MO record shall be produced, within the originating MSC, for each short message sent by a mobile subscriber.
Table 6.1.3.13: SMS-MO record
Field |
2G |
3G |
SMS over SGs |
Description |
---|---|---|---|---|
Record Type |
M |
M |
M |
SMS-Mobile originated. |
Served IMSI |
M |
M |
M |
The IMSI of the subscriber sending the short message. |
Served IMEI |
OC |
OC |
OC |
The IMEI of the ME sending the message, if available. |
Served MSISDN |
OM |
OM |
OM |
The primary MSISDN of the subscriber sending the message. For MSISDN-less subscription, this field holds the Dummy MSISDN as defined in TS 23.003 [104]. |
MS Classmark |
M |
M |
M |
The mobile station classmark. |
Service Centre |
M |
M |
M |
The address (E.164) of the SMS-service centre. |
Recording Entity |
M |
M |
M |
The E.164 number of the visited MSC. |
Location |
OM |
OM |
OM |
The Location Area Code and Cell Identity / Service Area Code and MCC+MNC from which the message originated. The Cell Identity contains the 16 least significant bits and the Tracking Area Code is placed in the Location Area Code filed if E-UTRAN is used to deliver the SMS. |
Event Time stamp |
M |
M |
M |
Origination time: The time at which the message was received by the MSC from the subscriber. |
Message Reference |
M |
M |
M |
A reference, provided by the MS uniquely identifying this message. |
SMS Result |
C |
C |
C |
The result of the attempted delivery if unsuccessful. |
Record extensions |
OC |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Destination number |
OM |
OM |
OM |
The destination number dialled by the MS sending the short message. |
CAMELSMSInformation |
C |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS. Shall be present only if CAMEL is applied. |
System Type |
– |
M |
M |
This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. The field shall be set to "unknown" for SMS delivery using E-UTRAN. |
Location Extension |
– |
– |
OM |
The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN is used to deliver the SMS. |
6.1.3.14 Short message service, mobile terminated
If enabled, an SMS-MT record shall be produced, within the terminating MSC, for each short message received by a mobile subscriber.
Table 6.1.3.14: SMS-MT record
Field |
2G |
3G |
SMS over SGs |
Description |
Record Type |
M |
M |
M |
SMS-Mobile Terminated. |
Service Centre |
M |
M |
M |
The E.164 address of the SMS centre. |
Served IMSI |
M |
M |
M |
The IMSI of the receiving party. |
Served IMEI |
OC |
OC |
OC |
The IMEI of the receiving party, if available. |
Served MSISDN |
OM |
OM |
OM |
The MSISDN of the receiving party. |
MS Classmark |
M |
C |
C |
The mobile station classmark. |
Recording Entity |
M |
M |
M |
The E.164 number of the visited MSC. |
Location |
OM |
OM |
OM |
The Location Area Code and Cell Identity /Service Area Code and MCC+MNC to which the message was delivered. The Cell Identity contains the 16 least significant bits and the Tracking Area Code is placed in the Location Area Code filed if E-UTRAN is used to deliver the SMS. |
Event time stamp |
M |
M |
M |
Delivery time: time at which message was sent to the MS by the MSC. |
SMS Result |
C |
C |
C |
The result of the attempted delivery if unsuccessful. |
Record extensions |
OC |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
System Type |
C |
M |
M |
This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface. The field shall be set to "unknown" for SMS delivery using E-UTRAN. |
CAMELSMSInformation |
C |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS. Shall be present only if CAMEL is applied. |
Location Extension |
– |
– |
OM |
The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN is used to deliver the SMS. |
6.1.3.15 SMS-MO interworking record
If enabled, an SMS-MO interworking record shall be produced, within the interworking MSC, for each short message generated by a mobile subscriber. These records may be used to settle accounts between PLMNs and SMS service centres. Where the Interworking MSC is also the originating MSC, an SMS-MO CDR will also be generated.
Table 6.1.3.15: SMS-MO interworking record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
SMS-MO interworking record. |
Service Centre |
M |
M |
The E.164 address of the SMS service centre. |
Served IMSI |
M |
M |
The IMSI of the sending party. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC. |
Event Time stamp |
M |
M |
The time at which the message was received by the interworking function. |
SMS Result |
C |
C |
The result of the attempted delivery if unsuccessful, when available. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record. |
6.1.3.16 SMS-MT gateway record
If enabled, an SMS-MT gateway record shall be produced, within the gateway MSC, for each short message sent to a mobile subscriber. Where the Gateway MSC is also the terminating MSC, an SMS-MT CDR will also be generated.
Table 6.1.3.16: SMS-MT gateway record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
SMS-MT gateway record. |
Service Centre |
M |
M |
The E.164 address of the SMS service centre. |
Served IMSI |
M |
M |
The IMSI of the receiving party. |
Served MSISDN |
OM |
OM |
The MSISDN of the receiving party. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC. |
Event Time stamp |
M |
M |
The time at which the message was received by the gateway. |
SMS Result |
C |
C |
The result of the attempted delivery if unsuccessful. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.17 Common equipment usage record
If enabled, a common equipment usage record shall be created in the VMSC to record the usage (duration) of common equipment, e.g. conference circuits, employed by a mobile subscriber.
Table 6.1.3.17: Common equipment usage record
Field |
2G |
3G |
Description |
Record Type |
M |
M |
Common equipment usage record. |
Equipment type |
M |
M |
e.g. Conference circuit. |
Equipment Id. |
C |
C |
The local id. Of the equipment employed. |
Served IMSI |
M |
M |
The IMSI of the party responsible for the seizure of the equipment.. |
Served MSISDN |
OM |
OM |
The primary MSISDN of the served party.. |
Recording Entity |
M |
M |
The E.164 number of the MSC in which the equipment is located. |
Basic service |
C |
C |
Bearer or teleservice employed, if appropriate. |
Rate Adaptation |
OC |
OC |
Present if "rate adaption" parameters for the basic service were signalled between the MS/UE and the network, see 3GPP TS 24.008 [208]. |
Fixed Network User Rate |
OC |
OC |
Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. |
ChangeOfService |
OC |
OC |
A list of changes of basic service during a connection each time-stamped. |
Supp. Services |
C |
C |
Supplementary services invoked in connection with this equipment. |
Event Time Stamp |
M OM |
M OM |
Seizure time: the time at which the equipment was seized. Release time: the time at which the equipment was released. |
Call Duration |
M |
M |
The total duration of the usage of the equipment. |
Call Reference |
M |
M |
A local identifier distinguishing between transactions. |
Sequence number |
C |
C |
Partial record sequence number if applicable. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
System Type |
– |
M |
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. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.18 Terminating CAMEL call attempt
If the generation of these records is enabled, a terminating CAMEL call attempt record shall be generated for each call toward a subscriber with a T-CSI or VT-CSI and if the terminating trigger criteria are met. The record is generated in the GMSC/gsmSSF carrying out the terminating CAMEL call handling and in the MSC server/gsmSSF carrying out the visited terminating CAMEL call attempt.
Table 6.1.3.18: Terminating CAMEL record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Terminating CAMEL interrogation. |
Served IMSI |
M |
M |
IMSI of the called party |
Served MSISDN |
OM |
OM |
The MSISDN of the called party. |
Recording Entity |
M |
M |
The E.164 number of the GMSC. |
Interrogation time stamp |
M |
M |
Time at which the interrogation was invoked. |
CAMEL Destination Number |
M |
M |
The number available for routing after the CAMEL server enquiry. |
GsmSCF Address |
M |
M |
The CAMEL server serving the subscriber. |
Service key |
M |
M |
The CAMEL service logic to be applied. |
Network call reference |
M |
M |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
M |
M |
This field contains the E.164 number assigned to the MSC that generated the network call reference. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Called Number |
M |
M |
The address of the called party as received by the GMSC/gsmSSF. |
Calling Number |
C |
C |
The address of the calling party, if available. |
Incoming TKGP |
OM |
OC |
The GMSC trunk group on which the call originated. If available in 3G, this parameter shall be supplied. |
Outgoing TKGP |
OM |
OC |
The trunk group on which the call left the GMSC. If available in 3G, this parameter shall be supplied. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer time: time of answer (for successful calls) Release time: time of traffic channel release |
Call duration |
M |
M |
The chargeable duration of the connection for successful calls, the holding time of call attempts. |
Data volume |
C |
– |
The number of data segments transmitted if available at the GMSC |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. |
Level of CAMEL service |
OC |
OC |
Indicator of the complexity of the CAMEL feature used. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
Free format data append indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. |
MSC server indication |
C |
C |
Indication if the CAMEL call handling is active in the MSC server. |
Default call handling 2 |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling for 2nd service such as dialled service. This field shall be present only if default call handling has been applied. |
GsmSCF address 2 |
C |
C |
Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Service key 2 |
C |
C |
The CAMEL service logic to be applied for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. |
Free format Data 2 |
C |
C |
This field contains data sent by the gsmSCF in the FCI message(s) for 2nd service such as dialled service. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for 2nd service. |
Free format data append indicator 2 |
C |
C |
Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for 2nd service. |
Location Routing Number |
– |
OC |
Location Routing Number for Number Portability feature |
LRN Source Indicator |
– |
OC |
LRN Source Indicator tells the source of the LRN |
LRN Query Status Indicator |
– |
OC |
Status of Number Portability query. |
JIP Parameter |
– |
OC |
Jurisdiction Information Parameter |
JIP Source Indicator |
– |
OC |
JIP Source Indicator tells the source of the JIP |
JIP Query Status Indicator |
– |
OC |
Status of Number Portability query. |
Partial Record Type |
OC |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.19 IMEI observation ticket
An observed IMEI ticket is generated whenever tracklisted, blocklisted or non-allow listed mobile equipment is detected during an IMEI check. The purpose of the ticket is to link the mobile equipment under observation with its current user (IMSI). The ticket also includes information describing when and where the equipment was used to enable the tracking of such equipment. Finally, if the ticket was triggered by a call attempt, a call reference is provided in order to locate the corresponding call record.
The IMEI tickets are generated by the NEF of the MSC performing the IMEI check.
Table 6.1.3.19: IMEI ticket
Field |
2G |
3G |
Description |
Served IMEI |
M |
M |
IMEI of the observed mobile equipment |
IMEI Status |
M |
M |
The result of the IMEI check e.g. blocklisted, tracklisted, unknown. |
Served IMSI |
M |
M |
The IMSI of the subscriber currently using the mobile equipment. |
Served MSISDN |
C |
C |
The MSISDN of the subscriber currently using the observed mobile equipment, only available if the event that triggered the IMEI check was an MOC, MTC, SMS-MO or SMS-MT |
Recording Entity |
M |
M |
The E.164 number of the recording MSC. |
Event Time Stamp |
M |
M |
The time at which the IMEI check was performed. |
Location |
M |
M |
The location area code and cell identity of the cell and MCC+MNC from which the mobile equipment was used. |
IMEI Check Event |
OM |
OM |
The event that caused IMEI checking to take place |
Call Reference |
OC |
OC |
Only available if the IMEI check was related to an MOC or MTC |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.1.3.20 Mobile Terminated Location Request (MT-LR)
If enabled, an LCS-MT record shall be produced, within the visited MSC, for each mobile a terminated Location Request is performed for.
Table 6.1.3.20: LCS-MT record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
LCS-MT record. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
LCS Client Type |
M |
M |
The type of the LCS client that invoked the LR. |
LCS Client Identity |
M |
M |
Further identification of the LCS client . |
Served IMSI |
C |
C |
The IMSI of the subscriber the LR is invoked for, if available. See NOTE |
Served MSISDN |
C |
C |
The MSISDN of the subscriber the LR is invoked for, if available. See NOTE |
Served IMEI |
C |
C |
The IMEI of the susbcriber the LR is invoked for, if available. See NOTE |
Location Type |
M |
M |
The type of the location request. |
LCS QoS |
C |
C |
QoS of the LR, if available. |
LCS Priority |
C |
C |
Priority of the LR, if available. |
MLC Number |
M |
M |
The E.164 address of the requesting GMLC. |
Event Time Stamp |
M |
M |
The time at which the LR was received by the MSC. |
MeasureDuration |
OM |
OM |
The duration of proceeding the location request . |
Notification To MS User |
C |
C |
The privacy notification to MS user that was applicable when the LR was invoked, if available. |
Privacy Override |
C |
C |
This parameter indicates if MS privacy was overridden by the LCS client, if available. |
Location |
OM |
– |
The LAC and CI and MCC+MNC when the LR is received. |
Location Estimate |
OC |
OC |
The location estimate for the subscriber if contained in geographic position and the LR was successful. |
Positioning Data |
C |
C |
The positioning method used or attempted, if available. |
LCS Cause |
OC |
OC |
The result of the LR if any failure or partial success happened as known at the radio interface. |
Cause for Termination |
M |
M |
The reason for the termination of the location service. |
Diagnostics |
C |
C |
A more detailed information about the Cause for Termination if any failure or partial success happened. |
System Type |
– |
M |
This field indicates the use of GERAN or UTRAN at the time of the LCS request. This field is present when either the UTRAN or GERAN air-interface is used on call set-up. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record. |
NOTE: at least one: IMSI, MSISDN or IMEI, shall be present. |
6.1.3.21 Mobile Originated Location Request (MO-LR)
If enabled, an LCS-MO record shall be produced, within the visited MSC, for each mobile an originated Location Request is performed for.
Table 6.1.3.21: LCS-MO record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
LCS-MO record. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
LCS Client Type |
C |
C |
The type of the LCS client that invoked the LR, if available. |
LCS Client Identity |
C |
C |
Further identification of the LCS client, if available. |
Served IMSI |
M |
M |
The IMSI of the subscriber the LR is invoked for. |
Served MSISDN |
OM |
OM |
The MSISDN of the subscriber the LR is invoked for. |
MOLR Type |
M |
M |
The type of the LR. |
LCS QoS |
C |
C |
QoS of the LR, if available. |
LCS Priority |
OC |
OC |
Priority of the LR, if available. |
MLC Number |
C |
C |
The E.164 address of the involved GMLC, if available. |
Event Time Stamp |
M |
M |
The time at which the LR was received by the MSC. |
MeasureDuration |
OM |
OM |
The duration of proceeding the location request . |
Location Estimate |
OC |
OC |
The location estimate for the subscriber if contained in geographic position and the LR was successful. |
Positioning Data |
C |
C |
The positioning method used or attempted, if available. |
LCS Cause |
C |
C |
The result of the LR if any failure or partial success happened as known at the radio interface. |
Cause for Termination |
M |
M |
The reason for the termination of the location service. |
Diagnostics |
C |
C |
A more detailed information about the Cause for Termination if any failure or partial success happened. |
System Type |
– |
M |
This field indicates the use of GERAN or UTRAN at the time of the LCS request. This field is present when either the UTRAN or GERAN air-interface is used on call set-up. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record. |
6.1.3.22 Network Induced Location Request (NI-LR)
If enabled, an LCS-NI record shall be produced, within the visited MSC, for each network induced location request performed for a MS, e.g. in case of emergency call.
Table 6.1.3.22: LCS-NI record
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
LCS-NI record. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
LCS Client Type |
C |
C |
The type of the LCS client that invoked the LR, if available. |
LCS Client Identity |
C |
C |
Further identification of the LCS client, if available. |
Served IMSI |
C |
C |
The IMSI of the calling party the LR is executed for if supplied by the UE. |
Served MSISDN |
C |
C |
The MSISDN of the calling party the LR is executed for if supplied by the UE. |
Served IMEI |
C |
C |
The IMEI of the calling party the LR is executed for if available. |
EMS-Digits |
OC |
OC |
The emergency service routing digits, if emergency call. |
EMS-Key |
OC |
OC |
The emergency service routing key, if emergency call. |
LCS QoS |
C |
C |
QoS of the LR, if available. |
LCS Priority |
C |
C |
Priority of the LR, if available. |
MLC Number |
C |
C |
The E.164 address of the involved GMLC, if available. |
Event Time Stamp |
M |
M |
The time at which the LR was received by the MSC. |
MeasureDuration |
OM |
OM |
The duration of proceeding the location request . |
Location Estimate |
OC |
OC |
The location estimate for the subscriber if contained in geographic position and the LR was successful. |
Positioning Data |
C |
C |
The positioning method used or attempted, if available. |
LCS Cause |
C |
C |
The result of the LR if any failure or partial success happened as known at the radio interface. |
Cause for Termination |
M |
M |
The reason for the termination of the location service. |
Diagnostics |
C |
C |
A more detailed information about the Cause for Termination if any failure or partial success happened. |
System Type |
– |
M |
This field indicates the use of GERAN or UTRAN at the time of the LCS request. This field is present when either the UTRAN or GERAN air-interface is used on call set-up. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record. |
6.1.3.23 Mobile originated call attempt (CAMEL CPH adapted version)
If the MSC / gsmSCF is able to provide CAMEL CPH services, this kind of record shall replace records according to clause 6.1.3.1 "Mobile originated call attempt". This applies to all mobile originated call attempts, even if no CPH operations are used in the individual call. Record fields that are specific to individual outgoing legs are recorded in the grouped field "CAMEL Call Leg Information".
If the generation of this kind of record is enabled then the MSC shall produce one MOC record. The incoming leg is recorded in the main body. Whenever there is a CAMEL dialogue, outgoing legs of the same call segment are recorded in the grouped field "CAMEL call leg information". Further legs in new call segments are recorded in CDRs of type "6.1.3.25 New Call Segment in a MO, CF or MT CAMEL Dialogue".
Examples for call situations where this type of record applies are the following:
– Mobile originating call without CPH being involved,
– Mobile originating call continuing after disconnect of the incoming leg in case of no partial record generation.
When partial records are generated, they are of type "6.1.3.25 New Call Segment in a MO, CF or MT CAMEL Dialogue",
– Mobile originating call with more than one outgoing leg on this call segment,
– Mobile originating call in which the original outgoing leg has been disconnected by gsmSCF.
Disconnect of the incoming leg is recorded by filling the related record fields in the main body of the record. Optionally a partial record may be generated. This partial record is of type "6.1.3.24 gsmSSF initiated CAMEL CPH call attempt".
Disappearing (DisconnectLeg, SplitLeg, etc.) of an outgoing leg is recorded by filling the related record fields in the "CAMEL Call Leg Information" field for the disappearing leg. Optionally a partial record may be generated. This partial record does not contain information of the leg that disappeared, i.e. it does not contain a "CAMEL Call Leg Information" field for that leg.
Connection of a further leg to this call segment is recorded by adding a further field "CAMEL Call Leg Information". Optionally a partial record may be generated.
Table 6.1.3.23: MOC record (CAMEL CPH adapted version)
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
M |
M |
IMSI of the calling party. |
Served IMEI |
C |
C |
IMEI of the calling ME, if available. |
Served MSISDN |
OM |
OM |
The primary MSISDN of the calling party. |
Called Number |
M |
M |
The address of the called party i.e. the number dialled by the calling subscriber. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
Incoming TKGP |
OM |
OC |
The MSC trunk group on which the call originated, usually from the BSS. If available in 3G, this parameter shall be supplied. |
Location |
M |
M |
The identity of the cell or the SAC and MCC+MNC at the time of CDR creation, including the location area code. |
Change of Location |
OC |
OC |
A list of changes in Location Area Code / Service Area Code / Cell Id and MCC+MNC. Each time-stamped. |
Basic service |
M |
M |
Bearer or teleservice employed. ‘speech’ in case of CAMEL CPH calls. |
Supp. Services |
C |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
AOC Parameters |
OC |
OC |
The charge advice parameters sent to the MS on call set-up. This field shall be supplied only when AoC parameters have been sent. |
Change of AOC Parameters |
OC |
OC |
New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. This field shall be supplied only when AoC parameters have been sent. |
MS Classmark |
M |
M |
The mobile station classmark employed on call set-up. |
Change of Classmark |
OC |
OC |
A list of changes to the classmark during the connection each time-stamped. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer: time of answer (for successful calls) Release time: time of traffic channel release for the incoming leg. |
Call duration |
C |
C |
The chargeable duration of the connection of the incoming leg for successful calls, the holding time of the incoming leg for call attempts. |
Radio Channel Requested |
OM |
– |
The type of radio traffic channel (full / half etc.) requested by the MS. |
Radio Channel Used |
M |
– |
The type of radio channel actually used (full or half rate). |
Change of Radio Channel |
OC |
– |
A list of changes each time stamped. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
GsmSCF address |
M |
M |
Identifies the CAMEL server serving the subscriber. |
Service key |
C |
C |
The CAMEL service logic to be applied. |
Network call reference |
M |
M |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
M |
M |
This field contains the E.164 number assigned to the MSC that generated the network call reference. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Speech Version Supported |
OM |
– |
Speech version supported by the MS with highest priority indicated by MS |
Speech Version Used |
OM |
– |
Speech version used for that call |
Number of DP encountered |
OM |
OM |
Number that counts how often armed detection points (TDP and EDP) were encountered. Sum of all DPs encountered in this call. |
Level of CAMEL service |
OM |
OM |
Indicator for the complexity of the CAMEL feature used. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
CAMEL Destination Number |
Destination modified by camel service. |
||
Translated Number |
Called number after digit translation within the MSC. |
||
Connected Number |
Number of connected party if different from ‘CAMEL Destination Number’. |
||
Roaming Number |
MSRN to route this leg (if applicable). |
||
MSC outgoing TKGP |
Trunk on which the leg leaves the MSC. |
||
Seizure Time |
Time of traffic channel seizure for this leg. |
||
Answer Time |
Time when the answer message is received for this leg. |
||
Release Time |
Time when the leg is released or moved into another call segment. |
||
Call Duration |
Time between answer and release timestamp of this leg. |
||
Additional Chg. Info |
Charge/no charge indicator and additional charging parameters, when available. |
||
Free Format Data |
If received in the FCI message from SCF. |
||
Free Format Data Append |
If received in the FCI message from SCF. |
||
Free Format Data 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append 2 |
If provided in the FCI message for a 2nd service. |
||
Diagnostics |
Detailed reason for disappearing of the leg in this call segment. |
||
Cause for Termination |
The reason for disappearing of the leg in this call segment. |
||
Default Call Handling 2 |
Present if a 2nd service (DP3) is triggered. |
||
gsm-SCF Address 2 |
Present if a 2nd service (DP3) is triggered. |
||
Service Key 2 |
Present if a 2nd service (DP3) is triggered. |
||
Free Format Data Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Location Routing Number |
For Number Portability feature, not available in 2G records. |
||
LRN Source Indicator |
Source of the LRN, not available in 2G records. |
||
LRN Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
JIP Parameter |
Jurisdiction Information Parameter, not available in 2G records. |
||
JIP Source Indicator |
The source of the JIP, not available in 2G records. |
||
JIP Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
Free Format Data Append Indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL id applied. |
System Type |
– |
M |
This field indicates the use of GERAN, UTRAN (or a value of unknown) of the incoming leg. 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. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
Redial Attempt |
OC |
OC |
Indicates to the network that a call is the result of a redial attempt to switch from speech to multimedia or vice-versa |
6.1.3.24 gsmSCF initiated CAMEL CPH call attempt
If the generation of these records is enabled then an MOC record shall be created for each gsmSCF initiated call attempt and for new parties in new call segments, which are created in a new call dialogue. Examples for call situations where this type of record applies are the following:
– gsmSCF initiated call segment association (new call):
There is only one call segment. It contains the outgoing leg, which is created via CPH Initiate Call Attempt operation (ICA).
– This outgoing leg can be connected to an SRF, which is recorded in the same record in the field "CAMEL Call Leg Information".
– gsmSCF initiated new party in an already established gsmSCF initiated CAP dialogue (new leg):
In a new call dialogue a further call leg in a new call segment is initiated via ICA operation.
– This call segment contains one outgoing leg, which can be connected to an SRF. This leg and if used the SRF are recorded in the record for this call segment in the field "CAMEL Call Leg Information".
– This leg can be connected to the other outgoing leg. This would terminate the call segment and thus the call record. The "Cause for Termination" indicates the reason for disappearing of the leg in this call segment. The Timestamps ("Call Duration", "Release Time", etc.) are filled in. The record of the call segment the leg is moved to records the leg in a further field "CAMEL Call Leg Information".
– The other leg could be connected to this leg which is recorded by adding a further field "CAMEL Call Leg Information".
Record fields for an incoming leg do not exist, because there is no incoming leg in the call segment this record is created for.
Table 6.1.3.24: MOC CPH record (gsmSCF initiated)
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served MSISDN |
OM |
OM |
The number of the initiating party. “Calling Party Number” as received in the ICA operation. |
Called Number |
M |
M |
The address of the called party. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
Basic service |
M |
M |
Bearer or teleservice employed. ‘speech’ in case of CAMEL CPH calls. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
GsmSCF address |
C |
C |
Identifies the CAMEL server serving the subscriber (network call reference). |
Network call reference |
M |
M |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
M |
M |
This field contains the E.164 number assigned to the MSC that generated the record. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Sum of all DPs encountered in this call. |
Level of CAMEL service |
OC |
OC |
Indicator for the complexity of the CAMEL feature used. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
CAMEL Destination Number |
Destination as received in the ICA operation. |
||
Translated Number |
Called number after digit translation within the MSC. |
||
Connected Number |
Number of connected party if different from ‘CAMEL Destination Number’. |
||
Roaming Number |
MSRN to route this leg (if applicable). |
||
MSC outgoing TKGP |
Trunk on which the leg leaves the MSC. |
||
Seizure Time |
Time of traffic channel seizure for this leg. |
||
Answer Time |
Time when the answer message is received for this leg. |
||
Release Time |
Time when the leg is released or moved into another call segment. |
||
Call Duration |
Time between answer and release timestamp of this leg. |
||
Additional Chg. Info |
Charge/no charge indicator and additional charging parameters, when available. |
||
Free Format Data |
If received in the FCI message from SCF. |
||
Free Format Data Append |
If received in the FCI message from SCF. |
||
Free Format Data 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append 2 |
If provided in the FCI message for a 2nd service. |
||
Diagnostics |
Detailed reason for disappearing of the leg in this call segment. |
||
Cause for Termination |
The reason for disappearing of the leg in this call segment. |
||
Default Call Handling 2 |
Present if a 2nd service (DP3) is triggered. |
||
gsm-SCF Address 2 |
Present if a 2nd service (DP3) is triggered. |
||
Service Key 2 |
Present if a 2nd service (DP3) is triggered. |
||
Free Format Data Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Location Routing Number |
For Number Portability feature, not available in 2G records. |
||
LRN Source Indicator |
Source of the LRN, not available in 2G records. |
||
LRN Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
JIP Parameter |
Jurisdiction Information Parameter, not available in 2G records. |
||
JIP Source Indicator |
The source of the JIP, not available in 2G records. |
||
JIP Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.25 New Call Segment in a MO, CF and MT CAMEL Dialogue
If the generation of these records is enabled then an MOC record shall be created for call segments without incoming leg, generated by a CAMEL dialogue for mobile originated, call forwarding or mobile terminating call attempts. Examples for call situations where this type of record applies are the following:
– Additional call segment, which is created by means of a "SplitLeg" operation or ICA (new party) operation.
– This call segment contains one outgoing leg, which can be connected to an SRF. This leg and if used the SRF are recorded in the record for this call segment in the field ‘Camel Call Leg Information’.
– This leg can be connected to the other outgoing leg. This would terminate the call segment and thus the call record. The "Cause for Termination" indicates the reason for disappearing of the leg in this call segment. The Timestamps ("Call Duration", "Release Time", etc.) are filled in. The record of the call segment the leg is moved to records the leg in a further field ‘Camel Call Leg Information’.
– The other leg could be connected to this leg which is recorded by adding a further field "CAMEL Call Leg Information".
– Call segment where the incoming leg disappeared (e.g. due to SplitLeg or DisconnectLeg operation). A record of this type is generated if partial records are generated.
Although an incoming leg does not exists, the "IMSI", the "IMEI" and the "Service Key" is recorded in the main body.
Table 6.1.3.25: MOC CPH record (new call segment)
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
M |
M |
IMSI of the served party (‘calling party’ in case of MOC, ‘forwarding party’ in case of call forwarding respectively ‘called party’ in case of MTC). |
Served IMEI |
C |
C |
IMEI of the served ME, if available (‘calling party’ in case of MOC, ‘forwarding party’ in case of call forwarding respectively ‘called party’ in case of MTC). |
Served MSISDN |
OM |
OM |
The MSISDN of the served party (‘calling party’ in case of MOC, ‘forwarding party’ in case of call forwarding respectively ‘called party’ in case of MTC). |
Called Number |
M |
M |
The address of the called party. |
Recording Entity |
M |
M |
The E.164 number of the visited MSC producing the record. |
Basic service |
M |
M |
Bearer or teleservice employed. ‘speech’ in case of CAMEL CPH calls. |
Supplementary Services |
C |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
GsmSCF address |
C |
C |
Identifies the CAMEL server serving the subscriber. |
Service Key |
C |
C |
The CAMEL service logic to be applied. |
Network call reference |
M |
M |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
M |
M |
This field contains the E.164 number assigned to the MSC that generated the network call reference. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Sum of all DPs encountered in this call. |
Level of CAMEL service |
OC |
OC |
Indicator for the complexity of the CAMEL feature used. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
CAMEL Destination Number |
Destination as received in the ICA operation. |
||
Translated Number |
Called number after digit translation within the MSC. |
||
Connected Number |
Number of connected party if different from ‘CAMEL Destination Number’. |
||
Roaming Number |
MSRN to route this leg (if applicable). |
||
MSC outgoing TKGP |
Trunk on which the leg leaves the MSC. |
||
Seizure Time |
Time of traffic channel seizure for this leg. |
||
Answer Time |
Time when the answer message is received for this leg. |
||
Release Time |
Time when the leg is released or moved into another call segment. |
||
Call Duration |
Time between answer and release timestamp of this leg. |
||
Additional Chg. Info |
Charge/no charge indicator and additional charging parameters, when available. |
||
Free Format Data |
If received in the FCI message from SCF. |
||
Free Format Data Append |
If received in the FCI message from SCF. |
||
Free Format Data 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append 2 |
If provided in the FCI message for a 2nd service. |
||
Diagnostics |
Detailed reason for disappearing of the leg in this call segment. |
||
Cause for Termination |
The reason for disappearing of the leg in this call segment. |
||
Default Call Handling 2 |
Present if a 2nd service (DP3) is triggered. |
||
gsm-SCF Address 2 |
Present if a 2nd service (DP3) is triggered. |
||
Service Key 2 |
Present if a 2nd service (DP3) is triggered. |
||
Free Format Data Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Location Routing Number |
For Number Portability feature, not available in 2G records. |
||
LRN Source Indicator |
Source of the LRN, not available in 2G records. |
||
LRN Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
JIP Parameter |
Jurisdiction Information Parameter, not available in 2G records. |
||
JIP Source Indicator |
The source of the JIP, not available in 2G records. |
||
JIP Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.26 Mobile originated call forwarding attempt (CAMEL CPH adapted version)
If the MSC / gsmSCF is able to provide CAMEL CPH services, this kind of record shall replace records according to clause 6.1.3.3 "Mobile originated call forwarding attempt". This applies to all mobile originated call forwarding attempts, even if no CPH operations are used in the individual call.
If the generation of MOC records is enabled in the forwarding MSC then the forwarding MSC shall produce an MOC record for the forwarded-leg of the call.
If further legs in new call segments are generated by this CAMEL dialogue, they are recorded in CDRs of type "6.1.3.25 New Call Segment in a MO, CF or MT CAMEL Dialogue".
Connection of a further leg to this call segment is recorded by adding a further field "CAMEL Call Leg Information". Optionally a partial record may be generated.
Table 6.1.3.26: MOC, call forwarding record (CAMEL CPH adapted version)
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Mobile originated. |
Served IMSI |
M |
M |
IMSI of the forwarding party. |
Served MSISDN |
OM |
OM |
The MSISDN of the forwarding party. |
Calling Number |
Oc |
Oc |
The address of the calling party. |
Called Number |
M |
M |
The address of the “forwarded-to” party. |
Recording Entity |
M |
M |
The E.164 number of the forwarding MSC |
Incoming TKGP |
OM |
OM |
The MSC trunk group on which the call originated at the forwarding MSC. |
Basic service |
C |
C |
‘speech’ in case of CAMEL CPH, not always available e.g. in case of call forwarding unconditional. |
Supplementary Services |
C |
C |
Supplementary services invoked as a result of this connection, if this information is available to the forwarding node. This field shall be present when one or more supplementary services have been invoked. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer time: time of answer (for successful calls) Release time: time of traffic channel release |
Call duration |
C |
C |
The chargeable duration of the connection for successful calls, the holding time of call attempts. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
GsmSCF address |
C |
C |
Identifies the CAMEL server serving the subscriber. |
Service key |
C |
C |
The CAMEL service logic to be applied. |
Network call reference |
C |
C |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
C |
C |
This field contains the E.164 number assigned to the MSC that generated the network call reference. |
CAMEL initiated CF indicator |
OC |
OC |
Indicates that the CAMEL server initiated call forwarding. Not available in case of gsm call forwarding. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Sum of all DPs encountered in this call. |
Level of CAMEL service |
OC |
OC |
Indicator of the complexity of the CAMEL feature used. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) messages. The data can be sent either in one FCI message or several FCI messages with append indicator. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
CAMEL Destination Number |
Destination modified by CAMEL service. |
||
Translated Number |
Called number after digit translation within the MSC. |
||
Connected Number |
Number of connected party if different from ‘CAMEL Destination Number’. |
||
Roaming Number |
MSRN to route this leg (if applicable). |
||
MSC outgoing TKGP |
Trunk on which the leg leaves the MSC. |
||
Seizure Time |
Time of traffic channel seizure for this leg. |
||
Answer Time |
Time when the answer message is received for this leg. |
||
Release Time |
Time when the leg is released or moved into another call segment. |
||
Call Duration |
Time between answer and release timestamp of this leg. |
||
Additional Chg. Info |
Charge/no charge indicator and additional charging parameters, when available. |
||
Free Format Data |
If received in the FCI message from SCF. |
||
Free Format Data Append |
If received in the FCI message from SCF. |
||
Free Format Data 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append 2 |
If provided in the FCI message for a 2nd service. |
||
Diagnostics |
Detailed reason for disappearing of the leg in this call segment. |
||
Cause for Termination |
The reason for disappearing of the leg in this call segment. |
||
Default Call Handling 2 |
Present if a 2nd service (DP3) is triggered. |
||
gsm-SCF Address 2 |
Present if a 2nd service (DP3) is triggered. |
||
Service Key 2 |
Present if a 2nd service (DP3) is triggered. |
||
Free Format Data Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Location Routing Number |
For Number Portability feature, not available in 2G records. |
||
LRN Source Indicator |
Source of the LRN, not available in 2G records. |
||
LRN Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
JIP Parameter |
Jurisdiction Information Parameter, not available in 2G records. |
||
JIP Source Indicator |
The source of the JIP, not available in 2G records. |
||
JIP Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
Free format data append indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.27 Terminating CAMEL call attempt (CAMEL CPH adapted version)
If the MSC / gsmSCF is able to provide CAMEL CPH services, this kind of record shall replace records according to clause 6.1.3.18 "Terminating CAMEL call attempt". This applies to all terminating CAMEL call attempts, even if no CPH operations are used in the individual call.
If the generation of these records is enabled, a terminating CAMEL call attempt record shall be generated for each call involving CAMEL CPH operations. The record is generated in the GMSC/gsmSSF carrying out the terminating CAMEL call handling and in the MSC server/gsmSSF carrying out the visited terminating CAMEL call attempt.
If further legs in new call segments are generated by this CAMEL dialogue, they are recorded in CDRs of type "6.1.3.25 New Call Segment in a MO, CF or MT CAMEL Dialogue".
Table 6.1.3.27: Terminating CAMEL record (CPH adapted version)
Field |
2G |
3G |
Description |
---|---|---|---|
Record Type |
M |
M |
Terminating CAMEL interrogation. |
Served IMSI |
M |
M |
IMSI of the called party |
Served MSISDN |
OM |
OM |
The MSISDN of the called party. |
Recording Entity |
M |
M |
The E.164 number of the GMSC. |
Interrogation time stamp |
M |
M |
Time at which the interrogation was invoked. |
GsmSCF Address |
M |
M |
The CAMEL server serving the subscriber. |
Service key |
M |
M |
The CAMEL service logic to be applied. |
Network call reference |
M |
M |
An identifier to correlate transactions on the same call taking place in different network nodes. |
MSC Address |
M |
M |
This field contains the E.164 number assigned to the MSC that generated the network call reference. |
Default call handling |
OC |
OC |
Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Called Number |
M |
M |
The address of the called party as received by the GMSC/gsmSSF. |
Calling Number |
C |
C |
The address of the calling party, if available. |
Incoming TKGP |
OM |
OC |
The GMSC trunk group on which the call originated. If available in 3G, this parameter shall be supplied. |
Event time stamps |
C C OM |
C C OM |
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts) Answer time: time of answer (for successful calls) Release time: time of traffic channel release |
Call duration |
C |
C |
The chargeable duration of the connection for successful calls, the holding time of call attempts. |
Cause for Termination |
M |
M |
The reason for the release of the connection. |
Diagnostics |
OM |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
C |
Partial record sequence number, only present in case of partial records. |
Number of DP encountered |
OC |
OC |
Number that counts how often armed detection points (TDP and EDP) were encountered. Sum of all DPs encountered in this call. |
Level of CAMEL service |
OC |
OC |
Indicator of the complexity of the CAMEL feature used. |
Free format Data |
C |
C |
This field contains data sent by the gsmSCF in the Furnish Charging Information (FCI) message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. |
CAMEL call leg information |
C |
C |
Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. |
CAMEL Destination Number |
Destination as received in the ICA operation or overwritten by TDP3. |
||
Translated Number |
Called number after digit translation within the MSC. |
||
Connected Number |
Number of connected party if different from ‘CAMEL Destination Number’. |
||
Roaming Number |
MSRN or B-party (if applicable). |
||
MSC outgoing TKGP |
Trunk on which the leg leaves the MSC. |
||
Seizure Time |
Time of traffic channel seizure for this leg. |
||
Answer Time |
Time when the answer message is received for this leg. |
||
Release Time |
Time when the leg is released or moved into another call segment. |
||
Call Duration |
Time between answer and release timestamp of this leg. |
||
CAMEL Init CF Indicator |
Indicates that the CAMEL server initiated call forwarding. |
||
Additional Charging Info |
Charge/no charge indicator and additional charging parameters, when available. |
||
Free Format Data |
If received in the FCI message from SCF. |
||
Free Format Data Append |
If received in the FCI message from SCF. |
||
Free Format Data 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append 2 |
If provided in the FCI message for a 2nd service. |
||
Diagnostics |
Detailed reason for disappearing of the leg in this call segment. |
||
Cause for Termination |
The reason for disappearing of the leg in this call segment. |
||
Default Call Handling 2 |
Present if a 2nd service (DP3) is triggered. |
||
gsm-SCF Address 2 |
Present if a 2nd service (DP3) is triggered. |
||
Service Key 2 |
Present if a 2nd service (DP3) is triggered. |
||
Free Format Data Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Free Format Data Append Incoming 2 |
If provided in the FCI message for a 2nd service. |
||
Location Routing Number |
For Number Portability feature, not available in 2G records. |
||
LRN Source Indicator |
Source of the LRN, not available in 2G records. |
||
LRN Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
JIP Parameter |
Jurisdiction Information Parameter, not available in 2G records. |
||
JIP Source Indicator |
The source of the JIP, not available in 2G records. |
||
JIP Query Status Indicator |
Status of Number Portability query, not available in 2G records. |
||
Free format data append indicator |
C |
C |
Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. |
MSC server indication |
C |
C |
Indication if the CAMEL call handling is active in the MSC server. |
Partial Record Type |
– |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.28 SRVCC MSC Call handling in MSC server enhanced for SRVCC
If the generation of these records is enabled then a MSC-SRVCC record shall be created for each voice call transfer from IMS domain to CS domain, for voice calls anchored in the IMS. These MSC-SRVCC records shall be produced in the enhanced MSC Server enhanced for SRVCC.
Table 6.1.3.28: MSC-SRVCC record
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MSC-SRVCC |
Served IMSI |
M |
IMSI of PS to CS Request. |
Served IMEI |
C |
Mobile Equipment Identity (IMEI, IMEISV) of the UE, if available |
Served MSISDN |
M |
The Correlation MSISDN of the PS to CS Request. |
Called Number |
M |
Session Transfer Number for Single Radio Voice Call Continuity (STN-SR) for transfer from PS to CS |
Recording Entity |
M |
The E.164 number of the enhanced MSC server producing the record. |
Outgoing TKGP |
OM |
The trunk group on which the call left the MSC, if available |
IMS Charging Identifier |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the enhanced MSC server with SIP interface. |
Related ICID |
OC |
This parameter holds the IMS charging identifier (ICID) from the IMS call leg. |
Related ICID Generation Node |
OC |
This parameter holds the identifier of the IMS node that generated the Related ICID. |
Location |
M |
Location of the UE after the successful SRVCC PS to CS Transfer. |
Change of Location |
OC |
A list of changes in Location of the UE. Each time-stamped. |
Basic service |
M |
teleservice speech |
Supplementary Services |
C |
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. |
MS Classmark |
C |
Classmark of MM Context for E-UTRAN SRVCC in PS to CS Request |
Event time stamps |
C C OM |
Transfer request time: time of PS to CS Request received by enhanced MSC server. Answer: time of answer received by enhanced MSC server on successful transfer Release time: time of traffic channel release |
ICS I2 active Flag |
C |
This field indicates that the MSC is IMS registered on the UE’s behalf during the session |
Call duration |
M |
The chargeable duration of the connection for successful transferred call. |
Cause for Termination |
M |
The reason for the release of the CS media. |
Diagnostics |
OM |
A more detailed reason for the release of the CS media |
Call reference |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
Partial Record Type |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.29 SRVCC CS Emergency Call handling in MSC server enhanced for SRVCC
If the generation of these records is enabled then a MSC-SRVCC Emergency record shall be created for each emergency call transfer from IMS domain to CS domain, for emergency calls anchored in the IMS. These MSC-SRVCC Emergency records shall be produced in the MSC server enhanced for SRVCC.
Table 6.1.3.29: MSC-SRVCC Emergency record
Field |
Category |
Description |
---|---|---|
Record Type |
M |
MSC-SRVCC |
Served IMSI |
C |
IMSI of PS to CS Request, if available. |
Served IMEI |
C |
Mobile Equipment Identity (IMEI, IMEISV) of the UE, if available |
Served MSISDN |
C |
The Correlation MSISDN of the PS to CS Request, if available. |
Called Number |
M |
Emergency Session Transfer Number for SR VCC (E-STN-SR) for transfer from PS to CS. |
Recording Entity |
M |
The E.164 number of the enhanced MSC server producing the record. |
Outgoing TKGP |
OM |
The trunk group on which the call left the MSC, if available |
IMS Charging Identifier |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the enhanced MSC server with SIP interface. |
Related ICID |
OC |
This parameter holds the IMS charging identifier (ICID) from the IMS call leg. |
Location |
M |
Location of the UE after the successful SRVCC PS to CS Transfer. |
Change of Location |
OC |
A list of changes in Location of the UE. Each time-stamped. |
Basic service |
M |
teleservice emergency |
MS Classmark |
C |
Classmark of MM Context for E-UTRAN SRVCC in PS to CS Request |
Event time stamps |
C C OM |
Transfer request time: time of PS to CS Request received by enhanced MSC server. Answer: time of answer received by enhanced MSC server on successful transfer Release time: time of traffic channel release |
ICS I2 active Flag |
C |
This field indicates that the MSC is IMS registered on the UE’s behalf during the session |
Call duration |
M |
The chargeable duration of the connection for successful transferred call. |
Cause for Termination |
M |
The reason for the release of the CS media. |
Diagnostics |
OM |
A more detailed reason for the release of the CS media |
Call reference |
M |
A local identifier distinguishing between transactions on the same MS |
Sequence number |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
A set of network / manufacturer specific extensions to the record, when available. |
Partial Record Type |
OC |
Indicates the event (time limit etc.) that caused the generation of a partial record. |
6.1.3.30 Mobile Terminating Roaming Forwarding (MTRF) call after successful retrieval of routeing information handling in VMSC
If the generation of these records is enabled then a MTRF record shall be created for each call re-routed from an original MSC to a destination MSC, resulting from Mobile Terminating Roaming Forwarding (MTRF) procedure. The MTRF records shall be produced in the MSC/VLR behaving as the Original MSC the call is re-routed from.
Table 6.1.3.30: MTRF record
Field |
3G |
Description |
---|---|---|
Record Type |
M |
Mobile Terminating Roaming Forwarding. |
Served IMSI |
M |
IMSI of the called party. |
Served IMEI |
C |
IMEI of the called ME, if available. |
Served MSISDN |
OM |
The MSISDN of the called party. |
Calling Number |
C |
The number of the calling party if available. |
Roaming Number |
M |
The Mobile Station Roaming Number employed by the VMSC for routing to the new VMSC. |
Recording Entity |
M |
The E.164 number of the VMSC (i.e Old VMSC the call is re-routed from) |
Incoming TKGP |
OM |
The VMSC trunk group on which the call originated. |
Outgoing TKGP |
OC |
The trunk group on which the call left the VMSC. |
Basic Service |
M |
teleservice employed |
Event time stamps |
C C OM |
Seizure time: time of incoming trunk seizure Answer time: time of answer for successful calls Release time: time of outgoing trunk release |
Call duration |
M |
The chargeable duration of the connection if successful, the holding time of the incoming trunk for call attempts if unsuccessful. |
Cause for Termination |
M |
The reason for the release of the call. |
Diagnostics |
OM |
A more detailed reason for the release of the connection. |
Call reference |
M |
A local identifier distinguishing between transactions at the same MS |
Sequence number |
C |
Partial record sequence number, only present in case of partial records. |
Record extensions |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
Partial Record Type |
OC |
Indicates the event (time limit, etc.) that caused the generation of a partial record. |
6.1.3.31 ICS register (MSC Server enhanced for ICS)
If the generation of these records is enabled then a ICS register record shall be created for each time when MSC register, re-register or de-register subscriber to IMS domain. These ICS register records shall be produced in the enhanced MSC Server enhanced for ICS.
Table 6.1.3.31: ICS register (MSC Server enhanced for ICS)
Field |
2G |
3G |
Description |
Record Type |
M |
M |
ICS register |
Served IMSI |
M |
M |
IMSI of the served MS. |
Served MSISDN |
OM |
OM |
IMS user E.164 identities |
Recording Entity |
M |
M |
The E.164 number of the entity (ICS-MSC) generating the record. |
New location |
M M OM |
M M OM |
MSC E.164 Number Location Area Code Cell Identification or Service Area Code and MCC+MNC The Cell Identity contains the 16 least significant bits and the Tracking Area Code is placed in the Location Area Code field if E-UTRAN location update. |
Location Extension |
OC |
OC |
The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN location update. |
Update time stamp |
M |
M |
Time at which the update was invoked. |
IMS Charging Identifier |
OM |
OM |
This parameter holds the IMS charging identifier (ICID) as generated by the enhanced MSC server with SIP interface. |
IMS Private user Identity |
OM |
OM |
This field contains the IMS Private User Identity and Public User Identity specifically reserved for IMS registrations. |
List of Inter Operator Identifiers |
OC |
OC |
Holds the identification of the home network (originating and terminating) if exchanged via SIP signalling, as recorded in the P-Charging-Vector header. This grouped field may occur several times in one CDR. |
Originating IOI |
OC |
OC |
This parameter corresponds to Orig-IOI header of the P-Charging-Vector defined in TS 24.292 [221]. |
Terminating IOI |
OC |
OC |
This parameter corresponds to Term-IOI header of the P-Charging-Vector defined in TS 24.292 [221]. |
Transit IOI List |
Oc |
Oc |
This parameter corresponds to Transit-IOI List of the P-Charging-Vector defined in TS 24.229 [221]. This field may occur several times in one CDR. |
Update Result |
C |
C |
The result of the location update if unsuccessful. |
Record extensions |
OC |
OC |
A set of network/ manufacturer specific extensions to the record, when available. |
6.2 Data description for CS domain online charging
6.2.0 General
CS domain charging is implemented by CAMEL techniques as described in TS 23.078 [67] and TS 29.078 [73], i.e. it is outside the scope of the 3GPP 32-series charging TSs.
6.2.1 Diameter message contents
Void (refer to clause 6.2.0).
Annex A (informative):
CDR File Transfer compliant with earlier 3GPP releases
This group of TMN functions is concerned with the bulk transfer of call and event records from the NEF record filestore to the NEF.
The call and event records shall be transferred from the NEF to the OSF by the use of FTAM protocol on X.25 or TCP/IP, and FTP or TFTP over TCP/IP. For further details of the use of FTAM see GSM 12.01 [297] and of the use of FTP see RFC 959 [400] and TFTP see [401].
In addition to the simple file transfer services provided by FTAM, peer-to-peer application process communication may be also be supported. The use of CMIS services for the uploading of files from the NEF to the OSF is specified in GSM 12.00 [296].
Annex B (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in this specification.
Annex C (informative):
Charging support for Voice Call Continuity (VCC)
VCC is a home IMS application that provides capabilities to transfer voice calls between the CS domain and the IMS. VCC provides functions for voice call originations, voice call terminations and for domain transfers between the CS domain and the IMS. This feature is defined in TS 23.206 [210].
The following principles apply to VMSC/GMSC that are capable of VCC:
In case of CS Origination call with anchoring in the IMS, the Access Leg is charged as follows: Normal MOC CDR is generated by the VMSC with special handling. One example of special handling is to zero rate the CS resource usage. This can be performed using the "Service Key" parameter in the MOC Record indicating a VCC call. The CDRs generated within the IMS domain to complete the anchoring mechanism are handled as specified in TS 32.260 [55].
In case of IMS origination call, the Access Leg is charged as follows: Normal IMS and IP-CAN (e.g. WLAN or GSM/GPRS) charging mechanism are applied. These mechanisms are defined in TS 32.260 [55] and IP-CAN Middle Tier TS respectively.
In case of Incoming call received via CS and routed to IMS, the Remote Leg is charged as follows: Normal MTC CDRs are generated by the GMSC of the terminating network with special handling. One example of special handling is to zero rate the CS resource usage. This can be performed using the "Service Key" parameter in the MTC Records indicating a VCC call. The CDRs generated within the IMS domain to complete the domain selection procedure are handled as specified in TS 32.260 [55].
In case of Incoming call received via CS and routed to CS with anchoring, the Remote Leg is charged as follows: Normal MTC CDRs are generated by the GMSC and the VMSC in the terminating network with special handling. One example of special handling is to zero rate the CS resource usage. This can be performed using the "Service Key" parameter in the MTC Records indicating a VCC call. The CDRs generated within the IMS domain to complete the anchoring procedure are handled as specified in TS 32.260 [55].
In case of Incoming call received via IMS and routed to IMS, the Remote Leg is charged as follows: Normal IMS and IP-CAN (e.g. WLAN or GSM/GPRS) charging mechanism are applied. These mechanisms are defined in TS 32.260 [55] and IP-CAN middle tier TS respectively.
In case of Incoming call received via IMS and routed to CS with anchoring, the Remote Leg is charged as follows: Normal MTC CDRs are generated by the GMSC or the VMSC in ther terminating network with special handling. One example of special handling is to zero rate the CS resource usage. This can be performed using the "Service Key" parameter in the MTC Records indicating a VCC call. The CDRs generated within the IMS domain to complete the domain selection procedure are handled as specified in TS 32.260 [55].
In case of domain transfer from IMS to CS, the Access Leg is charged as follows: Normal MOC CDR is generated by the VMSC of the new Access Leg with special handling. One example of special handling is to zero rate the CS resource usage. This can be performed using the "Service Key" parameter in the MOC Record indicating a VCC call. The IMS CDRs generated to perfom domain transfer are handled as specified in TS 32.260 [55].
In case of domain transfer from CS to IMS, the Access Leg is charged as follows: The MOC CDRs of the Source-Access Leg (i.e. the Access leg previously established over CS) are closed when the Source Acces Leg is released following normal CDR closure associated with CS call release. The IMS CDRs generated on the new access Leg are handled as specified in TS 32.260 [55].
Annex D (informative):
Change history
Change history |
||||||||
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Cat |
Old |
New |
Mar 2007 |
SA_35 |
SP-070039 |
0010 |
— |
Introduce CS charging implications of VCC |
B |
6.6.0 |
7.0.0 |
Mar 2007 |
SA_35 |
SP-070043 |
0011 |
— |
Add MCC MNC in Location/change of location field |
B |
6.6.0 |
7.0.0 |
Jun 2007 |
SA_36 |
SP-070268 |
0013 |
— |
Correction on MOC CDRs – Align with ITU ISUP Q.763 |
A |
7.0.0 |
7.1.0 |
Dec 2008 |
SA_42 |
— |
— |
— |
Upgrade to Release 8 |
— |
7.0.0 |
8.0.0 |
Sep 2009 |
SA_45 |
SP-090536 |
0014 |
– |
Correction to MO and MT SMS CDRs for SMS over SGs |
F |
8.0.0 |
8.1.0 |
Dec 2009 |
– |
– |
– |
– |
Update to Rel-9 version (MCC) |
– |
8.1.0 |
9.0.0 |
Mar 2010 |
SA_47 |
SP-100040 |
0016 |
— |
Correction on System Type parameter |
F |
9.0.0 |
9.1.0 |
Mar 2011 |
SA_51 |
SP-110108 |
0018 |
1 |
Introduction of new CDRs for SRVCC feature in enhanced MSC server – Alignment with 3GPP TS 23.216 |
F |
9.1.0 |
9.2.0 |
2011-03 |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.2.0 |
10.0.0 |
|
2011-03 |
– |
– |
– |
– |
Correction of Update to Rel-10 version (MCC) |
10.0.0 |
10.0.1 |
|
2011-06 |
SA_52 |
SP-110281 |
0020 |
— |
Clarification on Mobile Originating Call Forwarding CDR generation when no O-CSI |
F |
10.0.1 |
10.1.0 |
2011-09 |
SA_53 |
SP-110530 |
0022 |
1 |
Correction on MT-LR CDR – Alignment with TS 23.271 |
F |
10.1.0 |
10.2.0 |
2011-12 |
SA_54 |
SP-110709 |
0024 |
1 |
Correction on MSC-SRVCC CDRs for Suppl services and location |
A |
10.2.0 |
10.3.0 |
Mar 2012 |
SA_55 |
SP-120047 |
0028 |
1 |
Correction for E-UTRAN location (TAI and E-CGI) on Location Update (VLR) record |
A |
10.3.0 |
10.4.0 |
Mar 2012 |
SA_55 |
SP-120050 |
0025 |
1 |
Correction on Charging for Mobile Terminating Roaming Forwarding (MTRF) – alignment with TS 23.018 |
F |
10.3.0 |
10.4.0 |
Jun 2012 |
SA_56 |
SP-120397 |
0032 |
1 |
R11 CR 32250 Add charging parameters for NetLoc |
B |
10.5.0 |
11.0.0 |
Mar 2013 |
SA_59 |
SP-130054 |
0036 |
1 |
Related ICID Corrections for SRVCC Charging Correlation |
F |
11.0.0 |
11.1.0 |
Mar 2014 |
SA_63 |
SP-140037 |
0038 |
2 |
Charging management for IMS Centralized Services (ICS) |
C |
11.1.0 |
12.0.0 |
Jun 2014 |
SA_64 |
SP-140338 |
0039 |
1 |
Addition of description for IMS registration via CS access |
C |
12.0.0 |
12.1.0 |
Jul 2014 |
– |
– |
– |
– |
Rapporteur/MCC: General editorial changes and clean-up. |
– |
12.1.0 |
12.1.1 |
Sep 2014 |
SA_65 |
SP-140564 |
0040 |
1 |
Corrections for alignment between charging specifications |
F |
12.1.1 |
12.2.0 |
Dec 2014 |
SA_66 |
SP-140805 |
0041 |
– |
Correction on ‘Served IMSI’ in MOC Call Forwarding CDR |
F |
12.2.0 |
12.3.0 |
SP-140804 |
0042 |
– |
Additional corrections for removal of I-WLAN solution |
F |
||||
SP-140805 |
0043 |
– |
Corrections on definition for parameter category |
F |
||||
Jan 2016 |
Upgrade to Rel-13 (MCC) |
12.3.0 |
13.0.0 |
Change history |
|||||||
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
2017-03 |
SA#75 |
Promotion to Release 14 without technical change |
14.0.0 |
||||
2017-06 |
SA#76 |
SP-170500 |
0048 |
1 |
B |
Introduce MSISDN-less SMS MO via T4 charging |
14.1.0 |
2018-06 |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
2021-09 |
SA#93e |
SP-210895 |
0049 |
– |
F |
Inclusive language review |
17.0.0 |