electric power grid command filter system

专利摘要:
electric power grid command filter system. the present invention relates to a command filter module that receives a plurality of commands intended for reception by interconnected devices within the large electrical power distribution. the command filter module can authorize the plurality of commands to be executed by the respective devices based on predetermined command set rules. Historical and real-time data can be implemented by the command filter module to make an authorization decision for the plurality of commands. authorized commands can be transmitted by the command filter module for reception by the respective devices. the command filter module can generate rejection messages corresponding to unauthorized commands. rejection messages can be transmitted to an unauthorized command source.
公开号:BR112012021714B1
申请号:R112012021714
申请日:2011-02-16
公开日:2020-02-04
发明作者:David Taft Jeffrey
申请人:Accenture Global Services Ltd；
IPC主号:

专利说明:

Descriptive Report of the Invention Patent for ELECTRIC ENERGY DISTRIBUTION GRID CONTROL FILTER SYSTEM.
BACKGROUND
Field of the Invention [0001] The present invention generally relates to a system and method for managing a power grid, and more particularly to a system for filtering electric power grid device commands based on predetermined criteria.
Related technique [0002] A power grid can include any or all of the following: electricity generation, transmission of electricity, and distribution of electricity. Electricity can be generated using generation stations, such as a coal fire power plant, a nuclear power plant, etc. For efficiency purposes, the electricity generated is raised to a very high voltage (such as 345K Volts) and transmitted through the transmission lines. Transmission lines can transmit energy over long distances, such as along state lines or across international borders, until it reaches the wholesale customer, which may be a company that owns the distribution grid. The transmission lines can end at a transmission substation, which can lower the voltage too high to an intermediate voltage (such as 138K Volts). From a transmission substation, smaller transmission lines (such as sub-transmission lines) transmit the intermediate voltage to distribution substations. In distribution substations, the intermediate voltage can again be lowered to an average voltage (such as from 4K Volts to 23K Volts). One or more feeder circuits may emanate from distribution substations. For example, four to ten of the feeder circuits can emanate
Petition 870190108109, of 10/24/2019, p. 8/84
2/69 of the distribution substation. The feeder circuit is a 3-phase circuit comprising 4 wires (three wires for each of the 3 phases and one wire for the neutral. Feeder circuits can be routed over the ground (on posts) or under the ground. The voltage in the circuits feeders can be used periodically using distribution transformers, which lower the average voltage voltage to the consumer voltage (such as 240 / 120V) .The consumer voltage can then be used by the consumer.
[0003] One or more power companies can manage the power grid, including managing power outages, maintenance, and updates related to the power grid. However, management of the power grid is often inefficient and expensive. For example, a power company that handles the distribution grid can manage faults that can occur in the feeder circuits or in circuits, called side circuits, which branch off the feeder circuits. The management of the distribution grid often relies on telephone calls from customers, when a service interruption occurs, or relies on field workers analyzing the distribution grid.
[0004] Power companies have tried to upgrade the power grid using digital technology, sometimes called a smart grid. For example, smarter meters (sometimes called smart meters) are a type of advanced meter that identifies consumption in more detail than a conventional meter. The smart meter can then communicate this information, via some network, back to the local utility for monitoring and billing purposes (tele-measurement). Other devices within an intelligent grid can also be controlled via remote terminals. Leaving devices within an intelligent grid allows electronic control over devices through
Petition 870190108109, of 10/24/2019, p. 9/84
3/69 commands on a very resolute scale, such as a main mechanism in the home of a residential customer, or main industrial equipment of an industrial customer. Although unique commands of this nature are not in themselves dangerous to the entire health of the smart grid, many of these commands executed within a relatively short amount of time can cause adverse effects within the smart grid.
[0005] Document US-A1-2009 / 034419 refers to a wireless electrical distribution network that contains a plurality of electrical distribution nodes that communicate within a wireless electrical distribution network . A port for the wireless electrical distribution network communicates with the electrical distribution nodes in the wireless electrical distribution network, and connects the wireless electrical distribution network to at least one other network. A packet is transmitted from one electrical distribution node to another electrical distribution node according to a route included in the transmitted package. The route included in the transmitted packet is updated with network information received to determine an updated path cost for the included route and compared to alternative routes to select a preferred route based on the path cost. The preferred route selected is included in the packet and the packet is transmitted to another node, according to the preferred route selected.
[0006] US-A1-2004 / 139134 relates to a filter comprising a first device, a second device, a dynamic filter, and a device monitor. The dynamic filter is coupled to the first device and the second device, and selectively directs commands to the first device and the second device based on the dynamic status of the first device. The device monitor is coupled to the dynamic filter and the first device and is capable of determining 870190108109, of 10/24/2019, p. 10/84
4/69 tell the dynamic status of the first device.
BRIEF SUMMARY [0007] A command filter system for filtering commands from the filter device within a utility network is provided. The command filter system can be implemented in an intelligent grid to improve the management of an electricity distribution grid. The smart grid, as presently described, includes sensors used in various parts of the electricity distribution grid, using communications and computing technology to elevate the current electricity grid so that it can operate more efficiently and reliably and support additional services. for consumers. The smart grid as presently described, can elevate a traditional electricity transmission and grid or grid distribution, such as using strong two-way communications, advanced sensors, and distributed computers (including additional intelligence on electricity transmission and / or electricity distribution ). The smart grid can also include additional functionality in a central management facility to manage operations, detect and correct failures, manage resources, etc.
[0008] Commands used to control various devices within the smart grid can be generated manually or automatically. The command filter system can be implemented within the smart grid to analyze each device command and authorize the device commands for execution by a particular device. The command filter system can receive each command from the device within the smart grid. The command filter system can apply a set of rules to the device's commands. Based on the application of the rule set, the command filter system can authorize commands to be executed through particular devices. The control filter system can also
Petition 870190108109, of 10/24/2019, p. 11/84
5/69 prevent commands from being executed by particular devices. A rejection message can be generated by the command filter system for each command that is prevented from being executed. Each rejection message can be transmitted to a source of origin of the rejected command or to a supervisory location for subsequent intervention.
[0009] The command filter system can implement several predetermined rules to determine whether authorization should be given for several commands. The command filter system can analyze commands received simultaneously or within predetermined time windows. Predetermined rules can be directed to the number or type of commands received. The command filter system can retrieve historical data associated with the smart grid as well as current operating conditions for use in the analysis. Based on historical data, the command filter system can make an authorization decision for a particular command or group of commands. Using current operating conditions in conjunction with historical data, the command filter system can predict an effect on the intelligent grid to execute one or more commands being considered for authorization. Predetermined rules can be applied for the intended purpose to determine whether or not the commands should be authorized.
[00010] The command filter system can be implemented in smart grids having various configurations. The command filter can be implemented with software buses within the smart grid, such as communication network buses or network event recognition bus. The command filter can rely on authorized commands directly for devices, or it can rely on commands via communication networks and subnets. The command filter system can be a single system configured
Petition 870190108109, of 10/24/2019, p. 12/84
6/69 to receive substantially all device commands directly through the smart grid. In other configurations, the command filter system can be distributed within the smart grid, so that each distributed command filter system is responsible for analyzing commands associated with specific types of devices.
[00011] Other systems, methods, characteristics and advantages will be, or will become, evident to the person skilled in the art through examination of the figures and detailed description below. It is intended that all such systems, methods, features and additional advantages are included within this description, are within the scope of the invention, and are protected by the following claims.
BRIEF DESCRIPTION OF THE DRAWINGS [00012] Figure 1 is a block diagram of an example of the whole architecture for an energy grid.
[00013] Figure 2 is a block diagram of the NUCLEUS INDE represented in figure 1.
[00014] Figure 3 is a block diagram of another example of the whole architecture for the energy grid.
[00015] Figure 4 is a block diagram of the SUBSTATION INDE represented in figures 1 and 3.
[00016] Figure 5 is a block diagram of the INDE DEVICE represented in figures 1 and 3.
[00017] Figure 6 is a block diagram of yet another example of the whole architecture for the energy grid.
[00018] Figure 7 is a block diagram of yet another example of the whole architecture for the energy grid.
[00019] Figure 8 is a block diagram including a listing of some examples of the observation processes.
[00020] Figure 9 illustrates a flow diagram of the
Petition 870190108109, of 10/24/2019, p. 13/84
7/69
Grid State Measurements & Operations. [00021] Figure 10 illustrates
Non-Operating Data.
[00022] Figure 11 illustrates
Event Management.
a one a flow diagram flow diagram flow diagram of the processes of the processes of the processes [00023] Figure 12 illustrates Signaling of the Demand Response (DR).
[00024] Figure 13 illustrates a block diagram of an example command filter module.
[00025] Figure 14 illustrates the example of the command filter module of figure 13 implemented in an electric power distribution grid.
[00026] Figure 15 illustrates the example of the command filter module in Figure 13 implemented in another grid for electricity distribution.
[00027] Figure 16 illustrates the example of the command filter module of figure 13 implemented in another grid for electricity distribution.
[00028] Figure 17 illustrates the example of the command filter module of figure 13 implemented in another grid for electricity distribution.
[00029] Figure 18 illustrates an example of the operation flow diagram of the command example filter module of figure 13.
DETAILED DESCRIPTION OF THE DRAWINGS AND THE PRESENTLY PREFERRED MODALITIES [00030] As an overview, the preferred modalities described below refer to a command filter system. The command filter system can receive commands designed to control the operation of multiple devices within a power network. The command filter can apply one or more rules to the commands in order to
Petition 870190108109, of 10/24/2019, p. 14/84
8/69 to determine whether the commands should be authorized for execution by devices intended to receive.
Description of High Level Architecture INDE Complete Architecture [00031] Returning to the drawings, in which reference numerals refer to elements, figure 1 illustrates an example of the global architecture for INDE. This architecture can serve as a reference model that provides end-to-end collection, transport, storage, and intelligent data grid management; it can also provide analytics and analytics management, as well as integrating the processes and systems of the former into electric power distribution systems and processes. Therefore, it can be seen as a broad enterprise architecture. Certain elements, such as operational management and aspects of the network itself, as discussed in more detail below.
[00032] The architecture represented in figure 1 can include up to four data and integration buses: (1) a high speed sensor data bus 146 (which can include operational and non-operational data); (2) a dedicated event processing bus 147 (which may include event data); (3) an operations service bus 130 (which can serve to provide information on the smart grid for electric power distribution back office applications); and (4) a company service bus for remote office IT systems (shown in figure 1 as a company 114 integration environment bus to serve company 115 IT). Separate data buses can be performed in one or more ways. For example, two or more data buses, such as the high-speed sensor data bus 146 and event processing bus 147, can be different segments in a single
Petition 870190108109, of 10/24/2019, p. 15/84
9/69 data bus. Specifically, buses can have a segmented structure or platform. As discussed in more detail below, hardware and / or software, with one or more switches, can be used to route data on different segments of the data bus.
[00033] As another example, two or more of the data buses can be on separate buses, as separate physical buses in terms of the hardware needed to carry data on separate buses. Specifically, each of the busbars can include separate cable sets. In addition, some or all of the separate buses can be of the same type. For example, one or more of the buses may comprise a local area network (LAN), such as Ethernet® over a pair of unprotected twisted cable sets and Wi-Fi. As discussed in more detail below, hardware and / or software, such as a router, can be used to route data into data on a bus between different physical buses.
[00034] Still as one or the other example, two or more of the buses can be in different segments in a single bus structure, and one or more buses can be in different physical buses. Specifically, the high-speed sensor data bus 146 and event processing bus 147 can be different segments on a single data bus, while the business integration environment bus 114 can be on a physically separate bus.
[00035] Although figure 1 illustrates four buses, smaller or larger bus numbers can be used to load the four types of data listed. For example, a single non-segmented bus can be used to communicate sensor data and event processing data (bringing the total number of
Petition 870190108109, of 10/24/2019, p. 16/84
10/69 buses for three), as discussed below. And, the system can operate without the operations services bus 130 and / or the enterprise integration environment bus 114.
[00036] The IT environment can be SOA-compatible. Service Oriented Architecture (SOA) is a style of computer systems architecture for creating and using business processing, packaged as services, throughout its life cycle. SOA (AOS) also defines and conditions the IT infrastructure to allow different applications to exchange data and participate in business processes. However, the use of SOA and the business services bus are optional.
[00037] The figures illustrate different elements within the whole architecture, as follows: (1) NÚCLEO INDE 120; (2) SUBSTATION INDE 180; and (3) SINCE 188 DEVICE. This division of elements within the entire architecture is for illustration purposes. Another division of the elements can be used. The INDE architecture can be used to support both approaches, distributed and centralized, for network intelligence, and to provide mechanisms to deal with scale in large implementations.
[00038] The INDE Reference Architecture is an example of the technical architecture that can be implemented. For example, it can be an example of a meta-architecture, used to provide a starting point for developing any number of specific technical architectures, one for each electrical distribution solution, as discussed below. In this way, the specific solution for a particular electricity distribution may include one, some, or all elements in the INDE Reference Architecture. And the INDE Reference Architecture can provide a standardized starting point for developing the solution. Discussed below is the methodology for determining the specific technical architecture for a network of
Petition 870190108109, of 10/24/2019, p. 17/84
11/69 particular energy.
[00039] The INDE Reference Architecture can be a broad enterprise architecture. This purpose may be to provide an outline for managing end-to-end network and analytical data and integrating these into electrical power distribution systems and processes. Since smart grid technology affects every aspect of the electricity distribution business processes, the person must be aware of the effects not only on the customer's network, operations, and property levels, but also on the remote office levels of business. Consequently, the INDE Reference Architecture can and does reference the SOA enterprise level, for example, in order to support the SOA environment for interface purposes. This should not be taken as a requirement that a power distribution must convert your existing IT environment to SOA before a smart grid can be created and used. An enterprise service bus is a useful mechanism for facilitating IT integration, but it is not required in order to implement the rest of the smart grid solution. The discussion below focuses on different components of the INDE smart grid elements.
INDE Component Groups [00040] As discussed above, the different components in the INDE Reference Architecture can include, for example: (1) INDE CORE 120; (2) SUBSTATION INDE 180; and (3) INDE DEVICE 188. The following sections discuss these three examples of groups of elements of the INDE Reference Architecture and provide descriptions of the components of each group.
NÚCELO INDE [00041] Figure 2 illustrates the NÚCLEO INDE 120, which is the portion of the INDE Reference Architecture that can reside in an operations control center, as shown in figure 1. THE NÚCELOO INDE 120
Petition 870190108109, of 10/24/2019, p. 18/84
12/69 can contain a unified data architecture for storing grid data and an integration scheme for analysts to operate on that data. This data architecture can use the International Electrotechnical Commission (IEC) Common Information Model (CIM) as its high-level scheme. The IEC CIM is a standard developed by the electric power industry that has been officially adopted by the IEC, aiming to enable application software to exchange information about the configuration and status of an electrical network.
[00042] In addition, this data architecture can make use of middleware union 134 to connect other types of electricity distribution data (such as, for example, measurement data, operational and historical data, log files and events), and connectivity and meta-data files in a single data architecture that can have a single entry point for access by high-level applications, including business applications. Real-time systems can also access key data warehouses via a high-speed data bus and several warehouses can receive data in real time. Different types of data can be transported within one or more buses in the smart grid. As discussed below in SUBSTATION INDE section 180, substation data can be collected and stored locally at the substation. Specifically, a database, which can be associated with and close to the substation, can store the substation data. Analyzes belonging to the substation level can also be performed on substation computers and stored in the substation database, and all or part of the data can be transported to the control center.
[00043] The types of data carried can include data from
Petition 870190108109, of 10/24/2019, p. 19/84
13/69 operation and non-operational, events, network connectivity data, and network lease data. Operational data may include, but is not limited to, switch state, feeder state, capacitor state, section station, meter status, FCI state, line sensor state, voltage, current, real power, reactive power, etc. Non-operational data may include, but is not limited to, power quality, energy reliability, asset health, stress data, etc. Operational and non-operational data can be transported using an operational / non-operational data bus 146. Data collection applications in power grid transmission and / or electricity distribution may be responsible for sending some or all of data for the operational / non-operational data bus 146. In this way, applications that need this information may be able to obtain the data by subscribing to the information or invoking services that can make that data available.
[00044] Events may include messages and / or alarms that originate from various devices and sensors that are part of the smart grid, as discussed below. Events can be directly generated from devices and sensors in the network of smart grids as well as generated by the various analytical applications based on the measurement data from those sensors and devices. Examples of events may include measurement downtime, measured alarm, transformer downtime, etc. Grid components as grid devices (intelligent energy sensors (such as a sensor with an embedded processor that can be programmed for digital processing capability) temperature sensors, etc.), power system components that include additional embedded processing (RTUs , etc.), such as measurement networks
Petition 870190108109, of 10/24/2019, p. 20/84
14/69 intelligent (health measurement, reading measurement, etc.), and mobile field strength devices (downtime events, work order conclusions, etc.) can generate event data, operational and non-operational data. The event data generated within the smart grid can be transmitted over a bus 147.
[00045] Network connectivity data can define the layout of the electricity distribution grid. It can be a basic layout that defines the physical layout of the grid components (substations, segments, feeders, transformers, switches, reclosers, meters, sensors, electricity distribution poles, etc.) and their interconnections in the installation. Based on events within the grid (component failures, maintenance activity, etc.), and network connectivity can change on an ongoing basis. As discussed in more detail below, the structure of how data is stored as well as the combination of the data allows for the historical recreation of the network layout in various past times. Network connectivity data can be extracted from the Geographic Information System (GIS) on a periodic basis, as a modification to the electricity distribution grid made and this information is updated in the GIS application.
[00046] Network location data may include information about the grid component in the communications network. This information can be used to send messages and information to a particular network component. Grid location data can be entered manually into the Smart Grid database as new components of the Smart Grid are installed or extracted from the Asset Management System if that information is maintained electronically.
[00047] As discussed in more detail below, the data can
Petition 870190108109, of 10/24/2019, p. 21/84
15/69 be sent from various components on the network (such as SUBSTAÇÃO INDE 180 and / or DEVICE INDE 188). Data can be sent to CORE INDE 120 wirelessly, wired, or a combination of both. The data can be received by the electricity distribution communications networks 160, which can send the data to the routing device 190. Routing device 190 can comprise software and / or hardware for managing the routing of data on a segment of a conductive bus (when the bus comprises a segmented bus structure) or on a separate conductive bus. The routing device may comprise one or more switches or a router. Routing device 190 may comprise a network device whose software and hardware route and / or send data to one or more of the conductive bars. For example, routing device 190 can route operational and non-operational data to operational / non-operational bus 146. The router can also route event data to event bus 147.
[00048] Routing device 190 can determine how to route data based on one or more methods. For example, the routing device 190 can examine one or more headers in the transmitted data to determine whether to route the data to the segment for the operational / non-operational data bus 146 or for the segment for the event 147 bus. Specifically , one or more headers in the data can include whether the data is operational / non-operational data (so that the routing device 190 routes the data to the operational / non-operational data bus 146) or whether the data is event (so that routing device 190 routes event bus 147). Alternatively, routing device 190 can examine the source of the data or the
Petition 870190108109, of 10/24/2019, p. 22/84
16/69 data payload to determine the data type (for example, routing device 190 can examine the data format to determine whether the data is operational / non-operational data or event data).
[00049] One of the operational database stores 137 that stores the operational data, can be implemented as a true distributed database. Another of the stores, the history (identified as historical data 136 in figures 1 and 2), can be implemented as a distributed database. The other ends of these two databases can be located in the SUBSTATION INDE 180 group (discussed below). In addition, events can be stored directly in various data stores via the complex event processing bus. Specifically, events can be stored in event logs 135, which can be a repository for all events that have posted to event bus 147. The event log can store one, some, or all of the following: event id; type of type event; event source; priority of the event; and time of event generation. Event 147 tracking does not need to store long-term events, providing persistence for all events.
[00050] The data can be stored in such a way that the data can be as close as possible or practicable to the source. In an implementation, this may include, for example, the substation data being stored in SUBSTATION INDE 180. But that data may also be required at the level of operations control center 116 to make different types of decisions that the network considers at a very granular level. In conjunction with a distributed intelligence approach, a distributed data approach can be adopted to facilitate data availability
Petition 870190108109, of 10/24/2019, p. 23/84
17/69 at all levels of the solution through the use of database links and data services as applicable. In this way, the solution for storing historical data (which can be accessible at the level of the operations control center 116) may be similar to that of operational data storage. The data can be stored locally in the substation and database links configured in the repository instance in the control center, providing access to the data in the individual substations. Substation analytics can be performed locally at the substation using local data storage. Historical / collective analytics can be performed at the level of the operations control center 116 by accessing data in the instances of the local substation using the database links. Alternatively, the data can be stored centrally in the INDE 120 CORE. However, given the amount of data that may need to be transmitted from the INDE 188 DEVICES, storage of the data in the INDE 188 DEVICES may be preferred. Specifically, if there are millions or tens of millions of substations (which can happen in a power grid), the amount of data that needs to be transmitted to the INDE 120 CORE can create a communications bottleneck.
[00051] Finally, CORE INDE 120 can program or control one, some or all of SUBSTATION INDE 180 or DEDE 188 in the power grid (discussed below). For example, the NÚCLEO INDE 120 can modify the programming (such as downloading an updated program) or provide a control command to control any aspect of the INDE 180 SUBSTATION or the INDE 188 DEVICE (such as control of sensors or analytics). Other elements, not shown in figure 2, can include several integration elements to support this logical architecture.
[00052] Table 1 describes the certain elements of the CORE INDE
Petition 870190108109, of 10/24/2019, p. 24/84
18/69
120 as shown in figure 2.
Element of CORE INDE description CEP Services144 Provide high-speed, low-latency event flow processing, event filtering, and multi-stream event correlation Centralized Analytical Applications 139 It can consist of any number of customer analytical or commercial applications that are used in a non-real-time manner, primarily operating from CORE data stores Services ofViewing / Notification 140 Support for viewing data, states and event flows, and automatic notifications based on triggered event Application Management Services 141 Services (such as Application Support Services 142 and Distributed Computing Support 143) that support launching application execution, web services, and support for distributed computing and automated remote program download (for example, OSGi) Network management services 145 Automated monitoring of communications networks, applications and databases; health monitoring system, analysis of the root cause of the failure (non-network) Services ofMeta-Data ofNetwork 126 Services (such as Connectivity Services 127, Name Translation 128, and TEDS 129 Services) for storing, retrieving and updating system metadata, including network and communications / sensor network connectivity, point lists, sensor calibrations , protocols, device set points, etc. Grade 123 Data / Analytics Services Services (such as Sensor Data Services 124 and Analytics Management Services 125) to support access to network data and network analytics; analytics management System ofManagementof Data 121 Meter data management system functions (for example, Lodestar)
Petition 870190108109, of 10/24/2019, p. 25/84
19/69
Services ofMeasurement Datapain AMOS See discussion below Real-Time Complex Event Processing Bus 147 Message bus dedicated to handling event message flows - purpose of a dedicated bus to provide high bandwidth and low latency for highly bursty event message torrents. The event message can be in the form of an XML message. Other types of messages can be used.Events can be separated from operational / non-operational data, and can be transmitted on a separate or dedicated bus. Events typically have a higher priority as they usually require some immediate action from the operational perspective of electricity distribution (meter messages, faulty transformers, etc.)The event processing bus (and the associated event correlation processing service depicted in Figure 1) can filter out floods of events by decreasing in an interpretation that can be better actuated by other devices. In addition, the event processing bus can take multiple event flows, find multiple patterns occurring across multiple event flows, and provide an interpretation of multiple event flows. In this way, the event processing bus may not simply examine event data from a single device, but instead examine multiple devices (including multiple classes of devices that may be apparently unrelated) to find correlations. The analysis of a single or multiple event streams can be based on a rule.
Petition 870190108109, of 10/24/2019, p. 26/84
20/69
Bus Operational data may include data that reflects the current state of the optional / non-optional data in TimeReal 146 electrical grid state that can be used to control the grid (eg currents, voltages, real energy, reactive energy, etc.). Non-operational data may include data reflecting the health or condition of a device.Operational data having previously been transmitted directly to a specific device (thereby creating a potential silo problem of not making the data available to other devices or other applications). For example, operational data was previously transmitted to the SCADA (Supervisory Control of Data Acquisition) system for grid management (monitor and control grid). However, using the bus structure, operational data can also be used to balance load, asset utilization / optimization, system planning, etc., as discussed, for example, in figures 10 to19.Non-operational data was previously obtained by sending a person in the field to collect operational data (instead of automatically sending non-operational data to a central repository). Typically, operational and non-operational data are generated on multiple devices in the grid at predetermined times. This is in contrast to the event data, which is typically generated in disruptions, as discussed below.The message bus can be dedicated to handling data from operational and non-operational flows from substations and grid devices.The purpose of a dedicated bus can be to provide constant low latency through putting the data streams to match; as discussed elsewhere, a single bus can be used for transmission of both the operation of the non-operational data and the event processing data in some circumstances (effectively combining the operating / non-operating bus data as a processing bus event).
Petition 870190108109, of 10/24/2019, p. 27/84
21/69
Operations service bus 130 Message bus that supports integration of typical electricity distribution operations (EMS (energy management system), DMS (distribution management system), OMS (downtime management system), GIS (geographic information system ), shipping) with newer smart grid systems and functions (DRMS (demand response management system), external analytics, CEP, visualization). The various buses, including Operating / Non-Operating Data bus 146, Event 147 data bus, and Operations service bus 130 can obtain food, etc. through a security outline 117.The bus operations service 130 can serve as the intelligent grid information provider for back-end utility applications, as shown in figure 1. Analytical applications can make the data from sensors and devices on the grid raw into actionable information that will be available for electrical distribution applications to perform actions to control the grid. Although the majority of interactions between the rear of the power distribution and the CORE INDE 120 are expected to occur through this bus, the power distribution applications will have access to the other two buses and will also consume data from those buses (for example, operational / non-operational data bus meters 146, event bus 147 downtime events) Bank ofof 132 ofCIM data Top-level data storage for organizing network data; uses of the IEC CIM data scheme; provides the primary point of contact for accessing grid data for operating systems and business systems. The middleware union allows communication with the various databases.
Petition 870190108109, of 10/24/2019, p. 28/84
22/69
Datamart fromConnectivity131 The connectivity datamart 131 can contain the electrical connectivity information of the grid components. This information can be derived from the Geographic Information System (GIS) of the electric energy distribution that maintains as incorporated the geographic location of the components that make up the network. The data in the connectivity store 131 can describe hierarchical information about all components of the grid (substation, feeder, section, segment, branch, t- section, circuit breaker, recloser, switch, etc. - basically all assets). The 131 connectivity datamart can have the asset and connectivity information as constructed. In this way, the connectivity datamart 131 can comprise the asset database that includes all devices and sensors coupled to the grid components. Repository ofMeasurement datapain 133 The meter data repository 133 can provide quick access to meter usage data for analytics. This repository can hold all meter reading information from meters at the customer's premises. The data collected from the meters can be stored in the 133 meter data repositories and provided for other electricity distribution applications for billing (or other back-up operations) as well as other analyzes. Event logs135 Collection of incidental log files for the operation of various electricity distribution systems. Event logs 135 can be used for post mortem analysis of events and to mine data
Petition 870190108109, of 10/24/2019, p. 29/84
23/69
Historical Datacos 136 Telemetry data file in the form of a standard data history. Historical data 136 can maintain the time series of non-operating data as well as historical operating data. Analytical belonging to items such as power quality, reliability, health of analytical assets, etc. can be performed using data from historical data 136. Additionally, as discussed below, historical data 136 can be used to proceed to the grid topology at any point in time using the historical operational data in this repository in conjunction with the network topology as built stored in the connectivity data mart. In addition, the data can be stored as a flat record, as discussed below. Operational dataonals 137 Operational data 137 may comprise a real-time grid operational database. Operational data 137 can be incorporated in real distributed form with elements in the substations (with links in operational data 137) as well as the Operations center. Specifically, Operational Data 137 can maintain measurements of data obtained from sensors and devices coupled to grid components. Measurements of historical data are not maintained in this data store, instead being maintained in historical data 136. The database tables in Operational Data 137 can be updated with the most recent measurements obtained from these sensors and devices. FilesDFR / SER 138 Digital fault recorder and serial event recorder files; used for event analysis and data mining; files are generally created in substations by equipment and electricity distribution systems.
Table 1: Elements of the CORE INDE [00053] As discussed in Table 1, the real-time data bus 146 (which communicates the operation and non-operational data) and the complex real-time processing bus 147 (which communicates event processing data) in
Petition 870190108109, of 10/24/2019, p. 30/84
24/69 a single bus 346. An example of this is illustrated in block diagram 300 in figure 3.
[00054] As shown in figure 1, the buses are separated from the performance purposes. For CEP processing, low latency can be important for certain applications that are subject to very large message disruptions. Most grid data streams, on the other hand, are more or less constant, with the exception of digital fault recorder files, but these can usually be recovered on a controlled basis, while event breaks are asynchronous and random.
[00055] Figure 1 still shows additional elements in the operations control center 116 separate from CORE INDE 120. Specifically, figure 1 still shows the Meter Data Collection Station (s) system Collection Head End (s)) 153, which is responsible for communicating with meters (how to collect data from them and provide the data collected for the distribution of electricity). Demand response management system 154 is a system that communicates with equipment in one or more customer facilities that can be controlled by the distribution of electricity. The Downtime Management System 155 is a system that helps distribute electricity in managing downtime by tracking the location of downtime, managing what is being shipped, and how they are being fixed. The power management system 156 is a transmission level control system that controls devices at substations (for example) in the transmission network. Distribution management system 157 is a distribution system level control system that controls devices at substations and feeder devices (for example) for distribution networks. IP Network Services
Petition 870190108109, of 10/24/2019, p. 31/84
25/69
Services) 158 is a collection of service operations on one or more servers that support IP- type communications (such as TCP / IP, SNMP, DHCP and FTP). Mobile Data System 159 is a system that transmits / receives messages to mobile data terminals in the field. Load Flow Circuit & Analysis, Planning, Lighting Analysis and Grid Simulation Tools 152 are a collection of tools used by a utility in grid design, analysis and planning. IVR (integrated voice response) and Call Management 151 are systems for handling customer calls (automated by attendants). Telephone calls arriving regarding downtime can be automatically or manually entered and forwarded to the downtime management system 155. The Work Management System 150 is a system that monitors and manages work orders. The geographic information system 149 is a database that contains information about where the assets are geographically located and how the assets are connected together. If the environment has a Service Oriented Architecture (SOA), SOA Operations Support 148 is a collection of services to support the SOA environment.
[00056] One or more of the systems in Operations Control Center 116, which are outside the CORE INDE 120, are legacy product systems that a product system that an electric power distributor may have. Examples of such legacy product systems include SOA Operations Support 148, Geographic Information System 149, Work Management System 150, Call Management 151, Circuit & Load Flow Analysis, Planning, Lighting Analysis and Simulation Tools Grade 152, Meter 153 Data Collection Terminal (s), Demand Response Management System
Petition 870190108109, of 10/24/2019, p. 32/84
26/69
154, Downtime Management System 155, Power Management System 156, Distribution Management System 157, IP Network Services 158, and Mobile Shipping Data System 159. However, these legacy product systems may not be able to process or handle data that is received from an intelligent grid. The INDE 120 CORE may be able to receive smart grid data, smart grid data processing, and transfer processed data to one or more legacy product systems in a way that legacy product systems can use (such as particular formatting that is for the legacy product system). In this way, CORE INDE 120 can be seen as middleware.
[00057] Operations control center 116, including CORE INDE 120, can communicate with Enterprise IT 115. Generally speaking, the functionality in Enterprise IT 115 comprises back-office operations. Specifically, IT Enterprise IT 115 can use the Enterprise Integration Environment Bus 114 to send data to various systems within Enterprise IT 115, including Business Data Warehouse 104, Business Intelligence Applications 105, Enterprise Resource Planning 106, Various Financial Systems 107, Customer Information System 108, Human Resources System 109, Asset Management System 110, Enterprise SO Support 111, Network Management System 112, Message Services Company 113. Enterprise IT 115 can also include a portal 103 to communicate with the Internet 101 through a firewall 102.
SUBSTATION INDE [00058] Figure 4 illustrates an example of high level architecture for the SUBSTATION INDE 180 group.
Petition 870190108109, of 10/24/2019, p. 33/84
27/69 address elements that are actually housed in substation 170 in a substation control housing, on one or more servers co-allocated with electronics and substation systems.
[00059] Table 2 below lists and describes certain group elements of SUBSTATION INDE 180. Data security services 171 may be a part of the substation environment; alternatively they can be integrated into the SUBSTATION INDE 180 group.
ELEMENTS OFBESTAÇÃO INDE description Data StorageNon-Operational 181 Performance and health data; this is a component of distributed historical data Operational data storage 182 Grid status data in real time; this is part of a real distributed database Stacking Interfacesce / Communications 187 Supprte for communications, including TCP / IP, SNMP, DHCP, SFTP, IGMP, ICMP, DNP3, IEC 61850, etc. 186 Distributed / Remote Computing Support Support for remote program distribution, interprocessing communication, etc. (DCE, JINI, OSGi, for example) Signal Processing /Waveform 185 Support for digital signal processing components in real time; data normalization; engineering unit conversions Process Processingprotection / classification 184 Support for real-time event flow processing, event / waveform detectors and classifiers (ESP, ANN, SVM, etc.)
Petition 870190108109, of 10/24/2019, p. 34/84
28/69
Substation Analytics183 Support for real-time programmable analytics applications; DNP3 scan master;Substation analytics can include real-time analysis of operational and non-operational data to determine whether an event has occurred. Event determination can be based on rules with rules determining whether one of a plurality of possible events occurs based on the data. Substation analytics may also include automatic modification of the substation's operation based on a given event. In this way, the grid (including several portions of the grid) can be self-healing. This self-healing aspect avoids the requirement that data be transmitted to a central authority, data being analyzed at the central authority, and a command being sent from the central authority to the grid before the grid problem is corrected. In addition to determining the event, substation analytics can also generate a work order for transmission to a central authority. The work order can be used, for example, to schedule a device repair, such as a substation. LAN 172 substation Make the local network inside the substation for several portions of the substation, such as transmitter transmitting microprocessor 173, instrumentation of substation 174, recorders of event files 175, and RTUs station 176. Security services171 The substation can communicate externally with several communication networks for electricity distribution through the security services layer.
Table 2 Elements of the INDE SUBSTATION [00060] As discussed above, different elements within the smart grid may include additional functionality including additional processing / analytical capabilities and database features. The use of this additional functionality, within several elements
Petition 870190108109, of 10/24/2019, p. 35/84
29/69 in the smart grid, allows distributed architectures with centralized application and network performance management and administration. For functional, performance and scalability reasons, an intelligent grid involving thousands to tens of thousands of SUBSTATIONS INDE 180 and tens of thousands to millions of network devices can include distributed processing, data management, and process communications.
[00061] SUBSTATION INDE 180 may include one or more processors and one or more memory devices (such as non-operational data from substation 181 and data from substation operations 182). Non-operational data 181 and data of substation operations 182 can be associated with and near the substation, as located in or on the SUBSTATION INDE 180. The SUBSTATION INDE 180 may also include components of the smart grid that are responsible for the grid observation capability at a substation level. The components of the SUBSTATION INDE 180 can provide three primary functions: acquisition of operational data and storage in the distribution of distributed operational data; acquisition of non-operational data and storage in history; and processing local analytics on a real-time signal processing basis (as a sub-second). Processing may include digital voltage signal processing and current waveforms, detection and classification processing, including event flow processing; and communication of processing results to local systems and devices as well as to systems in the operations control center 116. Communication between SUBSTATION INDE 180 and other devices on the grid can be by electrical wire, wireless, or a combination of wired and wireless. For example, data transmission from SUBSTATION INDE 180 to operations control center 116 can be over wire
Petition 870190108109, of 10/24/2019, p. 36/84
30/69 electric. The SUBSTATION INDE 180 can transmit data, such as operating / non-operating data or event data, to operations control center 116. Routing device 190 can route the transmitted data to one of the operational / non-operating data buses 146 or event bus 147. [00062] Demand response optimization for distribution loss management can also be performed here. This architecture is in line with the distributed application architecture principle discussed earlier.
[00063] For example, connectivity data can be duplicated at substation 170 and operations control center 116, thereby allowing a substation 170 to operate independently even if the data communications network for operations control center 116 is not. functional. With this information (connectivity) stored locally, substation analytics can be performed locally even if the communication link to the operations control center is down.
[00064] Similarly, operational data can be duplicated at the operations control center 116 and at substations 170. Data from sensors and devices associated with a particular substation can be collected and the last measurement can be stored in this data store at the substation. The data structures of the operational data store can be the same and therefore the database links can be used to provide seamless access to the data residing in the substations through the instance of operational data storage in the control center. This provides a number of advantages including relieving data replication and allowing substation data analytics, which are more time sensitive, to occur locally and without security in the availability of communication beyond the substation. A-N-A
Petition 870190108109, of 10/24/2019, p. 37/84
31/69 lithic data at the operations control center 116 level may be less time sensitive (as operations control center 116 can typically examine historical data to discern patterns that are more productive rather than reactive) and can be able to get around the problems of the communications network, if any.
[00065] Finally, historical data can be stored locally in the substation and a copy of the data can be stored in the control center. Or, database links can be configured on the repository instance at operations control center 116, providing the operations control center with access to data at individual substations. Substation analytics can be performed locally at substation 170 using the local data store. Specifically, using the additional intelligence and storage capacity in the substation allows the substation to analyze itself and correct itself without input from a central authority. Alternatively, historical / collective analytics can also be performed at the level of the operations control center 116, accessing data in the instances of the local substation using the database links.
INDE DEVICE [00066] The INDE 188 DEVICE group can comprise any variety of devices within the smart grid, including multiple sensors within the smart grid, such as several 189 network distribution devices (for example, line sensors on the power lines ), 163 meters at the customer's premises, etc. The DEDE 188 DEVICE group may comprise a device added to the grid with particular functionality (such as an Intelligent Remote Terminal Unit (RTU) that includes dedicated programming), or may comprise an existing device within the
Petition 870190108109, of 10/24/2019, p. 38/84
32/69 grid with added functionality (such as an existing open architecture pole top RTU that is already in place on the grid that can be programmed to create a smart line sensor or smart grid device). The INDE 188 DEVICE can also include one or more processors and one or more memory devices.
[00067] Existing network devices cannot be opened from a software standpoint, and may not be able to support much in the way of modern network or Serbian software. Existing network devices may have been designed to acquire and store data for occasional downloading to some other device, such as a laptop computer, or to transfer batch files over the PSTN line to a remote host on demand. These devices may not be designed for operation in a digital network environment in real time. In such cases, data from the grid device can be obtained at substation level 170, or at the level of operations control center 116, depending on how the existing communications network has been designated. In the case of meter networks, it will usually be the case that the data is obtained from the meter data collection mechanism, since the meter networks are normally closed and the meters may not be addressed directly. As these networks evolve, meters and other network devices can be individually addressable, so that data can be transported directly to where it is needed, which may not necessarily be the operations control center 116, but it can be any place on the grid.
[00068] Devices such as faulty circuit indicators can be paired with wireless network interface cards, for connection over wireless networks of modest speed (such as 100 kbps). These devices can report status by exception and perform pre-defined functions
Petition 870190108109, of 10/24/2019, p. 39/84
33/69 fixed programmed. The intelligence of many network devices can be increased using local smart RTUs. Instead of having poletop RTUs that are designed as fixed-function closed architecture devices, RTUs can be used as open architecture devices that can be programmed by third parties and that can serve as an INDE 188 DEVICE in the INDE Reference Architecture. In addition, meters at customers' facilities can be used as sensors. For example, meters can measure consumption (how much energy is consumed for billing purposes) and can measure voltage (for use in volt / VAr optimization).
[00069] Figure 5 illustrates an example architecture for the DEDE 188 DEVICE group. Table 3 describes the right elements of the INDE 188 DEVICE. The intelligent grid device can include an embedded processor, so that the processing elements are less like SOA services and more like real-time program library routines, since the DEVICE group is implemented in a dedicated real-time DSP or microprocessor.
AVAILABLE ELEMENTSINDE SITIVO description 502 ring plugs Digital local circular buffer storage for waveform samples from analog transducers (voltage and current waveforms, for example) that can be used to hold data for waveforms at different time periods so that an event is detected, the waveform data leading to the event can also be stored 504 Device status buffers Buffer storage for external device status and state transition data Frequency trackerthree phases 506 Computes an estimate of the execution of the energy frequency of all three phases; used to correct
Petition 870190108109, of 10/24/2019, p. 40/84
34/69
frequency for other data as well as grid stability and power quality measures (especially when referring to DG) Fourier transform block508 Conversion of time domain to frequency domain waveforms to enable frequency domain analytics Time domain signal analytics 510 Time domain signal processing; transient extraction measures and envelope behavior Frequency domain signal analytics 512 Signal processing in the frequency domain; RMS extraction and energy parameters Secondary signal analytics 514 Calculation and compensation of phasors; calculation of selected error / failure measures Tertiary signal analytics516 Synchrophasoral calculation based on a schedule ofGPS and a system reference angle Event triggering and analysis518 Processing of all analytics for event detection and file capture trigger. Different types of INDE DEVICES may include different analytical event capabilities. For example, a line sensor can examine ITIC events by examining peaks in the waveform. If a peak occurs (or a series of peaks occurs), the line sensor, with the event analytical capability, can determine that an event has occurred and can also provide a recommendation as to the cause of the event. The capacity of the analytical event can be based on rules, with different sense rules used for different INDE DEVICES and different applications. File storage - capture / format / transmit 520 Ring buffer data capture based on event triggers 522 waveform flow service Support for waveform flow to a remote display client
Petition 870190108109, of 10/24/2019, p. 41/84
35/69
Communications Stacking Support for network communications and remote program loading GPS 524 Stopwatch It provides a high-resolution stopwatch to coordinate applications and synchronize data collection across a wide geographic area. The generated data may include a time stamp of the GPS 526 data structure. Status Analytics 528 Data capture for status messages
Table 3 Elements of the INDE DEVICE [00070] Figure 1 further illustrates customer installations 179, which may include one or more Smart Meters 163, a home monitor 165, one or more sensors 166, and one or more controls 167. In practice , sensors 166 can record data on one or more devices at customer premises 179. For example, a sensor 166 can record data on various main mechanisms within customer premises 179, such as the furnace, hot water heater, air conditioner, etc. Data from one or more sensors 166 can be sent to Smart Meter 163, which can package the data for transmission to operations control center 116 via communications network 160. In-house monitor 165 can provide the buyer with customer facilities an output device for viewing, in real time, data collected from the Smart Meter 163 and one or more sensors 166. In addition, an input device (such as a keyboard) can be associated with the monitor at home 165 in a way that the customer can communicate with the operations control center 116. In one embodiment, the monitor at home 165 can comprise a computer resident on the customer's premises.
[00071] Client facilities 165 can also include controls 167 that can control one or more devices at client facilities 179. Various mechanisms at client facilities 179 can be controlled, such as the heater, air conditioning, etc., depending on
Petition 870190108109, of 10/24/2019, p. 42/84
36/69 of the operations control center commands 116.
[00072] As depicted in figure 1, customer 169 facilities can communicate in a variety of ways, such as over the Internet 168, the public telephone network (PSTN) 169, or over a dedicated line (such as through the collector 164). Through any of the communication channels listed, data from one or more customer facilities 179 can be sent. As shown in figure 1, one or more customer facilities 179 may comprise an Intelligent Meter Network 178 (comprising a plurality of Intelligent Meters 163), sending data to a collector 164 for transmission to operations control center 116 via a electrical distribution management network 160. In addition, multiple sources of distributed energy generation / storage 162 (such as solar panels, etc.) can send data to a monitor control 161 for communication with the operations control center 116 through the electricity distribution management network 160.
[00073] As discussed above, devices on the power grid outside of operations control center 116 may include processing and / or storage capacity. The devices may include the SUBSTATION INDE 180 and the DEVICE INDE 188. In addition to the individual devices on the power grid, including additional intelligence, the individual devices can communicate with other devices on the power grid in order to exchange information (including sensor data and / or analytical data (such as event data)) in order to analyze the state of the energy grid (such as fault determination) and in order to change the state of the energy grid (as correcting faults). Specifically, individual devices can use the following: (1) intelligence (such as processing power); (2) storage (as distributed storage I discussed
Petition 870190108109, of 10/24/2019, p. 43/84
37/69 of the above); and (3) communication (such as the use of one or more buses discussed above). In this way, the individual devices in the power grid can communicate and cooperate with each other without supervision by the operations control center 116.
[00074] For example, the INDE architecture described above may include a device that perceives at least one parameter in the feeder circuit. The device can also include a processor that monitors the perceived parameter in the feeder circuit and that analyzes the perceived parameter to determine the state of the feeder circuit. For example, the analysis of the perception parameter can comprise a comparison of the perceived parameter with a predetermined limit and / or it can comprise a trend analysis. One of such perceived parameters may include perception of waveforms, and such an analysis may comprise determining whether the perceived waveforms indicate a failure in the supply circuit. The device can also communicate with one or more substations. For example, a particular substation can supply power to a particular feeder circuit. The device can sense the state of the particular feeder circuit, and determine if there is a particular feeder circuit failure. The device can communicate with the substation. The substation can analyze the fault determined by the device and can take corrective measures on the fault (such as reducing and supplying power to the supply circuit). In the example of the device sending data indicating a failure (based on waveform analysis), the substation can change the power supply to the feeder circuit without input from the operations control center 116. Or, the substation can combine the data indicating the fault with information about other sensors to further refine the fault analysis. The substation can also communicate with the operations control center 116, as with the application of intelligence from the downtime
Petition 870190108109, of 10/24/2019, p. 44/84
38/69 validity and / or the application of failure intelligence. In this way, the operations control center 116 can determine the failure and can determine the length of the downtime (such as the number of houses affected by the failure). In this way, the device perceiving the state of the feeder circuit can cooperatively work with the substation in order to correct the potential failure with or without requiring the operations control center 116 to intervene.
[00075] As another example, a line sensor, which includes additional intelligence using processing and / or memory capacity, can produce grid status data in a portion of the grid (such as a feeder circuit). Grid status data can be shared with the demand response management system 155 in the operations control center 116. The demand response management system 155 can control one or more devices at the customer sites on the feeder circuit. response to the state of the line sensor grid data. In particular, the demand response management system 155 can command the power management system 156 and / or the distribution management system 157 to reduce the load on the feeder circuit by turning off mechanisms at customer sites that receive power from the feeder circuit. in response to the line sensor indicating a period of inactivity in the feeder circuit. In this way, the line sensor in combination with the demand response management system 155 can automatically deflect the load from a defective feeder circuit and then isolate the defect.
[00076] As in yet another example, one or more transmitters in the power grid may have a microprocessor associated with it. These transmitters can communicate with other devices and / or databases residing in the power grid in order to determine
Petition 870190108109, of 10/24/2019, p. 45/84
39/69 to report a fault and / or control the power grid.
INDS Concept and Architecture
Outsourced Smart Grid Data / Analytical Service Models [00077] An application for smart grid architecture allows electricity distribution to subscribe to data grid and analytical management services while maintaining traditional control systems and related in-house operating systems. In this model, electricity distribution can install and have grid sensors and devices (as described above), and can own and operate a grid data transport communication system, or can outsource it. Grid data can flow from electricity distribution to a remote Intelligent Network Data Services (INDS) host site, where data can be managed, stored and analyzed. The utility can then subscribe to data and analytics services under an appropriate service financial model. The utility can avoid the initial capital expenditure investment and the ongoing costs of managing, supporting, and updating the smart grid / analytical infrastructure data in exchange for fees. The INDE Reference Architecture, described above, lends itself to the outsourcing arrangement described here.
Architecture for INDS Smart Grid Services [00078] In order to implement the INDS services model, the INDE Reference Architecture can be partitioned into a group of elements that can be hosted remotely, and those that can remain in the utility. Figure 6 illustrates how the architecture of the electricity distributor can partner once the CORE INDE 120 has been transformed into a remote one. A server can be included as part of the CORE INDE 120 which can act as the interface for remote systems. For distribution systems
Petition 870190108109, of 10/24/2019, p. 46/84
40/69 energy, this may look like a virtual CORE INDE 602. [00079] As the whole block diagram 600 in figure 6 shows, the SUBSTATION INDE 180 groups and the INDE 188 DEVICE are unchanged from the one represented in figure 1. The multiple bus structure can also be used as the power distribution electric too.
[00080] The INDE CORE 120 can be remotely housed, as the block diagram 700 shown in figure 7. On the hosting site, the INDE CORE 120 can be installed as needed to support INDS utility subscribers (shown as a Hosting Center). North American INDS 702). Each CORE 120 can be a modular system, so adding a new subscription is a routine operation. A separate part of the electricity distributor can manage and support the software for one, some, or all of the INDES NUCLEUS 120, as well as the applications that are downloaded from the INDS hosting site for each SUBSTATION INDE 180 and DEVICES INDE 188 of utilities.
[00081] In order to facilitate communications, low-latency and high-bandwidth communications services, such as over the 704 network (for example, an MPLS or other WAN), can be used that can reach the distribution centers of distribution operations. electricity of the subscriber, as well as the INDS hosting sites. As shown in figure 7, several areas can be served, such as California, Florida, and Ohio. This modularity of operations not only allows efficient management of several different grids. It also allows for better inter-grid management. There are instances when a failure in one grid can affect operations in a neighboring grid. For example, a failure in the Ohio grid can have a ripple effect on operations at a neighboring grid, such as a Mid-Atlantic grid. Use the modular structure as shown in figure 7
Petition 870190108109, of 10/24/2019, p. 47/84
41/69 makes it possible to manage individual grids and manage inter-grid operations. Specifically, an entire INDS system (which includes a processor and memory) can manage the interaction between the various INDES 120 NUCLEUSS. This can reduce the possibility of a catastrophic failure that cascades from one grid to another. For example, a failure in the Ohio grid can cause a cascade to a neighboring grid, such as the mid-Atlantic grid. The INDE 120 CORE dedicated to managing the Ohio grid can attempt to correct the failure in the Ohio grid. And, the entire INDS system can try to reduce the possibility of a cascade failure occurring on neighboring grids.
Specific examples of functionality in CORE INDE [00082] As shown in figures 1, 6, and 7, several functionalities (represented by blocks) are included in CORE INDE 120, two of which represented are meter data management services (MDMS) 121 and analytics and measurement services 122. Because of the modularity of the architecture, several features, such as MDMS 121 and analytics and measurement services 122, can be incorporated.
Observability Processes [00083] As discussed above, an application services functionality can include observability processes. Observability processes can allow the utility to observe the grid. These processes can be responsible for interpreting the raw data received from all sensors and devices in the grid to transform them into actionable information. Figure 8 includes a listing of some examples of the observability processes.
[00084] Figure 9 illustrates a 900 flow diagram of Grid State Measurements & Operations Processes. As shown, the Data Scanner may require data from the meter, as shown
Petition 870190108109, of 10/24/2019, p. 48/84
42/69 in block 902. The order can be sent to one or more grid devices, substation computers, and RTU line sensor. In response to the request, devices can collect operation data, as shown in blocks 904, 908, 912, and can send data (such as one, some, or all operational data, such as Voltage, Current, Actual Energy, and Energy data Reactive), as shown in blocks 906, 910, 914. The data scanner can collect operational data as shown in block 926, and can send data to the storage of operational data, as shown in block 928. Data storage Operational data can store operational data, as shown in block 938. The operational data store can further send a snapshot of historical data, as shown in block 940, and the historical can store snapshots of data, as shown in block 942. [00085] The meter status application can send a meter data request to the DCE Meter, as shown in block 924, which in turn sends a request to one or more meters to collect meter data as shown in block 920. In response to the request, the one or more meters collect meter data, as shown in block 916, and send the voltage data to the DCE Meter, as shown in block 918. The DCE Meter can collect the voltage data, as shown in block 922, and send the data to the data requester, as shown in block 928. The meter status application can receive the meter data, as shown in block 930, and determine whether they are for single value process or a voltage profile grid state, as shown in block 932. If it is for single value process, the meter data is sent to the request process, as shown in block 936 If the meter data for storage to determine the state of the grid at a time in the future, the data
Petition 870190108109, of 10/24/2019, p. 49/84
43/69 of the meter are stored in the operational data store, as shown in block 938. The operational data store still sends a snapshot of the data to the history, as shown in block 940, and the history stores the data snapshots, as shown in block 942.
[00086] Figure 9 further illustrates actions related to the response to demand (DR). The answer to demand refers to the dynamic demand mechanisms for managing the customer's electricity consumption in response to supply conditions, for example, with electricity customers having to reduce their consumption in critical times or in response to market prices. This may actually involve decreasing the energy used or starting to generate the site that may or may not be connected in parallel with the grid. This can be different from energy efficiency, which means using less electricity to perform the same tasks, on an ongoing basis or whenever that task is performed. In response to demand, customers using one or more control systems, can reduce loads in response to a request for a utility or market price conditions. Services (lights, machinery, air conditioning) can be reduced according to a pre-planned load prioritization scheme during critical execution periods. An alternative to load reduction is the generation of electricity on site to supplement the power grid. Under tight electricity supply conditions, the response to demand can significantly reduce the peak price and, in general, electricity price volatility.
[00087] The demand response can generally be used to refer to mechanisms used to encourage consumers to reduce demand, thereby reducing peak demand for electricity. Since electrical systems are generally difficult to
Petition 870190108109, of 10/24/2019, p. 50/84
44/69 mentioned to match peak demand (more margin of error and unforeseen events), lowering peak demand can reduce the entire facility's requirements and capital costs. Depending on the generation capacity configuration, however, the response to demand can also be used to increase demand (load) in high production and low demand times. Some systems can thus encourage energy storage for arbitrage between periods of low and high demand (or low and high prices). As the proportion of intermittent energy sources, such as wind energy in a system, grows, the response to demand may become increasingly important for the effective management of the electricity grid.
[00088] The DR status application can request the available DR capacity, as shown in block 954. The DR management system can then request available capacity from one or more home DR devices, as shown in block 948. The one or more home devices can collect the DR capacity available in response to the request, as shown in block 944, and send the DR capacity and response data to the DR management system, as shown in block 946. The DR management system can collect the DR capacity and response data, as shown in block 950, and send the DR capacity and response data to the application of the DR state, as shown in block 952. The application of the DR state can receive DR capacity and response data, as shown in block 956, and send response capacity and data to operational data storage as shown in block 958. Operating data storage can store enhance DR capacity and response data, as shown in block 938. The operational data store can also send a snapshot of the data to the history, as shown
Petition 870190108109, of 10/24/2019, p. 51/84
45/69 displayed in block 940, and the history can set up the data snapshot, as shown in block 942.
[00089] The substation computer can request application data from the substation application, as shown in block 974. In response, the substation application can request application from the substation device, as shown in block 964. The substation device can collect the application data, as shown in block 960, and send the application data to the substation device (which may include one, some or all of the Voltage, Current, Actual Energy, and Reactive Energy data) as shown in the block 962. The substation application can collect the application data, as shown in block 966, and send the application data to the requester (which can be the substation computer), as shown in block 968. The substation computer can receive the application data, as shown in block 970, and send the application data to storage and send the application data to the operational data store, as shown located in block 972.
[00090] The measurement of the state of the grid and the process of operational data can comprise deriving the state of the grid and topology of the grid at a given point in time, as well as providing this information to another system and data storage. Subprocessing can include: (1) measuring and capturing grid status information (this refers to the operational data pertaining to the grid that were discussed earlier); (2) send grid status information to other analytical applications (this allows other applications, such as analytical applications, to access grid state data); (3) grid state snapshot persisting for connectivity / operational data storage (this allows updating grid status information for connectivity / operational data storage in the appropriate format as
Petition 870190108109, of 10/24/2019, p. 52/84
46/69 also forward this information to history for persistence so that a grid topology at a point in time can be derived at a point in time later); (4) derive the grid topology at a point in time based on the default connectivity and current grid state (this provides the grid topology at a given point in time by applying the point of time snapshot of the grid state in history to base connectivity in the storage of connectivity data, as discussed in more detail below); and (5) provide grid topology information for applications on request.
[00091] Regarding the sub-process (4), the grid topology can be derived for a predetermined time, such as in real time, 30 seconds ago, 1 month ago, etc. In order to recreate the grid topology, multiple databases can be used, and a program for accessing data in the multiple databases to recreate the grid topology. A database can comprise a relational database that stores data for basic connectivity (database connectivity). The connectivity database can maintain grid topology information as done in order to determine the baseline connectivity model. Asset and topology information can be updated in this database on a periodic basis, depending on updates to the power grid, such as adding or modifying circuits in the power grid (for example, additional feeder circuits that are added to the power grid. energy). The connectivity database can be considered static because it does not change. The connectivity database can change if there are changes in the structure of the power grid. For example, if there is a modification to the feeder circuits, such as the addition of a feeder circuit, the connectivity database may change.
Petition 870190108109, of 10/24/2019, p. 53/84
47/69 [00092] A second database can be used to store dynamic data. The second database can comprise a non-relational database. An example of a non-relational database may comprise a historical database, which stores non-operational time series data as well as operational data. The historical database can store a series of uniform records such as: (1) time stamp; (2) device ID; (3) a data value; and (4) a device status. Furthermore, the stored data can be compressed. Because of this, non-operational operation / data in the power grid can be easily stored, and can be managed even though a considerable amount of data may be available. For example, data on the order of 5 Terabytes can be online at any time for use in order to recreate the grid topology. Because the data is stored in a simple flat record (as with no organizational approach), it allows for efficient data storage. As discussed in more detail below, data can be accessed by a specific marker, such as data element identifiers.
[00093] Various analytics for the grid may want to receive, as input, the grid topology at a particular point in time. For example, analytics related to power quality, reliability, asset health, etc. can use the grid topology as an input. In order to determine the grid topology, the baseline connectivity model, as defined by the data in the connectivity database, can be accessed. For example, if the topology of a particular feeder circuit is desired, the baseline connectivity model can define the various switches on the particular feeder circuit in the power grid. After which, the historical database can be accessed (based on the particular time) in order to
Petition 870190108109, of 10/24/2019, p. 54/84
48/69 to determine the values of the switches on the particular feeder circuit. Then, a program can combine the baseline connectivity model data and the history database in order to generate a representation of the particular feeder circuit at a particular time.
[00094] A more complicated example to determine the grid topology may include multiple feeder circuits (for example, feeder circuit A and feeder circuit B) that have an interconnect switch and sectionalizing switches. Depending on the states of the switches, certain switches (such as the interconnect switch and / or the sectionalizing switches), sections of the feeder circuits may belong to feeder circuit A or feeder circuit B. The program that determines the grid topology can access the data from both the baseline connectivity model and the historical database in order to determine connectivity at a particular time (for example, whose circuits belong to feeder circuit A or feeder circuit B).
[00095] Figure 10 illustrates a flow diagram 1000 of non-operational data processes. The application of the non-operational statement may require non-operational data as shown in block 1002. In response, the data scanner can gather non-operational data as shown in block 1004, in which by various devices on the power grid, such as grid devices, substation computers, and RTU line sensors, can collect non-operational data as shown in blocks 1006, 1008, 1110. As discussed above, non-operational data can include temperature, power quality, etc. The various devices on the power grid, such as network devices, substation computers, and RTU line sensors, can send non-operational data to the data scanner, as shown in blocks 1012, 1014, 1116. The esca
Petition 870190108109, of 10/24/2019, p. 55/84
49/69 data neater can collect non-operational data as shown in block 1018, and sends non-operational data to the application of non-operational statements as shown in block 1020. The application of non-operational statements can collect non-operational data, as shown in block 1022, and send the collected non-operational data to the history as shown in block 1024. The history can receive non-operational data, as shown in block 1026, stores the non-operational data as shown in block 1028, and sends non-operational data for one or more analytical applications as shown in block 1030.
[00096] Figure 11 illustrates a 1100 flow diagram of the Event Management processes. Data can be generated from multiple devices based on various events in the power grid and send over event bus 147. For example, the meter's data collection mechanism can send power downtime / restore notification information to the event bus, as shown in block 1102. The RTUs line sensor generates a fault message, and can send the fault message to the event bus, as shown in block 1104. The substation can have the analytics generate a fault message. fault and / or inactivity period, and can send the fault message and / or inactivity period to the event bus, as shown in block 1106. The history can send signal behavior to the event bus, as shown in block 1108. And multiple processes can send data over event bus 147. For example, the failure intelligence process can send a failure analysis event until through the event bus, as shown in block 1110. The event bus can collect the various events, as shown in block 1114. And Complex Event Processing (CEP) services can process events sent
Petition 870190108109, of 10/24/2019, p. 56/84
50/69 via the event bus, as shown in block 1120. CEP services can process queries against multiple high-speed real-time event message streams. After processing by the CEP services, event data can be sent via the event bus, as shown in block 1118. And the history can via the event bus one or more event logs for storage, as shown in block 1116 In addition, event data can be received by one or more applications, such as the downtime management system (OMS), downtime intelligence, failure analytics, etc., as shown in block 1122. In this way, the event bus can send the event data to an application, thereby avoiding the silo problem of not making the data available to other devices or other applications.
[00097] Figure 12 illustrates a 1200 flow diagram of the Demand Response Signaling (DR) processes. DR can be ordered by applying the distribution operation, as shown in block 1244. In response, the grid's state / connectivity can collect DR availability data, as shown in block 1202, and can send the data, as shown in block 1204. The distribution operation application can distribute the optimization of DR availability, as shown in block 1246, through the event bus (block 1254), to one or more DR Management Systems. The DR Management System can send DR information and signals to one or more customer facilities, as shown in block 1272. To one or more customer facilities, it can receive DR signals, as shown in block 1266, and send the response DR, as shown in block 1268. DR Management can receive the DR response, as shown in block 1274, and send DR responses to one, some, or all data buses of the operations
Petition 870190108109, of 10/24/2019, p. 57/84
51/69 tions 146, the billing database, and the marketing database, as shown in block 1276. The billing database and the marketing database can receive responses, as shown in blocks 1284 , 1288. The data bus from operations 146 can also receive responses, as shown in block 1226, and send the DR responses and available capacity to the DR data collection, as shown in block 1228. The data collection from DR can process DR responses and available capacity, as shown in block 1291, and send the data to the operations data bus, as shown in block 1294. The operations data bus can receive availability and response from DR, as shown in block 1230, and send them to the grid state / connectivity. The grid state / connectivity can receive the data, as shown in block 1208. The received data can be used to determine the grid state data, which can be sent (block 1206) via data bus operations (block 1220 ). The distribution operation application can receive grid status data (as an event message for DR optimization), as shown in block 1248. Using grid state data and DR availability and response, the application of the grid distribution operation can perform distribution optimization to generate distribution data, as shown in block 1250. Distribution data can be retrieved by the operations data bus, as shown in block 1222, and can be sent to the extract application connectivity, as shown in block 1240. The operational data bus can send data (block 1224) to the application of the distribution operation, which in turn can send one or more DR signals to one or more DR Management Systems (block 1252). The event bus can collect signals
Petition 870190108109, of 10/24/2019, p. 58/84
52/69 for each of the one or more DR Management Systems (block 1260) and send the DR signals to each of the DR Management Systems (block 1262). The DR Management System can then process the DR signals as discussed above.
[00098] The communication operation history can send data to the event bus, as shown in block 1214. The communication operation history can also send data from the generation portfolio, as shown in block 1212. Or, an application, as a Ventyx®, it can request virtual power plant (VPP) information, as shown in block 1232. The operations data bus can collect VPP data, as shown in block 1216, and send the data to the application, as shown in block 1218. The application can collect VPP data, as shown in block 1234, perform system optimization, as shown in block 1236, and send VPP signals to the event bus, as shown in block 1238. The The event bus can receive the VPP signals, as shown in block 1256, and send the VPP signals to the application of the distribution operation, as shown in block 1258. The application of the distribution operation can then receive and process the event messages, as discussed above.
[00099] The connection statement application can extract New Consumer data, as shown in block 1278, to be sent to the Marketing Database, as shown in block 1290. New consumer data can be sent to grid state / connectivity, as shown in block 1280, so that grid state connectivity can receive new DR connectivity data, as shown in block 1210.
[000100] The operator can send one or more signals of invasion when applicable, as shown in block 1242. The signals of invasion can be sent to the application of the distribution operation. O
Petition 870190108109, of 10/24/2019, p. 59/84
53/69 intrusion signal can be sent to the power management system, as shown in block 1264, the billing database, as shown in block 1282, and / or the marketing database, as shown in block 1286.
[000101] As previously described, several devices within the electric power distribution grid can be controlled through commands generated from the CORE INDE 120 or another command site. The commands can be generated through manual input or they can occur through automatic generation. One, some, or all devices within the power distribution grid can receive one or more individual commands for the operation in a particular way. For example, Smart Meters 163 monitoring customer facilities 179 can receive the respective commands to disconnect, connect, or adjust the power being supplied to the associated customer facilities. Customer facility devices such as sensors 166 and controls 167, can be given commands to reduce power to a particular device as a primary tool. Electricity distribution consumers agree to have reduced energy in relation to the particular main mechanisms or other energy devices for various reasons, such as financial reasons or as part of an eco-favorable charge control strategy, for example. Typically, adjusting each device to be disconnected, cycled, or controlled that consumes more or less energy individually will not have a great effect on the operation of an electricity distribution grid. However, if sufficient devices are controlled in such a way within the small enough time window, the combined effect of all devices operating simultaneously or relatively close in time, may have undesirable effects on the electricity distribution grid as causing or aidionanPetition 870190108109 , of 10/24/2019, p. 60/84
54/69 of grid instability. For example, if sufficient devices from the customer's premises are commanded to shut down over a number of customer's premises 179 within the relatively small time window, the reduction in energy can cause a blackout over a large area. Problems of this nature can arise through inadvertent or coincidental command entry or through malicious activity.
[000102] Figure 13 is an example of a command filter system including a 1300 command filter module configured to filter commands generated to control various devices within the electricity distribution grid. The 1300 command filter module can receive some or all commands to be received by devices within the power distribution grid and determine, before receiving on devices, whether executing the commands would result in an undesirable effect within the distribution grid. of electricity. The 1300 command filter module can authorize some or all of the commands to be executed and transmit the commands authorized to be received by the respective devices for execution or they can prevent unauthorized commands from being received by the respective devices for execution.
[000103] In one example, the command filter module 1300 can be run on one or more computer devices 1301 having a processor 1302 in communication with a memory 1304. The term module can be defined to include one or a plurality of modules executable. As described here, modules are defined to include software, hardware or some combination of them that can be executed by the 1302 processor. Software modules can include instructions stored in 1304 memory, or another memory device, that are executed by the 1302 processor or another processor. Hardware modules can include multiple devices, with
Petition 870190108109, of 10/24/2019, p. 61/84
55/69 components, circuits, gates, circuit edges, and the like that are executable, directed, and / or controlled for performance by processor 1302. Memory 1304 may include one or more memories and may be computer storage media or memories , such as a cache, buffer, RAM, removable media, hard disk, or other readable computer storage media. Readable computer storage media can include various types of volatile and non-volatile storage media. Various processing techniques can be implemented by processor 1302 such as multiprocessing, multitasking, parallel processing, and the like, for example. Processor 1302 can include one or more processors.
[000104] In one example, the 1300 command filter module can be one or more software modules stored in memory 1304 and executed by processor 1302. The 1300 command filter module can include several sub-modules to be executed by processor 1302. Processor 1302 can be located inside CORE INDE 120 or some other site within the grid of electric power distribution. In one example, the 1300 command filter module can be run to operate on event bus 147. [000105] The 1300 command filter module can receive 1306 commands to control device operation within the power distribution grid. . Commands 1306 can represent commands intended to be executed by the respective devices simultaneously or within a predetermined time window. For example, commands 1306 can be intended for receipt by devices within the client facility 179 connected to sensors 166, controls 167, or a monitor at home 165.
[000106] Referring now to figure 14, an example of the module of
Petition 870190108109, of 10/24/2019, p. 62/84
56/69 command filter 1300 configured to run on real-time complex event processing bus 147 is shown. The example in figure 14 can be implemented in the INDE architecture described in relation to figures 1-6. As shown in figure 14, several devices within the electrical distribution grid can be implemented through manual control. For example, a graphical user interface (GUI) 1402 can be used by an operator to transmit meter commands (MC) 1404, such as meter commands to connect / disconnect, to be received by multiple Smart Meters 163 within the Meter Network Intelligent 178. Meter commands 1404 can be communicated through devices capable of transmitting data from meter 1405 received from Smart Meters 163. GUI 1402 can transmit commands from meter 1404 to the data management system of meter 121. The commands of the 1404 meter can then be received by a 1406 meter data collection mechanism, which can be software modules, hardware modules, or a combination configured for collection data, commands, events, and any other data regarding the Meters Intelligent 163 within the electricity distribution system. In one example, the meter data collection mechanism 1406 may reside at the end (s) of the head of the meter data collection 153. In an alternative example, the data collection mechanism of the meter 1406 may be distributed in such a way that a plurality of 1406 meter data collection mechanisms exist within the electricity distribution grid. Data collected by the data collection mechanism of meter 1406 can be transmitted to and stored by one or more data repositories of meter 133 communicated during the operational / non-operational data bus 146.
Petition 870190108109, of 10/24/2019, p. 63/84
57/69 [000107] Meter commands 1404 can be received by event bus 147 and command filter module 1300. Command filter module 1300 can analyze meter commands 1404 to determine whether, upon execution, Controls moderate to cause an undesirable effect within the electrical distribution grid. The command filter module 1300 can transmit authorized meter commands (AMC) 1407 for reception and execution by the respective Smart Meters 163. Authorized meter commands 1407 can be transmitted to a 1408 meter command processor. meter 1408 can determine the content and intended container of authorized meter commands 1407. Meter command processor 1408 can transmit commands to a 1410 meter communications network. The 1410 meter communications network can be configured to transmit data from the meter, meter events, and meter commands for all or some of the Smart Meters 163 coupled to the Smart Meter Network 178 within the power distribution grid. Commands from authorized meters 1407 can finally be received by Smart Meters 163 at customer premises 179 for connecting or disconnecting the power distribution grid. A GUI 1411 can receive 1404 meter commands to be directly transmitted to the 1406 meter data collection mechanism.
[000108] The various devices in the customer installation can receive DR (DRC) 1412 commands that are authorized by the 1300 command filter module. For example, GUI 1414 can be used by an operator to manually enter DR 1412 commands. DR 1412 commands can be received from GUI 1414 by a VPP 1416 dispatch system. DR 1412 commands can be
Petition 870190108109, of 10/24/2019, p. 64/84
58/69 based on various considerations such as price, environmental factors, and load control. The VPP 1416 dispatch system can be configured to receive DR 1412 Commands and determine the devices at the customer's premises to be controlled based on DR 1412 Commands. DR 1412 Commands can be received by the operating / non-operating data bus 146 In other examples, DR Commands 1412 can be transmitted from the VPP 1416 dispatch system to event bus 147.
[000109] DR Commands 1412 can be received from the operating / non-operating data bus 146 by a DR signal distribution and DR response and data collection mechanism (DCE) system 1418. The distribution of DR signals and the DR 1418 response data collection mechanism can be configured to operate within the CORE INDE 120, such as within the DR 154 management system, or at some other remote site within or from the electric power distribution grid. . DR 1412 Commands can be analyzed by DR signal distribution and DR response distribution and DCE 1418 system to determine how the response to the desired demand should be performed, how to determine the particular devices receiving the commands. The DR signal distribution and DR response and DCE 1418 system can divide the DR 1412 Commands into individual devices or groups of dependent devices.
[000110] DR 1412 Commands can then be received by event bus 147 and command filter module 1300 to determine whether DR 1412 Commands are authorized to be executed by devices within client facilities 179. If DR Commands 1412 are to be executed by the devices inside the customer premises 179, Authorized DR commands (ADRC) 1417 can be transmitted by the co filter module
Petition 870190108109, of 10/24/2019, p. 65/84
59/69 I send 1300 to a DR 1420 command processor. The DR 1420 command processor can determine the contents of authorized DR 1417 Commands and identify the premises of the particular customer 179 and devices within the premises of the private customer 179 to receive the Authorized DR 1417 commands. Authorized DR 1417 commands can be transmitted by the DR 1420 command processor to a DR 1422 communications network that can be interconnected with all or some of the client facilities 179 within the authorized command distribution grid. Authorized DR 1417 Commands can be received by devices intended within each customer installation 179 and can be distributed via home DR gateway 1421.
[000111] Other types of commands can be manually entered into the electric power distribution grid, such as switching commands. For example, switching commands (SC) 1424 can be entered by an operator through a GUI 1425. In one example, switching commands 1424 can be intended to connect or disconnect switching devices 1436 within the power distribution grid , such as sectionalizers, restorers, and interconnections, for example. The reset commands 1424 can be received by the sectionalizing controls 1426 that can be configured to process switching commands 1424 and determine the particular devices in the power distribution grid that can be operated in order to execute switching commands. Switch commands 1424 can be received by event bus 147 and processed by command filter module 1300. Authorized switch commands (ASC) 1430 can be transmitted to one or more control command processors 1434. Command processors from control unit 1434 can transmit authorized switching commands
Petition 870190108109, of 10/24/2019, p. 66/84
60/69
1430 for the respective switching devices 1436 intended to receive a particular authorized switching command 1430.
[000112] Compensator commands (CC) 1427 can be entered by an operator through GUI 1429. Compensator commands 1427 can be intended for reception by devices used to compensate for the conditions of the electricity distribution grid such as capacitors, temperature compensators line drop, load regulators (LTCs), and voltage regulators, for example. The compensator command 1427 can be received by the compensator controls 1431 configured to determine the content of the compensator command 1427 and format the compensator command 1427 for reception by the particular compensator devices intended to receive the compensator command 1427. The compensator command 1427 can be transmitted by compensator controls 1431 to event bus 147 to be processed by command filter module 1300. Authorized compensator command (ACC) 1432 can be transmitted to control command processors 1434. Command processors control unit 1434 can provide the authorized compensating control 1432 for the compensating devices intended for 1438.
[000113] Referring again to figure 13, the detailed operation of the 1300 command filter module can be explained further. Commands 1306 can include device commands such as meter commands 1404, DR commands 1416, switch commands 1424, and compensator commands 1427. Upon receipt by the command filter module 1300, commands 1306 can be received by a module command reception module 1308. The command reception module 1308 can process commands 1306 to determine the desired container contents of each of the
Petition 870190108109, of 10/24/2019, p. 67/84
61/69 commands 1306. Command reception module 1308 can provide processed commands 1310 to a rule enforcement module 1312. Commands processed 1310 may include additional data related to the processing performed by command reception module 1308, a reformat of the 1306 commands, or both. [000114] Upon receipt of processed commands 1310, the application module for rules 1312 can apply a predetermined set of rules for processed commands 1310 to authorize, if any, commands 1306 for execution. The rules application module 1312 can retrieve a rule data set 1314 containing one or more rules for application for the processed commands 1310. Based on the application of the rules, the rules application module 1312 can determine which commands 1306 of the processed commands 1310 are authorized for execution. The rules 1312 application module can authorize some of the 1310 processed commands for execution or it can authorize the 1310 processed commands in volume, so that all commands being analyzed by the rules 1312 application module are authorized or rejected together.
[000115] Upon authorization, the 1312 rules application module can generate a 1316 authorization data set containing the 1306 commands together with the 1312 rules application module authorization decision. The 1316 authorization data set can be received by a 1318 command transmit module. The 1318 command transmit module can identify one, some, or all commands authorized to be executed by a respective device. Upon identification, the command transmit module 1318 can transmit authorized commands 1320 to be ultimately received by the intended device. For commands not authorized for execution, the 1318 command transmit module can generate a
Petition 870190108109, of 10/24/2019, p. 68/84
62/69 rejection message 1321 for each unauthorized command to be relayed to where the unauthorized command originated for notification, such as one of GUIs 1402, 1411, 1414, and 1425. In one example, the 1300 command filter module it can be executed on event bus 147, allowing command filter module 1300 to transmit authorized commands 1320 or to let event bus 147 perform the transmission.
[000116] The rules contained in rule data set 1314 can be static in nature or can be dynamic based on real-time conditions within the electricity distribution grid. Static rules can be unchanged, regardless of the example of the current electricity distribution grid example. For example, a static rule may exist limiting the number of devices that can be connected or disconnected within the predetermined time window, such as Smart Meters 163, devices within client facilities 179, switching devices 1436, or compensator 1438, or any combination. In one example, a rule can be directed towards limiting the number of devices at the example customer facilities (for example, industrial pumps) can be started, such as six starts per hour. In another example, a rule may be directed towards limiting the number of Smart Meters 163, which can be turned on or off within the predetermined amount of time. Other rules may apply regarding the duration that a device can be commanded to be connected or disconnected.
[000117] The rules application module 1312 can also be configured to enforce the rules of the rules data set 1314 with regard to the dynamic nature of an electricity distribution grid. The re application module
Petition 870190108109, of 10/24/2019, p. 69/84
63/69 gras 1312 can be configured to examine the historical operation data of the electricity distribution grid. In one example, the rule application module 1312 can be configured to retrieve information from historical data 136. The rule application module 1312 can apply to a rule in the rule data set 1314 for commands processed 1310 while doing cross reference of historical data 136. For example, rule data set 1314 may include a rule based on the number of disconnect / connection devices independent of a particular device. For example, only a predetermined number of devices can be left to be disconnected or connected within the predetermined amount of time regardless of the devices involved. If 1306 commands are directed to disconnect or connect more devices than the number of device inputs, the 1300 command filter module can analyze historical data 136 to determine whether patterns in the previous command, such as those in 1306 commands, resulted in undesirable effects within the electricity distribution grid. If, based on historical data, the connection or disconnection of particular devices to which the commands correspond, have not previously caused any adverse consequences on the electricity distribution grid, the commands can be authorized for execution. [000118] In a rules enforcement configuration using dynamic conditions, the rules enforcement module 1312 can also retrieve 1313 connectivity data from a connectivity datamart 131 while applying the rules. Based on historical data 136, connectivity data 131, and rule data set 1314, rule application module 1312 can determine whether current conditions in the electricity distribution grid will be undesirably affected to a degree that commands 1306 not of
Petition 870190108109, of 10/24/2019, p. 70/84
64/69 shall be authorized for execution. In one example, the rule application module 1312 may include a forecast module 1322 to determine command authorization based on historical data 136, connectivity data 1313, and rule data set 1314. The forecast module 1322 can predict the effect on the electricity distribution grid by authorizing some or all of the commands. The forecast module 1322 can generate predicted effects regarding the behavior of the electricity distribution grid based on various permutations of combinations of the 1306 commands. In one example, the forecast module 1322 can select a combination of 1306 commands for authorization, identified as the largest number of 1306 commands to be executed. In other examples, the forecast module 1306 can identify commands 1306 based on other considerations such as closer and less than a grid disturbance input. The disturbance entry in the grid can represent the minimum disturbance allowed in the electricity distribution grid, when executing device commands, such as 1306 commands. In alternative configurations, various conditions, static or dynamic, can be monitored by making authorization decisions regarding commands 1306. For example, voltage conditions, current conditions, or both can be monitored in strategic portions of the electricity distribution grid. Environmental conditions can also be monitored, such as room temperature.
[000119] Pre-configured power distribution grids can have different access points for communication, when being retrofitted with smart devices. Pre-configured power distribution grids can also include communications networks other than those described in relation to figure 14. Figures 15-17 illustrate examples of energy distribution grids
Petition 870190108109, of 10/24/2019, p. 71/84
65/69 electrical power having alternative communications network configurations. In figures 15-17, the command filter module 1300 can be executed in different portions in the electric power distribution grid with respect to devices configured to receive connect / disconnect commands, for example. In figure 15, an electrical power distribution grid 1500 similar to the configuration in figure 1 can be configured with a single communications network bus 1502 instead of distributed communications networks, such as DR communications networks and the communications network of the meter. In figure 15, the command filter module 1300 can be run to operate on the bus of the 1502 communications network. The configuration in figure 15 is similar to that in figure 13 in that the initial commands can be processed similarly before reaching the command filter module 1300. However, by providing authorization determinations, command module 1300 can transmit authorized meter commands 1407 directly to private Smart Meter 163, authorized commands DR 1417 to devices on customer premises 179 , authorized switching commands 1430 for switching devices 1436 and authorized compensating commands 1432 for compensating devices 1438. The communications network bus 1502 can be configured to interact with the command filter module 1300 not only to perform the command filter module 1300, but to direct authorized commands them to the respective device for execution.
[000120] Figure 16 is a schematic of an electric power distribution grid 1600. In the electric power distribution grid 1600, a single communications network bus 1602 can be implemented. The communications network bus 1602 can be implemented by third party providers or can be included in the
Petition 870190108109, of 10/24/2019, p. 72/84
66/69 electric power distribution grid 1600. Event bus 147 can communicate with communications bus 1602. Event bus 147 can run command filter module 1300 and receive commands 1404, 1412, 1424, and 1427. Authorized commands 1407, 1417, 1430, and 1432 can be distributed over the communications network bus 1602 to the various devices intended to receive the various device commands. The communications network bus 1602 can recognize the intended container of the authorized commands and, therefore, transmit the authorized commands.
[000121] Figure 17 is a schematic of a 1700 electric power grid. In the 1700 electric power grid, a distributed event bus is used. The event bus can include event buses 1702, 1704, and 1706, which each can perform, in a manner similar to that described with respect to event bus 147. One difference is that the distributed event buses 1702, 1704, and 1706 are not in communication with each other. In figure 17, event bus 1702 is configured to run command filter module 1300 for meter commands 1404 and Commands DR 1412. Meter commands 1404 can be processed by command filter module 1300 in such a way as described with respect to figure 13. Authorized meter commands 1407 can be transmitted to meter data collection monitor 1406, which can transmit commands to the meter communications network 1410. Authorized meter commands 1407 can be transmitted over the communications network from meter 1410 to Smart Meter intended 163. Similarly, event bus 1704 can also receive meter commands 1404 from GUI 1411. The 1300 command filter module from the event bus
Petition 870190108109, of 10/24/2019, p. 73/84
67/69
1704 can authorize meter commands 1404 and transmit authorized meter commands 1407 to meter data collection monitor 1406.
[000122] DR 1417 authorized commands can be transmitted for DR signal distribution and DR DCE 1418 response. DR signal distribution and DR response DCE 1418, can transmit authorized DR 1417 commands to the network DR communications 1422 for subsequent transmission to the relevant device of the customer installation via home DR gateway 1421. Switch commands 1424 and compensator commands 1427 can be received by event bus 1706 and filtered by the command filter module 1300. Authorized switching commands 1430 and authorized compensator commands 1432 can be transmitted to control command processors 1427 and subsequently routed to the relevant devices.
[000123] Figure 18 is an example of the operational flow of the 1300 command filter module. The 1300 command filter module can receive device commands (block 1800), like 1306 commands. The 1300 command filter module can determine if the commands received are invalid (block 1802). If one or more of the 1306 commands are invalid, the 1300 command filter module can monitor for receipt of subsequent device commands. In alternative examples, the 1300 command filter module may generate an invalid message for each command of the 1306 commands considered invalid. An invalidation message can be transmitted by the 1300 command filter module to the command source, such as a GUI used to enter commands. A sub-module of the 1300 command filter module can generate an invalidity message, such as the command receiving module 1308.
Petition 870190108109, of 10/24/2019, p. 74/84
68/69 [000124] The command filter module 1300 can determine the content of each valid command 1306 (block 1804). The determination can be carried out by the command receiving module 1308. By determining the content of valid commands 1306, the command filter module 1300 can retrieve relevant historical data from historical data 136 (block 1806). The command filter module 1300 can also retrieve relevant connectivity data 1313 from connectivity data datamart 131 (block 1808). Upon receipt of connectivity data 1313, rule application module 1312 can implement prediction module 1322 (block 1810) to determine the possible effect of executing commands 1306.
[000125] Rules application module 1312 can apply the relevant rules from rule data set 1314 (block 1812) to determine whether the predicted results violate any of the rules. The decision to authorize all 1306 commands (block 1814) can be made by the rules application module 1312. If all 1306 commands are authorized, commands 1306 can be transmitted by the command transmit module 1318 to be received by the respective devices ( block 1816). If all 1306 commands are not authorized, a decision can be made to determine whether any of the commands are authorized (block 1818). If none of the 1306 commands are authorized, rejection messages 1321 can be generated by the command transmit module 1320 (block 1820) and transmitted to a source of the respective commands 1306. If any of the 1306 commands must be authorized, the rejection messages 1321 can be transmitted to unauthorized commands 1306 by the command transmitting module 1318 (block 1822) and authorized commands can be transmitted to be received by the respective device.
Petition 870190108109, of 10/24/2019, p. 75/84
69/69 [000126] While this invention has been shown and described in connection with preferred embodiments, it is evident that certain changes and modifications in addition to those mentioned above can be made from the basic features of that invention. In addition, there are many different types of computer software and hardware that can be used in the practice of the invention, and the invention is not limited to the examples described above. The invention has been described with reference to the acts of symbolic representations of operations that are performed by one or more electronic devices. As such, it will be understood that such acts and operations include manipulation by the processing unit of the electronic device for electrical signals representing data in a structured form. This manipulation transforms the data or keeps it in places in the electronic device's memory system, which reconfigures or, on the contrary, alters the operation of the electronic device in a way well understood by those skilled in the art. The data structures, in which the data is kept, are physical locations of memory that have particular properties defined by the format of the data. Although the invention is described in the previous context, it is not intended to be limiting, as those skilled in the art will realize that the described acts and operations can also be implemented in the hardware. Thus, it is the intention of the Requesters to protect all variations and modifications within the valid scope of the present invention. The invention is intended to be defined by the following claims, including all equivalents.

