1、BRITISH STANDARDBS EN 61158-6-16:2008Industrial communication networks Fieldbus specifications Part 6-16: Application layer protocol specification Type 16 elementsICS 25.040.40; 35.100.70g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g
2、55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58BS EN 61158-6-16:2008This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 July 2008 BSI 2008ISBN 978 0 580 61637 2National forewordThis British Standard is t
3、he UK implementation of EN 61158-6-16:2008. It is identical with IEC 61158-6-16:2007. Together with all of the other sections of BS EN 61158-6, it supersedes BS EN 61158-6:2004 which is withdrawn. Together with BS EN 61158-2, BS EN 61158-3-16, BS EN 61158-4-16 and BS EN 61158-5-16, it partially supe
4、rsedes BS EN 61491:1999, which will be withdrawn upon publication of a revised edition currently in progress and which will be implemented as a Technical Report. The UK participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications Process measurement and cont
5、rol, 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. Compliance with a British Standard c
6、annot confer immunity from legal obligations. Amendments/corrigenda issued since publicationDate CommentsEUROPEAN STANDARD EN 61158-6-16 NORME EUROPENNE EUROPISCHE NORM March 2008 CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisc
7、hes 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-16:2008 E ICS 35.100.70; 25.040.40 Partially supersedes EN 61158-6:20
8、04 and EN 61491:1998English version Industrial communication networks - Fieldbus specifications - Part 6-16: Application layer protocol specification - Type 16 elements (IEC 61158-6-16:2007) Rseaux de communication industriels - Spcifications des bus de terrain - Partie 6-16: Spcification des servic
9、es des couches dapplication - Elments de type 16 (CEI 61158-6-16:2007) Industrielle Kommunikationsnetze - Feldbusse - Teil 6-16: Protokollspezifikation des Application Layer (Anwendungsschicht) - Typ 16-Elemente (IEC 61158-6-16:2007) This European Standard was approved by CENELEC on 2008-02-01. CENE
10、LEC 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 a
11、pplication 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 Secre
12、tariat 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
13、 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-16, prepared by SC 65C, Industrial networks, of IEC TC 65, Industrial-process measurement, control and a
14、utomation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61158-6-16 on 2008-02-01. This and the other parts of the EN 61158-6 series supersede EN 61158-6:2004. Together with EN 61158-2:2008 and its companion parts for Type 16, it also partially replaces EN 61491:19
15、98 which is at present being revised (to be issued as a Technical Report). 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 d
16、ates 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 a
17、ssociated 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 l
18、ayer 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 Inter
19、national Standard IEC 61158-6-16:2007 was approved by CENELEC as a European Standard without any modification. _ BS EN 61158-6-16:2008 2 CONTENTS INTRODUCTION.5 1 Scope.6 1.1 General .6 1.2 Specifications7 1.3 Conformance.7 2 Normative references .7 3 Terms, definitions, abbreviations, symbols and c
20、onventions .7 3.1 Referenced terms and definitions 7 3.2 Additional terms and definitions for Type 16 9 3.3 Additional abbreviations and symbols for Type 16 .10 3.4 Conventions 10 4 Abstract syntax.10 5 Transfer syntax.11 5.1 Introduction .11 5.2 RTC-MDT PDU merged abtract and transfer syntax.11 5.3
21、 RTC-AT PDU merged abtract and transfer syntax11 5.4 RTC-MDT PDU encoding.12 5.5 RTC-AT PDU encoding12 6 Structure of FAL protocol state machines .12 7 AP-Context state machine 14 7.1 Overview .14 7.2 States14 7.3 States, events and transitions14 8 FAL service protocol machine (FSPM) 15 8.1 Overview
22、 .15 8.2 MGT services 15 8.3 IDN services16 8.4 CYCIDN services.16 8.5 File transmission services .16 9 Application relationship protocol machine (ARPM)17 9.1 Overview .17 9.2 Master ARPM 17 9.3 Slave ARPM 18 9.4 Primitives received from the FSPM19 9.5 Indications received from the DMPM .21 10 DLL m
23、apping protocol machine (DMPM).22 10.1 Overview .22 10.2 Primitives received from the ARPM22 10.3 Indications received from the DL .22 Bibliography23 Annex ZA (normative) Normative references to international publications with their corresponding European publications 24 BS EN 61158-6-16:2008 3 Figu
24、re 4 ARPM slave AR state diagram .18 Table 1 RTC-MDT PDU attribute format .11 Table 2 RTC-AT PDU attribute format 11 Table 3 RTC-MDT PDU attribute encoding.12 Table 4 RTC-AT PDU attribute encoding12 Table 5 APCSM state-event table 15 Table 6 ARPM master state-event table .18 Table 7 ARPM slave state
25、-event table19 Table 8 ARPM to DL mapping 22 Table 9 DL to ARPM mapping 22 Figure 1 Relationships among protocol machines and adjacent layers .13 Figure 2 APCSM state diagram 14 Figure 3 ARPM master AR state diagram .17 BS EN 61158-6-16:2008 4 INTRODUCTION This part of IEC 61158 is one of a series p
26、roduced 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 availab
27、le 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 t
28、o 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 understandi
29、ng 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
30、 incompatible systems may work together in any combination. BS EN 61158-6-16:2008 5 INDUSTRIAL COMMUNICATION NETWORKS FIELDBUS SPECIFICATIONS Part 6-16: Application layer protocol specification Type 16 elements 1 Scope 1.1 General The fieldbus Application Layer (FAL) provides user programs with a me
31、ans 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 auto
32、mation environment and material specific to Type 16 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 ti
33、me window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This standard define in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of an abstract model for
34、defining application resources (objects) capable of being manipulated by users via the use of the FAL service, the primitive actions and events of the service; the parameters associated with each primitive action and event, and the form which they take; and the interrelationship between these action
35、s and events, and their valid sequences. The purpose of this standard is to define the services provided to the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and Systems Management at the boundary between the Application Layer and Systems Manage
36、ment of the Fieldbus Reference Model. This standard specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL appl
37、ication-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application proce
38、ss object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a
39、 specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in stan
40、dardizing BS EN 61158-6-16:2008 6 such object behavior. In addition to these services, some supporting services are also defined in this standard to provide access to the FAL to control certain aspects of its operation. 1.2 Specifications The principal objective of this standard is to specify the sy
41、ntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-16. 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 o
42、f protocols standardized in subparts of IEC 61158-6. 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 systems. There is no conformance of equipment to this appli
43、cation layer service definition standard. Instead, conformance is achieved through implementation of conforming application layer protocols that fulfill any given Type of application layer services as defined in this standard. 2 Normative references The following referenced documents are indispensab
44、le 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-4-16, Industrial communication networks Fieldbus specifications Part 4-16: Data-link laye
45、r protocol specification Type 16 elements IEC 61158-5-16, Industrial communication networks Fieldbus specifications Part 5-16: Application layer service definition Type 16 elements ISO/IEC 10731, Information technology Open Systems Interconnection Basic Reference Model Conventions for the definition
46、 of OSI services ISO/IEC 7498-1, Information technology Open Systems Interconnection Basic Reference Model Part 1: The Basic Model ISO/IEC 8822:1994, Information technology Open Systems Interconnection Presentation service definition ISO/IEC 8824, Information technology Open Systems Interconnection
47、Specification of Abstract Syntax Notation One (ASN.1) ISO/IEC 9545, Information technology Open Systems Interconnection Application Layer structure 3 Terms, definitions, abbreviations, symbols and conventions 3.1 Referenced terms and definitions 3.1.1 ISO/IEC 7498-1 terms For the purposes of this do
48、cument, the following terms as defined in ISO/IEC 7498-1 apply: d) application entity BS EN 61158-6-16:2008 7 e) application process f) application protocol data unit g) application service element h) application entity invocation i) application process invocation j) application transaction k) real
49、open system l) 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) applic
