Interactive Multimedia Engine with Dynamic Scenario Parsing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional interactive multimedia systems are inflexible and require extensive reprogramming to adapt to different applications, leading to high maintenance costs and complexity, as they are designed with statically defined real-time media processing capabilities that cannot easily accommodate varying virtual scenes and user interactions.

Innovation Solution

A device and method featuring a real-time media processing engine with a virtual scenario description repository, parser/loader, and plug-in modules that allow for dynamic loading and creation of processing chains based on descriptor streams and triggering rules, enabling the creation of a wide range of interactive multimedia applications with a single engine by separating scenario and engine components and using a scenario programming language.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a statically defined real-time media processing module is used, then the system structure is simple and easy to implement, but the system cannot adapt to different applications and requires extensive reprogramming

Engineering Contradiction:
Improveadaptability to different applicationsVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into a core engine with stable architecture and separate scenario-specific modules (virtual scene, media processing, interaction handling) that can be independently configured and replaced. This allows the core to remain simple while enabling adaptability through modular components.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The core engine is designed as a universal platform that can handle multiple different applications and scenarios through configuration rather than code changes. The same engine core supports diverse virtual scenes, media types, and interaction modes by loading different scenario modules.

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

2Adaptability or versatility

If the system is designed with fixed processing capabilities, then development and maintenance are easier, but any adaptation to new applications requires extensive reprogramming

Engineering Contradiction:
Improveflexibility to accommodate varying virtual scenesVSAvoidease of system adaptation
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system transitions from static fixed capabilities to dynamic configurable capabilities. The core engine dynamically loads and executes scenario-specific modules based on configuration files, allowing the system behavior to change without modifying the core code structure.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Scenario-specific configurations and modules are prepared in advance as separate files or modules that can be loaded into the core engine. This preliminary preparation allows quick adaptation to new applications by simply loading pre-configured scenario packages rather than reprogramming.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If extensive reprogramming is required for different applications, then the system can be highly customized, but maintenance costs and complexity increase significantly

Engineering Contradiction:
Improvecustomization capabilityVSAvoidmaintenance cost and complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of repair

Solution Approach 1:

By segmenting the system into a maintainable core engine and replaceable scenario modules, maintenance is confined to the stable core while scenario customizations are isolated in separate configuration files or modules that do not affect the core maintenance burden.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Scenario configurations are stored as external files or modules that can be copied, duplicated, and modified without affecting the core engine. This allows multiple applications to share the same core while having their own independent configuration copies.

Inventive Principle:
Principle #26Copying

4Productivity

If a generic core engine is used for multiple applications, then distribution and installation are simplified, but the engine must support a wide variety of scenarios

Engineering Contradiction:
Improveease of distribution and installationVSAvoidsupport for various virtual reality setups
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The core engine is designed as a universal platform with built-in support for multiple scenario types through configuration rather than code. A single core binary can be distributed once and will support diverse virtual reality setups by loading appropriate scenario modules from configuration files.

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

Solution Approach 2:

Configuration files serve as intermediaries between the generic core engine and specific application requirements. These files translate diverse scenario needs into a standardized format that the universal engine can process, enabling wide versatility without requiring engine modification.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8196132B2Interactive multimedia applications device
Publication Date: 2012.06.05 ALTERFACE
  • US8196132B2 patent drawing
  • US8196132B2 patent drawing
  • US8196132B2 patent drawing

AI summary

An interactive multimedia applications device and method for an interactive multimedia application comprises one or more live media capture devices providing a media stream, an engine comprising a real time media processing module for processing said media stream, and rendering means connected to multimedia output devices. In addition, said device comprises (i) a virtual scenario description repository adapted for storing a plurality of scenarios expressed in a scenario programming language; (ii) a memory module adapted for storing an internal representation of one of said scenarios, and an internal representation of a virtual scene and (iii) a parser/loader for parsing a selected one of said plurality of scenarios, and loading it in said memory module.