Transferred Account Procedure Data Record Format Specification Version Number 3 01 June 2006

Transferred Account Procedure Data Record Format Specification Version Number 3 01 June 06 This is a binding permanent reference document. Security lassification ategory* (see next page) Restricted embers X Restricted Associate embers X 3.11.05 Page 1 of 217

Restricted Information Access to and distribution of this document is restricted to the persons listed under the heading Security lassification ategory. 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 listed under Security lassification ategory without the prior written approval of the Association. The GS 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. opyright Notice opyright 05 GS Association GS and the GS Logo are registered and the property of the GS Association. Document History Version Date Brief Description 3.00.00 24 April 1999 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number 1 3.01.00 04 August 1999 Incorporation of R008; inclusion of essential corrections. 3.02.00 15 September 1999 Incorporation of Rs 009, 0, 011, 012, 013. 3.03.00 26 October 1999 Incorporation of Rs 014, 015. 3.04.00 05 January 00 Incorporation of Rs 016, 017, 018, 019, 0, 021, 022, 023. 3.05.00 01 ay 00 Incorporation of Rs 024, 026-027, 029-033, 035-041. 3.05.01 22 ay 00 Incorporation of R 043. 3.05.02 07 August 00 Incorporation of R 048. 3.06.00 08 ay 00 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number 2 Incorporation of Rs 025, 028, 034, 042. 3.06.01 07 August 00 Incorporation of Rs 044 057. 3.06.02 18 December Incorporation of R 084. 3.07.00 16 October 00 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number 3 Incorporation of Rs 058 069, 073. 3.07.01 09 arch 01 Incorporation of Rs 075, 079 080, 082, 084 085, 088, 090 093. 3.08.00 16 October 00 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number 4 Incorporation of Rs 070 072. 3.08.01 09 arch 01 Incorporation of Rs 074, 076 078, 086 087, 089. 3.08.02 17 July 01 Incorporation of Rs 095, 096, 099 4, 6 8 3.09.00 30 November 01 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number 9 (note release versions 5-8 skipped) Incorporation of Rs 1, 111, 113 124, 126 130 3..00 14 June 02 Version update from GS Association approval. Document is approved as baseline for major changes for Specification Version Number 3 3.11.05 Page 2 of 217

Release Version Number Incorporation of Rs 094, 097, 9, 112, 125, 131 167 3..01 November 02 Version update from GS Association approval. Document is approved as baseline for the final definition of Specification Version Number 3 Release Version Number Incorporation of Rs 168 197 3.11.00 29 ay 03 Version update from GS Association approval. Document is approved as baseline for major changes for Specification Version Number 3 Release Version Number 11 Incorporation of Rs 198 4, 6 225 3.11.01 21 June 04 Version update from GS Association approval. Document is approved as final baseline for major changes for Specification Version Number 3 Release Version Number 11 Incorporation of Rs 226, 227, 229, 231, 232, 234 241, 244 247, 249 278 3.11.02 17 December 04 Version update from GS Association approval. Document is approved as baseline for the definition of Specification Version Number 3 Release Version Number 11 Incorporation of Rs 279 295 3.11.03 26 ay 05 Version update from GS Association approval. Document is approved as baseline for the definition of Specification Version Number 3 Release Version Number 11 Incorporation of Rs 296 301 and 307 3.11.04 18 October 05 Version update from GS Association approval. Document is approved as baseline for the definition of Specification Version Number 3 Release Version Number 11 Incorporation of Rs 308, 3 313, 317 3 3.11.05 01 June 06 Version update from GS Association approval. Document is approved as baseline for the definition of Specification Version Number 3 Release Version Number 11 Incorporation of Rs 324 329, 331 hanges Since Last Version q 324 orrection of APN derivation for AEL usage. q 325 larification of text representation of IP addresses. q 326 larification of relationship between Exchange Rate and TAP urrency. q 327 larification of taxes in ontent Transaction Advised harge. q 328 larification on Total harge Refund. q 329 Removal of incorrect backward compatibility statement. q 331 Removal of reserved value local from all Type 3. 3.11.05 Page 3 of 217

TABLE OF ONTENTS 1. Introduction... 6 1.1. Scope of the Document... 6 1.2. Terminology... 6 1.3. Structure of the Document... 6 1.4. Document ross References... 7 2. Differences from the ommercial Requirement... 9 2.1. Transfer Frequency... 9 2.2. File reation Timestamp... 9 2.3. File Available Timestamp... 9 2.4. Version ontrol... 9 2.5. Reference Tables... 9 2.6. Supplementary Services... 2.7. ell Identification... 2.8. Dates and Times... 2.9. File Size Limitations... 2.. Support For Interstandard Number Portability... 3. Logical Structure... 11 3.1 Data Interchange... 12 3.2 Transfer Batch... 13 3.3 Batch ontrol Information... 14 3.4 Accounting Information... 15 3.5 Network Information... 16 3.6 obile Originated all... 17 3.7 O Basic all Information... 18 3.8 Location Information... 19 3.9 Basic Service Used... 3. harge Information... 21 3.11 AEL Service Used... 22 3.12 obile Terminated all... 23 3.13 T Basic all Information... 24 3.14 Supplementary Service Event... 25 3.15 Supplementary Service Used... 26 3.16 Service entre Usage... 27 3.17 all... 28 3.18 Basic all Information... 29 3.19 Service Used... 30 3. ontent Transaction... 31 3.21 ontent Transaction Basic Info... 32 3.22 harged Party Information... 33 3.23 ontent Service Used... 34 3.24 Advised harge Information... 35 3.25 Location Service... 36 3.26 Tracking ustomer Information... 37 3.27 Tracked ustomer Information... 38 3.28 Location Service Usage... 39 3.29 Audit ontrol Information... 40 4 Data Dictionary... 41 5 lassification of Errors...173 5.1 Validation rules not described in the Data Dictionary...176 5.2 Text Representation of IP Addresses...178 6 Physical Structure...179 6.1 Abstract Syntax...179 6.2 Transfer Syntax...7 6.3 File Naming onventions...7 6.3.1 hargeable TAP Data...7 6.3.2 Test TAP Data...7 ANNEX A: Supplementary Services...8 3.11.05 Page 4 of 217

ANNEX B: hanges from Previous Specification Version Number...211 3.11.05 Page 5 of 217

