ISO/IEC 10737:1994

Information technology — Telecommunications and information exchange between systems — Elements of Management Information Related to OSI Transport Layer Standards

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Éléments d'information de gestion concernant les normes de la couche Transport OSI

General Information

• Status: Withdrawn
• Publication Date: 21-Sep-1994
• Withdrawal Date: 21-Sep-1994
• ICS: 35.100.40 - Transport layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 20-Dec-1998

Relations

• Parent: ISO/IEC 10737:1994/Amd 1:1994 - Information technology — Telecommunications and information exchange between systems — Elements of Management Information Related to OSI Transport Layer Standards — Amendment 1: NCMS Management
• Effective Date: 15-Apr-2008
• Parent: ISO/IEC 10737:1994/Cor 1:1997 - Information technology — Telecommunications and information exchange between systems — Elements of Management Information Related to OSI Transport Layer Standards — Technical Corrigendum 1
• Effective Date: 15-Apr-2008
• Revised: ISO/IEC 10737:1998 - Information technology — Elements of management information related to OSI Transport layer
• Effective Date: 15-Apr-2008
• Corrected By: ISO/IEC 10737:1994/Cor 1:1997 - Information technology — Telecommunications and information exchange between systems — Elements of Management Information Related to OSI Transport Layer Standards — Technical Corrigendum 1
• Effective Date: 06-Jun-2022
• Amended By: ISO/IEC 10737:1994/Amd 1:1994 - Information technology — Telecommunications and information exchange between systems — Elements of Management Information Related to OSI Transport Layer Standards — Amendment 1: NCMS Management
• Effective Date: 06-Jun-2022

Standards Content (Sample)

I N TE R NAT I O NA L
ISO/IEC
STANDARD 10737
First edition
1994-1 0-01
B
Information technology -
Telecommunications and information
- Elements
exchange between systems
of Management Information Related to OS1
Transport Layer Standards
Technologies de l'information - Télécommunications et échange
- Eléments d'information de gestion
d'information entre systèmes
concernant les normes de la couche Transport OS1
Reference number
ISO/IEC 10737:1994(E)

---------------------- Page: 1 ----------------------
ISOflEC 10737:1994(E)
Contents
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 reference .
3 Definitions .
3.1 Basic reference model .
3.2 Information model .
3.3 GDMO .
3.4 Management Framework .
4 Symbols and Abbreviations .
5 Elements of Transport Layer Management Information .
5.1 Managed Object Hierarchy .
5.1.1 Summary of managed objects .
5.1.2 Relationships .
5.1.2.1 General description .
5.1.2.2 Layer n-1 Services .
5.1.2.3 Connections .
Minimum Event Filtering Capabilities .
5.1.3
5.1.4 Use of Optional Fields .
5.2 Common Transport Layer GDMO Definitions .
The transport subsystem managed object .
5.3
O ISO/IEC 1994
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any me
electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher.
ISOLEC Copyright Office Case postale 56 CH-121 1 Genève 20 Switzerland
Printed in Switzerland
ii

---------------------- Page: 2 ----------------------
ISODEC 10737:1994(E)
5.4 The transport entity managed object . 8
5.5 The connectionless-mode transport protocol Machine MO . 10
5.6 The Connection-Oriented Transport Protocol Machine MO . 13
5.7 The TSAP Managed Object . 16
5.8 The Transport Connection Managed Object and IVMO . 17
5.8.1 The Transport Connection Managed Object . 17
5.8.2 Transport Connection IVMO . 19
5.8.3 Elements of management Information for transportConnection MO and transport
Connection IVMO . 20
6 ASN.l Modules . 29
6.1 Object identifier definitions . 29
6.1.1 Abbreviations . 29
6.1.2 Other Object Identifier Definitions . 29
6.2 Other Definitions . 29
7 Conformance . 30
7.1 Conformance requirements to this International Standard . 30
7.2 Protocol specific conformance requirements . 30
Conformance to the management operation of IS0 8073 . 30
7.2.1
Conformance to the management operation of IS0 8602 . 30
7.2.2
A Allocation of Object Identifiers . 31
B Shorthand Description of Managed Objects . 34
C Examples of the use of relationships . 39
Index . 41

