ATIS 0412002-1402-2014 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II - Analysis.pdf

1、 Page 1 ATIS-0412002-1402 Unified Ordering Model Local Service Ordering (UOM-LSR) Volume II Analysis For Local Service Ordering Guidelines (LSOG) 2Q14 ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 2 ATIS is a technical planning and standards development organization that is committed

2、to rapidly developing and promoting technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry comm

3、ittees, and its Incubator Solutions Program. www.atis.org ATIS 0412002-1402 Unified Ordering Mode Local Service Ordering (UOM-LSR) Volume II Analysis Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Forum: Ordering and Billing Forum Local Service Orderi

4、ng Subcommittee Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2014 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 otherwise, without the prior w

5、ritten permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 3 Notice of Disclaimer and Limitation of Liability The information provided in this document is

6、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 be impli

7、ed. 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 OF INT

8、ELLECTUAL 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 USE OF OR

9、 RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 4 Change History Issue # Document Release Description of Changes OBF/LSOP Issue 2632 Issue 1 Initial Issue of UOM-LSR Volume II for Local Service Orderin

10、g (LSR LSOG Version 9) OBF/UOM-LSR Issue 2989 Issue 2 Initial Issue of UOM-LSR Volume II for Local Service Ordering (LSR LSOG Version 10) OBF/UOM-LSR Issue 3064 Issue 3 Initial Issue of UOM-LSR Volume II for Local Service Ordering (LSR LSOG Version 11) OBF/UOM-LSR Issue 3078 Issue 4 Initial Issue of

11、 UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 12) OBF/UOM-LSR Issue 3167 Issue 5 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 13) OBF/UOM-LSR Issue 3168 Issue 6 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 14) OB

12、F/UOMLSR Issue 3193 3Q08 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 3Q08) N/A 2Q14 Initial Issue of UOM-LSR Volume II for Local Service Ordering( LSR LSOG Version 2Q14) ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 5 Table of Contents 1. Introducti

13、on to UOM Documentation 7 1.1 UOM-LSR Volume I - Business Process Definition 7 1.2 UOM-LSR Volume II - Analysis . 8 1.3 UOM-LSR Volume III - Design . 8 1.4 UOM Generic Implementation Guidelines (GIG) Volume IV - Implementation . 8 2. UOM Requirements Summary . 8 2.1 System Requirements . 8 2.2 Secur

14、ity Requirements 9 2.3 Messaging Requirements 9 2.4 Reporting Requirements . 10 3. Overview of UOM-LSR Volume II 10 3.1 Intended Audience 11 3.2 Purpose . 11 3.3 Scope 11 3.4 Development Note 11 3.5 Assumptions of this Document . 12 3.6 Structure of Document 12 4. UOM-LSR High Level Process Overview

15、 . 13 5. Use Cases and Sequence Diagrams 14 5.1 UOM-LSR Pre-Order . 15 5.1.1 Address Validation . 17 5.1.2 Telephone Number Assignment . 19 5.1.3 Feature / Service Availability . 21 5.1.4 Appointment Scheduling / Appointment Reservation 23 5.1.5 Service Configuration . 25 5.1.6 Loop Qualification 26

16、 5.1.7 Customer Service Inquiry . 27 5.1.8 Facility Assignment Verification 28 5.1.9 Directory Listing Inquiry (DLI) 29 5.2 UOM-LSR Service Order Request and Response 30 5.2.1 Service Order Request 31 5.2.1.1 Local Service Request (LSR) . 31 5.2.1.2 End User (EU) 31 5.2.1.3 Loop Service (LS) 31 5.2.

17、1.4 Number Portability (NP) 31 5.2.1.5 Loop Service with Number Portability (LSNP) 31 5.2.1.6 Resale Service (RS) 31 5.2.1.7 Port Service (PS) 31 5.2.1.8 Resale Private Line (RPL) 32 5.2.1.9 Resale Frame Relay (RFR) . 32 5.2.1.10 CENTREX Resale Services (CRS). 32 5.2.1.11 DID/DOD/PBX Services (DDPS)

