ATIS 0401001-0008-2006 CABS (Carrier Access Billing System) Auxiliary Report Specifications.pdf

《ATIS 0401001-0008-2006 CABS (Carrier Access Billing System) Auxiliary Report Specifications.pdf》由会员分享，可在线阅读，更多相关《ATIS 0401001-0008-2006 CABS (Carrier Access Billing System) Auxiliary Report Specifications.pdf（42页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0401001-0008 CABS (Carrier Access Billing System) AUXILIARY REPORT SPECIFICATIONS CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 2 The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rap

2、idly developing and promoting technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees

3、 and its Incubator Solutions Program. ATIS 0401001-0008, Carrier Access Billing System (CABS) Auxiliary Report Specifications Is an ATIS standard developed by the Billing Committee under the ATIS Ordering and Billing Forum (OBF). Published by Alliance for Telecommunications Industry Solutions 1200 G

4、 Street, NW, Suite 500 Washington, DC 20005 Copyright 2006 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For

5、information contact ATIS at 202.628.6380. ATIS is online at . Telcordia Technologies, Inc. was formerly known as Bell Communications Research, Inc. or Bellcore. Portions of this document, previously published by Bellcore, may still reflect the former name as it was embedded in the documentation unde

6、r a prior license from the owners of the BELL trademark, which license has now expired. The use of this name does not suggest that Telcordia Technologies has licensed the names BELL, Bell Communications Research, or Bellcore for new uses or that the owners of the BELL trademark sponsor, endorse or a

7、re affiliated with Telcordia Technologies or its products or services in any way at this time. Printed in the United States of America. CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed

8、 solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO R

9、EPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUA

10、L PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANC

11、E UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 CONTENTS 1.0 PREFACE 5 2.0 GENERAL DESCRIPTION.7 2.1 Scope .7 2.2 CABS Auxiliary Report Specifications Revisions 7 2.3 Related OBF Issues .7 2.4 Organization of

12、 the Specifications 7 2.5 Data Element Requirements.8 2.5.1 Mechanized File Records 8 2.5.2 Tape Description .8 2.5.3 File Organization .8 2.5.4 Data Format 9 3.0 NPA/NXX LINE NUMBER RANGE TO END OFFICE DATA .11 3.1 Intent of Report/File 11 3.2 Report Description12 3.3 Distribution12 3.4 Paper Repor

13、t Requirements.13 3.4.1 Data Elements.13 3.4.2 Report Format .15 4.0 LOCAL ROUTING NUMBER (LRN) TO END OFFICE DATA16 4.1 Intent of Report/File 16 4.2 Report Description17 4.3 Distribution17 4.4 Paper Report Requirements.18 4.4.1 Data Elements.18 4.4.2 Report Format .20 5.0 UNBUNDLED NPA/NXX LINE NUM

14、BER RANGE (LNR) DATA 21 5.1 Intent of Report/File 21 5.2 Report Description21 5.3 Distribution22 5.4 Paper Report Requirements.22 5.4.1 Data Elements.22 5.4.2 Report Format .24 6.0 TAPE REQUIREMENTS25 6.1 Mechanized File Records .25 6.1.1 Common Fields .25 6.2 Sorting Requirements.26 CABS AUXILIARY

15、REPORT SPECIFICATIONS Issue 8, September, 2006 APPENDIX APPENDIX A - OBF ISSUES INCLUDED IN CARS REVISIONS A - 1 APPENDIX B - MECHANIZED FILE DATE ELEMENT DEFINITIONS B - 1 APPENDIX C - MECHANIZED FILE RECORDS C - 1 70-01-01 - CARS NPA/NXX End Office Pack Header C - 1 70-05-05 - CARS NPA/NXX End Off

16、ice Data C - 2 70-05-05 - CARS NPA/NXX End Office Data C - 3 70-10-05 - CARS LRN End Office Data C - 4 70-15-05 CARS Unbundled Line Number Range Data C - 5 70-99-99 CARS NPA/NXX End Office Pack Trailer C - 7 CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 1.0 PREFACE This document repr

