IEC TR 61850-90-22:2024

IEC TR 61850-90-22 ®
Edition 1.0 2024-12
TECHNICAL
REPORT
colour
inside
Communication networks and systems for power utility automation –
Part 90-22: SCD based substation network automated management with with
visualization and supervision support

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Secretariat Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform IEC Products & Services Portal - products.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews, graphical symbols and the glossary.
committee, …). It also gives information on projects, replaced With a subscription you will always have access to up to date
and withdrawn publications. content tailored to your needs.

IEC Just Published - webstore.iec.ch/justpublished
Electropedia - www.electropedia.org
Stay up to date on all new IEC publications. Just Published
The world's leading online dictionary on electrotechnology,
details all new publications released. Available online and once
containing more than 22 500 terminological entries in English
a month by email.
and French, with equivalent terms in 25 additional languages.

Also known as the International Electrotechnical Vocabulary
IEC Customer Service Centre - webstore.iec.ch/csc
(IEV) online.
If you wish to give us your feedback on this publication or need

further assistance, please contact the Customer Service
Centre: sales@iec.ch.
IEC TR 61850-90-22 ®
Edition 1.0 2024-12
TECHNICAL
REPORT
colour
inside
Communication networks and systems for power utility automation –

Part 90-22: SCD based substation network automated management with with

visualization and supervision support

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 33.200  ISBN 978-2-8327-0064-8

– 2 – IEC TR 61850-90-22:2024 © IEC 2024
CONTENTS
FOREWORD . 7
INTRODUCTION . 9
1 Scope . 10
2 Normative references . 10
3 Terms, definitions and abbreviated terms . 11
3.1 Terms and definitions . 11
3.2 Abbreviated terms . 13
4 Problem statement . 15
4.1 Available technologies . 15
4.2 Technical issues with current solution . 15
4.2.1 Substation network configuration issues . 15
4.2.2 Substation network testing and troubleshooting issues . 16
4.2.3 Substation network operation and maintenance issues . 17
4.2.4 Substation network cyber security issues . 17
4.3 Proposed technical solutions for present issues . 17
4.3.1 Substation network configuration based on SCD file . 17
4.3.2 Substation network supervision and visualization . 19
5 Use cases . 20
5.1 Common actors . 20
5.2 Use case 1: Substation network static-routing . 21
5.2.1 Overview . 21
5.2.2 Use case description . 21
5.2.3 Example: An illustration of substation network static-routing . 23
5.2.4 Static-routing scenario: Move of IED to a different port or bridge . 27
5.2.5 Static-routing scenario: Add IEDs and bridges . 29
5.2.6 Static-routing: Alternative technologies using SDN . 30
5.3 Use case 2: Substation network auto-routing . 31
5.3.1 Overview . 31
5.3.2 Use case description . 32
5.3.3 Example: An illustration of substation network auto-routing . 33
5.3.4 Auto-routing scenario: Move of IED to a different port or bridge . 35
5.3.5 Auto-routing scenario: Add IEDs and bridges . 36
5.3.6 Auto-routing scenario: substation network topology recovery . 38
5.3.7 Auto-routing scenario: forwarding path calculation . 43
5.4 Use case 3: GOOSE/SV path visualization . 45
5.4.1 Overview . 45
5.4.2 Use case description . 45
5.4.3 GOOSE/SV path visualization scenario: Normal state . 46
5.4.4 GOOSE/SV path visualization scenario: Communication fail . 47
5.4.5 GOOSE/SV path visualization scenario: IED duplication . 48
5.5 Use case 4: Bridge configuration management . 49
5.5.1 Overview . 49
5.5.2 Use case description . 50
5.6 Use case 5: Network information provided to HMI . 50
5.6.1 Overview . 50
5.6.2 Use case description . 51