权利要求:
Claims (8)
[1]
1/3
1. Electric power grid control filter system characterized by the fact that it comprises:
a memory configured to store a plurality of device command rules; and a command filter module stored in memory and executable by a processor configured to:
receive a plurality of commands, where each of the plurality of commands is received from a respective source device, and where each of the plurality of commands is configured to provide a command for execution by a respective device electrically coupled to a electric power distribution grid in a customer installation, where the command comprises a demand response command that affects the energy consumption of the respective device;
retrieving at least one device command rule from the plurality of device command rules;
recover historical data from the electricity distribution grid corresponding to the operation of the respective device, according to the past execution of the plurality of commands;
determine when at least one command from the plurality of commands is authorized for execution by the respective device, comprising:
analyze at least one device command rule and the historical data of the electricity distribution grid;
determine whether the execution of at least one command by the respective device would result in an undesirable effect within the electric power distribution grid; and transmit at least one command to be received by the respective device only when the at least one command is
Petition 870190108109, of 10/24/2019, p. 77/84
[2]
2/3 determined to be authorized for execution by the respective device.
2. Electric power grid command filter system, according to claim 1, characterized by the fact that the command filter module is still executable to generate a rejection message configured to be received by the respective control device. origin when at least one command is determined to be disallowed for execution by the respective device, where the rejection message is indicative of at least one command being disallowed for execution by the respective device.
[3]
3. Electric power grid control filter system, according to claim 1, characterized by the fact that the control filter module is still executable for:
retrieve connectivity data from the electricity distribution grid corresponding to the current operating conditions of the electricity distribution grid; and determining when at least one command from the plurality of commands is authorized for execution by the device based on the connectivity data of the electricity distribution grid.
[4]
4. Electric power grid control filter system, according to claim 3, characterized by the fact that the control filter module is still executable for:
determine at least one predicted effect of the electricity distribution grid from the authorization of at least one command based on the historical data of the electricity distribution grid and the connectivity data of the electricity distribution grid; and determine when at least one plurality command
Petition 870190108109, of 10/24/2019, p. 78/84
3/3 of commands are authorized for execution by the device based on at least one predicted effect.
[5]
5. Electric power grid control filter system, according to claim 4, characterized by the fact that at least one device control rule is a minimum disturbance limit of the electricity distribution grid, wherein the command filter module is still executable to determine when the at least one command of the plurality of commands is authorized to be executed by the device when the predicted effect is less than the minimum disturbance limit of the power distribution grid.
[6]
6. Electric power grid control filter system according to claim 1, characterized by the fact that at least one device control rule comprises limiting the device connection to a predetermined number of devices within a predetermined amount of time.
[7]
7. Electric power grid control filter system according to claim 1, characterized by the fact that at least one device control rule comprises limiting the restart of a device to a predetermined number of times within a predetermined amount of time.
[8]
8. Electric power grid command filter system, according to claim 1, characterized by the fact that the demand response command is based on at least one selected from the group consisting of a consideration of price, an environmental factor and load control.

