INTERNATIONAL
`
`ISO/IEC
`
`STANDARD
`
`7498-4
`
`First edition
`198941—15
`
`
`
`Information processing systems — Open
`Systems interconnection —— Basic Reference
`Model —
`
`Part 4 :
`
`Management framework
`
`Systémes de Ira/'rement de /’/'nf0rmat/'on — Interconnexion de systémes ouverts —
`Mode/e de reference de base —
`
`Part/e 4 .' Cadre ge’néra/ de gestion
`
`
`
`
`
`Reference number
`ISO/IEC 7498—4 : 1989 (E)
`
`NOAC EX1067 Page 1
`
`NOAC EX1067 Page 1
`
`

`

`lSO/IEC 7498-4 : 1989 (E)
`
`contents
`
`Page
`
`Foreword ................................ f ................
`
`Introduction ...............................................
`
`1
`
`2
`
`3
`
`Scope ................................................
`
`Normative references ....................................
`
`Definitions and abbreviations ..............................
`
`iii
`
`iv
`
`1
`
`1
`
`1
`
`2
`1 ..........................
`.
`.
`Concepts in OSI Management .
`4
`2
`4.1 Users’ requirements of OSl Management .......................
`4.2 The OSI Management environment ........................... 2
`4.3 Managed objects, their attributes and operations ..................
`2
`4.4 Management relationships between open systems ................
`2
`4.5
`08! Management functional areas ............................
`2
`
`3
`Model for OSI Management ................................
`5
`5.1 Overview .............................................. 3
`5.2 OSI Management structure .................................
`3
`5.3 Supporting functionality required by OSI Management ..............
`4
`5.4 Management Information Base ..............................
`4
`5.5
`Flow of management control ................................
`4
`5.6
`Flow of management information .............................
`4
`
`OSI Management specifics ................................
`6
`6.1 OSl Management standardization .............................
`6.2 OSI Management operation .................................
`6.3 The form of management information exchanges .................
`6.4 OSI Management conformance ..............................
`
`Annex A — Comments relating to the OSI Management Framework .....
`
`introduction ............................................
`A1
`A2 Abbreviations ...........................................
`
`A3 Brief Overview of OSI Management Scope and Concepts ...........
`A.4 Systems Management Standards .............................
`A5 Management Information and the Management information Base ......
`
`5
`5
`5
`6
`6
`
`7
`
`7
`7
`
`7
`8
`9
`
`0 lSO/IEC 1989
`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 publisher.
`
`ISO/IEC Copyright Office . Case postale 56 ~ CH-1211 Geneve . Switzerland
`Printed in Switzerland
`
`NOAC EX1067 Page 2
`
`NOAC EX1067 Page 2
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`Foreword
`
`ISO (the International Organization for Standardization) and IEC (the International
`Electrotechnical Commission) together form a system for worldwide standardization as
`a whole. National bodies that are members of ISO or IEC participate in the develop—
`ment 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,
`ISO/IEC JTC 1. Draft
`International Standards adopted by the joint
`technical committee are circulated to national bodies for approval before their accep-
`tance as International Standards. They are approved in accordance with procedures re-
`quiring at least 75 % approval by the national bodies voting.
`
`ISO/IEC 7498-4 was
`International Standard
`Committee ISO/IEC JTC 1, Information technology.
`
`prepared
`
`by
`
`Joint Technical
`
`NOAC EX1067 Page 3
`
`NOAC EX1067 Page 3
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`Introduction
`
`The Basic Reference Model of Open Systems interconnection (OSI), ISO/IEC 7498,
`provides a description of the activities necessary for systems to interwork using
`communication media. This part of ISO/IEC 7498 forms Part 4 of lSO/lEC 7498 and
`provides a description of the framework and structure of OSI Management in a way
`that supplements and clarifies the description of management contained in ISO / IEC
`7498.
`
`The purpose of this part of lSO/IEC 7498 is to provide a common basis for the
`coordinated development of management standards.
`
`It is also the purpose of this part of lSO/IEC 7498 to identify areas for developing or
`improving standards, and to provide a common reference for maintaining consistency
`of all related standards. It is not the intent ofthis part of lSO/IEC 7498 either to serve
`as an implementation specification, or to be a basis for appraising the conformance
`of actual implementations, or to provide a sufficient level of detail to define precisely
`the services and protocols of the management architecture. Rather,
`this part of
`lSO/IEC 7498 provides a conceptual and functional
`framework which allows
`independent
`teams of experts to work productively on the development of
`management standards.
`
`This part of lSO/IEC 7498 provides an extension to ISO/IEC 7498 and therefore
`assumes as a basis the concepts and terminology included therein. The objective of
`this document is to describe a framework for those management activities pertinent
`to OSI, and to identify the management services which are supported by OSI
`Management protocols.
`
`The description of the Management Framework given in this part of lSO/IEC 7498
`is developed in stages:
`
`Clause 1 defines the scope of this part of ISO/lEC 7498.
`
`Clause 2 lists related OSI Standards.
`
`Clause 3 defines terms and abbreviations used in this part of lSO/lEC 7498
`
`Clause 4 provides the description of general concepts relating to management.
`
`Clause 5 defines a model for OSI Management.
`
`Clause 6 introduces the areas of OSI Management standardization, specifies how
`each of the component parts of OSI Management operate and defines the form of
`management information exchanges.
`
`Management is manifest in a number of ways. Management is related to activities
`which control or monitor the use of resources. Within Open Systems the resources
`can be those which provide data storage or processing capabilities, or they can be
`those which provide interconnection capabilities.
`it
`is only the latter and the
`communications concerning their management which fall within the scope of OSI
`Management standardization.
`
`Human beings are ultimately responsible for managing the OSI Environment,
`although responsibilities may be delegated to automated processes.
`
`iv
`
`NOAC EX1067 Page 4
`
`NOAC EX1067 Page 4
`
`

`

`
`
`INTERNATIONAL STANDARD
`ISO/IEC 7498—4: 1989 (E)
`
`
`Information processing systems — Open Systems
`Interconnection — Basic Reference Model —
`
`Part 4 :
`
`Management framework
`
`1 Scope
`
`3 Definitions and abbreviations
`
`ISO/IEC 7498 establishes a framework for
`This part of
`coordinating the development of existing and future standards
`for OSI Management, and is provided for reference by those
`standards.
`
`It
`
`a) defines terminology of and describes concepts for OSI
`Management;
`
`This part of ISO/IEC 7498 makes use of the OSI
`3.1
`terminology defined in lSO/lEC 7498, specifically:
`
`a)
`
`(N)-entity
`
`b)
`
`(N)-layer
`
`c)
`
`(N)—protocol
`
`provides a structure for OSI Management together
`b)
`with an overview ofthe objectives of and facilities provided
`by OSI Management; and
`
`d)
`
`(N)-protocol-data-unit
`
`e) open system
`
`6) describes OSI Management activities.
`
`i) systems management
`
`This part of ISO/IEC 7498 does not specify services or
`protocols for OSI Management. It is neither an implementation
`specification for systems, nor a basis for appraising the
`conformance of implementations.
`
`2 Normative references
`
`The following standards contain provisions which, through
`reference in this text, constitute provisions of this part of
`ISO/IEC 7498. At the time of publication, the editions indi-
`cated were valid. All standards are subject to revision, and
`parties to agreements based on this part of ISO/IEC 7498 are
`encouraged to investigate the possibility of applying the most
`recent editions of the standards listed below. Members of IE0
`and ISO maintain registers of currently valid international
`Standards.
`
`ISO/IEC 7498:1984, Information processing systems - Open
`Systems Interconnection — Basic Reference Model.
`
`ISO/IEC 7498-2:1988, Information processing systems - Open
`Systems Interconnection - Basic Reference Model - Part 2:
`Security Architecture.
`
`3.2 Terms defined in lSO/lEC 7498 which are redefined for
`the purposes of this part of ISO /IEC 7498:
`
`An
`Systems management application-entity:
`3.2.1
`application-entity for the purpose of systems management
`communication.
`
`For the purpose of this part of ISO/IEC 7498,
`3.3
`following definitions apply:
`
`the
`
`The facilities to control, co-
`OSI Management:
`3.3.1
`ordinate and monitor the resources which allow communica‘
`tions to take place in the OSI Environment.
`
`(N)-layer operation: The monitoring and control of
`3.3.2
`a single instance of communication.
`
`3.3.3 Managed object: The OSI Management view of a
`resource within the OSI Environment that may be managed
`through the use of OSI Management protocol(s).
`
`3.3.4 Management Information Base: The conceptual
`repository of management information within an open system.
`
`NOAC EX1067 Page 5
`
`NOAC EX1067 Page 5
`
`

