1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationIndustrial communicationnetworks FieldbusspecificationsPart 6-15: Application layer protocol specification Type 15 elementsBS EN 61158-6-15:2012National forewordThis British Stan
2、dard is the UK implementation of EN 61158-6-15:2012. It isidentical to IEC 61158-6-15:2010. It supersedes BS EN 61158-6-15:2008which is withdrawn.The UK participation in its preparation was entrusted to Technical CommitteeAMT/7, Industrial communications: process measurement and control, including f
3、ieldbus.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions of acontract. Users are responsible for its correct application. The British Standards Institution 2012Published by BSI S
4、tandards Limited 2012ISBN 978 0 580 71568 6ICS 25.04.40; 35.100.70; 35.110Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of the StandardsPolicy and Strategy Committee on 31 July 2012.Amendments issued since publ
5、icationAmd. No. Date Text affectedBRITISH STANDARDBS EN 61158-6-15:2012EUROPEAN STANDARD EN 61158-6-15 NORME EUROPENNE EUROPISCHE NORM June 2012 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische No
6、rmung Management Centre: Avenue Marnix 17, B - 1000 Brussels 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61158-6-15:2012 E ICS 25.040.40; 35.100.70; 35.110 Supersedes EN 61158-6-15:2008English version Industrial communica
7、tion networks - Fieldbus specifications - Part 6-15: Application layer protocol specification - Type 15 elements (IEC 61158-6-15:2010) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 6-15: Spcification des protocoles des couches dapplication - Elments de type 15 (CEI
8、61158-6-15:2010) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-15: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 15-Elemente (IEC 61158-6-15:2010) This European Standard was approved by CENELEC on 2012-03-28. CENELEC members are bound to comply with the CEN/CENELEC I
9、nternal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to
10、any CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the
11、official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Pol
12、and, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 61158-6-15:2012EN 61158-6-15:2012 - 2 - Foreword The text of document 65C/607/FDIS, future edition 2 of IEC 61158-6-15, prepared by SC 65C, “Industrial networks“, of IEC/TC 65, “Industrial-pr
13、ocess measurement, control and automation“ was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN 61158-6-15:2012. The following dates are fixed: latest date by which the document has to be implemented at national level by publication of an identical national standard or by end
14、orsement (dop) 2012-12-28 latest date by which the national standards conflicting with the document have to be withdrawn (dow) 2015-03-28 This document supersedes EN 61158-6-15:2008. EN 61158-6-15:2012 includes the following significant technical changes with respect to EN 61158-6-15:2008: editorial
15、 corrections. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CENELEC and/or CEN shall not be held responsible for identifying any or all such patent rights. Endorsement notice The text of the International Standard IEC 61158-6-15
16、:2010 was approved by CENELEC as a European Standard without any modification. In the official version, for Bibliography, the following note has to be added for the standard indicated: IEC/TR 61158-1:2010 NOTE Harmonized as CLC/TR 61158-1:2010 (not modified). BS EN 61158-6-15:2012- 3 - EN 61158-6-15
17、:2012 Annex ZA (normative) Normative references to international publications with their corresponding European publications The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cit
18、ed applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. Publication Year Title EN/HD Year IEC 61158-5-15 201
19、0 Industrial communication networks - Fieldbus specifications - Part 5-15: Application layer service definition -Type 15 elements EN 61158-5-15 2012 ISO/IEC 7498-1 - Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model - - ISO/IEC 8822 - Information technolo
20、gy - Open Systems Interconnection - Presentation service definition - - ISO/IEC 8824-1 - Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation - - ISO/IEC 9545 - Information technology - Open Systems Interconnection - Application Layer structure - - BS EN 611
21、58-6-15:2012 2 61158-6-15 IEC:2010(E) CONTENTS INTRODUCTION.1H8 1 Scope.2H9 1.1 General .3H9 1.2 Specifications4H9 1.3 Conformance.5H10 2 Normative references . 6H10 3 Terms and definitions, abbreviations, symbols and conventions . 7H10 3.1 Terms and definitions 8H10 3.2 Abbreviations and symbols 9H
22、17 3.3 Conventions 10H19 3.4 Conventions used in state machines . 11H21 4 Abstract syntax for client/server . 12H22 5 Transfer syntax for client/server . 13H22 5.1 General .14H22 5.2 Common APDU structure 15H22 5.3 Service-specific APDU structures 16H26 5.4 Data representation on the wire . 17H51 6
23、Abstract syntax for publish/subscribe . 18H51 7 Transfer syntax for publish/subscribe . 19H52 7.1 General .20H52 7.2 APDU structure . 21H52 7.3 Sub-message structure . 22H53 7.4 APDU interpretation 23H55 7.5 Service specific APDU structures 24H57 7.6 Common data representation for publish/subscribe
24、. 25H79 8 Structure of FAL protocol state machines . 26H83 9 AP-context state machines for client/server 27H85 10 FAL service protocol machine (FSPM) for client/server. 28H85 10.1 General .29H85 10.2 FSPM state tables . 30H85 10.3 Functions used by FSPM. 31H92 10.4 Parameters of FSPM/ARPM primitives
25、 32H92 10.5 Client/server server transactions . 33H92 11 Application relationship protocol machines (ARPMs) for client/server . 34H94 11.1 Application relationship protocol machines (ARPMs) . 35H94 11.2 AREP state machine primitive definitions 36H95 11.3 AREP state machine functions 37H96 12 DLL map
26、ping protocol machine (DMPM) for client/server 38H96 12.1 AREP mapping to data link layer . 39H96 12.2 DMPM states. 40H97 12.3 DMPM state machine 41H97 12.4 Primitives exchanged between data link layer and DMPM . 42H98 12.5 Client/server on TCP/IP. 43H98 13 AP-Context state machines for publish/subs
27、cribe . 44H102 BS EN 61158-6-15:201261158-6-15 IEC:2010(E) 3 14 Protocol machines for publish/subscribe. 45H102 14.1 General . 46H102 14.2 Publish/subscribe on UDP . 47H104 Bibliography 48H105 Figure 1 APDU Format. 49H22 Figure 2 Client to server confirmed service request 50H24 Figure 3 Normal respo
28、nse from server to client 51H24 Figure 4 Exception response from server to client 52H24 Figure 5 Client to server unconfirmed service request 53H25 Figure 6 Publish/subscribe APDU 54H52 Figure 7 Flags of issue request 55H58 Figure 8 Flags of heartbeat request . 56H60 Figure 9 Flags of VAR request .
29、57H64 Figure 10 Flags of GAP request . 58H66 Figure 11 Flags of ACK request . 59H68 Figure 12 Flags of INFO_DST request . 60H72 Figure 13 Flags of INFO_REPLY request. 61H73 Figure 14 Flags of INFO_SRC request. 62H75 Figure 15 Flags of INFO_TS request 63H77 Figure 16 Flags of PAD request . 64H78 Figu
30、re 17 Encoding of octet .65H80 Figure 18 Encoding of boolean 66H80 Figure 19 Encoding of unsigned short 67H80 Figure 20 Encoding of unsigned long . 68H80 Figure 21 Encoding of unsigned long long 69H81 Figure 22 Encoding of float 70H81 Figure 23 Encoding of double 71H81 Figure 24 Relationships among
31、protocol machines and adjacent layers . 72H84 Figure 25 State transition diagram of FSPM. 73H85 Figure 26 Transaction state machine, per connection 74H86 Figure 27 Client/server server transactions 75H93 Figure 28 State transition diagram of the Client ARPM. 76H94 Figure 29 State transition diagram
32、of the server ARPM 77H95 Figure 30 State transition diagram of DMPM 78H97 Figure 31 APDU Format.79H98 Figure 32 TCP/IP PDU Format . 80H99 Figure 33 Publish/subscribe receiver . 81H103 Table 1 Conventions used for state machines 82H21 Table 2 Exception code 83H25 Table 3 Read discretes request . 84H2
33、6 Table 4 Read discretes response. 85H26 BS EN 61158-6-15:2012 4 61158-6-15 IEC:2010(E) Table 5 Read coils request 86H27 Table 6 Read coils response 87H27 Table 7 Write single coil request 88H28 Table 8 Write single coil response . 89H28 Table 9 Write multiple coils request . 90H29 Table 10 Write mu
34、ltiple coils response. 91H29 Table 11 Broadcast write single coil request 92H30 Table 12 Broadcast write multiple coils request 93H31 Table 13 Read input registers request . 94H31 Table 14 Read input registers response. 95H32 Table 15 Read holding registers request 96H32 Table 16 Read holding regist
35、ers response . 97H33 Table 17 Write single holding register request . 98H33 Table 18 Write single holding register response. 99H34 Table 19 Write multiple holding registers request. 100H34 Table 20 Write multiple holding registers response 101H35 Table 21 Mask write holding register request . 102H36
36、 Table 22 Mask write holding register request . 103H36 Table 23 Read/Write multiple holding registers request 104H37 Table 24 Read/Write multiple holding registers response . 105H38 Table 25 Read FIFO request106H38 Table 26 Read FIFO response .107H39 Table 27 Broadcast write single holding register
37、request 108H40 Table 28 Broadcast write multiple holding registers request. 109H41 Table 29 Read file record request 110H42 Table 30 Read file record response . 111H43 Table 31 Write file record request 112H44 Table 32 Write file record response . 113H46 Table 33 Read device identification request.
38、114H47 Table 34 Device identification categories . 115H48 Table 35 Read device ID code . 116H48 Table 36 Read device identification response 117H49 Table 37 Conformity level 118H50 Table 38 Requested vs. returned known objects 119H51 Table 39 APDU structure . 120H53 Table 40 Sub-message structure .
39、121H54 Table 41 Publish/subscribe service identifier encoding 122H54 Table 42 Attributes changed modally and affecting APDUs interpretations . 123H56 Table 43 Issue request 124H57 Table 44 Meaning of issue request flags 125H58 Table 45 Interpretation of issue 126H59 Table 46 Heartbeat request . 127H
40、60 Table 47 Meaning of heartbeat request flags . 128H61 BS EN 61158-6-15:201261158-6-15 IEC:2010(E) 5 Table 48 Interpretation of heartbeat . 129H62 Table 49 VAR request 130H63 Table 50 Meaning of VAR request flags . 131H64 Table 51 Interpretation of VAR. 132H65 Table 52 GAP request 133H66 Table 53 M
41、eaning of GAP request flags . 134H67 Table 54 Interpretation of GAP. 135H67 Table 55 ACK request 136H68 Table 56 Meaning of ACK request flags . 137H69 Table 57 Interpretation of ACK. 138H69 Table 58 Header request . 139H70 Table 59 Change in state of the receiver 140H71 Table 60 INFO_DST request 141
42、H71 Table 61 Meaning of INFO_DST request flags . 142H72 Table 62 INFO_REPLY request . 143H73 Table 63 Meaning of INFO_REPLY request flags. 144H74 Table 64 INFO_SRC request . 145H75 Table 65 Meaning of INFO_SRC request flags. 146H75 Table 66 INFO_TS request 147H76 Table 67 Meaning of INFO_TS request
43、flags 148H77 Table 68 PAD request 149H78 Table 69 Meaning of PAD request flags . 150H78 Table 70 Semantics . 151H79 Table 71 FSPM state table client transactions. 152H87 Table 72 FSPM state table server transactions . 153H92 Table 73 Function MatchInvokeID() 154H92 Table 74 Function HighBit() . 155H
44、92 Table 75 Parameters used with primitives exchanged between FSPM and ARPM 156H92 Table 76 Client ARPM states . 157H94 Table 77 Client ARPM state table 158H94 Table 78 Server ARPM states 159H94 Table 79 Server ARPM state table . 160H95 Table 80 Primitives issued from ARPM to DMPM . 161H95 Table 81
45、Primitives issued by DMPM to ARPM 162H95 Table 82 Parameters used with primitives exchanged between ARPM and DMPM . 163H96 Table 83 DMPM state descriptions. 164H97 Table 84 DMPM state table client transactions 165H97 Table 85 DMPM state table server transactions 166H98 Table 86 Primitives exchanged
46、between data-link layer and DMPM . 167H98 Table 87 Encapsulation parameters for client/server on TCP/IP . 168H99 BS EN 61158-6-15:2012 8 61158-6-15 IEC:2010(E) INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate the interconnection of automation system components. It is rel
47、ated to other standards in the set as defined by the “three-layer” fieldbus reference model described in IEC/TR 61158-1. The application protocol provides the application service by making use of the services available from the data-link or other immediately lower layer. The primary aim of this stan
48、dard is to provide a set of rules for communication expressed in terms of the procedures to be carried out by peer application entities (AEs) 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: as a guide for implementers and designers; for use in the testing and procurement of equipment; as part of an agreement for the admittance of systems into the open systems environment; as a refinement to the understanding of time-critical communications within OSI. This
