ATIS DLRMIS-006-2003 Design Layout Report Mechanized Interface Specification Industry Support Interface.pdf

1、ATIS/OBF-DLRMIS-006Design Layout ReportMechanized InterfaceSpecificationIndustry Support InterfaceOrdering and BillingForumATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 2003THIS PAGE INTENTIONALLY LEFT BLANK.ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued

2、 September 6, 2002 Implemented March 8, 2003Copyright 2002 by the Alliance for Telecommunications Industry Solutions,Inc. All rights reserved.The Design Layout Report, Mechanized Interface Specifications, Issue 6, datedMarch 2003, is copyrighted, printed and distributed, by the Alliance forTelecommu

3、nications Industry Solutions (ATIS) on behalf of the ATIS-sponsoredOrdering and Billing Forum (OBF).Except as expressly permitted, no part of this publication may be reproducedor distributed in any form, in an electronic retrieval system or otherwise,without the prior express written permission of A

4、TIS. All requests to reproducethis document shall be in writing and sent to: OBF Manager, c/o ATIS, 1200 GStreet, NW, Suite 500, Washington, DC 20005. OBF Funding Companies(which are defined in the OBF Guidelines) should refer to the OBF Guidelinesas respects their rights to reproduce this publicati

5、on.For ordering information, please contact:ATIS1200 G Street, NW, Suite 500Washington, DC 20005(202) 628-6380obfatis.orgA complete OBF Document Catalog and Ordering Form is available on the ATISWeb Site at:http:/www.atis.org/atis/docstore/index.aspATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued S

6、eptember 6, 2002 Implemented March 8, 2003PREFACEThis document was developed by the Interconnection Services Ordering the specific components ofeach file; the rules which govern provider/customer transmission of theDLR; error conditions; and the criteria for data formation generic to thetransmitted

7、design report. This document further defines the operativeguidelines that the provider/customer systems utilize.Figure 1-1 identifies the files which may be transmitted between providerand customer. The transmission times are negotiated between providerand customer.1. The provider prepares and trans

8、mits DLRs via the bulktransfer file. This file, referred to as the PROVIDER REPORTFILE, is described in section 3.4.2. The PROVIDER REPORT FILE is loaded into the customersystem.3. The customer system creates customer feedback files andtransmits feedback on the status of the Design Report recordsrec

9、eived from the provider. The term Customer Feedback Fileis a descriptive category that identifies two types of feedbackfiles: Acknowledgment Feedback File Error Feedback FileThese files, referred to as the Customer Feedback File, aredescribed in section 3.0.4. Records accepted into the customer data

10、base from thePROVIDER REPORT FILE, are processed.ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-23. DATA TRANSFER FORMAT OVERVIEW - (continued)PROVIDERDLRPROCESSORPROVIDER SYSTEM2. LOAD AND VALIDATE4. PROCESSCUSTOMER SYSTEM1. PROVIDER REPORTFILE3. CUST

11、OMERFEEDBACK FILESACKERRORFigure 1-1. PROVIDER/CUSTOMER DLR InterfaceATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-33.1 GENERIC FILE STRUCTUREEach file contains fixed length 80 byte records. The data type is“character.” Within the 80 byte records, the

12、re is a continuous string ofdata comprised of variable length tag names, tag values and delimiterswhich are described in Section 3.1.2 and 3.1.4. Each combination of tagnames, tag values and delimiters constitutes a sub-string (See Section3.1.3).A sub-string may span records.A transmission consists

13、of one or more batch sub-files. A batch sub-filemay contain “0” or more DLRs. “0” is a positive report that there are noDLRs to be sent. DLRs are made up of required and optional sub-strings.(See Figure 1-2).FILE CONTROL=XXXXNNNXXXXXXXXNNNNNN;DLR DATA CONTROL=XXXXNNNNNXXXXX;.DLR DATA=XXXXX;DLR DATA=

