1、 ATIS-0404100-0046 Access Service Request (ASR) Mechanized Interface Specifications Issue 35 ASR Version 46 March 2013 ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 As a leading technology and solutions development organization, ATIS brings together
2、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, operations
3、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 Institute (
4、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-American Tel
5、ecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0404100-0046 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 Billing
6、 Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2012 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retriev
7、al 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-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 Limited Exception for “Customized” Forms. In recognition of
8、 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 used by an i
9、ndividual 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 obtained by cont
10、acting 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 make it compa
11、ny 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 reproduced in whole
12、 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 BELL tradem
13、ark, 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 Technologies or its pro
14、ducts. 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 generally accepted
15、engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION
16、 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 LIABLE, BEYOND TH
17、E 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 THIS DOCUMENT IS A
18、T THE RISK OF THE USER. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0046 Access Service Request (ASR) Mechanized Interface Specifications Issue 35, ASR Version 46 Summary ATIS-0404100-0046 Effective
19、March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 SUMMARY OF CHANGES This issue of the Mechanized Interface Specifications provides the details to sup
20、port the mechanization implementation of the following OBF issues: Issue Numbers 3440, 3444, 3446, 3454, 3462 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 3439, 3445 (Withdrawn)
21、, 3452, 3453, 3458, 3461, 3463 Global Changes: Changed UNI/NNI reference to UNI/ENNI references throughout the document Section 1: No changes were made to this section Section 2: The following existing sections and record types were modified with ASOG 46: 2.1.2.2 CORRECTION REQUEST Inserted new allo
22、wable condition for EVCI field (Issue 3440) REC TYP = S ASR (ADMINISTRATIVE) Modified Number of Fields from 83 to 84 (3454) Modified Filler at line #30 from 6 to 5 (3454) Insert new field (NAG) at line #31 (3454) Renumbered remaining fields (3454) REC TYP = J END USER SPECIAL ACCESS Modified Data Ar
23、ea Length from 760 to 762 (3444) Modified Number of Fields from 61 to 62 (3444) Insert new field (LAG_P) at line #62 (3444) REC TYP = P TRANSPORT Modified Data Area Length from 697 to 699 (3444) Modified Number of Fields from 54 to 55 (3444) Insert new field (LAG_P) at line #55 (3444) ATIS-0404100-0
24、046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 REC TYP = F10B COMPANY SPECIFIC ASR LEVEL (ECI) Changed fields 28 (AALCON TEL), 31 (ALCON EMAIL) and 37 (LCON EMAIL) to Filler (3462) REC TYP = F47A ETHERNET VIRTUAL CONNECTION Modified Data Area Length from 708 to 709
25、 (3444) Modified Number of Fields from 35 to 36 (3444) Removed SVLAN IND at line #27 and replaced with filler (3444) Added SVLAN Data Array at line #28 (3444) Modified start position at line #29 (R/L) from 274 to 297 (3444) Modified start position at line #30 (OTC) from 275 to 298 (3444) Modified st
26、art position at line number #31 (Filler) from 279 to 302 (3444) Modified length at line #31 (Filler) from 62 to 39 (3444) Inserted new field (SVP) at line #36 (3444) Section 3: The following existing record type was modified with ASOG 46: REC TYP = N Confirmation Notice (CN) Changed data area length
27、 from 676 to 700 (3444) Changed Number of Fields from 52 to 53 (3444) Inserted new field (LAG_ID) at line #53 (3444) REC TYP = R50A CLARIFICATION/NOTIFICATION REQUEST Changed Number of Fields from 26 to 27 (3446) Modified length at line #25 (Filler) from 50 to 49 (3446) Inserted new field (SDI) at l
28、ine #26 (3446) Changed JEOPARDY ARRAY number 26 to 27 (3446) Section 4: No changes were made to this section Section 5: The following section was modified with ASOG 46: 5.2 REJECT CONDITIONS Modified a reject condition for EVCI field (Issue 3440) Modified existing reject condition for SECLOC field (
29、Issue 3454) Created a new reject condition for SECLOC field (Issue 3454) ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 Section 6: Added new Section 6.2.1 (S-VLAN) to explain the conversion of embedded base data due to the length change or deletion of
30、 the specified fields. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0046 Access Service Request (ASR) Mechanized Interface Specifications Issue 35, ASR Version 46 Section 1 General ATIS-0404100-0046 E
31、ffective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 THIS PAGE INTENTIONALLY LEFT BLANK. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 MECHANIZED INTERFACE SPECIFICATIONS SECTION 1 TABLE OF CONTENTS 1. GENERAL 1-1 1.1 MECHANIZ
32、ED 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-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 1-1 1. GENERAL This
33、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 Interface (ASOG Document) which describes the industry agreed upon guidelines for the o
34、rdering 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 provides error conditions for systems that support the provisioning of Access Services. In a
35、n 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 rules governing provider/customer transmission of the request; error conditions; and the
36、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 negotiated between provider and
37、 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 transmitted to the custome
38、r. 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 CONFIRMATION (FOC) FILE SERV
39、ICE REQUEST CONFIRMATION (SRC) FILE PROVIDER CORRECTION (PC) FILE CLARIFICATION/NOTIFICATION REQUEST (C/NR) FILE These files are described in Section 3.0. ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 1-2 Figure 1-1. ASR Provider/Customer INTERFACE (
40、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 CUSTOMERORDERPROCESSOR2. LOADVALIDATION4. PRO
41、CESSING1. REQUEST FILE(ASR RECORDS)3. RESPONSE FILES(acks / rejects)ERRORSRC(2)PC (3)C/NR (4)CUSTOMERPROVIDERFOC (1)ATIS-0404100-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 1-3 1.2 RECORD LAYOUT AND FILE STRUCTURE Each file contains fixed format, fixed length r
42、ecords 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 Transfer Files The first record in e
43、ach 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 information for the access request.
44、 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-0046 Effective March 16, 2013 Issued September 21, 2012 Implemented March 16, 2013 1-4 1.2.1 CONTROL DATA All data records have an initial control area (in
45、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 scheme that is associated with the REC_I
46、D 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 processed. Invalid information in this field
47、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 section 3.7 for the reverse feed records. REC
48、_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 contain the same REC_MODE value. Valid
49、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 (REC_TYP = S) on the initial request was accepted, then all records associated with this requ