5.7 Use case 6: Impact analysis in case of adding simulation device . 51
5.7.1 Overview . 51
5.7.2 Use case description . 51
6 Details of the auto-routing network configuration method . 52
6.1 Requirement . 52
6.1.1 Communication network topology discovery . 52
6.1.2 IED-learning . 53
6.1.3 Information presentation and monitoring . 53
6.1.4 LNs for bridge model . 53
6.2 Principle for auto-routing . 53
6.2.1 Auto-routing overview . 53
6.2.2 IED-learning . 54
6.2.3 Network topology discovery . 55
6.2.4 Plot GOOSE/SV path . 56
6.2.5 Install VLAN/MAC table configuration to bridges . 56
6.2.6 Verify the correctness of built GOOSE/SV paths . 57
6.2.7 TRILL example . 57
6.3 Comparison of existing technologies . 63
6.3.1 General . 63
6.3.2 Comparison of network redundancy technology . 63
6.3.3 Comparison of traffic control technology . 64
6.3.4 Other available technology . 64
6.4 Network device configuration . 65
6.4.1 General . 65
6.4.2 Network re-configuration scenarios . 65
6.4.3 Silent IED support by IID . 65
6.4.4 GOOSE/SV path configuration using BCD . 66
6.4.5 Configuration version control . 66
6.4.6 Example for network device configuration management . 66
7 GOOSE/SV path presentation and monitoring . 69
7.1 General . 69
7.2 "Substation network static-routing" based approach . 69
7.3 "Substation network auto-routing" based approach . 69
7.3.1 GOOSE/SV path presentation . 69
7.3.2 GOOSE/SV path monitoring . 70
7.3.3 GOOSE/SV path data modelling . 70
7.3.4 Example for information presentation and monitoring . 72
8 GOOSE/SV path traffic control and engineering strategy . 73
8.1 Overview. 73
8.2 "Substation network static-routing" based approach . 73
8.3 "Substation network auto-routing" based approach . 74
8.3.1 GOOSE/SV path traffic control . 74
8.3.2 Example for GOOSE/SV path traffic control . 74
8.3.3 GOOSE/SV path traffic engineering strategy . 75
8.3.4 Example for GOOSE/SV path traffic engineering strategy . 75
9 Handling of simulated GOOSE/SV messages . 77
9.1 General . 77
9.2 "Substation network static-routing" based approach . 77

– 4 – IEC TR 61850-90-22:2024 © IEC 2024
9.3 "Substation network auto-routing" based approach . 77
9.3.1 Dividing different operation plane with "s" bit . 77
9.3.2 Example for handling the simulated GOOSE/SV message . 78
10 Guidance on auto-routing network usage . 81
10.1 General . 81
10.2 Implementation of substation network auto-routing. 81
10.3 Auto-routing usage case . 85
10.3.1 IED position change or adding a new IED . 85
10.3.2 Adding a new bay . 89
10.3.3 SCD GOOSE/SV list application . 90
10.4 Substation network visualization support . 92
10.4.1 Substation network health state . 92
10.4.2 Performance assessment of substation network . 93
Annex A (informative) Illustration for bridge configurator and BCD file . 95
A.1 Generate BCD file with bridge configurator . 95
A.2 Description of the demo use case . 96
A.3 Demo BCD file . 101
A.4 Usage of BCD file . 103
A.4.1 General . 103
A.4.2 Usage to perform IED learning . 103
A.4.3 Usage to generate bridge configuration . 104
Annex B (informative) Recommendation of logical nodes . 106
B.1 LN: AR-Bridge Name LARB . 106
B.2 LN: AR-bridge Port Name: LARP. 106
B.3 LN: AR-bridge Neighbour Name:LARN . 107
B.4 LN: IED-Learning Outcome Name:LILO . 107
B.5 LN: GOOSE/SV Egress Path Name:LGEP. 108
Bibliography . 109

