Concentrator Protocol Translation for Smart Meter Data Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current resource monitoring and control systems face limitations such as limited meter data, slow data collection, protocol restrictions, manual resource control, and limited consumer interaction, particularly in systems like the National Electricity Market.

Innovation Solution

A communications system with a concentrator that manages and processes data from remote units, including meters, to facilitate efficient data exchange, configuration changes, and user interaction, using properties data to determine communication links and protocols, enabling advanced data management and control capabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a meter is configured to transmit meter data to a management server using traditional protocols, then the system can maintain compatibility with legacy infrastructure, but the data collection speed is slow and resource intensive

Engineering Contradiction:
Improvedata collection speedVSAvoidresource efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent introduces a concentrator as an intermediary device between meters and the management server. The concentrator collects data from multiple meters locally and performs preliminary processing, filtering, and aggregation before transmitting to the server. This mediator architecture reduces the burden on both meters and servers, enabling faster data collection without overwhelming system resources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into three distinct functional layers: meter devices for data collection, concentrators for local data management and processing, and management servers for centralized control. This segmentation allows each component to operate independently at optimized speeds, with the concentrator handling time-sensitive data aggregation locally while the server manages less time-critical operations.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If each meter is limited to a particular communications protocol, then the system maintains simplicity in protocol implementation, but replacing legacy meters with new communication systems requires complete meter replacement

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidsystem replacement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The concentrator serves as a protocol translation intermediary between meters using different communication protocols and the management server. It can receive data from meters using various protocols (DLMS, Modbus, proprietary protocols) and translate/normalize it for server communication, enabling legacy meters to work with modern systems without replacement.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The concentrator is designed with multi-functional capability to support multiple communication protocols simultaneously. It can interface with different meter types using their native protocols while presenting a unified interface to the management server, making the overall system universally compatible without requiring meter replacement.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If a meter is configured as a pure measurement device, then the device complexity is minimized, but any resource control actions such as shutting off supply require manual intervention

Engineering Contradiction:
Improveautomated resource controlVSAvoidmeter functionality complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system separates measurement functions (performed by simple meters) from control functions (performed by the management server through the concentrator). The meter remains a simple measurement device while the concentrator and server handle automated control actions by sending commands back through the same communication channel, eliminating the need for manual intervention.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements a feedback loop where the management server receives measurement data from meters through concentrators, processes the data according to control logic, and sends automated control commands back to the meters or associated control devices. This closed-loop feedback enables automated resource control without increasing meter complexity.

Inventive Principle:
Principle #23Feedback

4Loss of information

If the degree of interaction between a meter and consumer at their premises is very limited, then the system maintains simplicity in meter-consumer interaction, but consumers cannot access detailed usage information or control options

Engineering Contradiction:
Improveconsumer access to usage dataVSAvoidcommunication system complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system moves consumer interaction from the meter device dimension to the information network dimension. Instead of embedding complex interaction capabilities in the meter, the concentrator collects detailed usage data and makes it available through web-based portals, mobile applications, and email notifications, allowing consumers to access comprehensive information and control options through standard computing devices.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10063942B2Communications process, device and system
Publication Date: 2018.08.28 FREESTYLE TECH PTY LTD
  • US10063942B2 patent drawing
  • US10063942B2 patent drawing
  • US10063942B2 patent drawing

AI summary

A method executed by a concentrator connected between a plurality of remote units and a management server, the method including:(i) receiving and storing properties data associated with a remote unit including a microengine and a meter for measuring usage of a resource at a customer's premises, the properties data representing a profile of the remote unit;(ii) receiving message data representing a request associated with the remote unit from the management server;(iii) generating response data representing a response to the request based on the message data and the stored properties data; and(iv) sending the response data to one of the remote unit and the management server, as determined by the request based on the message data.