ES2827206T3 - System and procedure for configuring process bus network switches of intelligent electronic devices from a substation topology specification - Google Patents

Abstract

Procedure to obtain a configuration file of intelligent electronic device, IED, Process Bus network switch filtering rules from a substation specification according to the IEC 61850 standard, comprising the steps of: calculating, from a substation topology file, a control functions library file and a substation bay library file, a substation specification description file, and a substation traffic demand flow files comprising a GOOSE message profile subscription file and a Sampled Values message profile subscription file; generating destination MAC addresses; characterized by the fact that the procedure further comprises: simulating the Process Bus communications network using said substation traffic demand flow files and the topology of the Process Bus communications network, said topology comprising said switches of the Process Bus network, respective links and IED device links; calculating the shortest path between each publisher IED device and each subscriber IED device; calculating a switch multicast filter rules file, for each switch output port, comprising a multicast MAC address filter rule allowing the calculated shortest paths.

Description

DESCRIPTION

System and procedure for configuring process bus network switches of intelligent electronic devices from a substation topology specification

Technical field

This disclosure refers to a system and procedure for configuring switches, and optionally intelligent electronic devices (IED: Intelligent Electronic Devices), of a Process Bus network for IEDs (intelligent electronic devices) from a substation specification, which includes a substation topology specification, according to the IEC 61850 standard.

Background

The IEC 61850 standard is a standard for vendor agnostic engineering of an intelligent electronic device (IED) configuration so that electrical substation automation systems can communicate with each other. The IEC 61850 standard is part of a reference architecture of Technical Committee 57 (TC57) of the International Electrotechnical Commission (IEC) for electrical power systems and can be obtained, for example, from http://www.iec.ch . The same applies to the IEC 61869-9 standard. The referenced standards are found in the versions:

IEC 61850-8-1, "Communication Networks and systems for power utility automation - Part 8-1: Specific communication service mapping (SCSM) - Mapping to MMS (ISO 9506-1 and ISO 9506-2) and to ISO / IEC 8802 -3 ", Edition 2.0, 6/2011;

IEC 61850-9-2, "Communication networks and systems for power utility automation - Part 9-2: Specific communication service mapping (SCSM) - Sampled values over ISO / IEC 8802-3", Edition 2.0, 9/2011; IEC 61869-9, "Instrument transformers Part 9: Digital interface for instrument transformers", Edition 1.0, 4/2016;

that is, the IEC 61850 standard is like the IEC 61850-8-1 standard and the IEC 61850-9-2 standard both in version 2.0, and the IEC 61869-9 standard in version 1.0.

The abstract data models defined in the IEC 61850 standard can be mapped to a number of protocols. Current mappings in the standard include a Generic Object Oriented System Event (GOOSE). These protocols can work on TCP / IP networks or on substation LANs using high-speed switched Ethernet to obtain the response times necessary for safe and efficient substation operation. In particular, the IEC 61850 standard describes critical Ethernet traffic profiles used by Protection Automation and Control (PAC) devices, intelligent electronic devices (IEDs), in order to control and protect power systems. . These IED devices are typically found in substations, power generation plants, and industrial plants.

Two critical Ethernet traffic profiles are defined: the Generic Object Oriented Substation Event (GOOSE) message profile, according to the IEC 61850 - 8 standard, and the Sampled Values (SV : Sampled Values) according to the IEC 61869-9 standard. The former is especially used to transmit time-critical information, such as open or close commands to High Voltage Circuit Breakers, while the latter is normally used to transmit analog current and voltage measurements.

Critical Ethernet traffic is carried on a dedicated Ethernet network called the Process Bus. Process Bus communication is largely based on multicast transmission at the Ethernet protocol layer by means of a destination media access control address, MAC (Media Access Control) address, included in packets. Ethernet. This destination MAC address is a multicast MAC address and therefore the Process Bus communication is very inefficient as each message is forwarded to all IED device interfaces, including non-subscribers. of messages.

