1、 International Telecommunication Union ITU-T M.3020TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2011) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Management interface specification methodology Recommendation ITU-T M.3020
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.759 Common channel signal
3、ling 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 public telephone network M
4、.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.3599Integrated services digital networks M.3600M.3999 Common channel signalling systems M.400
5、0M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3020 (07/2011) i Recommendation ITU-T M.3020 Management interface specification methodology Summary Recommendation ITU-T M.3020 describes the management interface specification methodology (MISM). It describ
6、es the process to derive interface specifications based on user requirements, analysis and design (RAD). Guidelines are given on RAD using unified modelling language (UML) notation; however, other interface specification techniques are not precluded. The guidelines for using UML are described at a h
7、igh level in this ITU-T Recommendation. History Edition Recommendation Approval Study Group 1.0 ITU-T M.3020 1992-10-05 2.0 ITU-T M.3020 1995-07-27 4 3.0 ITU-T M.3020 2000-02-04 4 4.0 ITU-T M.3020 2007-07-22 4 5.0 ITU-T M.3020 2008-07-29 4 6.0 ITU-T M.3020 2009-05-14 2 7.0 ITU-T M.3020 2010-09-06 2
8、8.0 ITU-T M.3020 2011-07-14 2 ii Rec. ITU-T M.3020 (07/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-
9、T) is a permanent organ of ITU. 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 Telecommunication Standardization Assembly (WTSA), which meets every four ye
10、ars, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations 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 nec
11、essary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. Howev
12、er, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or 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
13、equivalents are used to express requirements. The use of such words does not suggest that compliance with 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
14、 a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or 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, IT
15、U had not received notice of intellectual property, protected by patents, which may be required to implement 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.it
16、u.int/ITU-T/ipr/. ITU 2012 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3020 (07/2011) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Term
17、s defined in this Recommendation . 2 4 Abbreviations 3 5 Conventions 4 6 Requirements for methodology and notational support 4 7 Methodology . 5 7.1 General considerations . 5 7.2 Application and structure of the methodology . 5 7.3 Detailed methodology 5 8 Management interface specifications . 8 9
18、Traceability in MISM process 8 10 Documentation structure . 8 Annex A Requirements . 9 A.1 Conventions 9 A.2 Requirements template . 12 A.3 Simplified requirements template . 14 Annex B Analysis . 16 B.1 Conventions 17 B.2 Analysis template . 19 B.3 IOC properties and inheritance . 28 Annex C MISM U
19、ML repertoire 30 C.1 Introduction 30 C.2 Basic model elements . 30 C.3 Stereotypes . 33 C.4 Association classes . 40 C.5 Abstract class 40 C.6 Application of and 41 Annex D Design 42 Annex E Information type definitions type repertoire . 43 E.1 Basic types 43 E.2 Enumerated type . 43 E.3 Complex typ
20、es 43 E.4 Useful types 43 E.5 Keywords 44 iv Rec. ITU-T M.3020 (07/2011) Page Annex F Guidelines on IOC properties, inheritance and entity import 45 F.1 IOC property . 45 F.2 Inheritance 46 F.3 Entity (interface, IOC and attribute) import . 46 Appendix I Requirements example . 47 Appendix II Analysi
21、s example 50 Appendix III Comparison with Recommendation ITU-T Z.601 58 Appendix IV Issues for further study 59 IV.1 SOA 59 IV.2 UML . 59 IV.3 Visibility . 59 IV.4 Type definitions 59 Appendix V Additional UML usage samples . 60 V.1 Proxy class 60 Appendix VI Guidelines on requirements numbering 62
22、Bibliography. 63 Rec. ITU-T M.3020 (07/2011) 1 Recommendation ITU-T M.3020 Management interface specification methodology 1 Scope This Recommendation describes the management interface specification methodology (MISM). It describes the process to derive machine-machine interface specifications based
23、 on user requirements, analysis and design (RAD). Guidelines are given on RAD using unified modelling language (UML) notation; however, other interface specification techniques are not precluded. The guidelines for using UML are described in this Recommendation. An interface specification addresses
24、management service(s) defined in ITU-T M.3200 and/or supporting the management processes defined in ITU-T M.3050.x series. Such a specification may support part of or one or more management services. The management services comprise of management functions. These functions may reference those define
25、d in ITU-T M.3400 or the processes defined in ITU-T M.3050.x series, specialized to suit a specific managed area, or new functions may be identified as appropriate. The methodology is applicable to both the traditional manager/agent style of management interfaces ITU-T M.3010 and the service oriente
26、d architecture (SOA) principles adopted for the management architecture of next generation networks ITU-T M.3060. 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
27、of publication, the editions indicated were valid. All Recommendations and other references are subject 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 li
28、st of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management
29、network. ITU-T M.3050.x Recommendation ITU-T M.3050.x (2007), enhanced Telecom Operations Map (eTOM). ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the management of next generation networks. ITU-T M.3200 Recommendation ITU-T M.3200 (1997), TMN management services and teleco
30、mmunications managed areas: Overview. ITU-T M.3400 Recommendation ITU-T M.3400 (2000), TMN management functions. ITU-T Q.812 Recommendation ITU-T Q.812 (2004), Upper layer protocol profiles for the Q and X interfaces. ITU-T X.680 Recommendation ITU-T X.680 (2008) | ISO/IEC 8824-1:2008, Information t
31、echnology Abstract Syntax Notation One (ASN.1): Specification of basic notation. ITU-T X.681 Recommendation ITU-T X.681 (2008) | ISO/IEC 8824-2:2008, Information technology Abstract Syntax Notation One (ASN.1): Information object specification. 2 Rec. ITU-T M.3020 (07/2011) ITU-T X.722 Recommendatio
32、n ITU-T X.722 (1992) | ISO/IEC 10165-4:1992, Information technology Open Systems Interconnection Structure of management information: Guidelines for the definition of managed objects. ITU-T Z.100 Recommendation ITU-T Z.100 (2007), Specification and Description Language (SDL). OMG UML OMG: Unified Mo
33、delling Language Specification, Version 1.5. A list of non-normative references can be found in the Bibliography. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms from ITU-T M.3010: user; management service; management function set. This Recommendation uses the
34、following terms from OMG UML: activity diagram; actor; association; class; class diagram; classifier; collaboration diagram; composition; modelElement; sequence diagram; state diagram; stereotype; use case. This Recommendation uses the following term from ITU-T M.3060: reference point. 3.2 Terms def
35、ined in this Recommendation This Recommendation defines the following terms: 3.2.1 agent: Encapsulates a well-defined subset of management functionality. It interacts with managers using a management interface. From the managers perspective, the agent behaviour is only visible via the management int
36、erface. NOTE Considered equivalent to IRPAgent b-3GPP TS 32.150. 3.2.2 information object class: Describes the information that can be passed/used in management interfaces and is modelled using the stereotype “Class“ in the UML meta-model. For a formal definition of information object class and its
37、structure of specification, see Annex B. Rec. ITU-T M.3020 (07/2011) 3 3.2.3 information service: Describes the information related to the entities (either network resources or support objects) to be managed and the way that the information may be managed for a certain functional area. Information s
38、ervices are defined for all IRPs. NOTE Considered identical to the definition of information service found in b-3GPP TS 32.150. 3.2.4 information type: Specification of the type of input parameters of operations. 3.2.5 integration reference point: An architectural concept that is described by a set
39、of specifications for the definition of a certain aspect of the management interface, comprising a requirements specification, an information service specification, and one or more solution set specifications. NOTE Considered identical to the definition of IRP found in b-3GPP TS 32.150. 3.2.6 manage
40、ment goals: High-level objectives of a user in performing management activities. 3.2.7 management interface: The realization of management capabilities between a manager and an agent, allowing a single manager to use multiple agents and a single agent to support multiple managers. NOTE Q, C2B/B2B an
41、d Itf-N (3GPP) are examples of management interfaces. 3.2.8 management role: Defines the activities that are expected of the operational staff or systems that perform telecommunications management. Management roles are defined independent of other components, i.e., telecommunications resources and m
42、anagement functions. 3.2.9 management scenario: A management scenario is an example of management interactions from a management service. 3.2.10 manager: Models a user of agent(s) and it interacts directly with the agent(s) using management interfaces. Since the manager represents an agent user, it
43、gives a clear picture of what the agent is supposed to do. From the agent perspective, the manager behaviour is only visible via the management interface. NOTE Considered equivalent to IRPManager b-3GPP TS 32.150. 3.2.11 matching information: Specification of the type of a parameter (possibly refere
44、nce to IOC or attribute of IOC). 3.2.12 protocol-neutral specification: Defines the management interfaces in support of management capabilities without concern for the protocol and information representation implied or required by, e.g., CORBA and XML. 3.2.13 protocol-specific specification: Defines
45、 the management interfaces in support of management capabilities for one specific choice of management technology (e.g., CORBA). NOTE Considered equivalent to solution set b-3GPP TS 32.150. 3.2.14 telecommunications resources: Telecommunications resources are physical or logical entities requiring m
46、anagement, using management services. 4 Abbreviations This Recommendation uses the following abbreviations: 3GPP 3rd Generation Partnership Project ADM Administrative (usage: requirements category) ASN.1 Abstract Syntax Notation One CM Conditional-Mandatory 4 Rec. ITU-T M.3020 (07/2011) CO Condition
47、al-Optional CON Conceptual (usage: requirements category) CORBA Common Object Request Broker Architecture FUN Functional (usage: requirements category) GDMO Guidelines for the Definition of Managed Objects IDL Interface Definition Language IOC Information Object Class IRP Integration Reference Point
48、 IS Information Service MISM Management Interface Specification Methodology NA Not Applicable NE Network Element NON Non-functional (usage: requirements category) OMG Object Management Group OO Object Oriented OSI Open Systems Interconnection SDL Specification and Description Language SOA Service Or
49、iented Architecture SS Solution Set TS Technical Specification UML Unified Modelling Language XML eXtensible Markup Language 5 Conventions Clause A.1 contains conventions applicable to the requirements phase. Clause B.1 contains conventions applicable to the analysis phase. 6 Requirements for methodology and notational support In developing the methodology and choosing a notation, the following requirements apply: 1)
