ISO/IEC 9506-2:1990
(Main)Industrial automation systems - Manufacturing Message Specification - Part 2: Protocol specification
Industrial automation systems - Manufacturing Message Specification - Part 2: Protocol specification
Systèmes d'automatisation industrielle — Spécification de messagerie industrielle — Partie 2: Spécification de protocole
General Information
Relations
Frequently Asked Questions
ISO/IEC 9506-2:1990 is a standard published by the International Organization for Standardization (ISO). Its full title is "Industrial automation systems - Manufacturing Message Specification - Part 2: Protocol specification". This standard covers: Industrial automation systems - Manufacturing Message Specification - Part 2: Protocol specification
Industrial automation systems - Manufacturing Message Specification - Part 2: Protocol specification
ISO/IEC 9506-2:1990 is classified under the following ICS (International Classification for Standards) categories: 25.040.40 - Industrial process measurement and control. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO/IEC 9506-2:1990 has the following relationships with other standards: It is inter standard links to ISO/IEC 9506-2:1990/Amd 2:1995, ISO/IEC 9506-2:1990/Amd 1:1993, ISO/IEC 9506-2:1990/Cor 1:1995, ISO/IEC 9506-2:1990/Cor 2:1995, ISO 9506-2:2000; is excused to ISO/IEC 9506-2:1990/Amd 2:1995, ISO/IEC 9506-2:1990/Cor 1:1995, ISO/IEC 9506-2:1990/Cor 2:1995, ISO/IEC 9506-2:1990/Amd 1:1993. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
You can purchase ISO/IEC 9506-2:1990 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
Standards Content (Sample)
INTERNATIONAL
ISOIIEC
STANDARD
9506-2
First edition
1990-10-15
Industrial automation systems - Manufacturing
Message Specification -
Part 2:
Protocol specification
Systkmes d’automatisation industriele - Spkcifica tion de messagerie industrielle -
Partie 2: Sphcification de protocole
C
- E
- =
= =
= =
= Z
= =
5 =
Z =
E =
= =
Z =
-
=
=
- = Reference number
E C
.-===Z
E
IS0 9506-2 : 1990 (El
506-2 : 1990 (E)
Page
I Scope . P
.................................................. P
I.1 Specifications
.................................................... I
1.2 Procedures
..................................................
B
1.3 Applicability.
I
I.4 ~onforgnance .
................................................. I
2 Normative references
3 definitions .
..................................... 3
3‘1 Reference Mode% definitions.
...................................
3.2 Service Convention definitioins
..............................
Abstract Syntax Notation definitions 3
3.3
...............................................
other definitions 4
3.4
....................................................... 8
4 Abbreviations
5 9
CoIIvCXitiOIIS. .
............................................ 9
Service Conventions
BaseofNwnericValues .
...................................................... 9
Notation
......................................... 9
Supporting Productions
........................................ 9
Pass-through Parameters
NegativeConfirmation. .
.................................... B I
Modifiers to a Service Request
lil
PresentationofErrors.
.........................................
UseofCompanionStandardFields
................................
.................................... 11
Cahg and Called MMS-user
...................... P 1
Sending and Receiving MMS-user and MMPM
............................ 11
Requesting and Responding MMS-user
ClientandServerofaService .
.A$N.%Definitions 112
..............................................
0 Em/EC 1990
A11 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.
Switzerland
CH-1211 Cenkve 20
HSWIEC Copyright office Case postale 54
Printed in Switzerland
ISO/IEC 9506-2 : 1990 (E)
6 Elements of Protocol Procedure 12
........................................
6.1 Descriptive Conventions 12
...................... 12
6.2 Entering and Leaving the MMS Environment
.............................. 13
6.3 Operating in the MMS Environment
Handling of Error Conditions . 18
6.4
The Reject Service and RejectPDU . 18
6.5
......................................................... 18
7 MMSPDU
The Confirmed-RequestPDU . 19
7.1
TheUnconfirmed-PDU . 20
7.2
7.3 The Confirmed-ResponsePDU . 20
7.4 The Confirmed-ErrorPDU . 20
........................................ 21
7.5 Supporting Productions
CommonMMSTypes . 31
7.6
....................... 34
8 Environment And General Management Protocol.
Introduction . 34
8.1
Initiate . 34
8.2
8.3 Conclude .
8.4 Abort .
8.5 Cancel .
Reject . 38
8.6
9 VMD Support Protocol .
Introduction . 39
9.1
9.2 Status . 39
9.3 UnsolicitedStatus .
9.4 GetNameList .
Rename. . 42
9.6
9.7 GetCapabilityList . 43
Domain Management Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Introduction . 44
10.1
InitiateDownloadSequence. . 44
10.2
10.3 DownloadSegment. .
TerminateDownloadSequence . 45
10.4
InitiateUploadSequence . 46
10.5
UploadSegment . 46
10.6
10.7 TerminateUploadSequence .
RequestDomainDownload . 47
10.8
10.9 RequestDomainUpload . 48
10.10 LoadDomainContent .
StoreDomainContent . 49
10.11
DeleteDomain . 49
10.12
10.13 GetDomainAttributes . 50
. . .
ISOAEC 9506-2 : 1990 (E)
11 Program Invocation Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Introduction. 51
11.2 CreateProgramInvocation 5 1
......................................
11.3 DeleteProgramInvocation
......................................
11.4 Start .
11.5 Stop .
11.6 Resume. .
11.7 Reset .
11.8 Kill . 55
11.9 GetProgramInvocationAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 Variable Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1 Conventions . 56
12.2 Protocol For Specifying Types.
.................................. 57
12.3 Protocol For Specifying Alternate Access . 57
12.4 Protocol for Specifying Data Values . 59
12.5 Protocol for Specifying Access To Variables 62
.......................
12.6 Read . 63
12.7 Write . 63
12.8 InformationReport 64
............................................
12.9 GetVariableAccessAttributes
.................................... 64
12.10 DefineNamedVariable. 65
.........................................
12.11 DefineScatteredAccess 65
.........................................
12.12 GetScatteredAccessAttributes . 66
DeleteVariableAccess
12.13 66
..........................................
12.14 DefineNamedVariableList
...................................... 67
12.15 GetNamedVariableListAttributes
................................ 67
12.16 DeleteNamedVariableList. 68
......................................
12.17 DefineNamedType . 68
12.18 GetNamedTypeAttributes . 69
12.19 DeleteNamedType
............................................. 69
13 Semaphore Management Protocol 70
.....................................
13.1 Introduction . 70
13.2 TakeControl . 70
13.3 RelinquishControl 7 1
.............................................
13.4 DefineSemaphore . 71
DeleteSemaphore. 72
13.5 .
ReportSemaphoreStatus 72
13.6 .
ReportPoolSemaphoreStatus. 72
13.7 .
13.8 ReportSemaphoreEntryStatus
................................... 73
13.9 AttachToSemaphore Modifier. 74
..................................
13.10 Semaphore and Resource Management Supporting Productions . . . . . . 74
ISOAEC 9506-2 : 1990 (E)
14 Operator Communication Protocol .
14.1 Introduction. .
14.2 Input .
Output . 75
14.3
15 EventManagement Protocol .
15.1 Introduction. .
......................................... 76
15.2 DefineEventCondition
.......................................... 76
DeleteEventCondition
15.3
................................... 77
15.4 GetEventConditionAttributes
.................................... 78
15.5 ReportEventConditionStatus
.................................
15.6 AlterEventConditionMonitoring
TriggerEvent .
15.7
DefineEventAction .
15.8
............................................ 80
15.9 DeleteEventAction
...................................... 81
15.10 GetEventActionAttributes
15.11 ReportEventActionStatus. .
15.12 DefineEventEnrollment .
........................................ 83
15.13 DeleteEventEnrollment
................................. 83
15.14 GetEventEnrollmentAttributes
.................................. 85
15.15 ReportEventEnrollmentStatus
.........................................
15.16 AlterEventEnrollment
............................................ 86
15.17 EventNotification
................................ 88
15.18 AcknowledgeEventNotification.
...........................................
15.19 GetAlarmSummary
.................................
15.20 GetAlarmEnrollmentSummary
..................................... 91
15.21 AttachToEventCondition.
....................................... 91
15.22 Supporting Productions
.......................................
16 Journal Management Protocol
Introduction. .
16.1
ReadJournal .
16.2
16.3 WriteJournal .
..............................................
16.4 InitializeJournal
ReportJournalStatus .
16.5
CreateJournal .
16.6
16.7 DeleteJournal .
....................................... 96
16.8 Supporting Productions
........................... 97
Mapping to ACSE and Presentation Services
17.1 MappingofPDUs. .
................................. 97
17.2 Directly-Mapped Abort Service
...................................
Construction of MMS PDUs 98
17.3
V
ISOAEC 9506-2 : 1990 (E)
17.4 Delivery of Service Primitives to an MMS-user . 98
17.5 RighttoSendData .
17.6 Reliable Underlying Service .
17.7 98
Flow Control .
Use of Presentation Contexts 98
17.8 .
17.9 Negotiation of MMS Abstract Syntaxes . 99
17.10 Termination of Application Association .
Abstract Syntax Definition. 101
17.11 .
17.12 Application Context Name. . 101
18 Conformance . 102
18.1 Introduction . 102
18.2 PICS Part One : Implementation Information. . 102
18.3 PICS Part Two: Service CBBs . 103
18.4 PICS Part Three: Parameter CBBs .
PICS Part Four: Local Implementation Values. 107
18.5 .
19 MMS Abstract Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Annexes
A Requirements for Companion Standards (normative) . . . . . . . . . . . . . . . . . . . . 115
B File Access Protocol (normative) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C File Management Protocol (informative). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1
Index. 127
ISO/IEC 9506-2 : 1990 (E)
Foreword
IS0 (the International Organization for Standardization) is a worldwide federation of
national standards bodies (IS0 member bodies). The work of preparing International
Standards is normally carried out through IS0 technical committees. Each member
body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, govern-
mental and non-governmental, in liaison with ISO, also take part in the work. IS0
collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
Draft International Standards adopted by the technical committees are circulated to
the member bodies for voting. Publication as an International Standard requires
approval by at least 75 % of the member bodies casting a vote.
International Standard ISO/IEC 9506-2 was prepared by Technical Committee ISO/IEC
TC 184, Industrial automation systems, Sub-Committee SC 5, System integration and
communication.
ISO/IEC 9506 consists of the following parts, under the general title lndustrialautoma-
tion systems - Manufacturing Message Specification :
-
Part 7: Service definition
- Part 2: Protocol specification.
vii
ISO/IEC 9506-2 : 1990 (E)
Introduction
This part of ISO/IEC 9506 provides a wide variety of services useful for various
manufacturing and process control devices. It is designed to be used both by itself and
in conjunction with Companion Standards, which describe the application of subsets
of these services to particular device types.
The services provided by the Manufacturing Message Specification (MMS) range from
simple to highly complex. It is not expected that all of these services will be supported
by all devices. The subset to be supported is limited in some cases by Companion Stan-
dards, and in all cases may be limited by the implementor. Characteristics important in
selection of a subset of services to be supported include:
applicability of the service to the device;
a)
b) the complexity of services and requirements;
c) the complexity of pro vision of a particular class of service via the network ver-
sus the complexity of the device.
Security considerations
When implementing MMS in secure or safety critical applications, features of the OS1
security architecture may need to be implemented. Appropriate features should be
selected from IS0 7498-2 covering safety architectures and features. Those of par-
ticular interest cover the position (in OSI) of
a) access control;
b) authentication;
c) non-repudiation.
Specific implementation methods shall be at the discretion of the implementor.
Complexity of services and requirements
Some MMS services are quite complex and should be considered as advanced func-
tions. Devices used in very simple applications often will not require such advanced
functions, and hence will not support such MMS services.
Keywords
Application Interworking
Application Layer Protocol
Information Processing Systems
Manufacturing Communications Network
Manufacturing Message Specification
Numerical Control System
Open Systems Interconnection
OS1 Reference Model
Process Control System
Programmable Controller
Programmable Device
Robotics Control System
Virtual Manufacturing Device
. . .
Vlll
ISO/IEC 9506-2 : 1990 (E)
General
This part of ISO/IEC 9506 is one of a set of International Standards produced to
facilitate the interconnection of information processing systems. It is positioned within
the application layer of the Open Systems Interconnection Environment as an Applica-
tion Service Element (ASE) with respect to other related standards by the Basic
Reference Model for Open Systems Interconnection (IS0 7498).
The aim of Open Systems Interconnection is to allow, with a minimum of technical
agreement outside the interconnection standards, the interconnection of information
processing systems :
from different manufacturers;
a)
b) under different managements;
c) of different levels of complexity;
of different ages.
d)
Purpose
The purpose of this part of ISO/IEC 9506 is to define the Manufacturing Message
Specification Protocol. It is most closely related to and lies within the field of applica-
tion of the Manufacturing Message Specification Service Definition, ISO/IEC 9506-l.
It also uses and references the Association Control Service Element Definition
(IS0 8649) and the Presentation Layer Service Definition (IS0 8822), whose provisions
it assumes in order to accomplish the aims of the Manufacturing Message Specification
Protocol. The inter-relationship of these International Standards is depicted in
Figure 1.
Manufacturing Message Specification Service Definition
I
Manufacturing Message Reference to aims
Specification
Protocol Reference to assumptions
Application Control Service Element Definition
and
Presentation Layer Service Definition
Specification
Figure l- Relatio nship between the Manufacturing
Protocol and adjacent services
The MMS protocol is structured so that subsets of protocol can be defined. The varia-
tions and options available within this part of ISO/IEC 9506 are essential to enable a
Manufacturing Message Specification to be provided for a wide variety of applications.
Thus, a minimally conforming implementation will not be suitable for use in all possi-
ble circumstances. It is important, therefore, to qualify all references to this part of
ISOAEC 9506 with statements of the options provided or required with statements of
the intended purpose of provision or use.
NOTE - The services of this part of ISO/IEC 9506 are generic, and intended to be referenced by
Companion Standards, each of which is directed to a more specific class of application. The ser-
vices of this part of ISO/IEC 9506 may also be used in a stand-alone manner (without the use of
Companion Standards).
It should be noted that, as the number of valid protocol sequences is very large, it is not
possible with current technology to verify that an implementation will operate the pro-
tocol defined in this part of ISO/IEC 9506 correctly under all circumstances. It is possi-
ble by means of testing to establish confidence that an implementation correctly
operates the protocol in a representative sample of circumstances. It is, however, in-
tended that this part of ISO/IEC 9506 can be used in circumstances where two
implementations fail to communicate in order to determine whether one or both have
failed to operate the protocol correctly.
ix
ISO/IEC 9506-2 : 1990 (E)
Intended users
The primary aims of this part of ISO/IEC 9506 is to provide a set of rules for com-
munication expressed in terms of the procedures to be carried out by peer MMS entities
at the time of communication. These rules for communication are intended to provide
a sound basis for development in order to serve a variety of purposes:
a) as a guide for implementors and designers;
b) for use in the testing and procurement of equipment;
c) as part of an agreement for the admittance of systems into the open systems en-
vironment ;
d) as a refinement to the understanding of OSI.
This part of ISOAEC 9506 is concerned, in particular, with the communication and in-
terworking of programmable devices on the plant floor. By using this part of
ISOAEC 9506 together with other standards positioned within the OS1 Reference
Model, otherwise incompatible systems may work together in any combination.
ISOAEC 9506-2 : 1990(E)
Industrial automation systems -
Manufacturing Message Specification -
Part 2: Protocol specification
1 Scope
The Manufacturing Message Specification is an application layer standard designed to support messaging communications
to and from programmable devices in a Computer Integrated Manufacturing (CIM) environment.
I .I Specifications
This part of ISOLIEC 9506 specifies:
procedures for a single protocol for the transfer of data and control information fiorn one application entity to a peer
application entity in the MMS-context;
the means of selecting the services to be used by the application entities while communicating in the MMS-context;
b)
the structure of the Manufacturing Messaging Specification Protocol Data Units used for the transfer of data and
control information.
1.2 Procedures
The procedures are defined in terms of
the interactions between peer application entities through the exchange of Manufacturing Message Specification
Application Protocol Data Units;
the interactions between an MMS-provider and the MMS-user in the same system through the exchange of MMS
primitives;
the interactions between an MMS-provider and the Association Control Service Element through the exchange of
C>
association control service primitives;
,the interactions between an MMS-provider and a presentation service provider through the exchange of Presentation
service primitives.
13 . Applicability
These procedures are applicable to instances of communication between systems which support MMS within the application
layer of the OS1 Reference Model, and which require the ability to interconnect in an open systems interconnection
environment.
1.4 Conformance
This part of ISO/lEC 9506 also specifies conformance requirements for systems implementing these procedures. This part
of ISOAEC 9506 does not contain tests to demonstrate compliance with such requirements.
2 Normative References
ISOAEC 9506-2: 1990(E)
The following standards contain provisions which, through reference in this text, constitute provisions of this part of
ISO/IEC 9506. At the time of publication, the editions indicated were valid. All standards are subject to revision, and
parties to agreements based on this part of ISO/IEC 9506 are encouraged to investigate the possibility of applying the
most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid
International Standards.
IS0 646: 1983, Information processing - IS0 7-bit coded character set for information interchange.
IS0 7498 : 1984, Information processing systems - Open Systems Interconnection - Basic Reference Model.
. IS0 7498-2 : 1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 2: Security
Architecture.
IS0 7498-3 : 1989, Jnforma tion processing systems - Open Systems Interconnection -- Basic Reference Model - Part 3: Naming
and addressing.
Open Systems Interconnection - Basic connection oriented session service
IS0 8326: 1987, Information processing systems -
definition.
ISOITR 8509: 1987, Information processing systems - Open Systems Interconnection - Service conventions.
File Transfer, Access and Management.
IS0 8571 : 1988, Information processing systems - Open Systems Interconnection -
IS0 86&: 1988, Information processing systems - Open Systems Interconnection - Service definition for the Association Control
Service Element.
Open Systems Interconnection - Protocol specification for the Association Con-
IS0 8656 : 1988, Jnforma tion processing systems -
trol Service Element.
Jnforma tion processing s ys terns - Open S ys terns Interconnection - Connection oriented presentation service
IS0 8822: 1988,
definition.
Open S ys terns Interconnection - Specification of Abs trac t Syntax Notation One
I SO 8824 : 1987, Jnforma tion processing systems -
(ASN. 7).
IS0 8824 /Add 1: - 11, Jnforma tion processing systems - Open Systems Interconnection - Specification of Abstract Syntax No ta-
tion One (ASN. 7) Addendum 1: A SN. I Extensions.
Open Systems Interconnection - Specification of Basic Encoding Rules for
IS0 8825 : 1987, Information processing systems -
Abstract Syntax Notation One (ASN. Il.
IS0 8825/Add 1: - 11, Jnforma tion processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules
for Abstract Syntax Notation One (ASN. 7) Addendum 7: ASN. 7 Extensions.
Virtual terminal service - Basic class.
ISO9040:- 11, Information processing systems - Open Systems Interconnection -
Open Systems Interconnection - Virtual terminal protocol - Basic class.
IS0 9041: - 11, Jnforma tion processing systems -
ISO/IEC 9566-l : 1990, Industrial automation systems - Manufacturing Message Specification - Part 7: Service definition.
ISO/IEC 9545-l : 1989, Information technology - Open Systems Interconnection - Application Layer Structure.
ISO/IEC 9594: - 11, Information processing systems - Open Systems Interconnection - The Directory.
IEEE 754 : 1985, IEEE Standard for Binary Flea ting-Poin t Arithmetic.
3 Definitions
NOTE - The definitions contained in this clause make use of abbreviations defined in clause 4.
For the purposes of this part of ISO/IEC 9506, the following definitions apply.
1) To be published.
ISOAEC 9506-2: 1990(E)
3.1 Reference Model definitions
This part of ISO/IEC 9506 is based on the concepts developed in the Basic Reference Model for Open Systems Intercon-
nection (IS0 7498), and makes use of the following terms defined in that International Standard:
application-entity;
application-process;
b)
application service element;
open system;
(N)-protocol;
e)
(N)-protocol-data-unit;
f )
(N)-service-access-point;
9)
(N)-layer
f
h) .
system;
.
(N)-user-data.
I)
32 . Service Convention definitions
This part of ISO/IEC 9506 makes use of the following terms defined in the OS1 Service Conventions (IS0 TR $509) as
they apply to the Manufacturing Message Specification:
confirm;
a)
indication;
W
primitive;
C>
request;
d)
response;
service primitive;
f >
service provider;
service user.
3.3 Abstract Syntax Notation definitions
This part of ISO/IEC 9506 makes use of the following terms defined in the Abstract Syntax Notation One (ASN.lj Speci-
fication (IS0 8824):
value;
1)
2) type;
simple type;
3)
structure type;
4)
component type;
5)
6) WG
7) tagging,
8) type (or value) reference name;
lSO/IEC 9506-2: 1990(E)
character string type;
9)
10) boolean type;
11) true;
12) false;
13) integer type;
14) bitstring type;
15) octetstring type;
16) null type;
17) sequence type;
18) sequence-of type;
19) wzged type;
20) choice type;
21) selection type;
22) real type;
23) object identifier type;
24) MACRO;
25) module;
26) production;
27) ASN.1 encoding rules;
28) ASN.l character set;
29) external type.
3.4 Other definitions
For the purpose of this part of XSOflEC 9506, the following definitions also apply:
3.4.1 AA-specific (Application Association specific):
An adjective used to describe an object whose name has a scope that is a single application association (i.e. the name may
be referenced only on the application association over which the object was defined).
3.4.2 attribute:
A data element, having a defined meaning, together with a statement of the set of possible values it may take.
3.4.3 Called MMS-user:
The MMS-user that issues the Initiakresponse service primitive.
ISOAEC 9506-2: 1990(E)
3.4.4 Calling MMS-user:
The MMS-user that issues the Initiate.request service primitive.
3.4.5 Client:
The peer communicating entity which makes use of a VMD for some particular purpose via a service request instance.
3.4.6 conformance building block (CBB):
An atomic unit used to describe MMS conformance requirements.
3.4.7 data:
Any representation to which meaning is or might be assigned (e.g. characters).
3.4.8 domain:
An abstract object that represents a subset of the capabilities of a VMD which is used for a specific purpose.
3.4.9 Domain-specific:
An adjective used to describe an object whose name has a scope that is a single domain (i.e. the name can be referenced
over all application associations established with the VMD that may reference this domain).
download:
3.4.10
MMS-user.
The process of transferring the content of a domain, including any subordinate objects, via load data to an
3.4.11 event management:
event actions, and event enrollments.
The management of event conditions,
3.4.12 file:
An unambiguously named collection of information having a common set of attributes.
3.4.13 file operation:
The transfer of files between open systems, the inspection, modification, or replacement of part of a file’s content, or the
management of a file and its attributes.
3.4.14 fiIestore:
names, residing at a particular open system.
An organized collection of files, including their attributes and
3.4.15 information:
The combination of data and the meaning that it conveys.
ISOAEC 9506-2: 1990(E)
3.4.16 invaiid PDU:
not comply with the requirements of this part of ISO/IEC 9506 with respect to structure, semantic
A PDU which d oes
meaning, or both.
3.4.17 journal:
A set of recorded, time-tagged event transitions, variable data, and/or comments, which may be logically ordered during
retrieval.
3.4.18 local matter:
A decision made by a system concerning its behaviour in the Manufacturing Message Specification that is not subject to
the requirements of this part of ISO/IEC 9506.
3.4.19 Manufacturing Message Protocol Machine (MMPM):
An abstract machine that carries out the procedures specified in this part of this part of ISO/IEC 9506.
3.4.20 MMS-context:
A spetication of the service elements of MMS and semantics of communication to be used during the lifetime of an
application association.
3.4.21 MMS-provider:
That part of the application entity that conceptually provides the MMS service through the exchange of MMS PDUs.
3.4.22 MMS-user:
That portion of the application process which conceptually invokes the Manufacturing Message Specification.
3.4.23 monitored event:
A detected change in the state of an event condition.
3.4.24 network-triggered event:
A trigger which occurs due to an explicit solicitation client.
bY a
3.4.25 operator station:
An abstract object representing equipment associated with a VMD that provides for input/output interaction with an
operator.
3.4.26 predefined object:
An object, whose name is of VMD-specific or Domain-specific scope, that is instantiated through the use of some mechanism
other than an MMS service.
ISOAEC 9506-2: 1990(E)
3.4.27 program invocation:
An abstract object representing a dynamic element which most closely corresponds to an execution thread in a multi-
tasking environment, which is composed of a set of domains.
3.4.28 protocol error:
A PDU that does not comply with the requirements of this part of ISO/IEC 9506.
3.4.29 Receiving MMPM:
The MMPM that receives an MMS PDU.
3.4.30 Receiving MMS-user:
The MMS-user that receives an indication or confirmation service primitive.
3.4.31 remote device control and monitoring:
The manipulation or inspection of the state of a device attached to the responder of a service request.
Requesting MMS-user:
3.4.32
The MMS-user that issues the request service primitive for a service.
3.4.33 Responding MMS-user:
The MMS-user that issues the response service primitive for a service.
3.4.34 semaphore:
A conceptual lock associated with a logical or physical resource that permits access to that resource only by an owner of
the lock.
3.4.35 semaphore management:
The control of semaphores.
3.4.36 Sending MMPM:
The MMPM that sends an MMS PDU.
3.4.37 Sending MMS-user:
The MMS-user that issues a request or response service primitive.
3.4.38 Server:
The peer communicating entity which behaves as a VMD for a particular service request instance.
ISO/IEC 9506-2: 1990(E)
3.4.39 standardized object:
An object instantiation, whose name is of VMD-specific or Domain-specific scope, whose definition is provided in this part
of ISO/IEC 9506 or an MMS Companion Standard.
3.4.40 type:
An abstract description of the class of data which may be conveyed by the value of a variable.
3.4.41 upload:
The process of transferring the content of a domain, including any subordinate objects, via load data from a remote user,
in such a manner as to allow subsequent download.
3.4.42 valid PDU:
A PDU which complies with the requirements of this part of ISO/IEC 9506 with respect to structure and semantic meaning.
3.4.43 variable:
One or more data elements that are referred to together by a single name or description.
3.4.44 variable access:
or components of variables defined at a PrMD.
The inspection or modification of variables
3.4.45 Virtual Manufacturing Device (VMD):
An abstract representation of a specific set of resources and functionality at a real manufacturing device and a mapping
of this abstract representation to the physical and functional aspects of the real manufacturing device.
3.4.46 VMD-specif ic:
An adjective used to describe an object whose name has a scope that is a single VMD (i.e. the name may be referenced by
all application associations established with the VMD).
Abbreviations
AA : application association
ACSE : Association Control Service Element
AE : application entity
AP : application process
APDU : application protocol data unit
ASE : application service eiement
ASN.1 : Abstract Syntax Notation One
CBB : conformance building block
FRSM : file read state machine
ISOAEC 9506-2: 1990(E)
RAM : File Transfer, Access and Management
MMPM : Manufacturing Message Protocol Machine
MMS : Manufacturing Message Specification
NC : Numerical Control
: operator communication services
ucs
OSI : Open Systems Interconnection
: Programmable Controller
PC
: protocol data unit
PDU
PSAP : presentation service access point
SAP : service access point
SDU : service data unit
ULSM : upload state machine
VMD : Virtual Manufacturing Device
VT : Virtual Terminal
5 Conventions
5.1 Service Conventions
This part of IS0 9506 uses the descriptive conventions contained in the OS1 Service Conventions (IS0 TR 8509). The model
defines the interactions between the MMS-user and the MMS-provider. Information is passed between an MMS-user and
an MMS-provider by service primitives, which may convey parameters.
5.2 Base of Numeric Values
This part of ISOflEC 9506 uses a decimal representation for all numeric values unless otherwise noted.
5.3 Notation
This part of ISO/IEC 9506 uses the abstract syntax notation defined in IS0 8824 (ASN.1 Specification). In keeping with
the intent and requirements of the ASN.1 Standard, all type reference symbols begin with an upper case letter. All value
references begin with a lower case letter.
5.4 Supporting Productions
Supporting productions introduced in the various clauses of this part of ISO/IEC 9506 are described where they are
When supporting productions are referenced multiple times from
referenced if they are used primarily in one place.
different places, they are collected at the end of the most relevant clause. In any case, an index of productions with page
numbers may be found at the end of this part of ISO/IEC 9506.
5.5 Pass-through Parameters
Many of the parameters of the various MMS services are passed from the request primitive via the service’s request PDU
to the indication primitive or from the response primitive via the service’s response PDU to the confirm primitive, without
other action being taken by the MMS-provider relative to the parameter.
ISOAEC 9506-2: 1990(E)
5.5.1 Pass-through Request Parameters
The type identified by the type reference name shall be the parameter of the same name (see 5.5) f!kom the service’s request
primitive, and shall appear as the parameter of the same name in the service’s indication primitive, if issued. The value
of the parameter in the request primitive, indication primitive, and the request PDU are semantically equivalent.
If the parameter is optional and it is omitted from the request service primitive, it shall be absent in the request PDU. If
an optional parameter is absent in the request PDU, it shall be absent in the indication service primitive.
If a parameter has a default in the request PDU and this default value is provided in the request service primitive, then the
parameter may be absent in the request PDU. If a parameter has a default value in the request PDU and this parameter
is absent in the request PDU, then the parameter shall specify the default value in the indication service primitive.
55.2 Pass-through Response Parameters
The type identified by the type reference name shall be the parameter of the same name (see 5.5) from the service’s
response primitive, and shall appear as the parameter of the same name in the service’s confirm primitive, if issued.
The value of the parameter in the response primitive, confirm primitive, and the response PDU shall be semantically
equivalent.
If the parameter is optional and it is omitted from the response service primitive, it shall be absent in the response PDU.
If an optional parameter is absent in the response PDU, it shall be absent in the confirm service primitive.
If a parameter has a default in the response PDU and this default value is provided in the response service primitive,
then the parameter may be absent in the response PDU. If a parameter has a default value in the response PDU and
this parameter is absent in the response PDU, then the parameter shall specify the default value in the confirm service
primitive.
5.5.3 Enumerated Values in Parameters
For those parameters in the service description that have enumerated values, the value specified for the corresponding
protocol parameter shall be the value of the same name (see 5.5) from the service primitive containing the parameter. The
values conveyed in the service primitive, resulting PDU, and the service primitive that results from receipt of the service
primitive shall be semantically equivalent.
NOTE - The correspondence between such values is identified in this part of ISO/IEC 9506 through the use of the same names
in the service primitives and protocol. In the service specification, such values are specified in all upper case characters. In the protocol
specification, the case of the name is chosen so as to satisfy ASN.1 syntax requirements, with the name in upper case characters following
the usage in the protocol in a comment.
5.6 Negative Confirmation
Most confirmed MMS services provide for negative confirmation in the case that an error occurs in the processing of the
service request by the responding MMS-user. Such negative confirmation shall be indicated by a Result(-) parameter and
an “Error’Qpe” parameter in the service’s response primitive. A Result(-) parameter and an “ErrorType” parameter that
is semantically equivalent to those parameters in the response primitive shall appear in the confirm service primitive.
The abstract syntax for a negative confirmation shall be the ErrorPDU of the service, with the “error” field derived from
the “Problem” parameter in the response service primitive.
ISOAEC 9506-2: 1990(E)
5.7 Modifiers to a Service Request
MMS services allow modifiers to be used with instances of service requests.
In instances of requests of services which make use of modifiers, the modifiers specified in a RequestPDU shall be seman-
tically equivalent to, and in the same order as, those modifiers specified in the request service primitive. The indication
primitive shall contain a list of modifiers that is semantically equivalent to, and in the same order as, the modifiers in the
RequestPDU.
5.8 Presentation of Errors
For each service presented in the body of this part of ISOLIEC 9506, the errors that may result from. the use of that service
are not presented with the protocol for the service. Errors are specified in a separate clause.
5.9 Use of Companion Standard Fields
In a number of places in the MMS protocol, a parameter is specified as for use by Companion Standards. This allows the
definition of the content of this field to be specified via some means outside the scope of this part of ISO/IEC 9506. Use of
such fields is specified in clause 19.
5.10 Calling and Called MMS-user
This part of ISO/IEC 9506 makes use of the terms Calling and Called MMS-user. The Calling MMS-user is the MMS-user
that, issues the Initiate.request service primitive. The Called MMS-user is the MMS-user that issues the Initiate.response
service primitive.
NOTE - The use of the term “called” in MMS is not the same as the general usage of the term in OSI. The MMS usage of the
term “called” corresponds to the OS1 usage of the term “responding”. This distinction has been introduced in order to avoid confusion
with the Requesting/Responding MMS-user definition given below.
5.11 Sending and Receiving MMS-user and MMPM
This part of ISOAEC 9506 makes use of the terms Sending and Receiving MMS-user. The Sending MMS-user is the
MMS-user that issues a request or response service primitive. The Receiving MMS-user is the MMS-user that receives
an indication or confirmation service primitive.
NOTE - It is important to note that, in the course of completion of a confirmed MMS service, both MMS-users will be senders
and receivers at one time. The fkt-st MINIS-user sends the request and receives the confkmation, while the second MMS-user receives the
indication and sends the response.
This part of ISO/IEC 9506 makes use of the terms Sending and Receiving MMPM. The Sending MMPM is the MMPM
that sends an MMS PDU. The Receiving MMPM is the MMPM that receives an MMS PDU.
5.12 Requesting and Responding MMS-user
This part of ISO/IEC 9506 makes use of the terms Requesting and Responding MMS-user. The Requesting MMS-user is
the MMS-user that issues the request service primitive for a service, while the Responding MMS-user is the MM&user
that issues the response service primitive for a service.
-
Responding MMS-user differs from the use the term Responding
NOTE It is important to note that the use of the term of
is used to reference the entity that responds
entity in ACSE and other standards . In those standards, the term to a connection request.
ISOAEC 9506-2: 1990(E)
5.13 Client and Server of a Service
This part
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...