1、BRITISH STANDARDBS EN 61158-6-17:2008Industrial communication networks Fieldbus specifications Part 6-17: Application layer protocol specification Type 17 elementsICS 25.040.40; 35.100.70g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g
2、55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-6-17:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2008 BSI 2008ISBN 978 0 580 61638 9National forewordThis British Standard is t
3、he UK implementation of EN 61158-6-17:2008. It is identical with IEC 61158-6-17: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 communic
4、ations 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 provisions of a contract. Users are responsible for its correct application. C
5、ompliance with a British Standard cannot confer immunity from legal obligations. Amendments/corrigenda issued since publicationDate CommentsEUROPEAN STANDARD EN 61158-6-17 NORME EUROPENNE EUROPISCHE NORM March 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Norm
6、alisation Electrotechnique 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-17:2008 E ICS 35.100.70; 25.040.40
7、 Partially supersedes EN 61158-6:2004English version Industrial communication networks - Fieldbus specifications - Part 6-17: Application layer protocol specification - Type 17 elements (IEC 61158-6-17:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 6-17: Spcifi
8、cation des services des couches dapplication - Elments de type 17 (CEI 61158-6-17:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-17: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 17-Elemente (IEC 61158-6-17:2007) This European Standard was approved by CENELEC on
9、 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
10、 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
11、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, Luxem
12、bourg, 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-17, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measureme
13、nt, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-17 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 fiel
14、dbus 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-
15、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-right
16、s 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
17、from their respective 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 17: PCT Application No. PCT/JP20
18、04/011537 YEC Communication control method PCT Application No. PCT/JP2004/011538 YEC Communication control method IEC and CENELEC take no position concerning the evidence, validity and scope of these patent rights. The holders of these patent rights have assured IEC that they are willing to negotiat
19、e 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. Information may be obtained from: YEC: Yokogawa Electric Corporation 2-9-32 Nakacho, Musashino-s
20、hi, 180-8750 Tokyo, Japan Attention: Intellectual Property 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 c
21、oncerned, 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-17:2008 6 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-17: Application layer protocol specification Type 17 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 res
23、pect, 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 17 fieldbus. The
24、 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 action
25、s, 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 17 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer
26、 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 app
27、lication 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 6115
28、8-5-17, and 2) define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 17 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 Specifica
29、tions 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-17. A secondary objective is to provide migration paths from previously-existing industrial communications protoco
30、ls. It is 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 auto
31、mation systems. BS EN 61158-6-17:2008 7 Conformance is achieved through implementation of this application layer protocol specification. 2 Normative reference The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited appli
32、es. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61158-5-17, Industrial communication networks Fieldbus specifications - Part 5-17: Application layer service definition Type 17 elements ISO/IEC 7498 (all parts), Information technology
33、Open Systems Interconnection Basic Reference Model ISO/IEC 8824-2, Information technology Abstract Syntax Notation One (ASN.1): Information object specification ISO/IEC 8825-1, Information technology ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) an
34、d Distinguished Encoding Rules (DER) ISO/IEC 9545, Information technology Open Systems Interconnection Application Layer structure ISO/IEC 10731, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition of OSI services 3 Definitions For the purposes of
35、 this document, the following terms and definitions apply. 3.1 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: d) application entity e) application protocol data unit f) application service element 3.1.2 ISO/
36、IEC 8824-2 terms For the purposes of this document, the following terms as defined in ISO/IEC 8824 apply: a) any type b) bitstring type c) Boolean type d) choice type e) false f) integer type g) null type h) octetstring type BS EN 61158-6-17:2008 8 i) sequence of type j) sequence type k) simple type
37、 l) structured type m) tagged type n) true o) type p) value 3.1.3 ISO/IEC 10731 terms a) (N)-connection b) (N)-entity c) (N)-layer d) (N)-service e) (N)-service-access-point f) confirm (primitive) g) indication (primitive) h) request (primitive) i) response (primitive) 3.1.4 Other terms and definiti
38、ons 3.1.4.1 application function or data structure for which data is consumed or produced 3.1.4.2 application process part of a distributed application on a network, which is located on one device and unambiguously addressed 3.1.4.3 application relationship cooperative association between two or mor
39、e application-entity-invocations for the purpose of exchange of information and coordination of their joint operation NOTE This relationship is activated either by the exchange of application-protocol-data-units or as a result of preconfiguration activities 3.1.5 application relationship application
40、 service element application-service-element that provides the exclusive means for establishing and terminating all application relationships 3.1.5.1 application relationship endpoint context and behavior of an application relationship as seen and maintained by one of the application processes invol
41、ved in the application relationship NOTE Each application process involved in the application relationship maintains its own application relationship endpoint. 3.1.5.2 attribute description of an externally visible characteristic or feature of an object BS EN 61158-6-17:2008 9 NOTE The attributes of
42、 an object contain information about variable portions of an object. Typically, they provide status information or govern the operation of an object. Attributes may also affect the behaviour of an object. Attributes are divided into class attributes and instance attributes. 3.1.5.3 behaviour indicat
43、ion of how an object responds to particular eventss 3.1.5.4 bridge intermediate equipment that connects two or more segments using a data-link layer relay function 3.1.5.5 channel single physical or logical link of an input or output application object of a server to the process 3.1.5.6 class a set
44、of objects, all of which represent the same kind of system component NOTE A class is a generalisation of an object; a template for defining variables and methods. All objects in a class are identical in form and behaviour, but usually contain different data in their attributes. 3.1.5.7 client a) obj
45、ect which uses the services of another (server) object to perform a task b) initiator of a message to which a server reacts 3.1.5.8 connection logical binding between application objects that may be within the same or different devices NOTE 1 Connections may be either point-to-point or multipoint. N
46、OTE 2 The logical link between sink and source of attributes and services at different custom interfaces of RT-Auto ASEs is referred to as interconnection. There is a distinction between data and event interconnections. The logical link and the data flow between sink and source of automation data it
47、ems is referred to as data interconnection. The logical link and the data flow between sink (method) and source (event) of operational services is referred to as event interconnection. 3.1.5.9 connection point buffer which is represented as a subinstance of an Assembly object 3.1.5.10 conveyance pat
48、h unidirectional flow of APDUs across an application relationship 3.1.5.11 dedicated AR AR used directly by the FAL User NOTE On Dedicated ARs, only the FAL Header and the user data are transferred. 3.1.5.12 device physical hardware connected to the link NOTE A device may contain more than one node.
49、 3.1.5.13 domain part of the RTE network consisting of one or two subnetwork(s) BS EN 61158-6-17:2008 10 NOTE Two subnetworks are required to compose a dual-redundant RTE network, and each end node in the domain is connected to both of the subnetworks. 3.1.5.14 domain master station which performs diagnosis of routes to all other domains, distribution of network time to nodes inside the domain, acquisition of absolute time from the network time master and notification of status of the domain 3.1.5.15 do