1. INTRODUTION 1.1. Scope of the Document This document defines the logical and physical data that must be transferred between PNs under the Transferred Account Procedure (TAP). The version of TAP supported by this document is Specification Version Number 3, Release Version Number11. The implementation timetable for this version of TAP is such that all TAP files created on or after 1 st ay 05 must conform to this standard (see TD.34 for further information on implementation of new TAP standards). The transfer medium is beyond the scope. The primary commercial requirement for data to be transferred is defined in permanent reference document BA.12. 1.2. Terminology 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 is considered the prime input document in terms of the commercial requirement and items are named accordingly. The other major input documents are 3GPP TS 32.005, which defines the data to be made available at the switch (S), and 3GPP TS 32.015, which defines charging data available. 1.3. Structure of the Document The document is divided into several sections, the purpose of each being as follows. Section 1: Introduction Section 2: It places the document in context and explains the purpose of each section of the document. Differences from the ommercial Requirement Identifies the differences between the original commercial requirement and the implementation delivered. Section 3: Logical Structure The section contains diagrams of the logical structure of the TAP interface. Section 4: Data Dictionary Section 5: The Data Dictionary identifies each item and describes it in detail. Included are rules on optionality, conditionality and validation (including error codes. The item derivations are also included. lassification of Errors Gives further information regarding the error severity levels. Also gives details of other general validation check, e.g. duplicates. Section 6: Physical Format Annex A: This section gives the encoding rules and physical definition of the TAP file. Supplementary Services 3.11.05 Page 6 of 217

Annex B: The section details the supplementary service events which may be present on the TAP interface and the context in which they should be delivered. hanges From Previous Specification Version Number This section highlights the requirements for changes made, the originator of that requirement and the Release Version when it is supported. 1.4. Document ross References 3GPP TS 23.032 3GPP TS 23.060 3GPP TS 24.008 3GPP TS 32.005 3GPP TS 32.015 3GPP TS 32.5 Universal Geographical Area Description General Packet Radio Service () Service description; Stage 2 obile radio interface Layer 3 specification ; ore network protocols ; Stage 3 3G all And Event Data For The S Domain GS all Event Data for the Packet Switched (PS) domain Telecommunication management ; harging management ;harging data description for the ircuit Switched (S) domain 3GPP TS 32.215 3GPP TS 44.008 3GPP TS 49.031 IBER anual v2.0 GS Association PRD BA.08 v3.18.01 Telecommunication managment ; harging management ;harging data description for the Packet Switched (PS) domain obile radio interface layer 3 specification Location Services (LS);Base Station System Application Part LS Extension (BSSAP-LE) Treatment of old data - Transferred Account Procedure and Bulk SS Data GS Association PRD BA.11 v3.09.01 GS Association PRD BA.12 v24.01 GS Association PRD BA.27 v25.0 GS Association PRD TD.13 v4.0 GS Association PRD TD.34 v3.02.01 IETF RF 1883 IETF RF 2373 IETF RF 2865 IETF RF 2866 Billing and Accounting Information - Treatment of Exchange rates Transferred Account Procedure and Billing Information harging and Accounting Principles TADIG ode Naming onventions (GS Infocentre database) TAP Release anagement Process Internet Protocol Version 6 - Specification IP Version 6 - Addressing Architecture Remote Authentication Dial In User Service RADIUS Accounting 3.11.05 Page 7 of 217

IETF RF 2869 IETF RF 791 ISO 3166-1 ISO 4217 ISO 646 ITU E.164 ITU-T Q.701 3GPP TS 22.002 3GPP TS 22.003 3GPP TS 22.004 3GPP TS 22.030 3GPP TS 23.003 3GPP TS 29.002 RADIUS Extensions DARPA Internet Program - Protocol Specification (for IPv4) odes for the representation of names of countries and their sudivisions odes for the representation of currencies and funds Information Processing - ISO 7-bit coded character set for information interchange Principles, criteria and procedures for the assignment and reclamation of E.164 country codes and associated identification codes for groups of countries Functional description of the message transfer part (TP) of Signalling System No.7 Bearer Services supported by a GS PN Teleservices supported by a GS PN General on Supplementary Services an achine Interface Numbering, Addressing and Identification obile Application Part Specification 3.11.05 Page 8 of 217

2. DIFFERENES FRO THE OERIAL REQUIREENT The TADIG 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 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, 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, or errors can be raised by the Recipient in this case. 2.2. File reation Timestamp The date and time of the file creation is included. 2.3. File Available Timestamp Due to constraints in the physical file transfer environment where PNs push data to HPNs it is not possible to identify the actual date and time when the file is fully available on the HPN 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 PNs concerned. 2.4. Version ontrol The TAP Specification Version and Release Version numbers are included in order to allow HPNs 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: essage 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. urrency onversion; each table row comprises a code with its exchange rate and an indication of how many decimal places are represented. UT 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, e.g. S, and entity identifier. The codes are used within the calls/events as required. 3.11.05 Page 9 of 217

2.6. Supplementary Services Unlike 3GPP TS 32.005, GS Association PRD BA.12 has no concept of events. BA.12 assumes that supplementary services, when not used in conjunction with a call e.g. 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 e.g. the number involved in call forward activation. These non call related Supplementary Services are treated as separate events within the TAP. 2.7. ell Identification The ell Id. Has been added. 2.8. Dates and Times All date/time items cater for illennium compliance and have the format YYDDHHSS. All timestamps are provided in the sending PN s local time further qualified by an offset from Universal (UT) Time. This enables the HPN to easily calculate its (HPN) 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.. Support For Interstandard Number Portability Inclusion of elements ESN (Electronic Serial Number), IN (obile IdentificationNumber) and DN (obile Directory Number) are required to support mobile number portability within markets supporting various technology standards, e.g. USA. 3.11.05 Page of 217

3. LOGIAL STRUTURE The following conventions have been used in the Logical Structure diagrams: '' indicates that the element is conditional; the conditionality rules are described in the Data Dictionary entry for the element Element A 0 Dash (green) lined boxes indicate group elements Element B 1 R Element 1 O Element D 1 R 'R' indicates that the element occurs one or more times. If the element is '' or 'O' then it may occur zero or more times O Element E 2 O Element F 2 Element G 2 Element H 2 Solid (black) lined boxes indicate item elements 'o' indicates that only one of the elements grouped at this level is applicable 'O' indicates that the element is optional; the optionality rules are described in the Data Dictionary entry for the element '' indicates that the element is mandatory 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: andatory: ust be present. onditional: 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 (e.g. from the network). Optional: Does not need to be present. Inclusion/exclusion of optional elements is at the discretion of the Sender PN, no specific agreements need to be in place to allow the PN 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. 3.11.05 Page 11 of 217

3.1 Data Interchange Data Interchange o Transfer Batch o Notification Sender Recipient File Sequence Number RAP File Sequence Number File Type Indicator Operator Specific Information O R File reation Timestamp O File Available Timestamp Transfer ut Off Timestamp Specification Version Number UT Time Offset UT Time Offset UT Time Offset Release Version Number Figure 3.1 Data Interchange Logical Structure Group Element Name Also Occurs In Detail Shown In Data Interchange Transfer Batch Figure 3.2 Notification 3.11.05 Page 12 of 217

3.2 Transfer Batch Transfer Batch Batch ontrol Information Accounting Information Network Information essage Description Information R all Event Details R Audit ontrol Information essage Description ode essage Description obile O Originated all obile O Terminated all O Supplementary Service Event Service O entre Usage O all O ontent Transaction O Location Service Figure 3.2 Transfer Batch Logical Structure Group Element Name Also Occurs In Detail Shown In Transfer Batch Figure 3.1 Batch ontrol Information Figure 3.3 Accounting Information Figure 3.4 Network Information Figure 3.5 essage Description Information all Event Details obile Originated all Figure 3.6 obile Terminated all Figure 3.12 Supplementary Service Event Figure 3.14 Service entre Usage Figure 3.16 all Figure 3.17 ontent Transaction Figure 3. Location Service Figure 3.25 Audit ontrol Information Figure 3.29 3.11.05 Page 13 of 217

3.3 Batch ontrol Information Batch ontrol Information Sender Recipient Specification Version Number File Type Indicator RAP File Sequence Number Operator Specific Information O R File Sequence Number File reation Timestamp O Transfer ut Off Timestamp File Available Timestamp Release Version Number UT Time Offset UT Time Offset UT Time Offset Figure 3.3 Batch ontrol Information Logical Structure Group Element Name Also Occurs In Detail Shown In Batch ontrol Information Figure 3.2 3.11.05 Page 14 of 217

3.4 Accounting Information Accounting Information Taxation R Discounting R Local urrency TAP urrency O urrency onversion R TAP Decimal Places Tax Rate ode Tax Type Tax Rate harge Type Discount ode Discount Applied Exchange Rate ode Number Of Decimal Places Exchange Rate Fixed O Discount Value O Discount Rate Figure 3.4 Accounting Information Logical Structure Group Element Name Also Occurs In Detail Shown In Accounting Information Figure 3.2 Taxation Discounting Discount Applied urrency onversion 3.11.05 Page 15 of 217

3.5 Network Information Network Information UT Time Offset Information R Recording Entity Information R UT Time Offset ode UT Time Offset Recording Entity ode Recording Entity Type Recording Entity Identification Figure 3.5 Network Information Logical Structure Group Element Name Also Occurs In Detail Shown In Network Information Figure 3.2 UT Time Offset Information Recording Entity Information 3.11.05 Page 16 of 217

3.6 obile Originated all obile Originated all O Basic all Information Location Information Equipment Identifier Basic Service Used Supplementary Service ode Third Party Information AEL Service Used Operator Specific Information O R IEI O ESN O Third Party Number LIR Status Indicator Figure 3.6 obile Originated all Logical Structure Group Element Name Also Occurs In Detail Shown In obile Originated all Figure 3.2 O Basic all Information Figure 3.7 Location Information Figure 3.12, Figure 3.14 Equipment Identifier Figure 3.12, Figure 3.14, Figure 3.17 Figure 3.8 Basic Service Used Figure 3.12 Figure 3.9 Third Party Information AEL Service Used Figure 3.12, Figure 3.17 Figure 3.11 3.11.05 Page 17 of 217

3.7 O Basic all Information O Basic all Information hargeable Subscriber RAP File Sequence Number Destination Network all Event Start Timestamp Total all Event Duration SI Toolkit Indicator ause For Termination ISI O IN O UT Time Offset ode SISDN DN Destination alled Number Dialled Digits alled Place alled Region SS Destination Number Figure 3.7 O Basic all Information Logical Structure Group Element Name Also Occurs In Detail Shown In O Basic all Information Figure 3.6 hargeable Subscriber Figure 3.13, Figure 3.14, Figure 3.18 Destination 3.11.05 Page 18 of 217

3.8 Location Information Location Information Network Location Home Location Information O Geographical Location Recording Entity ode all Reference Location Area ode ell Identity O Home BID Home Location Description Serving Network Serving BID O Serving Location Description O Figure 3.8 Location Information Logical Structure Group Element Name Also Occurs In Detail Shown In Location Information Figure 3.6, Figure 3.12, Figure 3.14 Network Location Home Location Information Figure 3.17 Geographical Location Figure 3.17 3.11.05 Page 19 of 217

3.9 Basic Service Used Basic Service Used Basic Service harging Timestamp harge Information HSSD Indicator R UT Time Offset ode Service ode Transparency Indicator Fixed Network User Rate User Protocol Indicator Guaranteed Bit Rate aximum Bit Rate O TeleService ode Bearer O Service ode Figure 3.9 Basic Service Used Logical Structure Group Element Name Also Occurs In Detail Shown In Basic Service Used Figure 3.6, Figure 3.12 Basic Service Service ode Figure 3.15 harge Information Figure 3.15, Figure 3.16, Figure 3.19, Figure 3.23, Figure 3.28 Figure 3. 3.11.05 Page of 217

3. harge Information harge Information harged Item Exchange Rate ode all Type Group harge Detail Tax Information Discount Information R R all Type 1 all Type 2 all Type 3 Tax Rate ode Tax Value Taxable Amount harge Type harge hargeable Units harged Units O harge Detail Timestamp Discount ode Discount Value Discountable Amount UT Time Offset ode Figure 3. harge Information Logical Structure Group Element Name Also Occurs In Detail Shown In harge Information Figure 3.9, Figure 3.15, Figure 3.16, Figure 3.19, Figure 3.23, Figure 3.28 harge Detail Tax Information Figure 3.11 Discount Information Figure 3.11 all Type Group 3.11.05 Page 21 of 217

3.11 AEL Service Used AEL Service Used AEL Service AEL Service Key Default all Handling Indicator Exchange Rate ode Tax Information R Discount Information AEL Invocation Fee 3G AEL Destination SE Information AEL O Destination Number O Destination Figure 3.11 AEL Service Used Logical Structure Group Element Name Also Occurs In Detail Shown In AEL Service Used Figure 3.6, Figure 3.12, Figure 3.17 3G AEL Destination Destination Figure 3.18 Tax Information Figure 3. Discount Information Figure 3. 3.11.05 Page 22 of 217

3.12 obile Terminated all obile Terminated all T Basic all Information Location Information Equipment Identifier Basic Service Used AEL Service Used Operator Specific Information O R Figure 3.12 obile Terminated all Logical Structure Group Element Name Also Occurs In Detail Shown In obile Terminated all Figure 3.2 T Basic all Information Figure 3.13 Location Information Figure 3.6, Figure 3.14 Equipment Identifier Figure 3.14, Figure 3.17 Figure 3.8 Figure 3.6 Basic Service Used Figure 3.6 Figure 3.9 AEL Service Used Figure 3.6, Figure 3.17 Figure 3.11 3.11.05 Page 23 of 217

3.13 T Basic all Information T Basic all Information hargeable Subscriber RAP File Sequence Number all Originator Originating Network all Event Start Timestamp Total all Event Duration SI Toolkit Indicator ause For Termination alling Number LIR Status Indicator SS Originator UT Time Offset Figure 3.13 T Basic all Information Logical Structure Group Element Name Also Occurs In Detail Shown In T Basic all Information Figure 3.12 hargeable Subscriber Figure 3.14, Figure 3.18 all Originator Figure 3.7 3.11.05 Page 24 of 217

3.14 Supplementary Service Event Supplementary Service Event hargeable Subscriber RAP File Sequence Number Location Information Equipment Identifier Supplementary Service Used Operator Specific Information O R Figure 3.14 Supplementary Service Event Logical Structure Group Element Name Also Occurs In Detail Shown In Supplementary Service Event Figure 3.2 hargeable Subscriber Figure 3.13, Figure 3.18 Location Information Figure 3.6, Figure 3.12 Equipment Identifier Figure 3.7 Figure 3.8 Supplementary Service Used Figure 3.15 3.11.05 Page 25 of 217

3.15 Supplementary Service Used Supplementary Service Used Supplementary Service ode Action ode Supplementary Service Parameters harging Timestamp harge Information Service ode R UT Time Offset ode Figure 3.15 Supplementary Service Used Logical Structure Group Element Name Also Occurs In Detail Shown In Supplementary Service Used Figure 3.14 harge Information Figure 3.9, Figure 3.16, Figure 3.19, Figure 3.23, Figure 3.28 Figure 3. Service ode Figure 3.9 3.11.05 Page 26 of 217

3.16 Service entre Usage Service entre Usage RAP File Sequence Number Serving Network harge Information SU harge Type SU Timestamps Operator Specific Information O R SU Basic Information Recording Entity ode Deposit Timestamp ompletion Timestamp harging Point SU hargeable Subscriber harged Party Status Non harged Number LIR Status Indicator Originating Network Destination Network UT Time Offset ode UT Time Offset ode GS O hargeable Subscriber IN O Priority ode essage Type ISI SISDN DN essage Status Distance harge Band ode essage Description ode Figure 3.16 Service entre Usage Logical Structure Group Element Name Also Occurs In Detail Shown In Service entre Usage Figure 3.2 SU Basic Information SU hargeable Subscriber GS hargeable Subscriber harge Information Figure 3.9, Figure 3.15, Figure 3.19, Figure 3.23, Figure 3.28 SU harge Type SU Timestamps Figure 3. 3.11.05 Page 27 of 217

3.17 all all Basic all Information Location Information Equipment Identifier Service Used AEL Service Used Operator Specific Information O R Network Location Home Location Information O Geographical Location Recording Entity ode Location Area ode ell Identity R O Figure 3.17 all Logical Structure Group Element Name Also Occurs In Detail Shown In all Figure 3.2 Basic all Information Figure 3.18 Location Information Network Location Home Location Information Figure 3.8 Geographical Location Figure 3.8 Equipment Identifier Figure 3.12, Figure 3.14 Figure 3.6 Service Used Figure 3.19 AEL Service Used Figure 3.6, Figure 3.12 Figure 3.11 3.11.05 Page 28 of 217

3.18 Basic all Information Basic all Information hargeable Subscriber RAP File Sequence Number Destination all Event Start Timestamp Total all Event Duration Partial Type Indicator Network Init. PDP ontext harging Id hargeable Subscriber PDP Address Network Access Identifier UT Time Offset ode ause For Termination PDP ontext Start Timestamp O Access Point Name NI Access Point Name OI UT Time Offset ode Figure 3.18 Basic all Information Logical Structure Group Element Name Also Occurs In Detail Shown In Basic all Information Figure 3.17 hargeable Subscriber Destination Figure 3.11 hargeable Subscriber Figure 3.13, Figure 3.14 Figure 3.7 3.11.05 Page 29 of 217

3.19 Service Used Service Used IS Signalling ontext Data Volume Incoming Data Volume Outgoing harge Information R Figure 3.19 Service Used Logical Structure Group Element Name Also Occurs In Detail Shown In Service Used Figure 3.17 harge Information Figure 3.9, Figure 3.15, Figure 3.16, Figure 3.23, Figure 3.28 Figure 3. 3.11.05 Page 30 of 217

3. ontent Transaction ontent Transaction ontent Transaction Basic Info harged Party Information Serving Parties Information ontent Service Used R Operator Specific Information O R ontent Provider Name ontent Provider R Internet Service Provider R Network R ontent Provider Id Type ontent Provider Identifier ISP Id Type ISP Identifier Network Id Type Network Identifier Figure 3. ontent Transaction Logical Structure Group Element Name Also Occurs In Detail Shown In ontent Transaction Figure 3.2 ontent Transaction Basic Info Figure 3.21 harged Party Information Figure 3.22 ontent Service Used Figure 3.23 Serving Parties Information ontent Provider Internet Service Provider Figure 3.25 Network Figure 3.25 3.11.05 Page 31 of 217

3.21 ontent Transaction Basic Info ontent Transaction Basic Info RAP File Sequence Number Order Placed Timestamp Requested Delivery Timestamp Actual Delivery Timestamp Total Transaction Duration Transaction Status UT Time Offset ode UT Time Offset ode UT Time Offset ode Figure 3.21 ontent Transaction Basic Info Logical Structure Group Element Name Also Occurs In Detail Shown In ontent Transaction Basic Info Figure 3. 3.11.05 Page 32 of 217

3.22 harged Party Information harged Party Information harged Party Identification R harged Party Home Identification R harged Party Location R harged Party Equipment harged Party Id Type harged Party Identifier Home Id Type Home Identifier Location Id Type Location Identifier Equipment Id Type Equipment Id Figure 3.22 harged Party Information Logical Structure Group Element Name Also Occurs In Detail Shown In harged Party Information Figure 3. harged Party Identification harged Party Home Identification harged Party Location harged Party Equipment 3.11.05 Page 33 of 217

3.23 ontent Service Used ontent Service Used Transaction Description Suppression Transaction Short Description Transaction Detail Description Transaction Identifier Transaction Authorisation ode Data Volume Incoming Data Volume Outgoing Total Data Volume ontent Transaction ode ontent Transaction Type Object Type harge Refund Indicator ontent harging Point harge Information R Advised harge Information Figure 3.23 ontent Service Used Logical Structure Group Element Name Also Occurs In Detail Shown In ontent Service Used Figure 3. harge Information Figure 3.9, Figure 3.15, Figure 3.16, Figure 3.19, Figure 3.28 Figure 3. Advised harge Information Figure 3.24 3.11.05 Page 34 of 217

3.24 Advised harge Information Advised harge Information Paid Indicator Payment ethod O Advised harge urrency Advised harge ommission Figure 3.24 Advised harge Information Logical Structure Group Element Name Also Occurs In Detail Shown In Advised harge Information Figure 3.23 3.11.05 Page 35 of 217

3.25 Location Service Location Service Recording Entity ode Tracking ustomer Information Tracked ustomer Information Operator Specific Information O R RAP File Sequence Number all Reference LS SP Information Location Service Usage LS SP Identification R Internet Service Provider R Network R ontent Provider Id Type ontent Provider Identifier Figure 3.25 Location Service Logical Structure Group Element Name Also Occurs In Detail Shown In Location Service Figure 3.2 Tracking ustomer Information Tracked ustomer Information Figure 3.26 Figure 3.27 Location Service Usage Figure 3.28 LS SP Information LS SP Identification Internet Service Provider Figure 3. Network Figure 3. 3.11.05 Page 36 of 217

3.26 Tracking ustomer Information Tracking ustomer Information Tracking ustomer Identification R Tracking ustomer Home Id R Tracking ustomer Location R Tracking ustomer Equipment ustomer Id Type ustomer Identifier Home Id Type Home Identifier Location Id Type Location Identifier Equipment Id Type Equipment Id Figure 3.26 Tracking ustomer Information Logical Structure Group Element Name Also Occurs In Detail Shown In Tracking ustomer Information Figure 3.25 Tracking ustomer Identification Tracking ustomer Home Id Tracking ustomer Location Tracking ustomer Equipment 3.11.05 Page 37 of 217

3.27 Tracked ustomer Information Tracked ustomer Information Tracked ustomer Identification R Tracked ustomer Home Id R Tracked ustomer Location R Tracked ustomer Equipment ustomer Id Type ustomer Identifier Home Id Type Home Identifier Location Id Type Location Identifier Equipment Id Type Equipment Id Figure 3.27 Tracked ustomer Information Logical Structure Group Element Name Also Occurs In Detail Shown In Tracked ustomer Information Figure 3.25 Tracked ustomer Identification Tracked ustomer Home Id Tracked ustomer Location Tracked ustomer Equipment 3.11.05 Page 38 of 217

3.28 Location Service Usage Location Service Usage LS QoS Requested LS QoS Delivered harging Timestamp harge Information R LS Request Timestamp Vertical Accuracy Requested Tracking Period UT Time Offset ode UT Time Offset ode Horizontal Accuracy Requested Response Time ategory Tracking Frequency LS Transaction Status Tracking Frequency Tracking Period Age Of Location Horizontal Accuracy Delivered Vertical Accuracy Delivered Positioning ethod Response Time Figure 3.28 Location Service Usage Logical Structure Group Element Name Also Occurs In Detail Shown In Location Service Usage Figure 3.25 harge Information Figure 3.9, Figure 3.15, Figure 3.16, Figure 3.19, Figure 3.23 Figure 3. LS QoS Requested LS QoS Delivered 3.11.05 Page 39 of 217

3.29 Audit ontrol Information Audit ontrol Information Earliest all Timestamp O Total harge Total harge Refund Total Discount Value Total Discount Refund all Event Details ount Operator Specific Information O R UT Time Offset Total Tax Refund Total Tax Value Total Advised harge Value R Latest all Timestamp O UT Time Offset Advised harge urrency Total Advised harge Total Advised harge Refund Total ommission Total ommission Refund Figure 3.29 Audit ontrol Information Logical Structure Group Element Name Also Occurs In Detail Shown In Audit ontrol Information Figure 3.2 Total Advised harge Value 3.11.05 Page 40 of 217

4 DATA DITIONARY 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 abbreviations within the ontext column are detailed in the ontext Abbreviations Table at the end of the dictionary. ode ontext 3G AEL Destination A group identifying the destination as returned by the AEL server. It may consist either of AEL Destination Number or Destination depending on service used. ust be present within group AEL Service Used where the destination has been modified by the AEL server. Access Point Name NI The Network Identifier part of the Access Point Name (APN) in dot notation. Derivation: In the case of usage,the actual connected APN NI as defined in 3GPP TS 32.215. Pre GS Release 98 from the GS item AccessPointName (see conditionality note below). 11 Syntax error where group Destination occurs within group Basic all Information. Syntax error where group Destination occurs within group 3G AEL Destination. In case of relevant to AEL usage: 1. The actual connected APN NI as modified by the SE in APN NI field as defined in 3GPP TS 32.215. 2. The original APN NI before modification by the SE in AEL APN NI field available within AEL Information as defined in 3GPP TS 32.215. In the case of WLAN usage, actual contents are at the discretion of the Sender. andatory within group Destination. Networks which have not yet upgraded to at least GS Release 3.11.05 Page 41 of 217

ode 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. ontext Values: This field is encoded as a string comprising of up to 63 characters. The actual contents are for further study. Access Point Name OI The Operator Identifier part of the Access Point Name (APN) in dot notation. Derivation: In the case of usage, the actual connected APN OI as defined in 3GPP TS 32.215. In case of relevant to AEL usage: 11 Syntax error where group Destination occurs within group Basic all Information. Syntax error where group Destination occurs within group 3G AEL Destination. 3. The actual connected APN OI as modified by the SE in APN OI field as defined in 3GPP TS 32.215. 4. The original APN OI before modification by the SE in AEL APN OI field available within AEL Information as defined in 3GPP TS 32.215. andatory within group Destination where the all represents an SGSN ticket or an assembled SGSN/GGSN ticket. This item is only available within networks which have upgraded to at least GS Release 98 and not available for WLAN network usage. Values: This field is encoded as a string comprising of up to 37 characters. The actual contents are for further study. Accounting Information A grouping of accounting related information. The group must contain a Local urrency and urrency onversion table. The group may conditionally include Taxation and Discounting tables and, 30 31 Tf Batch Tf Batch No Taxation group present and batch contains taxes. No Discounting group present and batch 3.11.05 Page 42 of 217

ode optionally, TAP urrency. ust be present within group Transfer Batch where any all Event Details contains a charge. 32 33 ontext Tf Batch Tf Batch contains discounts. andatory item Local urrency missing within group. Item TAP urrency not present and currency other than SDR specified in roaming agreement. 34 Tf Batch Group urrency onversion missing within group and the transfer includes one or more harge greater than zero. Action ode The Action ode qualifies the way in which the supplementary service is used. Derivation for Supplementary Services: GS item SS ActionType (3GPP TS 32.005). 35 Tf Batch SS SS andatory item TAP Decimal Places missing within group. Value out of range for supplementary service where associated Supplementary Service ode is for a supplementary service. Actual Delivery Timestamp Values: andatory within group Supplementary Service Used. 0 Registration SS only 1 Erasure SS only 2 Activation SS only 3 Deactivation SS only 4 Interrogation SS only 5 Invocation SS only 6 Registration of Password SS only 7 USSD Invocation USSD only The timestamp representing the actual time at which the start of the ontent Transaction was commenced. This is given in the time of the serving ontent Provider. There must be a UT Time Offset ode associated with 22 SS Value out of range for USSD message where associated Supplementary Service ode is for USSD message. Note: Error odes 11 & 21 removed in TAP release 3.11 (01 ay 05). ontent Syntax error and timestamp referenced as harging Point. 3.11.05 Page 43 of 217

ode the item. Example: The harged Party may request to download all messages at 20hrs in order to take advantage of off-peak rates while placing the order at an earlier time but the actual content download may have commenced at 0030hrs. ust be present within group ontent Transaction Basic Info when no other timestamp present within group or when item referenced as the harging Point. 11 21 30 31 ontext ontent ontent ontent ontent ontent Syntax error and timestamp not referenced as harging Point. Value out of range and timestamp referenced as harging Point. Value out of range and timestamp not referenced as harging Point. andatory associated UT Time Offset ode missing and timestamp referenced as harging Point. andatory associated UT Time Offset ode missing and timestamp not referenced as harging Point. 0 ontent Actual Delivery Timestamp after associated harge Detail timestamp and timestamp referenced as harging Point. 1 ontent Actual Delivery Timestamp after associated harge Detail timestamp and timestamp not referenced as harging Point. Advised harge The charge advised to the harged Party. 0 ontent ontent Actual Delivery Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file and the timestamp is referenced as the harging Point. The charge must not contain a negative value. Note that where there is an associated harge Refund Indicator present then this is an implicit negative value. ontent Value out of range. 3.11.05 Page 44 of 217

ode 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 harge urrency, or TAP urrency where no associated Advised harge urrency is present, or SDRs where neither is present. The number of decimal places is defined by item TAP Decimal Places. andatory within group Advised harge Information. ontext Advised harge urrency Values: > = 0 The currency in which the harged Party has been advised of the charge. The Advised harge urrency contains the urrency ode, which identifies the currency used for Advised harge. 11 Audit ontent Note that this item will not be present if using the TAP file currency. The standard TAP file currency default is SDRs unless bilaterally agreed otherwise or a specific currency default for the file can be defined by item TAP urrency (use of TAP urrency will be by bilateral agreement between partners). 21 Audit ontent Value out of range. Value out of range. Derivation: ISO 4217 urrency odes standard. Present within groups Advised harge Information Total Advised harge Value when different to TAP urrency and not SDRs. Example: urrency ode urrency name 3.11.05 Page 45 of 217

ode Advised harge Information Age Of Location EUR INR XDR USD Euro Indian rupee SDR U.S. dollar Where a customer has been advised of a charge then the Advised harge Information group identifies the actual charge and may, conditionally, provide additional information. The group must contain Advised harge, all other information is conditional. onditional information present may include Paid Indicator, Payment ethod (optionally), Advised harge urrency and ommission. ust be present within group ontent Service Used when charge has been advised to the customer. This value represents the elapsed time in minutes since the last network contact of the mobile station (i.e. the actuality of the location information). Derivation: GS/UTS item AgeOfLocationInformation (3GPP TS 29.002). ust be present within group LS QoS Delivered where available from the network and LS transaction status indicates last known location. ontext 30 ontent andatory item Advised harge not present within group. LS Value out of range. Audit ontrol Information Values: This field is coded as an integer within the range 0-32767. The value 0 indicates that the S is currently in contact with the network, whereas the value 32767 indicates that the location information is at least 32767 minutes old. The group identifies the end of the Transfer Batch. The following items are optional; Earliest all Timestamp, Latest all 30 Tf Batch andatory item Total harge missing within group. 3.11.05 Page 46 of 217

ode Timestamp and Operator Specific Information. Total harge, Total Tax Value, Total Discount Value and all Event Details ount are all mandatory. onditionally present are Total harge Refund, Total Advised harge Value, Total Tax Refund and Total Discount Refund. andatory within group Transfer Batch. 31 32 33 36 ontext Tf Batch Tf Batch Tf Batch Tf Batch andatory item Total Tax Value missing within group. andatory item Total Discount Value missing within group. andatory item all Event Details ount missing within group. Item Total Tax Refund present and use of ontent Transaction not bilaterally agreed. Also see error code 50 (section 5.1). 37 Tf Batch Item Total Discount Refund present and use of ontent Transaction not bilaterally agreed. Also see error code 50 (section 5.1). 38 Tf Batch Group Total Advised harge Value present and use of ontent Transaction not bilaterally agreed. Also see error code 50 (section 5.1). 39 Tf Batch onditional group Total Advised harge Value missing within group and one or more occurrences of ontent Transaction present containing Advised harge Information. 40 Tf Batch Item Total harge Refund expected with value greater than 0 and not present. Basic Service The group Basic Service identifies the actual Basic Service used. It must contain the Service ode, it will, conditionally also contain the 30 O T Note: Error odes 34 & 35 removed in TAP release 3.11 (01 ay 05). andatory group Service ode missing within group. 3.11.05 Page 47 of 217

ode following for UTS: Transparency Indicator, Fixed Network User Rate, User Protocol Indicator, Guaranteed Bit Rate and aximum Bit Rate. andatory within group Basic Service Used. ontext Note: Error odes 31, 32, 33, 34, 35 and 36 removed in TAP release 3.11 (01 ay 05). Basic Service Used A group of data identifying the type of service used together with all related charging information. 30 O T andatory group Basic Service missing within group. The group must have Basic Service and harge Information present. harging Timestamp item will be present as applicable and HSSD Indicator will be present where HSSD has been used. 32 O T andatory group harge Information missing within group. andatory within groups obile Originated all obile Terminated all one must be present. Batch ontrol Information All items are mandatory except File Type Indicator which will only be present where the file represent test data, RAP File Sequence Number (used where the batch has previously been returned with a fatal error and is now being resubmitted) and Operator Specific Information and File reation Timestamp which are optional. andatory within group Transfer Batch. 30 31 32 33 Tf Batch Tf Batch Tf Batch Tf Batch andatory item Sender missing within group. andatory item Recipient missing within group. andatory item File Sequence Number missing within group. andatory item File Available Timestamp missing within group. 34 Tf Batch andatory item Specification Version Number missing within group. 36 37 Tf Batch Tf Batch andatory item Transfer ut Off Timestamp missing within group. File Sequence Number previously received 3.11.05 Page 48 of 217

ode ontext and rejected with fatal error, therefore RAP File Sequence Number expected but not present. 38 Tf Batch File Type Indicator present within group and Transfer Batch expected as chargeable data (i.e. live data). 39 Tf Batch File Type Indicator not present within group and Transfer Batch expected as test data (i.e. non chargeable data). 40 Tf Batch RAP File Sequence Number present although File Sequence Number has not previously been rejected with a fatal error (e.g. previously missing or new files). Bearer Service ode A code which uniquely defines a Bearer Service. Group Bearer odes, identifiable by the description All, should only be used where details of the specific services affected are not available from the network. Note that compound Bearer Service group codes can only occur in conjunction with HSSD usage or call independent supplementary service operations. 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 DRs. Derivation: GS item BearerServiceode (3GPP TS 32.005). 11 21 O T SS O T SS Note: Error ode 35 removed in TAP release 3.11 (01 ay 05). Value out of range. Value out of range. The code is derived by taking the AP encoding as specified for BearerServiceode in 3GPP TS 29.002 and translating bits 7-4 3.11.05 Page 49 of 217

ode into a hex character and bits 3-1 into a second hex character. ust be present within group Service ode where the type of service used was a bearer service. ust not be present when the type of service used was a tele service and, therefore, Teleservice ode is present. ontext Values: 00 All Bearer Services All Data ircuit Asynchronous Services 21 Duplex Asynch. 300bps data circuit 22 Duplex Asynch. 10bps data circuit 23 Duplex Asynch. 10/75bps data circuit 24 Duplex Asynch. 2400bps data circuit 25 Duplex Asynch. 4800bps data circuit 26 Duplex Asynch. 9600bps data circuit 27 General Data ircuit Asynchronous Service 30 All Data ircuit Synchronous Services 32 Duplex Synch. 10bps data circuit 34 Duplex Synch. 2400bps data circuit 35 Duplex Synch. 4800bps data circuit 36 Duplex Synch. 9600bps data circuit 37 General Data ircuit Synchronous Service 40 All Dedicated PAD Access Services 41 Duplex Asynch. 300bps PAD access 42 Duplex Asynch. 10bps PAD access 43 Duplex Asynch. 10/75bps PAD access 44 Duplex Asynch. 2400bps PAD access 45 Duplex Asynch. 4800bps PAD access 46 Duplex Asynch. 9600bps PAD access 47 General PAD Access Service 50 All Dedicated Packet Access Services 54 Duplex Synch. 2400bps PAD access 55 Duplex Synch. 4800bps PAD access 56 Duplex Synch. 9600bps PAD access 57 General Packet Access Service 3.11.05 Page 50 of 217

ode 60 All Alternat Speech/Asynchronous Services 61 Alt. Speech/Asynch. 300bps unrestricted digital 62 Alt. Speech/Asynch. 10bps unrestricted digital 63 Alt. Speech/Asynch. 10/75bps unrestricted digital 64 Alt. Speech/Asynch. 2400bps unrestricted digital 65 Alt. Speech/Asynch. 4800bps unrestricted digital 66 Alt. Speech/Asynch. 9600bps unrestricted digital 70 All Alternate Speech/Synchronous Services 72 Alt. Speech/Synch. 10bps unrestricted digital 74 Alt. Speech/Synch. 2400bps unrestricted digital 75 Alt. Speech/Synch. 4800bps unrestricted digital 76 Alt. Speech/Synch. 9600bps unrestricted digital 80 All Speech followed by Data Asynchronous Services 81 Speech then Asynch. 300bps unrestricted digital 82 Speech then Asynch. 10bps unrestricted digital 83 Speech then Asynch. 10/75bps unrestricted digital 84 Speech then Asynch. 2400bps unrestricted digital 85 Speech then Asynch. 4800bps unrestricted digital 86 Speech then Asynch. 9600bps unrestricted digital 90 All Speech followed by Data Synchronous Services 92 Speech then Synch. 10bps unrestricted digital 94 Speech then Synch. 2400bps unrestricted digital 95 Speech then Synch. 4800bps unrestricted digital 96 Speech then Synch. 9600bps unrestricted digital A0 All Data ircuit Asynchronous Services (compound) B0 All Data ircuit Synchronous Services (compound) 0 All Asynchronous Services (compound) D0 All Synchronous Services (compound) all Event Details all Event Details is a repeating item which is one of obile Originated all, obile Terminated all, Supplementary Service Event, Service entre Usage, all, ontent Transaction or Location Service. Each occurrence must have no more than one of these present. andatory within group Transfer Batch, one occurrence being 32 34 35 ontext Tf Batch Tf Batch Tf Batch Service entre Usage present although not agreed bilaterally. ontent Transaction present although not agreed bilaterally. Also see error code 50 (section 5.1). all present although not agreed 3.11.05 Page 51 of 217

ode present for each call/event present. ontext bilaterally. Also see error code 50 (section 5.1). 36 Tf Batch Location Service present although not agreed bilaterally. Also see error code 50(section 5.1). all Event Details ount all Event Start Timestamp This item is an audit control and contains a count of the number of occurrences of all Event Details within the TAP transfer. Values: andatory within group Audit ontrol Information. > 0 The timestamp gives the start of the call event. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode associated with the timestamp. Note that local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. Note that this timestamp is, in most cases, the start of charging, e.g. the call answer time rather than the channel seizure time where the call is charged from answer time. In the case of an intermediate or last partial record of the same all ( ontext) the timestamp must be populated with the record start time and not the context start timestamp (see item PDP ontext Start Timestamp for identification of context start time in each partial record). 0 30 0 1 Audit Audit Audit O T O T O T O T O Note: Error odes 30 & 31 removed in TAP release 3.3 (01 ay 01). Note: Error ode 33 removed in TAP release 3.11 (01 ay 05). Value out of range. Value does not match the count of all Event Details. Note that any rejected all Event Details must be included for the purposes of this validation. Value out of range. andatory associated item UT Time Offset ode missing. all event start timestamp after charge detail timestamp. all event start timestamp after charging 3.11.05 Page 52 of 217

ode Derivation: GS item answertime or seizuretime (3GPP TS 32.005). This will normally be the equivalent of the start of charging or, where the call event is non chargeable, the equivalent point. For WLAN network usage, translated into local time of the WLAN Hot Spot Location, item event-timestamp (RF 2869). andatory within groups O Basic all Information T Basic all Information Basic all Information Format: YYDDHHSS 0 ontext T O T timestamp. all Event Start Timestamp before the commercial roaming start date for the specific network service and the TAP file is not a test file. all Originator Example: > PDP ontext activated at 2350hrs > Two partials raised on TAP (cut across 2400hrs) First partial: all Event Start Timestamp = PDP ontext Start Timestamp = 235000 Second partial: all Event Start Timestamp = 240000 PDP ontext Start Timestamp = 235000 The call originator applies only in respect of mobile terminated traffic. It identifies the person making the call. For SS T usage it identifies the SS delivering the SS and, where available, the originator of the SS. Also, some networks may inhibit the transfer of this information where LI presentation is prohibited. Derivation: GS item allingnumber (3GPP TS 32.005). This item is of type AddressString. Note: Error odes 30, 31, 32, 33 and 34 removed in TAP release 3. (01 ay 03). Note: Error ode 35 removed in TAP release 3.11 (01 ay 05). 3.11.05 Page 53 of 217

ode all Reference ust be present within group T Basic all Information where the network supports calling line identity (LI) or if TeleService ode indicates SS usage (values or 21) and available from the network. An identifier local to the Recording Entity. The identifier distinguishes between transactions on the same mobile station. Derivation: GS item allreference (3GPP TS 32.005). ontext O T SS LS ust be present within groups Network Location Location Service when available from the network. all Type Group A group identifying the IOT used by the VPN to price the call. The group contains mandatory items all Type 1, all Type 2 and all Type 3. 30 31 O O andatory item all Type 1 missing within group. andatory item all Type 2 missing within group. all Type 1 ust be present within group harge Information where harge Information occurs within a obile Originated all or within a all. The highest category call type in respect of the destination of the call. Values: andatory within group all Type Group. 32 O O O andatory item all Type 3 missing within group. Note: Error ode 33 removed in TAP release 3.11 (01 ay 05). Value out of range. 3.11.05 Page 54 of 217

ode 1 National 2 International HGGSN 11 VGGSN 12 Other GGSN 0 WLAN ontext 2 O Item not specified according to how the call has been priced (as verified against the Sender s IOT). Note: Error odes 0 & 1 removed in TAP release 3.09 (01 ay 02). Note: Values 1 & 2 are for use in obile Originated alls only Values, 11 & 12 are for use in alls only Value 0 is for use in all representing WLAN usage only all Type 2 An item which identifies the sub category of all Type 1. This defines, in more detail, the classification of the call within the IOT, as used by the VPN to price the call. The categories are as defined within the IOT and it not, therefore, possible to use a category which has not been identified within the VPN s IOT. andatory within group all Type Group. 0 O O O Value out of range. Item not specified according to how the call has been priced (as verified against the Sender s IOT). Values: 0 Unknown 1 obile 2 PSTN 3 Non Geographic 4 Premium Rate 5 Satellite destination Broadband 11 Narrowband 12 onversational 13 Streaming 14 Interactive 15 Background Note: alls Value 0 (zero) is for use in obile Originated alls and 3.11.05 Page 55 of 217

ode Values 1,2,3,4 & 5 are for use in obile Originated alls only Values, 11, 12, 13, 14 & 15 are for use in alls only ontext Premium Rate is as defined by the VPN s national telecom regulator. Non Geographic is used, for example, for special services and freephone/ toll free services. Unknown is only used when it has not been possible to identify the called number or usage as belonging to any other category (this will be a special case tariff defined in the VPN s IOT). all Type 3 An item which identifies the sub category of all Type 2. This defines, in more detail, the classification of the call within the IOT, as used by the VPN to price the call. The categories are as defined within the IOT and it not, therefore, possible to use a category which has not been identified within the VPN s IOT. 0 O O Item not specified according to how the call has been priced (as verified against the Sender s IOT). alled Number Values: andatory within group all Type Group. - numeric as defined within the VPN s IOT. The called number is the representation of the number dialled by the subscriber in establishing a call or the number to which the call is forwarded or transferred in those particular scenarios, the representation is always in International format, i.e. the number must begin with the ountry ode. In the case of SS O usage the called number item contains the SS address. The International representation of the called number means that it must start with the valid country code as listed in E.164 Assigned ountry odes (spare and reserved codes excluded). In addition this number must comply with E.164 definition of International public telecommunication number structure except where the call represents one of the following: Short code call Emergency call Unsuccessful call attempt 3.11.05 Page 56 of 217 11 O O O Syntax error and call does not represent an emergency call. Syntax error and call represents emergency call. Value out of range or number does not start with a valid country code as listed in E.164 Assigned ountry odes (spare and reserved codes excluded, reserved code 970 for Palestine is an exception and numbers starting with that ountry ode are valid).

ode Specially routed call (for example using * or # ) Where the destination has been modified by AEL. In all cases the number must start with the valid country code and contain only numeric digits. All other characters must be removed. See examples in TD.58. Derivation: Derived from GS item allednumber (3GPP TS 32.005) but it is represented in TAP in International format, i.e. the number begins with the ountry ode. ust be present within group Destination except for one of the following: use of the basic service emergency call unsuccessful call attempt when the call destination has been modified by AEL (AEL Destination Number is present) In case of unsuccessful call attempt or AEL destination modification item Dialled Digits must be filled in. In the case of SS-O usage this field must always be present. ontext alled Place Values: Each digit is numeric (0-9) The alled Place indicates, in plain text, the name of the geographic area to which the call was placed, e.g. Atlanta, Roma, Sydney, or the type of service used, e.g. Freephone. On international calls this item will contain the called country, e.g. Norway, South Africa, Thailand. ust be present within group Destination when provided by the VPN s billing system. O 3.11.05 Page 57 of 217

ode Not present within group Destination where the destination is non geographic, e.g. operator call (see also all Type and Sender PN Subtype). ontext alled Region Values: ISO 646 Actual content is at the Sender PN discretion alled Region contains the geographical region called or service used, this is a broader description than contained within alled Place, e.g. GA (Georgia), Lazio, NSW (New South Wales). ust be present within group Destination when provided by the VPN s billing system. Not present within group Destination where the destination is international or non geographic. O alling Number Values: ISO 646 Actual content is at the Sender PN discretion The calling number is the number from which the call was originated in the case of mobile terminated calls. For SS T this item must contain the SS SISDN. T T Number not in international format. Derivation: GS item allingnumber (3GPP TS 32.005). 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. Note: Error ode 11 removed in TAP release 3.11 (01 ay 05). ust be present within group all Originator where available from the network. Values: Each digit is numeric (0 9) 3.11.05 Page 58 of 217

ode AEL Destination Number The destination number returned by the AEL server to the interrogating (visited) S. Derivation: Derived from GS item allednumber (3GPP TS 32.005) but it is represented in TAP in International format, i.e. the number begins with the ountry ode. andatory within group 3G AEL Destination where Destination not present. ontext O T O T Number not short code and not represented in International format. AEL Invocation Fee Values: Each digit is numeric (0-9) or contains (representing *) or contains (representing #) or contains (representing a) or contains (representing b) or contains (representing c) or The charge for the AEL invocation after discounts have been deducted, where applicable (see Discount Information) but before any tax is added, where applicable (see Tax Information). O T The item must not contain a negative value. The charge is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Values: andatory within group AEL Service Used where the charge is greater than zero. > 0 (zero) 21 0 O T O T O T Value is negative. Value is 0 (zero). AEL Invocation Fee not in line with roaming agreement. Note: Rounding rules are at the discretion of the Sender, therefore, when validating the charge applied by the Sender (by using all 3.11.05 Page 59 of 217

ode ontext Type Group information and the Sender s IOT) the Recipient must allow for a tolerance. A minimum tolerance of 0.02 units of TAP urrency is recommended (independent of the number of TAP Decimal Places used for the TAP file). AEL Service Key The identification of the AEL service logic to be applied to the IN subscriber. Derivation: GS item ServiceKey as defined in 3GPP TS 32.005, 3GPP TS 32.015 and 3GPP TS 29.002. andatory within group AEL Service Used. 1 T O T O T AEL Invocation Fee is greater than 0 (zero) and AEL call not expected. Value out of range. AEL Service Range: 0 2147483647 (derived from 0 to 2^31) The level of AEL service provided by the VPN to the roaming AEL subscriber. The VPN may vary the associated AEL invocation fee according to the level of service provided. The value is derived from the actual AEL features which have been used during the call: Basic: All AEL features excluding control of call duration and online charging. edium: All AEL features including control of call duration but excluding control of online charging. High: All AEL features including control of online charging (i.e. timers set in the VS or SGSN [for ]) but excluding control of call duration. aximum: All AEL features including control of online 3.11.05 Page 60 of 217 O T O T Value out of range.

ode Derivation: charging (i.e. timers set in the VS or SGSN [for ]) and call duration. From the definition in GS Association PRD BA.27. andatory within group AEL Service Used where AEL Invocation Fee present within the call event. ontext AEL Service Used Values: 0 basic 1 medium 2 high 3 maximum This element is a group detailing the invocation of AEL services. The group must contain AEL Service Key. Where the AEL Invocation Fee is greater than zero this group must also contain the Exchange Rate ode. All other items are conditional. ust be present within groups obile Originated all obile Terminated all all where invocation of AEL services has taken place within the call. 30 31 33 35 O T O O T O T Item AEL Service missing within group although AEL Invocation Fee is present and greater than zero. AEL Destination Number missing within group although number was modified by AEL (logical group 3G AEL Destination). andatory item AEL Service Key missing within group. Destination present within group (logical group 3G AEL Destination). 36 37 AEL Destination Number present within group (logical group 3G AEL Destination). Group Destination missing within 3.11.05 Page 61 of 217

ode 40 41 42 43 ontext O T O T O T O T group although APN was modified by AEL (logical group 3G AEL Destination). Exchange Rate ode missing within the group and AEL Invocation Fee is greater than zero. Tax Information missing within the group and AEL Invocation Fee is greater than zero and taxation is expected according to roaming agreement. Tax Information present within the group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is greater than zero. Tax Information present within the group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is not greater than zero. ause For Termination Indicates the reason for termination of the call where that reason is anything other than normal. Derivation: GS items auseforterm (3GPP TS 32.005) and auseforreclosing (3GPP TS 32.015). For WLAN network usage mapped from acct-terminate-cause (RF 2866). 0 O T O T Note: Error odes 32, 34, 38 & 39 removed in TAP release 3.11 (01 ay 05). Value out of range. ause for termination specified and the call 3.11.05 Page 62 of 217

ode ust be present within groups O Basic all Information T Basic all Information Basic all Information 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. ontext event represents first or intermediate partial. Values: 3 Unsuccessful call attempt 4 Stable call abnormal termination 5 AEL initiated call release anagement intervention Note that the following GS values are not valid for use in TAP: 0 normal release 2 partial record call reestablishment Values 4, 5 and are valid within a all context only where the call did not terminate normally. Where partial alls are generated then only the last partial can contain a cause for termination where appropriate. Values 3, 4 and 5 are valid within a O/T only where the call did not terminate normally. Values 4 and are valid within a WLAN context only where the call did not terminate normally. Where partial alls for WLAN network usage are generated then only the last partial can contain a cause for termination where appropriate. Following is a mapping between the RF2866 Acct-Termination-ause values and ause for Termination values: TD.57 ause For Termination Values RF2866 Values RF2866 Short Description 3.11.05 Page 63 of 217

ode ell Identity <not present> 1 User Request 4 2 Lost arrier 4 3 Lost Service 4 4 Idle Timeout 4 5 Session Timeout 6 Admin Reset 7 Admin Reboot 4 8 Port Error 4 9 NAS Error 4 NAS Request 4 11 NAS Reboot 4 12 Port Unneeded 4 13 Port Preempted 4 14 Port Suspended 4 15 Service Unavailable 4 16 allback 4 17 User Error <not present> 18 Host Request The identity of the cell from which the call originated or in which it terminated. Derivation: Optionality: GS item ellid (3GPP TS 32.005). Operators may decide not to transfer the ell Identity. Present within groups Network Location Network Location 3.11.05 Page 64 of 217 ontext O T SS O T SS Value out of range.

ode if the call originates or terminates from a mobile, i.e. not available in call divert cases (subject to optionality). Is not present for WLAN network usage. The ell Identity is a two octet string as defined in 3GPP TS 44.008. ontext harge For the TAP the octets are converted to a decimal integer number in the range 00000 to 65535. The leading zeros are significant. E.g. 0101001000 equates to 26160 01100000 equates to 39946 000000111001 equates to 04337 The charge for the harge Detail after discounts have been deducted (if applicable, see Discount Information) but before any tax is added (if applicable, see Tax Information). alls alls Value out of range. The harge must not contain a negative value. The charge is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Example: A call of 2 minutes duration is charged at 1 SDR per 30 seconds; the call is liable for tax at 15% and the HPN will get the call discounted at %. Rated charge value 4.000 SDR Discount Rate % Tax Rate 15% 0 alls harge not in line with roaming agreement. Note: Rounding rules are at the discretion of the Sender, therefore, when verifying the charge applied by the Sender (by using all Type Group information and the Sender s IOT) the Recipient must allow for a tolerance. A minimum tolerance of 0.02 units of TAP urrency is recommended (independently of the number of TAP Decimal Places used for the TAP file). Note: Error ode0 & 1 removed in TAP release 3.11 (01 ay 05). TAP fields will have the following values: Discount Value 0.800 SDR (rated charge value * Discount Rate) harge (harge Type 00) 3.0 SDR (rated charge value Discount Value) Tax Value 0.480 SDR (harge * Tax Rate) 3.11.05 Page 65 of 217

ode ust be present within group harge Detail. ontext harge Detail Values: > or = 0 (zero) A repeating group detailing the harge and/or charge element. harge and harge Type are mandatory items, harged Units is optional and all other items are conditional. andatory within group harge Information, at least one occurrence must be present. Note that, where a harge has been levied, even where that harge is zero, there must be one occurrence, and only one, with a harge Type of 00. 32 33 38 alls alls alls Associated item harged Item is one of A,E,F or L and item hargeable Units present within group. Associated item harged Item is one of D,V,W or X and item hargeable Units not present. andatory item harge Type not present within group. 39 alls andatory item harge not present within group. harge Detail Timestamp The timestamp showing the start of charging for the harge Detail within which it occurs. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode associated with the timestamp. Note that local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. ust be present within group harge Detail where it is not the same as the associated harging Timestamp. 30 0 1 alls alls alls alls O Note: Error odes 30, 31, 34, 35, 36 & 37 removed in TAP release 3.11 (01 ay 05). Value out of range. andatory associated item UT Time Offset ode missing. harge Detail Timestamp earlier than harging Timestamp and the harge associated with this harge Detail is greater than zero (note UT time offset must be taken into consideration). harge Detail Timestamp is later than the end 3.11.05 Page 66 of 217

ode harge Information ontext Format: YYDDHHSS T harge information is provided for all chargeable elements. The group must contain harged Item and at least one occurrence of harge Detail. One or more occurrences must be present within groups Basic Service Used. Service Used Service entre Usage Location Service Usage 30 31 32 33 alls alls O alls of the call (all Event Start Timestamp plus Total all Event Duration) and the harge associated with this harge Detail is greater than zero (note UT time offset must be taken into consideration). Item harged Item missing within group. Item Exchange Rate ode missing within group and one or more harge within an associated harge Detail is greater than zero. Item all Type Group missing within group where the harge Information relates to Basic Service Used or Service Used. Group harge Detail missing within group. One occurrence must be present within group Supplementary Service Used where the event is chargeable. One or more occurrences must be present within group ontent Service Used if the service is charged through the TAP on a wholesale basis, i.e. not using Advised harge Information for settlement. 34 35 alls alls Group Tax Information missing within group but expected in accordance with roaming agreement for that particular call. Tax Information group missing must be interpreted as Tax Value zero. Group Discount Information missing within group but expected in accordance with roaming agreement. 36 alls Occurrence of group harge Detail containing harge Type 00 missing within group. 37 alls ore than one occurrence of harge Detail present with the same harge Type value. 38 O T Breakout of harge Types AIR (01) and/or TOLL (03) not present on a duration based charge, but expected in accordance with 3.11.05 Page 67 of 217

ode ontext roaming agreement; i.e., only harge Type 00 present within group. This validation rule can be applied only where bilaterally agreed between sender and recipient 39 O T In accordance with roaming agreement, charges are defined in individual harge Types, but the harge for harge Type 00 does not equal sum of harges for the other harge Types as stated within roaming agreement. This validation rule can be applied only where bilaterally agreed between sender and recipient. 40 alls Group Tax Information present within group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is greater than 0 (zero). 41 alls Group Tax Information present within group but not expected in accordance with roaming agreement for the call/event and Tax Value referenced within the group is not greater than 0 (zero). harge Refund Indicator The harge Refund Indicator is present when the ontent Transaction represents a refund. This item, when present, will change the signs of any revenue represented within the ontent Service Used occurrence. 42 alls ontent ontent all Type Group present within group and the call event is not a O or all. Value out of range ust be present within group ontent Service Used when the 3.11.05 Page 68 of 217

ode harge Type Values: ontent Transaction represents a refund. 1 Refund When present within harge Detail the item identifies the type of charge represented by the harge Detail. When present within Taxation the item identifies the type of charge associated with the applied tax referenced by the associated Tax Rate ode. Note; in the Values list, below, some values are identified as reserved. Reserved values are not to be considered valid values, they are noted here in order to prevent their usage, were they to be used this could create inter standard roaming conversion problems. Elements containing a reserved value will fail the Value Out Of Range validation check. Values: ust be present within group harge Detail. ust be present within group Taxation when the associated Tax Rate ode references a tax applied to a specific harge Type. Note that this is not required for harge Type 00. 00 Total charge for harge Information (the invoiceable value) 01 Airtime charge 02 reserved 03 Toll charge 04 Directory assistance 05 reserved 21 VPN surcharge 69 99 reserved 11 21 22 ontext alls Acctng alls Acctng Acctng Value out of range. Note that reserved values are out of range. Value out of range. Note that reserved values are out of range. Value is 00. hargeable Subscriber ontains the identification of the chargeable subscriber. The group must contain either the ISI or the IN of the hargeable Subscriber, but not both. 30 O T SS Neither of mandatory items ISI or IN present within group. 3.11.05 Page 69 of 217

ode hargeable Units Operators may bilaterally agree to make transfer of SISDN mandatory. andatory within groups O Basic all Information T Basic all Information Supplementary Service Event. onditional within group hargeable Subscriber. The hargeable Units item indicates the number of units which are chargeable within the harge Detail, this may not correspond to the number of rounded units charged. The item harged Item defines what the units represent. Derivation: For duration based charge; GS item allduration (3GPP TS 32.005). allduration is defined in seconds. The duration related to WLAN network usage is defined in seconds. Where services have been used in conjunction with volume based charge; outgoing volume GS item DataVolumeUplink incoming volume GS item DataVolumeDownlink total volume sum of GS items DataVolumeUplink DataVolumeDownlink and the data volume items are defined in octets. Where volume is related to WLAN network usage then the volume is defined in octets. Where volume is related to messages (Service entre Usage) then 31 32 0 1 2 3 ontext O T SS O T SS alls alls O T Both of mandatory items ISI and IN present within group. SISDN missing within group but expected in accordance with roaming agreement. Value out of range. hargeable Units for harge Type 00 are greater than Total all Event Duration for harged Item D. hargeable Units for harge Type 00 are greater than the sum of Data Volume Incoming and Data Volume Outgoing for harged Item X. hargeable Units for harge Type 00 are greater than the Data Volume Outgoing for harged Item V. hargeable Units for harge Type 00 are greater than the Data Volume Incoming for harged Item W. 3.11.05 Page 70 of 217

ode the message length is represented in characters. The item content reflects the chargeable not charged units. Examples: for Duration charge Actual duration is 73 seconds all charged in 30 second units (i.e. 90 seconds) hargeable Units contains 73 ontext for SU based volume charge Actual message length is 17 characters essage charged in character units (i.e. characters) hargeable Units contains 17 ust be present within group harge Detail where the charge is either duration based or volume based. harged Item Values: > or = 0 This field identifies the charging principle applied and the unitisation of hargeable Units. It is not intended to identify the service used. andatory within groups alls alls Value out of range. Values: harge Information A D E all set up attempt ontent Duration based charge Event based charge 3.11.05 Page 71 of 217

ode harged Party Equipment harged Party Home Identification F L V W X Fixed (one-off) charge alendar (e.g. daily usage charge) Volume (outgoing) based charge Volume (incoming) based charge Volume (total volume) based charge The actual value used for harged Item by a VPN is at their discretion and dependent on the tariff applied. The use of within a ontent Transaction is for use where none of the other values are more appropriate, e.g. if content is charged by data volume then one of V, W or X must be used. all/event type Valid values ircuit switched O and T calls SS O and SS T and WLAN Location Services Service entre Usage ontent Service Supplementary Service (including USSD) E A, D, F E A, D, F, L, V, W, X E D, E, F, L, D, F, L, V, W, X Information relating to equipment used by the harged Party for the ontent Transaction. The group, when present, must contain items Equipment Id Type and Equipment Identifier. Present within group harged Party Information where available. Information identifying the home environment of the harged Party. The group when present must contain items Home Id Type and Home 3.11.05 Page 72 of 217 30 31 ontext ontent ontent andatory item Equipment Id Type missing within group. andatory item Equipment Id missing within group. 30 ontent andatory item Home Id Type missing within group.

ode Identifier. This information is not required when the Home and Recipient are the same entity. One or more occurrences may be present within group harged Party Information where available. ontext 31 ontent andatory item Home Identifier missing within group. harged Party Id Type An item identifying the type of harged Party Identifier. andatory within group harged Party Identification. ontent ontent Value out of range. harged Party Identification Values: 1 SISDN 2 ISI 3 IN (obile Identification Number) 4 IP Address v4 5 IP Address v6 6 Login Name e.g. gcggenomp 7 Account Number e.g. A00376 8 E-mail Address e.g. Generic.Person@Domain.com The identification of the subscriber being charged for the transaction. The group must contain items harged Party Id Type and harged Party Identifier. The group must contain sufficient information for the Recipient to be able to uniquely identify the harged Party. 30 31 ontent ontent andatory item harged Party Id Type missing within group. andatory item harged Party Identifier missing within group. One or more occurrences must be present within group harged Party Information. harged Party Identifier The item holds an identifier for the harged Party. The identifier may only be unique in conjunction with other information within the harged Party Information, e.g. IN & ESN, SISDN & TADIG ode. ontent ontent Value out of range and item is a SISDN. 3.11.05 Page 73 of 217

ode harged Party Information harged Party Location harged Party Status The type of identifier is contained in the associated harged Party Id Type. andatory within group harged Party Identification. Information relating to the harged Party. The group must contain at least one occurrence of group harged Party Identification. Additional information conditionally available may include harged Party Home Identification, harged Party Location and harged Party Equipment. andatory within group ontent Transaction. Information on the geographical location of the harged Party at the time of ontent Transaction request. This information may not be available or relevant, e.g. where the content is timer requested (e.g. weekly). Availability of this information may also be subject to local regulatory rules/laws. ust be present within group harged Party Information where available. Indicates whether the chargeable subscriber is the originating or terminating party. andatory within group SU Basic Information. 0 ontext ontent Item content does not match harged Party Id Type. 0 ontent Item is an ISI of a known network operator and initial characters are different from the network operator s + N, or not as as bilaterally agreed. 30 ontent andatory group harged Party Identification missing within group. 30 31 ontent ontent SU SU andatory item Location Id Type missing within group. andatory item Location Identifier missing within group. Value out of range. harged Units Values: 0 Originating 1 Terminating The harged Units item indicates the rounded number of units which are actually charged for within the harge Detail occurrence. alls 3.11.05 Page 74 of 217

ode This value may not correspond to the number of hargeable Units as it represents the charged units given the pricing unitisation/segmentation, e.g. first segment minimum 60 seconds charged followed by 30 second unit charge. The item harged Item defines what the units represent. The item content reflects the rounded charged not chargeable units. harged Units must be presented in the same unitisation as the corresponding hargeable Units. ontext alls Value out of range. Examples: for Duration charge Actual duration is 73 seconds all charged in 30 second units (i.e. 90 seconds) harged Units contains 90 hargeable Units contains 73 for volume charge Actual message length is 17 characters essage charged in character units (i.e. characters) harged Units contains hargeable Units contains 17 A volume based charge indicates that the field represents a Data Volume or, in the case of Service entre Usage, essage Length. Optionality: Transfer is at the discretion of the Sender PN. ust be present within group harge Detail where hargeable 3.11.05 Page 75 of 217

ode Units is present (subject to optionality). ontext harging ID Values: > or = 0 A charging identifier which can be used together with GGSN address to identify all records produced in SSGN(s) and GGSN involved in a single PDP context. Value out of range. For WLAN networks this item can be used together with the WLAN billing record recording identity to identify all records involved in a single WLAN session. Derivation: GS item hargingid (3GPP TS 32.015). For WLAN networks the derivation is at the discretion of the Sender. Note that harging Id must remain unique (together with the recording entity) during a significant amount of time. andatory within group Basic all Information Range: 0 4294967295 (derived from 0 to 2^32) harging Point An indicator detailing which of the two timestamps, Deposit or ompletion, was used for tariffing purposes, i.e. the harging Point. SU SU Value out of range. andatory within group SU Timestamps. Values: ompletion Timestamp D Deposit Timestamp harging Timestamp The timestamp showing the start of the harge Information. This item will be present where it is not the same as an associated all Event Start Timestamp or where there is no such associated timestamp. alls alls Value out of range. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode 3.11.05 Page 76 of 217 30 alls andatory associated item UT Time Offset ode missing.

ode associated with the timestamp. Note that local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. Derivation: GS item answertime or seizuretime (3GPP TS 32.005). The actual derivation will be dependent upon the charging principles used by the Sender and as defined by their IOT. andatory within groups 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 LS Request Timestamp. 0 1 0 ontext O T LS SS LS harging Timestamp is later than end of call (all Event Start Timestamp plus Total all Event Duration). harging Timestamp is later than LS Request Timestamp plus Response Time. harging Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file. Within group Basic Service Used the timestamp will only be present where it is not the same as an associated all Event Start Timestamp. Format: YYDDHHSS LIR Status Indicator Indicates the LIR status of the call originator in the case of a obile Originated all (call forwarding context where Third Party Information is present), obile Terminated all or a Service entre Usage where the terminating party is the hargeable Subscriber. ust be present within groups O T SU O T SU Value out of range. all Originator 3.11.05 Page 77 of 217

ode Third Party Information where available. ust be present within group SU Basic Information where available and the harged Party Status indicates a terminating short message. ontext Values: 0 Presentation allowed 1 Presentation not allowed ommission ommission due to the Recipient. ontent This information will be present when commission is applied at a transaction level. ontent Value out of range. ommission must not contain a negative value. However, a negative value is implied when harge Refund Indicator is present. Taxes are not included in the commission. Taxation is not applicable to the commission. The charge is in the Advised harge urrency, or TAP urrency where no associated Advised harge urrency is present, or SDRs where neither is present. The number of decimal places is defined by item TAP Decimal Places. Present within group Advised harge Information when commission is applied at a transaction level. ompletion Timestamp Values: > = 0 The date/time when the service was completed, e.g. delivered, canceled, deleted, time expired. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode associated with the timestamp. Note that local time is the local time at the location of the chargeable 3.11.05 Page 78 of 217 11 21 SU SU SU SU Syntax error and charging point is D. Syntax error and charging point is. Value out of range and charging point is D. Value out of range and charging point is.

ode ontent harging Point ontent Provider subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. andatory within group SU Timestamps. Format: YYDDHHSS This item identifies which timestamp represents the charging point for this transaction. The item is only present where there is more than one timestamp present within ontent Transaction Basic Info. If there is only one timestamp present then that is deemed to be the charging point by default. Values: ust be present within group ontent Service Used where more than one timestamp is present within group ontent Transaction Basic Info. 1 Order Placed Timestamp 2 Requested Delivery Timestamp 3 Actual Delivery Timestamp A group giving information additional to the ontent Provider Name which identifies the ontent Provider. The group may be repeated to give as many identifiers as are available to the Sender. The group may not be present where either only the ontent Provider Name is known or the ontent Provider is the Sender. The group when present must contain items ontent Provider Id Type and ontent Provider Identifier. 30 31 0 11 21 0 30 31 ontext SU SU SU ontent ontent ontent ontent ontent ontent ontent andatory associated item UT Time Offset ode missing and charging point is D. andatory associated item UT Time Offset ode missing and charging point is. ompletion Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file. Syntax error and more than one timestamp present within ontent Transaction Basic Info. Syntax error and only one timestamp present within ontent Transaction Basic Info. Value out of range and more than one timestamp present within ontent Transaction Basic Info. Value out of range and only one timestamp present within ontent Transaction Basic Info. Referenced timestamp not present within associated group ontent Transaction Basic Info. andatory item ontent Provider Id Type missing within group. andatory item ontent Provider Identifier missing within group. 3.11.05 Page 79 of 217

ode ontext Present within group Serving Parties Information where available. ontent Provider Id Type An item identifying the type of ontent Provider Identifier andatory within groups ontent Provider 11 ontent LS ontent Syntax error Value out of range. LS SP Identification. 21 LS Value out of range. ontent Provider Identifier Values: 1 Name text representation, e.g. Amazon, Interflora, Yahoo! 2 TADIG code see items Sender/Recipient e.g. GBRVF, DEUD1 3 URL e.g. www.amazon.com 4 IP Address v4 5 IP Address v6 The item holds a unique identifier of the ontent Provider. The type of identifier is contained in the associated ontent Provider Id Type. 0 ontent ontent Item content does not match ontent Provider Id Type. andatory within groups ontent Provider 1 LS Item content does not match ontent Provider Id Type. LS SP Identification. ontent Provider Name This is the name of the ontent Provider as it may appear on a retail invoice, e.g. FT arket Watch. This name may not be the same as the trading name, e.g. Financial Times, London. 0 ontent ontent Syntax error Length greater than 24 characters. Values: andatory within group Serving Parties Information 3.11.05 Page 80 of 217

ode ontent Service Used Limited to maximum 24 characters length A group identifying the details of the actual transaction and associated charges. The group must contain an occurrence of each of ontent Transaction ode, ontent Transaction Type, Transaction Short Description and Transaction Identifier. All other items and groups are conditionally present with one or more occurrences of harge Information. andatory within group ontent Transaction. 30 31 32 33 ontext ontent ontent ontent ontent andatory item ontent Transaction ode missing within group. andatory item ontent Transaction Type missing within group. andatory item Transaction Short Description missing within group. andatory item Transaction Identifier missing within group. 34 ontent Item Object Type missing within group and Pull ontent Transaction ode used within Streaming ontent Transaction Type. 35 ontent Item Object Type missing within group and Pull ontent Transaction ode used within Download ontent Transaction Type. 0 ontent Total Data Volume value does not equal the sum of Data Volume Incoming + Data Volume Outgoing when all items are present within group. 1 ontent Total Data Volume and either Data Volume Incoming or Data Volume Outgoing present within group. 2 ontent Neither of groups harge Information or Advised harge Information present within group. 3 ontent onditional item ontent harging Point missing and more than one timestamp present 3.11.05 Page 81 of 217

ode ontent Transaction ontent Transaction Basic Info ontent Transaction represents the charging and transactional details for delivery of content to a customer. Usage of this element is by bilateral agreement between the Sender and Recipient. The group consists of mandatory groups ontent Transaction Basic Info, harged Party Information, Serving Parties Information and one or more occurrences of ontent Service Usage. Operator Specific Information may, optionally, be present one or more times. andatory within an occurrence of group all Event Details where none of the following are present: obile Originated all, obile Terminated all, Supplementary Service Event, Service entre Usage, all or Location Service. ontent Transaction Basic Info provides the basic detail of when the ontent Transaction was made and the result of the transaction. Group must contain one timestamp. This can be of any type, Order Placed Timestamp, Requested Delivery Timestamp, or Actual Delivery Timestamp. andatory within Group ontent Transaction. 30 31 32 33 30 31 32 ontext ontent ontent ontent ontent ontent ontent ontent within associated group ontent Transaction Basic Info. andatory group ontent Transaction Basic Info missing within group. andatory group harged Party Information missing within group. andatory group Serving Parties Information missing within group. andatory group ontent Service Used missing within group. No timestamp present within group. Item RAP File Sequence Number missing and ontent Transaction previously received and rejected. Item RAP File Sequence Number present and ontent Transaction not previously received and rejected. ontent Transaction ode A code representing the service that has been used. andatory within group ontent Service Used. 33 ontent ontent ontent Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). Value out of range. 3.11.05 Page 82 of 217

ode ontent Transaction Type Values: 0 Goods 1 Email 2 Push 3 Pull 4 Trade 5 Banking 6 Online Application 7 Instant essaging The type of ontent Transaction that has been used. The value of this item is dependent on the value of ontent Transaction ode. Values: andatory within Group ontent Service Used. 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 essage (applicable to Push, Pull) 9 Browse (applicable to Pull) ombined Send/Retrieve (applicable to Email) 11 Streaming (applicable to Pull) 12 Download (applicable to Pull) 13 Point to point (applicable to Instant essaging) 14 Point to multipoint (applicable to Instant essaging) 15 hat (applicable to Instant essaging and Online Appl.) 16 Presence Information (applicable to Instant essaging) 17 Online game (applicable to Online Appl.) ontext ontent ontent Value out of range. 3.11.05 Page 83 of 217

ode SE Information The information downloaded by the AEL server. Derivation: GS/UTS item Free Format Data (3GPP TS 32.5 & 3GPP TS 32.215). ust be present within group AEL Service Used where information has been downloaded. ontext alls urrency onversion Value: aximum 40 bytes, the value must be encoded in binary hexadecimal format as received from the AEL Server via the network, i.e. the data must not be modified in any way. The urrency onversion table consists of three mandatory elements, an Exchange Rate ode, a Number Of Decimal Places and associated Exchange Rate. For each hargeable Item the Exchange Rate is quoted as a code which can be looked up within this table to obtain the appropriate exchange rate. 30 31 Acctng Acctng andatory item Exchange Rate ode missing within group. andatory item Number Of Decimal Places missing within group. 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. odes are reusable from transfer to transfer. At least one occurrence must be present within group Accounting Information if one or more harge is greater than zero within the Transfer Batch, one occurrence being present for each unique Exchange Rate ode used within group harge Information. ustomer Id Type An item identifying the type of associated ustomer Identifier. 32 33 34 Acctng Acctng Acctng LS andatory item Exchange Rate missing within group. ore than one occurrence of group with same Exchange Rate ode where Number Of Decimal Places and/or Exchange Rate are not the same. ore than one occurrence of group with same Exchange Rate ode where Number Of Decimal Places and Exchange Rate are the same (i.e. duplicate urrency onversion table entry). LS Value out of range. 3.11.05 Page 84 of 217

ode Values: andatory within groups Tracking ustomer Identification Tracked ustomer Identification. 1 SISDN 2 ISI 3 IN (obile Identification Number) 4 IP Address v4 5 IP Address v6 6 Login Name e.g. gcggenomp 7 Account Number e.g. A00376 8 E-mail Address e.g. Generic.Person@Domain.com ontext where only values 1, 2 & 3 must be used within the group Tracked ustomer Identification. ustomer Identifier The item holds an identifier for the harged Party. The identifier may only be unique in conjunction with other information within the harged Party Information, e.g. IN & ESN, SISDN & TADIG ode. The type of identifier is contained in the associated ustomer Id Type. andatory within groups Tracking ustomer Identification 0 0 LS LS LS Value out of range and item is a SISDN. Item content does not match ustomer Id Type. Item is an ISI of a known network operator and initial characters are different from the network operator s + N, or not as as bilaterally agreed Tracked ustomer Identification. Data Interchange A TAP Data Interchange must contain either a Transfer Batch, 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 (lassification Of Errors). Data Volume The Data Volume Incoming identifies the number of incoming octets (bytes) 3.11.05 Page 85 of 217

ode Incoming within an occurrence of Service Used or ontent Service Used. Derivation: GS item datavolumedownlink (3GPP TS 32.015). For WLAN network usage items Acct-Input-Octets (RF 2866) and Acct-Input-Gigawords (RF 2869). andatory within group Service Used. Present within group ontent Service Used when available. ontext ontent ontent Value out of range. Data Volume Outgoing Values: > or = 0 (zero) The Data VolumeOutgoing identifies the number of outgoing octets (bytes) within an occurrence of Service Used or ontent Service Used. ontent Derivation: GS item datavolumeuplink (3GPP TS 32.015). ontent Value out of range. For WLAN network usage items Acct-Output-Octets (RF 2866) and Acct-Output-Gigawords (RF 2869). andatory within group Service Used. Present within group ontent Service Used when available. Default all Handling Indicator Values: > or = 0 (zero) Indicates whether or not a AEL call encountered default handling. Derivation: O T For non SS GS AEL calls: GS item DefaultallHandling (GS 32.005 and 29.002). O T Value out of range. 3.11.05 Page 86 of 217

ode For non SS AEL calls: GS item Default-Handling (GS 32.015 and 29.002). For all SS AEL calls: GS item DefaultSS-Handling (GS 32.015 and 29.002). ust be present within group AEL Service Used where the call has encountered default call handling. ontext Deposit Timestamp Values: 0 ontinue the call 1 Release the call The date/time when the message was deposited at the Service entre. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode associated with the timestamp. Note that local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. andatory within group SU Timestamps. Format: YYDDHHSS 11 21 30 31 SU SU SU SU SU SU Syntax error and charging point is. Syntax error and charging point is D. Value out of range and charging point is. Value out of range and charging point is D. andatory associated item UT Time Offset ode missing and charging point is. andatory associated item UT Time Offset ode missing and charging point is D. Destination The Destination indicates the number dialled by the subscriber (alled Number) or the SS Address in case of SS usage or in cases involving supplementary services such as call forwarding or transfer etc., the number to 0 SU Deposit Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file. 39 O Neither item alled Number nor item Dialled Digits present within call and call does not represent an emergency call. 3.11.05 Page 87 of 217

ode which the call is routed. The element contains additional optional information detailing the geographical destination of the call and, where available and appropriate, Dialled Digits and SS Destination Number. ust be present within group O Basic all Information except where there is no number present on the air interface, e.g. emergency calls. 40 41 42 ontext O O O Item alled Number contains only country code and item Dialled Digits not present Item alled Number not present and all Type 1 indicates an international call and item AEL Destination Number not present. alled Number not present and call represents SS usage. Destination Network The network towards which the call or message is routed. ust be present within group O Basic all Information where optimal routing is used. SU O SU O Note: Error codes 31, 32, 33, 34, and 35 removed in TAP release 3. (01 ay 03). Note: Error odes 30, 37 & 38 removed in TAP release 3.11 (01 ay 05). Value out of range. ust be present within group SU Basic Information where available except where a short message has not been delivered. Dialled Digits The full list of codes in use are given in TADIG PRD TD.13: PN Naming onventions. e.g. GBRN GBRVF DEUD1 DEUD2 ellnet Vodafone D1 D2 Privat The dialled digits item contains the actual digits as dialled by the subscriber, i.e. unmodified, in establishing a call. This will contain + and # where appropriate. The Dialled Digits item should contain everything the subscriber has entered before the send button is pushed (for example, pre-entered menu selections 3.11.05 Page 88 of 217 O O Value out of range.

ode Discount Applied Discount ode Discount Information for voicemail). For emergency calls operators may optionally insert the digits 112 or their national emergency number into the Dialled Digits. Values: ust be present within group Destination when available from the network. Each digit is numeric (0-9) or contains, or Discount Applied is one of Fixed Discount Value or Discount Rate. andatory within group Discounting. A code associated with the Discount Applied. Values: andatory within groups Range 0.. 99 Discounting Discount Information. Information identifying any call level discounts given via a discount agreement between the Sender and Recipient. A Discount ode must be present Where the Discount ode refers to a Discount Rate then the Discount Value and Discountable Amount must also be present, where the Discount ode refers to a Fixed Discount Value then the Discount Value and Discountable Amount must not be present. 30 31 11 2 0 30 31 32 ontext Acctng Acctng alls Acctng Acctng alls alls alls alls alls Neither of mandatory items Fixed Discount Value or Discount Rate present within group. Both of mandatory items Fixed Discount Value and Discount Rate present within group. Value out of range. Specified discount code was not defined in group Discount Applied. Referenced discount is not in line with roaming agreement. andatory item Discount ode missing within group. Item Discount Value missing within group and Discount ode refers to a Discount Rate. Item Discountable Amount missing within group and Discount ode refers to a Discount 3.11.05 Page 89 of 217