18、 32 5.2.1.12 Hunt Group Information (HGI) 32 5.2.1.13 ISDN BRI/PRI Service (IS) 32 5.2.1.14 Directory Listing Service (DL) . 32 5.2.2 Service Order Response 33 5.2.2.1 Local Response (LR) 33 5.3 UOM-LSR Post Order 34 5.3.1 Service Order Inquiry Process (SOIP) 35 5.3.2 Provider Notification (PN) . 35

19、 6. Information Model 36 6.1 UOM-LSR High Level View 37 6.2 LSR Inquiry Request and Response Classes 37 ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 6 6.3 Abbreviation List 37 6.4 Data Groups 39 6.5 UOM-LSR GRP Types Class Diagrams . 39 6.6 UOM-LSR Pre-Order . 41 6.6.1 Address Valida

20、tion Class Diagram . 41 6.6.2 Telephone Number Assignment Class Diagram . 42 6.6.3 Feature / Service Availability Class Diagram . 43 6.6.4 Appointment Scheduling Class Diagram 44 6.6.5 Service Configuration Class Diagram 45 6.6.6 Loop Qualification Class Diagram . 46 6.6.7 Local Customer Service Inq

21、uiry (CSI) Class Diagram . 48 6.6.8 Facility Assignment Verification Class Diagram . 49 6.6.9 Directory Listing Inquiry (DLI) Class Diagram . 50 6.7 UOM-LSR Service Order Request and Response 51 6.7.1 LSR Service Request Classes . 51 6.7.2 LSR Service Type Classes 51 6.7.3 LSR Basic Forms 53 6.7.3.1

22、 Local Service Request (LSR) Class Diagram . 54 6.7.3.2 End User (EU) Class Diagram 55 6.7.3.3 Loop Service (LS) Class Diagram 56 6.7.3.4 Number Portability (NP) Class Diagram 58 6.7.3.5 Loop Service with Number Portability (LSNP) Class Diagram . 59 6.7.3.6 Resale (RS) Class Diagram 60 6.7.3.7 Port

23、Service (PS) Class Diagram 61 6.7.3.8 Resale Private Line (RPL) Class Diagram . 62 6.7.3.9 Resale Frame Relay (RFR) Class Diagram 63 6.7.3.10 CENTREX Resale Services (CRS) Class Diagram 64 6.7.3.11 DID/DOD/PBX Service (DDPS) Class Diagram . 65 6.7.3.12 Hunt Group Information (HGI) Class Diagram 67 6

24、.7.3.13 ISDN BRI/PRI (IS) Class Diagram 67 6.7.3.14 Directory Listing (DL) Class Diagram . 69 6.7.4 LSR Service Response Classes . 71 6.7.4.1 Local Response (LR) Class Diagram 72 6.8 UOM-LSR Post Order 73 6.8.1 Service Order Inquiry Process (SOIP) 73 6.8.1.1 SOIP Service Order List Class Diagram 73

25、6.8.1.2 SOIP Service Order Detail Class Diagram 74 6.8.1.3 SOIP Service Order Activities Class Diagram 75 6.8.2 Provider Notification (PN) Class Diagram . 76 6.9 Simple Port Service Request (SPSR) Error! Bookmark not defined. 6.9.1 SPSR Diagram . Error! Bookmark not defined. Appendix A: Requirements

26、 Traceability Matrix 77 Appendix B: Change Control Process 79 References 80 ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 7 1. Introduction to UOM Documentation The intent of Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structur

27、ed methodology. The scope of UOM encompasses business requirements, analysis, design, and implementation. Logically, these components are defined within the UOM in four volumes depicted in the figure below. Process2. AnalysisUnified Model2. Logical Model- Class/Object Diagrams- Data Traceablity- Int

28、eraction Diagrams- State DiagramsVolume IVolume IIVolume IIIVolume IV3. Design 3. Information Model- Technology Information Model4. Implementation 4. Implementation Guidelines- Technology Specifications- Implementation Profile1. Business Process . Definition 1. Business Requirements- High Level Use

29、Cases- Data/Presentation Requirement- Business Validation Rules- Scenarios- Activity DiagramsLSOPLSOP LSOPLSOP/UOMASRUOM Process and Document Development1.1 UOM-LSR Volume I - Business Process Definition UOM-LSR Volume I provides an explanation of the business requirements and a conceptual overview

