IEC 62264-6:2020

IEC 62264-6 ®
Edition 1.0 2020-06
INTERNATIONAL
STANDARD
colour
inside
Enterprise-control system integration –
Part 6: Messaging service model
All rights reserved. Unless otherwise specified, 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
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and Definitions clause of
IEC publications issued since 2002. Some entries have been
IEC Customer Service Centre - webstore.iec.ch/csc collected from earlier publications of IEC TC 37, 77, 86 and
If you wish to give us your feedback on this publication or CISPR.

need further assistance, please contact the Customer Service

Centre: sales@iec.ch.
IEC 62264-6 ®
Edition 1.0 2020-06
INTERNATIONAL
STANDARD
colour
inside
Enterprise-control system integration –

Part 6: Messaging service model

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 25.040.40; 35.100.70 ISBN 978-2-8322-8453-7

– 2 – IEC 62264-6:2020 © IEC 2020
CONTENTS
FOREWORD . 6
INTRODUCTION . 8
1 Scope . 11
2 Normative references . 11
3 Terms, definitions, abbreviation, and conventions . 11
3.1 Terms and definitions . 11
3.2 Abbreviations . 12
3.3 Conventions . 13
4 Overview of the MSM . 13
4.1 Positioning of the MSM . 13
4.2 Abstract service model . 14
4.3 Transaction models supported . 14
4.4 Application roles . 15
4.5 MSM channels . 15
4.6 MSM channel services . 16
4.6.1 Types of channel services . 16
4.6.2 Channel management services . 16
4.6.3 Publication channel services . 16
4.6.4 Request channel services . 17
4.7 Notify listener service . 17
5 Methods of operation of channels . 18
5.1 Channel and topic identification . 18
5.2 Channel names and hierarchy . 18
5.2.1 Channel names. 18
5.2.2 Channel name hierarchy . 18
5.2.3 MSM root . 18
5.2.4 Channel scope . 19
5.2.5 Information scope . 19
5.2.6 Channel use . 19
5.3 Publication expiration . 20
5.4 Topics . 21
5.4.1 Topic definition . 21
5.4.2 Topic names . 21
5.5 Sessions . 22
5.6 Security . 22
5.6.1 Secure message exchanges . 22
5.6.2 Security tokens on channels . 22
5.6.3 Security token format . 23
5.6.4 MSM service provider implementations . 23
6 Service definitions . 23
6.1 Type definitions . 23
6.2 Defined return value of services . 24
6.3 Channel management services . 25
6.3.1 Create channel . 25
6.3.2 Add security tokens . 25
6.3.3 Remove security tokens . 26

6.3.4 Delete channel . 26
6.3.5 Get channel . 26
6.3.6 Get channels . 27
6.4 Notify listener service . 27
6.5 Provider publication services . 28
6.5.1 Open publication session . 28
6.5.2 Post publication . 28
6.5.3 Expire publication . 28
6.5.4 Close publication session . 29
6.6 Consumer publication services. 29
6.6.1 Open subscription session . 29
6.6.2 Read publication . 30
6.6.3 Remove publication . 30
6.6.4 Close subscription session . 31
6.7 Provider request services. 31
6.7.1 Open provider request session . 31
6.7.2 Read request . 32
6.7.3 Remove request . 32
6.7.4 Post response . 33
6.7.5 Close provider request session . 33
6.8 Consumer request services . 33
6.8.1 Open consumer request session . 33
6.8.2 Post request . 34
6.8.3 Read response . 34
6.8.4 Remove response . 35
6.8.5 Close consumer request session . 35
7 Scenarios . 36
7.1 Publish-subscribe scenarios. 36
7.1.1 Simple publish-subscribe scenario . 36
7.1.2 Publish-subscribe scenario with multiple messages . 36
7.1.3 Publish-subscribe scenario without notification . 37
7.1.4 Multiple publisher scenario . 38
7.1.5 Publish-subscribe scenario with publication expiration . 39
7.2 Request channel scenarios . 40
7.2.1 Request-response scenario with notification . 40
7.2.2 Request-response scenario without notification . 41
7.2.3 Multiple providers . 42
8 Conformance . 43
Annex A (informative)  MSM service provider considerations . 44
A.1 Service provider considerations . 44
A.2 Notification. 44
A.3 Security considerations . 44
A.4 MSM application implementation considerations . 44
A.5 MSM channel security considerations . 45
A.6 MSM session ID considerations . 45
A.7 Data format validation . 45
A.8 Allowed application checking . 45
A.9 Data exchange logging . 45
A.10 Common error handling . 45

