1、Enterprise-control system integration Part 6: Messaging Service Model PD IEC/PAS 62264-6:2016 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National foreword This Published Document is the UK implementation of IEC/PAS 62264- 6:2016. The UK participation in its pre
2、paration was entrusted to Technical Committee AMT/7, Industrial communications: process measurement and control, including fieldbus. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provi
3、sions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 91723 3 ICS 25.040.99; 35.100.01; 35.100.50 Compliance with a British Standard cannot confer immunity from legal obligations. This Pu
4、blished Document was published under the authority of the Standards Policy and Strategy Committee on 31 July 2016. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD IEC/PAS 62264-6:2016 IEC PAS 62264-6 Edition 1.0 2016-07 PUBLICLY AVAILABLE SPECIFICATION PRE-STA
5、NDARD Enterprise-control system integration Part 6: Messaging Service Model INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 25.040.99; 35.100; 35.100.50 ISBN 978-2-8322-3487-7 Registered trademark of the International Electrotechnical Commission Warning! Make sure that you obtained this publication fr
6、om an authorized distributor. colour inside PD IEC/PAS 62264-6:2016 2 IEC PAS 62264-6:2016 IEC 2016 CONTENTS FOREWORD . 6 INTRODUCTION . 8 1 Scope 10 2 Normative references. 10 3 Terms, definitions and abbreviations 10 Terms and definitions 10 3.1Abbreviations 11 3.2Conventions 12 3.3 4 The Messagin
7、g Service Model . 12 Interface model . 12 4.1Application to application data exchange . 12 4.2Transaction model . 14 4.3Communicating applications 14 4.4Managed communication channels 15 4.5Notification services 16 4.6MSM channel services 16 4.7MSM publication channel services . 17 4.8 4.8.1 Publica
8、tion channel services 17 MSM request channel services 18 4.9 4.9.1 Request services . 18 5 Methods of operation of MSM channels 18 Channel and topic identification . 18 5.1Channel names and hierarchy . 18 5.2 5.2.1 Channel names 18 5.2.2 Channel name hierarchy 19 5.2.3 MSM root . 19 5.2.4 Channel sc
9、ope . 19 5.2.5 Information scope 19 5.2.6 Channel use 20 Message filtering . 21 5.3Publication expiration 21 5.4Topics . 22 5.5 5.5.1 Topic definition 22 5.5.2 Standard topics 22 MSM sessions . 23 5.6Security 23 5.7 5.7.1 Secure message exchanges . 23 5.7.2 Security tokens on channels . 23 5.7.3 Sec
10、urity token format . 24 5.7.4 MSM service provider implementations . 24 6 MSM service definitions . 24 Type definitions . 24 6.1MSM service returns and faults 25 6.2MSM channel management services 26 6.3 6.3.1 Create channel 26 6.3.2 Add security tokens 26 PD IEC/PAS 62264-6:2016IEC PAS 62264-6:2016
11、 IEC 2016 3 6.3.3 Remove security tokens . 26 6.3.4 Delete channel . 27 6.3.5 Get channel . 27 6.3.6 Get channels . 28 Notify listener service 28 6.4 6.4.1 Notify listener . 28 MSM provider publication services . 28 6.5 6.5.1 Open publication session . 28 6.5.2 Post publication . 29 6.5.3 Expire pub
12、lication 29 6.5.4 Close publication session . 30 MSM consumer publication services 30 6.6 6.6.1 Open subscription session . 30 6.6.2 Read publication 30 6.6.3 Remove publication 31 6.6.4 Close subscription session . 31 MSM provider request services 32 6.7 6.7.1 Open provider request session . 32 6.7
13、.2 Read request . 32 6.7.3 Remove request . 32 6.7.4 Post response 33 6.7.5 Close provider request session . 33 MSM consumer request services . 34 6.8 6.8.1 Open consumer request session . 34 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
14、 35 7 Scenarios 36 Publish-subscribe scenarios 36 7.1 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 publishers scenario . 38 7.1.5 Publish-subscribe scenario with publica
15、tion expiration 39 Request channel scenarios 40 7.2 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 Compliance . 43 Annex A (informative) MSM service provider considerations . 44 A.1 Service provider con
16、siderations . 44 A.2 Notification 44 A.3 Security considerations . 44 A.4 MSM application implementation considerations 44 A.5 MSM channel security considerations 44 A.6 MSM session ID considerations . 45 A.7 Data format validation . 45 A.8 Allowed application checking . 45 PD IEC/PAS 62264-6:2016 4
17、 IEC PAS 62264-6:2016 IEC 2016 A.9 Data exchange logging 45 A.10 Common error handling . 45 A.11 Data transformation services . 45 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-appl
18、ication communication . 9 Figure 2 Application communication stack 13 Figure 3 Defined standards at each level 14 Figure 4 Messaging service model names 15 Figure 5 MSM channel management services . 17 Figure 6 MSM publication channel services 17 Figure 7 Services for request/response 18 Figure 8 Ch
19、anges and checkpoint channel example 21 Figure 9 Security of channels . 24 Figure 10 Publication scenario with notification . 36 Figure 11 Publication scenario with multiple messages . 37 Figure 12 Publication scenario without notification 38 Figure 13 Publication scenario with multiple provider app
20、lications . 39 Figure 14 Publication scenario with expired publications . 40 Figure 15 GET/SHOW request service scenario 41 Figure 16 CHANGE / RESPONSE request service scenario 42 Figure 17 Multiple providers CHANGE/RESPONSE scenario 43 Figure A.1 Transformation services with the MSM service provide
21、r . 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 MSM type definitions . 25 Table 2 MSM service returns and fault definitions . 25 Table 3 Create channel 26 Table 4 Add security token . 26 Table 5 Remov
22、e security token 27 Table 6 Delete channel 27 Table 7 Get channel . 27 Table 8 Get channels . 28 Table 9 Notify listener 28 Table 10 Open publication session . 29 Table 11 Post publication . 29 Table 12 Expire publication 29 Table 13 Close publication session 30 Table 14 Open subscription session .
23、30 Table 15 Read publication 31 PD IEC/PAS 62264-6:2016IEC PAS 62264-6:2016 IEC 2016 5 Table 16 Remove publication . 31 Table 17 Close subscription session . 31 Table 18 Open provider request session . 32 Table 19 Read request . 32 Table 20 Remove request 33 Table 21 Post response . 33 Table 22 Clos
24、e provider request session 33 Table 23 Open consumer request session 34 Table 24 Post request 34 Table 25 Read response 35 Table 26 Remove response 35 Table 27 Close consumer request session 35 PD IEC/PAS 62264-6:2016 6 IEC PAS 62264-6:2016 IEC 2016 INTERNATIONAL ELECTROTECHNICAL COMMISSION _ ENTERP
25、RISE-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
26、 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 referr
27、ed 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
28、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 internati
29、onal 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
30、 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 Publ
31、ications 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.
32、 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
33、) 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 co
34、sts (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 appli
35、cation 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. A PAS is a technical specification not fulfilling the requireme
36、nts for a standard, but made available to the public. IEC PAS 62264-6 has been processed by subcommittee 65E: Devices and integration in enterprise systems, of IEC technical committee 65: Industrial-process measurement, control and automation. The text of this PAS is based on the following document:
37、 This PAS was approved for publication by the P-members of the committee concerned as indicated in the following document Draft PAS Report on voting 65E/476/PAS 65E/502/RVD Following publication of this PAS, which is a pre-standard publication, the technical committee or subcommittee concerned may t
38、ransform it into an International Standard. PD IEC/PAS 62264-6:2016IEC PAS 62264-6:2016 IEC 2016 7 This PAS shall remain valid for an initial maximum period of 3 years starting from the publication date. The validity may be extended for a single period up to a maximum of 3 years, at the end of which
39、 it shall be published as another type of normative document, or shall be withdrawn. 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
40、 this document using a colour printer. PD IEC/PAS 62264-6:2016 8 IEC PAS 62264-6:2016 IEC 2016 INTRODUCTION This PAS is based on the use of ISA-95 object models defined in ISA-95 Parts 2, 4 and 5 (Parts 1 and 3 do not contain object models) to define a set of services that may be used to exchange in
41、formation messages. It is recognized that other, non-Part 6 sets of services are possible and are not deemed invalid as a result of this PAS. This PAS defines a Messaging Service Model (MSM) for exchanging data exchange messages in a publish/subscribe mode and a request/response mode. It defines a m
42、inimal interface subset to message exchange systems. 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 communication protoco
43、l. This PAS defines a set of services definitions that are designed to provide the functionality needed for a vendor-independent method for sending and receiving data exchange messages on a message exchange system, such as an Enterprise Service Bus (ESB). The knowledge requirements to interface to j
44、ust 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 services, for Level 3-3 and Level 4-3 communications. This removes the need for vendors to build custom interface after custom interfa
45、ce, and for end users to get locked into a single vendor because their investment prevents them from reusing any of the integration efforts. Enterprise-control system integration involves multiple different steps to exchange data between different computer system applications, as shown in Figure 1.
46、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. The ISA-95 Part 2 standard defines representations of a global format for Leve
47、l 4-3 data exchanges. The Part 4 standard defines representations 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 applic
48、ation initiates a data exchange with the BETA application, and BETA responds back to ALPHA. The format conversions are: ALPHAs local format to global format for the request data, global format to BETAs local format for the request data, BETAs local format to global format for the response data, and
49、global format to ALPHAs 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 may be codes, tag names, or equipment identifiers. EXAMPLE 3 Data which are represented in one element namespace, such as codes 1,2,3,4, may have a different namespace in another applic