Figure 1 – Static-routing engineering procedure, first stage . 22
Figure 2 – Static-routing engineering procedure, second stage . 23
Figure 3 – Physical substation network connectivity and planned GOOSE/SV path . 24
Figure 4 – Static-routing within an RSTP ring . 25
Figure 5 – Static-routing with a HSR ring . 27
Figure 6 – Static-routing scenario diagram: Move of IED to a different port or bridge . 28
Figure 7 – Static-routing scenario diagram: Add IEDs and bridges . 29
Figure 8 – Use case diagram for substation network auto-routing . 32
Figure 9 – Demonstration of a physical substation network topology . 33
Figure 10 – Demonstration of substation network auto-routing . 34
Figure 11 – Auto-routing scenario diagram: Move of IED to a different port or bridge . 35
Figure 12 – Auto-routing scenario diagram: Add IEDs and bridges . 37
Figure 13 – Use case diagram for substation network topology recovery . 38
Figure 14 – Redundancy with Auto-routing and STP/RSTP . 40
Figure 15 – Simplified Auto-routing network topology with STP/RSTP ring . 40
Figure 16 – Redundancy with auto-routing and HSR . 41
Figure 17 – Redundancy with auto-routing and PRP . 42

Figure 18 – Redundancy in pure auto-routing network . 43
Figure 19 – Use case diagram for forwarding path calculation . 44
Figure 20 – Use case diagram for GOOSE/SV path visualization . 45
Figure 21 – GOOSE/SV path visualization scenario diagram: Path normal state . 46
Figure 22 – GOOSE/SV path visualization scenario diagram: Communication fail . 47
Figure 23 – GOOSE/SV path visualization scenario diagram: IED duplication . 49
Figure 24 – Use case diagram for bridge configuration management . 50
Figure 25 – Use case diagram for Network information provided to HMI . 51
Figure 26 – Use case diagram of impaction in case of adding a simulated device . 52
Figure 27 – TRILL encapsulating and decapsulating . 58
Figure 28 – Ethernet and TRILL headers . 59
Figure 29 – Illustration of LSP flooding . 61
Figure 30 – Forwarding process of GOOSE/SV packet with TRILL . 62
Figure 31 – LSP update procedure of an IED disconnection/addition . 62
Figure 32 – LSP update procedure of a bridge addition/disconnection . 63
Figure 33 – Origin network topology for BCD file (Version 1.00) . 67
Figure 34 – Minor version change due to bay extension . 67
Figure 35 – Major version change of owe to the finish of substation phases . 68
Figure 36 – Multiport AR-bridge model . 71
Figure 37 – Logical relationship between the LNs . 71
Figure 38 – Example of a GOOSE path presentation and monitoring (normal state) . 72
Figure 39 – Example of a GOOSE path presentation and monitoring (abnormal state) . 73
Figure 40 – Illustration of GOOSE/SV path traffic control . 74
Figure 41 – Illustration of GOOSE/SV path engineering . 76
Figure 42 – Example of GOOSE/SV path traffic engineering . 76
Figure 43 – Topology and subscription relationship for three bays . 78
Figure 44 – Coexistence of simulation and actual signals . 80
Figure 45 – Bridges and IEDs to be connected . 82
Figure 46 – Final physical substation network . 82
Figure 47 – Flow chart of auto-routing implementation . 83
Figure 48 – Demonstration of IED move and addition . 85
Figure 49 – IED move action . 86
Figure 50 – Add new IED action . 88
Figure 51 – Demonstration of adding a new bay . 89
Figure 52 – Adding a new bay action . 90
Figure 53 – Example of SCD GOOSE/SV list application . 91
Figure 54 – Example of visual physical and logical topology . 93
Figure 55 – Example of substation network assessment . 94
Figure A.1 – Generation of BCD file . 95
Figure A.2 – Logical view of exampled IEDs . 97
Figure A.3 – Demo SCD file information (relevant and irrelevant to BCD) . 98
Figure A.4 – Demo IID file information (relevant and irrelevant to BCD) . 99
Figure A.5 – Demo BCD file structure generated from the demo SCD file and IID file . 100