– 4 – IEC 62264-6:2020 © IEC 2020
A.11 Data transformation services. 46
A.12 Cross company bridges . 46
A.13 Message maintenance . 47
Annex B (informative)  Enterprise Service Buses . 48
Bibliography . 50

Figure 1 – Steps in application-to-application communication . 9
Figure 2 – Defined standards at each level . 9
Figure 3 – Positioning and ole of MSM . 14
Figure 4 – Messaging service model terminology . 15
Figure 5 – Channel management services . 16
Figure 6 – Publication channel services . 17
Figure 7 – Services for request . 17
Figure 8 – Notify listener service . 18
Figure 9 – Changes and checkpoint channel example . 20
Figure 10 – Security of channels . 23
Figure 11 – Publication scenario with notification . 36
Figure 12 – Publication scenario with multiple messages . 37
Figure 13 – Publication without notification . 38
Figure 14 – Publication with multiple provider applications . 39
Figure 15 – Publication with expired publications . 40
Figure 16 – GET/SHOW request service scenario . 41
Figure 17 – CHANGE / RESPONSE request service scenario . 42
Figure 18 – Multiple providers CHANGE/RESPONSE scenario . 43
Figure A.1 – Transformation services with the MSM service provider . 46
Figure A.2 – Cross company bridge between multiple MSMs . 47
Figure B.1 – Standard interface to ESBs and other message exchange systems . 49

Table 1 – Application roles, channels, and services . 16
Table 2 – Channel use for transaction verbs . 19
Table 3 – Type definitions . 24
Table 4 – Service fault definitions . 24
Table 5 – Service parameter definitions . 25
Table 6 – Create channel . 25
Table 7 – Add security tokens . 25
Table 8 – Remove security tokens . 26
Table 9 – Delete channel . 26
Table 10 – Get channel . 27
Table 11 – Get channels . 27
Table 12 – Notify listener . 27
Table 13 – Open publication session . 28
Table 14 – Post publication . 28
Table 15 – Expire publication . 29

Table 16 – Close publication session . 29
Table 17 – Open subscription session . 30
Table 18 – Read publication . 30
Table 19 – Remove publication . 31
Table 20 – Close subscription session . 31
Table 21 – Open provider request session . 32
Table 22 – Read request . 32
Table 23 – Remove request . 33
Table 24 – Post response . 33
Table 25 – Close provider request session. 33
Table 26 – Open consumer request session. 34
Table 27 – Post request . 34
Table 28 – Read response . 35
Table 29 – Remove response . 35
Table 30 – Close consumer request session . 35

– 6 – IEC 62264-6:2020 © IEC 2020
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
ENTERPRISE-CONTROL SYSTEM INTEGRATION –

Part 6: Messaging service model

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent
rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62264-6 has been prepared by subcommittee 65E: Devices and
integration in enterprise systems, of IEC technical committee TC65: Industrial-process
measurement, control and automation.
The text of this International Standard is based on the following documents:
FDIS Report on voting
65E/706/FDIS 65E/724/RVD
Full information on the voting for the approval of this International Standard can be found in the
report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts in the IEC 62264, published under the general title Enterprise-control system
integration, can be found on the IEC website.

The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.

