1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU M.3013 (02/2000) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHON E CI RCU ITS, TELEGRAPHY, FACS I M I LE AND LEASED CIRCUITS Telecommunications management network Considera
2、tions for a telecomm u n ications management network ITU-T Recommendation M.3013 (Formerly CCITT Recommendation) ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general prin
3、ciples of maintenance and maintenance organization International transmission systems International telephone circuits Common channel signalling systems International telegraph systems and phototelegraph transmission International leased group and supergroup links International leased circuits Mobil
4、e telecommunication systems and services International public telephone network International data transmission systems Designations and information exchange International transport network M. 1 O-M.299 M. 300-M. 559 M. 560-M. 759 M.760-M.799 M. 800-M. 899 M. 900-M. 999 M. 1 000-M. 1 O99 M.1100-M.11
5、99 M. 1200-M. 1299 M. 1300-M. 1399 M. 1400-M. 1 999 M. 2000-M. 2999 Telecommunications management network M. 3008-M.3599 Integrated services digital networks Common channel signalling systems M. 3600-M. 3999 M.4000-M.4999 For further details, please rer to ITD-T List of Recommendations. ITU-T RECOMM
6、ENDATION M.3013 CONSIDERATIONS FOR A TELECOMMUNICATIONS MANAGEMENT NETWORK Summary The Telecommunications Management Network (TMN) is implemented to support management activities associated with telecommunication networks. This Recommendation introduces essential considerations needed to support ins
7、tallation and operation of a TMN based on the TMN principles, concepts and architecture, which are described in Recommendation M.30 1 O. Issues associated with evolution of new technologies for TMN applications are also identified. Background This Recommendation is based upon material extracted rom
8、Recommendation M.30 1 O (1 996). In this Recommendation the material has been updated, refined, and expanded to assist in the planning, design, implementation and operation of a TMN. Source ITU-T Recommendation M.3013 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Re
9、solution No. 1 procedure on 4 February 2000. Keywords Architecture, Implementation guidelines, Telecommunications management network (TMN). Recommendation M.3013 (02/2000) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunicatio
10、ns. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommun
11、ication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC
12、 Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication admin
13、istration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or
14、 applicability 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, the ITU had not received notice of intellectual property, protected by patents, which may be require
15、d to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 2000 All rights reserved. No part of this publication may be reproduced or utilized in any form or by
16、any means, electronic or mechanical, including photocopying and microfilm, without permission in writing fi-om the ITU. 11 Recommendation M.3013 (02/2000) CONTENTS 1 2 2.1 3 4 5 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 Scope . References . Structure of TMN documentation . 2.1.1 TMN overview 2.1.2 Architect
17、ure . 2.1.3 Interface specification methodology 2.1.4 Management requirements, functions and services . 2.1.5 Management information models 2.1.6 Communication services and protocols . Definitions Abbreviations Conventions General design and implementation considerations . Requirements impacting des
18、ign and implementation . Physical architecture overview . Physical block impacts for design and implementation Introduction . 6.4.1 Network element 6.4.2 Operations support system . 6.4.3 Workstation . Transformation function considerations . 6.5.1 Mediation device characteristics 6.5.2 Adaptation d
19、evice characteristics 6.5.3 Application of mediation and adaptation devices at the Q and X interfaces . TMN data communication characteristics 6.6.1 Messaging availabilityheliability . 6.6.2 Data communication network considerations 6.6.3 Message communication functionality 6.6.4 MCF considerations
20、. Interface impacts for design and implementation . 6.7.1 OS-NE Q interface . 6.7.2 OS-OS Q interface . 6.7.3 OS-OS X interface . 6.7.4 OS-WS F interface . 6.7.5 Human-computer interface (g reference point) Support functionality Recommendation M.3013 (02/2000) 1 2 2 4 5 5 5 6 6 6 7 8 9 9 10 11 11 12
21、 12 13 13 15 15 17 17 20 20 21 . 111 7 7.1 7.2 7.3 7.4 7.5 Additional design and implementation considerations for technology selection and integration . Business requirements for technology selection . Considerations for the selection of communication technologies may impact interoperability . Crit
22、eria based on interface-technology performance . Other fitness-for-use criteria for interface technology . Characteristics of TMN reference points and interfaces . Characteristics of intra-TMN reference points and interfaces . Characteristics of inter-TMN reference points and interfaces . Interface
23、technology alternatives OS1 systems management considerations 7.4.2 Internet integration considerations . 7.4.3 COBA integration considerations . Directory and naming services OS1 naming and addressing . COBA naming and addressing 7.2.1 7.2.2 7.2.3 Criteria associated with functionalhnformation arch
24、itecture design that 7.3.1 7.3.2 7.4.1 7.4.4 Technology integration issues . 7.5.1 X.500 directory support . 7.5.2 7.5.3 Appendix I . TMN architecture considerations for selected telecommunications managed I . 1 areas Intelligent Networks (INS) I . 1.1 IN activities within the scope of TMN managemen
25、t . I . 1.2 IN concepts I . 1.3 I . 1.4 Mapping of IN distributed functional plane to the TMN logical architecture I . 1.5 Mapping of IN physical plane to the TMN physical architecture 1.2 Transport network . Relationship between TMN and IN concepts 1.2.1 SDH communications examples Page 21 22 24 24
26、 24 24 25 25 28 28 28 31 31 32 34 34 38 39 40 41 41 42 42 43 44 46 46 iv Recommendation M.3013 (02/2000) Recommendation M.3013 CONSIDERATIONS FOR A TELECOMMUNICATIONS MANAGEMENT NETWORK (Geneva, 2000) 1 Scope This Recommendation describes how the Telecommunications Management Network (TMN) functiona
27、l, information and physical architectures, which are defined as fi-ameworks in Recommendation M.3010, can be used to support the requirements, analysis and design efforts necessary to implement TMN(s). This Recommendation provides guideline information that may be useful for TMN designers, architect
28、s and implementers. Many issues are enumerated that may be taken into consideration for implementing, upgrading or expanding a TMN capability. The design of a physical architecture is based upon logical, functional and information architecture specifications. Since multiple physical architectures ma
29、y meet the requirements of the logical architecture, TMN designerdarchitects should consider the following in order to achieve an optimal physical architecture design to be implemented: o determining access and control points with associated interaction models; maintaining necessary interfaces to no
30、n-TMN systems; considering evolution of interface technologies; o establishing system performance requirements; developing system reliability, availability and survivability requirements; identifymg system administration and other system support requirements. o o o o This Recommendation enumerates a
31、 number of considerations (non-exhaustively) in support of designing a physical architecture. This Recommendation also examines emerging technology directions that may support the business requirements of service providers and may also provide support in meeting the needs of the TMN physical archite
32、cture design to be implemented. 2 References 2.1 Structure of TMN documentation Many ITU-T Recommendations apply to TMN applications. This clause identifies the content matter of the various series of Recommendations that relate to TMNs. These Recommendations are continually in the process of expans
33、ion and enhancement to fulfil evolving requirements. Refer to current ITU-T catalogues for latest lists of applicable Recommendations. 2.1.1 TMN overview M.3000. 2.1.2 Architecture M.30lx-series, M.36Ox-series, M.36lx-series, X.70-series. 2.1.3 Interface specification methodology M.3020, G.85 1 .x-s
34、eries. Recommendation M.3013 (02/2000) 1 2.1.4 M.32xx-series, M.3300, M.3400, G.784, G.852.x-series, M.36xx-series. 2.1.5 Management information models M.3 lxx-series, G.774.x-series, G.85x-series, M.3 lxx-series, M.364x-series, Q.82x-series, Q.83x-series, Q.853.x-series, Q.854.x-series, Q.855.x-ser
35、ies, X.75 1 .x-series, G.776.x-series. 2.1.6 Communication services and protocols Q.8 lx-series, Q.28xx-series, X.7 lx-series, Q.94x-series, G.773, G.784. Management requirements, functions and services 3 Definitions Definitions of terms are provided in Recommendation M.3010. 4 Abbreviations This Re
36、commendation uses the following abbreviations: A AD AE ATM BM BML CCAF CCF CMIP CORBA DAP DCF DCN DFP DIB DIT DN DO DSA DSP DUA ECC EM EML Agent Adaptation Device Application Entity Asynchronous Transfer Mode Business Management Business Management Layer Call Control Access Function Call Control Fun
37、ction Common Management Information Protocol Common Object Request Broker Architecture Directory Access Protocol Data Communication Function Data Communication Network Distributed Functional Plane Directory Information Base Directory Information Tree Distinguished Name Directory Object Directory Sys
38、tem Agent Directory System Protocol Directory User Agent Embedded Control Channel Element Management Element Management Layer 2 Recommendation M.3013 (02/2000) EMS FE GDMO GFP IETF IIOP IN INAP IOR IP ISDN IT LAN LDAP M MAF MCF MD MF MIE! MIT MO NE NEF NEL NM NML NSAP ORB os OSF os1 OSIE PE PP PTO Q
39、A Element Management System Functional Entity Guidelines for the Definition of Managed Objects Global Functional Plane Internet Engineering Task Force Internet Inter-Orb Protocol Intelligent Network Intelligent Network Application Protocol Interoperable Object Reference Internet Protocol Integrated
40、Services Digital Network Information Technology Local Area Network Lightweight Directory Access Protocol Manager Management Application Function Message Communication Function Mediation Device Mediation Function Management Information Base Management Information Title Managed Object Network Element
41、Network Element Function Network Element Layer Network Management Network Management Layer Network Service Access Point Object Request Broker Operations System Operations Systems Function Open Systems Interconnection Open Systems Interconnection Environment Physical Entity Physical Plane Public Tele
42、communication Operator Q adaptor Recommendation M.3013 (02/2000) 3 QOS RDN RFC SCEF SCEP SCF SCP SDF SDH SDP SIB SLA SM SMAF SMAP SMF SMK SML SMS SNMP SRF ss7 SSF SSP TCP TL1 TMN TMN-AE UPT VOIP W SF XA Quality of Service Relative Distinguished Name Request for Comment Service Creation Environment F
43、unction Service Creation Environment Point Service Control Function Service Control Point Service Data Function Synchronous Digital Hierarchy Service Data Point SMDS Interface Protocol Service Level Agreement Service Management Service Management Access Function Service Management Access Point Servi
44、ce Management Function Shared Management Knowledge Service Management Layer Service Management System Simple Network Management Protocol Specialized Resource Function Signalling System No. 7 Service Switching Function Service Switching Point Transmission Control Protocol Transaction Language 1 Telec
45、ommunications Management Network TMN-Application Entity Universal Personal Telecommunication Voice over Internet Protocol Workstation Function X Adaptor 5 Conventions None. 4 Recommendation M.3013 (02/2000) 6 General design and implementation considerations 6.1 Introduction The design and implementa
46、tion of a TMN system should consider three important architectures: 1) physical; 2) informational; and 3) functional . These are defined in Recommendation M.3010 and discussed in this Recommendation. The implementation and design of these architectures in a TMN system fulfil business requirements of
47、 an organization. Technologies pertaining to design and implementation should be selected by giving consideration to a business model. Examples of various technologies are presented in this Recommendation. New Recommendations (e.g. functional models and information models) may be developed in the fu
48、ture that support additional business considerations. This clause identifies some architecture aspects that impact the design and implementation of a specific TMN system or component. 6.2 Requirements impacting design and implementation A TMN design and implementation specification should be given w
49、ith the minimum number of requirements that convey the needs of business. In the process of specifymg functional, informational and physical requirements, consideration should be given to (but not limited to) the following: o cost of implementation and life-cycle cost; o selection of a suitable modelling language used to describe requirements, analysis and design. Refer to Recommendation M.3020 for more detailed information; o specimng exposed functionality and information at the reference points that lead to a physical implementation. These specifications should be based on interaction be
