ITU-T X 750 AMD 1-1997 Information Technology - Open Systems Interconnection - Systems Management Management Knowledge Management Function - Series X Data Networks and Open System un.pdf

《ITU-T X 750 AMD 1-1997 Information Technology - Open Systems Interconnection - Systems Management Management Knowledge Management Function - Series X Data Networks and Open System un.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 750 AMD 1-1997 Information Technology - Open Systems Interconnection - Systems Management Management Knowledge Management Function - Series X Data Networks and Open System un.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 STD-ITU-T RECMN X-750 AND L-ENGL 1797 ia 48b2591 Ob459b5 790 m INTERNATIONAL TELECOMMUNICATION UNION lTU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.750 Amendment I (1 0/97) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U NI CATIONS OS1 management - Management functions and ODMA functions I

2、nformation technology - Open Systems I n tercon nect ion - Systems management: Management knowledge management function Amendment I : Extension for General Relationship Model ITU-T Recommendation X.750 - Amendment 1 (Previously CCIlT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND O

3、PEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenance Administrative arrangements OPEN SYSTEM INTERCONNECTION Model and notation Service definitions Connection-mode protocol specifications Connectionless-m

4、ode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing INTERWORKING BETWEEN NETWORKS General Satellite data transmission systems MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking Efficiency Quality

5、 of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) OS1 MANAGEMENT Systems Management framework and architecture Management Communication Service and Protocol X. 1-X. 19 X.20-X.49 X.50-X. 89 X.90-X. 149 X. 150-X. 179 X. 180-X. 199 X.200-X.209 X.210-X.219 X.220-X.229

6、 X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.290-X.299 X.300-X.349 X.350-X.399 X.400-X.499 X.500-X.599 X.600-X.629 X.630-X.639 X .640-X . 649 X.650-X.679 X.680-X.699 X.700-X.709 X.710-X.719 Structure of Management Information X.720-X.729 SECURITY OS1 APPLICATIONS Commitment, Concur

7、rency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.800-X.849 X.850-X.859 X.860-X.879 X.880-X.899 X.900-X.999 Il For further details, please refer to ITU-T List of Recommendations. STD-ITU-T RECMN X.750 AMD 1-ENGL 1997 Li8b259L Ob459b7 5b3 9 INTERNATIONAL STANDA

8、RD 10164-16 ITU-T RECOMMENDATION X.750 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - SYSTEMS MANAGEMENT: MANAGEMENT KNOWLEDGE MANAGEMENT FUNCTION AMENDMENT 1 Extension for General Relationship Model Source The ITU-T Recommendation X.750, Amendment 1 was approved on the 24th of October 1997

9、. The identical text is also published as ISOAEC International Standard 10164-16. ITU-T Rec. X.750 (1996)/Amd.l (1997 E) 1 STD-ITU-T RECMN X-750 AND 1-ENGL 2797 qb259L Ob457b8 4TT I FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecomm

10、uni- cations. The ITU Telecommunication Standardization Sector (IT-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 T

11、elecommunication 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 IT-T is covered by the procedure laid down

12、 in WTSC Resolution No. 1. In some areas of information technology which fall within IT-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 telecommunicatio

13、n administration 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, vali

14、dity 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, the ITU had not received notice of intellectual property, protected by patents, which may be

15、required 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 1998 All rights reserved. No part of this publication may be reproduced or utilized in any form

16、 or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. ii ITU-T Rec. X.750 (1996)/Amd.l (1997 E) CONTENTS Subclause 3.6 . Subclause 3.1 1 . Clause 4 Clause 6 Subclause 6.3 . Subclauses6.3,6.5,7.1.1.1,8.1.1.2,Table8,A.2.1 andA.2.3

17、 . Subclause 7.1.2 Subclauses7.1.2,8.1.2.12, 8.6.2andA.3.3 . Subclause 7.3 . New subclauses 8.1.2.12 and 8.1.2.13 . Subclause 8.6.2 Subclause 11.1.1.2 Subclause 11.1.5.1 . Subclause 11.1.5.2 Subclause 11.1.6.1 . Subclause 1 1.2.1.2 . Subclause A . 1 Subclause A.2.4 Subclause A.3.1 Subclause A.3.3 Su

18、bclause A.3.5 Subclause A.4.1 Subclause A.4.5 Subclause B . 1 . Subclause B.2 . Annexes A to E . Subclause C.1.3 Subclause C.4 . Subclause D.3.1 New subclauses E.3.16 and E.3.17 . . . ITU-T Rec . X.750 (1996)/Amd.l (1997 E) Page 1 1 1 2 2 2 2 2 2 2 3 3 3 3 4 4 4 4 5 6 7 8 8 9 9 10 11 11 11 12 . 111

19、STD*ITU-T RECMN X-750 AND 1-ENGL 1777 M Li8b2571 Ob45770 058 W ISO/iEC 10164-16 : 1997/Amd.l : 1998 (E) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - SYSTEMS MANAGEMENT: MANAGEMENT KNOWLEDGE MANAGEMENT FUNCTION AMENDMENT 1 Extension for General R

20、elationship Model 1) Subclause 3.6 Add references to these SMO-defined terms inserted among existing terms in alphabetical order: e) managed object class and renumber the list asflom the existing e) which becomes f), io the end. 2) Subclause 3.1 1 Add references to these GRM-defined terms inserted b

