1.1 General The IEC 62439 series is applicable to high-availability automation networks based on the Ethernet technology. This document: – specifies PRP and HSR as two related 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; – specifies the operation of the precision time protocol (PTP) in networks that implement the two redundancy protocols (Annex A); – specifies PTP profiles with performance suitable for power utilty automation (Annex B) and industrial automation (Annex C); – includes for better understanding a tutorial (Annex D) on the PTP features effectively used in high-availability automation networks; – includes a management information base for PTP (Annex E); – defines a conformance test suite for the above protocols (Annex F). 1.2 Code component distribution This document is associated with Code components. Each Code Component is a ZIP package containing at least the electronic representation of the Code Component itself and a file describing the content of the package (IECManifest.xml). The IECManifest contains different sections giving information on: – the copyright notice; – the identification of the code component; – the publication related to the code component; – the list of the electronic files which compose the code component; – an optional list of history files to track changes during the evolution process of the code component. The Code Components associated with this IEC standard are a set of SNMP MIBs. The Code Component IEC-62439-3-MIB.mib is a file containing the MIBs for PRP/HSR and PTP_SNMP. It is available in a full version, which contains the MIBs defined in this document with the documentation associated and access is restricted to purchaser of this document. The Code Components are freely accessible on the IEC website for download at: https://www.iec.ch/sc65c/supportingdocuments/IEC_62439-3.MIB.{VersionStateInfo}.full.zip but the usage remains under the licensing conditions.

PDF Catalog

