ITU-T Z 360-1997 Graphic GDMO A Graphic Notation for the Guidelines for the Definition of Managed Objects - Series Z Programming Languages Man-Machine Language - Specification of t.pdf

1、 STD-ITU-T RECMN Z.3bO-ENGL 1997 48b257L Ob41732 813 INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU 2.360 SERIES Z: PROGRAMMING LANGUAGES Man-machine language - Specification of the man- machine interface (05/97) Graphic GDMO: A graphic notation for the G

2、uidelines for the Definition of Managed Objects ITU-T Recommendation 2.360 (Previously CCIlT Recommendation) ITU-T Z-SERIES RECOMMENDATIONS PROGRAMMING LANGUAGES Specification and Description Language (SDL) Applicability of formal Description Techniques Message Sequence Chart CC High Level Language

3、(CHILL) MAN-MACHINE LANGUAGE General principles Basic syntax and dialogue procedures z. 100-2.109 Z. 1 IGZ. 1 19 z. 120-2.199 2.200-Z.299 2.300-2.499 2.300-2.309 2.310-2.319 Extended MML for visual display terminals 2.320-2.329 Miscellaneous 2.400-2.599 Forfurther details, please refer to ITU-T Lisi

4、 of Recommendations. ITU-T RECOMMENDATION 2.360 GRAPHIC GDMO: A GRAPHIC NOTATION FOR THE GUIDELINES FOR THE DEFINITION OF MANAGED OBJECTS Summary This Recommendation prescribes a graphic notation to provide an overview of GDMO/GRM specifications. GDMO, Guidelines for the Definition of Managed Object

5、s, is a formalism defined in Recommendation X.722 to define managed objects in Telecommunications Management Network (TMN). Attributes for representing relationships are defined in Recommendation X.732. The GDMO formalism is extended with a general relationship notation in Recommendation X.725 (Gene

6、ral Relationship Model). The overall object structure is defined by GDMO/GRM, while the syntax of the data is defined using Abstract Syntax Notation One (ASN.l), Recommendations X.208 or X.680. The three languages are widely used by many ITU Study Groups for the specification of managed objects for

7、many application areas. The languages are purely alphanumeric and the alphanumeric specifications using GDMOIGWASN. 1 are hard to overview. Current Recommendations using GDMO/GRM use various kinds of informal illustrations to provide overviews of different aspects of the specifications. However, the

8、y frequently use the same symbol for different notions, different symbols for the same notion, and can sometimes be misleading as to the contents of the specifications. Therefore, a standardized graphic notation was felt needed. The graphic notation shall be true to the notions of the alphanumeric n

9、otations. This Recommendation is based on: 0 an approved Requirement document, found in Appendix II; evaluation of some existing graphic notations, which did not meet the requirements; trial use on several Recommendations and other application areas. Source ITU-T Recommendation 2.360 was prepared by

10、 ITU-T Study Group 10 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 6th of May 1997. Keywords Attributes; General Relationship Model; Guidelines for the Definition of Managed Objects; Managed Object Class; Relationship Class. Recommendation 2.360 (05/97) 1 STD-ITU-T R

11、ECMN Z-3bO-ENGL 1997 48b257L Ob41735 522 = FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommuni- cations. The Telecommunication Standardization Sector (IT-T) is a permanent organ of the IT. The IT-T is responsible for studying tech

12、nical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups whic

13、h, 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 Resolution No. 1. In some areas of information technology which fall within IT-Ts purview, the necessary standards are prepared on a co

14、llaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPER= RIGHTS The IT draws attention to the possibility that the practice or i

15、mplementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The IT takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by IT members or others outside of the Recommendation development p

16、rocess. As of the date of approval of this Recommendation, the IT had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore s

17、trongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation 2.360

18、 (05/97) CONTENTS Introduction 1.1 scope 1.2 Terminology . Example usage of the graphic notation Graphic notation for templates . Managed Object Class template 4.2 Package template 4.3 Name Binding template 4.4 Connections References by attributes . Relationship Class template . Long labels . Symbol

19、s 4.1 Appendix I . Graphic GDMO Instantiation Appendix II . Requirements on Graphic GDMO . II.1 Background . Use of Graphic GDMO/GRM Requirements on a Graphic GDMO . The Graphic GDMO shall minimally provide the following information The labels used in Graphic GDMO shall satisfy the following require

20、ments specifications II.2 iI.3 II.4 iI.5 II.6 II.7 The Graphic GDMO specifications shall provide an overview of Alphanumeric GDMO/GRM Graphic GDMO may provide extensions illustrating use and implications of GDMO/GRM specifications Page 1 1 1 2 6 8 8 9 10 11 12 13 14 14 18 18 19 19 20 20 21 21 . Reco