类似技术:

---

公开号 | 公开日 | 专利标题

---

US10833532B2|2020-11-10|Method and system for managing a power grid

---

BR112012021714B1|2020-02-04|electric power grid command filter system

---

US9897665B2|2018-02-20|Power grid outage and fault condition management

---

EP3065245B1|2018-01-31|Power grid outage and fault condition management

---

AU2011256481B2|2014-07-03|Malicious attack detection and analysis

---

CA2807007C|2018-07-17|Intelligent core engine

---

AU2012241193B2|2015-06-25|Method and system for managing a power grid

---

AU2015230786B2|2016-09-08|Method and system for managing a power grid

同族专利:

---

公开号 | 公开日

---

CA2790309C|2015-10-27|

---

CA2790309A1|2011-08-25|

---

NZ601777A|2014-09-26|

---

EP2537001A1|2012-12-26|

---

US20110208366A1|2011-08-25|

---

RU2554540C2|2015-06-27|

---

MY165769A|2018-04-23|

---

EP2537001B1|2013-12-11|

---

AU2011218256B2|2014-03-13|

---

JP5932668B2|2016-06-08|

---

WO2011103118A1|2011-08-25|

---

CN102812334A|2012-12-05|

---

JP2013520946A|2013-06-06|

---

SG183338A1|2012-09-27|

