ATIS 0410003-0029-2016 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 54 Includes Access to Additional Content).pdf

《ATIS 0410003-0029-2016 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 54 Includes Access to Additional Content).pdf》由会员分享，可在线阅读，更多相关《ATIS 0410003-0029-2016 Unified Ordering Model (UOM) Volume III - Design For Access Service Ordering Guidelines (ASOG) (Version 54 Includes Access to Additional Content).pdf（391页珍藏版）》请在麦多课文档分享上搜索。

1、 Confidential | Copyright 2016 IHS Markit Ltd Access to Additional Content For: ATIS-0410003-0029, Dated: 09/2016 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS Markit as a convenience to the user in order to provide access to a

2、dditional content as authorized by the Copyright holder of this document Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ATIS-0410003-0029 Information contained in the above is the property of the Copyright holder and all Notice of Discla

3、imer however they resulted in no impact to the contents of this document: 3524, 3551, 3556, 3557, 3560, 3563 Global Changes Change all ASOG 53 to ASOG 54; Version 53 to Version 54; Issue 28 to Issue 29. Change ATIS document number from ATIS-0410003-0028 to ATIS-0410003-0029. Update Issue Date. Sort

4、the placement of some element and complexType definition structures alphabetically. (Note: The sequence of elements within a structure are not changed.) Other grammatical and spelling corrections that do not impact the technical content of this document are not reflected in the Summary of Changes. I

5、ssue 3549 removed references to Mechanized Specifications from section 2.1, ATIS References. Table of Contents Updated to reflect document re-pagination. SUMMARY OF CHANGES ASOG V54 Page 2 of 3 UOM-ASR VOLUME III SUMMARY OF CHANGES FOR ASOG V54 Schema Issue # Element Name Description of Change UOM-B

6、ASE UOM-BASE 3552 CONTACT_Type Added metadata references for the new SITECON (ASR-001) element UOM-BASE 3552 TelNumberExt17_Type Added metadata references for the new SITECON_TEL (ASR-001) element UOM-BASE 3552 EMAIL_Type Added metadata references for the new SITECON_EMAIL (ASR-001) element UOM-BASE

7、 3543 ORD_Short_Type Removed metadata references for PEND_ORD (ECI-025) element UOM-BASE 3543 CTYP_Type Removed metadata references for PCT (ECI-025) element UOM-BASE 3543 InformationRate8_Type Removed metadata references for EASPEED (ECI-025) element UOM-BASE 3543 PON_Type Removed metadata referenc

8、es for ACPON (ECI-025) element UOM-BASE 3543 ECCKT28_Type Removed metadata references for VCCID, EAID, ICID, ACCESSID, and PORTID (ECI-025) elements UOM-BASE 3543 ORD_Type Removed metadata references for ACCESSORD, PORTORD and VCORD (ECI-025) elements UOM-BASE 3543 IPV4_Type Removed metadata referen

9、ces for SUBNET_MASK (ECI-025) element UOM-BASE 3543 IPAI_Type Removed metadata references for IPAI and IP_ADDRESS (ECI-025) elements UOM-BASE 3543 IPVN_Type Removed metadata references for IP_ADDRESS (ECI-025) element UOM-BASE 3543 SystemNumber10_Type Removed metadata references for ASN (ECI-025) el

10、ement UOM-BASE 3543 IndicatorY_Type Removed metadata references for EXDI (ECI-025) element UOM-BASE 3543 ECI_ASR_LEVEL Removed the following types no longer in use: SM_TYPE, QOPT_Type, EA_Type, Remarks250_Type, ACAT_Type, CHPD_Type UOM-BASE 3543 ECI_CKT_LEVEL Removed the following types no longer in

11、 use: TNT_Type, OPTCON_Type, TRM_Type, VPN_Name_Type, VZEP_Type UOM-BASE 3536 DATE_Type Updated metadata reference for the CDLRD and DLRD (CN-011) element to remove MIS UOM-ASR UOM-ASR 3552 CONTACT Added the following new elements to the sequence: SITECON, SITECON_TEL, and SITECON_EMAIL after MTCE_E

