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

Transcription

1 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 Page 1 of 217

2 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 April 1999 Version update from GS Association approval. Document is approved as baseline for Specification Version Number 3 Release Version Number August 1999 Incorporation of R008; inclusion of essential corrections September 1999 Incorporation of Rs 009, 0, 011, 012, October 1999 Incorporation of Rs 014, January 00 Incorporation of Rs 016, 017, 018, 019, 0, 021, 022, ay 00 Incorporation of Rs 024, , , ay 00 Incorporation of R August 00 Incorporation of R 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, August 00 Incorporation of Rs December Incorporation of R 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 , arch 01 Incorporation of Rs 075, , 082, , 088, 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 arch 01 Incorporation of Rs 074, , , July 01 Incorporation of Rs 095, 096, 099 4, 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, , June 02 Version update from GS Association approval. Document is approved as baseline for major changes for Specification Version Number Page 2 of 217

3 Release Version Number Incorporation of Rs 094, 097, 9, 112, 125, 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 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, 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, , , 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 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 and 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, 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 , 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 Page 3 of 217

4 TABLE OF ONTENTS 1. Introduction Scope of the Document Terminology Structure of the Document Document ross References Differences from the ommercial Requirement Transfer Frequency File reation Timestamp File Available Timestamp Version ontrol Reference Tables Supplementary Services ell Identification Dates and Times File Size Limitations Support For Interstandard Number Portability Logical Structure Data Interchange Transfer Batch Batch ontrol Information Accounting Information Network Information obile Originated all O Basic all Information Location Information Basic Service Used harge Information AEL Service Used obile Terminated all T Basic all Information Supplementary Service Event Supplementary Service Used Service entre Usage all Basic all Information Service Used ontent Transaction ontent Transaction Basic Info harged Party Information ontent Service Used Advised harge Information Location Service Tracking ustomer Information Tracked ustomer Information Location Service Usage Audit ontrol Information Data Dictionary lassification of Errors Validation rules not described in the Data Dictionary Text Representation of IP Addresses Physical Structure Abstract Syntax Transfer Syntax File Naming onventions hargeable TAP Data Test TAP Data...7 ANNEX A: Supplementary Services Page 4 of 217

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

6 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 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 , which defines the data to be made available at the switch (S), and 3GPP TS , which defines charging data available 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 Page 6 of 217

7 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 Document ross References 3GPP TS GPP TS GPP TS GPP TS GPP TS GPP 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 GPP TS GPP TS IBER anual v2.0 GS Association PRD BA.08 v 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 v 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 v 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 Page 7 of 217

8 IETF RF 2869 IETF RF 791 ISO ISO 4217 ISO 646 ITU E.164 ITU-T Q.701 3GPP TS GPP TS GPP TS GPP TS GPP TS GPP TS 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 Page 8 of 217

9 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 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 File reation Timestamp The date and time of the file creation is included 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 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 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 Page 9 of 217

10 2.6. Supplementary Services Unlike 3GPP TS , 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 ell Identification The ell Id. Has been added 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 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 Page of 217

11 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 Page 11 of 217

12 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 Page 12 of 217

13 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 Page 13 of 217

14 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 Page 14 of 217

15 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 Page 15 of 217

16 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 Page 16 of 217

17 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 Page 17 of 217

18 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 Page 18 of 217

19 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 Page 19 of 217

20 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 Page of 217

21 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 Page 21 of 217

22 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 G AEL Destination Destination Figure 3.18 Tax Information Figure 3. Discount Information Figure Page 22 of 217

23 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 Page 23 of 217

24 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 Page 24 of 217

25 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 Page 25 of 217

26 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 Page 26 of 217

27 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 Page 27 of 217

28 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 Page 28 of 217

29 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 Page 29 of 217

30 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 Page 30 of 217

31 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 Page 31 of 217

32 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 Page 32 of 217

33 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 Page 33 of 217

34 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 Page 34 of 217

35 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 Page 35 of 217

36 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 Page 36 of 217

37 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 Page 37 of 217

38 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 Page 38 of 217

39 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 Page 39 of 217

40 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 Page 40 of 217

41 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 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 The original APN NI before modification by the SE in AEL APN NI field available within AEL Information as defined in 3GPP TS 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 Page 41 of 217

42 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 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 The original APN OI before modification by the SE in AEL APN OI field available within AEL Information as defined in 3GPP TS 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, Tf Batch Tf Batch No Taxation group present and batch contains taxes. No Discounting group present and batch Page 42 of 217

43 ode optionally, TAP urrency. ust be present within group Transfer Batch where any all Event Details contains a charge 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 ). 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 Page 43 of 217

44 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 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 Page 44 of 217

45 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 Page 45 of 217

46 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 ). 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 The value 0 indicates that the S is currently in contact with the network, whereas the value indicates that the location information is at least 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 Page 46 of 217

47 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 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 Page 47 of 217

48 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 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 Tf Batch Tf Batch andatory item Transfer ut Off Timestamp missing within group. File Sequence Number previously received Page 48 of 217

49 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 ) 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 and translating bits Page 49 of 217

50 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 Page 50 of 217