Boot Manager for Software Defined Radios
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software defined radios (SDRs) take an excessively long time to boot, typically taking 2 to 15 minutes, which is detrimental in time-critical situations requiring immediate communications, such as military emergencies, due to the formal separation between the operating environment and software applications and the use of a common object request broker.
Innovation Solution
A method involving the execution of first and second stage program codes by a boot manager to launch a low-level radio function application, load device drivers, middleware, and core framework, allowing for concurrent allocation and deallocation of device drivers, and enabling emergency communications applications to run quickly, thereby reducing boot time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the operating environment and software applications are booted in a specified sequence with formal separation, then the system architecture maintains reliability and modularity, but the boot time becomes excessively long (2 to 15 minutes)
Solution Approach 1:
The patent applies preliminary action by pre-configuring the SDR system with multiple boot images stored in non-volatile memory before operation is needed. When the system is activated, it can immediately load and execute a boot image without requiring sequential initialization of the entire operating environment and all software applications. This pre-prepared state enables the system to bypass the traditional lengthy boot sequence while maintaining architectural integrity.
Solution Approach 2:
The patent segments the boot process into distinct boot images, each containing specific subsets of the operating environment and software applications. Instead of loading everything in sequence, the system divides the complete software stack into modular boot images that can be selectively executed. This segmentation allows the system to maintain full functionality while reducing boot time by loading only what is immediately needed.
2Reliability
If all operating environment components and software applications are loaded sequentially, then the system ensures complete initialization and reliability, but the boot process takes 2 to 15 minutes which is unacceptable for emergency communications
Solution Approach 1:
The patent implements dynamics by making the boot process adaptive and configurable rather than fixed and static. The system can dynamically select which boot image to execute based on operational requirements - choosing a full boot image for non-critical operations or a reduced boot image for emergency situations. This dynamic approach allows the system to balance complete initialization with rapid response capability, adjusting the boot behavior to match the urgency of the situation.
Solution Approach 2:
The patent changes the parameter of boot configuration by providing multiple boot images with different levels of completeness. Each boot image represents a different parameter setting for system initialization - from minimal emergency-only configurations to full operational environments. By changing this parameter, the system can transition between rapid deployment mode and complete initialization mode, resolving the contradiction between speed and thoroughness.
3Stability of the object's composition
If the system loads the complete operating environment including middleware and core framework before allowing application execution, then the system maintains architectural integrity, but the boot time extends to several minutes
Solution Approach 1:
The patent applies preliminary action by pre-assembling valid combinations of operating environment components, middleware, and core framework into boot images that are stored and ready for immediate execution. These pre-configured boot images maintain architectural integrity because they are created through validated configurations, yet they eliminate the need to load and verify the complete software stack during each boot sequence. The system can immediately execute these pre-validated compositions, achieving both stability and speed.
Data Source
AI summary
A method for booting a software operating environment and software applications within a wireless communications system (100) is provided. The method (500) includes executing one or more boot manager programs (516). The method further includes executing a first stage program code (614) and a second stage program code (618) in response to a boot manager program. The method includes loading an operating system (714) and launching a low level radio function application (716) in response to a boot manager program. The low level radio function can be an emergency communications application. Subsequent to loading the operating system and launching the low level radio function application, the method further includes loading a middleware (812) and a core framework (814) in response to the second stage program code. The method includes loading a device driver software programs in response to the first stage program code. The device driver software programs can be allocated and deallocated upon stated events. A computer program product in a computer readable medium is also provided. A computer processing system for booting a software operating environment and software applications within a wireless communications system is also provided.