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

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

2、3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-6-8:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 BSI 2008ISBN 978 0 580 61628 0National 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-8:2008. It is identical with IEC 61158-6-8: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-8 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-8:2008 E ICS 35.100.70; 25.040.40 Partially s

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

8、ices des couches dapplication - Elments de type 8 (CEI 61158-6-8:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-8: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 8-Elemente (IEC 61158-6-8: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 appl

10、ication 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 Secretar

11、iat 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 Ne

12、therlands, 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-8, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control and autom

13、ation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-8 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 marke

14、t 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 w

15、hich 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

16、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

17、intellectual-property-right holders. IEC and CENELEC draw attention to the fact that it is claimed that compliance with this standard may involve the use of patents as follows, where the xx notation indicates the holder of the patent right: Type 8: DE 197 39 297 C2 PxC “Automatisierungssystem und St

18、euervorrichtung zur transparenten Kommunikation zwischen verschiedenen Netzwerken.“ US 2002/0042845 A1 PxC “Automation System and connecting Apparatus for the Transparent Communication between two Networks.“ IEC and CENELEC take no position concerning the evidence, validity and scope of these patent

19、 rights. The holders of these patent rights have assured IEC that they are willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holders of these patent rights are registered with IEC. In

20、formation may be obtained from: PxC: Phoenix Contact GmbH 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 co

21、ncerned, 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

22、61158-6-8:2008 7 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-8: Application layer protocol specification Type 8 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

23、, 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 8 fieldbus. The term

24、 “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, wi

25、th 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 8 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer proto

26、col 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 applicati

27、on 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-8,

28、 and 2) define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 8 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 Th

29、e 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-8. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is

30、 this latter objective which gives rise to the diversity of protocols standardized in the IEC 61158-6 series. 1.3 Conformance This standard does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation sy

31、stems. BS EN 61158-6-8:2008 8 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 u

32、ndated references, the latest edition of the referenced document (including any amendments) applies. IEC 60559, Binary floating-point arithmetic for microprocessor systems IEC 61158-3-8, Industrial communication networks Fieldbus specifications Part 3-8: Data-link layer service definition Type 8 ele

33、ments IEC 61158-4-8, Industrial communication networks Fieldbus specifications Part 4-8: Data-link layer protocol specification Type 8 elements IEC 61158-5-8, Industrial communication networks Fieldbus specifications Part 5-8: Application layer service definition Type 8 elements ISO/IEC 7498 (all pa

34、rts), Information technology Open Systems Interconnection Basic Reference 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) IS

35、O/IEC 8825, Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) ISO/IEC 9545, Information technology Open Systems Interconnection Application Layer structure 3 Terms and definitions For the pu

36、rposes of this document, the following terms, definitions, symbols, abbreviations and conventions apply. 3.1 ISO/IEC 7498-1 terms This standard is partly based on the concepts developed in ISO/IEC 7498-1, and makes use of the following terms defined therein: 3.2 application entity 3.3 application pr

37、ocess 3.4 application protocol data unit 3.5 application service element BS EN 61158-6-8:2008 9 3.6 application entity invocation 3.7 application transaction 3.8 transfer syntax 3.9 ISO/IEC 8822 terms For the purposes of this document, the following term as defined in ISO/IEC 8822 applies: 3.10 abst

38、ract syntax 3.11 ISO/IEC 9545 terms For the purposes of this document, the following terms as defined in ISO/IEC 9545 apply: 3.12 application-context 3.13 application-process-type 3.14 application-service-element 3.15 application control service element 3.16 ISO/IEC 8824 terms For the purposes of th

39、is document, the following terms as defined in ISO/IEC 8824 apply: 3.17 any type 3.18 bitstring type 3.19 Boolean type 3.20 choice type 3.21 component type 3.22 false 3.23 integer type 3.24 module 3.25 null type 3.26 object identifier 3.27 octetstring type BS EN 61158-6-8:2008 10 3.28 production 3.2