ode ust be present within group harge Information where discounts have been applied to the harge Information. ust be present within group AEL Service Used where discounts have been applied to the AEL Invocation Fee. ontext Rate. Discount Rate The rate of discount applied to harge Information where a percentage discount was applied as opposed to a fixed discount. The rate is held to 2 decimal places. Acctng Acctng Value out of range. andatory where no Fixed Discount Value present within group Discount Applied. Values: 0.00 thru 0.00 Discount Value Discountable Amount The actual value of a discount element applicable to harge Information where that discount is not a Fixed Discount Value. The Discount Value must be a positive value, i.e. greater than zero. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Values: ust be present within group Discount Information where the Discount ode refers to a Discount Rate. > 0 (zero) The actual part of the harge/tax/ael Invocation Fee to which the Discount Value and Discount Rate (ode) relate. The Discountable Amount must have a value greater than zero. 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 22 22 alls alls alls alls alls alls Value out of range. Where the associated Discount ode relates to a Discount Rate, the Discount Value does not correspond to the Discountable Amount and Discount Rate. Note: Rounding rules are at the discretion of the Sender and a tolerance must be allowed. A minimum tolerance of 0.02 units is recommended, independent of the number of TAP decimal places used for the TAP file. Value out of range. Discountable Amount is not in line with roaming agreement. 3.11.05 Page 90 of 217

ode Discounting Distance harge Band ode bilateral agreements, see TAP urrency. The Discountable Amount may include sum of all tax values, charges and AEL invocation fees or any part thereof. Values: ust be present within group Discount Information where the associated Discount ode releates to a Discount Rate. > 0 (zero) A table containing discount information where the discount is applied at call level, as defined by a discount agreement between the Sender and Recipient. 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. odes are reusable from transfer to transfer. andatory within group Accounting Information where group Discount Information is present within harge Information. One occurrence must be present for each unique Discount ode used within group Discount Information. A code corresponding to a group of countries where a specific tariff is applied. The correspondence between a value and a specific group of countries, and hence tariff, is defined by the Sender PN. The list of the countries for each area must be defined by the charging operator and specified in the SS bilateral agreement. ust be present within group SU harge Type where distance has been a parameter used to calculate the harge. 30 31 32 33 ontext Acctng Acctng Acctng Acctng SU SU andatory group Discount Applied missing within group. andatory item Discount ode missing within group. ore than one occurrence of group with same Discount ode where group Discount Applied is not the same. ore than one occurrence of group with same Discount ode where group Discount Applied is the same (i.e. duplicate Discounting table entry). Value out of range. 3.11.05 Page 91 of 217

ode Earliest all Timestamp Values: A Area A B Area B Area etc. The Earliest all Timestamp is, as it implies, the earliest start of charging timestamp on any record. It is not necessarily the start of charging timestamp of the first charge record on the file. The timestamp contains the same timestamp as that of the earliest all Event Details when all times have been normalised to UT time. Where the batch contains SU records either the completion or deposit timestamp must be taken into account according to the charging point value. When the batch contains ontent Transaction call/events the ontent harging 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. Timestamps from calls with severe errors must also be taken into account if possible i.e. no type or 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 UT Time Offset associated with the timestamp. Optionality: Transfer is at the discretion of the Sender PN. andatory within group Audit ontrol Information subject to optionality. 30 0 ontext Audit Audit Audit Audit Value out of range. andatory associated item UT Time Offset missing. The timestamp does not match the timestamp of the earliest all Event Detail Timestamp. Equipment Id Format: YYDDHHSS An item that uniquely identifies the equipment used by the harged Party. ontent The type of identifier is contained in the associated Equipment Id Type. 0 ontent LS Item content does not match Equipment Id Type. 3.11.05 Page 92 of 217

ode andatory within groups harged Party Equipment Tracking ustomer Equipment Tracked ustomer Equipment. ontext Equipment Id Type An item representing the type of Equipment Id. andatory within groups harged Party Equipment. ontent LS ontent LS Value out of range. Tracking ustomer Equipment Tracked ustomer Equipment Equipment Identifier Values: 0 IEI 1 ESN A conditional group element which identifies the equipment used. The information present must be one of either IEI or ESN. andatory within groups Supplementary Service Event obile Originated all obile Terminated all 30 31 O T SS O T SS Both mandatory items IEI and ESN present within group. Neither mandatory items IEI or ESN present within group. all where available from the network. ESN The Electronic Serial Number. The identifier which uniquely identifies the O T 3.11.05 Page 93 of 217

ode Exchange Rate Exchange Rate ode equipment used by the subscriber during the call. This is a non GS equipment identifier. Derivation: IBER manual v2.0 section 12. ust be present within group Equipment Identifier where available. Will not be present where the terminal equipment is not involved in the call e.g. in forwarded call cases or the mobile equipment is identified by an IEI. The Exchange Rate is the exchange rate expressed as the number of units of Local urrency to one unit of the currency used in the TAP file. Note that, while SDR is usually the currency used in the TAP file, the currency may be different based on bilateral agreement and, where so agreed, will be indicated by the currency code in the TAP urrency element, see TAP urrency. For information on how exchange rates are calculated see PRD BA.11. The number of decimal places present are indicated by the associated Number Of Decimal Places item. andatory within group urrency onversion. A code associated with an Exchange Rate. Example andatory within group urrency onversion. ust be present within group harge Information where a harge greater than zero is present within any harge Detail associated with the same harge Information. ust be present within group AEL Service Used where the AEL Invocation Fee is greater than 0 (zero). 0 11 1 2 ontext SS O T SS Acctng Acctng Acctng alls alls Acctng alls Value out of range. Syntax error Exchange Rate less than expected and referenced by one or more all Event Details. Syntax error Specified Exchange Rate ode not defined in group urrency onversion. Value out of range. The Exchange Rate referenced by Exchange Rate ode in all Event Details is greater than expected. 3.11.05 Page 94 of 217

ode In order to calculate the SDR value in TAP the local currency is divided by the exchange rate. 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 expected). The SDR amount will be higher and the VPN actually overcharge the HPN, especially if netting is in place. In case the amount of local currency is divided by an exchange rate holding a higher value (i.e. the exchange rate is greater than expected). The SDR amount will be lower and the VPN actually undercharge the HPN, especially if netting is in place. ontext Note: Error code 0 removed in TAP release 3.11 (01 ay 05). File Available Timestamp Values: Range 0.. 99 The date and time at which the file was made available to the Recipient PN. Physically this will normally be the timestamp when the file transfer commenced to the Recipient PN, i.e. start of push, however on some systems this will be the timestamp when the file was made available to be pulled. 11 21 Btch trl Notifictn Btch trl Notifictn Value out of range. Value out of range. The time is given in the local time of the Sender PN. There must be a UT Time Offset associated with the item. Note that where a file is being resubmitted, e.g. where the file contained a fatal error on earlier submission, this timestamp must not contain the original timestamp, i.e. the item contains the timestamp when the file was made available on resubmission. andatory within groups 30 31 0 Btch trl Notifictn Btch trl andatory associated item UT Time Offset missing. andatory associated item UT Time Offset missing. Timestamp is earlier than the Transfer ut Off Timestamp. Batch ontrol Information Notification 1 Btch trl Timestamp is earlier than the File reation Timestamp. Format: YYDDHHSS 2 Notifictn Timestamp is earlier than the Transfer ut Off Timestamp. 3.11.05 Page 95 of 217

ode 3 ontext Notifictn Timestamp is earlier than the File reation Timestamp. 4 Btch trl Timestamp is after the file received time at the HPN File reation Timestamp The timestamp at which the TAP file was created. The time is given in the local time of the Sender PN. There must be a UT Time Offset associated with the item. Optionality: 5 Notifictn Notifictn Btch trl Notifictn Btch trl Timestamp is after the file received time at the HPN Value out of range. Senders may choose not to supply this information. andatory within groups Notification Batch ontrol Information 30 0 Notifictn Btch trl Notifictn Btch trl andatory associated item UT Time Offset missing. Timestamp is earlier than the Transfer ut Off Timestamp. File Sequence Number subject to optionality. Format: YYDDHHSS A unique reference which identifies each TAP Data Interchange sent by one PN to another, specific, PN. Notifictn Btch trl The sequence commences at 1 and is incremented by one for each subsequent TAP Data Interchange sent by the Sender PN to a particular Recipient PN. Separate sequence numbering must be used for Test Data and hargeable Data. Having reached the maximum value (99999) the number must recycle to 1. Note that in the case of retransmission for any reason this number is not incremented. 0 0 Notifictn Btch trl Notifictn Btch trl Notifictn Btch trl Value out of range. The item does not match the File Sequence Number on the filename. File sequence number of the received file is greater than that expected. 3.11.05 Page 96 of 217