12、MAIL. UOM-ASR 3543 ECI_ASR_LEVEL Removed the following elements from the sequence: CHPD, PEND_ORD, SM, SM2, SM3, SM4, SM5, SM6, SM7, QOPT, PCT, EASPEED, EA_TYPE, CONFIG_REMARKS, ACPON, ACAT UOM-ASR 3543 ECI_CKT_LEVEL Removed the following elements from the sequence: TNT, VCCID, SOPTCON, SUBNET_MASK,

13、 TRM, VPN_NM, OPTCON, IPAI, IP_Address, ICID, EXDI, EGRESS, EAID, ASN SUMMARY OF CHANGES ASOG V54 Page 3 of 3 UOM-ASR VOLUME III SUMMARY OF CHANGES FOR ASOG V54 Schema Issue # Element Name Description of Change UOM-ASRInquiry No changes for ASOGv54. UOM-ASRMEC No changes for ASOGv54. UOM-ASRNotify U

14、OM-ASRNotify 3543 ECI_CKT_LEVEL_RTN Removed the following elements from the sequence: ACCESSID, ACCESSORD, PORTID, PORTORD, VCCID, VCORD UOM-ASRNotify 3543 ECI_ASR_LEVEL_RTN Removed the following elements from the sequence: CHPD UOM-ASRNotify 3549 BAN_CORRECTION Removed BAN_Correction, BAN_Correctio

15、n_Type, and BANC section UOM-ASRNotify 3549 Error_Clarification_Type Modified the multiplicity of the CNR to required under Error_Clarification_Type UOM-ASRNotify 3550 Notification_Type Removed Customer_Notify_Type, CUSTOMER_HDR_ComplexType, and Customer_Jeopardy from under Notification_Type. UOM-AS

16、RNotify 3550 Jeopardy_Notify_Type Removed CC element from within the sequence. UOM-ASRNotify 3550 Jeopardy_Notify_Type Modified the multiplicity of the CNR to required under Jeopardy_Notify_Type ATIS-0410003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 4 Table Of Contents

17、TABLE OF CONTENTS 4 1 SCOPE, PURPOSE, used in XML documents as element types and attribute names. Namespaces are used in XML to qualify names in order to separate them from other names. Note: A URI has a similar format to a URL. It is not always possible to resolve a URI to find an instance of an XM

18、L schema. Schema: A set of schema components. A collection (vocabulary) of type definitions and element declarations whose names belong to a particular namespace called a target namespace. A schema defines the allowable contents of a class of XML documents. The purpose of a schema is to define and A

19、TIS-0410003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 8 describe a class of XML instance documents by using these constructs to constrain and document the meaning, usage and relationships of their constituent parts: datatypes, elements and their content, attributes and

20、their values, entities and their contents, and notations. A class of documents refers to all possible permutations of structure in instance documents that will still conform to the rules of the schema. Schema Component: The generic term for the building blocks that comprise the abstract data model o

21、f the schema. There are 13 kinds of schema components defined: named components (Simple type definitions, Complex type definitions, Attribute declarations, Element declarations, attribute group definitions, identity-constraint definitions, model group definitions, notation declarations, annotations)

22、, and un-named components (model groups, particles, wildcards, and attribute uses). tML Schema: Constructs to constrain and document the meaning, usage and relationships of the constituent parts of tML instance documents. tML Schemas are based on the W3C XML Schema Recommendation. tML Namespace: A c

23、ollection of names, identified by a URI reference RFC2396, that is used in tML documents as element types and attributes UML: An OMG specification to provide system architects working on object analysis and design with one consistent language for specifying, visualizing, constructing, and documentin

24、g the artifacts of software systems and for modeling of business processes 4 Overview of UOM-ASR Volume III 4.1 Introduction to UOM The document, Unified Ordering Model Access Service Request Volume III Design, (UOM-ASR Volume III) is part of a set of documents that provides an end-to-end structured

25、 systems engineering approach to perform the design related to unified ordering via electronic interfaces. This document provides the design of the detailed business and analysis for an ordering model for the UOM interface. It describes the tML/XML Schemas with the intent that service providers and

26、their vendors can use the tML/XML Schemas when exchanging data for an ASR application. Because of the level of complexities inherent in such an electronic ordering model, a tML Framework Document (ITU-T M.3030) has been used as a guide to develop this volume. The intent of Unified Ordering Model (UO

27、M) 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, these components are defined within the UOM in four volumes. UOM-ASR Volume I - Business Requiremen

