BS EN 61158-6-4-2008 工业通信网络.现场总线规范.应用层协议规范.4型元件.pdf

BRITISH STANDARD BS EN 61158-6-4:2008 Industrial communication networks Fieldbus specifications Part 6-4: Application layer protocol specification Type 4 elements ICS 25.040.40; 35.100.70 BS EN 61158-6-4:2008 This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 © BSI 2008 ISBN 978 0 580 61625 9 National foreword 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 provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard cannot confer immunity from legal obligations. Amendments/corrigenda issued since publication DateComments This British Standard is the UK implementation of EN 61158-6-4:2008. It is identical with IEC 61158-6-4: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 preparation was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and control, including Fieldbus. EUROPEAN STANDARD EN 61158-6-4 NORME EUROPÉENNE EUROPÄISCHE NORM March 2008 CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für 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-4:2008 E ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-6:2004 English version Industrial communication networks - Fieldbus specifications - Part 6-4: Application layer protocol specification - Type 4 elements (IEC 61158-6-4:2007) Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-4: Spécification des services des couches d'application - Eléments de type 4 (CEI 61158-6-4:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-4: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 4-Elemente (IEC 61158-6-4:2007) This European Standard was approved by CENELEC on 2008-02-01. CENELEC 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 application 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 Secretariat 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 Netherlands, 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-4, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-4 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 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 which 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 of 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 intellectual-property-right holders. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IEC 61158-6-4:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 61158-6-4:2008 2 CONTENTS INTRODUCTION.ë 1 Scope.ê 1.1 General .ê 1.2 Specificationsê 1.3 Conformance.ê 2 Normative references .é 3 Terms, definitions, symbols, abbreviations and conventions .òòè 3.1 Referenced terms and definitions òòè 3.2 Abbreviations and symbolsòòç 3.3 Conventions òòç 4 FAL syntax description .1ï 4.1 FAL-AR PDU abstract syntax 1ï 4.2 Data types.1í 5 Transfer syntaxes.1í 5.1 APDU encoding.1í 5.2 Variable object encoding and packing .1é 5.3 Error codes .2ð 6 FAL protocol state machines 2ð 7 AP-context state machine.2ï 8 FAL service protocol machine (FSPM)2î 8.1 Primitives exchanged between FAL User and FSPM .2î 8.2 FSPM states2î 9 Application relationship protocol machine (ARPM)îè 9.1 Primitives exchanged between ARPM and FSPM îè 9.2 ARPM States.îè 10 DLL mapping protocol machine (DMPM).3ð 10.1 Data-link Layer service selection.3ð 10.2 Primitives exchanged between ARPM and DLPM 3ð 10.3 Primitives exchanged between DLPM and data-link layer 3ï 10.4 DLPM states3ï 11 Protocol options ò3í Bibliography3ì Figure 1 State transition diagram .1ð Figure 2 APDU header structure 1ì Figure 3 Instruction subfield of ControlStatus.1ì Figure 4 Errorcode subfield of ControlStatus1ì Figure 5 Remaining subfields of ControlStatus.1ë Figure 6 DataFieldFormat encoding .1ë Figure 7 Structure of request APDU body 1ë Figure 8 Structure of response APDU body1ê Figure 9 Variable identifier.1ê ß²²»¨ Æß ø²±®³¿¬·ª»÷ Ò±®³¿¬·ª» ®»º»®»²½»- ¬± ·²¬»®²¿¬·±²¿´ °«¾´·½¿¬·±²- ©·¬¸ ¬¸»·® ½±®®»-°±²¼·²¹ Û«®±°»¿² °«¾´·½¿¬·±²- .òòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòòíë BS EN 61158-6-4:2008 3 Figure 10 Code subfield of variable identifier .1ê Figure 11 Summary of FAL architecture.2ï Figure 12 FSPM proxy object state machine 2í Figure 13 FSPM real object state machine.2é Figure 14 ARPM state machineîè Figure 15 DLPM state machine 3ï Table 1 State machine description elements 1ð Table 2 APDU header 1ï Table 3 APDU body .1î Table 4 Transfer syntax for Array.ïè Table 5 Transfer syntax for Structure.ïç Table 6 Common variable object attributes ïç Table 7 Variable type identifiers.ïç Table 8 FIFO variable object attributes 2ð Table 10 Primitives exchanged between FAL-User and FSPM .2î Table 11 REQUEST.req FSPM constraints.2í Table 12 REQUEST.req FSPM actions 2ì Table 13 RESPONSE.cnf FSPM constraints 2ë Table 14 RESPONSE.cnf FSPM actions 2ê Table 15 AR Send.ind proxy FSPM constraints 2ê Table 16 AR Send.ind proxy FSPM actions2ê Table 17 AR Send.ind real FSPM constraints.2é Table 18 AR Send.ind real FSPM Actions 2é Table 19 Primitives issued by FSPM to ARPM .îè Table 20 Primitives issued by ARPM to FSPM .îè Table 21 Primitives issued by ARPM to ARPM.îè Table 22 AR Send.req ARPM constraints.îç Table 23 AR Send.req ARPM actions.îç Table 24 AR Acknowledge.req ARPM constraints îç Table 25 AR Acknowledge.req ARPM actions îç Table 26 AR Send.ind ARPM constraints .îç Table 27 AR Send.req ARPM actions.3ð Table 28 Primitives issued by ARPM to DLPM .3ï Table 29 Primitives issued by DLPM to ARPM .3ï Table 30 Primitives issued by DLPM to data-link layer .3ï Table 31 Primitives issued by data-link layer to DLPM .3ï Table 32 AR Send.req DLPM constraints .3î Table 33 AR Send.req DLPM actions .3î Table 34 AR Acknowledge.req DLPM constraints.3î Table 35 AR Acknowledge.req DLPM actions.3î Table 36 DL-UNITDATA.ind DLPM constraints.3í Table 37 DL-UNITDATA.ind DLPM actions.3í BS EN 61158-6-4:2008 4 Table 9 Error codes .îð INTRODUCTION This part of IEC 61158 is one of a series produced to facilitate the interconnection of automation system components. 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 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 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 concerned, 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 61158-6-4:2008 5 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-4: Application layer protocol specification Type 4 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, 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 4 fieldbus. The term “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, with 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 4 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this standard is to define the protocol provided to 1) define the wire-representation of the service primitives defined in IEC 61158-5-4, and 2) define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 4 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI application layer structure (ISO/IEC 9545). 1.2 Specifications The principal objective of this standard is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-4. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of protocols standardized in IEC 61158-6. 1.3 Conformance This standard do not specify individual implementations or products, nor do they constrain the implementations of application layer entities within industrial automation systems. BS EN 61158-6-4:2008 6 Conformance is achieved through implementation of this application layer protocol specification. 2 Normative references The following referenced documents are indispensable for the application 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 61158-3-4, Industrial communication networks Fieldbus specifications Part 3-4: Data- link layer service definition Type 4 elements IEC 61158-4-4, Industrial communication networks Fieldbus specifications Part 4-4: Data- link layer protocol specification Type 4 elements IEC 61158-5-4, Industrial communication networks Fieldbus specifications Part 5-4: Application layer service definition Type 4 elements ISO/IEC 10731, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition of OSI services ISO/IEC 7498-1, Information technology Open Systems Interconnection Basic Reference Model Part1: The Basic Model ISO/IEC 8822, Information technology Open Systems Interconnection Presentation service definition ISO/IEC 8824, Information technology Open Systems Interconnection Specification of Abstract Syntax Notation One (ASN.1) ISO/IEC 9545, Information technology Open Systems Interconnection Application Layer structure BS EN 61158-6-4:2008 7 3 Terms, definitions, symbols, abbreviations and conventions For the purposes of this document, the following definitions apply. 3.1 Referenced terms and definitions 3.1.1 ISO/IEC 7498-1 terms For the purposes of this document, the following terms as defined in ISO/IEC 7498-1 apply: a) application entity b) application process c) application protocol data unit d) application service element e) application entity invocation f) application process invocation g) application transaction h) real open system i) transfer syntax 3.1.2 ISO/IEC 8822 terms For the purposes of this document, the following terms as defined in ISO/IEC 8822 apply: a) abstract syntax b) presentation context 3.1.3 ISO/IEC 9545 terms For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply: a) application-association b) application-context c) application context name d) application-entity-invocation e) application-entity-type f) application-process-invocation g) application-process-type h) application-service-element i) application control service e