1、ATIS/OBFORDERING AND BILLINGFORUM (OBF)CABS(Carrier Access Billing System)AUXILIARY REPORTSPECIFICATIONSJANUARY, 2004 ISSUE 7Issue 7January, 2004CABS AUXILIARY REPORTSPECIFICATIONSOBFTHIS PAGE LEFT INTENTIALLY BLANKOBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Copyright 2004 by the Allia
2、nce for Telecommunications Industry Solutions Inc.All rights reserved.The CABS Auxiliary Report Specifications document, dated January, 2004 iscopyrighted, printed and distributed by the Alliance for Telecommunications IndustrySolutions (ATIS) on behalf of the ATIS-sponsored Ordering and Billing For
3、um (OBF).Except 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 expresswritten permission of ATIS. All requests to reproduce this document shall be in writingand sent to: OBF Manager, c
4、/o ATIS, 1200 G Street, NW, Suite 500, Washington, DC20005.OBF Funding Companies may reproduce and distribute this publication, or any portionthereof, for purposes of internal use, and may also reproduce and distribute the formscontained within the publication to third parties, provided that: (1) th
5、e distribution of anyform is limited to the primary business of the company and, (2) the following legend isplaced on each form: “This form (or material) may not be reproduced, distributed, or usedwithout the express written permission of the Alliance for Telecommunications IndustrySolutions (ATIS)
6、at 202-628-6380.”For ordering information, please contact:ATIS1200 G Street N.W., Suite 500Washington, DC 20005(202) 628-6380This document is available for immediate purchase via the Internet on the ATISDocument Center: https:/www.atis.org/atis/docstore/index.aspIssue 7January, 2004CABS AUXILIARY RE
7、PORTSPECIFICATIONSOBFNoticeThis document was developed by the Billing Committee of the Alliance forTelecommunications Industry Solutions (ATIS) Ordering and Billing Forum (OBF). TheOBF provides a venue for customers and providers in the telecommunications industryto identify, discuss and resolve nat
8、ional issues that affect ordering, billing, provisioningand exchange of information about access services and other connectivity and relatedmatters. The Billing Committee is responsible for identifying and incorporating thenecessary changes into this document. All changes to this document shall be m
9、adethrough the ATIS issue resolution process and adopted by the Billing Committee as setforth in the “Operating Procedures for ATIS Forums and Committees”.Disclaimer and Limitation of LiabilityThe information provided in this document is directed solely to professionals who havethe appropriate degre
10、e of experience to understand and interpret its contents inaccordance with generally accepted engineering or other professional standards andapplicable regulations. No recommendation as to products or vendors is made or shouldbe implied.NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION ISTE
11、CHNICALLY 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 PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUALPROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF
12、ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITHRESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOSTPROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATISEXPRESSLY ADVISES THAT ANY AND ALL USE OF OR RELIANCE UPON THEINFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK O
13、F THE USEROBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004CONTENTS1.0 PREFACE12.0 GENERAL DESCRIPTION 32.1 Scope.32.2 CABS Auxiliary Report Specifications Revisions32.3 Related OBF Issues .32.4 Organization of the Specifications32.5 Data Element Requirements 42.5.1 Mechanized File Records4
14、2.5.2 Tape Description.42.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/File73.2 Report Description .83.3 Distribution .83.4 Paper Report Requirements.83.4.1 Data Elements 83.4.2 Report Format.104.0 LOCAL ROUTING NUMBER (LRN) TO END
15、OFFICE DATA .114.1 Intent of Report/File114.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 LINE NUMBER RANGE (LNR) DATA155.1 Intent of Report/File155.2 Report Description .155.3 Distribution .165.4 Paper R
16、eport Requirements.165.4.1 Data Elements 165.4.2 Report Format.186.0 TAPE REQUIREMENTS196.1 Mechanized File Records.196.1.1 Common Fields.196.2 Sorting Requirements 20Issue 7January, 2004CABS AUXILIARY REPORTSPECIFICATIONSOBFAPPENDIXAPPENDIX A - OBF ISSUES INCLUDED IN CARS REVISIONS A - 1APPENDIX B
17、- 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 - 270-05-05 - CARS NPA/NXX End Office Data C - 370-10-05 - CARS LRN End Office Data C - 470-15-05 CARS Unbundled Lin
18、e Number Range Data C - 570-99-99 CARS NPA/NXX End Office Pack Trailer C - 7OBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Page 11.0 PREFACEThis document represents the Ordering and Billing Forum (OBF) Billing Committeerequirement to create a document of CABS Auxiliary Report Specificatio
19、ns (CARS) notassociated with the CABS Billing Output Specifications (BOS).These procedures were cooperatively developed in the OBF. They were written inresponse to OBF Issue 474. All changes to this document must be presented to theOBF General Session and accepted by consensus. The OBF Billing Commi
20、ttee isresponsible for the on-going maintenance and distribution of this document based onresolved issues.The OBF is a voluntary, self-policing group of customer and provider participants whomeet together to identify, discuss and resolve issues which are national in scope,involving ordering and bill
21、ing of access services. The OBF functions under the auspicesof the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications IndustrySolutions (ATIS). The Federal Communications Commission (FCC) authorized the CLCin a January 17, 1985 Memorandum Opinion and Order.Issue 7January, 2004CAB
22、S AUXILIARY REPORTSPECIFICATIONSOBFPage 2THIS PAGE LEFT INTENTIALLY BLANKOBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Page 32.0 GENERAL DESCRIPTION2.1 ScopeThe CABS Auxiliary Report Specifications (CARS) are guidelines for providing standardreports and/or standard mechanized file layout
23、s, where appropriate. These standardswill not be documented in the CABS Billing Output Specifications (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 fordata that can be derived from the
24、 bill or CSR. Implementation of CARS outputs, such as timing, content, media, etc. will benegotiated 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 Bill
25、ing Committee.All text revisions will be identified by a “|” in the right margin. The “|” 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 Specifi
26、cationsThese specifications are divided into sections that document the details necessary foreach report and/or mechanized file. Within each report section, the followingcomponents are included:1. Intent of the report/file, including OBF Issue2. Report/file description3. Distribution4. Data element
27、requirements for the paper report5. Report format6. Mechanized file record requirements (if applicable)7. Data element requirements for mechanized file (if applicable)Issue 7January, 2004CABS AUXILIARY REPORTSPECIFICATIONSOBFPage 4Resolved OBF Issues that have been incorporated into this document ar
28、e included asAppendix A. Appendix B provides definitions for 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 th
29、e standard report. Data element requirements forthe mechanized file records are documented within the text of each report section anddefined in Appendix B.2.5.1 Mechanized File RecordsResolved OBF issues incorporated into this document will specify if mechanized filerecords in tape format are availa
30、ble as a report medium. Each report section will identifyif tape format is available as a report medium and, if applicable, document the detailrecord required for the report. All detail records identified within the report sections arecontained in Appendix C.2.5.2 Tape DescriptionA tape report may b
31、e provided on a separate file or included as an addendum to theBilling Data 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 c
32、onsists of a pack header record followedby detail record(s) 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 trail
33、er record consists of record counts and other controlinformation about the pack.OBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Page 52.5.4 Data FormatIn general, the following rules apply to individual data fields, unless otherwise stated inthe report section: Fields are defined as alphan
34、umeric (X) or numeric (9). Alphanumeric 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
35、. Dates are presented in the format, year, month, date (CCYYMMDD); e.g.,July 14, 1999 would be “19990714”.Issue 7January, 2004CABS AUXILIARY REPORTSPECIFICATIONSOBFPage 6THIS PAGE LEFT INTENTIALLY BLANKOBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Page 73.0 NPA/NXX LINE NUMBER RANGE TO E
36、ND OFFICE DATA3.1 Intent of Report/FileThis report/file is requested, per OBF Issue 474, to identify the NPA/NXX Line NumberRanges (LNR) that are associated with each CLLI code. This data will apply to all Typesof Accounts having usage data. (This data was expanded from FGB, C, and D only withOBF Is
37、sue XXXX.) and represent the NPA/NXX LNRs that could have contributed to theusage accumulation on the CABS bill during the billing period. Due to variousconditions, e.g., NPA/NXX LNR changes during the month, the report may not representthe actual NPA/NXX LNR that are found on the CABS bill.NPA/NXX
38、LNR data will be a snapshot of that which is reflected on the Local ExchangeCarriers End Office Table at the time of billing. This snapshot may include the CLLIs,NPA/NXX LNRs that appear on the current bill, or may include an entire “dump” of allCLLIs and NPA/NXX LNRs on the LECs End Office Table. F
39、or each CLLI code, allNPA/NXX LNR data should be grouped together. Each NPA/NXX LNR should beassociated with only one CLLI-the CLLI where billing occurred, unless historical data isprovided. If historical data is provided EFFECTIVE DATES and END DATES arerequired on the multiple entries. The current
40、 entry will have no end date.Line number ranges that 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 willdetermine the day of the month this data will be provided and notify the customer; theschedule will remain constant
41、 from month to month.NPA/NXX LNR data may be provided separately from each processing center within acompany or provided on one report/file which includes the entire company. This will benegotiated between the individual customers and providers.The information provided by the end office company in a
42、 multiple bill meetpointenvironment will not be provided by the other companies on the route. There will be norequirement for the presentation of NPA/NXX LNR data where no requirement exists tofile these in NECA #4, for example, host/remote.The NPA/NXX LNR data provided via CARS outputs should not b
43、e used as thesole basis for filing billing claims. The bill remains as the official document forfiling any claims.Issue 7January, 2004CABS AUXILIARY REPORTSPECIFICATIONSOBFPage 83.2 Report DescriptionThe provider may provide the NPA/NXX LNR to End Office Data to the customer ineither paper or tape f
44、ormat. It will be the responsibility of the customer to contact theprovider and request the appropriate medium.The tape report may be provided on a separate file or included as an addendum to theBilling Data Tape. When tape is chosen by the customer as the report medium, it will bethe responsibility
45、 of the provider to specify whenever the report will be on a separate file,or included as an addendum to the Billing Data Tape (BDT). In no case should morethan one file be included on a single physical tape. That is, if the report is appended tothe BDT, the Category 70 records should follow the Cat
46、egory 10 records (and Category40 records if present) and precede the 99-99-99 file trailer record. A single physical tapemust never contain more than one file trailer record.3.3 DistributionThe NPA/NXX LNR to End Office report/file should be produced at least once per month.If the providers end offi
47、ce table is updated more than once a month and historical datais not provided, the report/file should be produced per table update, or on a bill periodbasis, or in accordance with other negotiated schedules.Distribution of the NPA/NXX LNR to End Office report/file should occur within ten (10)calenda
48、r days after the negotiated 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: CCYYMMDDDefa
49、ult: SpacesWhen Used: When historical data is not provided.OBFCABS AUXILIARY REPORTSPECIFICATIONSIssue 7January, 2004Page 9OFFICEThe COMMON LANGUAGE CLLI code for a providers end office or tandemproviding a specific access service.NPAThe NPA associated with the providers end office providing a specific accessservice.NXXThe NXX associated with the providers end office providing a specific accessserviceLOW LINE NUMBERThe low line number of the range for the NXX associated with the providers endoffice providing a specific access service.Additional Information: Default: 000