---------------------- Page: 3 ----------------------
0 ISO/IE(
ISOnEC 10737: 1994(E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the
specialized system for worldwide standardization. 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.
In the field of information technology, IS0 and IEC have establiihed a joint technical 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 at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 10737 was prepared by joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems.
Annex A forms an integral part of this International Standard. Aqnexes B and C are for information only.
iv

---------------------- Page: 4 ----------------------
O ISO/IEC ISOhEC 10737:1994(E)
Introduction
This document is one of a set of International Standards produced to facilitate the interconnection of open systems. The set of
International Standards covers the services, protocols and management information required to achieve such interconnection.
This International Standard is positioned with respect to other related International Standards by the layers defined in the
Reference Model for Open Systems interconnection (IS0 7498). In particular, it is concerned with the definition of Transport
Layer management information.
B

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD O ISOLEC ISODEC 10737:1994(E)
Information technology - Telecommunications and information
exchange between systems - Elements of Management
Information Related to OS1 Transport Layer Standards
1 Scope
This International Standard provides the specification of management information within an Open System related to those
operations of the OS1 Transport Layer specified by CCITT Recommendations and International Standards. Specifics on how
Transport layer management is accomplished is beyond the scope of this document. Transport Layer management information
is defined by specifying:
B
the managed object class definition of Transport Layer Managed Objects following guidelines put forth by the Structure
of Management Information (ISO/IEC 10165 and CCITT Recommendations X.720 - X.723),
0 the relationship of the Managed Objects and attributes to both the operation of the layer and to other objects and attributes
of the layer, and
the action type operations on the attributes of Transport Layer Managed Objects that are available to OS1 Systems
Management.
2 Normative references
The following CCITT Recommendations and International Standards contain provisions which, through reference in this text
, constitute provisions of this International Standard. At the time of publication, the editions indicated were valid. All
Recommendations and Standards are subject to revision, and parties to agreements based on this International Standard are
encouraged to investigate the possibility of applying the most recent editions of the Recommendations and Standards listed
below. Members of IEC and IS0 maintain registers of currently valid international standards. The CCITT Secretariat
maintains a list of the currently valid CCITT Recommendations.
Identical Recommendations I International Standards
2.1
i
1 CCITT Recommendation X.701 (1992) I ISO/IEC 10040: 1992, Information technology - Open Systems Interconnection -
Systems management overview.
CCITT Recommendation X.720 (1992) I ISO/IEC 10165- 1: 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) I ISO/IEC 10165-4: 1992, Information technology - Open Systems Interconnection -
'
Structure of management information: Guidelines for the definition of managed objects.
CCITT Recommendation X.723 (1991) I ISO/IEC 10165-5:-l) ~ Information technology - Open Systems Interconnection -
Structure of Management Information: Generic management information.
1 1) To be published.
1

---------------------- Page: 6 ----------------------
ISO/IEC 10737:1994(E) O ISO/EC
CCIïT Recommendation X.730 (1992) I ISOLEC 10164-1: 1993, Information technology - Open Systems Interconnection -
Systems Management: Object Management Function.
CCITT Recommendation X.731 (1992) I ISOLEC 10164-2: 1993, Information technology - Open Systems Interconnection -
Systems Management: State management function.
CCITT Recommendation X.732 (1992) I ISOLEC 10164-3: 1993, Information technology - Open Systems Interconnection -
Systems Management: Attributes for representing relationships.
CCITT Recommendation X.733 (1992) I ISOLEC 10164-4: 1992, Information technology - Open Systems Interconnection -
Systems Management: Alarm reporting function.
CCITT Recommendation X.734 (1992) I ISOLEC 10164-5: 1993, Information technology - Open Systems Interconnection -
Systems Management: Event report management function.
Paired Recommendations I International Standards equivalent in technical content
2.2
I
CCITT Recommendation X.200 (1988), Reference Model of Open Systems Interconnection for CCITT Applications.
IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model.
CCIïT Recommendation X.208 (1988), Specifcation of Abstract Syntax Notation One (ASN. 1).
ISOIIEC 8824: 1990, Information technology - Open Systems Interconnection - Specification of the Abstract Syntax
Notation One (ASN.1).
CCITT Recommendation X.214 (1988), Transport service definition for Open Systems Interconnection for CCITT
applications.
IS0 8072: 1994, Information technology - Open Systems Interconnection - Transport service definition.
CCITT Recommendation X.224 (1988), Transport protocol specification for Open Systems Interconnection for CCITT
applications.
ISOIIEC 8073: 1992, Information technology - Telecommunications and information exchange between systems - Open
Systems Interconnection - Protocol for providing the connection-mode transport service.
CCITT Recommendation X.700 (1992), Management Framework for Open Systems Interconnection for CCIlT applications.
IS0 7498-4: 1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 4:
Management Framework.
CCITT Recommendation X.7 10 (199 1), Common Management Information Service Definition for CCIlT applications.
IS0 9595: 199 1, Information technology - Open Systems Interconnection - Common management information service
definition.
CCITT Recommendation X.7 1 1 (199 1), Common Management Information Protocol Specification for CCITT applications.
IS0 9596- 1 : 199 1, Information technology - Open Systems Interconnection - Common management information
service protocol - Part I: Specification.
2.3 Additional reference
IS0 8602: 1987, Information processing systems - Open Systems Interconnection - Protocol for providing the
connectionless-mode Transport Service.
2