`

`ISO/IEC 7493-4 : 1989 (E)
`
`3.4 Abbreviations
`
`MIB Management Information Base
`
`OSI
`
`open systems interconnection
`
`OSIE OSI environment
`
`PDU
`
`protocol-data-unit
`
`SMAE systems management application-entity
`
`4 Concepts in OSI Management
`
`4.1 Users’ requirements of OSI Management
`
`4.3 Managed objects, their attributes and oper-
`afions
`
`A managed object is the OSI Management view of a resource
`within the OSIE that is subject to management, such as a
`layer entity, a connection or an item of physical communica—
`tions equipment. Thus a managed object is the abstracted
`view of such a resource that represents its properties as seen
`by (and for the purposes of) management.
`
`A managed object is defined in terms of attributes it pos—
`sesses, operations that may be performed upon it, notifica-
`tions that it may issue and its relationships with other man-
`aged objects. This is distinct from, but related to, any defini—
`tion or specification of the resource represented by the
`managed object as an element of the OSIE.
`
`Recognising the need for interconnection services which will
`carry information in a reliable and economic manner, OSI
`Management supports the users’ needs for
`
`The set of managed objects within a system, together with
`their attributes, constitutes that system's Management infor-
`mation Base (MlB).
`
`activities which enable managers to plan, organise,
`a)
`supervise, control and account forthe use of interconnec-
`tion services;
`
`b)
`
`the ability to respond to changing requirements;
`
`facilities
`c)
`behaviour; and
`
`to ensure predictable communications
`
`facilities which provide for information protection and
`d)
`for the authentication of sources of and destinations for
`transmitted data.
`
`The management tools which provide this support may vary
`in complexity depending upon the users’ requirements. Such
`tools may operate locally or co-operate across a number of
`open systems. OSI Management does not constrain the user
`interface.
`
`4.4 Management
`systems
`
`relationships between open
`
`The users' requirements for OSI Management may be met
`either by local operations or by the communication of
`information between open systems, or by both. OSI Manage—
`ment is achieved between open systemsthrough co-operation
`between one or more components ofthe management activity
`taking a managing role and others taking a managed role.
`The role played by a particular system may be static or may
`change over time, and may depend upon the particular
`management communication.
`
`OSl Management information flow between open systems is
`defined in terms of operations and notifications.
`
`4.5 OSI Management functional areas
`
`4.2 The OSI Management environment
`
`4.5.1 Introduction
`
`The OSl Management environment is that subset of the total
`08! environment (OSIE) which is concerned with the tools
`and services needed to monitor, control and coordinate
`interconnection activities. The OSI Management environment
`includes both the capability for managers to gather informa-
`tion and to exercise control, and the capability to maintain an
`awareness of and report on the status of resources in the
`OSIE.
`
`The individual open systems within the OSIE may have
`aspects of management responsibility delegated to them. The
`responsibility may be manifest in terms of
`
`a) autonomous management of the open system; and
`
`co-operation with other open systems, through the
`b)
`exchange of information, to perform coordinated manage-
`ment activities.
`
`individual
`responsibility is directed at
`This management
`resources, each of which may operate with a degree of
`independence from other
`resources. This management
`responsibility may be further extended to coordinate and
`control sets of resources to increase functionality and per-
`formance.
`
`is required for a number of purposes.
`OSl Management
`These requirements are categorized into a number of func—
`tional areas
`
`a)
`
`fault management (see 4.5.2);
`
`b) accounting management (see 4.5.3);
`
`o) configuration management (see 4.5.4);
`
`cl) performance management (see 4.5.5); and
`
`e) security management (see 4.5.6).
`
`Specific management functions, within these functional areas,
`are provided by OSl Management mechanisms. Many of the
`mechanisms are general in the sense that they are used to
`fulfil requirements in more than one functional area. Similarly,
`managed objects are general in the sense that they may be
`common to more than one functional area.
`
`Each of these functional areas is described briefly below. The
`lists of functions are not necessarily exhaustive.
`
`NOAC EX1067 Page 6
`
`NOAC EX1067 Page 6
`
`