The division of traffic on the Process Bus plays an important role, due to the strong real-time requirements for GOOSE and Sampled Values traffic. One of the most efficient ways to achieve traffic division is through static multicast filtering on the Ethernet switches that connect the various devices together on a network.

When using multicast filtering, each switch only allows outgoing traffic from a specific port if the corresponding destination MAC address is part of a filtering rule included in its internal multicast filtering whitelist, MFWL (Multicast Filtering White List), otherwise the traffic is blocked. Multicast filtering is crucial to reduce Process Bus bandwidth traffic and IED device communications processing requirements when too many multicast messages are received.

When a traffic division is applied in the Process Bus, by means of multicast filtering, the performance of the communications network reaches a highly deterministic behavior, perfectly describing a result of all the traffic flow in each Ethernet link, in with regard to flow rate and traffic profile. This information is used at the switch level to inspect incoming packets and define and enforce traffic monitoring rules based on priority reclassification and / or packet loss.

The correct operation of an IED device is highly dependent on the configuration of multicast filtering whitelists on the switches, so it is very important to use a robust and error-free configuration process.

Setting up an Ethernet communications network with multicast filtering on Ethernet switches is a complex task. This is due to the need to produce a large number of MFWLs (one list for each switch port), for application to Ethernet switches that are part of the Process Bus network.

If the process of configuring multicast filtering and all required MFWLs is done manually on each switch, it would be very labor intensive, time consuming, and have a high probability of failure. It is not possible to do this configuration using Substation Configuration Language (SCL) files, which are described in the IEC 61850 standard, because these files do not include the description of the communications network, that is, the topology and the link bandwidth.

Although the .SCL files include the description of all the critical messages that are exchanged between PAC devices, the tools used to produce these files do not contain the communications topology of the Process Bus network, that is, the number of switches and how they are linked to each other and to the existing IED device, nor are they capable of bridging between the multicast filtering settings and the destination MAC address information included in the .SCL file.

However, the SCD file can be used to establish publisher / subscriber traffic profile IED device pairs, although this is only available at the system deployment stage as actual IED devices are required for their generation. This is inconvenient, as the design and specification of the Process Bus network is preferably done prior to system deployment.

Document CN102368715 discloses a gateway-based implementation of the IEC-61850 protocol for centralized management of the exchanger network. The implementation equipment comprises a Simple Network Management Protocol (SNMP) server, an SNMP client, a client according to the IEC-61850 standard, a server according to the IEC-61850 standard and a gateway protocol that is formed by mapping management information between the SNMP client and the server according to the IEC-61850 standard. The SNMP server is used to provide an exchange management information node for an SNMP client protocol data message; the SNMP client obtains management information from an exchanger SNMP management information base (MIB) according to the SNMP client protocol data message; After the protocol gateway has obtained the management information, the management information is mapped into a management information model according to the IEC-61850 standard of the server according to the IEC-61850 standard and thus is forms a server data source according to the IEC-61850 standard; and the client according to the IEC-61850 standard communicates with the server according to the IEC-61850 standard by means of an IEC-61850 standard, so that the exchanger is controlled and managed.

Document CN102368715 however requires a permanent SNMP server to provide network management of the network exchangers.

Document EP1976218 refers to substation automation systems (SAS), in particular to a procedure and system for configuring an intelligent electronic device (IED) that complies with the 61850 standard of the International Electrotechnical Commission (IEC). The IED proxy device is a gateway device for NCC improved for data conversion between communication protocols according to the IEC 61850 standard and according to a standard other than IEC 61850. The IED proxy device is configured, based on a set of mappings, which they are encoded in the SA configuration description file (SCD: SA configuration description). The SCD file includes some mappings for data conversion between communication protocols according to the IEC 61850 standard and according to a standard other than IEC 61850.

Document EP1976218, however, uses information from SCD files to create a network mapping, so it does not take into account the communication network topology of the Process Bus in said mapping.