ode Note that where the file sequence number is being reused with a file already received and successfully processed and the content of the two files is different, then the received file is to be considered as invalid reused sequence number and rejected using the RAP process. Where the content of the two 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). ontext 1 Notifictn Btch trl File sequence number of the received file has already been received and successfully processed and the file is not a copy of the original file. andatory within groups File Type Indicator Range: Notification Batch ontrol Information. 00001 99999 for Test Data 00001 99999 for hargeable Data Indicates the type of data contained within the file, i.e. test or chargeable data. Btch trl Notifictn Note: some values are reserved for proprietary use on internal interfaces, these values are considered out of range unless bilateral usage is agreed. Btch trl Notifictn Value out of range. Present within groups Notification Batch ontrol Information where the file represents test data only, not present where the data is live chargeable data. Values: T Test Data [Values B, H, S and V are reserved for proprietary use] Fixed Discount Value The value of a fixed discount applied to a all Event Details. The Fixed Discount Value must contain a positive value. Acctng Acctng Value out of range. The value is in SDRs with the number of decimal places defined by item 3.11.05 Page 97 of 217

ode TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. andatory where no Discount Rate present within Discount Applied. ontext Fixed Network User Rate Values: > 0 (zero) The Fixed Network (e.g. PSPDN) User Rate. Derivation: Bearer apability Element, octet 6d, (3GPP TS 44.008). The value is derived by interpreting the 5 least significant bits of octet 6d as a binary number and converting it into an integer. O T O T Value out of range. ust 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. Geographical Location Values: 1 9.6 kbits per second 2 14.4 kbits per second 3 19.2 kbits per second 4 28.8 kbits per second 5 38.4 kbits per second 6 48 kbits per second 7 56 kbits per second 8 64 kbits per second Identifies the Geographical Location of the terminal equipment. All of the information within the group is optional (except for WLAN network usage as described under onditionality below) and may not be available where the terminal was not involved in the call, e.g. call forwarding scenarios. 30 31 O T SS O Item Serving Location Description is not present and Serving BID is present within group. Serving BID missing within group but 3.11.05 Page 98 of 217

ode Operators may bilaterally agree to make transfer of Serving BID and/or Serving Location Description mandatory. ust be present within group Location Information if the call involves the terminal equipment or if the Serving Network is different from the Sender. ust be present within group Location Information where available or if the Serving Network is different from the Sender. ust be present within group Location Information for WLAN network usage. 32 33 ontext T SS O T SS expected in accordance with roaming agreement. Serving Location Description missing within group but expected in accordance with roaming agreement. Item Serving Location Description not present for WLAN network usage. Basic all Information Basic all Information provides the basic detail to identify the chargeable subscriber together with other core information. 30 andatory group hargeable Subscriber missing within group. It comprises mandatory hargeable Subscriber, Destination, all Event Start Timestamp, Total all Event Duration and harging Id details together with conditional RAP File Sequence Number, Network Init. PDP ontext, Partial Type Indicator and ause For Termination information. 31 32 all is being resubmitted and RAP File Sequence Number is missing within group. andatory group Destination missing within group. andatory within group all. 33 andatory item all Event Start Timestamp missing within group. 34 andatory item Total all Event Duration missing within group. 35 andatory item harging Id missing within group. 38 Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). 41 Item RAP File Sequence Number present and 3.11.05 Page 99 of 217

ode ontext call not previously received and rejected. 42 Item Network Init. PDP ontext present within group and WLAN network usage. all all is used to represent GS General Packet Radio Service () and UTS packet switched service usage. It consists of the mandatory information Basic all Information, Location Information, and Service Used. Equipment Identifier will be present where available. Optionally Operator Specific Information may be supplied. 31 32 Note: Error codes 36 & 37 removed in TAP release 3. (01 ay 03). Note: Error codes 39 & 40 removed in TAP release 3.11 (01 ay 05). andatory group Basic all Information missing within group. andatory group Location Information missing within group. This call event is also used for WLAN network usage. Where AEL services are supported and invoked then one occurrence of AEL Service Used will be present for the invocation. andatory within an occurrence of group all Event Details where none of the following is present; obile Originated all, obile Terminated all, Supplementary Service Event, Service entre Usage, ontent Transaction or Location Service. 34 0 andatory group Service Used missing within group. Number of partials received exceeds limit defined by BARG in BA.12. Note: Error codes 30, 35 & 1 removed in TAP release 3.11 (01 ay 05). hargeable Subscriber Identifies the chargeable subscriber for the use of. Group hargeable Subscriber and items PDP Addressand Network Access Identifier are all conditional. One of either group hargeable Subscriber or item Network Access Identifier must be present. andatory within group Basic all Information. 30 32 34 Item hargeable Subscriber missing within group and the all is not representing a WLAN network usage. Item PDP Address missing within group and all does not represent a WLAN session. Neither item Network Access Identifier nor group hargeable Subscriber present within group. 3.11.05 Page 0 of 217

ode ontext 35 Item Network Access Identifier present within group and the all is not representing WLAN network usage. Destination Identifies the Access Point Name (Network Identifier and Operator Identifier parts). Location Information Within Basic all Information this item must always contain the actual connected APN. In case of AEL invocation an additional instance of Destination may be present within group AEL Service Used. Where relevant it must be populated with the original APN as entered by the customer where it is available from the network. Derivation: In case of usage, the actual connected APN NI/OI as defined in 3GPP TS 32.215. In case of relevant to AEL usage: 1. The actual connected APN NI/OI as modified by the SE in APN NI/OI fields as defined in 3GPP TS 32.215. 2. The original APN NI/OI before modification by the SE in AEL APN NI/OI fields within AEL Information as defined in 3GPP TS 32.215. andatory within group Basic all Information. ust be present within group AEL Service Used where the Destination has been modified by the AEL server when available from the network. The Location Information identifies the Network Location, where appropriate, the Geographical Location and, optionally, the Home 30 31 32 34 Note: Error codes 31 & 33 removed in TAP release 3.11 (01 ay 05). andatory item Access Point Name NI missing within group. Item Access Point Name OI missing within group. Note, this validation is only applicable where the serving network has upgraded to at least GS Release 98. Note that this validation is not applicable to WLAN network usage. Item Access Point Name OI present within group for WLAN network usage. andatory item Access Point Name NI missing within group where it occurs within group 3G AEL Destination. Note: Error code 33 removed in TAP release 3.11 (01 ay 05). 30 andatory group Network Location missing within group. 3.11.05 Page 1 of 217

ode Network Location Location Information. andatory within group all. Identifies the mandatory GGSN Address and SGSN Address(es) using Recording Entity odes (see Recording Entity ode). Location Area ode is present where available and ell Identity is optionally present when available. For WLAN network usage this group will contain one Recording Entity ode for WLAN billing information recording entity. andatory within group Location Information. ontext 31 Group Geographical Information missing for WLAN network usage. 31 32 33 ore than one Recording Entity ode is of type GGSN present within group. No Recording Entity ode of type GGSN present within group and not WLAN network usage. No Recording Entity ode of type SGSN present within group and not WLAN network usage. Service Used The Service Used group identifies the Data Volume Incoming and Outgoing together with harging Information. Presence of the IS Signalling ontext will identify where the context represents IS signalling only. andatory within group all. 34 35 36 37 32 33 34 For WLAN network usage, no Recording Entity ode of type WLAN billing information recording entity present within group. For WLAN network usage, more than one Recording Entity ode present within group. For WLAN network usage, item Location Area ode present within group. For WLAN network usage,item ell Identity present within group. andatory group harge Information missing within group. andatory item Data Volume Incoming missing within group. andatory item Data Volume Outgoing missing within group. 3.11.05 Page 2 of 217

ode ontext GS hargeable Subscriber Guaranteed Bit Rate Home BID A group containing ISI and/or SISDN details of the SU hargeable Subscriber. The group must contain either one of ISI or SISDN but it will contain both where they are both available. ust be present within group SU hargeable Subscriber where IN is not present. Describes the bitrate the UTS bearer service must guarantee to the user or application for circuit switched UTS. Derivation: Values: 3GPP TS32.305 item Guaranteed Bit Rate andatory within group Basic Service where available from the network. 1 14400bps 2 28800bps 3 300bps 4 33600bps 5 56000bps 6 57600bps 7 64000bps The Home BID (Billing Identifier) is a code identifying the home market area of the hargeable Subscriber. Derivation: IBER manual v2.0 section 12. Note: Error code 30 removed in TAP release 3.11 (01 ay 05). 30 SU Neither ISI or SISDN present within group. O T O T alls alls Syntax Error. Value out of range. Value out of range. 3.11.05 Page 3 of 217

ode andatory within group Home Location Information. ontext Home Id Type This item gives the type of Home Identifier associated with it. andatory within groups harged Party Home Identification ontent LS ontent LS Value out of range. Tracking ustomer Home Id Tracked ustomer Home Id. Home Identifier Values: 1 Name text representation, e.g. BT, Telecom Italia, ommerzbank 2 TADIG code see items Sender/Recipient e.g. GBRVF, DEUD1 3 Home BID see item Home BID 4 Home Location Description see item Home Location Description The item holds a unique identifier of the harged Party s Home. This may be, for example, a mobile network, fixed network, banking institution etc. The type of identifier is contained in the associated Home Id Type. 0 ontent ontent LS Item content does not match Home Id Type. andatory within groups harged Party Home Identification Tracking ustomer Home Id Tracked ustomer Home Id. Home Location Description A text description giving the home market area of the hargeable Subscriber. Derivation: IBER manual v2.0 section 12. alls 3.11.05 Page 4 of 217

ode andatory within group Home Location Information. ontext Home Location Information Home Location Information is an optional group which, when present must contain a Home BID and Home Location Description. 30 all andatory item Home BID missing within group. Optionality: Optional within groups 31 all andatory item Home Location Description missing within group. Location Information Location Information at the discretion of the Sender PN. Horizontal Accuracy Delivered The horizontal accuracy delivered for an LS request measured in metres. Derivation: GS/UTS item Ext-GeographicalInformation (TS 29.002, TS 32.005). The contents of the first octet indicates the 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 formulas referenced in TS 23.032. The result must be rounded to full metres. ust be present within group LS QoS Delivered where available from the network. Horizontal Accuracy Requested The horizontal accuracy requested for an LS request measured in metres. Derivation: LS QoS IE Octet 4 (3GPP TS 49.031). 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 formulas referenced in 3GPP TS 23.032. The resulting value needs 3.11.05 Page 5 of 217

ode to be rounded to full metres. Note that TS 23.032 specifies different formulas for the calculation of the horizontal and vertical accuracy in metres. ust be present within group LS QoS Requested where available from the network. ontext HSSD Indicator This indicator, set by the VPN and passed to the Recipient, indicates that HSSD has been used. O T ust be present within group Basic Service Used where HSSD has been used, otherwise not present. O T Value out of range. IEI Values: 1 HSSD used The International obile Equipment Identity number. The identifier which uniquely identifies the equipment used by the subscriber during the call. Derivation: GS item IEI (3GPP TS 32.005). ust be present within group Equipment Identifier where available. Will not be present where the terminal equipment is not involved in the call e.g. in forwarded call cases or the mobile equipment is identified by an ESN. O T SS O T SS Value out of range. IS Signalling ontext Defined in 3GPP TS 23.003 Note that whilst the IEI is 16 digits in length, the check digit is not currently transmitted on the air interface. Where the context represents IS signalling this identifier will be present. 3.11.05 Page 6 of 217 Value out of range.

ode The item will not be present on the network DR where the context is mixed IS signalling and customer generated data volume exchange. The item will only be present on the network DR where the context is representing solely IS signalling usage. When the item is present on the DR it is present as a null item. Derivation: 3GPP TS 32.215 item IS Signalling ontext (defined from R5 onwards). ontext andatory within group Service Used where available from the network. ISI Values: DR value TAP value null 1 The identifier which uniquely identifies the subscriber who has used the network and is liable for any charges that may be incurred. If the identification of the subscriber is with Network Access Identifier or the SISDN in WLAN usage, this item must contain characters equal to the Home PN s +N or the full ISI if available. If the recipient has not been allocated a and N (e.g., is not a GS operator), this field is defined bilaterally between sender and recipient. 0 alls alls alls Value out of range. First characters are different from home operators + N, or not as bilaterally agreed (e.g., if the recipient has not been allocated a and N). Derivation: GS item servedisi (3GPP TS 32.005). andatory within group hargeable Subscriber when IN not present. ust be present within group GS hargeable Subscriber when available. ust be present for WLAN usage when the ISI is used for 3.11.05 Page 7 of 217

ode identifying the chargeable user. ontext Internet Service Provider ISP Id Type ISP Identifier Latest all Timestamp Defined in 3GPP TS 23.003 Where an Internet Service Provider (ISP) has been used to access the service, i.e. initiate the ontent Transaction, then this repeating group contains identifying information. Present within groups Serving Parties Information LS SP Information where available. This item gives the type of Internet Service Provider (ISP) Identifier associated with it. Values: andatory within group Internet Service Provider. 1 Name text representation, e.g. AOL, Vizzavi 2 TADIG code see items Sender/Recipient e.g. GBRVF, DEUD1 3 URL e.g. www.aol.co.uk, www.vizzavi.co.uk 4 IP address v4 5 IP address v6 The item holds a unique identifier of the Internet Service Provider (ISP). The type of identifier is contained in the associated ISP Id Type. andatory within group Internet Service Provider. The Latest all Timestamp is, as it implies, the Latest start of charging timestamp on any record. It is not necessarily the start of charging 30 31 32 33 21 0 1 ontent ontent LS LS ontent ontent LS ontent ontent LS andatory item ISP Id Type missing within group. andatory item ISP Identifier missing within group. andatory item ISP Id Type missing within group. andatory item ISP Identifier missing within group. Value out of range. Value out of range. Audit Item content does not match ISP Id Type. Item content does not match ISP Id Type. 3.11.05 Page 8 of 217

ode timestamp of the last charge record on the file. ontext Audit Value out of range. The timestamp contains the same timestamp as that of the latest all Event Details when all times have been normalised to UT time. In case the batch contains SU records either the completion or deposit timestamp should be taken into account according to the charging point value. 30 0 Audit Audit andatory associated item UT Time Offset missing. The timestamp does not match the timestamp of the latest all Event Detail Timestamp. When the batch contains ontent Transaction call/events the ontent harging 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. Timestamps from calls with severe errors should also be taken into account if possible i.e. no or 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 UT Time Offset associated with the timestamp. Optionality: Transfer is at the discretion of the Sender PN. andatory within group Audit ontrol Information subject to optionality. Format: YYDDHHSS LS QoS Delivered The group identifies the quality of service delivered where it is different from the quality of service requested, as identified in group LS QoS Requested. 30 LS Item LS Transaction Status present and no other items present within group. All of the items within the group are subject to conditionality. Present within group Location Service Usage where the delivered service is not as requested. 31 LS Item Age Of Location missing from group and LS Transaction Status contains last known location. 3.11.05 Page 9 of 217

ode LS QoS Requested LS Request Timestamp LS SP Identification LS SP Information The group identifies the quality of service requested. The LS Request Timestamp must be present. All other items are present where available. andatory within group Location Service Usage. The timestamp identifying the requested service usage. The item is normally in the local time of the Sender (or Serving Network where this is not the Sender). There must be an associated UT Time Offset ode. andatory within group LS QoS Requested. Group containing identification of the location service content provider (LS SP). The group comprises two mandatory items, ontent Provider Id Type and ontent Provider Identifier. One or more occurrences must be present within group LS SP Information. This is a group containg the information to identify the Location Service ontent Provider (LS SP) and how they have accessed the network. There must be at least one occurrence of group LS SP Identification present. Groups Internet Service Provider and Network must be present where the information is available. ust be present within group Location Service where the LS SP can be identified. 3.11.05 Page 1 of 217 ontext 30 LS Item LS Request Timestamp not present within group. 30 30 31 LS LS LS LS Value out of range. andatory item UT Time Offset ode missing. andatory item ontent Provider Id Type missing within group. andatory item ontent Provider Identifier missing within group. 30 LS andatory group LS SP Identification missing within group.

ode LS Transaction Status The status of the LS transaction. Derivation: The value failure must be set, if the GS/UTS item PositionethodFailure-Diagnostic (TS 29.002) indicates a failure of processing the LS request within the serving network of the tracked or requesting subscriber subscriber. The value last known location must be set, if the GS/UTS item LocationEstimateType (3GPP TS 29.002) indicates this. The value last known location must override the value failure. The value denied must be set if the LS client is not authorised. I.e. the request is denied by the HPN of the tracked subscriber. ust be present within group LS QoS Delivered for non successful LS transactions. ontext LS Value out of range. Local urrency Values: 1 last known location 2 failure 3 denied ontains the urrency ode which identifies the currency used to price the calls and/or events prior to conversion to SDRs and therefore used in Exchange Rate. Acctng Acctng Value out of range. Note the use of SDRs may be subject to internal market bilateral agreements, see TAP urrency. 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 urrency was different. Derivation: 3.11.05 Page 111 of 217

ode ISO 4217 urrency odes standard. andatory within group Accounting Information. ontext Location Area ode Example: urrency ode AUD LP GBP urrency name Australian dollars hilean pesetas Pounds sterling Identification of the Location Area ode of the mobile equipment handling the call. Derivation: GS item locationareaode (3GPP TS 32.005). ust be present within groups Network Location Network Location except where not supported by the network or the call does not terminate at the equipment e.g. in call forwarding cases. O T SS O T SS Value out of range. Is not present for WLAN network usage. Location Id Type The Location Area ode is a two octet string as defined in 3GPP TS 44.008. For the TAP the octets are converted to a decimal integer number in the range 00000 to 65535. The leading zeros are significant. E.g. 0101001000 equates to 26160 01100000 equates to 39946 000000111001 equates to 04337 This item gives the type of location identifier associated with it. ontent andatory within groups ontent LS Value out of range. 3.11.05 Page 112 of 217

ode harged Party Location Tracked ustomer Location ontext Tracking ustomer Location. Location Identifier Values: 1 ountry text representation 2 ountry ITU E.164 representation e.g. 44 UK, 49 Germany 3 ountry ountry code e.g. DEU Germany, AN anada 4 Region text representation 5 Place text representation 6 IP location IP address v4 7 IP location IP address v6 8 TADIG code see items Sender/Recipient e.g. GBRVF, DEUD1 The item holds a unique identifier of the harged Party s location. The type of identifier is contained in the associated Location Id Type. 0 ontent ontent LS Item content does not match Location Id Type. andatory within groups harged Party Location Tracked ustomer Location Tracking ustomer Location. Location Information The location information identifies the Network Location, which includes the S responsible for handling the call and, where appropriate, the Geographical Location of the mobile. 30 O T SS andatory item Network Location missing within group. andatory within groups obile Originated all 31 O T SS Group Geographical Information missing but Serving BID expected in accordance with roaming agreement. This validation rule can be applied only where bilaterally agreed between Sender and 3.11.05 Page 113 of 217

ode Location Service Location Service Usage Supplementary Service Event obile Terminated all Location Service represents the charging and transactional details for use of the Location Service (LS) by a tracking customer. The group contains mandatory group Location Service Usage. One of groups Tracking ustomer Information or LS SP Information must be present. Group Tracked ustomer Information must be present where the tracked customer is not the tracking customer. Items all Reference and RAP File Sequence Number are present where available and applicable. Repeating item Operator Specific Information is optionally present. andatory within an occurrence of group all Event Details where none of the following are present; obile Originated all, obile Terminated all, Supplementary Service Event, Service entre Usage, ontent Transaction or all. Location Service Usage details the actual service quality requested and delivered together with the associated charging information. Group LS QoS Requested must be present with repeating group harge Information present at least once. andatory within group Location Service. ontext 32 O T SS 30 31 32 33 34 30 31 LS LS LS LS LS LS LS Recipient. Group Geographical Information missing but Serving Location Description expected in accordance with roaming agreement. This validation rule can be applied only where bilaterally agreed between Sender and Recipient. Neither of groups Tracking ustomer Information or LS SP Information present within group. andatory group Location Service Usage missing within group. Item RAP File Sequence Number missing and Location Service previously received and rejected. Item RAP File Sequence Number present and Location Service not previously received and rejected. Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error).. andatory group LS QoS Requested missing within group. andatory group harging Information missing within group. 3.11.05 Page 114 of 217

ode aximum Bit Rate The maximum bit rate available for circuit switched UTS. Derivation: 3GPP TS32.305 item aximum Bit Rate ontext O T O T Syntax Error. Value out of range. andatory within group Basic Service where available from the network. DN Values: 1 14400bps 2 28800bps 3 300bps 4 33600bps 5 56000bps 6 57600bps 7 64000bps obile Directory Number. This item supports wireless number portability within the North American market. Derivation: O T SS IBER manual v2.0 section. When a IN is present within group hargeable Subscriber then DN must be present, when available, associated with item IN. O T SS Value out of range. essage Description Note that privacy laws in some countries may restrict the DN availability. essage Description is a free format description of the Short essage Service used. It is mandatory but the content is entirely at the discretion of the network supplying the access to the service. The description must be in English. andatory within group essage Description Information. ess Desc 3.11.05 Page 115 of 217

ode essage Description ode essage Description Information essage Status A code used to cross reference the SU harge Type to the relevant description. andatory within group essage Description Information. andatory within group SU harge Type. A repeating table of pairs of essage Description and related essage Description ode. 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. odes are reusable from transfer to transfer. One occurrence must be present within Transfer Batch for each unique essage Description ode used within groupsu harge Type. The completion status of the message. andatory within group SU harge Type. 0 30 31 32 33 ontext ess Desc SU SU Tf Batch Tf Batch Tf Batch Tf Batch SU SU Specified message description code not defined in essage Description Information. andatory item essage Description ode missing within group. andatory item essage Description missing within group. ore than one occurrence of group with same essage Description ode where essage Description is not the same. ore than one occurrence of group with same essage Description ode where essage Description is the same. Value out of range. essage Type Values: 0 Unable to Deliver 1 Time Expired 2 Delivered / Succeeded 3 Deleted / anceled by SE 4 Deleted / anceled by Service entre Operators The type of service/message, e.g. fax, text. SU andatory within group SU harge Type. SU Value out of range. Values: 0 Text 1 Fax 3.11.05 Page 116 of 217

ode IN 2 Info obile Identification Number is an item which uniquely identifies the subscriber who has used the network and is liable for any charges that may be incurred. The IN is the mobile telephone number assigned by the HPN. The format of the number may conform to the North American Number Plan where it belongs to a North American operator. Derivation: IBER manual v2.0 section 12. andatory within group hargeable Subscriber when ISI not present. ust be present within group SU hargeable Subscriber when group GS hargeable Subscriber is not present. ontext alls alls Value out of range. O Basic all Information O Basic all Information provides the basic detail of who made the call and where to in respect of mobile originated traffic. 30 O andatory group hargeable Subscriber missing within group. It comprises mandatory hargeable Subscriber details together with conditional Destination, Destination Network, RAP File Sequence Number and ause For Termination information. 31 O andatory item all Event Start Timestamp missing within group. Where the call was initiated by the SI toolkit application the SI Toolkit Indicator flag will be present. 32 O andatory item Total all Event Duration missing within group. andatory within group obile Originated all. 33 O Item RAP File Sequence Number missing and call previously received and rejected. 34 O Item RAP File Sequence Number present and call not previously received and rejected. 35 O Group Destination missing and call is not for use of emergency service. 3.11.05 Page 117 of 217

ode ontext 36 O Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). obile Originated all obile Terminated all A obile Originated all item represents either tele or bearer service usage originated by the mobile subscription. In some cases the mobile itself may not be directly involved, e.g. some call forwarding scenarios. The obile Originated all must contain the O Basic all Information, Location Information and Basic Services Used. Note: There must be only one occurrence of the Basic Service Used group within this group even though the physical syntax indicates that this may be a repeating group. Where AEL services are supported and invoked then one occurrence of AEL Service Used will be present for the invocation. Where a supplementary service isused in conjunction with a call and itis deemed necessary for transfer (see Annex A) then Supplementary Service ode 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. Operator Specific Information may also be present, this is optional dependent on bilateral agreement. andatory within an occurrence of group all Event Details where none of the following are present; obile Terminated all, Supplementary Service Event, Service entre Usage, all, ontent Transaction or Location Service. A obile Terminated all item represents either tele or bearer service usage terminated by the mobile subscription. In some cases the mobile itself may 30 31 32 35 O O O O Note: Error codes 37 & 38 removed in TAP release 3.11 (01 ay 05). andatory group O Basic all Information missing within group. andatory group Location Information missing within group. andatory group Basic Service Used missing within group. ore than one occurrence of group Basic Service Used present within group. Note: Error codes 33 & 34 removed in TAP release 3.11 (01 ay 05). 30 T andatory group T Basic all Information missing within group. 3.11.05 Page 118 of 217

ode not be directly involved, e.g. some call forwarding scenarios. andatory elements are the T Basic all Information and the Basic Service Used. Only one basic service will be present and it will not be possible, for example, to distinguish between the data and speech parts of alternate services. Note: There must be only one occurrence of the Basic Service Used group within this group even though the physical syntax indicates that this may be a repeating group. Location Information and Equipment Identifier will normally be present except, for example, where the call does not terminate at the equipment e.g. call forward on no reply. Where AEL services are supported and invoked then one occurrence of AEL Service Used will be present for the invocation. Operator Specific Information may also be present, this is optional dependent on bilateral agreement. andatory within an occurrence of group all Event Details where none of the following are present; obile Originated all, Supplementary Service Event, Service entre Usage, all, ontent Transaction or Location Service. 31 32 35 ontext T T T andatory group Location Information missing within group. andatory group Basic Service Used missing within group. ore than one occurrence of group Basic Service Used present within group. Note: Error codes 33 & 34 removed in TAP release 3.11 (01 ay 05). SISDN The obile Subscriber ISDN number. Derivation: GS item SISDN (3GPP TS 32.005). It is represented in TAP in international format, i.e. the number begins with the country code related to the calling number. Defined in 3GPP TS 23.003 11 O T SS SU Syntax error and item SISDN not expected in accordance with roaming agreement. Syntax error and ISI not present or SISDN expected in accordance with roaming agreement. When an ISI is present within groups hargeable Subscriber or hargeable Subscriber then SISDN must be present, 12 SU Syntax error and ISI present and SISDN not expected in accordance with roaming agreement. 3.11.05 Page 119 of 217

ode T Basic all Information when available, associated with item ISI. ust be present within group GS hargeable Subscriber when available. ust be present when expected in accordance with roaming agreement. ust be present for WLAN network usage where the full ISI or Network Access Identifier not available. Note that privacy laws in some countries may restrict the SISDN availability. T Basic all Information provides the basic detail of who received the call and, conditionally, where from in respect of mobile terminated traffic. It comprises mandatory hargeable Subscriber details together with conditional all Originator, Originating Network, RAP File Sequence Number and ause For Termination information. Where the call was initiated by the SI toolkit application the SI Toolkit Indicator flag will be present. andatory within group obile Terminated all. 13 21 22 23 30 31 32 33 ontext O T SS O T SS SU SU O T SS T T T T Syntax error and item SISDN expected in accordance with roaming agreement. Number not represented in international format and SISDN not expected in accordance with roaming agreement. Number not represented in international format and ISI not present or SISDN expected in accordance with roaming agreement. Number not represented in international format and ISI present and SISDN not expected in accordance with roaming agreement. Number not represented in international format and SISDN expected in accordance with roaming agreement andatory group hargeable Subscriber missing within group. andatory item all Event Start Timestamp missing within group. andatory item Total all Event Duration missing within group. Item RAP File Sequence Number missing and call previously received and rejected. 3.11.05 Page 1 of 217

ode 34 35 ontext T T Item RAP File Sequence Number present and call not previously received and rejected. Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). Network Information relating to the Network used to access the service where the network is different to the Sender and is known. 30 ontent Note: Error codes 36, 37 & 38 removed in TAP release 3.11 (01 ay 05). andatory item Network Id Type missing within group. Present within groups 31 ontent andatory item Network Identifier missing within group. Serving Parties Information LS SP Information 32 LS andatory item Network Id Type missing within group. Network Access Identifier where available. The Network Access Identifier (NAI) is a username identifying a unique customer when generating WLAN DRs. The NAI (realm) must be a fully qualified domain name signifying the Home WLAN. 33 LS andatory item Network Identifier missing within group. Value out of range. Derivation: IETF RF 2486. andatory within group hargeable Subscriber where the ISI or SISDN is not available for identification of chargeable user. Format: username@realm 3.11.05 Page 121 of 217

ode Network Id Type Network Identifier e.g. pascal.leblanc@francnet.com This item gives the type of Network Identifier associated with it. Values: andatory within group Network. 1 Name text representation, e.g. BT, Telecom Italia 2 TADIG code see items Sender/Recipient e.g. GBRVF, DEUD1 3 Home BID see item Home BID 4 Home Location Description see item Home Location Description 5 APN Access Point Name 6 URL e.g. www.amazon.com The item holds a unique identifier of the Network. The type of identifier is contained in the associated Network Id Type. andatory within group Network. 21 0 1 ontext ontent ontent LS ontent ontent LS Value out of range. Value out of range. Item content does not match Network Id Type. Item content does not match Network Id Type. Network Information Network Information is a group of related information which pertains to the Sender PN. 30 Tf Batch andatory group UT Time Offset Information missing within group. It consists of the UT Time Offset Information table, which is mandatory and the Recording Entity Information table which must be present where Recording Entity odes are present within the TAP file. 33 Tf Batch Group Recording Entity Information missing within group. andatory within group Transfer Batch. Note: Error codes 31 & 34 removed in TAP release 3.11 (01 ay 05). Network Init. PDP ontext This item identifies where a all was initiated by the network and not the terminal equipment. Derivation Value out of range. 3.11.05 Page 122 of 217

ode 3GPP TS 32.015 data item NetworkInitiatedPDPontext. ust be present within group Basic all Information when the PDP context was initiated by the network, otherwise not present. Is not present for WLAN network usage. ontext Values: 1 Network initiated Network Location Identifies the location information relating to the network. It must have the S ode present, identifying the S handling the call and the all Reference will be present when available from the network. The Location Area ode and ell Identity may be present and the ell Identity is further optional at the discretion of the Sender PN. 30 O T SS andatory item Recording Entity ode missing within group. andatory within group Location Information. Non harged Number The number of the non charged party, either that to which the message is or was to be delivered or from which it originated (dependent on the message direction and charging for the service). Derivation: For GS subscribers GS item allednumber (3GPP TS 32.005). 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. 11 SU SU Syntax error and harged Party Status is originating. Syntax error and harged Party Status is terminating. This item may also be used for other address types, e.g. internet address. andatory within group SU Basic Information. Values: For GS subscribers each digit is numeric (0-9). 3.11.05 Page 123 of 217

