1、 ATIS-0410003-0028 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 53 ATIS-0410003-0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 2 As a leading technology and solutions development organization, the Alliance for Telecommuni
2、cations 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, de
3、vice 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, softw
4、are 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 initiati
5、ve, 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-0028 Unified Ordering Model (UOM) Volume III - Design Is an ATIS stand
6、ard 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 2016 by Alliance for Telecommunications
7、 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 States of
8、 America. ATIS-0410003-0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 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 interpret its co
9、ntents 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 CONFORMS
10、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 ATIS FOR
11、 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 ASOG V53
12、Page 1 of 2 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 the fol
13、lowing issues: 3529 (correction from ASOGv52, OEC BAN only ), 3544, 3525, 3548 The following issues went into Final Closure; however they resulted in no impact to the contents of this document: 3492, 3515, 3547 Global Changes Change all ASOG 52 to ASOG 53; Version 52 to Version 53; Issue 27 to Issue
14、 28. Change ATIS document number from ATIS-0410003-0027 to ATIS-0410003-0028. 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 corrections th
15、at do not impact the technical content of this document are not reflected in the Summary of Changes. Text Added new Section 8.1.1 regarding release conversion information and renumbered remaining sections (3525). Table of Contents Updated to reflect document re-pagination. SUMMARY OF CHANGES ASOG V5
16、3 Page 2 of 2 UOM-ASR VOLUME III SUMMARY OF CHANGES FOR ASOG V53 Schema Issue # Element Name Description of Change UOM-BASE UOM-BASE All ASOG_VER_Type Changed the enumeration value from 52 to 53. UOM-BASE 3544 Power5_Type Added this new simpleType (maxLength=5) with metadata references for the new P
17、TV (ACI-007, SES-008) element. UOM-BASE 3544 ECCKT28_Type Added metadata references for the new RCID (TRANS-005, ACI-007 and EUSA-013) elements. UOM-ASR UOM-ASR 3544 SES_LOCATION Added the new PTV element to the sequence after the existing SUBNET_MASK element. UOM-ASR 3544 ACI Added the new PTV elem
18、ent to the sequence after the existing SUBNET_MASK element. UOM-ASR 3548 ACI Added the new RCID element to the sequence after the existing SM element. UOM-ASR 3548 EUSA_SVC_DETAILS Added the new RCID element to the sequence after the existing PSPEED element. Moved the existing LMP element to be loca
19、ted after the existing SECNCI element. Moved the existing N_U element to be located after the LMP element. Moved the existing BSC element to be located after the new N_U element. Moved the existing ETET element to be located after the existing BSC element. UOM-ASR 3548 TRANSPORT Added the new RCID e
20、lement to the sequence after the existing NSL element. UOM-ASRInquiry No changes for ASOGv53. UOM-ASRMEC No changes for ASOGv53. UOM-ASRNotify UOM-ASRNotify 3529 BANC The type definition for the existing BAN element was renamed from BAN_Type to new BAN13_Type. UOM-ASRNotify 3529 BANC Modified the ex
21、isting APREP element to AP_REP for error identified during review. ATIS-0410003-0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 4 Table Of Contents TABLE OF CONTENTS 4 1 SCOPE, PURPOSE, used in XML documents as element types and attribute names. Namespaces are used in XML to qual
22、ify 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-0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 8 Schema: A set of schema components. A c
23、ollection (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 usin
24、g 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 insta
25、nce 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, Attr
26、ibute 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 the
27、 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 spe
28、cification 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 The
29、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 de
30、sign 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 in
31、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 busines
32、s 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 order
33、ing: 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-0028 UOM-ASR Volume III Issued Marc
34、h 25, 2016 Issue 28 for ASOG v53 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-0410003-
35、0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 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. Both the in
36、formational 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 the level o
37、f 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 electronic inter
38、exchange. 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. U
39、OM-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 selected was XML; therefore UOM-ASR Volume III includes appropriate XML schemas
40、related to unified access ordering. This document does not specify a particular transport protocol as it is assumed that the trading partners will determine the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. Th
41、e OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. Volume III specifies the interface standard for the Unified Ordering Model for access services using the telecommunications Markup Language (an extension of XML), as defined in tML Framework. All Fu
42、nctions in this standard are designed as optional features. The implementation of the functions (use cases) will be determined between individual customer and provider negotiations. UOM Volume IV Generic Implementation Guideline This document includes implementation specifications that must be addre
43、ssed before the system specifications can be realized using the selected implementation technology. In addition, a sample Joint Implementation Agreement (JIA) may be included as an appendix for trading partners to use as a starting template. As with the Design Phase, the Implementation Phase may als
44、o have to be repeated in order to provide support for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. ATIS-0410003-0028 UOM-ASR Volume III Issued March 25, 2016 Issue 28 for ASOG v53 11 Unified Model1. Business Requirements:-H
45、igh Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirements-Business Validation Rules2. Logical Analysis:-Informational Model-Behavioral Model-Sequence Diagrams-Class/Object Diagrams-State Diagrams-Traceability Matrix3. Technical Standard:-Technology Speci
46、fic- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF 1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document DevelopmentFigure 1 - UOM ASR Process and Document Develo
47、pment 4.2 Requirements of this document The following requirements have been taken into account by the Ordering Solutions Committee/Access Service Ordering Subcommittee in the development of UOM-ASR Volume III: UOM-ASR Volume III should be technology-specific and tML is chosen to be the technology t
48、o present the syntax of information definition. Therefore, the tML Schemas defined for the UOM-ASR should conform to the tML Framework Document (ITU-T M.3030). UOM-ASR Volume III tML Schemas for the Design phase of the UOM-ASR project should reflect the current analysis described in UOM-ASR Volume I
49、I (that reflects the requirements in UOM-ASR Volume I). UOM-ASR Volume III should be backward compatible with UOM-ASR Volume I and UOM-ASR Volume II. UOM-ASR Volume III should be generic, flexible, and have reusability. UOM-ASR Volume III edits in the tML Schemas are minimized to the maximum data length and a minimum subset of required fields. Other validation rules and processes are generally left to the customer/provider back-end systems. UOM-ASR Volume III will contain tag names not to exceed 20 characters in length and will be