The document SIVANTHI THANIKESAVAN ET AL: "Systematic real-time traffic segmentation in substation automation systems", 2013 IEEE 18th CONFERENCE ON EMERGING TECHNOLOGIES & FACTORY AUTOMATION (ETFA), IEEE, September 10, 2013 (2013-09-10), pages 1 -4, XP032517053, ISSN: 1946-0740, DOI: 10.1109 / ETFA.2013.6648113, on which the preamble of claim 1 is based, refers to a multicast traffic segmentation to avoid an overload of end devices that do not subscribe to traffic. Traffic can be segmented based on multicast and VLAN network address filters. This document presents a systematic approach to derive the appropriate multicast and VLAN network address filter settings for Ethernet switches in the substation. Derived switch filter settings ensure that traffic reaches only your subscribers and therefore proper operation of the substation automation system.

Document EP2916491A1 refers to a time-critical message transmission procedure in an OSI layer 2 network tunnel from an IED device in a first substation to an IED device in a second substation through a WAN network, in that each of the first and second substations comprises an edge IED device and is associated with a LAN network substation, in which each of the time-critical messages comprises message parameters. The procedure comprises the steps of: a) creating a translation table comprising corresponding values of the message parameters, between the LAN networks and the WAN network, b) defining a virtual IED device model in the second substation using the values translated messages of the message parameters, to impersonate the IED device of the first substation, c) translate the message parameters according to the translation table, d) send the critical messages in time from the IED device of the first substation to the WAN network, and e) receive time-critical messages from the IED device of the second substation from the WAN network.

The document INGALALLI ARAVIND ET AL: "SCD based IEC 61850 traffic estimation for substation automation networks", 2017 22ND IEEE INTERNATIONAL CONFERENCE ON EMERGING TECHNOLOGIES AND FACTORY AUTOMATION (ETFA), IEEE, September 12, 2017 (2017-09-12), pages 1 - 8, XP033292930, DOI: 10.1109 / ETFA.2017.8247596 refers to the IEC 61850 standard. This is a communication standard for SAS for data transmission within and between a station level, bay level and process level. The standard defines both the information model and the services used for communication between smart electronic devices (IDEs) in a substation. The information model can be mapped with application protocols such as MMS, GOOSE, SV, of which GOOSE and SV messages are time-critical and use Layer 2 of the Open Systems Interconnection model (OSI: Open Systems Interconnection ). The IEC 61850 standard also defines a substation configuration description (SCD), which defines the substation model, the IED equipment model, and the communication network model.

These facts are disclosed in order to illustrate the technical problem on which the present disclosure focuses.

General description

The disclosed general configuration process workflow is capable of specifying to configure GOOSE Critical Ethernet traffic profile settings and Sampled Values, on both publisher and subscriber IED devices, to produce all MFWL lists for configuring switches to divide traffic through Ethernet filtering and define traffic monitoring rules applicable at the switch level. Additionally, the disclosed general setup process workflow reduces the human intervention required throughout this process.

A procedure is disclosed to obtain a configuration file for filtering rules for Process Bus network switches of intelligent electronic devices, IEDs, from a substation specification according to the IEC 61850 standard, comprising the stages of:

calculate, from a substation topology file, a control function library file, and a substation bay library file, a substation specification description file, and demand flow files from substation traffic comprising a GOOSE message profile subscription file and a Sampled Values message profile subscription file;

generating destination MAC addresses;

simulate the Process Bus communications network using said substation traffic demand flow files and the Process Bus communications network topology, said topology comprising said Process Bus network switches, respective links and IED device links;

calculating the shortest path between each publisher IED device and each subscriber IED device; calculating a switch multicast filter rules file, for each switch output port, comprising a multicast MAC address filter rule allowing the calculated shortest paths.

A procedure is also disclosed to configure process bus network switches of intelligent electronic devices, IEDs, from a substation specification according to the IEC 61850 standard, which comprises the stages of:

calculate, from a substation topology file, a library of protection, automation and control functions and a library of substation bays, a substation specification description file, and a substation flow files. substation traffic demand comprising a GOOSE message profile subscription file and a Sampled Values message profile subscription file;

generating destination MAC addresses;

simulate the Process Bus communications network using said substation traffic demand flow files and the Process Bus communications network topology, said topology comprising said Process Bus network switches, respective links and IED device links;

