1、 ATIS-0404110-0032 Unified Ordering Model - Access Service Request (UOM-ASR) Volume I Business Requirements For An Electronic Ordering Interface ATIS-0404110-0032 UOM-ASR Volume I Issued March 23, 2018 Implemented September 15, 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-0032 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 2018 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-0032 UOM-ASR Volume I Issued March 23, 2018 Implemented September 15, 2018 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 V57 SYNOPSIS OF CHANGES Page 1 of 4 UOM-ASR VOLUME I ASOG V57 CHANGES - ISSUES INCLUDED IN THIS SYNOPSIS ISSUE NUMBER DESCRIPTION 3602 ASOG: Provider Test Acceptance Notification 3609 A
19、SOG: Modify PTA (020) practice to support new fields (ASR NO, PTA VER, VC NUM) and clarify existing assumptions ISSUES ASSOCIATED WITH ASOG V57 ISSUE NUMBER DESCRIPTION 3575 (withdrawn) ASOG: Define Service Operations, Administration and Maintenance (SOAM) elements within the service ordering proces
20、s 3604 ASOG: Field modification based on RTR update within ASOG 56 3605 ASOG: SR field modification for new values 3606 ASOG: Modify the SALI Form (Practice 015) to add Latitude and Longitude 3610 ASOG: Update fields on Trunking Form to support minimal disconnect principals UOM-ASR VOLUME I ASOG V57
21、 SYNOPSIS OF CHANGES Page 2 of 4 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 format change (e.g., mov
22、ed 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, change, deletion DC = Data ch
23、aracteristics 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 the ASR forms (i.e., add
24、itions, 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 VOLUME I ASOG V57 SYNOPSIS
25、OF CHANGES Page 3 of 4 UOM-ASR VOLUME I SYNOPSIS OF CHANGES FOR ASOG V57 PRAC # ISSUE # Field/Section Type Of Change Description of Change Field Length n/a 3609 4 UOM-ASR High Level Process Overview TEXT Within the third bullet, Post-Confirmation, spelled out Design Layout Record Notification and in
26、serted Provider Test Acceptance Notification (PTA). n/a 3602 4.1 UOM-ASR Functional Steps FIG 4 Updated the UOM-ASR Business Functions diagram (Figure 4) to include Provider Test Acceptance under Post-Confirmation functions. n/a 3602 4.1.1 Description TEXT Spelled out “design layout record” and adde
27、d provider test acceptance notification to the Description. n/a 3602 4.1.2 Process Steps TEXT Updated the Process Steps to include provider test acceptance. n/a 3602 5.3 UOM-ASR Post-Confirmation Notice Activities TEXT Updated text to include PTA Notification. n/a 3602 5.3 UOM-ASR Post-Confirmation
28、Notice Activities FIG 7 Updated the UOM-ASR Post-Confirmation Activities diagram to include PTA Notification activity. n/a 3609 5.3 UOM-ASR Post-Confirmation Notice Activities FIG 7 Within the UOM-ASR Post-Confirmation Activities diagram, modified decision “Error Condition Detected” to activity “Ini
29、tiate C/NR process”. Modified subsequent decision to “Service Request Completed”. n/a 3609 9 UOM-ASR Post-Confirmation Use Cases TEXT Updated text to capitalize “Confirmation” and include PTA Notification. n/a 3602 9 UOM-ASR Post-Confirmation Use Cases TEXT Updated text to reference PTA Use Case. n/
30、a 3602 9 UOM-ASR Post-Confirmation Use Cases FIG 33 Updated UOM-ASR Post-Confirmation Business Requirements Use Case diagram to include PTA Notification. n/a 3602 9.3 PTA Notification Use Case NEW Added new section 9.3, PTA Notification Use Case and new Figure 37 UOM-ASR PTA Notification Use. Renumb
31、ered existing sections and figures accordingly. UOM-ASR VOLUME I ASOG V57 SYNOPSIS OF CHANGES Page 4 of 4 UOM-ASR VOLUME I SYNOPSIS OF CHANGES FOR ASOG V57 PRAC # ISSUE # Field/Section Type Of Change Description of Change Field Length NOTES: The following non-substantive global changes were made to
32、the document: Change all ASOG 56 to ASOG 57; Version 56 to Version 57; Issue 31 to Issue 32 Change ATIS document number from ATIS-0404110-0031 to ATIS-0404110-0032 Update Issue Date Update all Figure numbers and references as applicable ATIS-0404110-0032 UOM-ASR Volume I Issued March 23, 2018 Implem
33、ented September 15, 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 INTRODUCTION 6 3 UOM-ASR 6 3.1 UOM-ASR BUSINESS REQUIREMENTS PROCESS . 8 4 UOM-ASR HIGH LEVEL PROCESS OVERVIEW 9 4.1 UOM-ASR FUNCTIONAL STEPS 11 4.1.1 Descriptio
34、n: 12 4.1.2 Process Steps (an example): 12 5 INTRODUCTION TO UOM-ASR PROCESS STEPS . 14 5.1 UOM-ASR PRE-ORDERING ACTIVITIES . 14 5.2 UOM-ASR SERVICE REQUEST PLACEMENT ACTIVITIES (SINGLE PROVIDER) . 15 5.3 UOM-ASR POST-CONFIRMATION NOTICE ACTIVITIES 16 5.3.1 Retrieve Service Request Information Activ
35、ities . 18 6 UOM-ASR USE CASES: HIGH LEVEL OVERVIEW . 19 6.1 UOM-ASR ACTORS . 19 6.2 HIGH LEVEL OVERVIEW OF THE UOM-ASR PROCESS USE CASES 20 7 UOM-ASR PRE-ORDERING USE CASES . 21 7.1 LOCATION INQUIRY USE CASE . 22 7.2 SERVICE AVAILABILITY INQUIRY USE CASE . 23 7.3 CFA INQUIRY USE CASE . 25 7.4 ETHER
36、NET SERVICE INQUIRY CASE 26 8 UOM-ASR SERVICE REQUEST PROCESS USE CASES 27 8.1 SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE 30 8.2 CLARIFICATION/NOTIFICATION REQUEST USE CASE 33 8.3 SERVICE REQUEST SUPPLEMENT USE CASE 34 8.4 CONFIRMATION NOTICE USE CASE 35 8.5 MEC EXCHANGE USE CASE 36 8.5.1 OEC
37、 Ready Inquiry Use Case . 38 8.5.2 OEC Ready Response Use Case . 39 8.5.3 OEC Information Inquiry Use Case . 40 8.5.4 OEC Information Response Use Case . 41 8.5.5 ASC-EC Confirmation Notification Use Case 42 8.6 MEC ERROR NOTIFICATION USE CASE 43 8.7 MEC CANCEL NOTIFICATION USE CASES . 44 8.8 MEC DI
38、SCONNECT USE CASES . 47 8.8.1 MEC Disconnect Receipt Inquiry Use Case 47 8.8.2 MEC Disconnect Receipt Response Use Case 48 9 UOM-ASR POST-CONFIRMATION USE CASES 49 9.1 JEOPARDY C/NR NOTIFICATION USE CASES 50 ATIS-0404110-0032 UOM-ASR Volume I Issued March 23, 2018 Implemented September 15, 2018 2 9.
39、2 CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION USE CASE 52 9.3 PTA NOTIFICATION USE CASE . 53 9.4 COMPLETION NOTIFICATION USE CASE 54 9.5 DESIGN LAYOUT REPORT NOTIFICATION USE 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 Det
40、ail . 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 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 case
41、s 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 . 62 A.12 STATE DIAGRAMS 63 A.13 ACTIVITY DIAGRAMS 64 A.13.1 Uses for Activity Diagrams . 65 A.13.2 Activity Diagram Technique
42、 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-ASR FATAL ERROR FUNCTIONAL DATA MATRIX 127 APPENDIX E: UNIFIED ORDERING - ASR SERVICE PACKAGES . 129 10 BIBLIOGRAPHY 139 Tabl
43、e 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 9 FIGURE 4 UOM-ASR BUSINESS FUNCTIONS . 11 FIGURE 5 UOM-ASR PRE-ORDERING ACTIVITIES 14 FIGURE 6 UOM-ASR SERVICE REQUEST PLACEMENT ACTIVITIES . 15
44、 FIGURE 7 UOM-ASR POST- CONFIRMATION ACTIVITIES 17 FIGURE 8 UOM-ASR CUSTOMER RETRIEVE SERVICE REQUEST INFORMATION ACTIVITIES . 18 FIGURE 9 UOM-ASR PROCESS BUSINESS REQUIREMENT USE CASES 20 FIGURE 10 UOM-ASR PRE-ORDERING BUSINESS REQUIREMENT USE CASES 21 FIGURE 11 UOM-ASR PERFORM LOCATION INQUIRY USE
45、 CASE 22 FIGURE 12 UOM-ASR PERFORM SERVICE AVAILABILITY INQUIRY USE CASE . 24 FIGURE 13 UOM-ASR PERFORM CFA INQUIRY USE CASE . 25 FIGURE 14 UOM-ASR ETHERNET SERVICE INQUIRY USE CASE . 26 ATIS-0404110-0032 UOM-ASR Volume I Issued March 23, 2018 Implemented September 15, 2018 3 FIGURE 15 UOM-ASR SERVI
46、CE REQUEST PROCESS BUSINESS REQUIREMENT USE CASES 29 FIGURE 16 UOM-ASR PERFORM SERVICE REQUEST PLACEMENT/PRE-VALIDATION USE CASE 31 FIGURE 17 UOM-ASR PERFORM FATAL ERROR PROCESSING USE CASE 32 FIGURE 18 UOM-ASR PERFORM CLARIFICATION/NOTIFICATION REQUEST USE CASE 33 FIGURE 19 UOM-ASR PERFORM SERVICE
47、REQUEST SUPPLEMENT USE CASE 34 FIGURE 20 UOM-ASR PERFORM CONFIRMATION NOTICE USE CASE . 35 FIGURE 21 UOM-ASR PERFORM MEC EXCHANGE USE CASE . 36 FIGURE 22 UOM-ASR PERFORM OEC READY INQUIRY USE CASE 38 FIGURE 23 UOM-ASR PERFORM OEC READY RESPONSE USE CASE . 39 FIGURE 24 UOM-ASR PERFORM OEC INFORMATION
48、 INQUIRY USE CASE . 40 FIGURE 25 UOM-ASR PERFORM OEC INFORMATION RESPONSE USE CASE 41 FIGURE 26 UOM-ASR PERFORM ASC-EC CONFIRMATION NOTIFICATION USE CASE . 42 FIGURE 27 UOM-ASR PERFORM MEC ERROR NOTIFICATION USE CASE. 43 FIGURE 28 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (CUSTOMER INITIATED)
49、 44 FIGURE 29 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (ASC-EC INITIATED) 45 FIGURE 30 UOM-ASR PERFORM MEC CANCEL NOTIFICATION USE CASE (OEC INITIATED) 46 FIGURE 31 UOM-ASR PERFORM MEC DISCONNECT RECEIPT INQUIRY USE CASE 47 FIGURE 32 UOM-ASR PERFORM MEC DISCONNECT RECEIPT RESPONSE USE CASE . 48 FIGURE 33 UOM-ASR POST-CONFIRMATION BUSINESS REQUIREMENTS USE CASE 49 FIGURE 34 UOM-ASR PERFORM JEOPARDY C/NR NOTIFICATION USE CASE 50 FIGURE 35 UOM-ASR PERFORM JEOPARDY C/NR NOTIFICATION CLEAR U
