TD.57 v36.5 - TAP Format Specs

GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members
Official Document TD.57 - TAP 3.12 Format Specification
TAP 3.12 Format Specification

Version 36.4
15 May 2019
This is a Binding Permanent Reference Document of the GSMA
Security Classification: Confidential - Full, Rapporteur, Associate and Affiliate

Members
Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the
Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and
information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted
under the security classification without the prior written approval of the Association.
Copyright Notice
Copyright © 2020 GSM Association
Disclaimer
The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept
any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document.
The information contained in this document may be subject to change without prior notice.
Antitrust Notice
The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.
V36.4 Page 1 of 317

Table of Contents
1 Introduction 5
1.1 Overview 5
1.2 Scope 5
1.3 Abbreviations 5
1.4 References 6
Billing Identifier (BID) Notification and Synchronization Process 7
1.5 Conventions 7
2 Differences from the Commercial Requirement 7
2.1 Transfer Frequency 7
2.2 File Creation Timestamp 7
2.3 File Available Timestamp 8
2.4 Version Control 8
2.5 Reference Tables 8
2.6 Supplementary Services 8
2.7 Location Information 8
2.8 Dates and Times 9
2.9 File Size Limitations 9
2.10 Support for Interstandard Number Portability 9
2.11 Calculated Exchange Rate for Currencies Not Published by GSER 9
2.12 Exchange Rate for Currencies Published by GSER 9
2.13 Exchange Rate higher than expected 9
2.14 Partial Type Indicator 10
2.15 TAP Versions Supported 10
2.16 Aggregated Usage Record Date(s) 10
2.17 Aggregated Usage Record Implementation Date 10
3 Logical Structure 11
3.1 Data Interchange 12
3.2 Transfer Batch 13
3.3 Batch Control Information 14
3.4 Accounting Information 15
3.5 Network Information 16
3.6 Aggregated Usage Record 17
3.7 Mobile Originated call 18
3.8 MO Basic Call Information 19
3.9 Location Information 20
3.10 Basic Service Used 21
3.11 Charge Information 22
3.12 CAMEL Service Used 23
3.13 Mobile Terminated Call 24
3.14 MT Basic Call Information 25
3.15 Mobile Session 26
3.16 Session Charge Information 27
3.17 Messaging Event 28
V36.4 Page 2 of 317

3.18 Supplementary Service Event 29

3.19 Supplementary Service Used 30
3.20 Service Centre Usage 31
3.21 GPRS Call 32
3.22 GPRS Basic Call Information 33
3.23 GPRS Service Used 34
3.24 Content Transaction 35
3.25 Content Transaction Basic Info 36
3.26 Charged Party Information 37
3.27 Content Service Used 38
3.28 Advised Charge Information 39
3.29 Location Service 40
3.30 Tracking Customer Information 41
3.31 Tracked Customer Information 42
3.32 Location Service Usage 43
3.33 Audit Control Information 44
4 Data Dictionary 45
4.1 A 46
4.2 B 62
4.3 C 66
4.4 D 114
4.5 E 122
4.6 F 129
4.7 G 133
4.8 H 140
4.9 I 143
4.10 L 146
4.11 M 154
4.12 N 166
4.13 O 174
4.14 P 178
4.15 R 183
4.16 S 193
4.17 T 208
4.18 U 231
4.19 V 234
4.20 Context Abbreviations 237
5 Classification of Errors 237
5.1 Known Issues Impact 237
5.2 Severity Levels 237
5.3 Naming and Numbering of Error Codes 238
5.3.1 Bilaterally Agreed Validation Errors 239
5.4 Other General Errors Not Listed in the Data Dictionary 239
5.5 Validation Rules Not Described in the Data Dictionary 241
V36.4 Page 3 of 317

5.6 Text Representation of IP Addresses 244

5.7 Validation of ASCII String Type elements 244
5.8 Identification of Emergency Calls 245
5.9 TAP Record Charge Validation Procedure 245
5.9 Provision of TAP Events on VoLTE handover scenarios 247
5.10 Provision of TAP Events on SMS Messaging 249
5.11 Provision of TAP Events on VoLTE S8 Home Routed (S8HR) Scenarios 250
5.12 Provision of TAP Events on VoLTE LBO HR, like for S8HR (new option) 251
6 Physical Structure 251
6.1 Abstract Syntax 252
6.2 Transfer Syntax 288
6.3 File Naming Conventions 288
6.3.1 Chargeable TAP Data 288
6.3.2 Test TAP Data 288
7 Migration to a New Release 288
Annex A Supplementary Services 290
Annex B Changes from Previous Specification Version Number 293
Annex C Description of 3GPP Releases and Specifications 301
C.1 Charging Specifications 301
C.2 Cause for Termination 301
C.3 Service Codes 302
Annex D Document Management 306
D.1 Document History 306
D.2 Other Information 316
V36.4 Page 4 of 317

1 Introduction
1.1 Overview
This document defines the logical and physical data that must be transferred between
PMNs under the Transferred Account Procedure (TAP). It additionally contains all the
validation rules that can be applied to a TAP3 file.
The transfer mechanism for TAP files is discussed in TD.28 [32].
The primary commercial requirement for data to be transferred is defined in permanent

reference document BA.12 [12].
Note: Because there are many standards and documents relating to the Transferred
Account Procedure, terminology can become confused, not least because each standard
may have its own term for any particular item of data. For the purposes of this document
BA.12 [12] is considered the prime input document in terms of the commercial requirement
and items are named accordingly.
The other major input documents are the 3GPP specifications listed in Annex C.
1.2 Scope
The version of TAP supported by this document is Specification Version Number 3, Release
Version Number 12. The implementation timetable for this version of TAP is such that all
TAP files created on or after 01 July 2017 must conform to this standard (see TD.34 [15] for
further information on implementation of new TAP standards).
1.3 Abbreviations
Term Description
ASN Abstract Syntax Notation
BER Binary Encoding Rules
PMN Public Mobile Network
HPMN Home PMN
IMF International Monetary Fund
TAP Transferred Account Procedure
VPMN Visited PMN
ATCF Access Transfer Control Function
CDR Call Detail Record
CS Circuit Switched
CSFB Circuit Switched Fall Back
eSRVCC Enhanced Single Radio Voice Call Continuity
GSER GSMA Standardised Exchange Rates
MSC Mobile Switching Centre
MSU Message Signal Unit
P-CSCF Proxy Call Session Control Function
V36.4 Page 5 of 317

PMN Public Mobile Network

REVOLVER Re-Evaluation of VoLTE: Verification of Roaming Models
TRF Transit and Roaming Function
VoIMS Voice over IP Multimedia Subsystem
VoLTE Voice over Long Term Evolution
1.4 References
Document
Ref Number Title
[1] 3GPP TS 22.004 General on Supplementary Services
[2] 3GPP TS 22.030 Man-Machine Interface (MMI) of the User Equipment (UE)
[3] 3GPP TS 29.002 Mobile Application Part (MAP) specification
[4] 3GPP TS 32.005 3G call and event data for the Circuit Switched (CS) domain
[5] 3GPP TS 32.015 GSM Call Event Data for the Packet Switched (PS) domain
[6] 3GPP TS 32.205 Charging data description for the Circuit Switched (CS) domain
[7] 3GPP TS 32.215 Charging data description for the Packet Switched (PS) domain
[8] 3GPP TS 32.298 Charging Data Record (CDR) Parameter Description
[9] CIBER Manual v2.0 CIBER Manual v2.0
[10] GSMA PRD BA.08 Timescales For Data Transfer
[11] GSMA PRD BA.11 Billing and Accounting Information – Treatment of Exchange rates
[12] GSMA PRD BA.12 Transferred Account Procedure and Billing Information
[13] GSMA PRD BA.27 Charging and Accounting Principles
[14] GSMA PRD TD.13 TADIG Code Naming Conventions (GSM Infocentre database)
[15] GSMA PRD TD.34 TAP Release Management Process
GSMA PRD BA.62 BA.62 Roaming Hubbing Business Requirements Commercial
[16]
Model
[17] GSM TS 12.05 Event and call data
[18] GSM TS 12.15 GPRS Charging
[19] <ref not in use>
[22] IETF RFC 2866 RADIUS Accounting
[23] IETF RFC 2869 RADIUS Extensions
[26] ISO 4217 Codes for the representation of currencies and funds
ISO 646 Information Processing – ISO 7-bit coded character set for
[27]
information interchange
ITU E.164 Principles, criteria and procedures for the assignment and
[28]
reclamation of E.164 country codes and associated identification
V36.4 Page 6 of 317

codes for groups of countries

[30] 3GPP TS 22.004 General on Supplementary Services
[31] IETF RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
[32] GSMA PRD TD.28 File Transfer Methods
[33] GSMA PRD TD.58 TAP3.12 Implementation Handbook
[34] IETF RFC 4282 The Network Access Identifier
[35] GSMA PRD TD.38 Billing Identifier (BID) Notification and Synchronization Process
[36] 3GPP TS 23.032 Universal Geographical Area Description (GAD)
[37] ITU REC X.680 Abstract Syntax Notation One (ASN.1)
ITU REC X.690 ASN.1 encoding rules: Specification of Basic Encoding Rules
[38] (BER), Canonical Encoding Rules (CER) and Distinguished
Encoding Rules (DER)
[39] GSMA PRD BA.29 RAEX Op Data Business Requirements
[40] GSMA PRD TD.77 RAEX Op Data Format Specification
[41] 3GPP TS 32.225 Charging data description for the
IP Multimedia Subsystem (IMS)
[42] 3GPP TS 32.274 Short Message Service (SMS) charging
[43] 3GPP TS 09.02 Mobile Application Part (MAP) Specification
[44] 3GPP TS 29.002 Mobile Application Part (MAP) specification
1.5 Conventions
The key words “must”, “must not”, “required”, “shall”, “shall not”, “should”, “should not”,
“recommended”, “may”, and “optional” in this document are to be interpreted as described in
RFC 2119 [31].
2 Differences from the Commercial Requirement

The IDS TAP file specification differs from the commercial requirement.
These differences are due to a number of factors including implementation considerations.

The detailed differences are itemised below.
2.1 Transfer Frequency

BA.12 [12] sets a maximum limit to the number of TAP files that a Recipient is obliged to
accept from a given Sender per day.
If the volume of traffic per day for a given Roaming Agreement is such that it cannot be
transferred within the number of files specified by BA.12 [12], without violating the file size
and/or number of records limit specified within this document, then this ‘files per day’ limit
may be exceeded. No Fatal, Severe or Warning errors can be raised by the Recipient in
this case.
2.2 File Creation Timestamp

The date and time of the file creation is included.
V36.4 Page 7 of 317

2.3 File Available Timestamp

Due to constraints in the physical file transfer environment where PMNs push data to
HPMNs it is not possible to identify the actual date and time when the file is fully available
on the HPMN’s system. In these cases the File Available Timestamp is set to the date and
time when the ‘push’ started.
The difference between this time and the actual time the transfer has completed is
considered to be insignificant under normal circumstances and any major differences noted
are expected to be handled by negotiation between the PMNs concerned.
2.4 Version Control

The TAP Specification Version and Release Version numbers are included in order to allow
HPMNs to be able to identify the standard being used on the interface.
2.5 Reference Tables

In order to minimise the amount of data transferred and to avoid the repetition of frequently
identical information at the call/event level a series of reference tables have been
incorporated:
 Message Description Information; each table row comprises a code with its
description.
 Taxation; each table row comprises a code with its tax type and rate.
 Discounting; each table row comprises a code with its discount applied, either the
fixed discount amount or a discount rate.
 Currency Conversion; each table row comprises a code with its exchange rate and
an indication of how many decimal places are represented.
 UTC Time Offset Information; each table row comprises a code with its offset value.
 Recording Entity Information; each table row comprises a code with its entity type,
for example MSC, and entity identifier.
The codes are used within the calls/events as required.
2.6 Supplementary Services

Unlike 3GPP TS 32.005 [4], GSM Association PRD BA.12 [12] has no concept of events.
BA.12 [12] assumes that supplementary services, when not used in conjunction with a call
action, for example activation, are treated in a similar manner to mobile originated calls.
There will be no called party but some supplementary services have additional information
which may be useful for example the number involved in call forward activation.
These non call related Supplementary Services are treated as separate events within the
TAP.
2.7 Location Information

The Location Area Code (LAC), Cell Identity and SGSN Address are maintained in TAP for
all applicable services for technical and operational reasons.
V36.4 Page 8 of 317

2.8 Dates and Times

All date/time items cater for millennium compliance and have the format
CCYYMMDDHHMMSS.
All timestamps are provided in the sending PMN’s local time further qualified by an offset
from Universal Time (UTC). This enables the HPMN to easily calculate its (HPMN) local
time, especially useful when computing charges for forwarding calls to roamed subscribers.
2.9 File Size Limitations

Due to the high system resource consumption of tools used for ASN.1 processing, as used
for TAP3, a file size limit has been set (see ‘Validation Rules Not Described In Data
Dictionary’).
2.10 Support for Interstandard Number Portability

Inclusion of elements ESN (Electronic Serial Number), MIN (Mobile Identification Number)
and MDN (Mobile Directory Number) are required to support mobile number portability
within markets supporting various technology standards, for example USA.
2.11 Calculated Exchange Rate for Currencies Not Published by GSER

The GSMA offers a GSER (GSMA Standardised Exchange Rates) tool as per the details
defined in BA.11 [11]. Most exchange rates use in the industry are published by GSER. The
full list of GSER currencies is available in BA.11 [11].
A tolerance of two units on the 5th significant digit of the calculated Exchange Rate for
currencies that are not published by GSER is required to avoid operational problems when
validating the Exchange Rate on different systems.
Note: This is needed due to inaccurate values of calculated exchange rates used in the
industry.
2.12 Exchange Rate for Currencies Published by GSER

Like IMF, GSER publishes exchange rates to 6 significant digits. Historically, some operator
systems have been developed to support only 5 decimal places for exchange rates and a
tolerance has therefore been introduced to allow operators who cannot support the full
number of significant digits published by GSER to round either up or down from the more
accurate GSER exchange rate.
Note: This is needed as not all operators are able to support more than 5 significant digits.
Operators who can support all digits as published by GSER must, of course, not round the
exchange rate in TAP and must populate TAP with the full GSER published exchange rate.
2.13 Exchange Rate higher than expected

A validation rule has been added for operational reasons to enable TAP files to be rejected
when Exchange Rates are higher than expected.
V36.4 Page 9 of 317

2.14 Partial Type Indicator

BA.12 [12] states that this element is mandatory to populate where the TAP record
represents part of a context, whereas there is no validation rule currently applied on Partial
Type Indicator existence and validity in TAP.
Practically, and due to implementation concerns, adding such validation rules would create
a number of operational issues, therefore such rules are not defined.
2.15 TAP Versions Supported

BA.12 [12] states rules governing liabilities for conversion between TAP versions. The
implicit requirement is for no restrictions on the TAP versions used.
Practically, this is technically no longer tenable and the technical constraint is that the public
interface will only support the latest two versions. At the time of writing, November 2013,
this means that the current TAP version v3.12 and the preceding one v3.11 are allowed on
the public interface. Use of any other TAP version must be bilaterally agreed.
The BA.12 [12] conversion requirements remain unaffected.
2.16 Aggregated Usage Record Date(s)

The business requirement as stated in BA.12 [12] requires only a single date, that is, the
record allows only aggregation of usage related to a single date.
In order to provide flexibility of usage there is an additional date included to enable definition
of a period that the aggregated usage represents.
2.17 Aggregated Usage Record Implementation Date

The business requirement as stated in BA.12 [12] refers to an effective date of 01 May
2017, however, due to technical considerations, the effective date of the specification is 01
July 2017.
V36.4 Page 10 of 317

3 Logical Structure
The following conventions have been used in the logical structure diagrams:
'C' indicates that the Dash (green) lined

element is conditional; the boxes indicate
conditionality rules are group elements
described in the Data
Dictionary entry for the
element Element A
Level 0
'R' indicates that the

element occurs one or more
Element B Element C Element D times. If the element is 'C'
Level 1 Level 1 Level 1 or 'O' then it may occur zero
or more times
C R OC C R
O O
Element E Element F Element G Element H
Level 2 Level 2 Level 2 Level 2
M M M M Solid (black)
lined boxes
indicate item
elements
'O' indicates that the

'o' indicates element is optional; the
that only one of optionality rules are
the elements described in the Data
grouped at this Dictionary entry for the 'M' indicates that
level is element the element is
applicable mandatory
Figure 1: Conventions used within Logical Structure Diagrams
In the following sections the logical structure is broken down diagrammatically to show the
logical record formats. Each item is clarified to show whether it is:
Mandatory Must be present.

Conditional In general, must be present. However in certain circumstances the
element may not occur because the particular circumstance is not
relevant or the information is not available (for example from the
network).
Optional Does not need to be present. Inclusion/exclusion of optional elements
is at the discretion of the Sender PMN, no specific agreements need to
be in place to allow the PMN to include these elements.
Repeating Occurs more than once for a given situation (may also be conditional or
optional).
The rules for conditionality and optionality are given in the data dictionary.
Where items are repeating items this is also documented. Again, fuller descriptions are
given in the data dictionary.
If an item is conditional and does not exist due to conditionality rules then, obviously, those
items below it in the hierarchy cannot exist either, even if denoted as mandatory. However,
if it does exist then any mandatory item directly below it in the hierarchy must also exist.
Note that the notation does not imply any particular “level” of data within the structure by
virtue of its position within the diagram. The only “levels” which exist are the hierarchic
levels denoted by the box which contains the data item name.
V36.4 Page 11 of 317

3.1 Data Interchange
Data
Interchange
o o
Transfer
Notification
Batch
M M
File RAP File Operator

File Type
Sender Recipient Sequence Sequence Specific
Indicator
Number Number Information
M M M C C O R
File File Transfer Cut Specification Release

Creation Available Off Version Version
Timestamp Timestamp Timestamp Number Number
O M M M M
UTC Time UTC Time UTC Time

Offset Offset Offset
M M M
Figure 2: Data Interchange Logical Structure
Group Element Name Also Occurs In Detail Shown In

Data Interchange
Transfer Batch Figure 3
Notification
Table 1: Data Interchange Element Cross References
V36.4 Page 12 of 317

3.2 Transfer Batch
Transfer
Batch
Batch Message Audit

Accounting Network Call Event
Control Description Control
Information Information Details
Information Information Information
M C M C R M R M
Message
Message
Description
Description
Code
M M
Mobile O O SupplementarO O O
Mobile Location
Originated y Service GPRS Call
Session Event Service
Call
M M M M M
AggregatedO Mobile O O Service O O

Messaging Content
Usage Terminated Centre
Event Transaction
Record Call Usage
M M M M M
Figure 3: Transfer Batch Logical Structure

Transfer Batch Figure 2
Batch Control Information Figure 4
Accounting Information Figure 5
Network Information Figure 6
Message Description
Information
Call Event Details
Aggregated Usage Record Figure 2
Mobile Originated Call Figure 8
Mobile Terminated Call Figure 13
Mobile Session Figure 15
Messaging Event Figure 17
Supplementary Service Event Figure 18
Service Centre Usage Figure 20
GPRS Call Figure 21
Content Transaction Figure 24
Location Service Figure 29
Audit Control Information Figure 33
Table 2: Transfer Batch Element Cross References
V36.4 Page 13 of 317

3.3 Batch Control Information
Batch
Control
Information
Specification Release RAP File Operator

File Type
Sender Recipient Version Version Sequence Specific
Number
Indicator
Number Number Information
M M M M C C O R
File
Sequence
Number
M
File Transfer Cut File

Creation Off Available
Timestamp Timestamp Timestamp
O M M

Offset Offset Offset
M M M
Figure 4: Batch Control Information Logical Structure

Batch Control Information Figure 3
Table 3: Batch Control Information Element Cross References
V36.4 Page 14 of 317

3.4 Accounting Information
Accounting
Information
TAP
Taxation Local TAP Currency
Discounting Decimal
Currency Currency Conversion
Places
C R C R M OC C R M
Number Of
Tax Rate Tax Discount Discount Exchange Exchange
Decimal
Code Indicator Code Applied Rate Code Rate
Places
M OC M M M M M
Charge
Tax Type Fixed O O
Type Discount
Discount
Rate
M C Value
M M
Tax Rate
Figure 5: Accounting Information Logical Structure

Accounting Information Figure 3
Taxation
Discounting
Discount Applied
Currency Conversion
Table 4: Accounting Information Element Cross References
V36.4 Page 15 of 317

3.5 Network Information
Network
Information
UTC Time Recording

Offset Entity
Information Information
M R C R
Recording
UTC Time UTC Time Recording Recording
Entity
Offset Code Offset Entity Code Entity Type Identification
M M M M M
Figure 6: Network Information Logical Structure

Network Information Figure 3
UTC Time Offset Information
Recording Entity Information
Table 5: Network Information Element Cross References
V36.4 Page 16 of 317

3.6 Aggregated Usage Record
Aggregated
Usage
Record
Aggregated Aggregated Aggregated RAP File Operator

Serving Aggregation AUR Tax
Usage Date Chargeable Usage Sequence Specific
Network Identifier Information
Start Unit Type Charge Number Information
M C C M C C R C O R
Aggregated Aggregated
Aggregation Exchange
Usage Date Chargeable
Type Rate Code
End Units
C C M C
AUR
Tax Rate AUR Tax
Taxable
Code Value
Amount
M M C
Call Type Call Type Call Type
Level 1 Level 2 Level 3
C C C
Figure 7: Aggregated Usage Record Logical Structure

AUR Tax Information
: Aggregated Usage Record Element Cross References
V36.4 Page 17 of 317

3.7 Mobile Originated call
Mobile
Originated
Call
MO Basic Basic CAMEL Operator

Location Equipment Supplementary Third Party
Call Service Service Code
Service Specific
Information Identifier Information
Information Used Used Information
M M C M C C C O R
O O
Third Party CLIR Status
IMEI ESN
Number Indicator
M M C C
Figure 8: Mobile Originated Call Logical Structure

Mobile Originated Call Figure 3
MO Basic Call Information 0
Location Information Figure 13 Figure 9
Figure 18
Equipment Identifier Figure 13
Figure 18
Figure 21
Basic Service Used Figure 13 Figure 10
Third Party Information
CAMEL Service Used Figure 13 Figure 12
Figure 21
Table 6: Mobile Originated Call Element Cross References
V36.4 Page 18 of 317

3.8 MO Basic Call Information
MO Basic
Call
Information
RAP File Call Event Total Call

Chargeable Destination SIM Toolkit Cause For
Sequence Start Event
Subscriber Network Indicator Termination
Number Timestamp Duration
M C C M M C C
SIM O MIN O
UTC Time
Chargeable Chargeable
Offset Code
Subscriber Subscriber
C C M
Destination
IMSI MIN C
M M
MSISDN MDN SMS

Called Dialled Called Called
Destination
Number Digits Place Region
C C Number
C C C C C
Figure 8: MO Basic Call Information Logical Structure

MO Basic Call Information Figure 8
Chargeable Subscriber Figure 14
Figure 18
Figure 22
Destination
SIM Chargeable Subscriber
MIN Chargeable Subscriber
Table 7: MO Basic Call Information Element Cross References
V36.4 Page 19 of 317

3.9 Location Information
Location
Information
Home Geographical
Network
Location Location
Location
Information
M O C
Home Serving
Recording Call Location Serving
Cell Identity Home BID Location Serving BID Location
Entity Code Reference Area Code Network
Description Description
M C C OC M M C OC OC
Figure 9: Location Information Logical Structure

Location Information Figure 8
Figure 13
Figure 18
Network Location
Home Location Information Figure 21
Geographical Location Figure 21
Figure 15
Figure 17
Table 8: Location Information Element Cross References
V36.4 Page 20 of 317

3.10 Basic Service Used
Basic
Service
Used
Basic Charging Charge HSCSD

Service Timestamp Information Indicator
M C M R C
UTC Time
Offset Code
Fixed User
Service Transparency Guaranteed Maximum
Indicator
Network Protocol
Code Bit Rate Bit Rate
User Rate Indicator
M C C C C C
O Bearer O
TeleService
Service
Code
Code
M M
Figure 10: Basic Service Used Logical Structure

Basic Service Used Figure 8
Figure 13
Basic Service
Service Code Figure 19
Charge Information Figure 19 Figure 11
Figure 20
Figure 23
Figure 27
Figure 32
Table 9: Basic Service Used Element Cross References
V36.4 Page 21 of 317

3.11 Charge Information
Charge
Information
Charged Exchange Call Type Charge Tax Discount

Item Rate Code Group Detail Information Information
M C C M R C R C
Call Type Call Type Call Type Tax Rate Taxable

Tax Value
Level 1 Level 2 Level 3 Code Amount
M M M M M C
Charge
Charge Chargeable Charged Discount Discount Discountable
Charge Detail
Type Units Units Code Value Amount
Timestamp
M M C O C M C C
UTC Time
Offset Code
Figure 11: Charge Information Logical Structure

Charge Information Figure 10
Figure 19
Figure 20
Figure 23
Figure 27
Figure 32
Charge Detail Figure 16
Tax Information Figure 12
Figure 16
Figure 17
Discount Information Figure 12
Call Type Group Figure 16
Figure 17
Table 10: Charge Information Element Cross References
V36.4 Page 22 of 317

3.12 CAMEL Service Used
CAMEL
Service
Used
CAMEL Default Call CAMEL

CAMEL Exchange Tax Discount 3G CAMEL CSE
Service Handling Invocation
Service Key Rate Code Information Information Destination Information
Level Indicator Fee
C M C C C R C C C C
CAMEL O O
GPRS
Destination
Destination
Number
M M
Figure 12: CAMEL Service Used Logical Structure

CAMEL Service Used Figure 8
Figure 13
Figure 21
3G CAMEL Description
GPRS Destination Figure 22
Figure 16
Tax Information Figure 11
Figure 17
Discount Information Figure 11
Table 11: CAMEL Service Used Element Cross References
V36.4 Page 23 of 317

3.13 Mobile Terminated Call
Mobile
Terminated
Call
MT Basic Basic CAMEL Operator

Location Equipment
Call Service Service Specific
Information Identifier
Information Used Used Information
M M C M C O R
Figure 13: Mobile Terminated Call Logical Structure

Mobile Terminated Call Figure 3
MT Basic Call Information Figure 14
Location Information Figure 8 Figure 9
Figure 18
Equipment Information Figure 18 Figure 8
Figure 21
Basic Service Used Figure 8 Figure 10
CAMEL Service Used Figure 8 Figure 12
Figure 21
Table 12: Mobile Terminated Call Element Cross References
V36.4 Page 24 of 317

3.14 MT Basic Call Information
MT Basic
Call
Information
RAP File Call Event Total Call

Chargeable Call Originating SIM Toolkit Cause For
Sequence Start Event
Subscriber Originator Network Indicator Termination
Number Timestamp Duration
M C C C M M C C
UTC Time
Offset
Calling CLIR Status SMS
Number Indicator Originator M
C C C
Figure 14: MT Basic Call Information Logical Structure

MT Basic Call Information Figure 13
Chargeable Subscriber Figure 18 0
Figure 22
Call Originator
Table 13: MT Basic Call Information Element Cross References
V36.4 Page 25 of 317

3.15 Mobile Session
Mobile
Session
Mobile RAP File Operator

Geographical Recording Cause For
Session Sequence Cell Identity Specific
Location Entity Code Termination
Service Number Information
M C C OC M R C O R
Service Total Call Session

Charged SIM Toolkit Location Event
Start Event Charge
Party Indicator Area Code Reference
Timestamp Duration Information
M C C M M M M R
UTC Time
Offset Code
Non-
Requested
Home M Charged
Public User Destination
IMSI Location Party
ID
Description C C
M O O
Non-Charged Non-Charged Requested

Requested
MSISDN Home BID IMEI Party Public User Public User
Number
Number ID ID
C O C C C C C
Figure 15: Mobile Session Logical Structure

Mobile Session Figure 3
Charged Party Figure 17
Figure 17 Figure 9
Geographical Location
Figure 21
Non-Charged Party Figure 17
Requested Destination
Session Charge Information Figure 16
Table 14: Mobile Session Element Cross References
V36.4 Page 26 of 317

3.16 Session Charge Information
Session
Charge
Information
Charged Exchange Call Type Charge Tax

Item Rate Code Group Detail Information
M C M M R C R
Figure 16: Session Charge Information Logical Structure

Session Charge Information Figure 15
Call Type Group Figure 17 Figure 11
Charge Detail Figure 11
Tax Information Figure 12 Figure 11
Table 15: Session Charge Information Element Cross References
V36.4 Page 27 of 317

3.17 Messaging Event
Messaging
Event
Messaging Non- Operator

Location Event Recording Exchange
Event Cell Identity Charged Specific
Area Code Reference Entity Code Rate Code
Service Party Information
M C OC M M R C C O R
Service
Start
RAP File Timestamp
Charged SIM Toolkit Geographical
Sequence M
Party Indicator Location
Number
M C C C
UTC Time
Offset Code
Network Call Type Tax
M Charge
Element Group Information
C R C M C R
Element
Element ID
Type
M M
Figure 17: Messaging Event Logical Structure

Messaging Event Figure 3
Charged Party Figure 15
Figure 15 Figure 9
Geographical Location
Figure 21
Network Element
Non-Charged Party Figure 15
Call Type Group Figure 16 Figure 11
Tax Informatiom Figure 12 Figure 11
Table 16: Messaging Event Element Cross References
V36.4 Page 28 of 317

3.18 Supplementary Service Event
Supplementary
Service Event
RAP File Operator

Chargeable Location Equipment Supplementary
Sequence Service Used
Specific
Subscriber Information Identifier
Number Information
M C M C M O R
Figure 18: Supplementary Service Event Logical Structure

Supplementary Service Event Figure 3
Figure 14 0
Chargeable Subscriber
Figure 22
Figure 8 Figure 9
Location Information
Figure 13
Equipment Identifier Figure 8
Supplementary Service Used Figure 19
Table 17: Supplementary Service Event Element Cross References
V36.4 Page 29 of 317

3.19 Supplementary Service Used
Supplementary
Service Used
Supplementary
Supplementary Charging Charge Service
Service Code
Action Code Service
Parameters Timestamp Information Code
M M C C C C R
UTC Time
Offset Code
Figure 19: Supplementary Service Used Logical Structure

Supplementary Service Used Figure 18
Figure 20
Figure 23
Figure 27
Figure 32
Service Code Figure 10
Table 18: Supplementary Service Used Element Cross References
V36.4 Page 30 of 317

3.20 Service Centre Usage
Service
Centre
Usage
RAP File Serving Charge SCU Charge SCU Operator

Sequence Network Information Type Timestamps Specific
Number Information
C C M M M O R
SCU Basic Recording

Information Entity Code Deposit Completion Charging
Timestamp Timestamp Point
M M
M M M
SCU Charged Non CLIR Status Originating Destination UTC Time UTC Time
Chargeable Party Status Charged Indicator Network Network Offset Code Offset Code
Subscriber Number
M M M C C C M M
GSM O MIN O
Chargeable Priority Code Message

Subscriber Type
M M
M M
IMSI MSISDN MDN Message Distance Message

Status Charge Description
Band Code Code
C C M M C M
Figure 20: Service Centre Usage Logical Structure

Service Centre Usage Figure 3
SCU Basic Information
SCU Chargeable Subscriber
Figure 10 Figure 11
Figure 19
Charge Information Figure 23
Figure 27
Figure 32
SCU Charge Type
SCU Timestamps
Table 19: Service Centre Usage Element Cross References
V36.4 Page 31 of 317

3.21 GPRS Call
GPRS Call
GPRS Basic GPRS Equipment GPRS CAMEL Operator

Call Location Identifier Service Service Used Specific
Information Information Used Information
M M C M C O R
GPRS Home Geographical

Network Location Location
M O C
Recording Location Cell Identity

Entity Code Area Code
M R C OC
Figure 21: GPRS Call Logical Structure

GPRS Call Figure 3
GPRS Basic Call Information Figure 22
GPRS Location Information
GPRS Network Location
Home Location Information Figure 9
Geographical Location Figure 15 Figure 9
Figure 17
Equipment Identifier Figure 13 Figure 8
Figure 18
GPRS Service Used Figure 23
CAMEL Service Used Figure 12
Table 20: GPRS Call Element Cross References
V36.4 Page 32 of 317

3.22 GPRS Basic Call Information
GPRS Basic
Call
Information
GPRS RAP File GPRS Call Event Total Call Partial Type Network Init. Charging Id
Chargeable Sequence Destination Start Event Indicator PDP Context
Subscriber Number Timestamp Duration
M C M M M C C M
UTC Time Cause For PDP Context

Chargeable PDP Network Offset Code Termination Start
Subscriber Address Access Timestamp
Identifier M C OC
C C C
UTC Time
Access Point Access Point Offset Code
Name NI Name OI
M
M C
Figure 22: GPRS Basic Call Information Logical Structure

GPRS Basic Call Information Figure 21
GPRS Chargeable Subscriber
GPRS Destination Figure 12
Chargeable Subscriber Figure 14 0
Figure 18
Table 21: GPRS Basic Call Information Element Cross References
V36.4 Page 33 of 317

3.23 GPRS Service Used
GPRS
Service
Used
IMS Data Volume Data Volume Charge

Signalling Incoming Outgoing Information
Context
C M M M R
Figure 23: GPRS Service Used Logical Structure

GPRS Service Used Figure 21
Figure 19
Figure 20
Figure 27
Figure 32
Table 22: GPRS Service Used Element Cross References
V36.4 Page 34 of 317

3.24 Content Transaction
Content
Transaction
Content Charged Serving Content Operator

Transaction Party Parties Service Specific
Basic Info Information Information Used Information
M M M M R O R
Content Content Internet Network

Provider Provider Service
Name Provider
M C R C R C R
Content Content ISP ISP Network Id Network

Provider Id Provider Id Type Identifier Type Identifier
Type Identifier
M M M M M M
Figure 24: Content Transaction Logical Structure

Content Transaction Figure 3
Content Transaction Basic Figure 25
Information
Charged Party Information Figure 26
Content Service Used Figure 27
Serving Parties Information
Content Provider
Internet Service Provider Figure 29
Network Figure 29
Table 23: Content Transaction Element Cross References
V36.4 Page 35 of 317

3.25 Content Transaction Basic Info
Content
Transaction
Basic Info
RAP File Order Requested Actual Total Transaction

Sequence Placed Delivery Delivery Transaction Status
Number Timestamp Timestamp Timestamp Duration
C C C C C C

Offset Code Offset Code Offset Code
M M M
Figure 25: Content Transaction Basic Info Logical structure

Content Transaction Basic Figure 24
Information
Table 24: Content Transaction Basic Info Element Cross References
V36.4 Page 36 of 317

3.26 Charged Party Information
Charged
Party
Information
Charged Charged Charged Charged

Party Party Home Party Party
Identification Identification Location Equipment
M R C R C R C
Charged Charged Home Id Home Location Location Equipment Equipment

Party Id Party Type Identifier Id Type Identifier Id Type Id
Type Identifier
M M M M M M M M
Figure 26: Charged Party Information Logical Structure

Charged Party Information Figure 24
Charged Party Identification
Charged Party Home
Identification
Charged Party Location
Charged Party Equipment
Table 25: Charged Party Information Element Cross References
V36.4 Page 37 of 317

3.27 Content Service Used
Content
Service
Used
Transaction Transaction Transaction Transaction Transaction

Description Short Detail Identifier Authorisation
Suppression Description Description Code
C M C M C
Data Volume Data Volume Total Data

Incoming Outgoing Volume
C C C
Content Content Object Type Charge Content Charge Advised

Transaction Transaction Refund Charging Information Charge
Code Type Indicator Point Information
M M C C C C R C
Figure 27: Content Service Used Logical Structure

Content Service Used Figure 24
Figure 19
Figure 20
Figure 23
Figure 32
Advised Charge Information Figure 28
Table 26: Content Service Used Element Cross References
V36.4 Page 38 of 317

3.28 Advised Charge Information
Advised
Charge
Information
Paid Payment Advised Advised Commission

Indicator Method Charge Charge
Currency
C OC C M C
Figure 28: Advised Charge Information Logical Structure

Advised Charge Information Figure 27
Table 27: Advised Charge Information Element Cross References
V36.4 Page 39 of 317

3.29 Location Service
Location
Service
Recording Tracking Tracked Operator

Entity Code Customer Customer Specific
Information Information Information
M C C O R
RAP File Call LCS SP Location

Sequence Reference Information Service
Number Usage
C C C M
LCS SP Internet Network

Identification Service
Provider
M R C R C R
Content Content
Provider Id Provider
Type Identifier
M M
Figure 29: Location Service Logical Structure

Location Service Figure 3
Tracking Customer Information Figure 30
Tracked Customer Information Figure 31
Location Service Usage Figure 32
LCS SP Information
LCS SP Identification
Internet Service Provider Figure 24
Network Figure 24
Table 28: Location Service Element Cross References
V36.4 Page 40 of 317

3.30 Tracking Customer Information
Tracking
Customer
Information
Tracking Tracking Tracking Tracking

Customer Customer Customer Customer
Identification Home Id Location Equipment
M R C R C R C
Customer Id Customer Home Id Home Location Location Equipment Equipment

Type Identifier Type Identifier Id Type Identifier Id Type Id
M M M M M M M M
Figure 30: Tracking Customer Information Logical Structure

Tracking Customer Information Figure 29
Tracking Customer
Identification
Tracking Customer Home Id
Tracking Customer Location
Tracking Customer Equipment
Table 29: Tracking Customer Information Element Cross References
V36.4 Page 41 of 317

3.31 Tracked Customer Information
Tracked
Customer
Information
Tracked Tracked Tracked Tracked

Customer Customer Customer Customer
Identification Home Id Location Equipment
M R C R C R C
Customer Id Customer Home Id Home Location Location Equipment Equipment

Type Identifier Type Identifier Id Type Identifier Id Type Id
M M M M M M M M
Figure 31: Tracked Customer Information Logical Structure

Tracked Customer Information Figure 29
Tracked Customer Identification
Tracked Customer Home Id
Tracked Customer Location
Tracked Customer Equipment
Table 30: Tracked Customer Information Element Cross References
V36.4 Page 42 of 317

3.32 Location Service Usage
Location
Service
Usage
LCS QoS LCS QoS Charging Charge

Requested Delivered Timestamp Information
M C C M R
UTC Time
Offset Code
LCS Vertical Tracking
Request Accuracy Period M
Timestamp Requested
M C C
UTC Time Horizontal Response Tracking

Offset Code Accuracy Time Frequency LCS Tracking Tracking Age Of
Requested Category Transaction Frequency Period Location
M C C C Status
C C C C
Horizontal Vertical Positioning Response

Accuracy Accuracy Method Time
Delivered Delivered
C C C C
Figure 32: Location Service Usage Logical Structure

Location Service Usage Figure 29
Figure 19
Figure 20
Figure 23
Figure 27
LCS QoS Requested
LCS QoS Delivered
Table 31: Location Service Usage Element Cross References
V36.4 Page 43 of 317

3.33 Audit Control Information
Audit Control
Information
Earliest Call Total Charge Total Charge Total Total Call Event Operator
Timestamp Refund Discount Discount Details Specific
Value Refund Count Information
O M C M C M O R
UTC Time
Offset Total Tax Total Tax Total Advised
Refund Value Charge Value
M
C M C R
Latest Call
Timestamp
Advised Total Total Advised Total Total
Charge Advised Charge Commission Commission
O Refund
Currency Charge Refund
C M C C C
UTC Time
Offset
Figure 33: Audit Control Information Logical Structure

Audit Control Information Figure 3
Total Advised Charge Value
Table 32: Audit Control Information Element Cross References
V36.4 Page 44 of 317

GSM Association Confidential
Official Document TD.57
4 Data Dictionary
The data dictionary gives a full listing of all data items within the Transferred Account Procedure (TAP).
In addition to providing descriptions, derivations and values where appropriate for all groups and items, it describes conditionality and validation
in detail.
The following table explains how to interpret the information in the data dictionary:
Element Description Error Code Context Severity Level Validation Description

This column This column contains a description of the meaning of the Data This column This column This column This column contains the
contains the Element. It instructs the TAP Sender how to create and contains the contains an contains the exact description of each
name of the populate TAP, but does not provide any instructions to the TAP error codes abbreviation severity level error, and provides the
Data Recipient. that must be of the call applicable to maximum validation that
Element or used for the event types each error. If can be applied by the TAP
Group The Derivation section explains how the value of the Data errors raised. for which the the error is Recipient.
Element is derived. In most cases this contains references to specific error raised, it must
3GPP standards documents. Additional can be follow the error Except for the specific
error codes raised. severity. errors listed in section 5,
The Conditionality section explains if the element is mandatory, can only be other errors not listed in
conditional (mandatory under certain conditions that are listed used by The this column can only be
here) or optional. bilateral abbreviations raised by bilateral
agreement. within the agreement.
Note: Mandatory item missing errors cannot be raised due to
‘Context’
information in this section, but only be raised if there is an
column are
explicit error defined in the Validation Description column.
detailed in
the Error!
The Value or Range sections explain the list of valid values or Reference
ranges, for those Data Elements where a list of values or source not
ranges is applicable. Where there is an explicit list of values or found. at the
ranges, then those values or ranges are used for the value out end of the
of range error, unless the Validation Description column
V36.4 Page 45 of 317

Element Description Error Code Context Severity Level Validation Description

specifies additional value criteria. dictionary.
Note: Value out of range errors cannot be raised due to
information in this section, but only be raised if there is an
explicit error defined in the Validation Description column.
The Format section explains the valid format in case it is not

easily explained by the Value or Range sections.
Table 33: Explanations of the Data Dictionary Columns
4.1 A
Element Description Error Context Severity Validation Description
Code Level
3G CAMEL A group identifying the destination as returned by the CAMEL
Destination server. It may consist either of CAMEL Destination Number or
GPRS Destination depending on service used.
Conditionality:
Must be present within group CAMEL Service Used where
the destination has been modified by the CAMEL server.
Note: The “3G CAMEL Destination” name has been historically

inherited in TD.57 from the wireless standards upon the
introduction of “GPRS relevant to CAMEL usage” as it has
represented part of the 3G developments. In TAP, CS & PS
CAMEL Information generated from both 2G & 3G networks
are valid to be populated below the “3G CAMEL Destination”
Group.
Access Point The Network Identifier part of the Access Point Name (APN) in 10 GPRS Severe Syntax error where group GPRS
Name NI dot notation. Destination occurs within group GPRS
Basic Call Information.
Derivation:
V36.4 Page 46 of 317


Code Level
In the case of GPRS usage without CAMEL invocation: 11 GPRS Severe Syntax error where group GPRS
The actual connected APN NI as defined in PS Domain Destination occurs within group 3G
Charging – see Annex C. Pre GSM Release ’98 from the CAMEL Destination.
GSM item AccessPointName (see conditionality note
below). 200 GPRS Severe Until 30 April 2015: APN NI is
EUInternet and data session is not
In case of GPRS usage with CAMEL invocation: home routed.
Within GPRS Basic Call Information, the actual connected From 01 May 2015: EU (or EEA)
APN NI as modified by the CSE in APN NI field as defined VPMN where local breakout (LBO) is
in PS Domain Charging – see Annex C. made available as per EU Roaming
Within 3G CAMEL Destination, the original APN NI before Regulation III and APN NI is
modification by the CSE in CAMEL APN NI field available EUInternet.
within CAMEL Information as defined in PS Domain Note (applies both before and after 01
Charging – see Annex C. May 2015): When, within the same call
record, there is an APN NI within
In the case of Wi-Fi usage this element must contain the CAMEL Service Used then this error
Venue Class where available, otherwise defaults to 0 can only be raised on that APN NI and
(zero). not on the APN NI within GPRS Basic
Call Information.
Conditionality:
Mandatory within group GPRS Destination.
Networks which have not yet upgraded to at least GSM

Release ’98 do not yet support the separation of the APN
into the Network Identifier and Operator Identifier parts and,
therefore, must populate a concatenation of both parts
within this item.
Values:
This field is encoded as a string comprising of up to 63
characters.
The actual contents are for further study.
Access Point The Operator Identifier part of the Access Point Name (APN) in 10 GPRS Severe Syntax error where group GPRS
Name OI dot notation. Destination occurs within group GPRS
V36.4 Page 47 of 317


Code Level
Basic Call Information.
Derivation:
In the case of GPRS usage without CAMEL invocation: 11 GPRS Warning Syntax error where group GPRS
The actual connected APN OI as defined in PS Domain Destination occurs within group 3G
Charging – see Annex C. CAMEL Destination.
Pre GSM Release ’98 from the GSM item
AccessPointName (see conditionality note below).
From GSM Release ’98 to 3GPP Release 7 from the GSM
item AccessPointNameOI (see conditionality note below).
From 3GPP Release 8 from the GSM item P-GW PLMN
Identifier (see conditionality note below).
In the case of GPRS usage with CAMEL invocation:
Within GPRS Basic Call Information, the actual connected
APN OI as modified by CSE in APN OI field as defined in
PS Domain Charging – see Annex C.
Within 3G CAMEL Destination, the original APN OI field
available within CAMEL Information as defined in PS
Domain Charging – see Annex C.
Conditionality:
Mandatory within group GPRS Destination where the
GPRS Call represents an SGSN or S-GW ticket or an
assembled SGSN/GGSN or S-GW/P-GW ticket.
This item is only available within networks which have
upgraded to at least GSM Release ’98 and not available for
Wi-Fi usage.
Values:
This field is encoded as a string comprising of up to 37
characters.
The actual contents are for further study.
Accounting A grouping of accounting related information. 30 Tf Batch Fatal No Taxation group present and batch
Information The group must contain a Local Currency and Currency contains taxes.
Conversion table. The group may conditionally include
V36.4 Page 48 of 317


Code Level
Taxation and Discounting tables and, optionally, TAP 31 Tf Batch Fatal No Discounting group present and
Currency. batch contains discounts.
Conditionality: 32 Tf Batch Fatal Mandatory item Local Currency

Must be present within group Transfer Batch where any missing within group.
Call Event Details contains a charge.
33 Tf Batch Fatal Item TAP Currency not present and
currency other than SDR specified in
roaming agreement.
34 Tf Batch Fatal Group Currency Conversion missing

within group and the transfer includes
one or more Charge greater than zero.
35 Tf Batch Fatal Mandatory item TAP Decimal Places

missing within group.
Action Code The Action Code qualifies the way in which the supplementary 10 SS Severe Syntax error.
service is used.
20 SS Severe Value out of range for supplementary
Derivation for Supplementary Services: service where associated
GSM item SS ActionType (See Annex C – CS Domain Supplementary Service Code is for a
Charging). supplementary service.
Conditionality: 22 SS Severe Value out of range for USSD message

Mandatory within group Supplementary Service Used. where associated Supplementary
Service Code is for USSD message.
Values:
0 Registration SS only Note: Error Codes 11 & 21 removed in
1 Erasure SS only TAP release 3.11 (01 May 2005).
2 Activation SS only
3 Deactivation SS only
4 Interrogation SS only
5 Invocation SS only
6 Registration of Password SS only
V36.4 Page 49 of 317


Code Level
7 USSD Invocation USSD only
Actual Delivery The timestamp representing the actual time at which the start 10 Content Severe Syntax error and timestamp referenced
Timestamp of the Content Transaction was commenced. This is given in as Charging Point.
the time of the serving Content Provider. There must be a UTC
Time Offset Code associated with the item. 11 Content Warning Syntax error and timestamp not
referenced as Charging Point.
Example:
The Charged Party may request to download all messages 20 Content Severe Value out of range and timestamp
at 2200hrs in order to take advantage of off-peak rates referenced as Charging Point.
while placing the order at an earlier time but the actual
content download may have commenced at 0030hrs. 21 Content Warning Value out of range and timestamp not
Conditionality:
Must be present within group 30 Content Severe Mandatory associated UTC Time
 Content Transaction Basic Info Offset Code missing and timestamp
when no other timestamp present within group or when referenced as Charging Point.
item referenced as the Charging Point.
31 Content Warning Mandatory associated UTC Time
Format: Offset Code missing and timestamp not
CCYYMMDDHHMMSS referenced as Charging Point.
Note: Within this timestamp the range for HHMMSS is 000000 100 Content Severe Actual Delivery Timestamp after
to 235959 associated Charge Detail timestamp
and timestamp referenced as Charging
Point.
101 Content Warning Actual Delivery Timestamp after

associated Charge Detail timestamp
and timestamp not referenced as
Charging Point.
200 Content Severe Actual Delivery Timestamp before the

commercial roaming start date (in
VPMN local time if no other time zone
V36.4 Page 50 of 317


Code Level
explicitly agreed) for the specific
service and the TAP file is not a test file
and the timestamp is referenced as the
Charging Point.
Advised The charge advised to the Charged Party. 10 Content Severe Syntax error.
Charge
The charge must not contain a negative value. Note that where 20 Content Severe Value out of range.
there is an associated Charge Refund Indicator present then
this is an implicit negative value.
The charge should always match the complete amount quoted

to the customer. Where the amount ‘advised’ (quoted) to the
customer included taxes then this charge should include taxes,
otherwise, there should be no taxes included.
The charge is in the Advised Charge Currency, or TAP

Currency where no associated Advised Charge Currency is
present, or SDRs where neither is present.
The number of decimal places is defined by item TAP Decimal

Places.
Conditionality:
Mandatory within group Advised Charge Information.
Values:
>=0
Advised The currency in which the Charged Party has been advised of 10 Audit Fatal Syntax error.
Charge the charge. The Advised Charge Currency contains the
Currency Currency Code, which identifies the currency used for Advised 11 Content Severe Syntax error.
Charge.
20 Audit Fatal Value out of range.
Note that this item will not be present if using the TAP file
currency. The standard TAP file currency default is SDRs 21 Content Severe Value out of range.
V36.4 Page 51 of 317


Code Level
unless bilaterally agreed otherwise or a specific currency
default for the file can be defined by item TAP Currency (use of
TAP Currency will be by bilateral agreement between
partners).
Derivation:
ISO 4217 [26].
Conditionality:
Present within groups
 Advised Charge Information
 Total Advised Charge Value
when different to TAP Currency and not SDRs.
Example:
Currency Code Currency name
EUR Euro
INR Indian rupee
XDR SDR
USD U.S. dollar
Advised The currency in which the Charged Party has been advised of 10 Audit Fatal Syntax error.
Charge the charge. The Advised Charge Currency contains the
Currency Currency Code, which identifies the currency used for Advised 11 Content Severe Syntax error.
Charge.
20 Audit Fatal Value out of range.
Note that this item will not be present if using the TAP file
currency. The standard TAP file currency default is SDRs 21 Content Severe Value out of range.
unless bilaterally agreed otherwise or a specific currency
default for the file can be defined by item TAP Currency (use of
TAP Currency will be by bilateral agreement between
partners).
Derivation:
ISO 4217 Currency Codes standard.
V36.4 Page 52 of 317


Code Level
Conditionality:
 Advised Charge Information
 Total Advised Charge Value
when different to TAP Currency and not SDRs.
Example:
EUR Euro
INR Indian rupee
XDR SDR
USD U.S. dollar
Advised Where a customer has been advised of a charge then the 30 Content Severe Mandatory item Advised Charge not
Charge Advised Charge Information group identifies the actual charge present within group.
Information and may, conditionally, provide additional information.
The group must contain Advised Charge, all other information

is conditional. Conditional information present may include
Paid Indicator, Payment Method (optionally), Advised Charge
Currency and Commission.
Conditionality:
Must be present within group Content Service Used when
charge has been advised to the customer.
Age of This value represents the elapsed time in minutes since the 20 LCS Severe Value out of range.
Location last network contact of the mobile station (i.e. the actuality of
the location information).
Derivation:
GSM/UMTS item AgeOfLocationInformation (See Annex C
– LCS Charging).
Conditionality:
V36.4 Page 53 of 317


Code Level
Must be present within group LCS QoS Delivered where
available from the network and LCS transaction status
indicates ‘last known location’.
Values:
This field is coded as an integer within the range 0- 32767.
The value 0 indicates that the MS is currently in contact
with the network, whereas the value 32767 indicates that
the location information is at least 32767 minutes old.
Aggregated Aggregated Chargeable Unit Type indicates the type of units 10 AUR Severe Syntax error.
Chargeable being aggregated within this occurrence of Aggregated Usage
Unit Type Record. 20 AUR Severe Value out of range.
Note that any aggregation of data volumes must be based on
the network CDRs which are providing bytes before converting
to any other data volume based Unit Type such as MB or GB.
Note also that when converting bytes to other Unit Types the
conversion must be based on 1024 bytes to KB, 1024 KB to
MB, 1024 MB to GB.
Conditionality:
Mandatory within group Aggregated Usage Record.
Values:
1 bytes
2 KB
3 MB
4 GB
5 MO seconds
6 MT seconds
7 MO & MT seconds combined
8 Number of MO SMS events
9 Number of inbound roamers
10 MSUs
Aggregated The Aggregated Chargeable Units item indicates the number 10 AUR Severe Syntax error.
V36.4 Page 54 of 317


Code Level
Chargeable of units which are chargeable within the Aggregated Usage
Units Record. 20 AUR Severe Value out of range.
The item Chargeable Unit Type defines what the units

represent.
Conditionality:
Must be present within group Aggregated Usage Record.
Values:
>0
Aggregated The invoiceable charge for the Aggregated Usage Record 10 AUR Severe Syntax error.
Usage Charge before any tax is added (if applicable, see AUR Tax
Information). 20 AUR Severe Value out of range.
The Aggregated Usage Charge must not contain a negative 200 AUR Severe Aggregated Usage Charge not in line
value. with roaming agreement. Charge
validation must be done according to
The charge is in SDRs with the number of decimal places section 5.9.
defined by item TAP Decimal Places. Note; the currency may
be subject to internal market bilateral agreements, see TAP Notes for validation rule 200:
Currency. Rounding rules are at the discretion of
the Sender, therefore, when verifying
Conditionality: the charge applied by the Sender the
Must be present within group Aggregated Usage Record when Recipient must allow for a tolerance of
greater than 0 (zero). 0.02 units of TAP Currency
(independently of the number of TAP
Values: Decimal Places used for the TAP file).
> or = 0 (zero) No tolerance is allowed when the
expected Charge is zero.
Aggregated The Aggregated Usage Date End represents the end of the 10 AUR Severe Syntax error.
Usage Date period of the usage being aggregated.
End 20 AUR Severe Value out of range.
Note that use of period based aggregation must be bilaterally
V36.4 Page 55 of 317


Code Level
agreed. 200 AUR Severe Item contains date earlier than
Aggregated Usage Date Start.
Conditionality:
Must be present within group Aggregated Usage Record where 201 AUR Severe Item contains date greater than
the aggregation occurred over a period greater than one day Aggregated Usage Date Start and
and when period based aggregation bilaterally agreed. May be period based aggregation not
present within group Aggregated Usage Record where the bilaterally agreed.
date is the same as Aggregated Usage Date Start.
Format:
CCYYMMDD
Aggregated Where there is no Aggregated Usage Date End present then 10 AUR Severe Syntax error.
Usage Date the Aggregated Usage Date Start represents the date of the
Start usage being aggregated. 20 AUR Severe Value out of range.
Where there is an Aggregated Usage Date End present then

the Aggregated Usage Date Start represents the start of the
period of the usage being aggregated.
Note that use of period based aggregation must be bilaterally

agreed.
Conditionality:
Must be present within group Aggregated Usage Record
Format:
CCYYMMDD
Aggregated The Aggregated Usage Record represents usage of a unit type 30 AUR Severe Mandatory item Aggregated Usage
Usage Record (Aggregated Chargeable Unit Type) which can be further Date Start missing within group.
segmented by a specified type of aggregation (defined in the
Aggregation Type) 31 AUR Severe Item Call Type Level 1 missing within
group and Aggregated Usage Charge
Use of the Aggregated Usage Record is only allowed when is greater than 0 (zero).
bilaterally agreed.
V36.4 Page 56 of 317


Code Level
32 AUR Severe Mandatory item Call Type Level 2
The AUR can only contain usage which has not been missing within group and Aggregated
previously included in TAP, including previous AUR records or Usage Charge is greater than 0 (zero).
detail TAP records, and where the network CDRs being
aggregated do not end after the Transfer Cut Off Timestamp. 35 AUR Severe Mandatory item Call Type Level 3
Where there are multiple time zones in the network the missing within group and Aggregated
timestamps will need to be normalised to account for the Usage Charge is greater than 0 (zero).
different UTC time offsets applicable.
The network CDR start or partial record start timestamp date 36 AUR Severe Mandatory item Aggregated
defines the applicable aggregation date. Chargeable Unit Type missing within
Note that the only exception allowing resubmission of usage is group.
where the AUR was previously rejected using RAP and is
being resubmitted. Note also that a detail TAP record that was 37 AUR Severe Mandatory item Aggregated
rejected using RAP can only be resubmitted as a detail TAP Chargeable Units missing within group.
record, the usage cannot be resubmitted as part of an AUR.
Mandatory elements are Aggregated Usage Date Start, 38 AUR Severe Item Aggregated Usage Charge not
Aggregated Chargeable Unit Type and Aggregated present and expected charge is greater
Chargeable Units. than zero.
Where the record represents aggregated usage over a period 39 AUR Severe Item Exchange Rate Code missing and
then the Aggregated Usage Date End must be present. Note Aggregated Usage Charge is greater
that a period so identified cannot contain an IOT change for the than zero.
aggregated usage. Every period must have a single rate
applicable in the IOT across the complete period. 40 AUR Severe Item Aggregation Identifier present
when item Aggregation Type not
Aggregated Usage Charge and Exchange Rate Code must be present.
present when the charge is greater than zero but may be
omitted when equal to zero.
When the Aggregated Usage Charge is greater than zero Call

Type Level 1, 2 and 3 must be present. When the aggregated
usage relates to usage that will only be rated at a later time, for
example invoice production, the Call Type Level 1/2/3 may be
required to identify the rate applicable.
V36.4 Page 57 of 317


Code Level
AUR Tax Information must be present when taxes apply and
when those taxes are greater than zero. This group is
repeated for each tax applicable.
Operator Specific Information may also be present, this is

optional dependent on bilateral agreement.
Conditionality:
Mandatory within an occurrence of group Call Event Details
where none of the following are present; Mobile Originated
Call, Mobile Terminated Call, Supplementary Service Event,
Service Centre Usage, GPRS Call, Content Transaction or
Location Service.
Aggregation Where aggregation is based on one of the allowed types within 10 AUR Severe Syntax error.
Identifier the Aggregated Chargeable Unit Type and applicable rate
(identified by Call Type Level 1/2/3 values) this identifies the 200 AUR Severe The associated Aggregation Type is
item used for such aggregation. IMSI (value 1) and Aggregation
Identifier does not contain an IMSI
Note that if Aggregation Type indicates IMSI Range then the which the Recipient is financially liable
Aggregation Identifier will have from and to IMSIS separated for as defined in the wholesale
by: character. (roaming) agreement between the
Example 1: 801550000000000:801550999999999 Sender and Recipient.
Example 2: 801550100000000:801550109999999
Note that the numbers in the range are inclusive and will have 201 AUR Severe The associated Aggregation Type is
the lower number first followed by: and then the higher IMSI Range (value 5) and Aggregation
number. Identifier does not contain an IMSI
range which the Recipient is financially
Conditionality: liable for as defined in the wholesale
Mandatory within group Aggregated Usage Record when (roaming) agreement between the
Aggregation Type is also present. Sender and Recipient.
Values: 202 AUR Severe Where the Aggregation Identifier

Values are defined by the Aggregation Type used. relates to an IMSI Range, the first
number is higher than the second
V36.4 Page 58 of 317


Code Level
number in the IMSI Range.
Aggregation Where aggregation is based on one of the allowed types within 10 AUR Severe Syntax error.
Type the Aggregated Chargeable Unit Type and applicable rate
(identified by Call Type Level 1/2/3 values) this identifies the 20 AUR Severe Value out of range.
type used for such aggregation.
Conditionality:
Present within group Aggregated Usage Record when the
aggregation is based on one of the defined Aggregation Types.
Values:
1 IMSI
2 APN
3 Rating Group
4 CAMEL Service Key
5 IMSI Range
AUR Tax A repeating group containing the Tax Rate Code and the AUR 30 AUR Severe Mandatory item Tax Rate Code
Information Tax Value and, where applicable AUR Taxable Amount. missing within group.
AUR Tax Information will be present when taxes apply and 31 AUR Severe Mandatory item AUR Tax Value
when those taxes are greater than zero. missing within group.
Aggregated Usage Charge may have several tax elements

associated with it, for example national tax, regional tax, local
tax. This group is repeated for each tax applicable.
Conditionality:
There must be one occurrence within Aggregated Usage
Record for each tax element associated with the Aggregated
Usage Charge where the taxes are greater than zero.
AUR Tax Value The actual value of the tax associated with the Tax Code and 10 AUR Severe Syntax error.
Aggregated Usage Charge.
20 AUR Severe Value out of range.
The AUR Tax Value must be greater than or equal to zero.
V36.4 Page 59 of 317


Code Level
22 AUR Severe Where the associated Tax Rate Code
The value is in SDRs with the number of decimal places relates to a Tax Rate, the AUR Tax
defined by item TAP Decimal Places. Note the currency may Value does not correspond to the AUR
be subject to internal market bilateral agreements, see TAP Taxable Amount (or, where no AUR
Currency. Taxable Amount is present, does not
correspond to the Aggregated Usage
Conditionality: Charge, and Tax Rate).
Must be present within group AUR Tax Information when Note 1: Rounding rules are at the
Aggregated Usage Charge is greater than zero and Tax Rate discretion of the Sender and a
Code is present. tolerance of 0.02 units of TAP Currency
must be allowed (independent of the
Values: number of decimal places used for the
>= 0 (zero) TAP file).
Note 2: No tolerance is allowed when
the expected AUR Tax Value is zero.
Note 3: In the absence of AUR Taxable
Amount the AUR Tax Value must
always be validated against the total
Aggregated Usage Charge. Any
Charge Type associated with the Tax
Code in Taxation must be ignored.
200 AUR Severe AUR Tax Value is not in line with the
roaming agreement at the
corresponding Aggregated Usage Date
Start.
Note that, where variable tax rates
apply the exact validation of the tax
rate may not be possible and,
therefore, cannot be carried out.
Note 1: Rounding rules are at the
discretion of the Sender and a
tolerance of 0.02 units of TAP Currency
must be allowed, independent of the
number of decimal places used for the
V36.4 Page 60 of 317


Code Level
TAP file.
the expected AUR Tax Value is zero.
AUR Taxable The actual part of the Aggregated Usage Charge to which the 10 Calls Severe Syntax error.
Amount AUR Tax Value and Tax Rate (Code) relate. Note that some
tax authorities allow for tax on tax. 20 Calls Severe Value out of range.
The AUR Taxable Amount must be greater than zero. 100 Calls Severe AUR Taxable Amount not in line with
roaming agreement.
The value is in SDRs with the number of decimal places
defined by TAP Decimal Places. Note that the currency may be
subject to internal market bilateral agreements, see TAP
Currency.
Conditionality:
Must be present within group AUR Tax Information when
Aggregated Usage Charge is greater than zero and Tax Rate
Code is present.
Values:
> 0 (zero)
Audit Control The group identifies the end of the Transfer Batch. 30 Tf Batch Fatal Mandatory item Total Charge missing
Information within group.
The following items are optional; Earliest Call Timestamp,
Latest Call Timestamp and Operator Specific Information. 31 Tf Batch Fatal Mandatory item Total Tax Value
Total Charge, Total Tax Value, Total Discount Value and Call
Event Details Count are all mandatory. 32 Tf Batch Fatal Mandatory item Total Discount Value
Conditionally present are Total Charge Refund, Total Advised
Charge Value, Total Tax Refund and Total Discount Refund. 33 Tf Batch Fatal Mandatory item Call Event Details
Count missing within group.
Conditionality:
Mandatory within group Transfer Batch. 36 Tf Batch Fatal Item Total Tax Refund present and use
V36.4 Page 61 of 317


Code Level
of Content Transaction not bilaterally
agreed.
Also see error code 50 (section 5.3).
37 Tf Batch Fatal Item Total Discount Refund present

and use of Content Transaction not
bilaterally agreed.
38 Tf Batch Fatal Group Total Advised Charge Value

present and use of Content
Transaction not bilaterally agreed.
39 Tf Batch Fatal Conditional group Total Advised

Charge Value missing within group and
one or more occurrences of Content
Transaction present containing
Advised Charge Information.
40 Tf Batch Fatal Item Total Charge Refund expected

with value greater than 0 and not
present.
Note: Error Codes 34 & 35 removed in

TAP release 3.11 (01 May 2005).
4.2 B
Code Level
Basic Service The group Basic Service identifies the actual Basic Service 30 MOC Severe Mandatory group Service Code missing
used. MTC within group.
V36.4 Page 62 of 317


Code Level
It must contain the Service Code, it will, conditionally also Note: Error Codes 31, 32, 33, 34, 35
contain the following for UMTS: Transparency Indicator, Fixed and 36 removed in TAP release 3.11
Network User Rate, User Protocol Indicator, Guaranteed Bit (01 May 2005).
Rate and Maximum Bit Rate.
Conditionality:
Mandatory within group Basic Service Used.
Basic Service A group of data identifying the type of service used together 30 MOC Severe Mandatory group Basic Service
Used with all related charging information. MTC missing within group.
The group must have Basic Service and Charge Information 32 MOC Severe Mandatory group Charge Information
present. Charging Timestamp item will be present as MTC missing within group.
applicable and HSCSD Indicator will be present where HSCSD
has been used.
Conditionality:
Mandatory within groups
Mobile Originated Call
Mobile Terminated Call
one must be present.
Batch Control All items are mandatory except File Type Indicator which will 30 Tf Batch Fatal Mandatory item Sender missing within
Information only be present where the file represents test data, RAP File group.
Sequence Number (used where the batch has previously been
returned with a fatal error and is now being resubmitted) and 31 Tf Batch Fatal Mandatory item Recipient missing
Operator Specific Information and File Creation Timestamp within group.
which are optional.
32 Tf Batch Fatal Mandatory item File Sequence Number
Conditionality: missing within group.
Mandatory within group Transfer Batch.
33 Tf Batch Fatal Mandatory item File Available
Timestamp missing within group.
34 Tf Batch Fatal Mandatory item Specification Version

Number missing within group.
V36.4 Page 63 of 317


Code Level
36 Tf Batch Fatal Mandatory item Transfer Cut Off

37 Tf Batch Warning File Sequence Number previously

received and rejected with fatal error,
therefore RAP File Sequence Number
expected but not present.
38 Tf Batch Fatal File Type Indicator present within group

and Transfer Batch expected as
chargeable data (that is, live data).
39 Tf Batch Fatal File Type Indicator not present within

group and Transfer Batch expected as
test data (i.e. non chargeable data).
40 Tf Batch Warning RAP File Sequence Number present

although File Sequence Number has
not previously been rejected with a
fatal error (for example previously
missing or new files).
41 TfBatch Fatal Mandatory item Release Version

Note: Error Code 35 removed in TAP

release 3.11 (01 May 2005).
Bearer Service A code which uniquely defines a Bearer Service. 10 MOC Severe Syntax error.
Code MTC
Group Bearer Codes, identifiable by the description ‘All’,
should only be used where details of the specific services 11 SS Warning Syntax error.
affected are not available from the network.
20 MOC Severe Value out of range.
V36.4 Page 64 of 317


Code Level
Note that compound Bearer Service group codes can only MTC
occur in conjunction with HSCSD usage or call independent
supplementary service operations. 21 SS Warning Value out of range.
Note that codes 27 & 37 (General Data A/Synchronous

Service) are used where a data rate greater than 9600bps is
used, the data rate used is not identifiable/specified on the
network CDRs.
Derivation:
GSM item BearerServiceCode (See Annex C – CS Domain
Charging).
The code is derived by taking the MAP encoding as

specified for BearerServiceCode (See Annex C – CS
Domain Charging) and translating bits 7-4 into a ‘hex’
character and bits 3-1 into a second ‘hex’ character.
Conditionality:
Must be present within group Service Code where the type
of service used was a bearer service. Must not be present
when the type of service used was a tele service and,
therefore, Teleservice Code is present.
Values:
00 All Bearer Services
20 All Data Circuit Asynchronous Services
21 Duplex Asynch. 300bps data circuit
23 Duplex Asynch. 1200/75bps data circuit
27 General Data Circuit Asynchronous Service
30 All Data Circuit Synchronous Services
V36.4 Page 65 of 317


Code Level
32 Duplex Synch. 1200bps data circuit
37 General Data Circuit Synchronous Service
40 All Dedicated PAD Access Services
41 Duplex Asynch. 300bps PAD access
43 Duplex Asynch. 1200/75bps PAD access
47 General PAD Access Service
50 All Dedicated Packet Access Services
54 Duplex Synch. 2400bps PAD access
57 General Packet Access Service
60 All Alternat Speech/Asynchronous Services
70 All Alternate Speech/Synchronous Services
80 All Speech followed by Data Asynchronous Services
90 All Speech followed by Data Synchronous Services
A0 All Data Circuit Asynchronous Services (compound)
B0 All Data Circuit Synchronous Services (compound)
C0 All Asynchronous Services (compound)
D0 All Synchronous Services (compound)
4.3 C
Code Level
Call Event Call Event Details is a repeating item which is one of 32 Tf Batch Severe Service Centre Usage present
Details Aggregated Usage Record, Mobile Originated Call, Mobile although not agreed bilaterally.
Terminated Call, Mobile Session, Messaging Event,
V36.4 Page 66 of 317


Code Level
Supplementary Service Event, Service Centre Usage, GPRS 34 Tf Batch Severe Content Transaction present although
Call, Content Transaction or Location Service. Each not agreed bilaterally.
occurrence must have no more than one of these present. Also see error code 50 (section 5.3).
Conditionality: 35 Tf Batch Severe GPRS Call representing packet

Mandatory within group Transfer Batch, one occurrence switched data present although no
being present for each call/event present. type of packet switched data service
agreed bilaterally.
Note: Packet switched data in the
context of this validation excludes Wi-
Fi.
36 Tf Batch Severe Location Service present although not

agreed bilaterally.
37 TfBatch Severe Messaging Event present although not

agreed bilaterally.
38 TfBatch Severe Mobile Session present although not

agreed bilaterally.
39 TfBatch Severe GPRS Call representing Wi-Fi usage

present although Wi-Fi not agreed
bilaterally.
See also error code 50 (section 5.4)
40 TfBatch Severe Aggregated Usage Record present

although not bilaterally agreed.
See also error code 50 (section 5.4)
V36.4 Page 67 of 317


Code Level
release 3.11 (01 May 2005).
Call Event This item is an audit control and contains a count of the 10 Audit Fatal Syntax error.
Details Count number of occurrences of Call Event Details within the TAP
transfer. 20 Audit Fatal Value out of range.
Conditionality: 100 Audit Fatal Value does not match the count of Call
Mandatory within group Audit Control Information. Event Details. Note that any rejected
Call Event Details must be included for
Values: the purposes of this validation.
>0
Call Event The timestamp gives the start of the call event. 10 MOC Severe Syntax error.
Start MTC
Timestamp The time is given in the local time of the Sender PMN (or GPRS
Serving Network where this is not the Sender). There must be
a UTC Time Offset Code associated with the timestamp. 20 MOC Severe Value out of range.
MTC
Note that local time is the local time at the location of the GPRS
chargeable subscriber. Where the location is not available, as
in some call forwarding scenarios, this will be a notional 30 MOC Severe Mandatory associated item UTC Time
‘network local time’. MTC Offset Code missing.
GPRS
Note that this timestamp is the event start time as provided by
the network. This will be either the call answer time or the 100 MOC Severe Call event start timestamp after charge
channel seizure time. MTC detail timestamp.
GPRS
If charging is from call answer time then this item can be
populated with either call answer time of channel seizure time. 101 MOC Severe Call event start timestamp after
In the case where Call Event Start Timestamp does not equal MTC charging timestamp.
the point of charging then a Charging Timestamp must be
provided. 200 MOC Severe Call Event Start Timestamp before the
MTC commercial roaming start date (in
If charging is from channel seizure time then Call Event Start GPRS VPMN local time if no other time zone
Timestamp must be populated with channel seizure time. explicitly agreed) for the specific
network service and the TAP file is not
V36.4 Page 68 of 317


Code Level
In the case of an intermediate or last partial record of the same a test file.
GPRS Call (GPRS Context) the timestamp must be populated Note 1: Old call records should not be
with the record start time and not the context start timestamp rejected in principle in Roaming
(see item PDP Context Start Timestamp for identification of Hubbing migration scenarios. See
GPRS context start time in each partial record). BA.62 [16] for further details.
Note 2: In cases where there is a lack
Derivation: of standardised mechanisms for the
GSM item answerTime or seizureTime (See Annex C – CS VPMN to block customers from service
Domain Charging and PS Domain Charging). This will invocation with reasonable efforts the
normally be the equivalent of the start of charging or, where VPMN is still entitled to charge the
the call event is non chargeable, the equivalent point. HPMN for such service invocation and
consequently the records cannot be
For Wi-Fi usage item event-timestamp (RFC 2869) in UTC rejected for being before the
time. commercial roaming start date. An
example of a service that cannot be
Conditionality: rejected for this reason is Circuit
Mandatory within groups Switched Video Telephony.
MO Basic Call Information Examples of such service invocations
MT Basic Call Information that cannot be rejected for this reason
GPRS Basic Call Information are Circuit Switched Video Telephony
and CAMEL information present in the
Format: call events
CCYYMMDDHHMMSS
Note: Within this timestamp the range for HHMMSS is 000000

– 235959
Example:
 PDP Context activated at 20090708235000
 Two partials raised on TAP (cut across midnight)
First partial:
Call Event Start Timestamp = PDP Context Start
Timestamp = 20090708235000
Second partial:
V36.4 Page 69 of 317


Code Level
Call Event Start Timestamp = 20090709000000
PDP Context Start Timestamp = 20090708235000
Call Originator The call originator applies only in respect of mobile terminated Note: Error Codes 30, 31, 32, 33 and
traffic. It identifies the person making the call. For SMS MT 34 removed in TAP release 3.10 (01
usage it identifies the SMSC delivering the SMS and, where May 2003).
available, the originator of the SMS. Note: Error Code 35 removed in TAP
release 3.11 (01 May 2005).
Also, some networks may inhibit the transfer of this information
where CLI presentation is prohibited.
Derivation:
GSM item CallingNumber (See Annex C – CS Domain
Charging). This item is of type AddressString.
Conditionality:
Must be present within group MT Basic Call Information
where the network supports calling line identity (CLI) or if
TeleService Code indicates SMS usage (values 20 or 21)
and available from the network.
Call Reference An identifier local to the Recording Entity. The identifier 10 MOC Severe Syntax error.
distinguishes between transactions on the same mobile MTC
station. SS
LCS
Derivation:
GSM item CallReference (See Annex C – CS Domain
Charging).
GSM item Message Reference (see Annex C – CS Domian

Charging) for SMS over circuit switched.
GSM item Message Reference (See Annex C – PS Domain

Charging) for SMS over GPRS
For LCS, item Local Record Sequence Number (See
V36.4 Page 70 of 317


Code Level
Annex C – LCS Charging).
Conditionality:
Must be present within groups
Network Location
Location Service
when available from the network.
Call Type A group identifying the IOT used by the VPMN to price the call. 30 MOC Severe Mandatory item Call Type Level 1
Group MTC missing within group.
The group contains mandatory items Call Type Level 1, Call GPRS
Type Level 2 and Call Type Level 3. MSESS
MSG
Conditionality:
Must be present within group Charge Information where 31 MOC Severe Mandatory item Call Type Level 2
Charge Information occurs within a Mobile Originated Call, MTC missing within group.
or a Mobile Terminated Call, or a GPRS Call. GPRS
MSESS
Must be present within the following groups: MSG
Session Charge Information
Messaging Event 32 MOC Severe Mandatory item Call Type Level 3
MTC missing within group.
GPRS
MSESS
MSG

release 3.11 (01 May 2005).
Call Type The highest category call type in respect of the destination or 10 MOC Severe Syntax error.
Level 1 origination of the call. MTC
GPRS
Conditionality: MSESS
Mandatory within group Call Type Group. MSG
Must be present within Aggregated Usage Record when AUR
the Aggregated Usage Charge is greater than 0 (zero).
V36.4 Page 71 of 317


Code Level
Values: MTC
0 Unknown/Not Applicable GPRS
1 National MSESS
2 International MSG
10 HGGSN/HP-GW AUR
11 VGGSN/VP-GW
12 Other GGSN/Other P-GW Note: Error Codes 100 & 101
100 Wi-Fi removed in TAP release 3.09 (01 May
2002).
Notes:
Value 0 is for use only in the following cases: Note: Error Code 102 removed in
 Mobile Terminated Calls TAP release 3.12 (01 May 2012).
 Mobile Sessions where Mobile Session Service is “MT
Voice over LTE”
 Mobile Sessions where Mobile Session Service is
“MO Voice over LTE” and the group Non Charged
Party contains only a Public User ID
 Aggregated Usage Records
Values 1 & 2 are for use only in the following cases:

 Mobile Originated Calls,
 Mobile Terminated Calls,
 Mobile Sessions
 Messaging Events
 Aggregated Usage Record
Values 10, 11 & 12 are for use in GPRS Calls and Aggregated
Usage Records only.
Value 100 is for use in GPRS Calls and Aggregated Usage
Records representing Wi-Fi usage only
Unknown/Not Applicable can be used when the VPMN cannot
V36.4 Page 72 of 317


Code Level
interpret the origin or does not differentiate charging based on
any other of the Call Type Level 1 values.
Call Type An item which identifies the sub category of Call Type Level 1. 10 MOC Severe Syntax error.
Level 2 MTC
This defines, in more detail, the classification of the call within GPRS
the IOT, as used by the VPMN to price the call. MSESS
MSG
Conditionality: AUR
Mandatory within group Call Type Group.
Must be present within Aggregated Usage Record when the
MTC
Aggregated Usage Charge is greater than 0 (zero).
GPRS
Values:
MSESS
0 Unknown/Not Applicable
MSG
1 Mobile
AUR
2 PSTN
Note: Error Code 100 removed in
3 Non Geographic
4 Premium Rate
5 Satellite destination
6 Forwarded call
7 Non forwarded call
10 QoS Broadband
11 QoS Narrowband
12 QoS Conversational
13 QoS Streaming
14 QoS Interactive
15 QoS Background
20 Unspecified/default LTE QCIs
21 LTE QCI 1 Conversational
24 LTE QCI 4 Streaming
25 LTE QCI 5 Interactive
(specialised for signalling)
V36.4 Page 73 of 317


Code Level
29 LTE QCI 9 Background
65 LTE QCI 65
66 LTE QCI 66
69 LTE QCI 69
70 LTE QCI 70
Notes:
Value 0 (zero) is for use in the following cases (regardless of
what has been defined in the IOT):
 Mobile Originated Calls
 Mobile Terminated Calls
 Mobile Sessions
 Messaging Events
 GPRS Calls
Values 1,2,3,4 & 5 are for use only in the following cases:
 Mobile Originated Calls
 Mobile Sessions where Mobile Session Service is
“MO Voice over LTE” or Emergency Call
Value 6 is for use in Mobile Terminated Calls and Aggregated
Usage Records only.
Value 7 is for use in Mobile Terminated Calls, Aggregated
Usage Records and Mobile Sessions where Mobile Session
Service is “MT Voice over LTE” only.
Values 10-15 and 20-29, 65, 66, 69 and 70 are for use in
GPRS Calls and Aggregated Usage Records only.
Values 21-29, 65, 66, 69 and 70 are for use where a specific
charge rate is defined in the IOT for the referenced QCI.
Value 20 is intended for use where a default QCI charge rate is
defined in the IOT and applies. For example an IOT defines a
V36.4 Page 74 of 317


Code Level
rate for QCI 5 and a default rate for all other QCIs.
Although values 20-29, 65-66 and 69-70 are intended for use
as described above, they are also allowed without any IOT
defined QCI specific charging.
Premium Rate is as defined by the numbering plan

administrator of the relevant country or region code.
Non Geographic is used, for example, for special services and
Freephone / toll free services.
Unknown/Not Applicable can be used when the VPMN cannot
interpret the destination/origin or does not differentiate
charging based on any other of the Call Type Level 2 values.
Call Type An item which identifies the sub category of Call Type Level 2. 10 MOC Severe Syntax error.
Level 3 MTC
This defines, in more detail, the classification of the call within GPRS
the IOT, as used by the VPMN to price the call. MSESS
MSG
Conditionality: AUR
Mandatory within group Call Type Group.
Must be present within Aggregated Usage Record when the 20 MOC Severe Value out of range.
Aggregated Usage Charge is greater than 0 (zero). MTC
Values: GPRS
 numeric (>=0) as defined within the VPMN’s IOT. MSESS
MSG
 where a VPMN has not defined a Call Type Level 3 in AUR
their IOT they can use any numeric values (>=0) in TAP.
Called Number The called number is the international representation of the 10 MOC Severe Syntax error and call does not
destination and contains different information depending on the represent an emergency call (as
call scenario: defined in chapter 5.7).
 Circuit Switched MO Call initiated by the roamer: The
international representation of the number dialled by the 11 MOC Warning Syntax error and call represents
V36.4 Page 75 of 317


Code Level
roamer in establishing the call emergency call (as defined in chapter
 Circuit Switched MO Call initiated as a result of an 5.7).
incoming call and invocation of conditional call forwarding:
20 MOC Severe Value out of range or number does not
The international representation of the number to which start with a valid country code as listed
the call is forwarded in E.164 “Assigned Country Codes”,
 SMS MO: The international representation of the SMSC and either CAMEL Destination Number
address used or Dialled Digits is not present.
Note 1: Spare and reserved codes,

The called number must always start with the valid country indicated by the inclusion of the words
code as listed in E.164 “Assigned Country Codes” (spare and “Reserved” or “Spare” in E.164 column
reserved codes are not valid, except the reserved code 970 for “Country, Geographical area or Global
Palestine which is valid), and contain only numeric digits. All service”, are NOT valid country codes,
other characters must be removed. See examples in TD.58. with the exception of reserved code
970 for Palestine which is valid.
In the following cases it is acceptable for the Called Number (if
present) to contain only the country code: Note 2: Additional E.164 notes for
 Short code call: Only country code, or country code shared country codes listing the
followed by short code currently assigned networks and their
identification codes must not be taken
 Emergency call: Only country code, or country code
into account. For example, a full
followed by the emergency service access code numeric Called Number starting with
 Unsuccessful call attempt: Only country code, or full 881 is always valid no matter which
number starting with the country code digits follow.
 Specially routed call (for example using ‘*’ or ‘#’): Only
21 MOC Warning Value out of range or number does not
country code start with a valid country code as listed
in E.164 “Assigned Country Codes”,
In all other cases the Called Number must contain the full long and both CAMEL Destination Number
number as defined by E.164 “International public and Dialled Digits are present.
telecommunication number structure.
Note 1: Spare and reserved codes
Derivation: are NOT valid country codes, with the
exception of reserved code 970 for
V36.4 Page 76 of 317


Code Level
Derived from GSM item CalledNumber (See Annex C – CS Palestine which is valid.
Domain Charging) but it is represented in TAP in
Note 2: Additional E.164 notes for
International format, i.e. the number begins with the Country
shared country codes listing the
Code. currently assigned networks and their
identification codes must not be taken
Conditionality: into account. For example, a full
Must be present within group Destination except for one of numeric Called Number starting with
the following: 881 is always valid no matter which
digits follow.
 use of the basic service emergency call
 unsuccessful call attempt Note: Error Code 201 removed in
 when the call destination has been modified by CAMEL TAP release 3.12 (with effect from 01
May 2013).
(CAMEL Destination Number is present)
If Called Number is not present then, in case of

unsuccessful call attempt or CAMEL destination
modification, item Dialled Digits must be filled in.
In the case of SMS-MO usage this field must always be

present.
Values:
Each digit is numeric (0-9)
Called Place The Called Place indicates, in plain text, the name of the 10 MOC Warning Syntax error.
geographic area to which the call was placed, for example
Atlanta, Roma, Sydney, or the type of service used, for
example Freephone.
On international calls this item will contain the called country,

e.g. Norway, South Africa, Thailand.
V36.4 Page 77 of 317


Code Level
Conditionality:
Must be present within group Destination when provided by
the VPMN’s billing system.
Not present within group Destination where the destination

is non geographic, for example operator call (see also Call
Type and Sender PMN Subtype).
Values:
ISO 646 [27]
Actual content is at the Sender PMN discretion
Called Place The Called Place indicates, in plain text, the name of the 10 MOC Warning Syntax error.
geographic area to which the call was placed, for example
Atlanta, Roma, Sydney, or the type of service used, for
example Freephone.
On international calls this item will contain the called country,

e.g. Norway, South Africa, Thailand.
Conditionality:

is non geographic, for example operator call (see also Call
Type and Sender PMN Subtype).
Values:
ISO 646
Called Region Called Region contains the geographical region called or 10 MOC Warning Syntax error.
service used, this is a broader description than contained
within Called Place, for example GA (Georgia), Lazio, NSW
V36.4 Page 78 of 317


Code Level
(New South Wales).
Conditionality:

is international or non geographic.
Values:
ISO 646 [27]
Called Region Called Region contains the geographical region called or 10 MOC Warning Syntax error.
service used, this is a broader description than contained
within Called Place, for example GA (Georgia), Lazio, NSW
(New South Wales).
Conditionality:

is international or non geographic.
Values:
ISO 646
Calling The calling number is the number from which the call was 10 MTC Warning Syntax error.
Number originated in the case of mobile terminated calls. For SMS MT
this item must contain the SMSC MSISDN. 20 MTC Warning Number not in international format.
Derivation: Note: Error Code 11 removed in TAP

GSM item CallingNumber (See Annex C – CS Domain release 3.11 (01 May 2005).
Charging). This item is of type AddressString. It is
V36.4 Page 79 of 317


Code Level
represented in TAP in international format, i.e. the number
begins with the country code related to the calling number.
Conditionality:
Must be present within group Call Originator where
available from the network.
Values:
Each digit is numeric (0 – 9)
CAMEL The destination number returned by the CAMEL server to the 10 MOC Severe Syntax error.
Destination interrogating (visited) MSC.
Number 20 MOC Severe Value out of range or number does not
Note: The CAMEL Destination Number, where present, is the start with a valid country code as listed
relevant destination field for charging and takes precedence in E.164 “Assigned Country Codes”.
even where the Called Number and/or Dialled Digits is/are also Note 1: Spare and reserved codes are
present. NOT valid country codes with the
exception of reserved code 970 for
Derivation: Palestine which is valid.
Derived from GSM item CalledNumber (See Annex C – CS
Domain Charging and (for SMS over PS only) PS Domain Note 2: Additional E.164 notes for
shared country codes listing the
Charging) but it is represented in TAP in International
currently assigned networks and their
format, i.e. the number must start with a valid Country Code identification codes must not be taken
for the routed destination. See Examples in TD.58 [33]. into account. For example, a full
numeric CAMEL Destination Number
Conditionality: starting with 881 is always valid no
Mandatory within group 3G CAMEL Destination where matter which digits follow.
GPRS Destination not present.
21 MOC Severe CAMEL Destination Number different
from what the Home CAMEL Server
Values: returned.
Each digit is numeric (0-9) or Note: The Sender may need to insert
contains ‘A’ (representing *) or a country code in front of what the
Home CAMEL Server returned.
contains ‘B’ (representing #) or
V36.4 Page 80 of 317


Code Level
contains ‘C’ (representing a) or
contains ‘D’ (representing b) or Note: Error Code 201 removed in
TAP release 3.12 (with effect from 01
contains ‘E’ (representing c) May 2013).
CAMEL The charge for the CAMEL invocation after discounts have 10 MOC Severe Syntax error.
Invocation Fee been deducted, where applicable (see Discount Information) MTC
but before any tax is added, where applicable (see Tax GPRS
Information).
20 MOC Severe Value is negative.
The item must not contain a negative value. MTC
GPRS
The charge is in SDRs with the number of decimal places
defined by item TAP Decimal Places. Note the currency may 21 MOC Warning Value is 0 (zero).
be subject to internal market bilateral agreements, see TAP MTC
Currency. GPRS
Conditionality: 200 MOC Severe CAMEL Invocation Fee not in line with
Mandatory within group CAMEL Service Used where the MTC roaming agreement.
charge is greater than zero. GPRS Note: Rounding rules are at the
discretion of the Sender, therefore,
Values: when validating the charge applied by
> 0 (zero) the Sender (by using Call Type Group
information and the Sender’s IOT) the
Recipient must allow for a tolerance of
0.02 units of TAP Currency
(independent of the number of TAP
Decimal Places used for the TAP file).
Note: No tolerance is allowed when
the expected CAMEL Invocation Fee is
zero.
201 MOC Severe CAMEL Invocation Fee is greater than

MTC 0 (zero) and CAMEL call not expected.
GPRS Note: The HPMN is responsible for
V36.4 Page 81 of 317


Code Level
configuring its CAMEL server
appropriately to avoid the use of
CAMEL service before commercial
launch of CAMEL.
CAMEL The identification of the CAMEL service logic to be applied to 10 MOC Warning Syntax error.
Service Key the IN subscriber. MTC
GPRS
Derivation:
GSM item ServiceKey (See Annex C – CS Domain 20 MOC Warning Value out of range.
Charging and PS Domain Charging). MTC
GPRS
Conditionality:
Mandatory within group CAMEL Service Used.
Range:
0 – 2147483647 (derived from 0 to 2^31)
CAMEL The level of CAMEL service provided by the VPMN to the 10 MOC Severe Syntax error.
Service Level roaming CAMEL subscriber. The VPMN may vary the MTC
associated CAMEL invocation fee according to the level of GPRS
service provided.
The value is derived from the actual CAMEL features which MTC
have been used during the call: GPRS
 Basic: All CAMEL features excluding control of call
duration and online charging.
 Medium: All CAMEL features including control of call
duration but excluding control of online charging.
 High: All CAMEL features including control of online
charging (i.e. timers set in the VMSC or SGSN [for
GPRS]) but excluding control of call duration.
 Maximum: All CAMEL features including control of online
charging (i.e. timers set in the VMSC or SGSN [for
V36.4 Page 82 of 317


Code Level
GPRS]) and call duration.
Derivation:
From the definition in GSM Association PRD BA.27 [13].
Conditionality:
Mandatory within group CAMEL Service Used where
CAMEL Invocation Fee present within the call event.
Values:
0 basic
1 medium
2 high
3 maximum
CAMEL This element is a group detailing the invocation of CAMEL 30 MOC Severe Item CAMEL Service Level missing
Service Used services. MTC within group although CAMEL
The group must contain CAMEL Service Key. Where the GPRS Invocation Fee is present and greater
CAMEL Invocation Fee is greater than zero this group must than zero.
also contain the Exchange Rate Code. All other items are
conditional. 31 MOC Severe CAMEL Destination Number missing
within group although number was
Conditionality: modified by CAMEL (logical group 3G
Must be present within groups CAMEL Destination).
 Mobile Originated Call
 Mobile Terminated Call 33 MOC Warning Mandatory item CAMEL Service Key
 GPRS Call MTC missing within group.
where invocation of CAMEL services has taken place GPRS
within the call.
35 MOC Severe GPRS Destination present within
MTC group (logical group 3G CAMEL
Destination).
36 GPRS Severe CAMEL Destination Number present

within group (logical group 3G CAMEL
V36.4 Page 83 of 317


Code Level
Destination).
37 GPRS Warning Group GPRS Destination missing

within group although APN was
modified by CAMEL (logical group 3G
CAMEL Destination).
40 MOC Severe Exchange Rate Code missing within

MTC the group and CAMEL Invocation Fee
GPRS is greater than zero.
41 MOC Severe Tax Information missing within the

MTC group and CAMEL Invocation Fee is
GPRS greater than zero and taxation is
expected according to roaming
agreement.
42 MOC Severe Tax Information present within the

MTC group but not expected in accordance
GPRS with roaming agreement for the
call/event and Tax Value referenced
within the group is greater than zero.
43 MOC Warning Tax Information present within the

MTC group but not expected in accordance
GPRS with roaming agreement for the
within the group is not greater than
zero.
Note: Error Codes 32, 34, 38 & 39

removed in TAP release 3.11 (01 May
2005).
Cause For Indicates the reason for termination of the call where that 10 MOC Severe Syntax error.
V36.4 Page 84 of 317


Code Level
Termination reason is anything other than normal. MTC
GPRS
Derivation: MSESS
GSM items CauseForTerm and CauseForRecClosing(See
Annex C – CS Domain Charging and PS Domain 20 MOC Severe Value out of range.
Charging). MTC
GPRS
For Wi-Fi usage mapped from acct-terminate-cause (RFC MSESS
2866 [22]).
100 GPRS Warning Cause for termination specified and
For Voice over LTE network usage, IMS item the call event represents first or
CauseForRecordClosing (see Annex C - IMS Domain intermediate partial.
Charging)
Conditionality:
MO Basic Call Information
MT Basic Call Information
GPRS Basic Call Information
Mobile Session
where the call release is abnormal, see values below.
Where the cause for termination is normal release, i.e.
value 0, then the item is not present.
Values:
1 Unsuccessful Service Delivery
3 Unsuccessful call attempt
4 Stable call abnormal termination
5 CAMEL initiated call release/Management intervention
20 Management intervention
21 Intra SGSN intersystem change
24 SGSN PLMNIDS change
Values 4, 5 (CAMEL initiated call release), 20, 21 and 24

are valid within a GPRS Call context only where the call did
V36.4 Page 85 of 317


Code Level
not terminate normally. Where partial GPRS Calls are
generated then only the last partial can contain a cause for
termination where appropriate.
Values 3, 4 and 5 (CAMEL initiated call release) are valid
within a MOC/MTC only where the call did not terminate
normally.
Values 4 and 20 are valid within a Wi-Fi context only where
the call did not terminate normally. Where partial GPRS
Calls for Wi-Fi usage are generated then only the last
partial can contain a cause for termination where
appropriate.
Values 1 and 5 (Management intervention) are valid for
Voice over LTE only where the session did not terminate
normally.
Note: Only the values as defined above are valid in TAP.

There are other valid 3GPP values (listed in Annex C),
however, they are not valid in TAP.
Following is a mapping between the RFC2866 Acct-

Termination-Cause values and Cause for Termination values:
TD.57 Cause For RFC2866 [22]22]

Termination RFC2866 [22] Short
Values Values Description
<not present> 1 User Request
4 2 Lost Carrier
4 3 Lost Service
4 4 Idle Timeout
4 5 Session Timeout
20 6 Admin Reset
20 7 Admin Reboot
4 8 Port Error
4 9 NAS Error
V36.4 Page 86 of 317


Code Level
4 10 NAS Request
4 11 NAS Reboot
4 12 Port Unneeded
4 13 Port Preempted
4 14 Port Suspended
4 15 Service
Unavailable
4 16 Callback
4 17 User Error
<not present> 18 Host Request
Cell Identity The identity of the cell from which the call originated or in 10 MOC Warning Syntax error.
which it terminated. MTC
SS
Derivation: GPRS
GSM item CellId (See Annex C – CS Domain Charging and MSESS
PS Domain Charging). MSG
Optionality:
Operators may decide not to transfer the Cell Identity.
Conditionality:
Network Location
GPRS Network Location
Messaging Event
Mobile Session
if the call originates or terminates from a mobile, i.e. not
available in call divert cases (subject to optionality).
Is not present for Wi-Fi usage.
The Cell Identity is a two octet string (See Annex C – CS

Domain Charging), except for E-UTRAN (see below).
For the TAP the octets are converted to a decimal integer
V36.4 Page 87 of 317


Code Level
number in the range 0 to 65535. The leading zeros are
significant only for the 2 octet strings in the standard and not in
TAP.
For example 0110011000110000 equates to 26160
1001110000001010 equates to 39946
0001000011110001 equates to 4337
The E-UTRAN Cell Identifier (ECI) consists of 28 bits (see

Annex C - PS Charging Domain)
Where d represents the first Octet of the ECGI (E-UTRAN Cell

Global Identifier) field, the ECI encoding within the ECGI field
shall start with bit 4 of octet d+3 in the E-UTRAN Cell Global
Identifier field (ECGI = MCC+MNC+ECI) which is the most
significant bit while bit 1 of octet d+6 is the least significant bit.
Charge The charge for the Charge Detail after discounts have been 10 Calls Severe Syntax error.
deducted (if applicable, see Discount Information) but before
any tax is added (if applicable, see Tax Information). 20 Calls Severe Value out of range.
The Charge must not contain a negative value. 200 Calls Severe Charge not in line with roaming
agreement. Charge validation must be
The charge is in SDRs with the number of decimal places done according to section 5.9.
defined by item TAP Decimal Places. Note the currency may Note: This error cannot be raised
be subject to internal market bilateral agreements, see TAP where the Charge is zero (0) for the
Currency. following scenarios:
Mobile Terminated Calls except SMS
Example: (Teleservice Code 20 or 21)
A call of 2 minutes duration is charged at 1 SDR per 30 Mobile Session with Mobile Session
seconds; the call is liable for tax at 15% and the HPMN will Service “MT Voice over LTE”
get the call discounted at 20%.
Notes for validation rule 200:
Rated charge value 4.000 SDR Rounding rules are at the discretion of
Discount Rate 20% the Sender, therefore, when verifying
Tax Rate 15% the charge applied by the Sender the
V36.4 Page 88 of 317


Code Level
Recipient must allow for a tolerance of
TAP fields will have the following values: 0.02 units of TAP Currency
Discount Value 0.800 SDR (independently of the number of TAP
(rated charge value * Discount Rate) Decimal Places used for the TAP file).
Charge (Charge Type 00) 3.200 SDR No tolerance is allowed when the
(rated charge value – Discount Value) expected Charge is zero.
Tax Value 0.480 SDR
(Charge * Tax Rate) The TAP fields to be used as a basis
for the calculation of the correct
Conditionality: Charge depends on the value of the
Must be present within group Charge Detail and Messaging Charged Item as follows:
Event. A: Chargeable Units (if present)
D, V, W, X: Chargeable Units
Values: C: Depends on the content
> or = 0 (zero) E: Not Applicable
F: Not Applicable
L: Call Event Start Timestamp
Error 200 on Charge can also be

raised where the total invoicable
Charge, in case of more than one
Charge Information group, is not in line
with the roaming agreement.
One example is the population of two
Charge Information groups in a GPRS
CDR, one for upload and one for
download, where both volumes are
rounded up, although the Sender’s IOT
specifies charging for total
(aggregated) volume.
Note: Error Code100 & 201 removed

in TAP release 3.11 (01 May 2005).
V36.4 Page 89 of 317


Code Level
TAP release 3.12 (with effect from 01
May 2013).
Charge Detail A repeating group detailing the Charge and/or charge element. 32 Calls Warning Associated item Charged Item is one
Charge and Charge Type are mandatory items, Charged Units of
is optional and all other items are conditional. E,F or L
and item Chargeable Units present
Conditionality: within group.
Mandatory within group Charge Information and Session
Charge Information, at least one occurrence must be 33 Calls Severe Associated item Charged Item is one
present. of
Note that, where a Charge has been levied, even where D,V,W or X
that Charge is zero, there must be one occurrence, and and item Chargeable Units not
only one, with a Charge Type of ‘00’. present.
38 Calls Severe Mandatory item Charge Type not

present within group.
39 Calls Severe Mandatory item Charge not present

within group.
Note: Error Codes 30, 31, 34, 35, 36 &

37 removed in TAP release 3.11 (01
May 2005).
Charge Detail The timestamp showing the start of charging for the Charge 10 Calls Severe Syntax error.
Timestamp Detail within which it occurs.
20 Calls Severe Value out of range.
The time is given in the local time of the Sender PMN (or
Serving Network where this is not the Sender). There must be 30 Calls Severe Mandatory associated item UTC Time
a UTC Time Offset Code associated with the timestamp. Offset Code missing.
Note that local time is the local time at the location of the 100 Calls Severe Charge Detail Timestamp earlier than
chargeable subscriber. Where the location is not available, as Charging Timestamp and the Charge
in some call forwarding scenarios, this will be a notional associated with this Charge Detail is
‘network local time’. greater than zero (note UTC time
V36.4 Page 90 of 317


Code Level
offset must be taken into
Conditionality: consideration).
Must be present within group Charge Detail where it is not
the same as the associated Charging Timestamp. 101 MOC Severe Charge Detail Timestamp is later than
MTC the end of the call (Call Event Start
Format: GPRS Timestamp plus Total Call Event
CCYYMMDDHHMMSS Duration) and the Charge associated
with this Charge Detail is greater than
Note: Within this timestamp the range for HHMMSS is 000000 zero (note UTC time offset must be
– 235959 taken into consideration).
Charge Charge information is provided for all chargeable elements 30 Calls Severe Item Charged Item missing within
Information except within Messaging Event and Mobile Session call group.
events.
31 Calls Severe Item Exchange Rate Code missing
The group must contain Charged Item and at least one within group and one or more Charge
occurrence of Charge Detail. within an associated Charge Detail is
greater than zero.
Conditionality:
One or more occurrences must be present within groups 32 MOC Severe Item Call Type Group missing within
Basic Service Used. MTC group where the Charge Information
GPRS Service Used GPRS relates to Basic Service Used or GPRS
Service Centre Usage Service Used.
Location Service Usage
33 Calls Severe Group Charge Detail missing within
One occurrence must be present within group group.
Supplementary Service Used where the event is
chargeable. 34 Calls Severe Group Tax Information missing within
group but expected in accordance with
One or more occurrences must be present within group roaming agreement for that particular
Content Service Used if the service is charged through the call. Tax Information group missing
TAP on a wholesale basis, i.e. not using Advised Charge must be interpreted as Tax Value zero.
Information for settlement. Tax Value zero may be applicable to
low charge calls where rounded value
Note 1: For GPRS CDRs the population of Charge Information results in 0 charge. In this case Tax
V36.4 Page 91 of 317


Code Level
groups must follow the Sender’s IOT. If the Sender’s IOT Information is not required.
specifies separate charging of outgoing and incoming volume Note (applicable from 01 May 2015):
for GPRS then a Charge Information for outgoing volume This error cannot be raised where
(Charged Item V) and a Charge Information for incoming 35 Calls Severe variable tax rates apply to the call
volume (Charged Item W) must be populated. It is not event and tax rate range starts from
acceptable to aggregate charging into one Charge Information zero.
with Charged Item X in such case. It is possible to reject
records (error 200 on Charge) not following this rule. 36 Calls Severe Group Discount Information missing
within group but expected in
Note 2: For voice, if the Sender’s IOT specifies a setup fee accordance with roaming agreement.
and a duration based charge then the setup fee can either be
included into the first charging interval (population of Charge 37 Calls Severe Occurrence of group Charge Detail
Information with Charged Item D only in this case) or separate containing Charge Type ‘00’ missing
Charge Information groups with Charged Item F and Charged within group.
Item D can be populated.
38 MOC Severe More than one occurrence of Charge
MTC Detail present with the same Charge
Type value.
Breakout of Charge Types AIR (01)

and/or TOLL (03) not present on a
duration based charge, but expected in
accordance with roaming agreement;
i.e., only Charge Type 00 present
within group. This validation rule can
be applied only where bilaterally
39 MOC Severe agreed between sender and recipient
MTC and where the call charge is greater
than 0.
In accordance with roaming

agreement, charges are defined in
individual Charge Types, but the
Charge for Charge Type 00 does not
equal sum of Charges for the other
V36.4 Page 92 of 317


Code Level
Charge Types as stated within roaming
40 Calls Severe agreement. This validation rule can be
applied only where bilaterally agreed
between sender and recipient.
Group Tax Information present within

group but not expected in accordance
with roaming agreement for the
41 Calls Warning call/event and Tax Value referenced
within the group is greater than 0
(zero).
Group Tax Information present within

42 Calls Warning call/event and Tax Value referenced
within the group is not greater than 0
(zero).
Call Type Group present within group

and the call event is not a MOC, MTC
or GPRS Call.
Charge Refund The Charge Refund Indicator is present when the Content 10 Content Severe Syntax error.
Indicator Transaction represents a refund.
20 Content Severe Value out of range
This item, when present, will change the signs of any revenue
represented within the Content Service Used occurrence.
Conditionality:
Must be present within group Content Service Used when
the Content Transaction represents a refund.
Values:
1 Refund
V36.4 Page 93 of 317


Code Level
Charge Type When present within Charge Detail the item identifies the type 10 Calls Severe Syntax error.
of charge represented by the Charge Detail.
11 Acctng Fatal Syntax error.
When present within Taxation the item identifies the type of
charge associated with the applied tax referenced by the 20 Calls Severe Value out of range.
associated Tax Rate Code. Should only be present where a Note that ‘reserved’ values are out of
charge breakdown is present in Charge Detail and where the range. Note that the use of value 50 is
tax is applicable to only a specific Charge Type rather than to only for use by bilateral agreement,
the total charge. use without bilateral agreement can be
treated as per reserved values, that is
Note: in the ‘Values’ list, below, some values are identified as ‘out of range’
‘reserved’. Reserved values are not to be considered valid
values, they are noted here in order to prevent their usage, 21 Acctng Fatal Value out of range.
were they to be used this could create inter standard roaming Note that ‘reserved’ values are out of
conversion problems. Elements containing a reserved value range. Note that the use of value 50 is
will fail the ‘Value Out Of Range’ validation check. only for use by bilateral agreement,
use without bilateral agreement can be
Charge Type 50 must be used by bilateral agreement only. treated as per reserved values, that is
When present, the Charge associated with Charge Type 50 will ‘out of range’
hold the total charge for Charge Information according to the
published IOT. In this case, the Charge associated with 22 Acctng Warning Value is ‘00’.
Charge Type 00 will hold the invoiceable amount that is the
total charge for Charge Information according to the
discounted IOT. Where Charge Type 50 is used without
bilateral agreement, it can be treated as a reserved number,
which can result in a severe, out of range, error where the
Recipient is unable to handle this within their system. Charge
Type 50, and its’ associated Charge, does not affect the
invoiceable value of the call event.
Conditionality:
Must be present within group Charge Detail.
Must be present within group Taxation when the associated

Tax Rate Code references a tax applied to a specific
V36.4 Page 94 of 317


Code Level
Charge Type. Note that this is not required for Charge Type
‘00’.
Values:
00 Total charge for Charge Information
(the invoiceable value)
01 Airtime charge
02 reserved
03 Toll charge
04 Directory assistance
05 – 20 reserved
21 VPMN surcharge
50 Total charge for Charge Information
according to the published IOT
69 – 99 reserved
Note:
The use of value 50 is only for use by bilateral agreement, use
without bilateral agreement can be treated as per reserved
values, that is ‘out of range’
Chargeable Contains the identification of the chargeable subscriber. 33 MOC Severe Neither of groups SIM Chargeable
Subscriber MTC Subscriber nor MIN Chargeable
The group must contain either the SIM Chargeable Subscriber SS Subscriber present within group.
or the MIN Chargeable Subscriber but not both. GPRS
Operators may bilaterally agree to make transfer of MSISDN Note: Error code 32 moved to SIM
mandatory. Chargeable Subscriber in TD57 v32.4
Conditionality:
Supplementary Service Event.
V36.4 Page 95 of 317


Code Level
Conditional within group GPRS Chargeable Subscriber.
Chargeable The Chargeable Units item indicates the number of units which 10 Calls Severe Syntax error.
Units are chargeable within the Charge Detail, this may not
correspond to the number of rounded units charged. The item 20 Calls Severe Value out of range.
Charged Item defines what the units represent.
100 MOC Severe Chargeable Units for Charge Type ‘00’
Derivation: MTC are greater than Total Call Event
For duration based charge; GSM item CallDuration (See GPRS Duration for Charged Item ‘D’.
Annex C – CS Domain Charging and PS Domain
Charging). CallDuration is defined in seconds. 101 GPRS Severe Chargeable Units for Charge Type ‘00’
are greater than the sum of Data
The duration related to Wi-Fi usage is defined in seconds. Volume Incoming and Data Volume
Outgoing for Charged Item ‘X’.
Where GPRS services have been used in conjunction with
volume based charge; 102 GPRS Severe Chargeable Units for Charge Type ‘00’
are greater than the Data Volume
outgoing volume GSM item DataVolumeGPRSUplink Outgoing for Charged Item ‘V’.
incoming volume GSM item DataVolumeGPRSDownlink
total volume sum of GSM items 103 GPRS Severe Chargeable Units for Charge Type ‘00’
DataVolumeGPRSUplink and are greater than the Data Volume
DataVolumeGPRSDownlink Incoming for Charged Item ‘W’.
The GPRS data volumes are defined in octets
Where volume is related to Wi-Fi usage then the volume is

defined in octets.
Where volume is related to messages (Service Centre

Usage) then the message length is represented in
characters.
The item content reflects the chargeable not charged units.
Examples:
V36.4 Page 96 of 317


Code Level
For Duration charge:
Actual duration is 73 seconds
Call charged in 30 second units (i.e. 90 seconds)
Chargeable Units contains 73
For SCU based volume charge:

Actual message length is 17 characters
Message charged in 10 character units (that is, 20
characters)
Conditionality:
Must be present within group Charge Detail where the
charge is either duration based or volume based.
Values:
> or = 0
Charged Item This field identifies the charging principle applied and the 10 Calls Severe Syntax error.
unitisation of Chargeable Units. It is not intended to identify
the service used. 20 Calls Severe Value out of range.
Conditionality:
Charge Information
Session Charge Information
Values:
A Call set up attempt
C Content
D Duration based charge
E Event based charge
F Fixed (one-off) charge
L Calendar (for example daily usage charge)
V Volume (outgoing) based charge
V36.4 Page 97 of 317


Code Level
W Volume (incoming) based charge
X Volume (total volume) based charge
The actual value used for Charged Item by a VPMN is at

their discretion and dependent on the tariff applied.
The use of ‘C’ within a Content Transaction is for use

where none of the other values are more appropriate, for
example if content is charged by data volume then one of
‘V’, ‘W’ or ‘X’ must be used.
Call/event type Valid values

Circuit switched MO and MT calls A, D, F
SMS MO and SMS MT E
GPRS and Wi-Fi A, D, F, L, V, W, X
Location Services D, E, F, L
Service Centre Usage E
Content Service C, D, F, L, V, W, X
Supplementary Service (including USSD) E
LTE Voice MO and MT calls A, D, F
Charged Party Group providing information on the chargeable party. IMSI is 30 MSESS Severe Mandatory Item IMSI not present
mandatory, MSISDN and IMEI are conditional and all other MSG within group.
items are optional.
Conditionality:
Mandatory within groups Mobile Session and Messaging
Event.
Charged Party Information relating to equipment used by the Charged Party 30 Content Warning Mandatory item Equipment Id Type
Equipment for the Content Transaction. missing within group.
The group, when present, must contain items Equipment Id 31 Content Warning Mandatory item Equipment Id missing
Type and Equipment Identifier. within group.
Conditionality:
V36.4 Page 98 of 317


Code Level
Present within group Charged Party Information where
available.
Charged Party Information identifying the home environment of the Charged 30 Content Severe Mandatory item Home Id Type missing
Home Party. within group.
Identification
The group when present must contain items Home Id Type and 31 Content Severe Mandatory item Home Identifier
Home Identifier. missing within group.
This information is not required when the Home and Recipient

are the same entity.
Conditionality:
One or more occurrences may be present within group
Charged Party Information where available.
Charged Party An item identifying the type of Charged Party Identifier. 10 Content Severe Syntax error.
Id Type
Conditionality: 20 Content Severe Value out of range.
Mandatory within group Charged Party Identification.
Values:
1 MSISDN
2 IMSI
3 MIN (Mobile Identification Number)
4 IP Address v4
5 IP Address v6
6 Login Name for example ‘gcgGenComp’
7 Account Number for example ‘ACC00376’
8 E-mail Address for example
‘[email protected]’
Charged Party The identification of the subscriber being charged for the 30 Content Severe Mandatory item Charged Party Id Type
Identification transaction. missing within group.
The group must contain items Charged Party Id Type and 31 Content Severe Mandatory item Charged Party
Charged Party Identifier. Identifier missing within group.
V36.4 Page 99 of 317


Code Level
The group must contain sufficient information for the Recipient

to be able to uniquely identify the Charged Party.
Conditionality:
One or more occurrences must be present within group
Charged Party Information.
Charged Party The item holds an identifier for the Charged Party. The 10 Content Severe Syntax error.
Identifier identifier may only be unique in conjunction with other
information within the Charged Party Information, for example 20 Content Severe Value out of range and item is a
MIN & ESN, MSISDN & TADIG Code. MSISDN.
The type of identifier is contained in the associated Charged 100 Content Severe Item content does not match Charged
Party Id Type. Party Id Type.
Conditionality: 200 Content Severe Item is an IMSI of a known network

Mandatory within group Charged Party Identification. operator and initial characters are
different from the network operator’s
MCC + MNC, or not as as bilaterally
agreed.
Charged Party Information relating to the Charged Party. 30 Content Severe Mandatory group Charged Party
Information Identification missing within group.
The group must contain at least one occurrence of group
Charged Party Identification. Additional information
conditionally available may include Charged Party Home
Identification, Charged Party Location and Charged Party
Equipment.
Conditionality:
Mandatory within group Content Transaction.
Charged Party Information on the geographical location of the Charged Party 30 Content Warning Mandatory item Location Id Type
Location at the time of Content Transaction request. missing within group.
This information may not be available or relevant, for example 31 Content Warning Mandatory item Location Identifier
V36.4 Page 100 of 317


Code Level
where the content is ‘timer’ requested (for example weekly). missing within group.
Availability of this information may also be subject to local
regulatory rules/laws.
Conditionality:
Must be present within group Charged Party Information
where available.
Charged Party Indicates whether the chargeable subscriber is the originating 10 SCU Severe Syntax error.
Status or terminating party.
20 SCU Severe Value out of range.
Conditionality:
Mandatory within group SCU Basic Information.
Values:
0 Originating
1 Terminating
Charged Units The Charged Units item indicates the rounded number of units 10 Calls Warning Syntax error.
which are actually charged for within the Charge Detail
occurrence. 20 Calls Warning Value out of range.
This value may not correspond to the number of Chargeable

Units as it represents the charged units given the pricing
unitisation/segmentation, for example first segment minimum
60 seconds charged followed by 30 second unit charge.
The item Charged Item defines what the units represent.
The item content reflects the rounded charged not chargeable

units.
Charged Units must be presented in the same unitisation as

the corresponding Chargeable Units.
Examples:
V36.4 Page 101 of 317


Code Level
For Duration charge:

Actual duration is 73 seconds
Call charged in 30 second units (that is 90 seconds)
Charged Units contains 90
For volume charge:

Actual message length is 17 characters
Message charged in 10 character units
(that is 20 characters)
Charged Units contains 20
A volume based charge indicates that the field represents a

Data Volume or, in the case of Service Centre Usage,
Message Length.
Optionality:
Transfer is at the discretion of the Sender PMN.
Conditionality:
Must be present within group Charge Detail where
Chargeable Units is present (subject to optionality).
Values:
> or = 0
Charging ID A charging identifier which can be used together with GGSN 10 GPRS Severe Syntax error.
address or P-GW address to identify all records produced in
SSGN(s) and GGSN or in S-GW(s) and P-GW involved in a 20 GPRS Severe Value out of range.
single PDP context.
For Wi-Fi usage this item is unique as a Wi-Fi record always

represents a complete Wi-Fi session.
V36.4 Page 102 of 317


Code Level
Derivation:
GSM item ChargingID (PS Domain Charging – see Annex
C).
For Wi-Fi the derivation is at the discretion of the Sender.

Note that Charging Id must remain unique (together with
the recording entity) during a significant amount of time.
Conditionality:
Mandatory within group GPRS Basic Call Information
Range:
0 – 4294967295 (derived from 0 to 2^32-1)
Charging Point An indicator detailing which of the two timestamps, Deposit or 10 SCU Severe Syntax error.
Completion, was used for tariffing purposes, i.e. the Charging
Point. 20 SCU Severe Value out of range.
Conditionality:
Mandatory within group SCU Timestamps.
Values:
C Completion Timestamp
D Deposit Timestamp
Charging The timestamp showing the start of the Charge Information. 10 Calls Severe Syntax error.
Timestamp This item will be present where it is not the same as an
associated Call Event Start Timestamp or where there is no 20 Calls Severe Value out of range.
such associated timestamp.
30 Calls Severe Mandatory associated item UTC Time
The time is given in the local time of the Sender PMN (or Offset Code missing.
Serving Network where this is not the Sender). There must be
a UTC Time Offset Code associated with the timestamp. 100 MOC Severe Charging Timestamp is later than end
MTC of call (Call Event Start Timestamp
Note that local time is the local time at the location of the plus Total Call Event Duration).
V36.4 Page 103 of 317


Code Level
chargeable subscriber. Where the location is not available, as
in some call forwarding scenarios, this will be a notional 101 LCS Severe Charging Timestamp is later than LCS
‘network local time’. Request Timestamp plus Response
Time.
Derivation:
GSM item answerTime or seizureTime (See Annex C – CS 200 SS Severe Charging Timestamp before the
Domain Charging and PS Domain Charging). The actual LCS commercial roaming start date (in
derivation will be dependent upon the charging principles VPMN local time if no other time zone
used by the Sender and as defined by their IOT. explicitly agreed) for the specific
service and the TAP file is not a test
Conditionality: file.
Mandatory within group Supplementary Service Used
where this occurs within Supplementary Service Event
Within group Location Service Usage the timestamp will

only be present where it is not the same as the associated
LCS Request Timestamp.
Within group Basic Service Used the timestamp will only be

present where it is not the same as an associated Call
Event Start Timestamp.
Format:
CCYYMMDDHHMMSS

– 235959
CLIR Status Indicates the CLIR status of the call originator in the case of a 10 MOC Warning Syntax error.
Indicator Mobile Originated Call (call forwarding context where Third MTC
Party Information is present), Mobile Terminated Call or a SCU
Service Centre Usage where the terminating party is the
Chargeable Subscriber. 20 MOC Warning Value out of range.
MTC
Conditionality: SCU
V36.4 Page 104 of 317


Code Level
Call Originator
Third Party Information
where available.
Must be present within group SCU Basic Information where

available and the Charged Party Status indicates a
terminating short message.
Values:
0 Presentation allowed
1 Presentation not allowed
Commission Commission due to the Recipient. 10 Content Severe Syntax error.
This information will be present when commission is applied at 20 Content Severe Value out of range.
a transaction level.
Commission must not contain a negative value. However, a

negative value is implied when Charge Refund Indicator is
present.
Taxes are not included in the commission. Taxation is not

applicable to the commission.
The charge is in the Advised Charge Currency, or TAP

Currency where no associated Advised Charge Currency is
present, or SDRs where neither is present.

Places.
Conditionality:
Present within group Advised Charge Information when
commission is applied at a transaction level.
V36.4 Page 105 of 317


Code Level
Values:
>=0
Completion The date/time when the service was completed, for example 10 SCU Warning Syntax error and charging point is ‘D’.
Timestamp delivered, transmitted, deleted, time expired.
11 SCU Severe Syntax error and charging point is ‘C’.
Serving Network where this is not the Sender). There must be 20 SCU Warning Value out of range and charging point
a UTC Time Offset Code associated with the timestamp. is ‘D’.
Note: local time is the local time at the location of the 21 SCU Severe Value out of range and charging point
chargeable subscriber. Where the location is not available, as is ‘C’.
in some call forwarding scenarios, this will be a notional
‘network local time’. 30 SCU Warning Mandatory associated item UTC Time
Offset Code missing and charging
Conditionality: point is ‘D’.
31 SCU Severe Mandatory associated item UTC Time
Format: Offset Code missing and charging
CCYYMMDDHHMMSS point is ‘C’.
Note: Within this timestamp the range for HHMMSS is 000000 200 SCU Severe Completion Timestamp before the
– 235959 commercial roaming start date (in
file.
Content This item identifies which timestamp represents the charging 10 Content Severe Syntax error and more than one
Charging Point point for this transaction. timestamp present within Content
Transaction Basic Info.
The item is only present where there is more than one
timestamp present within Content Transaction Basic Info. If 11 Content Warning Syntax error and only one timestamp
there is only one timestamp present then that is deemed to be present within Content Transaction
the charging point by default. Basic Info.
V36.4 Page 106 of 317


Code Level
Conditionality: 20 Content Severe Value out of range and more than one
Must be present within group Content Service Used where timestamp present within Content
more than one timestamp is present within group Content Transaction Basic Info.
21 Content Warning Value out of range and only one
Values: timestamp present within Content
1 Order Placed Timestamp Transaction Basic Info.
2 Requested Delivery Timestamp
3 Actual Delivery Timestamp 100 Content Severe Referenced timestamp not present
within associated group Content
Content A group giving information additional to the Content Provider 30 Content Warning Mandatory item Content Provider Id
Provider Name which identifies the Content Provider. Type missing within group.
The group may be repeated to give as many identifiers as are 31 Content Warning Mandatory item Content Provider
available to the Sender. The group may not be present where Identifier missing within group.
either only the Content Provider Name is known or the Content
Provider is the Sender.
The group when present must contain items Content Provider

Id Type and Content Provider Identifier.
Conditionality:
Present within group Serving Parties Information where
available.
Content An item identifying the type of Content Provider Identifier 10 Content Warning Syntax error.
Provider Id
Type Conditionality: 11 LCS Severe Syntax error
Content Provider 20 Content Warning Value out of range.
21 LCS Severe Value out of range.
Values:
V36.4 Page 107 of 317


Code Level
1 Name text representation,
for example Amazon, Interflora,Yahoo!
2 TADIG code see items Sender/Recipient
for example GBRVF, DEUD1
3 URL for example www.amazon.com
4 IP Address v4
5 IP Address v6
Content The item holds a unique identifier of the Content Provider. 10 Content Warning Syntax error.
Provider
Identifier The type of identifier is contained in the associated Content 100 Content Warning Item content does not match Content
Provider Id Type. Provider Id Type.
Conditionality: 101 LCS Severe Item content does not match Content
Mandatory within groups Provider Id Type.
Content Provider
Content This is the name of the Content Provider as it may appear on a 10 Content Severe Syntax error
Provider Name retail invoice, for example FT Market Watch. This name may
not be the same as the trading name, for example Financial 100 Content Severe Length greater than 24 characters.
Times, London.
Conditionality:
Mandatory within group Serving Parties Information
Values:
Limited to maximum 24 characters length
Content A group identifying the details of the actual transaction and 30 Content Severe Mandatory item Content Transaction
Service Used associated charges. Code missing within group.
The group must contain an occurrence of each of Content 31 Content Severe Mandatory item Content Transaction
Transaction Code, Content Transaction Type, Transaction Type missing within group.
Short Description and Transaction Identifier. All other items
and groups are conditionally present with one or more 32 Content Warning Mandatory item Transaction Short
occurrences of Charge Information. Description missing within group.
V36.4 Page 108 of 317


Code Level
Conditionality: 33 Content Severe Mandatory item Transaction Identifier

Mandatory within group Content Transaction. missing within group.
34 Content Severe Item Object Type missing within group

and ‘Pull’ Content Transaction Code
used within ‘Streaming’ Content
Transaction Type.
35 Content Severe Item Object Type missing within group

and ‘Pull’ Content Transaction Code
used within ‘Download’ Content
Transaction Type.
100 Content Severe Total Data Volume value does not

equal the sum of Data Volume
Incoming + Data Volume Outgoing
when all items are present within
group.
101 Content Warning Total Data Volume and either Data

Volume Incoming or Data Volume
Outgoing present within group.
102 Content Severe Neither of groups Charge Information

or Advised Charge Information present
within group.
103 Content Severe Conditional item Content Charging

Point missing and more than one
timestamp present within associated
group Content Transaction Basic Info.
Content Content Transaction represents the charging and transactional 30 Content Severe Mandatory group Content Transaction
Transaction details for delivery of content to a customer. Basic Info missing within group.
V36.4 Page 109 of 317


Code Level
Usage of this element is by bilateral agreement between the 31 Content Severe Mandatory group Charged Party
Sender and Recipient. Information missing within group.
The group consists of mandatory groups Content Transaction 32 Content Severe Mandatory group Serving Parties
Basic Info, Charged Party Information, Serving Parties Information missing within group.
Information and one or more occurrences of Content Service
Usage. Operator Specific Information may, optionally, be 33 Content Severe Mandatory group Content Service
present one or more times. Used missing within group.
Conditionality:
where none of the following are present: Mobile Originated
Call, Mobile Terminated Call, Supplementary Service
Event, Service Centre Usage, GPRS Call or Location
Service.
Content Content Transaction Basic Info provides the basic detail of 30 Content Severe No timestamp present within group.
Transaction when the Content Transaction was made and the result of the
Basic Info transaction. 31 Content Warning Item RAP File Sequence Number
missing and Content Transaction
Group must contain one timestamp. This can be of any type, previously received and rejected.
Order Placed Timestamp, Requested Delivery Timestamp, or
Actual Delivery Timestamp. 32 Content Warning Item RAP File Sequence Number
present and Content Transaction not
Conditionality: previously received and rejected.
Mandatory within Group Content Transaction.
33 Content Warning Item RAP File Sequence Number
present and TAP transfer batch being
resubmitted as corrected (having been
previously rejected with fatal error).
Content A code representing the service that has been used. 10 Content Severe Syntax error.
Transaction
Code Conditionality: 20 Content Severe Value out of range.
Mandatory within group Content Service Used.
V36.4 Page 110 of 317


Code Level
Values:
0 Goods
1 Email
2 Push
3 Pull
4 Trade
5 Banking
6 Online Application
7 Instant Messaging
Content The type of Content Transaction that has been used. The 10 Content Severe Syntax error.
Transaction value of this item is dependent on the value of Content
Type Transaction Code. 20 Content Severe Value out of range.
Conditionality:
Mandatory within Group Content Service Used.
Values:
0 Not applicable (i.e. none of the values below are
relevant)
1 Send (applicable to Email)
2 Retrieve (applicable to Email, Push, Pull, Online
Applications)
3 Storage (applicable to Email, Push, Pull, Online
Applications)
4 Buy (applicable to Goods, Trade)
5 Sell (applicable to Goods, Trade)
6 Pre-order (applicable to Goods)
7 Quote (applicable to Trade)
8 Message (applicable to Push, Pull)
9 Browse (applicable to Pull)
10 Combined Send/Retrieve (applicable to Email)
11 Streaming (applicable to Pull)
12 Download (applicable to Pull)
V36.4 Page 111 of 317


Code Level
13 Point to point (applicable to Instant Messaging)
14 Point to multipoint (applicable to Instant
Messaging)
15 Chat (applicable to Instant Messaging and
Online Appl.)
16 Presence Information (applicable to Instant
Messaging)
17 Online game (applicable to Online Appl.)
CSE The information downloaded by the CAMEL server. 10 Calls Warning Syntax error.
Information
Derivation:
GSM/UMTS item Free Format Data (See Annex C – CS
Domain Charging and PS Domain Charging).
Conditionality:
information has been downloaded.
Value:
Maximum 40 bytes, the value must be encoded in binary
hexadecimal format as received from the CAMEL Server
via the network, i.e. the data must not be modified in any
way.
Currency The Currency Conversion table consists of three mandatory 30 Acctng Fatal Mandatory item Exchange Rate Code
Conversion elements, an Exchange Rate Code, a Number Of Decimal missing within group.
Places and associated Exchange Rate. For each Chargeable
Item the Exchange Rate is quoted as a code which can be 31 Acctng Fatal Mandatory item Number Of Decimal
looked up within this table to obtain the appropriate exchange Places missing within group.
rate.
32 Acctng Fatal Mandatory item Exchange Rate
This table is used on a once-off basis and applies only to the missing within group.
transfer which contains it. A new table is sent with each
transfer. Codes are reusable from transfer to transfer. 33 Acctng Fatal More than one occurrence of group
with same Exchange Rate Code where
V36.4 Page 112 of 317


Code Level
Conditionality: Number Of Decimal Places and/or
At least one occurrence must be present within group Exchange Rate are not the same.
Accounting Information if one or more Charge is greater
than zero within the Transfer Batch, one occurrence being 34 Acctng Fatal More than one occurrence of group
present for each unique Exchange Rate Code used within with same Exchange Rate Code where
group Charge Information. Number Of Decimal Places and
Exchange Rate are the same (i.e.
duplicate Currency Conversion table
entry).
Customer Id An item identifying the type of associated Customer Identifier. 10 LCS Severe Syntax error.
Type
Conditionality: 20 LCS Severe Value out of range.
Tracking Customer Identification
Values:
1 MSISDN
2 IMSI
3 MIN (Mobile Identification Number)
4 IP Address v4
5 IP Address v6
6 Login Name for example ‘gcgGenComp’
7 Account Number for example ‘ACC00376’
8 E-mail Address for example
‘[email protected]’
where only values 1, 2 & 3 must be used within the group

Tracked Customer Identification.
Customer The item holds an identifier for the Charged Party. The 20 LCS Severe Value out of range and item is a
Identifier identifier may only be unique in conjunction with other MSISDN.
information within the Charged Party Information, for example
MIN & ESN, MSISDN & TADIG Code. 100 LCS Severe Item content does not match Customer
Id Type.
V36.4 Page 113 of 317


Code Level
The type of identifier is contained in the associated Customer
Id Type. 200 LCS Severe Item is an IMSI of a known network
operator and initial characters are
Conditionality: different from the network operator’s
Mandatory within groups MCC + MNC, or not as bilaterally
Tracking Customer Identification agreed
4.4 D
Code Level
Data A TAP Data Interchange must contain either a Transfer Batch,
Interchange where there is data available for transfer, or a Notification file
where there is no data available for transfer.
For technical reasons trailing characters may be present after

the group Data Interchange. Such characters should be
ignored. For more details see section 5 (Classification Of
Errors).
Data Volume The Data Volume Incoming identifies the number of incoming 10 GPRS Severe Syntax error.
Incoming octets (bytes) within an occurrence of GPRS Service Used or Content
Content Service Used.
20 GPRS Severe Value out of range.
Derivation: Content
GSM item dataVolumeGPRSDownlink (PS Domain
Charging – see Annex C).
For Wi-Fi usage items Acct-Input-Octets (RFC 2866 [22])
and Acct-Input-Gigawords (RFC 2869 [23]) converted into
octets.
Conditionality:
Mandatory within group GPRS Service Used.
Present within group Content Service Used when available.
V36.4 Page 114 of 317


Code Level
Values:
> or = 0 (zero)
Data Volume The Data VolumeOutgoing identifies the number of outgoing 10 GPRS Severe Syntax error.
Outgoing octets (bytes) within an occurrence of GPRS Service Used or Content
Content Service Used.
Derivation: Content
GSM item dataVolumeGPRSUplink (PS Domain Charging
– see Annex C).
For Wi-Fi usage items Acct-Output-Octets (RFC 2866 [22])
and Acct-Output-Gigawords (RFC 2869 [23]) converted into
octets.
Conditionality:
Mandatory within group GPRS Service Used.
Present within group Content Service Used when available.
Values:
> or = 0 (zero)
Default Call Indicates whether or not a CAMEL call encountered default 10 MOC Warning Syntax error.
Handling handling. MTC
Indicator GPRS
Derivation:
For non SMS GSM CAMEL calls: 20 MOC Warning Value out of range.
GSM item DefaultCallHandling (See Annex C – CS Domain MTC
Charging). GPRS
For non SMS GPRS CAMEL calls:
GSM item DefaultGPRS-Handling (See Annex C – PS
Domain Charging).
For all SMS CAMEL calls:
GSM item DefaultSMS-Handling (See Annex C – CS
Domain Charging and PS Domain Charging).
V36.4 Page 115 of 317


Code Level
Conditionality:
the call has invoked default call handling otherwise it must
not be present.
Values:
0 Continue the call
1 Release the call
Deposit The date/time when the message was deposited at the Service 10 SCU Warning Syntax error and charging point is ‘C’.
Timestamp Centre.
11 SCU Severe Syntax error and charging point is ‘D’.
Serving Network where this is not the Sender). There must be 20 SCU Warning Value out of range and charging point
a UTC Time Offset Code associated with the timestamp. is ‘C’.
Note that local time is the local time at the location of the 21 SCU Severe Value out of range and charging point
chargeable subscriber. Where the location is not available, as is ‘D’.
in some call forwarding scenarios, this will be a notional
‘network local time’. 30 SCU Warning Mandatory associated item UTC Time
Offset Code missing and charging
Conditionality: point is ‘C’.
31 SCU Severe Mandatory associated item UTC Time
Format: Offset Code missing and charging
CCYYMMDDHHMMSS point is ‘D’.
Note: Within this timestamp the range for HHMMSS is 000000 200 SCU Severe Deposit Timestamp before the
– 235959 commercial roaming start date (in
file.
Destination The Destination indicates the number dialled by the subscriber 39 MOC Severe Neither item Called Number nor item
(Called Number) or the SMSC Address in case of SMS usage Dialled Digits present within call and
V36.4 Page 116 of 317


Code Level
or in cases involving supplementary services such as call call does not represent an emergency
forwarding or transfer etc., the number to which the call is call (as defined in chapter 5.7).
routed.
40 MOC Severe Item Called Number contains only
The element contains additional optional information detailing country code and item Dialled Digits
the geographical destination of the call and, where available not present
and appropriate, Dialled Digits and SMS Destination Number.
41 MOC Severe Item Called Number not present and
Conditionality: item CAMEL Destination Number not
Must be present within group MO Basic Call Information present and call neither an
except where there is no number present on the air unsuccessful call attempt nor an
interface, for example emergency calls. emergency call (as defined in chapter
5.7).
42 MOC Severe Called Number not present and call

represents SMS usage.
43 MOC Severe Called Number contains CAMEL

Routing Number and Dialled Digits not
present.
Note: Error code 43 can only be raised
by HPMNs which have populated
CAMEL Routing Numbers in their
IR.21.
Note: Error codes 31, 32, 33, 34, and

May 2003).
Note: Error Codes 30, 37 & 38
2005).
Destination The network towards which the call or message is routed. 10 SCU Warning Syntax error.
Network MOC
Conditionality:
V36.4 Page 117 of 317


Code Level
Must be present within group MO Basic Call Information 20 SCU Warning Value out of range.
where optimal routing is used. MOC
Must be present within group SCU Basic Information where
available except where a short message has not been
delivered.
The full list of codes in use is given in PRD TD.13 [14].
Example
GBRCN
GBRVF
DEUD1
DEUD2
Dialled Digits The Dialled Digits item contains the actual digits as dialled by 10 MOC Severe Syntax error.
the subscriber, i.e. unmodified, in establishing a call. This will
contain ‘+’ and ‘#’ where appropriate. 20 MOC Severe Value out of range.
The Dialled Digits item should contain everything the 21 MOC Severe Contains CAMEL Routing Number.
subscriber has entered before the send button is pushed (for Note: Error code 21 can only be raised
example, pre-entered menu selections for voicemail). by HPMNs which have populated
CAMEL Routing Numbers in their
For emergency calls operators may optionally insert the digits IR.21.
‘112’ or their national emergency number into the Dialled
Digits.
Conditionality:
Must be present within group Destination when available
from the network.
If Called Number is not present then, in the case of either

unsuccessful call attempt or CAMEL call with presence of
CAMEL Destination Number, Dialled Digits must be
present.
If Dialled Digits is not available from the network then
V36.4 Page 118 of 317


Code Level
Called Number must be present.
Values:
Each digit is numeric (0-9) or
contains ‘+’, ‘*’ or ‘#’
Note: The network may translate a dialled * to A and a

dialled # to B. Where this is done then TAP must contain
the original values of * or # as actually dialled by the
subscriber.
Discount Discount Applied is one of Fixed Discount Value or Discount
Applied Rate.
Conditionality:
Mandatory within group Discounting.
Discount Code A code associated with the Discount Applied. 10 Calls Severe Syntax error.
Conditionality: 11 Acctng Fatal Syntax error.

Discounting 20 Acctng Fatal Value out of range.
Discount Information
102 Calls Severe Specified discount code was not
Values: defined in group Discount Applied.
Range 0 .. 99
200 Calls Severe Referenced discount is not in line with
roaming agreement.
Discount Information identifying any call level discounts given via a 30 Calls Severe Mandatory item Discount Code
Information discount agreement between the Sender and Recipient. missing within group.
A Discount Code must be present. Where the Discount Code 31 Calls Severe Item Discount Value missing within
refers to a Discount Rate then the Discount Value and group and Discount Code refers to a
Discountable Amount must also be present, where the Discount Rate.
Discount Code refers to a Fixed Discount Value then the
Discount Value and Discountable Amount must not be present. 32 Calls Severe Item Discountable Amount missing
V36.4 Page 119 of 317


Code Level
within group and Discount Code refers
Conditionality: to a Discount Rate.
Must be present within group Charge Information where
discounts have been applied to the Charge Information.

discounts have been applied to the CAMEL Invocation Fee.
Discount Rate The rate of discount applied to Charge Information where a 10 Acctng Fatal Syntax error.
percentage discount was applied as opposed to a fixed
discount. 20 Acctng Fatal Value out of range.
The rate is held to 2 decimal places.
Conditionality:
Mandatory where no Fixed Discount Value present within
group Discount Applied.
Values:
0.00 thru 100.00
Discount Value The actual value of a discount element applicable to Charge 10 Calls Severe Syntax error.
Information where that discount is not a Fixed Discount Value.
The Discount Value must be a positive value, i.e. greater than
zero. 22 Calls Severe Where the associated Discount Code
relates to a Discount Rate, the
The value is in SDRs with the number of decimal places Discount Value does not correspond to
defined by item TAP Decimal Places. Note the currency may the Discountable Amount and Discount
be subject to internal market bilateral agreements, see TAP Rate.
Currency. Note: Rounding rules are at the
Conditionality: tolerance of 0.02 units of TAP
Must be present within group Discount Information where Currency must be allowed
the Discount Code refers to a Discount Rate. (independent of the number of TAP
decimal places used for the TAP file).
V36.4 Page 120 of 317


Code Level
Values: Note: No tolerance is allowed when
> 0 (zero) the expected Discount Value is zero.
Discountable The actual part of the Charge/Tax/CAMEL Invocation Fee to 10 Calls Severe Syntax error.
Amount which the Discount Value and Discount Rate (Code) relate.
The Discountable Amount must have a value greater than
zero. 22 Calls Severe Discountable Amount is not in line with
roaming agreement.
defined by TAP Decimal Places. Note that the currency may
be subject to internal market bilateral agreements, see TAP
Currency.
The Discountable Amount may include sum of all tax values,

charges and CAMEL invocation fees or any part thereof.
Conditionality:
Must be present within group Discount Information where
the associated Discount Code relates to a Discount Rate.
Values:
> 0 (zero)
Discounting A table containing discount information where the discount is 30 Acctng Fatal Mandatory group Discount Applied
applied at call level, as defined by a discount agreement missing within group.
between the Sender and Recipient.
31 Acctng Fatal Mandatory item Discount Code
transfer. Codes are reusable from transfer to transfer. 32 Acctng Fatal More than one occurrence of group
with same Discount Code where group
Conditionality: Discount Applied is not the same.
Mandatory within group Accounting Information where
group Discount Information is present within Charge 33 Acctng Fatal More than one occurrence of group
Information. One occurrence must be present for each with same Discount Code where group
V36.4 Page 121 of 317


Code Level
unique Discount Code used within group Discount Discount Applied is the same (i.e.
Information. duplicate Discounting table entry).
Distance A code corresponding to a group of countries where a specific 10 SCU Severe Syntax error.
Charge Band tariff is applied.
Code 20 SCU Severe Value out of range.
The correspondence between a value and a specific group of
countries, and hence tariff, is defined by the Sender PMN.
The list of the countries for each area must be defined by the
charging operator and specified in the SMS bilateral
agreement.
Conditionality:
Must be present within group SCU Charge Type where
distance has been a parameter used to calculate the
Charge.
Values:
A Area A
B Area B
C Area C
etc.
4.5 E
Code Level
Earliest Call The Earliest Call Timestamp is, as it implies, the earliest start 10 Audit Warning Syntax error.
Timestamp of charging timestamp on any record. It is not necessarily the
start of charging timestamp of the first charge record on the 20 Audit Warning Value out of range.
file.
The timestamp contains the same timestamp as that of the 30 Audit Warning Mandatory associated item UTC Time
earliest Call Event Details when all times have been Offset missing.
normalised to UTC time.
100 Audit Warning The timestamp does not match the
V36.4 Page 122 of 317


Code Level
Where the batch contains SCU records either the completion timestamp of the earliest Call Event
or deposit timestamp must be taken into account according to Detail Timestamp.
the charging point value.
When the batch contains Content Transaction call/events the

Content Charging Point value must be taken into account if
more than one of Order Placed Timestamp, Requested
Delivery Timestamp or Actual Delivery Timestamp are present
in the call/event. If only a single timestamp is present then this
is taken as the charging point.
If a Content Transaction contains more than one Content

Charging Point then the earliest timestamp referenced must be
used to derive the Earliest Call Timestamp.
When the batch contains Messaging Event or Mobile Session

call/events the Service Start Timestamp value must be taken
into account.
Timestamps from calls with severe errors must also be taken

into account if possible i.e. no type 10 or 20 errors occurred in
the timestamp field
The time is given in the local time of the Sender (or Serving
Network where this is not the Sender). There must be a UTC
Time Offset associated with the timestamp.
Optionality:
Conditionality:
Mandatory within group Audit Control Information subject to
optionality.
Format:
V36.4 Page 123 of 317


Code Level
CCYYMMDDHHMMSS

– 235959
Element ID The identification of the network element which enables the 10 MSG Severe Syntax Error
Messaging Event.
Derivation:
For SMSC (See Annex C – CS Domain Charging and PS
Domain Charging) (Msisdn).
For S-CSCF and SM-IP-GW (see Annex C - SMS
Charging) (ipv4 or ipv6 address)
Conditionality
Mandatory within group Network Element
Element Type The item identifying the type of network element. 10 MSG Severe Syntax error.
Conditionality: 20 MSG Severe Value out of range

Mandatory within group Network Element.
Values:
SMSC (Short Message Service Centre)
S-CSCF (Serving Call Session Control Function)
SM-IP-GW (Short Message IP Gateway)
Equipment Id An item that uniquely identifies the equipment used by the 10 Content Warning Syntax error.
Charged Party.
100 Content Warning Item content does not match
The type of identifier is contained in the associated Equipment LCS Equipment Id Type.
Id Type.
Conditionality:
V36.4 Page 124 of 317


Code Level
Charged Party Equipment
Tracked Customer Equipment.
Equipment Id An item representing the type of Equipment Id. 10 Content Warning Syntax error.
Type LCS
Conditionality:
Mandatory within groups 20 Content Warning Value out of range.
Charged Party Equipment. LCS
Tracked Customer Equipment
Values:
0 IMEI
1 ESN
Equipment A conditional group element which identifies the equipment
Identifier used. The information present must be one of either IMEI or
ESN.
Conditionality:
Supplementary Service Event
GPRS Call
where available from the network.
ESN The Electronic Serial Number. The identifier which uniquely 10 MOC Warning Syntax error.
identifies the equipment used by the subscriber during the call. MTC
SS
This is a non GSM equipment identifier. GPRS
Derivation: 20 MOC Warning Value out of range.

CIBER manual v2.0 section 12 [9]. MTC
SS
Conditionality: GPRS
V36.4 Page 125 of 317


Code Level
Must be present within group Equipment Identifier where
available. Will not be present where the terminal equipment
is not involved in the call for example in forwarded call
cases or the mobile equipment is identified by an IMEI.
Event The Event Reference uniquely identifies a particular mobile 10 MSESS Severe Syntax error.
Reference session or messaging event, for example initiated by a SIP MSG
invitation. A single multimedia conference can give rise to
several mobile sessions with different Event references, for
example, if a user invites a single individual several times to
the same (long-running) conference.
Derivation:
IMS item IMS Charging Identifier
See Annex C - IMS Charging Domain
Note: for non IMS services (future use) the Event
Reference needs to be defined on a case by case basis.
Conditionality:
Mobile Session
Messaging Event
Exchange Rate The Exchange Rate is the exchange rate expressed as the 10 Acctng Fatal Syntax error
number of units of Local Currency to one unit of the currency
used in the TAP file. Note that, while SDR is usually the 200 Acctng Fatal Exchange Rate less than expected
currency used in the TAP file, the currency may be different (see BA.11 [11]) and applied to one or
based on bilateral agreement and, where so agreed, will be more Charges and at least one of the
indicated by the currency code in the TAP Currency element, Charges the Exchange Rate is applied
see TAP Currency. For information on how exchange rates are to is greater than zero.
calculated see PRD BA.11 [11][11].
201 Acctng Fatal Exchange Rate higher than expected
BA.11 [11] also defines what currencies are officially published (see BA.11 [11]) and applied to one or
by the GSER (GSMA Standardised Exchange Rates) tool, more Charges.
including launch dates for each currency.
Note 1: For all currencies not
V36.4 Page 126 of 317


Code Level
The number of decimal places present is indicated by the published by GSER: A tolerance of 2
associated Number Of Decimal Places item. units must be allowed on the 5th
A minimum of 5 significant digits must be present in TAP significant digit on the calculated
except where the TAP Currency is the same as the Local exchange rate.
Currency. Note 2: For all currencies published
by GSER: To allow for cases where
Note: If the full number of significant digits as published in rounding could be applied by the
accordance with BA.11 [11] cannot be supported by the Sender, the Recipient must allow for a
Sender, it is allowed to round to the number of significant digits tolerance to support the fact that the
that the Sender can support. It is allowed both to round up or Sender can round either up or down to
down to the nearest value that can be defined using a the number of significant digits it can
minimum of 5 significant digits. If the Sender is able to support support in TAP (see examples). At a
all significant digits as published, it must of course populate all minimum 5 significant digits must be
significant digits in TAP. present in TAP.
Note 3: The rule for Exchange Rate
If the published value already contains only 5 significant digits higher than expected applies even
or even less, no rounding must be applied by the Sender where a charge is zero (0) as an
(trailing zeros are not significant). Exchange Rate higher than expected
can result in a Charge of zero due to
Examples: rounding during rating.
0.112233 can be rounded to 0.11223 or 0.11224.
Note 1 and Note 2 are applicable to
123.456000 can be rounded to 123.45 or 123.46.
both Exchange Rate less than and
123.450000 must not be rounded, as it already contains only higher than expected validation (error
5 significant digits (123.45). codes 200 & 201).
123.400000 must not be rounded, as it already contains only
4 significant digits (123.4).
Conditionality:
Mandatory within group Currency Conversion.
Exchange Rate A code associated with an Exchange Rate. 10 Acctng Fatal Syntax error.
Code
In order to calculate the SDR value in TAP the local currency is 11 Calls Severe Syntax error
divided by the exchange rate.
V36.4 Page 127 of 317


Code Level
20 Acctng Fatal Value out of range.
In case the amount of local currency is divided by an exchange
rate holding a lower value (i.e. the exchange rate is less than 101 Calls Severe Specified Exchange Rate Code not
expected). The SDR amount will be higher and the VPMN defined in group Currency Conversion.
actually overcharge the HPMN, especially if netting is in place.
In case the amount of local currency is divided by an exchange Note: Error code 200 removed in TAP
rate holding a higher value (i.e. the exchange rate is greater release 3.11 (01 May 2005).
than expected). The SDR amount will be lower and the VPMN
actually undercharge the HPMN, especially if netting is in Note: Error code 202 removed in TAP
place. release 3.12 (01 May 2016).
Conditionality:
Must be present within group Charge Information and
Session Charge Information where a Charge greater than
zero is present within any Charge Detail associated with the
same Charge Information.
the CAMEL Invocation Fee is greater than 0 (zero).
Must be present within group Messaging Event where the
Charge is greater than 0 (zero).
Must be present within group Aggregated Usage Record
when Aggregated Usage Charge is greater than zero.
Values:
Range 0 .. 99
V36.4 Page 128 of 317

4.6 F
Code Level
File Available The date and time at which the file was made available to the 10 Btch Ctrl Fatal Syntax error.
Timestamp Recipient PMN. Note: Where the Sender uses an agent for
file transfer, this is the date and time the agent makes the file 11 Notifictn Warning Syntax error.
available to the Recipient or the Recipient’s agent.
20 Btch Ctrl Fatal Value out of range.
Physically this will normally be the timestamp when the file
transfer commenced to the Recipient PMN, i.e. start of push, 21 Notifictn Warning Value out of range.
however on some systems this will be the timestamp when the
file was made available to be pulled. 30 Btch Ctrl Fatal Mandatory associated item UTC Time
Offset missing.
The time is given in the local time of the Sender PMN. There
must be a UTC Time Offset associated with the item. Note: 31 Notifictn Warning Mandatory associated item UTC Time
Where the Sender uses an agent for file transfer, the Offset missing.
Timestamp and the UTC Time Offset could be that of the
agent. 100 Btch Ctrl Fatal Timestamp is earlier than the Transfer
Cut Off Timestamp.
Note that where a file is being resubmitted, for example where
the file contained a fatal error on earlier submission, this 101 Btch Ctrl Warning Timestamp is earlier than the File
timestamp must not contain the original timestamp, i.e. the Creation Timestamp.
item contains the timestamp when the file was made available
on resubmission. 102 Notifictn Warning Timestamp is earlier than the Transfer
Cut Off Timestamp.
Conditionality:
Mandatory within groups 103 Notifictn Warning Timestamp is earlier than the File
Batch Control Information Creation Timestamp.
Notification
104 Btch Ctrl Fatal Timestamp is more than one hour after
Format: the file received time at the HPMN.
CCYYMMDDHHMMSS Note: The tolerance of one hour has
been introduced as it cannot be
Note: Within this timestamp the range for HHMMSS is 000000 guaranteed that Sender and Recipient
– 235959 system clocks are synchronised, in
particular around daylight saving
V36.4 Page 129 of 317


Code Level
(wintertime/summertime) changes.
105 Notifictn Warning Timestamp is after the file received

time at the HPMN
File Creation The timestamp at which the TAP file was created. 10 Notifictn Warning Syntax error.
Timestamp Btch Ctrl
must be a UTC Time Offset associated with the item. 20 Notifictn Warning Value out of range.
Btch Ctrl
Optionality:
Senders may choose not to supply this information. 30 Notifictn Warning Mandatory associated item UTC Time
Btch Ctrl Offset missing.
Conditionality:
Mandatory within groups 100 Notifictn Warning Timestamp is earlier than the Transfer
Notification Btch Ctrl Cut Off Timestamp.
Batch Control Information
subject to optionality.
Format:
CCYYMMDDHHMMSS

– 235959
File Sequence A unique reference which identifies each TAP Data 10 Notifictn Fatal Syntax error.
Number Interchange sent by one PMN to another, specific, PMN. Btch Ctrl
The sequence commences at 1 and is incremented by one for 20 Notifictn Fatal Value out of range.
each subsequent TAP Data Interchange sent by the Sender Btch Ctrl
PMN to a particular Recipient PMN.
100 Notifictn Fatal The item does not match the File
Separate sequence numbering must be used for Test Data and Btch Ctrl Sequence Number on the filename.
Chargeable Data. Having reached the maximum value
(99999) the number must recycle to 1. 200 Notifictn Warning File sequence number of the received
Btch Ctrl file is greater than that expected
V36.4 Page 130 of 317


Code Level
Note that in the case of retransmission for any reason this
number is not incremented. 201 Notifictn Fatal File sequence number of the received
Btch Ctrl file has already been received and
Note that where the file sequence number is being reused with successfully processed and the file is
a file already received and successfully processed and the not a copy of the original file.
content of the two files is different, then the received file is to Note: This error can also be raised if
be considered as ‘invalid reused sequence number’ and the original file details are not available
rejected using the RAP process. Where the content of the two (for example DCH migration scenario).
files is the same then the file is to be considered as a ‘copy’ of
the original file and should be ignored (i.e. not rejected).
Conditionality:
Notification
Batch Control Information.
Range:
00001 – 99999 for Test Data
00001 – 99999 for Chargeable Data
File Type Indicates the type of data contained within the file, i.e. test or 10 Btch Ctrl Fatal Syntax error.
Indicator chargeable data. Notifictn
Note: Some values are reserved for proprietary use on internal 20 Btch Ctrl Fatal Value out of range.
interfaces; these values are considered out of range unless Notifictn
bilateral usage is agreed.
Conditionality:
Notification
where the file represents test data only, not present where
the data is ‘live’ chargeable data.
Values:
V36.4 Page 131 of 317


Code Level
T Test Data
[Values B, H, S and V are reserved for proprietary use]
Fixed Discount The value of a fixed discount applied to a Call Event Details. 10 Acctng Fatal Syntax error.
Value
The Fixed Discount Value must contain a positive value. 20 Acctng Fatal Value out of range.

defined by item TAP Decimal Places. Note the currency may
Currency.
Conditionality:
Mandatory where no Discount Rate present within Discount
Applied.
Values:
> 0 (zero)
Fixed Network The Fixed Network (for example PSPDN) User Rate. 10 MOC Warning Syntax error.
User Rate MTC
Derivation:
Bearer Capability Element, octet 6d, (See Annex C – CS 20 MOC Warning Value out of range.
Domain Charging). MTC
The value is derived by interpreting the 5 least significant bits

of octet 6d as a binary number and converting it into an
integer.
Conditionality:
Must be present within group Basic Service where a
General Bearer Service has been invoked except where
the item is not applicable, i.e. value is zero (0) or not
available.
Values:
V36.4 Page 132 of 317


Code Level
1 9.6 kbits per second
6 48 kbits per second
4.7 G
Code Level
Geographical Identifies the Geographical Location of the terminal equipment. 30 MOC Warning Item Serving Location Description is
Location MTC not present and Serving BID is present
All of the information within the group is optional (except for SS within group.
Wi-Fi usage as described under Conditionality below) and may GPRS
not be available where the terminal was not involved in the call, MSG
for example call forwarding scenarios. MSESS
Operators may bilaterally agree to make transfer of Serving 31 MOC Severe Serving BID missing within group but
BID and/or Serving Location Description mandatory. MTC expected in accordance with roaming
Exchange of the Serving Network element requires bilateral SS agreement.
agreement. GPRS
MSG
Must be present within group Location Information if the
call involves the terminal equipment or if the Serving 32 MOC Severe Serving Location Description missing
Network is different from the Sender. MTC within group but expected in
SS accordance with roaming agreement.
Must be present within group GPRS Location Information GPRS
where available or if the Serving Network is different from MSG
the Sender. MSESS
V36.4 Page 133 of 317


Code Level
33 GPRS Severe Item Serving Location Description not
present for Wi-Fi usage.
Must be present within group GPRS Location Information
for Wi-Fi usage.
34 MOC Severe Serving Network element present and
MTC its exchange not bilaterally agreed.
Must be present within group Messaging Event where
SS
available or if the Serving Network is different from the
GPRS
Sender.
MSG
MSESS
Must be present within group Mobile Session where
available or if the Serving Network is different from the
Sender.
GPRS Basic GPRS Basic Call Information provides the basic detail to 30 GPRS Severe Mandatory group GPRS Chargeable
Call identify the chargeable subscriber together with other core Subscriber missing within group.
Information information.
31 GPRS Warning Item RAP File Sequence Number is
It comprises mandatory GPRS Chargeable Subscriber, GPRS missing and GPRS Call previously
Destination, Call Event Start Timestamp, Total Call Event received and rejected.
Duration and Charging Id details together with conditional RAP
File Sequence Number, Network Init. PDP Context, Partial 32 GPRS Severe Mandatory group GPRS Destination
Type Indicator and Cause For Termination information. missing within group.
Conditionality: 33 GPRS Severe Mandatory item Call Event Start

Mandatory within group GPRS Call. Timestamp missing within group.
34 GPRS Severe Mandatory item Total Call Event

Duration missing within group.
35 GPRS Severe Mandatory item Charging Id missing

within group.
38 GPRS Warning Item RAP File Sequence Number

V36.4 Page 134 of 317


Code Level
41 GPRS Warning Item RAP File Sequence Number

present and call not previously
received and rejected.
42 GPRS Warning Item Network Init. PDP Context

present within group for Wi-Fi usage.
43 GPRS Severe Item Partial Type Indicator present

within group for Wi-Fi usage.
Note: Error codes 36 & 37 removed in

GPRS Call GPRS Call is used to represent packet switched service 31 GPRS Severe Mandatory group GPRS Basic Call
usage. It consists of the mandatory information GPRS Basic Information missing within group.
Call Information, GPRS Location Information, and GPRS
Service Used. Equipment Identifier will be present where 32 GPRS Severe Mandatory group GPRS Location
available. Optionally Operator Specific Information may be Information missing within group.
supplied.
34 GPRS Severe Mandatory group GPRS Service Used
This call event is also used for Wi-Fi usage. missing within group.
Where CAMEL services are supported and invoked then one 200 GPRS Warning Number of GPRS partials received
occurrence of CAMEL Service Used will be present for the exceeds limit defined in BA.12 [12].
invocation.
Note: Error codes 30, 35 & 201
Conditionality: removed in TAP release 3.11 (01 May
Mandatory within an occurrence of group Call Event Details 2005).
where none of the following is present; Mobile Originated
Event, Service Centre Usage, Content Transaction or
Location Service.
V36.4 Page 135 of 317


Code Level
GPRS Identifies the chargeable subscriber for the use of GPRS. 30 GPRS Severe Item Chargeable Subscriber missing
Chargeable within group and the GPRS Call does
Subscriber Group Chargeable Subscriber and items PDP Address and not representWi-Fi usage.
Network Access Identifier are all conditional.
32 GPRS Warning Item PDP Address missing within
For packet switched data usage (except Wi-Fi) group group and GPRS Call does not
Chargeable Subscriber and item PDP Address must be represent Wi-Fi usage.
present.
34 GPRS Severe Neither item Network Access Identifier
For Wi-Fi usage one of either group Chargeable Subscriber or nor group Chargeable Subscriber
item Network Access Identifier must be present. Item PDP present within group.
Address is not present.
35 GPRS Severe Item Network Access Identifier present
Conditionality: within group and the GPRS Call does
Mandatory within group GPRS Basic Call Information. not representWi-Fi usage.

GPRS Identifies the Access Point Name (Network Identifier and 30 GPRS Severe Mandatory item Access Point Name NI
Destination Operator Identifier parts). missing within group.
Within GPRS Basic Call Information this item must always 31 GPRS Warning Item Access Point Name OI missing
contain the actual connected APN. within group. Note, this validation is
only applicable where the serving
In case of CAMEL invocation an additional instance of GPRS network has upgraded to at least GSM
Destination may be present within group CAMEL Service Release ’98.
Used. Where relevant it must be populated with the original Note that this validation is not
APN as entered by the customer where it is available from the applicable to Wi-Fi usage.
network.
32 GPRS Warning Item Access Point Name OI present
Conditionality: within group for Wi-Fi usage.
Mandatory within group GPRS Basic Call Information.
34 GPRS Warning Mandatory item Access Point Name NI
Must be present within group CAMEL Service Used where missing within group where it occurs
V36.4 Page 136 of 317


Code Level
the GPRS Destination has been modified by the CAMEL within group 3G CAMEL Destination.
server and where it is available from the network.
Note: Error code 33 removed in TAP
release 3.11 (01 May 2005).
GPRS The GPRS Location Information identifies the GPRS Network 30 GPRS Severe Mandatory group GPRS Network
Location Location, where appropriate, the Geographical Location and, Location missing within group.
Information optionally, the Home Location Information.
31 GPRS Severe Group Geographical Location missing
Conditionality: for Wi-Fi usage.
Mandatory within group GPRS Call.
but Serving BID expected in
accordance with roaming agreement.
This validation rule can be applied only
where bilaterally agreed between
Sender and Recipient.

but Serving Location Description
expected in accordance with roaming
agreement.
GPRS Network Identifies the mandatory GGSN/P-GW Address and SGSN/S- 31 GPRS Severe More than one Recording Entity Code
Location GW Address(es) using Recording Entity Codes (see Recording is of type GGSN present within group.
Entity Code). Location Area Code is present where available
and Cell Identity is optionally present when available. 32 GPRS Severe No Recording Entity Code of type
GGSN and no Recording Entity Code
For Wi-Fi usage this group will contain one Recording Entity of type P-GW present within group and
Code for the Wi-Fi billing information recording entity. not Wi-Fi usage.
Conditionality: 33 GPRS Severe No Recording Entity Code of type

Mandatory within group GPRS Location Information. SGSN and no Recording Entity Code
V36.4 Page 137 of 317


Code Level
of type S-GW present within group and
not Wi-Fi usage.
34 GPRS Severe For Wi-Fi usage, no Recording Entity

Code of type Wi-Fi billing information
recording entity present within group.
35 GPRS Severe For Wi-Fi usage, more than one

Recording Entity Code present within
group.
36 GPRS Warning For Wi-Fi usage, item Location Area

Code present within group.
37 GPRS Warning For Wi-Fi usage,item Cell Identity

present within group.
38 GPRS Severe Location Area Code missing within

roaming agreement.
Note: This error cannot be raised for
Wi-Fi usage.
39 GPRS Severe More than one Recording Entity Code

is of type P-GW present within group.
40 GPRS Severe Recording Entity Codes of type GGSN

and P-GW present within group.
GPRS Service The GPRS Service Used group identifies the Data Volume 32 GPRS Severe Mandatory group Charge Information
Used Incoming and Outgoing together with Charging Information. missing within group.
Presence of the IMS Signalling Context will identify where the
context represents IMS signalling only. 33 GPRS Severe Mandatory item Data Volume Incoming
Conditionality:
V36.4 Page 138 of 317


Code Level
Mandatory within group GPRS Call. 34 GPRS Severe Mandatory item Data Volume Outgoing

release 3.11 (01 May 2005).
GSM A group containing IMSI and/or MSISDN details of the SCU 30 SCU Severe Neither IMSI or MSISDN present within
Chargeable Chargeable Subscriber. group.
Subscriber
The group must contain either one of IMSI or MSISDN but it
will contain both where they are both available.
Conditionality:
Must be present within group SCU Chargeable Subscriber
where MIN is not present.
Guaranteed Bit Describes the bitrate the UMTS bearer service must guarantee 10 MOC Severe Syntax Error.
Rate to the user or application for circuit switched UMTS. MTC
Derivation: 20 MOC Severe Value out of range.

Item Guaranteed Bit Rate, see Annex C – CS Domain MTC
Charging.
Conditionality:
Mandatory within group Basic Service where available from
the network.
Values:
1 14400bps
2 28800bps
3 32000bps
4 33600bps
5 56000bps
6 57600bps
7 64000bps
V36.4 Page 139 of 317

4.8 H
Code Level
Home BID The Home BID (Billing Identifier) is a code identifying the home 10 Calls Warning Syntax error.
market area of the Chargeable Subscriber.
20 Calls Warning Value out of range.
Derivation:
CIBER manual v2.0 section 12 [9].
Conditionality:
Mandatory within group Home Location Information.
Optional within group Charged Party at the discretion of the
Sender PMN.
Home Id Type This item gives the type of Home Identifier associated with it. 10 Content Severe Syntax error.
LCS
Conditionality:
Mandatory within groups 20 Content Severe Value out of range.
Charged Party Home Identification LCS
Tracked Customer Home Id.
Values:
1 Name Text representation, for example BT,
Telecom Italia, Commerzbank
2 TADIG Code See item Sender or Recipient, for
example GBRVF, DEUD1
3 Home BID See item Home BID
4 Home See item Home Location Description.
Location
Description
Home The item holds a unique identifier of the Charged Party’s 10 Content Severe Syntax error.
Identifier Home. This may be, for example, a mobile network, fixed
network, banking institution etc. 100 Content Severe Item content does not match Home Id
LCS Type.
The type of identifier is contained in the associated Home Id
Type.
V36.4 Page 140 of 317


Code Level
Conditionality:
Charged Party Home Identification
Tracked Customer Home Id.
Home Location A text description giving the home market area of the 10 Calls Warning Syntax error.
Description Chargeable Subscriber.
Derivation:
Conditionality:
Mandatory within group Home Location Information.
Optional within group Charged Party at the discretion of the
Sender PMN.
Home Location Home Location Information is an optional group which, when 30 Call Warning Mandatory item Home BID missing
Information present must contain a Home BID and Home Location within group.
Description.
31 Call Warning Mandatory item Home Location
Optionality: Description missing within group.
Optional within groups
GPRS Location Information
at the discretion of the Sender PMN.
Horizontal The horizontal accuracy delivered for an LCS request 20 LCS Severe Value out of range.
Accuracy measured in metres. Note: This error can only be raised for
Delivered TAP files made available on or after 24
Derivation: May 2012.
GSM/UMTS item Ext-GeographicalInformation (See Annex
C – LCS Charging). The contents of the first 4 bits of the
first octet indicate the type of shape used for the
determination of the position. Dependant on the shape
actually used the horizontal uncertainty has to be extracted
V36.4 Page 141 of 317


Code Level
from the remaining octets and has to be translated into a
value in metres using the standards formulae, see Annex C
– LCS Charging. The result must be rounded to full metres.
Conditionality:
Must be present within group
LCS QoS Delivered
Values:
>=0 (zero)
Horizontal The horizontal accuracy requested for an LCS request 20 LCS Severe Value out of range.
Accuracy measured in metres. Note: This error can only be raised for
Requested TAP files made available on or after 24
Derivation: May 2012.
LCS QoS IE Octet 4 (See Annex C – LCS Charging). The
7 least significant bits of octet 4 need to be interpreted as
an uncertainty code. This needs to be transformed into a
value in metres by applying the standards formulae, see
Annex C – LCS Charging. The result must be rounded to
full metres.
Conditionality:
LCS QoS Requested
Values:
>=0 (zero)
HSCSD This indicator, set by the VPMN and passed to the Recipient, 10 MOC Severe Syntax error.
Indicator indicates that HSCSD has been used. MTC
Conditionality: 20 MOC Severe Value out of range.

Must be present within group Basic Service Used where MTC
V36.4 Page 142 of 317


Code Level
HSCSD has been used, otherwise not present.
Values:
1 HSCSD used
4.9 I
Code Level
IMEI The International Mobile Equipment Identity number. The 10 MOC Warning Syntax error.
identifier which uniquely identifies the equipment used by the MTC
subscriber during the call. SS
GPRS
Derivation: MSESS
GSM item IMEI (See Annex C – CS Domain Charging and MSG
PS Domain Charging).
20 MOC Warning Value out of range.
Conditionality: MTC
Must be present within the following groups where SS
available: GPRS
Equipment Identifier MSESS
Charged Party MSG
Will not be present where the terminal equipment is not
involved in the call for example in forwarded call cases or
the mobile equipment is identified by an ESN.
Note: While the IMEI is 16 digits in length, the check digit is

not currently transmitted on the “air interface”.
IMS Signalling Where the GPRS context represents IMS signalling this 10 GPRS Severe Syntax error.
Context identifier will be present.
The item will not be present on the network CDR where the
context is mixed IMS signalling and customer generated data
volume exchange. The item will only be present on the network
V36.4 Page 143 of 317


Code Level
CDR where the context is representing solely IMS signalling
usage.
When the item is present on the CDR it is present as a null

item.
Derivation:
Item IMS Signalling Context, defined from R5 onwards (PS
Domain Charging – see Annex C).
Conditionality:
Mandatory within group GPRS Service Used where
Values:
GPRS CDR Value TAP Value
null 1
IMSI The identifier which uniquely identifies the subscriber who has 10 Calls Severe Syntax error.
used the network and is liable for any charges that may be
incurred. 20 Calls Severe Value out of range.
Note: This error can also be raised if
For Wi-Fi usage, if the identification of the subscriber is with the length of the IMSI is not as
Network Access Identifier or the MSISDN, this item, where expected by the HPMN
present, must contain characters equal to the Home PMN’s
MCC+MNC or the full IMSI if available. 200 Calls Severe First characters are different from
home operators MCC + MNC, or not
If the recipient has not been allocated a MCC and MNC (for as bilaterally agreed (for example, if
example, is not a GSM operator), this field, where present, is the recipient has not been allocated a
defined bilaterally between sender and recipient. MCC and MNC).
Derivation:
GSM item servedIMSI (See Annex C – CS Domain
Charging and PS Domain Charging).
V36.4 Page 144 of 317


Code Level
Conditionality:
Mandatory within group SIM Chargeable Subscriber.
Must be present within group GSM Chargeable Subscriber
when available.
Must be present for Wi-Fi usage when the IMSI is used for
identifying the chargeable user.
Must be present within group Charged Party.
Internet Where an Internet Service Provider (ISP) has been used to 30 Content Warning Mandatory item ISP Id Type missing
Service access the service, i.e. initiate the Content Transaction, then within group.
Provider this repeating group contains identifying information.
31 Content Warning Mandatory item ISP Identifier missing
Conditionality: within group.
Serving Parties Information 32 LCS Severe Mandatory item ISP Id Type missing
LCS SP Information within group.
where available.
33 LCS Severe Mandatory item ISP Identifier missing
within group.
ISP Id Type This item gives the type of Internet Service Provider (ISP) 10 Content Warning Syntax error.
Identifier associated with it.
20 Content Warning Value out of range.
Conditionality:
Mandatory within group Internet Service Provider. 21 LCS Severe Value out of range.
Values:
1 Name Text representation, for example
AOL, Vizzavi
3 URL For example www.aol.co.uk ,
www.vizzavi.co.uk
4 IP address v4
5 IP address v6
ISP Identifier The item holds a unique identifier of the Internet Service 10 Content Warning Syntax error.
V36.4 Page 145 of 317


Code Level
Provider (ISP).
100 Content Warning Item content does not match ISP Id
The type of identifier is contained in the associated ISP Id Type.
Type.
101 LCS Severe Item content does not match ISP Id
Conditionality: Type.
Mandatory within group Internet Service Provider.
4.10 L
Code Level
Latest Call The Latest Call Timestamp is, as it implies, the Latest start of 10 Audit Warning Syntax error.
Timestamp charging timestamp on any record. It is not necessarily the
start of charging timestamp of the last charge record on the 20 Audit Warning Value out of range.
file.
30 Audit Warning Mandatory associated item UTC Time
The timestamp contains the same timestamp as that of the Offset missing.
latest Call Event Details when all times have been normalised
to UTC time. 100 Audit Warning The timestamp does not match the
timestamp of the latest Call Event
In case the batch contains SCU records either the completion Detail Timestamp.
or deposit timestamp should be taken into account according
to the charging point value.
When the batch contains Content Transaction call/events the

Content Charging Point value must be taken into account if
more than one of Order Placed Timestamp, Requested
Delivery Timestamp or Actual Delivery Timestamp are present
in the call/event. If only a single timestamp is present then this
is taken as the charging point.
V36.4 Page 146 of 317


Code Level
If a Content Transaction contains more than one Content
Charging Point then the latest timestamp referenced must be
used to derive the Latest Call Timestamp.
When the batch contains Messaging Event or Mobile Session

call/events the Service Start Timestamp value must be taken
into account.
Timestamps from calls with severe errors should also be taken

into account if possible i.e. no 10 or 20 type error occurred in
the record
The time is given in the local time of the Sender (or Serving
Network where this is not the Sender). There must be a UTC
Time Offset associated with the timestamp.
Optionality:
Conditionality:
Mandatory within group Audit Control Information subject to
optionality.
Format:
CCYYMMDDHHMMSS

– 235959
LCS QoS The group identifies the quality of service delivered where it is 30 LCS Severe Item LCS Transaction Status present
Delivered different from the quality of service requested, as identified in and no other items present within
group LCS QoS Requested. group.
All of the items within the group are subject to conditionality. 31 LCS Severe Item Age Of Location missing from
group and LCS Transaction Status
V36.4 Page 147 of 317


Code Level
Conditionality: contains ‘last known location’.
Present within group Location Service Usage where the
delivered service is not as requested.
LCS QoS The group identifies the quality of service requested. 30 LCS Severe Item LCS Request Timestamp not
Requested The LCS Request Timestamp must be present. All other items present within group.
are present where available.
Conditionality:
Mandatory within group Location Service Usage.
LCS Request The timestamp identifying the requested service usage. 20 LCS Severe Value out of range.
Timestamp The item is normally in the local time of the Sender (or Serving
Network where this is not the Sender). There must be an 30 LCS Severe Mandatory item UTC Time Offset Code
associated UTC Time Offset Code. missing.
Conditionality:
Mandatory within group LCS QoS Requested.
Format:
CCYYMMDDHHMMSS

to 235959
LCS SP Group containing identification of the location service content 30 LCS Severe Mandatory item Content Provider Id
Identification provider (LCS SP). Type missing within group.
The group comprises two mandatory items, Content Provider 31 LCS Severe Mandatory item Content Provider
Id Type and Content Provider Identifier. Identifier missing within group.
Conditionality:
LCS SP Information.
LCS SP This is a group containing the information to identify the 30 LCS Severe Mandatory group LCS SP Identification
Information Location Service Content Provider (LCS SP) and how they missing within group.
have accessed the network.
V36.4 Page 148 of 317


Code Level
There must be at least one occurrence of group LCS SP

Identification present.
Groups Internet Service Provider and Network must be present

where the information is available.
Conditionality:
Must be present within group Location Service where the
LCS SP can be identified.
LCS The status of the LCS transaction. 20 LCS Severe Value out of range.
Transaction
Status Derivation:
The value ‘failure’ must be set, if the GSM/UMTS item
PositionMethodFailure-Diagnostic (See Annex C – LCS
Charging) indicates a failure of processing the LCS request
within the serving network of the tracked or requesting
subscriber subscriber.
The value ‘last known location’ must be set, if the

GSM/UMTS item LocationEstimateType (See Annex C –
LCS Charging) indicates this. The value ‘last known
location’ must override the value ‘failure’.
The value ‘denied’ must be set if the LCS client is not

authorised. I.e. the request is denied by the HPMN of the
tracked subscriber.
Conditionality:
LCS QoS Delivered
for non-successful LCS transactions.
Values:
V36.4 Page 149 of 317


Code Level
1 last known location
2 failure
3 denied
Local Contains the Currency Code which identifies the currency used 10 Acctng Fatal Syntax error.
Currency to price the calls and/or events prior to conversion to SDRs
and therefore used in Exchange Rate. This currency has to be 20 Acctng Fatal Value out of range (not listed in ISO
the one used in the Sender’s IOT. 4217 [26]).
Note the use of SDRs may be subject to internal market 21 Acctng Fatal Value not as specified in the Sender’s
bilateral agreements, see TAP Currency. Inter Operator Tariff (IOT).
Only one occurrence is allowed per TAP file and therefore it is

not permitted to have a TAP file containing calls or events
where the Local Currency was different.
Derivation:
ISO 4217 [26].
Conditionality:
Mandatory within group Accounting Information.
Example:
Currency Code Currency Name
AUD Australian Dollars
CLP Chilean Pesetas
GBP Pounds Sterling
Location Area Identification of the Location Area Code of the mobile 10 MOC Warning Syntax error.
Code equipment handling the call. MTC
SS
Derivation: GPRS
GSM item LocationAreaCode or User Location Information MSG
(See Annex C – CS Domain Charging and PS Domain MSESS
Charging).
11 MOC Severe Syntax error and item expected in
V36.4 Page 150 of 317


Code Level
Conditionality: MTC accordance with roaming agreement.
Must be present within groups SS
Network Location GPRS
GPRS Network Location MSG
Messaging Event MSESS
Mobile Session
when expected in accordance with roaming agreement. 20 MOC Warning Value out of range.
MTC
When not expected in accordance with roaming SS
agreement, must be present except where not supported GPRS
by the network or the call does not terminate at the MSG
equipment for example in call forwarding cases. MSESS
Is not present for Wi-Fi usage. 21 MOC Severe Value out of range and item expected
MTC in accordance with roaming
The type of location information used by the PS core network SS agreement.
depends on the type of Radio Access Network used. Location GPRS
Area Code will be used in the case of 2G and 3G coverage MSG
while Tracking Area Code will be used in the case of LTE MSESS
coverage.
The Location Area Code is a two octet string (See Annex C –

CS Domain Charging).
For TAP the octets are converted to a decimal integer number
in the range 0 to 65535. The leading zeros are significant only
for the 2 octet strings in the standard and not in TAP.
Examples:
0110011000110000 equates to 26160
1001110000001010 equates to 39946
0001000011110001 equates to 4337
The Tracking Area Code (TAC) is a two octet string which is

used within EPC for LTE to identify a Tracking Area within a
PMN (see Annex C – PS Domain Charging).
V36.4 Page 151 of 317


Code Level
Where d represents the first octet of the Tracking Area

Identifier (TAI) field, the TAC encoding starts with bit 8 of octet
d+3 as the most significant bit and bit 1 of octet d+4 represents
the least significant bit.
Location Id This item gives the type of location identifier associated with it. 10 Content Warning Syntax error.
Type
Conditionality: 20 Content Warning Value out of range.
Mandatory within groups LCS
Tracking Customer Location.
Values:
1 Country Text representation
2 Country ITU E.164 representation [28]
for example, 44 (UK), 49
(Germany)
3 Country Country code for example
DEU (Germany), CAN
(Canada)
4 Region Text representation
5 Place Text representation
6 IP Location IP Address v4
7 IP Location IP Address v6
8 TADIG Code See item Sender or Recipient,
for example GBRVF, DEUD1
Location The item holds a unique identifier of the Charged Party’s 10 Content Warning Syntax error.
Identifier location.
100 Content Warning Item content does not match Location
The type of identifier is contained in the associated Location Id LCS Id Type.
Type.
Conditionality:
V36.4 Page 152 of 317


Code Level
Tracking Customer Location.
Location The location information identifies the Network Location, which 30 MOC Severe Mandatory item Network Location
Information includes the MSC responsible for handling the call and, where MTC missing within group.
appropriate, the Geographical Location of the mobile. SS
Conditionality: 31 MOC Severe Group Geographical Location missing

Mandatory within groups MTC but Serving BID expected in
Mobile Originated Call SS accordance with roaming agreement.
Supplementary Service Event This validation rule can be applied only
Mobile Terminated Call where bilaterally agreed between
32 MOC Severe Group Geographical Location missing

MTC but Serving Location Description
SS expected in accordance with roaming
agreement.
Location Location Service represents the charging and transactional 30 LCS Severe Neither of groups Tracking Customer
Service details for use of the Location Service (LCS) by a tracking Information or LCS SP Information
customer. present within group.
The group contains mandatory group Location Service Usage. 31 LCS Severe Mandatory group Location Service
One of groups Tracking Customer Information or LCS SP Usage missing within group.
Information must be present. Group Tracked Customer
Information must be present where the tracked customer is not 32 LCS Warning Item RAP File Sequence Number
the tracking customer. Items Call Reference and RAP File missing and Location Service
Sequence Number are present where available and applicable. previously received and rejected.
Repeating item Operator Specific Information is optionally
present. 33 LCS Warning Item RAP File Sequence Number
V36.4 Page 153 of 317


Code Level
present and Location Service not
Conditionality: previously received and rejected.
where none of the following are present; Mobile Originated 34 LCS Warning Item RAP File Sequence Number
Call, Mobile Terminated Call, Supplementary Service present and TAP transfer batch being
Event, Service Centre Usage, Content Transaction or resubmitted as corrected (having been
GPRS Call. previously rejected with fatal error)..
Location Location Service Usage details the actual service quality 30 LCS Severe Mandatory group LCS QoS Requested
Service Usage requested and delivered together with the associated charging missing within group.
information.
31 LCS Severe Mandatory group Charging Information
Group LCS QoS Requested must be present with repeating missing within group.
group Charge Information present at least once.
Conditionality:
Mandatory within group Location Service.
4.11 M
Code Level
Maximum Bit The maximum bit rate available for circuit switched UMTS. 10 MOC Severe Syntax Error.
Rate MTC
Derivation:
Maximum Bit Rate, see Annex C – CS Domain Charging 20 MOC Severe Value out of range.
MTC
Conditionality:
Mandatory within group Basic Service where available from
the network.
Values:
1 14400bps
2 28800bps
3 32000bps
V36.4 Page 154 of 317


Code Level
4 33600bps
5 56000bps
6 57600bps
7 64000bps
MDN Mobile Directory Number. This item supports wireless number 10 MOC Warning Syntax error.
portability within the North American market. MTC
SS
Derivation: GPRS
20 MOC Warning Value out of range.
Conditionality: MTC
When a MIN is present within group MIN Chargeable SS
Subscriber then MDN must be present, when available, GPRS
associated with item MIN.
Note: Privacy laws in some countries may restrict the MDN

availability.
Message Message Description is a free format description of the Short 10 Mess Warning Syntax error.
Description Message Service used. It is mandatory but the content is Desc
entirely at the discretion of the network supplying the access to
the service.
The description must be in English.
Conditionality:
Mandatory within group Message Description Information.
Message A code used to cross reference the SCU Charge Type to the 10 Mess Warning Syntax error.
Description relevant description. Desc
Code SCU
Conditionality:
Mandatory within group Message Description Information. 100 SCU Warning Specified message description code
Mandatory within group SCU Charge Type. not defined in Message Description
Information.
V36.4 Page 155 of 317


Code Level
Message A repeating table of pairs of Message Description and related 30 Tf Batch Warning Mandatory item Message Description
Description Message Description Code. Code missing within group.
Information
This table is used on a once-off basis and applies only to the 31 Tf Batch Warning Mandatory item Message Description
transfer which contains it. A new table is sent with each missing within group.
transfer. Codes are reusable from transfer to transfer.
32 Tf Batch Fatal More than one occurrence of group
Conditionality: with same Message Description Code
One occurrence must be present within Transfer Batch for where Message Description is not the
each unique Message Description Code used within group same.
SCU Charge Type.
33 Tf Batch Warning More than one occurrence of group
with same Message Description Code
where Message Description is the
same.
Message The completion status of the message. 10 SCU Severe Syntax error.
Status
Conditionality: 20 SCU Severe Value out of range.
Mandatory within group SCU Charge Type.
Values:
0 Unable to Deliver
1 Time Expired
2 Delivered / Succeeded
3 Deleted / Canceled by SME
4 Deleted / Canceled by Service Centre
Operators
Message Type The type of service/message, for example fax, text. 10 SCU Severe Syntax error.

Values:
0 Text
V36.4 Page 156 of 317


Code Level
1 Fax
2 Info
Messaging A Messaging Event item represents a type of message and is 30 MSG Severe Mandatory item Messaging Event
Event further defined by item Messaging Event Service. Service missing within group.
The Messaging Event must contain Messaging Event Service, 31 MSG Severe Mandatory group Charged Party
Charged Party, Event Reference, Service Start Timestamp, missing within group.
Call Type Group, Charge and at least one occurrence of
Recording Entity Code. 32 MSG Severe Mandatory item Event Reference
Non Charged Party must be present where available and
Messaging Event Service is “MO SMS over IP”. 33 MSG Severe Mandatory item Service Start
RAP File Sequence Number, Geographical Information, SIM
Toolkit Indicator, Location Area Code, Tax Information and 34 MSG Severe Mandatory group Call Type Group
Exchange Rate Code will be present where applicable. missing within group.
One or more occurrences of Network Element will be present 35 MSG Severe Mandatory item Charge missing within
when available from the network. group.
Operator Specific Information may also be present. This is 36 MSG Severe Mandatory item Recording Entity Code
optional dependent on bilateral agreement. Cell Identity may missing within group.
be optionally present.
37 MSG Severe Item Location Area Code missing
Note: This event type can only be used for SMS over IP (IMS within group but expected in
based SMS) and cannot be used to represent SMS over SS7. accordance with roaming agreement
SMS MO/MT over the VPMN’s IMS Domain is provided in a 38 MSG Severe Group Tax Information missing within
TAP MSG Event. See section 5.10 on the provisioning rules of group but expected in accordance with
TAP CDRs in each type of SMS messaging scenario. roaming agreement for that particular
call. Tax Information group missing
Conditionality: must be interpreted as Tax Value 0
Mandatory within an occurrence of group Call Event Details (zero).
V36.4 Page 157 of 317


Code Level
Call, Mobile Terminated Call, Supplementary Service 39 MSG Severe Group Tax Information present within
Event, Service Centre Usage, GPRS Call, Content group but not expected in accordance
Transaction, Mobile Session or Location Service . with roaming agreement for the
(zero).
40 MSG Warning Group Tax Information present within

(zero).
41 MSG Severe Item Exchange Rate Code missing

within group and Charge is greater
than 0 (zero).
42 MSG Severe Group Geographical Location missing

within group but Serving BID expected
in accordance with roaming
agreement.
This validation can only be applied
43 MSG Severe Group Geographical Location missing

within group but Serving Location
Description expected in accordance
with roaming agreement.
Messaging The type of service which is recorded in the Messaging Event. 10 MSG Severe Syntax error.
V36.4 Page 158 of 317


Code Level
Event Service
Conditionality: 20 MSG Severe Value out of range.
Mandatory within group Messaging Event
Values:
1 MO SMS over IP (IMS based SMS)
2 MT SMS over IP (IMS based SMS)
MIN Mobile Identification Number is an item which uniquely 10 Calls Severe Syntax error.
identifies the subscriber who has used the network and is liable
for any charges that may be incurred. 20 Calls Severe Value out of range.
The MIN is the mobile telephone number assigned by the

HPMN. The format of the number may conform to the North
American Number Plan where it belongs to a North American
operator.
Derivation:
Conditionality:
Mandatory within group MIN Chargeable Subscriber.
Must be present within group SCU Chargeable Subscriber

when group GSM Chargeable Subscriber is not present.
MIN Contains the identification of a chargeable subscriber identified 30 MOC Severe MIN not present within group.
Chargeable by a MIN. MTC
Subscriber SS
The group must contain the MIN of the chargeable subscriber GPRS
and may optionally contain a MDN.
Conditionality:
Mandatory within group Chargeable Subscriber where SIM
Chargeable Subscriber is not present.
MO Basic Call MO Basic Call Information provides the basic detail of who 30 MOC Severe Mandatory group Chargeable
V36.4 Page 159 of 317


Code Level
Information made the call and where to in respect of mobile originated Subscriber missing within group.
traffic.
31 MOC Severe Mandatory item Call Event Start
It comprises mandatory Chargeable Subscriber, Call Event Timestamp missing within group.
Start Timestamp and Total Call Event Duration details together
with conditional Destination, Destination Network, RAP File 32 MOC Severe Mandatory item Total Call Event
Sequence Number and Cause For Termination information. Duration missing within group.
Where the call was initiated by the SIM toolkit application the 33 MOC Warning Item RAP File Sequence Number
SIM Toolkit Indicator flag will be present. missing and call previously received
and rejected.
Conditionality:
Mandatory within group Mobile Originated Call. 34 MOC Warning Item RAP File Sequence Number
35 MOC Severe Group Destination missing and call is

not for use of emergency service.
36 MOC Warning Item RAP File Sequence Number


Mobile A Mobile Originated Call item represents either tele or bearer 30 MOC Severe Mandatory group MO Basic Call
Originated Call service usage originated by the mobile subscription. In some Information missing within group.
cases the mobile itself may not be directly involved, for
example some call forwarding scenarios. 31 MOC Severe Mandatory group Location Information
The Mobile Originated Call must contain the MO Basic Call
Information, Location Information and Basic Services Used. 32 MOC Severe Mandatory group Basic Service Used
V36.4 Page 160 of 317


Code Level
Note: There must be only one occurrence of the Basic Service
Used group within this group even though the physical syntax 35 MOC Severe More than one occurrence of group
indicates that this may be a repeating group. Basic Service Used present within
group.
Where CAMEL services are supported and invoked then one
occurrence of CAMEL Service Used will be present for the Note: Error codes 33 & 34 removed in
invocation. TAP release 3.11 (01 May 2005).
Where a supplementary service is used in conjunction with a

call and I deemed necessary for transfer (see Annex A) then
Supplementary Service Code will be present. Third Party
Information may also be present.
Equipment Identifier will normally be transferred. The reason

that it may not be present is because the call did not originate
from the equipment.

MO Voice over CSFB is provided in a TAP MOC Event. Please

see section 5.9 on the provisioning rules of TAP CDRs in each
type of voice call scenario.
SMS MO over SGs is provided in a TAP MOC Event.Please

see section 5.10 on the provisioning rules of TAP CDRs in
each type of SMS messaging scenario.
Conditionality:
where none of the following are present; Mobile
Terminated Call, Supplementary Service Event, Service
Centre Usage, GPRS Call, Content Transaction or Location
Service .
V36.4 Page 161 of 317


Code Level
Mobile A Mobile Session where the type of usage is further detailed by 30 MSESS Severe Mobile Session Service missing within
Session Mobile Session Service. group.
The Mobile Session must contain Mobile Session Service, 31 MSESS Severe Mandatory group Charged Party
Charged Party, Event Reference, Recording Entity Code, missing within group.
Service Start Timestamp, Total Call Event Duration and
Session Charge Information. 32 MSESS Severe Event Reference missing within group.
Non-Charged Party must be present where Mobile Session 33 MSESS Severe Recording Entity Code missing within
Service is “MO Voice over LTE”, otherwise it will be present group.
where available for all other Mobile Session Services.
34 MSESS Severe Service Start Timestamp missing
Requested Destination must be present where Mobile Session within group.
Service is ‘MO Voice over LTE’, if available from the network.
35 MSESS Severe Total Call Event Duration missing
RAP File Sequence Number, SIM Toolkit Indicator, within group.
Geographical Information, Location Area Code and Cause for
Termination will be present where applicable and available. 36 MSESS Severe Mandatory group Session Charge
Information missing within group.
Operator Specific Information may also be present. This is
optional dependent on bilateral agreement. . Cell Identity may 37 MSESS Severe Item Location Area Code missing
be optionally present. within group but expected in
MO/MT Voice calls anchored in the VPMN’s IMS Domain must
be provided in a TAP MSESS Event. Please see section 5.9 on 38 MSESS Severe Group Geographical Location missing
the provisioning rules of TAP CDRs in each type of voice call within group but Serving BID expected
scenario. in accordance with roaming
agreement.
Conditionality: This validation can only be applied
Mandatory within an occurrence of group Call Event Details where bilaterally agreed between
where none of the following are present; Mobile Originated Sender and Recipient.
Event, Service Centre Usage, GPRS Call, Content 39 MSESS Severe Group Geographical Location missing
Transaction, Messaging Event or Location Service . within group but Serving Location
Description expected in accordance
V36.4 Page 162 of 317


Code Level
with roaming agreement.
40 MSESS Severe Group Non Charged Party missing

within group and Mobile Session
Service is “MO Voice over LTE”.
Mobile The type of service which is recorded in the Mobile Session. 10 MSESS Severe Syntax error.
Session
Service Conditionality: 20 MSESS Severe Value out of range.
Mandatory within group Mobile Session
Values:
1 MO Voice over LTE
2 MT Voice over LTE
3 Emergency call over LTE
Mobile A Mobile Terminated Call item represents either tele or bearer 30 MTC Severe Mandatory group MT Basic Call
Terminated service usage terminated by the mobile subscription. In some Information missing within group.
Call cases the mobile itself may not be directly involved, for
example some call forwarding scenarios. 31 MTC Severe Mandatory group Location Information
Mandatory elements are the MT Basic Call Information and the
Basic Service Used. Only one basic service will be present 32 MTC Severe Mandatory group Basic Service Used
and it will not be possible, for example, to distinguish between missing within group.
the data and speech parts of alternate services.
35 MTC Severe More than one occurrence of group
Note: There must be only one occurrence of the Basic Service Basic Service Used present within
Used group within this group even though the physical syntax group.
indicates that this may be a repeating group.
Location Information and Equipment Identifier will normally be TAP release 3.11 (01 May 2005).
present except, for example, where the call does not terminate
at the equipment for example call forward on no reply.
V36.4 Page 163 of 317


Code Level
Where CAMEL services are supported and invoked then one

occurrence of CAMEL Service Used will be present for the
invocation.

MT Voice over CSFB is provided in a TAP MTC Event. Please

see section 5.9 on the provisioning rules of TAP CDRs in each
type of voice call scenario.
SMS MT over SGs is provided in a TAP MTC Event.Please

see section 5.10 on the provisioning rules of TAP CDRs in
each type of SMS messaging scenario.
Conditionality:
Call, Supplementary Service Event, Service Centre Usage,
GPRS Call, Content Transaction or Location Service.
MSISDN The Mobile Subscriber ISDN number. 10 MOC Warning Syntax error and item MSISDN not
MTC expected in accordance with roaming
Derivation: SS agreement.
GSM item MSISDN (See Annex C – CS Domain Charging GPRS
and PS Domain Charging). It is represented in TAP in MSG
international format, i.e. the number begins with the country MSESS
code related to the calling number.
11 SCU Severe Syntax error and IMSI not present or
Conditionality: MSISDN expected in accordance with
Must be present within group SIM Chargeable Subscriber roaming agreement.
when available.
When an IMSI is present within group GPRS Chargeable 12 SCU Warning Syntax error and IMSI present and
Subscriber then MSISDN must be present, when available, MSISDN not expected in accordance
V36.4 Page 164 of 317


Code Level
associated with item IMSI. with roaming agreement.
Must be present within group GSM Chargeable Subscriber
when available. 13 MOC Severe Syntax error and item MSISDN
Must be present within group Charged Party where MTC expected in accordance with roaming
available. SS agreement.
Must be present when expected in accordance with GPRS
roaming agreement. MSG
Must be present for Wi-Fi usage where the full IMSI or MSESS
Network Access Identifier is not available.
Note that privacy laws in some countries may restrict the 20 MOC Warning Number not represented in
MSISDN availability. MTC international format and MSISDN not
GPRS agreement.
MSG
MSESS
21 SCU Severe Number not represented in

international format and IMSI not
present or MSISDN expected in
22 SCU Warning Number not represented in

international format and IMSI present
and MSISDN not expected in
23 MOC Severe Number not represented in

MTC international format and MSISDN
GPRS agreement
MSG
MSESS
MT Basic Call MT Basic Call Information provides the basic detail of who 30 MTC Severe Mandatory group Chargeable
Information received the call and, conditionally, where from in respect of Subscriber missing within group.
V36.4 Page 165 of 317


Code Level
mobile terminated traffic.
31 MTC Severe Mandatory item Call Event Start
It comprises mandatory Chargeable Subscriber, Call Event Timestamp missing within group.
Start Timestamp and Total Call Event Duration details together
with conditional Call Originator, Originating Network, RAP File 32 MTC Severe Mandatory item Total Call Event
Sequence Number and Cause For Termination information. Duration missing within group.
Where the call was initiated by the SIM toolkit application the 33 MTC Warning Item RAP File Sequence Number
SIM Toolkit Indicator flag will be present. missing and call previously received
and rejected.
Conditionality:
Mandatory within group Mobile Terminated Call. 34 MTC Warning Item RAP File Sequence Number
35 MTC Warning Item RAP File Sequence Number

Note: Error codes 36, 37 & 38

2005).
4.12 N
Code Level
Network Information relating to the Network used to access the service 30 Content Warning Mandatory item Network Id Type
where the network is different to the Sender and is known. missing within group.
Conditionality: 31 Content Warning Mandatory item Network Identifier

Present within groups missing within group.
Serving Parties Information
V36.4 Page 166 of 317


Code Level
LCS SP Information 32 LCS Severe Mandatory item Network Id Type
where available. missing within group.
33 LCS Severe Mandatory item Network Identifier

Network The Network Access Identifier (NAI) is a username identifying 10 GPRS Severe Syntax error.
Access a unique customer belonging to the Recipient when generating
Identifier Wi-Fi CDRs. 20 GPRS Severe Value out of range.
Derivation: 200 GPRS Severe Realm not belonging to the

IETF RFC 4282 [34]. Recipient.
Conditionality:
Mandatory within group GPRS Chargeable Subscriber
where the IMSI or MSISDN is not available for identification
of chargeable user.
Format:
username@realm
for example [email protected]
Network Group providing information on the Network Elements used to 30 MSG Severe Element ID missing within group.
Element enable the Messaging Event.
31 MSG Severe Element Type missing within group.
The group must contain Element ID and Element Type.
101 MSG Severe Element Type refers to SMSC and
Conditionality: syntax of the associated Element
One or more occurrence may be present in Messaging ID does not conform to MSISDN.
Event where the information is available from the network.
102 MSG Severe Element Type refers to S-CSCF
and syntax of the associated
Element ID does not conform to
section 5.5 (Text Representation of
IP Address)
V36.4 Page 167 of 317


Code Level
103 MSG Severe Element Type refers to SM-IP-GW
and syntax of the associated
Element ID does not conform to
section 5.5 (Text Representation of
IP Address).
Network Id This item gives the type of Network Identifier associated with it. 10 Content Warning Syntax error.
Type
Conditionality: 20 Content Warning Value out of range.
Mandatory within group Network.
21 LCS Severe Value out of range.
Values:
1 Name Text representation, for example BT,
Telecom Italia, Commerzbank
3 Home BID See item Home BID
4 Home See item Home Location Description.
Location
Description
5 APN Access Point Name
6 URL For example www.amazon.com
Network The item holds a unique identifier of the Network. 10 Content Warning Syntax error.
Identifier
The type of identifier is contained in the associated Network Id 100 Content Warning Item content does not match
Type. Network Id Type.
Conditionality: 101 LCS Severe Item content does not match

Mandatory within group Network. Network Id Type.
Network Network Information is a group of related information which 30 Tf Batch Fatal Mandatory group UTC Time Offset
Information pertains to the Sender PMN. Information missing within group.
It consists of the UTC Time Offset Information table, which is 33 Tf Batch Fatal Call Event Details other than
mandatory and the Recording Entity Information table which Content Transaction present within
must be present where Recording Entity Codes are present file and group Recording Entity
V36.4 Page 168 of 317


Code Level
within the TAP file. Information missing within group.
Conditionality: Note: Error codes 31 & 34

Mandatory within group Transfer Batch. removed in TAP release 3.11 (01
May 2005).
Network Init. This item identifies where a GPRS Call was initiated by the 10 GPRS Severe Syntax error.
PDP Context network and not the terminal equipment.
Derivation:
Data item NetworkInitiatedPDPContext (PS Domain
Charging – see Annex C).
Conditionality:
Must be present within group GPRS Basic Call Information
when the PDP context was initiated by the network,
otherwise not present.
Is not present for Wi-Fi usage.
Values:
1 Network initiated
Network Identifies the location information relating to the network. 30 MOC Severe Mandatory item Recording Entity
Location MTC Code missing within group.
It must have the MSC Code present, identifying the MSC SS
handling the call and the Call Reference will be present when
available from the network. The Location Area Code and Cell 31 MOC Severe Item Location Area Code missing
Identity may be present and the Cell Identity is further optional MTC within group but expected in
at the discretion of the Sender PMN. SS accordance with roaming
agreement.
Conditionality:
Mandatory within group Location Information.
Non Charged The number of the non-charged party, either that to which the 10 SCU Severe Syntax error and Charged Party
Number message is or was to be delivered or from which it originated Status is ‘originating’.
(dependent on the message direction and charging for the
V36.4 Page 169 of 317


Code Level
service). 11 SCU Warning Syntax error and Charged Party
Status is ‘terminating’.
Derivation:
For GSM subscribers GSM item CalledNumber (See Annex
C – CS Domain Charging). This item is of type
AddressString. In this case it is represented in TAP in
international format, i.e. the number begins with the country
code related to the calling number.
This item may also be used for other address types, for
example internet address.
Conditionality:
Mandatory within group SCU Basic Information.
Values:
For GSM subscribers each digit is numeric (0-9).
Where the non-charged number represents other address
types any value is allowed.
Non-Charged A group containing information relating to the party in the 30 MSESS Severe Neither Non Charged Party Number
Party service that is not charged. This is the called or calling party MSG nor Non Charged Public User ID
dependent upon the direction of the service. present
The group will contain Non Charged Party Number and/or Non
Charged Public User ID.
Conditionality:
Must be present within groups Messaging Event where
Messaging Event Service is ‘MO SMS over IP’ and Mobile
Session where Mobile Session Service is ‘MO Voice over
LTE’.
Must be present where available for other Service values
Non-Charged The number of the non-charged party, either the number to 10 MSESS Severe Syntax error and Mobile Session
Party Number which the call has been routed or from which it originated Service is ‘MO Voice over LTE’.
(dependent on the direction). Must be represented in
V36.4 Page 170 of 317


Code Level
international format. 11 MSESS Warning Syntax error and Mobile Session
Service is ‘MT Voice over LTE’
The Non-Charged Party Number must start with the valid
country code as listed in E.164 “Assigned Country Codes” [28] 12 MSG Warning Syntax error and Messaging Event
and contain only numeric digits. All other characters must be Service is ‘MO SMS over IP’ or ‘MT
removed. SMS over IP’
If the service used is MO or MT SMS (see Messaging Event 20 MSESS Severe Value out of range or number does
Service) then the content of the Non-Charged Party Number not start with a valid country code
must be the SMSC address, in international format. as listed in E.164 “Assigned
Country Codes” and Mobile
Derivation: Session Service ‘MO Voice over
IMS item Called Party Address or Calling Party Address LTE’.
(See Annex C – IMS Domain Charging) Note: Spare and reserved codes
are NOT valid country codes, with
Conditionality: the exception of reserved code 970
Must be present within group Non-Charged Party where for Palestine which is valid.
21 MSESS Warning Value out of range and Mobile
Session Service is ‘MT Voice over
Values: LTE’
Each digit is numeric (0-9).
22 MSG Warning Value out of range and Messaging
Event Service is ‘MO SMS over IP’
or ‘MT SMS over IP’.

TAP release 3.12 (with effect from
01 May 2013).
Non-Charged The Public User ID of the non-charged party. It is populated 10 MSG Warning Syntax Error
Public User ID with the SIP URI to which the call has been routed or from MSESS
which it originated (dependent on the direction).
In case the TEL URI is provided from the network, it is not
V36.4 Page 171 of 317


Code Level
allowed to be populated in the Non-Charged Public User ID
and must be populated only in the Non-Charged Party Number
element.
Derivation:
IMS item Called Party Address or Calling Party Address
(see Annex C – IMS Domain Charging)
Conditionality:
Must present within group Non-Charged Party where
Examples:
sip:[email protected]
sip:alice:[email protected];transport=tcp
sips:[email protected]?subject=project%20x&priority=urge
nt
sip:+1-212-555-1212:[email protected];user=phone
sips:[email protected]
sip:atlanta.com;method=REGISTER?to=alice%40atlanta.c
om
sip:alice;[email protected]
Notification A Notification file is sent where the transfer mechanism is 30 Notifictn Fatal Mandatory item Sender missing
electronic file transfer and there is no data available for within group.
transfer.
31 Notifictn Fatal Mandatory item Recipient missing
All items within the group are mandatory except RAP File within group.
Sequence Number which is conditional and File Creation
Timestamp which is optional. 32 Notifictn Fatal Mandatory item File Sequence
Conditionality:
Mandatory within group Data Interchange where no data is 33 Notifictn Fatal Mandatory item Specification
available for transfer and the transfer mechanism is Version Number missing within
V36.4 Page 172 of 317


Code Level
electronic file transfer. group.
35 Notifictn Warning Mandatory item File Available

36 Notifictn Warning Mandatory item Transfer Cut Off

37 Notifictn Warning File Sequence Number previously

received and rejected with fatal
error, therefore RAP File Sequence
Number expected but not present.
38 Notifictn Warning RAP File Sequence Number

present although File Sequence
Number has not previously been
rejected with a fatal error (for
example previously missing or new
files).
39 Notifictn Fatal Mandatory item Release Version


Number Of Identifies the number of decimal places represented within the 10 Acctng Fatal Syntax error.
Decimal item Exchange Rate.
Places 20 Acctng Fatal Value out of range.
Conditionality:
Values:
> or = zero
V36.4 Page 173 of 317

4.13 O
Code Level
Object Type This defines the type of object streamed or downloaded to the 10 Content Severe Syntax error.
customer.
20 Content Severe Object Type out of range for Content
Derivation: Transaction Code and Type
The object type values are based on, but not confined to, Pull/Streaming combination.
the withdrawn M-Services specification.
21 Content Severe Object Type out of range for Content
Conditionality: Transaction Code and Type
Present within group Content Service Used where ‘Pull’ Pull/Download combination.
Content Transaction Code used and either Content
Transaction Type ‘Streaming’ or ‘Download’ used.
Values:
0 Not known/other
(Valid for use with streaming and download
where the type of object cannot be identified
or does not match one of the values below.)
For use with Pull or Streaming:

1 Speech – Audio MPEG 4 AMR
2 Audio – Audio MPEG 4 AAC
3 Audio – MP3
4 Audio – WAVE
5 Video – H.263 real time video
6 Video – MPEG 4
7 – 19 Reserved for future use.
For use with Pull or Download

20 Ring Tone – MIDI
21 Ring Tone – Audio MP4
22 Ring Tone – iMelody
23 Ring Tone – WAVE
24-29 Reserved for future use.
V36.4 Page 174 of 317


Code Level
30 Wallpaper/Screen Saver – JPEG
31 Wallpaper/Screen Saver – WBMP
32 Wallpaper/Screen Saver –GIF87a & GIF89
34 Wallpaper/Screen Saver –Java MIDlet
35-39 Reserved for future use
40 Picture – JPEG
41 Picture – WBMP
42 Picture – GIF87a & GIF89
43 Picture – PNG
44 Picture – BMP
50 Speech – Audio MPEG 4 AMR
60 Audio – Audio MPEG 4
61 Audio – Audio MP3
62 Audio – WAVE
70 Vector Graphic – FFS
80 Video – H.263 real time video
81 Video – MPEG 4
82 Video – MPEG 2 DVD
90 Game
100 Application
Note: Reserved values are ‘out of range’ until values are

assigned.
Operator This is an optional repeating item which will contain information 30 All Warning Item is present without bilateral
Specific which is beyond the scope of TAP and has been bilaterally agreement.
Information agreed.
V36.4 Page 175 of 317


Code Level
The content of the item is defined by bilateral agreement and
may vary according to the context, for example content when
occurring within Mobile Originated Call may vary from that
when occurring within Transfer Batch.
Optionality:
Present when agreed bilaterally within groups
Notification
Aggregated Usage Record
Mobile Session
Messaging Event
Service Centre Usage
GPRS Call
Content Transaction
Location Service
Audit Control Information.
Order Placed The timestamp representing the time at which the Charged 10 Content Severe Syntax error and timestamp referenced
Timestamp Party placed the order for the content. This is given in the time as Charging Point.
of the serving Content Provider. There must be an associated
UTC Time Offset Code. 11 Content Warning Syntax error and timestamp not
Conditionality:
Must be present within group 20 Content Severe Value out of range and timestamp
Content Transaction Basic Info referenced as Charging Point.
when no other timestamp present within group or when
item referenced as the Charging Point. 21 Content Warning Value out of range and timestamp not
Format:
CCYYMMDDHHMMSS 30 Content Severe Mandatory associated UTC Time
Offset Code missing and timestamp
V36.4 Page 176 of 317


Code Level
Note: Within this timestamp the range for HHMMSS is 000000 referenced as Charging Point.
to 235959
31 Content Warning Mandatory associated UTC Time
Offset Code missing and timestamp
not referenced as Charging Point.
100 Content Severe Order Placed Timestamp after

Point.
101 Content Warning Order Placed Timestamp after

Charging Point.
200 Content Severe Order Placed Timestamp before the

commercial roaming start date (in
file.
Originating The network from which the call or message was routed. 10 MTC Warning Syntax error.
Network In the case of optimal routing the Originating Network code is SCU
different from the HPMN code.
20 MTC Warning Value out of range.
Conditionality: SCU
SCU Basic Information
if available.
For example:
GBRCN
V36.4 Page 177 of 317


Code Level
GBRVF
DEUD1
DEUD2
4.14 P
Code Level
Paid Indicator A flag which shows that the Charged Party has paid for the 10 Content Severe Syntax error.
service by another mechanism, for example credit card,
account, debit card. 20 Content Severe Value out of range.
The flag’s presence shows that the charge is not intended for
the retail invoice.
Conditionality:
Must be present within group Advised Charge Information
where the charge is being/has been settled by a
mechanism external to TAP.
Values:
1 Paid
Partial Type The Partial Type Indicator identifies the first and last partials in 10 GPRS Severe Syntax error.
Indicator a sequence.
Conditionality:
Must be present within group GPRS Basic Call Information
where the Call Event Detail represents a partial.
Not present for Wi-Fi usage as there are no partial records

for Wi-Fi sessions.
Values:
F first partial
V36.4 Page 178 of 317


Code Level
I intermediate partial
L last partial
Payment Where the charge is being/has been settled by a mechanism 10 Content Warning Syntax error.
Method other than TAP this item identifies the payment method (to be)
used. 20 Content Warning Value out of range.
Optionality:
This item is made available at the discretion of the Content
Provider and/or Sender.
Conditionality:
Must be present within group Advised Charge Information
where item Paid Indicator is also present, subject to
optionality.
Values:
0 not known
1 credit card
2 debit card
3 account
4 cash
5 cheque
6 direct debit
7 standing order
8 money order/banker’’s draft
Note: Value 0 (not known) is not a default value and must only
be used where there is the intention to identify the payment
method but it is genuinely not identifiable by the Content
Provider/Sender, for example mixed payment or information
not passed by retail outlet.
PDP Address An address (served) used with a Packet Data Protocol context 10 GPRS Warning Syntax error. Does not conform to
of a GPRS connection. This is an IP address. section 5.5.
V36.4 Page 179 of 317


Code Level
Derivation:
GSM item PDP Address (PS Domain Charging – see
Annex C).
For Wi-Fi usage, item Framed-IP-Address (RFC 2865).
Conditionality:
Mandatory within group GPRS Chargeable Subscriber.
For Wi-Fi usage, present when available.
PDP Context The timestamp gives the start of the PDP context in the case 10 GPRS Warning Syntax error.
Start where the Call Event Details (GPRS Call) represents an
Timestamp intermediate or last partial of a PDP context. 20 GPRS Warning Value out of range.
The time is given in the local time of the Sender PMN (or 30 GPRS Warning Mandatory associated item UTC Time
Serving Network where this is not the Sender). There must be Offset Code missing.
a UTC Time Offset Code associated with the timestamp.
31 GPRS Warning PDP Context Start Timestamp present
Note: The local time is the local time at the location of the but Partial Type Indicator is either not
chargeable subscriber. Where the location is not available, as present or identifies GPRS Call as the
in some call forwarding scenarios, this will be a notional ‘first’ partial.
‘network local time’.
100 GPRS Warning PDP Context Start Timestamp is later
Optionality: than Call Event Start Timestamp.
Operators may decide not to supply this information
(normally this will be because it is not available from the
billing system). Note: Error Code 101 removed in TAP
release 3.11 (01 May 2005).
Conditionality:
where available and Partial Type Indicator is present
identifying the GPRS Call as either an intermediate or last
partial (subject to optionality).
Format:
V36.4 Page 180 of 317


Code Level
CCYYMMDDHHMMSS

– 235959
Positioning The technology used for positioning a tracked mobile 20 LCS Severe Value out of range.
Method subscriber (e.g. Assisted GPS).
Derivation:
Positioning Data IE (See Annex C – LCS Charging). The
positioning technology can be derived by converting bits
the five most significant bits (bits 8-4) into an integer. It
needs to be noted that more than one positioning method
may be recorded in the Positioning Data IE (See Annex C –
LCS Charging). In order to identify the positioning
technology actually used bits 3-1 which code the usage of
the positioning technology need to be analysed.
Conditionality:
LCS QoS Delivered
Values:
0 Timing Advance
1 Reserved
2 Reserved
3 Mobile Assisted E-OTD
4 Mobile Based E-OTD
5 Mobile Assisted GPS
6 Mobile Based GPS
7 Conventional GPS
8-15 Reserved for GSM
16-31 Reserved for network specific positioning
methods
V36.4 Page 181 of 317


Code Level
Priority Code Indicates the priority assigned to the short message. 10 SCU Severe Syntax error.

Values:
0 Low
1 Normal
2 High
Public User ID An address identifying the subscriber, either in the form of a 10 MSG Warning Syntax Error
SIP URI or TEL URI. MSESS
Derivation:
IMS item SubscriptionID (See Annex C – IMS Domain
Charging)
Conditionality:
Must present within group Charged Party where available
from the network.
Examples:
nt
om
V36.4 Page 182 of 317

4.15 R
Code Level
RAP File A unique reference which identifies the Returned Account 10 Notifictn Warning Syntax error.
Sequence Procedure (RAP) file in which the record or batch was returned Btch Ctrl
Number to the Sender PMN by the Recipient PMN.
11 Calls Severe Syntax error
The record or batch, the error(s) having been resolved, is now
being resubmitted to the Recipient PMN. 20 Btch Ctrl Warning Value out of range.
Notifictn
Note: Where a TAP file is being resubmitted as corrected the
RAP File Sequence Number is not required on the Call Event 21 Calls Severe Value out of range
Details but it must be present on either the Notification or
Batch Control Information, as appropriate.
Note: The RAP File Sequence Number must not be present

when a previously missing TAP file (Transfer Batch or
Notification) is sent.
Conditionality:
Notification
where the TAP file is being resubmitted as corrected.
Mobile Session
Messaging Event
Service Centre Usage
Content Transaction Basic Info
Location Service
where the record is being resubmitted as corrected.
V36.4 Page 183 of 317


Code Level
Range:
00001 – 99999 for Test Data
00001 – 99999 for Chargeable Data
Recipient A unique identifier used to determine which network the data is 10 Notifictn Fatal Syntax error.
being sent to, i.e. the Recipient. Btch Ctrl
Derivation: 20 Notifictn Fatal Value out of range.

GSM Association PRD TD.13 [14]. Btch Ctrl
Conditionality: 100 Notifictn Fatal The item does not match the Recipient
Mandatory within group Notification. Btch Ctrl on the filename.
Mandatory within group Batch Control Information.
Examples:
GBRCN
GBRVF
DEUD1
DEUD2
Note: These codes must be in uppercase (as defined in TD.13

[14]).
Recording A code associated with a Recording Entity. 10 Network Fatal Syntax error
Entity Code
Conditionality: 11 MOC Severe Syntax error
Mandatory within groups MTC
Recording Entity Information MSESS
Location Service MSG
Network Location SS
Service Centre Usage where it must be of type SCU
‘Service Centre’ GPRS
Mobile Session LCS
Messaging Event
12 GPRS Severe Value out of range for a GPRS call
V36.4 Page 184 of 317


Code Level
In the case of GPRS network usage two or more (except for Wi-Fi usage), i.e. the
occurrences must be present within group GPRS Network Recording Entity Code refers to a
Location where one, and only one, occurrence must be of recording entity of a type other than
type ‘GGSN’ or ‘P-GW’ (see Recording Entity Type) and all GGSN, SGSN, P-GW or S-GW.
other occurrences must be of type ‘SGSN’ or ‘S-GW’.
13 GPRS Severe Value out of range for a GPRS call
In the case of Wi-Fi usage one occurrence must be present (only for Wi-Fi usage), i.e. the
identifying the Wi-Fi billing information recording entity or Recording Entity Code refers to a
the location of usage. recording entity of a type other than
Wi-Fi billing information recording
In the case of SMS over IP (IMS based SMS) usage, two or entity.
more occurrences must be present within groups
Messaging Event. There must be one occurrence of type 20 Network Fatal Value out of range.
‘P-CSCF’ and one occurrence of type ‘SGSN’ or ‘S-GW’.
An occurrence of type ‘P-GW’ may be present when used 100 MOC Severe Specified recording entity code not
to enable the event. MTC defined in the Recording Entity
MSESS Information
In the case of voice over LTE usage, two or more MSG
occurrences must be present within groups Mobile SS
Session. There must be one occurrence of type ‘P-CSCF’, SCU
‘TRF’ or ‘ATCF’ and one occurrence of type ‘SGSN’ or ‘S- GPRS
GW’. An occurrence of type ‘P-GW’ may be present when LCS
used to enable the event.
101 MOC Warning Entity Code refers to MSC (Recording
Values: MTC Entity Type 1) and syntax of the
0 .. 10000 SS referenced Recording Entity
Identification does not conform to
MSISDN, Signalling Point Code or
name.
102 SCU Severe Entity Code refers to SMSC

(Recording Entity Type 2) and syntax
of the referenced Recording Entity
MSISDN.
V36.4 Page 185 of 317


Code Level
103 GPRS Severe Entity Code refers to GGSN

section 5.5.
104 MOC Severe Entity Code refers to SGSN

MTC (Recording Entity Type 4) and syntax
GPRS of the referenced Recording Entity
MSESS Identification does not conform to
MSG MSISDN or section 5.5.
105 LCS Severe Recording Entity Code refers to GMLC

MSISDN or to section 5.5.
106 GPRS Severe Entity Code refers to P-GW (Recording

MSG Entity Type 7) and syntax of the
MSESS referenced Recording Entity
Section 5.5.
107 GPRS Severe Entity Code refers to S-GW (Recording

MSG Entity Type 8) and syntax of the
MSESS referenced Recording Entity
Section 5.5.
108 MSG Severe Entity Code refers to P-CSCF

MSESS (Recording Entity Type 9) and syntax
V36.4 Page 186 of 317


Code Level
Section 5.5.
109 MSESS Severe Entity Code refers to TRF (Recording

Entity Type 10) and syntax of the
referenced Recording Entity
Section 5.5.
110 MSESS Severe Entity Code refers to ATCF (Recording

Entity Type 11) and syntax of the
referenced Recording Entity
Section 5.5.
Recording The identification of the entity recording the call. 10 Network Fatal Syntax error.
Entity
Identification Derivation:
For MSC encoded as one of the following according to the
requirements of the Sender PMN.
The MSISDN of the entity (See Annex C – CS Domain
Charging and PS Domain Charging) for example
44836100456
The signalling point code (See Annex C – CS Domain
Charging and PS Domain Charging) for example 253464
A name for example “HELSINKI” or “Switch 1”.
For SMSC entity (See Annex C – CS Domain Charging and
PS Domain Charging) (Msisdn).
For GSN entities (See Annex C – CS Domain Charging
and PS Domain Charging) (GSNAddress).
For GSN entities, where SMS usage is recorded see Annex
C – CS Domain Charging and PS Domain Charging
(GSNAddress or Msisdn).
For GMLC entities see Annex C – CS Domain Charging
and PS Domain Charging (Msisdn) or as Ipv4 Address or
as Ipv6 Address.
V36.4 Page 187 of 317


Code Level
For Wi-Fi usage this could be the name (uppercase) or an
IP address of the Wi-Fi billing information recording entity
or location of the usage.
For P-CSCF, TRF and ATCF see Annex C - IMS Domain
Charging.
Conditionality:
Mandatory within group Recording Entity Information.
Recording A repeating group which identifies a Recording Entity 30 Network Fatal Mandatory item Recording Entity Code
Entity Identification together with an associated Recording Entity missing within group.
Information Code and Recording Entity Type.
31 Network Fatal Mandatory item Recording Entity Type
transfer. Codes are reusable from transfer to transfer. 32 Network Fatal Mandatory item Recording Entity
Identification missing within group.
Conditionality:
One occurrence must be present within group Network 33 Network Fatal More than one occurrence of group
Information for each unique Recording Entity Code used with same Recording Entity Code
within the TAP file. where Recording Entity Type and /or
Recording Entity Identification are not
the same.
34 Network Fatal More than one occurrence of group

with same Recording Entity Code
where Recording Entity Type and
Recording Entity Identification are the
same (i.e. duplicate Recording Entity
Information table entry).
Recording An item identifying the type of recording entity. 10 Network Fatal Syntax error.
Entity Type
Conditionality: 20 Network Fatal Value out of range.
Mandatory within group Recording Entity Information.
V36.4 Page 188 of 317


Code Level
Values:
1 MSC (Mobile Services Switching Centre)
2 SMSC (Short Message Service Centre)
3 GGSN (Gateway GPRS Support Node) or
P-GW (PDN Gateway)
4 SGSN (Serving GPRS Support Node)
5 GMLC (Gateway Mobile Location Centre)
6 Wi-Fi Billing Information Recording Entity
7 P-GW (PDN Gateway)
8 S-GW (Serving Gateway)
9 P-CSCF (Proxy Call Session Control Function)
10 TRF (Transit and Roaming Function)
11 ATCF (Access Transfer Control Function)
Note 1: The usage of value 3 for P-GW is for the situation

where a VPMN accessing a gateway node on the HPMN side
from a visited SGSN may not be able to identify whether
access was to a GGSN or P-GW.
Note 2: Both S-GW and SGSN could be used for both 3G and
4G networks and do not imply a specific Radio Access
Technology (RAT).
Release Indicates the release version associated with the Specification 10 Notifictn Fatal Syntax error.
Version Version Number. Btch Ctrl
Number
Conditionality: 20 Notifictn Fatal Value out of range.
Mandatory within group Notification. Btch Ctrl Note: This error can be used to reject
Mandatory within group Batch Control Information. an unexpected release version
(subject to the rules of Section 7).
Values:
12
Requested The timestamp representing the time requested by the 10 Content Severe Syntax error and timestamp referenced
Delivery Charged Party to initiate the start of the Content Transaction. as Charging Point.
Timestamp This is given in the time of the serving Content Provider. There
V36.4 Page 189 of 317


Code Level
must be an associated UTC Time Offset Code. 11 Content Warning Syntax error and timestamp not
Example:
The Charged Party may request to download all messages 20 Content Severe Value out of range and timestamp
at 2200hrs in order to take advantage of off-peak rates referenced as Charging Point.
even when placing the order at an earlier time.
21 Content Warning Value out of range and timestamp not
Conditionality: referenced as Charging Point.
Content Transaction Basic Info 30 Content Severe Mandatory associated UTC Time
when no other timestamp present within group or when Offset Code missing and timestamp
item referenced as the Charging Point. referenced as Charging Point.
Format: 31 Content Warning Mandatory associated UTC Time

CCYYMMDDHHMMSS Offset Code missing and timestamp
not referenced as Charging Point.
to 235959 100 Content Severe Requested Delivery Timestamp after
Point.
101 Content Warning Requested Delivery Timestamp after

Charging Point.
200 Content Severe Requested Delivery Timestamp before

the commercial roaming start date (in
file.
Requested A group containing information relating to the original
V36.4 Page 190 of 317


Code Level
Destination destination to which the customer requested to be connected.
Conditionality:
Must be present within group Mobile Session where
available from the network and Mobile Session Service is
‘MO Voice over LTE’.
Requested The TEL URI of the original destination to which the customer
Number requested to be connected. Must be represented in
international format. This is the equivalent of the Dialled Digits
for Circuit Switched calls, however reformatted.
The Requested Number must start with the valid country code
as listed in E.164 “Assigned Country Codes” [28] and contain
only numeric digits. All other characters must be removed.
Derivation:
IMS item Requested Party Address (See Annex C – IMS
Domain Charging)
Conditionality:
Must be present within group Requested Destination where
Values:
Each digit is numeric (0-9).
Requested The SIP URI of the original destination to which the customer
Public User ID requested to be connected.
In case the TEL URI is provided from the network, it is not

allowed to be populated in the Requested Public User ID and
must be populated only in the Requested Number element.
Derivation:
V36.4 Page 191 of 317


Code Level
IMS item Requested Party Address (see Annex C – IMS
Domain Charging)
Conditionality:
Must be present within group Requested Destination where
Examples:
nt
om
Response The actual response time for processing the LCS request
Time measured in seconds.
Derivation:
GSM/UMTS item measureDuration (See Annex C – LCS
Charging).
Conditionality:
LCS QoS Delivered
where available from the network
Response The response time category as requested for the response of 20 LCS Severe Value out of range.
Time Category an LCS request.
Derivation:
V36.4 Page 192 of 317


Code Level
LCS QoS IE octet 6 (See Annex C – LCS Charging). The
value is derived by interpreting the 2 most significant bits of
octet 6 as an integer.
Conditionality:
LCS QoS Requested
Values:
0 response time not specified
1 low delay
2 delay tolerant
3 reserved
4.16 S
Code Level
SCU Basic Service Centre Usage (SCU) Basic Information provides 30 SCU Severe Mandatory group SCU Chargeable
Information details of who made the call and where to, who received the Subscriber missing within group.
call and where from, in respect of mobile originated and mobile
terminated traffic respectively and the direction of the 31 SCU Severe Mandatory item Charged Party Status
transaction. missing within group.
The Chargeable Subscriber, Charged Party Status and Non 32 SCU Severe Mandatory item Non Charged Number
Charged Number elements are all mandatory. All other missing within group and Charged
elements are conditionally present. Party Status is ‘originating’.
Conditionality: 33 SCU Warning Mandatory item Non Charged Number

Mandatory within group Service Centre Usage. missing within group and Charged
Party Status is ‘terminating’.
34 SCU Warning Item CLIR Status Indicator missing
V36.4 Page 193 of 317


Code Level
within group and Charged Party Status
is ‘terminating’.
SCU Charge Contains the elements used to price the service usage, 30 SCU Severe Mandatory item Message Status
Type message status, priority code, distance charge band code and missing within group.
message type. Where the charge is based on volume, for
example message length, this information will be present within 31 SCU Severe Mandatory item Priority Code missing
the associated Charge Information. within group.
All elements within the group are mandatory except Distance 32 SCU Severe Item Distance Charge Band Code
Charge Band Code which will not be present where it was not missing within group and distance
a parameter in Charge calculation. defined as a pricing parameter within
SMS bilateral agreement.
Conditionality:
Mandatory within group Service Centre Usage. 33 SCU Severe Mandatory item Message Type
34 SCU Warning Mandatory item Message Description

Code missing within group.
SCU Occurs within SCU Basic Information. Contains the
Chargeable identification of the chargeable subscriber.
Subscriber
The group must contain either the group GSM Chargeable
Subscriber or the MIN of the chargeable subscriber, both may
not be present.
Conditionality:
Mandatory within group SCU Basic Information
SCU Contains the timestamps for message deposit and completion 30 SCU Severe Mandatory item Deposit Timestamp
Timestamps of actions together with an indicator showing which timestamp missing within group.
was used as the Charging Point.
31 SCU Severe Mandatory item Completion
All elements within the group are mandatory. Timestamp missing within group.
Conditionality: 32 SCU Severe Mandatory item Charging Point
V36.4 Page 194 of 317


Code Level
Mandatory within group Service Centre Usage. missing within group.
Sender A unique identifier used to determine the network which is the 10 Notifictn Fatal Syntax error.
Sender of the data. Btch Ctrl
The full list of codes in use is given in TADIG PRD TD.13 [14]. 20 Notifictn Fatal Value out of range.
Btch Ctrl
Conditionality:
Mandatory within group Notification. 100 Notifictn Fatal The item does not match the Sender
Mandatory in group Batch Control Information. Btch Ctrl on the filename.
Example content:
GBRCN
GBRVF
DEUD1
DEUD2
Note: These codes must be in uppercase (as defined in TD.13

[14]).
Service Centre A Service Centre Usage item represents usage of an APMNs 30 SCU Severe Mandatory group SCU Basic
Usage Short Message Service Centre (SMSC). Information missing within group.
This usage can only occur where there is a bilateral agreement 31 SCU Warning Item RAP File Sequence Number
to make these services available to the HPMN’s subscribers. missing and SCU previously received
All elements within the group are mandatory except RAP File and rejected.
Sequence Number and Serving Network which are conditional
and Operator Specific Information which is optional. 32 SCU Warning Item RAP File Sequence Number
present and SCU not previously
Exchange of the Serving Network element requires bilateral received and rejected.
agreement.
33 SCU Severe Mandatory item Recording Entity Code
where none of the following are present; Mobile Originated 34 SCU Severe Mandatory group Charge Information
Call, Mobile Terminated Call, Supplementary Service missing within group.
V36.4 Page 195 of 317


Code Level
Event, GPRS Call, Content Transaction or Location Service
. 35 SCU Severe Mandatory group SCU Charge Type
36 SCU Severe Mandatory group SCU Timestamps

37 SCU Warning Item RAP File Sequence Number

38 SCU Severe Serving Network element present and

its exchange not bilaterally agreed.

release 3.11 (01 May 2005).
Service Code The Service Code is one of Teleservice Code or Bearer Note: Error codes 30, 31, 32 & 33
Service Code as determined by the service type used. removed in TAP release 3.11 (01 May
2005).
Conditionality:
Mandatory within group Basic Service.
One occurrence must be present within group
Supplementary Service Used for each basic service
affected by the Supplementary Service action except where
this applies to all basic services when it will not be present.
Service Start The timestamp gives the start of the event or call. 10 MSESS Severe Syntax error.
Timestamp MSG
Serving Network where this is not the Sender). There must be 20 MSG Severe Value out of range.
a UTC Time Offset Code associated with the timestamp. MSESS
Note that this timestamp is the event start time as provided by 30 MSESS Severe Mandatory associated item UTC Time
the network. MSG Offset Code missing.
V36.4 Page 196 of 317


Code Level
Derivation: 100 MSESS Severe Service Start Timestamp after Charge

IMS item Service Delivery Start Time Stamp (See Annex C Detail Timestamp.
– IMS Domain Charging
200 MSESS Severe Service Start Timestamp before the
Conditionality: MSG commercial roaming start date (in
Mandatory within group Mobile Session. VPMN local time if no other time zone
Format: network service and the TAP file is not
CCYYMMDDHHMMSS a test file.
Note: Old call records should not be
Note: Within this timestamp the range for HHMMSS is 000000 rejected in principle in Roaming
– 235959 Hubbing migration scenarios. See
BA.62 for further details.
Serving BID The Serving BID (Billing Identifier) is a code associated with a 10 MOC Severe Syntax error.
geographical area such as a cell site or group of cell sites. MTC
Where a Serving BID has been supplied there must be a SS
Serving Location Description present. GPRS
MSESS
The Serving BID presence is not required where only the MSG
Serving Location Description is used as a pricing parameter as
per the Sender’s IOT definition. 20 MOC Severe Value out of range.
MTC
Derivation: SS
Listed on the BID report in effect for the applicable call date GPRS
as defined within PRD TD.38 [35]. MSESS
MSG
Optionality:
Operators may decide not to transfer the Serving BID. 21 MOC Severe Value not assigned to Sender or, if a
MTC Serving Network element is present in
Conditionality: SS the record, not assigned to the
Must be present within group Geographical Location where GPRS operator identified in the Serving
available (subject to optionality). Value must be assigned MSESS Network element.
to the Sender unless a Serving Network element is present MSG Note: Please see TD.38 [35] for
V36.4 Page 197 of 317


Code Level
in the call record. In that case, it must belong to the clarification regarding Roaming
operator identified in the Serving Network element. Hubbing where alias TADIG Codes are
used.
Serving A text description giving the geographical location of the 10 MOC Severe Syntax error.
Location terminal equipment. Operators may optionally use a MTC
Description description as a default where there has been no terminal SS
equipment involved. GPRS
The Serving Location Description must be present where there MSESS
is an associated Serving BID and its content will then be MSG
predefined.
Where the location of the subscriber is a pricing parameter the

Serving Location Description will contain a value as explicitly
defined in the IOT of the Sender. Note that in case the IOT
defines both a ‘normal’ charge and one or more ‘exceptional’
charge(s) then only call/events containing an ‘exceptional’
charge need to contain the Serving Location Description.
For Wi-Fi usage this item must be present and will contain a
text description of the Wi-Fi Hot Spot or location, for example
“London City Airport”.
Other than the above described circumstances the content is

at the discretion of the Sender and is optionally supplied.
Derivation:
Listed on the BID report in effect for the applicable call date
as defined in TD.38 [35] where the Serving BID is present.
Where the location of the subscriber is a pricing parameter
the Serving Location Description (if present) must contain a
value as explicitly defined in the IOT of the Sender.
In all other cases the content is at the discretion of the
Sender.
V36.4 Page 198 of 317


Code Level
Optionality:
Operators may omit this information unless one of the
following:
 Item Serving BID present.
 The location of the subscriber is a pricing
parameter as explicitly defined in the Sender’s IOT.
 Wi-Fi usage
Conditionality:
Must be present within group Geographical Location where
a Serving BID is present or where the location of the
subscriber is a pricing parameter as explicitly defined in the
Sender’s IOT.
Must be present within group Geographical Location for Wi-
Fi network usage.
Serving A unique identifier used to determine the network where the 10 MOC Severe Syntax error.
Network call event was originally created. MTC
SS
While this would normally be a TADIG PMN code (see TADIG SCU
PRD TD.13 [14]) this may not be true in certain specific cases, GPRS
for example inter standard roaming. MSESS
MSG
The exchange and content of the Serving Network element AUR
need to be bilaterally agreed.
20 MOC Severe Value out of range, that is, it is not a
Conditionality: MTC bilaterally agreed value.
Must be present within groups SS
Geographical Location SCU
Service Centre Usage GPRS
Aggregated Usage Record MSESS
if the Serving Network is different from the Sender. MSG
AUR
Exchange of the Serving Network element requires bilateral
agreement.
V36.4 Page 199 of 317


Code Level
Serving Information on entities that were used to access the Content 30 Content Severe Mandatory item Content Provider
Parties Service. Name missing within group.
Information
This group must contain the item Content Provider Name.
Additional data should be provided when the information is
available to the Sender.
Conditionality:
Mandatory within group Content Transaction.
Session Session Charge Information is provided for chargeable 30 MSESS Severe Item Charged Item missing within
Charge elements within Mobile Session call/events. group.
Information
The group must contain Charged Item and Call Type Group 31 MSESS Severe Item Exchange Rate Code missing
and at least one occurrence of Charge Detail. within group and one or more Charge
within an associated Charge Detail is
Conditionality: greater than zero.
Mobile Session 32 MSESS Severe Item Call Type Group missing within
group
33 MSESS Severe Group Charge Detail missing within

group.
34 MSESS Severe Group Tax Information missing within

roaming agreement for that particular
call. Tax Information group missing
must be interpreted as Tax Value zero.
36 MSESS Severe Occurrence of group Charge Detail

containing Charge Type ‘00’ missing
within group.
37 MSESS Severe More than one occurrence of Charge
V36.4 Page 200 of 317


Code Level
Detail present with the same Charge
Type value.
38 MSESS Severe Breakout of Charge Types AIR (01)

and/or TOLL (03) not present on a
duration based charge, but expected in
accordance with roaming agreement;
that is only Charge Type 00 present
within group. This validation rule can
be applied only where bilaterally
agreed between sender and recipient
and where the call charge is greater
than 0.
39 MSESS Severe In accordance with roaming

agreement, charges are defined in
individual Charge Types, but the
Charge for Charge Type 00 does not
equal sum of Charges for the other
Charge Types as stated within roaming
agreement. This validation rule can be
applied only where bilaterally agreed
between sender and recipient.
40 MSESS Severe Group Tax Information present within

(zero).
41 MSESS Warning Group Tax Information present within

V36.4 Page 201 of 317


Code Level
(zero).
SIM Contains the identification of a chargeable subscriber identified 30 MOC Severe IMSI missing within group.
Chargeable by an IMSI. MTC
Subscriber SS
The group must contain the IMSI of the chargeable subscriber GPRS
and may optionally contain an MSISDN.
32 MOC Severe MSISDN missing within group but
Operators may bilaterally agree to make transfer of the MTC expected in accordance with roaming
MSISDN mandatory. SS agreement.
GPRS
Conditionality
Mandatory within group Chargeable Subscriber where MIN
Chargeable Subscriber is not present.
SIM Toolkit The SIM Toolkit Indicator will be present when the call has 10 MOC Warning Syntax error
Indicator been initiated by the SIM Toolkit application. MTC
MSG
MO Basic Call Information 20 MOC Warning Value out of range
MT Basic Call Information MTC
Messaging Event MSG
Mobile Session MSESS
where the call has been initiated by the SIM toolkit.
Values:
1 initiated by SIM toolkit
SMS The SMS Destination Number item contains the actual 10 MOC Severe Syntax error.
Destination destination (intended recipient) of the SMS text message.
Number 20 MOC Severe Value out of range.
Derivation:
Derived from item destinationNumber
(SmsTpDestinationNumber) (See Annex C – CS Domain
Charging and PS Domain Charging).
V36.4 Page 202 of 317


Code Level
Must be populated with the digits exactly as entered by the
subscriber.
Conditionality:
Must be present within group Destination for SMS MO calls
when the information is available from the network.
Values:
Each digit is numeric (0-9) or contains ‘+’, ‘*’ or ‘#’.
SMS The SMS Originator holds the identification of the actual 10 MTC Warning Syntax error.
Originator sender of the SMS (not the SMSC). Must be populated with the
data as received from the network. Note: Error Code 20 removed in TAP
release 3.11 (01 May 2005).
Conditionality:
Must be present within group Call Originator where
available from the network and TeleService Code indicates
SMS usage.
Specification To enable a PMN to encode and/or read a file it is necessary to 10 Notifictn Fatal Syntax error.
Version uniquely identify the format. This is achieved through the Btch Ctrl
Number Specification Version Number.
20 Notifictn Fatal Value out of range.
There must be a Release Version Number associated with this Btch Ctrl
item.
Conditionality:
Mandatory within group Notification.
Value:
3 for TAP3
Supplementary A code which uniquely defines the supplementary service, a 10 SS Severe Syntax error.
Service Code group of supplementary services, or a USSD message.
11 MOC Warning Syntax error.
Derivation for Supplementary Service:
V36.4 Page 203 of 317


Code Level
GSM item SupplementaryServiceCode (See Annex C – CS 20 SS Severe Value out of range.
Domain Charging).
The code is derived by taking the MAP encoding (See 21 MOC Warning Value out of range.
Annex C – Supplementary Service Codes) and translating
bits 8-5 into a ‘hex’ character and bits 4-1 into a second 22 MOC Severe Value ‘FF’.
‘hex’ character.
30 SS Warning USSD, value ‘FF’, present and
Conditionality: associated Charge Information does
Mandatory within group Supplementary Service Used. not contain a charge greater than zero.
Mandatory within group Mobile Originated Call where a
supplementary service has been used in conjunction with
the call unless supplied in a separate Supplementary
Service Event record.
Values:
00 All supplementary services
10 All line identification services
11 Calling number identification presentation
12 Calling number identification restriction
13 Connected number identification presentation
14 Connected number identification restriction
18 All name identification SS
19 Calling name presentation
20 All call forwarding
21 Call forwarding unconditional
24 Call deflection
28 All conditional Call Forwarding
29 Call forwarding on mobile subscriber busy
2A Call forwarding on no reply
2B Call forwarding on subscriber not reachable
30 All call offering services
31 Call transfer
40 All call completion services
41 Call waiting
42 Call hold
V36.4 Page 204 of 317


Code Level
43 Completion of calls to busy subscribers – origination
side
44 Completion of calls to busy subscribers – destination
side
45 Multicall
50 All multi party services
51 Multi party service
60 All community of interest services
61 Closed user groups
70 All charging supplement services
71 Advice of charge (information)
72 Advice of charge (charging)
80 All additional info transfer services
81 UUS1 user to user signalling
90 All call barring
91 All Barring of outgoing Call Services
92 Barring of all outgoing calls
93 Barring of all outgoing international calls
94 Barring of all OG international except HPMN
99 All Barring of incoming Call Services
9A Barring of all incoming calls
9B Barring of all IC calls when outside HPMN
FF USSD Message
Supplementary A Supplementary Service Event element represents usage of 30 SS Severe Mandatory group Chargeable
Service Event supplementary services or an USSD message. The Subscriber missing within group.
supplementary service can happen outside or in conjunction
with a standard call dependent on network configuration. 31 SS Warning Item RAP File Sequence Number
missing and SS previously received
Chargeable Subscriber, Location Information, Equipment and rejected.
Identifier and Supplementary Service Used must be present.
32 SS Warning Item RAP File Sequence Number
RAP File Sequence Number is conditionally present. present and SS not previously
V36.4 Page 205 of 317


Code Level
optional dependent on bilateral agreement. 33 SS Severe Mandatory group Location Information
Conditionality:
Mandatory within an occurrence of group Call Event Details 35 SS Warning Item RAP File Sequence Number
where none of the following are present; Mobile Originated present and TAP transfer batch being
Call, Mobile Terminated Call, Service Centre Usage, GPRS resubmitted as corrected (having been
Call, Content Transaction or Location Service. previously rejected with fatal error).
36 SS Severe Mandatory group Supplementary

Service Used missing within group.

Supplementary The Supplementary Service Parameters element is an element 10 SS Warning Syntax error.
Service of the Supplementary Service Used. The contents of the
Parameters element and the value it represents is entirely dependent upon
the Supplementary Service Action. 20 SS Warning Value out of range.
Derivation for Supplementary Service:

GSM item ssParameters (See Annex C – CS Domain
Charging).
Conditionality:
Must be present within group Supplementary Service Used
where relevant, i.e. for those Supplementary Service
Actions detailed below.
Note: In the case of USSD message, when the whole

message content is not available, at least the USSD
service code must be present.
Values:
V36.4 Page 206 of 317


Code Level
Event Action Parameter
Call forward Reg’n Forwarded to number
unconditional
Call fwd busy Reg’n Forwarded to number
Call fwd no reply Reg’n Forwarded to number
Call fwd not reachable Reg’n Forwarded to number
Explicit Call Transfer Inv’n Transferred to number
USSD message USSD The contents of the
Inv’n USSD message as
entered by the user or
sent by the mobile
station
Supplementary This element details the Supplementary Service used and 30 SS Severe Mandatory item Supplementary
Service Used relevant charging information. Service Code missing within group.
The group must contain the fields Supplementary Service 31 SS Severe Mandatory item Action Code missing
Code, Action Code and Charging Timestamp. Conditionally within group.
the following information may also be present; Supplementary
Service Parameters, Charge Information and Service Code 32 SS Warning Item Supplementary Service
(which may be repeated for each service affected). Parameters present when
Supplementary Service is not for call
Conditionality: forward registration or does not
Within group Supplementary Service Event the group is represent USSD usage.
mandatory and may only occur once.
33 SS Warning Item Supplementary Service
Parameters not present when
Supplementary Service is for call
forward registration or invocation
usage.
36 SS Severe Mandatory item Charging Timestamp

101 SS Severe Invalid or non transferable
V36.4 Page 207 of 317


Code Level
Supplementary Service Code and
Action code combination present within
group.
Note: Error codes 34, 35, 37, 38 &

May 2005).
4.17 T
Code Level
TAP Currency TAP Currency contains the Currency Code which identifies the 10 Acctng Fatal Syntax error.
currency used for charges throughout the Transfer Batch
where that currency is not in the standard SDRs. 20 Acctng Fatal Value out of range.
Note: This error cannot be raised for
The use of a currency other than SDRs will be by bilateral the values XDR and SDR.
agreement. The item is only provided for use in internal
markets. 200 Acctng Fatal TAP Currency not in line with bilateral
agreement.
Derivation:
ISO 4217 [26].
Optionality:
Only present within internal markets where agreed
bilaterally.
Conditionality:
Subject to optionality, must be present within Accounting
Information when currency other than Special Drawing
Rights is used as specified in the roaming agreement.
Example:
V36.4 Page 208 of 317


Code Level
EUR Euro
INR Indian rupee
USD US Dollar
TAP Decimal Identifies the number of decimal places used within all absolute 10 Acctng Fatal Syntax error.
Places monetary values within the TAP file.
The same number of decimal places must be present for all
tax, discount, charge and audit values throughout the whole
TAP file.
Conditionality:
Mandatory within group Accounting Information.
Values:
Range 0 – 6
Tax Indicator This indicator, set by the Sender and passed to the Recipient, 10 Acctng Warning Syntax error.
indicates that the related tax is a Value Added Tax.
20 Acctng Warning Value out of range.
Conditionality:
Can be present within group Taxation where the related tax
is a Value Added Tax. Indication of a Value Added Tax by
population of the field is optional and up to the Sender.
Values:
1 Value Added Tax
Tax A repeating group containing the Tax Rate Code and the Tax 30 Calls Severe Mandatory item Tax Rate Code
Information Value and, where applicable Taxable Amount. missing within group.
Each element of Charge Information may have several tax 31 Calls Severe Mandatory item Tax Value missing
elements associated with it, for example national tax, regional within group.
tax, local tax.
Conditionality: release 3.11 (01 May 2005).
There must be one occurrence within Charge Information
V36.4 Page 209 of 317


Code Level
for each tax element associated with the Charge
Information (see also Taxation).
There must be one occurrence within group CAMEL

Service Used for each tax element associated with the
CAMEL Invocation Fee.
There must be one occurrence within Session Charge

Information for each tax element associated with the
Session Charge Information (see also Taxation).
There must be one occurrence within group Messaging

Event for each tax element associated with the Charge
(see also Taxation).
Tax Rate A tax rate associated with a Tax Type and Tax Rate Code. 10 Acctng Fatal Syntax error.
The Tax Rate defines the rate applicable to the charge. Due to
the fact that the charge may not be invoiced until a later point 20 Acctng Fatal Value out of range.
in time and that some national legislations dictate that the tax
rate applicable is determined by the invoice date, there is a
possibility that the rate on the invoice may differ from the rate
on the transfer. However, the likelihood of this happening is
extremely low.
The rate is given to 5 decimal places.
Conditionality:
Mandatory within group Taxation except where the
associated Tax Rate Code represents an absolute/fixed tax
value in which case it must not be present.
Values:
00.00000 thru 99.99999
Tax Rate Code A code associated with a Tax Type and Tax Rate. 10 Acctng Fatal Syntax error.
V36.4 Page 210 of 317


Code Level
Conditionality: 11 Calls Severe Syntax error.
Mandatory within group Taxation.
Mandatory within group Tax Information. 20 Acctng Fatal Value out of range.
Mandatory within group AUR Tax Information
100 Calls Severe Specified Tax Rate Code was not
Values: defined in the group Taxation
Range 0 .. 999
200 Calls Severe The referenced Tax Rate is not in line
with the roaming agreement at the
corresponding call date. Note that,
where variable tax rates apply to the
call/event the exact validation of the
tax rate may not be possible and,
therefore, cannot be carried out.
Tax Type The type of tax represented by the Tax Rate Code and Tax 10 Acctng Fatal Syntax error.
Rate combination.
Conditionality:
Mandatory within group Taxation.
Values:
01 National (for example Federal, Dominion, VAT,
etc.)
02 Regional (for example State, Province)
03 County
04 Local/City
Note: Tthe above tax types may represent specific taxes, for
example any of Public Utilities, Sales & Use, Communications
taxes may be National, Regional, County or Local/City.
Tax Value The actual value of the tax associated with the Tax Code and 10 Calls Severe Syntax error.
Charge Information.
The Tax Value must be of a value greater than or equal to
V36.4 Page 211 of 317


Code Level
zero. 22 Calls Severe Where the associated Tax Rate Code
The value is in SDRs with the number of decimal places relates to a Tax Rate, the Tax Value
defined by item TAP Decimal Places. Note the currency may does not correspond to the Taxable
be subject to internal market bilateral agreements, see TAP Amount (or, where no Taxable Amount
Currency. is present, does not correspond to the
total Charge within Charge
Conditionality: Information) and Tax Rate.
Mandatory within group Tax Information. Note 1: Rounding rules are at the
Values: tolerance of 0.02 units of TAP
>= 0 (zero) Currency must be allowed
(independent of the number of decimal
places used for the TAP file).
the expected Tax Value is zero.
Note 3: In the absence of Taxable
Amount the Tax Value must always be
validated against the total charge
(Charge Type 00) in the given Charge
Information, even if another Charge
Type has been specified in the
definition of the applied Tax Code in
Taxation.
200 Calls Severe Tax Value is not in line with the

roaming agreement at the
corresponding call event date.
Note that, where variable tax rates
apply to the call event the exact
validation of the tax rate may not
possible and, therefore, cannot be
carried out.
Note 1: Rounding rules are at the
tolerance of 0.02 units of TAP
V36.4 Page 212 of 317


Code Level
Currency must be allowed,
independent of the number of decimal
places used for the TAP file.
the expected Tax Value is zero.
Note 3: This error cannot be raised
where both the Charge and the Tax
Value are zero (0) for the following
scenarios:
Mobile Terminated Calls except SMS
(Teleservice Code 20 or 21)
Mobile Session with Mobile Session
Service “MT Voice over LTE”
Taxable The actual part of the Charge to which the Tax Value and Tax 10 Calls Severe Syntax error.
Amount Rate (Code) relate.
The Taxable Amount must of a value greater than zero.
Note: When the associated tax is defined with a Charge Type 100 Calls Severe Taxable Amount not in line with
then the Taxable Amount should be populated based on the roaming agreement.
charges with the same Charge Type.

defined by TAP Decimal Places. Note that the currency may be
subject to internal market bilateral agreements, see TAP
Currency.
Conditionality:
Must be present within group Tax Information where the
associated Tax Value and Tax Rate Code do not relate to
the total Charge within Charge Information.
Values:
> 0 (zero)
Taxation The Taxation table is a repeating group of Tax Rate Code, Tax 30 Acctng Fatal Mandatory item Tax Rate Code
V36.4 Page 213 of 317


Code Level
Type, Tax Rate, Charge Type and Tax Indicator. missing within group.
Tax Rate Code and Tax Type are mandatory. Tax Rate and 31 Acctng Fatal Mandatory item Tax Type missing
Charge Type are conditional. Tax Indicator is optional. within group.
This table is used on a once-off basis and applies only to the 33 Acctng Fatal More than one occurrence of group
transfer which contains it. A new table is sent with each with same Tax Rate Code where Tax
transfer. Codes are reusable from transfer to transfer. Type, Tax Rate and/or Charge Type
are not the same.
Conditionality:
Mandatory within group Accounting Information except 34 Acctng Warning More than one occurrence of group
where taxes are not applicable. One occurrence must be with same Tax Rate Code where Tax
present for each unique Tax Rate Code used within group Type and Tax Rate are the same (i.e.
Tax Information. duplicate Taxation table entries).
Note: Error codes 32 and 35 removed

in TAP release 3.11 (01 May 2005).
TeleService A code which uniquely defines a TeleService. 10 MOC Severe Syntax error.
Code MTC
Group TeleService Codes, identifiable by the description ‘All’,
should only be used where details of the specific services 11 SS Warning Syntax error.
affected are not available from the network.
Note that compound TeleService group codes can only occur MTC Note: Value 21 is only allowed for
in call independent supplementary service operations. MTC and value 22 is only allowed for
MOC.
Derivation: 21 SS Warning
GSM item TeleServiceCode (See Annex C – CS Domain Value out of range.
Charging).
The code is derived by taking the MAP encoding (See

Annex C – Teleservice Codes) and translating bits 8-5 into
a ‘hex’ character and bits 4-1 into a second ‘hex’ character.
V36.4 Page 214 of 317


Code Level
Conditionality:
Must be present within group Service Code where the type
of service used was a teleservice. Must not be present
when the type of service used was a bearer service and,
therefore, Bearer Service Code is present.
Values:
00 All teleservices
10 All Speech transmission services
11 Telephony
12 Emergency calls
20 All SMS Services
21 Short Message MT/PP
22 Short Message MO/PP
60 All Fax Services
61 Facsimile Group 3 & alternative speech
62 Automatic Facsimile Group 3
63 Automatic Facsimile Group 4
70 All data teleservices (compound)
80 All teleservices except SMS (compound)
90 All voice group call services
91 Voice group call
92 Voice broadcast call
Third Party A group containing information identifying the original calling Note: Error Codes 30, 31, 32, 33 and
Information party in a call forwarding call context. 34 removed in TAP release 3.10 (01
May 2003).
The group must contain a CLIR Status Indicator and Third
Party Number will be conditionally present.
Example:
Party S calls Party T and a conditional call forward takes
place to Party U.
The MOC relating to the call forward leg (from party T to
party U) will contain, in the Third Party Information, details
V36.4 Page 215 of 317


Code Level
of party S (subject to availability).
Conditionality:
Must be present within group Mobile Originated Call where
the associated Supplementary Service Code indicates a
conditional call forward invocation and the information is
Third Party The Third Party Number is the number identifying the original 10 MOC Warning Syntax error.
Number calling party in a conditional call forwarding context.
20 MOC Warning Number not represented in
Derivation: international format.
GSM item CallingNumber (See Annex C – CS Domain
Charging). This item is of type AddressString. It is
represented in TAP in international format, i.e. the number
begins with the country code related to the calling number.
Conditionality:
Must be present within group Third Party Information where
available.
Values:
Each digit is numeric (0-9)
Total Advised The sum of all the advised charges associated with the 10 Audit Fatal Syntax error.
Charge corresponding currency excluding those representing a refund
(Charge Refund Indicator). 20 Audit Fatal Value out of range.
The Total Advised Charge must not contain a negative value. 100 Audit Fatal Value does not match the calculated
sum of non refund advised charges
Note that charges from records with severe errors should also associated with the same currency.
be included where possible.

Places.
V36.4 Page 216 of 317


Code Level
Conditionality:
Mandatory within group Total Advised Charge Value.
Values:
> or = 0 (zero)
Total Advised The sum of all the advised charges associated with the 10 Audit Fatal Syntax error.
Charge Refund corresponding currency representing a refund (Charge Refund
Indicator). 20 Audit Fatal Value out of range.
The Total Advised Charge Refund must be greater than zero. 100 Audit Fatal Value does not match the calculated
Note that charges from records with severe errors should also sum of refund advised charges
be included where possible. associated with the same currency.

Places.
Conditionality:
Present within group Total Advised Charge Value where
refunds are present and the total is greater than zero.
Values:
> (zero)
Total Advised A repeating group holding the sums of all advised charges and 30 Audit Fatal Mandatory item Total Advised Charge
Charge Value commissions by associated currency. missing within group.
The group must contain Total Advised Charge. Conditional 100 Audit Fatal Item Total Commission expected and
items are Advised Charge Currency, Total Commission, Total not present.
Advised Charge Refund, Total Commission Refund.
101 Audit Fatal Item Total Commission Refund
Conditionality: expected and not present.
Present within group Audit Control Information where
Content Transactions are present within the file and there 102 Audit Fatal Item Total Advised Charge Refund
are Advised Charges present within one or more of the expected and not present.
Content Transactions.
V36.4 Page 217 of 317


Code Level
Total Call The item contains the actual total duration of a call event as a 10 MOC Severe Syntax error.
Event Duration number of seconds. MTC
GPRS
The Total Call Event Duration must always contain the call MSESS
duration calculated from the call end time (channel release)
minus the Call Event Start Timestamp, or Service Start 20 MOC Severe Value out of range
Timestamp, as applicable. MTC
GPRS
The item is used, in conjunction with the Call Event Start MSESS
Timestamp or Service Start Timestamp (and UTC Time Offset
Code) to calculate the call event end time. This is needed for 100 MOC Severe Total Call Event Duration is greater
ageing calculations and validation against the File Available MTC than 0 (zero) for SMS call.
Timestamp.
200 GPRS Warning Total Call Event Duration exceeds limit
Conditionality: defined in BA.12 [12].
Mandatory within groups Note: Not applicable to Wi-Fi usage.
Mobile Session
Values:
> or = 0
Note: for SMS calls the value must be 0 (zero).

Total Charge The sum of all the charges associated with Charge Type 00 10 Audit Fatal Syntax error.
and CAMEL Invocation Fee, excluding those representing a
refund (Charge Refund Indicator). 20 Audit Fatal Value out of range.
The Total Charge must not contain a negative value. 100 Audit Fatal Value does not match the calculated
sum of non refund charges which
Note that charges from records with severe errors must also be includes sum of CAMEL Invocation
included where possible. Fee for all CAMEL calls in the Transfer
Batch.
V36.4 Page 218 of 317


Code Level
Currency.
Conditionality:
Mandatory within group Audit Control Information.
Values:
> or = 0 (zero)
Total Charge The sum of all the charges associated with Charge Type 00 10 Audit Fatal Syntax error.
Refund representing a refund (Charge Refund Indicator).
20 Audit Fatal Value out of range (except zero).
The Total Charge Refund must be greater than zero.
21 Audit Fatal Item Total Charge Refund has a value
Note that charges from records with severe errors should also of zero.
100 Audit Fatal Value does not match the calculated
The value is in SDRs with the number of decimal places sum of refund charges associated with
defined by item TAP Decimal Places. Note the currency may Charge Type 00.
Currency.
Conditionality:
Present within group Audit Control Information where
Values:
> 0 (zero)
Total The sum of all the commissions associated with the 10 Audit Fatal Syntax error.
Commission corresponding currency excluding those representing a refund
The Total Commission must be greater than zero. 100 Audit Fatal Value does not match the calculated
V36.4 Page 219 of 317


Code Level
sum of non refund commissions
Note that commissions from records with severe errors should associated with the same currency.
also be included where possible.

Places.
Conditionality:
the non refund commissions total is greater than zero.
Values:
> 0 (zero)
Total The sum of all the commissions associated with the 10 Audit Fatal Syntax error.
Commission corresponding currency representing a refund (Charge Refund
Refund Indicator). 20 Audit Fatal Value out of range.
The Total Commission Refund must be greater than zero. 100 Audit Fatal Value does not match the calculated
sum of refund commissions associated
Note that commissions from records with severe errors should with the same currency.
also be included where possible.

Places.
Conditionality:
Values:
> 0 (zero)
Total Data The Total Data Volume identifies the total number of octets 10 Content Severe Syntax error.
Volume (bytes) within the one occurrence of Content Service Used.
20 Content Severe Value out of range.
V36.4 Page 220 of 317


Code Level
This item is used instead of items Data Volume Incoming and
Outgoing where the data direction cannot be separately
identified.
Conditionality:
Present within group Content Service Used when
information is available.
Values:
> or = 0 (zero)
Total Discount The sum of the Discount Values plus each application of a 10 Audit Fatal Syntax error.
Refund Fixed Discount Value contained in the batch representing a
refund (Charge Refund Indicator). 20 Audit Fatal Value out of range
The Total Discount Refund must be greater than zero. 100 Audit Fatal Value does not match the calculated
sum of refund discounts from Call
This is present for audit purposes only. Event Details.
Note that discount from records with severe errors should also

Currency.
Conditionality:
Present within group Audit Control Information where the
refund discount total is greater than zero.
Values:
> 0 (zero)
Total Discount The sum of the Discount Values plus each application of a 10 Audit Fatal Syntax error.
Value Fixed Discount Value contained in the batch excluding those
V36.4 Page 221 of 317


Code Level
representing a refund (Charge Refund Indicator). 20 Audit Fatal Value out of range
The Total Discount Value must not contain a negative value. 100 Audit Fatal Value does not match the calculated
sum of non refund discounts from Call
Note that discount from records with severe errors should also

Currency.
Conditionality:
Values:
> or = 0 (zero)
Total Tax The sum of the Tax Values contained in the batch representing 10 Audit Fatal Syntax error.
Refund a refund (Charge Refund Indicator).
20 Audit Fatal Value out of range
The Total Tax Refund must be greater than zero.
100 Audit Fatal Value does not match the calculated
This is present for audit purposes only. sum of refund taxes from Call Event
Details.
Note that tax from records with severe errors should also be
included where possible.

Currency.
V36.4 Page 222 of 317


Code Level
Conditionality:
Present within group Audit Control Information where the
refund tax total is greater than zero.
Values:
> 0 (zero)
Total Tax The sum of the Tax Values (Tax Value and AUR Tax Valu) 10 Audit Fatal Syntax error.
Value contained in the batch excluding those representing a refund
The Total Tax Value must not contain a negative value. 100 Audit Fatal Value does not match the calculated
sum of non refund taxes from Call
Note that taxes from records with severe errors should also be
included where possible.

Currency.
Conditionality:
Values:
> or = 0 (zero)
Total The item contains the actual total duration of a Content 10 Content Severe Syntax error.
Transaction Transaction as a number of seconds.
Duration 20 Content Severe Value out of range.
The item can be used in conjunction with the latest associated
timestamp (Order Placed, Requested Delivery or Actual
Delivery timestamps) to calculate the Content Transaction end
time used for age validation.
V36.4 Page 223 of 317


Code Level
Conditionality:
Present within group Content Transaction Basic Info where
available.
Values:
>=0
Tracked Information relating to equipment used by the Tracked 30 LCS Warning Mandatory item Equipment Id Type
Customer Customer. missing within group.
Equipment
The group, when present, must contain items Equipment Id 31 LCS Warning Mandatory item Equipment Id missing
Conditionality:
Present within group Tracked Customer Information where
available.
Tracked Information identifying the home environment of the Tracked 30 LCS Severe Mandatory item Home Id Type missing
Customer Customer. within group.
Home Id
The group, when present, must contain items Home Id Type 31 LCS Severe Mandatory item Home Identifier
and Home Identifier. missing within group.
Conditionality:
Tracked Customer Information where available.
Tracked The identification of the customer being tracked. 30 LCS Severe Mandatory item Customer Id Type
Customer missing within group.
Identification The group must contain items Customer Id Type and Customer
Identifier. 31 LCS Severe Mandatory item Customer Identifier
Conditionality:
Tracked Customer Information.
Tracked Information identifying the tracked customer. 30 LCS Severe Mandatory group Tracked Customer
V36.4 Page 224 of 317


Code Level
Customer The group must contain at least one occurrence of group Identification missing within group.
Information Tracked Customer Identification with all other groups being
conditional on availability.
The group identifies a single tracked customer. As the

identification of a customer/home/location may be done in
more than one way or by combination of elements (for example
MSISDN-IMSI-Account Number: Home BID-TADIG Code:
Country-Region) the groups containing these elements may
occur more than once.
Conditionality:
Mandatory within group Location Service where it is not the
same as the tracking customer.
Tracked Information on the location of the tracked customer. 30 LCS Warning Mandatory item Location Id Type
Location This is not the actual location as delivered by the location
service request, it identifies the geographical or virtual location 31 LCS Warning Mandatory item Location Identifier
of the tracked customer, for example country, network, ip missing within group.
address.
Availability of this data may be subject to local regulatory

rules/laws.
Conditionality:
Must be present within group Tracked Customer
Information where available.
Tracking Information relating to equipment used by the Tracking 30 LCS Warning Mandatory item Equipment Id Type
Customer Customer. missing within group.
Equipment
The group, when present, must contain items Equipment Id 31 LCS Warning Mandatory item Equipment Id missing
Conditionality:
V36.4 Page 225 of 317


Code Level
Present within group Tracking Customer Information where
available.
Tracking Information identifying the home environment of the Tracking 30 LCS Severe Mandatory item Home Id Type missing
Customer Customer. within group.
Home Id
The group, when present, must contain items Home Id Type 31 LCS Severe Mandatory item Home Identifier
and Home Identifier. missing within group.
Conditionality:
Tracking Customer Information where available.
Tracking The identification of the customer requesting the tracking. 30 LCS Severe Mandatory item Customer Id Type
Customer The group must contain items Customer Id Type and Customer missing within group.
Identification Identifier.
31 LCS Severe Mandatory item Customer Identifier
Tracking Customer Information.
Tracking Information identifying the tracking customer. 30 LCS Severe Mandatory group Tracking Customer
Customer Identification missing within group.
Information The group must contain at least one occurrence of group
Tracking Customer Identification with all other groups being
conditional on availability.
Conditionality:
Must be present within group Location Service where the
Tracking Customer can be identified.
Tracking Information on the location of the tracking customer. 30 LCS Warning Mandatory item Location Id Type
Location This is the geographical or virtual location of the tracking
customer, for example country, network, ip address. 31 LCS Warning Mandatory item Location Identifier
Availability of this data may be subject to local regulatory
rules/laws.
V36.4 Page 226 of 317


Code Level
Conditionality:
Must be present within group Tracking Customer
Information where available.
Tracking The time interval measured in seconds between two 20 LCS Severe Value out of range.
Frequency consecutive location estimates for continuous/periodic tracking. Note: This error can only be raised for
TAP files made available on or after 24
Conditionality: May 2012.
LCS QoS Requested/Delivered
where applicable and available from the network
Values:
>=0 (zero)
Tracking The overall tracking period measured in seconds for 20 LCS Severe Value out of range.
Period continuous/periodic tracking. Note: This error can only be raised for
TAP files made available on or after 24
Conditionality: May 2012.
LCS QoS Requested/Delivered
where applicable and available from the network
Values:
>=) (zero)
Transaction The authorisation code passed to the Content Provider for this 10 Content Warning Syntax error.
Authorisation content transaction.
Code
This will only be present where there are no privacy/regulatory
implications and when the information is available.
Conditionality:
Present within group Content Service Used where
available.
Transaction Indicates that the Charged Party has requested the 10 Content Warning Syntax error.
V36.4 Page 227 of 317


Code Level
Description Transaction Description (short & detail) to be suppressed and
Suppression therefore not to be detailed on any correspondence to the 20 Content Warning Value out of range.
Charged Party.
Conditionality:
Present within group Content Service Used when the
Charged Party has requested the description of the detail
to be suppressed.
Values:
1 Suppress description
Transaction The item contains, in plain text, the long description detailing 10 Content Warning Syntax error.
Detail the Content Service. For example names and quantities of the
Description stocks traded, title of books purchased or name of ring tone
downloaded.
This item gives a more precise definition of the transaction

than the Transaction Short Description.
Conditionality:
Present within group Content Service Used where
available.
Transaction An identifier uniquely representing the Content Transaction for 10 Content Severe Syntax error.
Identifier the given Content Provider.
This will often be an identifier notified to the customer at the

time of transaction request, for example order number.
Conditionality:
Transaction The item contains, in plain text, the short description detailing 10 Content Warning Syntax error
Short the Content Service. For example Stock Information, Books, or
Description Mobile Accessories. 100 Content Warning Length greater than 24 characters.
V36.4 Page 228 of 317


Code Level
This item gives a more general definition of the transaction
than the Transaction Detail Description.
Conditionality:
Values:
Limited to maximum 24 characters length
Transaction Indicates the status of the Transaction when the status is 10 Content Severe Syntax error.
Status anything other than Normal or Success.
20 Content Severe Value out of range.
Conditionality:
Present within group Content Transaction Basic Info when
the status of the transaction is other than Normal/Success.
Values:
0 Unconfirmed
1 Failed
Transfer Batch A TAP file which must contain at least one Call Event Detail 30 Tf Batch Fatal Mandatory group Batch Control
and must also contain supporting Batch Control Information Information missing within group.
and Audit Control Information. Accounting Information must be
present where any Call Event Detail contains a charge. It may 31 Tf Batch Fatal Group Accounting Information not
also contain Message Description Information details where present and a charge is present within
these have been used within the batch. the Transfer Batch.
Conditionality: 32 Tf Batch Fatal Mandatory group Network Information

Mandatory within group Data Interchange. missing within group.
34 Tf Batch Warning Group Message Description

Information not present and a Service
Centre Usage is present within
Transfer Batch.
35 Tf Batch Fatal Group Call Event Details not present
V36.4 Page 229 of 317


Code Level
within group.
36 Tf Batch Fatal Mandatory group Audit Control

Information missing from group.

release 3.11 (01 May 2005).
Transfer Cut The timestamp used to select calls for transfer. All call records 10 Btch Ctrl Fatal Syntax error.
Off Timestamp available prior to the timestamp are transferred. This gives an
indication to the HPMN as to how ‘up-to-date’ the information 20 Btch Ctrl Fatal Value out of range.
is.
Where the timestamp is present within a Notification file it is 30 Btch Ctrl Fatal Mandatory associated item UTC Time
nominal showing that no data available for transfer are being Offset missing.
held by the Sender PMN with a Charging Timestamp prior to
this.
must be a UTC Time Offset associated with the item.
Conditionality:
Mandatory within group Notification.
Format:
CCYYMMDDHHMMSS

– 235959
Transparency An indicator which shows whether the service was used in 10 MOC Severe Syntax error.
Indicator transparent or non-transparent mode. The item is applicable MTC
only to UMTS calls.
Derivation: MTC
GSM item TransparencyIndicator (See Annex C – CS
V36.4 Page 230 of 317


Code Level
Domain Charging).
Conditionality:
Must be present within group Basic Service where call is
UMTS and the indicator is relevant.
Values:
0 Transparent
1 Non-Transparent
4.18 U
Code Level
User Protocol This item identifies the high layer user protocol signalled 10 MOC Severe Syntax error.
Indicator between the mobile station and the network. MTC

Derivation: MTC
Derived values using bits 0-3 of GSM/UMTS item Rate
Indication (See Annex C – CS Domain Charging). The
‘Source Value’ (see Values below) is derived using Other
Rate Adaption bits (2 & 3) followed by Rate Adaption bits (0
& 1).
Conditionality:
Must be present within group Basic Service where derivable
from the network supplied data (i.e. Rate Indication).
Values:
UPI Meaning Source Value (Rate
V36.4 Page 231 of 317


Code Level
Value Indication bits 2&3, 0&1)
0 No rate adaption nn00
1 V.110,I.460/X.30 rate nn01
adaption
2 ITU-T X.31 flag stuffing nn10
3 V.120 0011
4 H.223 & H.245* 0111
5 PIAFS 1011
Note: ‘nn’ represents any value.

* Note that H.324 (which is used by circuit switched video
telephony) uses the “H.223/H.245” setting at the protocol level.
UTC Time All timestamps are in the local time of the Sender PMN (or 10 Notifictn Warning Syntax error.
Offset Serving Network where appropriate). So that the time can be
equated to time in the Recipient PMN, the difference between 11 Network Fatal Syntax error.
local time and UTC time must be supplied.
12 Btch Ctrl Warning Syntax error and associated item is
Derivation: File Creation Timestamp.
UTC Time Offset = Local Time minus UTC Time
13 Btch Ctrl Fatal Syntax error and associated item is
Examples: Transfer Cut Off Timestamp.
Washington DC, USA 1000hrs 10/Oct/97 14 Btch Ctrl Fatal Syntax error and associated item is
UTC Time 1500hrs 10/Oct/97 File Available Timestamp.
UTC Time Offset = 10 – 15 = -5
15 Audit Warning Syntax error and associated item is
Madrid, Spain 1600hrs 10/Oct/97 Earliest Call Timestamp.
UTC Time 1500hrs 10/Oct/97
UTC Time Offset = 16 – 15 = +1 16 Audit Warning Syntax error and associated item is
Latest Call Timestamp.
V36.4 Page 232 of 317


Code Level
Sydney, Australia 0100hrs 11/Oct/97
UTC Time 1500hrs 10/Oct/97 20 Notifictn Warning Value out of range.
UTC Time Offset = (01 + 24) – 15 = +10
21 Network Fatal Value out of range.
(Note: where dates are different 24 hours are added to the
time of the greater date) 22 Btch Ctrl Warning Value out of range and associated
item is File Creation Timestamp.
Conditionality:
Mandatory within items 23 Btch Ctrl Fatal Value out of range and associated
File Creation Timestamp item is Transfer Cut Off Timestamp.
Transfer Cut Off Timestamp
File Available Timestamp 24 Btch Ctrl Fatal Value out of range and associated
Earliest Call Timestamp item is File Available Timestamp.
Latest Call Timestamp
Mandatory within group UTC Time Offset Information. 25 Audit Warning Value out of range and associated
Note that the HPMN needs the location and UTC Time Offset item is Earliest Call Timestamp.
for each type of timestamp. On a call level there might be
more than one UTC Time Offset valid. 26 Audit Warning Value out of range and associated
item is Latest Call Timestamp.
Format:
HHMM
Range:
-1300 to +1400 in steps of 15 MM (minutes)
UTC Time A code associated with a UTC Time Offset. 10 Network Fatal Syntax error.
Offset Code
The code is used with its associated timestamp to enable 11 Calls Severe Syntax error.
conversion of the Sender PMN’s local time to UTC time.
20 Network Fatal Value out of range.
Conditionality:
Mandatory within group UTC Time Offset Information. 100 Calls Severe Specified UTC Time Offset Code not
Mandatory within items defined in group UTC Time Offset
Call Event Start Timestamp Information.
Charging Timestamp
V36.4 Page 233 of 317


Code Level
Charge Detail Timestamp
Deposit Timestamp
Completion Timestamp
Order Placed Timestamp
Requested Delivery Timestamp
Actual Delivery Timestamp
LCS Request Timestamp
PDP Context Start Timestamp
Service Start Timestamp
Values:
Range 0 .. 99
UTC Time A table containing UTC Time Offset Information. 30 Network Fatal Mandatory item UTC Time Offset
Offset Code missing within group.
Information This table is used on a once-off basis and applies only to the
transfer which contains it. A new table is sent with each transfer. 31 Network Fatal Mandatory item UTC Time Offset
Codes are reusable from transfer to transfer. missing within group.
Conditionality: 32 Network Fatal More than one occurrence of group

One or more occurrences must be present within group with same UTC Time Offset Code
Network Information. where UTC Time Offset is not the
same.
33 Network Fatal More than one occurrence of group

with same UTC Time Offset Code
where UTC Time Offset is the same.
4.19 V
Code Level
Vertical The vertical accuracy delivered for an LCS request measured in 20 LCS Severe Value out of range.
Accuracy metres. Note: This error can only be raised
Delivered for TAP files made available on or
V36.4 Page 234 of 317


Code Level
Derivation: after 24 May 2012.
GSM/UMTS item Ext-GeographicalInformation (See Annex C
– LCS Charging). The contents of the first 4 bits of the first
octet indicate the type of shape used for the determination of
the position. Dependant on the shape actually used the
horizontal uncertainty has to be extracted from the remaining
octets and has to be translated into a value in metres using
the standards formulae, see Annex C – LCS Charging. The
result must be rounded to full metres.
Conditionality:
LCS QoS Delivered
Values:
>=) (zero)
Vertical The vertical accuracy requested for an LCS request measured in 20 LCS Severe Value out of range.
Accuracy metres. Note: This error can only be raised
Requested for TAP files made available on or
Derivation: after 24 May 2012.
LCS QoS IE Octet 5 (See Annex C – LCS Charging). The 7
least significant bits of octet 5 need to be interpreted as an
uncertainty altitude code. This needs to be transformed into
a value in metres by applying the standards formulae, see
Annex C – LCS Charging. The result must be rounded to full
metres.
Note: TS 23.032 [36] specifies different formulas for the
calculation of the horizontal and vertical accuracy in metres.
Conditionality:
LCS QoS Requested
V36.4 Page 235 of 317


Code Level
Values:
>=) (zero)
V36.4 Page 236 of 317

4.20 Context Abbreviations

Abbreviation Context
Acctng Accounting Information
Audit Audit Control Information
AUR Aggregated Usage Record
Btch Ctrl Batch Control Information
Calls Call Event Details
Content Content Transaction
GPRS GPRS Call
LCS Location Service
Mess Desc Message Description Information
MSESS Mobile Session
MOC Mobile Originated Call
MSG Messaging Event
MTC Mobile Terminated Call
Network Network Information
Notifictn Notification
SCU Service Centre Usage
SS Supplementary Service Event
Tf Batch Transfer Batch
Table 34: Context Abbreviations
5 Classification of Errors
5.1 Known Issues Impact

All validations must take into account those issues which have been identified since the last
release.
IDS TDS maintains and publishes a Known Issues List which highlights issues and, where
appropriate or applicable, workarounds.
The Known Issues List can be found on the GSMA Infocentre Roaming>Format Release
Pages>Known Issues Lists page (https://infocentre2.gsma.com/roaming/Format-Release-
Pages/Pages/Known-Issues-List-.aspx).
5.2 Severity Levels

All errors are assigned one of the following severity levels:
 Fatal
A fatal error puts into question the content of the complete file, i.e. all records in the file.
In case of a fatal error either the file format is not correct or the file control information
contains invalid data. When a fatal error is encountered in the file, the HPMN can refuse
liability for the complete file.
 Severe
Records with severe errors affect the ability to charge the subscriber. They should not
have been forwarded by the VPMN Operator to the HPMN Operator who may reject
V36.4 Page 237 of 317

financial liability for the individual call/event, a rejected call/event may be included in a
rejects and returns process where available.
 Warning
Records with warnings are billable, i.e. the problem does not affect the ability of the
HPMN to charge its customer. The record contains data that might be created as a result
of some failure or might cause problems for customer care. These errors are a result of
optional field validation. The HPMN is not obliged to report such errors and they may
instead opt to avoid raising them at all. The purpose of defining this type of error is to
provide a mechanism for the VPMN Operator to be informed about the deviations from
TAP standard so that they can correct any such errors to increase the quality of their
files.
The severity of errors may depend on the context in which the element or group appears in
the Transfer Batch.
In order to not stop the invoicing of all the call/events in a file when a call/event could be
rejected with both a ‘Fatal’ and a ‘Severe’ error the Recipient is advised to use the ‘Severe’
error and not the ‘Fatal’ one.
TD.57 contains all the validation rules that can be applied to a TAP3 file. The Recipient is
advised to apply only the rules that concerns the fields used by their billing system
and not all of them. Unnecessary RAP processing or even disputing will then be
prevented.
5.3 Naming and Numbering of Error Codes

The following rules apply to the naming and numbering of errors defined in the data
dictionary:
Error Code Validation Description

Range
10 to 19 Format Errors
The data does not match the picture value, for example alpha character in
numeric field. The error description refers to these values as Syntax error. Syntax
errors relate to the physical implementation document (section 6 Physical
Structure) where the data type for the item is specified. Explanatory comments in
the ASN.1 syntax have to be taken into account (for example the structure of an
Ipv4 address). Syntax errors cannot be raised based on the information in the data
dictionary as these errors must be explicitly reported as range errors.
All these errors are uniquely identified by error code and field name.
20 to 29 Value out of range in field
The value in a field does not match the range or is not in the list of values allowed
for this field.
30 to 49 Invalid group structure
The group has elements either missing but expected or present and not expected,
that is, the structure of the group is invalid.
V36.4 Page 238 of 317

Note: In cases where the physical ASN.1 structure of a TAP file contains an
additional group that allows for building a list of elements, any group structure
validation rules that apply to the group as defined in the Data Dictionary must be
applied to the lower level group as defined in the ASN.1 physical specification.
The effect of this is that the ‘list’ element is transparent.
100 to 199 Inconsistencies between fields
These errors affect more than one field and are caused by contradicting values.
There could be contradicting values in the subfields of one field, in different fields
of the same record, or for example contradictions between the file name and
values listed in the record.
All these errors have an error code in the range 100 to 199 and are uniquely
identified by error code and field name.
200 to 249 Specific Errors
Specific errors are errors that do not fit into one of the groups above. Possible
reasons are duplicate calls or old data.
All these errors have an error code in the range 200 to 249 and are uniquely
identified by error code and field name.
Table 35: Naming and Numbering of Errors
5.3.1 Bilaterally Agreed Validation Errors

Errors which may occur after proprietary validation rules as agreed by operators bilaterally.
A range of codes 9000-9999 is reserved for these types of error.
Note: These errors can only be used following an explicit agreement between the two
roaming partners to implement validation rules that are not defined in TD.57. These error
codes cannot be raised over the public interface without such explicit bilateral agreement
between the operators. For validation rules that are already defined in TD.57 the standard
TD.57 error codes must be used.
5.4 Other General Errors Not Listed in the Data Dictionary

Error Context Severity Validation Description
Code Level
50 Notifictn Fatal Unknown tag.
Tf Batch
The tag is not recognised as a valid tag within TAP and does not
occur at extension marker position.
Note that this can include tags where there is no bilateral

agreement for their use and the receiving party’s systems have not
been modified to be able to handle them.
51 Notifictn Fatal Non repeating element occurs more than once within the group.
Tf Batch
52 Notifictn Fatal Tag invalid within context, for example MO Basic Call Information
Tf Batch occurring within Mobile Terminated Call and does not occur at
extension marker position.
53 Notifictn Fatal File not encoded according to ASN.1 BER, for example file
V36.4 Page 239 of 317

Tf Batch received with a size of zero bytes.

54 Notifictn Warning Binary data after the first valid ASN.1 unit present in file and
Tf Batch ignored.
55 All Fatal Encoded INTEGER larger than 4 bytes and related data element is
not one of the elements specified in Abstract Syntax section where
allowed maximum is 8 bytes.
56 Audit and Fatal Encoded INTEGER larger than 8 bytes.
GPRS
57 All Warning Valid ASN.1 encoded information found and ignored at extension
marker position.
Note: Further processing of the ASN.1 data identified as being part

of extension marker information must not be applied.
Table 36: General Errors Not Included in Data Dictionary
Errors 50 – 53 above are deemed to be fatal as their occurrence is indicative of a corruption

within the ASN.1 syntax.
Note that during the validation process not all errors for a specific data element can be
reported because some errors make it impossible or unnecessary to continue validation of
the element, therefore, error codes should be reported in the following sequence:
 50 – 59
 30 – 49
 10 – 19
 20 – 29
It is not necessary to continue validation of an element once a ‘severe’ or ‘fatal’ error has
been encountered. If a ‘warning’ error is encountered it is still necessary to continue
validation in case a ‘severe’ or ‘fatal’ error is also present for the element.
Where an error has been found it is only necessary to report the first instance of the most
severe error to the sender PMN.
The above error 52 can only be applied if the physical ASN.1 syntax is violated. Logical
errors cannot be rejected using error 52.
For example: A Call Type Group present within the Charge Information for a Supplementary
Service Event does not violate the ASN.1 syntax.
The ASN.1 syntax allows production of elements with a size (length) of zero bytes. This is
valid according to BER but all parties creating TAP must take measures to avoid such
implementations. When such errors are encountered in a TAP file it is allowed to raise either
of the following errors:
 Syntax Error on the zero length item

 Group Structure Error applicable to the group which contains the item; this treats it as
though the zero length item were not present in the group.
The severity of the error must be according to the severity of the applicable Syntax or Group
Structure error. The Group Structure Error may not always be applicable.
V36.4 Page 240 of 317

A VPMN cannot treat an item with length zero as an invalid BER encoding, i.e. fatal error
code 53 (file not encoded according to ASN.1 BER) must not be applied.
For example; where the field Tax Value in Tax Information is present but has no content
(length is zero) the HPMN can only raise one of the following errors:
 Severe error code 10 (syntax error) on item Tax Value in the Calls context.
 Severe error code 31 (tax value missing) on group Tax Information in the Calls
context.
No other validation rule is applicable.
Where an empty ‘list’ construction element is found (represented by ‘sequence of’ keyword
in ASN.1 syntax) the underlying logical element is to be treated as not present.
Where a single ‘logical’ field, as per the Data Dictionary, is represented physically in ASN.1
as a composite element consisting of several ASN.1 fields, physical structure errors like
missing elements should be handled as syntax error in the ‘logical’ field.
5.5 Validation Rules Not Described in the Data Dictionary

Error Context Severity Validation Description
Code Level
250 MOC Severe Call is duplicate. Chargeable Subscriber, Recording Entity Type
and Identification, Call Event Start Time, Called Number, Service
Code and Total Call Duration match call record already processed
and the call reference is identical in both call records. If Called
Number is not present Dialled Digits must be used.
251 MTC Severe Call is duplicate. Chargeable Subscriber, Recording Entity Type
and Identification, Call Event Start Time, Calling Number, Service
Code and Total Call Duration match call record already processed
and the Call Reference is identical in both call records.
252 SS Severe Event is duplicate. Chargeable Subscriber, Recording Entity Type
and Identification, Charging Timestamp, Supplementary Service
Code and Action match call record already processed and the Call
Reference is identical in both call records.
253 SCU Severe Event is duplicate. SCU Chargeable Subscriber, Recording Entity
Type and Identification, Deposit Timestamp, Non Charged Number
and Message Type match call record already processed.
255 GPRS Severe Call is duplicate. Chargeable Subscriber, Recording Entity
Identification (where the Recording Entity Type is GGSN, P-GW or
Wi-Fi Billing Information Recording Entity), Charging Id and Call
Event Start Time match call record already processed and an
Operator Specific Information (OSI) starting with the keyword
“AccountingSessionID:” is identical in both cases.
256 Content Severe Call is duplicate if Content Provider Name, Transaction Identifier,
Charge Refund Indicator match Content Transaction already
processed.
257 LCS Severe Call is duplicate if Recording Entity Type and Identification, Call
Reference, LCS Request Timestamp, Response Time, Tracking
Customer and Tracked Customer is the same as Location Service
record already processed.
V36.4 Page 241 of 317

258 MSG Severe Message is a duplicate. IMSI, Service Start Timestamp, Messaging
Event Service and Event Reference are identical in both call
records.
259 MSESS Severe Call is a duplicate. IMSI, Service Start Timestamp, non-charged
party (see note below) , Mobile Session Service, Total Call Event
Duration and Event Reference are identical in both call records.
Note: Non charged party can be represented in either Non Charged

Party Number or Non Charged Public User Id and if any of the two
elements (on two different CDRs) have the same content then they
are considered duplicates (case sensitive string compare, leading
and trailing spaces to be ignored).
Such duplicate scenarios are:
 Non Charged Party Number in CDR1 matches Non
Charged Party Number in CDR2.
 Non Charged Party Number in CDR1 matches Non
Charged Public User Id in CDR2.
 Non Charged Public User Id in CDR1 matches Non
Charged Party Number in CDR2.
 Non Charged Public User Id in CDR1 matches Non
Charged Public User Id in CDR2.
280 AUR Severe Record is a duplicate. Aggregated Usage Date Start, Aggregated
Usage Date End (when present), Serving Network (when present),
Aggregation Identifier (when present), Aggregated Chargeable Unit
Type and Aggregated Chargeable Units are identical in both
records.
Note:
The duplicate check is made against previously accepted records that were transferred in a
chargeable data (CD) file. Records that were transferred in test data (TD) files cannot be used as a
basis for the duplicate check. A record is not deemed accepted if it is being rejected in RAP.
Timestamp fields used for the duplicate call check must be normalised to UTC before comparing
them to each other. For the purpose of normalisation the associated UTC offsets must be used. This
rule applies to Call Event start time (MOC, MTC, GPRS), Charging Timestamp (SS), Deposit
Timestamp (SCU) and LCS Request Timestamp (LCS).
When the Call Reference is not present (or has a value of 0) calls may be mistakenly detected as
duplicate calls for example in specific cases of call forwarding. Such cases should be handled with
care and any disputes must be resolved manually.
Where the Recording Entity Identification refers to an IPv6 address leading zeros in the segments of
the address must be ignored for duplicate check.
The Call Reference is used for the duplicate check criteria only when the call references in both call
records contain non zero values. Leading zeroes in Call Reference must be ignored for duplicate
checking.
The Operator Specific Information (OSI) starting with the keyword “AccountingSessionID:” is used for
duplicate check criteria only when populated in both call records and only when the GPRS Call CDRs
represent Wi-Fi sessions (identified by RecordingEntityType).
Note that where ‘Chargeable Subscriber’ is referenced above for duplicate call check purposes IMSI
or MIN by itself is sufficient. When IMSI or MIN is present in a call MSISDN and/or MDN, when also
present in the same call, must not be included when performing the duplicate check.
Although not part of the standard duplicate check, for practical reasons, the Recipient may choose to
include the Sender information when implementing the duplicate check. Under these circumstances
V36.4 Page 242 of 317

truly duplicate TAP events submitted in different Sender TAP files may not be detected.
142 Calls Severe Call Event Details ends after the File Available Timestamp. The
timestamp of the call event completion may be calculated from the
Call Event Start Timestamp and the Total Call Event Duration.
For Aggregated Usage Record, where present, the Aggregated

Usage Date End must be used for the completion time. Where
Aggregated Usage Date End not present use Aggregated Usage
Date Start.
For Supplementary Service Event the Charging Timestamp must be

used for the completion time.
For SCU the Completion Timestamp should be taken into

consideration
For Content Transaction the latest timestamp of Order Placed

Timestamp, Requested Delivery Timestamp or Actual Delivery
Timestamp in conjunction with the Total Transaction Duration must
be used.
For Location Service the LCS Request Timestamp must be used in

conjunction with the Response Time.
For Mobile Session the timestamp of the call event completion may
be calculated from the Service Start Timestamp and Total Call
Event Duration.
For Messaging Event the Service Start Timestamp must be used for
the completion time.
260 Calls Warning Call old. Call is older than ‘Standard Timescale’ specified in BA.08
[10].
261 Calls Severe Call older than allowed in ‘Exceptional Situations’ in BA.08 [10]
262 Btch Ctrl Warning Difference between actual date/time file received and File Available
Notifictn Timestamp is greater than the Standard File Transmission
Timescale as specified in BA.08 [10].
263 Btch Ctrl Fatal Difference between actual date/time file received and File Available
Timestamp is greater than the Exceptional File Transmission
Timescale as specified in BA.08 [10].
Note:
Call age is calculated as difference between the call completion time or, where the call/event has no
duration, the timestamp associated with the call/event and the File Available Timestamp normalized
to use the same time basis (for example UTC). For Aggregated Usage Record there is an implicit
timestamp of 23:59:59, this applies to whichever date is being used for the calculation (Aggregated
Usage Date Start / Aggregated Usage Date End).
In the case of Aggregated Usage Record the Aggregation Usage Start Date must be used. The
Aggregation Usage Start Date must be compared against the date part of the File Available
Timestamp only.
In case of SCU either the Completion or Deposit Timestamp should be used to get call event age
depending on the value of charging point: completion time when ‘C’ and deposit time when ‘D’.
In the case of Content Transaction the latest timestamp of Order Placed Timestamp, Requested
Delivery Timestamp or Actual Delivery Timestamp in conjunction with the Total Transaction Duration
must be used.
V36.4 Page 243 of 317

For Location Service the LCS Request Timestamp must be used in conjunction with the Response
Time to find the end time.
‘Standard Timescale’ and ‘Exceptional Situations’ age can be redefined on a bilateral basis.
‘Standard’ and ‘Exceptional’ ‘File Transmission Timescales’ can be redefined on a bilateral basis.
270 Audit Warning Total number of occurrences of group Call Event Details within the
TAP transfer batch exceeds 200,000.
271 Tf Batch Fatal The size of the TAP Transfer Batch file is larger than 100MB (100 x
1024 x 1024 bytes).
This error should not be applied if the file can be processed.
272 Tf Batch Fatal The applicable IOT of the Sender does not comply with the
applicable regulatory terms.
Table 37: Validation Rules Not Included in the Data Dictionary
5.6 Text Representation of IP Addresses

The text representation of IP addresses must be formatted as follows:
For Ipv4 addresses as x.x.x.x where ‘x’s represent the decimal values of the four 8-bit
segments. Any section of the address can have up to 3 digits. Leading zeros for any
section of the address are optional.
Examples of valid Ipv4 addresses:

 192.68.0.13
 192.068.000.013
For Ipv6 addresses as x:x:x:x:x:x:x:x where ‘x’s represent the hexadecimal values of the
eight 16-bit segments. Leading zeros for any section of the address are optional.
Compression of zeros by usage of the symbol ”::” is not allowed. This might require a
normalisation of the Ipv6 address for population in TAP when read from the network in a
compressed form. Presentation of the last 2 sections of the address in Ipv4 format is not
allowed either. Hexadecimal characters can be upper or lower case.
Examples of valid Ipv6 addresses:
 FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
 1080:0:0:0:8:800:200c:417a
 28:04:64:aB:Cd:0:0:0
Ipv4 and Ipv6 addresses must not include embedded blank spaces.
Note that IP addresses are ASCII strings and therefore leading and trailing spaces must be
discarded.
5.7 Validation of ASCII String Type elements

For the following ASCII String elements, case sensitivity will not be part of any validation:
 Access Point Name NI

 Access Point Name OI
 Called Place
 Called Region
V36.4 Page 244 of 317

 Content Provider Name

 Message Description
 Public User ID
 Serving Location Description
 Transaction Detail Description
 Transaction Short Description
For example, if a Serving Location Description is specified in the IOT as “Cruiseship”, the
corresponding TAP element with a value of “cruiseship”, “CRUISESHIP” or “Cruiseship” will
pass the validation successfully.
All other elements are validated as per the Data Dictionary and case sensitive validation will
be applied as stated.
5.8 Identification of Emergency Calls

For emergency calls over circuit switched these can be identified in TAP in the following
ways:
 Usage of Teleservice 12, in this case Dialled Digits may not be present.
 Usage of Teleservice 10 or 11 together with population of Dialled Digits. The value of

Dialled Digits can be “112” or any other emergency call short code as defined in the
VPMN’s AA.14.
For emergency voice calls over LTE, these can be identified in TAP in the following way:
 Usage of value ‘3 ‘ (Emergency call over LTE) within Mobile Session Service.
5.9 TAP Record Charge Validation Procedure

This section defines the TAP record Charge validation procedure. All operators, or their
agents, must follow the below procedure when validating TAP charges in received TAP
records.
 The charge (and tax) in the TAP record must first be validated against the technical
charging parameters (see below) in the TAP record, without taking the Call Type
Levels into consideration.
 If the technical charging parameters do not identify any rate in the IOT then the TAP
record can be rejected.
 If the technical charging parameters identify a unique rate in the IOT and the charge
is incorrect according to those parameters then the TAP record can be rejected.
 If the technical charging parameters identify a unique rate in the IOT and the charge
is correct according to those parameters then the TAP record must be accepted. In
this case the Call Type Levels will be ignored.
 If the technical charging parameters identify more than one rate in the IOT, further
analysis must be done on the identified IOT rates to compare the Call Type Levels in
the TAP record with the Call Type Levels for those rates in the IOT.
V36.4 Page 245 of 317

Note: In this case, it is acceptable to rely on Call Type Levels to further define the
rate (as described below) because it is not always possible or practical for the IOT to
contain exact number ranges for all rates.
 When Call Type Levels analysis is required it has to be tried in up to three steps, first
by just including Call Type Level 1, second a combination of Call Type Levels 1 and
2, and third a combination of Call type levels 1, 2 and 3. If a step results in identifying
a single rate in the Sender’s IOT then the next step won’t be applied any more.
 If the additional Call Type Level analysis does not identify a unique rate in the
Sender’s IOT then the TAP record can be rejected.
 If the additional Call Type Level analysis does identify a unique rate in the
Sender’s IOT and the Charge is correct then the TAP record must be accepted.
 If the additional Call Type Level analysis does identify a unique rate in the
Sender’s IOT and the Charge is incorrect then the TAP record can be rejected.
 The Call Type Levels in the TAP record and as defined in the Sender’s IOT cannot
be cross validated against technical charging parameters.
The below table defines what technical charging parameters are used in the charge
validation for each type of call record:
Type of Call Technical Charging Parameters

AUR Aggregated Usage Date Start, Serving Network,
Aggregation Type, Aggregated Chargeable Unit
Type and Units.
MOC Service, Location, Destination (CAMEL
Destination Number when present, otherwise
Called Number and/or Dialled Digits), IAC, Time
Band, Charged Item with associated Chargeable
Units
MSESS Service, Location, Destination (Non-Charged
Party and/or Requested Destination), IAC, Time
Band, Charged Item with associated Chargeable
Units
MTC Service, Location, Time Band, Charged Item with
associated Chargeable Units
MO SMS Location, Destination (the SMSC, CAMEL
Destination Number when present, otherwise
Called Number) and Time Band
MSG Location, Destination (the SMSC, Non-Charged
Party) and Time Band
MT SMS Location and Time Band
SSE Service, Location and Time Band
USSD Location and Time Band
PSData Location, APN, Time Band, Charged Item with
Wi-Fi Location, Hotspot, Time Band, Charged Item with
Table 38: Technical Charging Parameters
The following flowchart helps illustrate the above procedure.
V36.4 Page 246 of 317

Note: The flowchart needs to be read together with the text above.
Start
TAP Call-
Record
Received
Validate
against TCPs*
*Technical Charging
Parameters
Defined Rate(s)
No Reject the Call End
in IOT
Yes
Yes
Unique Rate Charge is Correct No
No
Yes
Unique Rate Yes

Using CTL1 Accept the Call
No
No
End
Unique Rate Yes
Using CTL1+CTL2
No
Unique Rate Yes

Using CTL1+CTL2
+CTL3
No
Figure 34: TAP Record Charge Validation Procedure
5.9 Provision of TAP Events on VoLTE handover scenarios

Note: The ongoing REVOLVER work will impact this section and the following reflects
options 2 and 3 in the REVOLVER white paper.
Enhanced SRVCC enable seamless handover of VoLTE Calls from LTE to the CS network
and vice versa. A single TAP Mobile Session CDR (MSESS CDR) must be generated for
the complete VoLTE Call usage also where the VoLTE call has been anchored in the IMS
network and handover has taken place between different network technologies.
A MOC CDR must not be provided on the TAP interface for the VoLTE Network CDR
generated by the MSC on the CS network where the VoLTE call has been anchored in the
V36.4 Page 247 of 317

IMS network. The detailed rules on the provision of TAP CDRs on the handover scenarios
are described below to avoid double charging on the HPMN side.
The table below describes the rules that need to be followed on the provision of TAP CDRs
in each voice call scenario as follows:
Call Scenario TAP CDR Comments

Voice over CS Network (2G/3G) MOC / MTC Event The Voice Call use CS Network
nodes only.
Voice over CSFB MOC / MTC Event The Voice Call use CS Network
nodes only.
Origination/Termination of Voice over MSESS Event1 The Voice Call use IMS
IMS Call Network nodes only.
Origination/Termination of VoIMS on MSESS Event1 The Voice Call is anchored in
LTE Network with handover to CS IMS Network
Network (2G/3G)
Origination/Termination of VoIMS on MSESS Event1 The Voice Call is anchored in
CS Network (2G/3G) with handover IMS Network
to the LTE Network
Table 39: TAP Event Types for VoLTE Call Scenarios
(1) Note: Apply for both Mobile Originated and Terminated VoIMS call scenarios
There are two VoLTE architectures which have been endorsed by the GSMA on the
standard routing of VoLTE calls to the end destination in the roaming environment. The two
routing scenarios are:
1. VoLTE Home Routing

2. VPMN Assisted Routing.
The following table describes the source network CDRs needed to obtain the necessary
Charging Information on the provision of the TAP CDRs per each routing scenario and with
/without eSRVCC which would have potentially taken place during an ongoing VoLTE call.
Call Scenario Network CDR Source TAP CDR Comments
VoLTE Home Routing P-CSCF Network CDR or MSESS No eSRVCC has
ATCF Network CDR Event taken place
VoLTE Home Routing & ATCF Network CDR1 MSESS
eSRVCC1 Event
VoLTE Home Routing & P-CSCF Network CDR MSESS The P-CSCF &
eSRVCC2 Event MSC Network
CDRs must be
MSC Network CDR
aggregated into
the TAP MSESS
Event.
VPMN Assisted Routing TRF Network CDR MSESS No eSRVCC has
Event taken place
V36.4 Page 248 of 317

VPMN Assisted Routing & TRF Network CDR MSESS

eSRVCC Event
Table 40: Network CDR Sources for VoLTE Call Scenarios
Notes: (1) In line with 3GPP R11 or above(2) Not in line with 3GPP R11 or above
5.10 Provision of TAP Events on SMS Messaging

The table below describes the rules to be followed on the provision of TAP CDRs in each
type of SMS Messaging scenario as follows:
SMS Messaging Scenario TAP CDR Comments

SMS MO/MT over CS Network MOC / MTC Event The SMS message is submitted over
(2G/3G) CS network nodes.
SMS MO/MT over SGs MOC / MTC Event The SMS message is submitted over
CS network nodes.
SMS MO/MT in SGSN MOC / MTC Event The SMS message is submitted over
PS network nodes
SMS MO/MT over IMS MSG Event The submission of the SMS message
uses E-UTRAN , EPC and IMS
network nodes.
SMS MO/MT in MME MSG Event The submission of the SMS message
uses E-UTRAN and MME network
nodes.
Table 41: TAP Event Types for SMS Messaging Scenarios
The following table describes the source network CDRs needed to obtain the necessary
Charging Information on the provision of the TAP CDRs per each SMS Messaging scenario
type:
Call Scenario Network CDR Source Comments

SMS MO/MT over CS SMS-MO Network CDR The SMS message is submitted
Network (2G/3G) SMS-MT Network CDR over CS network nodes.
SMS MO/MT over SGs SMS-MO Network CDR The SMS message is submitted
SMS-MT Network CDR over CS network nodes.
SMS MO/MT in SGSN S-SMO-CDR SGSN Network The SMS message is submitted
CDR over PS network nodes
S-SMT-CDR SGSN Network
CDR
SMS MO/MT in MME S-SMO-CDR MME Network The submission of the SMS
CDR message uses E-UTRAN and
S-SMT-CDR MME Network CDR MME network nodes.
Table 42: Network CDR Sources for SMS Messaging Scenarios
V36.4 Page 249 of 317

Note: A Network CDR has not been standardised for SMS submission over IMS Domain
where the SIP Message method has been used to route the SMS from the visited P-CSCF
to the Home S-CSCF.
5.11 Provision of TAP Events on VoLTE S8 Home Routed (S8HR) Scenarios

The table below describes the network CDRs and potential TAP CDRs for some common
VoLTE S8 Home Routed (S8HR) scenarios as follows:
Call Scenario Network CDR Source TAP CDR Comment

Signalling session One S-GW CDRs Event: One GPRS Call record: If signalling is
without any voice or  Bearer Charging Id  IMS Signalling (QCI charged
video calls value = ‘X’ value = 5 and Bearer Could also be
Bearer Charging Id SMS
value = ‘X’)
Voice call Two S-GW CDRs Events: Two GPRS Call records: No SRVCC has
 Bearer Charging Id  Voice media bearer taken place
value = ‘X’ (QCI value = 1 and
 Bearer Charging Id Bearer Charging Id
value = ‘Y’ value = ‘X’)
 IMS Voice Signalling
(QCI value = 5 and
Bearer Charging Id
value = ‘Y’)
3 Voice calls Four S-GW CDRs Events: Two GPRS Call records: No SRVCC has
 Bearer Charging Id  Voice media bearer taken place
value = ‘X1’ (QCI value = 1 and
value = ‘X2’ value = ‘X1’)
 Bearer Charging Id  Voice media bearer
value = ‘X3’ (QCI value = 1 and
Bearer Charging Id
 Bearer Charging Id
value = ‘X2’)
value = ‘Y’
 Voice media bearer
(QCI value = 1 and
Bearer Charging Id
value = ‘X3’)
(QCI value = 5 and
Bearer Charging Id
value = ‘Y’)
Voice and video Three S-GW CDRs Events: Three GPRS Call records: No SRVCC
call  Bearer Charging Id  Voice media bearer eSRVCC has
value = ‘X’ (QCI value = 1 and taken place
 Bearer Charging Id  Video media bearer
V36.4 Page 250 of 317

Call Scenario Network CDR Source TAP CDR Comment

value = ‘Z’ (QCI value = 2 and
Bearer Charging Id
value = ‘Y’)
(QCI value = 5 and
Bearer Charging Id
value = ‘Z’)
Voice with Two S-GW CDRs Events: Two GPRS Call records: SRVCC eSRVCC
handover LTE to  Bearer Charging Id  Voice media bearer has taken place
3G value = ‘X’ (QCI value = 1 and
One MSC-SRVCC Event (QCI value = 5 and
Bearer Charging Id
value = ‘Y’)
One MOC record
Table 43: Network / TAP CDR Types for VoLTE S8HR Scenarios
Note: BA.27 recommends charging for signalling, however if the VPMN doesn’t charge
for signalling the corresponding record may not be present in TAP. If a signalling record
is present in TAP, then it may not be part of the same TAP file as the voice/video parts.
One signalling record could support many calls, so there is not a 1-1 mapping between
any signalling record and the call that take place during that signalling session. TD.58
contains more detailed examples.
5.12 Provision of TAP Events on VoLTE LBO HR, like for S8HR (new option)
From a wholesale perspective, Origination and Termination of Voice over IMS calls could be
handled like S8HR, as GPRS Calls. The TAP CDR will be provided by the SGW.
Similarly, the TAP CDR for SMS MO/MT over IMS will be provided like a GPRS call, from
the SGW. No MSG CDR will be created.
The table 43 remains applicable.
6 Physical Structure
This document defines the physical format of Data Record Format Version 03.
In contrast to Data Record Format versions 01 and 02, Data Record Format version 03 uses
a flexible format encoding based on the ASN.1 standard which is widely used within the
telecommunication world.
V36.4 Page 251 of 317

Accordingly, the specification of the physical format consists of two parts:
 The definition of the abstract syntax.

 The definition of the transfer syntax (i.e. the encoding rules).
6.1 Abstract Syntax

This section defines the abstract syntax for Data Record Format version 03 using the ASN.1
standard as specified within ITU Rec. X.680 [37].
In order to support a wide range of ASN.1 conversion tools, this specification only uses
basic ASN.1 features which are common to both versions of the standard.
Namely, the following basic data types are used:
 INTEGER
 OCTET STRING
 VisibleString (only for TAP file creation)
 NumericString (only for TAP file creation)
Furthermore the following ASN.1 features for the construction of new data types are used:
 SEQUENCE / SEQUENCE OF
 CHOICE
Depending on the level of conformance to the ASN.1 standard and the actual functionality of
their conversion utility, operators can employ further ASN.1 features for the implementation
of the validation rules as laid out within the data dictionary. Most notably this applies to the
following ASN.1 features for the definition of new ASN.1 subtypes:
 Definition of value ranges for subtypes derived from the INTEGER type
 Definition of permitted alphabets for string (sub)types
It is possible to use these subtyping features on top of the following ASN.1 specification,
because they do not affect the actual physical encoding according to the Basic Encoding
Rules.
Although ASN.1 does not limit the size of INTEGERs the maximum size of a TAP encoded
INTEGER is 8 bytes for the following elements within the Data Dictionary:
Element Context
Total Charge Audit
Total Discount Value Audit
Total Tax Value Audit
Data Volume Incoming GPRS, Content
Data Volume Outgoing GPRS, Content
Chargeable Units GPRS, Content
Charged Units GPRS, Content
Charging Id GPRS
Total Discount Refund Audit
V36.4 Page 252 of 317

Total Charge Refund Audit

Total Advised Charge Audit
Total Advised Charge Refund Audit
Total Commission Audit
Total Commission Refund Audit
Total Data Volume Content
Total Tax Refund Audit
Aggregated Usage Charge AUR
Aggregated Chargeable Units AUR
AUR Tax Value AUR
AUR Taxable Amount AUR
Table 44: 8 Byte Integers
For any other data item the maximum size of an encoded INTEGER is 4 bytes. This gives
an implicit default value range constraint on any INTEGER defined within the specification
that has no explicit value range defined.
It is strongly recommended to use an enhanced ASN.1 syntax specification when creating

TAP files. The additions that can be done will significantly increase the integrity of created
TAP files by specifying ASN.1 constraints that can be automatically followed by the compiler
and coding tool at TAP file creation. The recommended modifications for file creation are
indicated within the ASN.1 specification as follows:
 “OPTIONAL, -- *m.m.” which should be replaced by “,”.

 Common data types should be redefined as indicated in the comments of the ‘non
tagged common data types’ section.
 Size constraints should be uncommented, i.e. remove the ‘-- ‘ before the keyword
‘SIZE’.
ASN.1 definition and tag numbers for fields Specification Version Number and Release
Version Number must remain the same in all TAP releases to enable cross release pre-
decoding identification of the specification and release version used in any TAP file.
The following ranges for tags are currently used:
Tag range Description

0 Reserved for TAP use
1 to 6 In use for TAP
7 Reserved for TAP use – application # released TAP 3.11
8 In use for TAP and RAP
18 to 31 Reserved for TAP use
33 to 35 Reserved for TAP use – application # released TAP 3.11
V36.4 Page 253 of 317


101 In use for TAP
133 In use for TAP
138 In use for TAP
143 In use for TAP and RAP
156 In use for TAP
159 In use for TAP
V36.4 Page 254 of 317


204 In use for TAP
206 In use for TAP
223 In use for TAP
400 In use for TAP
407 In use for TAP
465 to 511 Reserved for TAP use
512 to 1023 Reserved for RAP usage
Table 45: Tag Ranges
V36.4 Page 255 of 317

--
--
-- The following ASN.1 specification defines the abstract syntax for
--
-- Data Record Format Version 03
-- Release 12
--
-- The specification is structured as follows:
-- (1) structure of the Tap batch
-- (2) definition of the individual Tap ‘records’
-- (3) Tap data items and groups of data items used within (2)
-- (4) Common, non-Tap data types
-- (5) Tap data items for content charging
--
-- It is mainly a translation from the logical structure
-- diagrams. Where appropriate, names used within the
-- logical structure diagrams have been shortened.
-- For repeating data items the name as used within the logical
-- structure have been extended by adding ‘list’ or ‘table’
-- (in some instances).
--
TAP-0312 DEFINITIONS IMPLICIT TAGS ::=
BEGIN
--
-- Structure of a Tap batch
--
DataInterChange ::= CHOICE

{
transferBatch TransferBatch,
notification Notification,
...
}
-- Batch Control Information must always, both logically and physically,

-- be the first group/item within Transfer Batch – this ensures that the
-- TAP release version can be readily identified. Any new groups/items
-- required may be inserted at any point after Batch Control Information
TransferBatch ::= [APPLICATION 1] SEQUENCE

{
batchControlInfo BatchControlInfo OPTIONAL, -- *m.m.
accountingInfo AccountingInfo OPTIONAL,
networkInfo NetworkInfo OPTIONAL, -- *m.m.
messageDescriptionInfo MessageDescriptionInfoList OPTIONAL,
callEventDetails CallEventDetailList OPTIONAL, -- *m.m.
auditControlInfo AuditControlInfo OPTIONAL, -- *m.m.
V36.4 Page 256 of 317

...
}
Notification ::= [APPLICATION 2] SEQUENCE

{
sender Sender OPTIONAL, -- *m.m.
recipient Recipient OPTIONAL, -- *m.m.
fileSequenceNumber FileSequenceNumber OPTIONAL, -- *m.m.
rapFileSequenceNumber RapFileSequenceNumber OPTIONAL,
fileCreationTimeStamp FileCreationTimeStamp OPTIONAL,
fileAvailableTimeStamp FileAvailableTimeStamp OPTIONAL, -- *m.m.
transferCutOffTimeStamp TransferCutOffTimeStamp OPTIONAL, -- *m.m.
specificationVersionNumber SpecificationVersionNumber OPTIONAL, -- *m.m.
releaseVersionNumber ReleaseVersionNumber OPTIONAL, -- *m.m.
fileTypeIndicator FileTypeIndicator OPTIONAL,
operatorSpecInformation OperatorSpecInfoList OPTIONAL,
...
}
CallEventDetailList ::= [APPLICATION 3] SEQUENCE OF CallEventDetail
CallEventDetail ::= CHOICE

{
mobileOriginatedCall MobileOriginatedCall,
mobileTerminatedCall MobileTerminatedCall,
supplServiceEvent SupplServiceEvent,
serviceCentreUsage ServiceCentreUsage,
gprsCall GprsCall,
contentTransaction ContentTransaction,
locationService LocationService,
messagingEvent MessagingEvent,
mobileSession MobileSession,
aggregatedUsageRecord AggregatedUsageRecord,
...
}
--
-- Structure of the individual Tap records
--
BatchControlInfo ::= [APPLICATION 4] SEQUENCE

{
sender Sender OPTIONAL, -- *m.m.
recipient Recipient OPTIONAL, -- *m.m.
fileSequenceNumber FileSequenceNumber OPTIONAL, -- *m.m.
fileCreationTimeStamp FileCreationTimeStamp OPTIONAL,
transferCutOffTimeStamp TransferCutOffTimeStamp OPTIONAL, -- *m.m.
fileAvailableTimeStamp FileAvailableTimeStamp OPTIONAL, -- *m.m.
specificationVersionNumber SpecificationVersionNumber OPTIONAL, -- *m.m.
releaseVersionNumber ReleaseVersionNumber OPTIONAL, -- *m.m.
fileTypeIndicator FileTypeIndicator OPTIONAL,
V36.4 Page 257 of 317


...
}
AccountingInfo ::= [APPLICATION 5] SEQUENCE

{
taxation TaxationList OPTIONAL,
discounting DiscountingList OPTIONAL,
localCurrency LocalCurrency OPTIONAL, -- *m.m.
tapCurrency TapCurrency OPTIONAL,
currencyConversionInfo CurrencyConversionList OPTIONAL,
tapDecimalPlaces TapDecimalPlaces OPTIONAL, -- *m.m.
...
}
NetworkInfo ::= [APPLICATION 6] SEQUENCE

{
utcTimeOffsetInfo UtcTimeOffsetInfoList OPTIONAL, -- *m.m.
recEntityInfo RecEntityInfoList OPTIONAL,
...
}
MessageDescriptionInfoList ::= [APPLICATION 8] SEQUENCE OF

MessageDescriptionInformation
AggregatedUsageRecord ::= [APPLICATION 453] SEQUENCE

{
aggregatedUsageDateStart AggregatedUsageDateStart OPTIONAL, -- *m.m.
aggregatedUsageDateEnd AggregatedUsageDateEnd OPTIONAL,
servingNetwork ServingNetwork OPTIONAL,
aggregationType AggregationType OPTIONAL,
aggregationIdentifier AggregationIdentifier OPTIONAL,
callTypeLevel1 CallTypeLevel1 OPTIONAL,
aggregatedChrgUnitType AggregatedChrgUnitType OPTIONAL, -- *m.m.
aggregatedChrgUnits AggregatedChrgUnits OPTIONAL, -- *m.m.
aggregatedUsageCharge AggregatedUsageCharge OPTIONAL,
exchangeRateCode ExchangeRateCode OPTIONAL,
aURTaxInformationList AURTaxInformationList OPTIONAL,
operatorSpecInformation OperatorSpecInformationList OPTIONAL,
...
}
MobileOriginatedCall ::= [APPLICATION 9] SEQUENCE

{
basicCallInformation MoBasicCallInformation OPTIONAL, -- *m.m.
locationInformation LocationInformation OPTIONAL, -- *m.m.
equipmentIdentifier ImeiOrEsn OPTIONAL,
V36.4 Page 258 of 317

basicServiceUsedList BasicServiceUsedList OPTIONAL, -- *m.m.

supplServiceCode SupplServiceCode OPTIONAL,
thirdPartyInformation ThirdPartyInformation OPTIONAL,
camelServiceUsed CamelServiceUsed OPTIONAL,
...
}
MobileTerminatedCall ::= [APPLICATION 10] SEQUENCE

{
basicCallInformation MtBasicCallInformation OPTIONAL, -- *m.m.
basicServiceUsedList BasicServiceUsedList OPTIONAL, -- *m.m.
...
}
SupplServiceEvent ::= [APPLICATION 11] SEQUENCE

{
chargeableSubscriber ChargeableSubscriber OPTIONAL, -- *m.m.
supplServiceUsed SupplServiceUsed OPTIONAL, -- *m.m.
...
}
ServiceCentreUsage ::= [APPLICATION 12] SEQUENCE

{
basicInformation ScuBasicInformation OPTIONAL, -- *m.m.
recEntityCode RecEntityCode OPTIONAL, -- *m.m.
chargeInformation ChargeInformation OPTIONAL, -- *m.m.
scuChargeType ScuChargeType OPTIONAL, -- *m.m.
scuTimeStamps ScuTimeStamps OPTIONAL, -- *m.m.
...
}
GprsCall ::= [APPLICATION 14] SEQUENCE

{
gprsBasicCallInformation GprsBasicCallInformation OPTIONAL, -- *m.m.
gprsLocationInformation GprsLocationInformation OPTIONAL, -- *m.m.
gprsServiceUsed GprsServiceUsed OPTIONAL, -- *m.m.
V36.4 Page 259 of 317


...
}
ContentTransaction ::= [APPLICATION 17] SEQUENCE

{
contentTransactionBasicInfo ContentTransactionBasicInfo OPTIONAL, -- *m.m.
chargedPartyInformation ChargedPartyInformation OPTIONAL, -- *m.m.
servingPartiesInformation ServingPartiesInformation OPTIONAL, -- *m.m.
contentServiceUsed ContentServiceUsedList OPTIONAL, -- *m.m.
...
}
LocationService ::= [APPLICATION 297] SEQUENCE

{
callReference CallReference OPTIONAL,
trackingCustomerInformation TrackingCustomerInformation OPTIONAL,
lCSSPInformation LCSSPInformation OPTIONAL,
trackedCustomerInformation TrackedCustomerInformation OPTIONAL,
locationServiceUsage LocationServiceUsage OPTIONAL, -- *m.m.
...
}
MessagingEvent ::= [APPLICATION 433] SEQUENCE

{
messagingEventService MessagingEventService OPTIONAL, -- *m.m.
chargedParty ChargedParty OPTIONAL, -- *m.m.
simToolkitIndicator SimToolkitIndicator OPTIONAL,
geographicalLocation GeographicalLocation OPTIONAL,
eventReference EventReference OPTIONAL, -- *m.m.
recEntityCodeList RecEntityCodeList OPTIONAL, -- *m.m.
networkElementList NetworkElementList OPTIONAL,
locationArea LocationArea OPTIONAL,
cellId CellId OPTIONAL,
serviceStartTimestamp ServiceStartTimestamp OPTIONAL, -- *m.m.
nonChargedParty NonChargedParty OPTIONAL,
callTypeGroup CallTypeGroup OPTIONAL, -- *m.m.
charge Charge OPTIONAL, -- *m.m.
taxInformationList TaxInformationList OPTIONAL,
...
}
MobileSession ::= [APPLICATION 434] SEQUENCE
V36.4 Page 260 of 317

{
mobileSessionService MobileSessionService OPTIONAL, -- *m.m.
chargedParty ChargedParty OPTIONAL, -- *m.m.
eventReference EventReference OPTIONAL, -- *m.m.
recEntityCodeList RecEntityCodeList OPTIONAL, -- *m.m.
serviceStartTimestamp ServiceStartTimestamp OPTIONAL, -- *m.m.
causeForTerm CauseForTerm OPTIONAL,
totalCallEventDuration TotalCallEventDuration OPTIONAL, -- *m.m.
nonChargedParty NonChargedParty OPTIONAL,
requestedDestination RequestedDestination OPTIONAL,
sessionChargeInfoList SessionChargeInfoList OPTIONAL, -- *m.m.
...
}
AuditControlInfo ::= [APPLICATION 15] SEQUENCE

{
earliestCallTimeStamp EarliestCallTimeStamp OPTIONAL,
latestCallTimeStamp LatestCallTimeStamp OPTIONAL,
totalCharge TotalCharge OPTIONAL, -- *m.m.
totalChargeRefund TotalChargeRefund OPTIONAL,
totalTaxRefund TotalTaxRefund OPTIONAL,
totalTaxValue TotalTaxValue OPTIONAL, -- *m.m.
totalDiscountValue TotalDiscountValue OPTIONAL, -- *m.m.
totalDiscountRefund TotalDiscountRefund OPTIONAL,
totalAdvisedChargeValueList TotalAdvisedChargeValueList OPTIONAL,
callEventDetailsCount CallEventDetailsCount OPTIONAL, -- *m.m.
...
}
--
-- Tap data items and groups of data items
--
AccessPointNameNI ::= [APPLICATION 261] AsciiString --(SIZE(1..63))
AccessPointNameOI ::= [APPLICATION 262] AsciiString --(SIZE(1..37))
ActualDeliveryTimeStamp ::= [APPLICATION 302] DateTime
AddressStringDigits ::= BCDString
AdvisedCharge ::= [APPLICATION 349] Charge
V36.4 Page 261 of 317

AdvisedChargeCurrency ::= [APPLICATION 348] Currency
AdvisedChargeInformation ::= [APPLICATION 351] SEQUENCE

{
paidIndicator PaidIndicator OPTIONAL,
paymentMethod PaymentMethod OPTIONAL,
advisedChargeCurrency AdvisedChargeCurrency OPTIONAL,
advisedCharge AdvisedCharge OPTIONAL, -- *m.m.
commission Commission OPTIONAL,
...
}
AgeOfLocation ::= [APPLICATION 396] INTEGER
AURTaxInformation ::= [APPLICATION 454] SEQUENCE

{
taxCode TaxCode OPTIONAL, -- *m.m
aURTaxValue AURTaxValue OPTIONAL, -- *m.m
aURTaxableAmount AURTaxableAmount OPTIONAL,
...
}
AggregatedUsageDateStart ::= [APPLICATION 455] LocalDate
AggregatedUsageDateEnd ::= [APPLICATION 456] LocalDate
AggregationType ::= [APPLICATION 457] INTEGER
AggregationIdentifier ::= [APPLICATION 458] AsciiString
AggregatedChrgUnitType ::= [APPLICATION 459] INTEGER
AggregatedChrgUnits ::= [APPLICATION 460] INTEGER
AggregatedUsageCharge ::= [APPLICATION 461] AbsoluteAmount
AURTaxInformationList ::= [APPLICATION 464] SEQUENCE OF AURTaxInformation
AURTaxValue ::= [APPLICATION 462] AbsoluteAmount
AURTaxableAmount ::= [APPLICATION 463] AbsoluteAmount
BasicService ::= [APPLICATION 36] SEQUENCE

{
serviceCode BasicServiceCode OPTIONAL, -- *m.m.
transparencyIndicator TransparencyIndicator OPTIONAL,
fnur Fnur OPTIONAL,
userProtocolIndicator UserProtocolIndicator OPTIONAL,
guaranteedBitRate GuaranteedBitRate OPTIONAL,
maximumBitRate MaximumBitRate OPTIONAL,
...
V36.4 Page 262 of 317

BasicServiceCode ::= [APPLICATION 426] CHOICE

{
teleServiceCode TeleServiceCode,
bearerServiceCode BearerServiceCode,
...
}
BasicServiceCodeList ::= [APPLICATION 37] SEQUENCE OF BasicServiceCode
BasicServiceUsed ::= [APPLICATION 39] SEQUENCE

{
basicService BasicService OPTIONAL, -- *m.m.
chargingTimeStamp ChargingTimeStamp OPTIONAL,
chargeInformationList ChargeInformationList OPTIONAL, -- *m.m.
hSCSDIndicator HSCSDIndicator OPTIONAL,
...
}
BasicServiceUsedList ::= [APPLICATION 38] SEQUENCE OF BasicServiceUsed
BearerServiceCode ::= [APPLICATION 40] HexString --(SIZE(2))
CalledNumber ::= [APPLICATION 407] AddressStringDigits
CalledPlace ::= [APPLICATION 42] AsciiString
CalledRegion ::= [APPLICATION 46] AsciiString
CallEventDetailsCount ::= [APPLICATION 43] INTEGER
CallEventStartTimeStamp ::= [APPLICATION 44] DateTime
CallingNumber ::= [APPLICATION 405] AddressStringDigits
CallOriginator ::= [APPLICATION 41] SEQUENCE

{
callingNumber CallingNumber OPTIONAL,
clirIndicator ClirIndicator OPTIONAL,
sMSOriginator SMSOriginator OPTIONAL,
...
}
CallReference ::= [APPLICATION 45] OCTET STRING --(SIZE(1..8))
CallTypeGroup ::= [APPLICATION 258] SEQUENCE

{
callTypeLevel1 CallTypeLevel1 OPTIONAL, -- *m.m.
V36.4 Page 263 of 317

...
}
CallTypeLevel1 ::= [APPLICATION 259] INTEGER
CamelDestinationNumber ::= [APPLICATION 404] AddressStringDigits
CamelInvocationFee ::= [APPLICATION 422] AbsoluteAmount
CamelServiceKey ::= [APPLICATION 55] INTEGER
CamelServiceLevel ::= [APPLICATION 56] INTEGER
CamelServiceUsed ::= [APPLICATION 57] SEQUENCE

{
camelServiceLevel CamelServiceLevel OPTIONAL,
camelServiceKey CamelServiceKey OPTIONAL, -- *m.m.
defaultCallHandling DefaultCallHandlingIndicator OPTIONAL,
taxInformation TaxInformationList OPTIONAL,
discountInformation DiscountInformation OPTIONAL,
camelInvocationFee CamelInvocationFee OPTIONAL,
threeGcamelDestination ThreeGcamelDestination OPTIONAL,
cseInformation CseInformation OPTIONAL,
...
}
CauseForTerm ::= [APPLICATION 58] INTEGER
CellId ::= [APPLICATION 59] INTEGER
Charge ::= [APPLICATION 62] AbsoluteAmount
ChargeableSubscriber ::= [APPLICATION 427] CHOICE

{
simChargeableSubscriber SimChargeableSubscriber,
minChargeableSubscriber MinChargeableSubscriber,
...
}
ChargeableUnits ::= [APPLICATION 65] INTEGER
ChargeDetail ::= [APPLICATION 63] SEQUENCE

{
chargeType ChargeType OPTIONAL, -- *m.m.
charge Charge OPTIONAL, -- *m.m.
chargeableUnits ChargeableUnits OPTIONAL,
V36.4 Page 264 of 317

chargedUnits ChargedUnits OPTIONAL,

chargeDetailTimeStamp ChargeDetailTimeStamp OPTIONAL,
...
}
ChargeDetailList ::= [APPLICATION 64] SEQUENCE OF ChargeDetail
ChargeDetailTimeStamp ::= [APPLICATION 410] ChargingTimeStamp
ChargedItem ::= [APPLICATION 66] AsciiString --(SIZE(1))
ChargedParty ::= [APPLICATION 436] SEQUENCE

{
imsi Imsi OPTIONAL, -- *m.m.
msisdn Msisdn OPTIONAL,
publicUserId PublicUserId OPTIONAL,
homeBid HomeBid OPTIONAL,
homeLocationDescription HomeLocationDescription OPTIONAL,
imei Imei OPTIONAL,
...
}
ChargedPartyEquipment ::= [APPLICATION 323] SEQUENCE

{
equipmentIdType EquipmentIdType OPTIONAL, -- *m.m.
equipmentId EquipmentId OPTIONAL, -- *m.m.
...
}
ChargedPartyHomeIdentification ::= [APPLICATION 313] SEQUENCE

{
homeIdType HomeIdType OPTIONAL, -- *m.m.
homeIdentifier HomeIdentifier OPTIONAL, -- *m.m.
...
}
ChargedPartyHomeIdList ::= [APPLICATION 314] SEQUENCE OF

ChargedPartyHomeIdentification
ChargedPartyIdentification ::= [APPLICATION 309] SEQUENCE

{
chargedPartyIdType ChargedPartyIdType OPTIONAL, -- *m.m.
chargedPartyIdentifier ChargedPartyIdentifier OPTIONAL, -- *m.m.
...
}
ChargedPartyIdentifier ::= [APPLICATION 287] AsciiString
ChargedPartyIdList ::= [APPLICATION 310] SEQUENCE OF ChargedPartyIdentification
ChargedPartyIdType ::= [APPLICATION 305] INTEGER
V36.4 Page 265 of 317

ChargedPartyInformation ::= [APPLICATION 324] SEQUENCE

{
chargedPartyIdList ChargedPartyIdList OPTIONAL, -- *m.m.
chargedPartyHomeIdList ChargedPartyHomeIdList OPTIONAL,
chargedPartyLocationList ChargedPartyLocationList OPTIONAL,
chargedPartyEquipment ChargedPartyEquipment OPTIONAL,
...
}
ChargedPartyLocation ::= [APPLICATION 320] SEQUENCE

{
locationIdType LocationIdType OPTIONAL, -- *m.m.
locationIdentifier LocationIdentifier OPTIONAL, -- *m.m.
...
}
ChargedPartyLocationList ::= [APPLICATION 321] SEQUENCE OF ChargedPartyLocation
ChargedPartyStatus ::= [APPLICATION 67] INTEGER
ChargedUnits ::= [APPLICATION 68] INTEGER
ChargeInformation ::= [APPLICATION 69] SEQUENCE

{
chargedItem ChargedItem OPTIONAL, -- *m.m.
callTypeGroup CallTypeGroup OPTIONAL,
chargeDetailList ChargeDetailList OPTIONAL, -- *m.m.
taxInformation TaxInformationList OPTIONAL,
discountInformation DiscountInformation OPTIONAL,
...
}
ChargeInformationList ::= [APPLICATION 70] SEQUENCE OF ChargeInformation
ChargeRefundIndicator ::= [APPLICATION 344] INTEGER
ChargeType ::= [APPLICATION 71] NumberString --(SIZE(2..3))
ChargingId ::= [APPLICATION 72] INTEGER
ChargingPoint ::= [APPLICATION 73] AsciiString --(SIZE(1))
ChargingTimeStamp ::= [APPLICATION 74] DateTime
ClirIndicator ::= [APPLICATION 75] INTEGER
Commission ::= [APPLICATION 350] Charge
CompletionTimeStamp ::= [APPLICATION 76] DateTime
V36.4 Page 266 of 317

ContentChargingPoint ::= [APPLICATION 345] INTEGER
ContentProvider ::= [APPLICATION 327] SEQUENCE

{
contentProviderIdType ContentProviderIdType OPTIONAL, -- *m.m.
contentProviderIdentifier ContentProviderIdentifier OPTIONAL, -- *m.m.
...
}
ContentProviderIdentifier ::= [APPLICATION 292] AsciiString
ContentProviderIdList ::= [APPLICATION 328] SEQUENCE OF ContentProvider
ContentProviderIdType ::= [APPLICATION 291] INTEGER
ContentProviderName ::= [APPLICATION 334] AsciiString
ContentServiceUsed ::= [APPLICATION 352] SEQUENCE

{
contentTransactionCode ContentTransactionCode OPTIONAL, -- *m.m.
contentTransactionType ContentTransactionType OPTIONAL, -- *m.m.
objectType ObjectType OPTIONAL,
transactionDescriptionSupp TransactionDescriptionSupp OPTIONAL,
transactionShortDescription TransactionShortDescription OPTIONAL, -- *m.m.
transactionDetailDescription TransactionDetailDescription OPTIONAL,
transactionIdentifier TransactionIdentifier OPTIONAL, -- *m.m.
transactionAuthCode TransactionAuthCode OPTIONAL,
dataVolumeIncoming DataVolumeIncoming OPTIONAL,
dataVolumeOutgoing DataVolumeOutgoing OPTIONAL,
totalDataVolume TotalDataVolume OPTIONAL,
chargeRefundIndicator ChargeRefundIndicator OPTIONAL,
contentChargingPoint ContentChargingPoint OPTIONAL,
chargeInformationList ChargeInformationList OPTIONAL,
advisedChargeInformation AdvisedChargeInformation OPTIONAL,
...
}
ContentServiceUsedList ::= [APPLICATION 285] SEQUENCE OF ContentServiceUsed
ContentTransactionBasicInfo ::= [APPLICATION 304] SEQUENCE

{
orderPlacedTimeStamp OrderPlacedTimeStamp OPTIONAL,
requestedDeliveryTimeStamp RequestedDeliveryTimeStamp OPTIONAL,
actualDeliveryTimeStamp ActualDeliveryTimeStamp OPTIONAL,
totalTransactionDuration TotalTransactionDuration OPTIONAL,
transactionStatus TransactionStatus OPTIONAL,
...
}
V36.4 Page 267 of 317

ContentTransactionCode ::= [APPLICATION 336] INTEGER
ContentTransactionType ::= [APPLICATION 337] INTEGER
CseInformation ::= [APPLICATION 79] OCTET STRING --(SIZE(1..40))
CurrencyConversion ::= [APPLICATION 106] SEQUENCE

{
exchangeRateCode ExchangeRateCode OPTIONAL, -- *m.m.
numberOfDecimalPlaces NumberOfDecimalPlaces OPTIONAL, -- *m.m.
exchangeRate ExchangeRate OPTIONAL, -- *m.m.
...
}
CurrencyConversionList ::= [APPLICATION 80] SEQUENCE OF CurrencyConversion
CustomerIdentifier ::= [APPLICATION 364] AsciiString
CustomerIdType ::= [APPLICATION 363] INTEGER
DataVolume ::= INTEGER
DataVolumeIncoming ::= [APPLICATION 250] DataVolume
DataVolumeOutgoing ::= [APPLICATION 251] DataVolume
--
-- The following datatypes are used to denote timestamps.
-- Each timestamp consists of a local timestamp and a
-- corresponding UTC time offset.
-- Except for the timestamps used within the Batch Control
-- Information and the Audit Control Information
-- the UTC time offset is identified by a code referencing
-- the UtcTimeOffsetInfo.
--
--
-- We start with the “short” datatype referencing the
-- UtcTimeOffsetInfo.
--
DateTime ::= SEQUENCE

{
--
-- Local timestamps are noted in the format
--
-- CCYYMMDDhhmmss
--
-- where CC = century (‘19’, ‘20’,...)
-- YY = year (‘00’ – ‘99’)
-- MM = month (‘01’, ‘02’, ... , ‘12’)
V36.4 Page 268 of 317

-- DD = day (‘01’, ‘02’, ... , ‘31’)

-- hh = hour (‘00’, ‘01’, ... , ‘23’)
-- mm = minutes (‘00’, ‘01’, ... , ‘59’)
-- ss = seconds (‘00’, ‘01’, ... , ‘59’)
--
localTimeStamp LocalTimeStamp OPTIONAL, -- *m.m.
utcTimeOffsetCode UtcTimeOffsetCode OPTIONAL, -- *m.m.
...
}
--
-- The following version is the “long” datatype
-- containing the UTC time offset directly.
--
DateTimeLong ::= SEQUENCE

{
localTimeStamp LocalTimeStamp OPTIONAL, -- *m.m.
utcTimeOffset UtcTimeOffset OPTIONAL, -- *m.m.
...
}
DefaultCallHandlingIndicator ::= [APPLICATION 87] INTEGER
DepositTimeStamp ::= [APPLICATION 88] DateTime
Destination ::= [APPLICATION 89] SEQUENCE

{
calledNumber CalledNumber OPTIONAL,
dialledDigits DialledDigits OPTIONAL,
calledPlace CalledPlace OPTIONAL,
calledRegion CalledRegion OPTIONAL,
sMSDestinationNumber SMSDestinationNumber OPTIONAL,
...
}
DestinationNetwork ::= [APPLICATION 90] NetworkId
DialledDigits ::= [APPLICATION 279] AsciiString
Discount ::= [APPLICATION 412] DiscountValue
DiscountableAmount ::= [APPLICATION 423] AbsoluteAmount
DiscountApplied ::= [APPLICATION 428] CHOICE

{
fixedDiscountValue FixedDiscountValue,
discountRate DiscountRate,
...
}
V36.4 Page 269 of 317

DiscountCode ::= [APPLICATION 91] INTEGER
DiscountInformation ::= [APPLICATION 96] SEQUENCE

{
discountCode DiscountCode OPTIONAL, -- *m.m.
discount Discount OPTIONAL,
discountableAmount DiscountableAmount OPTIONAL,
...
}
Discounting ::= [APPLICATION 94] SEQUENCE

{
discountCode DiscountCode OPTIONAL, -- *m.m.
discountApplied DiscountApplied OPTIONAL, -- *m.m.
...
}
DiscountingList ::= [APPLICATION 95] SEQUENCE OF Discounting
DiscountRate ::= [APPLICATION 92] PercentageRate
DiscountValue ::= AbsoluteAmount
DistanceChargeBandCode ::= [APPLICATION 98] AsciiString --(SIZE(1))
EarliestCallTimeStamp ::= [APPLICATION 101] DateTimeLong
ElementId ::= [APPLICATION 437] AsciiString
ElementType ::= [APPLICATION 438] INTEGER
EquipmentId ::= [APPLICATION 290] AsciiString
EquipmentIdType ::= [APPLICATION 322] INTEGER
Esn ::= [APPLICATION 103] NumberString
EventReference ::= [APPLICATION 435] AsciiString
ExchangeRate ::= [APPLICATION 104] INTEGER
ExchangeRateCode ::= [APPLICATION 105] Code
FileAvailableTimeStamp ::= [APPLICATION 107] DateTimeLong
FileCreationTimeStamp ::= [APPLICATION 108] DateTimeLong
FileSequenceNumber ::= [APPLICATION 109] NumberString --(SIZE(5))
FileTypeIndicator ::= [APPLICATION 110] AsciiString --(SIZE(1))
V36.4 Page 270 of 317

FixedDiscountValue ::= [APPLICATION 411] DiscountValue
Fnur ::= [APPLICATION 111] INTEGER
GeographicalLocation ::= [APPLICATION 113] SEQUENCE

{
servingBid ServingBid OPTIONAL,
servingLocationDescription ServingLocationDescription OPTIONAL,
...
}
GprsBasicCallInformation ::= [APPLICATION 114] SEQUENCE

{
gprsChargeableSubscriber GprsChargeableSubscriber OPTIONAL, -- *m.m.
gprsDestination GprsDestination OPTIONAL, -- *m.m.
callEventStartTimeStamp CallEventStartTimeStamp OPTIONAL, -- *m.m.
partialTypeIndicator PartialTypeIndicator OPTIONAL,
pDPContextStartTimestamp PDPContextStartTimestamp OPTIONAL,
networkInitPDPContext NetworkInitPDPContext OPTIONAL,
chargingId ChargingId OPTIONAL, -- *m.m.
...
}
GprsChargeableSubscriber ::= [APPLICATION 115] SEQUENCE

{
chargeableSubscriber ChargeableSubscriber OPTIONAL,
pdpAddress PdpAddress OPTIONAL,
networkAccessIdentifier NetworkAccessIdentifier OPTIONAL,
...
}
GprsDestination ::= [APPLICATION 116] SEQUENCE

{
accessPointNameNI AccessPointNameNI OPTIONAL, -- *m.m.
accessPointNameOI AccessPointNameOI OPTIONAL,
...
}
GprsLocationInformation ::= [APPLICATION 117] SEQUENCE

{
gprsNetworkLocation GprsNetworkLocation OPTIONAL, -- *m.m.
homeLocationInformation HomeLocationInformation OPTIONAL,
...
}
GprsNetworkLocation ::= [APPLICATION 118] SEQUENCE
V36.4 Page 271 of 317

{
recEntity RecEntityCodeList OPTIONAL, -- *m.m.
...
}
GprsServiceUsed ::= [APPLICATION 121] SEQUENCE

{
iMSSignallingContext IMSSignallingContext OPTIONAL,
dataVolumeIncoming DataVolumeIncoming OPTIONAL, -- *m.m.
dataVolumeOutgoing DataVolumeOutgoing OPTIONAL, -- *m.m.
...
}
GsmChargeableSubscriber ::= [APPLICATION 286] SEQUENCE

{
imsi Imsi OPTIONAL,
...
}
GuaranteedBitRate ::= [APPLICATION 420] OCTET STRING --(SIZE (1))
HomeBid ::= [APPLICATION 122] Bid
HomeIdentifier ::= [APPLICATION 288] AsciiString
HomeIdType ::= [APPLICATION 311] INTEGER
HomeLocationDescription ::= [APPLICATION 413] LocationDescription
HomeLocationInformation ::= [APPLICATION 123] SEQUENCE

{
homeBid HomeBid OPTIONAL, -- *m.m.
homeLocationDescription HomeLocationDescription OPTIONAL, -- *m.m.
...
}
HorizontalAccuracyDelivered ::= [APPLICATION 392] INTEGER
HorizontalAccuracyRequested ::= [APPLICATION 385] INTEGER
HSCSDIndicator ::= [APPLICATION 424] AsciiString --(SIZE(1))
Imei ::= [APPLICATION 128] BCDString --(SIZE(7..8))
ImeiOrEsn ::= [APPLICATION 429] CHOICE

{
imei Imei,
V36.4 Page 272 of 317

esn Esn,
...
}
Imsi ::= [APPLICATION 129] BCDString --(SIZE(3..8))
IMSSignallingContext ::= [APPLICATION 418] INTEGER
InternetServiceProvider ::= [APPLICATION 329] SEQUENCE

{
ispIdType IspIdType OPTIONAL, -- *m.m.
ispIdentifier IspIdentifier OPTIONAL, -- *m.m.
...
}
InternetServiceProviderIdList ::= [APPLICATION 330] SEQUENCE OF

InternetServiceProvider
IspIdentifier ::= [APPLICATION 294] AsciiString
IspIdType ::= [APPLICATION 293] INTEGER
ISPList ::= [APPLICATION 378] SEQUENCE OF InternetServiceProvider
NetworkIdType ::= [APPLICATION 331] INTEGER
NetworkIdentifier ::= [APPLICATION 295] AsciiString
Network ::= [APPLICATION 332] SEQUENCE

{
networkIdType NetworkIdType OPTIONAL, -- *m.m.
networkIdentifier NetworkIdentifier OPTIONAL, -- *m.m.
...
}
NetworkList ::= [APPLICATION 333] SEQUENCE OF Network
LatestCallTimeStamp ::= [APPLICATION 133] DateTimeLong
LCSQosDelivered ::= [APPLICATION 390] SEQUENCE

{
lCSTransactionStatus LCSTransactionStatus OPTIONAL,
horizontalAccuracyDelivered HorizontalAccuracyDelivered OPTIONAL,
verticalAccuracyDelivered VerticalAccuracyDelivered OPTIONAL,
responseTime ResponseTime OPTIONAL,
positioningMethod PositioningMethod OPTIONAL,
trackingPeriod TrackingPeriod OPTIONAL,
trackingFrequency TrackingFrequency OPTIONAL,
ageOfLocation AgeOfLocation OPTIONAL,
...
}
V36.4 Page 273 of 317

LCSQosRequested ::= [APPLICATION 383] SEQUENCE

{
lCSRequestTimestamp LCSRequestTimestamp OPTIONAL, -- *m.m.
horizontalAccuracyRequested HorizontalAccuracyRequested OPTIONAL,
verticalAccuracyRequested VerticalAccuracyRequested OPTIONAL,
responseTimeCategory ResponseTimeCategory OPTIONAL,
trackingPeriod TrackingPeriod OPTIONAL,
trackingFrequency TrackingFrequency OPTIONAL,
...
}
LCSRequestTimestamp ::= [APPLICATION 384] DateTime
LCSSPIdentification ::= [APPLICATION 375] SEQUENCE

{
contentProviderIdType ContentProviderIdType OPTIONAL, -- *m.m.
contentProviderIdentifier ContentProviderIdentifier OPTIONAL, -- *m.m.
...
}
LCSSPIdentificationList ::= [APPLICATION 374] SEQUENCE OF LCSSPIdentification
LCSSPInformation ::= [APPLICATION 373] SEQUENCE

{
lCSSPIdentificationList LCSSPIdentificationList OPTIONAL, -- *m.m.
iSPList ISPList OPTIONAL,
networkList NetworkList OPTIONAL,
...
}
LCSTransactionStatus ::= [APPLICATION 391] INTEGER
LocalCurrency ::= [APPLICATION 135] Currency
LocalDate ::= NumberString --(SIZE(8))

--
-- Local dates are noted in the format
--
-- CCYYMMDD
--
-- where CC = century (‘19’, ‘20’,...)
-- YY = year (‘00’ – ‘99’)
-- MM = month (‘01’, ‘02’, ... , ‘12’)
-- DD = day (‘01’, ‘02’, ... , ‘31’)
--
LocalTimeStamp ::= [APPLICATION 16] NumberString --(SIZE(14))
LocationArea ::= [APPLICATION 136] INTEGER
V36.4 Page 274 of 317

LocationDescription ::= AsciiString
LocationIdentifier ::= [APPLICATION 289] AsciiString
LocationIdType ::= [APPLICATION 315] INTEGER
LocationInformation ::= [APPLICATION 138] SEQUENCE

{
networkLocation NetworkLocation OPTIONAL, -- *m.m.
homeLocationInformation HomeLocationInformation OPTIONAL,
...
}
LocationServiceUsage ::= [APPLICATION 382] SEQUENCE

{
lCSQosRequested LCSQosRequested OPTIONAL, -- *m.m.
lCSQosDelivered LCSQosDelivered OPTIONAL,
chargingTimeStamp ChargingTimeStamp OPTIONAL,
...
}
MaximumBitRate ::= [APPLICATION 421] OCTET STRING --(SIZE (1))
Mdn ::= [APPLICATION 253] NumberString
MessageDescription ::= [APPLICATION 142] AsciiString
MessageDescriptionCode ::= [APPLICATION 141] Code
MessageDescriptionInformation ::= [APPLICATION 143] SEQUENCE

{
messageDescriptionCode MessageDescriptionCode OPTIONAL, -- *m.m.
messageDescription MessageDescription OPTIONAL, -- *m.m.
...
}
MessageStatus ::= [APPLICATION 144] INTEGER
MessageType ::= [APPLICATION 145] INTEGER
MessagingEventService ::= [APPLICATION 439] INTEGER
Min ::= [APPLICATION 146] NumberString --(SIZE(2..15))
MinChargeableSubscriber ::= [APPLICATION 254] SEQUENCE

{
min Min OPTIONAL, -- *m.m.
mdn Mdn OPTIONAL,
...
V36.4 Page 275 of 317

MoBasicCallInformation ::= [APPLICATION 147] SEQUENCE

{
destination Destination OPTIONAL,
destinationNetwork DestinationNetwork OPTIONAL,
...
}
MobileSessionService ::= [APPLICATION 440] INTEGER
Msisdn ::= [APPLICATION 152] BCDString --(SIZE(1..9))
MtBasicCallInformation ::= [APPLICATION 153] SEQUENCE

{
callOriginator CallOriginator OPTIONAL,
originatingNetwork OriginatingNetwork OPTIONAL,
...
}
NetworkAccessIdentifier ::= [APPLICATION 417] AsciiString
NetworkElement ::= [APPLICATION 441] SEQUENCE

{
elementType ElementType OPTIONAL, -- *m.m.
elementId ElementId OPTIONAL, -- *m.m.
...
}
NetworkElementList ::= [APPLICATION 442] SEQUENCE OF NetworkElement
NetworkId ::= AsciiString --(SIZE(1..6))
NetworkInitPDPContext ::= [APPLICATION 245] INTEGER
NetworkLocation ::= [APPLICATION 156] SEQUENCE

{
callReference CallReference OPTIONAL,
V36.4 Page 276 of 317


...
}
NonChargedNumber ::= [APPLICATION 402] AsciiString
NonChargedParty ::= [APPLICATION 443] SEQUENCE

{
nonChargedPartyNumber NonChargedPartyNumber OPTIONAL,
nonChargedPublicUserId NonChargedPublicUserId OPTIONAL,
...
}
NonChargedPartyNumber ::= [APPLICATION 444] AddressStringDigits
NonChargedPublicUserId ::= [APPLICATION 445] AsciiString
NumberOfDecimalPlaces ::= [APPLICATION 159] INTEGER
ObjectType ::= [APPLICATION 281] INTEGER
OperatorSpecInfoList ::= [APPLICATION 162] SEQUENCE OF OperatorSpecInformation
OperatorSpecInformation ::= [APPLICATION 163] AsciiString
OrderPlacedTimeStamp ::= [APPLICATION 300] DateTime
OriginatingNetwork ::= [APPLICATION 164] NetworkId
PacketDataProtocolAddress ::= [APPLICATION 165] AsciiString
PaidIndicator ::= [APPLICATION 346] INTEGER
PartialTypeIndicator ::= [APPLICATION 166] AsciiString --(SIZE(1))
PaymentMethod ::= [APPLICATION 347] INTEGER
PdpAddress ::= [APPLICATION 167] PacketDataProtocolAddress
PDPContextStartTimestamp ::= [APPLICATION 260] DateTime
PlmnId ::= [APPLICATION 169] AsciiString --(SIZE(5))
PositioningMethod ::= [APPLICATION 395] INTEGER
PriorityCode ::= [APPLICATION 170] INTEGER
PublicUserId ::= [APPLICATION 446] AsciiString
RapFileSequenceNumber ::= [APPLICATION 181] FileSequenceNumber
V36.4 Page 277 of 317

RecEntityCode ::= [APPLICATION 184] Code
RecEntityCodeList ::= [APPLICATION 185] SEQUENCE OF RecEntityCode
RecEntityId ::= [APPLICATION 400] AsciiString
RecEntityInfoList ::= [APPLICATION 188] SEQUENCE OF RecEntityInformation
RecEntityInformation ::= [APPLICATION 183] SEQUENCE

{
recEntityType RecEntityType OPTIONAL, -- *m.m.
recEntityId RecEntityId OPTIONAL, -- *m.m.
...
}
RecEntityType ::= [APPLICATION 186] INTEGER
Recipient ::= [APPLICATION 182] PlmnId
ReleaseVersionNumber ::= [APPLICATION 189] INTEGER
RequestedDeliveryTimeStamp ::= [APPLICATION 301] DateTime
RequestedDestination ::= [APPLICATION 450] SEQUENCE

{
requestedNumber RequestedNumber OPTIONAL,
requestedPublicUserId RequestedPublicUserId OPTIONAL,
...
}
RequestedNumber ::= [APPLICATION 451] AddressStringDigits
RequestedPublicUserId ::= [APPLICATION 452] AsciiString
ResponseTime ::= [APPLICATION 394] INTEGER
ResponseTimeCategory ::= [APPLICATION 387] INTEGER
ScuBasicInformation ::= [APPLICATION 191] SEQUENCE

{
chargeableSubscriber ScuChargeableSubscriber OPTIONAL, -- *m.m.
chargedPartyStatus ChargedPartyStatus OPTIONAL, -- *m.m.
nonChargedNumber NonChargedNumber OPTIONAL, -- *m.m.
originatingNetwork OriginatingNetwork OPTIONAL,
destinationNetwork DestinationNetwork OPTIONAL,
...
}
V36.4 Page 278 of 317

ScuChargeType ::= [APPLICATION 192] SEQUENCE

{
messageStatus MessageStatus OPTIONAL, -- *m.m.
priorityCode PriorityCode OPTIONAL, -- *m.m.
distanceChargeBandCode DistanceChargeBandCode OPTIONAL,
messageType MessageType OPTIONAL, -- *m.m.
messageDescriptionCode MessageDescriptionCode OPTIONAL, -- *m.m.
...
}
ScuTimeStamps ::= [APPLICATION 193] SEQUENCE

{
depositTimeStamp DepositTimeStamp OPTIONAL, -- *m.m.
completionTimeStamp CompletionTimeStamp OPTIONAL, -- *m.m.
chargingPoint ChargingPoint OPTIONAL, -- *m.m.
...
}
ScuChargeableSubscriber ::= [APPLICATION 430] CHOICE

{
gsmChargeableSubscriber GsmChargeableSubscriber,
minChargeableSubscriber MinChargeableSubscriber,
...
}
Sender ::= [APPLICATION 196] PlmnId
ServiceStartTimestamp ::= [APPLICATION 447] DateTime
ServingBid ::= [APPLICATION 198] Bid
ServingLocationDescription ::= [APPLICATION 414] LocationDescription
ServingNetwork ::= [APPLICATION 195] AsciiString
ServingPartiesInformation ::= [APPLICATION 335] SEQUENCE

{
contentProviderName ContentProviderName OPTIONAL, -- *m.m.
contentProviderIdList ContentProviderIdList OPTIONAL,
internetServiceProviderIdList InternetServiceProviderIdList OPTIONAL,
networkList NetworkList OPTIONAL,
...
}
SessionChargeInfoList ::= [APPLICATION 448] SEQUENCE OF SessionChargeInformation
SessionChargeInformation ::= [APPLICATION 449] SEQUENCE

{
chargedItem ChargedItem OPTIONAL, -- *m.m.
callTypeGroup CallTypeGroup OPTIONAL, -- *m.m.
V36.4 Page 279 of 317

chargeDetailList ChargeDetailList OPTIONAL, -- *m.m.

taxInformationList TaxInformationList OPTIONAL,
...
}
SimChargeableSubscriber ::= [APPLICATION 199] SEQUENCE

{
imsi Imsi OPTIONAL, -- *m.m.
...
}
SimToolkitIndicator ::= [APPLICATION 200] AsciiString --(SIZE(1))
SMSDestinationNumber ::= [APPLICATION 419] AsciiString
SMSOriginator ::= [APPLICATION 425] AsciiString
SpecificationVersionNumber ::= [APPLICATION 201] INTEGER
SsParameters ::= [APPLICATION 204] AsciiString --(SIZE(1..40))
SupplServiceActionCode ::= [APPLICATION 208] INTEGER
SupplServiceCode ::= [APPLICATION 209] HexString --(SIZE(2))
SupplServiceUsed ::= [APPLICATION 206] SEQUENCE

{
supplServiceCode SupplServiceCode OPTIONAL, -- *m.m.
supplServiceActionCode SupplServiceActionCode OPTIONAL, -- *m.m.
ssParameters SsParameters OPTIONAL,
chargingTimeStamp ChargingTimeStamp OPTIONAL, -- *m.m.
chargeInformation ChargeInformation OPTIONAL,
basicServiceCodeList BasicServiceCodeList OPTIONAL,
...
}
TapCurrency ::= [APPLICATION 210] Currency
TapDecimalPlaces ::= [APPLICATION 244] INTEGER
TaxableAmount ::= [APPLICATION 398] AbsoluteAmount
Taxation ::= [APPLICATION 216] SEQUENCE

{
taxCode TaxCode OPTIONAL, -- *m.m.
taxType TaxType OPTIONAL, -- *m.m.
taxRate TaxRate OPTIONAL,
chargeType ChargeType OPTIONAL,
taxIndicator TaxIndicator OPTIONAL,
...
V36.4 Page 280 of 317

TaxationList ::= [APPLICATION 211] SEQUENCE OF Taxation
TaxCode ::= [APPLICATION 212] INTEGER
TaxIndicator ::= [APPLICATION 432] AsciiString --(SIZE(1))
TaxInformation ::= [APPLICATION 213] SEQUENCE

{
taxCode TaxCode OPTIONAL, -- *m.m.
taxValue TaxValue OPTIONAL, -- *m.m.
taxableAmount TaxableAmount OPTIONAL,
...
}
TaxInformationList ::= [APPLICATION 214] SEQUENCE OF TaxInformation
-- The TaxRate item is of a fixed length to ensure that the full 5

-- decimal places is provided.
TaxRate ::= [APPLICATION 215] NumberString (SIZE(7))
TaxType ::= [APPLICATION 217] AsciiString --(SIZE(2))
TaxValue ::= [APPLICATION 397] AbsoluteAmount
TeleServiceCode ::= [APPLICATION 218] HexString --(SIZE(2))
ThirdPartyInformation ::= [APPLICATION 219] SEQUENCE

{
thirdPartyNumber ThirdPartyNumber OPTIONAL,
...
}
ThirdPartyNumber ::= [APPLICATION 403] AddressStringDigits
ThreeGcamelDestination ::= [APPLICATION 431] CHOICE

{
camelDestinationNumber CamelDestinationNumber,
gprsDestination GprsDestination,
...
}
TotalAdvisedCharge ::= [APPLICATION 356] AbsoluteAmount
TotalAdvisedChargeRefund ::= [APPLICATION 357] AbsoluteAmount
TotalAdvisedChargeValue ::= [APPLICATION 360] SEQUENCE

{
V36.4 Page 281 of 317

advisedChargeCurrency AdvisedChargeCurrency OPTIONAL,

totalAdvisedCharge TotalAdvisedCharge OPTIONAL, -- *m.m.
totalAdvisedChargeRefund TotalAdvisedChargeRefund OPTIONAL,
totalCommission TotalCommission OPTIONAL,
totalCommissionRefund TotalCommissionRefund OPTIONAL,
...
}
TotalAdvisedChargeValueList ::= [APPLICATION 361] SEQUENCE OF

TotalAdvisedChargeValue
TotalCallEventDuration ::= [APPLICATION 223] INTEGER
TotalCharge ::= [APPLICATION 415] AbsoluteAmount
TotalChargeRefund ::= [APPLICATION 355] AbsoluteAmount
TotalCommission ::= [APPLICATION 358] AbsoluteAmount
TotalCommissionRefund ::= [APPLICATION 359] AbsoluteAmount
TotalDataVolume ::= [APPLICATION 343] DataVolume
TotalDiscountRefund ::= [APPLICATION 354] AbsoluteAmount
TotalDiscountValue ::= [APPLICATION 225] AbsoluteAmount
TotalTaxRefund ::= [APPLICATION 353] AbsoluteAmount
TotalTaxValue ::= [APPLICATION 226] AbsoluteAmount
TotalTransactionDuration ::= [APPLICATION 416] TotalCallEventDuration
TrackedCustomerEquipment ::= [APPLICATION 381] SEQUENCE

{
...
}
TrackedCustomerHomeId ::= [APPLICATION 377] SEQUENCE

{
...
}
TrackedCustomerHomeIdList ::= [APPLICATION 376] SEQUENCE OF

TrackedCustomerHomeId
TrackedCustomerIdentification ::= [APPLICATION 372] SEQUENCE
V36.4 Page 282 of 317

{
customerIdType CustomerIdType OPTIONAL, -- *m.m.
customerIdentifier CustomerIdentifier OPTIONAL, -- *m.m.
...
}
TrackedCustomerIdList ::= [APPLICATION 370] SEQUENCE OF

TrackedCustomerIdentification
TrackedCustomerInformation ::= [APPLICATION 367] SEQUENCE

{
trackedCustomerIdList TrackedCustomerIdList OPTIONAL, -- *m.m.
trackedCustomerHomeIdList TrackedCustomerHomeIdList OPTIONAL,
trackedCustomerLocList TrackedCustomerLocList OPTIONAL,
trackedCustomerEquipment TrackedCustomerEquipment OPTIONAL,
...
}
TrackedCustomerLocation ::= [APPLICATION 380] SEQUENCE

{
...
}
TrackedCustomerLocList ::= [APPLICATION 379] SEQUENCE OF TrackedCustomerLocation
TrackingCustomerEquipment ::= [APPLICATION 371] SEQUENCE

{
...
}
TrackingCustomerHomeId ::= [APPLICATION 366] SEQUENCE

{
...
}
TrackingCustomerHomeIdList ::= [APPLICATION 365] SEQUENCE OF

TrackingCustomerHomeId
TrackingCustomerIdentification ::= [APPLICATION 362] SEQUENCE

{
customerIdType CustomerIdType OPTIONAL, -- *m.m.
customerIdentifier CustomerIdentifier OPTIONAL, -- *m.m.
...
}
V36.4 Page 283 of 317

TrackingCustomerIdList ::= [APPLICATION 299] SEQUENCE OF

TrackingCustomerIdentification
TrackingCustomerInformation ::= [APPLICATION 298] SEQUENCE

{
trackingCustomerIdList TrackingCustomerIdList OPTIONAL, -- *m.m.
trackingCustomerHomeIdList TrackingCustomerHomeIdList OPTIONAL,
trackingCustomerLocList TrackingCustomerLocList OPTIONAL,
trackingCustomerEquipment TrackingCustomerEquipment OPTIONAL,
...
}
TrackingCustomerLocation ::= [APPLICATION 369] SEQUENCE

{
...
}
TrackingCustomerLocList ::= [APPLICATION 368] SEQUENCE OF

TrackingCustomerLocation
TrackingFrequency ::= [APPLICATION 389] INTEGER
TrackingPeriod ::= [APPLICATION 388] INTEGER
TransactionAuthCode ::= [APPLICATION 342] AsciiString
TransactionDescriptionSupp ::= [APPLICATION 338] INTEGER
TransactionDetailDescription ::= [APPLICATION 339] AsciiString
TransactionIdentifier ::= [APPLICATION 341] AsciiString
TransactionShortDescription ::= [APPLICATION 340] AsciiString
TransactionStatus ::= [APPLICATION 303] INTEGER
TransferCutOffTimeStamp ::= [APPLICATION 227] DateTimeLong
TransparencyIndicator ::= [APPLICATION 228] INTEGER
UserProtocolIndicator ::= [APPLICATION 280] INTEGER
UtcTimeOffset ::= [APPLICATION 231] AsciiString --(SIZE(5))
UtcTimeOffsetCode ::= [APPLICATION 232] Code
UtcTimeOffsetInfo ::= [APPLICATION 233] SEQUENCE

{
utcTimeOffsetCode UtcTimeOffsetCode OPTIONAL, -- *m.m.
V36.4 Page 284 of 317

utcTimeOffset UtcTimeOffset OPTIONAL, -- *m.m.

...
}
UtcTimeOffsetInfoList ::= [APPLICATION 234] SEQUENCE OF UtcTimeOffsetInfo
VerticalAccuracyDelivered ::= [APPLICATION 393] INTEGER
VerticalAccuracyRequested ::= [APPLICATION 386] INTEGER
--
-- Tagged common data types
--
--
-- The AbsoluteAmount data type is used to
-- encode absolute revenue amounts.
-- The accuracy of all absolute amount values is defined
-- by the value of TapDecimalPlaces within the group
-- AccountingInfo for the entire TAP batch.
-- Note, that only amounts greater than or equal to zero are allowed.
-- The decimal number representing the amount is
-- derived from the encoded integer
-- value by division by 10^TapDecimalPlaces.
-- for example for TapDecimalPlaces = 3 the following values
-- will be derived:
-- 0 represents 0.000
-- for TapDecimalPlaces = 5 the following values will be
-- derived:
-- 1234 represents 0.01234
-- 123456 represents 1.23456
-- This data type is used to encode (total)
-- charges, (total) discount values and
-- (total) tax values.
--
AbsoluteAmount ::= INTEGER
Bid ::= AsciiString --(SIZE(5))
Code ::= INTEGER
--
-- Non-tagged common data types
--
--
-- Recommended common data types to be used for file encoding:
--
V36.4 Page 285 of 317

-- The following definitions should be used for TAP file creation instead of
-- the default specifications (OCTET STRING)
--
-- AsciiString ::= VisibleString
--
-- Currency ::= VisibleString
--
-- HexString ::= VisibleString
--
-- NumberString ::= NumericString
--
-- AsciiString contains visible ISO 646 characters.
-- Leading and trailing spaces must be discarded during processing.
-- An AsciiString cannot contain only spaces.
AsciiString ::= OCTET STRING
--
-- The BCDString data type (Binary Coded Decimal String) is used to represent
-- several digits from 0 through 9, a, b, c, d, e.
-- Two digits are encoded per octet. The four leftmost bits of the octet
represent
-- the first digit while the four remaining bits represent the following digit.
-- A single f must be used as a filler when the total number of digits to be
-- encoded is odd.
-- No other filler is allowed.
BCDString ::= OCTET STRING
--
-- The currency codes from ISO 4217
-- are used to identify a currency
--
Currency ::= OCTET STRING
--
-- HexString contains ISO 646 characters from 0 through 9, A, B, C, D, E, F.
--
HexString ::= OCTET STRING
--
-- NumberString contains ISO 646 characters from 0 through 9.
--
NumberString ::= OCTET STRING
--
-- The PercentageRate data type is used to
-- encode percentage rates with an accuracy of 2 decimal places.
-- This data type is used to encode discount rates.
V36.4 Page 286 of 317

-- The decimal number representing the percentage

-- rate is obtained by dividing the integer value by 100
-- Examples:
--
-- 1500 represents 15.00 percent
-- 1 represents 0.01 percent
--
PercentageRate ::= INTEGER
END
V36.4 Page 287 of 317

6.2 Transfer Syntax

The Transferred Account Information Elements, as defined above, have to be encoded using
the Basic Encoding Rules (BER) as specified within ITU Rec. X.690 [38].
6.3 File Naming Conventions
6.3.1 Chargeable TAP Data

TAP files containing chargeable data must follow the following naming convention:
CDxxxxxyyyyySEQNO
where
CD identifies the file as containing chargeable data

xxxxx contains the sender PMN in uppercase
yyyyy contains the recipient PMN in uppercase
SEQNO contains the File Sequence Number
6.3.2 Test TAP Data

TAP files containing test data must follow the following naming convention:
TDxxxxxyyyyySEQNO
where
TD identifies the file as containing test data

xxxxx contains the sender PMN in uppercase
yyyyy contains the recipient PMN in uppercase
SEQNO contains the File Sequence Number
7 Migration to a New Release

The rules in this section apply to TAP files exchanged over the public interface. TAP files
exchanged over the private interface, for example between an operator and their agent, is
out of scope of these migration rules.
There is an Effective Date for each release. This is the date from which companies may
send and must be able to receive the release over the public interface.
As only the latest two TAP versions are supported on the public interface, the Effective Date
of a new release (n) also indicates the date from which release n-2 cannot be sent on the
public interface. See also paragraph below regarding handling of resubmitted files. Any
exceptions to this must be bilaterally agreed in good time before the Effective Date to ensure
TAP exchanges are not impacted.
BA.12 [12] defines the liabilities regarding file conversion between versions.
Any company implementing a new release may implement the input and output
simultaneously or may implement one at a time.
V36.4 Page 288 of 317

Companies which plan to migrate to a new release before the Effective Date are responsible
for bilaterally agreeing such exchange with their roaming partners.
Where a TAP file has been rejected or reported as missing and it has been created before
migration, the file may be corrected and/or resubmitted in either the original release or the
currently supported release, taking the timescales defined in BA.08 [10] into consideration
where applicable.
It is not allowed to revert to the old release, once the first files of the new release have been
exchanged in commercial operation (excluding resubmitted files which have been
rejected/reported as missing before the release switch, test files and files up-converted in
error by DCH).
Each company must state in its AA.14 (RAEX Op Data [39] & [40]) what TAP versions it can
send and receive over the public interface and changes to this must be sent at least 2 weeks
before the change becomes effective. A migration to a release containing major changes
must only be performed after the appropriate format testing has been completed.
V36.4 Page 289 of 317

Annex A Supplementary Services

In order to determine the records raised in conjunction with the use of Supplementary
Services it is necessary to distinguish between the administration of services by the
subscriber and additional information raised as a result of the usage of those services.
In general the following functions (actions) are available to the subscriber for the
administration of supplementary services.
 Registration:
The programming by the subscriber of information to enable subsequent operation of
a service for example the “forwarded-to” number for call forwarding.
 Activation:
Some services, call forwarding for example, are activated as a result of registration
and no further action is required. Other services, call barring for example, must be
explicitly activated.
 Deactivation:
Deactivates a previously activated service.
 Erasure:
The deletion of information provided during registration.
 Interrogation:
This function permits the subscriber to interrogate the status of supplementary
services and any information (numbers, passwords etc.) stored during registration.
 Invocation:
The use of a service. A supplementary service may be invoked by the subscriber or
automatically by the network.
Call Hold and Call Transfer, for example, are both invoked explicitly by the subscriber
whereas Call Forwarding on No Reply is invoked implicitly by the network if the subscriber
fails to answer an incoming call within a predefined time limit.
All supplementary service events are considered instantaneous even though, for example,
an interrogation may take several seconds to complete by the network. Nevertheless most
supplementary service actions utilise network resources and charging principles take
account of this.
The invocation of a supplementary service occurs in conjunction with a mobile originated or

mobile terminated call event (attempt). Depending on the network configuration (see 3GPP
TS 32.005 [4]), the invocation of the supplementary service can be recorded either within the
same call record as the corresponding call or within a separate ‘supplementary service
action’ call record. On the TAP interface both concepts are supported (IN line vs. OFF line
recording). Wherever the information is received within a single call record from the network
by the VPMN operator, only one call event should be created for TAP, in order to support
customer care enquiries by the HPMN operator.
Not all of the actions described are relevant for all supplementary services. Valid
combinations are described in detail in 3GPP TS 22.004 [1]. The following table contains the
relevant combinations for the purpose of TAP.
For the purposes of the table a notation is used as follows:
V36.4 Page 290 of 317

‘-‘ An invalid combination of Service Code and Action (as defined by 3GPP TS 22.004
[1])
‘Y’ A valid and relevant combination of Service Code and Action which must be
transferred in the TAP
‘O’ A valid and relevant combination of Service Code and Action which optionally can be
transferred in the TAP for customer care purposes
‘N’ A valid and relevant combination of Service Code and Action which must not be
transferred in the TAP
‘F’ A valid and relevant combination of Service Code and Action that is for further study
In addition to the actions described in 3GPP TS 22.004 [1] further possible actions are
described within the man-machine interface, 3GPP TS 22.030 [2]. These are:
 Deactivate all call forwarding

 Deactivate all conditional call forwarding
 Deactivate all call barring
 Deactivate all incoming call bars
 Deactivate all outgoing call bars
For further details concerning general use of supplementary services see 3GPP TS 22.004
[1].
Action
Interrogation
Deactivation
Registration
Invocation
Password
Activation
Erasure
Supplementary Service 0 1 2 3 4 5 6
00 All supplementary services - - - - - - O
10 All line identification service - - - - - - -
11 Calling number identification presentation - - - - N O -
12 Calling number identification restriction - - O - N N -
13 Connected number identification presentation - - - - N N -
14 Connected number identification restriction - - N - N N -
18 All name identification SS - - - - N N -
19 Calling name presentation - - - - N O -
20 All call forwarding O O O O - - -
21 Call forwarding unconditional O O O O N - -
24 Call deflection - - - - - O -
28 All conditional call forwarding O O O O - - -
29 Call forwarding on mobile subscriber busy O O O O N Y -
2A Call forwarding on no reply O O O O N Y -
2B Call forwarding on subscriber not reachable O O O O N Y -
30 All call offering services - - - - - - -
31 Call transfer - - - - - O -
40 All call completion services - - - - - - -
41 Call waiting - - O O N N -
42 Call hold - - - - - O -
43 Completion of calls to busy subscribers – - O O O N O -
origination side
44 Completion of calls to busy subscribers – - O O O N O -
destination side
V36.4 Page 291 of 317

Action
Interrogation
Deactivation
Registration
Invocation
Password
Activation
Erasure
Supplementary Service 0 1 2 3 4 5 6
45 Multicall N - - - N O -
50 All multi party services - - - - - - -
51 Multi party service - - - - - O -
60 All community of interest services - - - - - - -
61 Closed user groups - - - - - O -
70 All charging supplementary services - - - - - - -
71 Advice of charge – information - - - - - O -
72 Advice of charge – charging - - - - - O -
80 All additional info transfer services - - - - - - -
81 UUS1 user to user signalling - - O O - O -
90 All call barring O - - O - - N
91 All barring of outgoing call services - - - O - - -
92 Barring of all outgoing calls - O O O N - -
93 Barring of all outgoing international calls - O O O N - -
94 Barring of all outgoing international except HPMN - O O O N - -
99 All barring of incoming call services - - - O - - -
9A Barring of all incoming calls - O O O N - -
9B Barring of all IC calls when outside HPMN - O O O N - -
Table 46: Relevant Supplementary Service Combinations to be Transferred in TAP
V36.4 Page 292 of 317

Annex B Changes from Previous Specification Version Number

This section lists the requirements for TAP Specification Version Number 3, i.e. the changes
needed from TAP Specification Version Number 2 Release Version Number 2.
Description Originator Release Comments

Version
Aggregated Usage WAS 12 Bilaterally agreed new record for
representation of aggregated
wholesale usage and charges –
Aggregated Usage Record.
Effective from 01 July 2017.
Wi-Fi changes Wi-Fi 12 Changes to enable interoperability
Roaming with Wi-Fi roaming.
Task Force Effective from 01 May 2013.
Charge validation BARG 12 Standardisation of the Charge
validation procedure.
Effective from 01 May 2013.
Support of Voice and SMS BARG 12 Adds two new Call Event Detail
over LTE (VoLTE) records, one to support voice over
LTE (Mobile Session) and another to
support SMS over LTE (Messaging
Event).
Enabler for differential MTC BARG 12 Addition of Call Type Levels, with new
charging values, to enable charge
differentiation for MTCs based on
incoming route.
Support of LTE/SAE bit pipe BARG 11 Adds new recording entity types.
accounting model Updates to Call Type Level 1 and
duplicate checks.
Addition of optional Tax BARG 11 Addition of optional Tax Indicator to
Indicator identify VAT specifically.
Clarification on item TADIG 11 Clarification and simplification of item
derivations derivations for each GSM/3GPP
release.
Additional valid SS TADIG 11 Alignment of valid SS actions with
Code/Action Code technical standards.
combinations
Network Extensions support BARG 11 Addition of validation rule to support
bilateral use of Serving Network to
identify Network Extensions.
Support published and BARG 11 Enable inclusion of published IOT
discounted IOTs charge in addition to invoiceable,
discounted, charge.
Simplification of TAP BARG 11 Simplification of data structures in line
with BA.12.
Major changes include
Replacement of HSCSD parameters
with simple indicator
Simplification of CAMEL including
representation of charges
Simplification of Charge Information
including removal of Day Category
and Time Band information
Removal of dual service codes
(MOC/MTC)
Removal of QoS in GPRS ~ replaced
V36.4 Page 293 of 317

by inclusion of Call Type Level 1/2/3

and new values for these items
Removal of Value Added Service
Removal of implementation TADIG 11 Removal of implementation guidance
annexes annexes to new handbook (TD.58).
Removal of redundant ASN.1 TADIG 11 ASN.1 items no longer in use
items removed and application numbers
released for future use.
IMS support BARG 11 Addition of IMS Signalling Indicator.
Additional items for UMTS BARG 11 New items added to support UMTS
CS bearer circuit switched bearer usage charging
principles.
Clarification of video TADIG 11 Text addition to clarify technical
telephony representation representation of video telephony
protocol.
Enhanced flexibility of ASN.1 TADIG 11 Rationalisation of Recording Entity
structures representation in physical format.
Enhanced MOC duplicate TADIG 11 Cater for Dialled Digits within MOC
check duplicate check.
Enhanced Wi-Fi TADIG 11 Addition of specific username
representation identification item.
Revised derivation details for WiFi
data volumes.
Increase in allowable number of
recording entities.
Fatal Exchange Rate error at TADIG 11 Change exchange rate validation
call level errors at call level from severe to fatal.
Identification of SMS BARG 11 New item added to MOC for
destination number identification of actual SMS
destination number.
Physical enhancement for TADIG 11 Allow non telephony identification of
non GSM applications non charged parties.
Reduction in maximum file TADIG 11 Change maximum TAP file size to
size. 100Mb.
Satellite value in Call Type BARG 11 Addition of new ‘satellite’ value in Call
Type Level 2.
Wi-Fi duplicate check TADIG 11 Enhancement to GPRS Call duplicate
check to cater for Wi-Fi usage.
Addition of Dialled Digits BARG 10 New item Dialled Digits added to
complement Called Number.
Additional validation for TADIG 10 Additional validation to stop
multiple basic services misrepresentation of basic service
usage.
Annex to clarify GPRS SMS TADIG 10 New annex to clarify how to
identification distinguish CS and PS SMS usage.
Annex to clarify various TADIG 10 New annex detailing item population
charge related items where Charged Item is ‘N’, also
population of tax items.
Annex to clarify various TADIG 10 New annex clarifying population of
timestamp & duration items Total Call Event Duration and related
items within charging related items.
Bilateral location and charge NA TADIG 10 NA market area validation (bilateral) of
validation location information (Serving BIDs and
Serving Location Descriptions) and
Air/Toll charge breakdown.
CAMEL support in GPRS BARG 10 Addition of CAMEL information to
GPRS contexts.
Change ASN.1 type (VAS TADIG 10 Change ASN.1 types for VAS
elements) Description and VAS Short
V36.4 Page 294 of 317

Description.
Change Called Country BARG 10 Change derivation of Called Country
representation TADIG Code to use ISO standard.
Change to representation of TADIG 10 Tax information broken down to allow
taxes validation of tax value against taxable
charges.
Clarification of timestamps in TADIG 10 Clarification on population of Call
GPRS partials Event Start Timestamp within
intermediate and last GPRS partials.
Clarification on Called TADIG 10 New annex giving examples of how to
Number and Dialled Digit populate Called Number and Dialled
population Digits.
Clarification on GPRS partial TADIG 10 New annex giving guidelines re
handling handling of GPRS partials.
Clarification re BER usage TADIG 10 Clarification that strict BER is to be
used for encoding TAP.
Consistent Called Number BARG 10 Called Number to always be
representation represented in ‘international’ format
Content Transaction ASN.1 TADIG 10 Change of ASN.1 syntax to allow
correction repeating Content Service Used
representation.
Daily Usage Charge support BARG 10 Clarification of how to represent Daily
Usage Charges.
Duplicate file handling TADIG 10 Clarification on how to handle
clarification duplicate files and reused sequence
numbers.
GMLC recording entity TADIG 10 Clarification on how to populate
clarification Recording Entity for GMLCs.
GPRS cause for termination TADIG 10 Clarification to representation of cause
clarification for termination in GPRS partial cases.
GPRS partial limits BARG 10 Number of GPRS partials for single
context limited.
GPRS QoS parameters BARG 10 GPRS GSM and UMTS QoS
rationalised parameters rationalised to reflect
charging requirement and
infrastructure capability.
Handling unexpected CAMEL BARG 10 Additional validation to reject
information unexpected CAMEL invocation
charges.
Increase integer sizes TADIG 10 Various items of type INTEGER
require size increases from 4 bytes to
8 bytes.
Invalid ASN.1 tag clarification TADIG 10 Clarification regarding BER and
syntax violation (invalid tags).
Location Service support BARG 10 New call/event to support Location
Services (LCS).
Market area specific NA TADIG 10 Inclusion of bilateral validation for
validation included North American market. This is a
market specific validation rather than
only bi-polar – bi-polar changes would
not be included.
M-Services support BARG 10 Addition of new item and item values
to support m-services requirement.
Partial Type validation BARG 10 Partial Type Indicator validation
severity increased to severe.
Reference data constraints TADIG 10 Various changes to validation severity
and ranges to limit reference data
tables to reasonable levels.
SS events correction TADIG 10 Correction to table of SS events
V36.4 Page 295 of 317

eligible for inclusion in TAP.

Taxation validation BARG 10 Additional validation to ensure tax is in
NA BARG line with roaming agreements
UMTS CS bearer usage BARG 10 Additional items and restructuring of
existing items to allow differential
pricing of UMTS CS bearer usage.
USSD usage validation BARG 10 Additional validation for USSD usage.
USSD validation BARG 10 Insertion of validation rules for USSD
usage.
Validation of commercial TADIG 10 New validation to ensure that a HPMN
liability can reject financial liability for
call/events dated prior to the
commercial roaming start date either
for new agreements or new services.
Validation of empty ASN.1 TADIG 10 Clarification on handling of zero length
items (empty) ASN.1 items.
Various general corrections TADIG 10 Value derivation corrections for QoS
Peak Throughput, User Protocol
Indicator.
Removal of IOT references in
discounting.
Correction of contexts for VAS Used
validation.
Clarification/correction to valid ranges
for various items of type
AddressStringDigits.
Wi-Fi support BARG 10 Interim solution to enable Wi-Fi
TADIG support by reusing GPRS Call
elements.
Additional validation for TADIG 09 New validation rule (severe error) to
Charging Timestamp check integrity of Charging
Timestamp.
Clarification of bilateral item TADIG 09 Clarification to validation rules
validation applicable when bilateral items/groups
present.
Clarification of population of TADIG 09 New appendix to clarify the derivation
Destination group items of Type Of Number and Numbering
Plan, includes extracts from the
relevant GSM technical papers.
Clarification to call timestamp TADIG 09 Addition of derivation and descriptive
derivation text to Call Event Start Timestamp
and Charging Timestamp.
Correction to support GPRS TADIG 09 Allow GSN recording entity
SMS identification to contain either
GSNAddress or Msisdn.
Correction to Transfer Cut BARG 09 Existing validation severity to become
Off Timestamp validation fatal errors.
GPRS Call duplicate check BARG 09 Change to the GPRS duplicate check
to enforce only one GPRS Call for any
given part of a context (i.e. no
separate SGSN and GGSN charging).
Removal of Delivery Note TADIG 09 Removal of all references to Delivery
information Note, now contained in TD.33.
Revised Call Type validation BARG 09 New validation to validate Call Type
information against the IOT.
Serving Network validation TADIG 09 New syntax validation rule added.
Tax treatment clarification BARG 09 Statement that 296mitted296 of tax
information from a call/event where
tax is applicable must be the same as
V36.4 Page 296 of 317

zero tax (i.e. tax cannot be 297mitted

from the TAP file and later applied to
an invoice only).
Various editorial corrections TADIG 09 See the following:
Validation rules for Quality Of Service
Used.
Call Reference contexts.
Charge Information diagram (Time
Band Subtype).
GPRS Basic Call Information diagram
(Charging Id).
Validation rules for Order Placed
Timestamp, Requested Delivery
Timestamp and Actual Delivery
Timestamp.
Physical syntax optionality correction
for Content Transaction items.
Note Release Version TADIG 08 Release Versions skipped to align
skipped PRD versions with TAP versions (see
also TD.34 TAP Release
Management).
Management).
Management).
Note Release Versions 05 – TADIG 05 Release Versions skipped to align
08 inclusive skipped PRD versions with TAP versions (see
Management).
Addition of Content BARG 04 New Call Event Details to cater for
Transaction content transaction charging plus
associated audit control information.
Addition of GPRS Call partial TADIG 04 New item PDP Context Start
context start timestamp Timestamp for intermediate and last
partials to identify true context start
(optional item).
Additional occurrences of TADIG 04 Change Operator Specific Information
free format data item to be repeating.
Called Number Analysis TADIG 04 Called Number Analysis group only
presence rationalised required if MOCs or SCUs present
within file.
Change Ipv6 address length TADIG 04 Change IPTextV6Address size to
reflect standard (RfC 2373).
Exceptional file transmission BARG 04 Addition of ‘fatal’ validation for
timescale validation. excessive differences between actual
time a TAP file is received and the
indicated availability timestamp.
Fix relative positions of TADIG 04 Clarification to ensure version number
Specification and Release items must never be moved from their
Version Numbers within file. relative positions within files.
New item Mobile Directory NA TADIG 04 New item MDN to support mobile
Number number portability within an inter
standard roaming environment
(CIBER/TAP).
New item Serving Network TADIG 04 New item Serving Network to identify
V36.4 Page 297 of 317

the serving network when this is not

the TAP file sender.
Pegged exchange rate BARG 04 Revised/new validation to ensure
validation. variances from expected pegged
exchange rates do not penalise the
HPMN.
Support CAMEL usage within BARG 04 Addition of CAMEL usage data within
GPRS context GPRS Call. Changes to CAMEL
usage data structure to support GPRS
invocation.
Support GPRS and inter TADIG 04 Chargeable subscriber structure
standard roaming change within GPRS Call to support
MINs and MDNs.
Support revised IOT structure BARG 04 Changes to Call Type structure and
values to support 3 level IOT
structure.
Support UMTS QoS BARG 04 Addition of UMTS QoS parameters
within GPRS Call.
Additional GPRS call TADIG 03 Enhanced GPRS data item validation
validation to ensure data integrity.
ASN.1 list validation TADIG 03 Clarification of validation for ASN.1
clarification lists.
BID/Serving location NA TADIG 03 Additional validation to support use of
validation BIDs.
Exchange Rate validation TADIG 03 Exchange Rate not required for zero
rated calls.
Rationalisation of reference TADIG 03 Changes to various reference data
data validation element validation to ensure
consistency.
Removal of TADIG 03 Removal of rules 30 & 31 for Call
incorrect/redundant validation Event Details.
rules Removal of rule 30 for Basic HSCSD
Parameters.
SMSC identification BARG 03 Inclusion of SMSC address within
MTCs where SMS received.
Tax Value validation changes NA TADIG 03 Changes to relax Tax Value validation
where the Sender has variable tax
rates applicable to part or whole of the
Charge.
Various clarifications TADIG 03 Upper case Sender and Recipient
items.
Derivation of Charged and
Chargeable Units.
Meaning of ‘reserved’ values.
Integer size within ASN.1
specification.
Call Type validation.
UTC Time Offset description.
Support of charging for BARG 02 An interim solution for USSD
USSDs charging; reuse of the Supplementary
Service Event.
Support use of Notification TADIG 02 Addition of test file indicator (file type
within Rejects & Returns indicator) to Notification files.
testing
Test timeliness of TAP file BARG 02 Addition of a validation rule comparing
transfer. the File Available Timestamp with the
actual date/time the file was received
at the HPMN (or their nominated
agent).
V36.4 Page 298 of 317

14.4 kbps User Rate SERG 01 Addition of channel coding within

HSCSD.
Additional call destination NAIG 01 Addition of called place and region
details (mobile originated information.
calls)
Alternate TAP currency NAIG 01 Addition of currency item to show
where the currency of the charges on
the TAP are not in SDRs. This is for
use by bilateral agreement, primarily
in internal markets, for example
national roaming.
Call level discounts BARG 01 Discount rates and absolute amounts
per call/event. All charges will be net
of discounts.
CAMEL phase 2 BARG 01 Addition of CAMEL service level used
SERG and free format CAMEL server
information. The ‘follow-on’ feature
will be supported by raising separate
CDRs for each ‘follow-on’ leg.
Cause for termination BARG 01 Addition of cause for call termination
NAIG information.
SERG
Charges by rate period NAIG 01 Charge information allows provision of
charges at rate period level.
EFR BARG 01 Speech versions requested and used
SERG included.
Enhanced location NAIG 01 Addition of longitude and latitude.
information SATIG Addition of served BID information
and/or descriptive location
information.
Enhancement to duplicate TADIG 01 Addition of MSC call reference
checks number.
Extra decimal places on BARG 01 Addition of a new item identifying the
charge amounts. number of decimal places used
throughout the TAP file.
FIGS SMG10 01 Inclusion of a fraud monitoring
FF indicator and third party number.
Flexible format encoding GSM 01 ASN.1 used.
mechanism Association
GPRS phase 1 BARG 01 Addition of a new call type for GPRS
SERG service usage.
Home market location NAIG 01 Addition of home BID information.
information
HPMN Repricing BARG 01 Addition of type of call, day category
and time band information.
Charge information structured to show
changes in rate periods.
HSCSD BARG 01 Addition of HSCSD information
SERG elements.
Identification of ‘local’ TADIG 01 Addition of local currency item, i.e. the
currency currency of the charge prior to
conversion to SDRs (see Alternate
TAP currency).
Identification of tax at BARG 01 All call charges will be exclusive of tax
call/event level and specific tax values will be
associated with each call/event, where
appropriate.
Millennium compliance BARG 01 All dates expanded to include century
TADIG information.
V36.4 Page 299 of 317

MSP BARG 01 MSISDN used included on the

SERG transfer.
Multiple tax types IIG 01 The table of tax codes is enhanced to
NAIG cater for multiple types of tax
Provision of non-specific data NAIG 01 Inclusion of a general purpose item for
item use by bilateral agreement and its
content will be specified between
roaming partners.
Removal of table size TADIG 01 Supported by the flexible format.
constraints SATIG
Separation of Air and Toll IIG 01 Separate charge details may be
charges NAIG supplied identifying individual
elements of the invoiceable charge.
SIM Application Toolkit SERG 01 Addition of an indicator identifying
where the call/event was initiated by
the SIM application toolkit.
SPNP BARG 01 Implicitly supported using CAMEL
SERG service usage information.
Support of multiple standard SATIG 01 IS41 characteristics are supported by
roaming inclusion of the MIN and ESN.
Support of Rejects & Returns BARG 01 Addition of item identifying data to be
process NAIG resubmitted having been previously
rejected as invalid.
Total call/event duration BARG 01 Addition of total call duration. This
TADIG allows calls where charging was by
volume only to be ‘age checked’
correctly.
Table 47: Specification changes
V36.4 Page 300 of 317

Annex C Description of 3GPP Releases and Specifications
C.1 Charging Specifications

The table below provides a description of the development of 3GPP releases and the
corresponding charging specifications applicable to every GSM/3GPP release.
Note: All 3GPP specifications (including the old GSM specifications previously maintained
by ETSI) can be found on the 3GPP ftp site: http://www.3gpp.org/ftp/Specs/archive/.
Phase 2
Releases Releases Releases 6, 7,
and Release 5
97, 98 99, 4 8, 9, 10, 11
Release 96
CS domain charging TS 12.05 [17] TS 12.05 TS 32.005 TS 32.205 TS 32.298 [8]
[17] [4] [6]
PS domain charging TS 12.15 TS 32.015 TS 32.215 TS 32.298 [8]
[18] [5] [7]
IMS domain charging TS 32.225 TS 32.298 [8]
[41]
SMS Charging TS 32.298 [8] &
32.274 [42]
LCS charging TS 32.298 [8]
Table 48: 3GPP Charging Specifications for 3GPP Releases
C.2 Cause for Termination

The below two tables list the Cause for Termination values which are valid for each 3GPP
release. The valid values have been separately listed for circuit switched and packet
switched and IMS domains.
Value Description Phase 2 and Releases Release 5 Releases

Release 96 97, 98, 99, 6, 7, 8, 9,
4 10, 11
TS 12.05 [17] TS 32.205 TS 32.205 TS 32.298
[6] [6] [8]
0 Normal Release Y Y Y Y
1 Partial Record Y Y Y Y
2 Partial Record Call
Y Y Y Y
Reestablishment
3 Unsuccessful Call Attempt Y Y Y Y
4 Stable Call Abnormal
Y Y Y Y
Termination
5 CAMEL Initiated Call
Y Y Y
Release
6 CAMEL CPH Call
Y*
Configuration Change
Table 49: Cause for Termination Values – Circuit Switched Domain
*Note: Value 6 above was only present in Release 5.
V36.4 Page 301 of 317

Value Description Releases Release 99 Releases 4, 5 Releases 6, 7,

97, 98 8, 9, 10, 11
TS 12.15 TS 32.015 [5] TS 32.215 [7] TS 32.298 [8]
[18]
0 Normal Release Y Y Y Y
4 Abnormal
Y Y Y Y
Release
5 CAMEL initiated
Y Y Y
Call Release
16 Volume Limit Y Y Y Y
17 Time Limit Y Y Y Y
18 SGSN Change Y Y Y Y
19 Maximum
Change Y Y Y Y
Condition
20 Management
Y Y Y Y
Intervention
21 Intra SGSN
Intersystem Y Y
Change
22 RAT Change Y
23 MS Time Zone
Y
Change
24 SGSN PLMNID
Y
Change
Table 50: Cause for Termination Values – Packet Switched Domain
Value Description Release 5 Releases 6, 7, 8,

9, 10, 11
TS 32.225 [41] TS 32.298 [8]
0 Service Delivery End Successfully Y Y
1 Unsuccessful Service Delivery Y Y
3 Time limit Y Y
4 Service Change Y Y
5 Management Intervention Y Y
6 Maxchangecond Y (see note below)
Table 51: Cause for Termination Values – IMS Domain
Note: Value 6 above was only present in Release 5
C.3 Service Codes

The below three tables shows the development of the 3GPP releases and the corresponding
valid Teleservice codes , Bearer Service codes and Supplementary Service Codes for each
3GPP release.
Value Description Phase 2 Releases 96, 97, 98 Releases 99, 4, 5, 6,

7, 8, 9, 10, 11
TS 09.02 [43] TS 09.02 [43] TS 29.002 [44]
00 All teleservices
Y Y Y
V36.4 Page 302 of 317

Value Description Phase 2 Releases 96, 97, 98 Releases 99, 4, 5, 6,

7, 8, 9, 10, 11
TS 09.02 [43] TS 09.02 [43] TS 29.002 [44]
10 All Speech
transmission Y Y Y
services
11 Telephony
Y Y Y
12 Emergency calls
Y Y Y
20 All SMS services
Y Y Y
21 Short message
Y Y Y
MT/PP
22 Short message
Y Y Y
MO/PP
60 All facsimile
transmission Y Y Y
services
61 Facsimile group 3
& alternative Y Y Y
speech
62 Automatic
Y Y Y
facsimile group 3
63 Automatic
Y Y Y
facsimile group 4
70 All data
teleservices Y Y Y
(compound)
80 All teleservices
except SMS Y Y Y
(compound)
90 All voice group
Y Y
call services
91 Voice group call
Y Y
92 Voice broadcast
Y Y
call
Table 52: 3GPP Releases and Corresponding Valid Teleservice Codes
Phase 2 and Releases 99, 4, 5, 6,

Value Description Releases 96, 97, 98 7, 8, 9, 10, 11
TS 09.02 [43] TS 29.002 [44]
00 All Bearer Services Y Y
20 All Data Circuit Asynchronous Services Y Y
21 Duplex Asynch. 300bps data circuit Y Y
23 Duplex Asynch. 1200/75bps data circuit Y Y
27 General Data Circuit Asynchronous
Y Y
Service
30 All Data Circuit Synchronous Services Y Y
V36.4 Page 303 of 317

Phase 2 and Releases 99, 4, 5, 6,

Value Description Releases 96, 97, 98 7, 8, 9, 10, 11
TS 09.02 [43] TS 29.002 [44]
32 Duplex Synch. 1200bps data circuit Y Y
37 General Data Circuit Synchronous
Y Y
Service
40 All Dedicated PAD Access Services Y Y
41 Duplex Asynch. 300bps PAD access Y Y
43 Duplex Asynch. 1200/75bps PAD access Y Y
47 General PAD Access Service Y Y
50 All Dedicated Packet Access Services Y Y
54 Duplex Synch. 2400bps PAD access Y Y
57 General Packet Access Service Y Y
60 All Alternate Speech/Asynchronous
Y Y
Services
70 All Alternate Speech/Synchronous
Y Y
Services
80 All Speech followed by Data
Y Y
Asynchronous Services
90 All Speech followed by Data
Y Y
Synchronous Services
A0 All Data Circuit Asynchronous Services
Y Y
(compound)
B0 All Data Circuit Synchronous Services
Y Y
(compound)
C0 All Asynchronous Services (compound) Y Y
D0 All Synchronous Services (compound) Y Y
Table 53: 3GPP Releases and Corresponding Valid Bearer Service Codes
Value Description Phase 2 Release 97 Release Releases 99,

and 98 4, 5, 6, 7, 8,
Release 96 9, 10, 11
TS 09.02 TS 09.02 TS 09.02 TS 29.002
[43] [43] [43] [44]
00 All supplementary services Y Y Y Y
10 All line identification Y Y Y Y
services
11 Calling number Y Y Y Y
identification presentation
12 Calling number Y Y Y Y
identification restriction
13 Connected number Y Y Y Y
identification presentation
V36.4 Page 304 of 317


and 98 4, 5, 6, 7, 8,
Release 96 9, 10, 11
TS 09.02 TS 09.02 TS 09.02 TS 29.002
[43] [43] [43] [44]
14 Connected number Y Y Y Y
identification restriction
18 All name identification SS Y Y Y
19 Calling name presentation Y Y Y
20 All call forwarding Y Y Y Y
21 Call forwarding Y Y Y Y
unconditional
24 Call deflection Y Y Y
28 All conditional Call Y Y Y Y
Forwarding
29 Call forwarding on mobile Y Y Y Y
subscriber busy
2A Call forwarding on no reply Y Y Y Y
2B Call forwarding on Y Y Y Y
subscriber not reachable
30 All call offering services Y Y Y Y
31 Call transfer Y Y Y Y
40 All call completion services Y Y Y Y
41 Call waiting Y Y Y Y
42 Call hold Y Y Y Y
43 Completion of calls to busy Y Y Y Y
subscribers – originating
side
44 Completion of call to busy Y Y Y
subscribers – destination
side
45 Multicall Y Y
50 All multi party services Y Y Y Y
51 Multi party service Y Y Y Y
60 All community of interest Y Y Y Y
services
61 Closed user groups Y Y Y Y
70 All charging supplement Y Y Y Y
services
71 Advice of charge Y Y Y Y
(information)
72 Advice of charge (Charging) Y Y Y Y
80 All additional info transfer Y Y Y Y
services
81 UUS1 user to user Y Y Y Y
signalling
82 UUS2 user-to-user Y Y
signalling
83 UUS3 user-to-user Y Y
signalling
90 All call barring Y Y Y Y
91 All Barring of outgoing Call Y Y Y Y
Services
92 Barring of all outgoing calls Y Y Y Y
93 Barring of all outgoing Y Y Y Y
international calls
94 Barring of all OG Y Y Y Y
V36.4 Page 305 of 317


and 98 4, 5, 6, 7, 8,
Release 96 9, 10, 11
TS 09.02 TS 09.02 TS 09.02 TS 29.002
[43] [43] [43] [44]
international except HPMN
99 All Barring of incoming Call Y Y Y Y
Services
9A Barring of all incoming calls Y Y Y Y
9B Barring of all IC calls when Y Y Y Y
outside HPMN
FF USSD Message Y Y Y Y
Table 54: 3GPP Releases and Supplementary Service Codes
Annex D Document Management
D.1 Document History

Approval Editor /
Version Date Brief Description of Change
Authority Company
3.00.00 24 Apr TAP 3.1 Major Release
1999 Version update from GSM
Association approval.
Document is approved as
baseline for
Specification Version Number 3
Release Version Number 1
3.01.00 04 Aug Incorporation of CR008; inclusion
1999 of essential corrections.
3.02.00 15 Sep Incorporation of CRs 009, 010,
1999 011, 012, 013.
3.03.00 26 Oct Incorporation of CRs 014, 015.
1999
3.04.00 05 Jan Incorporation of CRs 016, 017,
2000 018, 019, 020, 021, 022, 023.
3.05.00 01 May Incorporation of CRs 024, 026-
2000 027, 029-033, 035-041.
3.05.01 22 May Incorporation of CR 043.
2000
3.05.02 07 Aug Incorporation of CR 048.
2000
3.06.00 08 May TAP 3.2 Major Release
2000 Version update from GSM
baseline for
Incorporation of CRs 025, 028,
034, 042.
3.06.01 07 August Incorporation of CRs 044 – 057.
2000
3.06.02 18 Dec Incorporation of CR 084.
2000
V36.4 Page 306 of 317

Approval Editor /
Authority Company
3.07.00 16 Oct 01 May 2001: TAP 3.3 Major
2000 Release
Version update from GSM
baseline for
Incorporation of CRs 058 – 069,
073.
3.07.01 09 Mar Incorporation of CRs 075, 079 –
2001 080, 082, 084 – 085, 088, 090 –
093.
3.08.00 16 Oct 01 November 2001: TAP 3.4
2000 Major Release
baseline for
Incorporation of CRs 070 – 072.
3.08.01 09 Mar Incorporation of CRs 074, 076 –
2001 078, 086 – 087, 089.
3.08.02 17 Jul 2001 Incorporation of CRs 095, 096,
099 – 104, 106 – 108
3.09.00 30 Nov 01 May 2002: TAP 3.09 Major
2001 Release
baseline for
(note release versions 5-8
skipped)
113 – 124, 126 – 130
3.10.00 14 Jun 01 May 2003: TAP 3.10 Major
2002 Release
baseline for major changes for
109, 112, 125, 131 – 167
3.10.01 20 Nov Version update from GSM
2002 Association approval.
baseline for the final definition of
Incorporation of CRs 168 – 197
3.11.00 29 May 01 May 2005: TAP 3.11 Major
2003 Release
V36.4 Page 307 of 317

Approval Editor /
Authority Company
206 – 225
3.11.01 21 Jun Version update from GSM
Document is approved as final
229, 231, 232, 234 – 241, 244 –
247, 249 – 278
3.11.02 17 Dec Version update from GSM
baseline for the definition of
3.11.03 26 May Version update from GSM
and 307
3.11.04 18 Oct Version update from GSM
Incorporation of CRs 308, 310 –
313, 317 – 320
331
3.11.06 01 Dec Version update from GSM
344 – 345
V36.4 Page 308 of 317

Approval Editor /
Authority Company
3.11.07 12 Feb Version update from GSM
Incorporation of CR 347
Incorporation of CRs 348, 350 –
354
3.11.09 11 Oct Incorporation of CR 355
2007
3.11.10 25 Oct 01 May 2008: TAP 3.11 Minor
2007 Release
Definition of TAP3.11.10, Minor
Release, 1 May 2008.
Incorporation of CRs 362 – 363.
3.11.11 22 May Incorporation of CRs 364 – 370.
2008
3.11.12 22 Dec Incorporation of CRs 371 – 378. TADIG #66 (e-vote) Peter
2008 Chapman /
Vodafone
3.11.13 04 Jun CR381 – TADIG doc 67_035 – TADIG #67 Peter
2009 Total Commission error Chapman /
correction. Vodafone
CR382 – TADIG doc 67_036rev1
– Timestamp range clarification.
CR384 – TADIG doc 67_038 –
Error correction to SS Code
conditionality.
CR386 – TADIG doc 67_040 –
Call Event Start Timestamp
clarification.
3.11.14 26 Nov CR387 – TADIG doc 68_021 – TADIG #68 Peter
2009 Clarify TAP currency Chapman /
CR388 – TADIG doc 68_022 – Vodafone
Clarification on GPRS partial
example
CR389 – TADIG doc 68_023 –
Clarification on timestamp formats
CR390 – TADIG doc 68_024 –
Clarification on ASN.1 binary
encoding rules
CR391 – TADIG doc 68_025 –
Error correction to Tax Value
tolerance
CR392 – TADIG doc 68_026 –
Clarification on CAMEL Default
Call Handling Indicator
conditionality
CR393 – TADIG doc 68_027 –
Editorial change re maintaining
V36.4 Page 309 of 317

Approval Editor /
Authority Company
location information
CR394 – TADIG doc 68_028 –
Clarification on validation of old
call records in roaming hubbing
scenarios
CR395 – TADIG doc 68_029 –
Clarification on tolerance on non
IMF currency exchange rates
CR396 – TADIG doc 68_030 –
Validation of Serving BID with
alias TADIG Codes in roaming
hubbing
28.00 31 Dec 01 May 2010: TAP 3.11 Minor Peter
2009 Release Chapman /
MCR399 – TADIG doc 68_096 – TADIG #68 Vodafone
Definition of minor TAP3 release EMC #79
for 01 May 2010
mCR 379 – TADIG doc 66_052 – TADIG #66
Rejection of CAMEL MOCs with
CAMEL Routing Number in Called
Number TADIG #66
mCR 380 – TADIG doc 66_053 –
File Available Timestamp TADIG #68
tolerance added
mCR 397 – TADIG doc TADIG #68
68_031rev1 – New validation rule
for Local Currency
mCR 398 – TADIG doc
68_032rev1 – Support of
LTE/SAE bit pipe accounting
model
mCR 400 – TADIG doc 69_004 – TADIG e-vote 03-17
tolerance on exchange rates for Dec 09
IMF currencies
28.1 08 Feb mCR 401 – TADIG doc 69_005 – TADIG e-vote 12-25 Peter
2010 Error Correction to Recording Jan 10 Chapman /
Entity Code validation Vodafone
28.2 28 May mCR 402 – TADIG doc 69_013 – TADIG #69 Peter
2010 clarification to tolerance on Chapman /
exchange rates for IMF currencies Vodafone
mCR 403 – TADIG doc 69_014 –
clarification to tolerance on
exchange rates for non IMF
currencies
mCR 404 – TADIG doc 69_015 –
editorial change to remove
redundant validation on Serving
Network
28.3 16 Dec mCR 406 – TADIG doc 70_013 – TADIG #70 Peter
2010 Clarification on Called Number Chapman /
mCR 407 – TADIG doc 70_014 – Vodafone
Clarification on Dialled Digits
mCR 408 – TADIG doc 70_015 –
Clarification on Recording Entity
Identification values
29.0 21 Jan 01 May 2011: TAP 3.11 Minor Peter
V36.4 Page 310 of 317

Approval Editor /
Authority Company
mCR 405 – TADIG doc 69_016 – TADIG #69 Vodafone
Improved validation on
Teleservice Code
MCR 409 – TADIG doc 70_016 – TADIG #70
Validation change for zero rated EMC Email
MTCs Approval
29.1 07 Mar Correction of editorial errors in N/A Peter
2011 data dictionary Cause for Chapman /
Termination and Charge Type, Vodafone
plus other formatting corrections.
29.2 15 Apr Correction of ASN.1 syntax N/A Peter
2011 definition errors introduced by Chapman /
automatic Word correction. Vodafone
29.3 02 Jun mCR 411 – Clarification on Fatal TADIG #71 Peter
2011 error 53. Chapman /
mCR 413 – Supplementary Vodafone
Service Code additions.
30.0 30 Jun 01 May 2012: TAP 3.12 Major TADIG #71 Peter
2011 Release EMC #94 Chapman /
mCR 414 – TADIG doc 71_058 – Vodafone
Remove mandatory marking from
Equipment Identifier within ASN.1
for SSE.
mCR 415 – TADIG doc 71_059 –
Exchange Rate greater than
expected.
mCR 416 – TADIG doc 71_060 –
Introduction of Call Type Levels to
MTCs.
mCR 417 – TADIG doc 71_061 –
Support for Voice and SMS over
LTE (VoLTE).
mCR 418 – TADIG doc 71_071 –
Adapt MSISDN physical
representation to the one given by
3GPP.
MCR 419 – TADIG doc 71_085 –
Definition of Major TAP3 release
01 May 2012.
30.1 28 Dec mCR 420 – TADIG doc 72_004 – TADIG e-vote Peter
2011 new UTC time offset Chapman /
clarification note for exchange
rate higher than expected
default Call Type Level 3 values
mCR 423 – TADIG doc TADIG e-vote
72_038rev1 – inclusion of call
destination number into IOT
check
72_039rev1 – error corrections re
VoLTE
exclude SMS MT from call type
level validation
V36.4 Page 311 of 317

Approval Editor /
Authority Company
transfer cut off timestamp warning
error corrected to fatal
IP address format clarification
updated 3GPP references for
release 10
72_044rev1 – SS action codes
error correction
introduction of IMS Charging
Identifier (Event Reference) on
TAP
validation change to Network
Information catering for Content
Transactions
mCR 432 – TADIG doc 73_004 – TADIG e-vote
adition of derivation for Cell Id in
LTE
30.2 15 Mar Editorial change adding missing Peter
2012 validation contexts MSESS & Chapman /
MSG to Serving BID/Location Vodafone
Description/Network elements.
mCR433 – TADIG doc 73_009 – TADIG e-vote
Call Type Levels validation
30.3 31 May mCR 434 – TADIG doc 73_020 – TADIG #73 Peter
2012 clarification on duplicate call Chapman /
validation. Vodafone
mCR 435 – TADIG doc 73_021 –
clarification on GPRS before
launch regarding LTE.
mCR 436 – TADIG doc 73_022 –
clarification regarding Recording
Entity Types.
mCR 437 – TADIG doc 73_023 –
error correction on Network
Element.
mCR 438 – TADIG doc 73_024 –
error correction regarding
maximum TAP file size.
mCR 439 – TADIG doc 73_025 –
ignore leading zeroes for Call
Reference in duplicate call check.
mCR 440 – TADIG doc 73_026 –
add validation rules to integer
fields which should not be
negative.
mCR 441 – TADIG doc 73_027 –
clarification to error 201 on File
Sequence Number.
mCR 442 – TADIG doc 73_043 –
changes to duplicate check
validation description related to
MSESS.
mCR 443 – TADIG doc 73_076 –
V36.4 Page 312 of 317

Approval Editor /
Authority Company
clarification on Call Type Level 1.
mCR 444 – TADIG doc 73_079 –
Call Type Level 1 validation rule
exception.
30.4 22 Nov mCR 445 – TADIG doc 74_018 – TADIG #74 Peter
2012 Clarification on usage of Non Chapman /
Cahrged Party for duplicate call Vodafone
check in Mobile Session.
mCR 446 – TADIG doc 74_019 –
Consistency in 3GPP references.
mCR 447 – TADIG doc 74_020 –
Validation on Partial Type
Indicator.
mCR 448 – TADIG doc 74_021 –
Clarification on validation of
Exchange Rate.
mCR 449 – TADIG doc 74_022 –
Population of the TEL URI in the
Non Charged Party Number.
mCR 450 – TADIG doc 74_023 –
Clarifications on Ipv6 population.
mCR 451 – TADIG doc 74_045 –
Clarification on the derivation of
User Location Information in LTE.
mCR 452 – TADIG doc 74_046 –
Correcting the derivation of the
Call Reference for SMS over CS.
31.0 10 Dec 01 May 2013: TAP 3.12 Minor Peter
2012 Release (see also v32.0) Chapman /
WiFi related changes.
mCR 1001 – Clarification of TADIG e-vote
Charge validation procedure.
31.0 04 Mar Editorial removal of duplicate TDS #49 Peter
2013 Data Dictionary entries (H). Chapman /
Vodafone
31.1 22 Mar mCR 1002 – addition of TADIG e-vote Jenny Chong /
2013 Chargeable Subscriber as GPRS GSMA
Call duplicate check parameter
31.2 23 May mCR 1003 – TADIG doc 75_010 TADIG #75 Peter
2013 – validation clarifications Chapman /
mCR 1004 – TADIG doc 75_011 Vodafone
– correction for Serving Location
Description in WiFi case
mCR 1005 – TADIG doc 75_012
– correction on SS Used
description
– correction on Network Access
Identifier validation
32.0 03 Oct 01 May 2013: TAP 3.12 Minor Peter
2013 Release (correction, see also Chapman /
v31.0) Vodafone
mCR 1007 – clarification that VT TADIG e-vote
calls cannot be rejected prior to
commercial launch
MCR 1011 – Add requested TADIG e-vote
V36.4 Page 313 of 317

Approval Editor /
Authority Company
destination to Mobile Session
(Note: extra ASN.1 group entry
added within MobileSession –
missing from original CR)
32.1 05 Dec mCR 1008 – TADIG doc TADIG #76 Peter
2013 76_009rev1 – Add SS to severe Chapman /
error 142 Vodafone
76_010rev1 – Remove GPRS
context from severe 101 on Call
Event Start Timestamp
76_011rev1 – EUInternet APN
validation
– Call Reference in duplicate call
validation
76_013rev1 – Calirify Non-
Charged Party Number content
for SMS usage
– Support two TAP versions on
public interface
76_029rev1 – new section
Migration To A New Release –
from TD.34
– removal of incorrect validation
rule – GPRS Network Location
– Commercial launch date
clarification
32.1 05 Dec Insert missing Data Dictionary text Editorial change Peter
2013 for mCR 1010 – TADIG doc Chapman /
76_011rev1 – EUInternet APN Vodafone
validation.
32.2 02 Jun mCR1018 – TADIG doc 77_023 – TADIG #77 Peter

2014 Charge validation clarifications Chapman /
mCR1021 – TADIG doc 77_025 – Vodafone
Clarification on usage of Call
Reference in duplicate call check
mCR1022 – TADIG doc 77_015 –
Extension of duplicate call check
criteria for GPRS Wi-Fi case
mCR1023 – TADIG doc 77_022 –
Addition of two new Recording
Entity Types, TRF and ATCF
32.3 15 Sep mCR1025 – Call Type Level 2 TADIG e-vote Peter
2014 clarification regarding premium Chapman /
rate defining body. Vodafone
mCR1027 – Bilaterally agreed
error codes clarification.
32.4 14 Jan mCR1026 - TADIG doc 78_042 - TADIG #78 Peter
2015 Add validation error for missing Chapman /
V36.4 Page 314 of 317

Approval Editor /
Authority Company
IMSI (or MIN) Vodafone
mCR1028 - TADIG doc 78_010 -
Provision of TAP events on
VoLTE handover scenarios
mCR1029 - TADIG doc 78_012 -
Removing the Recording Entity
Type in error code 255
mCR1030 - TADIG doc 78_018 -
Add clarification note to error 34
of Charge Information group
32.5 04 Mar CR1033 - Clarification on Charge IDS e-vote Peter
2015 Information regarding Sender’s Chapman /
IOT Vodafone
CR1034 - Validation of value ‘EU
Internet’ in APN
32.6 04 Jun CR1036 - editorial correction to IDS #79 Peter
2015 validation context for Chargeable Chapman /
Subscriber Vodafone
CR1037 - align section 1 with
GSMA template structure
CR1039 - no CAMEL record
rejection as long as CAMEL
Invocation Fee zero
33.0 04 Jun 01 November 2015: TAP 3.12 Peter
2015 Minor Release Chapman /
CR1035 - add QCI values to Call IDS #79 Vodafone
Type Level 2
33.1 30 Jul 2015 CR1042 - Provision of TAP IDS e-vote Peter
Events for voice and SMS Chapman /
messaging scenarios Vodafone
CR1043 - Allow inclusion of
access charge into first interval
33.2 18 Nov CR1044 - Modify error 200 on IDS #80 Peter
2015 Charge to cover total invoiceable Chapman /
charge Vodafone
CR1048 - Allow VoLTE
emergency call use of Call Type
Level 2 value 3
CR1049 - Clarification of S-
GW/SGSN usage in TAP
CR1050 - Clarify validation 20 on
Called Number for shared country
codes
CR1051 - Addition of firther QCI
values to Call Type Level 2
34.0 18 Nov 01 May 2016: TAP 3.12 Minor IDS #80 Peter
CR1047 - GSMA Exchange Rate Vodafone
System
34.0 14 Apr Editorial correction: Annex B text n/a Peter

2016 “Call Type Level ½/3” corrected to Chapman /
1/2/3 Services
34.1 25 May CR1052 - Clarification on IDS #81 Peter
2016 population of taxes related to Chapman /
charge types Vodafone
CR1053 - Clarification on spare
V36.4 Page 315 of 317

Approval Editor /
Authority Company
and reserved ITU country codes
CR1054 - Clarification on the
importance of CAMEL Destination
Number
CR1055 - Provision of TAP
Events on S8HR scenarios
CR1056 - Clarification of
exchange rate tolerance after
GSER launch
CR1057 - Clarify that Known
Issues must be taken into account
35.0 25 May 01 November 2016: TAP 3.12 IDS #81 Peter
2016 Minor Release Chapman /
CR1059 - Add new CTL2 values Vodafone
for new QCI values
35.1 08 Dec CR1060 – clarification that CTL2 IDS #82 Peter
2016 values 20-29 allowed Chapman /
indepenedent of IOT. Vodafone
CR1061 – correction on eSRVCC
and removal of scenario ‘3 voice
calls’.
36.0 08 Dec 01 July 2017: TAP 3.12 Minor IDS #82 Peter
CR1062 – Definition of new Vodafone
36.0 12 Jan Editorial Update: added Editorial Shamit Bhat/
2016 rapFileSequenceNumber to GSMA
AggregatedUsageRecord physical
structure
36.1 07 Apr CR1064 - Syntax error correction IDS e-vote Peter
2017 Chapman /
Vodafone
36.2 18 May CR1065 – AUR age validation IDS #83 Peter
2017 change Chapman /
Vodafone
36.2 21 Jun Editorial: changed reference to Editorial Shamit Bhat/
2017 section 5.8 to 5.9 in charge GSMA
element definition
36.3 30 Nov CR1066 – Clarification on IDS #84 Peter
2017 AccountingSessionId usage in Chapman /
GPRS Call duplicate check Vodafone
36.4 16 May TD.57 CR1067 TAP 3.12 Format IDS #87 Randall
2019 Specification Peterson/
Union
Wireless
36.5 23 Dec TD.57 CR1068 TAP 3.12 Format IDS #88 Randall
2019 Specification Peterson/
Union
Wireless
D.2 Other Information

Type Description
Document Owner IDS
Editor / Company Randall Peterson / Union Wireless
V36.4 Page 316 of 317

It is our intention to provide a quality product for your use. If you find any errors or omissions,
please contact us with your comments. You may notify us at [email protected]
Your comments or suggestions & questions are always welcome.
V36.4 Page 317 of 317

TD.57 v36.5 - TAP Format Specs

Uploaded by

Copyright:

Available Formats

TD.57 v36.5 - TAP Format Specs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TD.57 v36.5 - TAP Format Specs

Uploaded by

Copyright:

Available Formats

What is the scope of the document?

What is the scope of the document?

What logical structures are used to organize the data?

What logical structures are used to organize the data?

GSM Association Confidential - Full, Rapporteur, Associate and Affiliate Members

Official Document TD.57 - TAP 3.12 Format Specification

TAP 3.12 Format Specification

This is a Binding Permanent Reference Document of the GSMA

Security Classification: Confidential - Full, Rapporteur, Associate and Affiliate

V36.4 Page 1 of 317

V36.4 Page 2 of 317

3.18 Supplementary Service Event 29

V36.4 Page 3 of 317

5.6 Text Representation of IP Addresses 244

V36.4 Page 4 of 317

The transfer mechanism for TAP files is discussed in TD.28 [32].

The primary commercial requirement for data to be transferred is defined in permanent

V36.4 Page 5 of 317

PMN Public Mobile Network

V36.4 Page 6 of 317

codes for groups of countries

2 Differences from the Commercial Requirement

These differences are due to a number of factors including implementation considerations.

2.1 Transfer Frequency

2.2 File Creation Timestamp

V36.4 Page 7 of 317

2.3 File Available Timestamp

2.4 Version Control

2.5 Reference Tables

The codes are used within the calls/events as required.

2.6 Supplementary Services

2.7 Location Information

V36.4 Page 8 of 317

2.8 Dates and Times

2.9 File Size Limitations

2.10 Support for Interstandard Number Portability

2.11 Calculated Exchange Rate for Currencies Not Published by GSER

2.12 Exchange Rate for Currencies Published by GSER

2.13 Exchange Rate higher than expected

V36.4 Page 9 of 317

2.14 Partial Type Indicator

2.15 TAP Versions Supported

The BA.12 [12] conversion requirements remain unaffected.

2.16 Aggregated Usage Record Date(s)

2.17 Aggregated Usage Record Implementation Date

V36.4 Page 10 of 317

'C' indicates that the Dash (green) lined

'R' indicates that the

'O' indicates that the

Figure 1: Conventions used within Logical Structure Diagrams

Mandatory Must be present.

V36.4 Page 11 of 317

3.1 Data Interchange

File RAP File Operator

File File Transfer Cut Specification Release

UTC Time UTC Time UTC Time

Figure 2: Data Interchange Logical Structure

Group Element Name Also Occurs In Detail Shown In

Table 1: Data Interchange Element Cross References