calculating the shortest path between each publisher IED device and each subscriber IED device; calculating a switch multicast filter rule file, for each switch output port, comprising a multicast filter rule allowing the calculated shortest paths;

translating the switch multicast filter rules file into a file that follows the structure accepted by the network switch, comprising an algorithm to perform this translation for each network switch model of each switch manufacturer;

defining traffic monitoring rules for each switch port of the network, which comprises calculating a bandwidth used in each switch port of the network for each type of communication.

One embodiment comprises translating the switch multicast filter rules file into a file format acceptable to each switch in the Process Bus network.

An embodiment comprises a step of performing said translation for each switch model / manufacturer combination of the Process Bus network.

In one embodiment, the library of control functions comprises protection, automation and control functions.

An embodiment of the disclosure, in which simulating the Process Bus communications network further comprises simulating the profile of bandwidth utilization and traffic flow on each communications link, comprising the step of calculating for each port switch output the bandwidth used, for each type of traffic (GOOSE and Sampled Values) both in steady state and during an event in which an increase in used bandwidth is expected. With the results and some parameters defined by a user, one or more traffic monitoring rules are defined, said traffic monitoring rules in particular comprising a priority reclassification monitoring rule and / or a packet loss monitoring rule. .

In one embodiment, the files of the library of protection, automation and control functions and of the library of substation bays comprise standardized primary equipment name templates, PAC functions, logical nodes and, in particular, corresponding objects data, according to the IEC 61850 standard, virtual IED devices and corresponding demands for publishing and subscribing critical traffic profiles.

In one embodiment, computing a substation specification description file comprises instantiating substation bays, instantiating substation IED devices, instantiating substation PAC functions, and instantiating substation critical traffic profiles according to IEC 61850 standard, wherein said instantiation processes comprise specifying, for said substation topology, all the PAC functions and corresponding IED devices that are required by each substation bay according to said templates.

In one embodiment, generating the destination MAC addresses comprises the steps of: using said substation topology, said instantiated bays, and said instantiated IED devices; instantiate GOOSE and Sampled Values traffic according to the IEC 61850 standard and the IEC 61869-9 standard respectively;

calculating traffic destinations from said instantiated critical traffic profiles;

provide an available MAC address, for each calculated traffic destination, within a group of MAC addresses corresponding to a traffic flow according to the IEC 61850 standard.

One embodiment comprises the step of configuring said switches using said switch multicast filter rule calculated file in a compatible format to be imported into the switches of the network.

In one embodiment, any file among such files is a Comma Separated Value (CSV) file or any combination of files of such files are CSV type files. Alternatively, an alternative embodiment uses XML.

In one embodiment, the GOOSE message profile subscription file comprises a GOOSE publisher / subscriber pair and corresponding traffic parameters, comprising for each record of said file:

an identifier of the published GOOSE profile;

a name of the subscriber IED device;

GOOSE message type - type corresponds to a message with a defined packet size in bytes;

the destination MAC address;

a VLAN identifier;

a VLAN network priority;

a heartbeat interval T0;

according to IEC 61850 standard.

In one embodiment, the Sampled Values message profile subscription file comprises a publisher / subscriber pair of Sampled Values and corresponding traffic parameters, comprising for each record of said file:

an identifier of the published Sampled Values;

a name of the subscriber IED device;

the type of Sampled Values message;

the destination MAC address;

a VLAN identifier;

a VLAN priority.

In one embodiment, the switch multicast filter rules file comprises for each record in said file: Switch identifier;

switch port number;

multicast MAC address.

In one embodiment, the generation of destination MAC addresses comprises obtaining a MAC address allocation file comprising for each record of said file: publishing IED device name;

traffic profile according to the IEC 61850 standard to which the MAC value belongs;

an identifier of the published GOOSE or Sampled Value profile;

multicast MAC address.

Also disclosed is a procedure for configuring a process bus network of substation IED devices comprising the procedure for obtaining a configuration file of filter rules for process bus network switches of IED devices of any one of the forms of described embodiment, further comprising the step of configuring said switches using said switch multicast filter rule calculated file.