14、XXXXXXXXX;DLR DATA=XX.DLR DATA=XXXXXXXXXXXXXXXX;DLR DATA=XXXXXXXXXXXXXDLR DATA=XXXXNNNNNXX;DLRXXXX;DLR DATA=XXXXXXXXX;DLR DATA=XX;DLR DATA=NNNNNNNNNN;DLR DATA=XXXXXXXX;CONTROL=XXXXXXX;END OFFILE=NNNNNNNNNNN;12345678980Figure 1-2. Structure of Transfer FilesATIS/OBF-DLRMIS-006 Effective March 8, 2003

15、Issued September 6, 2002 Implemented March 8, 20033-43.1.1 File ControlAll files have sub-strings which serve as control areas for a system toidentify, process, and load the respective DLR data into its data bases.File HeaderThe first sub-string in each interface file must be the file header control

16、data. This file header identifies the originator, the recipient and specificdate/time information. When the files header is in error, the entire fileis rejected. The file header must always span 80 characters of the firstrecord in the file as described in Section 3.3.File TrailerThe last sub-string

17、in each interface file must be trailer control data.This file trailer identifies the end of the transmitted file and the numberof items transmitted. The file trailer is described in Section 3.3. Whenno DLR application data exist for a file, the header and trailer must bepresent in the file, and the

18、trailer must contain zeros in the count fields.Other File ControlsFiles may contain several levels of transmitted data as depicted in Figure1-3. The interface must contain sub-strings (which serve as control) toindicate start and end of transmitted data within the file. The levels oftransmission wit

19、hin a File Transmission Level, Batch Level and DLRLevel. These levels are described in Section 3.4.1.2.ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-5TRANSFER FORMAT LAYOUTSTransmission File StructureTransHdrTagTransHdrBatchHdrTagTransmission/Batch Le

20、velsSTART TRANS=BatchHdrBatchTlrTagBatchTlrTransTlrTagTransTlrBatch/DLR LevelsSTART BATCH=TH EOTBHDHDLR DLREODEOB BHDH EODEOBDLRBatchHdrTagBatchHdrDLRHdrTagDLRHdrDLRTlrTagBatchTlrDLR/Element LevelsSTART DLR=DLRHdrTagDLRHdr Data ElementsDLRTlrTagFigure 1-3. Transfer Format LayoutsXXXXXXXXXMMDDYYYYHHM

21、MSSMMDDYYYYHHMMSS (30 SPACES) ;START BATCH= NNNNMMDDYYYYHHMMSS (49 SPACES) ; END BATCH= NNNNNN; END TRANS= NNNNNNNNNN;NNNNMMDDYYYYHHMMSS (49 SPACES) ;START DLR= NNNNNNNXXXXXXXXXXXXXXXX; END DLR=;END BATCH= NNNNNN;NNNNNNNXXXXXXXXXXXXXXXX; IC=ATX;PON=YES00764597;VER=AA;CKR= /DSEZ/126115/LL /; END DLR=

22、;ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-6THIS PAGE INTENTIONALLY LEFT BLANK.ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-73.1.2 DelimitersDelimiters will be used to separate the data element (ta

23、g values) fromtheir respective tags (tag names). Delimiters will also be used to denotethe end or last position of the data element.CODE DESCRIPTION= Separates the tag and data element; Separates the tagged data elements (sub-strings); Signifies the last of a group of related data elements An escape

24、 sequence characterThe natural occurrence of the=;orinthedata will be preceded by anescape indicator of .3.1.3 Sub-StringsTransfer Files are made up of a continuous string of data spanning 80byte records. Within the continuous string there are sub-strings of datathat delineate components of the file

25、, identify specific data elements andprovide control information.There are two sub-strings in the mechanized interface as described in thefollowing sections.3.1.3.1 Provider Report File and Customer AcknowledgmentFeedback File Sub-StringsThese sub-strings begin with an identifier (Tag Name), followe

26、d by adelimiter to separate the identifier from the element it identifies, followedby the data element, followed by a second delimiter to denote the end ofthe element.START TRANS=NNNXXNNNNNXXXXXXXXXXXXXX;PON=FFS0012345678;tag namedelimiter 1elementdelimiter 2ATIS/OBF-DLRMIS-006 Effective March 8, 20

