BS EN 61158-6-7-2008 Industrial communication networks Fieldbus specifications Application layer protocol specification Type 7 elements《工业通讯网络 现场总线规范 应用层协议规范 7型元件》.pdf

1、BRITISH STANDARDBS EN 61158-6-7:2008Industrial communication networks Fieldbus specifications Part 6-7: Application layer protocol specification Type 7 elementsICS 25.040.40; 35.100.70g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g

2、3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-6-7:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 BSI 2008ISBN 978 0 580 61627 3National forewordA list of organizations repres

3、ented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application.Compliance with a British Standard cannot confer immunity from legal obligations.Amendments/c

4、orrigenda issued since publicationDate CommentsThis British Standard is the UK implementation of EN 61158-6-7:2008. It is identical with IEC 61158-6-7:2007. Together with all of the other sections of BS EN 61158-6, it supersedes BS EN 61158-6:2004 which is withdrawn. The UK participation in its prep

5、aration was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control, including Fieldbus.EUROPEAN STANDARD EN 61158-6-7 NORME EUROPENNE EUROPISCHE NORM March 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation E

6、lectrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref. No. EN 61158-6-7:2008 E ICS 35.100.70; 25.040.40 Partially s

7、upersedes EN 61158-6:2004English version Industrial communication networks - Fieldbus specifications - Part 6-7: Application layer protocol specification - Type 7 elements (IEC 61158-6-7:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 6-7: Spcification des servi

8、ces des couches dapplication - Elments de type 7 (CEI 61158-6-7:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-7: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 7-Elemente (IEC 61158-6-7:2007) This European Standard was approved by CENELEC on 2008-02-01. CENELEC

9、members are bound to comply with the CEN/CENELEC Internal 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 appli

10、cation to the Central Secretariat or to 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 Central Secretari

11、at has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Net

12、herlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Foreword The text of document 65C/476/FDIS, future edition 1 of IEC 61158-6-7, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control and automa

13、tion, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-7 on 2008-02-01. This and the other parts of the EN 61158-6 series supersede EN 61158-6:2004. With respect to EN 61158-6:2004 the following changes were made: deletion of Type 6 fieldbus for lack of market

14、 relevance; addition of new fieldbus types; partition into multiple parts numbered 6-2, 6-3, 6-20. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2008-11-01 latest date by wh

15、ich the national standards conflicting with the EN have to be withdrawn (dow) 2011-02-01 NOTE Use of some of the associated protocol types is restricted by their intellectual-property-right holders. In all cases, the commitment to limited release of intellectual-property-rights made by the holders o

16、f those rights permits a particular data-link layer protocol type to be used with physical layer and application layer protocols in type combinations as specified explicitly in the EN 61784 series. Use of the various protocol types in other combinations may require permission from their respective i

17、ntellectual-property-right holders. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61158-6-7:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 61158-6-7:2008 2 CONTENTS INTRODUCTION.7 1 Scope.8 1.1 General .8 1.

18、2 Specifications8 1.3 Conformance.8 2 Normative references .9 3 Terms, definitions, symbols, abbreviations and conventions .9 3.1 Terms and definitions from other ISO/IEC standards .9 3.2 Terms and definitions from IEC 61158-5-7.10 3.3 Additional terms and definitions.11 3.4 Abbreviations and symbol

19、s15 3.5 Conventions 15 3.6 Conventions used in state machines .15 4 Abstract syntax of data type .16 4.1 Data abstract syntax specification .16 4.2 FAL PDU abstract syntax 20 5 Transfer syntaxes.21 5.1 Compact encoding.21 5.2 Data type encoding .22 6 Structure of protocol machines .81 7 AP-context s

20、tate machine.82 8 Sub-MMS FAL service protocol machine (FSPM)82 8.1 General .82 8.2 Projection of the SUB-MMS PDUs on the MCS services 82 8.3 Projection of the SUB-MMS abort service on the MCS services.82 8.4 Construction of a SUB-MMS-PDU from a service primitive 83 8.5 Extraction of a valid service

21、 primitive from a SUB-MMS-PDU 83 8.6 Negotiation of an abstract syntax and a transfer syntax commonly called presentation-context83 8.7 Identification of the SUB-MMS core abstract syntax 85 8.8 Identification of the application context name 86 8.9 Identification of the ASE of the core abstract synta

22、x and the transfer syntax .86 9 Association relationship protocol machine (ARPM ) 86 10 DLL mapping protocol machine (DMPM).87 10.1 MPS ARPM and DMPM .87 10.2 MCS ARPM and DMPM .98 11 Protocol options .134 11.1 Conformances classes 134 Bibliography154 Figure 1 Example of an evaluation net .16 Figure

23、 2 Encoding of a CompactValue .21 Figure 3 Organisation of the bits and octets within a PDU23 Annex ZA (normative) Normative references to international publications with their corresponding European publications 155 BS EN 61158-6-7:2008 3 Figure 4 Encoding of a Bitstring .26 Figure 5 Encoding of a

24、Floating point value .27 Figure 6 Encoding of a structure 28 Figure 7 Encoding of a Boolean array 29 Figure 8 Representation of a MCS PDU .35 Figure 9 Relationships among Protocol Machines and Adjacent Layers .81 Figure 10 A_Readloc service evaluation net 87 Figure 11 A_Writeloc service evaluation n

25、et.88 Figure 12 A_Update service evaluation net 89 Figure 13 A_Readfar service evaluation net.90 Figure 14 A_Writefar service evaluation net.92 Figure 15 A_Sent service evaluation net 93 Figure 16 A_Received service evaluation net.93 Figure 17 Association establishment: Requester element state machi

26、ne 100 Figure 18 Association establishment: Responder element state machine .101 Figure 19 Association termination: Requester element state machine 103 Figure 20 Association termination: Responder element state machine .105 Figure 21 Association revocation: Requester element state machine .106 Figur

27、e 22 Association revocation: Acceptor element state machine107 Figure 23 Interactions between state machine in an associated mode data transfer.109 Figure 24 Transfer service: Requester element state machine .113 Figure 25 Transfer service: Acceptor element state machine .114 Figure 26 Unacknowledge

28、d transfer: Requester element state machine.115 Figure 27 Unacknowledged transfer: Acceptor element state machine .115 Figure 28 Acknowledged transfer: Requester element state machine.117 Figure 29 Acknowledged transfer: Acceptor element state machine .118 Figure 30 Numbering mechanism state machine

29、 119 Figure 31 Retry machanism state machine.121 Figure 32 Anticipation mechanism state machine.124 Figure 33 Segmentation mechanism state machine126Figure 34 Reassembly mechanism state machine 128 Figure 35 Interaction of state machine in a non associated data transfer .130 Figure 36 Unacknowledged

30、 transfer: Requester element state machine.131 Figure 37 Unacknowledged transfer: Acceptor element state machine .131 Figure 38 Acknowledged transfer: Requester element state machine.132 Figure 39 Acknowledged transfer: Acceptor element state machine .133 Table 1 Example of encoding of a SEQUENCE 18

31、 Table 2 Example of encoding of a SEQUENCE OF 18 Table 3 Example of encoding of a CHOICE19 Table 4 Example of encoding of an object identifier .20 Table 5 Example of encoding of a PDU21 Table 6 MPS PDU types 24 BS EN 61158-6-7:2008 4 Table 7 Fields of a CompactValuePDU 24 Table 8 Fields of a Variabl

32、eDescriptionPDU.31 Table 9 Fields of an AccessDescriptionPDU 32 Table 10 Fields of a TypeDescriptionPDU33 Table 11 Fields of a ListDescriptionPDU 34 Table 12 Coding of the different MCS PDU types.36 Table 13 Coding of the variable part of the PDU 36 Table 14 Structure of association establishment re

33、quest37 Table 15 Structure of an associated establishment response .41 Table 16 Structure of an association termination request .43 Table 17 Structure of an association termination response 43 Table 18 Structure of an association revocation request 44 Table 19 Structure of an associated transfer req

34、uest .45 Table 20 Structure of an associated transfer acknowledgement .45 Table 21 Structure of a non-associated transfer request 46 Table 22 Structure of a non-associated transfer acknowledgement 47 Table 23 Definitions of object classes 49 Table 24 Definition of Sub-MMS Services 50 Table 25 Struct

35、ure of the antiduplication list.122 Table 26 Structure of the reassembly list .127 Table 27 PV_R/W parameter values 135 Table 28 PV_IND parameter values .135 Table 29 PV_LIS parameter values135 Table 30 Constraints on PV_LIS parameter .136 Table 31 PV_AT parameter values.136 Table 32 PV_RE parameter

36、 values 136 Table 33 PV_UT parameter values.136 Table 34 Constraints on PV_RE parameter 136 Table 35 PH_R_A parameter values 137 Table 36 PH_R_S parameter values 137 Table 37 PH_R_P parameter values 137 Table 38 PH_P_A parameter values 138 Table 39 PH_P_S parameter values 138 Table 40 PH_P_P paramet

37、er values 138 Table 41 PH_COH parameter values .138 Table 42 PH_FIA parameter values139 Table 43 PH_SPF parameter values 139 Table 44 PH_SPM parameter values139 Table 45 PH_ACC parameter values140 Table 46 PH_RES parameter values140 Table 47 PH_AK parameter values 140 Table 48 PH_RA parameter values

38、 140 Table 49 PH_SR parameter values 140 BS EN 61158-6-7:2008 5 Table 50 PH_CF parameter values 141 Table 51 Constraints on PH_RA parameter141 Table 52 Constraints on PH_SR parameter141 Table 53 PT_OCT parameter values 141 Table 54 PT_BIN parameter values142 Table 55 PT_VIS parameter values142 Table

39、 56 PT_BOO parameter values142 Table 57 PT_BCD parameter values 142 Table 58 PT_BTM parameter values 143 Table 59 PT_INT parameter values143 Table 60 PT_UNS parameter values 143 Table 61 PT_FPT parameter values.143 Table 62 PT_GTM parameter values144 Table 63 PT_TAB parameter values.144 Table 64 PT_

40、STR parameter values 144 Table 65 Constraints on PT_TAB parameter 145 Table 66 Constraints on PT_STR parameter 145 Table 67 Conformance classes for environment management148 Table 68 Conformance classes for VMD management .149 Table 69 Conformance classes for PI managment150 Table 70 Conformance cla

41、sses for domain management151 Table 71 Conformance classes for variable/variable list management152 Table 72 Conformance classes for event management 153 BS EN 61158-6-7:2008 6 INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate the interconnection of automation system comp

42、onents. It is related 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

43、 aim of this standard 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

44、 of purposes: as a guide for implementors 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 standard is con

45、cerned, in particular, with the communication and interworking of sensors, effectors and other automation devices. By using this standard together with other standards positioned within the OSI or fieldbus reference models, otherwise incompatible systems may work together in any combination. BS EN 6

46、1158-6-7:2008 7 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-7: Application layer protocol specification Type 7 elements 1 Scope 1.1 General The fieldbus application layer (FAL) provides user programs with a means to access the fieldbus communication environment. In this respect,

47、 the FAL can be viewed as a “window between corresponding application programs.” This standard provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 7 fieldbus. The term

48、“time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, wit

49、h attendant risk to equipment, plant and possibly human life. This standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 7 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protoco