ITU-T M 3170 2-2007 Multi-technology network management Information agreement (TMF608) (Study Group 4)《多技术网络管理 信息协议(TMF608)研究组4》.pdf

《ITU-T M 3170 2-2007 Multi-technology network management Information agreement (TMF608) (Study Group 4)《多技术网络管理 信息协议(TMF608)研究组4》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3170 2-2007 Multi-technology network management Information agreement (TMF608) (Study Group 4)《多技术网络管理 信息协议(TMF608)研究组4》.pdf（20页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3170.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Multi-technology network management: Information agreement (TMF608) ITU-T

2、 Recommendation M.3170.2 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.

3、759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International p

4、ublic telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channe

5、l signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3170.2 (03/2007) i ITU-T Recommendation M.3170.2 Multi-technology network management: Information agreement (TMF608) Summary The multi-technology network management (MTNM) solution

6、suite realizes a TMN interface between the NML and EML according to ITU-T Recommendation M.3010 for the FCAPS management of multi-technology fixed transport, access and aggregation networks. This Recommendation explains the structure of the MTNM information agreement (TMF608) and relates its compone

7、nts to the M.3020 methodology for TMN interface specification. It wraps TMF608 and associated supporting documents by referencing them normatively and relating them to identified Recommendations on TMN functionality (FCAPS-based) and TMN interface specification methodology but not to Recommendations

