ITU-T D 190-2002 Exchange of international traffic accounting data between Administrations using electronic data interchange (EDI) techniques - SERIES D GENERAL TARIFF PRINCIPLES Gnth.pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMU N KATION STANDARDIZATION SECTOR OF ITU D.190 SERIES D: GENERAL TARIFF PRINCIPLES General tariff principles - Transmission of monthly international accounting information (06/2002) Exchange of international traffic accounting data between Administ

2、rations using electronic data interchange (EDI) techniques ITU-T Recommendation D. 190 ITU-T D-SERIES RECOMMENDATIONS GENERAL TARIFF PRINCIPLES TERMS AND DEFINITIONS GENERAL TARIFF PRINCIPLES Private leased telecommunication facilities Tariff principles applying to data communication services over d

3、edicated public data networks Charging and accounting in the international public telegram service Charging and accounting in the international telemessage service Principles applicable to GII-Internet Charging and accounting in the international telex service Charging and accounting in the internat

4、ional facsimile service Charging and accounting in the international videotex service Charging and accounting in the international phototelegraph service Charging and accounting in the mobile services Charging and accounting in the international telephone service Drawing up and exchange of internati

5、onal telephone and telex accounts International sound- and television-programme transmissions Charging and accounting for international satellite services Transmission of monthiy international accounting SeNice and privilege telecommunications Settlement of international telecommunication balances o

6、f accounts _,. Charging and accounting principles for intemational telecommunication services provided over the ISDN Charging and accounting principles for universal personal telecommunication Charging and accounting principles for intelligent network supported services Recommendations applicable in

7、 Europe and the Mediterranean Basin Recommendations applicable in Latin America Recommendations applicable in Asia and Oceania Recommendations applicable to the Afiican Region RECOMMENDATIONS FOR REGIONAL APPLICATION D.0 D.1-D.9 D.10-D.39 D.40-D.44 D.50-D.59 D.60-D.69 D.70-D.75 D.76-D.79 D.80-D.89 D

8、.90-D.99 D. 100-D. 159 D. 160-D. 179 D. 180-D. 184 D. 185-D.189 D.19GD.191 D. 192-D. 195 D. 196-D.209 D.210-D.279 D.280-D.284 D.45-D.49 D.285-D.299 D.300-D.399 D.400-D.499 D.500-D.599 D.600-D.699 For further details, please refer to the list of ITU-TRecommendations. ITU-T Recommendation D.190 Exchan

9、ge of international traffic accounting data between Administrations using electronic data interchange (EDI) techniques Summary The purpose of this Recommendation is to promote a set of common data standards which can be used by Administrations to exchange traffic accounting and settlement data with

10、each other using Electronic Data Interchange (EDI) techniques. The use of ED1 techniques is expected to provide a faster and more secure means of exchanging data, and to reduce costs by automating the process for entering data received from other Administrations to computer systems. Source ITU-T Rec

11、ommendation D.190 was prepared by ITU-T Study Group 3 (2001-2004) and approved under the WTSA Resolution 1 procedure on 14 June 2002. ITU-T Rec. D.190 (06/2002) i FOREWORD The International Telecommunication Union (ITLJ) is the United Nations specialized agency in the field of telecommunications. Th

12、e ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standa

13、rdization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information

14、technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INT

15、ELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights,

16、whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors ar

17、e cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 2002 Ail rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ii ITU-T Rec. D.190

18、 (06/2002) CONTENTS 1 Introduction 2 Purpose . 3 Common data standards 4 Standard message formats 5 Standard reference data codes 6 Procedure for sending and receiving data . Annex A . Flatfile format for monthly telephone and telex accounts . A.l Detailed records A.2 Subtotal and matching records .

19、 A.3 Set of code tables A.3.1 Carrier Code . A.3.2 Service Type Code - Unique Alpha code A.3.3 Traffic Type Code A.3.4 Currency Code Annex B . EDIFACT format for monthly telephone and telex accounts 1 1 1 1 2 2 6 ITU-T Rec . D.190 (06/2002) iii ITU-T Recommendation D.190 Exchange of international tr