---------------------- Page: 7 ----------------------
ISODEC 10737:1994(E)
O ISO/IEC
3 Defïni tions
3.1 Basic reference model
This International Standard makes use of the following terms defined in IS0 7498.
a) Open System
(N)-service-access-point
b)
cl Transport Layer
4 Transport Protocol
e> Layer Management
f) Systems management
D 3.2 Information model
This International Standard makes use of the following terms defined in ISOAEC 10165-1.
Attributes
Attribute type
Containment
Distinguished Name
Inheritance
Managed Object
Management Operations
Notifications
i’r Object Class
Relative Distinguished Name
Subclass
Superclass
3.3 GDMO
This International Standard makes use of the following terms defined in ISOAEC 10165-4.
a) Managed Object Class Definition
b) Template
cl Parameter
3.4 Management Framework
This International Standard makes use of the following term defined in IS0 7498-4.
Management Information
3

---------------------- Page: 8 ----------------------
0 ISO/IEC
ISODEC 10737:1994(E)
4 Symbols and Abbreviations
Within the Managed Object definitions and GDMO templates the following abbreviations are used in the standard-name
element of a document-identifier when making references to other documents.
DMI CCITT Rec X.721(1992) I ISOAEC 10165-2: 1992
I ISOAEC 10165-5
GMI CCITT Rec X.723
This International Standard makes use of the following symbols and abbreviations.
AK TPDU Data Acknowledge TPDU
CMIP Common Management Information Protocol
CMIS Common Management Information Service
DR TPDU Disconnect Request TPDU
EA TPDU Expedited Acknowledge TPDU
ED TPDU Expedited Data TPDU
ER TPDU Error TPDU
Guidelines for Definition of MOs
GDMO
IVMO Initial Values Managed Object
MO Managed Object
os1 Open Systems Interconnection
PM Protocol machine
RDN Relative Distinguished Name
TC Transport Connection
TPDU Transport Protocol Data Unit
TSAP Transport Service Access Point
5 Elements of Transport Layer Management Information
5.1 Managed Object Hierarchy
5.1.1 Summary of managed objects
The following set of managed objects are defined for the Transport Layer:
Transport Subsystem managed object (transportSubsystem, see 5.3)
a)
Transport Entity managed object (transporflntity, see 5.4)
b)
Connectionless Transport Protocol Machine managed object (clmodeTPM, see 5.5)
cl
Connection-Oriented Transport Protocol Machine managed object (comodeTPM, see 5.6)
d)
Transport SAP managed object (tSAP, see 5.7)
e)
Transport Connection managed object (transportConnection, see 5.8.1)
f)
Transport Connection Initial Values managed object (transportConnectionIVM0, see 5.8.2)
g)
These Managed Objects represent OS1 Management's view of those elements of an Open System which support the OS1
Transport Service subject to OS1 management operations. The containment hierarchy is illustrated in figure 1. Managed
objects which can have multiple instances are illustrated by multiple boxes. These objects are defined in detail in the following
subclduses.

---------------------- Page: 9 ----------------------
O ISO/IEC ISOAEC 10737: 1994(E)
Transport
Subsystem
MO
CO-Mode
CL-Mode
Transport
D Transport
PM MO
Transport
Transport
Connection
Connection
Figure 1 - Transport Layer Containment: Hierarchy
5.1.2 Relationships
5.1.2.1 General description
B
The use of Relationship attributes is illustrated by examples in Annex C of this Intemational Standard. The following describes
the individual relationships for Transport layer in more detail.
5.1.2.2 Layer n-1 Services
The Transport Layer Entity has a relation (actualNSAP) to the NSAP MO.
, 5.1.2.3 Connections
There is a relationship (underlyingConnectionNames) between a Transport Connection MO and its underlying Network
,
Layerconnection MO (if one exists).
1
5

