Container-Based Simulation Architecture for Distributed Entity Modeling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software architectures lack a framework for simulating physical entities in a time domain on distributed computer networks, specifically failing to provide a container-based architecture for realistic simulation environments and flight simulators.

Innovation Solution

A container-based software architecture with an object-oriented simulation framework that includes simulation containers, views containers, and participant components, enabling realistic simulations of physical entities and their environments by providing execution environments, run loop management, event posting, and network data reflection services, along with graphical and motion input support.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a traditional software architecture is used for simulation, then the system can be implemented with basic programming structures, but the system lacks extensibility and scalability for adding new entities and environments

Engineering Contradiction:
Improveextensibility and scalabilityVSAvoidarchitecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The simulation system is divided into independent container components (simulation container, views container, participant container) that can be separately developed, deployed, and scaled. Each container encapsulates specific functionality, allowing the system to extend capabilities by adding new container types without restructuring the entire architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The container-based architecture creates universal building blocks that can serve multiple simulation scenarios. The simulation container framework can host various types of participants (entities, non-entities, controllers) and support different view types, providing multi-functionality through a unified architectural pattern that enhances adaptability.

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

2Adaptability or versatility

If a container-based architecture with multiple containers and participants is implemented, then the simulation system becomes extensible and scalable, but the device complexity and implementation difficulty increase

Engineering Contradiction:
Improvesimulation environment varietyVSAvoidsystem structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The simulation container acts as an intermediary that manages the complex interactions between participants, views, and the simulation environment. It provides standardized interfaces and coordination mechanisms that simplify the system structure by centralizing management logic, thereby reducing the apparent complexity for users and developers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The architecture employs nested container structures where participant containers are nested within simulation containers, and views are nested within participant containers. This hierarchical nesting organizes complexity into manageable layers, allowing the system to support diverse simulation environments while maintaining a clear structural hierarchy that simplifies implementation.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Ease of manufacture

If plug-in components are used to enable extensibility, then new entities can be added without rewriting existing software, but the interface management and component integration become more complex

Engineering Contradiction:
Improvesoftware modification easeVSAvoidinterface management complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The container interface definitions establish standardized parameters and methods that plug-in components must implement. By changing and customizing these interface parameters to match specific simulation needs, new entities can be integrated without modifying existing container code, thereby easing software modification while maintaining interface consistency through controlled parameter variations.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8150664B2Container-based architecture for simulation of entities in time domain
Publication Date: 2012.04.03 ZEDASOFT
  • US8150664B2 patent drawing
  • US8150664B2 patent drawing
  • US8150664B2 patent drawing

AI summary

The present invention relates generally to a software architecture for simulation of physical entities. The invention provides an object-oriented container based framework architecture for simulator software implementations, methods, and objects in a time domain on a distributed computer network. The invention further provides an interface system and a plug-in definition which allows compartmentalization of participants in the container and easy extensibility of the system.