ISO/IEC 10164-2:1993
(Main)Information technology — Open Systems Interconnection — Systems Management: State Management Function — Part 2:
Information technology — Open Systems Interconnection — Systems Management: State Management Function — Part 2:
Defines a systems management function which may be used by an application process to interact for the purpose of systems management. Among others, establishes user requirements for the state management function, establishes models that relate the service and generic definitions provided by this function to user requirements, defines the services provided by the function, specifies the protocol that is necessary in order to provide the services, defines the relationship between the service and management operations and notifications, defines relationships with other systems management functions.
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Gestion-systèmes: Fonction de gestion d'états — Partie 2:
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 10164-2
First edition
1993-06- 15
Information technology - Open Systems
Interconnection - Systems Management:
State Management Function
Technologies de I’information - Interconnexion de systemes
ouverts (09) - Ges tion-sys temes: Fonc tion de ges tion d ‘6 ta ts
Reference number
ISO/IEC 10164~2:1993(E)
---------------------- Page: 1 ----------------------
ISO/IEC 10164-2 : 1993(E)
Page
Contents
Foreword
iv
Introduction
1 Scope
2 Normative references
2.1 Identical Recommendations I International Standards
2.2 Paired Recommendations I International Standards equivalent
in technical content
2.3 Additional references
3 Definitions
3.1 Basic reference model definitions
3.2 Management framework definitions
3.3 CMIS definitions
3.4 Systems management overview definitions
3.5 Management information model definitions
3.6 Service conven tions definitions
3.7 OS1 conformance testing definitions
4 Abbreviations
5 Conventions
6 Requirements
7 Model
7.1 Generic states
7.2 Status attributes
7.3 Object class specific state information
13
Generic definitions
8
13
8.1 Generic attributes
18
8.2 Generic notifications
19
8.3 Managed objects
19
8.4 Compliance
19
Service Definition
9
19
9.1 Introduction
20
9.2 Management of state attributes
20
10 Functional units
21
11
Protocol
21
Elements of procedure
11.1
21
11.2 Abstract Syntax
22
Negotiation of functional units
11.3
23
12 Relationships with other functions
23
13 Conformance
23
13.1 General conformance class requirements
23
13.2 Dependent conformance class requiremen ts
0 ISO/IEC 1993
All rights reserved. No part of this publication may be reproduced or utilized in any form or
by aiy means, electronk or mechanical, including photocopying and microfilm, without per-
mission in writing from the publisher.
I SO/1 EC Copyright Office l Case Postale 56 l CH-1 211 Geneve 20 l Switzerland
Printed in Switzerland
11
---------------------- Page: 2 ----------------------
ISO/IEC 10164-2 : 1993(E)
Foreword
ISO (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 ISO 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. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations,
governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
In the field of information technology, ISO and IEC have established a joint technical
committee, ISOAEC 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 at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 10164-2 was prepared by Joint Technical Committee
ISOAEC JTC 1, Information technology, in collaboration with the CCI’IT. The identical
text is published as CCITT Recommendation X.731.
ISO/IEC 10164 consists of the following Parts, under the general title Information
technology - Open Systems Interconnection - Systems Management:
- Part 1 : Object Management Function
- Part 2 : State Management Function
- Part 3 : Attributes for representing relationships
- Part 4 : Alarm reporting function
- Part 5 : Event report managementfunction
- Part 6: Log control function
- Part 7: Security alarm reporting function
- Part 8: Security audit trail function
- Part 9: Objects and attributes for access control
- Part 10: Accounting meterfunction
- Part 11: Workload monitoring function
- Part 12: Test management function
- Part 13: Summarization function
- Part 14: Confidence and diagnostic test categories
. . .
111
---------------------- Page: 3 ----------------------
ISO/IEC 10164-2 : 1993(E)
Introduction
ISO/IEC 10164 is a multipart Standard developed according to ISO 7498 and
ISO/IEC 7498-4. ISO/IEC 10164 is related to the following International Standards:
ISO/IEC 9595: 1990, Information technology - Open Systems Interconnection -
Common management information Service definition;
ISO/IEC 9596: 1990, Information technology - Open Systems Interconnection -
Common management information protocol;
- Open Systems Interconnection -
ISO/IEC 10040: 1992, Informatiort technology
Systems management overview;
ISO/IEC 10165: 1992, Information technology - Open Systems Interconnection -
Structure of management information.
---------------------- Page: 4 ----------------------
ISOLIEC 10164-2 : 1993 (E)
INTERNATIONAL, STANDARD
CCITT RECOMMENDATION
INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION -
SYSTEMS MANAGEMENT: STATE MANAGEMENT FUNCTION
1 Scope
This Recommendation % International Standard defines a Systems management function which may be used by an
application process in a centralized or decentralized management environment to interact for the purpose of Systems
management as defined by CCITT Rec. X.700 I ISO/IEC 7498-4. This Recommendation l International Standard
defines the state management function and consists of Service and generic definitions. It is positioned in the
application layer of CCITT Rec. X.200 I ISO/IEC 7498 and is defined according to the model provided by
ISO/IEC 9545. The role of Systems management functions are described by CCITT Rec. X.701 I ISO/IEC 10040.
This Recomrnendation I International Standard
-
establishes user requirements for the state management function;
-
establishes models that relate the Service and generic definitions provided by this function to user
requirements;
-
defines the Services provided by the function;
-
defines generic attribute types, notification types and parameters documented in accordance with
CCITT Rec. X.722 I ISO/IEC 10165-4;
-
specifies the protocol that is necessary in Order to provide the Services;
-
defines the relationship between the Service and management operations and notifications;
-
specifies compliance requirements placed on other Standards that makes use of these generic defiinitions;
-
defines relationships with other Systems management functions;
specifies conformance requirements.
This Recommendation l International Standard does not
function;
define the nature of any implementation intended eo provide the state management
-
specify the manner in which management is accomplished by the User of the state management function;
-
define the nature of any interactions that result in the use of the state management function;
-
specify the Services necessary for the establishment, normal and abnormal release of a management
association;
preclude the definition of further notification types;
define managed objects.
2
Normative references
The following CCITT Recommendations and International Standards contain provisions which, through reference in
this text, constitute provisions of this Recommendation I International Standard. At the time of publication, the editions
indicated were valid. All Recomrnendations and Standards are subject to revision, and Parties to agreements based on
this Recommendation I International Standard are encouraged to investigate the possibility of applying the most recent
CCITT Rec. X.731(1992 E) 1
---------------------- Page: 5 ----------------------
ISOLIEC 10164-2 : 1993 (E)
editions of the Recommendations and Standards indicated below. Members of IEC and ISO mainhin registers of
currently valid International Standards. The CCITT Secretariat maintains a list of the currently valid CCITT
Recommendations.
21 l
Identical Recommendations I International Standards
-
CCITT Recommendation X.701 (1992) I 1SOIIEC 10040: 1992, Information technology - Open Systems
Interconnection - Systems management overview.
- CCITT Recommendation X.720 (1992) !l ISO/IEC 101651:1993, Information technology - Open
Systems Interconnection - Structure of management information: Management information model.
-
CCITT Recommendation X.721 (1992) I ISO/IEC 10165-2: 1992, Information technology - Open
Systems Interconnection - Structure of management information: Definition of management
information.
-
CCITT Recommendation X.722 (1992) l ISO/IEC 10165-4:1992, Information technology - Open
Systems Interconnection - Structure of management information: Guidelines for the definition of
managed objects.
-
CCITT Recommendation X.732 (1992) l ISO/IEC 10164-3:1993, Information technology - Open
- Systems Management: Attributes for representing relationships.
Systems Interconnection
-
CCITT Recommendation X.733 (1992) l ISOLEC 10164-4:1992, Information technology - Open
Systems Interconnection - Systems Management: Alarm reporting function.
- CCITT Recommendation X.734 (1992) l ISO/IEC 10164-5:1993, Information technology - Open
Systems Interconnection - Systems Management: Event report managementfunction.
-
CCITT Recommendation X.735 (1992) I HSO/IEC 10164-6:1993, Information technol’ogy - Open
Systems Interconnection - Systems Management: Log controljunction.
22 0 Paired Recommendations I International Standards equivalent in technical content
- CCITT Recommendation X.200 (1988), Reference Model of Open Systems Interconnection for CCIlT
Applications.
ISO 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference
Model.
- CCITT Recommendation X.209 (1988), Specijication of basic encoding rules for Abstract Syntax
Notation One (ASN. 1).
ISO/IEC 8825: 1990, Information technology - Open Systems Interconnection - Specification of Basic
Encoding Rules for Abstract Syntax Notation One (ASN.1).
-
CCITT Recommendation X.210 (1988), Open Systems Interconnection Layer Service Definition
Conventions.
ISO/TR 8509: 1987, Information processing systems - Open Systems Interconnection - Service
conventions.
-
CCITT Recommendation X.290 (1992), OSI conformance testing methodology and framework for
protocol Recommendations for CCIIT applications - General concepts.
ISOIIEC 9646-1: 1991, Information technology - Open Systems Interconnection - Conformance testing
methodology andframework - Part I: General concepts.
-
CCITT Recommendation X.700 (1992), Management Framework Definition for Open Systems
Interconnection (OSI) for CCIlT Applications.
ISO/IEC 7498-4: 1989, Information processing systems
- Open Systems Interconnection - Basic
Reference Model - Part 4: Managementframework.
-
CCITT Recommendation X.710 (KW), Common Management Information Service Definition for
CCIlT applications.
ISO/lEC 9595: 199 1, Information technology - Open Systems Interconnection - Common management
information Service decfinition.
2 CCITT Rec. X.731(1992 E)
---------------------- Page: 6 ----------------------
ISOiIEC 10164-2 : 1993 (E)
23 0 Additional references
-
Open Systems Interconnection - Application layer
ISO/IEC 9545: 1989, Information technology -
structure.
Definitions
3
F’or the purposes of this Recommendation l International Standard, the following definitions apply.
31 0 Basic reference model definitions
This Recommendation I International Standard makes use sf tie following terms defined in CCITT Rec. X.200 l
ISO 7498:
open system;
a)
b) Systems management.
Management framework definitions
32 l
This Recommendation I International Standard makes use of the following term defined in CCITT Rec. X.700 I
ISOLIEC 7498-4:
managed Object
33 . CMIS definitions
This Recommendation l International Standard makes use of the following term defined in CCIT’I’ Rec. X.710 I
ISO/IEC 9595:
attribute
34 0 Systems management overview definitions
This Recommendation I International Standard makes use of the following terms defined in CCITT Rec. X.701 1
ISO/IEC 10040:
agent:
a)
agent role;
b)
dependent conformance;
c)
general conformance;
d)
generic defiiitions;
e)
managed Object class;
f)
manager;
8)
manager role;
h)
notification;
9
.
Systems management functional unit;
J)
Systems management function;
J-0
Systems management application protocol;
1)
(Systems management) Operation.
m)
35 l Management information model definitions
This Recommendation I International Standard makes use of the following term defined in CCITT Rec. X.720 I
ISO/IEC 10165-1:
managed Object boundary
3
CCITT Rec. X.731(1992 E)
---------------------- Page: 7 ----------------------
ISO/IEC 10164-2 : 1993 (E)
l Service conventions definitions
36
This Recommendation I International Standard makes use sf the following terms defined in CCITT Rec. X.210 I
ISO/TR 8509:
a) tonfirm (primitive);
b) confrrmed-Service;
c) indication (primitive);
d) non-confinned-Service;
request (primitive);
d
response (primitive).
f)
37 0 OS1 conformance testing definitions
This Recommendation l International Standard malces use sf the following terrn defined in CCITT Rec. X.290 I
ISOLIEC 9646- 1:
System conformance Statement
4
Abbreviations
ASN.1 Abstract Syntax Notation One
CMIS Common Management Information Service
Conf Confrrmation
Ind Indication
MAPDU Management application protocol data unit
0s Open Systems interconnection
Request
Req
Response
RsP
SMAPM Systems management application protocol machine
Structure of management information
SM1
5 Conventions
This Recommendation l International Standard defmes Services for the state management function following the
descriptive conventions defined in CCITT Rec. X.210 I ISO/TR 8509. In clause 9, the defmition of each Service
includes a table that lists the Service Parameters. For a given Service primitive, the presence of each Parameter is
described by one of the following values:
M the Parameter is mandatory;
the value of the Parameter is equal to the value of ehe Parameter in the column to the left;
(=)
U the use of the Parameter is a Service-user Option;
-
ehe Parameter is not present in the interaction described by the primitive concemed;
the Parameter is conditional;
C
the Parameter is subject to the constraints imposed by CCITT Rec. X.710 I ISO/IEC 9595.
P
NOTE - The Parameters that are marked “P” in Service tables of this Recommendation B International Standard are
mapped directly onto the corresponding Parameters of the @MIS Service primitive, without changing the semantics or Syntax of the
parameters. The remaining Parameters are used to construct an MAPDU.
4 CCITT Rec. X.731(1992 E)
---------------------- Page: 8 ----------------------
ISO/IEC 10164-2 : 1993 (E)
6
Requirements
The MIS-User needs the ability to examine and be notified of changes in state, to monitor overall operability and
usage of resources in a consistent specific resources.
manner, and to control the general availability of
This Recommendation l International Standard defines the generic attributes and operations that tan be part of any
managed Object definition in Order to provide a standardized OS1 management technique for dealing with management
states.
The state management provides for
the reporting of changes in the state attributes;
reading the state attributes;
changing the state attributes.
Modell
The management state of a managed Object represents the instantaneous condition of availability and operability of the
’ associated resource from the Point of view of management. Different classes of managed Object have a variety of state
attributes that express and control aspects of the Operation of their associated resource that are peculiar to each class.
However, the management state is expected to be common to a large number of resources and for this reason is
standardized; it expresses key aspects of their usability at any given time. Its purpose is to control the general
availability of a resource and to make visible information about that general availability.
71 0 Generic states
Three primary factors affect the management state of a managed Object with regard to its corresponding
resources’
availability. Some managed objects may not be affected by all three of these factors. These are
-
operability: whether or not the resource is physically installed and working, if applicable;
-
usage: whether or not the resource is actively in use at a specific instant, and if so, whether or not it has
spare capacity for additional users at that instant. A resource is said to be “in use” when it has received
one or more requests for Service that it has not yet completed or otherwise discharged, or when some
part of its capacity has been allocated, and not yet reclaimed, as a result of a previous Service request;
administration: permission to use or Prohibition against using the resource, imposed through the
management Services.
The state of a managed Object does not affect its ability to respond to management operations.
7.1.1 Operational state
The operability of a resource is described by the operational state attribute, which has two possible values: disabled
and enabled. These are described in 8.1.1.1.
Some classes of managed Object exhibit only a constant enabled value for the operational state. When a resource has
no visible dependencies on other resources, and no components that tan develop visible defects, the managed Object
may not exhibit the disabled operational state. Likewise, managed objects that cease to exist when the resource
becomes inoperable do not exhibit the disabled operational state during their existente. When a resources ceases to
exist, but there is still a managed Object maintaining state attributes about that resource, then the operational state will
be disabled. The set of operational state values supported is specified in each individual managed Object class
definition.
#en a managed Object is unable to reflect the operational state of its associated resource and the unknown Status
.
attribute defined in 8.1.2. 61 s supported, the unknown Status attribute value will be true.
Specific events associated with the resource Cause specific tran sitions from one operational state value to the other.
These events and transitions are summarised in Figure 1, and are described below.
CCITT Rec. X.731(1992 E) 5
---------------------- Page: 9 ----------------------
ISOmC 10164-2 : 1993 (E)
ENABLED
57
Enable Di sable
DISABLED
tLI
TI SO01 20-92
Figure 1 - Operational state diagram
7.1.1.1 Enable
T’his event consists of action being taken to render the resource partially or fully operable. This event tan occur only if
the managed object’s operational state is disable8. The enable event Causes a transition to the enabled operational
state,
7.1.1.2 Disable
This event consists sf some occurrence that renders ehe resource totally inoperable. The disable event Causes a
transition to the disabled operational state.
7.1.2 Usage state
The usage of a resource is described by the usage state attribute, which has three possible values: idle, active and busy.
These are described in 8.1.1.2. The set of usage state values supported is specified in each individual managed Object
class definition.
Some classes of managed Object exhibit only a subset of the possible usage state values. Managed objects whose
associated resource supports only one User do not exhibit the active usage state, being either idle or busy. Managed
objects whose resource has no practical limit on the number of users do not exhibit the busy usage state.
When a managed Object is unable to reflect the usage state of its associated resource and the unknown Status attribute
defmed in 8.1.2.6 is supported, the unknown Status attribute value will be true.
It is the natural Operation of the resource that Causes usage state transitions to occur, and therefore management cannot
request a managed Object to Change from one usage state to another. Management tan only gather information about
ehe usage state of a managed Object; the usage state is read-only in nature.
Specific events associated with the resource Cause transitions from one usage state value to another. These events and
transitions are summarised in Figure 2 and are described below.
6 CCITT Rec. X.731(1992 E)
---------------------- Page: 10 ----------------------
ISOLIEC 10164-2 : 1993 (E)
User
New
quit
user
(nonsharable
(nonsharable
Object)
Object)
I
I
r
Figure 2 - Usage state diagram
7.1.2.1 New user
This event consists of some agency commencing to use the resource. It tan occur only if the managed object’s
operational state is enabled and its usage state is either idle or active. The new User event Causes a transition as
follow s:
-
if, after the event, the resource still has sufficient operating capacity to provide for additional users, the
usage state becomes or remains active,
-
if, after the event, the resource has no operating capacity to spare for additional users, the usage state
becomes busy.
7.1.2.2 User quit
This event consists of an existing user of the resource terminating its use. It tan occur only if the managed object’s
usage state is either active or busy. It tan result from a Change of operational state from enabled to disabled. The user
quit event Causes a transition as follows:
-
if, after the event, the resource still has existing users, the usage state becomes or remains active;
-
if, after the event, the resource has no users, the usage state becomes idle.
7.1.2.3 Capacity increase (CI)
This event consists of an increase in the maximum operating capacity of the resource. It is significant only if the
managed object’s usage state is busy. The capacity increase event Causes a transition to the active state if the managed
Object was in the busy state.
7.1.2.4 Capacity decrease (CD)
This event consists of a decrease in the maximum operating capacity of the resource. It is significant only if the
managed object’s usage state is active. The capacity decrease event Causes a transition as follows:
-
if, after the event, the resource still has spare operating capacity, the usage state remains active;
-
if, after the event, the resource has no spare operating capacity, the usage state becomes busy;
-
if the managed Object is in the busy state when a capacity decrease occurs, the managed Object will
continue to reside in the busy state until either a capacity increase or a user quit event occurs.
7
CCITT Rec. X.731(1992 E)
---------------------- Page: 11 ----------------------
ISO/IEC 10164-2 : 1993 (E)
7.1.3 Administrative state
The administration of managed operability and usage of managed objects and 1s
objects operates independently ,ofthe
described by the administrative state attribute, which has three values. These are represented in a third state diagram in
Figure 3. These administrative states are called locked, unlocked and shutting down and are described in 8.1.1.3.
Some classes of managed Object exhibit only a subset of the possible administrative state values. Some resources
cannot be locked, and hence their corresponding managed objects exhibit only the unlocked state, Other resources tan
not be shut down gracefully, and hence their corresponding managed objects do not exhibit the shutting down state.
The actual subset of administrative state values supported varies from one class of managed Object to another, and is
specified in each individual managed Object definition.
Specific events associated with the managed Object Cause specific transitions from one administrative state value to
a-nother, depending upon the original value of the administrative state, the specific event, and also upon the number of
users of the resource. These events an d transitions are summarised in Figure 3, and are described below.
User
UNLOCKED
quit
I
Shut
Unlack Unlack down
Shut
fxgi User
down
i quit
V
idle)
I
Läst
Lack
LOCKED
I I
TE001 40-92
Figure 3 - Administrative state diagram
7.1.3.1 Unieck
This event consists of an Operation being performed at the managed Object boundary to unleck the managed object’s
corresponding resource. It tan occur only if the managed object’s administrative state is locked or shutting down. It
Causes a transition to the unlocked administrative state.
7.1.3.2 Lack
This event consists of an Operation being performed at the managed Object boundary to leck the managed object’s
corresponding resource. It tan occur only if the managed object’s administrative state is unlocked or shutting down. It
Causes a transition to the locked administrative state.
7.1.3.3 Shut down
This event consists of an Operation being performed at the managed Object boundary to shut down the managed
Object’ s corresponding resource. It tan occur only if the managed object’s administrative state is unlocked. It Causes a
state transition as follows:
-
if, at the time of the event, the resource existing users, the administrative state becomes shutting
down;
if, at the time of the event, the resource has no users, ehe administrative state becomes locked.
8 CCITT Rec. X.731(1992 E)
---------------------- Page: 12 ----------------------
ISO/IEC 10164-2 : 1993 (E)
7.1.3.4 User quit
This event consists of an existing user of the resource terminating its use. It tan occur only if the managed object’s
administrative state is unlocked or shutting down. If the administrative state is unlocked, no administrative state
transition occurs. If the administrative state is shutting down, the user quit event Causes a transition as follows:
-
if, after the event, the resource still has existing users, the administrative state remains as shutting down;
-
if, after the event, the resource has no users, ehe administrative state becomes locked.
7.1.4 Dependencies among generic states
It is the responsibility of the managed Object class definer to specify which combinations of state values at-e, and which
are not, supported by each individual managed Object class.
#en all three state attributes are supported by a managed obj ect, the following are the possible combinations of
values for the three state attributes (see also Figure 4).
-
disabled, idle, locked: The resource is totally inoperable, it is not servicing any users and it is also
administratively prohibited from use. To make it available for use, both management permission (an
unleck Operation) and some corrective action are necessary.
- enabled, idle, locked: The resource is partially or fully operable, it is not servicing any users but is
administratively prohibited from use. To make it available for use, only management permission (an
unleck Operation) is required.
- enabled, active, shutting down: The resource is partially or fully operable and in use, but usage is
administratively limited to current instances of use. For an additional User to gain access, management
permission (an unleck Operation) is required. Otherwise, when all current users have terminated their
use of the resource, the managed Object will automatically transit to the enabled, idle, locked state.
- enabled, busy, shutting down: The resource is partially or fully operable and in use, but usage is
administratively limited to current instances of use; in addition, it has no spare capacity to provide for
additional users. For an additional user to gain access, beside waiting for an existing User to terminate,
management permission (an unleck Operation) is also required. Otherwise, when all current users have
terminated their use of the resource, the managed Object will automatically transit to the enabled, idle,
locked state.
- disabled, idle, unlocked: The resource is totally inoperable, it is servicing no users but it is not
administratively prohibited from use. To make it available for use, some corrective action is required
- enabled, idle, unlocked: The resource operable, it is not actually in use and is not
1s partially or fully
administratively prohibited from use.
- enabled, active, unlocked: The resource is partially or fully operable, it is currently in use and is not
administratively prohibited from use. It has sufficient spare capacity to provide for additional users
simultaneously.
- enabled, busy, unlocked: The resource is partially or fully operable, it is currently in use and it is not
administratively prohibited from use. Currently it has no spare capacity to provide for additional users.
For an additionaI user to gain access, it is necessary to wait for an existing User to terminate or for some
capacity increase to occur.
Figure 5 illustrates the combined state diagram of operational and administrative states.
Figure 6 illustrates the combined state diagram of administrative and usage states.
Figure 7 illustrates the combined state diagram of operational and usage states.
CCITT Rec. X.731(1992 E) 9
---------------------- Page: 13 ----------------------
ISO/IEC 10164-2 : 1993 (E)
UNLOCKED
1
ENABLED
DISABLED
4 _ .~--
--pp-- -----
-------
~-
*4
7
8+
3 5 5,lO ib
--- ~-~.
~. -
-b Active b Busy
Idle Idle
-~-- - _
1
1+ 4 1q 8 A 63 ?l
[ 1 1 II I
1
I I I 1 I I I
11,2 --
4
I I
SHUTTING DOWN
6
Active 4 - Busy
ENABLED
m
2
---l
-
4 4 11 l212
/
i-7
3
Idle 278
4
P-F
>
278
DISABLED
ENABLED
m 7
LOCKED
-92
1 Unlack
5 New user 9 Capacity increase
2 Lack 6 User quit 10 Capacity decrease
3 Enable 7 New user (nonsharable resource)
11 Shutdown
4 Disable 8 Last user quit
Figure 4 - Combined state diagram
10 CCITI’ Rec. X.731(1992 E)
---------------------- Page: 14 ----------------------
ISO/IEC 10164-2 : 1993 (E)
UNLOCKED
w
Enable
b
DISABLED
ENABLED
Disable
Unlack
ENABLED
Lack Lack
Unlack 1 Urdock
I
SHUTTING DOWN
I
m
Lack,
Last user quit
Enable
1
DISABLED ENABLED
Disable
LOCKED
TISOO160
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.