20、affic accounting data between Administrations using electronic data interchange (EDO techniques 1 Introduction 1.1 The current practice is for Administrations to exchange monthly traffic accounts with each other for the international public-switched telephone, telex, telegram and packet-switched dat

21、a services, in accordance with ITU-T Recs D. 1 O, D.42 and D. 170, and for these accounts normally to be settled on a quarterly or monthly basis. Accounts for a number of other international telecommunication services may also be included in the traffic settlement process. 1.2 Most Administrations u

22、se a computer system to produce paper-based outgoing monthly traffic accounts which are then sent by mail or facsimile to other Administrations. Many Administrations also check and record the data contained in incoming monthly traffic accounts received from other Administrations by entering that dat

23、a into a computer system. Some Administrations use a computer system to produce quarterly or monthly settlement statements or to check and record those received from other Administrations. 2 Purpose 2.1 The purpose of this Recommendation is to promote a set of common data standards which can be used

24、 by Administrations to exchange traffic accounting and settlement data with each other ushg Electronic Data Interchange (EDI) techniques. 2.2 The use of ED1 techniques is expected to provide a faster and more secure means of exchanging data, and to reduce costs by automating the process for entering

25、 data received fiom other Administrations to computer systems. 3 Common data standards 3.1 The common data standards provide a set of standard message formats for exchanging traffic accounting and settlement data, and a set of standard codes for identifjmg the items of reference data used in those f

26、ormats. 3.2 The common data standards support both flatfile data formats and formats which conform to the EDIFACT standard. It is likely that some Administrations will adopt the flatfile format and some the EDIFACT format. Administrations capable of handling both will be able to exploit use of ED1 t

27、echniques to the fullest extent. 4 Standard message formats 4.1 i) Each message has three components: A header record which contains details of the receiving and sending Administrations and a brief description of the message, such as, a service type, year, month and sequence number for a monthly tra

28、ffic account. Detailed records containing the main body of the message. For example, the account line detailed of a monthly traffic account (see A. 1). ii) ITU-T Rec. D.190 (0612002) 1 iii) 5 5.1 i) ii) iii) iv) 5.2 5.2.1 A subtotal and matching record containing reconciliation totals to enable the

29、receiving Administration to confirm the completeness of the detail records received. Clause A.2 contains an example of the flatfile format for telephone and telex accounts and Annex B the EDIFACT equivalent. The two formats have a broadly similar content, with some differences of structure. Standard

30、 reference data codes Tables of standard reference data codes are maintained for the following kinds of data: Service Type codes with 2 alpha digits: for example TP = Telephone. Traffic Type codes with 4 alpha digits, including spaces: for example, AR = International Direct Dialling Reduced Rate. Cu

31、rrency codes of 3 alpha digits: for example XDR = Special Drawing Rights. AdministratiodROA Codes of 5 characters: 3 alpha, including spaces, and to identify the country, 2numeric to identify the Administration with the country. For example ABC0 1 = Country A Telecom Corporation. Flatfile formal for

32、 monthly telephone and telex accounts and set of code tables. Clauses A.l and A.2 show the Flatfile format for monthly telephone and telex accounts. The latest versions of this format can be downloaded fi-ee from the ETIS-ED1 website (http:/www.is.etis.org) or by contacting the ITU TSB. 5.2.2 Clause

33、 A.3 shows the convention for the code tables and types of codes available for use with the flatfile system. The code tables are regularly updated by the ETIS-ED1 Groupl. 5.3 Administrations which enter into bilateral agreements to use ED1 are requested to inform the TSB in order that its list can b

34、e augmented. 6 Procedure for sending and receiving data 6.1 The procedure for sending data is that the sending Administration converts the data produced by its computer system from its own internal data standard to the common data standard and sends it to the receiving Administration mailbox over an

35、 X.400 Message Handling System or over an ED1 data network. On receiving the data, the receiving Administration converts it from the common data standard to its own internal data standard for further processing by its computer system. 6.2 Additional protocols allow the receiving Administration to fo

36、rmally accept a traffic account or settlement statement without amendment, or to return it to the sending Administration in an amended form. 1 The ETIS-EDI Group is a non-profit making organisation of international operators established to develop and implement a computer based system for the rapid

37、exchange of international traffic accounts. ETIS, who own the intellectual property rights to them, has agreed to grant a license, to an unrestricted number of individual operators, on a worldwide non-discriminatory basis and on reasonable terms and conditions. The license will provide for access to