21、mmendation 2.360 (05/97) 111 Recommendation 2.360 GRAPHIC GDMO: A GRAPHIC NOTATION FOR THE GUIDELINES FOR THE DEFINITION OF MANAGED OBJECTS (Geneva, I99 7) 1 Introduction 1.1 Scope This Recommendation provides a graphic notation for a subset of the information provided in the templates defined in Re

22、commendation X.722, Information technology - Open Systems Interconnection - Structure of management information: Guidelines for the definition of managed objects. The purpose of the graphic notation is to provide an overview of TMN specifications for TMN specifiers, implementors and users. The graph

23、ic notation provides an overview of what definitions exist and the relationships between these definitions. To accomplish this overview, not all information provided in the templates has to be presented in the graphic notation. Therefore, the graphic notation covers only a subset of the information

24、found in and required by the templates. If inconsistencies between Alphanumeric GDMOIGRM and Graphic GDMO specifications are discovered, the alphanumeric specification is normative. The graphic notation allows both detailed and compact depictions of specifications. The compact notation is expected t

25、o be the most useful one for ordinary users. The detailed notation is a tool for explaining the detailed relationships between the statements of the specifications and to show the relationships to the alphanumeric notation. Typically, a graph may depict all information in one Recommendation. However

26、, the specifier is free to include and exclude what he finds convenient, graphs can overlap, and there is no Recommendation on what shall be included in one graph or not. A Graphic GDMO graph should be provided with a title and text indicating how this graph is delimited relative to the alphanumeric

27、 specifications to which it refers. Clause 2 introduces the graphic notation and concludes with a made-up example (see Figure 4) using the most compact form of the notation. Clause 3 provides a real world example from the area of Access Control. Clauses 4 and 5 provide a more detailed explanation of

28、 the example in Clause 2, Figure 4, and expansion from the compact notation to show all the details. Clause 6 provides an extension of the graphic notation to the Relationship Class template defined in Recommen- dation X.725. Appendix I extends the graphic notation for classes with a separate, howev

29、er, similar graphic notation for depicting instances. Appendix Ii contains the requirements which Graphic GDMO was developed to meet. 1.2 Terminology This Recommendation defines the following terms: 1.2.1 for Graphic GDMO/GRh4 is Graphic GDMO. graphic GDMOKRM: This is used as a full name of the grap

30、hic notation for GDMOIGRM. The short name Recommendation 2.360 (05I97) 1 STD-ITU-T RECMN Z.3bO-ENGL 1997 m LiAb259L Obil1738 23L m 1.2.2 synonymously called graphs or drawings. 1.2.3 1.2.4 parameters. The labels may refer to other GDMOIGRM statements or non-GDMOIGRM statements (e.g. in ASN. 1). 1.2.

31、5 1.2.6 1.2.7 1.2.8 of templates and references. graphic GDMOIGRM specifications: Specifications using Graphic GDMOIGRM. These specifications are template: A complete permissible syntax module in Alphanumeric GDMOIGRM. statement: An instance of a GDMOIGRM template together with filled in application

32、 specific labels and subtemplate: A part of a complete GDMOIGRM template. substatement: A part of a complete GDMOIGRM statement. symbol: An item in Graphic GDMOIGRM which corresponds to a template. connective: An item in Graphic GDMO/GRM which corresponds to a reference between templates or a series

33、 2 Symbols Symbol Statement alamLog MANAGED OBJECT CLASS -1 namepackage PACKAGE alamLogName I alamLogName ATTRIBUTE y nameGroup 1 nameGroup ATTRIBUTE GROUP I I Y namecontroi Y namecontroi BEHAVIOUR I X 1 information of unspecified template T1 O101 5O-97/dO1 Figure 1I2.360 - Template statement symbol

34、s 2 Recommendation 2.360 (05I97) STD-ITU-T RECMN Z-3bO-ENGL 1997 D 48b2591 Dbli1737 178 Sub-statement symbol Sub-statement or statement DERIVED FROM BEHAVIOUR ACTIONS NO nl Y NOTIFICATIONS I CB namepackgel I PnameGroup 1 y,I T1 O1 O1 60-97/dM CHARACTERIZED BY CONDITIONAL PACKAGE ATTRIBUTE GROUPS ATT

35、RIBUTES REGISTERED AS Figure 2/2.360 - Sub-statement symbols CI bl ac 1 nl namepackage properly Package nameGroup name oidl Recommendation 2.360 (05/97) 3 Symbol 4 I X Y - Means Explanation Subordinate statement: also used as roles in references. Referenced statement. A reference is made up of an ar

36、row plus a role Mel x; x = . The role label can be left out if role label = referenced label. X 1-0 I I Y Reference from x to an object of any class. DERIVED FROM y; depicted by a dashed line. DB Y - Defined by y; depicted by a dashed line. *-.I y I Two-way reference = two mutually dependent referen