An embodiment comprises the step of configuring said IED devices with the destination MAC addresses generated using the Substation Configuration Description file.

An embodiment comprises the step of importing the MAC attribution file into a system configuration tool, and further comprising the step of configuring said IED devices with the destination MAC addresses generated using the substation configuration description file. exported by the system configuration tool.

A system for configuring process bus network switches of intelligent electronic devices, IEDs, is also disclosed based on a substation specification according to the IEC 61850 standard, comprising a data processor and a respective memory, said data processor being willing to perform any of the disclosed procedures.

Non-transient storage media that includes program instructions to implement a system to configure Process Bus network switches of intelligent electronic devices, IEDs, from a substation specification according to the IEC 61850 standard, including the program instructions executable instructions to perform any of the disclosed procedures.

Brief description of the drawings

The following figures provide preferred embodiments to illustrate the description and should not be construed as limiting the scope of the invention.

Figure 1A: Schematic representation of an embodiment of the general configuration process workflow according to the disclosure.

Figure 1B: Schematic representation of a more specific alternative of the general configuration process workflow embodiment according to the disclosure.

Figure 2: Example of an embodiment of an .MFRS file that follows a manufacturer-specific format after a translation of an .MFR file.

Figure 3: Schematic representation of an implementation of requests for publication and subscription of critical traffic profiles of IED devices according to the disclosure.

Figure 4: Schematic representation of an embodiment of Process Bus network switches of IED devices according to the disclosure.

Detailed description

The general configuration process workflow begins with the definition of a library of protection, automation and control functions 1 and a library of substation bays 2, see Figure 1A. These libraries contain substation bay templates and functions used in the general configuration process workflow. The templates include standardized primary equipment names, PAC functions, logical nodes according to the IEC 61850 standard, virtual iEd devices, and corresponding critical traffic profile publishing and subscription demands.

The process also requires that the information on the topology of substation of interest 3 be combined with the existing libraries, instantiate the bays of substation 4, instantiate the IED devices of substation 5, instantiate the PAC functions of substation 6 and instantiate the critical traffic profiles of the substation 7. The instantiation process consists of specifying for the topology of the substation of interest, all the PAC functions and corresponding IED devices that are required for each bay of the substation according to these templates. Critical traffic profiling instantiation considers the use of a destination MAC address generator 8. The generator assumes the topology of the substation, the instantiated bays and the IED device and instantiates the GOOSE and Sampled Values traffic, checking the destination of the traffic and providing an available MAC address according to the MAC address group to which the traffic flow belongs, as recommended in the IEC 61850 standard.

The instantiations can be carried out by a single software tool, hereinafter referred to as the system specification tool 9, or by several tools that are combined with each other for the same purpose. For example, the instantiation of the bays, IED device and PAC function can be done with the same IT tool, but the instantiation of the traffic profiles can be done with a different IT tool.

The output of the system specification tool is the substation specification description file (.SSD) 10, and the substation traffic demand flow files. The first, according to the IEC 61850 standard, specifies the data models used for the purchase of IED devices. The second lists all critical traffic, from GOOSE and SV (Sampled Values), that will exist at the substation of interest using two files: the GOOSE subscription file (.GOS) 11 and the SV subscription file (.SVS ) 12.

In the GOOSE subscription file each line describes a publisher / subscriber pair and the traffic parameters. The file is a columnar CSV file with the following information:

GOOSE Identifier: The (encoded) name of the published profile

Subscriber IED device: The (encoded) name of the subscriber IED device

GOOSE message type - a type corresponds to a message with a packet size defined in bytes

Destination MAC address

VLAN identifier

VLAN network priority

Heartbeat interval T0

An example of the content of the .GOS file is presented in Table 1.

In the SV subscription file (.SVS) each line describes a publisher / subscriber pair and corresponding traffic parameters. The file is a columnar CSV file with the following information:

Sampled Values Identifier: The (coded) name of the published Sampled Values Subscribing IED Device: The (coded) name of the subscribing IED device

