1、 ATIS-0410003-0027 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 52 ATIS-0410003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 2 As a leading technology and solutions development organization, the Alliance for Telecom
2、munications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently working to address the All-IP transition, network functions virtualization, big data analytics, cloud services
3、, device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development lifecycle from design and innovation through standards, specifications, requirements, business use cases, s
4、oftware toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global init
5、iative, a member of and major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0410003-0027 Unified Ordering Model (UOM) Volume III - Design Is an ATIS s
6、tandard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Ordering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2015 by Alliance for Telecommunicat
7、ions Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an 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 . Printed in the United State
8、s of America. ATIS-0410003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 3 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 interpre
9、t its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR C
10、ONFORMS 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 THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY
11、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 AT THE RISK OF THE USER SUMMARY OF CHANGES A
12、SOG V52 Page 1 of 3 This issue of the Unified Ordering Model (UOM) Volume III Design provides the XML schemas that support the Access Service Ordering Guidelines (ASOG) and the Unified Ordering Model Volume I Business Requirements for Version 52. Changes to this document have been made in support of
13、 the following issues: 3519, 3529, 3533, 3535, 3538, 3540, 3541 The following issues went into Final Closure; however they resulted in no impact to the contents of this document: 3530, 3531, 3532, 3534 (withdrawn), 3537, 3539 Global Changes Change all ASOG 51 to ASOG 52; Version 51 to Version 52; Is
14、sue 26 to Issue 27. Change ATIS document number from ATIS-0410003-0026 to ATIS-0410003-0027. Update Issue Date. Sort the placement of some element and complexType definition structures alphabetically. (Note: The sequence of elements within a structure are not changed.) Other grammatical and spelling
15、 corrections that do not impact the technical content of this document are not reflected in the Summary of Changes. Table of Contents Updated to reflect document re-pagination. SUMMARY OF CHANGES ASOG V52 Page 2 of 3 UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V52 Schema Issue # Element Name De
16、scription of Change UOM-BASE UOM-BASE All ASOG_VER_Type Changed the enumeration value from 51 to 52. UOM-BASE 3519 IndicatorY_Type Added metadata references for the new WSI_P (ASR-001) element. Renamed the existing WSI (ASR-001) element to WSI_S and updated its metadata reference to match. UOM-BASE
17、3529 BAN13_Type Added this new simpleType (maxLength=13) with metadata references for the existing BAN (ASR-001, CN-011, and MEC-018) element. UOM-BASE 3535 CI_Type Added this new simpleType (maxLength=3) with metadata references for the new CI (SES-008) element. UOM-BASE 3535 PBITCI_Type Added this
18、 new simpleType (maxLength=8) with metadata references for the new P_BITC_I (EVC-016) element. UOM-BASE 3535 PBITCE_Type Added this new simpleType (maxLength=2) with metadata references for the new P_BITC_E (EVC-016) element. UOM-BASE 3538 IndicatorYN_Type Added this new simpleType (maxLength=1) wit
19、h metadata references for the existing EDA (ASR-001) element. UOM-BASE 3540 ECCKT28_Type Added metadata references for the new MCLAG_ID (CN-011 and SES-008) elements. UOM-BASE 3540 LAG_Type Added metadata references for the new MCLAG (SES-008) element. UOM-BASE 3540 LAGP_Type Added metadata referenc
20、es for the new MCLAG_P (SES-008) element. UOM-BASE 3541 IndicatorY_Type Added metadata references for the new LOAI element. UOM-BASE 3541 CNA_Type Added metadata references for the new LOA_CCNA element. UOM-ASR UOM-ASR 3519 ADMIN Added the new WSI_P element to the sequence after the existing PLU ele
21、ment. Renamed the existing WSI element to WSI_S. The type definition for the WSI_S element was renamed from WSI_Type to IndicatorY_Type. UOM-ASR 3529 ADMIN The type definition for the existing BAN element was renamed from BAN_Type to new BAN13_Type. UOM-ASR 3529 ASC_EC_DETAILS The type definition fo
22、r the existing BAN element was renamed from BAN_Type to new BAN13_Type. UOM-ASR 3529 OTHER_EC_DETAILS The type definition for the existing BAN element was renamed from BAN_Type to new BAN13_Type. SUMMARY OF CHANGES ASOG V52 Page 3 of 3 UOM-ASR VOLUME III - SUMMARY OF CHANGES FOR ASOG V52 Schema Issu
23、e # Element Name Description of Change UOM-ASR 3533 SALI The type definition for the existing ACTEL, AACTEL, ALCON_TEL and AALCON_TEL elements were renamed from TelNumberExt14_Type to existing TelNumberExt17_Type. UOM-ASR 3535 SES_SVC_DETAILS Added the new CI element to the sequence after the existi
24、ng HVP element. UOM-ASR 3535 LREF_MAPPING Added the following new elements to the sequence: P_BITC_I and P_BITC_E after existing BCF_I element. UOM-ASR 3538 ADMIN The type definition for the existing EDA Base Type was changed from the existing element IndicatorY_Type to new IndicatorYN_Type. UOM-ASR
25、 3540 SES_SVC_DETAILS Added the following new elements to the sequence: MCLAG_ID, MCLAG and MCLAG_P after existing LAG_P element. Moved the existing MSFS element to be located after the existing PROFI element. Moved the existing SM element to be located after the MSFS element. Moved the existing WAC
26、D1 element to be located after the new MCLAG_P element. Moved the existing L2CP_ADDR element to be located after the existing L2CPP element. UOM-ASRInquiry UOM-ASRInquiry 3541 CFA_INQUIRY_Type Added the LOAI and LOA_CCNA elements to the sequence in the existing CFA_INQUIRY_Type UOM-ASRMEC No changes
27、 for ASOGv52. UOM-ASRNotify UOM-ASRNotify 3540 CN Added the new MCLAG_ID element to the sequence after the existing LAG_ID element. Moved the existing PROJECT element to be located after the existing AP_REP_TEL element. Moved the existing PROVINT element to be located after the PROJECT element. Move
28、d the existing CNO element to be located after the existing PIA element. Moved the existing APP element to be located after the CNO element. Moved the existing SRN element to be located after the APP element. Moved the existing CB_TEL_NO element to be located after the SRN element. Moved the existin
29、g CBPC element to be located after the CB_TEL_NO element. UOM-ASRNotify 3529 CN The type definition for the existing BAN element was renamed from BAN_Type to new BAN13_Type. ATIS-0410003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 4 Table Of Contents 1. SCOPE, PURPOSE AND
30、 FIELD OF APPLICATION . 5 1.1 SCOPE 5 1.2 PURPOSE 5 1.3 APPLICATION . 5 2. STANDARDS/REFERENCES . 5 2.1 ATIS REFERENCES 5 2.2 OTHER STANDARDS . 6 2.3 ACRONYMS 6 3. DEFINITIONS . 7 4. OVERVIEW OF UOM-ASR VOLUME III . 8 4.1 INTRODUCTION TO UOM 8 4.2 REQUIREMENTS OF THIS DOCUMENT . 11 4.3 STRUCTURE OF
31、THIS DOCUMENT . 12 4.4 HOW TO USE THIS DOCUMENT . 12 5. REQUIREMENTS OVERVIEW 12 6. ANALYSIS OVERVIEW . 12 7. IMPLEMENTATION OVERVIEW 13 8. DESIGN (TECHNOLOGY INFORMATION MODEL) 13 8.1 TML SCHEMAS 13 8.1.1 CONFORMANCE STATEMENT TO THE TML FRAMEWORK . 13 8.1.2 UOM-BASE SCHEMA . 14 8.1.3 UOM-ASR SCHEM
32、A 184 8.1.4 UOM-ASRINQUIRY SCHEMA 252 8.1.5 UOM-ASRMEC SCHEMA 261 8.1.6 UOM-ASRNOTIFY SCHEMA . 270 ATIS-0410003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 5 1 Scope, Purpose, used in XML documents as element types and attribute names. Namespaces are used in XML to qualif
33、y names in order to separate them from other names. Note: A URI has a similar format to a URL. It is not always possible to resolve a URI to find an instance of an XML schema. ATIS-0410003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 8 Schema: A set of schema components. A
34、 collection (vocabulary) of type definitions and element declarations whose names belong to a particular namespace called a target namespace. A schema defines the allowable contents of a class of XML documents. The purpose of a schema is to define and describe a class of XML instance documents by us
35、ing these constructs to constrain and document the meaning, usage and relationships of their constituent parts: datatypes, elements and their content, attributes and their values, entities and their contents, and notations. A class of documents refers to all possible permutations of structure in ins
36、tance documents that will still conform to the rules of the schema. Schema Component: The generic term for the building blocks that comprise the abstract data model of the schema. There are 13 kinds of schema components defined: named components (Simple type definitions, Complex type definitions, At
37、tribute declarations, Element declarations, attribute group definitions, identity-constraint definitions, model group definitions, notation declarations, annotations), and un-named components (model groups, particles, wildcards, and attribute uses). tML Schema: Constructs to constrain and document t
38、he meaning, usage and relationships of the constituent parts of tML instance documents. tML Schemas are based on the W3C XML Schema Recommendation. tML Namespace: A collection of names, identified by a URI reference RFC2396, that is used in tML documents as element types and attributes UML: An OMG s
39、pecification to provide system architects working on object analysis and design with one consistent language for specifying, visualizing, constructing, and documenting the artifacts of software systems and for modeling of business processes 4 Overview of UOM-ASR Volume III 4.1 Introduction to UOM Th
40、e document, Unified Ordering Model Access Service Request Volume III Design, (UOM-ASR Volume III) is part of a set of documents that provides an end-to-end structured systems engineering approach to perform the design related to unified ordering via electronic interfaces. This document provides the
41、design of the detailed business and analysis for an ordering model for the UOM interface. It describes the tML/XML Schemas with the intent that service providers and their vendors can use the tML/XML Schemas when exchanging data for an ASR application. Because of the level of complexities inherent i
42、n such an electronic ordering model, a tML Framework Document (ITU-T M.3030) has been used as a guide to develop this volume. The intent of Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structured methodology. The scope of UOM encompasses busin
43、ess requirements, analysis, design, and implementation. Logically, these components are defined within the UOM in four volumes. UOM-ASR Volume I - Business Requirements This document describes the business requirements. This volume includes a high-level overview of the three primary processes in ord
44、ering: pre-ordering, service request, and post-confirmation activities. It also includes more detailed information in the use cases and activity diagrams. Two appendices include the data dictionary and the functional data matrix. The UOM-ASR Volume I is ATIS-0410003-0027 UOM-ASR Volume III Issued Se
45、ptember 19, 2015 Issue 27 for ASOG v52 9 focused on ordering for access services only. As other services are added in the future, additional Volume I documents may be developed. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains the UOM-ASR Volume I document. ATIS-04
46、10003-0027 UOM-ASR Volume III Issued September 19, 2015 Issue 27 for ASOG v52 10 UOM-ASR Volume II - Analysis This analysis document provides the logical view of the business requirements stated in Volume I. The primary sections include the information model, sequence diagrams, and behavior model. B
47、oth the informational and behavioral models are described using the Unified Modeling Language (UML). UOM-ASR Volume II utilizes UML for descriptive purposes and in some instances may not strictly adhere to existing UML specifications. The UML provides the notation used within Volume II. Because of t
48、he level of complexities inherent in such an electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop Volume II. Some additional requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electr
49、onic interexchange. Volume II is not specific to any particular technology or protocol. If additional Volume I documents are developed, Volume II may need to be expanded to address additional requirements. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume II. UOM-ASR Volume III - Design The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the selected implementation technology. The first technology