– 6 – IEC TR 61850-90-22:2024 © IEC 2024
Figure A.6 – Using the demo BCD file to perform IED-learning . 104
Figure A.7 – Using the demo BCD file to generate bridge configuration . 105

Table 1 – Current steps followed on building GOOSE/SV paths in SCD . 15
Table 2 – Pros and cons of static-routing and auto-routing . 19
Table 3 – Common actor . 20
Table 4 – Extracted subscription information of IED1, IED2 and IED3 . 24
Table 5 – Generated bridge configuration information . 25
Table 6 – Generated bridge configuration information with redundancy path . 26
Table 7 – Generated bridge configuration information (including all interconnect ports
of the RSTP ring) . 26
Table 8 – Extracted subscription information of IED1, IED2 and IED3 . 33
Table 9 – Outcome of IED learning . 34
Table 10 – Example of GOOSE/SV ingress flow table . 54
Table 11 – Advantages and drawbacks of auto-routing versus RSTP, HSR or PRP . 64
Table 12 – Advantages and drawbacks of different traffic control strategies . 64
Table 13 – Scenarios requiring network re-configuration . 65
Table 14 – Traffic estimation . 75
Table 15 – Data flow inside a bay . 78
Table 16 – Data flow cross bays . 78
Table 17 – Extracted subscription information of the example . 79
Table 18 – Example forwarding table of maintenance plane (SW1) . 79
Table 19 – Example forwarding table of working plane (SW1) . 81
Table 20 – Example forwarding table of working plane (SW2) . 81
Table 21 – GOOSE/SV associations abstracted from SCD file . 83
Table 22 – Topology discovered and IED-learning result of Figure 44 . 84
Table 23 – Generated GOOSE/SV flow table . 84
Table 24 – Example forwarding table of AR-bridge SW1 . 85
Table 25 – GOOSE/SV associations related with IED e7 . 86
Table 26 – SCD GOOSE/SV list example of SW2 . 91
Table A.1 – Elements different between SCD file and BCD file. 95
Table A.2 – IED subscription information in demo SCD file . 96
Table B.1 – Data objects of LARB . 106
Table B.2 – Data objects of LARP . 107
Table B.3 – Data objects of LARN . 107
Table B.4 – Data objects of LILO . 108
Table B.5 – Data objects of LGEP . 108

INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
COMMUNICATION NETWORKS AND SYSTEMS –
FOR POWER UTILITY AUTOMATION –

Part 90-22: SCD based substation network automated management with
visualization and supervision support

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and
in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC Publication(s)"). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC takes no position concerning the evidence, validity or applicability of any claimed patent rights in
respect thereof. As of the date of publication of this document, IEC had not received notice of (a) patent(s), which
may be required to implement this document. However, implementers are cautioned that this may not represent
the latest information, which may be obtained from the patent database available at https://patents.iec.ch. IEC
shall not be held responsible for identifying any or all such patent rights.
IEC TR 61850-90-22 has been prepared by IEC technical committee 57, Power systems
management and associated information exchange. It is a Technical Report.
The text of this Technical Report is based on the following documents:
Draft Report on voting
57/2692/DTR 57/2737/RVDTR
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this Technical Report is English.

– 8 – IEC TR 61850-90-22:2024 © IEC 2024
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
A list of all parts in the IEC 61850 series, published under the general title Communication
networks and systems for power utility automation, can be found on the IEC website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
• reconfirmed,
• withdrawn, or
• revised.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.

