1、 ATIS-0404100-0053 Access Service Request (ASR) Mechanized Interface Specifications Issue 42 ASR Version 53 September 2016 ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 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-0053 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 2016 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-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 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-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 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-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0053 Access Service Request (ASR) Mechanized Interface Specifications Issue 42, ASR Version 53 Summary ATIS-040
19、4100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 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 3529 (correction from ASOGv52, OEC BAN only), 3544, 3548 The following OBF Issues went into Final Closure; however, they have no impact on mechanization on the record layouts/rules defined wi
21、thin this document: Issue Numbers 3492, 3515, 3525, 3547 ASOG 53 will be the last release supported by the MECH SPEC documentation: Issue 3491 went into Closure discontinuing the use of Access Service Request (ASR) Mechanized Interface Specifications ATIS-0404100. This will sunset effective December
22、 31, 2016 MECH SPEC will no longer be supported as a transmission method for ASRs. ASOG 53 will be the last release with MECH SPEC documentation. All future transmission of ASRs will be transmitted via UOM as of January 1, 2017. DLRs are not impacted by this Issue. The recommended transition strateg
23、y from MECH SPEC to an alternate method is as follows: Effective January 1, 2017 the only accepted standardized industry transmission method between a Customer and a Provider is a UOM based transaction as batch transactions are no longer accepted. o This is inclusive of all pending requests and resp
24、onse transactions. Customer/Provider negotiations may occur to address specific situations outside the specific recommendations. Any customer needing to convert to UOM must work with their providers to create a schedule of implementation by July 1, 2016. Section 1: No changes were made to this secti
25、on Section 2: REC TYP = J END USER SPECIAL ACCESS Replaced FILLER with RCID at line #54 (3548) Modified Filler length at line #53 from 39 to 12 (3548) ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 REC TYP = F40B (Multi EC) Modified OEC_DATA Array
26、 at line #13 to change BAN field from length of 12 to 13 (3529) Modified OEC_DATA Array at line #13 to change the HBAN from start length 118 to start length 119 (3529) Modified OEC_DATA Array at line #13 to change the OECVTA from start length 130 to start length 131 (3529) Modified OEC_DATA Array at
27、 line #13 to change the ASG from start length 147 to start length 148 (3529) Modified OEC_DATA Array at line #13 to change the Filler from start length 153 to start length 154 and from length of 78 to 77 (3529) REC TYP = L (Switched Ethernet Services) Changed data area length from 596 to 601 (3544)
28、Added PTV field with length of 5 at line #44 (3544) Changed number of fields from 43 to 44 (3544) REC TYP = P TRANSPORT Replaced FILLER with RCID at line #52 (3548) Modified Filler length at line #51 from 1 to 3 (3548) REC TYP = C (Additional Circuit Info) Modified Filler at line #29 from length of
29、6 to length of 1 (3544) Added PTV field with length of 5 at line #30 (3544) Inserted new field for RCID at line #63 (3548) Changed data area length from 764 to 792 Change number of fields from 61 to 63 Section 3: No changes were made to this section Section 4: No changes were made to this section Se
30、ction 5: No changes were made to this section Section 6: No changes were made to this section ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0053 Access Service Request (ASR) Mechanized Interface Sp
31、ecifications Issue 42, ASR Version 53 Section 1 General ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 MECHANIZ
32、ED 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 Provider 1-7 1.3.2 Provider Customer 1-7 ATIS-0404100-0053 Effective Septe
33、mber 17, 2016 Issued March 25, 2016 Implemented September 17, 2016 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 Guidelines Industry Support
34、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 the ASR. It also provi
35、des 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 components of each file; the ru
36、les 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 may be transmitted be
37、tween 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 into the provider system.
38、 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 file, the provider sy
39、stem 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-0053 Effective September 17, 2016 Issued Marc
40、h 25, 2016 Implemented September 17, 2016 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 Access Service Ordering Guidelines (ASOG) (3) PC = Provider Correction
41、(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-0053 Effective September 17, 2016 Issued March 25, 2016 Implemented September 17
42、, 2016 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 CONTROL ACCESS ORDE
43、R 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 Header Record, e
44、ach 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-0053 Effective September 17, 2016 Issued March 25, 2016 Imple
45、mented September 17, 2016 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 fields that a
46、re 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 one-charac
47、ter 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 field may be f
48、ound 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. REC_MODEs
49、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 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 (RE