SV message type (Sampled Values)

Destination MAC address

VLAN identifier

VLAN network priority

An example of the content of the .SVS file is presented in Table 2.

Once the IED devices 13 to be deployed in the substation have their data model according to the .s Sd file, they generate an IED device configuration description (.ICD) file 14 used by a system configuration tool 15 to mapping between the logical nodes, specified in each instantiated IED device, and the existing nodes in the data model of the real IED device.

The system configuration tool generates the final configuration file necessary to properly configure all IED 13 devices within the substation, that is, the substation configuration description file (.SCD) 16. This file includes the configuration of the entire substation and is loaded into each of the IED devices.

Regarding the configuration of the multicast filtering rules on the substation switches, it is done using the .GOS and .SVS file (11, 12). The files are used in a simulation tool for information and communications technology (ICT: Information and Communications Technology) 17 that is capable of simulating all the existing traffic profiles on the Process Bus. The tool requires a description of the communications topology of the network 18, that is, the number of switches, how they are linked to each other and to the existing IED devices.

The simulation is complete, in terms of connections, because during an initialization stage all publishers initially broadcast their services and each subscriber requests the desired services, thus obtaining a complete characterization of the active connections during this initialization simulation stage. of the substation.

By following the shortest path between each publisher and subscriber IED device, the tool is able to define multicast filter rules on switch port outputs and produce the required MFWL for each switch and for each port. Finally, these rules are included in the multicast filtering rule files (.MFR) 19 that are assigned to each switch on the LAN for configuration. The file is a columnar CSV file with the following information:

Switch identifier

Switch port number

Multicast MAC address

An example of the content of the .MFR file is presented in Table 3.

The ICT simulation tool is also capable of characterizing the expected bandwidth utilization and the traffic profile on each communication link, which is used to define Traffic 20 monitoring rules on each switch port based on a reclassification of priorities and / or packet loss.

Finally, the substation switches 21 are configured according to the generated .MFR files and the defined traffic monitoring rules.

A more specific workflow embodiment alternative is also considered in Figure 1B. This alternative follows the setup process workflow described above, but adds some files that may improve the process. The first change is the introduction of the MAC Address Allocation (.MAC) file 10A, which is a file that lists the MAC addresses allocated to each GOOSE or SV profile.

In the MAC address allocation file each line describes the MAC address provided by destination MAC address generator 8 to each of the GOOSE and Sampled Values profiles. The file is a columnar CSV file with the following information: Publishing IED device name;

Traffic profile according to the IEC 61850 standard to which the MAC value belongs;

An identifier of the published GOOSE or Sampled Value profile;

Multicast MAC address.

An example of the content of the .MAC file is presented in Table 4.

Also provided in the alternative embodiment of the workflow is a translation tool 19A, which takes the .MFR 19 file into a file in a format compatible with each network switch model of each switch manufacturer: the filtering rules Multicast Switch (.MFRS) 19B.

The format of the .MFRS file varies from manufacturer to manufacturer. An example of such a file is presented in Figure 2.

Ultimately, a consistent configuration is achieved between the PAC devices and the Process Bus switches.

Advantageously, the simulation can also be used as a normal substation simulation, simply continuing after said initialization stage. For example, traffic and loads can be simulated and the project can be adjusted by the human operator. As the computing workload to initialize the simulation and the human workload to establish the simulation environment have already been performed, in practice this is a "free" execution of the simulation setup.

Furthermore, the simulation can also be used to statistically characterize critical network traffic delays for each profile, under steady state conditions and during the occurrence of a disturbance that causes IED devices to generate traffic according to their configurations.

The simulation stage is suitably accurate, so that the generated switching fabric is also correspondingly accurate, which ensures that the allowed connections between network devices will be necessary and sufficient for the operation of the substation.

It should be noted that the format of any one or more of the aforementioned files can be of the CSV type or any other suitable format such as a binary file, an XML file, a JSON file, among others, since the CSV type is a from among various possibilities.

Examples of preferred embodiments

