Modem Configuration Data Storage in Dual OS Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing approaches for reducing mobile device start-up time are hindered by the need for different modem designs for Windows and Android OS, leading to increased costs and complexity due to the use of flash memory in Windows and flashless modems in Android, which complicates calibration and boot-up processes, especially when supporting dual OS systems.
Innovation Solution
A communication terminal design that unifies the calibration process across multiple operating systems by using a system boot firmware to store and provide modem configuration data, including firmware and calibration data, before the OS boots up, allowing for a common storage approach and reducing the need for additional hardware and software modifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If flash memory is used in modem for Windows OS, then configuration data can be stored in modem, but manufacturing cost and device complexity increase
Solution Approach 1:
The patent extracts the flash memory component from the modem design and relocates configuration data storage to the main device's flash memory. The modem is designed to operate without internal flash memory, instead receiving configuration data from the main device's storage during boot-up, thereby simplifying modem design while maintaining configuration storage capability.
Solution Approach 2:
The main device's flash memory and processor are made multi-functional by enabling them to store and manage modem configuration data in addition to their primary functions. The system boot firmware in the main device performs dual roles: booting the main device and providing configuration data to the modem, eliminating the need for separate modem-specific storage.
2Reliability
If different modem designs are used for Windows and Android, then each OS gets optimized performance, but manufacturing cost and calibration complexity increase
Solution Approach 1:
A single universal modem design is created that can serve both Windows and Android operating systems. The modem receives OS-specific configuration data from the main device's flash memory during boot-up, allowing one modem hardware design to support multiple OS platforms without requiring separate calibrated modem units for each OS.
Solution Approach 2:
Instead of creating different hardware designs, the system changes the software parameters and configuration data provided to the modem based on the operating system. The same physical modem receives different configuration sets depending on whether it's booting Windows or Android, achieving OS-specific optimization without hardware differentiation.
3Device complexity
If flashless modem design is used for Android, then manufacturing cost is reduced, but boot-up time increases due to configuration data transfer
Solution Approach 1:
The system performs preliminary action by pre-storing all necessary modem configuration data in the main device's flash memory before the boot-up process begins. The system boot firmware retrieves and provides this configuration data to the modem during the boot sequence, ensuring the modem is fully configured and operational as quickly as possible without requiring internal flash memory.
Data Source
AI summary
A communication terminal is described comprising a modem; a first memory configured to store configuration data for the modem; a second memory configured to store a system boot firmware; and a processor configured to execute the system boot firmware and to read the configuration data from the memory and provide it for the modem under the control of the system boot firmware.