SIST EN 61158-6-2:2012
(Main)Industrial communication networks - Fieldbus specifications - Part 600: Application layer protocol specification (IEC 61158-6-2:2010)
Industrial communication networks - Fieldbus specifications - Part 600: Application layer protocol specification (IEC 61158-6-2:2010)
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 2 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 2 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 a) define the wire-representation of the service primitives defined in IEC 61158-5-2:2010, and b) define the externally visible behavior associated with their transfer. This standard specifies the protocol of the Type 2 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).
Industrielle Kommunikationsnetze - Feldbusse - Teil 600: Protokollspezifikation des Application Layer (Anwendungsschicht) (IEC 61158-6-2:2010)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-2: Spécification des protocoles des couches d'application - Eléments de type 2 (CEI 61158-6-2:2010)
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 600. del: Specifikacija protokola aplikacijskega nivoja (IEC 61158-6-2:2010)
Aplikacijski nivo procesnih vodil (FAL) omogoča uporabniškim programom dostop do komunikacijskega okolja procesnih vodil. Glede na to je mogoče aplikacijski nivo procesnih vodil šteti za »okno med ustreznimi aplikacijami«. Ta standard določa skupne elemente za osnovne časovno kritične in časovno nekritične sporočilne komunikacije med aplikacijami v avtomatizacijskem okolju in material, specifičen za procesna vodila tipa 2. Izraz »časovno kritičen« se uporablja za predstavitev prisotnosti časovnega okna, v okviru katerega se zahteva dokončanje enega ali več opredeljenih dejanj z določeno stopnjo gotovosti. Zaradi neuspešnega dokončanja opredeljenih dejanj v časovnem oknu je možna odpoved aplikacij, ki zahtevajo dejanja, pri čemer so ogroženi oprema, obrat in morda človeška življenja. Ta standard opredeljuje interakcije med oddaljenimi aplikacijami in določa zunanje vidno vedenje, ki ga zagotavlja aplikacijski nivo procesnih vodil tipa 2 v zvezi z a) formalno abstraktno sintakso, ki opredeljuje podatkovne enote protokola aplikacijskega nivoja, ki se prenašajo med aplikacijskimi osebki, ki komunicirajo, b) prenosno sintakso, ki opredeljuje pravila kodiranja, ki se uporabljajo za podatkovne enote protokola aplikacijskega nivoja, c) strojem stanj aplikacijskega konteksta, ki opredeljuje vedenje aplikacijskega opravila, vidnega med aplikacijskimi osebki, ki komunicirajo, in d) stroji stanj aplikacijskega razmerja, ki opredeljujejo komunikacijsko vedenje med aplikacijskimi osebki, ki komunicirajo. Namen tega standarda je opredeliti protokol za a) določitev žične predstavitve primitivov opravil iz standarda IEC 61158-5-2:2010 in b) določitev zunanje vidnega vedenja, povezanega z njihovim prenosom. Ta standard določa protokol aplikacijskega nivoja procesnih vodil tipa 2 v skladu z osnovnim referenčnim modelom OSI (ISO/IEC 7498-1) in strukturo aplikacijskega nivoja OSI (ISO/IEC 9545).
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 61158-6-2:2012
01-september-2012
1DGRPHãþD
SIST EN 61158-6-2:2008
Industrijska komunikacijska omrežja - Specifikacije za procesna vodila - 600. del:
Specifikacija protokola aplikacijskega nivoja (IEC 61158-6-2:2010)
Industrial communication networks - Fieldbus specifications - Part 600: Application layer
protocol specification (IEC 61158-6-2:2010)
Industrielle Kommunikationsnetze - Feldbusse - Teil 600: Protokollspezifikation des
Application Layer (Anwendungsschicht) (IEC 61158-6-2:2010)
Réseaux de communication industriels - Spécifications des bus de terrain - Partie 6-2:
Spécification des protocoles des couches d'application - Eléments de type 2 (CEI 61158-
6-2:2010)
Ta slovenski standard je istoveten z: EN 61158-6-2:2012
ICS:
25.040.40 Merjenje in krmiljenje Industrial process
industrijskih postopkov measurement and control
35.100.70 Uporabniški sloj Application layer
35.110 Omreževanje Networking
SIST EN 61158-6-2:2012 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 61158-6-2:2012
---------------------- Page: 2 ----------------------
SIST EN 61158-6-2:2012
EUROPEAN STANDARD
EN 61158-6-2
NORME EUROPÉENNE
June 2012
EUROPÄISCHE NORM
ICS 25.040.40; 35.100.70; 35.110 Supersedes EN 61158-6-2:2008
English version
Industrial communication networks -
Fieldbus specifications -
Part 6-2: Application layer protocol specification -
Type 2 elements
(IEC 61158-6-2:2010)
Réseaux de communication industriels - Industrielle Kommunikationsnetze -
Spécifications des bus de terrain - Feldbusse -
Partie 6-2: Spécification des protocoles Teil 6-2: Protokollspezifikation des
des couches d'application - Application Layer (Anwendungsschicht) -
Eléments de type 2 Typ 2-Elemente
(CEI 61158-6-2:2010) (IEC 61158-6-2:2010)
This European Standard was approved by CENELEC on 2012-03-28. 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 CEN-CENELEC Management Centre 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 CEN-CENELEC Management Centre has the same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, 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, Turkey and the United Kingdom.
CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung
Management Centre: Avenue Marnix 17, B - 1000 Brussels
© 2012 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61158-6-2:2012 E
---------------------- Page: 3 ----------------------
SIST EN 61158-6-2:2012
EN 61158-6-2:2012 - 2 -
Foreword
The text of document 65C/607/FDIS, future edition 2 of IEC 61158-6-2, 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 approved by CENELEC as EN 61158-6-2:2012.
The following dates are fixed:
(dop) 2012-12-28
• latest date by which the document has
to be implemented at national level by
publication of an identical national
standard or by endorsement
• latest date by which the national (dow) 2015-03-28
standards conflicting with the
document have to be withdrawn
This document supersedes EN 61158-6-2:2008.
EN 61158-6-2:2012 includes the following significant technical changes with respect to EN 61158-6-
2:2008:
– Clause 2 and Bibliography: update of normative and bibliographic references;
– 3.4: update of abbreviations;
– 4.1.2.1: update list of service request/response PDUs (Time Sync and Parameter ASEs/objects);
– 4.1.8.6: update of Time Sync ASE/object;
– new 4.1.8.7: new Parameter ASE/object;
– 4.1.9.4: minor update of a common parameter;
– 4.1.10.2: update/add object and services codes for Time Sync and Parameter ASEs;
– 4.1.11: minor updates of error codes;
– new 11.7: new QoS specification.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent
rights.
Endorsement notice
The text of the International Standard IEC 61158-6-2:2010 was approved by CENELEC as a European
Standard without any modification.
In the official version, for Bibliography, the following notes have to be added for the standards indicated:
IEC 61131-3 NOTE Harmonized as EN 61131-3.
IEC/TR 61158-1:2010 NOTE Harmonized as CLC/TR 61158-1:2010 (not modified).
---------------------- Page: 4 ----------------------
SIST EN 61158-6-2:2012
- 3 - EN 61158-6-2:2012
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year
IEC 61158-3-2 2007 Industrial communication networks - Fieldbus EN 61158-3-2 2008
specifications -
Part 3-2: Data-link layer service definition -
Type 2 elements
IEC 61158-4-2 2010 Industrial communication networks - Fieldbus EN 61158-4-2 2012
specifications -
Part 4-2: Data-link layer protocol specification
- Type 2 elements
IEC 61158-5-2 2010 Industrial communication networks - Fieldbus EN 61158-5-2 2012
specifications -
Part 5-2: Application layer service definition -
Type 2 elements
IEC 61588 2009 Precision clock synchronization protocol for - -
networked measurement and control systems
IEC 61784-3-2 - Industrial communication networks - Profiles - EN 61784-3-2 -
Part 3-2: Functional safety fieldbuses -
Additional specifications for CPF 2
IEC 62026-3 2008 Low-voltage switchgear and controlgear - EN 62026-3 2009
Controller-device interfaces (CDIs) -
Part 3: DeviceNet
ISO/IEC 7498-1 - Information technology - Open Systems - -
Interconnection - Basic Reference Model: The
Basic Model
ISO/IEC 8802-3 - Information technology - Telecommunications - -
and information exchange between systems -
Local and metropolitan area networks -
Specific requirements -
Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method
and physical layer specifications
ISO/IEC 8824 Series Information technology - Abstract Syntax - -
Notation One (ASN.1)
ISO/IEC 8825-1 - 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
ISO/IEC 10646 - Information technology - Universal multiple-- -
octet coded character set (UCS)
---------------------- Page: 5 ----------------------
SIST EN 61158-6-2:2012
EN 61158-6-2:2012 - 4 -
Publication Year Title EN/HD Year
ISO/IEC 10731 - Information technology - Open Systems - -
Interconnection - Basic reference model -
Conventions for the definition of OSI services
ISO 11898 1993 Road vehicles - Interchange of digital - -
information - Controller area network (CAN)
for high-speed communication
IEEE 802.1Q - IEEE Standard for Local and Metropolitan - -
Area Networks - Virtual Bridged Local Area
Networks
IEEE 802.1D - IEEE Standard for Local and Metropoitan - -
Area Networks - Media Access Control (MAC)
Bridges
IETF RFC 791 - Internet Protocol - DARPA Internet Program - -
Protocol Specification
IETF RFC 1122 - Requirements for Internet Hosts - - -
Communication Layers
IETF RFC 2475 - An architecture for differentiated services - -
IETF RFC 1759 - Printer MIB - -
IETF RFC 1035 - Domain Names - Implementation and - -
Specification
---------------------- Page: 6 ----------------------
SIST EN 61158-6-2:2012
IEC 61158-6-2
®
Edition 2.0 2010-08
INTERNATIONAL
STANDARD
Industrial communication networks – Fieldbus specifications –
Part 6-2: Application layer protocol specification – Type 2 elements
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XL
ICS 25.04.40; 35.100.70; 35.110 ISBN 978-2-88912-118-2
® Registered trademark of the International Electrotechnical Commission
---------------------- Page: 7 ----------------------
SIST EN 61158-6-2:2012
– 2 – 61158-6-2 © IEC:2010(E)
CONTENTS
FOREWORD.12
INTRODUCTION.14
1 Scope.15
1.1 General .15
1.2 Specifications.15
1.3 Conformance.16
2 Normative references .16
3 Terms, definitions, symbols, abbreviations and conventions .17
3.1 Terms and definitions from other ISO/IEC standards .17
3.2 Terms and definitions from IEC 61158-5-2.18
3.3 Additional terms and definitions.18
3.4 Abbreviations and symbols.24
3.5 Conventions .24
3.6 Conventions used in state machines .29
4 Abstract syntax.30
4.1 FAL PDU abstract syntax .30
4.2 Data abstract syntax specification .120
4.3 Encapsulation abstract syntax .124
5 Transfer syntax .138
5.1 Compact encoding.138
5.2 Data type reporting.145
6 Structure of FAL protocol state machines .150
7 AP-Context state machine .150
7.1 Overview .150
7.2 Connection object state machine.150
8 FAL service protocol machine (FSPM).160
8.1 General .160
8.2 Primitive definitions .160
8.3 Parameters of primitives.164
8.4 FSPM state machines.165
9 Application relationship protocol machines (ARPMs) . 166
9.1 General .166
9.2 Connection-less ARPM (UCMM).166
9.3 Connection-oriented ARPMs (transports).176
10 DLL mapping protocol machine 1 (DMPM 1) .247
10.1 General .247
10.2 Link producer .247
10.3 Link consumer.248
10.4 Primitive definitions .248
10.5 DMPM state machine .250
10.6 Data-link Layer service selection .251
11 DLL mapping protocol machine 2 (DMPM 2) .251
11.1 General .251
11.2 Mapping of UCMM PDUs.252
11.3 Mapping of transport class 0 and class 1 PDUs .257
---------------------- Page: 8 ----------------------
SIST EN 61158-6-2:2012
61158-6-2 © IEC:2010(E) – 3 –
11.4 Mapping of transport class 2 and class 3 PDU’s .258
11.5 Mapping of transport classes 4 to 6 .258
11.6 IGMP Usage.258
11.7 Quality of Service (QoS) for CP 2/2 messages .259
11.8 Management of an encapsulation session . 262
12 DLL mapping protocol machine 3 (DMPM 3) .263
Bibliography.264
Figure 1 – Attribute table format and terms .25
Figure 2 – Service request/response parameter.25
Figure 3 – Example of an STD .29
Figure 4 – Network connection parameters .49
Figure 5 – Time tick .51
Figure 6 – Connection establishment time-out .53
Figure 7 – Transport Class Trigger attribute.86
Figure 8 – CP2/3_initial_comm_characteristics attribute format .89
Figure 9 – Segment type.97
Figure 10 – Port segment.98
Figure 11 – Logical segment encoding.100
Figure 12 – Extended network segment .104
Figure 13 – Encapsulation message .124
Figure 14 – FixedLengthBitString compact encoding bit placement rules . 142
Figure 15 – Example compact encoding of a SWORD FixedLengthBitString.142
Figure 16 – Example compact encoding of a WORD FixedLengthBitString.142
Figure 17 – Example compact encoding of a DWORD FixedLengthBitString .143
Figure 18 – Example compact encoding of a LWORD FixedLengthBitString .143
Figure 19 – Example 2 of formal encoding of a structure type specification. 147
Figure 20 – Example of abbreviated encoding of a structure type specification . 148
Figure 21 – Example 1 of formal encoding of an array type specification . 148
Figure 22 – Example 2 of formal encoding of an array type specification . 149
Figure 23 – Example 1 of abbreviated encoding of an array type specification .149
Figure 24 – Example 2 of abbreviated encoding of an array type specification .150
Figure 25 – I/O Connection object state transition diagram . 151
Figure 26 –Bridged Connection object state transition diagram .155
Figure 27 – Explicit Messaging Connection object state transition diagram . 157
Figure 28 – State transition diagram of UCMM client . 169
Figure 29 – State transition diagram of high–end UCMM server. 170
Figure 30 – State transition diagram of low–end UCMM server . 172
Figure 31 – Sequence diagram for a UCMM with one outstanding message.174
Figure 32 – Sequence diagram for a UCMM with multiple outstanding messages.175
Figure 33 – TPDU buffer .176
Figure 34 – Data flow diagram using a client transport class 0 and server transport
class 0 .179
Figure 35 – Sequence diagram of data transfer using transport class 0. 179
---------------------- Page: 9 ----------------------
SIST EN 61158-6-2:2012
– 4 – 61158-6-2 © IEC:2010(E)
Figure 36 – Class 0 client STD .180
Figure 37 – Class 0 server STD .181
Figure 38 – Data flow diagram using client transport class 1 and server transport
class 1 .182
Figure 39 – Sequence diagram of data transfer using client transport class 1 and
server transport class 1 .183
Figure 40 – Class 1 client STD .185
Figure 41 – Class 1 server STD .186
Figure 42 – Data flow diagram using client transport class 2 and server transport
class 2 .188
Figure 43 – Diagram of data transfer using client transport class 2 and server transport
class 2 without returned data .189
Figure 44 – Sequence diagram of data transfer using client transport class 2 and
server transport class 2 with returned data .190
Figure 45 – Class 2 client STD .191
Figure 46 – Class 2 server STD .193
Figure 47 – Data flow diagram using client transport class 3 and server transport
class 3 .196
Figure 48 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 without returned data.197
Figure 49 – Sequence diagram of data transfer using client transport class 3 and
server transport class 3 with returned data .198
Figure 50 – Class 3 client STD .200
Figure 51 – Class 3 server STD .203
Figure 52 – Data flow diagram using transport classes 4 and 5.205
Figure 53 – Sequence diagram of message exchange using transport classes 4 and 5 . 206
Figure 54 – Sequence diagram of messages overwriting each other .207
Figure 55 – Sequence diagram of queued message exchange using transport classes
4 and 5 .208
Figure 56 – Sequence diagram of retries using transport classes 4 and 5 . 208
Figure 57 – Sequence diagram of idle traffic using transport classes 4 and 5. 209
Figure 58 – Classes 4 and 5 basic structure .210
Figure 59 – Class 6 basic structure.211
Figure 60 – Classes 4 to 6 general STD.212
Figure 61 – Class 4 sender STD .214
Figure 62 – Class 4 receiver STD .217
Figure 63 – Sequence diagram of three fragments using transport class 5. 220
Figure 64 – Sequence diagram of fragmentation with retries using transport class 5. 221
Figure 65 – Sequence diagram of two fragments using transport class 5 . 221
Figure 66 – Sequence diagram of aborted message using transport class 5 . 222
Figure 67 – Class 5 sender STD .223
Figure 68 – Class 5 receiver STD .226
Figure 69 – Data flow diagram for transport class 6 .231
Figure 70 – Sequence diagram of message exchange using transport class 6 . 233
Figure 71 – Sequence diagram of retries using transport class 6 . 233
Figure 72 – Sequence diagram of idle traffic using transport class 6 . 234
---------------------- Page: 10 ----------------------
SIST EN 61158-6-2:2012
61158-6-2 © IEC:2010(E) – 5 –
Figure 73 – Sequence diagram of request overwriting null .235
Figure 74 – Sequence diagram of response overwriting ACK of null. 235
Figure 75 – Sequence diagram of three fragments using transport class 6. 236
Figure 76 – Sequence diagram of fragmentation with retries using transport class 6. 237
Figure 77 – Sequence diagram of two fragments using transport class 6 . 237
Figure 78 – Sequence diagram of aborted fragmented sequence using transport
class 6 .238
Figure 79 – Class 6 client STD .239
Figure 80 – Class 6 server STD .242
Figure 81 – Data flow diagram for a link producer and consumer . 247
Figure 82 – State transition diagram for a link producer . 250
Figure 83 – State transition diagram for a link consumer. 251
Figure 84 – DS field in the IP header .261
Figure 85 – IEEE 802.1Q tagged frame.261
Table 1 – Get_Attribute_All response service rules .26
Table 2 – Example class level object/service specific response data of
Get_Attribute_All .26
Table 3 – Example Get_Attribute_All data array method .27
Table 4 – Set_Attribute_All request service rules .28
Table 5 – Example Set_Attribute_All attribute ordering method.28
Table 6 – Example Set_Attribute_All data array method.28
Table 7 – State event matrix format .30
Table 8 – Example state event matrix .30
Table 9 – UCMM_PDU header format .33
Table 10 – UCMM command codes.33
Table 11 – Transport class 0 header.34
Table 12 – Transport class 1 header.35
Table 13 – Transport class 2 header.35
Table 14 – Transport class 3 header.35
Table 15 – Classes 4 to 6 header format.35
Table 16 – Real-time data header – exclusive owner .36
Table 17 – Real-time data header– redundant owner .37
Table 18 – Forward_Open request format .39
Table 19 – Forward_Open_Good response format .40
Table 20 – Forward_Open_Bad response format .40
Table 21 – Large_Forward_Open request format .41
Table 22 – Large_Forward_Open_Good response format .42
Table 23 – Large_Forward_Open_Bad response format.42
Table 24 – Forward_Close request format .43
Table 25 – Forward_Close_Good response format.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.