– 8 – IEC 62264-6:2020 © IEC 2020
INTRODUCTION
This document is based on the use of IEC 62264 object models defined in IEC 62264-2,
IEC 62264-4 and IEC 62264-5 to define a set of services that may be used to exchange
messages. This document defines a messaging service model (MSM) for exchanging messages
in a publish-subscribe mode and a request-response mode.
The Messaging Service Model provides a method for applications to send and receive
messages from MSM service providers without regard to the underlying communication
mechanism, as part of a complete application-to-application data exchange.
This document defines a model for message exchange services (Messaging Service Model)
that are designed to provide a technology independent method for sending and receiving
transaction messages to or from underlying exchange services.
The knowledge requirements to interface to just one message exchange system can be
immense and are usually not transferable to a different system. MSM defines a single interface,
independent of the underlying exchange services, for exchanging data objects defined by
IEC 62264-2 and by IEC 62264-4. This removes the need for vendors to build custom interface
after custom interface, and for end users to get locked into a single vendor because their
investment prevents them from reusing any of the integration efforts.
Exchanging the data objects between different computer system applications involves multiple
different steps, as shown in Figure 1.
a) The applications usually have different internal representations of exchanged objects in
their own local data stores. This representation is usually converted from the local format
to a commonly accepted global format. IEC 62264-2 defines models of a global format for
Level 4-3 data exchanges. IEC 62264-4 defines models of a global format for Level 3-3 data
exchanges. This conversion, from local to global and global to local, is usually performed
twice for any two-way communications.
EXAMPLE 1 Assume two applications, ALPHA and BETA: the ALPHA application initiates a data exchange with
the BETA application, and BETA responds back to ALPHA. The format conversions are: ALPHA’s local format
to global format for the request data, global format to BETA’s local format for the request data, BETA’s local
format to global format for the response data, and global format to ALPHA’s format for the response data.
b) Conversion is performed to align the namespaces among the exchanging applications and
is usually performed four times for any two-way communications.
EXAMPLE 2 Names for elements of data can be codes, tag names, or equipment identifiers.
EXAMPLE 3 Data which are represented in one element namespace, such as codes 1,2,3,4, can have a
different namespace in another application, such as codes Ok, Done, Error, Delay.
c) Once information is in the global format with global names, the exchanged information is
sent from one application to another application.
d) Messages are transported from one application to another, either within the same computer
environment or across computers. Transport mechanisms are defined in other standards,
such as TCP/IP and Ethernet standards.
e) When data exchange information is received, there are specific rules that define what
resultant data are to be returned. The transaction rules are defined in IEC 62264-5.

Figure 1 – Steps in application-to-application communication
MSM is a minimal interface subset that can reside on most exchange services and is based on
well-defined and structured data objects and transaction messages.
Each layer shown in Figure 2 addresses a specific element of application data exchange.
1) A Data Object layer defines the meaning, format, and structure of the basic elements of
exchanged information.
NOTE 1 This layer uses application space specific definitions, such as the IEC 62264-2 and IEC 62264-4 object
definitions, MESA B2MML, MIMOSA CCOM objects, and "Nouns" defined in OAGIS.
2) A Transaction layer defines the meaning, format, and structure of actions to be taken on the
data objects.
NOTE 2 This layer can use IEC 62264-5 transaction style specific definitions. Another transaction layer
definition could be the OAGIS "Verb" definitions.
3) The MSM defines an interface to the OSI Application layer’s services.
4) The application, presentation, session and lower level layers define the meaning, format,
and structure for coordination, buffering, and exchange of messages or files. These layers
contain transfer or exchange style specific definitions, such as Enterprise Service Buses,
Enterprise Message Delivery Systems, the OPC UA specification (IEC 62541 standard),
RSS, FTP, Named Pipes, Ethernet, TCP/IP, HTTP, and others.

Figure 2 – Defined standards at each level

– 10 – IEC 62264-6:2020 © IEC 2020
The IEC 62264-5 standard defines transactions on the information. The Messaging Service
Model (MSM) defines an interface to methods for exchange. In a sense, MSM defines the
standard "on-ramp" and "off-ramp" to the application layer services. It defines how data is
placed into exchange methods and how it is retrieved from the exchange methods.
NOTE 1 Message synchronization using the MSM service is distinct from the message synchronization provided by
the 62264-5 transaction models as well as distinct from the synchronization mechanisms provided at lower levels of
the communications stack.
NOTE 2 In this document, asynchronous message exchanges between consumers and producers can be
considered to be pairs of distinct, unidirectional messages.
This document includes two informative annexes. Annex A is informative. It provides
considerations for (MSM) service providers. Annex B is informative. It provides a brief
description of Enterprise Service Buses as a message exchange mechanism.

ENTERPRISE-CONTROL SYSTEM INTEGRATION –

Part 6: Messaging service model