ode Notification Where the non-charged number represents other address types any value is allowed. A Notification file is sent where the transfer mechanism is electronic file transfer and there is no data available for transfer. All items within the group are mandatory except RAP File Sequence Number which is conditional and File reation Timestamp which is optional. andatory within group Data Interchange where no data is available for transfer and the transfer mechanism is electronic file transfer. 30 31 32 33 35 36 37 38 ontext Notifictn Notifictn Notifictn Notifictn Notifictn Notifictn Notifictn Notifictn andatory item Sender missing within group. andatory item Recipient missing within group. andatory item File Sequence Number missing within group. andatory item Specification Version Number missing within group. andatory item File Available Timestamp missing within group. andatory item Transfer ut Off Timestamp missing within group. File Sequence Number previously received and rejected with fatal error, therefore RAP File Sequence Number expected but not present. RAP File Sequence Number present although File Sequence Number has not previously been rejected with a fatal error (e.g. previously missing or new files). Number Of Decimal Places Identifies the number of decimal places represented within the item Exchange Rate. Acctng Acctng Note: Error ode 34 removed in TAP release 3.11 (01 ay 05). Value out of range. 3.11.05 Page 124 of 217

ode andatory within group urrency onversion. ontext Values: Object Type > or = zero This defines the type of object streamed or downloaded to the customer. ontent Derivation: The object type values are based on, but not confined to, the - Services specification in SE.25. ontent Object Type out of range for ontent Transaction ode and Type Pull/Streaming combination. Present within group ontent Service Used where Pull ontent Transaction ode used and either ontent Transaction Type Streaming or Download used. 21 ontent Object Type out of range for ontent Transaction ode and Type Pull/Download combination. 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/Streaming: 1 Speech Audio PEG 4 AR 2 Audio Audio PEG 4 AA 3 Audio P3 4 Audio WAVE 5 Video H.263 real time video 6 Video PEG 4 7-19 reserved for future use For use with Pull/Download: Ring Tone IDI 21 Ring Tone Audio P4 22 Ring Tone ielody 23 Ring Tone WAVE 24-29 reserved for future use 30 Wallpaper/Screen Saver JPEG 3.11.05 Page 125 of 217

ode 31 Wallpaper/Screen Saver WBP 32 Wallpaper/Screen Saver GIF87a & GIF89 33 Wallpaper/Screen Saver PNG 34 Wallpaper/Screen Saver Java IDlet 35-39 reserved for future use 40 Picture JPEG 41 Picture WBP 42 Picture - GIF87a & GIF89 43 Picture PNG 44 Picture BP 45-49 reserved for future use 50 Speech - Audio PEG 4 AR 51-59 reserved for future use 60 Audio - Audio PEG 4 AA 61 Audio Audio P3 62 Audio WAVE 63-69 reserved for future use 70 Vector Graphic FFS 71-79 reserved for future use 80 Video - H.263 real time video 81 Video PEG 4 82 Video PEG 2 DVD 82-89 reserved for future use 90 Game 91-99 reserved for future use 0 Application 1-9 reserved for future use ontext Operator Specific Information Note: reserved values are out of range until values are assigned. This is an optional repeating item which will contain information which is beyond the scope of TAP and has been bilaterally agreed. The content of the item is defined by bilateral agreement and may vary according to the context, e.g. content when occurring within obile Originated all may vary from that when occurring within Transfer Batch. 30 All Item is present without bilateral agreement. 3.11.05 Page 126 of 217

ode Optionality: Present when agreed bilaterally within groups Notification Batch ontrol Information obile Originated all obile Terminated all Supplementary Service Event Service entre Usage all ontent Transaction Location Service Audit ontrol Information. ontext Order Placed Timestamp The timestamp representing the time at which the harged Party placed the order for the content. This is given in the time of the serving ontent Provider. There must be an associated UT Time Offset ode. ust be present within group ontent Transaction Basic Info when no other timestamp present within group or when item referenced as the harging Point. 11 21 ontent ontent ontent ontent Syntax error and timestamp referenced as harging Point. Syntax error and timestamp not referenced as harging Point. Value out of range and timestamp referenced as harging Point. Value out of range and timestamp not referenced as harging Point. 30 ontent andatory associated UT Time Offset ode missing and timestamp referenced as harging Point. 31 ontent andatory associated UT Time Offset ode missing and timestamp not referenced as harging Point. 0 ontent Order Placed Timestamp after associated 3.11.05 Page 127 of 217

ode 1 ontext ontent harge Detail timestamp and timestamp referenced as harging Point. Order Placed Timestamp after associated harge Detail timestamp and timestamp not referenced as harging Point. Originating Network The network from which the call or message was routed. In the case of optimal routing the Originating Network code is different from the HPN code. ust be present within groups 0 ontent T SU T SU Order Placed Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file. Value out of range. T Basic all Information SU Basic Information if available. Paid Indicator e.g. GBRN ellnet GBRVF Vodafone DEUD1 D1 DEUD2 D2 Privat A flag which shows that the harged Party has paid for the service by another mechanism, e.g. credit card, account, debit card. The flag s presence shows that the charge is not intended for the retail invoice. ontent ontent Value out of range. ust be present within group Advised harge Information where the charge is being/has been settled by a mechanism external to TAP. 3.11.05 Page 128 of 217

ode Partial Type Indicator Values: 1 Paid The Partial Type Indicator identifies the first and last partials in a sequence. ust be present within group Basic all Information where the all Event Detail represents a partial. ontext Value out of range. Payment ethod Values: F I L first partial intermediate partial last partial Where the charge is being/has been settled by a mechanism other than TAP this item identifies the payment method (to be) used. Optionality: ontent ontent Value out of range. This item is made available at the discretion of the ontent Provider and/or Sender. ust be present within group Advised harge 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 3.11.05 Page 129 of 217

ode PDP Address identifiable by the ontent Provider/Sender, e.g. mixed payment or information not passed by retail outlet. An address (served) used with a Packet Data Protocol context of a connection. This is an IP address. Derivation: GS item PDP Address (3GPP TS 32.015). For WLAN network usage, item Framed-IP-Address (RF 2865). andatory within group hargeable Subscriber. For WLAN network usage, present when available. ontext Does not conform to section 5.2. PDP ontext Start Timestamp The timestamp gives the start of the PDP context in the case where the all Event Details ( all) represents an intermediate or last partial of a PDP context. Value out of range. The time is given in the local time of the Sender PN (or Serving Network where this is not the Sender). There must be a UT Time Offset ode associated with the timestamp. 30 andatory associated item UT Time Offset ode missing. Note that the local time is the local time at the location of the chargeable subscriber. Where the location is not available, as in some call forwarding scenarios, this will be a notional network local time. 31 PDP ontext Start Timestamp present but Partial Type Indicator is either not present or identifies all as the first partial. Optionality: Operators may decide not to supply this information (normally this will be because it is not available from the billing system). 0 PDP ontext Start Timestamp is later than all Event Start Timestamp. Note: Error ode 1 removed in TAP release 3.11 (01 ay 05). ust be present within group Basic all Information where available and Partial Type Indicator is present identifying the all as either an intermediate or last partial (subject to 3.11.05 Page 130 of 217

ode Positioning ethod optionality). Format: YYDDHHSS The technology used for positioning a tracked mobile subscriber (eg. Assisted GPS). Derivation: Positioning Data IE (TS 49.031). 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 (TS 49.031). In order to identify the positioning technology actually used bits 3-1 which code the usage of the positioning technology need to be analysed. ust be present within group LS QoS Delivered where available from the network.. ontext LS Value out of range. Priority ode Values: 0 Timing Advance 1 Reserved 2 Reserved 3 obile Assisted E-OTD 4 obile Based E-OTD 5 obile Assisted GPS 6 obile Based GPS 7 onventional GPS 8-15 reserved for GS 16-31 reserved for network specific positioning methods Indicates the priority assigned to the short message. SU andatory within group SU harge Type. SU Value out of range. 3.11.05 Page 131 of 217

ode RAP File Sequence Number Values: 0 Low 1 Normal 2 High A unique reference which identifies the Returned Account Procedure (RAP) file in which the record or batch was returned to the Sender PN by the Recipient PN. The record or batch, the error(s) having been resolved, is now being resubmitted to the Recipient PN. Note that where a TAP file is being resubmitted as corrected the RAP File Sequence Number is not required on the all Event Details but it must be present on either the Notification or Batch ontrol Information, as appropriate. Note that the RAP File Sequence Number must not be present when a previously missing TAP file (Transfer Batch or Notification) is sent. ust be present within groups Notification Batch ontrol Information where the TAP file is being resubmitted as corrected. ust be present within groups O Basic all Information T Basic all Information Supplementary Service Event Service entre Usage Basic all Information ontent Transaction Basic Info Location Service where the record is being resubmitted as corrected. 11 21 ontext Notifictn Btch trl alls Btch trl Notifictn alls Syntax error Value out of range. Value out of range Range: 00001 99999 for Test Data 00001 99999 for hargeable Data 3.11.05 Page 132 of 217

ode Recipient A unique identifier used to determine which network the data is being sent to, i.e. the Recipient. ontext Notifictn Btch trl Derivation: GS Association PRD TD.13: PN Naming onventions. Notifictn Btch trl Value out of range. andatory within group Notification. 0 Notifictn Btch trl The item does not match the Recipient on the filename. andatory within group Batch ontrol Information. Example content: ode GBRN GBRVF DEUD1 DEUD2 Note: These codes must be in uppercase (as defined in TD.13). Recording Entity ode A code associated with a Recording Entity. andatory within groups Recording Entity Information Location Service Network Location 11 Network O T SS SU LS Syntax error Syntax error Service entre Usage where it must be of type Service entre In the case of network usage two or more occurrences must be present within group Network Location where one, and only one, occurrence must be of type GGSN (see Recording Entity Type) and all other occurrences must be of type SGSN. In the case of WLAN network usage one occurrence must be 12 13 Value out of range for a call (except for WLAN network usage), i.e. the Recording Entity ode refers to a recording entity of a type other than GGSN or SGSN. Value out of range for a call (only for WLAN network usage), i.e. the Recording Entity ode refers to a recording entity of a type other than WLAN billing information 3.11.05 Page 133 of 217

ode Values: present identifying the WLAN billing information recording entity. 0.. 000 0 1 2 3 ontext Network O T SS SU LS O T SS SU O T recording entity. Value out of range. Specified recording entity code not defined in the Recording Entity Information Entity ode refers to S (Recording Entity Type 1) and syntax of the referenced Recording Entity Identification does not conform to SISDN (3GPP TS 23.003), Signalling Point ode (ITU-T Q.701) or uppercase name. Entity ode refers to SS (Recording Entity Type 2) and syntax of the referenced Recording Entity Identification does not conform to SISDN (3GPP TS 23.003). Entity ode refers to GGSN (Recording Entity Type 3) and syntax of the referenced Recording Entity Identification does not conform to section5.2. 4 O T Entity ode refers to SGSN (Recording Entity Type 4) and syntax of the referenced Recording Entity Identification does not conform to section 5.2. 5 LS Recording Entity ode refers to GL (Recording Entity Type 5) and syntax of the referenced Recording Entity Identification 3.11.05 Page 134 of 217

ode Recording Entity Identification The identification of the entity recording the call. andatory within group Recording Entity Information. ontext does not conform to SISDN (3GPP TS 23.003) or to section 5.2. Network Recording Entity Information For S encoded as one of the following according to the requirements of the Sender PN. The SISDN of the entity as per 3GPP TS 23.003 e.g. 448360456 The signalling point code as per 3GPP TS 23.003 e.g. 253464 A name e.g. HELSINKI Note: must be uppercase. For SS entity as per 3GPP TS 32.005 (sisdn). For GSN entities as per 3GPP TS 32.015 (GSNAddress). For GSN entities, where SS usage is recorded, as per 3GPP TS 32.005 or 3GPP TS 32.015 (GSNAddress or sisdn). For GL entities as per 3GPP TS 32.5 and 3GPP TS 32.215 (sisdn) or as Ipv4 Address or as Ipv6 Address. For WLAN network usage this could be the name (uppercase) or an IP address of the WLAN billing information recording entity. A repeating group which identifies a Recording Entity Identification together with an associated Recording Entity ode and Recording Entity Type. 30 Network andatory item Recording Entity ode missing within group. 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. odes are reusable from transfer to transfer. One occurrence must be present within group Network Information for each unique Recording Entity ode used within the TAP file. 31 32 33 Network Network Network andatory item Recording Entity Type missing within group. andatory item Recording Entity Identification missing within group. ore than one occurrence of group with same Recording Entity ode where Recording Entity Type and /or Recording Entity Identification are not the same. 34 Network ore than one occurrence of group with same Recording Entity ode where Recording 3.11.05 Page 135 of 217

ode Recording Entity Type An item identifying the type of recording entity. andatory within group Recording Entity Information. ontext Network Network Entity Type and Recording Entity Identification are the same (i.e. duplicate Recording Entity Information table entry). Value out of range. Release Version Number Requested Delivery Timestamp Values: 1 S (obile Services Switching entre) 2 SS (Short essage Service entre) 3 GGSN (Gateway Support Node) 4 SGSN (Serving Support Node) 5 GL (Gateway obile Location entre) 6 WLAN Billing Information Recording Entity Indicates the release version within the Specification Version Number. Values: 11 andatory within item Specification Version Number. The timestamp representing the time requested by the harged Party to initiate the start of the ontent Transaction. This is given in the time of the serving ontent Provider. There must be an associated UT Time Offset ode. Example: The harged Party may request to download all messages at 20hrs in order to take advantage of off-peak rates even when placing the order at an earlier time. ust be present within group ontent Transaction Basic Info 11 21 30 Notifictn Btch trl Notifictn Btch trl ontent ontent ontent ontent ontent Value out of range. Syntax error and timestamp referenced as harging Point. Syntax error and timestamp not referenced as harging Point. Value out of range and timestamp referenced as harging Point. Value out of range and timestamp not referenced as harging Point. andatory associated UT Time Offset ode missing and timestamp referenced as 3.11.05 Page 136 of 217

ode when no other timestamp present within group or when item referenced as the harging Point. 31 ontext ontent harging Point. andatory associated UT Time Offset ode missing and timestamp not referenced as harging Point. 0 ontent Requested Delivery Timestamp after associated harge Detail timestamp and timestamp referenced as harging Point. 1 ontent Requested Delivery Timestamp after associated harge Detail timestamp and timestamp not referenced as harging Point. 0 ontent Requested Delivery Timestamp before the commercial roaming start date for the specific service and the TAP file is not a test file. Response Time The actual response time for processing the LS request measured in seconds. Derivation: GS/UTS item measureduration (3GPP 32.005). Response Time ategory ust be present within group LS QoS Delivered where available from the network The response time category as requested for the response of an LS request. Derivation: LS QoS IE octet 6 (3GPP TS 49.031). The value is derived by interpreting the 2 most significant bits of octet 6 as an integer. LS Value out of range. 3.11.05 Page 137 of 217

ode ust be present within group LS QoS Requested where available from the network ontext SU Basic Information Values: 0 response time not specified 1 low delay 2 delay tolerant 3 reserved Service entre Usage (SU) Basic Information provides details of who made the call and where to, who received the call and where from, in respect of mobile originated and mobile terminated traffic respectively and the direction of the transaction. The hargeable Subscriber, harged Party Status and Non harged Number elements are all mandatory. All other elements are conditionally present. andatory within group Service entre Usage. 30 31 32 SU SU SU andatory group SU hargeable Subscriber missing within group. andatory item harged Party Status missing within group. andatory item Non harged Number missing within group and harged Party Status is originating. 33 SU andatory item Non harged Number missing within group and harged Party Status is terminating. SU harge Type ontains the elements used to price the service usage, message status, priority code, distance charge band code and message type. Where the charge is based on volume, e.g. message length, this information will be present within the associated harge Information. All elements within the group are mandatory except Distance harge Band ode which will not be present where it was not a parameter in harge calculation.. 34 30 31 32 SU SU SU SU Item LIR Status Indicator missing within group and harged Party Status is terminating. andatory item essage Status missing within group. andatory item Priority ode missing within group. Item Distance harge Band ode missing within group and distance defined as a pricing parameter within SS bilateral agreement. 3.11.05 Page 138 of 217

ode andatory within group Service entre Usage. 33 ontext SU andatory item essage Type missing within group. SU hargeable Subscriber Occurs within SU Basic Information. ontains the identification of the chargeable subscriber. 34 30 SU SU andatory item essage Description ode missing within group. Group empty i.e. no IN and no GS hargeable Subscriber present within group. The group must contain either the group GS hargeable Subscriber or the IN of the chargeable subscriber, both may not be present. andatory within groups 31 SU Both IN and GS hargeable Subscriber present within group. SU Timestamps Sender SU Basic Information ontains the timestamps for message deposit and completion of actions together with an indicator showing which timestamp was used as the harging Point. All elements within the group are mandatory. andatory within group Service entre Usage. A unique identifier used to determine the network which is the Sender of the data. 30 31 32 SU SU SU Notifictn Btch trl andatory item Deposit Timestamp missing within group. andatory item ompletion Timestamp missing within group. andatory item harging Point missing within group. The full list of codes in use are given in TADIG PRD TD.13: PN Naming onventions. andatory within group Notification. andatory in group Batch ontrol Information. 0 Notifictn Btch trl Notifictn Btch trl Value out of range. The item does not match the Sender on the filename. Example content: ode GBRN GBRVF 3.11.05 Page 139 of 217

ode DEUD1 DEUD2 ontext Service entre Usage Note: These codes must be in uppercase (as defined in TD.13). A Service entre Usage item represents usage of an APNs Short essage Service entre (SS). 30 SU andatory group SU Basic Information missing within group. This usage can only occur where there is a bilateral agreement to make these services available to the HPN s subscribers. All elements within the group are mandatory except RAP File Sequence Number and SP Information which are conditional and Operator Specific Information which is optional. 31 32 SU SU Item RAP File Sequence Number missing and SU previously received and rejected. Item RAP File Sequence Number present and SU not previously received and rejected. andatory within an occurrence of group all Event Details where none of the following are present; obile Originated all, obile Terminated all, Supplementary Service Event, all, ontent Transaction or Location Service. 33 34 SU SU andatory item Recording Entity ode missing within group. andatory group harge Information missing within group. 35 SU andatory group SU harge Type missing within group. 36 SU andatory group SU Timestamps missing within group. 37 SU Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). Service ode The Service ode is one of Teleservice ode or Bearer Service ode as determined by the service type used. Note: Error codes 38 & 39 removed in TAP release 3.11 (01 ay 05). Note: Error codes 30, 31, 32 & 33 removed in TAP release 3.11 (01 ay 05). 3.11.05 Page 140 of 217

ode andatory within group Basic Service. ontext 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. Serving BID The Serving BID (Billing Identifier) is a code associated with a geographical area such as a cell site or group of cell sites. Where a Serving BID has been supplied there must be a Serving Location Description present. Derivation: Listed on the BID report in effect for the applicable call date as defined within PRD TD.38. O T SS O T SS Value out of range. Optionality: Operators may decide not to transfer the Serving BID. ust be present within group Geographical Location where available (subject to optionality). Value must be assigned to the Sender. 21 O T SS Value not assigned to Sender. Serving Location Description A text description giving the geographical location of the terminal equipment. Operators may optionally use a description as a default where there has been no terminal equipment involved. The Serving Location Description must be present where there is an associated Serving BID and its content will then be predefined. O T SS 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 WLAN network usage this item is mandatory and will contain a text description of the WLAN Hot Spot, e.g. London ity Airport. 3.11.05 Page 141 of 217

ode 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 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. 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. WLAN network usage ust 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. ust be present within group Geographical Location for WLAN network usage. ontext Serving Network A unique identifier used to determine the network where the call event was originally created. While this would normally be a TADIG PN code (see TADIG PRD TD.13) this may not be true in certain specific cases, e.g. inter standard roaming. O T SS SU ust be present within groups Geographical Location O T SS SU Value out of range, i.e. it is neither a TADIG PN ode nor a bilaterally agreed value. 3.11.05 Page 142 of 217

ode Service entre Usage ontext Serving Parties Information if the Serving Network is different from the Sender. Information on entities that were used to access the ontent Service. This group must contain the item ontent Provider Name. Additional data should be provided when the information is available to the Sender. andatory within group ontent Transaction. 30 ontent andatory item ontent Provider Name missing within group. SI Toolkit Indicator The SI Toolkit Indicator will be present when the call has been initiated by the SI Toolkit application. O T Syntax error ust be present within groups O T Value out of range O Basic all Information T Basic all Information where the call has been initiated by the SI toolkit. SS Destination Number Values: 1 initiated by SI toolkit The SS Destination Number item contains the actual destination (intended recipient) of the SS text message. Derivation: O O Value out of range. Derived from item destinationnumber (SmsTpDestinationNumber) (3GPP TS 32.5 or 32.005). ust be populated with the digits exactly as entered by the subscriber. ust be present within group Destination for SS O calls when the information is available from the network. 3.11.05 Page 143 of 217

ode SS Originator Values: Each digit is numeric (0-9) or contains, or. The SS Originator holds the identification of the actual sender of the SS (not the SS). ust be populated with the data as received from the network. ust be present within group all Originator where available from the network and TeleService ode indicates SS usage. ontext T Note: Error ode removed in TAP release 3.11 (01 ay 05). Specification Version Number To enable a PN to encode and/or read a file it is necessary to uniquely identify the format. This is achieved through the Specification Version Number. There must be a Release Version Number present within this item. Notifictn Btch trl Notifictn Btch trl Value out of range. andatory within group Notification. andatory within group Batch ontrol Information. 30 Notifictn Btch trl andatory associated item Release Version Number missing. Supplementary Service ode Value: 3 for TAP3 A code which uniquely defines the supplementary service, a group of supplementary services, or a USSD message. Derivation for Supplementary Service: GS item SupplementaryServiceode (3GPP TS 32.005). The code is derived by taking the AP encoding (3GPP TS 29.002) and translating bits 8-5 into a hex character and bits 4-1 into a second hex character. 11 21 SS O T SS O T Value out of range. Value out of range. andatory within group Supplementary Service Used. andatory within group obile Originated all where a 22 O T Value FF. 3.11.05 Page 144 of 217

ode supplementary service has been used in conjunction with the call. Values: 00 All supplementary services All line identification services 11 alling number identification presentation 12 alling number identification restriction 13 onnected number identification presentation 14 onnected number identification restriction All call forwarding 21 all forwarding unconditional 28 All conditional all Forwarding 29 all forwarding on mobile subscriber busy 2A all forwarding on no reply 2B all forwarding on subscriber not reachable 30 All call offering services 31 all transfer 40 All call completion services 41 all waiting 42 all hold 43 ompletion of calls to busy subscribers 50 All multi party services 51 ulti party service 60 All community of interest services 61 losed user groups 70 All charging supplement services 71 Advice of charge (charging) 72 Advice of charge (information) 80 All additional info transfer services 81 User to user signalling 90 All call barring 91 All Barring of outgoing all Services 92 Barring of all outgoing calls 93 Barring of all outgoing international calls 94 Barring of all OG international except HPN 99 All Barring of incoming all Services 9A Barring of all incoming calls 3.11.05 Page 145 of 217 ontext 30 SS USSD, value 'FF', present and associated harge Information does not contain a charge greater than zero.

ode Supplementary Service Event 9B Barring of all I calls when outside HPN FF USSD essage A Supplementary Service Event element represents usage of supplementary services or an USSD message. The supplementary service can happen outside or in conjunction with a standard call dependent on network configuration. hargeable Subscriber, Location Information, Equipment Identifier and Supplementary Service Used must be present. RAP File Sequence Number is conditionally present. Operator Specific Information may also be present, this is optional dependent on bilateral agreement. andatory within an occurrence of group all Event Details where none of the following are present; obile Originated all, obile Terminated all, Service entre Usage, all, ontent Transaction or Location Service. 30 31 32 33 34 35 ontext SS SS SS SS SS SS andatory group hargeable Subscriber missing within group. Item RAP File Sequence Number missing and SS previously received and rejected. Item RAP File Sequence Number present and SS not previously received and rejected. andatory group Location Information missing within group. andatory item Equipment Identifier missing within group. Item RAP File Sequence Number present and TAP transfer batch being resubmitted as corrected (having been previously rejected with fatal error). 36 SS andatory group Supplementary Service Used missing within group. Supplementary Service Parameters The Supplementary Service Parameters element is an element of the Supplementary Service Used. The contents of the element and the value it represents is entirely dependent upon the Supplementary Service Action. Derivation for Supplementary Service: GS item ssparameters (3GPP TS 32.005). SS SS Note: Error codes 37 & 38 removed in TAP release 3.11 (01 ay 05). Value out of range. 3.11.05 Page 146 of 217

ode ust 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. Event Action Parameter all forward Reg n Forwarded to number unconditional all fwd busy Reg n Forwarded to number all fwd no reply Reg n Forwarded to number all fwd not Reg n Forwarded to number reachable Explicit all Inv n Transferred to number Transfer ontext Supplementary Service Used USSD message USSD Inv n The contents of the USSD message as entered by the user or sent by the mobile station. This element details the Supplementary Service used and relevant charging information. 30 SS andatory item Supplementary Service ode missing within group. The group must contain the Supplementary Service ode and Action ode. onditionally the following information may also be present; Supplementary Service Parameters, harging Timestamp, harge Information and Basic Service ode (which may be repeated for each service affected). Within group Supplementary Service Event the group is mandatory and may only occur once. 31 32 SS SS andatory item Action ode missing within group. Item Supplementary Service Parameters present when Supplementary Service is not for call forward registration or does not represent USSD usage. 33 SS Item Supplementary Service Parameters not present when Supplementary Service is for call forward registration or invocation usage. 3.11.05 Page 147 of 217

ode 36 ontext SS Item harging Timestamp missing within group. 1 SS Invalid or non transferable Supplementary Service ode and Action code combination present within group. TAP urrency TAP urrency contains the urrency ode which identifies the currency used for charges throughout the Transfer Batch where that currency is not in the standard SDRs. Acctng Acctng Note: Error codes 34, 35, 37, 38 & 0 removed in TAP release 3.11 (01 ay 05). Value out of range. The use of a currency other than SDRs will be by bilateral agreement. The item is only provided for use in internal markets. Derivation: ISO 4217 urrency odes standard. 0 Acctng TAP urrency not in line with bilateral agreement. Optionality: Only present within internal markets where agreed bilaterally. Subject to optionality, must be present within Accounting Information when currency other than SDR is used as specified in the roaming agreement. TAP Decimal Places Example: urrency ode EUR INR USD urrency name Euro Indian rupee U.S. dollar Identifies the number of decimal places used within all absolute monetary values within the TAP file. The same number of decimal places must be present for all tax, discount, Acctng Acctng Value out of range. 3.11.05 Page 148 of 217

ode charge and audit values throughout the whole TAP file. andatory within group Accounting Information. ontext Values: Range 0 6 Tax Information A repeating group containing the Tax Rate ode and the Tax Value and, where applicable Taxable Amount. 30 alls andatory item Tax Rate ode missing within group. Each element of harge Information may have several tax elements associated with it, e.g. national tax, regional tax, local tax. 31 alls andatory item Tax Value missing within group. There must be one occurrence within harge Information for each tax element associated with the harge Information (see also Taxation). Note: Error code 32 removed in TAP release 3.11 (01 ay 05). There must be one occurrence within group AEL Service Used for each tax element associated with the AEL Invocation Fee. Tax Rate A tax rate associated with a Tax Type and Tax Rate ode. Acctng 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 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. Acctng Value out of range. The rate is given to 5 decimal places. andatory within group Taxation except where the associated Tax Rate oderepresents an absolute/fixed tax value in which case it must not be present. Values: 00.00000 thru 99.99999 Tax Rate ode A code associated with a Tax Type and Tax Rate. Acctng 3.11.05 Page 149 of 217

ode andatory within group Taxation. andatory within group Tax Information. 11 ontext alls Acctng Value out of range. Values: Range 0.. 999 0 alls Specified Tax Rate ode was not defined in the group Taxation Tax Type The type of tax represented by the Tax Rate ode and Tax Rate combination. 0 alls Acctng 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. andatory within group Taxation. Acctng Value out of range. Values: 01 National (e.g. Federal, Dominion, VAT, etc.) 02 Regional (e.g. State, Province, etc.) 03 ounty 04 Local/ity Note that the above tax types may represent specific taxes, i.e. any of Public 3.11.05 Page 150 of 217

ode Tax Value Taxable Amount Utilities, Sales & Use, ommunications taxes may be National, Regional, ounty or Local/ity. The actual value of the tax associated with the Tax ode and harge Information. The Tax Value must be of a value greater than or equal to zero. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Values: andatory within group Tax Information. >= 0 (zero) The actual part of the harge to which the Tax Value and Tax Rate (ode) relate. The Taxable Amount must of a value greater than zero. 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 urrency. onditionality ust be present within group Tax Information where the associated Tax Value and Tax Rate ode do not relate to the total harge 3.11.05 Page 151 of 217 22 0 0 ontext alls alls alls alls alls alls alls Value out of range. Where the associated Tax Rate ode relates to a Tax Rate, the Tax Value does not correspond to the Taxable Amount (or harge where no Taxable Amount present) and Tax Rate. Note: Rounding rules are at the discretion of the Sender and a tolerance must be allowed. A minimum tolerance of 0.02 units is recommended, independent of the number of decimal places used for the TAP file. 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. Value out of range. Taxable Amount not in line with roaming agreement.

ode Taxation Values: within harge Information. > 0 (zero) The Taxation table is a repeating group of Tax Rate ode, Tax Type, Tax Rate and harge Type. Tax Rate ode and Tax Type are mandatory, Tax Rate and harge Type are conditional. 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. odes are reusable from transfer to transfer. andatory within group Accounting Information except where taxes are not applicable. One occurrence must be present for each unique Tax Rate ode used within group Tax Information. 30 31 33 34 ontext Acctng Acctng Acctng Acctng andatory item Tax Rate ode missing within group. andatory item Tax Type missing within group. ore than one occurrence of group with same Tax Rate ode where Tax Type, Tax Rate and/or harge Type are not the same. ore than one occurrence of group with same Tax Rate ode where Tax Type and Tax Rate are the same (i.e. duplicate Taxation table entries). TeleService ode A code which uniquely defines a TeleService. Group TeleService odes, identifiable by the description All, should only be used where details of the specific services affected are not available from the network. Note that compound TeleService group codes can only occur in call independent supplementary service operations. Derivation: GS item TeleServiceode (3GPP TS 32.005). 11 21 O T SS O T SS Note: Error codes 32 and 35 removed in TAP release 3.11 (01 ay 05). Value out of range. Value out of range. The code is derived by taking the AP encoding (3GPP TS 29.002) and translating bits 8-5 into a hex character and bits 4-1 into a second hex character. ust be present within group Service ode where the type of 3.11.05 Page 152 of 217

ode service used was a teleservice. ust not be present when the type of service used was a bearer service and, therefore, Bearer Service ode is present. ontext Third Party Information Values: 00 All teleservices Speech 11 Telephony 12 Emergency calls All SS Services 21 Short essage T/PP 22 Short essage O/PP 31 Advanced HS access 41 Videotex access profile 42 Videotex access profile 2 43 Videotex access profile 3 51 Teletex (ircuit Switch) 52 Teletex (Packet Switch) 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 SS (compound) A group containing information identifying the original calling party in a call forwarding call context. The group must contain a LIR 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 O relating to the call forward leg (from party T to party U) will contain, in the Third Party Information, details of party S (subject to availability). Note: Error odes 30, 31, 32, 33 and 34 removed in TAP release 3. (01 ay 03). 3.11.05 Page 153 of 217