---

BR112012021714A2|2016-08-23|

---

CN102812334B|2015-09-23|

---

AU2011218256A1|2012-10-04|

---

RU2012140010A|2014-03-27|

---

ZA201206230B|2015-04-29|

---

HK1179686A1|2013-10-04|

---

US8918842B2|2014-12-23|

---

ES2450121T3|2014-03-24|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP2000112852A|1998-10-06|2000-04-21|Toshiba Corp|Mechanism for limiting the number of terminals to be simultaneously used in communication system|

---

RU2202122C2|2001-01-03|2003-04-10|Щеглов Андрей Юрьевич|System for checking access to processes being run|

---

JP4033692B2|2002-03-08|2008-01-16|富士通株式会社|Firewall security management method and management program thereof|

---

JP2004094455A|2002-08-30|2004-03-25|Denon Ltd|Computer system|

---

US8335860B2|2002-12-19|2012-12-18|Nokia Corporation|Filtering application services|

---

US7349997B2|2003-01-15|2008-03-25|Hewlett-Packard Development Company, L.P.|Dynamic command filter|

---

JP4030920B2|2003-05-28|2008-01-09|Ｎｅｃフィールディング株式会社|Power supply control system, power supply control device, power supply control method, and program during power failure|

---

US7950044B2|2004-09-28|2011-05-24|Rockwell Automation Technologies, Inc.|Centrally managed proxy-based security for legacy automation systems|