17、esents the Ordering and Billing Forum (OBF) Billing Committee requirement to create a document of CABS Auxiliary Report Specifications (CARS) not associated with the CABS Billing Output Specifications (BOS). These procedures were cooperatively developed in the OBF. They were written in response to O

18、BF Issue 474. All changes to this document must be presented to the OBF General Session and accepted by consensus. The OBF Billing Committee is responsible for the on-going maintenance and distribution of this document based on resolved issues. The OBF is a voluntary group of provider and customer p

19、articipants who convene to identify, discuss and resolve issues, which involve the ordering and billing of access services at a national level. The term access may encompass Interstate, Intrastate, and Local. The OBF functions under the Alliance for Telecommunications Industry Solutions (ATIS) autho

20、rized by the Federal Communications Commission (FCC) in a January 17, 1985 Memorandum Opinion and Order. Page 5 CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 THIS PAGE LEFT INTENTIALLY BLANKCABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 2.0 GENERAL DESCRIPTION 2.1 Scop

21、e The CABS Auxiliary Report Specifications (CARS) are guidelines for providing standard reports and/or standard mechanized file layouts, where appropriate. These standards will not be documented in the CABS Billing Output Specifications (BOS) (this is a Telcordia copyrighted document). The following

22、 guidelines apply to report outputs that are documented in CARS. CARS will not be used for the development of industry standard report outputs for data that can be derived from the bill or CSR. Implementation of CARS outputs, such as timing, content, media, etc. will be negotiated between the indivi

23、dual customers and providers. 2.2 CABS Auxiliary Report Specifications Revisions This document will be updated as necessary based upon resolved OBF Issues as identified by the OBF Billing Committee. All text revisions will be identified by a “|” in the right margin. The “|” will be placed to the imm

24、ediate right of each line of revised text. 2.3 Related OBF Issues OBF Issues incorporated into the CARS document are displayed as Appendix A of this document. 2.4 Organization of the Specifications These specifications are divided into sections that document the details necessary for each report and

25、/or mechanized file. Within each report section, the following components are included: 1. Intent of the report/file, including OBF Issue 2. Report/file description 3. Distribution 4. Data element requirements for the paper report 5. Report format 6. Mechanized file record requirements (if applicabl

26、e) 7. Data element requirements for mechanized file (if applicable) CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 Resolved OBF Issues that have been incorporated into this document are included as Appendix A. Appendix B provides definitions for the mechanized file data elements and A

27、ppendix C the mechanized file detail records. 2.5 Data Element Requirements Defined within each report section are the data elements, data attributes, and additional pertinent information necessary for the standard report. Data element requirements for the mechanized file records are documented with

28、in the text of each report section and defined in Appendix B. 2.5.1 Mechanized File Records Resolved OBF issues incorporated into this document will specify if mechanized file records in tape format are available as a report medium. Each report section will identify if tape format is available as a

29、report medium and, if applicable, document the detail record required for the report. All detail records identified within the report sections are contained in Appendix C. 2.5.2 Tape Description A tape report may be provided on a separate file or included as an addendum to the Billing Data Tape. Whe

30、n 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 Organization Each file will consist of a pack of data. A pack consists of a pack header record followed by detail record(s) followed by a pack tr

31、ailer record. A pack header record consists of customer and provider identification data along with control information. The detail records contain the same information that is displayed on the paper report. The pack trailer record consists of record counts and other control information about the pa

32、ck. CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 2.5.4 Data Format In general, the following rules apply to individual data fields, unless otherwise stated in the report section: Fields are defined as alphanumeric (X) or numeric (9). Alphanumeric fields will be left justified and bl

33、ank filled. Numeric fields will be right justified and zero filled. Signed numeric fields will be decimally aligned and will contain appropriate positive or negative identification in the zone bits of the right-most character. Dates are presented in the format, year, month, date (CCYYMMDD); e.g., Ju