`

`ISO/IEC 7493-4 : 1989 (E)
`
`4.5.2 Fault management
`
`to
`
`Fault management encompasses fault detection, isolation and
`the correction of abnormal operation of the OSI Environment.
`Faults cause open systems to fail to meet their operational
`objectives and they may be persistent or transient. Faults
`manifest themselves as particular events (e.g. errors) in the
`operation of an open system. Error detection provides a
`capability to recognise faults. Fault management includes
`functions to
`
`a) maintain and examine error logs;
`
`a) gather statistical information;
`
`b) maintain and examine logs of system state histories;
`
`determine system performance under natural and
`c)
`artificial conditions; and
`
`alter system modes of operation for the purpose of
`d)
`conducting performance management activities.
`
`b) accept and act upon error detection notifications;
`
`4.5.6 Security’management
`
`c)
`
`trace and identify faults;
`
`d) carry out sequences of diagnostic tests; and
`
`the
`is to support
`The purpose of security management
`application of security policies by means of functions which
`include
`
`e) correct faults.
`
`the creation, deletion and control of security services
`a)
`and mechanisms;
`
`4.5.3 Accounting management
`
`b)
`
`the distribution of security-relevant information; and
`
`Accounting management enables charges to be established
`for the use of resources in the OSlE, and for costs to be
`identified for the use ofthose resources. Accounting manage-
`ment includes functions to
`
`c)
`
`the reporting of security-relevant events.
`
`NOTE - ISO/iEC 7498-2 provides further information on the place-
`ment of OSI Management functions within the overall Security
`Architecture.
`
`a) inform users of costs incurred or resources consumed;
`
`b) enable accounting limits to be set and tariff schedules
`to be associated with the use of resources; and
`
`0) enable costs to be combined where multiple resources
`are invoked to achieve a given communication objective.
`
`4.5.4 Configuration management
`
`Configuration management identifies, exercises control over,
`collects data from and provides data to open systems for the
`purpose of preparing for, initialising, starting, providing for the
`continuous operation of, and terminating interconnection
`services. Configuration management includes functions to
`
`5 Model for OSI Management
`
`5.1 Overview
`
`OSI Management encompasses those activities needed to
`control, coordinate and monitor the resources which allow
`communications to take place in the OSI Environment.
`Activities relate to the means by which
`
`a) a real open system obtains information to enable the
`supervision and control of its communications resources;
`and
`
`real open systems cooperate to supervise and control
`b)
`the OSI Environment.
`
`a) set the parameters that control the routine operation
`of the open system;
`
`The model of OSI Management is defined in terms of
`
`b) associate names with managed objects and sets of
`managed objects;
`
`c)
`
`the OSI Management structure (see 5.2);
`
`0)
`
`initialize and close down managed objects;
`
`information on demand about the current
`collect
`d)
`condition of the open system;
`
`e) obtain announcements of significant changes in the
`condition of the open system; and
`
`f) change the configuration of the open system.
`
`the supporting functionality required by OSl Manage-
`d)
`ment (see 5.3);
`
`e)
`
`the Management Information Base (see 5.4);
`
`f)
`
`the flow of control amongst processes (see 5.5); and
`
`g)
`
`the flow of information between entities (see 5.6).
`
`5.2 03! Management structure
`
`4.5.5 Performance management
`
`Performance management enablesthe behaviour of resources
`in the OSlE and the effectiveness of communication activities
`to be evaluated. Performance management includes functions
`
`is effected through a set of management
`Management
`processes. These processes are not necessarily located at
`one local system but may be distributed in many ways over
`a number of systems. Where management processes which
`are not co-resident need to communicate with one another
`
`NOAC EX1067 Page 7
`
`NOAC EX1067 Page 7
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`they communicate using OSI
`in the OSI Environment,
`Management protocols. OSI Management is accomplished
`through
`
`a) systems management;
`
`b)
`
`(N)-layer management; and
`
`c)
`
`(N)-layer operation.
`
`Systems management provides mechanisms for the monitor-
`ing, control and coordination of managed objects through the
`use of application-layer systems management protocols. OSI
`communications concerning systems management functions
`are realized through a systems management application-
`entity (SMAE). Systems management may be used to manage
`any objects within or associated with an open system.
`
`(N)-layer management provides mechanisms for the monitor-
`ing, control and coordination of managed objects which relate
`to communications activities within the (N)—layer, through the
`use of special-purpose management protocols within the (N)-
`layer. (N)-layer management can affect multiple instances of
`communication. The (N)-|ayer may therefore be managed
`through the use of systems management protocols or through
`the use of (N)-layer management protocols.
`
`(N)-layer operation provides mechanisms for the monitoring
`and control of a single instance of communication.
`
`imply any particular
`This part of lSO/lEC 7498 does not
`relationships among management mechanisms.
`
`management information is standardized. This does not imply
`any form of physical or logical storage for the information and
`its implementation is a matter of local concern and outside
`the scope of OSI standards.
`
`Management information may be shared between manage-
`ment processes and structured according to the requirements
`of those processes. The MlB neither restricts the interpretation
`of management data to a pre-defined set, nor to whether the
`data is stored in a processed or unprocessed form. However
`both the abstract syntax and the semantics of information
`which is part of the MIB are defined so that they can be
`represented in OSI protocol exchanges.
`
`5.5 Flow of management control
`
`Management processes, which support OSI Management,
`receive control information
`
`from people and/or software acting as administrative
`a)
`agents local to a management process; and
`
`b)
`
`from remote systems through their:
`
`1) SMAEs
`2)
`(N)-layer management entities
`3)
`(N)-entities
`
`The management processes exert control
`
`directly upon managed objects in the same open
`0)
`system; and
`
`5.3 Supporting functionality required by OSI Man-
`agement
`
`upon managed objects in other open systems by
`d)
`protocol exchanges through their:
`
`An open system must have sufficient functionality at all seven
`layers to support an SMAE before the systems management
`functionality provided by that SMAE can be accessed by
`another open system.
`
`When the functionality to support any SMAEs does not exist,
`the greatest OSI Management
`functionality that can be
`available on such an open system is the set of separate,
`individual functionalities provided by the layer managements
`of the (N)—|ayers within that open system. in order to support
`(N)-layer management, sufficient communication functionality
`must exist at layers 1 to (N-1).
`
`When neither systems management nor (N)-layer manage-
`ment can be provided, then the greatest OSI Management
`functionality that can be available is the set of separate,
`individual management functionalities provided by (N)-layer
`operation.
`
`1) SMAEs
`2)
`(N)-layer management entities
`3)
`(N)-entities
`
`from administrative agents to local
`The flow of control
`management processes occurs entirely within the Local
`System Environment, and as such is outside the scope of OSI
`Management standardization. Such local control may result
`in OSI Management communications. The abstract syntax
`and semantics of control flow within the OSI Environment are
`defined so that they can be represented in OSI protocol
`exchanges.
`
`5.6 Flow of management information
`
`information within a Management
`The OSI Management
`Information Base may be provided by, and made available to
`
`An SMAE can exist on an open system independently of the
`existence of (N)—layer management entities at any of the
`layers.
`
`a)
`
`local administrative agents; and
`
`b)
`
`remote open systems, through:
`
`5.4 Management Information Base
`
`is that information
`A Management Information Base (MIB)
`within an open system which may be transferred or affected
`through the use of OSl Management protocols. The MlB is
`the set of managed objects within an open system, however
`only the managed objects relating to the OSI Environment are
`subject to standardization. In addition, the logical structure of
`
`1) systems management protocols
`2)
`(N)—|ayer management protocols
`3)
`(N)-protocols
`
`Information exchanges may provide monitoring information or
`may result in the exercise of control. Information exchanges
`between administrative agents and the MIB occur entirely
`within the local system and are outside the scope of OSI
`Management standardization.
`
`4
`
`NOAC EX1067 Page 8
`
`NOAC EX1067 Page 8
`
`