---

JP2006140580A|2004-11-10|2006-06-01|Ricoh Co Ltd|Power line transport communication system, power line transport communication method, and distribution board|

---

US8041967B2|2005-02-15|2011-10-18|Hewlett-Packard Development Company, L.P.|System and method for controlling power to resources based on historical utilization data|

---

JP2007122289A|2005-10-26|2007-05-17|Dainippon Printing Co Ltd|Ic card having a plurality of operating systems, and ic card program|

---

JP4514691B2|2005-11-14|2010-07-28|中国電力株式会社|Supervisory control system and method|

---

US7519855B2|2006-06-15|2009-04-14|Motorola, Inc.|Method and system for distributing data processing units in a communication network|

---

US8279870B2|2007-08-01|2012-10-02|Silver Spring Networks, Inc.|Method and system of routing in a utility smart-grid network|

---

WO2009128905A1|2008-04-17|2009-10-22|Siemens Energy, Inc.|Method and system for cyber security management of industrial control systems|

---

SG10201606766QA|2008-05-09|2016-10-28|Accenture Global Services Ltd|Method and system for managing a power grid|

---

US8504668B2|2010-02-01|2013-08-06|Gridglo Corp.|System and method for managing delivery of public services|

---

US8391142B2|2010-02-11|2013-03-05|Verizon Patent And Licensing, Inc.|Access window envelope controller in wireless network|