1 Scope
This document defines a technology independent model for a set of abstract services that is
located above the application layer of the OSI model, and that is used for exchanging
transaction messages based on the transaction models defined in IEC 62264-5. The model,
which is called the Messaging Service Model (MSM), is intended for interoperability between
manufacturing operations domain applications and applications in other domains.
NOTE It is recognized that other sets of services not defined in accordance with this document are possible for the
exchange of MOM information and are not deemed invalid as a result of this document.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62264-1, Enterprise-control system integration – Part 1: Models and terminology
IEC 62264-2, Enterprise-control system integration – Part 2: Object and attributes for
enterprise-control system integration
IEC 62264-4, Enterprise-control system integration – Part 4: Objects models attributes for
manufacturing operations management integration
IEC 62264-5, Enterprise-control system integration – Part 5: Business to manufacturing
transactions
3 Terms, definitions, abbreviation, and conventions
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1.1
channel description
text that describes a channel
3.1.2
channel type
primary use of a channel for publications or for requests

– 12 – IEC 62264-6:2020 © IEC 2020
3.1.3
channel URI
primary identifier for a channel
3.1.4
filter expression
filtering element that may be applied to messages on a channel
3.1.5
listener identification
implementation defined element that is used to indicate to an application when a new message
has arrived
3.1.6
message content
body of the message
3.1.7
message expiry
duration until the expiration of a publication message on a publication channel
3.1.8
message ID
identifier generated upon posting of a message to a channel in a session
3.1.9
MSM service
set of implemented services based on the messaging service model
3.1.10
MSM Service Provider
application that exposes and implements the MSM service
3.1.11
namespace
collection of names or words that define a formal and distinct set
3.1.12
security token
physical device or software code used to gain access to a channel
3.1.13
session ID
identifier generated upon an application creating a session on a channel and provided to the
application for use in the MSM service
3.1.14
topic
identification of the information content in a message
3.2 Abbreviations
B2MML Business to Manufacturing Markup Language
CB (radio) Citizens’ Band radio
CCOM Common Conceptual Object Model
ERP Enterprise Resource Planning

ESB Enterprise Service Bus
FTP File Transfer Protocol
HTTP Hypertext Transmission Protocol
JMS Java Message Service
MSM Messaging Service Model
MIMOSA Operations and Maintenance Information Open System Alliance
OAG Open Applications Group
OAGIS Open Applications Group Integration Specification
OMAC Organization for Machine Automation and Control
OpenO&M Open Operations and Maintenance Group
OPC UA OPC Unified Architecture
REST Representational State Transfer
RSS Really Simple Syndication
SOAP Simple Object Access Protocol
TCP/IP Transmission Control Protocol / Internet Protocol
UDDI Universal Description, Discovery and Integration
URI Universal Resource Identifier
WS_* World Wide Web Service standards
XML Extensible Markup Language
XSLT Extensible Stylesheet Language Transformations

3.3 Conventions
Input and returned parameters defined in Clause 6 are mandatory unless they are explicitly
defined as optional.
4 Overview of the MSM
4.1 Positioning of the MSM
Application to application data exchange is represented in communication models as a single
"Application" layer, as shown in Figure 1. Although the OSI model represents communication
systems, additional mechanisms are required to describe the complexity of object-based
application-to-application transactional communication. These mechanisms are specified by
standards for defining data objects and for defining transaction messages
The generic data object models are defined by IEC 62264-2 and IEC 62264-4 and they are
implemented by specific data representation technologies (e.g. B2MML, MIMOSA CCOM and
OAGIS nouns). The generic transaction messages are defined by IEC 62264-5 and they are
implemented by specific message transaction technologies (e.g. OAGIS 9.0 Verbs). The data
objects are transformed into transaction messages. These transaction messages are passed to
the underlying exchange services through the MSM service, which is based on the Message
Service Model defined by this document. This message flow is shown in Figure 3.
MSM is an interface that resides on the exchange service used by an application and exchanges
the transaction messages using the exchange services.

– 14 – IEC 62264-6:2020 © IEC 2020