INTRODUCTION
As an international standard, IEC 61850 currently serves thousands of substations around the
world. Meanwhile, SCD configuration is subject to changes that could be brought up by retrofit,
addition or removal of IED(s), etc., and the configuration of bridges needs to be updated
accordingly. The procedures of these works have always relied on manual approaches.
Some questions raised naturally are the following.
– How does a bridge in the substation network update its configuration (e.g. VLAN setting)
dynamically in case of SCD changes?
– How does a GOOSE/SV path rebuild automatically following the SCD update instead of
being done manually?
– How does the bridge learn that a newly added IED is connected to it?
– How does a bridge discover the change in case of substation network connectivity changes?
These questions are the drivers to set up a Task Force to investigate the above questions and
develop IEC TR 61850-90-22. These issues were demonstrated, gaps were identified,
requirements were analysed and use cases are described in this document, which is a Technical
Report.
To address these, the concept of auto-routing is introduced in this document.
At present, auto-routing is a system-level functionality of substation network performing through
a combination of a variety of advantages of AR-Bridges as specified in this document. AR-
Bridges could provide sophisticated function compared with IEC 61850 bridges that are
employed in existing network systems. Auto-routing is an independent functionality and can co-
exist with HSR/PRP and RSTP within a network.
The recovery time of auto-routing network is not addressed in this document. The key reason
for this is that the system or AR-bridge should take out of service for the testing of the
functionality after distribution or updating of the new SCD.

– 10 – IEC TR 61850-90-22:2024 © IEC 2024
COMMUNICATION NETWORKS AND SYSTEMS
FOR POWER UTILITY AUTOMATION –

Part 90-22: SCD based substation network automated management with
visualization and supervision support

1 Scope
This part of IEC 61850, which is a Technical Report, aims to provide analysis, principles, use
cases and guidance on how to use GOOSE/SV static-routing or auto-routing based on System
Configuration Description (SCD) file to automated manage the substation network while without
changing the requirements of IEDs. Furthermore, this document also intends to give novel
practices on network and GOOSE/SV path condition monitoring which support visualization and
supervision from higher level application side.
Using the concepts developed in the IETF's Transparent Interconnection of Lots of Links (TRILL)
using IS-IS protocol that is defined in RFC 6326 and ISO/IEC 10589 standards, this document
defines network and system management data object models that are specific to power system
operations. These data objects will be used to monitor the health of networks and systems, to
detect abnormal behaviours of IEDs which contradict SCD file, such as unexpected IEDs or
unexpected GOOSE/SV flows, and to support the management of the performance and
reliability of the information infrastructure.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 61850 (all parts), Communication networks and systems for power utility automation
IEC 62351 (all parts), Power systems management and associated information exchange –
Data and communications security
IEC 62351-7:2017, Power systems management and associated information exchange – Data
and communications security – Part 7: Network and System Management (NSM) data object
models
IEC TR 62351-90-3:2021, Power systems management and associated information exchange
– Data and communications security – Part 90-3: Guidelines for network and system
management
IEC 62439-1, Industrial communication networks – High availability automation networks –
Part 1: General concepts and calculation methods
IEC 62439-3:2021, Industrial communication networks – High availability automation networks
– Part 3: Parallel Redundancy Protocol (PRP) and High-availability Seamless Redundancy
(HSR)
IEC 62443 (all parts), Security for industrial automation and control systems

IEEE Std 802.1AB™, IEEE Standard for local and metropolitan area networks – Station and
Media Access Control Connectivity Discovery
IEEE Std 802.1D™, IEEE Standard for local and metropolitan area networks –Media Access
Control (MAC) Bridges
IEEE Std 802.1Q™, IEEE Standard for local and metropolitan area networks – Bridges and
bridged networks
IETF RFC 6325, Routing Bridges (RBridges): Base Protocol Specification
IETF RFC 6326, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms and definitions given in IEC TR 61850-90-4 and
the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1 Terms and definitions
3.1.1
GOOSE/SV auto-routing
method of dynamic building of GOOSE/SV paths using VLAN/MAC tables in bridges, according
to GOOSE/SV association together with the outcome from network topology discovery and IED
learning, abbreviated as auto-routing in this document
3.1.2
GOOSE/SV static-routing
method of static building of GOOSE/SV paths using VLAN/MAC table in bridges according to
the information defined in SCD file, abbreviated as static-routing in this document
3.1.3
AR-bridge
AutoRouting-bridge
bridge with sophisticated function extended from IEC 61850 bridge, that is the fundamental
device or component to approach the performance of substation network auto-routing
3.1.4
AR-bridge neighbour
node that physically connects to the AR-bridge, and responds to the information it is advertising
3.1.5
bridge
network device that connects network segments at the data link layer (layer 2) of the OSI model,
according to the principles of IEEE 802-2014
Note 1 to entry: A bridge is often referred to as a "layer 2 switch". In this document, the word "bridge" means the
logic used to forward a frame from one port to another at layer 2, while "switch" designates a device with additional
functionalities.
Note 2 to entry: In case of confusing with primary switch, bridge is used to represent switch in this document.
[SOURCE: IEC TR 61850-90-4:2020, 3.1.1, modified (addition of Note 2 to entry)]

