Relative Time Clock for Automated Meter Reading Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Automated meter reader systems face challenges in synchronization due to time zone differences, daylight savings, and time drift, leading to overburdening of reader devices when collecting meter readings from a large number of endpoint devices.
Innovation Solution
Implementing a relative time clock in endpoint devices that records meter readings in fixed intervals, allowing for conversion of requested times into intervals, enabling collection systems to retrieve data without real-time synchronization, simplifying logic and reducing communication burden.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If real-time synchronization is implemented among endpoint devices and reader devices, then measurement precision of meter reading data is improved, but device complexity and communication burden increase significantly
Solution Approach 1:
The patent replaces expensive, complex real-time synchronization mechanisms with inexpensive relative time clocks that track only elapsed intervals. Each endpoint device maintains a simple counter of time intervals since installation or last reset, avoiding the need for complex synchronization protocols while maintaining sufficient accuracy for meter reading purposes.
Solution Approach 2:
The patent changes the time measurement parameter from absolute time (requiring synchronization to time zones, daylight savings, leap years) to relative time (simple interval counting). This parameter transformation eliminates the need for handling complex time synchronization issues while preserving the ability to accurately record and retrieve meter reading data for any time period.
2Measurement precision
If reader devices collect meter readings from a large number of endpoint devices with time drift correction, then measurement precision is maintained, but productivity of the collection system decreases due to overburdening reader devices
Solution Approach 1:
The patent extracts the time tracking function from the reader device and places it in each endpoint device's relative time clock. This eliminates the need for the reader device to perform complex time drift calculations and multiple message exchanges, significantly reducing its computational burden and allowing it to efficiently collect data from large numbers of endpoint devices.
Solution Approach 2:
Each endpoint device independently maintains its own relative time clock and autonomously records meter reading data with interval counters. This self-service approach eliminates the need for the reader device to manage synchronization or perform time drift corrections, improving overall system productivity while maintaining data accuracy.
3Reliability
If absolute time clocks with real-time synchronization are used in endpoint devices, then reliability of time-stamped data is improved, but ease of operation and system simplicity deteriorate
Solution Approach 1:
The patent segments the time tracking function into simple interval counters within each endpoint device, independent of external time synchronization systems. Each device independently tracks elapsed intervals since a reference point, eliminating the need to handle complex time zone transitions, daylight savings changes, and leap year adjustments while maintaining reliable time-stamped data.
Data Source
AI summary
A system, method and device are provided for obtaining, from each endpoint device, meter reading data where the meter reading data are recorded and managed based on a relative time clock in each endpoint device. The relative time clock may be a simple inexpensive clock that tracks minutes and triggers recording of meter reading data for a particular hour at the end of that hour. In that embodiment, a collection system sends an endpoint device a request that includes a requested time that is converted into a relative time so that the endpoint device can understand the request. Since each recorded interval is generated based on a relative time maintained by the clock in the endpoint device rather than an absolute (real) time, the endpoint device does not need to maintain accurate date/time or to read meter reading data from the utility meter based on a real date/time.