BS EN IEC 61158-6-25:2019
$215.11
Industrial communication networks. Fieldbus specifications – Application layer protocol specification. Type 25 elements
Published By | Publication Date | Number of Pages |
BSI | 2019 | 130 |
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 International Standard provides common elements for basic time-critical and non-timecritical messaging communications between application programs in an automation environment and material specific to Type 25 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 document defines in an abstract way the externally visible behavior provided by the different Types of the fieldbus Application Layer in terms of:
-
the abstract syntax defining the application layer protocol data units conveyed between communicating application entities,
-
the transfer syntax defining the application layer protocol data units conveyed between communicating application entities,
-
the application context state machine defining the application service behavior visible between communicating application entities; and
-
the application relationship state machines defining the communication behavior visible between communicating application entities.
The purpose of this document is to define the protocol provided to:
-
define the wire-representation of the service primitives defined in IEC 61158-5-25, and
-
define the externally visible behavior associated with their transfer.
This document specifies the protocol of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545).
FAL services and protocols are provided by FAL application-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 process 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 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 standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
7 | CONTENTS |
12 | FOREWORD |
14 | INTRODUCTION |
15 | 1 Scope 1.1 General |
16 | 1.2 Specification 1.3 Conformance 2 Normative references |
17 | 3 Terms, definitions, symbols, abbreviations and conventions 3.1 Reference model terms and definitions 3.1.1 ISO/IEC 7498-1 terms 3.1.2 ISO/IEC 8822 terms 3.1.3 ISO/IEC 9545 terms |
18 | 3.1.4 ISO/IEC 8824-1 terms 3.2 Additional Type 25 terms and definitions |
20 | 3.3 Symbols and abbreviations |
21 | 3.4 Conventions 3.4.1 General conventions 3.4.2 Conventions for class definitions 3.4.3 Conventions for bit description in octets Figures Figure 1 – Bit description in octets |
22 | 3.4.4 Conventions for state machine descriptions Tables Table 1 – State transition descriptions Table 2 – Descriptions of state machine elements Table 3 – Conventions used in state machine |
23 | 4 FAL syntax description 4.1 FAL PDU type S abstract syntax 4.1.1 Basic abstract syntax |
27 | 4.2 FAL PDU type N abstract syntax 4.2.1 Basic abstract syntax 4.2.2 CyclicData-PDU |
28 | 4.2.3 MulticastData-PDU 4.2.4 PtoPData-PDU 4.2.5 Aliveinfo-PDU 4.2.6 Aliveinfo6-PDU |
29 | 4.2.7 Inq-PDU 4.2.8 Ninq-PDU 4.2.9 Reply-PDU 4.2.10 RetransEnq-PDU 4.2.11 RetransConfirm-PDU |
30 | 4.2.12 RetransNak-PDU 4.3 Data type assignments for type S 4.4 Data type assignments for type N |
31 | 5 FAL transfer syntax 5.1 Encoding rules 5.1.1 Unsigned encoding |
32 | 5.1.2 Octet string encoding 5.1.3 SEQUENCE encoding 5.2 FALPDU type S elements encoding 5.2.1 RCL_header Table 4 – Frame Class Table 5 – DA_STaddress – DA_STaddress Table 6 – DA_MACaddress |
33 | 5.2.2 RHE-PDU Table 7 – CMD field format Table 8 – Send Direction |
34 | Table 9 – RHE ReceiveStatus Table 10 – Physical Linkdown |
35 | 5.2.3 LCC-PDU 5.2.4 LCA-PDU Table 11 – RHE_pattern 1~4 Table 12 – LCC-Kind |
36 | 5.2.5 LCN-PDU Table 13 – RCL Status |
37 | 5.2.6 LNA-PDU 5.2.7 SCR-PDU 5.2.8 Cyclic_S-PDU |
38 | 5.2.9 Cyclic_header 5.2.10 Control-PDU 5.2.11 RMTCTL-PDU |
39 | 5.2.12 INFO-PDU |
40 | 5.3 FALPDU type N elements encoding 5.3.1 General 5.3.2 FALAR-N Header Figure 2 – hd_sa Table 14 – hd_h_type |
41 | Figure 3 – hd_da |
42 | Table 15 – Usage of Mgn or Lnn |
44 | Table 16 – Detailed conditions for sequence number check of reception message |
45 | Figure 4 – Valid sequence number for reception message Figure 5 – hd_m_ctl Table 17 – Valid bits of hd_m_ctl |
46 | Table 18 – Specified TCD |
47 | Table 19 – hd_pkind Table 20 – PDU with an effective hd_pseq |
49 | Figure 6 – Valid reception packet sequence number Table 21 – Detailed conditions for sequence number check of reception packet (Multicast communication with retransmission) |
50 | Table 22 – Detailed conditions for packet sequence number check |
51 | Table 23 – Relation between message transmission/reception Table 24 – hd_mode Table 25 – Message priority level |
52 | Table 26 – Value of α Table 27 – Example of header information for a UDP message fragmentation Table 28 – Example of header information for a TCP message fragmentation |
53 | Table 29 – inqid_inq_sa value Table 30 – inqid_tr_adr value |
54 | 5.3.3 CyclicData-PDU Table 31 – inqid_inq_seq value Table 32 – Relationship between inqid_id_seq and inqid_tr_adr |
55 | 5.3.4 MulticastData-PDU 5.3.5 PtoP Data-PDU 5.3.6 Aliveinfo-PDU |
56 | Table 33 – Type of an alive-message Table 34 – Type of an alive-message protocol |
57 | Table 35 – Time of each al_mode Table 36 – Status change of tasks Table 37 – Change of tasks content |
58 | 5.3.7 Aliveinfo6-PDU |
59 | 5.3.8 Inq-PDU |
60 | 5.3.9 Ninq-PDU 5.3.10 Reply-PDU Figure 7 – Node-list |
61 | 5.3.11 RetransEnq-PDU 5.3.12 RetransConfirm-PDU |
62 | 5.3.13 RetransNak-PDU |
63 | 6 Structure of the FAL protocol state machine 7 FAL service protocol machine (FSPM) 7.1 Overview 7.2 FSPM type S 7.2.1 Overview Figure 8 – Relationships between protocol machines |
64 | 7.2.2 Interface of cyclic communication to FAL users Figure 9 – Structure of FSPM type S |
65 | Table 38 – The threshold of transmission factor Table 39 – Example of the traffic control configuration menu |
66 | 7.2.3 State machine of FSPM Figure 10 – Shared memory allocation in type S network Table 40 – Cyclic data state table |
67 | 7.3 FSPM type N 7.3.1 Overview Table 41 – Acyclic data state table |
68 | 7.3.2 FSPM Figure 11 – Structure of FSPM type N |
69 | Table 42 – Cyclic data state table Table 43 – Acyclic data state table |
70 | 8 Application relationship protocol machine (ARPM) 8.1 ARPM type S 8.1.1 Overview |
71 | 8.1.2 Cyclic control Figure 12 – Structure of ARPM type S |
72 | Figure 13 – Sequence of cyclic communication Figure 14 – The primitives for cyclic control |
73 | Table 44 – Cyclic control state table |
74 | Table 45 – Cyclic control functions |
75 | 8.1.3 Remote control Figure 15 – The primitives for Remote control Table 46 – Cyclic control variables |
76 | Table 47 – Remote control state table |
79 | Table 48 – Remote control functions |
80 | 8.1.4 RCL communication control Figure 16 – The primitives for RCL communication control Table 49 – Remote control variables |
81 | Table 50 – RCL communication control state table |
82 | Table 51 – RCL communication control functions |
84 | 8.1.5 RT communication control Table 52 – RCL communication control variables |
85 | Figure 17 – The primitives for RT communication control Table 53 – RT communication control state table |
87 | Table 54 – RT communication control functions Table 55 – RT communication control variables |
88 | 8.2 ARPM type N 8.2.1 Overview 8.2.2 General control Figure 18 – Structure of ARPM type N |
90 | 8.2.3 Cyclic transmission control Figure 19 – Primitives of Cyclic transmission control |
91 | Table 56 – Cyclic transmission control state table |
93 | Table 57 – Cyclic transmission control functions |
95 | 8.2.4 Acyclic transmission control Table 58 – Cyclic transmission control variables |
96 | Figure 20 – Primitives of acyclic transmission control Table 59 – Acyclic transmission control state table |
106 | Table 60 – Acyclic transmission control functions |
109 | Table 61 – Acyclic transmission control variables |
110 | 8.2.5 RT communication control Table 62 – RT communication control state table |
121 | Table 63 – RT communication control functions |
125 | Table 64 – RT communication control variables |
126 | 9 DLL mapping protocol machine (DMPM) 9.1 DMPM type S |
127 | 9.2 DMPM type N 9.2.1 General 9.2.2 Communication port in transport layer 9.2.3 Quality of Service Table 65 – ARPM to DL mapping Table 66 – Assignment policy of communication ports |
128 | Figure 21 – DSCP format Figure 22 – IEEE 802.1Q tag frame format Table 67 – Default DSCP, IEEE 802.1D and IEEE 802.1Q priority mapping |
129 | Bibliography |