ITU-T M 3010 AMD 1-2003 Principles for a telecommunications management network Amendment 1 TMN conformance and TMN compliance (Amendment 1)《电信管理网修正原则1 电信管理网的一致性和电信管理网遵守M系列 电信管理网和网络.pdf

《ITU-T M 3010 AMD 1-2003 Principles for a telecommunications management network Amendment 1 TMN conformance and TMN compliance (Amendment 1)《电信管理网修正原则1 电信管理网的一致性和电信管理网遵守M系列 电信管理网和网络.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3010 AMD 1-2003 Principles for a telecommunications management network Amendment 1 TMN conformance and TMN compliance (Amendment 1)《电信管理网修正原则1 电信管理网的一致性和电信管理网遵守M系列 电信管理网和网络.pdf（14页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T M.3010TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(12/2003) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Telecommunications management network Princ

2、iples for a telecommunications management network Amendment 1: TMN conformance and TMN compliance ITU-T Recommendation M.3010 (2000) Amendment 1ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUIT

3、S Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.89

4、9 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone network M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exc

5、hange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.301

6、0 (2000)/Amd.1 (12/2003) i ITU-T Recommendation M.3010 Principles for a telecommunications management network Amendment 1 TMN conformance and TMN compliance Summary This amendment contains an updated clause 13, “TMN conformance and TMN compliance“. Source Amendment 1 to ITU-T Recommendation M.3010 (

7、2000) was approved by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure on 14 December 2003. Keywords architecture, conformance and compliance, interfaces, reference model, telecommunications management network (TMN) ii ITU-T Rec. M.3010 (2000)/Amd.1 (12/2003) FOREWORD The

8、 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 questions and issuing Reco

9、mmendations 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 on these topics. The

10、 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 expression “Admini

11、stration“ 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 applicability) and comp

12、liance 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 the Recommendation

13、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 applicability of claimed I

14、ntellectual 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 implement this Recommendat

15、ion. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission

16、of ITU. ITU-T Rec. M.3010 (2000)/Amd.1 (12/2003) iii CONTENTS Page 1 Scope 1 2 Additions 1 2.1 Clause 2 (References). 1 3 Changes 1 3.1 Clause 13 (TMN conformance and TMN compliance) 1 13 TMN conformance and TMN compliance . 1 13.1 Introduction 1 13.2 TMN conformance definitions . 1 13.3 TMN interfa

17、ce protocol conformance 2 13.4 TMN interface information conformance 3 13.5 TMN compliance 5 ITU-T Rec. M.3010 (2000)/Amd.1 (12/2003) 1 ITU-T Recommendation M.3010 Principles for a telecommunications management network Amendment 1 TMN conformance and TMN compliance 1 Scope This amendment contains ex

18、tensions to the 2000 version of ITU-T Rec. M.3010. 2 Additions 2.1 Clause 2 (References) Add the following references: 21 ITU-T Recommendation X.722 (1992), Information technology Open Systems Interconnection Structure of management information: Guidelines for the definition of managed objects. 22 I

19、TU-T Recommendation Q.816 (2001), CORBA-based TMN services. 23 ITU-T Recommendation Q.816.1 (2001), CORBA-based TMN services: Extensions to support coarse-grained interfaces. 24 ITU-T Recommendation X.780 (2001), TMN guidelines for defining CORBA managed objects. 25 ITU-T Recommendation X.780.1 (200

20、1), TMN guidelines for defining coarse-grained CORBA managed object interfaces. 3 Changes 3.1 Clause 13 (TMN conformance and TMN compliance) Replace the entire clause with the following: 13 TMN conformance and TMN compliance 13.1 Introduction This clause defines TMN conformance and TMN compliance. T

21、MN conformance, which is testable, relates to the interfaces between TMN physical blocks. TMN compliance relates to the TMN architecture, principles and functions. 13.2 TMN conformance definitions The goal of TMN conformance is to increase the probability that different systems within a TMN will be

22、able to interoperate, that TMNs in different service/network providers administrations will be able to interoperate as much as the administrations agree to do, and that a customers system and a service providers TMN will be able to interoperate as much as the two agree to interoperate. 2 ITU-T Rec.

23、M.3010 (2000)/Amd.1 (12/2003) The definitions can, in principle, be applied to Q, X or F interfaces. However, present requirements and standards for the F interface are in the formative stage. Therefore, the definitions in this clause apply to Q and X interfaces. However, this clause enumerates TMN

24、conformance definitions which are testable. The TMN supports two general-purpose paradigms: the CMIP/OSI system management paradigm and the CORBA framework paradigm. TMN conformance to either of these paradigms is a condition for systems interworking within these paradigms but is not sufficient to g

25、uarantee interoperability within the paradigm. Interfaces are not interoperable between the paradigms. It is always recommended that the purchaser/user of these systems perform some form of verification testing to determine that any two systems, claiming any type of TMN conformance, interoperate. In

26、teroperability testing must include testing of the interface protocols, the shared/exposed information over those interfaces, and the interface functionality of the system. Definitions associated with TMN interface conformance are provided as follows: TMN interface protocol conformance definition; l

27、evels of TMN interface information conformance. The TMN interface specification must be documented, publicly available, and licensable at a reasonable price on a non-discriminatory basis. 13.3 TMN interface protocol conformance An interface (Q, X) of a system is TMN interface protocol conformant if

28、and only if all of the following are met: 1) The interface uses a communications protocol stack specified by ITU-T Recommendations for TMN. Currently, the communications protocol stack must conform to ITU-T Rec. Q.811 12 for lower layer protocols and ITU-T Rec. Q.812 13 for upper layer protocols. A

