Xantic s D91 Format of Maritime & Land Mobile Telecommunications Accounting Information

Transcription

1 Xantic s D91 Format of Maritime & Land Mobile Telecommunications Accounting Information Issue No.: 2.3 Issue Date: 22 October 2004 Prepared by: Xantic Copyright 2004 Xantic

2 ISSUE AND AMENDMENTS REGISTER Issue No. And Amendments Issue Amendment Issue Date Author Number 1.0 Original 19/04/95 Telstra, IS MS&RS 1.1 Change field definition from Numeric to Alpha/Num for the following fields in Call Record Type 02: - NAMORG, NAMDES, CDFACI, MERENU, CHARAT 04/10/95 Telstra, IS MS&RS 1.2 Expanded and updated the sample D91 file to include most service categories and changes to the fields in Call Record Type 02: - NAMORG & NAMDES Updated the field CDCS/CES in Call Record Type Added item 4 under Differences between Telstra s D91 Billing Data File and an ITU Standard D.91 file to include NUMWRD field differences 1.4 Updated item 5.4. CDKIND: Kind of Traffic to include call type 76 INMARSAT-B High Speed Data 1.5 Update item 5.4. CDKIND: Kind of Traffic to include additional codes covering various INMARSAT-M Data calls and INMARSAT-C calls. Update item 4.3. Call Record: Type 02 to include new Antenna Size field. 1.6 Update item 5.4. CDKIND: Kind of Traffic to include call type 27 Telephone Aeronautical Satellite 1.7 Update item 5.4. CDKIND: Kind of Traffic to include call types 91, 92, 93 - INMARSAT Global Area Network (M4) References to Telstra Mobile Satellite & Radio Services (MS&RS) and radio billing deleted, CES replaced by LES 1.8 Chang to Section 4.3. Call Record Type 02, position 149, Field Name DECIMN. From Number of decimal places in TXAMOU and TAXTOT, equals 2 To Number of decimal places in TXAMOU and TAXTOT, equals 3. The change is due to GST calculation. Chang to Section 4.4. Call Record Type 03, position 19, Field Name DECIMN. From Number of decimal places in AMTTOT, equals 2 To Number of decimal places in AMTOT, equals 3. The change is due to GST calculation. 02/12/96 Telstra, IS MS&RS 28/02/97 Telstra, IS MS&RS 29/05/97 Telstra, IS MS&RS 01/08/98 Telstra, IS MS&RS 01/04/99 Telstra, IS MS&RS 30/04/2000 G Huddy 27/11/2000 T Lin 1.9 Update Document to reflect name change to Station /12/2000 Station Update document to reflect name change to Xantic 06/07/2001 Xantic 2.0 Update item 4.1. File Header Record: Type 00 To include Invoice No. 13/02/2004 Reda Azim Xantic Update item 4.3. Call Record: Type 02 to change the contents of field NAMORG from Call Origin to Terminal Name or MES ID Add to the contents of field NAMDES Destination Country. Update item 5.4. CDKIND: Kind of Traffic to include call types F1, F2, F3, F4, F5, F6, F7, F8, F9 INMARSAT Fleet Fleet 33, 55, 77 and a new CDKIND codes for INMC. 2.1 Update CDKIND codes 10/04/2004 Reda Azim Billing Data File Structure Issue No: 2.0 Page 2

3 2.2 Update CDKIND codes explanation table (section 5.4) 14/06/2004 Marcela Laguzzi 2.3 Add a new CDKIND codes for Fleet K, Fleet k fax and Low speed data, Fleet k fax and Low speed data, Fleet k fax and Low speed data, Fleet k Fax. 22/10/2004 Reda Azim Billing Data File Structure Issue No: 2.0 Page 3

4 TABLE OF CONTENTS ISSUE AND AMENDMENTS REGISTER...2 TABLE OF CONTENTS BACKGROUND ELECTRONIC TRAFFIC BILLING DATA FILE DIFFERENCES BETWEEN XANTIC S D91 BILLING DATA FILE AND ITU STANDARD D.91 FILE BILLING DATA FILE STRUCTURE File Header Record: Type Traffic Type Header Record: Type Call Record: Type Summary Record: Type Trailer Record: Type CODE VALUES USED IN XANTIC'S D91 FILES CDDIRE: Traffic Codes CDCURR: Currency Codes LES: Land Earth Station (Ocean Region) CDKIND: Kind of Traffic CDKIND: Kind of Traffic (cont.) CDFACI: Facility Code CHARAT: Charge Rate ANTSIZE: Antenna Size APPENDIX 1. SAMPLE ELECTRONIC DATA FILE IN D91 FORMAT FROM XANTIC...14 Billing Data File Structure Issue No: 2.0 Page 4