8、 on TMN interface analysis models. This Recommendation can also be used as a first lead-in to the MTNM information agreement. Source ITU-T Recommendation M.3170.2 was approved on 16 March 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. M.3170.2 (03

9、/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questio

10、ns and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations o

11、n these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the

12、 expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or appli

13、cability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with t

14、he Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicab

15、ility of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implemen

16、t this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced, by any means

17、 whatsoever, without the prior written permission of ITU. ITU-T Rec. M.3170.2 (03/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 3 4 Abbreviations 3 5 Conventions 3 6 TMF608 overview A lead-in to the MTNM information agreement 3 6.1 Relationship to other M.3170-series Recommendation

18、s 5 6.2 Relationship to other TMN Recommendations 5 6.3 Relationship to other TM Forum specifications. 5 6.4 Overview of UML diagram fragments and state diagrams 6 6.5 Mapping the fine-grained UML to a service-oriented UML 8 7 Referencing TMF608 10 Bibliography. 12 ITU-T Rec. M.3170.2 (03/2007) 1 IT

19、U-T Recommendation M.3170.2 Multi-technology network management: Information agreement (TMF608) 1 Scope The multi-technology network management (MTNM) solution suite is an implementation standard of a TMN interface between the NML and EML according to ITU-T M.3010 for the FCAPS management of multi-t

20、echnology fixed transport, access and aggregation networks. The MTNM implementation view specifies a CORBA-based TMN Q interface between an NMS (CORBA client or TMN manager) and an EMS (CORBA server or TMN agent which is in contact to the NEL). The MTNM solution suite consists of the following deliv

21、erables: The MTNM business view is specified in the business agreement (BA) TMF513. The MTNM system view is specified in UML in the information agreement (IA) TMF608. The MTNM CORBA-based implementation and deployment views are specified in the CORBA IDL solution set (SS) TMF814 (with HTML documenta

22、tion) and associated implementation statement (IS) templates and guidelines TMF814A. The MTNM supporting documentation (SD) guides and lightens the work with the MTNM views and also includes normative parts of the interface such as name/value pairs. This Recommendation outlines the structure of TMF6

23、08 and describes its relationship to the other M.3170-series Recommendations and to other TMN Recommendations. This Recommendation emphasizes that the M.3170-series Recommendations go for Level B TMN interface information conformance (as defined by ITU-T M.3010): the managed object classes supported

24、 by the MTNM NML-EML Interface are specified in approved standards of the de facto standards body TM Forum (TMF608 v3.0, b-TMF608 v2.1, TMF814 v3.0, TMF814 v2.1 and ITU-T M.3170.3 see clauses 6.4 and 6.5). This Recommendation provides a coarse overview of the UML diagram fragments and state diagrams

25、 of TMF608 and presents some principles for mapping the MTNM fine-grained UML TMF608 v3.0 and b-TMF608 v2.1 to a service-oriented UML TMF814 v3.0 SD that forms a starting point for any service-oriented solution set construction such as the service-oriented CORBA IDL of TMF814 v3.0, TMF814 v2.1 and I

26、TU-T M.3170.3. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are sub

27、ject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document

28、 within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T G.805 ITU-T Recommendation G.805 (2000), Generic functional architecture of transport networks. ITU-T G.852.2 ITU-T Recommendation G.852.2 (1999), Enterprise viewpoint description of transp

29、ort network resource model. ITU-T M.3010 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. 2 ITU-T Rec. M.3170.2 (03/2007) ITU-T M.3013 ITU-T Recommendation M.3013 (2000), Considerations for a telecommunications management network. ITU-T M.3020 ITU-T Recomme

30、ndation M.3020 (2007), Management interface specification methodology. ITU-T M.3050.x ITU-T Recommendations M.3050.x (2004), Enhanced Telecom Operations Map (eTOM). NOTE This series of Recommendations has the following structure: M.3050.0 eTOM Introduction. M.3050.1 eTOM The business process framewo

31、rk. M.3050.2 eTOM Process decompositions and descriptions. M.3050.3 eTOM Representative process flows. M.3050.4 eTOM B2B integration: Using B2B inter-enterprise integration with the eTOM. M.3050/Supplement 1 eTOM ITIL application note. M.3050/Supplement 2 eTOM Public B2B Business Operations Map (BOM

32、). M.3050/Supplement 3 eTOM to M.3400 mapping. ITU-T M.3170.0 ITU-T Recommendation M.3170.0 (2007), Muti-technology network management Introduction and supporting documentation. ITU-T M.3170.1 ITU-T Recommendation M.3170.1 (2007), Multi-technology network management Business agreement (TMF513). ITU-

33、T M.3170.3 ITU-T Recommendation M.3170.3 (2007), Multi-technology network management CORBA IDL solution set (TMF814) with implementation statement templates and guidelines (TMF814A). ITU-T M.3200 ITU-T Recommendation M.3200 (1997), TMN management services and telecommunications managed areas: overvi

34、ew. ITU-T M.3400 ITU-T Recommendation M.3400 (2000), TMN management functions. ITU-T X.735 ITU-T Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, Information technology Open Systems Interconnection Systems Management: Log control function. TMF513 v3.0 TM Forum TMF513 Version 3.0 (2004), Multi-tec

35、hnology network management (MTNM) NML-EML Interface: Business agreement, except for the table of references contained in Appendix B. NOTE This Recommendation does not reference this table for the same reasons explained in the note of TMF608 v3.0. Instead the truly normative references of TMF513 v3.0

36、, namely TMF608 v3.0, ITU-T G.805 and ITU-T X.735, are added to the references clause of this Recommendation while the useful and available non-normative references are added to the bibliography of this Recommendation (see TMF044 v2.0 and b-TMF402 v5.10). TMF608 v3.0 TM Forum TMF608 Version 3.0 (200

37、4), Multi-Technology Network Management (MTNM) NML-EML Interface: Information Agreement, Rational Rose (UML) version and generated HTML version, except for the table of references contained in Appendix B. NOTE This table of references consists of the columns “reference“, “description“ and “brief use

38、 summary“. Whilst the last column is meant to clearly indicate for each reference (i.e., row) whether the reference is needed for the implementation of the specification (a normative reference) or was used for the development of the ITU-T Rec. M.3170.2 (03/2007) 3 specification (a non-normative refe

39、rence), it turned out that this goal was not reached unambigously in all cases. Therefore, this Recommendation does not reference this table. Instead the truly normative references of TMF608 v3.0, namely TMF513 v3.0, ITU-T G.805 and ITU-T X.735, are added to the references clause of this Recommendat

40、ion while the useful and available non-normative references are added to the bibliography of this Recommendation (see b-TMF044 v2.0 and b-TMF404 v2.8). TMF814 v2.1 TM Forum TMF814 Version 2.1 (2002), Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set. TMF814 v3.0 TM

41、 Forum TMF814 Version 3.0 (2004), Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set. TMF814 v3.0 SD TM Forum TMF814 Version 3.0 (2004), Multi-Technology Network Management (MTNM) NML-EML Interface: CORBA IDL Solution Set, Supporting Document “Traceability between I

42、A and SS“, file “MappingIASS.pdf“. 3 Definitions Refer to clause 3 of ITU-T M.3170.0. 4 Abbreviations Refer to clause 4 of ITU-T M.3170.0. 5 Conventions This Recommendation does not use any particular notational or other conventions. 6 TMF608 overview A lead-in to the MTNM information agreement This

43、 information agreement specifies the MTNM NML-EML interface information model for the management of multi-technology networks including transport networks based SONET/SDH, OTN, ATM, DSL and point-to-point Ethernet technologies. The interface information model is essentially defined in terms of M.317

44、0.1/TMF513 business agreement specifications followed by the interface information model specifications themselves. The referenced business agreement specifications include: Project scope and objectives which provide an executive summary by identifying the Interface being addressed and describing th

45、e benefits gained by the problems solution. Interface information requirements which reference M.3170.1/TMF513 to list the functional and non-functional interface information requirements to be fulfilled by the interface information model described in this information agreement. Interface informatio

46、n use cases which reference M.3170.1/TMF513 to identify the interface information use case diagrams and descriptions needed to describe the way actors use the interface and the interactions across the interface covered in this information agreement. Requirement traceability matrices which refer to M

47、.3170.1/TMF513 to show the traceability of use cases to requirement statements, of object classes to use cases, etc. See clause 6 of ITU-T M.3170.1 and TMF513 v3.0 for the various types of traceability matrices. 4 ITU-T Rec. M.3170.2 (03/2007) NOTE 1 Traceability between the information agreement (I

48、A) and the CORBA IDL solution set (SS) is provided by the supporting document “Traceability between IA and SS“ TMF814 v3.0 SD (contained in the solution set TMF814 v3.0). This document lists all classes, attributes, relationships, operations, enums, strings and structs defined in the IA and associat

49、es them with the respective IDL definitions in the SS. The interface information model specifications provide a protocol-neutral description of the interface that cover the business agreement specifications. The TM Forum MTNM team has been using UML and the Rational Rose modelling tool to develop the MTNM interface information model. The complete protocol-neutral master specification is contained in the Rat