1、 STD-ETSI TR 101 b48-ENGL 1797 M 3400855 03b534 294 m TR 1 O1 648 1.2.1 (1999-02) Technical Report Telecommunications Management Network (TMN); Managed object modelling guidelines COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTDmETSI TR LO1 648-EN
2、GL 3999 m 3400855 0336535 120 m 2 TR 1 O1 648 VI .2.1 (i 99942) Reference RTWTMN-00029 (9cOOios.PDF) Kevwords ETSI Postai adxess F-O6921 Sophia Antipolis Cedex - FRANCE office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Siret No 348 623 562 00017 - NAF 742 C Association but n
3、on lucrai enregistre ia Cous-PrBhture de Grasse (06) No 7W88 Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 internet secretariat etsi.fr Individual copies of this ETSI deliverable can be downloaded from http:/www.etsi.org If you find errors in the present document, send your comment lo: editor etsi.
4、f r Coavriuh t Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in ail media. Q European Telecornunications Standards IWtiNte 1999. ETSI All lights reserved. COPYRIGHT European Telecommunications Sta
5、ndards InstituteLicensed by Information Handling ServicesSTDmETSI TR 102 b48-ENGL 2999 3400855 037b53b Ob7 S TR 101 648 V1.2.1 (199902) Contents Intellectual Property Rights 5 Foreword . 5 1 Scope . 6 2 References . 3 Definitions and abbreviations 7 3.1 Definitions . 7 3.2 Abbreviations 7 4 5 Pre-In
6、formation Modelling Work 8 5.1 Introduction . 8 5.2 5.2.1 General . 9 5.2.2 5.2.2.1 Tasks, infonnation and relationships 9 5.2.2.2 Describe TMN management services task 10 5.2.2.3 Describe TMN management context task . 10 5.2.2.4 Perform information modelling tssk . 10 5.2.2.5 Consolidate available
7、infonnation task 10 5.2.2.6 Define management information schema task 10 5.3 The Ensemble - a specification framework 11 5.3.1 General . 11 5.3.2 Ensemble structure . 11 5.3.2.1 Management context 12 5.3.2.1.1 Management view and level of abstraction . 12 5.3.2.1.2 Resources 13 5.3.2.1.3 Functions 1
8、4 5.3.2.2 Information model 14 5.3.2.3 Scenarios 14 5.4 5.4.1 Introduction 14 5.4.3 Using RM-ODP viewpoints in a specification design methodology . . 16 5.5 Additional Information 16 5.5.1 Representation of structure 16 5.5.2 Goals of the pre-information modelling work 16 5.5.3 Reference material .
9、. 17 6 Principles for the application of GDMO 17 Furpose and Structure of Modelling Guidelines 8 M.3020 TMN Interface Definition Methodology 9 The definition process 9 ODP based approach (ITU-T G.851-1) - Methodology overview . 14 5.4.2 RM-ODP viewpoint descriptions . . 15 6.1 6.2 6.2.1 6.2.2 6.2.3
10、6.2.4 6.3 6.3.1 6.3.2 6.3.3 6.4 6.4.1 6.4.2 6.5 6.6 6.6.1 6.6.2 introduction . 17 Use of Attributes 17 Value Set Specification for Attributes . 17 Specifying Required, Permitted and Supported Values . 18 Guidelines for Attribute-Value Set Selection . 18 General Attribute Guidelines . 19 Use of Inher
11、it ance 19 General Inheritance Guidelines 19 Principles and Guidelines for Instantiable Classes . 19 Principles and Guidelines for Uninstantiable Classes 19 . 20 Multiple Inheritance Rules and Guidelines 20 Multiple Inheritance . 21 Use of Allomorphism 21 Use of Relationships 22 General Rules and Gu
12、idelines 22 Modellhg Relations with Attributes 22 Use of Multiple Inheritance . ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD-ETSI TR LO1 b48-ENGL 1999 = 3400855 037b537 TT3 W 4 TR 101 648 V1.2.1 (199902) 6.6.3 6.6.4 6.7 6.8 6.9 6.9.1 6.9.
13、2 6.10 6.10.1 6.10.2 Modelling Relations with Managed Object Classes . 22 Modelling Relations with Name Bindings . 23 Use of ptionality Behaviour Specification 25 Guidelines and Principles for Class Invariants . 25 Behavioural Preconditions and Postconditions 26 Use of Packages . 26 Mandatory Packag
14、es 26 Conditional Packages (X.720 subclause 5.1.5) 26 Use of StructuMg 24 Bibliography . 28 History 32 ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD.ETS1 TR 101 bq-ENGL 1999 3400855 037b538 93T TR 101 648 V1.2.1 (199942) 5 Intellectual Pro
15、perty Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in SR o00 314: “Intellectual Property Rights (IPRs); Essen
16、tial, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/www.etsi.org/ipr). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, h
17、as been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in SR o00 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technica
18、l Committee Telecommunications Management Network 0. It is anticipated that the present document will continue to evolve as ETSI Working Groups gain experience in the specification of TMN interfaces. ETSI intends to review and update these guidelines on a regular basis. ETSI COPYRIGHT European Telec
19、ommunications Standards InstituteLicensed by Information Handling Services. STDeETSI TR LO1 648-ENGL 1779 H 3400855 0376537 876 TR 1 O1 648 V1.2.1 (1 999-02) 6 1 Scope The present document provides guidelines for the definition of additional Managed Object Classes, the use of existing Managed Object
20、 Class definitions and the inclusion of these objects in existing inheritance and containment hierarchies. The present document: Provides general rules for defiing Managed Objects. Provides general rules for defining Generic Object Classes. Provides additional Guidelines on the use of GDMO. Identifi
21、es relevant staudards containing modelling guidelines, and identifies which clauses are recommended for use in ETSI models (for example where options exist). The present document does not: Imply any specific system implementation. Include testing the Information model. 2 References The following doc
22、uments contain pvisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. 0 For a
23、 non-specific reference, the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same ITU-T Recommendation M.3 100: “Generic Network information Model (1 St revision)“. ITU-T Recommendation M.3020: “TMN interface speci
24、fication methodology“. Void. ITU-T Recommendation X.700: “Management framework for Open Systems Interconnection (OSO for CCI“ applications“. -T Recommendation X.701: “Information technology - Open Systems Interconnection - Systems management overview“. ITU-T Recommendation X.720: “Information techno
25、logy - Open Systems Interconnection - Structure of management information: Management information model“. -T Recommendation X.721: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management information“. ITU-T Recommendation X.722: “Informa
26、tion technology - Open Systems Interconnection - Structure of Management Information: Guidelines for the definition of managed objects“. Void. Void. Void. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD*ETSI TR 101 b48-ENGL 1999 W 3400855 03
27、7b540 598 TR 101 648 V1.2.1 (19ssO2) 7 1121 ETR 230 “Network Aspects (NA); Telecommunications Management Network (TMN); TMN standardisation overview“. -T Recommendation M.3010: “Principles for a Telecommunications management network. ISOIIEC 10165-1: “Information technology - Open Systems Interconne
28、ction - Sucture of management information: Management Infomtion Model“. ISO/zEC 10165-2: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management information“. -T Recommendation X.710 Information technology - Open Systems Interconnection
29、- Common Management information Service ITU-T Recommendation G.85 1-1: “Management of the transport network - Application of the RM-ODP framework“. u31 u41 u51 161 u71 3 3.1 Definitions and abbreviations Definitions For the purposes of the present document, the following temis and definitions apply:
30、 standards: this generic term is used in the present document to refer to -R Recommendations, ETSI ETSs ENS and Ems, ECMA TRs, ISO/IEC standards and EWOS TRs. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN. 1 CMIP CMIS DMI ECMA E/R ETR ETS ETSI EUR
31、ESCOM EWOS GDMO IDL IEC IS0 ITU ITU-T LU MF MFS MIM MO MOCS MS NMP OMG OMT os1 PICS Abstract Syntax Notation One Common Management Information Protocol Common Management Information Service Definition of Management Information European Computer Manufacturers Association Entity -Relationship ETSI Tec
32、hnical Report European Telecommunication Standard European Telecommunications Standards Institute European Institute for Research and Strategic Studies in Telecommunications European Workshop for Open Systems Guidelines for the Definition of Managed Objects interface Description Language Internation
33、al Electro-technical Commission International Organization for Siandardization Intemationai Telecommunication Union Telecommunications sector Logical layered Architecture Management Function Management Function Set Management Information Model Managed Object Managed Object Conformance Statement Mana
34、gement Service Network Management Forum Object Management Group Object Modelling Technique Open Systems Interconnection Protocol Implementation Conforniance Statement ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services8 PNO Public Network Operator
35、RM-ODP SMF Systems Management Function SMI Structure of Management information SNMP Sile Network Management Protocol TMN Telecommunications Management Network TR Technical Report Reference Model for Open Distributed Processing TR 101 648 V1.2.1 (199942) 4 Purpose and Structure of Modelling Guideline
36、s The objective of the present document is to provide guidance to those ETSI Working Groups producing TMN Management Information Models (MIM). It aims to: enable models developed by different groups to co-exist; assist in producing consistency across dels developed by different groups. The use of th
37、e guidelines is intended to produce Managed Object (MO) models that are implementable and reusable. It is therefore important to reuse the work of others and develop models in such a way that they can themselves be reused. It is intended that these modelling guidelines should be “Methodology Neutral
38、“. These guidelines assume that whenever possible and appmpriate, the ITU-T Recommendation X.700 4 Systems Management or ODMA Recommendations wiil be used as a basis of TMN managed object modelling. An overview of the relevant lTU-T Recommendation X.700 4 can be found in ETR 230 121 TMN Standardizat
39、ion Overview. The guidelines start by considering methods for requkments capture, they go on to consider Information and Dynamic Aspects of information modelling. The use of the NMP ensemble approach for documenting information models is considered, together with the use of Class libraries. This is
40、followed by a consideration of principles for GDMO implementation. Consideration of other protocols to be used in the evolving Testing the information model is considered to be outside the scope of these guidelines. is for further study. 5 Pre-Information Modelling Work 5.1 I nt roduction The develo
41、pment of Management Information Models is just one part of the activities involved in the definition and development of TMNs. There are several models of software system (waterfall, spiral) which distinguish between different activities. There is a consensus that eliciting and analysis of the needs
42、and constraints expressed by the procurers of the system is part of such activities. This activity can have names such are requirement capture, requirement definition to name but a few. If we consider management information modelling to be a specificatioddesign activity it is natural to thii that re
43、quirements related activity precedes it. This clause briefly discusses the requirement related activities which typically will take place, in part, at least prior to management information modelling in a TMN context. The origins of requirements on Th4N systems that drive the definition of informatio
44、n models are wide and varied. It is not appropriate to address such philosophical matters here. It is assumed that, at a point in the development of TMN systems or standards, the scope of a management problem is defied at a sufficient level of detail to allow the modelling of management information
45、as a set of managed objects. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD=ETSI TR LOL b48-ENGL 3999 m 3400855 0376542 3b0 m TR 101 64 V1.2.1 (1 99-2) 9 Information about a management problem scope cm be organized in a number of ways which
46、 provide input to the management information modelling activity. These include: Definition of Management Services, etc. following ITU-T Recommendation M.3020 2. Definition of Management Functions, etc. following the Ensemble concept defined by NMP. Application of Open Distributed Processing (ODP) sy
47、stemview-points following IW-T Recornmendation G.851-1 17. Ail of these approaches have a number of features in common. The person modelling defines: Entities (Resources) that will be responsive to requests to engage in their magement. 0 Functions of people and machines which request entities to eng
48、age in management activity to achieve particular management goals. Typical entities are telephone exchange switches, cables for the transport of telephone traffic, counters representing the volume of traffic carried by a particular circuit, etc. It has been popular to categorize functions into those
49、 for configuration management, fault management, performance management, security management and accounting management. Management goals are states of the entities that the owners of the entities wish to estabiish and maintain. For example, a PNO running a particuiar network requires network equipment mis-operations to be unambiguously identified or a service subscriber wants to be notified of the duration of a service interruption affecting it. Before tackling a management information modelling task, available requirement statements should be