---

US8315743B2|2010-02-19|2012-11-20|The Boeing Company|Network centric power flow control|US20120284790A1|2006-09-11|2012-11-08|Decision-Zone Inc.|Live service anomaly detection system for providing cyber protection for the electric grid|

---

US8805552B2|2007-08-28|2014-08-12|Causam Energy, Inc.|Method and apparatus for actively managing consumption of electric power over an electric power grid|

---

US9177323B2|2007-08-28|2015-11-03|Causam Energy, Inc.|Systems and methods for determining and utilizing customer energy profiles for load control for individual structures, devices, and aggregation of same|

---

US9130402B2|2007-08-28|2015-09-08|Causam Energy, Inc.|System and method for generating and providing dispatchable operating reserve energy capacity through use of active load management|

---

US8890505B2|2007-08-28|2014-11-18|Causam Energy, Inc.|System and method for estimating and providing dispatchable operating reserve energy capacity through use of active load management|

---

US10295969B2|2007-08-28|2019-05-21|Causam Energy, Inc.|System and method for generating and providing dispatchable operating reserve energy capacity through use of active load management|

---

US8806239B2|2007-08-28|2014-08-12|Causam Energy, Inc.|System, method, and apparatus for actively managing consumption of electric power supplied by one or more electric power grid operators|