---------------------- Page: 10 ----------------------
ISODEC 10737:1994(E) 0 ISO/IEC
5.1.3 Minimum Event Filtering Capabilities
The transport layer management definitions embodied in this specification imply the frequent and possibly excessive
generation of notifications of notifications during regular layer operation. These notifications are especially useful for effective
fault management where they facilitate the tracing and pinpointing of error situations. To avoid the excessive dissemination of
these event reports under normal operating conditions, it is advisable for a managed system to have as a minimum the
capability to perform discrimination based on
the source managed object class;
a)
the object Identifier values in the probable cause and specific problems field of Communication alarms, and the
b)
communication type field of Communication informations.
5.1.4 Use of Optional Fields
Where reference is made in this International Standard to ASN.l syntax defined in Rec. X.723 I ISO/IEC 10165-5 or
Rec.X.721 I ISOAEC 10165-2, only the following fields shall be employed:
those which are not OPTIONAL in the ASN.l syntax;
a)
those which are OPTIONAL, but whose use is explicitly required by this International Standard;
b)
those which are OPTIONAL, but whose ASN.l type is SET OF MngmntExtension.
c)
The use of any other field is prohibited.
5.2 Common Transport Layer GDMO Definitions
commonCreationDeletion-B BEHAVIOUR
DEFINED AS
!Managed object class imports the 10165-2 objectcreation and objectDeletion
notifications. Used as follows:
Objectcreation - Generated whenever an instance of the managed object class is
created. Implementations may optionally include the sourceIndicator parameter ii
the notification. If creation occured as a result of internal operation of the
resource, the value 'resourceOperation' is used.If creation occured in response
to a management operation, the value 'managementoperation' is used. A value of
'unknown' may be returned if it is not possible to determine the source of the
operation. None of the other optional parameters are used.
ObjectDeletion - Generated whenever an instance of the managed object class is
deleted. Implementations may optionally include the sourceIndicator parameter in
the notification. if deletion occured as a result of internal operation of the
resource, the value 'resourceOperation' is used. If deletion occured in response
to a management operation, the value 'managementoperation' is used. A value of
'unknown' may be returned if it is not possible to determine the source of the
operation. None of the other optional parameters are used.!;
commonStateChange-B BEHAVIOUR
DEFINED AS
!Managed object class imports the 10165-2 statechange notification. Used to
report the changes to the operationalstate attribute, and where present, the
administrativeState attribute. A single parameter set is included in the State
change definition field. Only the (mandatory) attributeId and (optional)
newAttributeValue parameters are used.!;
octetsSentReceivedCounter-B BEHAVIOUR
DEFINED AS
!The octetsSentCounter and octetsReceivedCounter shall count only user data
octets in valid data TPDUs. They shall not count user data octets in data TPDUs
which are rejected for any reason, nor user data octets in non-data TPDUs.!;
6

---------------------- Page: 11 ----------------------
O ISOIIEC ISOBEC 10737:1994(E)
successfulConnectionEstablishment-B BEHAVIOUR
DEFINED AS
!This Package imports the comunicationsInformation notification from "GMI". It
is used to report the following events :
successfulConnectionEstablishment: Generated when a connection is successfully
established. However the precise synchronization between the notification and
the corresponding protocol and service interface interactions is not defined by
this Specification
The value TLM.successfu1ConnectionEstablishment shall be reported in the
informationType field.!;
deactivateConnection-B BEHAVIOUR
DEFINED AS
!The deactivate action causes the connection to be terminated. The termination
should occur as rapidly as practical, but no particular time constraints are
implied. Typically, this action simulates a disconnect request received across
the service interface. If a more rapid means for terminating the connection
exists, then this should be used. The termination shall occur in conformance to
the protocol standard. The Managed Object remains in existence after completion
of the Deactivate Action. It is subsequently deleted when the connection is
B
terminated, in the same way as if the connection has been terminated by other
means. A Deactivate action may fail (with the ProcessingError response) if it is
temporarily not possible to terminate the connection.!;
resettingTimer-B BEHAVIOUR
DEFINED AS
!This attribute specifies the interval between certain events in the operation
of the protocol state machine. If the value of the attribute is changed to a new
value while the protocol state machine is in operation, the implementation shall
take the necessary steps to ensure that for any time interval which was in
progress when the corresponding attribute was changed, the next expiration of
that interval takes place no later than the expiration of the interval in
progress or the specified interval whichever is the sooner. The precision with
which this time shall be implemented shall be the same as that associated with
the basic operation of the timer attribute.!;
5.3 The transport subsystem managed object
-- Managed Object for Transport Layer Subsystem
D -- There is exactly one of these MOs within
-- a system. It exists to provide a container for the layer entity MOs.
--
-- The transportsubsystem managed object cannot be created or deleted
-- explicitly by management operation. It exists inherently in a system;
-- created and deleted as part of system operation.
transportsubsystem MANAGED OBJECT CLASS
DERIVED FROM "GMI " : subsys tem;
-- which is derived from "DM1":top
CHARACTERIZED BY transportsubsystem-P PACKAGE
ATTRIBUTES
"GMI" : subsystemId
INITIAL VALUE TLM.transportSubsystemId-Value
GET ;
..
I,
REGISTERED AS {TLM.moi transportsubsystem (1));
-- Name Bindings
transportSubsystem-system NAME BINDING
SUBORDINATE OBJECT CLASS transportsubsystem AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS "DM1":system AND SUBCLASSES;
7

