ISO/IEC 10040:1998 情報技術—オープンシステム相互接続—システム管理の概要 | ページ 5

3.1 Basic reference model definitions

This Recommendation | International Standard is based on the concepts in the Basic Reference Model for Open Systems Interconnection and makes use of the following terms defined in ITU-T Ree. X.200 | ISO/IEC 7498-1:

• a) application service element;
• b) systems management.

3.6.1 agent : An MIS-User, which for a particular systems management interaction, has taken an agent role.

3.6.2 agent role : A role taken by an MIS-User in which it is capable of performing management operations on managed objects and of emitting notifications on behalf of managed objects.

3.6.3 generic definitions : Definitions of managed object classes, attribute types, notification types or management operation types, made available for general use.

3.6.4 (management) interaction : A single management operation or a single notification or an identified set of logically related management operations and notifications during which the manager and agent role do not change.

3.6.5 managed object class : A named set of managed objects sharing the same (named) sets of attributes, notifications, management operations (packages), and which share the same conditions for presence of those packages.

3.6.6 managed object conformance statement (MOCS) : A statement made by a supplier of a managed object implementation, stating the capabilities and options which have been implemented, and any features which have been omitted.

3.6.7 management information conformance statement (MICS) : A statement from a supplier about an implementation's manager role capabilities and options relating to management information which have been implemented and any features which have been omitted.

3.6.8 MICS proforma : A document, in the form of a questionnaire, which when completed by the supplier of an implementation having manager role capability becomes a MICS.

3.6.9 MOCS proforma : A document, in the form of a questionnaire, designed by the managed object definer or conformance test suite specifier, which when completed for a managed object implementation becomes the MOCS.

3.6.10 managed (open) system : A real open system containing an MIS-User which can take the agent role.

3.6.11 management domain : A specification of a collection of managed objects of interest.

3.6.12 management information : The information within an open system which may be transferred by OSI management protocols.

3.6.13 management jurisdiction : A representation of the relationship between a management policy and a management domain.

3.6.14 management policy : An identifiable specification that can be evaluated with respect to managed objects.

3.6.15 management policy violation : The condition existing when managed objects fail to comply with the semantics of a policy.

3.6.16 management support object : A systems managed object defined specifically to support a systems management function (e.g. log, discriminator).

3.6.17 manager : An MIS-User, which for a particular systems management interaction, has taken a manager role.

3.6.18 manager role : A role taken by an MIS-User in which it is capable of issuing management operations and of receiving notifications.

3.6.19 managing (open) system : A real open system containing an MIS-User which can take the manager role.

3.6.20 MIS-User : An application making use of systems management services.

3.6.21 notification : Information emitted by a managed object relating to an event that has occurred within the managed object.

3.6.22 notification type : A named data-type defining a specific kind of notification.

3.6.23 (N)-layer managed object : A managed object specific to the (N)-layer.

3.6.24 (N)-layer management protocol : An (N)-layer protocol for the exchange of (N)-layer management information supported solely by protocols of the layers (N-l) and below.

3.6.25 (systems management) operation : An operation on a managed object to effect systems management.

3.6.26 systems managed object : A managed object relevant to more than one layer, to the system as a whole, or to specific management functions.

3.6.27 systems management application process : An application process participating in systems management.

3.6.28 systems management application service element : An application service element providing systems management services.

3.6.29 systems management function : A part of systems management activities which satisfy a set of logically related user requirements.

3.6.30 systems management functional area : A category of systems management user requirements.

3.6.31 systems management functional unit : A named non-empty set of systems management services defined for the purpose of identifying specific sets of functionality where there is a requirement to establish or negotiate the use of such functionality between end systems or for reference purposes in other standards.

3.6.32 systems management functional unit package : A named non-empty set of systems management functional units, defined for the purposes of negotiation of functional units on an association.

3.6.33 systems management (application) protocol : An application layer protocol supporting systems management services.

3.6.34 systems management service : A named set of service primitives that provide a service for use in systems management.