1、 ATIS-0410002-0031 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) Version 56 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 2 As a leading technology and solutions development organization, the Alliance for Te
2、lecommunications 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 ser
3、vices, 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 cas
4、es, software 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
5、 initiative, 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 0410002-0031 Unified Ordering Model (UOM) Volume II - Analysis Is an
6、ATIS standard 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 Telecommu
7、nications 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
8、States of America. ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 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
9、 interpret 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 SUFFIC
10、IENT 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 THE AMOUNT OF ANY SUM RECEIVED IN PA
11、YMENT 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 AT THE RISK OF THE USER. ATIS-04100
12、02-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 4 Change History Issue # Document Release Description of Changes 31 R1 Initial version for ASR 56 30 R1 Initial version for ASR 55 29 R1 Initial version for ASR 54 28 R1 Initial version for ASR 53 27 R1 Initial version fo
13、r ASR 52 26.1 R1 Revision to align Error_ComplexType model with schema 26 R1 Initial version for ASR 51 25 R1 Initial version for ASR 50 24 R1 Initial version for ASR 49 23 R1 Initial version for ASR 48 22 R1 Initial version for ASR 47 21 R1 Initial version for ASR 46 20 R1 Initial version for ASR 4
14、5 19 R1 Initial version for ASR 44 18 R1 Initial version for ASR 43 17 R1 Initial version for ASR 42 16 R1 Initial version for ASR 41 15 R1 Initial version for ASR 40 14 R1 Initial version for ASR 39 13 R1 Initial version for ASR 38 12 R1 Initial version for ASR 37 11 R1 Initial version for ASR 36 1
15、0 R1 Initial version for ASR 35 9 R1 Initial version for ASR 34 8 R1 Initial version for ASR 33 7 R1 Initial version for ASR 32 6 R1 Initial version for ASR 31 5 R1 Initial version for ASR 30 4 R1 Initial version for ASR 29 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for A
16、SOG v56 Page 5 3 R1 Initial version for ASR 28 2 R2 Minor changes to synch up with schema affecting the TQ form 2 R1 Initial version for ASR 27 1 R3 Final version of UOM-ASR Volume II for ASR 26 1 R2 Revisions to support synchronization with Volume III XML schema 1 R1 Base line version of UOM-ASR Vo
17、lume II for ASR 26 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 6 Table of Contents CHANGE HISTORY 4 TABLE OF CONTENTS 6 1 UOM DOCUMENTATION 8 2 INTRODUCTION TO UOM-ASR VOLUME II 9 2.1 INTENDED AUDIENCE . 9 2.2 PURPOSE 9 2.3 SCOPE 9 2.4 DEVELOPMENT NOTE .
18、10 3 OVERVIEW OF UOM-ASR VOLUME II 10 3.1 ASSUMPTIONS OF THIS DOCUMENT 10 3.2 STRUCTURE OF DOCUMENT . 11 3.3 OVERALL PROCESS DESCRIPTION 11 3.4 UOM-ASR HIGH LEVEL PROCESS OVERVIEW 11 4 UOM REQUIREMENTS SUMMARY . 12 4.1 BUSINESS REQUIREMENTS . 12 4.2 SYSTEM REQUIREMENTS . 12 4.3 SECURITY REQUIREMENTS
19、: 12 4.4 MESSAGING REQUIREMENTS: . 13 4.5 USER PROFILE REQUIREMENTS . 14 4.6 REPORTING REQUIREMENTS 15 5 USE CASE REALIZATIONS USING SEQUENCE DIAGRAMS . 15 5.1 UOM PRE-ORDER USE CASES 15 5.1.1 Location Inquiry 16 5.1.2 Service Availability Inquiry . 17 5.1.3 CFA Inquiry 19 5.2 UOM SERVICE REQUEST US
20、E CASES 20 5.2.1 Customer Provider Communication . 22 5.2.2 Multiple Exchange Carrier Communication . 34 5.3 UOM POST-CONFIRMATION USE CASES 53 5.3.1 Jeopardy Status . 54 5.3.2 Provider Initiated Jeopardy 54 5.3.3 Retrieve Service Request Information . 56 5.3.4 Retrieve Service Request Information b
21、y Customer . 56 5.3.5 Completion Notification 57 5.3.6 Design Notification . 58 6 INFORMATION MODEL 60 6.1 UOM-ASR HIGH LEVEL VIEW 60 6.2 INQUIRY REQUEST CLASSES 61 6.2.1 ASR Inquiry Request Classes . 62 6.3 INQUIRY RESPONSE CLASSES 68 6.3.1 ASR Inquiry Response Classes . 68 6.4 SERVICE REQUEST CLAS
22、SES . 73 6.4.1 ASR Service Request Classes 73 6.4.2 Multiple Exchange Carrier Communication Request Classes . 114 6.5 SERVICE RESPONSE CLASSES . 117 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 7 6.5.1 ASR Service Response Classes . 118 6.5.2 Multiple Exch
23、ange Carrier Communication Response Classes 119 6.6 NOTIFICATION CLASSES . 122 6.6.1 ASR Notification Classes . 123 6.6.2 Multiple Exchange Carrier Communication Notification Classes 130 6.7 ACKNOWLEDGEMENT CLASSES 133 6.7.1 ASR Acknowledgement . 133 6.7.2 MEC Acknowledgement. 134 6.8 EXCEPTION RESP
24、ONSE CLASS . 134 7 BEHAVIOR MODEL 136 7.1 STATE AND ACTIVITY DIAGRAMS . 136 REFERENCES 139 APPENDIX A: MEET POINT COORDINATION PROCESS FLOW 140 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 8 1 UOM Documentation The document, Unified Ordering Model Volume I
25、I Analysis, (UOM-ASR Volume II) is part of a set of documents that provides an end-to-end structured systems engineering approach to perform the analysis related to unified ordering via electronic interfaces. This document provides the analysis of the detailed business and systems requirements for a
26、n ordering model. It describes the information model and the behavioral model with the intent that service providers, customers, and their vendors understand how the data, business rules and systems rules work together with the behavior of the data and rules. Because of the level of complexities inh
27、erent in such an electronic ordering model, Unified Modeling Language (UML) tools by RationalRose and MyEclipse have been used to develop this volume. UOM-ASR Volume II utilizes UML for descriptive purposes and in some instances may not strictly adhere to existing UML specifications. The intent of U
28、nified 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 implementation. Logically, these components are defined within the UOM in four volumes. UOM-ASR Volum
29、e 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 post-confirmation activities. It also includes more detailed information in the use cases and activ
30、ity 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, additional Volume I documents may be developed. The OBF Ordering Solutions Committee/Access Servic
31、e Ordering Subcommittee maintains the UOM-ASR Volume I document. 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 informat
32、ional 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 of comp
33、lexities inherent in such an electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop this Volume II. Some additional requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic intere
34、xchange. Volume II is not specific to any particular technology or protocol. If additional Volume I documents are developed, this Volume II may need to be expanded to address additional requirements. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume I
35、I. 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 selected is XML; therefore UOM-ASR Volume III includes appropriate XML schem
36、as related to unified ordering. This document does not specify a particular 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
37、 Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. UOM-ASR Volume IV - Implementation This document includes implementation specifications that must be addressed before the system specifications can be realized using the selected implementation technology. In add
38、ition, 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 ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 f
39、or ASOG v56 Page 9 provide support for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirem
40、ents-Business Validation Rules2. Logical Analysis:-Informational Model-Behavioral Model-Sequence Diagrams-Class/Object Diagrams-State Diagrams-Traceability Matrix3. Technical Standard:-Technology Specific- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation P
41、rofileOBF1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document Development2 Introduction to UOM-ASR Volume II 2.1 Intended Audience The audience for this volume is the technical and software development staff of service
42、providers and customers. The audience includes anyone who wishes to gain a better understanding of the interface between the customer and the provider, or between providers, in the provisioning of Access Services. 2.2 Purpose The document is intended to assist providers and customers in the process
43、of conducting the analysis phase of their development steps to realize an electronic, unified ordering system. 2.3 Scope UOM-ASR Volume II describes the detailed analysis of the informational and behavioral model within a Unified Ordering Model. In addition, it defines at a more detailed level of th
44、e business requirements and ATIS-0410002-0031 UOM-ASR Volume II Issued September 22, 2017 Issue 31 for ASOG v56 Page 10 systems requirements needed to conduct ordering activities efficiently over an electronic interface. This includes a blending of the pre-ordering, service request and post-confirma
45、tion activities. Specifically, UOM-ASR Volume II-Analysis describes access service ordering as defined in: UOM-ASR Volume I Access Service Ordering Guidelines (ASOG) Multiple Exchange Carriers Ordering and Design (MECOD) Design Layout Report (DLR) Guidelines for Access Service These business require
46、ments are developed and maintained within the Ordering and Billing Forum (OBF) under the auspices of the Ordering Solutions Committee/Access Service Ordering Subcommittee. UOM-ASR Volume II Analysis contains both the Informational and Behavioral Models that provide the reader a broad understanding o
47、f Service Ordering. Specifically, each model provides a dimension to the overall process: Informational Model describes the data relationships. Behavioral Model describes the data as it acts with stimuli/events over time. Both the Informational and Behavioral Models are described using the Unified M
48、odeling Language (UML). The UML provides the notation used within UOM-ASR Volume II. Because of the level of complexities inherent in such an electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop this volume1. NOTE: A new UML tool has been
49、chosen for updating class diagrams, starting with ASOG35. With the previous UML tool, one and only one associations displayed a 1 on the association line connecting classes. With this new tool, the 1 is omitted. Any changed class diagrams (moving forward) will no longer display the 1. The absence of a multiplicity indicator on these association lines should be interpreted as one and only one multiplicity. 2.4 Development Note The UOM process is iterative in nature. Subsequent iterations of UOM-ASR Volume II - Analysis may expand the functionality
