1、 ATIS-0404100-0044 Access Service Request (ASR) Mechanized Interface Specifications Issue 33 ASR Version 44 March 2012 ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 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-0044 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 2011 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-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 “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-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 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-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0044 Access Service Request (ASR) Mechanized Interface Specifications Issue 33, ASR Version 44 Summary ATIS-04041
17、00-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 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 3397, 3411, 3412, 3420, 3421, 3425, 3426, ECI Bytes The following OBF Issues went into Final Closure; however, they have no impact on mechanization on the record layouts/rules defined within this docum
19、ent: Issue Numbers 3367 (Wthd), 3419, 3422 (UOM), 3423, 3424, 3427 Section 1: No changes were made to this section Section 2: The following existing record types were modified with ASOG 44: REC TYP = S ASR (ADMINISTRATIVE) Inserted new field (EDA) at line #53 replacing Filler (Issue 3426) Inserted n
20、ew field (JPR) at line #83 (Issue 3421) Changed data area length from 788 to 799 Changed number of fields from 82 to 83 REC TYP = F44A SERVICE ADDRESS LOCATION INFORMATION (EUSA PRILOC) Changed existing AAI field at line #17 to Filler (Issue 3397) Inserted new field (LCON EMAIL) at line #38 (Issue 3
21、425) Inserted new field (AALCON_TEL) at line #39 (Issue 3425) Inserted new field (ALCON EMAIL) at line #40 (Issue 3425) Reinserted existing AAI field at line #41and expanded the length to 150 bytes (Issue 3397) Changed data area length from 554 to 838 Changed number of fields from 37 to 41 REC TYP =
22、 F44B SERVICE ADDRESS LOCATION INFORMATION Changed existing AAI field at line #17 to Filler (Issue 3397) Inserted new field (LCON EMAIL) at line #38 (Issue 3425) Inserted new field (AALCON_TEL) at line #39 (Issue 3425) Inserted new field (ALCON EMAIL) at line #40 (Issue 3425) Reinserted existing AAI
23、 field at line #41and expanded the length to 150 bytes (Issue 3397) Changed data area length from 554 to 838 Changed number of fields from 37 to 41 ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 REC TYP = F10B COMPANY SPECIFIC ASR LEVEL (ECI) (SECOND
24、OF TWO COMPANY SPECIFIC ASR LEVEL ECI RECORDS) Inserted new fields (AALCON TEL, ACAT, ACPON, ALCON EMAIL, CDR, CONFIG REMARKS, CPEV, EA TYPE, EXPNM, LCON EMAIL, NWKSTAT, PER, QOPT, SALESCON, SALESCON EMAIL, SALESCON TEL NO, SAR) at lines #28-44 (ECI Bytes) Changed data area length from 421 to 1002 C
25、hanged number of fields from 27 to 44 REC TYP = F30A COMPANY SPECIFIC CIRCUIT LEVEL (ECI) Inserted new fields (ASN, CCAT, CFAPA, CSHIELD, EAID, EXDI, ICID, OPTCON, PWRT, TRM, VLAN TAG, VPN NM) at lines #36-47 (ECI Bytes) Changed data area length from 1064 to 1189 Changed number of fields from 35 to
26、47 REC TYP = F47A ETHERNET VIRTUAL CONNECTION Inserted new field (EVCMPID) at line #34 (Issue 3420) Changed data area length from 666 to 708 Changed number of fields from 33 to 34 Section 3: The following existing record type was modified with ASOG 44: REC TYP = R30A COMPANY SPECIFIC CIRCUIT LEVEL (
27、ECI) Inserted new fields (ACCESSID, ACCESSORD, PORTID, PORTORD, VCCID, VCORD, VLAN TAG) at lines #16-22 (ECI Bytes) Changed data area length from 456 to 595 Changed number of fields from 15 to 22 REC TYP = N CONFIRMATION NOTICE (CN) Inserted new field (NFR) at line #52 (Issue 3412) Changed data area
28、 length from 675 to 676 Changed number of fields from 51 to 52 Section 4: Deleted original Section 4.9.2.1 Initial Request (Issue 3411) Added new Section 4.9.2.1 - ICSC to clarify the use of the ICSC field for Multi-EC Requests (Issue 3411) ATIS-0404100-0044 Effective March 17, 2012 Issued September
29、 23, 2011 Implemented March 17, 2012 Section 5: No changes were made to this section Section 6: Added new Section 6.2.1 AAI to explain conversion of the length change to the AAI field ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 THIS PAGE INTENTIONA
30、LLY LEFT BLANK. ATIS-0404100-0044 Access Service Request (ASR) Mechanized Interface Specifications Issue 33, ASR Version 44 Section 1 General ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0044 Effectiv
31、e March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 MECHANIZED INTERFACE SPECIFICATIONS SECTION 1 TABLE OF CONTENTS 1. GENERAL 1-1 1.1 MECHANIZED INTERFACE OVERVIEW . 1-1 1.2 RECORD LAYOUT AND FILE STRUCTURE 1-3 1.2.1 CONTROL DATA 1-4 1.3 TRANSMISSION PROCESSING 1-7 1.3.1 Customer
32、Provider . 1-7 1.3.2 Provider Customer . 1-7 ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 1-1 1. GENERAL This document describes the rules that govern the mechanized transmission of data between entities ordering and providing access services. This
33、document supports the Access Service Ordering Guidelines 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 acc
34、eptance and confirmation of data as necessitated by 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
35、 or on behalf of the Ordering the specific components 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 sys
36、tems utilize. Figure 1-1 identifies the files, which 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 describ
37、ed 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 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 REQUES
38、T FILE are processed. 5. In addition to the response 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
39、in Section 3.0. ATIS-0404100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 1-2 Figure 1-1. ASR Provider/Customer INTERFACE (1) FOC = Firm Order Confirmation (2) SRC = Service Request Confirmation - For companies supporting the 4 - Step process as defined in the A
40、ccess Service Ordering Guidelines (ASOG) (3) PC = Provider Correction (4) C/NR = Clarification/Notification Request CUSTOMERORDERPROCESSOR2. LOADVALIDATION4. PROCESSING1. REQUEST FILE(ASR RECORDS)3. RESPONSE FILES(acks / rejects)ERRORSRC(2)PC (3)C/NR (4)CUSTOMERPROVIDERFOC (1)ATIS-0404100-0044 Effec
41、tive March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 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 HE
42、ADER PAD TO 1200 CONTROL ACCESS ORDER INFO PAD CONTROL 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
43、error, the entire file is rejected. Following the Header 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-040
44、4100-0044 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 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 respectiv
45、e records into its database. Table 1-1 lists the fields 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
46、 Field Definition Description REC_TYP Record Type A 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,
47、which is described below. Valid values for this field 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
48、or request to be rejected from the loading process. 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
49、for the first time and must be used when the request 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 must be resubmitted with a REC_MODE of C. C = Change Request (Forward Feed) R = Response (Reverse Feed) X = Resend (