30、of the solution. It defines “what” the user initially sees as the problem and “how” the user sees the business solution. The business requirements for LSR functionality are described in ATIS/OBF Local Service Ordering Guideline (LSOG). The OBF LSO Subcommittee maintains the LSOG documents. The LSOG

31、constitutes UOM-LSR Volume I. It is separated into several practices that address specific business functions. The LSOG practices may be grouped into the following functional areas: Pre-Order, Service Order, and Post-Order. The Pre-Order practice describes the pre-order inquiry and response function

32、s that may take place prior to the ordering process. The practice also defines each data element and contains both the common business rules and the information regarding use of the pre-order functions within the practice. The Service Order practices describe the various forms used for the purpose o

33、f requesting local service. It includes field definitions, conventions, descriptions, and various scenarios to outline the process for a local service request. ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 8 The Post-Order practices outline the forms provided for local service respons

34、es and service order inquiries. 1.2 UOM-LSR Volume II - Analysis This analysis document provides the logical view of the proposed solution to meet the needs of the business requirements stated in ATIS/OBF LSR process. The primary sections include the use case and sequence diagrams, and informational

35、 model. The informational models are described using the Unified Modeling Language (UML). The UML provides the notation used within Volume II. Because of the level of complexities inherent in such an electronic ordering model, a unified modeling language tool has been used to develop this Volume II.

36、 A traceability matrix is included in Appendix A to map the details in Volume II to the Business Requirements defined in the LSOG. Some additional requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic inter-exchange. Volume II is not s

37、pecific 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 LSO Subcommittee maintains the UOM-LSR Volume II. 1.3 UOM-LSR Volume III - Design The logical view of the proposed reso

38、lution (model), created in the Analysis Phase, is translated into the language appropriate for the selected implementation technologies. XML is the implementation technology that is currently supported. This document does not specify a particular protocol as it is assumed that the trading partners w

39、ill determine the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF LSO Subcommittee maintains the UOM-LSR Volume III for XML implementation 1.4 UOM Generic Implementation Guidelines (GIG) Volume IV - Impl

40、ementation This 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

41、as a starting template. As with the Design Phase, the Implementation Phase may also have to be repeated in order to provide support for multiple technologies. The UOM-ASR and LSO Subcommittee maintain the UOM-GIG Volume IV. The LSO Subcommittee maintains UOM-LSR Appendices related to LSR in Volume I

42、V. 2. UOM Requirements Summary 2.1 System Requirements Additional system requirements are needed to support an implemented UOM interface. These requirements are in addition to the business requirements specified by the various OBF documents and address issues involving security, messaging, and accou

43、nt profiles that will be provided in UOM Volume IV. Additional requirements may also be added based upon customer provider negotiations as documented in pair wise Joint Implementation Agreements. ATIS 0412002-1402 UOM-LSR Volume II Issued 6/30/14 LSOG 2Q14 9 2.2 Security Requirements Security requir

44、ements include encryption, authentication, and non-repudiation. Refer to tML Transport Specification found in the ATIS Document Center. 2.3 Messaging Requirements Messaging requirements include attributes needed for message handling, delivery, responses, acknowledgements, and exceptions. Element MES

45、SAGE_ID: Class: UOM_HDR_Type Attribute: MESSAGE_ID Usage: Required Type: Character string with maximum length of 25 Description: Used as an invocation id. Message originator assigns a new message id to each message of type Request or Notification. Message recipient responds with the same message id

46、with each message of type Response, Acknowledgement, or Exception. Element MSG_TIMESTAMP: Class: UOM_HDR_Type Attribute: MSG_TIMESTAMP Usage: Required Type: xs:dateTime Description: Used to timestamp each message with the date and time the message was created. It is assumed messages are created just prior to transmission. This field is indented for logging purposes to help debugging and evaluating performance. Element TYPE: Class: EXCEPTION_RESPONSE Attribute: TYPE Usage: Required Type: ExceptionType_Type (enumeration) Values: GENERAL_FAILURE GENERAL_ERROR_RETRYABLE TRANSPORT_FAILURE TRA