38、 the updated code tables and any other relevant datdinformation related to the application of the flatfle system. Details of the license and conditions can be obtained fiom the ETIS-ED1 website (http:/www.is.etis.org) or fiom the ITU TSB. 2 ITU-T Rec. D.190 (06/2002) Annex A Flatfde format for month

39、ly telephone and telex accounts A.l Detailed records Detailed records El. Nbr Field Remarks Always “M“ as Monthly YYMM YYMM (2 + 4) (2 + 4) D = Direct, C = Cascade (14 + 2) ECU or XFO or USD or XDR 1,3 or4 ,ubtotal; 8 = total record; 1 2 - Record identifier 1 A 1 1 Service type code 121 AI 21 3 3 4

40、- Code of account issuing operator 5 A 4 18 Code of account destination operator 5 A 9 13 Month of the account 4 N 14 17 5 6 - Code of onerator orirzin of traffic 15 IN I18 122 7 8 - Codeof Istoperatortrafficpasses by I 5 I A I 23 I 27 Codeof2ndoneratortrafficnassesbv I 5 I A I 28 I 32 9 10 - Codeof

41、3rdoperatortrafficpassesby I 5 I A I 33 I 37 Code of operator destination of traffic 5 A 38 42 Traffic month 4 N 43 46 11 12 13 - Traffic type code 4 A 47 50 Number of calls 9 N 51 59 14 15 - Number of minutes 1101 N I60 169 Share fee per call 16 Share fee per minute 16 IN I76 181 17 Accounting; pro

42、cedure Il I A I82 182 18 Amount 1161 N I83 198 19 Currency code 13 I A I99 I101 20 Rece 9=c - Record type 1 N 102 102 d types: 1 = detail; 2 = subtotal; 3 = wrong; 4 = corrected detail; 5 = corrected rrected total. Null fields other than fillers must be filled with null characters (numerics = O; alp

43、hanumerics = underscore). Negative numeric fields to start with “-I sign. ITU-T Rec. D.190 (0612002) 3 A.2 Subtotal and matching records Subtotal and matching records Yr Nbr Field 1 LE I CL Remarks I matching record 3,8,9 Record types: 1 = detail; 2 = subtotat 3 = wrong; 4 = corrected detail; 5 = co

44、rrected subtotal; 8 = total record; 9 = corrected total. Null fields other than fiilers must be filled with null characters (numerics = O; alphanumerics = underscore). Negative numeric fields to start with “-“ sim. I I I I A.3 Set of code tables The ETIS International Settlement Group maintains a se

45、t of code tables that enable the implementation of ITU-T Rec. D.190. This annex provides examples of the tables currently available from ETIS. The following code tables are currently in use: 1) Carrier Code; 2) Service Type; 3) Traffic Type; 4) Currency. Below are examples of each of the tables. A.3

46、.1 Carrier Code Format = 5 Characters, first 3 characters will always be 3 alpha to identi the Country; second two characters will always be 2 digits to identi the Carrier or Administration in that Country. i.e. AAA = unique Alpha Country Code, (matching the IS0 standard) 99 = unique 2 digits code i

47、dentiing Carrier AAA99 4 ITU-T Rec. D.190 (0612002) A.3.2 Format = 2 Characters, will always be alpha to identi the service being used (Le. Telephone, Telex,). Examples: XX = Service i ZZ = Service 2. Service Type Code - Unique Alpha code A.3.3 Traffic Type Code Format = 4 Characters, each will defi

48、ne a separate element of the call information. Within this information the 4 types of Traffic Codes can be defined as follows: a) b) c) d) Traffic Code can be alpha or symbol identifier to denote each of the 4 elements. i.e. XX-X zzxz. Basic traffic - (i.e. IDD .); Connection Procedure - Remuneratio

49、n Factor - (Billing Method (Credit Card). . .); Time Classification - (i.e. Standard, Peak,. . .). A.3.4 Currency Code There are 4 specific currency values in the exchange process. They can be defined as: 1) Dollar; 2) Gold Franc; 3) Special Drawing Right; 4) Euro. Format = 3 alpha characters. i.e. XXX. ITU-T Rec. D.190 (06/2002) 5 Annex B EDIFACT format for monthly telephone and telex accounts Monthiy Field Record id Service type code Issuing carrier Destination carrier Account month Origin carrier Bypass carrier- 1 Bypass carrier-2 Bypass carrier-3 Destination carrier Trafic month