– 12 – IEC TR 61850-90-22:2024 © IEC 2024
3.1.6
diagnostic device
device/software that can capture arbitrary IEC 61850 packets, analyse the contents of packets,
and reveal the transmission behaviour of packets
3.1.7
IEC 61850 bridge
subset of the IEEE 802.1 options with extensions defined in IEC 61850-8-1 and
IEC TR 61850-90-4
Note 1 to entry: With the following functionality:
– A bridge port operates in full-duplex mode.
– A bridge supports loop prevention only through RSTP/MSTP; Compatible variants offered by vendors to speed
up recovery are allowed, although the claimed performance is usually only achieved within a one-vendor
environment.
– A bridge keeps MAC address filtering always enabled. The lifetime of a filtering database entry is limited to 10
seconds (IEEE 802.1Q recommends 300,0 s).
– A bridge supports VLAN traffic filtering, but contrarily to IEEE 802.1Q, an egress port may send a frame with
VLAN ID = 0, although this practice is deprecated.
– A bridge (edge) port may forward frames with different VLAN ID to an end device (thus behaving as a trunk port).
A bridge port is not obliged to remove the VLAN tags. Contrarily to the intention of VLANs, end devices may be
attached simultaneously to several VLANs, but ignore the VLAN header.
– A bridge port accepts VLAN-tagged frames from an end device even when they do not match its default VLAN-
ID.
– A bridge supports frames of at least 1 522 octets to allow redundancy control in HSR or PRP, support of up to 1
535 octets is recommended. Jumbo frames are not used.
– A bridge may start transmission of a frame over the egress port while the frame over the ingress port has not
been completely received ("cut-through"), although IEEE 802.1 only allows sending after the frame has been
completely received ("store-and-forward").
– A bridge acting as a Transparent Clock for the Precision Time Protocol modifies the time stamp in the frame
body, but it is not allowed to modify the source address, contrarily to the debated IEEE 802.1 rule.
– A bridge supports network management by IEC 61850-90-4 especially for the purpose of ports and RSTP
settings, VLAN and priorities settings and multicast filtering.
3.1.8
IED-learning
mechanism that learns by bridges of the port that IEDs are connected to by detecting the unique
identity (for instance MAC, APPID, or a combination of elements) of GOOSE/SV packets, and
mapping between them and the IED name, which are extracted from SCD file, similar to the
MAC address learning
3.1.9
GOOSE/SV association
relation expressed in an SCD file between an IED (serving a data by publishing a GOOSE/SV
control block containing this data in its dataset) and one or more IEDs (consuming this specific
data by subscribing the GOOSE/SV)
Note 1 to entry: The consumption of this data by the IED subscribing to the GOOSE/SV is described by an ExtRef
in the consuming IED referencing the data and the GOOSE/SV carrying the data.
3.1.10
GOOSE/SV path
GOOSE/SV multicast distribution tree created in substation network to implement GOOSE/SV
association, rooted at source port of a GOOSE/SV packet from one publisher, ended at
destination ports of all subscribers, including intermediate bridges
3.1.11
GOOSE/SV simulator
device/software that generates simulated GOOSE/SV packets for a given existing frame

3.1.12
maintentance plane
working plane
logical independent virtual working area created by an AR-bridge for IEDs in testing mode or
related
...