OS Switching Controller for Peripheral Conflict Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Dual operating system architectures face conflicts during switching, leading to initialization failures and system crashes due to conflicting system commands and settings from competing operating systems when one OS is in a sleep state.

Innovation Solution

Implementing a controller that intercepts and prevents setting commands from the first operating system when switching to the second OS, and uses synchronization managers to ensure only one OS controls peripheral devices, with an optional response table to simulate device responses for smooth switching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dual operating systems are integrated into a single electronic device to take advantage of both systems, then the versatility and functionality of the device is improved, but system conflicts and initialization failures occur when switching between operating systems

Engineering Contradiction:
Improvedual operating system functionalityVSAvoidsystem stability during switching
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

A controller is introduced as an intermediary component between the first operating system, second operating system, and peripheral devices. The controller intercepts setting commands from the inactive operating system and prevents them from reaching peripheral devices, thereby mediating the interaction between dual operating systems and eliminating conflicts during switching.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Use of energy by moving object

If the first operating system remains in sleep state while second operating system is activated, then resource sharing is improved, but the first operating system continues to send setting commands causing conflicts

Engineering Contradiction:
Improvepower saving through sleep stateVSAvoidcommand conflict prevention
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The controller acts as a mediator that receives setting commands from the first operating system in sleep state and intercepts them before they reach peripheral devices. This allows the first OS to remain in low-power sleep state while preventing its commands from conflicting with the active second OS.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The controller proactively intercepts and blocks setting commands from the inactive operating system before they can execute and cause conflicts. This preliminary anti-action prevents potential initialization failures and system crashes before they occur.

Inventive Principle:
Principle #9Preliminary anti-action

3Ease of operation

If setting commands from inactive operating system are allowed to reach peripheral devices, then the inactive OS maintains its operational readiness, but initialization failures and system crashes occur

Engineering Contradiction:
Improveoperating system switching smoothnessVSAvoidperipheral device initialization success
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The controller serves as an intermediary that selectively blocks setting commands from the inactive operating system while allowing commands from the active operating system to pass through. This ensures reliable peripheral device initialization by the active OS without interference from the inactive OS.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9052920B2Electronic devices and methods for switching between dual operating systems
Publication Date: 2015.06.09 WISTRON CORP
  • US9052920B2 patent drawing
  • US9052920B2 patent drawing
  • US9052920B2 patent drawing

AI summary

A method for switching between dual operating systems for an electronic device installed with at least two operating systems is provided. The method includes the steps of: activating and operating a first operating system, wherein the first operating system initializes at least one peripheral device; switching to and activating a second operating system; preventing the first operating system from issuing a setting command to the peripheral device when the first operating system is switched to the second operating system; and enabling the second operating system to obtain the control right of the peripheral device to initialize the peripheral device.