37、ces in opposite I I alarmlog alarm alarmlog Branching = reference to either x or y; note that in case of combined use of branching and two-way references, the interpretation is not unique. alarmlist NAME BINDING SUBORDINATE OBJECT CLASS alarm NAMED BY SUPERIOR OBJECT CLASS alarmlog alarmlist NAME BI

38、NDING alarm AND SUBCLASSES SUBORDINATE OBJECT CLASS NAMED BY SUPERIOR OBJECT CLASS alarmlog AND SUBCLASSES I -I i alarmlog alarmlist NAME BINDING SUBORDINATE OBJECT CLASS alarm AND SUBCLASSES NAMED BY SUPERIOR OBJECT CLASS alarmlog AND SUBCLASSES Dashed lines are optionally provided to point out the

39、 subclasses. Figure 312.360 - Oonnection symbols 4 Recommendation 2.360 (05/97) Notation DF log STD-ITU-T RECMN Z.3bO-ENGL I997 qBb2591 Ob41741 82b W DERIVED FROM Templates CB pl CB p2 CP cp1 CP cp2 - CHARACTERIZED BY CONDITIONAL PACKAGE alarmlog al AC acl NO nl RA abc alarmlog CHARACTERIZED BY BEHA

40、VIOURS ATTRIBUTES ATTRIBUTE GROUPS ACTIONS NOTIFICATIONS REGISTERED AS Pl MANAGED OBJECT CLASS log MANAGED OBJECT CLASS log PACKAGE bl al ag 1 al acl nl abc NAME BINDING alarmlist SUBORDINATE OBJECT CLASS alarm AND SUBCLASSES alarmlog NAMED BY SUPERIOR OBJECT CLASS alarmlog AND SUBCLASSES DF! i -=-I

41、 priorityAlarm T1 O1 0180-97/d4 Figure 4/2.360 - Examples of shorthand and combined notations Recommendation 2.360 (05/97) 5 STD-ITU-T RECMN Z-IbO-ENGL 1997 48b259L Ob1i271i2 7b2 rule accessControlRules A 1 7 notificationErnitter I I Relationship L 3 The purpose of this clause is to show how the gra

42、phic notation can be used. The example shown depicts a realistic graph. The example depicts the relevant information contained in Recommendation X.741 Objects and Attributes for Access Control. The most compact form of the graphic notation is used. Example usage of the graphic notation I DFI I I I I

43、 I l l I I I I I I I I DF I I l I I I I ! targets I I I I I I I I I I -7 I I : operations- Targets i operations I glo balRule Package initiatorlist I globalRule I -_- I I DF I I T10101SU97m DF capa bilitylnitiators I- labelinitiators l I aciinitiators Figure 5/2.360 - Example compact graphic notatio

44、n 6 Recommendation 2.360 (05797) STD-ITU-T RECMN Z-3bO-ENGL 1777 W 4b257L Ob4L743 bT7 W Figure 6 Shows the same graph extended with references to packages and attributes. nib I Accecscontrd IDF DF Relationship I I nile CB RilePackage CP availabilHyStatusPackage CP duration CP dailyScheduling CP wkly

45、schduling CP extemalScheduler CB authentimtlonCondronPackage denialResponse accessPefmission CB StatMionPackage statecondtion auhentiionmeni A I A I I I DF I I I I I IF I I I I - I I DF I I I notificationErnitter L I I I I I I I I I I I I l I I I I I l I targets I il I Figure 6/2.360 - Example compo

46、sed and compact graphic notation 7 Recommendation 2.360 (05/97) STD-ITU-T RECMN Z-3bO-ENGL 1777 W LiBb259L Ob41744 535 9 CONDITIONAL PACKAGE 4 Graphic notation for templates 4.1 Managed Object Class template Figure 7 depicts a detailed graphic notation for a subset of the information provided in the

47、 Managed Object Class tempiate. Note the use of prefix abbreviations to indicate the different kind of items. Graphic notation I aiarrniog I Alphanumeric notation alarrniog DERIVED FROM Il 2) translation; 3) instantiation. 14 Recommendation 2.360 (05/97) - - STD-ITU-T RECMN Z-360-ENGL 1777 48b2591 O

48、b41751 775 d 7 Figure 1.1 depicts a GDMO specification using Graphic GDMO. system L I TI O1 4MW/d26 DF admin-subNet , admin-subNet SUP Figure I.UZ.360 - Example GDMO specification 7, 7, 7, admin-degenerate , system-subNet system-subNet SUP Inheritance stage: The inheritance stage executes Derived Fr

49、om statements of Managed Object Classes and Relationship Classes, Characterized By and Conditional Packages references - and implicitly Defined By statements of the metalanguage - Package statements, Attributes references and statements, Attribute Groups references and statements, and And Subclasses statement of Name Bindings. This way, the properties of the object classes are no more referred to, they are inherited into the object class to be instantiated. su bNetwo rk mmP I sub SUP sub Figure 1.2 shows