{"id":255858,"date":"2024-10-19T16:54:56","date_gmt":"2024-10-19T16:54:56","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-iec-tr-61850-90-42020\/"},"modified":"2024-10-25T12:23:28","modified_gmt":"2024-10-25T12:23:28","slug":"bsi-pd-iec-tr-61850-90-42020","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-iec-tr-61850-90-42020\/","title":{"rendered":"BSI PD IEC TR 61850-90-4:2020"},"content":{"rendered":"
1.1 General<\/b><\/p>\n
This part of IEC 61850, which is a Technical Report, is intended for an audience familiar with network communication and\/or IEC 61850-based systems and particularly for substation protection and control equipment vendors, network equipment vendors and system integrators.<\/p>\n
This document focuses on engineering a local area network limited to the requirements of IEC 61850-based substation automation. It outlines the advantages and disadvantages of different approaches to network topology, redundancy, clock synchronization, etc. so that the network designer can make educated decisions. In addition, this document outlines possible improvements to both substation automation and networking equipment.<\/p>\n
This document addresses data transfer over the network in IEC 61850, such as transmitting tripping commands for protection via GOOSE messages, and in particular the multicast data transfer of large volumes of sampled values (SV) from merging units (MUs).<\/p>\n
This document considers seamless redundancy to increase the network availability under failure conditions and the high precision clock synchronization that is central to the process bus and synchrophasor operation.<\/p>\n
This document is not intended as a tutorial on networking or on IEC 61850. Rather, it references and summarizes standards and publications to assist the engineers. Many publications discuss the Ethernet technology but do not address the networks in terms of substation automation. Therefore, many technologies and options have been ignored since they were not considered relevant for a future-proof substation automation network design.<\/p>\n
This document does not address network-based security, which is the subject of IEC 62351 and IEC 62443.<\/p>\n
This document does not address technologies for wide area networks; these are covered by IEC TR 61850-90-12. Guidelines for communication outside of the substation that uses exclusively the routable Internet Protocol have been published, especially in documents IEC TR 61850-90-1 (substation to substation), IEC TR 61850-90-2 (substation to control center) and IEC TR 61850-90-5 (synchrophasor transmission). However, data flows used in substationto- substation communication, or substation-to-control centre communication such as R-GOOSE and R-SV are covered when they transit over Ethernet links within the substation.<\/p>\n
This document does not dispense the responsible system integrator from an analysis of the actual application configuration, which is the base for a dependable system.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
4<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | FOREWORD <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 1 Scope 1.1 General 1.2 Namespace name and version <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 1.3 Code Component distribution Tables Table 1 \u2013 Attributes of (Tr)IEC 61850-90-4:2018A namespace <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 2 Normative references <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 3 Terms, definitions, abbreviated terms and conventions 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 3.3 Conventions 3.3.1 Network diagram symbols <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 3.3.2 Port and link symbols Figures Figure 1 \u2013 Network symbols Figure 2 \u2013 Port symbols <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 3.3.3 Bridges symbols 4 Overview of IEC 61850 networks 4.1 Logical allocation of functions and interfaces Figure 3 \u2013 Bridge symbol as beam Figure 4 \u2013 Bridge symbol as bus <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | Figure 5 \u2013 Levels and logical interfaces in grid automation (adapted from IEC 61850-5) Table 2 \u2013 IEC 61850-5 interface definitions <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 4.2 IEC 61850 protocol stack 4.2.1 General 4.2.2 IEC 61850 traffic classes Figure 6 \u2013 IEC 61850 protocol stack <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 4.2.3 MMS protocol Figure 7 \u2013 MMS protocol time\/distance chart <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 4.2.4 GOOSE protocol <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 8 \u2013 GOOSE protocol time\/space chart Figure 9 \u2013 GOOSE protocol time chart <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.2.5 SV protocol 4.2.6 R-GOOSE and R-SV Figure 10 \u2013 Example of SV traffic (4 800 Hz) <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 4.3 Station bus and process bus <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 5 Network design checklist 5.1 Design principles 5.2 Engineering flow Figure 11 \u2013 Station bus, process bus and traffic example <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.3 Checklist to be observed 5.3.1 Summary Figure 12 \u2013 Example of engineering flow <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.3.2 Environmental issues 5.3.3 EMI immunity 5.3.4 Form factor 5.3.5 Physical media <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 5.3.6 Substation application and network topology 5.3.7 Redundancy 5.3.8 Reliability, availability, maintainability 5.3.9 Logical data flows and traffic patterns <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 5.3.10 Latency for different types of traffic 5.3.11 Performance 5.3.12 Network management 5.3.13 Network supervision 5.3.14 Time synchronization and accuracy 5.3.15 Remote connectivity 5.3.16 Cyber security <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 5.3.17 Scalability, upgradeability and future-proof 5.3.18 Testing 5.3.19 Cost 6 Ethernet technology for substations 6.1 Ethernet subset for substation automation 6.2 Topology <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | Figure 13 \u2013 Ethernet LAN (with redundant links) <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 6.3 Physical layer 6.3.1 Data rate and medium 6.3.2 Full-duplex communication and auto-negotiation 6.3.3 Copper cabling at 100 Mbit\/s <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 14 \u2013 Bridge with copper (RJ45) ports Figure 15 \u2013 Shielded Cat5e cable <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 6.3.4 Optical cabling at 100 Mbit\/s (100BASE-FX) Figure 16 \u2013 RJ45 connector <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Figure 17 \u2013 LC connector <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 6.3.5 Optical cabling at 1 Gbit\/s (1000BASE-LX) 6.3.6 Copper cabling at 1 Gbit\/s 6.4 Link layer 6.4.1 Unicast and multicast MAC addresses Figure 18 \u2013 Bridge with optical fibres (LC connectors) <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 6.4.2 Link layer and bridges <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 6.4.3 Bridging nodes 6.4.4 Loop prevention and RSTP <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 19 \u2013 RSTP principle <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 6.4.5 Traffic control in the bridges 6.4.6 Unicast MAC address filtering <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 6.4.7 Multicast MAC address filtering <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 6.4.8 Virtual LANs (VLANs) traffic control <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure 20 \u2013 IEEE 802.3 frame format without and with VLAN tagging <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Table 3 \u2013 Example of port ingress setting table Table 4 \u2013 Example of port egress settings <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 6.4.9 Comparison VLAN versus multicast filtering Table 5 \u2013 Advantages and drawbacks of VLAN versus multicast filtering <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 6.4.10 Layer 2 redundancy protocols <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Figure 21 \u2013 PRP principle <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure 22 \u2013 HSR principle <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 6.5 Network layer 6.5.1 Internet protocol Figure 23 \u2013 HSR and PRP coupling (multicast) <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 6.5.2 IP public and private addresses 6.5.3 Subnet masks Table 6 \u2013 IANA private IP address blocks (copied from RFC 1918) <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 6.5.4 Network address translation 7 Network and substation topologies 7.1 General rule Table 7 \u2013 IP address and mask example <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 7.2 Connection of the SCADA Figure 24 \u2013 Mapping of electrical grid to data network topology <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | 7.3 Reference topologies and network redundancy Figure 25 \u2013 Example of substation with separation of the station bus into two sections <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 8 \u2013 Summary of reference topologies <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 9 \u2013 Reference topologies and redundancy protocols used <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 7.4 Reference topologies 7.4.1 Station bus topologies <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure 26 \u2013 Station bus as single bridge Table 10 \u2013 Station bus as single bridge <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Figure 27 \u2013 Station bus as hierarchical star Table 11 \u2013 Station bus as hierarchical star <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Figure 28 \u2013 Station bus as dual star with PRP <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Table 12 \u2013 Station bus as dual star <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure 29 \u2013 Station bus as ring of RSTP bridges Table 13 \u2013 Station bus as ring <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 30 \u2013 Station bus as separated Main 1 (Bus 1) and Main 2 (Bus 2) LANs <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 14 \u2013 Station bus as separated Main 1 and Main 2 protection <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Figure 31 \u2013 Station bus as ring of HSR bridging nodes Table 15 \u2013 Station bus as ring of bridging nodes <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 32 \u2013 Station bus as ring and subrings with RSTP <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 16 \u2013 Station bus as ring and subrings <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure 33 \u2013 Station bus as parallel rings with bridging nodes Table 17 \u2013 Station bus as parallel rings <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 34 \u2013 Station bus as parallel HSR rings Table 18 \u2013 Station bus as parallel HSR rings <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure 35 \u2013 Station bus as hierarchical rings with RSTP bridging nodes <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Table 19 \u2013 Station bus as ring of rings with RSTP <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 36 \u2013 Station bus as hierarchical rings with HSR bridging nodes <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Table 20 \u2013 Station bus as ring of rings with HSR <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 37 \u2013 Station bus as ring and subrings with HSR Table 21 \u2013 Station bus as ring and subrings with HSR <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | 7.4.2 Process bus and attachment of primary equipment <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Figure 38 \u2013 Double busbar bay with directly attached sensors <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 39 \u2013 Double busbar bay with SAMUs and process bus <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure 40 \u2013 Double busbar bay with ECT\/EVTs and process bus <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure 41 \u2013 1 \u00bd CB diameter with conventional, non-redundant attachment <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure 42 \u2013 1 \u00bd CB diameter with SAMUs and process bus <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure 43 \u2013 1 \u00bd CB diameter with ECT\/EVT and process bus <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Figure 44 \u2013 Process bus as connection of PIA and PIB (non-redundant protection) <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table 22 \u2013 Process bus as connection of PIA and PIB <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Figure 45 \u2013 Process bus as single star (not redundant protection) <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 23 \u2013 Process bus as single star <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Figure 46 \u2013 Process bus as dual star Table 24 \u2013 Process bus as dual star <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure 47 \u2013 Process bus as a single bridge (no protection redundancy) <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Table 25 \u2013 Process bus as single bridge <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Figure 48 \u2013 Process bus as separated LANs for main 1 and main 2 <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Table 26 \u2013 Process bus as separated LANs <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure 49 \u2013 Process bus as ring of HSR nodes <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | 7.4.3 Station bus and process bus connection Table 27 \u2013 Process bus as simple ring Table 28 \u2013 Advantages and drawbacks of physical separation <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Table 29 \u2013 Advantages and drawbacks of logical separation <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 50 \u2013 Process bus as star to merging units and station bus as RSTP ring Table 30 \u2013 Process bus as star to merging units <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Figure 51 \u2013 Station bus and process bus as rings connected by a router Table 31 \u2013 Connection of station bus to process bus by routers <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Figure 52 \u2013 Station bus ring and process bus ring with HSR <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table 32 \u2013 Connection of station bus to process bus by RedBoxes <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Figure 53 \u2013 Station bus as dual PRP ring and process bus as HSR ring Table 33 \u2013 Connection of duplicated station bus to process bus by RedBoxes <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | 8 Addressing in the substation 8.1 Network IP address plan for substations 8.1.1 General structure 8.1.2 IP address allocation of NET <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | 8.1.3 IP address allocation of BAY 8.1.4 IP address allocation of device Table 34 \u2013 Example IP address allocation of NET Table 35 \u2013 Example IP address allocation of BAY <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | 8.1.5 IP address allocation of devices with PRP 8.2 Routers and GOOSE \/ SV traffic Table 36 \u2013 Example IP address allocation of device Table 37 \u2013 Example IP address allocation of switches in PRP <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | 8.3 Communication outside the substation 9 Application parameters 9.1 MMS parameters 9.2 GOOSE parameters <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | 9.3 SV parameters 10 Performance 10.1 Station bus performance 10.1.1 Logical data flows and traffic patterns <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 38 \u2013 IEC 61850-5 interface traffic <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | 10.1.2 GOOSE traffic estimation 10.1.3 MMS traffic estimation Table 39 \u2013 Message types and addresses <\/td>\n<\/tr>\n | ||||||
123<\/td>\n | 10.1.4 station bus measurements Figure 54 \u2013 Station bus used for the measurements <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | 10.2 Process bus performance Figure 55 \u2013 Typical traffic (packet\/s) on the station bus <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | 11 Latency 11.1 Application requirements 11.2 Latency and determinism <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Figure 56 \u2013 Example of latency in function of traffic <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | 11.3 Latency requirements for different types of traffic 11.3.1 Latency requirements in IEC 61850-5 11.3.2 Latencies of physical paths 11.3.3 Latencies of bridges Table 40 \u2013 Latency requirements of IEC 61850-5 Table 41 \u2013 Elapsed time for an IEEE 802.3 frame to traverse the physical medium <\/td>\n<\/tr>\n | ||||||
128<\/td>\n | 11.3.4 Latency and hop counts 11.3.5 Network latency budget Table 42 \u2013 Delay for an IEEE 802.3 frame to ingress or to egress a port <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | 11.3.6 Example of traffic delays 11.3.7 Engineering a network for IEC 61850 protection Table 43 \u2013 Latencies caused by waiting for a lower-priority frame to egress a port <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | 12 Network traffic control 12.1 Factors that affect performance 12.1.1 Influencing factors 12.1.2 Traffic reduction Figure 57 \u2013 Generic multicast domains <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | 12.1.3 Example of traffic reduction scheme <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | 12.1.4 Multicast domains in a combined station bus and process bus network Figure 58 \u2013 Traffic patterns <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | 12.2 Traffic control by VLANs 12.2.1 Trunk traffic reduction by VLANs Figure 59 \u2013 Multicast domains for a combined process bus and station bus <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | 12.2.2 VLAN usage 12.2.3 VLAN handling at the IEDs 12.2.4 Example of correct VLAN configuration <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | 12.2.5 Example of incorrect VLAN configuration Figure 60 \u2013 Bridges with correct VLAN configuration <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Figure 61 \u2013 Bridges with poor VLAN configuration <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | 12.2.6 Retaining priority throughout the network 12.2.7 Traffic filtering with VLANs <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | 12.3 Traffic control by multicast filtering 12.3.1 Trunk traffic reduction by multicast filtering Figure 62 \u2013 Bridges with traffic segmentation through VLAN configuration <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | 12.3.2 Multicast\/VLAN management and redundancy protocol reconfiguration 12.3.3 Physical topologies and multicast management implications Figure 63 \u2013 Station bus separated into multicast domains by voltage level <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Figure 64 \u2013 Multicast traffic on an RSTP ring <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Figure 65 \u2013 RSTP station bus and HSR ring <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | 12.3.4 Connecting two HSR RedBoxes over an RSTP network 12.4 Configuration support from tools and SCD files Figure 66 \u2013 RSTP station bus and HSR process bus <\/td>\n<\/tr>\n | ||||||
143<\/td>\n | 13 Dependability 13.1 Resiliency requirements 13.2 Availability and reliability requirements <\/td>\n<\/tr>\n | ||||||
144<\/td>\n | 13.3 Recovery time requirements 13.4 Maintainability requirements 13.5 Dependability calculations <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | 13.6 Risk analysis attached to “unwanted events” 14 Time services 14.1 Clocks 14.1.1 Relative and absolute clocks <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | 14.1.2 Absolute time sources 14.1.3 Clock synchronization and accuracy requirements <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | 14.1.4 Expressing the clock accuracy Figure 67 \u2013 Clock quality definitions <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | 14.2 Time Scales 14.2.1 Definition of the second Figure 68 \u2013 Deviation between atomic day and Earth day (source: Wikipedia, modified) <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | 14.2.2 Time scales 14.2.3 Time representation <\/td>\n<\/tr>\n | ||||||
150<\/td>\n | 14.2.4 Leap second handling Figure 69 \u2013 TAI, UTC and UT1 time scales <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Figure 70 \u2013 Example of BIMP bulletin (Source: BIMP) <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Table 44 \u2013 Two representations of a positive leap second <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Figure 71 \u2013 Leap second transition at UTC midnight according to BIMP <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | 14.3 Synchronization in IEC 61850 14.3.1 Time synchronization requirements in IEC 61850-5 Table 45 \u2013 Synchronization classes (taken from IEC 61850-5) <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | 14.3.2 Time representation objects in IEC 61850 objects Table 46 \u2013 Network time synchronization classes <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table 47 \u2013 Time representations in IEC 61850 <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | 14.4 Clock synchronization protocols 14.4.1 General 14.4.2 1 PPS 14.4.3 IRIG-B Figure 72 \u2013 1 PPS synchronisation <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | 14.4.4 SNTP clock synchronization for IEC 61850-8-1 (station bus) <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Figure 73 \u2013 SNTP clock synchronization and delay measurement <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | 14.4.5 PTP (IEC 61588) synchronization <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | Figure 74 \u2013 PTP elements <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | Figure 75 \u2013 PTP clock correction and peer delay measurement (one-step) <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | Figure 76 \u2013 PTP two-step clock correction and peer delay measurement <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | Figure 77 \u2013 Clock accuracy degradation in a chain of TCs <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | Figure 78 \u2013 Doubly attached clocks in a PRP network <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | Figure 79 \u2013 Clocks in a PRP network coupled by BCs with an HSR ring <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Figure 80 \u2013 Hierarchy of clocks <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | 14.5 Merging units synchronization 14.6 Degraded situation upon loss of reference <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 14.7 Clock synchronization architecture and testing <\/td>\n<\/tr>\n | ||||||
176<\/td>\n | 15 Network security 16 Network management 16.1 Protocols for network management Figure 81 \u2013 Clock synchronization distribution <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | 16.2 Network management tool 16.3 Network diagnostic tool <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | 17 Remote connectivity 18 Network testing 18.1 Introduction to testing <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | 18.2 Environmental type testing Figure 82 \u2013 Quality assurance stages (copied from IEC 61850-4) <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | 18.3 Conformance testing 18.3.1 Protocols subject to conformance testing 18.3.2 Integrator acceptance and verification testing 18.3.3 Basic verification test set-up Table 48 \u2013 Standards applicable to network elements <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | 18.3.4 Basic VLAN handling test Figure 83 \u2013 Test set-up for verification test <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | 18.3.5 Basic priority tagging test 18.3.6 Basic multicast handling test 18.3.7 Basic RSTP recovery test <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | 18.3.8 Basic PRP test <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | 18.3.9 Basic HSR test Figure 84 \u2013 Test set-up for PRP and PUP <\/td>\n<\/tr>\n | ||||||
185<\/td>\n | 18.3.10 Basic IEC\/IEEE 61850-9-3 test Figure 85 \u2013 Test set-up for HSR and PUP <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | 18.3.11 Basic PTP TC test 18.3.12 Basic PTP BC test 18.4 Factory and site acceptance testing <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | 19 IEC 61850 bridge and port object model 19.1 Purpose <\/td>\n<\/tr>\n | ||||||
188<\/td>\n | 19.2 Bridge model 19.2.1 Simple model <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | Figure 86 \u2013 Multiport device model <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | 19.2.2 Bridge Logical Node linking <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | 19.3 Clock model 19.3.1 General clock model Figure 87 \u2013 Linking of bridge objects <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | 19.3.2 Simple clock model Figure 88 \u2013 General clock model in a device <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Figure 89 \u2013 Clock model for OC and BC <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | 19.3.3 PTP datasets 19.3.4 PTP clock objects 19.3.5 Linking of clock objects <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | 19.3.6 PTP TC objects Figure 90 \u2013 Ordinary Clock and Boundary Clock objects <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | Figure 91 \u2013 Transparent Clock objects <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | 19.4 Autogenerated IEC 61850 objects 19.4.1 Conditions for element presence Figure 92 \u2013 Transparent Clock linking <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | Table 49 \u2013 Conditions for presence of elements within a context <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | 19.4.2 Abbreviated terms used in data object names 19.4.3 Logical nodes Table 50 \u2013 Normative abbreviations for data object names <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | Figure 93 \u2013 Class diagram LogicalNodes_90_4::LogicalNodes_90_4 <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Figure 94 \u2013 Class diagram LNGroupL::LNGroupLExt <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | Figure 95 \u2013 Class diagram LNGroupL::LNGroupLNew1 <\/td>\n<\/tr>\n | ||||||
204<\/td>\n | Figure 96 \u2013 Class diagram LNGroupL::LNGroupLNew2 <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | Table 51 \u2013 Data objects of ClockPortLN <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | Table 52 \u2013 Data objects of PortBindingLN Table 53 \u2013 Data objects of PTPClockLN <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | Table 54 \u2013 Data objects of LCCHExt <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | Table 55 \u2013 Data objects of LPHDExt <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | Table 56 \u2013 Data objects of LTIMExt <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | Table 57 \u2013 Data objects of LBRI <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | Figure 97 \u2013 Usage of Multicast MAC Filtering <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Table 58 \u2013 Data objects of LCMF <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | Figure 98 \u2013 Usage of VLAN filtering Table 59 \u2013 Data objects of LCVF <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | Table 60 \u2013 Data objects of LPCP <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | Table 61 \u2013 Data objects of LPMS <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | Table 62 \u2013 Data objects of LTPC <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | Table 63 \u2013 Data objects of LTTC <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | Table 64 \u2013 Data objects of LTPP <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | Table 65 \u2013 Data objects of LTTP <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Table 66 \u2013 Data objects of LBSP <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | Table 67 \u2013 Data objects of LPLD <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | 19.4.4 Data semantics Table 68 \u2013 Attributes defined on classes of LogicalNodes_90_4 package <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 19.4.5 Enumerated data attribute types Table 69 \u2013 Literals of RstpStateKind Table 70 \u2013 Literals of VlanTagKind <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Table 71 \u2013 Literals of PortStKind Table 72 \u2013 Literals of ChannelRedundancyKind <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | 19.5 Mapping of bridge objects to SNMP 19.5.1 Mapping of LLN0 and LPHD attributes to SNMP Table 73 \u2013 Literals of LdpPortCfgKind Table 74 \u2013 Mapping of LLN0 and LPHD attributes to SNMP <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | 19.5.2 Mapping of LBRI attributes to SNMP for bridges 19.5.3 Mapping of LPCP attributes to SNMP for bridges Table 75 \u2013 Mapping of LBRI and LBSP attributes to SNMP for bridges Table 76 \u2013 Mapping of LPCP attributes to SNMP for bridges <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | 19.5.4 Mapping of LPLD attributes to SNMP for bridges 19.5.5 Mapping of HSR\/PRP link redundancy entity to SNMP Table 77 \u2013 Mapping of LPLD attributes to SNMP for bridges <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | 19.6 Mapping of clock objects to the IEC 61588 Datasets and IEC 62439-3 SNMP MIB Table 78 \u2013 Mapping of LCCH attributes for SNMP for HSR\/PRP LREs Table 79 \u2013 Mapping of clock objects in IEC 61850, IEC 61588 and IEC 62439-3:2016, Annex E <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | 19.7 Machine-readable description of the bridge objects 19.7.1 Method and examples <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | 19.7.2 Simple IED with PTP Figure 99 \u2013 Simple IED with PTP but no LLDP support <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | 19.7.3 Four-port bridge Figure 100 \u2013 Four-port bridge <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | 19.7.4 RedBox wit HSR Figure 101 \u2013 RedBox with LLDP but no PTP <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | 19.7.5 Connected PRP and HSR networks. Figure 102 \u2013 Coupled PRP and HSR networks <\/td>\n<\/tr>\n | ||||||
309<\/td>\n | Annex A (informative)Case study \u2013 Process bus configurationfor busbar protection system A.1 General A.1.1 Process bus for busbar protection A.1.2 Preconditions for case studies <\/td>\n<\/tr>\n | ||||||
310<\/td>\n | A.1.3 Case studies Figure A.1 \u2013 Preconditions for the process bus configuration example <\/td>\n<\/tr>\n | ||||||
311<\/td>\n | A.1.4 Calculation scheme for case 1-a Table A.1 \u2013 Summary of expected latencies <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | A.2 Solutions A.2.1 Potential solutions A.2.2 Reduction of sampling rate A.2.3 Increasing the transmission speed A.2.4 Controlling the traffic A.2.5 Partitioning the network A.2.6 Conclusions <\/td>\n<\/tr>\n | ||||||
313<\/td>\n | Annex B (informative)Case study \u2013 Simple topologies(Transener\/Transba, Argentina) B.1 Transba architecture and topology \u2013 132 kV substations Figure B.1 \u2013 First Ethernet-based Transba substation automation network <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | B.2 Transener architecture and topology \u2013 500 kV substations Figure B.2 \u2013 Transba SAS architecture <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | B.3 Transener SAS architectures \u2013 Esperanza Figure B.3 \u2013 Transener substation automation network <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | B.4 Transener SAS architectures \u2013 El Morej\u00f3n <\/td>\n<\/tr>\n | ||||||
317<\/td>\n | Figure B.4 \u2013 Transener SAS architecture \u2013 ET Esperanza <\/td>\n<\/tr>\n | ||||||
318<\/td>\n | Figure B.5 \u2013 Transener 500 kV architecture \u2013 El Morej\u00f3n <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | Figure B.6 \u2013 500 kV kiosk topology <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Figure B.7 \u2013 33 kV kiosk topology <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | Annex C (informative)Case study \u2013 An IEC 61850 station bus(Powerlink, Australia) C.1 Normative aspects C.2 Substation layout and topologies C.2.1 Reference substation: 275 kV \/ 132 kV C.2.2 Substation sizes Figure C.1 \u2013 Example HV and LV single line diagram and IEDs <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | C.2.3 Physical site layout considerations C.2.4 Panel layout for a bay Table C.1 \u2013 Site categories HV Table C.2 \u2013 Site categories MV <\/td>\n<\/tr>\n | ||||||
323<\/td>\n | C.2.5 HV building modules Figure C.2 \u2013 HV bay and cabinet module Table C.3 \u2013 Building modules <\/td>\n<\/tr>\n | ||||||
324<\/td>\n | C.3 Requirements put on the network C.3.1 Requirement classes C.3.2 Connectivity requirements C.3.3 Redundancy requirements <\/td>\n<\/tr>\n | ||||||
325<\/td>\n | C.3.4 Quality of Service requirements C.3.5 Components (hardware and software) C.4 Equipment Selection C.4.1 Criteria C.4.2 Physical links <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | C.4.3 Node connections C.4.4 Core router firewall C.4.5 Core bridge C.5 Data network topologies C.5.1 Separate and common data network <\/td>\n<\/tr>\n | ||||||
327<\/td>\n | Figure C.3 \u2013 Data network areas <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | Table C.4 \u2013 Network modules <\/td>\n<\/tr>\n | ||||||
329<\/td>\n | Figure C.4 \u2013 Substation LAN topology <\/td>\n<\/tr>\n | ||||||
330<\/td>\n | C.5.2 Station bus (station functions) or SCADA gateway \/ HMI Figure C.5 \u2013 SAS Gen1 High level traffic flows <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | C.5.3 Station core C.5.4 Transformer protection over the network Figure C.6 \u2013 SCADA & gateway connection Figure C.7 \u2013 Station Core <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | C.5.5 Automated voltage regulation (AVR) C.5.6 External connections C.5.7 Segmentation requirements <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | C.5.8 Station bus and bay domains Figure C.8 \u2013 Overall VLANs Figure C.9 \u2013 Three domains <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | C.5.9 Multicast filtering Figure C.10 \u2013 One domain per diameter, bus zone and transformer protection Table C.5 \u2013 Domain assignment for three domains Table C.6 \u2013 Domain assignment for one domain per diameter <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | C.5.10 Use of VLANs C.5.11 IP addressing C.6 Estimation of the traffic flow C.6.1 Types of traffic C.6.2 GOOSE C.6.3 MMS traffic estimate C.6.4 Other services <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | C.7 Latencies C.8 Conclusion Table C.7 \u2013 Summary of expected latencies Table C.8 \u2013 Traffic types and estimated network load <\/td>\n<\/tr>\n | ||||||
337<\/td>\n | Annex D (informative)Case study \u2013 Station bus with VLANs(Trans-Africa, South Africa) D.1 General D.1.1 Normative aspects D.1.2 Background D.1.3 Electrical network overview <\/td>\n<\/tr>\n | ||||||
338<\/td>\n | D.1.4 Substation communication overview D.1.5 Design and project objectives D.2 Conceptual design D.2.1 Substation automation networks <\/td>\n<\/tr>\n | ||||||
339<\/td>\n | D.2.2 Design parameters D.2.3 Network topology and redundancy <\/td>\n<\/tr>\n | ||||||
340<\/td>\n | Figure D.1 \u2013 Conceptual topology of substationLAN network with redundancy <\/td>\n<\/tr>\n | ||||||
341<\/td>\n | D.2.4 Interface standards Figure D.2 \u2013 Detailed topology of substation LAN with redundancy <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | Table D.1 \u2013 VLAN numbering and allocation <\/td>\n<\/tr>\n | ||||||
343<\/td>\n | D.2.5 Inter-VLAN routing D.2.6 Network quality of service policies D.2.7 IP Traffic prioritization and differentiated services (DiffServ) Table D.2 \u2013 Prioritization selection for various applications <\/td>\n<\/tr>\n | ||||||
344<\/td>\n | D.2.8 Packet classification D.2.9 Packet marking Figure D.3 \u2013 Original IPv4 Type of Service (ToS) octet Table D.3 \u2013 Mapping of applications to service levels <\/td>\n<\/tr>\n | ||||||
345<\/td>\n | Figure D.4 \u2013 Differentiated Services (DiffServ) codepoint field Table D.4 \u2013 List of DiffServ codepoint field values <\/td>\n<\/tr>\n | ||||||
346<\/td>\n | D.2.10 Network IP addressing and device allocations Table D.5 \u2013 Example of DSCP to class of service mapping Table D.6 \u2013 Example of DSCP mappings Table D.7 \u2013 Typical substation IP Address map (IP range: 10.0.16.0\/21) <\/td>\n<\/tr>\n | ||||||
347<\/td>\n | D.2.11 IP Address management D.2.12 Network coupling D.2.13 Routing requirements and WAN Interfacing D.2.14 Network time synchronization D.2.15 Network time protocol (SNTP) D.2.16 Device management philosophy <\/td>\n<\/tr>\n | ||||||
349<\/td>\n | D.3 Detailed design: solution specifications for substation-A D.3.1 General D.3.2 Physical environment Table D.8 \u2013 SNMP MIBs applicable to substation devices <\/td>\n<\/tr>\n | ||||||
350<\/td>\n | Table D.9 \u2013 Example of device naming <\/td>\n<\/tr>\n | ||||||
351<\/td>\n | D.3.3 Local area network Table D.10 \u2013 Example of interface addressing and allocation Table D.11 \u2013 Example of device access and SNMP assignment <\/td>\n<\/tr>\n | ||||||
352<\/td>\n | Table D.12 \u2013 Example of hardware identification <\/td>\n<\/tr>\n | ||||||
353<\/td>\n | Table D.13 \u2013 Example of device name table Table D.14 \u2013 Example of firmware and software table <\/td>\n<\/tr>\n | ||||||
354<\/td>\n | Table D.15 \u2013 Example of interface addressing and allocation Table D.16 \u2013 Example of network switch details Table D.17 \u2013 Example of VLAN definitions <\/td>\n<\/tr>\n | ||||||
355<\/td>\n | Table D.18 \u2013 Example of IP routing Table D.19 \u2013 Example of QoS mapping <\/td>\n<\/tr>\n | ||||||
356<\/td>\n | Table D.20 \u2013 Example of trunk and link aggregation table (void) Table D.21 \u2013 LAN switch port speed and duplex configuration <\/td>\n<\/tr>\n | ||||||
357<\/td>\n | Table D.22 \u2013 LAN switch port security settings <\/td>\n<\/tr>\n | ||||||
358<\/td>\n | Table D.23 \u2013 Example of DHCP snooping Table D.24 \u2013 Example of storm control table <\/td>\n<\/tr>\n | ||||||
359<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Communication networks and systems for power utility automation – Network engineering guidelines<\/b><\/p>\n |