ATIS 0410003-0030-2017 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 55).pdf

《ATIS 0410003-0030-2017 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 55).pdf》由会员分享，可在线阅读，更多相关《ATIS 0410003-0030-2017 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 55).pdf（389页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0410003-0030 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) Version 55 ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 2As a leading technology and solutions development organization, the Alliance for Telecommunic

2、ations 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, dev

3、ice 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, softwa

4、re 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 initiativ

5、e, 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-0030 Unified Ordering Model (UOM) Volume III - Design Is an ATIS standa

6、rd 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 2017 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-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 3Notice 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 cont

9、ents 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 TO

10、 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 T

11、HIS 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 V55 Pa

12、ge 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 55. Changes to this document have been made in support of the follo

13、wing issues: 3571 The following issues went into Final Closure; however they resulted in no impact to the contents of this document: 3561, 3562, 3569 (Withdrawn), 3570, 3572 Global Changes Change all ASOG 54 to ASOG 55; Version 54 to Version 55; Issue 29 to Issue 30. Change ATIS document number from

14、 ATIS-0410003-0029 to ATIS-0410003-0030. 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 that do not impact the technical conten

15、t of this document are not reflected in the Summary of Changes. Table of Contents Updated to reflect document re-pagination. SUMMARY OF CHANGES ASOG V55 Page 2 of 2 UOM-ASR VOLUME III SUMMARY OF CHANGES FOR ASOG V54 Schema Issue # Element Name Description of Change UOM-BASE UOM-BASE 3571 EA_TYPE Add

16、ed new EA_TYPE to UOM-BASE and added metadata references to new EA_TYPE_A, EA_TYPE_Z elements (ECI-025) UOM-ASR UOM-ASR 3571 ECI_ASR_LEVEL Added new elements to the bottom of the sequence of EA_TYPE_A and EA_TYPE_Z. UOM-ASRInquiry No changes for ASOGv55. UOM-ASRMEC No changes for ASOGv55. UOM-ASRNot

17、ify No changes for ASOGv55. ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 4Table 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 qualify names in order to separate them from

18、 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. Schema: A set of schema components. A collection (vocabulary) of type definitions and element declarations whose names belong to a particular namespace called a t

19、arget namespace. A schema defines the allowable contents of a class of XML documents. The purpose of a schema is to define and ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 8describe a class of XML instance documents by using these constructs to constrain and docum

20、ent 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 instance documents that will still conform to

21、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, Attribute declarations, Element declarations,

22、 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 meaning, usage and relationships of the

23、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 specification to provide system architects w

24、orking 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 document, Unified Ordering Model Access S

25、ervice 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 design of the detailed business and analysi

26、s 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 such an electronic ordering model, a tML

27、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 business requirements, analysis, design, and imp

28、lementation. 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 ordering: pre-ordering, service request, and p

29、ost-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 focused on ordering for access services only. As other services are added in the future,

30、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-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 9ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2

31、017 Issue 30 for ASOG v55 10UOM-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 informational and behavioral models are descr

32、ibed 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 of complexities inherent in such an electron

33、ic 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 interexchange. Volume II is not specific to any

34、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

35、 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 related to unified access ordering. This do

36、cument 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. The OBF Ordering Solutions Committee/Access S

37、ervice 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 Functions in this standard are designed as op

38、tional 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 addressed before the system specifications can b

39、e 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 also have to be repeated in order to provide s

40、upport for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 11Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagr

41、ams-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 Specific- Interface Specification4. Implementatio

42、n 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 Development 4.2 Requirements of this document The

43、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 to present the syntax of information definiti

44、on. 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 II (that reflects the requirements in UOM-ASR

45、 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

46、. Other validation rules and processes are generally left to the customer/provider back-end systems. ATIS-0410003-0030 UOM-ASR Volume III Issued March 24, 2017 Issue 30 for ASOG v55 12 UOM-ASR Volume III will contain tag names not to exceed 20 characters in length and will be in upper case format to

47、 conform with the current OBF guidelines. UOM-ASR Volume III does not convey licensing right to non-COMMON LANGUAGE licensees to use the COMMON LANGUAGE1code sets identified throughout the UOM-ASR Volume III document in their internal operations. Where COMMON LANGUAGE is provided, its intended use b

48、y non-COMMON LANGUAGE licensees is limited. Allowable uses will be specified by the COMMON LANGUAGE licensee, per their COMMON LANGUAGE contract. 4.3 Structure of this document The remainder of the document consists of the following sections: Sections 5, 6 and 7 provide references to the documents t

49、hat define the requirements, analysis, and implementation specifications for the UOM-ASR application. Section 8 consists of tML Schemas: o UOM-Base Schema, that defines all reusable domain specific and non-domain specific common types and elements that are used in tML Schemas for various UOM applications, and o UOM-ASR, UOM-ASRInquiry, UOM-ASRMEC and UOM-ASRNotify that present the service request, inquiry, notification, acknowledgement, and exception response interactions in the access domain. 4.4 How to use this document This document