Resume Command for Stalled Smart Meter Data Transfers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The Companion Specification for Energy Metering (COSEM) and Device Language Message Specification (DLMS) lack a seamless method for resuming data-file transfers if the process stalls or fails, leading to inefficiencies in network bandwidth consumption, battery life, and increased transfer time, especially in high-latency networks.
Innovation Solution
Implementing a resume command that allows smart utility meters to manage data transfers by resuming, canceling, or prioritizing processes based on existing transfers, using a 'cancel-if-necessary' notation and threshold periods to optimize data transfer operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the entire data-file transfer process is re-started when a transfer stalls or fails, then the data transfer can be completed, but network bandwidth consumption increases and battery life is reduced
Solution Approach 1:
The patent segments the data transfer process into distinct blocks that can be independently tracked and resumed. Each data file is divided into transferable units with unique identifiers, allowing the system to resume from the point of failure rather than restarting the entire transfer, thus conserving battery life while ensuring completion.
Solution Approach 2:
The patent implements preliminary actions by establishing transfer block identifiers and tracking mechanisms before the actual data transfer begins. This preliminary setup enables the system to quickly determine what has been transferred and what needs to be resumed, avoiding unnecessary re-transmission and energy consumption.
2Reliability
If the entire data-file transfer process is re-started when a transfer stalls or fails, then the data transfer can be completed, but network bandwidth consumption increases
Solution Approach 1:
The patent segments the data transfer process into distinct blocks that can be independently tracked and resumed. Each data file is divided into transferable units with unique identifiers, allowing the system to resume from the point of failure rather than restarting the entire transfer, thus conserving network bandwidth while ensuring completion.
Solution Approach 2:
The patent implements a feedback mechanism where the system continuously monitors transfer status, block completion, and error conditions. This feedback enables intelligent decision-making about whether to resume or restart transfers, optimizing network bandwidth usage by avoiding redundant transmissions of already-successfully-transferred blocks.
3Productivity
If multiple data transfers are managed without a resume command, then simple processing is maintained, but transfer time increases and success rate decreases
Solution Approach 1:
The patent creates a universal resume command structure that can handle multiple data transfer scenarios (single file, multiple files, concurrent transfers) through a unified interface. The BLOCK_TRANSFER_RESUME command works across different transfer contexts, managing complexity internally while presenting a simple interface, thus improving productivity without proportionally increasing device complexity.
Solution Approach 2:
The patent introduces an intermediary command layer (BLOCK_TRANSFER_RESUME) that mediates between the simple user request and the complex transfer management operations. This intermediary handles the complexity of tracking multiple transfers, determining resume points, and coordinating re-transmissions, thereby improving transfer efficiency while shielding users from complexity.
4Ease of operation
If data transfers are managed in high-latency networks without resume functionality, then communication simplicity is maintained, but control difficulty increases
Solution Approach 1:
The patent implements preliminary action by pre-establishing block identifiers and transfer state tracking mechanisms before data transmission begins. In high-latency networks, this preliminary setup allows the system to quickly assess transfer status and resume operations without lengthy status verification, reducing overall transfer time while maintaining operational control.
Solution Approach 2:
The patent ensures continuity of useful action by enabling seamless resumption of data transfers interrupted by latency or failures. The system maintains continuous progress tracking and can immediately resume transfers from the last successful block, eliminating idle waiting time and maintaining productive action throughout the transfer process despite network latency.
Data Source
AI summary
Techniques for data transfer are described herein. In an example, a command to transfer a first data file is received at a computing device. The computing device determines if at least two processes exist, or do not exist, from among processes including: a first transfer process of the first data file; a second transfer process of a second data file; and a third process, not related to the first data-transfer or the second data-transfer. An action is selected from among a plurality of actions, wherein the selecting is based at least in part on which processes were found to exist. The plurality of actions may include: resuming the first transfer process; canceling the second transfer process and starting a new process to transfer the first data file; rejecting the command; allowing the third process to conclude and then starting the new process to transfer the first data file; and starting the new process to transfer the first data file.