5 Billing Data File Structure Issue No: 2.0 Page 5

6 1. Background In keeping with ITU Recommendations D.91 and growing practice by other overseas telecommunications administrations, Xantic has developed the means to deliver via electronic means international accounting for radio and satellite (INMARSAT) communications data. The purpose of this document is to provide recipients with an understanding of he electronic file structure from Xantic. 2. Electronic Traffic Billing Data File Xantic has based the format and content of its Electronic Billing Traffic Data File on the ITU-T D.91 (Draft Version). However, since this has proven inadequate to satisfy all of Xantic s requirements, some changes have had to be made. 3. Differences between Xantic s D91 Billing Data File and ITU Standard D.91 File. 3.1 As some AAIC s (International Accounting Authorities) have more than one account with Xantic, and Xantic has other application for the use of Billing Traffic Data Files, the AAIC number mentioned in D.91 is not used. Instead, the Xantic assigned customer account number is used. Since this number is six digits long, changes in the format of the file name have been necessary 3.2 D.91 uses the Accounting Authority, 01 record as a batch header to specify what type of calls follow it via the CDDIRE field. However, the D.91 description of the 01 record specifies that there is only one record per file. Therefore there would have to be a file for each value of CDDIRE. The naming conventions of the file imply that there is a file for each INMARSAT traffic service. For most large customers Xantic has several accounts. D.91 specifies that each diskette or contain only one file. These factors would lead to an excessive number of diskettes or s being sent to the same customer. To overcome this, Xantic has relaxed the following rules: - That only one 01 record appears on each file, Billing Data File Structure Issue No: 2.0 Page 6

7 - Our files may have several 01 records per file. A file may include traffic from only one of the following: INMARSAT-A, INMARSAT-B, INMARSAT-C, INMARSAT-M, INMARSAT MINI-M, INMARSAT GAN, INMARSAT Fleet, CONNECTMESSAGING And AMOSCONNECT. A file may include call data records from several INMARSAT services. The service can be determined by the values of CALSIG and CDKIND. That only one file is put on each diskette or , - Our diskettes/ s may have several files on them. That all records on a file are 160 characters long. -Our files are standard DOS text files with each record delimited by a carriage control and line feed characters, each record is only as long as it needs to be to hold the data. The file names are of the form AANNNNNN.YMM where: AA is the first 2 characters of Xantic s AAIC Code NNNNNN is the 6 digits Xantic Account Number Y is 5 to represent 1995 MM is the number of the month Zero always goes in the TXAMOU filed of all 012 records. Because of difficulties in categorising all INMARSAT-C calls, Xantic has created 12 new values for CDKIND, to distinguish them as temporary Xantic codes, they are alphabetic, with the first character C. These will be used until the ITU defines a complete set of codes for INMARSAT-C traffic. The Billing Data Files have been compressed using the file compression utility PKZIP and will be changed to an executable file thus appearing in the form AANNNNNN.EXE. Instructions with regard to decompressing and opening of these files can be found in the README.TXT file enclosed on each diskette. The UNMWRD field as specified by ITU standard D.91 displays the duration of a call in HHMMSS i.e., Hours, Minutes and Seconds. To enable this field to cater for extended call durations, Xantic has shown this field in SSSSSS seconds. The ANTSIZE (Antenna Size) field is an additional filed that displays the various terminal antenna sizes for each call. With the greater efficiencies, speed and flexibility available nowadays for exchange of data via the Internet, the delivery of D.91 billing information in encrypted format to a Web Page is now Xantic s preferred medium for delivery of electronic Billing Data Records (BDR s). Customers are Billing Data File Structure Issue No: 2.0 Page 7

8 therefore encouraged to make use of this progressively discontinued. To arrange access to Xantic s Web Site for retrieval of D.91 BDR s please contact your Xantic Account Manager. 4. Billing Data File Structure The file is a standard DOS ASCII text file, where each record is delimited by a carriage control and line feed control characters. There is no requirement within DOS to pad the records out to a fixed length, so this has not been done. Wherever possible, the ITU D.91 field names are used. A sample layout of the billing data file in D.91 format from Xantic has been attached to Appendix File Header Record: Type 00 Position Length Format Field Name Contents 1 2 Numeric CODART Field determining record type - Value Alpha/Num CDAAIC GS AAIC Number - AA Numeric CREATN Billing Month End Date - YYMMDD Numeric REFERN Reference = Invoice Number and Billing Month 4.2. Traffic Type Header Record: Type 01 Position Length Format Field Name Contents 1 2 Numeric CODART Field determining record type - Value Numeric ACCTNO Customer Account Number 11 1 Numeric CDDIRE Traffic Codes - 3, 4 or 5 - as per D91 Specification Alpha/Num NATADM Name of Customer Account 62 3 Alpha CDCURR ISO Invoice Currency Code 65 8 Numeric RATCON Currency Conversion Rate, 1 Unit of Invoice Curr = xxxxxx units of settlement currency 73 1 Numeric DECIMN Number of decimal places of RATCON 74 4 Numeric YEAMON Statement Month YYMM 78 1 Alpha CDSUPP = S for Supplement if any of previous months traffic included in the batch Billing Data File Structure Issue No: 2.0 Page 8