27、03Issued September 6, 2002 Implemented March 8, 20033-83.1.3.2 Error Feedback Sub-StringsThis sub-string begins with an error code, an identifier (Tag Name)followed by a delimiter, followed by an optional associated error message,followed by a second delimiter to denote the end of the sub-string.M+E

28、C DSGCON=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX;tag namedelimiter 1messagedelimiter 2error codeError codes are described in section 3.9.3.1.4 File Control TagsFile tags are unique identifiers associated with each file control dataelement. DLR tag names are described in Section 3.4.1.3.TAG NAME DESCRIPTIONSTA

29、RT TRANS Identifies the file header and start of the interface file.START BATCH Identifies the batch header and start of a single batchof DLRs.END BATCH Identifies the end of a single batch of DLRs within theinterface file.END TRANS Identifies the file trailer and the end of the interfacefile.ATIS/O

30、BF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-93.2 TRANSMISSION PROCESSING3.2.1 Forward FeedThe term FORWARD FEED is used to describe the transmission from theprovider to the customer and consists of the following file: PROVIDER REPORT FILE3.2.2 Reverse Fee

31、dThe term REVERSE FEED is used to describe the transmission from thecustomer to the provider and may contain the following files: ACKNOWLEDGMENT FEEDBACK FILE ERROR FEEDBACK FILEUse of the Error Feedback File process is optional based upon individualprovider/customer negotiations.ATIS/OBF-DLRMIS-006

32、 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-103.3 FILE CONTROL LAYOUTSAt minimum a transmission must contain transmission and batchheader and trailer control sub-strings.The File Header sub-string is the only truly fixed positional string ofcontrol data as it relates

33、to the 80 byte file record. The beginning of theheader string must start in position one of the 80 byte record and endwith its delimiter in position 80.Additionally, the File Header indicates the type of file being transmitted(i.e. PROVIDER REPORT, ACKNOWLEDGMENT, or ERROR FILE).CONTROL LAYOUTSSub-S

34、tring1-1 FILE HEADER (Transmission Header Record)1-2 PROVIDER REPORT FILE TRAILER (Provider Transmission TrailerRecord)1-3 PROVIDER REPORT FILE BATCH HEADER (Provider Batch HeaderRecord)1-4 PROVIDER REPORT FILE BATCH TRAILER (Provider Batch TrailerRecord)1-5 PROVIDER DLR HEADER (DLR Transmission Lev

35、el Record)1-6 PROVIDER DLR TRAILER (DLR Transmission Level Record)1-7 CUSTOMER FILE TRANSFER (Transmission Trailer Record)ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-111-1 FILE HEADER (Transmission Header Record)FIELD DESCRIPTION STRT LTH VALUEHEADE

36、R TAG NAME 1 11 START TRANSDELIMITER 12 1 =*FILE TYPE 13 1 R, A, or EEC ID 14 4 XXXXIC ID 18 4 XXXXTRANSMISSION DATE 22 8 MMDDCCYYTRANSMISSION TIME 30 6 HHMMSSPREVIOUS TRANSMISSION DATE 36 8 MMDDCCYYPREVIOUS TRANSMISSION TIME 44 6 HHMMSSFILLER 50 30 SPACESDELIMITER 80 1 ;*Valid entries for File Type

37、:R - PROVIDER REPORT FILEA - CUSTOMER ACKNOWLEDGMENT FILEE - CUSTOMER ERROR FILEATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-121-2 FILE TRAILER (Transmission Trailer Record)(PROVIDER REPORT FILE)FIELD DESCRIPTION STRT LTH VALUETRAILER TAG NAME 1 9 EN

38、D TRANSDELIMITER 10 1 =# OF DLRs IN TRANSMISSION 11 6 NNNNNN# OF BATCHES INTRANSMISSION17 4 NNNNDELIMITER 21 1 ;1-3 BATCH HEADER (Batch Transmission Level Record)FIELD DESCRIPTION STRT LTH VALUEBATCH HEADER TAG NAME 1 11 START BATCHDELIMITER 12 1 =BATCH SEQ # 13 4 NNNNBATCH DATE 17 8 MMDDCCYYBATCH T

