1、 ATIS-0404100-0047 Access Service Request (ASR) Mechanized Interface Specifications Issue 36 ASR Version 47 September 2013 ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 As a leading technology and solutions development organization, ATIS brings t
2、ogether the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, ope
3、rations and more. These priorities follow a fast-track development lifecyclefrom design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits and interoperability testing. ATIS is accredited by the American National Standards Ins
4、titute (ANSI). ATIS is the North American Organizational Partner for the 3rdGeneration Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-Amer
5、ican Telecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0404100-0047 Access Service Request (ASR) Mechanized Interface Specifications Is an ATIS standard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Ordering and
6、 Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2013 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic
7、 retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 Limited Exception for “Customized” Forms. In re
8、cognition of the business needs and processes Implemented N/A by companies throughout the industry, ATIS, on behalf of the OBF, grants the following limited exception to the copyright policy given above. The forms contained within this document, once “Customized,” may be reproduced, distributed and
9、used by an individual or company provided that the following legend is placed on all “Customized” forms: “This form/screen is based upon the Ordering and Billing Forums (OBF) industry consensus approved guidelines, found in the Access Service Ordering Guidelines (ASOG) document. The ASOG may be obta
10、ined by contacting the Alliance for Telecommunications Industry Solutions (ATIS) at 1-800-387-2199 or: http:/www.atis.org/docstore/default.aspx” For purposes of this limited exception, the term “Customized” means, the modification, by a company, of an ASOG form to be issued to a trading partner to m
11、ake it company specific by, for example, adding a company logo, graying-out optional fields not required by that specific issuing company, and converting into an electronic format/screen. This limited exception does not affect the ASOG document itself which remains copyrighted and may not be reprodu
12、ced in whole or part. 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 under a prior license from the owners of the
13、 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 are affiliated with Telcordia Technologie
14、s or its products. Printed in the United States of America. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with general
15、ly accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 NO REPRESENTATION OR WARRANTY IS MADE THAT
16、 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 INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE L
17、IABLE, 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 RELIANCE UPON THIS INFORMATION PROVIDED IN TH
18、IS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0047 Access Service Request (ASR) Mechanized Interface Specifications Issue 36, ASR Version 47 Summary ATIS-040
19、4100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 SUMMARY OF CHANGES This issue of the Mechanized Interface Specifications
20、 provides the details to support the mechanization implementation of the following OBF issues: Issue Numbers 3459, 3468, 3470, 3472, 3476 The following OBF Issues went into Final Closure; however, they have no impact on mechanization on the record layouts/rules defined within this document: Issue Nu
21、mbers 3465, 3466, 3467, 3469, 3475 Section 1: No changes were made to this section Section 2: The following existing sections and record types were modified with ASOG 47: REC TYP = D ASR (BILLING the specific components of each file; the rules governing provider/customer transmission of the request;
22、 error conditions; and the criteria for data formation generic to the request. This document further defines those operative guidelines that the provider/customer systems utilize. Figure 1-1 identifies the files, which may be transmitted between provider and customer. The transmission times are nego
23、tiated between provider and customer. 1. The customer transmits access order requests via a bulk transfer file. This file, referred to as the REQUEST FILE, is described in Section 2.0. 2. The REQUEST FILE is loaded into the provider system. 3. An input response file is created by the provider and is
24、 transmitted to the customer. This file, referred to as the RESPONSE FILE, is described in Section 3.0. 4. Records accepted into the provider database from the REQUEST FILE are processed. 5. In addition to the response file, the provider system creates and transmits the following files: ERROR FILE C
25、ONFIRMATION (FOC) FILE SERVICE REQUEST CONFIRMATION (SRC) FILE PROVIDER CORRECTION (PC) FILE CLARIFICATION/NOTIFICATION REQUEST (C/NR) FILE These files are described in Section 3.0. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 1-2 Figure 1-1. AS
26、R Provider/Customer INTERFACE (1) FOC = Firm Order Confirmation (2) SRC = Service Request Confirmation - For companies supporting the 4 - Step process as defined in the Access Service Ordering Guidelines (ASOG) (3) PC = Provider Correction (4) C/NR = Clarification/Notification Request CUSTOMERORDERP
27、ROCESSOR2. LOADVALIDATION4. PROCESSING1. REQUEST FILE(ASR RECORDS)3. RESPONSE FILES(acks / rejects)ERRORSRC(2)PC (3)C/NR (4)CUSTOMERPROVIDERFOC (1)ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 1-3 1.2 RECORD LAYOUT AND FILE STRUCTURE Each file co
28、ntains fixed format, fixed length records padded to 1200 bytes. The structure of each file is illustrated in Figure 1-2. The data type for all fields is character. CONTROL HEADER PAD TO 1200 CONTROL ACCESS ORDER INFO PAD CONTROL ACCESS ORDER INFO PAD - - - CONTROL INFO PAD Figure 1-2. Structure of T
29、ransfer Files The first record in each file must be the Header Record that identifies the type of file being transmitted and the originator. When a files Header Record is in error, the entire file is rejected. Following the Header Record, each file contains a specific set of records that convey the
30、information for the access request. When no Application Records exist for a file, a Header Record must be transmitted for that file with 0 (zero) in the count field. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 1-4 1.2.1 CONTROL DATA All data re
31、cords have an initial control area (in the first 48 bytes or the first 100 bytes, depending on the record type) that enables a system to identify, process, and load the respective records into its database. Table 1-1 lists the fields that are considered Control Data; table 1-2 provides the banking s
32、cheme that is associated with the REC_ID control data field; and table 1-3 provides the incrementing scheme for the extension of REC_ID. Table 1-1 Control Data Field Descriptions Field Definition Description REC_TYP Record Type A one-character field that identifies the particular record being proces
33、sed. Invalid information in this field may cause the record or request to be rejected from the loading process. Record Type of F and R require an additional data element REC_ID, which is described below. Valid values for this field may be found in table 2-2 for the forward feed records and in sectio
34、n 3.7 for the reverse feed records. REC_MODE Record Mode A one-character field that identifies the purpose of the request. Invalid information in this field may cause the record or request to be rejected from the loading process. REC_MODEs may not be intermixed - all records within the request must
35、contain the same REC_MODE value. Valid entries in this field include the following: I = Initial Request (Forward Feed) A value of I indicates that the request is being submitted for the first time and must be used when the request has never been sent. If an initial request was rejected and all recor
36、ds associated with the request were also rejected, the records can be resubmitted with an I or C value. However, if the Admin Record (REC_TYP = S) on the initial request was accepted, then all records associated with this request must be resubmitted with a REC_MODE of C. C = Change Request (Forward
37、Feed) R = Response (Reverse Feed) X = Resend (Forward Feed) A value of X indicates that the request was previously sent and should exist in the providers database but the provider has asked for a resend of the request. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented
38、September 21, 2013 1-5 Field Definition Description REC_ID REC_CODE REC_EXT Record Identifier Record Code Record Extension A three-character code, applicable to the F and R series records that further identifies the record. Invalid information in this field may cause the record or request to be reje
39、cted from the loading process. The Record Code is the first two characters of the REC_ID. It is a two-character numeric entry, assigned from a discrete bank of numbers. Depending on the bank from which the numeric values are assigned, the REC_CODE identifies the category of the record. The REC_CODE
40、begins with the first numeric value for the records respective bank and is incremented to the next consecutive numeric value. When the REC_CODE has been incremented, all assigned values must be transmitted in their proper numeric sequence. The Record Extension is the third character of the REC_ID. I
41、t is an alphabetic character assigned for identifying multiple occurrences of a particular REC_CODE. The REC_EXT entry begins with a value of A. It is alphabetically incremented in consecutive order (from B to Z) when there is a need for additional space corresponding to a specific REC_CODE. When th
42、e REC_CODE is incremented to the next higher numeric, all REC_EXT values must have been assigned and must be transmitted in their proper alphabetical sequence. ICSC A four-character field that identifies the providers Interexchange Carrier Service Center. CCNA A three-character field that identifies
43、 the Customer Carrier Name Abbreviation. ASR The ten-character Access Service Request Number assigned to the request by the provider. ASR1 An additional eight-character field provided to include the additional characters for an eighteen-character ASR number. PON Identifies the Purchase Order Number
44、assigned by the customer to the request. REQTYP A two-character field that identifies the type of service being requested and the status of the request. ACT A one-character field that identifies the activity of the ASR. VER A two-character field that identifies the customers version number of the re
45、quest. REFNUM A four-character field that identifies the Reference Number that is unique to a circuit or circuit segment in the request. * Used to denote an area of the control data section that is reserved for future use. ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemen
46、ted September 21, 2013 1-6 Table 1-2 REC_ID Banking Scheme The following table shows the Record Types that have a bank of records that are reserved for current and future use for a particular process. For example, the F00A through F09Z records are reserved for use with Associated ASR Level data. Onl
47、y those REC_IDs specifically listed in Section 2, Table 2-2 of this document are to be used in the transmittal of data between trading partners. BANKING SCHEME REC_ID RECORD NAME 00-09, A-Z Associated ASR Level Data 10-19, A-Z Company Specific ASR Level (ECI) 20-29, A-Z Associated Circuit Level Data
48、 30-39, A-Z Company Specific Circuit Level (ECI) 40, A-Z Multi-EC Ordering 41, A-Z Translation Questionnaire and End Office Detail 42, A-Z End Office Information 43, A-Z Network Assignment Information 44, A-Z Service Address Location Information 45, A-Z Ports Configuration (PRILOC) 46, A-Z Ports Con
49、figuration (SECLOC) 47, A-Z Ethernet Virtual Connection 48, A-Z Virtual Concatenation 50, A-Z Clarification/Notification Request 51-99, A-Z Reserved For Future Use Table 1-3 Incrementing Scheme for REC_ID REC_CODE REC_EXT 00 A 00 B00 Z 01 A 01 B01 Z ATIS-0404100-0047 Effective September 21, 2013 Issued March 29, 2013 Implemented September 21, 2013 1-7 1.3 TRANSMISSION PROCESSING 1.3.1 CUSTOMER PROVIDER The transmission from the customer to the provider may contain the following files: REQUEST FILE 1.3.2 PROVIDER CUS
