Read-Only Production Operating System Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Production workstations often have generic operating systems with unused memory resources that can serve as an attack vector for unwanted applications like viruses and malware, potentially spreading to programmed products or connected devices.

Innovation Solution

A method to generate a read-only production operating system by creating a baseline OS based on a target workstation's hardware profile, executing an installation script, and adding necessary resources to the OS, then writing the production OS to read-only media, ensuring only essential resources are included and minimizing the risk of unwanted applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a generic operating system is installed on production workstations, then the workstation can run various applications and programming tools, but the unused memory resources create an attack space for unwanted applications like viruses and malware

Engineering Contradiction:
Improveapplication compatibilityVSAvoidattack surface for malware
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only the necessary resources and applications required for production programming tasks from the generic operating system, removing extraneous components that create security vulnerabilities. This is achieved by capturing the actual resource usage during programming operations and building a customized OS image that includes only those resources, thereby eliminating the attack surface while maintaining functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by tailoring the operating system resources specifically to the needs of production programming workstations. Instead of a uniform generic OS, the system captures actual resource requirements (drivers, libraries, applications) used during programming operations and configures the OS image with precisely those resources, making each workstation optimized for its specific function while minimizing security exposure.

Inventive Principle:
Principle #3Local quality

2Adaptability or versatility

If extraneous resources are included in the operating system, then the workstation can potentially run unwanted applications, but this allocates unused memory space that increases security risks

Engineering Contradiction:
Improveresource availabilityVSAvoidsystem security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs self-service by automatically capturing resource usage during programming operations and using that information to configure the operating system image. The workstation itself generates the profile of needed resources through monitoring actual operations, eliminating the need for manual configuration or guessing which resources are necessary, thereby ensuring minimal yet sufficient resource inclusion.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements feedback by monitoring and capturing actual resource usage during programming operations, then using this captured information to configure the operating system image. The system observes what resources are actually accessed and needed, feeds this information back into the OS image creation process, and generates a customized image that includes only those resources, creating a closed-loop optimization that balances functionality and security.

Inventive Principle:
Principle #23Feedback

3Reliability

If a read-only operating system image is used, then the attack surface is minimized and security is improved, but the system requires careful preparation to ensure all necessary resources are included

Engineering Contradiction:
Improvesystem securityVSAvoidOS image preparation process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by capturing and profiling resource requirements during a preparation phase before the actual production use. The system monitors and records all resource accesses during programming operations, builds the customized OS image with these pre-identified resources, and then uses this pre-configured image for secure production operations. This preliminary resource profiling eliminates the need for complex post-deployment modifications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system performs preliminary configuration by capturing resource usage patterns during a setup phase, then using this captured information to pre-configure the read-only OS image with exactly the resources needed. This preliminary action ensures that when the read-only image is deployed for production, all necessary resources are already included, eliminating the complexity of manual resource identification and configuration.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9122551B2Methods and systems for generating read-only operating systems
Publication Date: 2015.09.01 THE BOEING CO
  • US9122551B2 patent drawing
  • US9122551B2 patent drawing
  • US9122551B2 patent drawing

AI summary

Methods and systems for use in generating read-only production operating systems including at least one application for use with a target workstation are disclosed. One example method includes providing a baseline operating system based on a hardware profile of the target workstation, executing an installation script for a target application, adding at least one resource to the baseline operating system based on an error message indicating at least one resource called by the installation script is not found, and writing, at a computing device, a production operating system to a read-only media. The production operating includes the baseline operating system and the at least one resource.