21、efore and after existing term in alphabetical order: binding; binding support; managed relationship class; relationship cardinality; relationship management notification; relationship management operation; role cardinality; relationship mapping specification; relationship class specification; role;

22、unbinding; unbinding support. 3) Clause 4 Insert the following abbreviation by alphabetical order: GRM General relationship model ITU-T Rec. X.750 (1996)/Amd.l (1997 E) 1 - STD-ITU-T RECMN X-750 AND 1-ENGL 1777 = 48b2571 0645771 T94 ISODEC 10164-16 : 1997/Amd.l : 1998 (E) 4) Clause 6 In this clause

23、change: - Definition knowledge: Information on the formal specification of managed object classes, name bindings, etc., e.g. templates for classes, name bindings. Definition knowledge: Information on the formal specification of managed object classes and managed relationship classes and related spec

24、ifications, e.g. templates for classes, attributes, name bindings. to: - Add an X in the Table 1 cell in the Definition knowledge column in the Relationship knowledge row. 5) Subclause 6.3 In the 2nd item: relationship role bindings relationship mapping specifications to: 6) In subclauses 6.3, 6.5,

25、7.1.1.1, 8.1.1.2, Table 8, and in behaviour text in A.2.1 and A.2.3, replace each occurrence of the term relationship class that is not preceded by managed with the term de$ned in GRMmanaged relationship class but do not change the label supportedRelationshipClassList. Subclauses 6.3,6.5,7.1.1.1,8.1

26、.1.2, Table 8, A.2.1 and A.2.3 7) Subclause 7.1.2 In this subclause change GDMO and ASN.l specifications to GDMO, GRM and ASN.l specifications. 8) Subclauses 7.1.2,8.1.2.12,8.6.2 and A.3.3 In subclauses 7.1.2, 8.1.2.12, 8.6.2 and A.3.3, change all occurrences of GDMO template(s) to template(s). 9) S

27、ubclause 7.3 Add an X in thefour Table 2 cells that are in either the Definition managed objects or Definition Directory objects columns and that are in either the Managed object class knowledge or Relationship knowledge rows. Change both occurrences of X (Note 7) to X and eliminate Note 7. 10) Renu

28、mber subclause 8.1.2. I2 as 8. I .2.14 and insert two new subclauses before it: 8.1.2.12 Relationship class template managed object The relationship class template managed object represents a GRM relationship class specification. The relationship class template managed object class is defined as a s

29、ubclass of the template managed object class. Its New subclauses 8.1.2.12 and 8.1.2.13 mandatory, read-only attributes are: a) derived from; b) behaviour. Its optional, read-only attributes are: a) supports; b) qualified by; c) role specifier. 2 ITU-T Rec. X.750 (1996)/Amd.l 1997 E) ISOIIEC 10164-16

30、 : 1997/Amd.l : 1998 (E) Relationship class template Relationship mapping template 8.1.2.13 Relationship mapping template managed object The relationship mapping template managed object represents a GRM relationship mapping specification. The relationship mapping template managed object class is def

31、ined as a subclass of the template managed object class. Its mandatory, read-only attributes are: a) mapped relationship class; b) behaviour; c) role mapping specification; d) registered as. Its optional, read-only attributes are: a) relationship object; b) operations mapping. managementRelationship

32、Class managementRelationshipMapping 11) Subclause 8.6.2 In this subclause, change the two occurrences of GDMO specifications to GDMO, GRM or ASN.1 specifications. Append to this subclause the following paragraphs: The Directory auxiliary class relationship class template is defined for inclusion in

33、Directory entries of Directory structural class Registered information and represents a Gi2M relationship class specification. It must contain the attributes Derived from and Behaviour. It may contain the attributes Supports, Qualified by, and Role specifier. The Derived from attribute identifies th

34、e immediate superclasses of a managed relationship class. The Behaviour attribute specifies the behaviour associated with the managed relationship class. The Supports attribute defines the relationship management operations and notifications that a managed relationship supports. The Qualified by att

35、ribute specifies the attributes that are associated with the managed relationship as a whole. The Role specifier attribute identifies the roles associated with the managed relationship class. The Directory auxiliary class Relationship mapping template is defined for inclusion in Directory entries of