34、ly 14, 1999 would be “19990714”. CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 THIS PAGE LEFT INTENTIALLY BLANKCABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 3.0 NPA/NXX LINE NUMBER RANGE TO END OFFICE DATA 3.1 Intent of Report/File This report/file is requested, per O

35、BF Issue 474, to identify the NPA/NXX Line Number Ranges (LNR) that are associated with each CLLI code. This data will apply to all Types of Accounts having usage data. (This data was expanded from FGB, C, and D only with OBF Issue XXXX.) and represent the NPA/NXX LNRs that could have contributed to

36、 the usage accumulation on the CABS bill during the billing period. Due to various conditions, e.g., NPA/NXX LNR changes during the month, the report may not represent the actual NPA/NXX LNR that are found on the CABS bill. NPA/NXX LNR data will be a snapshot of that which is reflected on the Provid

37、er Company Names 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 all CLLIs and NPA/NXX LNRs on the LECs End Office Table. For each CLLI code, all NPA/NXX LNR data should be grouped together

38、. Each NPA/NXX LNR should be associated with only one CLLI-the CLLI where billing occurred, unless historical data is provided. If historical data is provided EFFECTIVE DATES and END DATES are required on the multiple entries. The current entry will have no end date. Line number ranges that have bee

39、n 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 the day of the month this data will be provided and notify the customer; the schedule will remain constant from month to month. NPA/NXX LNR data may be provided sep

40、arately from each processing center within a company or provided on one report/file which includes the entire company. This will be negotiated between the individual customers and providers. The information provided by the end office company in a multiple bill meetpoint environment will not be provi

41、ded by the other companies on the route. There will be no requirement for the presentation of NPA/NXX LNR data where no requirement exists to file these in NECA #4, for example, host/remote. The NPA/NXX LNR data provided via CARS outputs should not be used as the sole basis for filing billing claims

42、. The bill remains as the official document for filing any claims. CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 3.2 Report Description The provider may provide the NPA/NXX LNR to End Office Data to the customer in either paper or tape format. It will be the responsibility of the cus

43、tomer to contact the provider and request the appropriate medium. The tape report may be provided on a separate file or included as an addendum to the Billing Data Tape. When tape is chosen by the customer as the report medium, it will be the responsibility of the provider to specify whenever the re

44、port will be on a separate file, or included as an addendum to the Billing Data Tape (BDT). In no case should more than one file be included on a single physical tape. That is, if the report is appended to the BDT, the Category 70 records should follow the Category 10 records (and Category 40 record

45、s if present) and precede the 99-99-99 file trailer record. A single physical tape must never contain more than one file trailer record. 3.3 Distribution The NPA/NXX LNR to End Office report/file should be produced at least once per month. If the providers end office table is updated more than once

46、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 with other negotiated schedules. Distribution of the NPA/NXX LNR to End Office report/file should occur within ten (10) calendar days after the negotiated sch

47、eduled date(s). CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 3.4 Paper Report Requirements 3.4.1 Data Elements BILL DATE The provider designated date for which an access/ interconnection service bill is rendered. Additional Information: Format: CCYYMMDD Default: Spaces When Used: Wh

48、en historical data is not provided. EFFECTIVE DATE (Optional)Identifies the first date the NPA/NXX LNR was assigned to the end office for billing. Additional Information: Format: CCYYMMDD Default: spaces When Used: When historical data is provided. END DATE (Optional)Identifies the last date the NPA

49、/NXX LNR was assigned to the end office for billing. Additional Information: Format: CCYYMMDD Default: spaces When Used: When historical data is provided for segments other than current. EXTRACT DATE The date the data was extracted from the system for billing/reporting HIGH LINE NUMBER The high line number of the range for the NXX associated with the providers end office providing a specific access service. Additional Information: Default 999 CABS AUXILIARY REPORT SPECIFICATIONS Issue 8, September, 2006 LOW LINE NUMBER The low line number of the range for