28、ts This document describes the business requirements. This volume includes a high-level overview of 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 appendi

29、ces include the data dictionary and the functional data matrix. The UOM-ASR Volume I is focused on 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 m

30、aintains the UOM-ASR Volume I document. ATIS-0410003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 9 ATIS-0410003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 10 UOM-ASR Volume II - Analysis This analysis document provides the logical view of the

31、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 described using the Unified Modeling Language (UML). UOM-ASR Volume II utilizes UML for descriptive purposes and in so

32、me 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 electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop Volume

33、II. Some additional requirements are included in Volume II in order 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, Volume II may need to be expan

34、ded to address additional requirements. The OBF Ordering Solutions 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 f

35、or the selected implementation technology. The first technology selected was XML; therefore UOM-ASR Volume III includes appropriate XML schemas related to unified access ordering. This document does not specify a particular transport protocol as it is assumed that the trading partners will determine

36、 the appropriate transport protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. Volume III specifies the interface standard for the Un

37、ified Ordering Model for access services using the telecommunications Markup Language (an extension of XML), as defined in tML Framework. All Functions in this standard are designed as optional features. The implementation of the functions (use cases) will be determined between individual customer a

38、nd provider negotiations. UOM Volume IV Generic Implementation Guideline 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 (JI

39、A) may be included as an appendix for trading partners to use 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 OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implem

40、entation Guideline. ATIS-0410003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 11 Unified Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirements-Business Validation Rules2. Logical Analysis:-In

41、formational Model-Behavioral Model-Sequence Diagrams-Class/Object Diagrams-State Diagrams-Traceability Matrix3. Technical Standard:-Technology Specific- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF 1. Business ProcessDefinition2. Analysis3.

42、Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document DevelopmentFigure 1 - UOM ASR Process and Document Development 4.2 Requirements of this document The following requirements have been taken into account by the Ordering Solutions Committee/Access Service Order

43、ing Subcommittee in the development of UOM-ASR Volume III: UOM-ASR Volume III should be technology-specific and tML is chosen to be the technology to present the syntax of information definition. Therefore, the tML Schemas defined for the UOM-ASR should conform to the tML Framework Document (ITU-T M

44、.3030). UOM-ASR Volume III tML Schemas for the Design phase of the UOM-ASR project should reflect the current analysis described in UOM-ASR Volume II (that reflects the requirements in UOM-ASR Volume I). UOM-ASR Volume III should be backward compatible with UOM-ASR Volume I and UOM-ASR Volume II. UO

45、M-ASR Volume III should be generic, flexible, and have reusability. UOM-ASR Volume III edits in the tML Schemas are minimized to the maximum data length and a minimum subset of required fields. Other validation rules and processes are generally left to the customer/provider back-end systems. ATIS-04

46、10003-0029 UOM-ASR Volume III Issued September 23, 2016 Issue 29 for ASOG v54 12 UOM-ASR Volume III will contain tag names not to exceed 20 characters in length and will be in upper case format to conform with the current OBF guidelines. UOM-ASR Volume III does not convey licensing right to non-COMM

47、ON LANGUAGE licensees to use the COMMON LANGUAGE1code sets identified throughout the UOM-ASR Volume III document in their internal operations. Where COMMON LANGUAGE is provided, its intended use by non-COMMON LANGUAGE licensees is limited. Allowable uses will be specified by the COMMON LANGUAGE lice

48、nsee, per their COMMON LANGUAGE contract. 4.3 Structure of this document The remainder of the document consists of the following sections: Sections 5, 6 and 7 provide references to the documents that define the requirements, analysis, and implementation specifications for the UOM-ASR application. Se

49、ction 8 consists of tML Schemas: o UOM-Base Schema, that defines all reusable domain specific and non-domain specific common types and elements that are used in tML Schemas for various UOM applications, and o UOM-ASR, UOM-ASRInquiry, UOM-ASRMEC and UOM-ASRNotify that present the service request, inquiry, notification, acknowledgement, and exception response interactions in the access domain. 4.4 How to use this document This document should be used as a source to facilitate interoperability between trading partners on the TMN X interface usi