1、ATIS/OBFORDERING AND BILLINGFORUM (OBF)CABS(Carrier Access Billing System)AUXILIARY REPORTSPECIFICATIONSMARCH, 2003 ISSUE 6Issue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFTHIS PAGE LEFT INTENTIALLY BLANKOBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003Copyright 2003 by the Alliance f
2、or Telecommunications Industry Solutions Inc.All rights reserved.The CABS Auxiliary Report Specifications document, March, 2003 is copyrighted, printedand distributed by the Alliance for Telecommunications Industry Solutions (ATIS) on behalfof the ATIS-sponsored Ordering and Billing Forum (OBF).Exce
3、pt as expressly permitted, no part of this publication may be reproduced or distributedin any form, in an electronic retrieval system or otherwise, without the prior express writtenpermission of ATIS. Permission may be obtained by contacting ATIS at 202-628-6380.OBF Funding Companies (which are defi
4、ned in the OBF Guidelines) should refer to theOBF Guidelines (accessible from: http:/www.atis.org/atis/clc/obf/obfhom.htm) regardingtheir rights to reproduce this publication.For ordering information, please contact:ATIS1200 G Street N.W., Suite 500Washington, DC 20005(800) 387-A complete OBF Docume
5、nt Catalog and On-line Document Store is available on the ATISWeb Site at: http:/www.atis.org/atis/docstore/index.aspIssue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFNoticeThis document was developed by the Billing Committee of the Alliance forTelecommunications Industry Solutions (ATIS) Orde
6、ring and Billing Forum (OBF). TheOBF provides a forum for customers and providers in the telecommunications industry toidentify, discuss and resolve national issues which affect ordering, billing, provisioning andexchange of information about access services, other connectivity and related matters.T
7、he Billing Committee is responsible for identifying and incorporating the necessarychanges into this document. All changes to this document shall be made through the OBFissue resolution process and adopted by the Billing Committee as set forth in the OBFGuidelines.Disclaimer and Limitation of Liabil
8、ityThe information provided in this document is directed solely to professionals who have theappropriate degree of experience to understand and interpret its contents in accordancewith generally accepted engineering or other professional standards and applicableregulations. No recommendation as to p
9、roducts or vendors is made or should be implied.NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION ISTECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE,GOVERNMENTAL RULE OR REGULATION, AND FURTHER NO REPRESENTATIONOR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANYPARTICULAR
10、 PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUALPROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANYSUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TOANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OROTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPR
11、ESSLY ADVISESTHAT ANY AND ALL USE OF OR RELIANCE UPON THE INFORMATION PROVIDED INTHIS DOCUMENT IS AT THE RISK OF THE USER.OBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003CONTENTS1.0 PREFACE12.0 GENERAL DESCRIPTION32.1 Scope 32.2 CABS Auxiliary Report Specifications Revisions.32.3 Related OB
12、F Issues32.4 Organization of the Specifications.32.5 Data Element Requirements.42.5.1 Mechanized File Records 42.5.2 Tape Description42.5.3 File Organization 42.5.4 Data Format 53.0 NPA/NXX LINE NUMBER RANGE TO END OFFICE DATA .73.1 Intent of Report/File 73.2 Report Description 83.3 Distribution .83
13、.4 Paper Report Requirements.83.4.1 Data Elements .83.4.2 Report Format .104.0 LOCAL ROUTING NUMBER (LRN) TO END OFFICE DATA .114.1 Intent of Report/File 114.2 Report Description 124.3 Distribution .124.4 Paper Report Requirements.124.4.1 Data Elements .124.4.2 Report Format .145.0 UNBUNDLED NPA/NXX
14、 LINE NUMBER RANGE (LNR) DATA155.1 Intent of Report/File 155.2 Report Description 155.3 Distribution .165.4 Paper Report Requirements.165.4.1 Data Elements .165.4.2 Report Format .176.0 TAPE REQUIREMENTS .196.1 Mechanized File Records.196.1.1 Common Fields 196.2 Sorting Requirements 20Issue 6March,
15、2003CABS AUXILIARY REPORTSPECIFICATIONSOBFAPPENDIXAPPENDIX A - OBF ISSUES INCLUDED IN CARS REVISIONS A - 1APPENDIX B - MECHANIZED FILE DATE ELEMENT DEFINITIONS B - 1APPENDIX C - MECHANIZED FILE RECORDS C - 170-01-01 - CARS NPA/NXX End Office Pack Header C - 170-05-05 - CARS NPA/NXX End Office Data C
16、 - 270-05-05 - CARS NPA/NXX End Office Data C - 370-10-05 - CARS LRN End Office Data C - 470-15-05 CARS Unbundled Line Number Range Data C - 570-99-99 CARS NPA/NXX End Office Pack Trailer C - 7OBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003Issued: 11/01/89 Revised: 3/2003Page 11.0 PREFACET
17、his document represents the Ordering and Billing Forum (OBF) Billing Committeerequirement to create a document of CABS Auxiliary Report Specifications (CARS) notassociated with the CABS Billing Output Specifications (BOS).These procedures were cooperatively developed in the OBF. They were written in
18、response to OBF Issue 474. All changes to this document must be presented to the OBFGeneral Session and accepted by consensus. The OBF Billing Committee is responsiblefor the on-going maintenance and distribution of this document based on resolved issues.The OBF is a voluntary, self-policing group o
19、f customer and provider participants whomeet together to identify, discuss and resolve issues which are national in scope, involvingordering and billing of access services. The OBF functions under the auspices of theCarrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solu
20、tions(ATIS). The Federal Communications Commission (FCC) authorized the CLC in a January17, 1985 Memorandum Opinion and Order.Issue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFIssued: 11/01/89 Revised: 3/2003Page 2THIS PAGE LEFT INTENTIALLY BLANKOBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6Ma
21、rch, 2003Issued: 11/01/89 Revised: 3/2003Page 32.0 GENERAL DESCRIPTION2.1 ScopeThe CABS Auxiliary Report Specifications (CARS) are guidelines for providing standardreports and/or standard mechanized file layouts, where appropriate. These standards willnot be documented in the CABS Billing Output Spe
22、cifications (BOS). The followingguidelines apply to report outputs that are documented in CARS. CARS will not be used for the development of industry standard report outputs for datathat can be derived from the bill or CSR. Implementation of CARS outputs, such as timing, content, media, etc. will be
23、negotiated between the individual customers and providers.2.2 CABS Auxiliary Report Specifications RevisionsThis document will be updated as necessary based upon resolved OBF Issues asidentified by the OBF Billing Committee.All text revisions will be identified by a “|” in the right margin. The “|”
24、will be placed to theimmediate right of each line of revised text.2.3 Related OBF IssuesOBF Issues incorporated into the CARS document are displayed as Appendix A of thisdocument.2.4 Organization of the SpecificationsThese specifications are divided into sections that document the details necessary
25、foreach report and/or mechanized file. Within each report section, the following componentsare included:1. Intent of the report/file, including OBF Issue2. Report/file description3. Distribution4. Data element requirements for the paper report5. Report format6. Mechanized file record requirements (i
26、f applicable)7. Data element requirements for mechanized file (if applicable)Issue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFIssued: 11/01/89 Revised: 3/2003Page 4Resolved OBF Issues that have been incorporated into this document are included asAppendix A. Appendix B provides definitions for
27、 the mechanized file date elements andAppendix C the mechanized file detail records.2.5 Data Element RequirementsDefined within each report section are the data elements, data attributes, and additionalpertinent information necessary for the standard report. Data element requirements for themechaniz
28、ed file records are documented within the text of each report section and definedin Appendix B.2.5.1 Mechanized File RecordsResolved OBF issues incorporated into this document will specify if mechanized filerecords in tape format are available as a report medium. Each report section will identify if
29、tape format is available as a report medium and, if applicable, document the detail recordrequired for the report. All detail records identified within the report sections are containedin Appendix C.2.5.2 Tape DescriptionA tape report may be provided on a separate file or included as an addendum to
30、the BillingData Tape. When provided, the tape will contain records that are fixed length (225 bytes)and will use labels consistent with standard IBM Operating Systems.2.5.3 File OrganizationEach file will consist of a pack of data. A pack consists of a pack header record followedby detail record(s)
31、followed by a pack trailer record.A pack header record consists of customer and provider identification data along withcontrol information. The detail records contain the same information that is displayed onthe paper report. The pack trailer record consists of record counts and other controlinforma
32、tion about the pack.OBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003Issued: 11/01/89 Revised: 3/2003Page 52.5.4 Data FormatIn general, the following rules apply to individual data fields, unless otherwise stated in thereport section: Fields are defined as alphanumeric (X) or numeric (9). Al
33、phanumeric fields will be left justified and blank filled. Numeric fields will be right justified and zero filled. Signed numeric fields will be decimally aligned and will contain appropriatepositive or negative identification in the zone bits of the right-most character. Dates are presented in the
34、format, year, month, date (CCYYMMDD); e.g., July14, 1999 would be “19990714”.Issue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFIssued: 11/01/89 Revised: 3/2003Page 6THIS PAGE LEFT INTENTIALLY BLANKOBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003Issued: 11/01/89 Revised: 3/2003Page 73.
35、0 NPA/NXX LINE NUMBER RANGE TO END OFFICE DATA3.1 Intent of Report/FileThis report/file is requested, per OBF Issue 474, to identify the NPA/NXX Line Number Ranges(LNR) that are associated with each CLLI code. This data will apply to FG B, FG C, and FGDonly and represent the NPA/NXX LNRs that could
36、have contributed to the usage accumulation onthe CABS bill during the billing period. Due to various conditions, e.g., NPA/NXX LNR changesduring the month, the report may not represent the actual NPA/NXX LNR that are found on theCABS bill.NPA/NXX LNR data will be a snapshot of that which is reflecte
37、d on the Local Exchange CarriersEnd Office Table at the time of billing. This snapshot may include the CLLIs, NPA/NXX LNRs thatappear on the current bill, or may include an entire “dump” of all CLLIs and NPA/NXX LNRs onthe LECs End Office Table. For each CLLI code, all NPA/NXX LNR data should be gro
38、upedtogether. Each NPA/NXX LNR should be associated with only one CLLI-the CLLI where billingoccurred, unless historical data is provided. If historical data is provided EFFECTIVE DATES andEND DATES are required on the multiple entries. The current entry will have no end date.Line number ranges that
39、 have been unbundled will not be included in this data.The NPA/NXX LNR data may be provided at least once a month. Each provider will determine theday of the month this data will be provided and notify the customer; the schedule will remainconstant from month to month.NPA/NXX LNR data may be provide
40、d separately from each processing center within a company orprovided on one report/file which includes the entire company. This will be negotiated betweenthe individual customers and providersThe information provided by the end office company in a multiple bill meetpoint environment willnot be provi
41、ded by the other companies on the route. There will be no requirement for thepresentation of NPA/NXX LNR data where no requirement exists to file these in NECA #4, forexample, host/remote.The NPA/NXX LNR data provided via CARS outputs should not be used as the sole basisfor filing billing claims. Th
42、e bill remains as the official document for filing any claims.Issue 6March, 2003CABS AUXILIARY REPORTSPECIFICATIONSOBFIssued: 11/01/89 Revised: 3/2003Page 83.2 Report DescriptionThe provider may provide the NPA/NXX LNR to End Office Data to the customer in either paper ortape format. It will be the
43、responsibility of the customer to contact the provider and request theappropriate medium.The tape report may be provided on a separate file or included as an addendum to the BillingData Tape. When tape is chosen by the customer as the report medium, it will be theresponsibility of the provider to sp
44、ecify whenever the report will be on a separate file, or includedas an addendum to the Billing Data Tape (BDT). In no case should more than one file be includedon a single physical tape. That is, if the report is appended to the BDT, the Category 70 recordsshould follow the Category 10 records (and
45、Category 40 records if present) and precede the 99-99-99 file trailer record. A single physical tape must never contain more than one file trailerrecord.3.3 DistributionThe NPA/NXX LNR to End Office report/file should be produced at least once per month. If theproviders end office table is updated m
46、ore than once a month and historical data is not provided,the report/file should be produced per table update, or on a bill period basis, or in accordance withother negotiated schedules.Distribution of the NPA/NXX LNR to End Office report/file should occur within ten (10) calendardays after the nego
47、tiated scheduled date(s).3.4 Paper Report Requirements3.4.1 Data ElementsREPORT DATEThe date the information is extractedLOCAL EXCHANGE CARRIERThe name of the Local Exchange Carrier providing the report.BILL DATEThe billing period dateAdditional Information: Format: CCYYMMDDDefault: SpacesWhen Used:
48、 When historical data is not provided.OBF CABS AUXILIARY REPORTSPECIFICATIONSIssue 6March, 2003Issued: 11/01/89 Revised: 3/2003Page 9OFFICEThe COMMON LANGUAGE CLLI code for a providers end office or tandem providing aspecific access service.NPAThe NPA associated with the providers end office providi
49、ng a specific access service.NXXThe NXX associated with the providers end office providing a specific access serviceLOW LINE NUMBERThe low line number of the range for the NXX associated with the providers end officeproviding a specific access service.Additional Information: Default: 0000 (zero)HIGH LINE NUMBERThe high line number of the range for the NXX associated with the providers end officeproviding a specific access service.Additional Information: Default 999EFFECTIVE DATE (Optional)Identifies the first date the NPA/NXX LNR was assigned to th