ode ust be present within group obile Originated all where the associated Supplementary Service ode indicates a conditional call forward invocation and the information is available from the network. ontext Third Party Number The Third Party Number is the number identifying the original calling party in a conditional call forwarding context. Derivation: GS item allingnumber (3GPP TS 32.005). 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. alls alls Number not represented in international format. ust be present within group Third Party Information where available. Total Advised harge Values: Each digit is numeric (0-9) The sum of all the advised charges associated with the corresponding currency excluding those representing a refund (harge Refund Indicator). The Total Advised harge must not contain a negative value. Note that charges from records with severe errors should also be included where possible. The number of decimal places is defined by item TAP Decimal Places. 0 Audit Audit Audit Value out of range. Value does not match the calculated sum of non refund advised charges associated with the same currency. andatory within group Total Advised harge Value. Total Advised harge Refund Values: > or = 0 (zero) The sum of all the advised charges associated with the corresponding currency representing a refund (harge Refund Indicator). Audit 3.11.05 Page 154 of 217

ode The Total Advised harge Refund must be greater than zero. Note that charges from records with severe errors should also be included where possible. The number of decimal places is defined by item TAP Decimal Places. Present within group Total Advised harge Value where refunds are present and the total is greater than zero. 0 ontext Audit Audit Value out of range. Value does not match the calculated sum of refund advised charges associated with the same currency. Total Advised harge Value Values: > (zero) A repeating group holding the sums of all advised charges and commissions by associated currency. 30 Audit andatory item Total Advised harge missing within group. Total all Event Duration The group must contain Total Advised harge. onditional items are Advised harge urrency, Total ommission, Total Advised harge Refund, Total ommission Refund. Present within group Audit ontrol Information where ontent Transactions are present within the file and there are Advised harges present within one or more of the ontent Transactions. The item contains the actual total duration of a call event as a number of seconds. The item is used, in conjunction with the all Event Start Timestamp (and UT Time Offset ode) to calculate the call event end time, this is needed for ageing calculations and validation against the File Available Timestamp. andatory within groups O Basic all Information 0 1 2 0 Audit Audit Audit O T O T O T Item Total ommission expected and not present. Item Total ommission Refund expected and not present. Item Total Advised harge Refund expected and not present. Value out of range Total all Event Duration is greater than 0 (zero) for SS call. T Basic all Information Basic all Information 0 Total all Event Duration exceeds limit defined by BARG in BA.12. 3.11.05 Page 155 of 217

ode Values: > or = 0 ontext Note: for SS calls the value must be 0 (zero). Total harge The sum of all the charges associated with harge Type 00 and AEL Invocation Fee, excluding those representing a refund (harge Refund Indicator). Audit Audit Value out of range. The Total harge must not contain a negative value. Note that charges from records with severe errors must also be included where possible. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. 0 Audit Value does not match the calculated sum of non refund charges which includes sum of AEL Invocation Fee for all AEL calls in the Transfer Batch. andatory within group Audit ontrol Information. Total harge Refund Values: > or = 0 (zero) The sum of all the charges associated with harge Type 00 representing a refund (harge Refund Indicator). The Total harge Refund must be greater than zero. Note that charges from records with severe errors should also be included where possible. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. 21 0 Audit Audit Audit Audit Value out of range (except zero). Item Total harge Refund has a value of zero. Value does not match the calculated sum of refund charges associated with harge Type 00. Present within group Audit ontrol Information where refunds are present and the total is greater than zero. Values: 3.11.05 Page 156 of 217

ode > 0 (zero) Total ommission The sum of all the commissions associated with the corresponding currency excluding those representing a refund (harge Refund Indicator). The Total ommission must be greater than zero. Note that commissions from records with severe errors should also be included where possible. The number of decimal places is defined by item TAP Decimal Places. Present within group Total Advised harge Value where the non refund commissions total is greater than zero. 0 ontext Audit Audit Audit Value out of range. Value does not match the calculated sum of non refund advised charges associated with the same currency. Total ommission Refund Values: > 0 (zero) The sum of all the commissions associated with the corresponding currency representing a refund (harge Refund Indicator). The Total ommission Refund must be greater than zero. Note that commissions from records with severe errors should also be included where possible. The number of decimal places is defined by item TAP Decimal Places. 0 Audit Audit Audit Value out of range. Value does not match the calculated sum of refund advised charges associated with the same currency. Present within group Total Advised harge Value where refunds are present and the total is greater than zero. Total Data Volume Values: > (zero) The Total Data Volume identifies the total number of octets (bytes) within the one occurrence of ontent Service Used. This item is used instead of items Data Volume Incoming and Outgoing where the data direction cannot be separately identified. ontent ontent Value out of range. 3.11.05 Page 157 of 217

ode Present within group ontent Service Used when information is available. ontext Total Discount Refund Values: > or = 0 (zero) The sum of the Discount Values plus each application of a Fixed Discount Value contained in the batch representing a refund (harge Refund Indicator). Audit Audit Value out of range The Total Discount Refund must be greater than zero. This is present for audit purposes only. 0 Audit Value does not match the calculated sum of refund discounts from all Event Details. Note that discount from records with severe errors should also be included where possible. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Present within group Audit ontrol Information where the refund discount total is greater than zero. Total Discount Value Values: > 0 (zero) The sum of the Discount Values plus each application of a Fixed Discount Value contained in the batch excluding those representing a refund (harge Refund Indicator). Audit Audit Value out of range The Total Discount Value must not contain a negative value. This is present for audit purposes only. 0 Audit Value does not match the calculated sum of non refund discounts from all Event Details. Note that discount from records with severe errors should also be included where possible. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. 3.11.05 Page 158 of 217

ode andatory within group Audit ontrol Information. ontext Total Tax Refund Values: > or = 0 (zero) The sum of the Tax Values contained in the batch representing a refund (harge Refund Indicator). The Total Tax Refund must be greater than zero. This is present for audit purposes only. Note that tax from records with severe errors should also be included where possible. 0 Audit Audit Audit Value out of range Value does not match the calculated sum of refund taxes from all Event Details. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. Present within group Audit ontrol Information where the refund tax total is greater than zero. Total Tax Value Values: > 0 (zero) The sum of the Tax Values contained in the batch excluding those representing a refund (harge Refund Indicator). The Total Tax Value must not contain a negative value. This is present for audit purposes only. Note that taxes from records with severe errors should also be included where possible. 0 Audit Audit Audit Value out of range. Value does not match the calculated sum of non refund taxes from all Event Details. The value is in SDRs with the number of decimal places defined by item TAP Decimal Places. Note the currency may be subject to internal market bilateral agreements, see TAP urrency. 3.11.05 Page 159 of 217

ode andatory within group Audit ontrol Information. ontext Total Transaction Duration Values: > or = 0 (zero) The item contains the actual total duration of a ontent Transaction as a number of seconds. The item can be used in conjunction with the latest associated timestamp (Order Placed, Requested Delivery or Actual Delivery timestamps) to calculate the ontent Transaction end time used for age validation. ontent ontent Value out of range. Present within group ontent Transaction Basic Info where available. Tracked ustomer Equipment Values: > = 0 Information relating to equipment used by the Tracked ustomer. The group, when present, must contain items Equipment Id Type and Equipment Identifier. 30 31 LS LS andatory item Equipment Id Type missing within group. andatory item Equipment Id missing within group. Present within group Tracked ustomer Information where available. Tracked ustomer Home Id Information identifying the home environment of the Tracked ustomer. The group, when present, must contain items Home Id Type and Home Identifier. 30 31 LS LS andatory item Home Id Type missing within group. andatory item Home Identifier missing within group. One or more occurrences may be present within group Tracked ustomer Information where available. Tracked ustomer Identification The identification of the customer being tracked. The group must contain items ustomer Id Type and ustomer Identifier. 30 31 LS LS andatory item ustomer Id Type missing within group. andatory item ustomer Identifier missing 3.11.05 Page 160 of 217

ode Tracked ustomer Information Tracked ustomer Location Tracking ustomer Equipment One or more occurrences must be present within group Tracked ustomer Information. Information identifying the tracked customer. The group must contain at least one occurrence of group Tracked ustomer 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 (e.g. SISDN-ISI-Account Number : Home BID- TADIG ode : ountry-region) the groups containing these elements may occur more than once. andatory within group Location Service where it is not the same as the tracking customer. Information on the location of the tracked customer. This is not the actual location as delivered by the location service request, it identifies the geographical or virtual location of the tracked customer, e.g. country, network, ip address. Availability of this data may be subject to local regulatory rules/laws. ust be present within group Tracked ustomer Information where available. Information relating to equipment used by the Tracking ustomer. The group, when present, must contain items Equipment Id Type and Equipment Identifier. Present within group Tracking ustomer Information where available. 3.11.05 Page 161 of 217 ontext within group. 30 LS andatory group Tracked ustomer Identification missing within group. 30 31 30 31 LS LS LS LS andatory item Location Id Type missing within group. andatory item Location Identifier missing within group. andatory item Equipment Id Type missing within group. andatory item Equipment Id missing within group.

ode Tracking Information identifying the home environment of the Tracking ustomer. ustomer Home Id The group, when present, must contain items Home Id Type and Home Identifier. Tracking ustomer Identification Tracking ustomer Information One or more occurrences may be present within group Tracking ustomer Information where available. The identification of the customer requesting the tracking. The group must contain items ustomer Id Type and ustomer Identifier. One or more occurrences must be present within group Tracking ustomer Information. Information identifying the tracking customer. The group must contain at least one occurrence of group Tracking ustomer Identification with all other groups being conditional on availability. ust be present within group Location Service where the Tracking ustomer can be identified. Tracking Information on the location of the tracking customer. ustomer Location This is the geographical or virtual location of the tracking customer, e.g. country, network, ip address. Availability of this data may be subject to local regulatory rules/laws. ust be present within group Tracking ustomer Information where available. 30 31 30 31 ontext LS LS LS LS andatory item Home Id Type missing within group. andatory item Home Identifier missing within group. andatory item ustomer Id Type missing within group. andatory item ustomer Identifier missing within group. 30 LS andatory group Tracking ustomer Identification missing within group. 30 31 LS LS andatory item Location Id Type missing within group. andatory item Location Identifier missing within group. Tracking Frequency The time interval measured in seconds between two consecutive location estimates for continuous/periodic tracking. 3.11.05 Page 162 of 217

ode ust be present within group LS QoS Requested/Delivered where applicable and available from the network ontext Tracking Period Transaction Authorisation ode The overall tracking period measured in seconds for continuous/periodic tracking. ust be present within group LS QoS Requested/Delivered where applicable and available from the network The authorisation code passed to the ontent Provider for this content transaction. This will only be present where there are no privacy/regulatory implications and when the information is available. Present within group ontent Service Used where available. ontent Transaction Description Suppression Indicates that the harged Party has requested the Transaction Description (short & detail) to be suppressed and therefore not to be detailed on any correspondence to the harged Party. ontent ontent Value out of range. Transaction Detail Description Values: Present within group ontent Service Used when the harged Party has requested the description of the detail to be suppressed. 1 Suppress description The item contains, in plain text, the long description detailing the ontent Service. E.g. names and quantities of the stocks traded, title of books purchased or name of ring tone downloaded. ontent This item gives a more precise definition of the transaction than the 3.11.05 Page 163 of 217

ode Transaction Short Description. onditionality ontext Transaction Identifier Present within group ontent Service Used where available. An identifier uniquely representing the ontent Transaction for the given ontent Provider. This will often be an identifier notified to the customer at the time of transaction request, e.g. order number. andatory within group ontent Service Used. ontent Transaction Short Description The item contains, in plain text, the short description detailing the ontent Service. E.g. Stock Information, Books, or obile Accessories. This item gives a more general definition of the transaction than the Transaction Detail Description. 0 ontent ontent Syntax error Length greater than 24 characters. onditionality andatory within group ontent Service Used. Values: Limited to maximum 24 characters length Transaction Status Indicates the status of the Transaction when the status is anything other than Normal or Success. ontent ontent Value out of range. Present within group ontent Transaction Basic Info when the status of the transaction is other than Normal/Success. Transfer Batch Values: 0 Unconfirmed 1 Failed A TAP file which must contain at least one all Event Detail and must also contain supporting Batch ontrol Information and Audit ontrol Information. Accounting Information must be present where any all Event 3.11.05 Page 164 of 217 30 31 Tf Batch Tf Batch andatory group Batch ontrol Information missing within group. Group Accounting Information not present

ode Detail contains a charge. It may also contain essage Description Information details where these have been used within the batch. andatory within group Data Interchange. 32 34 35 36 ontext Tf Batch Tf Batch Tf Batch Tf Batch and a charge is present within the Transfer Batch. andatory group Network Information missing within group. Group essage Description Information not present and a Service entre Usage is present within Transfer Batch. Group all Event Details not present within group. andatory group Audit ontrol Information missing from group. Transfer ut Off Timestamp The timestamp used to select calls for transfer. All call records available prior to the timestamp are transferred. This gives an indication to the HPN as to how 'up-to-date' the information is. Btch trl Btch trl Note: Error code 33 removed in TAP release 3.11 (01 ay 05). Value out of range. Where the timestamp is present within a Notification file it is nominal showing that no data available for transfer are being held by the Sender PN with a harging Timestamp prior to this. 30 Btch trl andatory associated item UT Time Offset missing. The time is given in the local time of the Sender PN. There must be a UT Time Offset associated with the item. andatory within group Notification. andatory within group Batch ontrol Information. Transparency Indicator Format: YYDDHHSS An indicator which shows whether the service was used in transparent or non-transparent mode. The item is applicable only to UTS calls. O T 3.11.05 Page 165 of 217

ode Derivation: GS item TransparencyIndicator (GS 32.005). ontext O T Value out of range. ust be present within group Basic Service where call is UTS and the indicator is relevant. User Protocol Indicator Values: 0 Transparent 1 Non-Transparent This item identifies the high layer user protocol signalled between the mobile station and the network. O T Derivation: Derived values using bits 0-3 of GS/UTS item Rate Indication as defined in TS 3GPP 32.005. The 'Source Value' (see Values below) is derived using Other Rate Adaption bits (2 & 3) followed by Rate Adaption bits (0 & 1). O T Value out of range. ust be present within group Basic Service where derivable from the network supplied data (i.e. Rate Indication). Values: UPI Source Value Value eaning (Rate Indication bits 2&3, 0&1) 0 no rate adaption nn00 1 V.1, I.460/X.30 nn01 rate adaption 2 ITU-T X.31 flag stuffing nn 3 V.1 0011 * 4 H.223 & H.245 0111 5 PIAFS 11 note nn represents any value 3.11.05 Page 166 of 217

ode UT Time Offset * note that H.324 (which is used by circuit switched video telephony) uses the "H.223/H.245" setting at the protocol level. All timestamps are in the local time of the Sender PN (or Serving Network where appropriate). So that the time can be equated to time in the Recipient PN, the difference between local time and UT time must be supplied. 11 ontext Notifictn Network Derivation: UT Time Offset = Local Time minus UT Time 12 Btch trl Syntax error and associated item is File reation Timestamp. Example: Washington D, USA 00hrs /Oct/97 UT Time 1500hrs /Oct/97 13 Btch trl Syntax error and associated item is Transfer ut Off Timestamp. UT Time Offset = - 15 = -5 14 Btch trl Syntax error and associated item is File Available Timestamp. adrid, Spain UT Time 1600hrs /Oct/97 1500hrs /Oct/97 15 Audit Syntax error and associated item is Earliest all Timestamp. UT Time Offset = 16-15 = +1 16 Audit Syntax error and associated item is Latest all Timestamp. Sydney, Australia 00hrs 11/Oct/97 Notifictn Value out of range. UT Time 1500hrs /Oct/97 UT Time Offset = (01 + 24) - 15 = + (note that where dates are different 24 hours are added to the time of the greater date) 21 22 Network Btch trl Value out of range. Value out of range and associated item is File reation Timestamp. andatory within items 23 Btch trl Value out of range and associated item is Transfer ut Off Timestamp. File reation Timestamp Transfer ut Off Timestamp 24 Btch trl Value out of range and associated item is File Available Timestamp. File Available Timestamp 25 Audit Value out of range and associated item is Earliest all Timestamp. 3.11.05 Page 167 of 217

ode Earliest all Timestamp Latest all Timestamp andatory within group UT Time Offset Information. Note that the HPN needs the location and UT Time Offset for each type of timestamp. On a call level there might be more than one UT Time Offset valid. ontext 26 Audit Value out of range and associated item is Latest all Timestamp. Format: ±HH UT Time Offset ode Range: -1300 to +1300 in steps of 15 (minutes)- A code associated with a UT Time Offset. The code is used with harging Timestamp, Deposit Timestamp and ompletion Timestamp to enable conversion of the Sender PN s local time to UT time. 11 Network alls Network Value out of range. andatory within group UT Time Offset Information. andatory within items 0 alls Specified UT Time Offset ode not defined in group UT Time Offset Information. Values: Range 0.. 99 all Event Start Timestamp harging Timestamp harge Detail Timestamp Deposit Timestamp ompletion Timestamp Order Placed Timestamp Requested Delivery Timestamp Actual Delivery Timestamp LS Request Timestamp PDP ontext Start Timestamp 3.11.05 Page 168 of 217

ode UT Time Offset Information A table containing UT Time Offset 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. odes are reusable from transfer to transfer. One or more occurrences must be present within group Network Information. 30 31 32 ontext Network Network Network andatory item UT Time Offset ode missing within group. andatory item UT Time Offset missing within group. ore than one occurrence of group with same UT Time Offset ode where UT Time Offset is not the same. 33 Network ore than one occurrence of group with same UT Time Offset ode where UT Time Offset is the same. Vertical Accuracy Delivered The vertical accuracy delivered for an LS request measured in metres. Derivation: GS/UTS item Ext-GeographicalInformation (TS 29.002, TS 32.002). The contents of the first octet indicates the 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 formulas referenced in TS 23.032. The result must be rounded to full metres. ust be present within group LS QoS Delivered where available from the network Vertical Accuracy Requested The vertical accuracy requested for an LS request measured in metres. Derivation: LS QoS IE Octet 5 (3GPP TS 49.031). 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 formulas referenced in 3GPP TS 23.032. The 3.11.05 Page 169 of 217

ode resulting value needs to be rounded to full metres. Note that TS 23.032 specifies different formulas for the calculation of the horizontal and vertical accuracy in metres. ust be present within group LS QoS Requested where available from the network ontext 3.11.05 Page 170 of 217

ontext Abbreviations Table Abbreviation ontext Acctng Accounting Information Audit Audit ontrol Information Btch trl Batch ontrol Information alls all Event Details ontent ontent Transaction all LS Location Service ess Desc essage Description Information O obile Originated all T obile Terminated all Network Network Information Notifictn Notification SU Service entre Usage SS Supplementary Service Event Tf Batch Transfer Batch 3.11.05 Page 171 of 217

5 LASSIFIATION OF ERRORS All errors are assigned one of the following severity levels: 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 HPN can refuse liability for the complete file. Records with severe errors affect the ability to charge the subscriber. They should not have been forwarded by the VPN Operator to the HPN Operator who may reject financial liability for the individual call/event, a rejected call/event may be included in a rejects and returns process where available. Records with warnings are billable, i.e. the problem does not affect the ability of the HPN 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 HPN 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 VPN 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 '' and a '' error the Recipient is advised to use the '' error and not the '' 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. The following rules apply to the naming and numbering of errors defined in the data dictionary: Error ode Range to 19 Format Errors The data does not match the picture value, e.g. alpha character in numeric field. The error description refers to these values as 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 (e.g. 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. 3.11.05 Page 173 of 217

Error ode Range 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. All these errors are uniquely identified by error code and field name. 30 to 49 Invalid group structure The group has elements either missing but expected or present and not expected, i.e. the structure of the group is invalid. All these errors are uniquely identified by error code and field name. 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. 0 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 0 to 199 and are uniquely identified by error code and field name. 0 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 0 to 249 and are uniquely identified by error code and field name. 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. Other general errors not listed in the data dictionary: Error ode ontext 3.11.05 Page 174 of 217

Error ontext ode 50 Notifictn Tf Batch 51 Notifictn Tf Batch 52 Notifictn Tf Batch 53 Notifictn Tf Batch 54 Notifictn Tf Batch Unknown tag. The tag is not recognised as a valid tag within TAP and does not occur at extensibility 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. Non repeating element occurs more than once within the group. Tag invalid within context, e.g. O Basic all Information occurring within obile Terminated all and does not occur at extensibility marker position. File not encoded according to ASN.1 BER. Note: Recipient may require files encoded according to strict BER. Binary data after the first valid ASN.1 unit present in file and ignored. 55 All 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 Encoded INTEGER larger than 8 bytes. 57 All Valid ASN.1 encoded information found and ignored at extensibility marker position. Note: Further processing of the ASN.1 data identified as being part of extensibility marker information must not be applied. 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 - 19-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 PN. The above error 52 can only be applied if the physical ASN.1 syntax is violated. Logical errors cannot be rejected using error 52. 3.11.05 Page 175 of 217

For example: A all Type Group present within the harge Information for a T 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. A VPN cannot treat an item with length zero as an invalid BER encoding, i.e. 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 HPN can only raise one of the following errors: error code (syntax error) on item Tax Value in the alls context. error code 31 (tax value missing) on group Tax Information in the alls 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.1 Validation rules not described in the Data Dictionary Error ode ontext 250 O all is duplicate. hargeable Subscriber, Recording Entity Type and Identification, all Event Start Time, alled Number, Service ode and Total all Duration match call record already processed and the call reference is identical in both call records. If alled Number is not present Dialled Digits must be used. 251 T all is duplicate. hargeable 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 Event is duplicate. hargeable 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 SU Event is duplicate. SU hargeable subscriber, Recording Entity Type and Identification, deposit timestamp, non charged number and message type match call record already processed. 3.11.05 Page 176 of 217

Error ode ontext 255 all is duplicate. Recording Entity Type and Identification (where the type is GGSN or WLAN Billing Information Recording Entity), harging Id and all Event Start Time match call record already processed. 256 ontent all is duplicate if ontent Provider Name, Transaction Identifier, harge Refund Indicator match ontent Transaction already processed. 257 LS all is duplicate if Recording Entity Type and Identification, all Reference, LS Request Timestamp, Response Time, Tracking ustomer and Tracked ustomer is the same as Location Service record already processed. Note: The duplicate check is made against previously accepted records, i.e. previously rejected records may be resubmitted when corrected by the VPN subject to a rejects and returns process being available. When the call reference is not present calls may be mistakenly detected as duplicate calls e.g. in specific cases of call forwarding. Such cases should be handled with care and any disputes must be resolved manually. Note that where hargeable Subscriber is referenced above for duplicate call check purposes ISI or IN by itself is sufficient. When ISI or IN is present in a call SISDN and/or DN, when also present in the same call, must not be included when performing the duplicate check. 142 alls all Event Details ends after the File Available Timestamp. The timestamp of the call event completion may be calculated from the all Event Start Timestamp and the Total all Event Duration. For SU the ompletion Timestamp should be taken into consideration For ontent 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 LS Request Timestamp must be used in conjunction with the Response Time. 260 alls all old. all is older than Standard Timescale specified in BARG PRD BA.08. 261 alls all older than allowed by BARG in Exceptional Situations in BARG PRD BA.08 262 Btch trl Notifictn Difference between actual date/time file received and File Available Timestamp is greater than the Standard File Transmission Timescale as specified in BARG PRD BA.08. 3.11.05 Page 177 of 217

Error ode ontext 263 Btch trl Difference between actual date/time file received and File Available Timestamp is greater than the Exceptional File Transmission Timescale as specified in BARG PRD BA.08. Note: all 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 (e.g. UT). In case of SU either the completion or deposit timestamp should be used to get call event age depending on the value of charging point: completion time when and deposit time when D In the case of ontent 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 LS 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 Total number of occurrences of group all Event Details within the TAP transfer batch exceeds 0,000. 271 Tf Batch The size of the TAP transfer batch file is larger than 0b 5.2 Text Representation of IP Addresses This error should not be applied if the file can be processed.. 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. ompression of zeros by usage of the symbol ;; is not allowed. Presentation of the last 2 sections of the address in IPv4 format is not allowed either. This representation is recommended by the relevant RF documents. Examples of valid IPv6 addresses: FED:BA98:7654:32:FED:BA98:7654:32 80:0:0:0:8:800:0:417A 3.11.05 Page 178 of 217

6 PHYSIAL STRUTURE 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. Accordingly, the specification of the physical format consists of two parts: 6.1 Abstract Syntax 1. The definition of the abstract syntax. 2. The definition of the transfer syntax (i.e. the encoding rules). This section defines the abstract syntax for Data Record Format version 03 using the ASN.1 standard as specified within ITU Rec. X.680. 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 OTET 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: SEQUENE / SEQUENE OF HOIE 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. ost 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 Total harge Total Discount Value Total Tax Value Data Volume Incoming Data Volume Outgoing hargeable Units ontext Audit Audit Audit, ontent, ontent, ontent 3.11.05 Page 179 of 217

Element harged Units harging Id Total Discount Refund Total harge Refund Total Advised harge Total Advised harge Refund Total ommission Total ommission Refund Total Data Volume Total Tax Refund ontext, ontent Audit Audit Audit Audit Audit Audit ontent Audit For any othe 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,. ommon 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. TADIG also recommends to use strict BER for TAP file encoding and relaxed BER for decoding TAP files. 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 predecoding 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 9 to 13 In use for TAP 13 Reserved for TAP use - application # released TAP 3.11 14 to 17 In use for TAP 18 to 31 Reserved for TAP use 32 Reserved for TAP use - application # released TAP 3.4 33 to 35 Reserved for TAP use - application # released TAP 3.11 3.11.05 Page 180 of 217

Tag range Description 36 to 46 In use for TAP 47 to 48 Reserved for TAP use application # released TAP 3.4 49 to 50 Reserved for TAP use - application # released TAP 3.11 51 Reserved for TAP use - application # released TAP 3. 52 to 54 Reserved for TAP use - application # released TAP 3.11 55 to 59 In use for TAP 60 to 61 Reserved for TAP use - application # released TAP 3.11 62 to 76 In use for TAP 77 to 78 Reserved for TAP use - application # released TAP 3.11 79 to 80 In use for TAP 81 to 84 Reserved for TAP use - application # released TAP 3.11 85 to 86 Reserved for TAP use - application # released TAP 3.11 87 to 92 In use for TAP 93 Reserved for TAP use - application # released TAP 3.11 94 to 98 In use for TAP 99 to 0 Reserved for TAP use - application # released TAP 3.11 1 In use for TAP 2 Reserved for TAP use - application # released TAP 3.11 3 to 111 In use for TAP 112 Reserved for TAP use - application # released TAP 3.11 113 to 118 In use for TAP 119 to 1 Reserved for TAP use - application # released TAP 3.11 121 to 123 In use for TAP 124 to 127 Reserved for TAP use - application # released TAP 3.11 128 to 129 In use for TAP 130 to 132 Reserved for TAP use - application # released TAP 3.11 133 In use for TAP 134 Reserved for TAP use - application # released TAP 3.11 135 to 136 In use for TAP 137 Reserved for TAP use - application # released TAP 3.11 138 In use for TAP 139 to 140 Reserved for TAP use - application # released TAP 3.11 3.11.05 Page 181 of 217

Tag range Description 141 to 142 In use for TAP 143 In use for TAP and RAP 144 to 147 In use for TAP 148 Reserved for TAP use - application # released TAP 3.11 149 Reserved for TAP use - application # released TAP 3. 150 to 151 Reserved for TAP use - application # released TAP 3.11 152 to 153 In use for TAP 154 to 155 Reserved for TAP use - application # released TAP 3.11 156 In use for TAP 157 to 158 Reserved for TAP use - application # released TAP 3.11 159 In use for TAP 160 Reserved for TAP use - application # released TAP 3. 161 Reserved for TAP use - application # released TAP 3.11 162 to 167 In use for TAP 168 Reserved for TAP use - application # released TAP 3.11 169 to 170 In use for TAP 171 Reserved for TAP use - application # released TAP 3.11 172 Reserved for TAP use - application # released TAP 3.4 173 to 176 Reserved for TAP use - application # released TAP 3.11 177 to 178 Reserved for TAP use application # released TAP 3.4 179 to 180 Reserved for TAP use - application # released TAP 3.11 181 to 186 In use for TAP 187 Reserved for TAP use 188 to 190 In use for TAP 190 Reserved for TAP use - application # released TAP 3.11 191 to 193 In use for TAP 194 Reserved for TAP use 195 to 196 In use for TAP 197 Reserved for TAP use 198 to 1 In use for TAP 2 to 3 Reserved for TAP use - application # released TAP 3.11 4 In use for TAP 5 Reserved for TAP use 6 In use for TAP 7 Reserved for TAP use - application # released TAP 3.11 8 to 219 In use for TAP 3.11.05 Page 182 of 217

Tag range Description 2 to 222 Reserved for TAP use - application # released TAP 3.11 223 In use for TAP 224 Reserved for TAP use - application # released TAP 3.11 225 to 228 In use for TAP 229 Reserved for TAP use - application # released TAP 3.11 230 Reserved for TAP use - application # released TAP 3. 231 to 234 In use for TAP 235 to 243 Reserved for TAP use - application # released TAP 3.11 244 to 245 In use for TAP 246 to 247 Reserved for TAP use - application # released TAP 3.11 248 Reserved for TAP use 249 Reserved for TAP use - application # released TAP 3.11 250 to 251 In use for TAP 252 Reserved for TAP use - application # released TAP 3.11 253 to 256 In use for TAP 257 Reserved for TAP use - application # released TAP 3.11 258 to 262 In use for TAP 263 to 264 Reserved for TAP use - application # released TAP 3.11 265 to 267 Reserved for TAP use - application # released TAP 3. 268 Reserved for TAP use - application # released TAP 3.11 269 Reserved for TAP use - application # released TAP 3. 270 to 275 Reserved for TAP use - application # released TAP 3.11 276 to 278 Reserved for TAP use - application # released TAP 3. 279 to 282 In use for TAP 283 to 284 Reserved for TAP use - application # released TAP 3.11 285 to 295 In use for TAP 296 Reserved for TAP use - application # released TAP 3.11 297 to 398 In use for TAP 3.11.05 Page 183 of 217

Tag range Description 399 Reserved for TAP use - application # released TAP 3.11 400 In use for TAP 401 Reserved for TAP use - application # released TAP 3.11 402 to 405 In use for TAP 406 Reserved for TAP use - application # released TAP 3.11 407 In use for TAP 408 to 409 Reserved for TAP use - application # released TAP 3.11 4 to 431 In use for TAP 432 to 511 Reserved for TAP use 512 to 23 Reserved for RAP usage 3.11.05 Page 184 of 217

-- -- -- The following ASN.1 specification defines the abstract syntax for -- -- Data Record Format Version 03 -- Release 11 -- -- 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) ommon, 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-0311 DEFINITIONS IPLIIT TAGS ::= BEGIN -- -- Structure of a Tap batch -- DataInterhange ::= HOIE { transferbatch TransferBatch, notification Notification,... } -- Batch ontrol 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 ontrol Information TransferBatch ::= [APPLIATION 1] SEQUENE { batchontrolinfo BatchontrolInfo OPTIONAL, -- *m.m. accountinginfo AccountingInfo OPTIONAL, networkinfo NetworkInfo OPTIONAL, -- *m.m. messagedescriptioninfo essagedescriptioninfolist OPTIONAL, calleventdetails alleventdetaillist OPTIONAL, -- *m.m. auditontrolinfo AuditontrolInfo OPTIONAL, -- *m.m.... } Notification ::= [APPLIATION 2] SEQUENE { sender Sender OPTIONAL, -- *m.m. recipient Recipient OPTIONAL, -- *m.m. filesequencenumber FileSequenceNumber OPTIONAL, -- *m.m. rapfilesequencenumber RapFileSequenceNumber OPTIONAL, filereationtimestamp FilereationTimeStamp OPTIONAL, fileavailabletimestamp FileAvailableTimeStamp OPTIONAL, -- *m.m. transferutofftimestamp TransferutOffTimeStamp OPTIONAL, -- *m.m. specificationversionnumber SpecificationVersionNumber OPTIONAL, -- *m.m. releaseversionnumber ReleaseVersionNumber OPTIONAL, -- *m.m. filetypeindicator FileTypeIndicator OPTIONAL, 3.11.05 Page 185 of 217

... } operatorspecinformation OperatorSpecInfoList OPTIONAL, alleventdetaillist ::= [APPLIATION 3] SEQUENE OF alleventdetail alleventdetail ::= HOIE { mobileoriginatedall obileoriginatedall, mobileterminatedall obileterminatedall, supplserviceevent SupplServiceEvent, serviceentreusage ServiceentreUsage, gprsall Gprsall, contenttransaction ontenttransaction,... } locationservice LocationService, -- -- Structure of the individual Tap records -- BatchontrolInfo ::= [APPLIATION 4] SEQUENE { sender Sender OPTIONAL, -- *m.m. recipient Recipient OPTIONAL, -- *m.m. filesequencenumber FileSequenceNumber OPTIONAL, -- *m.m. filereationtimestamp FilereationTimeStamp OPTIONAL, transferutofftimestamp TransferutOffTimeStamp OPTIONAL, -- *m.m. fileavailabletimestamp FileAvailableTimeStamp OPTIONAL, -- *m.m. specificationversionnumber SpecificationVersionNumber OPTIONAL, -- *m.m. releaseversionnumber ReleaseVersionNumber OPTIONAL, -- *m.m. filetypeindicator FileTypeIndicator OPTIONAL, rapfilesequencenumber RapFileSequenceNumber OPTIONAL,... } operatorspecinformation OperatorSpecInfoList OPTIONAL, AccountingInfo ::= [APPLIATION 5] SEQUENE { taxation TaxationList OPTIONAL, discounting DiscountingList OPTIONAL, localurrency Localurrency OPTIONAL, -- *m.m. tapurrency Tapurrency OPTIONAL, currencyonversioninfo urrencyonversionlist OPTIONAL,... } tapdecimalplaces TapDecimalPlaces OPTIONAL, -- *m.m. NetworkInfo ::= [APPLIATION 6] SEQUENE { utctimeoffsetinfo UtcTimeOffsetInfoList OPTIONAL, -- *m.m. recentityinfo RecEntityInfoList OPTIONAL,... } essagedescriptioninfolist ::= [APPLIATION 8] SEQUENE OF essagedescriptioninformation obileoriginatedall ::= [APPLIATION 9] SEQUENE { basicallinformation obasicallinformation OPTIONAL, -- *m.m. locationinformation LocationInformation OPTIONAL, -- *m.m. equipmentidentifier ImeiOrEsn OPTIONAL, basicserviceusedlist BasicServiceUsedList OPTIONAL, -- *m.m. supplserviceode SupplServiceode OPTIONAL, thirdpartyinformation ThirdPartyInformation OPTIONAL, 3.11.05 Page 186 of 217

... } camelserviceused amelserviceused OPTIONAL, operatorspecinformation OperatorSpecInfoList OPTIONAL, obileterminatedall ::= [APPLIATION ] SEQUENE { basicallinformation tbasicallinformation OPTIONAL, -- *m.m. locationinformation LocationInformation OPTIONAL, -- *m.m. equipmentidentifier ImeiOrEsn OPTIONAL, basicserviceusedlist BasicServiceUsedList OPTIONAL, -- *m.m.... } camelserviceused amelserviceused OPTIONAL, operatorspecinformation OperatorSpecInfoList OPTIONAL, SupplServiceEvent ::= [APPLIATION 11] SEQUENE { chargeablesubscriber hargeablesubscriber OPTIONAL, -- *m.m. rapfilesequencenumber RapFileSequenceNumber OPTIONAL, locationinformation LocationInformation OPTIONAL, -- *m.m. equipmentidentifier ImeiOrEsn OPTIONAL, -- *m.m.... } supplserviceused SupplServiceUsed OPTIONAL, -- *m.m. operatorspecinformation OperatorSpecInfoList OPTIONAL, ServiceentreUsage ::= [APPLIATION 12] SEQUENE { basicinformation ScuBasicInformation OPTIONAL, -- *m.m.... } rapfilesequencenumber RapFileSequenceNumber OPTIONAL, servingnetwork ServingNetwork OPTIONAL, recentityode RecEntityode OPTIONAL, -- *m.m. chargeinformation hargeinformation OPTIONAL, -- *m.m. scuhargetype ScuhargeType OPTIONAL, -- *m.m. scutimestamps ScuTimeStamps OPTIONAL, -- *m.m. operatorspecinformation OperatorSpecInfoList OPTIONAL, Gprsall ::= [APPLIATION 14] SEQUENE { gprsbasicallinformation GprsBasicallInformation OPTIONAL, -- *m.m. gprslocationinformation GprsLocationInformation OPTIONAL, -- *m.m. equipmentidentifier ImeiOrEsn OPTIONAL, gprsserviceused GprsServiceUsed OPTIONAL, -- *m.m.... } camelserviceused amelserviceused OPTIONAL, operatorspecinformation OperatorSpecInfoList OPTIONAL, ontenttransaction ::= [APPLIATION 17] SEQUENE { contenttransactionbasicinfo ontenttransactionbasicinfo OPTIONAL, -- *m.m. chargedpartyinformation hargedpartyinformation OPTIONAL, -- *m.m. servingpartiesinformation ServingPartiesInformation OPTIONAL, -- *m.m. contentserviceused ontentserviceusedlist OPTIONAL, -- *m.m. operatorspecinformation OperatorSpecInfoList OPTIONAL,... } LocationService ::= [APPLIATION 297] SEQUENE { rapfilesequencenumber RapFileSequenceNumber OPTIONAL, 3.11.05 Page 187 of 217

... } recentityode RecEntityode OPTIONAL, -- *m.m. callreference allreference OPTIONAL, trackingustomerinformation TrackingustomerInformation OPTIONAL, lsspinformation LSSPInformation OPTIONAL, trackedustomerinformation TrackedustomerInformation OPTIONAL, locationserviceusage LocationServiceUsage OPTIONAL, -- *m.m. operatorspecinformation OperatorSpecInfoList OPTIONAL, AuditontrolInfo ::= [APPLIATION 15] SEQUENE { earliestalltimestamp EarliestallTimeStamp OPTIONAL, latestalltimestamp LatestallTimeStamp OPTIONAL, totalharge Totalharge OPTIONAL, -- *m.m. totalhargerefund TotalhargeRefund OPTIONAL, totaltaxrefund TotalTaxRefund OPTIONAL, totaltaxvalue TotalTaxValue OPTIONAL, -- *m.m. totaldiscountvalue TotalDiscountValue OPTIONAL, -- *m.m. totaldiscountrefund TotalDiscountRefund OPTIONAL, totaladvisedhargevaluelist TotalAdvisedhargeValueList OPTIONAL, calleventdetailsount alleventdetailsount OPTIONAL, -- *m.m.... } operatorspecinformation OperatorSpecInfoList OPTIONAL, -- -- Tap data items and groups of data items -- AccessPointNameNI ::= [APPLIATION 261] AsciiString --(SIZE(1..63)) AccessPointNameOI ::= [APPLIATION 262] AsciiString --(SIZE(1..37)) ActualDeliveryTimeStamp ::= [APPLIATION 302] DateTime AddressStringDigits ::= BDString Advisedharge ::= [APPLIATION 349] harge Advisedhargeurrency ::= [APPLIATION 348] urrency AdvisedhargeInformation ::= [APPLIATION 351] SEQUENE { paidindicator PaidIndicator OPTIONAL, paymentethod Paymentethod OPTIONAL, advisedhargeurrency Advisedhargeurrency OPTIONAL, advisedharge Advisedharge OPTIONAL, -- *m.m. commission ommission OPTIONAL,... } AgeOfLocation ::= [APPLIATION 396] INTEGER BasicService ::= [APPLIATION 36] SEQUENE { serviceode BasicServiceode OPTIONAL, -- *m.m. transparencyindicator TransparencyIndicator OPTIONAL, fnur Fnur OPTIONAL,... } userprotocolindicator UserProtocolIndicator OPTIONAL, guaranteedbitrate GuaranteedBitRate OPTIONAL, maximumbitrate aximumbitrate OPTIONAL, BasicServiceode ::= [APPLIATION 426] HOIE 3.11.05 Page 188 of 217

