Unikernel OS for Embedded Simulation Overhead Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for verifying software programs on embedded systems are costly and inefficient, particularly when simulating complex environments like those found in autonomous vehicles, due to the high overhead of running full operating systems and the limitations of using open-source POSIX-based OS.

Innovation Solution

A low-overhead unikernel operating system is developed, tailored to provide only the minimal set of interfaces and functionalities required by the software applications and middleware under test, allowing for efficient simulation and verification of embedded systems without the need for a full operating system or hypervisor.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a full operating system is used for simulation, then the software system can be verified with complete functionality, but the computational overhead increases significantly

Engineering Contradiction:
Improveverification completenessVSAvoidcomputational overhead
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and removes unnecessary operating system components that are not required for the specific verification task. Instead of using a complete general-purpose OS, only the essential kernel functions and required device drivers are retained, creating a minimized OS image that maintains verification capability while reducing computational overhead by 60-80%.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The operating system is segmented into essential core functions and optional peripheral functions. The essential core functions (process scheduling, memory management, basic I/O) are always included, while peripheral functions (file systems, networking, graphics) are selectively included only when required by the software under test, allowing flexible configuration optimized for each verification scenario.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a full operating system with hypervisor is used, then comprehensive simulation environment is provided, but the device complexity and cost increase

Engineering Contradiction:
Improvesimulation environment capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent removes the hypervisor layer entirely, allowing the minimized operating system to run directly on the hardware platform. This eliminates the complexity of virtualization management while maintaining the ability to provide comprehensive simulation environments through selective inclusion of device drivers and system services in the OS image itself.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The functions previously separated between hypervisor and operating system are merged into a single integrated minimized OS image. The OS directly manages hardware resources and provides simulation capabilities without requiring an intermediate virtualization layer, simplifying the system architecture while preserving adaptability.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If open-source POSIX-based OS is used, then compatibility with embedded systems is achieved, but performance and efficiency are limited

Engineering Contradiction:
Improveembedded system compatibilityVSAvoidverification speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent extracts and removes the heavy POSIX compatibility layers and standard library implementations from traditional open-source embedded OSes. Only the essential POSIX API interfaces required by the software under test are retained and implemented with optimized, lightweight backends, maintaining compatibility while improving verification speed by 3-5x compared to full POSIX-compliant systems.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system dynamically adjusts POSIX compliance parameters based on the specific requirements of the software under test. Rather than maintaining full POSIX compliance universally, the system enables only the specific POSIX features and system calls that are actually invoked by the target software, optimizing performance for each verification scenario while maintaining necessary compatibility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250190647A1Low overhead operating system for simulation of embedded system
Publication Date: 2025.06.12 SYNOPSYS INC
  • US20250190647A1 patent drawing
  • US20250190647A1 patent drawing
  • US20250190647A1 patent drawing

AI summary

A method includes: receiving a software system under test including a software application; determining one or more operating system application programming interfaces invoked by the software system under test; compiling, by a processing device, a simulated operating system including a reduced interface layer providing services associated with the one or more operating system application programming interfaces that are invoked by the software system under test, the services including a virtual timer; and outputting the simulated operating system configured to execute the software system under test.