40、9 simple type 3.30 sequence of type 3.31 sequence type 3.32 structured type 3.33 tag 3.34 tagged type 3.35 true 3.36 type 3.37 ISO/IEC 8825 terms For the purposes of this document, the following terms as defined in ISO/IEC 8825 apply: 3.38 encoding (of a data value) 3.39 data value 3.40 Terms and de

41、finitions from IEC 61158-5-8 3.41 application relationship 3.42 client 3.43 error class 3.44 publisher 3.45 server 3.46 subscriber 3.47 Other terms and definitions The following terms and definitions are used in this standard. 3.48 called service user or a service provider that receives an indicatio

42、n primitive or a request APDU 3.49 calling service user or a service provider that initiates a request primitive or a request APDU BS EN 61158-6-8:2008 11 3.50 management information network accessible information that supports the management of the Fieldbus environment 3.51 receiving service user t

43、hat receives a confirmed primitive or an unconfirmed primitive, or a service provider that receives a confirmed APDU or an unconfirmed APDU 3.52 resource resource is a processing or information capability of a subsystem 3.53 sending service user that sends a confirmed primitive or an unconfirmed pri

44、mitive, or a service provider that sends a confirmed APDU or an unconfirmed APDU 4 FAL syntax description 4.1 FAL-AR PDU abstract syntax 4.1.1 Top level definition The productions defined here shall be used with the Peripherals Encoding Rules (see 5.2) for APDU encoding. APDU := CHOICE PRIVATE 0 Con

45、firmedSend-RequestPDU, PRIVATE 1 ConfirmedSend-ResponsePDU, PRIVATE 2 UnconfirmedSend-PDU, PRIVATE 3 UnconfirmedAcknowledgedSend-CommandPDU, PRIVATE 4 Establish-RequestPDU, PRIVATE 5 Establish-ResponsePDU, PRIVATE 6 Establish-ErrorPDU, PRIVATE 7 Abort-PDU, PRIVATE 8 DataSendAcknowledge-PDU 4.1.2 Con

46、firmed send service ConfirmedSend-RequestPDU := SEQUENCE APPLICATION 0 AddressAREP, InvokeID, ConfirmedServiceRequest ConfirmedSend-ResponsePDU := SEQUENCE APPLICATION 1 AddressAREP, InvokeID, pduBody CHOICE ConfirmedServiceResponse, ConfirmedServiceError 4.1.3 Unconfirmed send service UnconfirmedSe

47、nd-PDU := SEQUENCE APPLICATION 2 AddressAREP, InvokeID, pduBody CHOICE UnconfirmedServiceRequest, UnconfirmedSendPD-PDU BS EN 61158-6-8:2008 12 4.1.4 Unconfirmed acknowledge send service UnconfirmedAcknowledgeSend-CommandPDU := SEQUENCE APPLICATION 3 AddressAREP, InvokeID, UnconfirmedServiceRequest

48、4.1.5 Establish service Establish-RequestPDU := SEQUENCE APPLICATION 4 AddressAREP, ConType, MaxOSCC, MaxOSCS, MAXUCSC, MAXUCSS, CIU, InvokeID, initiateRequest PRIVATE 0 IMPLICIT Initiate-RequestPDU Establish-ResponsePDU := SEQUENCE APPLICATION 5 AddressAREP, InvokeID, initiateResponse PRIVATE 0 IMP

49、LICIT Initiate-ResponsePDU Establish-ErrorPDU := SEQUENCE APPLICATION 6 AddressAREP, InvokeID, initiateError PRIVATE 0 IMPLICIT Initiate-ErrorPDU 4.1.6 MaxOSCC MaxOSCC := Unsigned8 4.1.7 MaxOSCS MaxOSCS := Unsigned8 4.1.8 MaxUCSC MaxUCC := Unsigned8 4.1.9 MaxUCSS MaxUCS := Unsigned8 4.1.10 CIU CIU := Unsigned32 4.1.11 InvokeID InvokeID := Unsigned8 4.1.12 ConType ConType := ENUMERATED mmaz (0) BS