---------------------- Page: 12 ----------------------
ISOflEC 10737:1994(E) 0 ISO/IEC
WITH ATTRIBUTE "GMI" : subsystemId;
REGISTERED AS {TLM.nboi transportsubsystem-system (1));
5.4
The transport entity managed object
-- There may be multiple instances of these MOs within a system.
-- Its definition permits it to be deleted and created explicitly by
-- management operation, or to be created and deleted automatically
-- as part of system operation.
transportEntity MANAGED OBJECT CLASS
DERIVED FROM "GMI" : communicationsEntity;
-- which is derived from "DM1":top
CHARACTERIZED BY transportEntity-P PACKAGE
BEHAVIOUR tEPackageImportedNotifications-B,
commonCreationDeletion-B;
ATTRIBUTES
actualNSAP GET,
checksumErrorsDetected GET,
protocolErrors GET,
targetNSAP GET-REPLACE ADD-REMOVE,
undecodedNSDUs GET;
ATTRIBUTE GROUPS
-- The following attribute group is present in each of the transport
-- MOs which define counters. It allows all of the
-- counters to be retrieved in a single request.
"GMI I' :counters
checksumErrorsDetected
protocolErrors
undecodedNSDUs;
NOTIFICATIONS
-- protocolErrorNotification;
-- The following notification is issued by the entity MO
-- because in some cases it may be impossible to associate the
-- protocol Error with any of the protocol Machines.
"DM1":communicationsAlgrm
tEProtocolErrorPDUHeader
tEProtocolErrorSourceAddress
tEProtocolErrorReasonCode,
"DMI" : objectDeletion,
"DMI" : objectcreation; ; ;
REGISTERED AS {TLM.moi transportEntity (2));
-- Behaviours
-- Definition of the tEPackageImportedNotifications and of the mapping
-- of specific protocol error parameters into the fields of
-- communicationsAlarm Notification.
--
tEPackageImportedNotifications-B BEHAVIOUR
DEFINED AS
!Notification issued when a Transport Entity receives a PDU which is invalid or
contains a protocol error. The notification includes the header of the invalid
PDU, the source N-Address, and the reason why the PDU is considered to be in
error. The Reason code appears only if the protocol error relates to the
connection-mode protocol, and if it has been possible to relate the PDU to a
particular connection. The reason code is the value placed in the corresponding
parameter of the ER TPDU, if sent. The tEPackage imports the communicationsAlarm
Notification from DMI, in order to report the ProtocolError event. The
probablecause shall be sqt to TLM.communicationsProtocolError. The
tEProtocolErrorPDUheader, tEProtocolErrorSourceAddress and
tEProtocolErrorReasonCode are reported as parameters in the
additionalInformation field of the communicationsAlarm. The significance
subparameter of each item of the problemData shall be set to the value 'False'
(i.e. not significant) so that a managing system receiving the event will be
less likely to reject it. The perceivedseverity shall be set to Minor. A
8

---------------------- Page: 13 ----------------------
O ISO/IEC ISOhEC 10737:1994(E)
subsequent communicationsAlarm with a perceivedseverity value of 'Cleared' shall
not be generated. No other fields or parameters shall be used,with the exception
of further parameters in the additionalInformationfield.!;
-- Name Bindings
transportEntity-transportSubsystem-Automatic NAME BINDING
SUBORDINATE OBJECT CLASS transportEntity AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS transportSubsystem AND SUBCLASSES;
WITH ATTRIBUTE "GM1":comunicationsEntityId;
BEHAVIOUR transportEntity-transportSubsystem-Automatic-B BEHAVIOUR
DEFINED AS
!This name binding shall be used when the transportEntity MO is created
automatically by the operation of the system. The details of this operation
are outside the scope of this Specification.!;;
REGISTERED AS {TLM.nboi transportEntity-transportSubsystem-Automatic (11));
transportEntity-transportSubsystem-Management NAME BINDING
SUBORDINATE OBJECT CLASS transportEntity AND SUBCLASSES;
NAMED BY
SUPERIOR OBJECT CLASS transportsubsystem AND SUBCLASSES;
WITH ATTRIBUTE "GM1":communicationsEntityId;
BEHAVIOUR transportEntity-transportsubsystem-Management-B BEHAVIOUR
DEFINED AS
!This name bin
...