---

US8099197B2|2009-08-18|2012-01-17|Enphase Energy, Inc.|Method and system for distributed energy generator message aggregation|

---

US8578011B2|2010-06-15|2013-11-05|At&T Mobility Ii Llc|Systems, methods, and computer program products for providing a remote non-IP-addressable device with an IP stack|

---

EP2400617B1|2010-06-24|2021-04-14|ABB Power Grids Switzerland AG|Implementing a substation automation load transfer function|

---

KR101820738B1|2010-10-05|2018-01-23|삼성전자주식회사|Method and system for provisioning energy profile in home area network|

---

US9961550B2|2010-11-04|2018-05-01|Itron Networked Solutions, Inc.|Physically secured authorization for utility applications|

---

KR20120087274A|2010-12-23|2012-08-07|한국전자통신연구원|Emm client system, emm platform for building energy management and remote building management method|

---

US9768613B2|2011-05-31|2017-09-19|Cisco Technology, Inc.|Layered and distributed grid-specific network services|

---

US8965590B2|2011-06-08|2015-02-24|Alstom Grid Inc.|Intelligent electrical distribution grid control system data|

---

US9281689B2|2011-06-08|2016-03-08|General Electric Technology Gmbh|Load phase balancing at multiple tiers of a multi-tier hierarchical intelligent power distribution grid|