Consider a PAC system composed of 4 IED devices, in which two of them are publishers, IED devices 1 and 2, and two are subscribers, IED devices 3 and 4. All communications will take place in VLAN 1234 with priority 7.

The instantiation process of this system, carried out by the system specification tool, has produced a flow of traffic demand between IED devices that is described in Figure 3 and the corresponding list of published messages that is presented in Table 5. The destination MAC addresses shown in Table 4 are outputs from the destination MAC address generator. The system configuration tool is used to configure the IED devices using the produced .SSD and .MAC files and the following process steps (10, 11, 14, 15, 16 and 17). The tool also produces the .MAC, .GOS and .SVS files that are presented in Tables 6, 7 and 8. Consider the Process Bus network topology applied to connect the four IED devices and presented in Figure 4 This network comprises two switches with 3 ports each. The ICT simulation tool uses this topology, combined with the .GOS and .SVS files, to generate the corresponding .MFR files for each switch, Tables 9 and 10. The .MFR files are finally used to configure switches 1 and 2 .

The IED devices and the Process Bus switches are now configured consistently. The term "comprises", when used herein, is intended to indicate the presence of indicated features, integers, stages, components but not to prevent the presence or aggregation of one or more features, integers, stages, components, or groups of them.

Flow charts of particular embodiments of the procedures described in this disclosure are represented in figures. The flow charts do not represent any particular medium, but rather the flow charts illustrate the functional information required by a person skilled in the art to perform said required procedures in accordance with the present disclosure.

Those skilled in the art will appreciate that, unless otherwise indicated herein, the particular sequence of steps described is illustrative only and may be varied without departing from that divulgation. Thus, unless otherwise indicated, the described steps are out of order so that, when possible, the steps can be performed in any convenient or desirable order.

It should be appreciated that certain embodiments of the disclosure as described herein may be incorporated as code (eg, an algorithm or software program) that resides in firmware and / or on a usable medium by a computing device that it has a control logic to allow execution on a computer system that has a computer processor, such as any of the servers described in this document. Such a computer system typically includes memory storage configured to provide code execution output that configures a processor according to execution. The code can be arranged as firmware or software, and can be arranged as a set of modules, which includes the various modules and algorithms described herein, such as discrete code modules, function calls, procedure calls, or objects in an object-oriented programming environment. If implemented using modules, the code may comprise a single module or a plurality of modules that operate cooperatively with each other to configure the machine on which it runs to perform associated functions, as described herein.

The disclosure should in no way be viewed as restricted to the embodiments described and one skilled in the art will envision many possibilities for modifications thereof.

The embodiments described above are combinable. The following claims further set forth particular embodiments of the disclosure.

Claims (15)