39、IME 25 6 HHMMSSFILLER 31 49 SPACESDELIMITER 80 1 ;ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-131-4 BATCH TRAILER (Batch Transmission Level Record)FIELD DESCRIPTION STRT LTH VALUEBATCH TRAILER TAG NAME 1 9 END BATCHDELIMITER 10 1 =# OF DLRs IN BATCH

40、 11 6 NNNNNNDELIMITER 17 1 ;1-5 DLR HEADER (DLR Transmission Level Record)FIELD DESCRIPTION STRT LTH VALUEDLR HEADER TAG NAME 1 9 START DLRDELIMITER 10 1 =DLR SEQUENCE # 11 7 NNNNNNNDLR PON NUMBER 18 16 CHRDLR PON VERSION 34 2 CHRDELIMITER 36 1 ;ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued Sept

41、ember 6, 2002 Implemented March 8, 20033-141-6 DLR TRAILER (DLR Transmission Level Record)FIELD DESCRIPTION STRT LTH VALUEDLR TRAILER TAG NAME 1 7 END DLRDELIMITER 8 1 =DELIMITER 9 1 ;1-7 IC FILE TRAILER (Transmission Trailer Record)(ACKNOWLEDGMENT FEEDBACK FILE)FIELD DESCRIPTION STRT LTH VALUETRAIL

42、ER TAG NAME 1 9 END TRANSDELIMITER 10 1 =# OF DLRs IN TRANSMISSION 11 6 NNNNNN# OF BATCHES IN TRANSMISSION 17 4 NNNNDELIMITER 21 1 ;(ERROR FEEDBACK FILE)FIELD DESCRIPTION STRT LTH VALUETRAILER TAG NAME 1 9 END TRANSDELIMITER 10 1 =# OF DLRs REJECTED 11 6 NNNNNNTOTAL # OF ERRORS 17 6 NNNNNNDELIMITER

43、23 1 ;ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued September 6, 2002 Implemented March 8, 20033-153.4 FORWARD FEED (Provider - Customer)The Forward Feed is the PROVIDER REPORT FILE transmission from theprovider to a specific customer which includes information for the DLR.This information is pr

44、ovided to the appropriate customer via thePROVIDER REPORT FILE. The respective sub-string formats aredescribed in this section.3.4.1 EC Report FileThis file contains the providers reports of DLRs transmitted to a specificcustomers designated location. The data in the PROVIDER REPORT Fileis edited by

45、 the customer prior to being processed and loaded into thecustomers data base.3.4.1.1 File StructureThis file contains levels of transmission information:TransmissionBatchDLRHeader and trailer file control sub-strings delineate each of these levels.ATIS/OBF-DLRMIS-006 Effective March 8, 2003Issued S

46、eptember 6, 2002 Implemented March 8, 20033-163.4.1.2 Transmission LevelsFile Transmission LevelThe File Transmission Level allows for provider to customer selective timetransmissions. There may be any number of transmissions per day. Atthe file transmission level, the file header and file trailer s

47、ub-strings arealways required.File HeaderThe first sub-string in each PROVIDER REPORT FILE must be the fileheader control data. One and only one File Header sub-string is allowedper REPORT FILE and must precede all other data. The file header mustalways be the first 80 characters of the first record

48、 in the file asdescribed in Section 3.3. When no DLR data exists for the file, the fileheader must still be present.File TrailerThe last sub-string in the file must be the file trailer control data. Thisfile trailer signifies the end of the transmitted file and provides summarystatistics of the numb

49、er of DLRs and Batches transmitted. The filetrailer is described in Section 3.3. When no DLR data exists within thisfile, this trailer must be present and contain zeros in the count fields.File BatchThe File Batch Level is a mandatory subset of a file transmission. A filetransmission must contain one or more batches. A batch provides forarbitrary grouping of DLRs. A batch may contain any number of DLRs ormay contain no DLRs. When there are no DLRs within a batch, thissignifies a null batch. At the batch transmission, the batch header andtrailer are always required.Batch He