36、 Directory structurai class Registered information and represents a GRM relationship mapping specification. It must contain the attributes Behaviour, Mapped relationship class, Role mapping specification set, and Registered as. It may contain the attributes Relationship object and Operations mapping

37、. The Behaviour attribute defines the behaviour associated with the relationship mapping. The Mapped relationship class attribute specifies the managed relationship class to which the represented relationship mapping is related. The Role mapping specification set attribute identifies candidate manag

38、ed object classes that may fulfil a given role. The Registered as attribute contains the object identifier of the represented relation mapping. The Relationship object attribute indicates the class of a relationship object that shall represent the managed relationship. The Operations mapping attribu

39、te specifies the mapping of a relationship management operation to one or more systems management operations. 12) Subclause 11.1.1.2 Add entries to Table 6for relationship class template and relationship mapping template (inserting before the entry for the template class). 13) Subclause 11.1.5.1 Add

40、 entries to Table 9 for the new attributes mentioned in the new subclauses 8.1.2.12 and 8.1.2.13. 14) Subclause 11.1.5.2 Insert in Table 14 the following entries before the entry for the template class: ITU-T Rec. X.750 (1996)/Amd.l (1997 E) 3 ISODEC 10164-16 : 1997lAmd.l : 1998 (E) 15) Subclause 11

41、.1.6.1 Insert in Table 15 the following entries before the entry for the template class: relationshipMappingTemplate I relationshipClassTemplate managementRelationshipMapping I managementRelationshipClass Operations mapping Qualified by OperationsMapping qualifiedB y 16) Subclause 11.2.1.2 Relations

42、hip object Role mapping specification set Add to Table 17 the following enfries (inserting in alphabetical order). relationshipobject roleMappingSpecificationSet I Mapped relationship class I mappedRelationshipC1ass I Role specifier supports roleSpecifier supports 17) Subclause A.l In this subclause

43、 change: -%PRAGMA version BIT STRING v1990(0), v1994(1) : = v1990, 1994) to: - 18) Subclause A.2.4 In this subclause change: -%PRAGMA version BIT STRING v19900), v1994(1) := VI 990 to: - Also in this subclause change: FROM Attribute-ASNlModule Ooint-iso-ccitt(2) ms(9) smi(3) partZ(2) asnlModule(2) t

44、o: FROM Attribute-ASNlModule Qoint-iso-itu-t(2) ms(9) smi(3) part2(2) asnlModue(2) 1) 4 ITU-T Rec. X.750 (1996)/Amd.l (1997 E) ISOAEC 10164-16 : 1997/Amd.l : 1998 (E) 19) Subclause A.3.1 Add to this subclause these managed object class definitions (inserting in alphabetical order): relationshipClass

45、Template MANAGED OBJECT CLASS DERIVED FROM template; CHARACTERIZED BY relationshipClassPackage PACKAGE BEHAVIOUR relationshipClassBehaviour BEHAVIOUR DEFINED AS ! A managed object with this behaviour represents a RELATIONSHIP CLASS template. ? -7, ATTRIBUTES derivedFrom GET, behaviour GET; CONDITION

46、AL PACKAGES relationshipClassSupportsPackage PACKAGE BEHAVIOUR relationshipClassSupportsBehaviour BEHAVIOUR DEFINED AS ! A managed object with this behaviour represents a template that was defined with the SUPPORTS construct. ATTRIBUTES 1 supports GET; defined with the SUPPORTS construct“, REGISTERE

47、D AS MKMDmkmPackage 53; PRESENT IF “managed object represents a template that was relationshipClassQualifiedByPackage PACKAGE BEHAVIOUR relationshipClassQualifiedByBehaviour BEHAVIOUR DEFINED AS ! A managed object with this behaviour represents a template that was defined with the QUALIFIED BY const

48、ruct. I -99 ATTRIBUTES qualifiedBy GET; defined with the QUALIFIED BY construct“, REGISTERED AS (MKMD.mkmPackage 6); PRESENT IF “managed object represents a template that was relationshipClassRoleSpecifierPackage PACKAGE BEHAVIOUR relationshipCIassRoleSpecifierBehaviour BEHAVIOUR DEFINED AS ! A mana

49、ged object with this behaviour represents a template that was defined with the role-specifier supporting production. I -9, ATTRIBUTES roleSpecifier GET; defined with the role-specifier supporting production“; REGISTERED AS MKMDmkmPackage 7); PRESENT IF “managed object represents a template that was REGISTERED AS (MKMD.mkmM0bjectClass 16); relationshipMappingTemplate MANAGED OBJECT CLASS DERIVED FROM template; CHARACTERIZED BY relationshipMappingPackage PACKAGE BEHAVIOUR relationshipMappingBehaviour BEHAVIOUR DEFIN