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

the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities;
the transfer syntax defining encoding rules that are applied to the application layer protocol data units;
the application context state machine defining the application service behavior visible between communicating application entities;
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

define the wire-representation of the service primitives defined in IEC 61158-5-2, and
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).

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-2.

A secondary objective is to provide migration paths from previously-existing industrial communications protocols.

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. Conformance is achieved through implementation of this application layer protocol specification.

PDF Catalog

PDF Pages	PDF Title
4	Foreword Endorsement notice
5	Annex ZA (normative) Normative references to international publications with their corresponding European publications
8	English CONTENTS
18	INTRODUCTION
19	1 Scope 1.1 General 1.2 Specifications
20	1.3 Conformance 2 Normative references
22	3 Terms, definitions, symbols, abbreviations and conventions 3.1 Terms and definitions from other ISO/IEC standards
23	3.2 Terms and definitions from IEC 6115852 3.3 Additional terms and definitions
30	3.4 Abbreviations and symbols
31	3.5 Conventions Figures Figure 1 – Attribute table format and terms
32	Figure 2 – Service request/response parameter Tables Table 1 – Get_Attribute_All response service rules
33	Table 2 – Example class level object/service specific response data of Get_Attribute_All Table 3 – Example Get_Attribute_All data array method
34	Table 4 – Set_Attribute_All request service rules Table 5 – Example Set_Attribute_All attribute ordering method Table 6 – Example Set_Attribute_All data array method
35	Figure 3 – Example of an STD
36	4 Abstract syntax 4.1 FAL PDU abstract syntax Table 7 – State event matrix format Table 8 – Example state event matrix
40	Table 9 – UCMM_PDU header format Table 10 – UCMM command codes
41	Table 11 – Transport class 0 header Table 12 – Transport class 1 header Table 13 – Transport class 2 header Table 14 – Transport class 3 header
42	Table 15 – Real-time data header – exclusive owner Table 16 – Real-time data header– redundant owner
46	Table 17 – Forward_Open request format
47	Table 18 – Forward_Open_Good response format
48	Table 19 – Forward_Open_Bad response format Table 20 – Large_Forward_Open request format
49	Table 21 – Large_Forward_Open_Good response format
50	Table 22 – Large_Forward_Open_Bad response format Table 23 – Forward_Close request format
51	Table 24 – Forward_Close_Good response format Table 25 – Forward_Close_Bad response format
52	Table 26 – Unconnected_Send request format
53	Table 27 – Unconnected_Send_Good response format Table 28 – Unconnected_Send_Bad response format
54	Table 29 – Unconnected_Send request format (modified)
55	Table 30 – Unconnected_Send_Good response format (modified) Table 31 – Unconnected_Send_Bad response format (modified)
56	Table 32 – Get_Connection_Data request format Table 33 – Get_Connection_Data response format
57	Table 34 – Search_Connection_Data request format Table 35 – Get_Connection_Owner request format Table 36 – Get_Connection_Owner response format
58	Figure 4 – Network connection parameters
61	Figure 5 – Time tick Table 37 – Time-out multiplier Table 38 – Time tick units
63	Figure 6 – Connection establishment time-out
66	Table 39 – Encoded application path ordering
67	Table 40 – Transport class, trigger and Is_Server format Table 41 – MR_Request_Header format
68	Table 42 – MR_Response_Header format Table 43 – Structure of Get_Attribute_All_ResponsePDU body
69	Table 44 – Structure of Set_Attribute_All_RequestPDU body Table 45 – Structure of Get_Attribute_List_RequestPDU body Table 46 – Structure of Get_Attribute_List_ResponsePDU body Table 47 – Structure of Set_Attribute_List_RequestPDU body Table 48 – Structure of Set_Attribute_List_ResponsePDU body
70	Table 49 – Structure of Reset_RequestPDU body Table 50 – Structure of Reset_ResponsePDU body Table 51 – Structure of Start_RequestPDU body Table 52 – Structure of Start_ResponsePDU body Table 53 – Structure of Stop_RequestPDU body
71	Table 54 – Structure of Stop_ResponsePDU body Table 55 – Structure of Create_RequestPDU body Table 56 – Structure of Create_ResponsePDU body Table 57 – Structure of Delete_RequestPDU body Table 58 – Structure of Delete_ResponsePDU body
72	Table 59 – Structure of Get_Attribute_Single_ResponsePDU body Table 60 – Structure of Set_Attribute_Single_RequestPDU body Table 61 – Structure of Set_Attribute_Single_ResponsePDU body Table 62 – Structure of Find_Next_Object_Instance_RequestPDU body Table 63 – Structure of Find_Next_Object_Instance_ResponsePDU body
73	Table 64 – Structure of Apply_Attributes_RequestPDU body Table 65 – Structure of Apply_Attributes_ResponsePDU body Table 66 – Structure of Save_RequestPDU body Table 67 – Structure of Save_ResponsePDU body Table 68 – Structure of Restore_RequestPDU body
74	Table 69 – Structure of Restore_ResponsePDU body Table 70 – Structure of Get_Member_ResponsePDU body Table 71 – Structure of Set_Member_RequestPDU body Table 72 – Structure of Set_Member_ResponsePDU body Table 73 – Structure of Insert_Member_RequestPDU body
75	Figure 7 – Member ID/EX description (WORD) Table 74 – Structure of Insert_Member_ResponsePDU body Table 75 – Structure of Remove_Member_ResponsePDU body
76	Table 76 – Common structure of _Member_RequestPDU body (basic format) Table 77 – Common structure of _Member_ResponsePDU body (basic format) Table 78 – Common structure of _Member_RequestPDU body (extended format)
77	Table 79 – Common structure of _Member_ResponsePDU body (extended format) Table 80 – Extended Protocol ID Table 81 – Structure of _Member_RequestPDU body (Multiple Sequential Members)
78	Table 82 – Structure of _Member_ResponsePDU body (Multiple Sequential Members) Table 83 – Structure of _Member_RequestPDU body (International String Selection) Table 84 – Structure of _Member_ResponsePDU body (International String Selection)
79	Table 85 – Structure of Group_Sync_RequestPDU body Table 86 – Structure of Group_Sync_ResponsePDU body Table 87 – Identity object class attributes Table 88 – Identity object instance attributes
81	Table 89 – Identity object bit definitions for status instance attribute Table 90 – Default values for extended device status field (bits 4 to 7) of status instance attribute Table 91 – Class level object/service specific response data of Get_Attribute_All
82	Table 92 – Instance level object/service specific response data of Get_Attribute_All Table 93 – Object-specific parameter for Reset Table 94 – Reset service parameter values
83	Table 95 – Message Router object class attributes Table 96 – Message Router object instance attributes Table 97 – Class level object/service specific response data of Get_Attribute_All
84	Table 98 – Instance level object/service specific response data of Get_Attribute_All Table 99 – Structure of Symbolic_Translation_RequestPDU body Table 100 – Structure of Symbolic_Translation_ResponsePDU body Table 101 – Object specific status for Symbolic_Translation service
85	Table 102 – Assembly object class attributes Table 103 – Assembly object instance attributes Table 104 – Assembly Instance ID ranges
86	Table 105 – Acknowledge Handler object class attributes
87	Table 106 – Acknowledge Handler object instance attributes Table 107 – Structure of Add_AckData_Path_RequestPDU body Table 108 – Structure of Remove_AckData_Path_RequestPDU body
88	Table 109 – Time Sync object class attributes Table 110 – Time Sync object instance attributes
91	Table 111 – ClockIdentity encoding for different network implementations
92	Table 112 – ClockClass values Table 113 – TimeAccuracy values
93	Table 114 – TimePropertyFlags bit values Table 115 – TimeSource values Table 116 – Types of Clock Table 117 – Network protocol to PortPhysicalAddressInfo mapping
94	Table 118 – Parameter object class attributes Table 119 – Parameter Class Descriptor bit values
95	Table 120 – Parameter object instance attributes
96	Table 121 – Semantics of Descriptor Instance attribute Table 122 – Minimum and Maximum Value semantics
97	Table 123 – Scaling Formula attributes
98	Table 124 – Scaling links
99	Table 125 – Class level object/service specific response data of Get_Attribute_All Table 126 – Instance level object/service specific response data of Get_Attribute_All (Parameter object stub)
100	Table 127 – Instance level object/service specific response data of Get_Attribute_All (full Parameter object)
101	Table 128 – Structure of Get_Enum_String_RequestPDU body Table 129 – Structure of Get_Enum_String_ResponsePDU body Table 130 – Enumerated strings Type versus Parameter data type
102	Table 131 – Connection Manager object class attributes Table 132 – Connection Manager object instance attributes
103	Table 133 – Class level object/service specific response data of Get_Attribute_All Table 134 – Instance level object/service specific response data of Get_Attribute_All
104	Table 135 – Instance level object/service specific request data of Set_Attribute_All
105	Table 136 – Connection object class attributes Table 137 – Connection object instance attributes
106	Table 138 – Values assigned to the state attribute
107	Figure 8 – Transport Class Trigger attribute Table 139 – Values assigned to the instance_type attribute
108	Table 140 – Possible values within Direction Bit Table 141 – Possible values within Production Trigger Bits
109	Table 142 – Possible values within Transport Class Bits Table 143 – TransportClass_Trigger attribute values summary
110	Table 144 – Transport Class 0 client behavior summary Table 145 – Transport Class 1, 2 and 3 client behavior summary Table 146 – Values defined for the CP2/3_produced_connection_id attribute
111	Figure 9 – CP2/3_initial_comm_characteristics attribute format Table 147 – Values defined for the CP2/3_consumed_connection_id attribute
112	Table 148 – Values for the Initial Production Characteristics nibble
113	Table 149 – Values for the Initial Consumption Characteristics nibble
116	Table 150 – Values for the watchdog_timeout_action
118	Table 151 – Structure of Connection_Bind_RequestPDU body Table 152 – Object specific status for Connection_Bind service Table 153 – Structure of Producing_Application_Lookup_RequestPDU body Table 154 – Structure of Producing_Application_Lookup_ResponsePDU body
119	Table 155 – Producing_Application_Lookup Service status codes
120	Figure 10 – Segment type
121	Figure 11 – Port segment Table 156 – Possible port segment examples
122	Table 157 – TCP/IP link address examples
123	Figure 12 – Logical segment encoding Table 158 – Extended Logical Type
125	Table 159 – Electronic key segment format
126	Table 160 – Logical segments examples Table 161 – Network segments
128	Figure 13 – Extended network segment Table 162 – Extended subtype definitions
129	Figure 14 – Symbolic segment encoding Table 163 – Symbolic segment examples
130	Table 164 – Data segment Table 165 – ANSI_Extended_Symbol segment
133	Table 166 – Addressing categories Table 167 – Class code ID ranges
134	Table 168 – Attribute ID ranges Table 169 – Service code ranges
135	Table 170 – Class codes Table 171 – Reserved class attributes for all object class definitions
136	Table 172 – Common services list
137	Table 173 – Message Router object specific services list Table 174 – Acknowledge Handler object specific services list Table 175 – Parameter object specific services list Table 176 – Services specific to Connection Manager
138	Table 177 – Services specific to Connection object Table 178 – Device type numbering
140	Table 179 – Connection Manager service request error codes
148	Table 180 – General status codes
150	Table 181 – Extended status code for a general status of “Key Failure in path
151	Table 182 – Identity object status codes
153	4.2 Data abstract syntax specification
158	4.3 Encapsulation abstract syntax Figure 15 – Encapsulation message
159	Table 183 – Encapsulation header Table 184 – Encapsulation command codes
161	Table 185 – Encapsulation status codes
162	Table 186 – Nop request encapsulation header Table 187 – RegisterSession request encapsulation header Table 188 – RegisterSession request data portion
163	Table 189 – RegisterSession reply encapsulation header Table 190 – RegisterSession reply data portion
164	Table 191 – UnRegisterSession request encapsulation header Table 192 – ListServices request encapsulation header
165	Table 193 – ListServices reply encapsulation header Table 194 – ListServices reply data portion
166	Table 195 – Communications capability flags Table 196 – ListIdentity request encapsulation header
167	Table 197 – ListIdentity reply encapsulation header Table 198 – ListIdentity reply data portion (successful)
168	Table 199 – CPF 2 identity item Table 200 – ListInterfaces request encapsulation header
169	Table 201 – ListInterfaces reply encapsulation header Table 202 – SendRRData request encapsulation header
170	Table 203 – SendRRData request data portion Table 204 – SendRRData reply encapsulation header
171	Table 205 – SendUnitData request encapsulation header Table 206 – SendUnitData request data portion Table 207 – Common packet format
172	Table 208 – CPF item format Table 209 – Item Type ID numbers
173	Table 210 – Null address item Table 211 – Connected address item Table 212 – Sequenced address item Table 213 – Unconnected data item
174	Table 214 – Connected data item Table 215 – Sockaddr info items
175	5 Transfer syntax 5.1 Compact encoding Table 216 – Usage of CPF items
176	Table 217 – BOOLEAN encoding Table 218 – Example compact encoding of a BOOL value
177	Table 219 – Encoding of SignedInteger values Table 220 – Example compact encoding of a SignedInteger value Table 221 – UnsignedInteger values Table 222 – Example compact encoding of an UnsignedInteger Table 223 – FixedLengthReal values
178	Table 224 – Example compact encoding of a REAL value Table 225 – Example compact encoding of a LREAL value Table 226 – FixedLengthReal values Table 227 – STRING value
179	Table 228 – STRING2 value Table 229 – STRINGN value Table 230 – SHORT_STRING value Table 231 – Example compact encoding of a STRING value Table 232 – Example compact encoding of STRING2 value Table 233 – SHORT_STRING type
180	Figure 16 – FixedLengthBitString compact encoding bit placement rules Figure 17 – Example compact encoding of a SWORD FixedLengthBitString Figure 18 – Example compact encoding of a WORD FixedLengthBitString Figure 19 – Example compact encoding of a DWORD FixedLengthBitString Figure 20 – Example compact encoding of a LWORD FixedLengthBitString
181	Table 234 – Example compact encoding of a single dimensional ARRAY
182	Table 235 – Example compact encoding of a multidimensional ARRAY Table 236 – Example compact encoding of a STRUCTURE
183	5.2 Data type reporting Table 237 – Identification codes and descriptions of elementary data types
184	Table 238 – Identification codes and descriptions of constructed data types
185	Figure 21 – Example 1 of formal encoding of a structure type specification Table 239 – Formal structure encoding definition
186	Figure 22 – Example 2 of formal encoding of a structure type specification Figure 23 – Example 3 of formal encoding of a handle structure type specification Table 240 – Formal structure with handles encoding definition
187	Figure 24 – Example 4 of formal encoding of a handle structure type specification Figure 25 – Example 5 of abbreviated encoding of a structure type specification Table 241 – Abbreviated structure encoding definition
188	Figure 26 – Example 1 of formal encoding of an array type specification Table 242 – Formal array encoding definition
189	Figure 27 – Example 2 of formal encoding of an array type specification Table 243 – Abbreviated array encoding definition
190	6 Structure of FAL protocol state machines Figure 28 – Example 1 of abbreviated encoding of an array type specification Figure 29 – Example 2 of abbreviated encoding of an array type specification
191	7 AP-Context state machine 7.1 Overview 7.2 Connection object state machine Figure 30 – I/O Connection object state transition diagram
192	Table 244 – I/O Connection state event matrix
195	Figure 31 – Bridged Connection object state transition diagram Table 245 – Bridged Connection state event matrix
196	Figure 32 – Explicit Messaging Connection object state transition diagram
197	Table 246 – Explicit Messaging Connection state event matrix
199	8 FAL service protocol machine (FSPM) 8.1 General 8.2 Primitive definitions
200	Table 247 – Primitives issued by FAL user to FSPM Table 248 – Primitives issued by FAL user to FSPM
202	Table 249 – Primitives issued by FSPM to FAL user
203	8.3 Parameters of primitives
204	8.4 FSPM state machines 9 Application relationship protocol machines (ARPMs) 9.1 General Table 250 – Parameters used with primitives exchanged between FAL user and FSPM
205	9.2 Connection-less ARPM (UCMM)
206	Table 251 – Primitives issued by FSPM to ARPM Table 252 – Primitives issued by ARPM to FSPM Table 253 – Parameters used with primitives exchanged between FSPM and ARPM
207	Figure 33 – State transition diagram of UCMM client9 Table 254 – UCMM client states
208	Table 255 – State event matrix of UCMM client
209	Figure 34 – State transition diagram of high–end UCMM server Table 256 – High-end UCMM server states
210	Table 257 – State event matrix of high-end UCMM server
211	Figure 35 – State transition diagram of low–end UCMM server Table 258 – Low-end UCMM server states Table 259 – State event matrix of low–end UCMM server
212	Figure 36 – Sequence diagram for a UCMM with one outstanding message
213	Figure 37 – Sequence diagram for a UCMM with multiple outstanding messages
214	9.3 Connection-oriented ARPMs (transports) Figure 38 – TPDU buffer Table 260 – Notification
215	Table 261 – Transport classes Table 262 – Primitives issued by FSPM to ARPM
216	Table 263 – Primitives issued by ARPM to FSPM Table 264 – Parameters used with primitives exchanged between FSPM and ARPM
217	Figure 39 – Data flow diagram using a client transport class 0 and server transport class 0 Figure 40 – Sequence diagram of data transfer using transport class 0
218	Figure 41 – Class 0 client STD Table 265 – Class 0 transport client states Table 266 – Class 0 client SEM
219	Figure 42 – Class 0 server STD Table 267 – Class 0 transport server states Table 268 – Class 0 server SEM
220	Figure 43 – Data flow diagram using client transport class 1and server transport class 1
221	Figure 44 – Sequence diagram of data transferusing client transport class 1 and server transport class 1
222	Table 269 – Class 1 transport client states
223	Figure 45 – Class 1 client STD Table 270 – Class 1 client SEM
224	Figure 46 – Class 1 server STD Table 271 – Class 1 transport server states
225	Table 272 – Class 1 server SEM
226	Figure 47 – Data flow diagram using client transport class 2 and server transport class 2
227	Figure 48 – Diagram of data transfer using client transport class 2and server transport class 2 without returned data
228	Figure 49 – Sequence diagram of data transfer using client transport class 2and server transport class 2 with returned data
229	Figure 50 – Class 2 client STD Table 273 – Class 2 transport client states
230	Table 274 – Class 2 client SEM
231	Figure 51 – Class 2 server STD Table 275 – Class 2 transport server states
232	Table 276 – Class 2 server SEM
234	Figure 52 – Data flow diagram using client transport class 3and server transport class 3
235	Figure 53 – Sequence diagram of data transfer using client transport class 3 and server transport class 3 without returned data
236	Figure 54 – Sequence diagram of data transfer using client transportclass 3 and server transport class 3 with returned data
237	Table 277 – Class 3 transport client states
238	Figure 55 – Class 3 client STD Table 278 – Class 3 client SEM
239	Table 279 – Class 3 transport server states
240	Figure 56 – Class 3 server STD
241	Table 280 – Class 3 server SEM
242	10 DLL mapping protocol machine 1 (DMPM 1) 10.1 General 10.2 Link producer Figure 57 – Data flow diagram for a link producer and consumer
243	10.3 Link consumer 10.4 Primitive definitions Table 281 – Primitives issued by ARPM to DMPM Table 282 – Primitives issued by DMPM to ARPM Table 283 – Parameters used with primitives exchanged between ARPM and DMPM
244	Table 284 – Primitives exchanged between data-link layer and DMPM Table 285 – Parameters used with primitives exchanged between DMPM and Data-link
245	10.5 DMPM state machine Table 286 – Selection of connection ID Table 287 – Link producer states
246	Figure 58 – State transition diagram for a link producer Figure 59 – State transition diagram for a link consumer Table 288 – State event matrix of link producer Table 289 – Link consumer states
247	10.6 Data-link Layer service selection 11 DLL mapping protocol machine 2 (DMPM 2) 11.1 General 11.2 Mapping of UCMM PDUs Table 290 – State event matrix of link consumer Table 291 – UCMM request
248	Table 292 – UCMM reply
250	Table 293 – Network Connection ID selection
251	Table 294 – Sockaddr Info usage
254	Table 295 – Example multicast assignments
255	11.3 Mapping of transport class 0 and class 1 PDUs Table 296 – UDP data format for class 0 and class 1
256	11.4 Mapping of transport class 2 and class 3 PDU’s Table 297 – Transport class 2 and class 3 connected data
257	11.5 Mapping of transport classes 4 to 6 11.6 IGMP Usage
258	11.7 Quality of Service (QoS) for CP 2/2 messages
259	Figure 60 – DS field in the IP header
260	Figure 61 – IEEE 802.1Q tagged frame Table 298 – Default DSCP and IEEE 802.1D mapping
262	11.8 Management of an encapsulation session 12 DLL mapping protocol machine 3 (DMPM 3)
263	Bibliography

Published By	Publication Date	Number of Pages
BSI	2014	266


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Title	Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 2 elements
Replaces	BS EN 61158-6-2:2012
Publisher	BSI
Committee	GEL/65/3
Pages	266
Publication Date	2014-11-30
Withdrawn Date	2022-07-29
Replaced By	BS EN IEC 61158-6-2:2019
ISBN	978 0 580 79468 1
Standard Number	BS EN 61158-6-2:2014
Identical National Standard Of	IEC 61158-6-2:2014, EN 61158-6-2:2014, EN 62496-3-1:2010, EN 61158-6-X
Descriptors	Interfaces (data processing), Packets (data transmission), Fieldbus, Industrial, Communication procedures, Computer networks, Process control, Communication networks, Application layer (OSI), Data transmission, Bus networks, Coding (data conversion), Open systems interconnection, Automatic control systems
ICS Codes	35.110 - Networking

BS EN 61158-6-2:2014

PDF Catalog

Related products

IEC 61158-6-2:2014