1、 ATIS-0410002-0027 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) Version 52 ATIS-0410002-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 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-0027 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 2015 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-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 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-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 Page 4 Change History Issue # Document Release Description of Changes 27 R1 Initial version for 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 AS
13、R 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 45 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 4
14、1 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 10 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
15、 Initial version for ASR 31 5 R1 Initial version for ASR 30 4 R1 Initial version for ASR 29 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 ATIS-0410002-0027 UOM-ASR Vo
16、lume II Issued September 19, 2015 Issue 27 for ASOG v52 Page 5 1 R2 Revisions to support synchronization with Volume III XML schema 1 R1 Base line version of UOM-ASR Volume II for ASR 26 SUMMARY OF CHANGES ASOG V52 Page 1 of 2 This issue of the Unified Ordering Model (UOM) Volume II Analysis provide
17、s the analysis and details to 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 following issues: 3519, 3529, 3533, 3535, 3538, 3540, 3541 The following issues
18、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; Issue 26 to Issue 27 Change ATIS document number from ATIS-0410002-0026 to ATIS-0410002
19、-0027 Update Issue Date Other grammatical and spelling 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 new sections, re-numbered sections, and document re-pagination SUMMARY OF CHANGES ASOG V52 Pag
20、e 2 of 2 UOM-ASR VOLUME II SUMMARY OF CHANGES FOR ASOG V52 Section # Issue # Model Object or Section Name Description of Change 6.2.1.3 3541 CFA_INQUIRY_Type Added the following new attributes: LOAI and LOA_CCNA. 6.4.1.2.1 3519 ADMIN Added the following new attribute: WSI_P Renamed the existing WSI
21、attribute to WSI_S. The type definition for the WSI_S attribute was renamed from WSI_Type to IndicatorY_Type. 6.4.1.2.1 3529 ADMIN The type definition for the existing BAN attribute was renamed from BAN_Type to BAN13_Type. 6.4.1.2.1 3538 ADMIN The type definition for the existing EDA attribute was r
22、enamed from IndicatorY_Type to new IndicatorYN_Type. 6.4.1.2.7 3535 SES_SVC_DETAILS Added the following new attribute: CI 6.4.1.2.7 3540 SES_SVC_DETAILS Added the following new attributes: MCLAG, MCLAG_ID and MCLAG_P. 6.4.1.3.6 3529 ASC_EC_DETAILS The type definition for the existing BAN attribute w
23、as renamed from BAN_Type to BAN13_Type. 6.4.1.3.6 3529 OTHER_EC_DETAILS The type definition for the existing BAN attribute was renamed from BAN_Type to BAN13_Type. 6.4.1.3.8 3533 SALI The type definition for the existing ACTEL, AACTEL, ALCON_TEL and AALCON_TEL elements were renamed from TelNumberExt
24、14_Type to existing TelNumberExt17_Type. 6.4.1.3.11 3535 LREF_MAPPING Added the following new attributes: P_BITC_I and P_BITC_E. 6.6.1.2 3529 CN The type definition for the existing BAN attribute was renamed from BAN_Type to BAN13_Type. 6.6.1.2 3540 CN Added the following new attribute: MCLAG_ID ATI
25、S-0410002-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 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 . 10 3 OVERVIEW OF UOM-A
26、SR 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: 12 4.4 MESSAGING RE
27、QUIREMENTS: . 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 USE CASES 20 5.2.1 Cust
28、omer Provider Communication . 21 5.2.2 Multiple Exchange Carrier Communication . 34 5.3 UOM POST-CONFIRMATION USE CASES 52 5.3.1 Jeopardy Status . 53 5.3.2 Provider Initiated Jeopardy 53 5.3.3 Customer Initiated Jeopardy 55 5.3.4 Retrieve Service Request Information . 56 5.3.5 Retrieve Service Reque
29、st Information by Customer . 56 5.3.6 Retrieve Service Request Information by Provider 57 5.3.7 Completion Notification 57 5.3.8 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 C
30、LASSES 67 6.3.1 ASR Inquiry Response Classes . 67 6.4 SERVICE REQUEST CLASSES . 71 6.4.1 ASR Service Request Classes 71 ATIS-0410002-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 Page 7 6.4.2 Multiple Exchange Carrier Communication Request Classes . 112 6.5 SERVICE RESPONSE
31、CLASSES . 115 6.5.1 ASR Service Response Classes . 116 6.5.2 Multiple Exchange Carrier Communication Response Classes 117 6.6 NOTIFICATION CLASSES . 120 6.6.1 ASR Notification Classes . 121 6.6.2 Customer Notification Class 128 6.6.3 Multiple Exchange Carrier Communication Notification Classes 130 6
32、.7 ACKNOWLEDGEMENT CLASSES 133 6.7.1 ASR Acknowledgement . 133 6.7.2 MEC Acknowledgement. 134 6.8 EXCEPTION RESPONSE 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-0027 UOM-ASR Volume II Issued S
33、eptember 19, 2015 Issue 27 for ASOG v52 Page 8 1 UOM Documentation The document, Unified Ordering Model Volume II 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 el
34、ectronic interfaces. This document provides the analysis of the detailed business and systems requirements for an 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 a
35、nd systems rules work together with the behavior of the data and rules. Because of the level of complexities inherent 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 de
36、scriptive purposes and in some instances may not strictly adhere to existing UML specifications. 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, d
37、esign, 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 ordering: pre-ordering, service
38、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 focused on ordering for access services only. As other services are added i
39、n 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. UOM-ASR Volume II - Analysis This analysis document provides the logical view of the business requirements stated in Volume
40、 I. The primary sections include the information model, sequence diagrams, and behavior model. Both 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 t
41、o existing UML specifications. The UML provides the notation used within 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 Volume II. Some additional requirements
42、are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic interexchange. 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 re
43、quirements. 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 implementati
44、on technology. The first technology selected is XML; therefore UOM-ASR Volume III includes appropriate XML schemas 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
45、 necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. UOM-ASR Volume IV - Implementation This document includes implementation specifications that must be
46、 addressed 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 m
47、ay also have to be repeated in order to ATIS-0410002-0027 UOM-ASR Volume II Issued September 19, 2015 Issue 27 for ASOG v52 Page 9 provide support for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. Unified Model1. Business Re
48、quirements:-High 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:-Tec
49、hnology Specific- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF1. 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 providers and customers. The audience includes anyone who wishes to gain a better understanding of the interface between the customer and the pr
