Patent Application
20140280714
This disclosure relates to systems and methods for managing communication between devices of an electric power generation and delivery system, and more particularly, to systems and methods for facilitating mixed-mode communication between stations in an electric power generation and delivery system.
Non-limiting and non-exhaustive embodiments of the disclosure are described, including various embodiments of the disclosure with reference to the figures, in which:
The embodiments of the disclosure will be best understood by reference to the drawings. It will be readily understood that the components of the disclosed embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the systems and methods of the disclosure is not intended to limit the scope of the disclosure, as claimed, but is merely representative of possible embodiments of the disclosure. In addition, the steps of a method do not necessarily need to be executed in any specific order, or even sequentially, nor do the steps need be executed only once, unless otherwise specified.
In some cases, well-known features, structures, or operations are not shown or described in detail. Furthermore, the described features, structures, or operations may be combined in any suitable manner in one or more embodiments. It will also be readily understood that the components of the embodiments, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. For example, throughout this specification, any reference to “one embodiment,” “an embodiment,” or “the embodiment” means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Thus, the quoted phrases, or variations thereof, as recited throughout this specification are not necessarily all referring to the same embodiment.
Several aspects of the embodiments disclosed herein may be implemented as software modules or components. As used herein, a software module or component may include any type of computer instruction or computer executable code located within a memory device that is operable in conjunction with appropriate hardware to implement the programmed instructions. A software module or component may, for instance, comprise one or more physical or logical blocks of computer instructions, which may be organized as a routine, program, object, component, data structure, etc., that performs one or more tasks or implements particular abstract data types.
In certain embodiments, a particular software module or component may comprise disparate instructions stored in different locations of a memory device, which together implement the described functionality of the module. Indeed, a module or component may comprise a single instruction or many instructions, and may be distributed over several different code segments, among different programs, and across several memory devices. Some embodiments may be practiced in a distributed computing environment where tasks are performed by a remote processing device linked through a communications network. In a distributed computing environment, software modules or components may be located in local and/or remote memory storage devices. In addition, data being tied or rendered together in a database record may be resident in the same memory device, or across several memory devices, and may be linked together in fields of a record in a database across a network.
Embodiments may be provided as a computer program product including a non-transitory machine-readable medium having stored thereon instructions that may be used to program a computer or other electronic device to perform processes described herein. The non-transitory machine-readable medium may include, but is not limited to, hard drives, floppy diskettes, optical disks, CD-ROMs, DVD-ROMs, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, solid-state memory devices, or other types of media/machine-readable medium suitable for storing electronic instructions. In some embodiments, the computer or other electronic device may include a processing device such as a microprocessor, microcontroller, logic circuitry, or the like. The processing device may further include one or more special purpose processing devices such as an application specific interface circuit (ASIC), PAL, PLA, PLD, field programmable gate array (FPGA), or any other customizable or programmable device.
Electrical power generation and delivery systems are designed to generate, transmit, and distribute electrical energy to loads. Electrical power generation and delivery systems may include equipment, such as electrical generators, electrical motors, power transformers, power transmission and distribution lines, circuit breakers, switches, buses, transmission lines, voltage regulators, capacitor banks, and the like. Such equipment may be monitored, controlled, automated, and/or protected using intelligent electronic devices (IEDs) that receive electric power system information from the equipment, make decisions based on the information, and provide monitoring, control, protection, and/or automation outputs to the equipment.
In some embodiments, an IED may include, for example, remote terminal units, differential relays, distance relays, directional relays, feeder relays, overcurrent relays, voltage regulator controls, voltage relays, breaker failure relays, generator relays, motor relays, automation controllers, bay controllers, meters, recloser controls, communication processors, computing platforms, programmable logic controllers (PLCs), programmable automation controllers, input and output modules, governors, exciters, statcom controllers, static VAR compensator (SVC) controllers, on-load tap changer (OLTC) controllers, and the like. Further, in some embodiments, IEDs may be communicatively connected via a network that includes, for example, multiplexers, routers, hubs, gateways, firewalls, and/or switches to facilitate communications on the networks, each of which may also function as an IED. Networking and communication devices may also be integrated into an IED and/or be in communication with an IED. As used herein, an IED may include a single discrete IED or a system of multiple IEDs operating together.
IEDs may communicate with other IEDs, monitored equipment, and/or network devices using one or more suitable communication protocols and/or standards. In certain embodiments, IEDs, monitored equipment, and/or network devices included in an electric power generation and delivery system may communicate using one or more bandwidth conservative protocols. In further embodiments, IEDs, monitored equipment, and/or network devices included in an electric power generation and delivery system may communicate using one or more less-bandwidth conservative protocols. In certain circumstances, an electric power generation and delivery system may include a first set of IEDs, monitored equipment, and/or network devices that are configured to communicate using one or more bandwidth conservative protocols and a second set that are configured to communicate using one or more less-bandwidth conservative protocols.
In certain embodiments one or more IEDs, monitored equipment, and/or network devices included in an electric power generation and delivery system may communicate using a variety of protocols, such as IEC 61850 GOOSE (Generic Object Oriented Substation Events), SV (Sampled Values), MMS (Manufacturing Messaging Specification) SEL Fast Message (FM), and/or the like. In further embodiments, one or more IEDs, monitored equipment, and/or network devices included in an electric power generation and delivery system may communicate using a Mirrored Bits® protocol, a Distributed Network Protocol (DNP), and or any other suitable communication protocol. In some embodiments, IEC 61850 GOOSE, MMS, or the like may be considered a less-bandwidth conservative communication protocol, whereas Mirrored Bits®, DNP, FM, or the like may be considered bandwidth conservative communication protocols.
IEDs, monitored equipment, and/or network devices may communicate (e.g., transmit and/or receive) messages (e.g., GOOSE, Mirrored Bits®, and/or DNP messages) that include bits, bit pairs, measurement values, and/or any other relevant data elements. Certain communication protocols (e.g., GOOSE) may allow a message generated from a single device to be transmitted to multiple receiving devices (e.g., subscriber devices and/or particular receiving devices designated or identified in a message). Such messages may be referred to as multi-cast messages. In certain embodiments, (e.g., embodiments that utilize GOOSE), a message may be part of a message stream that includes multiple redundant copies of the message and/or similar messages. Messages in the message stream may include one or more control instructions, monitored system data, communications with other IEDs, monitored equipment and/or other network devices, and/or any other relevant communication, message, or data. In further embodiments, messages in the message stream may provide an indication as to a data state (e.g., a measured data state) of one or more components and/or conditions within an electrical power generation and delivery system.
Certain systems and methods disclosed herein allow for communication between IEDs, monitored equipment, and/or network devices that implement a variety of communication protocols using message proxying techniques. For example, a first IED in a system may be configured to utilize a less-bandwidth conservative protocol (e.g., GOOSE), while a second IED may be configured to utilize a bandwidth conservative protocol (e.g., Mirrored Bits® and/or DNP). One or more network devices communicatively coupled with the first IED and the second IED may receive a message from the first IED and transmit a message to the second IED in a protocol that the second IED understands. For example, the one or more network devices may receive a message in a less-bandwidth conservative protocol from the first IED and may transmit a corresponding message to the second IED in a bandwidth conservative protocol. In this manner, communication between IEDs, monitored equipment, and/or network devices implementing a variety of communication protocols may be facilitated.
Further systems and methods disclosed herein may allow network devices to package a plurality of messages received from one or more IEDs into a single message and to transmit the packaged single message to an intended receiving device (e.g., a receiving IED). In certain circumstances, such packaging of messages may be referred to as message aggregation. In certain embodiments, by packaging multiple messages into a single message, high network message traffic and/or congestion at an intended receiving device or through a particular communication channel and/or pathway may be reduced.
Systems and methods disclosed herein further allow for communication between one or more stations (e.g., substations and/or sets of IEDs, monitored equipment, and/or network devices) of an electric power generation and delivery system that implement a variety of communication protocols. For example, a first substation of an electric power generation and delivery system may utilize a first communication protocol to facilitate communication between IEDs, monitored equipment, and/or network devices included therein. A second substation of an electric power generation and delivery system may utilize a second communication protocol to facilitate communication between IEDs, monitored equipment, and/or network devices included therein.
An automation controller may be utilized to automate, control, and/or protect devices and equipment included in the first and second substations. The automation controller, however, may only be capable of communicating using the first communication protocol. Accordingly, while devices and/or equipment in the first substation may communicate directly with the automation controller in the first communication protocol, devices included in the second substation may not be capable of communicating directly with the automation controller. Consistent with certain embodiments, proxying and/or message aggregation techniques disclosed herein implementing one or more network devices and/or message configuration modules may be utilized to facilitate communication between the second substation and the automation controller.
A step-up power transformer 104 may be configured to increase the output of the electric generator 102 to a higher voltage sinusoidal waveform. A bus 106 may distribute the higher voltage sinusoidal waveform to a transmission line 108 that in turn may connect to a bus 120. In certain embodiments, the system 100 may further include one or more breakers 112-118 that may be configured to be selectively actuated to reconfigure the electric power generation and delivery system 100. A step down power transformer 122 may be configured to transform the higher voltage sinusoidal waveform to lower voltage sinusoidal waveform that is suitable for delivery to a load 124.
The IEDs 126-138, illustrated in
In certain embodiments, IEDs 126-138 may issue control instructions to the monitored equipment in order to control various aspects relating to the monitored equipment. For example, an IED (e.g., IED 136) may be in communication with a circuit breaker (e.g., breaker 114), and may be capable of sending an instruction to open and/or close the circuit breaker, thus connecting or disconnecting a portion of a power system. In another example, an IED may be in communication with a recloser and capable of controlling reclosing operations. In another example, an IED may be in communication with a voltage regulator and capable of instructing the voltage regulator to tap up and/or down. Information of the types listed above, or more generally, information or instructions directing an IED or other device to perform a certain action, may be generally referred to as control instructions.
IEDs 126-138 may be communicatively linked together using a data communications network, and may further be communicatively linked to a central monitoring system, such as a supervisory control and data acquisition (SCADA) system 142, an information system (IS) 144, and/or a wide area control and situational awareness (WCSA) system 140. In certain embodiments, various components of the electrical power generation and delivery system 100 illustrated in
The illustrated embodiments are configured in a star topology having an automation controller 150 at its center, however, other topologies are also contemplated. For example, the IEDs 126-138 may be communicatively coupled directly to the SCADA system 142 and/or the WCSA system 140. The data communications network of the system 100 may utilize a variety of network technologies, and may comprise network devices such as modems, routers, firewalls, virtual private network servers, and the like. Further, in some embodiments, the IEDs 126-138 and other network devices (e.g., one or more communication switches or the like) may be communicatively coupled to the communications network through a network communications interface.
Consistent with embodiments disclosed herein, IEDs 126-138 may be communicatively coupled with various points to the electric power generation and delivery system 100. For example, IED 134 may monitor conditions on transmission line 108. IEDs 126, 132, 136, and 138 may be configured to issue control instructions to associated breakers 112-118. IED 130 may monitor conditions on a bus 152. IED 128 may monitor and issue control instructions to the electric generator 102.
In certain embodiments, communication between and/or the operation of various IEDs 126-138 and/or higher level systems (e.g., SCADA system 142 or IS 144) may be facilitated by an automation controller 150. The automation controller 150 may also be referred to as a central IED, access controller, communications processor, and/or information processor.
The IEDs 126-138 may communicate a variety of types of information to the automation controller 150 including, but not limited to, status and control information about the individual IEDs 126-138, IED settings information, calculations made by the individual IEDs 126-138, event (e.g., a fault) reports, communications network information, network security events, and the like. In some embodiments, the automation controller 150 may be directly connected to one or more pieces of monitored equipment (e.g., electric generator 102 or breakers 112-118).
The automation controller 150 may also include a local human machine interface (HMI) 146. In some embodiments, the local HMI 146 may be located at the same substation as automation controller 150. The local HMI 146 may be used to change settings, issue control instructions, retrieve an event report, retrieve data, and the like. The automation controller 150 may further include a programmable logic controller accessible using the local HMI 146. In certain embodiments, the automation controller 150 and/or any other system illustrated in
The automation controller 150 may also be communicatively coupled to a time source (e.g., a clock) 148. In certain embodiments, the automation controller 150 may generate a time signal based on the time source 148 that may be distributed to communicatively coupled IEDs 126-138. Based on the time signal, various IEDs 126-138 may be configured to collect and/or calculate time-aligned data points including, for example, synchrophasors, and to implement control instructions in a time coordinated manner. In some embodiments, the WCSA system 140 may receive and process the time-aligned data, and may coordinate time synchronized control actions at the highest level of the electrical power generation and delivery system 100. In other embodiments, the automation controller 150 may not receive a time signal, but a common time signal may be distributed to IEDs 126-138.
The time source 148 may also be used by the automation controller 150 for time stamping information and data. Time synchronization may be helpful for data organization, real-time decision-making, as well as post-event analysis. Time synchronization may further be applied to network communications. The time source 148 may be any time source that is an acceptable form of time synchronization, including, but not limited to, a voltage controlled temperature compensated crystal oscillator, Rubidium and Cesium oscillators with or without a digital phase locked loops, microelectromechanical systems (MEMS) technology, which transfers the resonant circuits from the electronic to the mechanical domains, or a global positioning system (GPS) receiver with time decoding. In the absence of a discrete time source 148, the automation controller 150 may serve as the time source 148 by distributing a time synchronization signal.
To maintain voltage and reactive power within certain limits for safe and reliable power delivery, an electrical power generation and delivery system may include switched capacitor banks (SCBs) (e.g., capacitor 110), actuated by breaker 118 controlled by IED 138, configured to provide capacitive reactive power support and compensation in high and/or low voltage conditions within the electrical power system.
In certain embodiments, messages indicating a data state may be embodied as messages using one or more bandwidth conservative protocols and/or one or more less-bandwidth conservative protocols. A message may further indicate not only a particular data state, but also whether the message indicates a data state that is different than a data state indicated by one or more preceding message. That is, a message may include an indication that a data state associated with the message represents a data state change from a prior message. In certain embodiments, the prior message may be an immediately preceding message. In certain embodiments, data state change information may be indicated by a data state change indicator (DSCI) included in the message. For example, a DSCI included in a message may be set to “1” following a data state change event. According to some embodiments, the DSCI may be asserted in only a first message following a data state change event. In other embodiments, the DSCI may be asserted for a specified period of time or for a specified number of messages (e.g., a message stream). The DSCI may be set a different value upon a subsequent data state change event. By utilizing DSCI, a receiving device may determine that a particular message indicates a recent data state change without having to examine certain contents of the message and/or previously received messages.
In certain embodiments, an IED may transmit to subscribing (e.g., receiving) devices and/or receive from publishing (e.g., transmitting) devices messages 200 reflecting a particular data state (e.g., “Data State 1”) at periodic intervals at a first communication rate after a certain period in which the data state has remained constant (e.g., a message stream). For example, if a measured data state has not changed within the last 30 seconds, an IED may transmit messages 200 at periodic intervals at the first communication rate. In certain embodiments, this periodic interval may be relatively long, reflecting that a data state change has not recently occurred. Transmitting the same or similar state messages periodically in a message stream may introduce a degree of redundancy, helping to ensure that subscribing devices receive messages during periods of network congestion and/or low network bandwidth conditions. Further, the continuous transmission may serve as an indicator that the transmitting device is continuing to operate as expected. Accordingly, the continuous stream of messages may be referred to as a “heartbeat”.
When a data state change occurs (e.g., at 202), the IED may publish and/or receive messages 204 reflecting the changed state (e.g., “Data State 2”) at periodic intervals having a second communication rate. As illustrated, in certain embodiments, the second communication rate may be faster than the first communication rate. Accordingly, the period between sequential messages 204 may be shorter than the period between sequential messages 200. As time progresses following the data state change event 202, the communication rate of the messages 204 may progressively slow to reach, for example, a rate at or near the first communication rate. In this manner, data state messages may be transmitted at a relatively fast rate immediately following a data state change event 202 that progressively slows as the data state change event 202 becomes older. According to some embodiments, the transmission rate may decrease exponentially for a period of time following the data state change event 202.
Transmitting measured data state messages at a faster rate after a data state change event 202 may ensure that devices subscribing to the communications (e.g., subscribing IEDs) are more likely to receive the messages indicating the data state change as closely as possible in time to the actual data state change event 202. Transmitting redundant messages at a relatively fast rate, however, may introduce network congestion and/or bandwidth issues in some devices (e.g., communication switches, routers, radios, multiplexors, a real-time automation controller, IEDs, PLCs, and/or the like).
The network switches 308-312 may be configured to receive messages from the network 300 and to transmit certain messages to an associated IED 302-306, 318. For example, network switch 308 may be configured to receive messages from the network 300 and to transmit certain of the received messages to IED 302 and/or IED 318. As discussed above, in certain circumstances, a receiving IED (e.g., IED 302 and/or 318) may include a finite receiving FIFO that may only store a predetermined number of messages, and thus may not be capable of storing certain messages if a significant number of messages are received in a relatively short period (e.g., during periods of high network message traffic). Similarly, a network switch (e.g., network switch 308) may have a limited transfer rate that is lower than its receiving rate. For example, a network switch may have a 1 MB/second data transmission rate but a receiving rate that is substantially greater, thereby creating an asymmetry between inbound and outbound communication rates. If such a network switch includes a finite receiving and/or transmitting buffer and a substantial amount of data (e.g., a message stream) is received by such a network switch in a short period of time, the network switch may be unable to transmit received messages before the finite buffers become full and thus messages may be dropped or lost. In further circumstances, network devices and/or IEDs may have insufficient computing resources to process network traffic at “wire speed.”
Certain IEDs may utilize bandwidth conservative protocols (e.g., Mirrored Bits®, DNP, or the like) to manage the flow of messages and reduce the occurrence of dropped or lost messages and/or communication bottlenecks described above. Other IEDs, however, may not be configured to utilize a bandwidth conservative protocol, and may instead be limited to utilizing a less-bandwidth conservative protocol (e.g. GOOSE). Consistent with embodiments disclosed herein, certain IEDs, monitored equipment, and/or network devices may include a communication architecture allowing for communication between devices and/or stations implementing a variety of communication protocols (e.g., bandwidth conservative protocols and less-bandwidth conservative protocols). For example, one or more network devices may receive a message in a less-bandwidth conservative protocol from a first IED and may transmit a corresponding message to a second IED in a bandwidth conservative protocol.
IEDs 302-306, 320 may be configured to communicate via a network 300 using messages that, in certain embodiments, may provide an indication as to a data state and/or data state change of one or more components and/or conditions within an electrical power generation and delivery system. In certain embodiments, IEDs 302-306, 320 and/or network radios 314, 316 may be configured to communicate using one or more bandwidth conservative protocols and/or one or more less-bandwidth conservative protocols. The network switches 308, 312 and/or network radios 314, 316 may be configured to receive messages from the network 300 and to transmit certain messages to an associated IED 302-306, 320 using one or more suitable communication protocols. For example, network switch 308 may be configured to receive messages from the network 300 and to transmit certain of the received messages to IED 302 and/or IED 320. Similarly, IED 304 may communicate (e.g., exchange messages) with the network 300 via one or more network radios 314, 316 or other similar network devices implementing a wireless communication methodology.
Certain IEDs may utilize bandwidth conservative protocols (e.g., Mirrored Bits®, DNP, or the like) to manage the flow of messages and reduce the occurrence of dropped or lost messages and/or communication bottlenecks. Other IEDs, however, may not be configured to utilize a bandwidth conservative protocol, and may instead be limited to utilizing a less-bandwidth conservative protocol (e.g. GOOSE). Consistent with embodiments disclosed herein, certain IEDs, monitored equipment, and/or network devices (e.g., network radios 314, 316) may include a communication architecture allowing for communication between devices and/or stations implementing a variety of communication protocols (e.g., bandwidth conservative protocols and less-bandwidth conservative protocols). For example, network radio 314 may receive a message from the network 300 in a less-bandwidth conservative protocol and may transmit a corresponding message to network radio 316 in a bandwidth conservative protocol.
To facilitate communication between IED 400 and IEDs 402, 404, network device 406 may receive a bandwidth conservative protocol message 408 from IED 400, reconfigure the bandwidth conservative protocol message 408 into a protocol understood by IEDs 402, 404 (e.g., a less-bandwidth conservative protocol), and transmit the reconfigured messages as less-bandwidth conservative protocol messages 410, 412 to IEDs 402, 404 respectively. For example, IED 400 may transmit a Mirrored Bits® message (e.g., message 408) to network device 406 which, in certain embodiments may be a network switch. IEDs 402, 404 may subscribe to messages generated by IED 400, but may be unable to communicate using the same protocol as IED 400. Accordingly, network device 406 may receive the Mirrored Bits® message and configure the Mirrored Bits® message as a corresponding message (e.g., a GOOSE message) that IEDs 402, 404 may understand for transmission to IEDs 402, 404. In this manner, communication between IEDs, monitored equipment, and/or network devices implementing a variety of communication protocols may be facilitated.
In certain embodiments, network device 406 may be aware of the receiving capabilities of IEDs 402, 404 and may use this information in determining a message format that IEDs 402, 404 may understand. Network device 406 may be aware of the receiving capabilities of IEDs 402, 404 through communication with IEDs 402, 404, information contained in message 408, predetermined programming of network device 406, and/or any other suitable method.
To facilitate communication between IED 400 and IED, 404, network device 406 may receive a less-bandwidth conservative protocol message 414 from IED 404 intended for IED 400, reconfigure the less-bandwidth conservative protocol message 414 into a protocol understood by IED 400 (e.g., a bandwidth conservative protocol), and transmit the reconfigured message as a bandwidth conservative protocol message 416 to IED 400. For example, IED 404 may transmit a GOOSE message intended for IED 400 (e.g., message 414) to network device 406 which, in certain embodiments may be a network switch. IED 400 may subscribe to messages generated by IED 404, but may be unable to communicate using the same protocol as IED 404. Accordingly, network device 406 may receive the GOOSE message and configure the GOOSE message as a corresponding message (e.g., a Mirrored Bits® message) that IED 400 may understand for transmission to IED 400. In this manner, communication between IEDs, monitored equipment, and/or network devices implementing a variety of communication protocols may be facilitated.
IED 500 may be configured to communicate using a bandwidth conservative protocol. IED 502 may be configured to process information in a less-bandwidth conservative protocol (e.g., less-bandwidth conservative protocol messages such as, for example, GOOSE messages). As messages transmitted by IED 500 and received by IED 502 may be in a bandwidth-conservative protocol (e.g., message 506), IED 502 may include a module 504 that configures incoming messages received in the bandwidth conservative protocol into messages that IED 502 can process (e.g., less-bandwidth conservative protocol messages). Similarly, module 504 may reconfigure messages generated by IED 502 in a less-bandwidth conservative protocol (e.g., GOOSE) to a bandwidth conservative protocol (e.g., Mirrored Bits®, DNP, and/or the like) and transmit the reconfigured message (e.g., message 508) to IED 500. By reconfiguring incoming messages into a protocol that IED 502 can process, communication between IEDs, monitored equipment, and/or network devices implementing a variety of communication protocols may be facilitated.
In certain circumstances, IED 600 may only be capable of receiving and/or storing certain messages if a significant number of messages are received in a relatively short period (e.g., during periods of high network message traffic) due to, for example, a finite receiving buffer included in IED 600 or the like. Accordingly, if IEDs 602-606 all transmit messages 610-614 (e.g., “Message 1”, “Message 2”, and “Message 3”) at the same time or within a relatively short time period and IED 600 is not capable of receiving all of the message at the same time or within the time period, certain messages of the transmitted messages 610-614 may be lost and/or dropped.
To ensure that all messages are received by IED 600, certain messages (e.g., messages 610-614) transmitted by IEDs 602-606 may be routed through the network device 608. For example, messages 610-614 transmitted at the same time or within a relatively short time period may be routed through the network device 608. To ensure that messages transmitted to IED 600 are not lost and/or dropped due to periods of high network message traffic, network device 608 may configure (e.g., repackage) information included the messages 610-614 into a new message package 616. Configuring multiple messages 610-614 into a message package 616 may reduce the overall number of messages transmitted to IED 600, thereby reducing issues caused by high network message traffic and/or congestion conditions.
In certain embodiments, network device 608 may configure the information included in the messages 610-614 into a new message package 616 in a format that receiving IED 600 may understand. For example, if IED 600 is GOOSE-enabled, network device 608 may configure the message package 616 according to the GOOSE protocol. Similarly, if IED 600 is Mirrored Bite-enabled, network device 608 may configure the message package 616 according to the Mirrored Bits® protocol.
In certain embodiments, network device 608 may be aware of the receiving capabilities of IED 600 and may use this information in determining a message format that IED 600 may understand. Network device 608 may be aware of the receiving capabilities of IED 600 through communication with IED 600, predetermined programming of network device 608, and/or any other suitable method.
Message package 616 may include information that associates particular information included in the message package 616 with a particular transmitting IED (e.g., IED 602-606). Using this information, the receiving IED 600 may identify what information contained in the message package 616 is associated with a particular transmitting IED. For example, the message package 616 may include one or more subscription identifiers associating certain information contained in the message package 616 with a particular transmitting IED.
As illustrated, an automation controller 710 may be communicatively coupled with various IEDs 712-720. IEDs 712-720 may be remote from automation controller 710 and may communicate over various media and/or communication channels or pathways such as direct communication (e.g., IEDs 714), over a wide-area communications network 722 (e.g., IED 720), or via one or more network devices 740, 742, as described in more detail below. The illustrated embodiments are configured in a star topology having an automation controller 710 at its center, however, other topologies are also contemplated. The automation controller 710 may be utilized to automate, control, and/or protect devices and equipment included in the first and second substations. Although system 700 utilizes an automation controller 710 to coordinate automation, control, and system protection actions, any other suitable IED device or devices may be utilized.
System 700 includes a generation substation 702. Substation 702 may include various generators 724, 726 connected to a bus 728 through transformers 730, 732. Bus 728 may be connected to bus 734 in substation 704 via transmission line 736. Although the equipment illustrated in substation 702 may be monitored and/or controlled by various IEDs, only a single IED 712 is shown. IED 712 may be configured to monitor, control, and/or provide protection for transformer 730. IED 712 may receive a common time signal 738 that, as indicated above, may be distributed in system 700 using a communications network and/or using a universal time source such as GPS or the like. In certain embodiments, utilizing a common or universal time source may ensure that IEDs have a synchronized time signal that can be used to generate time synchronized data such as synchrophasor.
Substation 704 may include a generator 744, which may be a distributed generator, and which may be connected to bus 734 through step-up transformer 746. Bus 734 may be monitored, protected, and/or controlled by IED 718 using, for example, current transformer 780. Bus 734 may be connected to a distribution bus 748 via a step-down transformer 750. Transformer 750 may be monitored, protected, and or controlled by IED 716. Various distribution lines 752, 754 may be connected to distribution bus 748. For example, distribution line 752 may connect certain equipment in substation 706 with distribution bus 748. In certain embodiments, distribution line 752 may be monitored, protected, and/or controlled using IED 714, which may be configured to selectively open and close breaker 756. One or more loads 758 may be fed from distribution line 752. In certain embodiments, further step-down transformer 760 may be used to step down a voltage for consumption by the one or more loads 758.
Distribution line 754 may connect certain equipment in substation 708 including bus 762. Bus 762 may also receive electric power from distributed generator 764 via transformer 766. Distribution line 768 may deliver electric power from bus 762 to one or more loads 770 directly or, as illustrated, via further step down transformer 772. Circuit breaker 774 may be used to selectively connect bus 762 to distribution line 768. IED 720 may be used to control circuit breaker 774 and/or monitor and protect distribution line 768 using voltage transformer 776 or current transformer 778.
Automation controller 710 and/or IEDs, monitored equipment, and/or network devices included in substations 702-708 may communicate using a variety of communication protocols. For example, devices and equipment included in electrical generation and distribution system 700 may communicate using GOOSE, Mirrored Bits®, DNP, bandwidth conservative, less-bandwidth conservative, and/or any other suitable communication protocols.
In certain embodiments, various devices and equipment included in electrical generation and delivery system 700 may communicate using different communication protocols. For example, devices and equipment included in substation 702, including IED 712, may be configured communicate using a first protocol (e.g., GOOSE). Automation controller 710 may be configured to communicate with a second protocol different than the first protocol. To facilitate mixed-mode communicate between IED 712 and automation controller 710, proxying methods such as those illustrated in and described in reference to
A network device 740 may be communicatively coupled in the communication channel and/or pathway between automation controller 710 and IED 712. In certain embodiments, network device 740 may be included in substation 702 as illustrated. In further embodiments, network device 740 may be external to substation 702. Additionally, although
Network device 740 may receive communications and/or messages from IED 712 in the first communication protocol intended for automation controller 710. Network device 740 may reconfigure the received communications and/or messages from the first communication protocol to the second communication protocol. By reconfiguring the communications and/or messages received from IED 712 into the second protocol, network device 740 may generate corresponding communications and/or messages that the automation controller 710 may understand. In this manner, communication between system elements (e.g., IED 712 and automation controller 710) configured to communicate using different protocols may be achieved.
Circumstances where different portions of an electric power generation and delivery system are configured to communicate with different communication protocols may arise when a new substation implementing a newer communication protocol is installed and/or connected to an existing electrical generation and delivery system. Accordingly, using the proxying and message aggregation methods disclosed herein to facilitate mixed-mode communication may allow for newer IEDs, equipment, and/or network devices implementing newer communication protocols to be connected to an existing electric power generation and delivery system implementing legacy communication protocols while maintaining the system's ability to engage in control, monitoring, and protection activities.
In certain embodiments, each system element (e.g., IEDs, monitored equipment, network devices, and/or the like) may utilize a discrete network device (e.g., network device 740) for implementing proxying methods to facilitate communication with system elements configured to communicate using different communication protocols. In some embodiments, utilizing a single network device 742 for proxying communications generated by a plurality of other systems elements (e.g., IEDs, monitored equipment, network devices, and/or the like) may reduce the number of proxying network devices required in a system and/or substation, as including a discrete network device implementing the proxying methods disclosed herein for system element requiring mixed-mode communication may not be required.
In other embodiments, message aggregation systems and methods such as the systems and methods illustrated in and described in reference to
As illustrated, substation 704 may include a network device 742 communicatively coupled to IEDs 716, 718. In certain embodiments, network device 742 may be included in substation 704 as shown. In further embodiments, network device 742 may be external to substation 704. Additionally, although
Network device 742 may receive communications and/or messages from IEDs 716, 718 in the first communication protocol intended for automation controller 710. In certain circumstances, network device 742 may reconfigure the received communications and/or messages in the second communication protocol for transmission to automation controller 710 as the communications and/or messages are received by the network device 742. In periods of high message traffic and/or low bandwidth in the communication channels and/or pathways between network device 742 and automation controller 710, however, network device 742 and/or automation controller 710 may not be capable of reconfiguring, transmitting, receiving, and/or processing communications at the same or similar rate they are generated and/or received (e.g., when multiple message are received at the same time or within a relatively short time period). Under such conditions, communications and/or messages may be dropped and/or lost.
To ensure all messages are received by automation controller 710, certain communications and/or messages generated by IEDs 716, 718 intended for automation controller 710 received by network device 742 may be reconfigured (e.g., aggregated and/or repackaged) as a message package according to the second communication protocol. Configuring multiple messages into a message package may reduce the overall number of messages transmitted to automation controller 710, thereby reducing issues caused by high network message traffic and/or low network bandwidth conditions.
As discussed above, a message package may include information that associates particular information included in the message package with a particular transmitting IED (e.g., IEDs 716, 718). Using this information, the receiving device (e.g., automation controller 710) may identify what information contained in the message package is associated with a particular IED. For example, in certain embodiments, a message package may include one or more subscription identifiers associating certain information contained in the message package with a particular transmitting IED.
In certain embodiments, network devices 740, 742 may be aware of the receiving and/or communication capabilities of automation controller 710, and may use this information in determining a message format that automation controller 710 may understand. For example, network devices 740, 742 may be aware that automation controller 710 is configured to communicate using the second communication protocol, and thus may reconfigure and/or aggregate messages intended for the automation controller 710 according to the second communication protocol. In certain embodiments, network devices 740, 742 may be aware of the receiving and/or communication capabilities of the automation controller through communication with the automation controller 710 or another system (e.g., a database 790), programming on the network devices 740, 742, and/or any other suitable method.
Although
At 806, after determining that the intended receiving device is configured to communicate according to the second communication protocol, a message reconfiguration system included in the device may reconfigure the message according to the second communication protocol. At 808, the reconfigured message may be transmitted to the intended receiving device according to the second communication protocol. In this manner, mixed-mode communication between the device generating the message and the intended receiving device may be achieved.
At 904, the device may access information indicating that the intended receiving device is configured to communicate according to a particular communication protocol. In certain circumstances, this communication protocol may be different than the communication protocol(s) the messages were received in by the device at 902. In certain embodiments, the information may be accessed by communicating with the intended receiving device, a database, or another system, through programming of the device, and/or by any other suitable method. At 906, information included in the messages received at 902 may be reconfigured (e.g., packaged) into a new message package according to the particular communication protocol. For example, if a receiving device is GOOSE-enabled, the device performing method 900 may configure the message package according to the GOOSE protocol. Similarly, if a receiving device is Mirrored Bits®-enabled, the device performing method 900 may configure the message package according to the Mirrored Bits® protocol.
At 908, the device may transmit the message package to an intended receiving device. In certain embodiments, the message package may include information that associates particular information included in the message package with a particular device that originally transmitted the message to the device performing method 900 at 902 (e.g., a publishing device). Using this information, the receiving device may identify what information contained in the message package is associated with a particular transmitting device. For example, the message package may include one or more subscription identifiers associating certain information contained in the message package with a particular publishing device.
At 1006, a communications interface of the network device may be configured to communicate with the first and second devices. For example, the communications interface may be configured to received messages from the first device and transmit messages to the second device. At 1008, a message reconfiguration system of the network device may be configured to access information indicating a communication protocol of an intended receiving device (e.g., the second device). By accessing information indicating a communication protocol of an intended receiving device, consistent with the systems and methods disclosed herein, the network device may reconfigure messages received in a different communication protocol into a communication protocol that the intended receiving device may understand.
The user interface 1108 may be used to control certain features of the network device 1100 (e.g., via any suitable interactive interface to a user, one or more visual or audible status indicators, and/or the like). The user interface 1108 may be integrated in the network device 1100 or, alternatively, may be a user interface for a laptop or other similar device communicatively coupled with the computer system 1100. In certain embodiments, the user interface 1108 may be produced on a touch screen display. The communications interface 1106 may be any interface capable of communicating with other computer systems and/or other equipment (e.g., remote network equipment) communicatively coupled to computer system 1100.
The processor 1102 may include one or more general purpose processors, application specific processors, microcontrollers, digital signal processors, FPGAs, or any other customizable or programmable processing device. The processor 1102 may be configured to execute computer-readable instructions stored on the non-transitory computer-readable storage medium 1110. In some embodiments, the computer-readable instructions may be computer-executable functional modules. For example, the computer-readable instructions may include one or more functional modules configured to implement all or part of the functionality of the systems and methods described above in reference to
While specific embodiments and applications of the disclosure have been illustrated and described, it is to be understood that the disclosure is not limited to the specific configurations and components disclosed herein. Accordingly, many changes may be made to the details of the above-described embodiments without departing from the underlying principles of this disclosure. The scope of the present invention should, therefore, be determined only by the following claims.
