BS EN IEC 62439-3:2018 – TC:2020 Edition
$280.87
Tracked Changes. Industrial communication networks. High availability automation networks – Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy (HSR)
Published By | Publication Date | Number of Pages |
BSI | 2020 | 380 |
IEC 62439-3:2016 is available as /2 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition. IEC 62439-3:2016 is applicable to high-availability automation networks based on the Ethernet technology. This part of IEC 62439 specifies two redundancy protocols designed to provide seamless recovery in case of single failure of an inter-bridge link or bridge in the network, which are based on the same scheme: parallel transmission of duplicated information. This third edition cancels and replaces the second edition published in 2012. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: – technical corrections and extension of specifications; – consideration of IEC 61588 clock synchronization with end-to-end delay measurement alongside the existing peer-to-peer delay measurement in PRP.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | compares BS EN IEC 62439-3:2018 |
2 | TRACKED CHANGES Text example 1 โ indicates added text (in green) |
208 | undefined |
212 | English CONTENTS |
218 | FOREWORD |
220 | INTRODUCTION 0.1 General 0.2 Changes with respect to the previous edition 0.3 Patent declaration |
222 | 1 Scope 2 Normative references |
223 | 3 Terms, definitions, abbreviations, acronyms, and conventions 3.1 Terms and definitions 3.2 Abbreviations and acronyms |
224 | 3.3 Conventions |
225 | 4 Parallel Redundancy Protocol (PRP) 4.1 PRP principle of operation 4.1.1 PRP network topology 4.1.2 PRP LANs with linear or bus topology Figures Figure 1 โ PRP example of general redundant network |
226 | 4.1.3 PRP LANs with ring topology 4.1.4 DANP node structure Figure 2 โ PRP example of redundant network as two LANs (bus topology) Figure 3 โ PRP example of redundant ring with SANs and DANPs |
227 | 4.1.5 PRP attachment of singly attached nodes Figure 4 โ PRP with two DANPs communicating |
228 | 4.1.6 Compatibility between singly and doubly attached nodes 4.1.7 Network management 4.1.8 Implication on application 4.1.9 Transition to non-redundant networks |
229 | 4.1.10 Duplicate handling Figure 5 โ PRP RedBox, transition from single to double LAN |
230 | Figure 6 โ PRP frame extended by an RCT |
231 | Figure 7 โ PRP VLAN-tagged frame extended by an RCT Figure 8 โ PRP padded frame closed by an RCT |
232 | Figure 9 โ Duplicate Discard algorithm boundaries |
233 | Tables Table 1 โ Duplicate discard cases |
234 | 4.1.11 Network supervision 4.1.12 Redundancy management interface 4.2 PRP protocol specifications 4.2.1 Installation, configuration and repair guidelines |
235 | 4.2.2 Unicast MAC addresses 4.2.3 Multicast MAC addresses 4.2.4 IP addresses 4.2.5 Nodes |
236 | 4.2.6 Duplicate Accept mode (testing only) 4.2.7 Duplicate Discard mode Table 2 โ Monitoring data set |
237 | Table 3 โ NodesTable attributes |
240 | 4.3 PRP_Supervision frame 4.3.1 PRP_Supervision frame format Table 4 โ PRP_Supervision frame with no VLAN tag |
241 | 4.3.2 PRP_Supervision frame contents Table 5 โ PRP_Supervision frame with (optional) VLAN tag |
242 | 4.3.3 PRP_Supervision frame for RedBox 4.3.4 Reception of a PRP_Supervision frame and NodesTable Table 6 โ PRP_Supervision frame contents Table 7 โ PRP_Supervision TLV for Redbox |
243 | 4.4 Bridging node 4.5 Constants 4.6 PRP service specification 5 High-availability Seamless Redundancy (HSR) 5.1 HSR objectives Table 8 โ PRP constants |
244 | 5.2 HSR principle of operation 5.2.1 Basic operation with a ring topology Figure 10 โ HSR example of ring configuration for multicast traffic |
245 | 5.2.2 DANH node structure Figure 11 โ HSR example of ring configuration for unicast traffic |
246 | 5.2.3 Topology Figure 12 โ HSR structure of a DANH |
247 | Figure 13 โ HSR example of topology using two independent networks |
248 | Figure 14 โ HSR example of peer coupling of two rings |
249 | Figure 15 โ HSR example of connected rings |
250 | Figure 16 โ HSR example of coupling two redundant PRP LANs to a ring |
251 | Figure 17 โ HSR example of coupling from a ring node to redundant PRP LANs |
252 | Figure 18 โ HSR example of coupling from a ring to two PRP LANs |
253 | Figure 19 โ HSR example of coupling three rings to one PRP LAN |
254 | 5.2.4 RedBox structure Figure 20 โ HSR example of meshed topology |
255 | Figure 21 โ HSR structure of a RedBox |
256 | 5.3 HSR node specifications 5.3.1 HSR operation 5.3.2 DANH receiving from its link layer interface |
257 | 5.3.3 DANH receiving from an HSR port |
258 | 5.3.4 DANH forwarding rules |
259 | 5.3.5 CoS |
260 | 5.3.6 Clock synchronization 5.3.7 Deterministic medium access 5.4 HSR RedBox specifications 5.4.1 RedBox properties 5.4.2 RedBox receiving from interlink |
262 | 5.4.3 RedBox forwarding on the ring 5.4.4 RedBox receiving from an HSR port |
264 | 5.4.5 RedBox receiving from its link layer interface 5.4.6 Redbox ProxyNodeTable handling 5.4.7 RedBox CoS |
265 | 5.4.8 RedBox clock synchronization 5.4.9 RedBox medium access 5.5 QuadBox specification 5.6 Duplicate Discard method 5.7 Frame format for HSR 5.7.1 Frame format for all frames Figure 22 โ HSR frame without a VLAN tag |
266 | 5.7.2 HSR_Supervision frame Figure 23 โ HSR frame with VLAN tag |
267 | Table 9 โ HSR_Supervision frame with no VLAN tag |
268 | Table 10 โ HSR_Supervision frame with optional VLAN tag |
269 | 5.8 Constants |
270 | 5.9 HSR service specification Figure 24 โ HSR node with management counters Table 11 โ HSR Constants |
271 | 6 Protocol Implementation Conformance Statement (PICS) Figure 25 โ HSR RedBox with management counters |
272 | 7 PRP/HSR Management Information Base (MIB) |
289 | Annexes Annex A (normative) Clocks synchronization over redundant paths in IEC 62439-3 A.1 Overview A.2 Attachment to redundant LANs by a boundary clock Figure A.1 โ Doubly Attached Clock as BC (MCA is best master) |
290 | A.3 Attachment to redundant LANs by doubly attached ordinary clocks |
291 | Figure A.2 โ Doubly Attached Clock when MCA is best master |
292 | A.4 PRP mapping to PTP A.4.1 Scenarios and device roles Figure A.3 โ Doubly attached clocks when OC1 is best master |
294 | A.4.2 Operation in PRP Figure A.4 โ Elements of PRP networks |
295 | A.4.3 Configuration specification Figure A.5 โ Connection of a master clock to an ordinary clock over PRP |
296 | A.4.4 Specifications of DANP as DAC A.4.5 Clock model of a RedBox for PTP |
297 | Figure A.6 โ PRP RedBox as BCs (OC3 and BC7 are best masters) |
298 | Figure A.7 โ RedBox DABC clock model |
299 | Figure A.8 โ PRP RedBoxes as DABC with E2E โ BC7 is master |
300 | Figure A.9 โ PRP RedBoxes as DABC with E2E โ timing |
301 | Figure A.10 โ PRP RedBoxes as DABC with P2P โ OC5 is best master |
302 | Figure A.11 โ PRP RedBoxes as DABC with P2P โ timing |
303 | Figure A.12 โ PRP RedBox as DATC with E2E โsignal flow |
305 | Figure A.13 โ PRP RedBox as DATC with E2E โ timing |
306 | Figure A.14 โ PRP RedBox as DATC with P2P |
307 | Figure A.15 โ PRP RedBox as DATC with P2P โ timing |
310 | Figure A.16 โ PRP RedBox as SLTC with E2E |
311 | Figure A.17 โ PRP RedBox as SLTC with E2E โ timing |
312 | Figure A.18 โ PRP RedBox as SLTC with P2P |
313 | A.5 HSR Mapping to PTP A.5.1 PTP traffic in HSR |
314 | Figure A.19 โ HSR with one GMC |
315 | Figure A.20 โ PTP messages sent and received by an HSR node (1-step). |
316 | A.5.2 HSR nodes specifications Figure A.21 โ PTP messages sent and received by an HSR node (2-step) |
317 | A.5.3 Redundant clocks in HSR A.5.4 Attachment of an MC to an external LAN |
318 | A.6 PRP to HSR Mapping A.6.1 Connection methods A.6.2 PRP-HSR connection by BC Figure A.22 โ Attachment of a GMC to an HSR ring through a RedBox as TC |
319 | A.6.3 PRP-HSR connection by TCs Figure A.23 โ PRP to HSR coupling by BCs |
320 | A.7 Doubly attached clock model A.7.1 State machine Figure A.24 โ PRP to HSR coupling by TCs |
321 | Figure A.25 โ Port states including transitions for redundant operation |
322 | Table A.1 โ States |
323 | A.7.2 Supervision of the port Table A.2 โ Transitions Table A.3 โ Variables |
324 | A.7.3 BMCA for paired ports Figure A.26 โ BMCA for redundant masters |
325 | A.7.4 Selection of the port state A.8 PTP datasets for high availability A.8.1 General A.8.2 Data types |
326 | A.8.3 Datasets for ordinary or boundary clocks |
330 | A.8.4 Object for transparent clocks |
333 | Annex B (normative) PTP profile for Power Utility Automation โ Redundant clock attachment B.1 Application domain B.2 PTP profile specification B.3 Redundant clock attachment |
334 | Annex C (normative) PTP profiles for high-availability automation networks C.1 Application domain C.2 PTP profile specification C.3 Clock types |
335 | C.4 Protocol specification common C.5 Protocol specification for L3E2E automation profile C.6 Protocol specification for L2P2P automation profile |
336 | C.7 Timing requirements C.7.1 Measurement conditions C.7.2 Network time inaccuracy C.7.3 Network elements C.7.4 Requirements for grandmasters |
337 | C.7.5 Requirements for TCs C.7.6 Requirements for BCs C.7.7 Requirements for media converters C.7.8 Requirements for links |
338 | C.8 Network engineering C.9 Default settings |
339 | C.10 Redundant clock handling Table C.1 โ PTP attributes for the Industrial Automation profile |
340 | C.11 Protocol Implementation Conformance Statement (PICS) C.11.1 Conventions C.11.2 PICS |
341 | Table C.2 โ PICS for clocks |
342 | Annex D (informative) Precision Time Protocol tutorial for IEC 62439-3 D.1 Objective D.2 Precision and accuracy Figure D.1 โPrecision and accuracy example |
343 | D.3 PTP clock types Figure D.2 โ Precision Time Protocol principle |
344 | D.4 PTP main options Figure D.3 โ Precision Time Protocol elements |
345 | D.5 Layer 2 and layer 3 communication D.6 1-step and 2-step correction D.6.1 Time correction in TCs Figure D.4 โ Delays and time-stamping logic in TCs |
346 | D.6.2 2-step to 1-step translation Figure D.5 โ Correction of the Sync message by 1-step and 2-step (peer-to-peer) |
347 | Figure D.6 โ Translation from 2-step to 1-step in TCs |
348 | D.7 End-To-End link delay measurement D.7.1 General method D.7.2 End-to-End link delay measurement with 1-step clock correction Figure D.7 โ Translation from 2-step to 1-step โ message view |
349 | D.7.3 End-to-End link delay measurement with 2-step clock correction Figure D.8 โ End-to-end link delay measurement with 1-step clock correction |
350 | D.7.4 End-to-End link delay calculation by Delay_Req/Delay_Resp D.8 Peer-to-Peer link delay calculation D.8.1 Peer-to-Peer link delay calculation with 1-step correction Figure D.9 โ End-to-end delay measurement with 2-step clock correction |
351 | D.8.2 Peer-to-Peer link delay calculation with 2-step correction Figure D.10 โ Peer-to-peer link delay measurement with 1-step clock correction |
352 | Figure D.11 โ Peer-to-peer link delay measurement with 2-step clock correction |
353 | Annex E (normative) Management Information base for singly and doubly attached clocks |
378 | Bibliography |