1、 ATIS-0404110-0031 Unified Ordering Model - Access Service Request (UOM-ASR) Volume I Business Requirements For An Electronic Ordering Interface ATIS-0404110-0031 UOM-ASR Volume I Issued September 22, 2017 Implemented March 17, 2018 i As a leading technology and solutions development organization, t
2、he Alliance for Telecommunications 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 an
3、alytics, cloud services, 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
4、, business use cases, 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
5、 the oneM2M global 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 0404110-0031 Unified Ordering Model - Access Servic
6、e Request (UOM-ASR) Business Requirements for an Electronic Ordering Interface Is an 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
7、 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2017 by the Alliance for Telecommunications Industry Solutions, Inc. 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 pub
8、lisher. For information contact ATIS at 202-628-6380. ATIS is online at . Limited Exception for “Customized” Forms. In recognition of the business needs and processes implemented by companies throughout the industry, ATIS grants the following limited exception to the copyright policy. The forms cont
9、ained within, once “Customized,” may be reproduced, distributed and used by an individual or company provided that the following is placed on all “Customized” forms: “This form/screen is based upon the Ordering and Billing Forums (OBF) industry consensus approved guidelines, found in the Access Serv
10、ice Ordering Guidelines (ASOG) document. The ASOG may be obtained by contacting the Alliance for Telecommunications Industry Solutions (ATIS) at 1-800-387-2199 or: http:/www.atis.org/docstore/default.aspx.” ATIS-0404110-0029 UOM-ASR Volume I Issued September 23, 2016 Implemented March 18, 2017 ii Fo
11、r purposes of this limited exception, the term “Customized” means, the modification, by a company, of an ASOG form to be issued to a trading partner to make it company specific by, for example, adding a company logo, graying-out optional fields not required by that specific issuing company, and conv
12、erting into an electronic format/screen. This limited exception does not affect the ASOG document itself which remains copyrighted and may not be reproduced in whole or part. Telcordia Technologies, Inc. was formerly known as Bell Communications Research, Inc. or Bellcore. Portions of this document,
13、 previously published by Bellcore, may still reflect the former name as it was embedded in the documentation under a prior license from the owners of the BELL trademark, which license has now expired. The use of this name does not suggest that Telcordia Technologies has licensed the names BELL, Bell
14、 Communications Research, or Bellcore for new uses or that the owners of the BELL trademark sponsor, endorse or are affiliated with Telcordia Technologies or its products. Printed in the United States of America. Notice of Disclaimer and Limitation of Liability The information provided in this docum
15、ent is directed solely to professionals who have the appropriate degree of experience to understand and 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 b
16、e implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT 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
17、 OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT 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 US
18、E OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0404110-0031 UOM-ASR Volume I Issued September 22, 2017 Implemented March 17, 2018 1 Table of Contents SECTION PAGE TABLE OF CONTENTS . 1 TABLE OF FIGURES . 2 1 INTRODUCTION TO UOM 4 2 UML . 6 2.1 INTRO
19、DUCTION 6 3 UOM-ASR 6 3.1 UOM-ASR BUSINESS REQUIREMENTS PROCESS . 9 4 UOM-ASR HIGH LEVEL PROCESS OVERVIEW 10 4.1 UOM-ASR FUNCTIONAL STEPS 12 4.1.1 Description: 14 4.1.2 Process Steps (an example): 14 5 INTRODUCTION TO UOM-ASR PROCESS STEPS . 16 5.1 UOM-ASR PRE-ORDERING ACTIVITIES . 16 5.2 UOM-ASR SE
20、RVICE REQUEST PLACEMENT ACTIVITIES (SINGLE PROVIDER) . 17 5.3 UOM-ASR POST-CONFIRMATION NOTICE ACTIVITIES 18 5.3.1 Retrieve Service Request Information Activities . 19 6 UOM-ASR USE CASES: HIGH LEVEL OVERVIEW . 20 6.1 UOM-ASR ACTORS . 20 6.2 HIGH LEVEL OVERVIEW OF THE UOM-ASR PROCESS USE CASES 21 7
21、UOM-ASR PRE-ORDERING USE CASES . 22 7.1 LOCATION INQUIRY USE CASE . 23 7.2 SERVICE AVAILABILITY INQUIRY USE CASE . 24 7.3 CFA INQUIRY USE CASE . 26 7.4 ETHERNET SERVICE INQUIRY CASE 27 8 UOM-ASR SERVICE REQUEST PROCESS USE CASES 28 8.1 SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE . 31 8.2 CLARI
22、FICATION/NOTIFICATION REQUEST USE CASE 34 8.3 SERVICE REQUEST SUPPLEMENT USE CASE 35 8.4 CONFIRMATION NOTICE USE CASE 36 8.5 MEC EXCHANGE USE CASE 37 8.5.1 OEC Ready Inquiry Use Case . 39 8.5.2 OEC Ready Response Use Case . 40 8.5.3 OEC Information Inquiry Use Case . 41 8.5.4 OEC Information Respons
23、e Use Case . 42 8.5.5 ASC-EC Confirmation Notification Use Case 43 8.6 MEC ERROR NOTIFICATION USE CASE 44 8.7 MEC CANCEL NOTIFICATION USE CASES . 45 8.8 MEC DISCONNECT USE CASES . 48 8.8.1 MEC Disconnect Receipt Inquiry Use Case 48 8.8.2 MEC Disconnect Receipt Response Use Case 49 9 UOM-ASR POST-CON
24、FIRMATION USE CASES 50 9.1 JEOPARDY C/NR NOTIFICATION USE CASES 51 ATIS-0404110-0029 UOM-ASR Volume I Issued September 23, 2016 Implemented March 18, 2017 2 9.2 CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION USE CASE 53 9.3 COMPLETION NOTIFICATION USE CASE 54 9.4 DESIGN LAYOUT REPORT NOTIFICATION USE
25、 CASE 55 APPENDIX A: UML INTRODUCTION 56 A.1 SCOPE 56 A.2 USE CASE(S) 56 A.3 ACTORS 56 A.4 USE CASE . 57 A.4.1 Level of Detail . 57 A.5 USE CASE DIAGRAMS 57 A.6 USE CASE TECHNIQUES . 60 A.6.1 Identify all actors. 60 A.6.2 Identify all use cases. . 60 A.6.3 Create use case diagram. 60 A.6.4 Document
26、all primary use cases using the use case template. . 60 A.6.5 Document the use case scenarios. 61 A.6.6 Verify all use cases with users. 61 A.7 TIPS FOR ACTORS . 61 A.8 TIPS FOR PRIMARY USE CASES 61 A.9 TIPS FOR USE CASE SCENARIOS 62 A.10 TIPS FOR USE CASE RELATIONSHIPS 62 A.11 SEQUENCE DIAGRAMS . 6
27、2 A.12 STATE DIAGRAMS 63 A.13 ACTIVITY DIAGRAMS 64 A.13.1 Uses for Activity Diagrams . 65 A.13.2 Activity Diagram Technique 65 APPENDIX B: UOM-ASR DATA DICTIONARY . 68 APPENDIX B.1: UOM VALIDATION AND TRANSPORT DATA DICTIONARY . 106 APPENDIX C: UOM-ASR FUNCTIONAL DATA MATRIX . 107 APPENDIX D: UOM-AS
28、R FATAL ERROR FUNCTIONAL DATA MATRIX 127 APPENDIX E: UNIFIED ORDERING - ASR SERVICE PACKAGES . 129 10 BIBLIOGRAPHY 139 Table of Figures FIGURE 1 UOM-ASR PROCESS AND DOCUMENT DEVELOPMENT 5 FIGURE 2 ACCESS ORDERING RELATIONSHIPS AND DELIVERABLES . 7 FIGURE 3 UOM-ASR LOGICAL STAGES . 10 FIGURE 4 UOM-AS
29、R BUSINESS FUNCTIONS . 12 FIGURE 5 UOM-ASR PRE-ORDERING ACTIVITIES 16 FIGURE 6 UOM-ASR SERVICE REQUEST PLACEMENT ACTIVITIES 17 FIGURE 7 UOM-ASR POST- CONFIRMATION ACTIVITIES 18 FIGURE 8 UOM-ASR CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION ACTIVITIES 19 FIGURE 9 UOM-ASR PROCESS BUSINESS REQUIREMENT
30、USE CASES . 21 FIGURE 10 UOM-ASR PRE-ORDERING BUSINESS REQUIREMENT USE CASES 22 FIGURE 11 UOM-ASR PERFORM LOCATION INQUIRY USE CASE 23 FIGURE 12 UOM-ASR PERFORM SERVICE AVAILABILITY INQUIRY USE CASE 25 FIGURE 13 UOM-ASR PERFORM CFA INQUIRY USE CASE 26 FIGURE 14 UOM-ASR ETHERNET SERVICE INQUIRY USE C
31、ASE . 27 FIGURE 15 UOM-ASR SERVICE REQUEST PROCESS BUSINESS REQUIREMENT USE CASES 30 ATIS-0404110-0029 UOM-ASR Volume I Issued September 23, 2016 Implemented March 18, 2017 3 FIGURE 16 UOM-ASR PERFORM SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE 32 FIGURE 17 UOM-ASR PERFORM FATAL ERROR PROCESSI
32、NG USE CASE . 33 FIGURE 19 UOM-ASR PERFORM CLARIFICATION/NOTIFICATION REQUEST USE CASE 34 FIGURE 20 UOM-ASR PERFORM SERVICE REQUEST SUPPLEMENT USE CASE . 35 FIGURE 21 UOM-ASR PERFORM CONFIRMATION NOTICE USE CASE . 36 FIGURE 22 UOM-ASR PERFORM MEC EXCHANGE USE CASE . 37 FIGURE 23 UOM-ASR PERFORM OEC
33、READY INQUIRY USE CASE 39 FIGURE 24 UOM-ASR PERFORM OEC READY RESPONSE USE CASE 40 FIGURE 25 UOM-ASR PERFORM OEC INFORMATION INQUIRY USE CASE 41 FIGURE 26 UOM-ASR PERFORM OEC INFORMATION RESPONSE USE CASE 42 FIGURE 27 UOM-ASR PERFORM ASC-EC CONFIRMATION NOTIFICATION USE CASE . 43 FIGURE 28 UOM-ASR P
34、ERFORM MEC ERROR NOTIFICATION USE CASE . 44 FIGURE 29 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (CUSTOMER INITIATED) 45 FIGURE 30 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (ASC-EC INITIATED) 46 FIGURE 31 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (OEC INITIATED) . 47 FIGURE 32 UO
35、M-ASR PERFORM MEC DISCONNECT RECEIPT INQUIRY USE CASE . 48 FIGURE 33 UOM-ASR PERFORM MEC DISCONNECT RECEIPT RESPONSE USE CASE. 49 FIGURE 34 UOM-ASR POST-CONFIRMATION BUSINESS REQUIREMENTS USE CASE . 50 FIGURE 35 UOM-ASR PERFORM JEOPARDY C/NR NOTIFICATION USE CASE . 51 FIGURE 36 UOM-ASR PERFORM JEOPA
36、RDY C/NR NOTIFICATION CLEAR USE CASE 52 FIGURE 37 UOM-ASR PERFORM CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION USE CASE . 53 FIGURE 38 UOM-ASR PERFORM COMPLETION USE CASE . 54 FIGURE 39 UOM-ASR DESIGN LAYOUT REPORT NOTIFICATION USE CASE 55 FIGURE 40 USE CASE DIAGRAM 58 FIGURE 41 USE CASE EXAMPLE 59
37、 FIGURE 42 SEQUENCE DIAGRAM . 63 FIGURE 43 STATE DIAGRAM 64 FIGURE 44 ACTIVITY DIAGRAM NO BRANCHING . 65 FIGURE 45 ACTIVITY DIAGRAM WITH BRANCHING 66 FIGURE 46 ACTIVITY DIAGRAM WITH DECISION BOX 66 FIGURE 47 ACTIVITY DIAGRAM CONCURRENT PATHS 67 ATIS-0404110-0029 UOM-ASR Volume I Issued September 23,
38、 2016 Implemented March 18, 2017 4 1 Introduction to UOM 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 implementation. Logically, the
39、se components are defined within the UOM in four volumes. UOM-ASR Volume I Provides an explanation of the business requirements and a conceptual overview of the solution. This conceptual overview is high-level. It defines “what” the user initially sees as the problem and “how” the user sees the busi
40、ness solution. UOM Volume II Analysis may be seen as using the requirements and developing a more detailed understanding of the scope. In effect, this step defines “what” the proposed technical resolution needs to support. It is a logical view of the proposed solution, which meets the business need,
41、 and it is not based on any particular software protocol. UOM Volume III The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the selected implementation technology. Design focuses on “how” the implementation shall resolv
42、e the business requirements. It may be necessary to repeat the Design Phase if more than one implementation technology is selected. UOM Volume IV Resolves any outstanding implementation specifications that must be addressed before the system specifications can be realized using the selected implemen
43、tation technology. As with the Design Phase, the Implementation Phase may also have to be repeated in order to provide support for multiple technologies. ATIS-0404110-0029 UOM-ASR Volume I Issued September 23, 2016 Implemented March 18, 2017 5 Unified Model1. Business Requirements:-High Level Use Ca
44、ses-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 Specific- Interface S
45、pecification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document DevelopmentFigure 1 UOM-ASR Process and Document Development ATIS-0404110-
46、0029 UOM-ASR Volume I Issued September 23, 2016 Implemented March 18, 2017 6 2 UML 2.1 Introduction By definition a model is an abstraction. The Unified Modeling Language (UML) is the “visual” notation used within UOM Volume I. The UML supports several constructs that provide a consistent notation u
47、sed to describe the UOM. The use of UML is for descriptive purposes. In some instances this Volume may not strictly adhere to existing UML specifications. The UML is graphical in nature and is sometimes referred to as a visual specification language. The use of graphics helps in a.) abstracting desi
48、gn features and b.) showing the relationships between design elements. The UML should be used to document all the relevant relationships that are important in describing this abstract view. The constructs used in Volume I are: Use Cases that define the users view of the system Activity Diagrams that
49、 can be used to describe process flows 3 UOM-ASR The purpose of this document is to clearly define the business requirements for the electronic ordering of Access Service Requests (ASRs), including the exchange of data between providers in support of jointly provided (Meet Point) services, and the transmitting of Design Layout Report (DLR) information. As such, this document is referred to as UOM-ASR. It is the first volume, in the set of four, defined within the UOM process
