EP3785466B1 - Dynamically distributing processing among nodes in a wireless mesh network - Google Patents

Dynamically distributing processing among nodes in a wireless mesh network Download PDF

Info

Publication number
EP3785466B1
EP3785466B1 EP18829554.7A EP18829554A EP3785466B1 EP 3785466 B1 EP3785466 B1 EP 3785466B1 EP 18829554 A EP18829554 A EP 18829554A EP 3785466 B1 EP3785466 B1 EP 3785466B1
Authority
EP
European Patent Office
Prior art keywords
node
service
directory
data
service request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP18829554.7A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP3785466A1 (en
Inventor
Keith Torpy
Ruben Salazar
David Decker
Randy Turner
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Landis and Gyr Technology Inc
Original Assignee
Landis and Gyr Innovations Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Landis and Gyr Innovations Inc filed Critical Landis and Gyr Innovations Inc
Priority to EP23164473.3A priority Critical patent/EP4224822A3/en
Publication of EP3785466A1 publication Critical patent/EP3785466A1/en
Application granted granted Critical
Publication of EP3785466B1 publication Critical patent/EP3785466B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H02—GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02J—CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J13/00—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network
    • H02J13/00006—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network characterised by information or instructions transport means between the monitoring, controlling or managing units and monitored, controlled or operated power network element or electrical equipment
    • H02J13/00028—Circuit arrangements for providing remote indication of network conditions, e.g. an instantaneous record of the open or closed condition of each circuitbreaker in the network; Circuit arrangements for providing remote control of switching means in a power distribution network, e.g. switching in and out of current consumers by using a pulse code signal carried by the network characterised by information or instructions transport means between the monitoring, controlling or managing units and monitored, controlled or operated power network element or electrical equipment involving the use of Internet protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
    • Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
    • Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
    • Y04S40/18—Network protocols supporting networked applications, e.g. including control of end-device applications over a network

Definitions

  • GB 2 514 961 A refers to a data transmission apparatus and method.
  • a grid comprising smart meters with at least two IDs in which one of the IDs is used by the smart meter for sending consumption data that needs to be attributed to the owner or user of the smart meter, for example for billing purposes.
  • the device has means for storing one or more IDs that are attributed to a physical metering device and a plurality of IDs that are not attributable to any physical metering device.
  • the device has means to receive messages comprising data and a sender ID and means to compare the sender ID with the stored IDs.
  • the device provides the received data to a first communication channel if the sender ID corresponds with one of IDs attributed to the physical devices IDs, and alternatively it provides the received data to a second communication channel if the sender ID corresponds with one of IDs not attributed to the physical devices IDs.
  • Advantages may include obtaining results with less delay, using fewer head-end processing resources when scaling, using less network bandwidth, minimizing the overall cost, improving fault tolerance, and improving scalability.
  • a meter collects data regarding electric parameters.
  • the meter may determine that it requires the resources of a service node.
  • the meter may send a service request to a directory node requesting assistance in locating a suitable service node or the meter may send a service request seeking a suitable service node.
  • the service request may include an indication of the type of service needed, the collected data, and the meter's address. Once a service node is identified, the service node satisfies the service request and sends the results of the analysis back to the meter.
  • Service nodes support the distributed processing of computational tasks, including, but not limited to grid analytic services, such as monitoring transformers, determining feeder voltages, and configuring feeder switches, information services, computational services, storage services, and translation services.
  • An example of a resource distribution network is an electric distribution network or grid.
  • the grid may include devices and components, such as substations, transformers, and switches, and may provide electricity to a number of premises.
  • a meter may be associated with each premises that receives electricity. The meter may measure electric consumption at the premises, as well as other electric parameters, such as power, voltage, current, frequency, and phase.
  • the meters may communicate with each other and with a central system, such as a head-end system. Each meter may be associated with a node on a wireless mesh network. Other devices, such as routers and collectors, may also be associated with nodes on the wireless mesh network.
  • Some of the nodes may be configured to analyze the collected data.
  • the analysis may be performed by the node that collected the data or the analysis may be performed by another node on the network on behalf of the node that collected the data.
  • a meter locates another node capable of providing analytic services that is available to perform the analysis using a directory node.
  • the directory node provides directory services by maintaining information about the capabilities of service nodes.
  • Service nodes are nodes which are able to perform an operation on behalf of another node.
  • the directory node In response to receiving a service request from a node, the directory node identifies a service node and forwards the service request to the service node.
  • a node may send a request for assistance and wait for a service node to respond.
  • a service node may be topologically and geographically closer to a node that collects data than the head-end system.
  • a number of advantages can be achieved over using only the services performed by the head-end system.
  • One advantage is reducing the amount of time required to complete the analysis. There may be a delay between the time data is collected by a meter and the time that the head-end system receives the data which can delay analysis of the data. Analyzing the data using a local service node may eliminate the need to send the data to the head-end system for analysis so the analysis may be performed more quickly.
  • Another advantage to analyzing data using a local service node is that the amount of network traffic may be minimized.
  • Yet another advantage is minimizing the cost of the hardware or other components needed to perform the analysis. Since a meter may use a service node to perform the analysis, the meter is not required to have the same capabilities as the service node. As opposed to adding the ability to perform analytics on every meter deployed in the field, distributing service nodes in the network allows devices without the ability to perform certain operations to remain in the network.
  • a particular service node may be selected for a specific operation based on a selection policy. Selection policies include those that consider the capabilities or performance of the possible service nodes, the availabilities of the possible service nodes (e.g., least busy), the topological distances of the possible service nodes, or are random. By dynamically picking a service node to perform the analysis, the analysis may be performed quickly and efficiently based on the current conditions and pending requests.
  • FIG. 1 depicts an exemplary operating environment that includes a central system 100 and a wireless mesh network.
  • the devices in the wireless mesh network may communicate with the central system 100 via devices 110, 120.
  • Devices 110, 120 may be collectors and may communicate with the central system via additional devices and networks not shown in FIG. 1 .
  • the nodes in the wireless mesh network may include meters, routers, collectors, and other network devices.
  • a collector 110, 120 may be a directory node.
  • a directory node maintains information about nodes that can assist other nodes with processing, i.e., maintains information about one or more service nodes. Other nodes may also be directory nodes.
  • FIG. 1 illustrates that node 190 is a directory node.
  • the nodes 130-180 are associated with meters located at different premises, nodes 110, 120 are collectors, node 190 is a directory node, and central system 100 is a head-end system.
  • FIG. 2 depicts an example where a node requires assistance in processing its collected data and utilizes a service node.
  • Node 220 may be associated with a meter located at a premises that includes a local generation device 250, such as a set of solar panels.
  • the meter 220 collects data regarding electricity usage and production. An application or other program running on the meter requires analysis of the collected data.
  • the meter 220 determines that it requires the services of another node to perform the analysis and sends a service request 256 along with the collected data to service node 240.
  • Service node 240 satisfies the service request by performing the analysis and sends the results 258 of the analysis back to the meter.
  • the meter 220 previously identified service node 240 as capable of providing the analysis.
  • meter 220 may store information about one or more service nodes including the services provided by each service node.
  • FIG. 2 may also be used to depict an example where a node 220, discovers a service node that can provide assistance with a computational task, such as processing data. Once node 220 determines that it requires the services of another node to perform the analysis, if it does not have information about a node that is able to provide the service, then it may use a service request to identify a service node.
  • a computational task such as processing data.
  • Node 230 may be a directory node and may maintain information about service nodes and the services that they provide.
  • Node 220 may send a service request 252 to the directory node that identifies the service it needs and includes any data needed to perform the service.
  • directory node 230 identifies service node 240 as available to provide the service and forwards the service request 253 to the service node.
  • Service node 240 satisfies the service request and returns the result 258 to node 220.
  • Node 220 may initiate the analysis based on an application or other program running on the node. For example, node 220 may be configured to perform the analysis periodically or based on a sensed condition. Alternatively, node 220 may initiate the analysis in response to receiving a communication from another node. Node 210 may send a request 250 to node 220 requesting node 220 perform the analysis or requesting information from node 220 that requires the analysis. If so, then node 220 initiates the analysis and uses service node 240 to complete the analysis. Node 220 may discover service node 240 using any of the foregoing discovery methods. After node 220 receives the results 258 from service node 240, node 220 responds 260 to node 210.
  • the requested service may be performed by multiple service nodes in parallel.
  • Node 220 may send parallel service requests to two service nodes.
  • node 220 may send a service request to directory node 230 and directory node may perform part of the analysis and send a service request to service node 240 to perform other parts of the analysis.
  • FIG. 4 depicts a block diagram illustrating an example of using distributed processing to perform analytic services.
  • measurement data collected by a meter at a premises is used to assess the operational status of a transformer.
  • a substation 410 provides power to transformer 420 and transformer 430.
  • the transformers provide power to meters 450a-f, 460, 470.
  • Meters 450a-f, 460, 470 are each associated with a premises.
  • Meters 450a-c, 460, 470 are associated with transformer 420 and meters 450d-f are associated with transformer 430.
  • the meters may be configured to measure electric parameters including, but not limited to, electricity usage or consumption, load, voltage, power, phase and harmonic data, at configurable time intervals.
  • Meters 450a-f, directory node 460, service node 470, routers 445 and 447, and collector 445 are connected via a wireless mesh network.
  • Collector 455 is also connected to the head end system 480.
  • the meter may send a service request to directory node 460 to request the assistance of a service node.
  • the directory node 460 identifies service node 470 as being capable of performing the analysis .
  • the directory node 460 forwards the service request to the service node 470.
  • the service node 470 analyzes the data and provides the results of the analytic services to meter 450c.
  • the results may indicate the operational status of transformer 420 or may provide a result that can be used to determine the status of the transformer.
  • the meter 450c may initiate an action based on the results of the analysis. The action may be to report the results back to another system, such the head-end system 480.
  • a large number of transformers may be pro-actively monitored, and the monitoring may be applied down to the distribution transformer level.
  • the results may be aggregated and may be sent to the head-end system or otherwise used to maintain the electric distribution network.
  • Transformer monitoring may include thermal change monitoring or frequency response analysis.
  • the useful life of a transformer is determined partially by the ability of transformer to dissipate internally generated heat to its surroundings. The comparison of actual and predicted operating temperatures may be used to identify abnormal operation. The consequences of temperature rise may not be sudden, but gradual as long as it is within break down limit. Among these consequences, insulation deterioration is economically important since insulation is very costly.
  • Thermal modelling may use a mathematical model that predicts the temperature profile of the transformer using the principle of thermal analysis. The thermal model is used to determine the top oil temperature and hot spot temperature (maximum temperature occurring in the winding insulation system) temperature rise.
  • a service node may be configured to provide thermal modelling.
  • a meter may collect data for a number of time intervals over a period of time. For example, a meter may collect data for a number of 15 minute time intervals over a 24 hour period of time. The meter may communicate the collected data to a head-end system once every 24 hour period so that the head-end system may determine consumption at the premises associated with the meter. If the head-end system is used to analyze the data, then there is a delay in performing the analysis since the data may be sent to the head-end system only once every 24 hours. This delay may be significantly reduced by distributing service nodes throughout the system. A meter may send its collected data to a service node that is local to the meter for analysis using a different schedule than it uses to send data to the head-end system.
  • FIG. 5 depicts a portion of an exemplary electric distribution network that includes feeder switches.
  • the feeder switches may be configured so that substation 510 powers transformers 512, 514, 516 and substation 520 powers transformers 522, 524, 526.
  • Feeder switches 530-536 are placed on the power lines at various locations and may be used to control the flow of power on the grid.
  • Meters 540a-n, 570a-b are connected to the transformers and provide metrology services to an associated premises.
  • the meters 540an, 570a-b, as well as other additional nodes may collect information about the operation of the electric distribution network and may communicate with each other via one or more wireless mesh networks.
  • the additional nodes may be associated with other devices on the electric distribution network, such as substation 550a or feeder switches 560a, 560b.
  • the nodes collect measurement data or other information about the operation of the electric distribution network in order to analyze the current configuration of the feeder switches.
  • the collected measurement data may be analyzed to determine when and how to control the feeder switches to minimize the impact of an event, such as an outage or changes in demand.
  • the results may be sent to node 550a.
  • Node 550a may use the results to determine what action to take. In some instances, node 550a may determine whether to turn one or both of the feeder switches 530, 532 ON or OFF. Node 550a may not have the authority to control other devices, such as feeder switches 550, 532. If it does not have sufficient authority, then the node may transmit the results of the analysis, which may include recommendations for actions to be taken, to a system that has the authority to control the feeder switch, such as a node associated with the feeder switch or a head-end system.
  • FIG. 6 depicts an exemplary node 600.
  • the node includes a core platform module 610 and applications 640 and 645.
  • the core platform module 610 provides a basic computing framework for applications 640 and 645.
  • the core platform module 610 may be coded in Java.
  • the node may also include an extension services module 620.
  • the extension services module extends the services provided by the core platform and thus extends the capabilities of node 600.
  • the extension services module may allow the node to discover and communicate with directory nodes and service nodes, and it may enable the node to support additional advanced functions, features, and applications, such as distributed computation, aggregation of raw data over groups of nodes, transactional energy, digital wallet/block chain, integration of cognitive computing/AI capabilities, predictive analytics, pattern recognition, etc.
  • the core platform module 610 may provide the applications with a consistent interface to the services provided by the services modules via an application programming interface (API).
  • API application programming interface
  • the services modules and the core platform module are collectively referred to as system modules 605.
  • Different nodes may have different services modules or may have services modules that support different functions.
  • the extension services module in a directory node may support directory functions, whereas the extension services module for a different type of node may support only discovery of a directory node.
  • Services modules other than extension service module 620 may also be included.
  • Services modules may include grid analytics services module 630 that supports transformer health monitoring, phase harmonics monitoring, duck curve flattening, and feeder switch management. Additional analytic services may also be provided including information services, computational services, storage services, and translation services.
  • Information services may include services related to weather, energy pricing, time of use (TOU) scheduling, and notifications.
  • Computational services may include analytics, as well as computations related to transactional energy, energy trading, and energy forecasting.
  • Storage services may include storing data or other information on behalf of another node or device.
  • Translation services include translating between different protocols.
  • the services provided by a services module may also be accessed through requests that originate from other nodes on the wireless mesh network.
  • Communication services may include communications with external entities, such as email, text, or messaging. Services modules may be added or updated.
  • the extension services module 620 may be configured to request services from other nodes or provide services to other nodes.
  • An application 640 on the node may initiate an analysis of collected data.
  • the application accesses the core platform module 610 using an API. If the system modules of the node do not support the analysis, the core platform module may pass the request to the extension services module 620, which may send a request to a directory node or to a service node.
  • the node collecting the data or requesting services from a service node is not limited to a meter.
  • methods, apparatuses, or systems that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Medical Informatics (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Power Engineering (AREA)
  • Remote Monitoring And Control Of Power-Distribution Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)
EP18829554.7A 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network Active EP3785466B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP23164473.3A EP4224822A3 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US15/965,202 US10237338B1 (en) 2018-04-27 2018-04-27 Dynamically distributing processing among nodes in a wireless mesh network
PCT/US2018/063067 WO2019209376A1 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network

Related Child Applications (2)

Application Number Title Priority Date Filing Date
EP23164473.3A Division EP4224822A3 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network
EP23164473.3A Division-Into EP4224822A3 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network

Publications (2)

Publication Number Publication Date
EP3785466A1 EP3785466A1 (en) 2021-03-03
EP3785466B1 true EP3785466B1 (en) 2023-05-31

Family

ID=64902395

Family Applications (2)

Application Number Title Priority Date Filing Date
EP18829554.7A Active EP3785466B1 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network
EP23164473.3A Pending EP4224822A3 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP23164473.3A Pending EP4224822A3 (en) 2018-04-27 2018-11-29 Dynamically distributing processing among nodes in a wireless mesh network

Country Status (7)

Country Link
US (2) US10237338B1 (zh)
EP (2) EP3785466B1 (zh)
JP (1) JP7132353B2 (zh)
CN (2) CN114727358B (zh)
AU (2) AU2018421443B2 (zh)
CA (1) CA3097689A1 (zh)
WO (1) WO2019209376A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11183878B2 (en) 2017-08-07 2021-11-23 Landis+Gyr Innovations, Inc. Maintaining connectivity information for meters and transformers located in a power distribution network
US10237338B1 (en) 2018-04-27 2019-03-19 Landis+Gyr Innovations, Inc. Dynamically distributing processing among nodes in a wireless mesh network
US11646602B2 (en) 2020-03-11 2023-05-09 Landis+Gyr Innovations, Inc. Topology and phase detection for electrical supply network
US11757986B2 (en) 2020-10-23 2023-09-12 Dell Products L.P. Implementing an intelligent network of distributed compute nodes

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8121741B2 (en) * 2008-05-09 2012-02-21 International Business Machines Corporation Intelligent monitoring of an electrical utility grid
US8270313B2 (en) * 2009-11-13 2012-09-18 Mitsubishi Electric Research Laboratories, Inc. Ranking nodes in networks with topologies arranged as directed acyclic graphs
GB2514961B (en) * 2010-04-29 2015-01-21 Toshiba Res Europ Ltd Data transmission apparatus and method
US8385286B2 (en) * 2010-09-03 2013-02-26 Nokia Corporation Resource sharing between secondary networks
US9118219B2 (en) * 2011-07-07 2015-08-25 Landis+Gyr Innovations, Inc. Methods and systems for determining an association between nodes and phases via a smart grid
US9094385B2 (en) * 2011-08-05 2015-07-28 Battelle Memorial Institute Intelligent sensor and controller framework for the power grid
CN102427277B (zh) * 2011-10-26 2015-01-28 广州德昊电力科技有限公司 区域智能配电网系统
US9130403B2 (en) * 2011-11-01 2015-09-08 Current Technologies International Gmbh System, method and computer program product for determining load profiles
CN103281805B (zh) * 2013-05-28 2016-05-11 武汉大学 一种无线传感器节点和rfid数据融合的方法
US9791485B2 (en) * 2014-03-10 2017-10-17 Silver Spring Networks, Inc. Determining electric grid topology via a zero crossing technique
US9772921B2 (en) * 2014-03-17 2017-09-26 Silver Spring Networks, Inc. Techniques for collecting and analyzing notifications received from neighboring nodes across multiple channels
US9866012B2 (en) * 2014-05-02 2018-01-09 Maple Microsystems Inc. Method and system for reporting faults and control in an electrical power grid
CN104134161A (zh) * 2014-07-01 2014-11-05 贵州电网公司信息通信分公司 一种配电网馈线段等效化简的方法
CN104134999B (zh) * 2014-08-06 2016-06-08 国家电网公司 基于多数据源的配电网量测有效性分析实用化计算方法
CN109477863A (zh) * 2016-06-13 2019-03-15 电网监控有限公司 用于电力网中的动态故障检测的方法和系统
US10652633B2 (en) * 2016-08-15 2020-05-12 Delta Energy & Communications, Inc. Integrated solutions of Internet of Things and smart grid network pertaining to communication, data and asset serialization, and data modeling algorithms
US10237338B1 (en) 2018-04-27 2019-03-19 Landis+Gyr Innovations, Inc. Dynamically distributing processing among nodes in a wireless mesh network

Also Published As

Publication number Publication date
EP4224822A3 (en) 2023-09-06
JP2021522722A (ja) 2021-08-30
WO2019209376A1 (en) 2019-10-31
AU2022200840B2 (en) 2023-03-02
CN114727358A (zh) 2022-07-08
AU2018421443A1 (en) 2020-11-19
US20190334977A1 (en) 2019-10-31
JP7132353B2 (ja) 2022-09-06
EP3785466A1 (en) 2021-03-03
CA3097689A1 (en) 2019-10-31
CN112313997A (zh) 2021-02-02
AU2018421443B2 (en) 2022-03-03
US10237338B1 (en) 2019-03-19
CN114727358B (zh) 2023-11-21
CN112313997B (zh) 2022-05-27
US10511657B2 (en) 2019-12-17
AU2022200840A1 (en) 2022-03-03
EP4224822A2 (en) 2023-08-09

Similar Documents

Publication Publication Date Title
EP3785466B1 (en) Dynamically distributing processing among nodes in a wireless mesh network
Fateh et al. Wireless network design for transmission line monitoring in smart grid
US10305736B2 (en) Methods, network nodes, and computer program products for price signal feedback for network optimization
Zahedi et al. Energy efficient reservation-based cluster head selection in WSNs
Judge et al. Secure transmission lines monitoring and efficient electricity management in ultra-reliable low latency industrial internet of things
US11652703B2 (en) Dynamic processing distribution for utility communication networks
JP2021522722A5 (zh)
KR101924628B1 (ko) 트래픽 오프로딩을 제어하기 위한 장치 및 방법
Matta et al. A wireless sensor network for substation monitoring and control in the smart grid
US8649269B2 (en) Method of controlling resource usage in communication systems
Matta et al. Putting sensor data to the service of the smart grid: from the substation to the AMI
CN112291802A (zh) 一种通信节点的协作方法和系统
JP2012147155A (ja) Ｐ２ｐ通信に関する情報提供方法、ｐ２ｐ通信に関する情報提供システム、移動端末、及びプログラム
CN116601460A (zh) 智能电网中的自适应计量
CN105659218A (zh) 通信系统、通用服务控制设备、数据发送方法和非瞬态计算机可读介质
WO2018104915A1 (en) Methods, circuits, devices, systems and associated computer executable code for operating a wireless communication network
CN110635927B (zh) 节点切换方法、网络节点、网络系统
Guo et al. Optimal Placement of Cloudlets Considering Electric Power Communication Network and Renewable Energy Resource
Premkumar et al. Optimal DAU Placement for Smart Distribution Grid Communication Network
Shahryari et al. Demand side management using the internet of energy based on LoRaWAN technology
Panahi et al. Smart Grids and Green Wireless Communications
Villers et al. Grid metrics for monitoring Green network
Khan et al. A QoS-aware Data Aggregation Strategy for Resource constrained IoT-enabled AMI Network in Smart Grid
Matta et al. Pribacc: In-network sensor data processing for efficient smart grid monitoring applications
Yu et al. Research on Heterogeneous Communication Network for Power Distribution Automation

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20201125

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602018050533

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0040240000

Ipc: H04L0067120000

Ref country code: DE

Ref legal event code: R079

Ipc: H04L0067120000

RIC1 Information provided on ipc code assigned before grant

Ipc: H04Q 9/00 20060101ALI20221021BHEP

Ipc: H04W 40/24 20090101ALI20221021BHEP

Ipc: H04L 67/10 20220101ALI20221021BHEP

Ipc: H04L 67/12 20220101AFI20221021BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20221208

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602018050533

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1571676

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230615

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230517

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: LANDIS+GYR TECHNOLOGY, INC.

REG Reference to a national code

Ref country code: NL

Ref legal event code: FP

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1571676

Country of ref document: AT

Kind code of ref document: T

Effective date: 20230531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230831

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230930

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230901

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20231120

Year of fee payment: 6

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20231207 AND 20231213

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231123

Year of fee payment: 6

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 602018050533

Country of ref document: DE

Owner name: LANDIS+GYR TECHNOLOGY, INC. (N.D. GES. D. STAA, US

Free format text: FORMER OWNER: LANDIS+GYR INNOVATIONS, INC., ALPHARETTA, GA, US

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20231002

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: TR

Payment date: 20231127

Year of fee payment: 6

Ref country code: FR

Payment date: 20231120

Year of fee payment: 6

Ref country code: DE

Payment date: 20231121

Year of fee payment: 6

Ref country code: CH

Payment date: 20231202

Year of fee payment: 6

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602018050533

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

26N No opposition filed

Effective date: 20240301

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20230531