{... } teleserviceode TeleServiceode, bearerserviceode BearerServiceode, BasicServiceodeList ::= [APPLIATION 37] SEQUENE OF BasicServiceode BasicServiceUsed ::= [APPLIATION 39] SEQUENE { basicservice BasicService OPTIONAL, -- *m.m. chargingtimestamp hargingtimestamp OPTIONAL, chargeinformationlist hargeinformationlist OPTIONAL, -- *m.m.... } hssdindicator HSSDIndicator OPTIONAL, BasicServiceUsedList ::= [APPLIATION 38] SEQUENE OF BasicServiceUsed BearerServiceode ::= [APPLIATION 40] HexString --(SIZE(2)) allednumber ::= [APPLIATION 407] AddressStringDigits alledplace ::= [APPLIATION 42] AsciiString alledregion ::= [APPLIATION 46] AsciiString alleventdetailsount ::= [APPLIATION 43] INTEGER alleventstarttimestamp ::= [APPLIATION 44] DateTime allingnumber ::= [APPLIATION 405] AddressStringDigits alloriginator ::= [APPLIATION 41] SEQUENE { callingnumber allingnumber OPTIONAL, clirindicator lirindicator OPTIONAL, ssoriginator SSOriginator OPTIONAL,... } allreference ::= [APPLIATION 45] OTET STRING --(SIZE(1..8)) alltypegroup ::= [APPLIATION 258] SEQUENE { calltype1 alltype1 OPTIONAL, -- *m.m. calltype2 alltype2 OPTIONAL, -- *m.m. calltype3 alltype3 OPTIONAL, -- *m.m.... } alltype1 ::= [APPLIATION 259] INTEGER alltype2 ::= [APPLIATION 255] INTEGER alltype3 ::= [APPLIATION 256] INTEGER ameldestinationnumber ::= [APPLIATION 404] AddressStringDigits amelinvocationfee ::= [APPLIATION 422] AbsoluteAmount amelservicekey ::= [APPLIATION 55] INTEGER amelservice ::= [APPLIATION 56] INTEGER amelserviceused ::= [APPLIATION 57] SEQUENE { 3.11.05 Page 189 of 217

... } camelservice amelservice OPTIONAL, camelservicekey amelservicekey OPTIONAL, -- *m.m. defaultallhandling DefaultallHandlingIndicator OPTIONAL, exchangerateode ExchangeRateode OPTIONAL, taxinformation TaxInformationList OPTIONAL, discountinformation DiscountInformation OPTIONAL, camelinvocationfee amelinvocationfee OPTIONAL, threegcameldestination ThreeGcamelDestination OPTIONAL, cseinformation seinformation OPTIONAL, auseforterm ::= [APPLIATION 58] INTEGER ellid ::= [APPLIATION 59] INTEGER harge ::= [APPLIATION 62] AbsoluteAmount hargeablesubscriber ::= [APPLIATION 427] HOIE { simhargeablesubscriber SimhargeableSubscriber, minhargeablesubscriber inhargeablesubscriber,... } hargeableunits ::= [APPLIATION 65] INTEGER hargedetail ::= [APPLIATION 63] SEQUENE { chargetype hargetype OPTIONAL, -- *m.m. charge harge OPTIONAL, -- *m.m.... } chargeableunits hargeableunits OPTIONAL, chargedunits hargedunits OPTIONAL, chargedetailtimestamp hargedetailtimestamp OPTIONAL, hargedetaillist ::= [APPLIATION 64] SEQUENE OF hargedetail hargedetailtimestamp ::= [APPLIATION 4] hargingtimestamp hargeditem ::= [APPLIATION 66] AsciiString --(SIZE(1)) hargedpartyequipment ::= [APPLIATION 323] SEQUENE { equipmentidtype EquipmentIdType OPTIONAL, -- *m.m. equipmentid EquipmentId OPTIONAL, -- *m.m.... } hargedpartyhomeidentification ::= [APPLIATION 313] SEQUENE { homeidtype HomeIdType OPTIONAL, -- *m.m. homeidentifier HomeIdentifier OPTIONAL, -- *m.m.... } hargedpartyhomeidlist ::= [APPLIATION 314] SEQUENE OF hargedpartyhomeidentification hargedpartyidentification ::= [APPLIATION 309] SEQUENE { chargedpartyidtype hargedpartyidtype OPTIONAL, -- *m.m. chargedpartyidentifier hargedpartyidentifier OPTIONAL, -- *m.m.... } 3.11.05 Page 190 of 217

hargedpartyidentifier ::= [APPLIATION 287] AsciiString hargedpartyidlist ::= [APPLIATION 3] SEQUENE OF hargedpartyidentification hargedpartyidtype ::= [APPLIATION 305] INTEGER hargedpartyinformation ::= [APPLIATION 324] SEQUENE { chargedpartyidlist hargedpartyidlist OPTIONAL, -- *m.m. chargedpartyhomeidlist hargedpartyhomeidlist OPTIONAL,... } chargedpartylocationlist hargedpartylocationlist OPTIONAL, chargedpartyequipment hargedpartyequipment OPTIONAL, hargedpartylocation ::= [APPLIATION 3] SEQUENE { locationidtype LocationIdType OPTIONAL, -- *m.m. locationidentifier LocationIdentifier OPTIONAL, -- *m.m.... } hargedpartylocationlist ::= [APPLIATION 321] SEQUENE OF hargedpartylocation hargedpartystatus ::= [APPLIATION 67] INTEGER hargedunits ::= [APPLIATION 68] INTEGER hargeinformation ::= [APPLIATION 69] SEQUENE { chargeditem hargeditem OPTIONAL, -- *m.m. exchangerateode ExchangeRateode OPTIONAL, calltypegroup alltypegroup OPTIONAL, chargedetaillist hargedetaillist OPTIONAL, -- *m.m. taxinformation TaxInformationList OPTIONAL,... } discountinformation DiscountInformation OPTIONAL, hargeinformationlist ::= [APPLIATION 70] SEQUENE OF hargeinformation hargerefundindicator ::= [APPLIATION 344] INTEGER hargetype ::= [APPLIATION 71] NumberString --(SIZE(2..3)) hargingid ::= [APPLIATION 72] INTEGER hargingpoint ::= [APPLIATION 73] AsciiString --(SIZE(1)) hargingtimestamp ::= [APPLIATION 74] DateTime lirindicator ::= [APPLIATION 75] INTEGER ommission ::= [APPLIATION 350] harge ompletiontimestamp ::= [APPLIATION 76] DateTime ontenthargingpoint ::= [APPLIATION 345] INTEGER ontentprovider ::= [APPLIATION 327] SEQUENE { contentprovideridtype ontentprovideridtype OPTIONAL, -- *m.m. contentprovideridentifier ontentprovideridentifier OPTIONAL, -- *m.m.... } 3.11.05 Page 191 of 217

ontentprovideridentifier ::= [APPLIATION 292] AsciiString ontentprovideridlist ::= [APPLIATION 328] SEQUENE OF ontentprovider ontentprovideridtype ::= [APPLIATION 291] INTEGER ontentprovidername ::= [APPLIATION 334] AsciiString ontentserviceused ::= [APPLIATION 352] SEQUENE { contenttransactionode ontenttransactionode OPTIONAL, -- *m.m. contenttransactiontype ontenttransactiontype OPTIONAL, -- *m.m. objecttype ObjectType OPTIONAL, transactiondescriptionsupp TransactionDescriptionSupp OPTIONAL, transactionshortdescription TransactionShortDescription OPTIONAL, -- *m.m. transactiondetaildescription TransactionDetailDescription OPTIONAL,... } transactionidentifier TransactionIdentifier OPTIONAL, -- *m.m. transactionauthode TransactionAuthode OPTIONAL, datavolumeincoming DataVolumeIncoming OPTIONAL, datavolumeoutgoing DataVolumeOutgoing OPTIONAL, totaldatavolume TotalDataVolume OPTIONAL, chargerefundindicator hargerefundindicator OPTIONAL, contenthargingpoint ontenthargingpoint OPTIONAL, chargeinformationlist hargeinformationlist OPTIONAL, advisedhargeinformation AdvisedhargeInformation OPTIONAL, ontentserviceusedlist ::= [APPLIATION 285] SEQUENE OF ontentserviceused ontenttransactionbasicinfo ::= [APPLIATION 304] SEQUENE { rapfilesequencenumber RapFileSequenceNumber OPTIONAL, orderplacedtimestamp OrderPlacedTimeStamp OPTIONAL, requesteddeliverytimestamp RequestedDeliveryTimeStamp OPTIONAL, actualdeliverytimestamp ActualDeliveryTimeStamp OPTIONAL, totaltransactionduration TotalTransactionDuration OPTIONAL,... } transactionstatus TransactionStatus OPTIONAL, ontenttransactionode ::= [APPLIATION 336] INTEGER ontenttransactiontype ::= [APPLIATION 337] INTEGER seinformation ::= [APPLIATION 79] OTET STRING --(SIZE(1..40)) urrencyonversion ::= [APPLIATION 6] SEQUENE { exchangerateode ExchangeRateode OPTIONAL, -- *m.m. numberofdecimalplaces NumberOfDecimalPlaces OPTIONAL, -- *m.m. exchangerate ExchangeRate OPTIONAL, -- *m.m.... } urrencyonversionlist ::= [APPLIATION 80] SEQUENE OF urrencyonversion ustomeridentifier ::= [APPLIATION 364] AsciiString ustomeridtype ::= [APPLIATION 363] INTEGER DataVolume ::= INTEGER DataVolumeIncoming ::= [APPLIATION 250] DataVolume DataVolumeOutgoing ::= [APPLIATION 251] DataVolume 3.11.05 Page 192 of 217

-- -- The following datatypes are used to denote timestamps. -- Each timestamp consists of a local timestamp and a -- corresponding UT time offset. -- Except for the timestamps used within the Batch ontrol -- Information and the Audit ontrol Information -- the UT time offset is identified by a code referencing -- the UtcTimeOffsetInfo. -- -- -- We start with the "short" datatype referencing the -- UtcTimeOffsetInfo. -- DateTime ::= SEQUENE { -- -- Local timestamps are noted in the format -- -- YYDDhhmmss -- -- where = century ('19', '',...) -- YY = year ('00' - '99') -- = month ('01', '02',..., '12') -- DD = day ('01', '02',..., '31') -- hh = hour ('00', '01',..., '24') -- mm = minutes ('00', '01',..., '59') -- ss = seconds ('00', '01',..., '59') -- localtimestamp LocalTimeStamp OPTIONAL, -- *m.m.... } utctimeoffsetode UtcTimeOffsetode OPTIONAL, -- *m.m. -- -- The following version is the "long" datatype -- containing the UT time offset directly. -- DateTimeLong ::= SEQUENE { localtimestamp LocalTimeStamp OPTIONAL, -- *m.m. utctimeoffset UtcTimeOffset OPTIONAL, -- *m.m.... } DefaultallHandlingIndicator ::= [APPLIATION 87] INTEGER DepositTimeStamp ::= [APPLIATION 88] DateTime Destination ::= [APPLIATION 89] SEQUENE { callednumber allednumber OPTIONAL, dialleddigits DialledDigits OPTIONAL, calledplace alledplace OPTIONAL,... } calledregion alledregion OPTIONAL, ssdestinationnumber SSDestinationNumber OPTIONAL, DestinationNetwork ::= [APPLIATION 90] NetworkId DialledDigits ::= [APPLIATION 279] AsciiString Discount ::= [APPLIATION 412] DiscountValue 3.11.05 Page 193 of 217

DiscountableAmount ::= [APPLIATION 423] AbsoluteAmount DiscountApplied ::= [APPLIATION 428] HOIE {... } fixeddiscountvalue FixedDiscountValue, discountrate DiscountRate, Discountode ::= [APPLIATION 91] INTEGER DiscountInformation ::= [APPLIATION 96] SEQUENE { discountode Discountode OPTIONAL, -- *m.m. discount Discount OPTIONAL, discountableamount DiscountableAmount OPTIONAL,... } Discounting ::= [APPLIATION 94] SEQUENE { discountode Discountode OPTIONAL, -- *m.m. discountapplied DiscountApplied OPTIONAL, -- *m.m.... } DiscountingList ::= [APPLIATION 95] SEQUENE OF Discounting DiscountRate ::= [APPLIATION 92] PercentageRate DiscountValue ::= AbsoluteAmount DistancehargeBandode ::= [APPLIATION 98] AsciiString --(SIZE(1)) EarliestallTimeStamp ::= [APPLIATION 1] DateTimeLong EquipmentId ::= [APPLIATION 290] AsciiString EquipmentIdType ::= [APPLIATION 322] INTEGER Esn ::= [APPLIATION 3] NumberString ExchangeRate ::= [APPLIATION 4] INTEGER ExchangeRateode ::= [APPLIATION 5] ode FileAvailableTimeStamp ::= [APPLIATION 7] DateTimeLong FilereationTimeStamp ::= [APPLIATION 8] DateTimeLong FileSequenceNumber ::= [APPLIATION 9] NumberString --(SIZE(5)) FileTypeIndicator ::= [APPLIATION 1] AsciiString --(SIZE(1)) FixedDiscountValue ::= [APPLIATION 411] DiscountValue Fnur ::= [APPLIATION 111] INTEGER GeographicalLocation ::= [APPLIATION 113] SEQUENE { servingnetwork ServingNetwork OPTIONAL, servingbid ServingBid OPTIONAL, servinglocationdescription ServingLocationDescription OPTIONAL,... } GprsBasicallInformation ::= [APPLIATION 114] SEQUENE 3.11.05 Page 194 of 217

{... } gprshargeablesubscriber GprshargeableSubscriber OPTIONAL, -- *m.m. rapfilesequencenumber RapFileSequenceNumber OPTIONAL, gprsdestination GprsDestination OPTIONAL, -- *m.m. calleventstarttimestamp alleventstarttimestamp OPTIONAL, -- *m.m. totalalleventduration TotalallEventDuration OPTIONAL, -- *m.m. causeforterm auseforterm OPTIONAL, partialtypeindicator PartialTypeIndicator OPTIONAL, pdpontextstarttimestamp PDPontextStartTimestamp OPTIONAL, networkinitpdpontext NetworkInitPDPontext OPTIONAL, chargingid hargingid OPTIONAL, -- *m.m. GprshargeableSubscriber ::= [APPLIATION 115] SEQUENE { chargeablesubscriber hargeablesubscriber OPTIONAL, pdpaddress PdpAddress OPTIONAL, networkaccessidentifier NetworkAccessIdentifier OPTIONAL,... } GprsDestination ::= [APPLIATION 116] SEQUENE { accesspointnameni AccessPointNameNI OPTIONAL, -- *m.m. accesspointnameoi AccessPointNameOI OPTIONAL,... } GprsLocationInformation ::= [APPLIATION 117] SEQUENE { gprsnetworklocation GprsNetworkLocation OPTIONAL, -- *m.m. homelocationinformation HomeLocationInformation OPTIONAL,... } geographicallocation GeographicalLocation OPTIONAL, GprsNetworkLocation ::= [APPLIATION 118] SEQUENE { recentity RecEntityodeList OPTIONAL, -- *m.m. locationarea LocationArea OPTIONAL, cellid ellid OPTIONAL,... } GprsServiceUsed ::= [APPLIATION 121] SEQUENE { issignallingontext ISSignallingontext OPTIONAL, datavolumeincoming DataVolumeIncoming OPTIONAL, -- *m.m. datavolumeoutgoing DataVolumeOutgoing OPTIONAL, -- *m.m. chargeinformationlist hargeinformationlist OPTIONAL, -- *m.m.... } GsmhargeableSubscriber ::= [APPLIATION 286] SEQUENE { imsi Imsi OPTIONAL, msisdn sisdn OPTIONAL,... } GuaranteedBitRate ::= [APPLIATION 4] OTET STRING -- (SIZE (1)) HomeBid ::= [APPLIATION 122] Bid HomeIdentifier ::= [APPLIATION 288] AsciiString 3.11.05 Page 195 of 217

HomeIdType ::= [APPLIATION 311] INTEGER HomeLocationDescription ::= [APPLIATION 413] LocationDescription HomeLocationInformation ::= [APPLIATION 123] SEQUENE {... } homebid HomeBid OPTIONAL, -- *m.m. homelocationdescription HomeLocationDescription OPTIONAL, -- *m.m. HorizontalAccuracyDelivered ::= [APPLIATION 392] INTEGER HorizontalAccuracyRequested ::= [APPLIATION 385] INTEGER HSSDIndicator ::= [APPLIATION 424] AsciiString --(SIZE(1)) Imei ::= [APPLIATION 128] BDString --(SIZE(7..8)) ImeiOrEsn ::= [APPLIATION 429] HOIE { imei Imei, esn Esn,... } Imsi ::= [APPLIATION 129] BDString --(SIZE(3..8)) ISSignallingontext ::= [APPLIATION 418] INTEGER InternetServiceProvider ::= [APPLIATION 329] SEQUENE { ispidtype IspIdType OPTIONAL, -- *m.m. ispidentifier IspIdentifier OPTIONAL, -- *m.m.... } InternetServiceProviderIdList ::= [APPLIATION 330] SEQUENE OF InternetServiceProvider IspIdentifier ::= [APPLIATION 294] AsciiString IspIdType ::= [APPLIATION 293] INTEGER ISPList ::= [APPLIATION 378] SEQUENE OF InternetServiceProvider NetworkIdType ::= [APPLIATION 331] INTEGER NetworkIdentifier ::= [APPLIATION 295] AsciiString Network ::= [APPLIATION 332] SEQUENE { networkidtype NetworkIdType OPTIONAL, -- *m.m. networkidentifier NetworkIdentifier OPTIONAL, -- *m.m.... } NetworkList ::= [APPLIATION 333] SEQUENE OF Network LatestallTimeStamp ::= [APPLIATION 133] DateTimeLong LSQosDelivered ::= [APPLIATION 390] SEQUENE { lstransactionstatus LSTransactionStatus OPTIONAL, horizontalaccuracydelivered HorizontalAccuracyDelivered OPTIONAL, verticalaccuracydelivered VerticalAccuracyDelivered OPTIONAL, responsetime ResponseTime OPTIONAL, 3.11.05 Page 196 of 217

... } positioningethod Positioningethod OPTIONAL, trackingperiod TrackingPeriod OPTIONAL, trackingfrequency TrackingFrequency OPTIONAL, ageoflocation AgeOfLocation OPTIONAL, LSQosRequested ::= [APPLIATION 383] SEQUENE { lsrequesttimestamp LSRequestTimestamp OPTIONAL, -- *m.m. horizontalaccuracyrequested HorizontalAccuracyRequested OPTIONAL,... } verticalaccuracyrequested VerticalAccuracyRequested OPTIONAL, responsetimeategory ResponseTimeategory OPTIONAL, trackingperiod TrackingPeriod OPTIONAL, trackingfrequency TrackingFrequency OPTIONAL, LSRequestTimestamp ::= [APPLIATION 384] DateTime LSSPIdentification ::= [APPLIATION 375] SEQUENE { contentprovideridtype ontentprovideridtype OPTIONAL, -- *m.m. contentprovideridentifier... } ontentprovideridentifier OPTIONAL, -- *m.m. LSSPIdentificationList ::= [APPLIATION 374] SEQUENE OF LSSPIdentification LSSPInformation ::= [APPLIATION 373] SEQUENE { lsspidentificationlist LSSPIdentificationList OPTIONAL, -- *m.m. isplist ISPList OPTIONAL, networklist NetworkList OPTIONAL,... } LSTransactionStatus ::= [APPLIATION 391] INTEGER Localurrency ::= [APPLIATION 135] urrency LocalTimeStamp ::= [APPLIATION 16] NumberString --(SIZE(14)) LocationArea ::= [APPLIATION 136] INTEGER LocationDescription ::= AsciiString LocationIdentifier ::= [APPLIATION 289] AsciiString LocationIdType ::= [APPLIATION 315] INTEGER LocationInformation ::= [APPLIATION 138] SEQUENE { networklocation NetworkLocation OPTIONAL, -- *m.m. homelocationinformation HomeLocationInformation OPTIONAL,... } geographicallocation GeographicalLocation OPTIONAL, LocationServiceUsage ::= [APPLIATION 382] SEQUENE { lsqosrequested LSQosRequested OPTIONAL, -- *m.m. lsqosdelivered LSQosDelivered OPTIONAL,... } chargingtimestamp hargingtimestamp OPTIONAL, chargeinformationlist hargeinformationlist OPTIONAL, -- *m.m. 3.11.05 Page 197 of 217