9 4.3. Call Record: Type 02 Position Length Format Field Name Contents 1 2 Numeric CODART Field determining record type - Value Alpha/Num LES LES code 10 6 Numeric DATCOM Date of Call YYMMDD - UTC 16 4 Numeric TMETFC Time of start of call HHMM - UTC Alpha/Num CALSIG Vessel Call Sign or MES ID Alpha/Num NAMORG Terminal Name or MES ID Alpha/Num NAMDES Call Destination & Destination Country Alpha/Num CDKIND Call Kind Code Alpha/Num CDFACI Facility Code Numeric NUMWRD Number of words or duration of call in seconds Numeric TXAMOU Amount of facility charge or zero - we always put zero in here Numeric BITNUM Number of bits Alpha/Num MERENU Message Reference Number Alpha/Num CHARAT Charge Rate Numeric TAXTOT Total Amount of charge Numeric DECIMN Number of decimal places in TXAMOU and TAXTOT, equals Alpha/Num ANTSIZE Antenna Size 4.4. Summary Record: Type 03 Position Length Format Field Name Contents 1 2 Numeric CODART Field determining record type - Value Numeric AMTTOT Total of TAXTOT for all previous 02 records for the previous call sign Numeric DECIMN Number of decimal places in AMTTOT, equals 3 Billing Data File Structure Issue No: 2.0 Page 9

10 4.5. Trailer Record: Type 99 Position Length Format Field Name Contents 1 2 Numeric CODART Field determining record type - Value Numeric NOBATC Number of batches (01 records) 5 16 Numeric AMTTOT Total of AMTTOT for all 03 records on the file. This is also the same as the total of TAXTOT on all 02 records on the file Numeric DECIMN Number of decimal places in AMTTOT, equals 2 5. Code Values Used in Xantic's D91 Files 5.1. CDDIRE: Traffic Codes 3 Terrestrial traffic chargeable to the MES customer 4 Satellite traffic chargeable to the MES customer 5 Reverse charge originating from the MES 5.2. CDCURR: Currency Codes AUD XDR USD Australian Dollar Special Drawing Rights US Dollar 5.3. LES: Land Earth Station (Ocean Region) AOE Atlantic Ocean Region East AOW Atlantic Ocean Region West PHI302 Indian Ocean Region PHP202 Pacific Ocean Region Billing Data File Structure Issue No: 2.0 Page 10

11 5.4. CDKIND: Kind of Traffic 00 Other 02 Inmarsat-A automatic telephone 03 Not used 04 Not used 05 Not used 09 Not used 12 Inmarsat-A automatic Telex 13 Inmarsat-A manual Telex 18 Not used 27 Not used 32 Not used 2S Two Stage Access Fixed to A, B, M, mm, GAN or Fleet. 40 Not used 41 Inmarsat-C to multi address Telex- parent address 42 Inmarsat-C to multi address Telex- offspring address 43 Not used 44 Inmarsat-C to multi address PSDN parent address 45 Inmarsat-C to multi address PSDN offspring address 47 Mobile originated status request 48 Not used 53 Inmarsat-C -Terrestrial originated FleetNet EGC Call 54 Inmarsat-C-Terrestrial originated SafetyNet EGC call 55 Inmarsat-C Mobile to Xantic mailbox 60 Inmarsat-M automatic telephone / fax 61 Inmarsat-miniM automatic telephone/ fax 65 Inmarsat-M data 66 Inmarsat-miniM data 70 Inmarsat-B automatic telephone / fax 73 Inmarsat-B data 76 Inmarsat-B high speed data 79 Inmarsat-B automatic telex 91 Inmarsat-GAN telephone / fax, Swift64 92 Inmarsat-GAN ISDN, Swift64 93 Inmarsat-GAN MPDS (Undefined Bit Rate), Swift 64 AC AmosConnect CF Inmarsat-C Fax Mobile to Fixed CG Inmarsat-C SMS to GSM CH Positive delivery notification to mobile CI Inmarsat-C to Internet CM Inmarsat C Mobile to Mobile CS Inmarsat-C Mobile to Internet offspring address CT Inmarsat-C Mobile to PSTN parent address CU Inmarsat-C Mobile to PSTN offspring address Billing Data File Structure Issue No: 2.0 Page 11

