1、 ATIS-0404100-0042 Access Service Request (ASR) Mechanized Interface Specifications Issue 31 ASR Version 42 March 2011 ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 The Alliance for Telecommunication Industry Solutions (ATIS) is the leading technical
2、 planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 250 companies actively formulate standards in ATIS 18 Committees. In addition, numerous Incubators, Focus a
3、nd Exploratory Groups address emerging industry priorities. For more information, please visit ATIS 0404100-0042 Access Service Request (ASR) Mechanized Interface Specifications Is an ATIS standard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Or
4、dering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2010 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an
5、electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Limited Exception for “Customized” Forms. In recognition of the business needs and processes Implemented N/A by companies throughout the
6、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 used by an individual or company provided that the following legend is placed on all “Cust
7、omized” forms: ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 “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 b
8、e obtained 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 partne
9、r to make 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 r
10、eproduced 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
11、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 are affiliated with Telcordia Techn
12、ologies 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 g
13、enerally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 NO REPRESENTATION OR WARRANTY IS MADE TH
14、AT 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
15、 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 RELIANCE UPON THIS INFORMATION PROVIDED IN
16、THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0042 Access Service Request (ASR) Mechanized Interface Specifications Issue 31, ASR Version 42 Summary ATIS-04041
17、00-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 SUMMARY OF CHANGES This issue of the Mechanized Interface Specifications provides
18、the details to support the mechanization implementation of the following OBF issues: Issue Numbers 3386, 3390 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 Numbers 3336 (withdrawn), 3378
19、 (withdrawn), 3379, 3388, 3389, 3391 Section 1: There were no changes to this section Section 2: The following existing record type was modified with ASOG 42: REC TYP = P TRANSPORT Inserted new field (IP ADDRESS) at line #48 (issue 3386) Inserted new field (SUBNET MASK) at line #49 (issue 3386) Chan
20、ged data area length from 580 to 610 Changed number of fields from 47 to 49 REC_TYP = F47A ETHERNET VIRTUAL CONNECTION Modified DSCP field from 6 characters to 12 (Issue 3390) and renumbered remaining fields in Level of Service Detail Data Array Section 3: There were no changes to this section Secti
21、on 4: There were no changes to this section Section 5: There were no changes to this section Section 6: There were no changes to this section ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0042 Access S
22、ervice Request (ASR) Mechanized Interface Specifications Issue 31, ASR Version 42 Section 1 General ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010
23、 Implemented March 19, 2011 MECHANIZED INTERFACE SPECIFICATIONS SECTION 1 TABLE OF CONTENTS 1. 1-1 GENERAL1.1 .1-1 MECHANIZED INTERFACE OVERVIEW1.2 1-3 RECORD LAYOUT AND FILE STRUCTURE1.2.1 1-4 CONTROL DATA1.3 1-7 TRANSMISSION PROCESSING1.3.1 .1-7 Customer Provider1.3.2 .1-7 Provider CustomerATIS-04
24、04100-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 1-1 1. GENERAL This document describes the rules that govern the mechanized transmission of data between entities ordering and providing access services. This document supports the Access Service Ordering Guidel
25、ines Industry Support Interface (ASOG Document) which describes the industry agreed upon guidelines for the ordering of access services. The ASR Mechanized Interface Specifications contains file structures, rules for mechanized transmission and acceptance and confirmation of data as necessitated by
26、the ASR. It also provides error conditions for systems that support the provisioning of Access Services. In an effort to insure that all possible customers and providers of Access Services are addressed in all issues and documentation maintained by or on behalf of the Ordering the specific component
27、s of each file; the rules governing provider/customer transmission of the request; 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
28、 may be transmitted between provider and customer. The transmission times are negotiated 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 int
29、o the provider system. 3. An input response file is created by the provider and is 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
30、 file, the provider system creates and transmits the following files: ERROR FILE CONFIRMATION (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-0042 Effective March 19
31、, 2011 Issued September 24, 2010 Implemented March 19, 2011 CUSTOMERORDERPROCESSOR2. LOADVALIDATION4. PROCESSING1. REQUEST FILE(ASR RECORDS)3. RESPONSE FILES(acks / rejects)ERRORSRC(2)PC (3)C/NR (4)CUSTOMERPROVIDERFOC (1)Figure 1-1. ASR Provider/Customer INTERFACE (1) FOC = Firm Order Confirmation (
32、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 1-2 ATIS-0404100-0042 Effective March 19, 2011 Issued September 24, 2010 Implem
33、ented March 19, 2011 1-3 1.2 RECORD LAYOUT AND FILE STRUCTURE Each file contains 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 CONTR
34、OL ACCESS ORDER INFO PAD - - - CONTROL INFO PAD Figure 1-2. Structure of Transfer 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 He
35、ader Record, each file contains a specific set of records that convey the 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-0042 Effective March 19, 2011 Issued September
36、24, 2010 Implemented March 19, 2011 1-4 1.2.1 CONTROL DATA All data records 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 fie
37、lds that are considered Control Data; table 1-2 provides the banking scheme 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
38、one-character field that identifies the particular record being processed. 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 fiel
39、d may be found in table 2-2 for the forward feed records and in section 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.
40、REC_MODEs may not be intermixed - all records within the request must 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
41、 has never been sent. If an initial request was rejected and all records 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
42、must be resubmitted with a REC_MODE of C. C = Change Request (Forward 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-040410
43、0-0042 Effective March 19, 2011 Issued September 24, 2010 Implemented March 19, 2011 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 in
44、formation in this field may cause the record or request to be rejected 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,
45、 the REC_CODE identifies the category of the record. The REC_CODE 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 sequ
46、ence. The Record Extension is the third character of the REC_ID. It 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
47、for additional space corresponding to a specific REC_CODE. When the 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 Ca
48、rrier Service Center. CCNA A three-character field that identifies 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 eighte
49、en-character ASR number. PON Identifies the Purchase Order Number 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 request. REFNUM A four-character field that identifies the Reference Number that is unique to a circuit or circuit segment in the request. * Use