`

`6 OSI Management specifics
`
`6.1 OSI Management standardization
`
`Areas of OSI Management standardization include
`
`the services and protocols used to transfer manage-
`a)
`ment information between open systems; and
`
`the abstract syntax and semantics of the information
`b)
`transferred in management protocols.
`
`These areas of standardization apply to systems manage-
`ment, (N)—|ayer management and normal (N)—|ayer operation.
`
`The actual specification of the syntax, semantics, services and
`protocols, and the concepts applicable to managed objects
`are provided in specific OSl standards. The physical represen-
`tation of managed objects and their physical storage are local
`matters and are not subject to standardization.
`
`Systems management standards specifythe systems manage-
`ment services and protocols, plus the abstract syntax and
`semantics of the information transferred in such protocols.
`
`The (N)—|ayer management protocols and the management
`aspects of (N)-protocols are defined by international Stan-
`dards specifying those protocols in order to cover layer
`related aspects of the above management facilities. (N)-layer
`standards may specify (N)-layer management protocols and
`their use.
`
`This standard does not imply that any systems management
`protocols or layer management protocols are mandatory,
`neither does it constrain the use of management information
`in any (N)—protocol exchanges.
`
`6.2 OSI Management operation
`
`6.2.1 Systems management
`
`Systems management communications provide the normal
`method for exchanging OSI management information. These
`communications take place between Systems Management
`applications-entities. Systems Management protocols are
`application layer protocols. Any application-process which
`communicates according to Systems Management protocol
`standards does so through an SMAE. The service elements
`used to support Systems Management are Application Service
`Elements.
`
`Not all open systems provide the full functionality of the seven
`layers specified in ISO/IEC 7498. Where such open systems
`are not the initial source of, nor the ultimate destination for the
`transfer of data, they act for such instances of communication
`as relay open systems. Where such systems are required to
`act as sources of system management information or are
`subject
`to systems management control,
`information is
`communicated using systems management protocols.
`
`6.2.2 (N)-layer management
`
`(N)—layer management supports the monitoring, control and
`coordination of (N)-layer managed objects. (N)-layer manage-
`ment protocols are supported by protocols of the layers (N-i)
`and below. They do not provide communication capability
`
`ISO/IEC 7498-4 : 1989 (E)
`
`offered by the (N +l) and higher layers. (N)-layer management
`protocols can only convey management information between
`peer (N)-layer management entities pertinent to the (N)-sub-
`systems in which these entities reside.
`
`(N)—layer management protocols should only be used where
`special
`requirements dictate that systems management
`protocols are inappropriate or when systems management
`protocols are not available.
`
`(N)-layer management protocols provide such functions as
`
`communicating parameter values associated with
`a)
`managed objects which relate to the operation of the
`(N)-layer;
`
`b) testing the functionality provided by the (N-1)-layer;and
`
`information describing faults or
`conveying error
`c)
`diagnostic information related to the operation of the (N)-
`layer
`
`Each (N)-layer management protocol is independent of other
`layer management protocols. This part of ISO/lEC 7498 does
`not
`require the development of
`(N)-layer management
`protocols for each of the seven layers.
`
`6.2.3 (N)-layer operation
`
`Management functions may exist within the (N)—protocols in
`all seven layers of OSI. The management information that is
`carried within an (N)-protocol must be distinguishable from
`information which the protocol carries for other purposes. It
`is the responsibility of the (N)-protoco| to provide this distinc-
`tion.
`
`Management information carried by (N)-protocol exists for the
`purpose of controlling and monitoring a single instance of
`communication. Examples of management information carried
`within an (N)-protocol are
`
`a) parameters carried in connection establishment PDUs
`that apply to the specific instance of communication which
`is being established;
`
`parameters carried in particular PDUs which can
`b)
`modify the environment in which this instance of com-
`munication operates;
`
`0) error information describing faults encountered during
`the operation of that specific instance of communication;
`and
`
`d) parameters carried in connection release PDUs which
`report information pertaining to that specific instance of
`communication which is being released.
`
`6.2.4 Relationships between systems management, (N)-
`layer management and (N)-Iayer operation
`
`(N)-layer management and
`Whereas the specification of
`(N)-layer operation standards is not the concern of systems
`management,
`the
`semantics of
`(N)-layer management
`information and the operations permitted thereon must be
`consistent with such information and operations defined by
`systems management.
`
`NOAC EX1067 Page 9
`
`NOAC EX1067 Page 9
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`(N)-|ayer management entities are of different types from
`those (N)-entities which operate (N)-protocols as defined in
`lSO/lEC 7498. (N)-layer management protocols are distin-
`guished from normal (N)-protocols by the use of (N-1)-layer
`addressing mechanisms or by discrimination mechanisms
`within the (N)-layer.
`
`(N)-layer management entities and (N)—entities operate,
`independently of each other, upon managed objects which
`relate to the operation of the (N)—layer.
`
`(N)-services, or services provided specifically for
`normal
`management purposes. The information exchanges may be
`either 2-party or N—party in nature, depending upon the
`requirements of the initiator of the exchange and the nature
`of the services available to carry out the exchange.
`
`Any party may take the role of initiator in a management
`exchange; the remaining parties to the exchange take the role
`of responder. The exchange may be initiated forthe purposes
`of performing management operations or notifications.
`
`The form of management
`6.3
`changes
`
`information ex-
`
`6.4 OSI Management conformance
`
`Management information exchanges are effected by the use
`of Application Layer or (N)-layer services; these may be
`
`This part of lSO/IEC 7498 does not imply any conformance
`requirements for systems management, (N)-layer management
`or (N)-layer operation.
`
`NOAC EX1067 Page 10
`
`NOAC EX1067 Page 10
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`ANNEX A
`
`(informative)
`
`COMMENTS RELATING TO THE OSI MANAGEMENT FRAMEWORK
`
`A.1 Introduction
`
`The OSl Management Framework provides the concepts and an abstract model of OSI Management for use by those developing
`OSI Standards.
`
`The purpose of this Annex is to provide additional explanatory material as an aid to understanding the concepts in the body of
`this part of lSO/lEC 7498 and to explain their application.
`
`A.2 Abbreviations
`
`008 Quality of Service
`
`A.3 Brief Overview of OSI Management Scope and Concepts
`
`Three forms of management information exchange are defined within the OSI Management architecture for which standards are
`expected
`
`a) systems management;
`b)
`(N)—Iayer management; and
`c)
`(N)-layer operation.
`
`Systems management is the preferred form of management information exchange and provides mechanisms for the exchange
`of information relating to the monitoring, control and coordination of communications resources of concern to open systems. The
`Framework uses the term managed objects to describe the management view of these resources. Systems management acts
`upon managed objects in order to manage the resources to which these objects relate. Such managed objects can relate to one
`or more OSI layers.
`
`Systems Management
`Protocols
`
`
`
`
`
`
`
`
`7 —_App1ication 7
`_e
`.-
`5— —.
`
`
`4—
`-4
`
`
`
`3—
`—3
`
`
`
`2—
`_2
`
`
`
`1—
`—1
`
`
`Normal Communlcatlons
`Protocols
`
`Figure A.1 - Systems Management Information Exchange
`
`It is perceived that the majority of management information exchanges between open systems will require context negotiation, the
`establishment of a management session, a reliable end—to-end transport service etc., in exactly the same way as other application
`layer exchanges. Therefore systems management communication is effected through application layer protocols (see figure A.1).
`Note that the Framework does not exclude the use of connectionless services.
`
`Systems management services and protocols are being developed by the OSI Management Working Group in ISO.
`
`NOAC EX1067 Page 11
`
`NOAC EX1067 Page 11
`
`

`

`ISO/IEC 7498-4 : 1989 (E)
`
`(Ni-layer management is used in special circumstances to carry information relating specifically to the operation of an (N)-layer.
`An example of layer management is the transport layer network connection management subprotocol (NCMS). it is important
`to note that layer management at one layer should not replicate any of the functionality of the layers above it, as this would be at
`variance with the Basic Reference Model. Figure A.2 shows an example of such an exchange in the transport layer. (N)-layer
`management exchanges can occur in any layer, although layers 2, 3 and 4 are those where such standards are most likely to
`occur.
`
`Layer management standards are the responsibility of the relevant layer standards group, within ISO.
`
`
`
`
`
`
`
`Management Protocols
`
`
`
`
`
`
`
`
`
`Application
`
`Data Link
`
`Physical
`
`
`
`7 Application
`
`6 Presentation
`
`4
`
`a
`
`2 Data Link
`
`1 Physical
`
`Normal Communications
`Protocols
`
`7
`
`6
`
`4
`
`a
`
`2
`
`l
`
`7
`
`6
`
`5
`
`2
`
`1
`
`Figure A.2 - (N)-Layer Management Exc