1、 ATIS-0404110-0027 Unified Ordering Model - Access Service Request (UOM-ASR) Volume I Business Requirements For An Electronic Ordering Interface ATIS-0404110-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016 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-0027 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 2015 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-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016 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. UOM-ASR VOLUME I ASOG V52 SYNOPSIS OF CHANGES Page 1 of 3 UOM-ASR VOLUME I ASOG V52 CHANGES - ISSUES INCLUDED IN THIS SYNOPSIS ISSUE NUMBER DESCRIPTION 3541 UOM: Add LOA to CFA pre-order validation for UOM U
19、OM-ASR VOLUME I ASOG V52 SYNOPSIS OF CHANGES Page 2 of 3 The following table depicts the type of change category definitions: TYPE OF CHANGE = CATEGORY DEFINITIONS NEW = Adding a new field REM = Removing an existing field FN = Field/Tag name change (e.g., EXEMPT REASON changed to ER) FORMAT = Field
20、format change (e.g., moved to another section of the form, etc.) DEF = Definition change DEFN = Definition notes addition, change, deletion VE = Valid entries addition, change, deletion VEN = Valid entry notes addition, change, deletion USE = Usage statement change USEN = Usage notes addition, chang
21、e, deletion DC = Data characteristics change (e.g., change from numeric to alpha/numeric) DCL = Data characteristics length change DCN = Data characteristics note addition, change, deletion EX = Example addition, change, deletion EXN = Example notes addition, change, deletion FORM = Changes made to
22、the ASR forms (i.e., additions, rearrangements, field length changes or deletions of fields) GLOSSARY = Identifies changes within the glossary sections (i.e., additions or deletions of fields) TEXT = Identifies changes within the text of a section (i.e., additions or deletions of fields) UOM-ASR VOL
23、UME I ASOG V52 SYNOPSIS OF CHANGES Page 3 of 3 UOM-ASR VOLUME I SYNOPSIS OF CHANGES FOR ASOG V52 PRAC # ISSUE # Field/Section Type Of Change Description of Change Field Length N/A 3541 Figure 17 VE Updated PreCondition #2 N/A 3541 Appendix B NEW Added LOA_CCNA to Appendix B 3 N/A 3541 Appendix B NEW
24、 Added LOAI to Appendix B 1 N/A 3541 Appendix C NEW Added LOA_CCNA in Connecting Facility Assignment Inquiry section 3 N/A 3541 Appendix C NEW Added LOAI in Connecting Facility Assignment Inquiry section 1 NOTES: ATIS-0404110-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016
25、 1 Table of Contents SECTION PAGE TABLE OF CONTENTS . 1 TABLE OF FIGURES . 2 1 INTRODUCTION TO UOM 4 2 UML . 6 2.1 INTRODUCTION 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 Ste
26、ps (an example): 14 5 INTRODUCTION TO UOM-ASR PROCESS STEPS . 15 5.1 UOM-ASR PRE-ORDERING ACTIVITIES . 15 5.2 UOM-ASR SERVICE REQUEST PLACEMENT ACTIVITIES (SINGLE PROVIDER) . 17 5.3 UOM-ASR POST-CONFIRMATION NOTICE ACTIVITIES 18 5.3.1 Provider Jeopardy Activities 19 5.3.2 Customer Jeopardy Activitie
27、s 20 5.3.3 Retrieve Service Request Information Activities . 21 5.3.4 Completion Notification Activities 23 6 UOM-ASR USE CASES: HIGH LEVEL OVERVIEW . 24 6.1 UOM-ASR ACTORS . 24 6.2 HIGH LEVEL OVERVIEW OF THE UOM-ASR PROCESS USE CASES 25 7 UOM-ASR PRE-ORDERING USE CASES . 26 7.1 LOCATION INQUIRY USE
28、 CASE . 27 7.2 SERVICE AVAILABILITY INQUIRY USE CASE . 28 7.3 CFA INQUIRY USE CASE . 30 8 UOM-ASR SERVICE REQUEST PROCESS USE CASES 31 8.1 SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE 34 8.2 CLARIFICATION/NOTIFICATION REQUEST USE CASE 38 8.3 SERVICE REQUEST SUPPLEMENT USE CASE 40 8.4 CONFIRMATI
29、ON NOTICE USE CASE 41 8.5 MEC EXCHANGE USE CASE 42 8.5.1 OEC Ready Inquiry Use Case . 44 8.5.2 OEC Ready Response Use Case . 45 8.5.3 OEC Information Inquiry Use Case . 46 8.5.4 OEC Information Response Use Case . 47 8.5.5 ASC-EC Confirmation Notification Use Case 48 8.6 MEC ERROR NOTIFICATION USE C
30、ASE 49 8.7 MEC CANCEL NOTIFICATION USE CASES . 50 8.8 MEC DISCONNECT USE CASES . 53 8.8.1 MEC Disconnect Receipt Inquiry Use Case 53 8.8.2 MEC Disconnect Receipt Response Use Case 54 ATIS-0404110-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016 2 9 UOM-ASR POST-CONFIRMATION
31、 USE CASES 55 9.1 JEOPARDY STATUS USE CASES . 56 9.2 RETRIEVE SERVICE REQUEST INFORMATION USE CASES 59 9.3 COMPLETION NOTIFICATION USE CASE 61 9.4 DESIGN LAYOUT REPORT USE CASE 62 APPENDIX A: UML INTRODUCTION 63 A.1 SCOPE 63 A.2 USE CASE(S). 63 A.3 ACTORS 63 A.4 USE CASE . 64 A.4.1 Level of Detail .
32、 64 A.5 USE CASE DIAGRAMS 64 A.6 USE CASE TECHNIQUES . 67 A.6.1 Identify all actors. 67 A.6.2 Identify all use cases. . 67 A.6.3 Create use case diagram. 67 A.6.4 Document all primary use cases using the use case template. . 67 A.6.5 Document the use case scenarios. 68 A.6.6 Verify all use cases wit
33、h users. 68 A.7 TIPS FOR ACTORS . 68 A.8 TIPS FOR PRIMARY USE CASES 68 A.9 TIPS FOR USE CASE SCENARIOS 69 A.10 TIPS FOR USE CASE RELATIONSHIPS 69 A.11 SEQUENCE DIAGRAMS . 69 A.12 STATE DIAGRAMS 70 A.13 ACTIVITY DIAGRAMS 71 A.13.1 Uses for Activity Diagrams . 72 A.13.2 Activity Diagram Technique 72 A
34、PPENDIX B: UOM-ASR DATA DICTIONARY . 75 APPENDIX C: UOM-ASR FUNCTIONAL DATA MATRIX . 99 APPENDIX D: UOM-ASR FATAL ERROR FUNCTIONAL DATA MATRIX 123 APPENDIX E: UNIFIED ORDERING - ASR SERVICE PACKAGES . 130 10 BIBLIOGRAPHY 141 Table of Figures FIGURE 1 UOM-ASR PROCESS AND DOCUMENT DEVELOPMENT 5 FIGURE
35、 2 ACCESS ORDERING RELATIONSHIPS AND DELIVERABLES . 8 FIGURE 3 UOM-ASR LOGICAL STAGES . 10 FIGURE 4 UOM-ASR 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
36、PROVIDER JEOPARDY ACTIVITIES . 19 FIGURE 9 UOM-ASR CUSTOMER JEOPARDY ACTIVITIES 20 FIGURE 10 UOM-ASR CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION ACTIVITIES 21 FIGURE 11 UOM-ASR PROVIDER RETRIEVE SERVICE REQUEST INFORMATION ACTIVITIES 22 FIGURE 12 UOM-ASR COMPLETION NOTIFICATION ACTIVITIES 23 FIGUR
37、E 13 UOM-ASR PROCESS BUSINESS REQUIREMENT USE CASES 25 FIGURE 14 UOM-ASR PRE-ORDERING BUSINESS REQUIREMENT USE CASES 26 ATIS-0404110-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016 3 FIGURE 15 UOM-ASR PERFORM LOCATION INQUIRY USE CASE 27 FIGURE 16 UOM-ASR PERFORM SERVICE A
38、VAILABILITY INQUIRY USE CASE 29 FIGURE 17 UOM-ASR PERFORM CFA INQUIRY USE CASE 30 FIGURE 18 UOM-ASR SERVICE REQUEST PROCESS BUSINESS REQUIREMENT USE CASES 33 FIGURE 19 UOM-ASR PERFORM SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE 35 FIGURE 20 UOM-ASR PERFORM FATAL ERROR PROCESSING USE CASE. 36 F
39、IGURE 21 UOM-ASR PERFORM NON-FATAL ERROR PROCESSING USE CASE 37 FIGURE 22 UOM-ASR PERFORM CLARIFICATION/NOTIFICATION REQUEST USE CASE 39 FIGURE 23 UOM-ASR PERFORM SERVICE REQUEST SUPPLEMENT USE CASE . 40 FIGURE 24 UOM-ASR PERFORM CONFIRMATION NOTICE USE CASE . 41 FIGURE 25 UOM-ASR PERFORM MEC EXCHAN
40、GE USE CASE . 42 FIGURE 26 UOM-ASR PERFORM MEC EXCHANGE USE CASE (CONTINUED) 43 FIGURE 27 UOM-ASR PERFORM OEC READY INQUIRY USE CASE 44 FIGURE 28 UOM-ASR PERFORM OEC READY RESPONSE USE CASE 45 FIGURE 29 UOM-ASR PERFORM OEC INFORMATION INQUIRY USE CASE 46 FIGURE 30 UOM-ASR PERFORM OEC INFORMATION RES
41、PONSE USE CASE 47 FIGURE 31 UOM-ASR PERFORM ASC-EC CONFIRMATION NOTIFICATION USE CASE . 48 FIGURE 32 UOM-ASR PERFORM MEC ERROR NOTIFICATION USE CASE . 49 FIGURE 33 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (CUSTOMER INITIATED) 50 FIGURE 34 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (ASC
42、-EC INITIATED) 51 FIGURE 35 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (OEC INITIATED) . 52 FIGURE 36 UOM-ASR PERFORM MEC DISCONNECT RECEIPT INQUIRY USE CASE . 53 FIGURE 37 UOM-ASR PERFORM MEC DISCONNECT RECEIPT RESPONSE USE CASE 54 FIGURE 38 UOM-ASR POST-CONFIRMATION BUSINESS REQUIREMENTS USE
43、 CASE . 55 FIGURE 39 UOM-ASR PERFORM PROVIDER JEOPARDY STATUS USE CASE . 56 FIGURE 40 UOM-ASR PERFORM PROVIDER JEOPARDY CLEAR USE CASE . 57 FIGURE 41 UOM-ASR PERFORM CUSTOMER JEOPARDY STATUS USE CASE 57 FIGURE 42 UOM-ASR PERFORM CUSTOMER JEOPARDY STATUS CLEAR . 58 FIGURE 43 UOM-ASR PERFORM CUSTOMER
44、JEOPARDY STATUS CLEAR . 58 FIGURE 44 UOM-ASR PERFORM CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION USE CASE . 59 FIGURE 45 UOM-ASR PERFORM PROVIDER RETRIEVE SERVICE REQUEST INFORMATION USE CASE 60 FIGURE 46 UOM-ASR PERFORM COMPLETION USE CASE . 61 FIGURE 47 UOM-ASR DESIGN LAYOUT REPORT USE CASE . 62
45、 FIGURE 48 USE CASE DIAGRAM 65 FIGURE 49 USE CASE EXAMPLE 66 FIGURE 50 SEQUENCE DIAGRAM . 70 FIGURE 51 STATE DIAGRAM 71 FIGURE 52 ACTIVITY DIAGRAM NO BRANCHING . 72 FIGURE 53 ACTIVITY DIAGRAM WITH BRANCHING 73 FIGURE 54 ACTIVITY DIAGRAM WITH DECISION BOX 73 FIGURE 55 ACTIVITY DIAGRAM CONCURRENT PATH
46、S 74 ATIS-0404110-0027 UOM-ASR Volume I Issued September 25, 2015 Implemented March 19, 2016 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 requi
47、rements, analysis, design and implementation. Logically, these 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 in
48、itially sees as the problem and “how” the user sees the business 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 v
49、iew of the proposed solution, which meets the business need, 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 resolve the business requirements. It may be necessary to repeat the Design Phase if more than one implementa