PDF Pages	PDF Title
1	30459122 30459122-1-250
265	251-364
379	A-30389552
380	undefined
383	Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
385	English CONTENTS
393	FOREWORD
396	INTRODUCTION
398	1 Scope 1.1 General 1.2 Code component distribution
399	2 Normative references
400	3 Terms, definitions, abbreviated terms, and conventions 3.1 Terms and definitions
402	3.2 Abbreviated terms
403	3.3 Conventions 4 Parallel Redundancy Protocol (PRP) 4.1 PRP principle of operation 4.1.1 PRP network topology
404	Figures Figure 1 – PRP example of general duplicated network
405	4.1.2 PRP LANs with linear or bus topology 4.1.3 PRP LANs with ring topology Figure 2 – PRP example of duplicated network in bus topology
406	4.1.4 DANP node structure Figure 3 – PRP example of redundant ring with SANs and DANPs
407	4.1.5 PRP attachment of singly attached nodes Figure 4 – PRP with two DANPs communicating
408	4.1.6 Compatibility between singly and doubly attached nodes 4.1.7 Network management 4.1.8 Implication on application
409	4.1.9 Transition to a single-thread network 4.1.10 Duplicate handling Figure 5 – PRP RedBox, transition from single to double LAN
410	Figure 6 – PRP frame closed by an RCT
411	Figure 7 – PRP VLAN-tagged frame closed by an RCT Figure 8 – PRP padded frame closed by an RCT
413	Figure 9 – Duplicate Discard algorithm boundaries Tables Table 1 – Duplicate discard cases
414	4.1.11 Network supervision 4.1.12 Redundancy management interface
415	4.2 PRP protocol specifications 4.2.1 Installation, configuration and repair guidelines 4.2.2 Unicast MAC addresses 4.2.3 Multicast MAC addresses
416	4.2.4 IP addresses 4.2.5 Node specifications 4.2.6 Duplicate Accept mode (testing only)
417	4.2.7 Duplicate Discard mode Table 2 – Monitoring data set
418	Table 3 – NodesTable attributes
421	4.3 PRP_Supervision frame 4.3.1 PRP_Supervision frame format
422	Table 4 – PRP_Supervision frame with no VLAN tag
423	4.3.2 PRP_Supervision frame contents Table 5 – PRP_Supervision frame with (optional) VLAN tag
424	4.3.3 PRP_Supervision frame for RedBox 4.3.4 Bridging node (deprecated) Table 6 – PRP_Supervision frame contents Table 7 – PRP_Supervision TLV for Redbox
425	4.4 Constants 4.5 PRP layer management entity (LME) 5 High-availability Seamless Redundancy (HSR) 5.1 HSR objectives Table 8 – PRP constants
426	5.2 HSR principle of operation 5.2.1 Basic operation with a ring topology Figure 10 – HSR example of ring traffic for multicast frames
427	Figure 11 – HSR example of ring traffic for unicast frames
428	5.2.2 HSR connection to other networks
430	Figure 12 – HSR example of coupling two redundant PRP LANs to a ring (unicast)
432	Figure 13 – HSR example of coupling from a ring node to PRP LANs (multicast)
433	Figure 14 – HSR example of coupling from a ring to two PRP LANs (multicast)
434	Figure 15 – HSR example of coupling three rings to one PRP LAN
435	Figure 16 – HSR example of peer coupling of two rings
436	Figure 17 – HSR example of connected rings
437	Figure 18 – HSR example of meshed topology
438	Figure 19 – HSR example of topology using two independent networks
439	Figure 20 – HSR example of coupling an RSTP LAN to HSR by two bridges
440	5.2.3 DANH node structure Figure 21 – HSR structure of a DANH
441	5.2.4 RedBox structure Figure 22 – HSR structure of a RedBox
442	5.3 HSR protocol specifications 5.3.1 HSR layout 5.3.2 HSR operation
444	5.3.3 DANH sending from its link layer interface
445	5.3.4 DANH receiving from an HSR port 5.3.5 DANH forwarding rules
447	5.3.6 HSR Class of Service 5.3.7 HSR clock synchronization 5.3.8 Deterministic transmission delay and jitter 5.4 HSR RedBox specifications 5.4.1 RedBox properties
448	5.4.2 RedBox receiving from port C (interlink)
450	5.4.3 RedBox receiving from port A or port B (HSR ring)
452	5.4.4 RedBox receiving from its link layer interface (local) 5.4.5 Redbox ProxyNodeTable handling 5.4.6 RedBox CoS 5.4.7 RedBox clock synchronization 5.4.8 RedBox medium access
453	5.5 QuadBox specification 5.6 Duplicate Discard method 5.7 Frame format for HSR 5.7.1 Frame format for all frames Figure 23 – HSR frame without a VLAN tag
454	5.7.2 HSR_Supervision frame Figure 24 – HSR frame with VLAN tag
455	Table 9 – HSR_Supervision frame with no VLAN tag
456	Table 10 – HSR_Supervision frame with optional VLAN tag
457	5.8 HSR constants
458	5.9 HSR layer management entity (LME) Table 11 – HSR Constants
459	Figure 25 – HSR node with management counters
460	6 Protocol Implementation Conformance Statement (PICS) Figure 26 – HSR RedBox with management counters
461	Table 12 – PICS
462	7 PRP/HSR Management Information Base (MIB)
477	Annex A (normative)Synchronization of clocks over redundant paths A.1 Overview A.2 PRP mapping to PTP A.2.1 Particular operation of PRP for PTP messages
478	Figure A.1 – Connection of a DAC master to a DAC slave over PRP
479	A.2.2 Scenarios and device roles
480	Figure A.2 – Elements of PRP time distribution networks
481	A.2.3 Attachment to redundant LANs by a BC A.2.4 Attachment to redundant LANs by doubly attached clocks Figure A.3 – Doubly Attached Clock as BC (OC3A is best master)
483	Figure A.4 – Doubly Attached Clocks OC1 and OC2
485	A.2.5 Specifications of DANP as DAC Figure A.5 – Doubly attached clocks when OC1 has the same identity on both LANs
486	A.2.6 PRP-SAN RedBoxes for PTP
487	Figure A.6 – PRP RedBox as TWBCs
488	Figure A.7 – RedBox DABC clock model
490	Figure A.8 – PRP RedBoxes as DABC with E2E – message flow
491	Figure A.9 – PRP RedBoxes as DABC with E2E – timing
492	Figure A.10 – PRP RedBoxes as DABC with P2P on PRP – message flow
493	Figure A.11 – PRP RedBoxes as DABC with P2P on PRP – timing
495	Figure A.12 – PRP-SAN RedBox as SLTC with E2E – message flow
497	Figure A.13 – PRP RedBox as SLTC with E2E – timing
498	Figure A.14 – PRP RedBox as SLTC with P2P – message flow
499	Figure A.15 – PRP RedBox as SLTC with P2P – timing diagram
502	Figure A.16 – PRP RedBox as DATC with E2E – message flow
503	Figure A.17 – PRP RedBox as DATC with E2E – timing
504	Figure A.18 – PRP RedBox as DATC with P2P – message flow
505	Figure A.19 – PRP RedBox as DATC with P2P – timing
506	A.3 HSR Mapping to PTP A.3.1 HSR messages and other messages A.3.2 HSR operation with PTP messages
508	A.3.3 HSR with redundant master clocks Figure A.20 – HSR with two GCs (GC1 is grandmaster, GC2 is back-up)
509	A.3.4 HSR timing diagram for PTP messages Figure A.21 – PTP messages sent and received by an HSR node (1-step)
510	A.3.5 HSR nodes specifications Figure A.22 – PTP messages sent and received by an HSR node (2-step)
512	A.4 HSR RedBoxes for PTP A.4.1 HSR-SAN RedBox Figure A.23 – Attachment of a GC to an HSR ring through a RedBox as TC and BC
513	A.4.2 HSR-PRP RedBox connection by BC
514	Figure A.24 – PRP to HSR coupling by BCs
515	A.4.3 HSR-PRP RedBox connection by TC
516	Figure A.25 – PRP to HSR coupling by DATC and SLTC
517	A.4.4 HSR to HSR connection by QuadBoxes Figure A.26 – HSR coupling to two PRP and one HSR network
518	A.5 Doubly attached clock specification A.5.1 State machine
519	Figure A.27 – Port states including transitions for redundant operation
520	Table A.1 – States
521	A.5.2 Supervision of the port Table A.2 – Transitions Table A.3 – Variables
522	A.5.3 BMCA for paired ports Figure A.28 – BMCA for redundant masters
523	A.5.4 Selection of the port state A.6 PTP datasets for high availability A.6.1 General A.6.2 Data types
524	A.6.3 Datasets for OC or BC
532	A.6.4 Datasets for TCs
533	Annex B (normative)PTP profile for Power Utility Automation (PUP) –Redundant clock attachment B.1 Application domain B.2 PTP profile specification B.3 Specifications B.4 Redundant clock attachment
534	Annex C (normative)PTP industry profiles for high-availability automation networks C.1 Application domain C.2 PTP profile specification
535	C.3 Clock types C.4 Protocol specification common C.4.1 Base protocol C.4.2 Version control
536	C.4.3 Time scale C.4.4 BMCA C.4.5 Time correction mechanism C.4.6 Management C.4.7 1 PPS support C.4.8 Leap second transition C.4.9 Use of port number
537	C.4.10 Time distribution security C.5 Protocol specification for L3E2E industry profile C.5.1 Base protocol C.5.2 Multicast address C.5.3 Delay calculation mechanism C.5.4 Sync message padding
538	C.6 Protocol specification for L2P2P industry profile C.6.1 Base protocol C.6.2 Delay measurement mechanism C.6.3 Consideration of media converters C.7 Common timing requirements for L2P2P and L3E2E C.7.1 Measurement conditions C.7.2 Network time inaccuracy
539	C.7.3 Response to time step changes C.7.4 Requirements for GCs Figure C.1 – Response to a time step
540	Table C.1 – ClockClass
541	C.7.5 Requirements for TCs C.7.6 Requirements for BCs
542	Figure C.2 – States of a BC
544	C.8 Requirements for media converters C.9 Requirements for links C.10 Network engineering
545	C.11 Default settings
546	C.12 Handling of doubly attached clocks Table C.2 – PTP attributes
547	C.13 Protocol Implementation Conformance Statement (PICS) for PTP C.13.1 PICS conventions C.13.2 PICS for PTP Table C.3 – PICS for clocks
549	C.14 Recommendations for time representation C.14.1 Usage of flags in TimePropertyDS
550	C.14.2 UTC leap second transition
551	C.14.3 ALTERNATE_TIME_OFFSET_INDICATOR_TLV Table C.4 – Transitions with an inserted leap second (UTC binary and C37.118) Table C.5 – Transitions with a removed leap second (UTC binary and C37.118)
553	Table C.6 – ATOI transition to Pacific Summer Time (spring) Table C.7 – ATOI transitions to Pacific Standard Time (autumn)
554	Table C.8 – Transitions with an inserted leap second in Pacific Standard Time Table C.9 – Transitions with a removed leap second in Pacific Standard Time
555	Annex D (informative)Precision Time Protocol tutorial for the PTP Industrial profile D.1 Objective D.2 Precision and accuracy Figure D.1 – Time error as a probability distribution function
556	D.3 PTP clock types
557	Figure D.2 – PTP principle with GC, TC and OC
558	D.4 PTP main options Figure D.3 – PTP elements
559	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
560	D.6.2 2-step to 1-step translation Figure D.5 – 1-step and 2-step correction of a Sync message (peer-to-peer)
561	Figure D.6 – Translation from 2-step to 1-step correction in TCs
562	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 correction – message view
563	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 correction
564	D.7.4 End-to-end link delay calculation by Delay_Req – Delay_Resp D.7.5 Consideration of media converters in end-to-end delay calculation Figure D.9 – End-to-end delay measurement with 2-step correction
565	D.8 Peer-to-peer link delay calculation D.8.1 Peer-to-peer link delay calculation with 1-step correction Figure D.10 – Peer-to-peer link delay measurement with 1-step correction
566	D.8.2 Peer-to-peer link delay calculation with 2-step correction Figure D.11 – Peer-to-peer link delay measurement with 2-step correction
567	D.8.3 Consideration of media converters in peer delay calculation
568	Figure D.12 – Peer delay measurement and Sync message delay with media converter
569	Annex E (normative)Management Information base for singly and doubly attached clocks
597	Annex F (normative)Conformance testing for PRP and HSR and handlingof redundancy in PIP and PUP F.1 General F.2 PRP conformance test F.2.1 PRP test set-up
598	F.2.2 PRP test components F.2.3 Test for documentation and labelling Figure F.1 – Test set-up for PRP
599	F.2.4 Test for (unicast) IP addresses F.2.5 Test for configuration Table F.1 – Test for PRP documentation and labelling Table F.2 – Test for (unicast) IP addresses
600	F.2.6 Test of DANP Table F.3 – Test for PRP configuration (Table 8) Table F.4 – Test for PRP supervision frames (Table 4 and Table 5)
602	Table F.5 – Test for PRP tagging (4.1.10.2, 4.2.7.3)
603	Table F.6 – Test of a DANP without a NodesTable Table F.7 – Test of a DANP with a NodesTable
604	F.2.7 Test of PRP Redboxes Table F.8 – Test for discard over different ports
605	Table F.9 – Test for PRP supervision frames (Table 4 and Table 5) Table F.10 – Test of RedBox for ProxyNodeTable
606	F.2.8 Test for Management Table F.11 – Test of RedBox for forwarding
607	Table F.12 – Test for DANP receive/transmit counters
608	F.2.9 Test of DANP or RedBox for processing of PTP frames Figure F.2 – Test set-up for PRP and PTP with L2P2P
610	Table F.13 – Test procedure for processing of PTP frames
611	Table F.14 – Test for processing of PTP frames
612	Table F.15 – Test for processing of PTP frames
613	F.3 HSR conformance test F.3.1 HSR test set-up Table F.16 – Test procedure for processing of PTP frames
614	F.3.2 HSR test components F.3.3 Test for HSR documentation and labelling Figure F.3 – Test set-up for HSR (without PTP)
615	F.3.4 Test of DANH or RedBox for IP addresses F.3.5 Test of DANH for configuration Table F.17 – Test for HSR documentation Table F.18 – Test for IP addresses
616	F.3.6 Test of DANH Table F.19 – Test procedure for HSR configuration (Table 11)
617	Table F.20 – Test for HSR supervision frames (Table 9 and Table 10)
618	Table F.21 – Test for HSR tagging
619	Table F.22 – Test of DANH for HSR Mode H multicast Table F.23 – Test of DANH for HSR Mode H unicast
620	F.3.7 Test of HSR RedBoxes Table F.24 – Test of DANH for other modes than Mode H Table F.25 – Test of RedBox for HSR supervision frames (Table 9 and Table 10)
621	Table F.26 – Test of RedBox for ProxyNodeTable Table F.27 – Test of RedBox for Mode H Unicast
622	F.3.8 Test of DANH or RedBox for receive/transmit counters Table F.28 – Test of DANH or RedBox for receive/transmit counters
623	F.3.9 Test of DANH or RedBox for processing of PTP frames in L2P2P Figure F.4 – Test set-up for HSR with L2P2P
624	Table F.29 – Test for processing of PTP frames (slave)
625	Table F.30 – Test for processing of PTP frames (master)
627	Bibliography

Published By	Publication Date	Number of Pages
BSI	2023	630


PDF Format	Searchable	Printable	Preview Now

Status	Withdrawn
Pages	630
Publication Date	2023-05-30
ISBN	978 0 539 23172 4
Standard Number	BS EN IEC 62439-3:2022 – TC
Title	Tracked Changes. Industrial communication networks. High availability automation networks – Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy (HSR)
Replaces	BS EN IEC 62439-3:2018 – TC
Descriptors	Computer networks, Automatic control systems, Data processing, Industrial, Open systems interconnection, CSMA/CD networks, Communication networks, Data transmission, Local area networks, Information exchange, Process control
Publisher	BSI
Committee	GEL/65
ICS Codes	25.040.01 - Industrial automation systems in general

BS EN IEC 62439-3:2022 – TC 2023

PDF Catalog

Related products

BS EN IEC 62439-3:2018 – TC:2020 Edition

BS EN IEC 61439-1:2021 – TC

BS EN 62493:2015 – TC:2020 Edition

BS EN IEC 61439-2:2021 – TC

BS EN IEC 62439-3:2022

BS EN IEC 62439-2:2022 – TC 2023

BS EN IEC 61439-5:2023 – TC