---

US9641026B2|2011-06-08|2017-05-02|Alstom Technology Ltd.|Enhanced communication infrastructure for hierarchical intelligent power distribution grid|

---

US20120316688A1|2011-06-08|2012-12-13|Alstom Grid|Coordinating energy management systems and intelligent electrical distribution grid control systems|

---

US9255949B2|2011-06-10|2016-02-09|Quadlogic Controls Corporation|Local transformer level grid management systems and methods|

---

US20140343983A1|2011-09-16|2014-11-20|Autogrid Inc.|System and a method for optimization and management of demand response and distributed energy resources|

---

US8660868B2|2011-09-22|2014-02-25|Sap Ag|Energy benchmarking analytics|

---

US8862279B2|2011-09-28|2014-10-14|Causam Energy, Inc.|Systems and methods for optimizing microgrid power generation and management with predictive modeling|

---

US8751036B2|2011-09-28|2014-06-10|Causam Energy, Inc.|Systems and methods for microgrid power generation management with selective disconnect|

---

US9225173B2|2011-09-28|2015-12-29|Causam Energy, Inc.|Systems and methods for microgrid power generation and management|

---

US9037306B2|2011-11-10|2015-05-19|International Business Machines Corporation|Monitoring and optimizing an electrical grid state|

---

CN102427522A|2011-12-27|2012-04-25|浙江省电力公司|Equipment and method for linking video monitoring system with intelligent regulation and control operating system|

---

US8761953B2|2012-04-30|2014-06-24|Innovari, Inc.|Grid optimization resource dispatch scheduling|

---

US9318920B2|2012-06-01|2016-04-19|Baltimore Gas And Electric Company|Method and system for the installation of fault circuit indicators on an electrical feeder|

---

US9461471B2|2012-06-20|2016-10-04|Causam Energy, Inc|System and methods for actively managing electric power over an electric power grid and providing revenue grade date usable for settlement|

---

US9465398B2|2012-06-20|2016-10-11|Causam Energy, Inc.|System and methods for actively managing electric power over an electric power grid|

---

US9207698B2|2012-06-20|2015-12-08|Causam Energy, Inc.|Method and apparatus for actively managing electric power over an electric power grid|

---

US9563215B2|2012-07-14|2017-02-07|Causam Energy, Inc.|Method and apparatus for actively managing electric power supply for an electric power grid|

---

US9513648B2|2012-07-31|2016-12-06|Causam Energy, Inc.|System, method, and apparatus for electric power grid and network management of grid elements|

---

US8983669B2|2012-07-31|2015-03-17|Causam Energy, Inc.|System, method, and data packets for messaging for electric power grid elements over a secure internet protocol network|

---

US10861112B2|2012-07-31|2020-12-08|Causam Energy, Inc.|Systems and methods for advanced energy settlements, network-based messaging, and applications supporting the same on a blockchain platform|

---

CN103679306A|2012-08-31|2014-03-26|国际商业机器公司|Method and system for saving building energy consumption|

---

US9634522B2|2012-09-19|2017-04-25|International Business Machines Corporation|Power grid data monitoring and control|

---

US8849715B2|2012-10-24|2014-09-30|Causam Energy, Inc.|System, method, and apparatus for settlement for participation in an electric power grid|

---

US9281686B2|2012-11-06|2016-03-08|General Electric Technology Gmbh|State estimation for cooperative electrical grids|

---

US9342806B2|2013-02-28|2016-05-17|P800X, Llc|Method and system for automated project management|

---

US10496942B2|2013-02-28|2019-12-03|P800X, Llc|Method and system for automated project management of excavation requests|

---

US9678520B2|2013-03-15|2017-06-13|Dominion Resources, Inc.|Electric power system control with planning of energy demand and energy efficiency using AMI-based data analysis|

---

US9294454B2|2013-03-15|2016-03-22|Microsoft Technology Licensing, Llc|Actively federated mobile authentication|

---

US9847639B2|2013-03-15|2017-12-19|Dominion Energy, Inc.|Electric power system control with measurement of energy demand and energy efficiency|

---

US9563218B2|2013-03-15|2017-02-07|Dominion Resources, Inc.|Electric power system control with measurement of energy demand and energy efficiency using t-distributions|

---

US9582020B2|2013-03-15|2017-02-28|Dominion Resources, Inc.|Maximizing of energy delivery system compatibility with voltage optimization using AMI-based data control and analysis|

---

US9553453B2|2013-03-15|2017-01-24|Dominion Resources, Inc.|Management of energy demand and energy efficiency savings from voltage optimization on electric power systems using AMI-based data analysis|

---

US9692231B2|2013-09-06|2017-06-27|Amazon Technologies, Inc.|Managing power feeds through waveform monitoring|

---

JP6527511B2|2013-11-12|2019-06-05|エスエムエイ ソーラー テクノロジー アクティエンゲゼルシャフトＳＭＡ Ｓｏｌａｒ Ｔｅｃｈｎｏｌｏｇｙ ＡＧ|Method for communication of a system control unit with a plurality of energy generation systems via a gateway, and a correspondingly configured and programmed data server|

---

US9454141B2|2014-06-06|2016-09-27|Innovari, Inc.|Real time capacity monitoring for measurement and verification of demand side management|

---

US10116560B2|2014-10-20|2018-10-30|Causam Energy, Inc.|Systems, methods, and apparatus for communicating messages of distributed private networks over multiple public communication networks|

---

JP5957772B2|2014-11-13|2016-07-27|パナソニックＩｐマネジメント株式会社|Device control apparatus and demand response method|

---

DE102015212026A1|2015-06-29|2016-12-29|Siemens Aktiengesellschaft|A method of operating a network with multiple node devices and a network|

---

US10732656B2|2015-08-24|2020-08-04|Dominion Energy, Inc.|Systems and methods for stabilizer control|

---

US10475138B2|2015-09-23|2019-11-12|Causam Energy, Inc.|Systems and methods for advanced energy network|

---

US20180121521A1|2016-10-28|2018-05-03|Salesforce.Com, Inc.|Time-based reporting of data using a database system|

---

CN109308008B|2017-07-28|2021-08-03|上海三菱电梯有限公司|Active disturbance rejection control device with abnormality coping capability|

---

CN110492907A|2018-05-15|2019-11-22|华为技术有限公司|The method and device of archives is established for ammeter|

法律状态:
2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according art. 34 industrial property law|

---

2019-08-20| B06U| Preliminary requirement: requests with searches performed by other patent offices: suspension of the patent application procedure|

---

2019-12-03| B09A| Decision: intention to grant|

---

2020-02-04| B16A| Patent or certificate of addition of invention granted|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 16/02/2011, OBSERVADAS AS CONDICOES LEGAIS. |

优先权:

---

申请号 | 申请日 | 专利标题

---

US12/709,081|US8918842B2|2010-02-19|2010-02-19|Utility grid command filter system|

---

PCT/US2011/024979|WO2011103118A1|2010-02-19|2011-02-16|Utility grid command filter system|

---