ATIS 0410002-0021-2012 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) (Version 46).pdf

《ATIS 0410002-0021-2012 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) (Version 46).pdf》由会员分享，可在线阅读，更多相关《ATIS 0410002-0021-2012 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) (Version 46).pdf（127页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0410002-0021 Unified Ordering Model (UOM) Volume II - Analysis For Access Service Ordering Guidelines (ASOG) Version 46 ATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 Page 2 As a leading technology and solutions development organization, ATIS brings togethe

2、r the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operation

3、s and more. These priorities follow a fast-track development lifecyclefrom design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits and interoperability testing. ATIS is accredited by the American National Standards Institute

4、 (ANSI). ATIS is the North American Organizational Partner for the 3rdGeneration Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American T

5、elecommunication Commission (CITEL). For more information, visit www.atis.org. ATIS 0410002-0021 Unified Ordering Model (UOM) Volume II - Analysis Is an ATIS standard developed by the Ordering Solutions Committee/Access Service Ordering Subcommittee under the ATIS Ordering and Billing Forum (OBF). P

6、ublished by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2012 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or o

7、therwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals w

8、ho 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 be implied. ATIS-0410002-0021 UOM-ASR Volu

9、me II Issued September 21, 2012 Issue 21 for ASOG v46 Page 3 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

10、FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT 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 CONSEQUENT

11、IAL 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-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 Page 4 Change History Issue # Document Release Description of Changes 21

12、R1Initial version for ASR 46 20 R1 Initial version for ASR 45 19 R1Initial version for ASR 44 18 R1 Initial version for ASR 43 17 R1Initial version for ASR 42 16 R1 Initial version for ASR 41 15 R1Initial version for ASR 40 14 R1 Initial version for ASR 39 13 R1Initial version for ASR 38 12 R1 Initi

13、al version for ASR 37 11 R1Initial 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 Initial version for ASR 31 5 R1 Initial version for ASR 30 4 R1 Initial version for ASR 29 3 R1 Initial version

14、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 Volume II for ASR 26 ATIS-0410002-0021

15、 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 Page 5 Table of Contents Change History . 4 Table of Contents . 5 1. UOM Documentation 8 2. Introduction to UOM-ASR Volume II . 11 2.1. Intended Audience . 11 2.2. Purpose . 11 2.3. Scope . 11 2.4. Development Note 12 3. Overview of

16、UOM-ASR Volume II 13 3.1. Assumptions of this Document . 13 3.2. Structure of Document 13 3.3. Overall Process Description 13 3.4. UOM-ASR High Level Process Overview . 14 4. UOM Requirements Summary . 16 4.1. Business Requirements . 16 4.2. System Requirements . 16 4.3. Security Requirements: . 16

17、4.4. Messaging Requirements: . 16 4.5. User Profile Requirements 19 4.6. Reporting Requirements 19 5. Use Case Realizations using Sequence Diagrams . 20 5.1. UOM Pre-Order Use Cases . 20 5.1.1. Location Inquiry . 21 5.1.2. Service Availability Inquiry . 23 5.1.3. CFA Inquiry . 25 5.2. UOM Service Re

18、quest Cases 27 5.2.1. Service Request Placement/Pre-Validation . 28 5.2.2. Service Request Placement/Pre-Validation Reject Alternative 30 5.2.3. Fatal Error Processing 32 5.2.4. Non-Fatal Error Processing 34 5.2.5. Clarification/Notification Request 36 5.2.6. UOM Service Request Supplement Process 3

19、9 5.2.6.1. Service Request Placement Reject Alternative . 41 5.2.7. Confirmation Notice Sequence Diagrams 42 5.2.8. Confirmation Notice (CN) . 42 5.2.9. Confirmation Notice (PIA) 44 5.3. UOM Post-Confirmation Use Cases . 45 5.3.1. Jeopardy Status . 46 5.3.2. Provider Initiated Jeopardy 47 5.3.3. Cus

20、tomer Initiated Jeopardy . 49 5.3.4. Retrieve Service Request Information . 50 5.3.5. Retrieve Service Request Information by Customer . 51 5.3.6. Retrieve Service Request Information by Provider 51 5.3.7. Completion Notification . 52 5.3.8. Design Notification 53 6. Information Model . 55 6.1. UOM-

21、ASR High Level View . 56 6.2. Inquiry Request Classes 57 6.2.1. ASR Inquiry Request Classes . 58 6.2.1.1. Location Inquiry . 59 6.2.1.2. Service Availability Inquiry . 60 6.2.1.3. CFA Inquiry . 61 ATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 Page 6 6.2.1.4. Ord

22、er Information Inquiry 62 6.3. Inquiry Response Classes . 63 6.3.1. ASR Inquiry Response Classes 63 6.3.1.1. Location Results . 64 6.3.1.2. Service Availability Results . 65 6.3.1.3. CFA Results . 66 6.3.1.4. Order Information Results 67 6.4. Service Request Classes 68 6.4.1. ASR Service Request Cla

