ISO/IEC 9595:1990
(Main)Information technology — Open Systems Interconnection — Common management information service definition
Information technology — Open Systems Interconnection — Common management information service definition
Technologies de l'information — Interconnexion de systèmes ouverts — Définition du service commun d'information de gestion
General Information
Relations
Standards Content (Sample)
I NTER NAT1 ON AL ISO/IEC
STANDARD
First edition
1 990-05- 1 5
Information technology - Open Systems
Interconnection - Common management
information service definition
Technologies de l'information - Interconnexion de systèmes ouverts - Définition
du service commun d'information de gestion
Reference number
IS0 9595 : 1990 (E)
---------------------- Page: 1 ----------------------
ISO/IEC 9595 : 1990 (E)
Page
Contents
Foreword iii
........................................
Iscope . 1
2 Normative references . 1
1
3 Definitions .
3.1 Basic Reference Model definitions . 1
3.2 Management Framework definitions . 1
3.3 ACSE definitions . 1
3.4 Service conventions definitions . 1
3.5 Additional definitions . 2
4 Symbols and abbreviations . 2
2
5 Conventions .
6 Service overview . 2
6.1 Association services . 2
6.2 Management notification services . 3
6.3 Management operation services . 3
6.4 Management information tree . 3
6.5 Management object selection . 3
7 Functional units . 3
7.1 Kernel functional unit . 4
7.2 Additional functional units . 4
8 Service definition . 4
8.1 Association services . 4
8.2 Management notification service . 5
8.3 Management operation services . 6
9 Sequencing information . 15
M-GET. M.CREATE. M-DELETE . 15
9.1
9.2 M.EVENT.REPORT. M.SET. M-ACTION . 15
Annexes
A (informative) CMISE-service-user behaviour . 1 6
@ ISO/IEC 1990
All rights resewed . 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 publisher .
ISO/iEC Copyright Office Case postale 56 CH-1211 Genève Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISO/IEC 9595 : 1990 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide standardiz-
ation. National bodies that are members of IS0 or IEC participate in the development
of International Standards through technical committees established by the respective
organization to deal with particular fields of technical activity. IS0 and IEC technical
committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with IS0 and IEC, also take part in the
work.
of information technology, IS0 and IEC have established a joint technical
In the field
committee, ISO/IEC JTC 1. Draft International Standards adopted by the joint
technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by atleast 75 olo of the national bodies casting
a
a vote.
International Standard ISOAEC 9595 was prepared by Joint Technical Committee
ISOAEC JTC 1, Information technology.
Annex A is for information only.
iii
---------------------- Page: 3 ----------------------
a
a
---------------------- Page: 4 ----------------------
ISO/IEC 9595 : 1990 (E)
INTERNATIONAL STANDARD
~~
Information technology - Open Systems Interconnection -
Common management information service definition
ISO/IEC 7498-4 : 1989, Information processing systems -
1 Scope
Open Systems Interconnection - Basic Reference Model - Part
4: Management Framework.
This International Standard defines an Application Service
Element (the Common Management Information Service
ISOf’iR 8509 : 1987, Information processing systems - Open
Element), which may be used by an application process in a
Systems Interconnection - Service conventions.
centralized or decentralized management environment to
exchange information and commands for the purpose of
IS0 8649 : f987, Information processing systems - Open
systems management, as defined by the OS1 Management
Systems Interconnection - Service definition for the
Framework in ISO/reC 7498-4. This International Standard is
Association Control Service Element.
positioned in the application layer of IS0 7498 and is defined
according to the model provided by ISO/reC 9545.
ISO/IEC 9545 I), information processing system - open
Systems Interconnection - Application Layer Structure (ALS).
0 This International Standard defines
- a set of service primitives that constitute the application
3 Defmîtions
service element;
For the purposes of this International Standard. the following
- the parameters that are passed in each service primitive;
definitions apply.
- any necessary information for the semantic description of
each service primitive. 3.1 Basic Rderence Model definitions
This International Standard makes use of the following terms
This Intemational Standard does not define
defined in IS0 7498.
- the nature of any implementation intended to provide the
a) application-service-element;
defined service;
b) open system;
- the semantics associated with the information or c) systems-management.
commands that are exchanged by means of the service;
3.2 Management kamework dennitionS
- the manner in which management is accomplished by the
user of the service: This International Standard makes use of the following terms
defined in ISO/lEC 7498-4.
- the nature of any interactions which result in the use of the
service.
a) managed object;
b) management information;
No requirement is made for conformance to this International
c) systems management application-entity.
Standard.
3.3 ACSE def‘itions
2 Normative references
This Internationai Standard makes use of the following ternis
defined in IS0 8649.
The following International Standards contain provisions
which, through reference in this text, constitute provisions of a) application-association;
this International Standard. At the time of publication, the b) application context;
editions indicated were valid. All standards are subject to
c) association;
revision, and parties to agreements based on this International
d) association-initiator.
Standard are encouraged to investigate the possibility of
applying the most recent editions of the standards listed below.
3.4 Service conventions definitions
Members of IEC and IS0 maintain registers of currently valid
International Standards.
This International Standard makes use of the following terms
defined in ISOm 8509.
IS0 7498 : 1984, Information processing systems - Open
Systems Interconnection - Basic Reference Model.
a) confirm (primitive);
b) confirmed-service;
c) indication (pdmitive);
l) To be published.
1
---------------------- Page: 5 ----------------------
ISO/IEC 9595 : 1990 (E)
the value of the parameter is equal to the value of the
d) non-confirmed-service; (=)
parameter in the column to the left
e) request (primitive);
f) response (primitive).
the use of the parameter is a service-user option
U
3.5 Additional definitions
_.
the parameter is not present in the interaction described
by the primitive concerned
3.5.1 Attribute: A property of a managed object, An attribute
has a value.
C the parameter is conditional. The condition(s) are
defined by the text which describes the parameter.
3.5.2 Common Management Information Service Element "he
particular application-service-element defined in this
international Standard.
6 Service overview
3.5.3 Common Management Information Services: The set of
Management information services are used by application
services provided by the Common Management Information
processes in peer open systems, to exchange infoimation and
Service Element.
commands for the purpose of systems management.
3.5.4 CMISEservice-provider: An abstraction of the totality
There are two types of information transfer service
of those entities which provide CMISE services to peer CMISE-
service-users.
a) a management notification service;
3.5.5 CMISE-service-user: The part of an application process
b) a management operation service.
that makes use of the Common Management Information
Service Element.
The Common Management Information Service provides
additional structuring facilities. These enable
3.5.6 Functional unit: The unit of service used for the
negotiation of service options.
a) multiple responses to confirmed operations to be
"linked" to the operation by the use of a linked identification
3.5.7 invoking CMISEservice-user: The CMISE-sevice-user
parameter;
that invokes a management operation or notification.
b) operations to be performed on multiple managed
objects selected to satisfy some criteria and be subject to a
3.5.8 Performing CMIsE-service-user: The CMTSE-service-user
"synchronizing" condition.
that perfoms a management operation or notification invoked
by a peer CMISE-service-user.
The CMISE services are listed in table 1.
Table 1 - CMISE services
4 Symbds and abbreviations
Service
Type
ACSE Association Control Service Element
confirmed/non-confirmed
M-EV"I-REKIRT
confinned
M-GET
ASE Application Service Element
confirmed/non-confirmed
M-SFR
coiifirnied/non-confirmed
M-ACI'ION
CMIS Common Management information Service
M-CREATE confirmed
M-DELETE confirmed
Common Management Information Service Element
CMISE
Conf Confirm 6.1 Association services
Jnd Indication This International Standard does not provide separate services
for the establishment and release of application associations.
Req Request The CMISE-service-user relies on the services of IS0 8649 for
the control of application-associations.
Rsp Response
During the association establishment phase, various ASES may
exchange initialisation information to establish an
association iiaing ACSE. The application context specifies the
5 Conventions
rules required for coordinating the information belonging to
different ASES, embedded in ACSE user infomiation service
This International Standard defines services for CMIS
parameters. The application context, presentation and session
following the descriptive conventions defined in ISOm 8509.
requirements are conveyed using parameters of the
In clause 8, the definition of each CMIS service includes a table
A-ASSOCIATE service.
that lists the parameters of its primitives. The definition of
parameters in the Rsp/Conf column of a table apply only to the
The A-RELEASE and A-ABORT services of IS0 8649 are used
confirmed service. For a given primitive, the presence of each
for the termination of an association. These may be invoked by
parameter is described by one of the following values
either of the CMISE-service-users.
M the parameter is mandatory
2
---------------------- Page: 6 ----------------------
ISO/IEC 9595 : 1990 (E)
4.2 Management notification services 4.5 Managed object selection
The definition of the notification and the consequent behaviour Managed object selection involves two phases: scoping and
of the communicating entities is dependent upon the filtering.
specification of the managed object which generated the
notification and is outside the scope of the Common Scoping entails the identification of the managed object(,) to
which a filter is to be applied.
Management Information Service. However, certain
notifications are used frequently within the scope of systems
Filtering entails the application of a set of tests to each
management and CMIS provides the following definition of the
member of the set of previously scoped managed objects to
common service that may be used to convey management
information applicable to the notification. extract a subset.
The M-EVENT-REPORT service is invoked by a CMISE- The subset of scoped managed objects that satisfy the filter is
service-user to report an event about a managed object to a peer selected for the operation.
CMISE-service-user. The service may be requested in a
confirmed or a non-confirmed mode. In the confirmed mode, a NOTE - If no filter is specified, then the set of scoped managed
objects is selected for the operation.
reply is expected.
6.5.1 Scoping
6.3 Management operation services
The base managed object is defined as the root of the subtree of
The definition of the operation and the consequent behaviour of
the management information tree from which the search is to
the communicating entities is dependent upon the specification
O
commence. Four specifications of scoping level are defined,
of the managed object at which the operation is directed and is
indicating whether the filter is to be applied to
outside the scope of the Common Management Information
Service. However, certain operations are used frequently within
a) the base object alone:
the scope of systems management and CMIS provides the
following definitions of the common services that may be used
the nth level subordinates of the base object:
to convey management information applicable to the b)
operations.
the base object and all of its subordinates down to and
c)
including the nth level;
6.3.1 The M-GET service is invoked by a CMISE-service-user
to request the retrieval of management information from a peer
d) the base object and all of its subordinates (whole
CMISE-service-user. The service may only be requested in a
confirnied mode, and a reply is expected. subtree).
NOTE -The base object is &fined to be level zero.
6.3.2 The M-SET service is invoked by a CMISE-service-user
to request the modification of management information by a
a 6.5.2 Filtering
peer CMISE-service-user. The service may be requested in
confirmed or a non-confirmed mode. In the confirmed mode, a
reply is expected. A filter is a set of one or more assertions about the presence or
values of attributes in a scoped managed object. If the filter
6.3.3 The M-ACTION service is invoked by a CMISE-service- involves more than one assertion, the assertions are grouped
together using logical operators. If the filter test succeeds for a
user to request a peer CMISE-service-user io perform an action.
in a confirmed or a non-confirmed given managed object, then that managed object is selected for
The service may be requested
performance of the operation.
0 mode. In the confirmed mode, a reply is expected.
6.3.4 The M-CREATE service is invoked by a CMISE-service- 6.5.3 Synchronization
user to request a peer CMISE-service-user to create an instance
of a managed object. The service may only be requested in the A synchronization parameter is provided to allow the CMISE-
in which operations are to
confirmed mode, and a reply is expected. service-user to indicate the manner
be synchronized across managed object instances when
multiple managed objects have been selected by the scope and
6.3.5 The M-DELETE service is invoked by a CMISE-service-
filter mechanism. The CMISE-service-user may request one of
user to request a peer CMISE-service-user to delete an instance
two types of synchronization: atomic or best effort. Since the
of a managed object. The service may only be requested in the
order in which object instances are selected by the filter is a
confirmed mode, and a reply is expected.
local matter, synchronization based on order is not
meaningful.
4.4 Management information tree
NOTE - CMIS does not provide a parameter to indicate
Management information may be viewed as a collection of
synchronization across attributes within a managed object. This will be
managed objects, each of which has attributes, and may have
specified as part of the managed object behaviour and may vary for
defined events and actions. Names of instances of managed
different attribute combinations and operations.
objects are arranged hierarchically in a management
infomation tree.
7 Functionai units
It is conceivable that there may be dynamic changes to the
management information tree and that this knowledge may not
The general service capabilities are designated as functional
be instantaneously available to other open systems.
units, where functional units correspond to the support of
service primitives or parameters.
3
---------------------- Page: 7 ----------------------
ISO/IEC 9595 : 1990 (E)
8.1 Association services
7.1 Kernel functional Unit
8.1.1 Association establishment
Ali of the CMISE services listed in table 1 are included in the
The A-ASSOCIATE service of IS0 8649 is invoked by a
kernel functional unit. For the services in the kernel functional
CMISE-service-user to establish an association with a peer
unit, the linked identification parameter shall not be used
CMISE-service-user. Association establishment is the first
unless the multiple reply functional unit is agreed for use on the
phase of any instance of management information service
association between the CMISE-service-users. The scope and
activity.
synchronization parameters shall not be used unless the
multiple object selection functional unit has been agreed. The
Table 2 lists the parameters that are defined by this
filter parameter shall not be used unless the filter functional
International Standard to be the CMIS specific part of the user
unit has been agreed.
information parameter of the A-ASSOCIATE service. This
information is specified by the association-initiator and
7.2 Additional functional units
exchanged when establishing an association. Exchange of this
initialisation information is required prior to using
7.2.1 Multiple object selection functional unit
management operation and notification services.
This functional unit makes available the use of the scope and
Table 2 - A-ASSOCIATE user information
synchronization parameters in the services in the kernel
functional unit. These parameters are not present in the
Parameier Name I R*d I Rsp/Conf
M-EVENT-REPORT and M-CREATE services.
Functional units
! U I U
~~ 7
-
If the multiple object selection functional unit is proposed,
Access control I U I
then the multiple reply functional unit shall also be proposed.
User information U U I
7.2.2 Filter functional unit
8.1.1.1 Functional units
This functional unit makes available the use of the filter
When supplied by the initiating CMISE-service-user, this
parameter in the services in the kernel functional unit. The
parameter specifies the set of additional functional units that
filter parameter is not present in the M-EVENT-REPORT and
the initiating CMISE-service-user is proposing for use on the
M-CREATE services.
association. When returned by the responding CMISE-service-
user, this parameter specifies the set of additional functional
7.2.3 Multiple reply finctional unit
units that the responding CMISE-service-user is proposing for
use on the association.
This functional unit makes available the use of the linked
identification parameter in the services in the kernel functional
When this parameter is not supplied, it is assumed that no
unit. The linked identification parameter is not present in the
additional functional unit is proposed.
M-EVENT-REPORT and M-CREATE services.
Any additional functional unit that has been proposed by both
NOTE - The use of the multiple reply functional unit may result in a
CMISE-service users is agreed to be available for use on the
large amount of data to be returned. Currently, CMIS provides no facility
association.
for controlling the flow of data or for controlling an operation;
additional mechanisms to cater for this situation are necessary and are
If the extended service functional unit is successfully
for further study.
negotiated, then presentation layer services other than the
P-DATA service are available for use. Details of which other
7.2.4 Extended service functional unit
presentation services and how they are used are described in the
definitions of the application context in use on the
This functional unit makes available presentation layer
association.
services in addition to the P-DATA service.
8.1.1.2 Access control
8 Service definition
This parameter is information of unspecified form to be used as
input to access control functions in establishing default access
The CMISE services are listed in table 1.
privileges for all exchanges on the association. If a subsequent
service request specifies an access control parameter, then the
Parameters returned as part of the confirm primitive may occur
access privileges for that and only that invocation of the
as the result of a successful operation (these are described as
service are determined from that parameter.
"included in the success confirmation"), or as the notification
of an error condition (these are described as "included in the
8.1.1.3 User information
failure confirmation").
The initiating CMISE-service-user and/or the responding
Some operations may report an error code. In the event of
CMISE-service-user may optionally include user inforniation
multiple errors, with one of the errors being a security
on the request and/or response primitive respectively. The
violation. then the error code "access denied" shall be returned.
meaning of this parameter is application context specific.
4
---------------------- Page: 8 ----------------------
ISO/IEC 9595 : 1990 (E)
8.1.2 Association release
8.2.1.3 Managed object class
The A-RELEASE service of IS0 8649 is invoked by a CMISE-
service-user to request the orderly termination of an association This parameter specifies the class of the managed object in
which the event occurred. It may be included in any
between peer application entities. This International Standard
does not specify any use of the parameters of the A-RELEASE confirmation.
service.
83.1.4 Managed object instance
The A-ABORT service is invoked by a CMISE-service-user to
This parameter specifies the instance of the managed object in
request the abrupt temiination of the association between peer
application entities. which the event occurred. It may be included in any
confirmation.
Table 3 lists the parameter that is defined by this International
Standard to be the abort source parameter of the A-ABORT 8.2.1.5 Event type
service.
Tliis parameter specifies the type of event being reported. It
Table 3 - A-ABORT user information may be included in the success confirmation and shall be
included if the event reply parameter is included.
CMlSParameter I A-AFJORTReqhd
8.2.1.6 Event time
Abort source I M I
This parameter contains the time of generation of the event.
0 The abort source parameter indicates the initiating source of the
abort, It takes one of the following symbolic values
8.2.1.7 Event information
- CMISE-service-provider;
This parameter contains information that the invoking CMISE-
service-user is able to supply about the event.
- CMISE-service-user.
8.2.1.8 Current time
8.2 Management notification service
This parameter contains the time at which the response was
The M-EVENT REPORT service is used by a CMISE-service-user
hi the success confirmation.
generated. It may be included
to report an event to a peer CMISE-service-user. It is defined as
a confirmed and a non-confirmed service.
8.2.1.9 Event reply
8.2.1 M-EVENT-REPORT parameters
This parameter contains the reply to the event report. It may be
included in the success confimiation.
Table 4 lists the parameters for this service.
8.2.1.10 Errors
Table 4 - M-EVENT-REPORT parameters
This parameter contains the error notification for the
Parameter Name I Reqhd I Rsp/Conf
operation. It shall be included by the performing CMISE-
Invoke identifier I M l M(=)
service-user in the failure confirmation. The following errors
-
Mode I M I
may occur
0 IManaged object class M U
Managed object instance M U - duplicate invocation: the invoke identifier specified was
or operation;
M C(=) allocated to another notification
Event time U -
_. - invalid argument value: the event information value
U
Event information
specified was out of range or otherwise inappropriate;
Current time - U
Event reply - C
- mistyped argument: one of the parameters supplied has not
I Errors -
I I C
I
been agreed for use on the association between the CMISE-
service-users;
8.2.1.1 Invoke identifier
- no such argument: the event information specified was not
This parameter specifies the identifier assigned to the
recognized;
notification. It can be used to distinguish this notification
from other notifications or operations that the CMISE-service-
- no such event type: the event type specified was not
provider may have in progress.
recognized;
8.2.1.2 Mode
- no such object class: the class of the specified managed
object was not recognized
This parameter specifies the mode requested for the operation.
The possible values are
- no such object instance: the instance of the specified
managed object was not recognized;
- confirmed
- processing failure: a general failure in processing the
- non-confirmed.
notification was encountered
5
---------------------- Page: 9 ----------------------
ISO/IEC 9595 : 1990 (E)
8.3.1.1.2 Linked identifier
- resource limitation: the notification was not processed due
If multiple replies are to be sent for this operation, then this
to resource limitation;
parameter specifies the identification that is provided by the
- unrecognized operation: the operation is not one of those performing CMISE-service-user when those replies are
returned. The linked identifier shall have the same value as that
agreed between the CMISE-service-users.
of the invoke identifier provided in the indication piiniitive.
8.22 M-EVENT-REPORT pr~~edure~
8.3.1.1.3 Base object class
8.2.2.1 The invoking CMISE-service-user reports an event to
This parameter specifies the class of the managed object that is
a performing CMISE-service-user by issuing an M-EVENT-
to be used as the starting point for the selection of managed
REPORT request primitive to the CMISE-service-provider.
objects on which the filter (when supplied) is to be applied.
8.2.2.2 The CMISE-service-provider issues an M-EVENT-
REPORT indication primitive to the performing CMISE- 8.3.1.1.4 Base object instance
service-user.
This parameter specifies the instance of the managed object
8.2.2.3 In the confirmed mode, the perfomiing CMISE-service- that is to be used as the starting point for the selection of
user reports acceptance or rejection of the M-EVENT-REPORT managed objects on which the filter (when supplied) is to be
request primitive by issuing an M-EVENT-REPORT response applied.
primitive to the CMISE-service-provider.
8.3.1.1.5 Scope
8.2.2.4 In the confirmed mode, the CMISE-service-provider
issues an M-EVENT-REPORT confirm primitive to the This parameter indicates the subtree, rooted at the base
managed object, which is to be searched. The levels of search
invoking CMISE-service-user.
that may be performed are
8.3 Management operation services
- the base object alone;
8.3.1 M-GET service
- the nth level subordinates of the base object:
The M-GET service is used by a CMISE-service-user to retrieve
attribute values from a peer CMISE-service-user. It is defined as - the base object and all of its subordinates down to and
a confirmed service.
including the nth level;
8.3.1.1 M-GET parameters
- the base object and all of its subordinates.
Table 5 lists the parameters for this service.
The default scope is the base object alone.
Tabie 5 - M-GJCT parameters
8.3.1.1.6 Filter
This parameter specifies the set of assertions that defines the
filter test to be applied to the scoped managed object(s).
Multiple assertions may be grouped using the logical operators
AND, OR and NOT. Each assertion may be a test for equality.
ordering, presence, or set comparison. Assertions about the
value of an attribute are evaluated according to the matching
rules associated with the attribute syntax. If an attribute value
assertion is present in the filter and that attribute is not present
in the scoped managed object, then the result of the test for that
attribute value assertion shall be evaluated as FALSE. The
managed object(s) for which the filter test evaluates to TRUE
is(-) selected for the application of the operation. if the filter
is not specified, all of the managed objects included by the
scope are selected.
8.3.1.1.7 Access control
This parameter is information of unspecified form to be used as
8.3.1.1.1 Invoke identifier
input to access control functions.
This parameter specifies the identifier assigned to the
8.3.1.1.8 Synchronization
operation. It can be used to distinguish this operation from
other notifications or operations that the CMISE-service-
This parameter indicates how the invoking CMISE-service-user
provider may have in progress.
wants information retrievals synchronized across the selected
object instances. Two ways of synchronizing a series of
retrievals are defined
6
---------------------- Page: 10 ----------------------
ISO/IEC 9595 : 1990 (E)
- Atomic: All retrievals are checked to see whether they can - access denied: the requested operation was not perfornied
be performed. If any retrieval cannot be performed, then none for reasons pertinent to the security of the open system;
is performed, otherwise all retrievals a~ perfo
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.