1. Procedure to obtain a configuration file of intelligent electronic device, IED, Process Bus network switch filtering rules, from a substation specification according to the IEC 61850 standard, comprising the stages of: calculate from a substation topology file, a control function library file and a substation bay library file, a substation specification description file, and demand flow files substation traffic data comprising a GOOSE message profile subscription file and a Sampled Values message profile subscription file; generating destination MAC addresses; characterized by the fact that the procedure further comprises: simulate the Process Bus communications network using said substation traffic demand flow files and the Process Bus communications network topology, said topology comprising said Process Bus network switches, respective links and IED device links; calculating the shortest path between each publisher IED device and each subscriber IED device; calculating a switch multicast filter rules file, for each switch output port, comprising a multicast MAC address filter rule allowing the calculated shortest paths. 2. Procedure for obtaining a configuration file for filter rules of Process Bus network switches of IED devices according to the preceding claim, in which simulating the Process Bus communications network further comprises simulating the use of bandwidth and the traffic profile on each communication link, further comprising the step of calculating for each switch output port one or more traffic monitoring rules, said traffic monitoring rules in particular comprising a reclassification monitoring rule of priorities and / or a packet loss monitoring rule. 3. Method for obtaining a configuration file of IED device Process Bus network switch filter rules according to any one of the preceding claims, comprising translating the switch multicast filter rules file into a file format acceptable for each switch in the Process Bus network. 4. Procedure for obtaining a configuration file of IED device Process Bus network switch filter rules according to the preceding claim, comprising a step of performing said translation for each Bus network switch model / manufacturer combination of Processes. 5. Method for obtaining a configuration file for IED device Process Bus network switch filtering rules according to any one of the preceding claims, wherein the library of control functions comprises protection, automation and control functions. 6. Method for obtaining a configuration file for filter rules for Process Bus network switches of IED devices according to any one of the preceding claims, in which the substation bay and control functions library files comprise templates of standardized primary equipment names, PAC functions, logical nodes and, in particular, corresponding data objects, according to the IEC 61850 standard, virtual IED devices and corresponding publication and subscription demands of critical traffic profiles. 7. Procedure for obtaining a configuration file of IED device Process Bus network switch filter rules according to any one of the preceding claims, wherein calculating a substation specification description file comprises instantiating bays of the substation, instantiate substation IED devices, instantiate substation PAC functions and instantiate substation critical traffic profiles according to the IEC 61850 standard, in which said instantiation processes include specifying, for said substation topology, all functions PAC and corresponding IED devices that are required for each bay of the substation according to these templates. 8. Procedure for obtaining a configuration file of IED device Process Bus network switch filter rules according to any one of the preceding claims, in which generating the destination MAC addresses comprises the steps of: use said substation topology, said instantiated bays, and said instantiated IED devices; instantiate GOOSE and Sampled Values traffic according to the IEC 61850 standard; calculating traffic destinations from said instantiated critical traffic profiles; provide an available MAC address, for each calculated traffic destination, within a group of MAC addresses corresponding to the traffic flow according to the IEC 61850 standard. 9. Procedure for obtaining a configuration file for filter rules for Process Bus network switches of IED devices according to any one of the preceding claims, wherein any file among said files is a CSV file or any combination of files of such files are files of type CSV, or in which any file of such files is an XML file or any combination of files of such files are XML files. 10. Method for obtaining a configuration file of IED device Process Bus network switch filter rules according to any one of the preceding claims, wherein the GOOSE message profile subscription file comprises a publisher / GOOSE subscriber and corresponding traffic parameters, comprising for each record of said file: an identifier of the published GOOSE profile; a name of the subscriber IED device; the GOOSE message type; the destination MAC address; a VLAN identifier; a VLAN network priority; a heartbeat interval T0; according to IEC 61850 standard. 11. Method for obtaining a configuration file for IED device Process Bus network switch filtering rules according to any one of the preceding claims, wherein the Sampled Values message profile subscription file comprises a publisher pair / subscriber of Sampled Values and the corresponding traffic parameters, which comprise for each record of said file: an identifier of the published Sampled Values; a name of the subscriber IED device; the type of Sampled Values message; the destination MAC address; a VLAN identifier; Y where the switch multicast filter rules file comprises for each record in said file: switch identifier; switch port number; multicast MAC address; Y in which the generation of destination MAC addresses comprises obtaining a MAC address allocation file, which comprises for each record of said file: multicast MAC address value; publishing IED device name; traffic profile according to the IEC 61850 standard to which the multicast MAC address value belongs; an identifier of the published GOOSE or Sampled Value profile. 12. Procedure for configuring a process bus network of substation IED devices comprising the procedure for obtaining a configuration file of filter rules for process bus network switches of IED devices of any one of the preceding claims, which it further comprises the step of configuring said switches using said switch multicast filter rule calculated file. 13. Procedure for configuring a Process Bus network of substation IED devices according to the preceding claim, further comprising the step of importing the MAC attribution file into a system configuration tool. 14. System for configuring process bus network switches of intelligent electronic devices, IEDs, based on a substation specification according to the IEC 61850 standard, comprising a data processor and a respective memory, said data processor being arranged to performing the method of any one of the preceding claims. 15. Non-transient storage media that include program instructions to implement a system to configure process bus network switches of intelligent electronic devices, IEDs, from a substation specification according to the IEC 61850 standard, including the program instructions executable instructions to carry out the procedure of any one of claims 1-13.