23、sses . 68 6.4.1.1. ASR Service Type Classes . 68 6.4.1.1.1. Transport Service . 70 6.4.1.1.2. Transport Ethernet Virtual Connection Service 71 6.4.1.1.3. Transport Virtual Connection Service . 72 6.4.1.1.4. Standalone Ethernet Virtual Connection Service 73 6.4.1.1.5. End User Special Access Service

24、74 6.4.1.1.6. End User Special Access Ethernet Virtual Connection Service 75 6.4.1.1.7. End User Virtual Connection Service 76 6.4.1.1.8. Feature Group A Service . 77 6.4.1.1.9. Message Trunk Service 78 6.4.1.1.10. Ring Service . 79 6.4.1.1.11. SS7 Link Service 80 6.4.1.1.12. WATS Service 81 6.4.1.1

25、.13. Standalone Trunking Service . 82 6.4.1.1.14. Cancel Service . 83 6.4.1.2. ASR Basic Forms . 84 6.4.1.2.1. Administrative (ASR) Form . 84 6.4.1.2.2. End User Special Access (EUSA) Form . 86 6.4.1.2.3. Feature Group A (FGA) Form . 87 6.4.1.2.4. Ring Form . 88 6.4.1.2.5. Transport Form 89 6.4.1.2.

26、6. Trunking Form 91 6.4.1.2.7. WATS Access Line (WAL) Form 92 6.4.1.3. ASR Additional Forms 93 6.4.1.3.1. Additional Circuit Information (ACI) Form 93 6.4.1.3.2. Additional Ring Information (ARI) Form . 95 6.4.1.3.3. Enhanced Customer Interface (ECI) Form . 96 6.4.1.3.4. End Office Detail (EOD) Form

27、 98 6.4.1.3.5. Multipoint Service Legs (MSL) Form 99 6.4.1.3.6. Multiple Exchange Company (MULTI-EC) Form 100 6.4.1.3.7. Network Assignment Information (NAI) Form . 101 6.4.1.3.8. Service Address Location Information (SALI) Form 102 6.4.1.3.9. Translation Questionnaire (TQ) Form . 103 6.4.1.3.10. Vi

28、rtual Connection (VC) Form . 104 6.4.1.3.11. Ethernet Virtual Connection (EVC) Form 105 6.4.1.3.12. Ports Configuration (PC) Form . 106 6.4.1.3.13. Virtual Concatenation (VCAT) Form 107 6.4.2. Service Response Classes . 108 6.4.2.1. ASR Service Response Classes 109 6.4.3. Notification Classes . 110

29、6.4.3.1. ASR Notification Classes . 111 6.4.3.1.1. Error Clarification Notification 112 6.4.3.1.2. Confirmation Notification 113 6.4.3.1.3. Design (DLR) Notification 114 6.4.3.1.4. BAN Correction Notification . 115 6.4.3.1.5. Jeopardy Notification 116 ATIS-0410002-0021 UOM-ASR Volume II Issued Septe

30、mber 21, 2012 Issue 21 for ASOG v46 Page 7 6.4.3.1.6. Order Information Notification 117 6.4.3.2. Customer Notification. 118 6.4.3.2.1. Customer Jeopardy Notification . 119 6.4.4. Acknowledgement Class 120 6.4.5. Exception Response Class 121 7. Behavior Model . 124 7.1. State and Activity Diagrams .

31、 124 References 127 ATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 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 ap

32、proach to perform the analysis related to unified ordering via electronic 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, custo

33、mers, 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 inherent in such an electronic ordering model, Unified Modeling Language (UML) tools by RationalRose and MyEclipse have been u

34、sed 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 Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structured methodology

35、. The scope of UOM encompasses business requirements, analysis, design, 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 o

36、f 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 activity diagrams. Two appendices include the data dictionary and the functional data matrix. The UOM-ASR Volume I is focused on

37、 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 Service Ordering Subcommittee maintains the UOM-ASR Volume I document. ATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2

38、012 Issue 21 for ASOG v46 Page 9 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 informational and behavioral models are

39、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 complexities inherent in such an ele

40、ctronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop this Volume II. A traceability matrix is included in the appendix to map the details in Volume II to the Business Requirements. Some additional requirements are included in Volume II in ord

41、er 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 requirements. The OBF Ordering Sol

42、utions 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 implementation technology. The first technol

43、ogy 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 necessary to repeat the Design

44、Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. ATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Issue 21 for ASOG v46 Page 10 UOM-ASR Volume IV - Implementation This

45、document includes implementation specifications that must be 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 te

46、mplate. As with the Design Phase, the Implementation Phase may also have to be repeated in order to 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 Case

47、s-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 Spe

48、cification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document DevelopmentATIS-0410002-0021 UOM-ASR Volume II Issued September 21, 2012 Iss

49、ue 21 for ASOG v46 Page 11 2. 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 provider in the provisioning of Access Services. 2.2. Purpose The document is intended to assist providers and customers in the process of conducting the analysis phase of their development steps to realize an electronic, unified ordering system. 2.3. Scope UOM-AS