29、valid and consistent selection of protocols must be chosen from the choices enumerated in ITU-T Recs Q.811 12 and Q.812 13. In particular, valid selection must be made for the CMIP/OSI System management or CORBA framework paradigms. 2) For the CMIP/OSI system management paradigm, the system interfac

30、e documentation specifies the International Standardized Profiles (ISPs), where they exist, enumerated in ITU-T Recs Q.811 12 and Q.812 13 which are supported. Conformance with ITU-T Recs Q.811 12 and Q.812 13 is specified with respect to specific ISPs. Management Communications profiles are selecte

31、d based on types of TMN Management Services that need to be provided over the interface as per the corresponding tables in ITU-T Recs Q.811 12 and Q.812 13. Standardized Implementation Conformance Statements in the form of Protocol Implementation Conformance Statements (PICS) (ITU-T Rec. X.290 7), a

32、nd Protocol Implementation Extra Information For Testing (PIXIT) (ITU-T Rec. X.290 7) must be provided. 3) For the CORBA framework paradigm, the systems must support the protocol and services specified in the ITU-T Q.816-series Recommendations as appropriate. 4) The system interface documentation sp

33、ecifies if the interface can be used as an X interface or a Q interface. 5) The system interface can act in the appropriate role(s) for the protocol over that interface (e.g., agent and/or manager for CMIP, initiator/responder for FTAM, server and/or client for the CORBA framework). The system inter

34、face documentation specifies the roles in which the system can act. 6) If the protocol stack selected in 1) requires information modelling, then a standardized information modelling technique must be used. For the CMIP/OSI system management paradigm this information modelling shall follow ITU-T Recs

35、 X.720 5 and X.722 21. In ITU-T Rec. M.3010 (2000)/Amd.1 (12/2003) 3 the CORBA framework, more than one paradigm choice is provided for modelling. For the CORBA framework paradigms, the information modelling shall follow the ITU-T X.780-series Recommendations as appropriate. The framework chosen sha

36、ll be specified in the model. 7) If GDMO-based information models are implemented, the system interface must meet one of the levels of TMN interface information conformance as documented in 13.4. 13.4 TMN interface information conformance A system interface may make a claim, by level, of information

37、 conformance for each management functionality that the interface supports. It is expected that this management functionality will be by information model document. 13.4.1 Level A interface information conformance An interface of a system is Level A interface information conformant, for this managem

38、ent functionality, if and only if all of the following are met: 1) The system interface is TMN interface protocol conformant i.e., meets the criteria in the definition in 13.3 for either paradigm. 2) The managed-object classes the system interface supports are defined in the applicable information m

39、odels specified in ITU-T Recommendations relevant to this management functionality. The system interface documentation shall list the Recommendations that define the specified information models with the inclusion of the version number and date. For the CMIP/OSI system management paradigm, the infor

40、mation models shall be defined using ITU-T Recs X.720 and X.722. For the CORBA framework paradigm, the information models shall be defined using X.780 series as appropriate. For the CMIP/OSI system management paradigm, standardized Implementation Conformance Statements in the form of Managed Objects

41、 Conformance Statements (MOCS), and Management Information Conformance Statements (MICS), and Managed Relationship Conformance Statement (MRCS), if applicable, must be provided (ITU-T Rec. X.724 4). For the CORBA framework paradigm, implementation conformance statements proformas following the ITU-T

42、 X.781-series Recommendations must be provided. 3) If the system interface uses managed-object classes which have been subclassed from classes enumerated in 2) in this definition, for the sole purpose of providing for missing model functionality, then these managed-object classes must be defined fol

43、lowing the strict inheritance rules as specified in ITU-T Rec. X.720 5 for the CMIP/OSI system management paradigm or in the ITU-T X.780-series Recommendations as appropriate for the CORBA framework paradigm. 4) Any additional object classes other than those enumerated in 2) in this definition, that

44、 are needed to extend the ITU-T information model due to missing model functionality, shall have accompanying documentation which fully specifies the information models with the inclusion of the version number and date. For the CMIP/OSI system management paradigm separate standardized Implementation

45、 Conformance Statements in the form of Managed Objects Conformance Statements (MOCS), and Management Information Conformance Statements (MICS), and Managed Relationship Conformance Statement (MRCS), if applicable, must be provided (ITU-T Rec. X.724 4) for these object classes. For the CORBA framewor

46、k paradigm, implementation conformance statements proformas following the ITU-T Rec. X.781-series Recommendations must be provided. 4 ITU-T Rec. M.3010 (2000)/Amd.1 (12/2003) 13.4.2 Level B interface information conformance An interface of a system is Level B interface information conformant, for th

47、is management functionality, if and only if all of the following are met: 1) The system interface is TMN interface protocol conformant i.e., meets the criteria in the definition in 13.3 for either paradigm. 2) For the CMIP/OSI system management paradigm, the information models shall be defined using

48、 ITU-T Recs X.720 5 and X.722 21. For the CORBA framework paradigm, the information models shall be defined using the ITU-T X.780-series Recommendations as appropriate. For both paradigms, if the managed-object classes the system interface supports are defined in the applicable information models sp

49、ecified in other de jura standards bodies (e.g., ETSI, T1, TTC) or de facto standards bodies (e.g., ATM Forum, TMF, 3GPP). The system interface documentation shall list the documents that define the specified information models with the inclusion of the version number and date. For the CMIP/OSI system management paradigm, standardized Implementation Conformance Statements in the form of Managed Objects Conformance Statements (MOCS), and Management Information Conformance Statements (MICS), and Managed Relationship