Communication Device Reboot Resumption via Count Value
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional communication systems face challenges in quickly restarting data transmission/reception after a communication device is rebooted, as they require time-consuming key sharing and frequent updates to nonvolatile memory, leading to potential memory deterioration and increased failure risks.
Innovation Solution
A communication device employing a volatile memory for storing a count value, which generates and transmits a data frame with an incremented count value, and a nonvolatile memory for storing this value at intervals, allowing the device to resume operations quickly by adding a predetermined value when rebooted, reducing the need for key sharing and minimizing memory writes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the count value is initialized in volatile memory upon reboot, then security authentication can be maintained, but data transmission/reception cannot be restarted quickly and key sharing must be performed again
Solution Approach 1:
The count value is preliminarily stored in nonvolatile memory before reboot occurs. When reboot happens, the system quickly retrieves the pre-stored count value from nonvolatile memory instead of initializing it, enabling fast resumption of data transmission while maintaining security authentication continuity
Solution Approach 2:
Nonvolatile memory acts as an intermediary between volatile memory and the reboot event. It preserves the count value across power cycles and provides it back to the system after reboot, bridging the gap between security requirements and fast restart needs
2Reliability
If the count value is frequently written to nonvolatile memory, then data persistence is improved, but memory deterioration increases and failure risk rises
Solution Approach 1:
Instead of writing the count value to nonvolatile memory after every transmission, the system uses periodic writing at predetermined intervals. This reduces the frequency of write operations to nonvolatile memory, extending its lifespan while still ensuring data persistence through periodic updates
Solution Approach 2:
The system writes the count value to nonvolatile memory less frequently than the maximum needed for complete data persistence (partial action). By accepting that not every single count value change is immediately persisted, the system reduces wear on nonvolatile memory while maintaining adequate data recovery capability
Data Source
AI summary
A communication device according to the present invention aims to restart data transmission/reception between communication devices in a short amount of time, without performing key sharing again, even when a communication device of a transmitting side is rebooted. The communication device includes a volatile memory storing a count value, a generator generating data including a count value, a communicator transmitting data to another communication device, a storage instructor, each time the communicator transmits data, updating the volatile memory with a count value, and a nonvolatile memory. A count value is incremented each time the communicator transmits data, the storage instructor causes the nonvolatile memory to store a count value at certain intervals, and the generator, when the communication device is rebooted, includes in data a sum of a certain value and a count value stored in the nonvolatile memory.