BS EN IEC 61158-5-21:2019 – TC:2020 Edition
$280.87
Tracked Changes. Industrial communication networks. Fieldbus specifications – Application layer service definition. Type 21 elements
Published By | Publication Date | Number of Pages |
BSI | 2020 | 178 |
IEC 61158-5-21:2019 specifies the structure and services of the type 21 IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). This second edition cancels and replaces the first edition published in 2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: •added Write and Read service; •miscellaneous editorial corrections.
PDF Catalog
PDF Pages | PDF Title |
---|---|
94 | undefined |
97 | Annex ZA(normative)Normative references to international publicationswith their corresponding European publications |
99 | CONTENTS |
102 | FOREWORD |
104 | INTRODUCTION |
105 | 1 Scope 1.1 Overview |
106 | 1.2 Specifications 1.3 Conformance 2 Normative references |
107 | 3 Terms, definitions, symbols, abbreviations, and conventions 3.1 Terms and definitions from other ISO/IEC standards 3.1.1 ISO/IEC 74981 terms 3.1.2 ISO/IEC 8822 terms 3.1.3 ISO/IEC 88241 terms |
108 | 3.1.4 ISO/IEC 9545 terms 3.2 Fieldbus data link layer terms 3.3 Fieldbus application layer specific definitions |
114 | 3.4 Abbreviations and symbols 3.5 Conventions 3.5.1 Overview |
115 | 3.5.2 General conventions 3.5.3 Conventions for class definitions |
116 | 3.5.4 Conventions for service definitions |
117 | 4 Concepts 4.1 Common concepts 4.1.1 Overview |
118 | 4.1.2 Architectural relationships Figures Figure 1 – Relationship to the OSI Basic Reference Model |
119 | Figure 2 – Architectural positioning of the fieldbus application layer |
120 | 4.1.3 Fieldbus application layer structure |
121 | Figure 3 – Client/server interactions |
122 | Figure 4 – Pull model interactions |
123 | Figure 5 – Push model interactions |
124 | Tables Table 1 – Types of timeliness |
125 | Figure 6 – APOs services conveyed by the FAL |
127 | Figure 7 – Application entity structure |
128 | Figure 8 – FAL management of objects |
129 | Figure 9 – ASE service conveyance |
131 | 4.1.4 Fieldbus application layer naming and addressing Figure 10 – Defined and established AREPs |
132 | 4.1.5 Architecture summary |
133 | 4.1.6 FAL service procedures Figure 11 – FAL architectural components |
134 | 4.1.7 Common FAL attributes 4.1.8 Common FAL service parameters |
135 | 4.1.9 APDU size 4.2 Type specific concepts |
136 | Figure 12 – Interaction between FAL and DLL Figure 13 – Publisher-subscriber communication model |
137 | 4.2.1 Node, AP, and object dictionary Figure 14 – Client-server communication model Figure 15 – Object model Table 2 – Overall structure of the OD |
138 | 4.2.2 APO ASEs 5 Data type ASE 5.1 General 5.1.1 Overview Figure 16 – ASEs of a Type 21 application |
139 | 5.1.2 Basic type overview 5.1.3 Fixed-length type overview Figure 17 – Data type class hierarchy example |
140 | 5.1.4 Constructed type overview 5.1.5 Specification of user-defined data types 5.1.6 Transfer of user data |
141 | 5.2 Formal definition of data type objects 5.2.1 Data type class |
142 | 5.3 FAL defined data types 5.3.1 Fixed-length types |
145 | 5.3.2 String types |
146 | 5.4 Data type ASE service specification 6 Communication model specification 6.1 ASEs 6.1.1 Application process ASE |
149 | Table 3 – Identify service |
151 | Table 4 – Status service |
152 | 6.1.2 Service data object ASE |
153 | Table 5 – Access rights for object |
154 | Table 6 – Read service |
156 | Table 7 – Write service |
158 | Table 8 – Write and Read service |
160 | Table 9 – Write and Read Multiple service |
162 | 6.1.3 Process data object ASE |
164 | Table 10 – TB-transfer Table 11 – COS-transfer |
165 | 6.1.4 Application relationship ASE Figure 18 – The AR ASE conveys APDUs between APs |
166 | Table 12 – Conveyance of service primitives by AREP role Table 13 – Valid combinations of AREP roles involved in an AR |
170 | Table 14 – AR-unconfirmed send |
171 | Table 15 – AR-confirmed send |
172 | 6.2 ARs 6.2.1 Point-to-point user-triggered confirmed client/server AREP (PTC-AR) |
173 | 6.2.2 Multipoint network-scheduled unconfirmed publisher-subscriber AREP (MSUAR) |
175 | 6.2.3 Multipoint user-triggered unconfirmed publisher-subscriber AREP (MTUAR) |
176 | 6.3 Summary of FAL classes 6.4 Permitted FAL services by AREP role Table 16 – FAL class summary Table 17 – Services by AREP role |
177 | Bibliography |