1、 International Telecommunication Union ITU-T M.3170.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Multi-technology network management: Business agreement (TMF513) ITU-T Re
2、commendation M.3170.1 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.759
3、 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 publ
4、ic 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 channel s
5、ignalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3170.1 (03/2007) i ITU-T Recommendation M.3170.1 Multi-technology network management: Business agreement (TMF513) Summary The multi-technology network management (MTNM) solution suite
6、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 business agreement (TMF513) and relates its components to ke
7、y Recommendations on TMN functionality for q reference points between the NML and EML. It wraps TMF513 and associated supporting documents by referencing them normatively and relating them to identified Recommendations on TMN (NGNM) and principles of functional (NG) network architectures (such as tr
8、ansmission layering without adaptation details). This Recommendation can also be used as a lead-in to the MTNM business agreement. Source ITU-T Recommendation M.3170.1 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.
9、1 (03/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 qu
10、estions 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 Recommendati
11、ons on 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
12、, the 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
13、applicability) 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 w
14、ith the 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 app
15、licability 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 imp
16、lement 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 2007 All rights reserved. No part of this publication may be reproduced, by any
17、means whatsoever, without the prior written permission of ITU. ITU-T Rec. M.3170.1 (03/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 4 Abbreviations 3 5 Conventions 3 6 TMF513 overview A lead-in to the MTNM business agreement 3 6.1 Relationship to other M.3170-series Recommendati
18、ons 4 6.2 Relationship to other TMN Recommendations 4 6.3 Relationship to other TM Forum specifications. 5 7 Referencing TMF513 6 Bibliography. 8 ITU-T Rec. M.3170.1 (03/2007) 1 ITU-T Recommendation M.3170.1 Multi-technology network management: Business agreement (TMF513) 1 Scope The multi-technolog
19、y 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-technology fixed transport, access and aggregation networks. The MTNM implementation view specifies a CORBA-based TMN Q inte
20、rface 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 deliverables: The MTNM business view is specified in the business agreement (BA) TMF513. The MTNM system view is specified in UM
21、L 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 documentation) and associated implementation statement (IS) templates and guidelines TMF814A. The MTNM supporting documentation (SD)
22、 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 TMF513 and describes its relationship to the other M.3170-series Recommendations, other TMN Recommendations and other TM Forum
23、specifications. 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 su
24、bject 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 documen
25、t 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 trans
26、port network resource model. ITU-T M.3010 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3013 ITU-T Recommendation M.3013 (2000), Considerations for a telecommunications management network. ITU-T M.3020 ITU-T Recommendation M.3020 (2007), Manageme
27、nt 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 framework. 2 ITU-T Rec. M.3170.1 (03/2
28、007) 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 (BO
29、M). M.3050/Supplement 3 eTOM to M.3400 mapping. ITU-T M.3170.0 ITU-T Recommendation M.3170.0 (2007), Multi-technology network management: Introduction and supporting documentation. ITU-T M.3170.2 ITU-T Recommendation M.3170.2 (2007), Multi-technology network management: Information agreement (TMF608
30、). ITU-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
31、: overview. 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), M
32、ulti-Technology Network Management (MTNM) NML-EML Interface: Business Agreement, except for the table of references contained in Appendix B. NOTE This table of references consists of the columns “reference“, “description“ and “brief use summary“. Whilst the last column is meant to clearly indicate f
33、or 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 specification (a non-normative reference), it turned out that this goal was not reached unambigously in all cases. Therefore this R
34、ecommendation does not reference this table. Instead the truly normative references of TMF513 v3.0, namely TMF608, 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 Reco
35、mmendation (see b-TMF044 v2.0 and b-TMF402 v5.10). TMF608 v3.0 TM Forum TMF608 Version 3.0 (2004), 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.
36、NOTE This Recommendation does not reference this table for the same reasons explained in the Note for TMF513 v3.0. 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 Recommendation while the useful and av
37、ailable non-normative references are added to the Bibliography of this Recommendation (see b-TMF044 v2.0 and b-TMF404 v2.8. 3 Definitions Refer to clause 3 of ITU-T M.3170.0. ITU-T Rec. M.3170.1 (03/2007) 3 4 Abbreviations Refer to clause 4 of ITU-T M.3170.0. 5 Conventions This Recommendation does n
38、ot use any particular notational or other conventions. 6 TMF513 overview A lead-in to the MTNM business agreement This business agreement defines the business problem statement and business requirement model for the information exchange or interface between network management systems (NMSs) and elem
39、ent management systems (EMSs) enabling unified management of SONET/SDH, OTN, DSL, ATM and point-to-point Ethernet transport and access networks. The business problem statement is described in two parts: Business problem description, project scope and objectives which identify the business problem re
40、garding the management of a variety of transport network equipment, including the scope, objectives, business scenarios and the benefits to be gained through the solution. Business processes which describe the related business processes and proposed improvements in terms of the enhanced telecom oper
41、ations map ITU-T M.3050.x b-GB921 v7.0 b-GB921D v6.1 b-TMF517 v1.1. For MTNM the focus is on the resource management and operations business processes (RM normal sequences, dynamic requirements. Additional requirements are defined for the remaining categories of b-TMF402 v5.10: abnormal or exception
42、 conditions, dynamic requirements; expectations and non-functional requirements; system administration requirements. Use cases which present use case descriptions and diagrams to define the interactions across each of the process interfaces covered in the business agreement. Use cases are defined in
43、 several categories (or management function sets): NMS-EMS session management, EMS-NE session management, discovery and inventory, provisioning, connection management, protection management, fault management, equipment, craft-related, performance management, GUI cut-through, ATM provisioning, and AT
44、M connection management. Use case details include the following components: use case ID: use case name, summary, actor(s), preconditions, begins when, description, ends when, exceptions, post conditions and traceability. The use case template is similar to the use case template of ITU-T M.3020. Busi
45、ness requirement model UML diagrams which contain a summary of the business requirement UML model along with the traceability to the requirements. This serves as the starting point for developing an information agreement and solution set(s). The model is divided into a static model (complete class d
46、ictionary with mapping to static and dynamic requirements but no UML diagram fragments these are part of TMF608) and a dynamic model (i.e., the collaboration and state diagrams of TMF608). 4 ITU-T Rec. M.3170.1 (03/2007) Traceability matrices which provide matrices that show traceability for: use ca
47、ses to requirements; UML classes to requirements; UML classes to use cases; static requirements to UML classes; dynamic requirements to use cases and UML class operations; and the remaining additional requirements (exceptional, non-functional, administrative). The detailed static requirements, norma
48、l and exceptional dynamic requirements, use cases, business requirement UML model and traceability matrices for the MTNM NML-EML interface shall be in accordance with TMF513 v3.0, which extends b-TMF513 v.2.1. NOTE TMF513 v3.0 incorporates b-TMF513 v2.1 (though with certain well-documented changes),
49、 and so b-TMF513 v2.1 is not a formal prerequisite for TMF513 v3.0. However, knowledge of the more readily accessible v2.1 may greatly simplify the approach to and understanding of v3.0. 6.1 Relationship to other M.3170-series Recommendations M.3170.1/TMF513 defines the requirements for the interface both in terms of the objects and operations that the interface is required to support and the overall behaviour of t
