Non-real-time OS Timestamped Queue for Boot Data Loss
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional real-time operating systems fail to reliably process time-sensitive information due to processing latency and overload, and are unable to receive and process data during boot or reboot sequences, leading to potential loss of critical information.
Innovation Solution
Implementing a non-real-time operating system that timestamps time-sensitive input and stores it in a temporary queue for processing at a later time, allowing for efficient catch-up processing and prioritizing the activation of the metrology driver during boot or reboot sequences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a real-time operating system processes time-sensitive input instantaneously, then processing speed is improved, but processing reliability deteriorates when the system experiences latency or overload
Solution Approach 1:
The system performs preliminary actions by receiving and storing time-sensitive input data in a queue before the operating system is fully operational. The boot sequence is modified to initialize the data reception component and queue structure in advance, allowing data to be buffered and processed reliably once the system is ready, thus preventing data loss during boot or overload conditions.
2Loss of time
If the operating system prioritizes immediate task execution, then time sensitivity is improved, but data loss increases during boot or reboot sequences
Solution Approach 1:
A queue data structure serves as an intermediary between the data reception component and the operating system's processing components. This intermediary buffer allows time-sensitive data to be received and held during boot sequences or system overload, then transferred to processing components when they become available, preventing data loss while maintaining time-sensitive processing capabilities.
3Ease of operation
If the system uses a conventional boot sequence, then system initialization is simplified, but data reception capability is lost during initialization
Solution Approach 1:
The boot sequence is segmented into distinct phases: a first phase that initializes only the data reception component and queue structure, and a second phase that initializes the operating system's processing components. This segmentation allows data reception to begin early in the boot process while the rest of the system initializes, maintaining data reception capability without complicating the overall boot process.
Data Source
AI summary
The techniques described herein implement an operating system that can reliably process time sensitive information in non real-time manner. Thus, the operating system described herein is capable of processing an instance of time sensitive input during a time period after the instance of time sensitive input is received (e.g., at a future point in time). To accomplish this, the techniques timestamp each instance of time sensitive input when it is received at a device. The techniques then store the timestamped instance of time sensitive input in a temporary queue, and make the timestamped instance available to the operating system at a time period after the time period when it is received, as indicated by the timestamp. Additional techniques described herein prioritize the activation of a driver configured to receive the time sensitive information during a boot sequence or a reboot sequence.