Memory-Centric Architecture Eliminates OS Boot Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computers rely on a disk-centric architecture, requiring a transition from BIOS to the Operating System and storage devices for program execution, leading to inefficiencies in data flow and processing time, limiting developers to create applications for specific operating systems rather than target architectures.

Innovation Solution

The introduction of a novel computer architecture, 'memory-centric' design, utilizing the NETMORY interconnect to facilitate direct communication and data flow between the core and the network, eliminating the need for a storage device and Operating System, allowing applications to run directly from the platform and embedded firmware.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a disk-centric architecture with Operating System is used, then standardized environment and hardware/software resources are provided, but processing time increases and data flow efficiency deteriorates

Engineering Contradiction:
Improvestandardized environmentVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts and removes the Operating System layer from the computer architecture, allowing applications to run directly on the hardware platform. This eliminates the BIOS-OS transition overhead and direct disk access requirements, significantly reducing processing time while maintaining standardized environments through the embedded firmware layer.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by pre-loading applications and data into memory before execution is needed. The memory-centric architecture keeps frequently accessed data in memory rather than on disk, eliminating I/O wait time and enabling instant application startup and resumption after interruptions.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If BIOS and Operating System transition is implemented, then embedded code to normal code transition occurs, but system complexity and device requirements increase

Engineering Contradiction:
Improvecode transition capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent removes the Operating System component entirely from the system architecture. Applications compile directly to machine code that runs on the hardware platform with embedded firmware, eliminating the need for BIOS-OS transitions, boot sectors, and OS kernel management, thereby reducing system complexity while maintaining adaptability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The embedded firmware serves multiple functions simultaneously: it initializes hardware, manages memory, handles I/O operations, and provides a runtime environment for applications. This multi-functional firmware replaces the combined roles of BIOS and Operating System, simplifying the system while maintaining versatility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Stability of the object's composition

If data is stored on disk and loaded into memory, then persistent storage is achieved, but data flow efficiency and access speed decrease

Engineering Contradiction:
Improvepersistent storageVSAvoiddata access speed
Core Design Contradiction:
Stability of the object's compositionVSSpeed

Solution Approach 1:

The patent pre-loads applications and frequently accessed data into memory during system initialization or beforehand, so that when execution is needed, the data is already in fast memory rather than requiring disk I/O. This eliminates the bottleneck of loading data from disk during runtime.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent changes the primary data storage dimension from disk-based persistent storage to memory-based storage. By using memory-mapped files and keeping working sets in memory, the system achieves persistent storage capabilities while operating from the faster memory dimension rather than the slower disk dimension.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Adaptability or versatility

If multiple Operating Systems are supported, then developer versatility is improved, but system complexity and development overhead increase

Engineering Contradiction:
Improveoperating system compatibilityVSAvoiddevelopment overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The embedded firmware provides a universal runtime environment that directly supports multiple application architectures without requiring separate Operating System ports. Developers compile applications once for the target hardware platform, and the firmware handles the universal interface, eliminating the need to develop and maintain multiple OS-specific versions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9697114B2Netmory
Publication Date: 2017.07.04 LERMAN MIKHAEL
  • US9697114B2 patent drawing
  • US9697114B2 patent drawing
  • US9697114B2 patent drawing

AI summary

An apparatus, method, and system are provided as a solution for computer operation. An embodiment of the apparatus includes a device that interconnects the core of the computer through the memory interface. The apparatus provides a communication path from the computer core to the world wide network. Computing communication and storage functions of the conventional computer are incorporated in the apparatus. The purpose of the apparatus is to enable the computer data and program to flow into and out of the computer core without being stored on a peripheral device such a disk or other media.