12 5.4. CDKIND: Kind of Traffic (cont.) CX DA DC F1 F2 F3 F4 F5 F6 F7 F8 F9 F0 2F 3F 5F 7F FC GC IC IL IM IS LA MM MT MW ND PC PD PL PM PN PO PS PT RL RM RS TC TL TM TS XC XL Inmarsat-C Mobile to LES Inmarsat-C Distress Alert Inmarsat-C PSDN Fixed to Mobile C Fleet 33 TP telephone Not Used Fleet 33 MPDS (Undefined Bit Rate) Fleet 55 TP telephone Fleet 55 ISDN Fleet 55 MPDS (Undefined Bit Rate) Fleet 77 TP telephone Fleet 77 ISDN Fleet 77 MPDS (Undefined Bit Rate) Fleet K ISDN Fleet K fax Fleet K Fax/Low speed data Fleet K Fax/Low speed data Fleet K Fax/Low speed data Inmarsat-C Fax LES to Fixed Inmarsat-C SMS from GSM phones to C Inmarsat-C from Internet to C mobile Inmarsat-C Data reports Large to Internet Inmarsat-C Data reports Medium to Internet Inmarsat-C Data reports Small to Internet Inmarsat-C Mobile 2 Fixed Land Mobile Alert ConnectMessaging MailConnect ConnectMessaging TelexConnect ConnectMessaging WebConnect Inmarsat-C NDN negative delivery notification PhoneConnect Inmarsat-C Positive Delivery Notification Inmarsat-C Data Report Large to PSDN (X25) Inmarsat-C Data Report Medium to PSDN (X25) Inmarsat-C Poll no text Inmarsat-C Poll with Text Inmarsat-C Data Report Small to PSDN (X25) Inmarsat-C PSTN Fixed to Mobile C Inmarsat-C Data Report Large to DNID file/mailbox for customer retrieval Inmarsat-C Data Report Medium to DNID file/mailbox for customer retrieval Inmarsat-C Data Report Small to DNID file/mailbox for customer retrieval Inmarsat-C Telex Fixed to Mobile C Inmarsat-C Data Report Large to Telex, Fax, PSTN modem Inmarsat-C Data Report Medium to Telex, Fax, PSTN modem Inmarsat-C Data Report Small to Telex, Fax, PSTN modem Inmarsat-C LES to Mobile to Inmarsat-C Inmarsat-C LES to Fixed /Land Mobile alert delivery to offspring address Billing Data File Structure Issue No: 2.0 Page 12

13 5.6. CDFACI: Facility Code 34 Personal Call 35 Reversed Charge Call 5.7. CHARAT: Charge Rate 1 Peak 2 Cheap 3 Standard 5.8. ANTSIZE: Antenna Size A B C D Indeterminate Normal Gain Intermediate Gain High Gain Billing Data File Structure Issue No: 2.0 Page 13

14 6. Appendix 1. Sample Electronic Data File in D91 Format from Xantic A sample electronic traffic billing data file in D91 format from Xantic has been attached AA Test Customer Communications Ltd XDR VIP TCAT2 TOP CAT VIP TCAT2 TOP CAT Test Customer Communications Ltd XDR S 02PHP SAKURA Hong Kong PHI SAKURA India PHP NAMITA Romania PHP NAMITA United Kin PHP NAMITA Greece PHP NAMITA Greece PHI NAMITA Honduras PHI AZURE WATERS Philippines PHP AZURE WATERS Switzerland PHP AZURE WATERS Switzerland PHP APOLLO PHP APOLLO PHP REF CH PHP APOLLO PHP REF CH PHP APOLLO Status - Ref: PHP REF CH AOE DOLPHIN AOE REF CH PHI SEA DRAGON Status - Ref: PHI MORNING GLORY CA PHI REF CH PHP MORNING GLORY CA PHP REF CH PHI MORNING GLORY CA PHI REF CH PHI MORNING GLORY CA Billing Data File Structure Issue No: 2.0 Page 14

15 02PHI REF CH PHI MORNING GLORY CD PHI REF CH PHI ANUSHKA Russia PHI ANUSHKA Russia AOW ANUSHKA Byelorussia AOW ANUSHKA Byelorussia AOW ANUSHKA Sweden AOW ANUSHKA United Kin AOW ANUSHKA Panama Repub AOE LADY LUCK India Billing Data File Structure Issue No: 2.0 Page 15