aximumbitrate ::= [APPLIATION 421] OTET STRING -- (SIZE (1)) dn ::= [APPLIATION 253] NumberString essagedescription ::= [APPLIATION 142] AsciiString essagedescriptionode ::= [APPLIATION 141] ode essagedescriptioninformation ::= [APPLIATION 143] SEQUENE { messagedescriptionode essagedescriptionode OPTIONAL, -- *m.m. messagedescription essagedescription OPTIONAL, -- *m.m.... } essagestatus ::= [APPLIATION 144] INTEGER essagetype ::= [APPLIATION 145] INTEGER in ::= [APPLIATION 146] NumberString --(SIZE(2..15)) inhargeablesubscriber ::= [APPLIATION 254] SEQUENE { min in OPTIONAL, -- *m.m. mdn dn OPTIONAL,... } obasicallinformation ::= [APPLIATION 147] SEQUENE { chargeablesubscriber hargeablesubscriber OPTIONAL, -- *m.m. rapfilesequencenumber RapFileSequenceNumber OPTIONAL, destination Destination OPTIONAL, destinationnetwork DestinationNetwork OPTIONAL, calleventstarttimestamp alleventstarttimestamp OPTIONAL, -- *m.m. totalalleventduration TotalallEventDuration OPTIONAL, -- *m.m. simtoolkitindicator SimToolkitIndicator OPTIONAL, causeforterm auseforterm OPTIONAL,... } sisdn ::= [APPLIATION 152] BDString --(SIZE(1..8)) tbasicallinformation ::= [APPLIATION 153] SEQUENE { chargeablesubscriber hargeablesubscriber OPTIONAL, -- *m.m. rapfilesequencenumber RapFileSequenceNumber OPTIONAL, calloriginator alloriginator OPTIONAL, originatingnetwork OriginatingNetwork OPTIONAL, calleventstarttimestamp alleventstarttimestamp OPTIONAL, -- *m.m. totalalleventduration TotalallEventDuration OPTIONAL, -- *m.m. simtoolkitindicator SimToolkitIndicator OPTIONAL, causeforterm auseforterm OPTIONAL,... } NetworkAccessIdentifier ::= [APPLIATION 417] AsciiString NetworkId ::= AsciiString --(SIZE(1..6)) NetworkInitPDPontext ::= [APPLIATION 245] INTEGER NetworkLocation ::= [APPLIATION 156] SEQUENE { recentityode RecEntityode OPTIONAL, -- *m.m. callreference allreference OPTIONAL, 3.11.05 Page 198 of 217

... } locationarea LocationArea OPTIONAL, cellid ellid OPTIONAL, NonhargedNumber ::= [APPLIATION 402] AsciiString NumberOfDecimalPlaces ::= [APPLIATION 159] INTEGER ObjectType ::= [APPLIATION 281] INTEGER OperatorSpecInfoList ::= [APPLIATION 162] SEQUENE OF OperatorSpecInformation OperatorSpecInformation ::= [APPLIATION 163] AsciiString OrderPlacedTimeStamp ::= [APPLIATION 300] DateTime OriginatingNetwork ::= [APPLIATION 164] NetworkId PacketDataProtocolAddress ::= [APPLIATION 165] AsciiString PaidIndicator ::= [APPLIATION 346] INTEGER PartialTypeIndicator ::= [APPLIATION 166] AsciiString --(SIZE(1)) Paymentethod ::= [APPLIATION 347] INTEGER PdpAddress ::= [APPLIATION 167] PacketDataProtocolAddress PDPontextStartTimestamp ::= [APPLIATION 260] DateTime PlmnId ::= [APPLIATION 169] AsciiString --(SIZE(5)) Positioningethod ::= [APPLIATION 395] INTEGER Priorityode ::= [APPLIATION 170] INTEGER RapFileSequenceNumber ::= [APPLIATION 181] FileSequenceNumber RecEntityode ::= [APPLIATION 184] ode RecEntityodeList ::= [APPLIATION 185] SEQUENE OF RecEntityode RecEntityId ::= [APPLIATION 400] AsciiString RecEntityInfoList ::= [APPLIATION 188] SEQUENE OF RecEntityInformation RecEntityInformation ::= [APPLIATION 183] SEQUENE { recentityode RecEntityode OPTIONAL, -- *m.m. recentitytype RecEntityType OPTIONAL, -- *m.m. recentityid RecEntityId OPTIONAL, -- *m.m.... } RecEntityType ::= [APPLIATION 186] INTEGER Recipient ::= [APPLIATION 182] PlmnId ReleaseVersionNumber ::= [APPLIATION 189] INTEGER RequestedDeliveryTimeStamp ::= [APPLIATION 301] DateTime ResponseTime ::= [APPLIATION 394] INTEGER ResponseTimeategory ::= [APPLIATION 387] INTEGER 3.11.05 Page 199 of 217

ScuBasicInformation ::= [APPLIATION 191] SEQUENE { chargeablesubscriber ScuhargeableSubscriber OPTIONAL, -- *m.m. chargedpartystatus hargedpartystatus OPTIONAL, -- *m.m. nonhargednumber NonhargedNumber OPTIONAL, -- *m.m. clirindicator lirindicator OPTIONAL, originatingnetwork OriginatingNetwork OPTIONAL, destinationnetwork DestinationNetwork OPTIONAL,... } ScuhargeType ::= [APPLIATION 192] SEQUENE { messagestatus essagestatus OPTIONAL, -- *m.m. priorityode Priorityode OPTIONAL, -- *m.m.... } distancehargebandode DistancehargeBandode OPTIONAL, messagetype essagetype OPTIONAL, -- *m.m. messagedescriptionode essagedescriptionode OPTIONAL, -- *m.m. ScuTimeStamps ::= [APPLIATION 193] SEQUENE { deposittimestamp DepositTimeStamp OPTIONAL, -- *m.m. completiontimestamp ompletiontimestamp OPTIONAL, -- *m.m. chargingpoint hargingpoint OPTIONAL, -- *m.m.... } ScuhargeableSubscriber ::= [APPLIATION 430] HOIE { gsmhargeablesubscriber GsmhargeableSubscriber, minhargeablesubscriber inhargeablesubscriber,... } Sender ::= [APPLIATION 196] PlmnId ServingBid ::= [APPLIATION 198] Bid ServingLocationDescription ::= [APPLIATION 414] LocationDescription ServingNetwork ::= [APPLIATION 195] AsciiString ServingPartiesInformation ::= [APPLIATION 335] SEQUENE { contentprovidername ontentprovidername OPTIONAL, -- *m.m. contentprovideridlist ontentprovideridlist OPTIONAL, internetserviceprovideridlist InternetServiceProviderIdList OPTIONAL, networklist NetworkList OPTIONAL,... } SimhargeableSubscriber ::= [APPLIATION 199] SEQUENE { imsi Imsi OPTIONAL, -- *m.m. msisdn sisdn OPTIONAL,... } SimToolkitIndicator ::= [APPLIATION 0] AsciiString --(SIZE(1)) SSDestinationNumber ::= [APPLIATION 419] AsciiString SSOriginator ::= [APPLIATION 425] AsciiString SpecificationVersionNumber ::= [APPLIATION 1] INTEGER 3.11.05 Page 0 of 217

SsParameters ::= [APPLIATION 4] AsciiString --(SIZE(1..40)) SupplServiceActionode ::= [APPLIATION 8] INTEGER SupplServiceode ::= [APPLIATION 9] HexString --(SIZE(2)) SupplServiceUsed ::= [APPLIATION 6] SEQUENE { supplserviceode SupplServiceode OPTIONAL, -- *m.m. supplserviceactionode SupplServiceActionode OPTIONAL, -- *m.m. ssparameters SsParameters OPTIONAL, chargingtimestamp hargingtimestamp OPTIONAL, chargeinformation hargeinformation OPTIONAL, basicserviceodelist BasicServiceodeList OPTIONAL,... } Tapurrency ::= [APPLIATION 2] urrency TapDecimalPlaces ::= [APPLIATION 244] INTEGER TaxableAmount ::= [APPLIATION 398] AbsoluteAmount Taxation ::= [APPLIATION 216] SEQUENE { taxode Taxode OPTIONAL, -- *m.m. taxtype TaxType OPTIONAL, -- *m.m. taxrate TaxRate OPTIONAL, chargetype hargetype OPTIONAL,... } TaxationList ::= [APPLIATION 211] SEQUENE OF Taxation Taxode ::= [APPLIATION 212] INTEGER TaxInformation ::= [APPLIATION 213] SEQUENE { taxode Taxode OPTIONAL, -- *m.m. taxvalue TaxValue OPTIONAL, -- *m.m. taxableamount TaxableAmount OPTIONAL,... } TaxInformationList ::= [APPLIATION 214] SEQUENE OF TaxInformation TaxRate ::= [APPLIATION 215] NumberString (SIZE(7)) TaxType ::= [APPLIATION 217] AsciiString --(SIZE(2)) TaxValue ::= [APPLIATION 397] AbsoluteAmount TeleServiceode ::= [APPLIATION 218] HexString --(SIZE(2)) ThirdPartyInformation ::= [APPLIATION 219] SEQUENE { thirdpartynumber ThirdPartyNumber OPTIONAL, clirindicator lirindicator OPTIONAL,... } ThirdPartyNumber ::= [APPLIATION 403] AddressStringDigits ThreeGcamelDestination ::= [APPLIATION 431] HOIE { cameldestinationnumber ameldestinationnumber, 3.11.05 Page 1 of 217

... } gprsdestination GprsDestination, TotalAdvisedharge ::= [APPLIATION 356] AbsoluteAmount TotalAdvisedhargeRefund ::= [APPLIATION 357] AbsoluteAmount TotalAdvisedhargeValue ::= [APPLIATION 360] SEQUENE { advisedhargeurrency Advisedhargeurrency OPTIONAL, totaladvisedharge TotalAdvisedharge OPTIONAL, -- *m.m. totaladvisedhargerefund TotalAdvisedhargeRefund OPTIONAL, totalommission Totalommission OPTIONAL, totalommissionrefund TotalommissionRefund OPTIONAL,... } TotalAdvisedhargeValueList ::= [APPLIATION 361] SEQUENE OF TotalAdvisedhargeValue TotalallEventDuration ::= [APPLIATION 223] INTEGER Totalharge ::= [APPLIATION 415] AbsoluteAmount TotalhargeRefund ::= [APPLIATION 355] AbsoluteAmount Totalommission ::= [APPLIATION 358] AbsoluteAmount TotalommissionRefund ::= [APPLIATION 359] AbsoluteAmount TotalDataVolume ::= [APPLIATION 343] DataVolume TotalDiscountRefund ::= [APPLIATION 354] AbsoluteAmount TotalDiscountValue ::= [APPLIATION 225] AbsoluteAmount TotalTaxRefund ::= [APPLIATION 353] AbsoluteAmount TotalTaxValue ::= [APPLIATION 226] AbsoluteAmount TotalTransactionDuration ::= [APPLIATION 416] TotalallEventDuration TrackedustomerEquipment ::= [APPLIATION 381] SEQUENE { equipmentidtype EquipmentIdType OPTIONAL, -- *m.m. equipmentid EquipmentId OPTIONAL, -- *m.m.... } TrackedustomerHomeId ::= [APPLIATION 377] SEQUENE {... } homeidtype HomeIdType OPTIONAL, -- *m.m. homeidentifier HomeIdentifier OPTIONAL, -- *m.m. TrackedustomerHomeIdList ::= [APPLIATION 376] SEQUENE OF TrackedustomerHomeId TrackedustomerIdentification ::= [APPLIATION 372] SEQUENE {... } customeridtype ustomeridtype OPTIONAL, -- *m.m. customeridentifier ustomeridentifier OPTIONAL, -- *m.m. 3.11.05 Page 2 of 217

TrackedustomerIdList ::= [APPLIATION 370] SEQUENE OF TrackedustomerIdentification TrackedustomerInformation ::= [APPLIATION 367] SEQUENE { trackedustomeridlist TrackedustomerIdList OPTIONAL, -- *m.m. trackedustomerhomeidlist TrackedustomerHomeIdList OPTIONAL, trackedustomerloclist TrackedustomerLocList OPTIONAL,... } trackedustomerequipment TrackedustomerEquipment OPTIONAL, TrackedustomerLocation ::= [APPLIATION 380] SEQUENE {... } locationidtype LocationIdType OPTIONAL, -- *m.m. locationidentifier LocationIdentifier OPTIONAL, -- *m.m. TrackedustomerLocList ::= [APPLIATION 379] SEQUENE OF TrackedustomerLocation TrackingustomerEquipment ::= [APPLIATION 371] SEQUENE { equipmentidtype EquipmentIdType OPTIONAL, -- *m.m. equipmentid EquipmentId OPTIONAL, -- *m.m.... } TrackingustomerHomeId ::= [APPLIATION 366] SEQUENE {... } homeidtype HomeIdType OPTIONAL, -- *m.m. homeidentifier HomeIdentifier OPTIONAL, -- *m.m. TrackingustomerHomeIdList ::= [APPLIATION 365] SEQUENE OF TrackingustomerHomeId TrackingustomerIdentification ::= [APPLIATION 362] SEQUENE {... } customeridtype ustomeridtype OPTIONAL, -- *m.m. customeridentifier ustomeridentifier OPTIONAL, -- *m.m. TrackingustomerIdList ::= [APPLIATION 299] SEQUENE OF TrackingustomerIdentification TrackingustomerInformation ::= [APPLIATION 298] SEQUENE { trackingustomeridlist TrackingustomerIdList OPTIONAL, -- *m.m. trackingustomerhomeidlist TrackingustomerHomeIdList OPTIONAL, trackingustomerloclist TrackingustomerLocList OPTIONAL,... } trackingustomerequipment TrackingustomerEquipment OPTIONAL, TrackingustomerLocation ::= [APPLIATION 369] SEQUENE {... } locationidtype LocationIdType OPTIONAL, -- *m.m. locationidentifier LocationIdentifier OPTIONAL, -- *m.m. TrackingustomerLocList ::= [APPLIATION 368] SEQUENE OF TrackingustomerLocation TrackingFrequency ::= [APPLIATION 389] INTEGER 3.11.05 Page 3 of 217

TrackingPeriod ::= [APPLIATION 388] INTEGER TransactionAuthode ::= [APPLIATION 342] AsciiString TransactionDescriptionSupp ::= [APPLIATION 338] INTEGER TransactionDetailDescription ::= [APPLIATION 339] AsciiString TransactionIdentifier ::= [APPLIATION 341] AsciiString TransactionShortDescription ::= [APPLIATION 340] AsciiString TransactionStatus ::= [APPLIATION 303] INTEGER TransferutOffTimeStamp ::= [APPLIATION 227] DateTimeLong TransparencyIndicator ::= [APPLIATION 228] INTEGER UserProtocolIndicator ::= [APPLIATION 280] INTEGER UtcTimeOffset ::= [APPLIATION 231] AsciiString --(SIZE(5)) UtcTimeOffsetode ::= [APPLIATION 232] ode UtcTimeOffsetInfo ::= [APPLIATION 233] SEQUENE { utctimeoffsetode UtcTimeOffsetode OPTIONAL, -- *m.m. utctimeoffset UtcTimeOffset OPTIONAL, -- *m.m.... } UtcTimeOffsetInfoList ::= [APPLIATION 234] SEQUENE OF UtcTimeOffsetInfo VerticalAccuracyDelivered ::= [APPLIATION 393] INTEGER VerticalAccuracyRequested ::= [APPLIATION 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 ^TapDecimalPlaces. -- e.g. for TapDecimalPlaces = 3 the following values -- will be derived: -- 0 represents 0.000 -- 12 represents 0.012 -- 1234 represents 1.234 -- for TapDecimalPlaces = 5 the following values will be -- derived: -- 0 represents 0.00000 -- 1234 represents 0.01234 -- 123456 represents 1.23456 -- This data type is used to encode (total) -- charges, (total) discount values and -- (total) tax values. -- 3.11.05 Page 4 of 217

AbsoluteAmount ::= INTEGER Bid ::= AsciiString --(SIZE(5)) ode ::= INTEGER -- -- Non-tagged common data types -- -- -- Recommended common data types to be used for file encoding: -- -- The following definitions should be used for TAP file creation instead of -- the default specifications (OTET STRING) -- -- AsciiString ::= VisibleString -- -- urrency ::= 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 ::= OTET STRING -- -- The BDString data type (Binary oded 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. BDString ::= OTET STRING -- -- The currency codes from ISO 4217 -- are used to identify a currency -- urrency ::= OTET STRING -- -- HexString contains ISO 646 characters from 0 through 9, A, B,, D, E, F. -- HexString ::= OTET STRING -- -- NumberString contains ISO 646 characters from 0 through 9. -- NumberString ::= OTET 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. -- The decimal number representing the percentage -- rate is obtained by dividing the integer value by 0 -- Examples: 3.11.05 Page 5 of 217

-- -- 1500 represents 15.00 percent -- 1 represents 0.01 percent -- PercentageRate ::= INTEGER END 3.11.05 Page 6 of 217

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. 6.3 File Naming onventions 6.3.1 hargeable TAP Data TAP files containing chargeable data must follow the following naming convention: where DxxxxxyyyyySEQNO D xxxxx yyyyy SEQNO identifies the file as containing chargeable data contains the sender PN in uppercase contains the recipient PN in uppercase 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 xxxxx yyyyy SEQNO identifies the file as containing test data contains the sender PN in uppercase contains the recipient PN in uppercase contains the File Sequence Number 3.11.05 Page 7 of 217

ANNEX A: SUPPLEENTARY SERVIES 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 e.g. 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. all Hold and all Transfer, for example, are both invoked explicitly by the subscriber whereas all 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), 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 VPN operator, only one call event should be created for TAP, in order to support customer care enquiries by the HPN operator. Not all of the actions described are relevant for all supplementary services. Valid combinations are described in detail in 3GPP TS 22.004. The following table contains the relevant combinations for the purpose of TAP. For the purposes of the table a notation is used as follows: '-' An invalid combination of Service ode and Action (as defined by 3GPP TS 22.004). 3.11.05 Page 8 of 217

'Y' 'O' 'N' 'F' A valid and relevant combination of Service ode and Action which must be transferred in the TAP A valid and relevant combination of Service ode and Action which optionally can be transferred in the TAP for customer care purposes. A valid and relevant combination of Service ode and Action which must not be transferred in the TAP A valid and relevant combination of Service ode and Action that is for further study In addition to the actions described in 3GPP TS 22.004 further possible actions are described within the man-machine interface, 3GPP TS 22.030. 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. Supplementary Service Action Reg Era Act Deact Int Inv Pwd (0) (1) (2) (3) (4) (5) (6) 00 All supplementary services - - - - - - O All line identification service - - - - - - - 11 alling number identification - - - - N O - presentation 12 alling number identification - - O - N N - restriction 13 onnected number - - - - N N - identification presentation 14 onnected number - - N - N N - identification restriction All call forwarding - O - O - - - 21 all forwarding O O O O N - - unconditional 28 All conditional call O O O O - - - forwarding 29 all forwarding on mobile O O O O N Y - subscriber busy 2A all forwarding on no reply O O O O N Y - 2B all forwarding on subscriber O O O O N Y - not reachable 30 All call offering services - - - - - - - 31 all transfer - - - - - O - 40 All call completion services - - - - - - - 41 all waiting - - O O N N - 3.11.05 Page 9 of 217

Supplementary Service Action Reg Era Act Deact Int Inv Pwd (0) (1) (2) (3) (4) (5) (6) 42 all hold - - - - - O - 43 ompletion of calls to busy - - O O - O - subscribers 50 All multi party services - - - - - - - 51 ulti party service - - - - - O - 60 All community of interest - - - - - - - services 61 losed user groups - - - - - O - 70 All charging supplementary - - - - - - - services 71 Advice of charge - - - - - O - information 72 Advice of charge - charging - - - - - O - 80 All additional info transfer - - - - - - - services 81 User to user signalling - - O O - O - 90 All call barring O - - O - - N 91 All barring of outgoing call - - - O - - - services 92 Barring of all outgoing calls - - O O N - - 93 Barring of all outgoing - - O O N - - international calls 94 Barring of all outgoing - - O O N - - international except HPN 99 All barring of incoming call - - - O - - - services 9A Barring of all incoming calls - - O O N - - 9B Barring of all I calls when outside HPN - - O O N - - 3.11.05 Page 2 of 217

ANNEX B: HANGES FRO PREVIOUS SPEIFIATION VERSION NUBER 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 omments Version Simplification of TAP BARG 11 Simplification of data structures in line with BA.12. ajor changes include Replacement of HSSD parameters with simple indicator Simplification of AEL including representation of charges Simplification of harge Information including removal of Day ategory and Time Band information Removal of dual service codes (O/T) Removal of QoS in ~ replaced by inclusion of all Type 1/2/3 and new values for these items Removal of Value Added Service Removal of implementation annexes TADIG 11 Removal of implementation guidance annexes to new handbook (TD.58). Removal of redundant ASN.1 items TADIG 11 ASN.1 items no longer in use removed and application numbers released for future use. IS support BARG 11 Addition of IS Signalling Indicator. Additional items for UTS S bearer BARG 11 New items added to support UTS circuit switched bearer usage charging principles. larification of video telephony representation TADIG 11 Text addition to clarify technical representation of video telephony protocol. Enhanced flexibility of ASN.1 structures TADIG 11 Rationalisation of Recording Entity representation in physical format. Enhanced O duplicate check TADIG 11 ater for Dialled Digits within O duplicate check. Enhanced WLAN representation TADIG 11 Addition of specific username identification item. Revised derivation details for WLAN data volumes. Increase in allowable number of recording entities. Exchange Rate error at call level TADIG 11 hange exchange rate validation errors at call level from severe to fatal. Identification of SS destination number BARG 11 New item added to O for identification of actual SS destination number. Physical enhancement for non GS applications TADIG 11 Allow non telephony identification of non charged parties. Reduction in maximum TADIG 11 hange maximum TAP file size to 0b. file size. Satellite value in all Type BARG 11 Addition of new 'satellite' value in all Type 2. WLAN duplicate check TADIG 11 Enhancement to all duplicate check to cater for WLAN usage. Addition of Dialled Digits BARG New item Dialled Digits added to complement alled Number. 3.11.05 Page 211 of 217

Description Originator Release omments Version Additional validation for multiple basic services TADIG Additional validation to stop misrepresentation of basic service usage. Annex to clarify SS identification TADIG New annex to clarify how to distinguish S and PS SS usage. Annex to clarify various charge related items TADIG New annex detailing item population where harged Item is 'N', also population of tax items. Annex to clarify various timestamp & duration items TADIG New annex clarifying population of Total all Event Duration and related items within charging related items. Bilateral location and charge validation NA TADIG NA market area validation (bilateral) of location information (Serving BIDs and Serving Location Descriptions) and Air/Toll charge breakdown. AEL support in BARG Addition of AEL information to contexts. hange ASN.1 type (VAS elements) TADIG hange ASN.1 types for VAS Description and VAS Short Description. hange alled ountry representation BARG TADIG hange derivation of alled ountry ode to use ISO standard. hange to representation TADIG Tax information broken down to allow validation of taxes larification of timestamps in partials larification on alled Number and Dialled Digit population of tax value against taxable charges. TADIG larification on population of all Event Start Timestamp within intermediate and last partials. TADIG New annex giving examples of how to populate alled Number and Dialled Digits. larification on partial handling TADIG New annex giving guidelines re handling of partials. larification re BER usage TADIG larification that strict BER is to be used for encoding TAP. onsistent alled Number representation BARG alled Number to always be represented in 'international' format ontent Transaction ASN.1 correction TADIG hange of ASN.1 syntax to allow repeating ontent Service Used representation. Daily Usage harge support BARG larification of how to represent Daily Usage harges. Duplicate file handling clarification TADIG larification on how to handle duplicate files and reused sequence numbers. GL recording entity clarification TADIG larification on how to populate Recording Entity for GLs. cause for termination clarification TADIG larification to representation of cause for termination in partial cases. partial limits BARG Number of partials for single context limited. QoS parameters rationalised BARG GS and UTS QoS parameters rationalised to reflect charging requirement and infrastructure capability. BARG Additional validation to reject unexpected AEL invocation charges. Handling unexpected AEL information Increase integer sizes TADIG Various items of type INTEGER require size increases from 4 bytes to 8 bytes. 3.11.05 Page 212 of 217

Description Originator Release omments Version Invalid ASN.1 tag clarification TADIG larification regarding BER and syntax violation (invalid tags). Location Service support BARG New call/event to support Location Services (LS). arket area specific NA TADIG validation included Inclusion of bilateral validation for North American market. this is a market specific validation rather than only bi-polar bi-polar changes would not be included. -Services support BARG Addition of new item and item values to support m-services requirement. Partial Type validation BARG Partial Type Indicator validation severity increased to severe. Reference data constraints TADIG Various changes to validation severity and ranges to limit reference data tables to reasonable levels. SS events correction TADIG orrection to table of SS events eligible for inclusion in TAP. Additional validation to ensure tax is in line with roaming agreements Taxation validation BARG NA BARG UTS S bearer usage BARG Additional items and restructuring of existing items to allow differential pricing of UTS S bearer usage. USSD usage validation BARG Additional validation for USSD usage. USSD validation BARG Insertion of validation rules for USSD usage. Validation of commercial liability Validation of empty ASN.1 items Various general corrections WLAN support Additional validation for harging Timestamp larification of bilateral item validation larification of population of Destination group items larification to call timestamp derivation orrection to support SS orrection to Transfer ut Off Timestamp validation TADIG New validation to ensure that a HPN can reject financial liability for call/events dated prior to the commercial roaming start date either for new agreements or new services. TADIG larification on handling of zero length (empty) ASN.1 items. TADIG Value derivation corrections for QoS Peak Throughput, User Protocol Indicator. Removal of IOT references in discounting. orrection of contexts for VAS Used validation. larification/correction to valid ranges for various items of type AddressStringDigits. BARG TADIG Interim solution to enable WLAN support by reusing all elements. TADIG 09 New validation rule (severe error) to check integrity of harging Timestamp. TADIG 09 larification to validation rules applicable when bilateral items/groups present. TADIG 09 New appendix to clarify the derivation of Type Of Number and Numbering Plan, includes extracts from the relevant GS technical papers. TADIG 09 Addition of derivation and descriptive text to all Event Start Timestamp and harging Timestamp. TADIG 09 Allow GSN recording entity identification to contain either GSNAddress or sisdn. BARG 09 Existing validation severity to become fatal errors. 3.11.05 Page 213 of 217

Description Originator Release omments Version all duplicate check BARG 09 hange to the duplicate check to enforce only one all for any given part of a context (i.e. no separate SGSN and GGSN charging). Removal of Delivery Note information TADIG 09 Removal of all references to Delivery Note, now contained in TD.33. Revised all Type validation BARG 09 New validation to validate all Type information against the IOT. Serving Network TADIG 09 New syntax validation rule added. validation Tax treatment clarification BARG 09 Statement that ommission of tax information from a call/event where tax is applicable must be the same as zero tax (i.e. tax cannot be ommitted from the TAP file and later applied to an invoice only). Various editorial corrections Note Release Version skipped Note Release Version skipped Note Release Version skipped Note Release Versions 05-08 inclusive skipped Addition of ontent Transaction Addition of all partial context start timestamp Additional occurrences of free format data item alled Number Analysis presence rationalised hange Ipv6 address length TADIG 09 See the following: q Validation rules for Quality Of Service Used. q all Reference contexts. q harge Information diagram (Time Band Subtype). q Basic all Information diagram (harging Id). q Validation rules for Order Placed Timestamp, Requested Delivery Timestamp and Actual Delivery Timestamp. q Physical syntax optionality correction for ontent Transaction items. TADIG 08 Release Versions skipped to align PRD versions with TAP versions (see also TD.34 TAP Release anagement). TADIG 07 Release Versions skipped to align PRD versions with TAP versions (see also TD.34 TAP Release anagement). TADIG 06 Release Versions skipped to align PRD versions with TAP versions (see also TD.34 TAP Release anagement). TADIG 05 Release Versions skipped to align PRD versions with TAP versions (see also TD.34 TAP Release anagement). BARG 04 New all Event Details to cater for content transaction charging plus associated audit control information. TADIG 04 New item PDP ontext Start Timestamp for intermediate and last partials to identify true context start (optional item). TADIG 04 hange Operator Specific Information to be repeating. TADIG 04 alled Number Analysis group only required if Os or SUs present within file. TADIG 04 hange IPTextV6Address size to reflect standard (Rf 2373). 3.11.05 Page 214 of 217

Description Originator Release Version Exceptional file transmission timescale validation. Fix relative positions of Specification and Release Version Numbers within file. New item obile Directory Number New item Serving Network Pegged exchange rate validation. Support AEL usage within context omments BARG 04 Addition of 'fatal' validation for excessive differences between actual time a TAP file is received and the indicated availability timestamp. TADIG 04 larification to ensure version number items must never be moved from their relative positions within files. NA TADIG 04 New item DN to support mobile number portability within an inter standard roaming environment (IBER/TAP). TADIG 04 New item Serving Network to identify the serving network when this is not the TAP file sender. BARG 04 Revised/new validation to ensure variances from expected pegged exchange rates do not penalise the HPN. BARG 04 Addition of AEL usage data within all. hanges to AEL usage data structure to support invocation. TADIG 04 hargeable subscriber structure change within Support and inter standard roaming all to support INs and DNs. Support revised IOT BARG 04 hanges to all Type structure and values to structure support 3 level IOT structure. Support UTS QoS BARG 04 Addition of UTS QoS parameters within all. Additional call TADIG 03 Enhanced data item validation to ensure validation data integrity. ASN.1 list validation TADIG 03 larification of validation for ASN.1 lists. clarification BID/Serving location NA TADIG 03 Additional validation to support use of BIDs. validation Exchange Rate validation TADIG 03 Exchange Rate not required for zero rated calls. Rationalisation of TADIG 03 hanges to various reference data element reference data validation validation to ensure consistency. Removal of TADIG 03 Removal of rules 30 & 31 for all Event Details. incorrect/redundant Removal of rule 30 for Basic HSSD validation rules Parameters. SS identification BARG 03 Inclusion of SS address within Ts where SS received. Tax Value validation NA TADIG 03 changes hanges to relax Tax Value validation where the Sender has variable tax rates applicable to part or whole of the harge. Various clarifications TADIG 03 Upper case Sender and Recipient items. Derivation of harged and hargeable Units. eaning of 'reserved' values. Integer size within ASN.1 specification. all Type validation. UT Time Offset description. Support of charging for USSDs Support use of Notification within Rejects & Returns testing BARG 02 An interim solution for USSD charging; reuse of the Supplementary Service Event. TADIG 02 Addition of test file indicator (file type indicator) to Notification files. 3.11.05 Page 215 of 217

Description Originator Release omments Version Test timeliness of TAP file transfer. BARG 02 Addition of a validation rule comparing the File Available Timestamp with the actual date/time the file was received at the HPN (or their nominated agent). 14.4 kbps User Rate SERG 01 Addition of channel coding within HSSD. Additional call destination NAIG 01 Addition of called place and region information. details (mobile originated 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, e.g. national roaming. all level discounts BARG 01 Discount rates and absolute amounts per AEL phase 2 ause for termination BARG SERG BARG NAIG SERG call/event. All charges will be net of discounts. 01 Addition of AEL service level used and free format AEL server information. The followon feature will be supported by raising separate DRs for each follow-on leg. 01 Addition of cause for call termination information. harges by rate period NAIG 01 harge information allows provision of charges at rate period level. EFR BARG 01 Speech versions requested and used included. SERG Enhanced location information NAIG SATIG 01 Addition of longitude and latitude. Addition of served BID information and/or Enhancement to duplicate checks Extra decimal places on charge amounts. FIGS Flexible format encoding mechanism phase 1 descriptive location information. TADIG 01 Addition of S call reference number. BARG 01 Addition of a new item identifying the number of decimal places used throughout the TAP file. SG 01 Inclusion of a fraud monitoring indicator and third FF party number. GS 01 ASN.1 used. Associatio n BARG 01 Addition of a new call type for service SERG usage. NAIG 01 Addition of home BID information. Home market location information HPN Repricing BARG 01 Addition of type of call, day category and time band information. harge information structured to show changes in rate periods. HSSD Identification of local currency BARG SERG 01 Addition of HSSD information elements. TADIG 01 Addition of local currency item, i.e. the currency of the charge prior to conversion to SDRs (see Alternate TAP currency). 3.11.05 Page 216 of 217

Description Originator Release omments Version Identification of tax at call/event level BARG 01 All call charges will be exclusive of tax and specific tax values will be associated with each call/event, where appropriate. illennium compliance BARG TADIG 01 All dates expanded to include century information. SP BARG 01 SISDN used included on the transfer. SERG ultiple tax types IIG 01 The table of tax codes is enhanced to cater for Provision of non-specific data item Removal of table size constraints Separation of Air and Toll charges NAIG multiple types of tax NAIG 01 Inclusion of a general purpose item for use by bilateral agreement and its content will be specified between roaming partners. TADIG SATIG IIG NAIG 01 Supported by the flexible format. 01 Separate charge details may be supplied identifying individual elements of the invoiceable charge. SI Application Toolkit SERG 01 Addition of an indicator identifying where the call/event was initiated by the SI application toolkit. SPNP Support of multiple standard roaming Support of Rejects & Returns process Total call/event duration BARG SERG 01 Implicitly supported using AEL service usage information. SATIG 01 IS41 characteristics are supported by inclusion of the IN and ESN. BARG 01 Addition of item identifying data to be NAIG resubmitted having been previously rejected as BARG TADIG invalid. 01 Addition of total call duration. This allows calls where charging was by volume only to be age checked correctly. 3.11.05 Page 217 of 217