Figure 3 – Positioning and role of MSM
4.2 Abstract service model
The MSM defines a set of common abstract services that is located above the application layer
of the OSI model, and that is used for exchanging transaction messages based on the
transaction models defined in IEC 62264-5. These services, which are called MSM Service,
provide a method for multiple applications to communicate using the transaction models defined
in IEC 62264-5. The MSM:
a) does not define how the services are implemented,
b) does not define the architecture of the supporting application,
c) does not define any specific underlying communication method.
The MSM provides an implementation independent common interface to different MSM service
providers.
The characteristics of services, such as security features, reliability, guaranteed delivery,
quality of service, transformation capability, and other features are not defined in this document.
4.3 Transaction models supported
The MSM defines a standard interface for applications to exchange data using any of the
transaction models defined by IEC 62264-5 (i.e. PUSH model, PULL model and PUBLISH
model).
Although any transaction models defined by IEC 62264-5 can be exchanged through the MSM
service, the following limitations on verbs that can be used for MSM services shall be
considered:
a) for a PUBLISH model with multiple subscribers and multiple publishers, the subscribers and
publishers can have no direct knowledge of other applications. Only SYNC messages
exchanges can be used for this model;
b) for a PUSH model and PULL model, the application sends unsolicited requests for a service
and has no direct knowledge of the receiving application that will process the request. Only
GET/SHOW, PROCESS/ACKNOWLEDGE. CHANGE/RESPONSE and CANCEL message
exchanges can be used for these models.

4.4 Application roles
MSM uses a simpler terminology for application roles than that used in IEC 62264-5. The roles
of Information Provider and Information Receiver of IEC 62264-5 are merged into one role
called Provider Application. The roles of Information User and Information Sender of
IEC 62264-5 are merged into one role called Consumer Application. The difference of the
terminology between this document and IEC 62264-5 is shown in Figure 4.
NOTE IEC 62264-5 defines four roles:
1) Information Provider (to receive GET messages and send SYNC messages),
2) Information Receiver (to receive PROCESS, CHANGE, and CANCEL messages),
3) Information Users (to send GET messages and receive SYNC messages),
4) Information Sender (to send PROCESS, CHANGE, and CANCEL messages).
The Provider Application is the owner of data. The Provider Application can publish changes to
the data, can receive requests to change the data, and respond to queries for the data. A
Consumer Application uses and manipulates data owned by Provider Applications. It can
subscribe to changes of the data, can send requests to change the data, and receive reported
information.
NOTE The phrase "owner of data" is used to identify the application that has responsibility for enforcing the
consistency of data.
An application can be a provider application, consumer application or both.

Figure 4 – Messaging service model terminology
4.5 MSM channels
The MSM is based on the abstract concept of MSM channels. An MSM channel represents a
specific communication pathway between applications. MSM channels can be of a type used
for requests or a type used for publications as shown in Table 1.
Each MSM channel is identified by a URI or equivalent identifier and supports two-way
communications between provider applications and consumer applications. An MSM channel is
created to support either publication channel services or request channel services. MSM
channels have associated topics, which are identified when subscribing to a channel, when
posting a publication, and when posting a request.
A provider application posts a publication to a publication channel. A consumer application
subscribes to a publication channel and reads publications. Consumer applications could
subscribe to publication notifications if supported by the specific publication channel service. If
notifications are not supported, then the consumer application polls the publication channel
using the read publication service.

– 16 – IEC 62264-6:2020 © IEC 2020
A consumer application posts a request to a request channel. A provider application subscribes
to a publication channel and reads publications. Provider applications could subscribe to
publication notifications if supported by the specific publication channel service. If notifications
are not supported, then the provider application polls the publication channel using the read
publication service.
Table 1 – Application roles, channels, and services
Application role Channel type associated MSM services available in the channel
with role
Provider Publication channel Provider publication services
Provider Request channel Provider request services
Consumer Publication channel Consumer publication services
Consumer Request channel Consumer request services

4.6 MSM channel services
4.6.1 Types of channel services
MSM defines the following groups of channel service:
– Channel management services,
– Publication channel services,
– Request channel services.
4.6.2 Channel management services
The services provided for each MSM channel are known as the channel management services.
The channel management services are used to create and delete channels and to control the
Security Token specification for channels.
The channel management services are shown in Figure 5. These services would usually be
called by a provider application, or by a dedicated channel management application.

Figure 5 – Channel management services
4.6.3 Publication channel services
The Publication Channel Services are used to post, expire, remove, and read publication
messages.
The Publication Channel Services are shown in Fig
...