XR Runtime Container for Cross-Device 3D-in-2D App Development

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing game development engines pose a high barrier for terminal development engineers due to their complexity and are not suitable for developing XR applications, especially those with 3D scenes embedded in 2D applications, leading to challenges in cross-device and cross-platform compatibility.

Innovation Solution

A runtime container is integrated into a content generator to provide a runtime environment for XR application development, allowing terminal development engineers to create XR applications with reduced complexity and enabling cross-platform and cross-device compatibility by shielding underlying device information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If game development engines are used for XR application development, then development functionality is provided, but development complexity and barrier increase significantly

Engineering Contradiction:
ImproveEase of XR application developmentVSAvoidDevelopment engine complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent extracts the essential runtime environment functionality from complex game development engines and encapsulates it in a dedicated runtime container. This container provides only the necessary XR runtime capabilities (scene rendering, resource management, lifecycle control) without the unnecessary complexity of full game engines, thereby reducing the development barrier while maintaining core functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the XR application into two independent parts: application content (business logic, 3D scenes, resources) and runtime container (execution environment). This segmentation allows terminal development engineers to focus solely on creating application content without needing to understand or manage the complexity of the runtime environment, significantly easing the development process.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If traditional development engines are used, then application development is possible, but cross-device and cross-platform compatibility becomes difficult

Engineering Contradiction:
ImproveCross-device and cross-platform compatibilityVSAvoidDevelopment complexity for compatibility
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The runtime container is designed as a universal execution environment that can run on multiple different devices and platforms (mobile phones, tablets, PCs, XR headsets). It provides standardized interfaces and abstractions that hide underlying device differences, allowing the same application content to run across diverse platforms without modification, thereby achieving cross-device and cross-platform compatibility.

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

Solution Approach 2:

The runtime container acts as an intermediary layer between the application content and the underlying operating system/device hardware. It provides a standardized interface that abstracts away device-specific complexities, allowing terminal development engineers to write platform-independent application content while the runtime container handles platform-specific adaptations, thus simplifying cross-platform development.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If runtime container is integrated into content generator, then development complexity is reduced, but system architecture becomes more complex

Engineering Contradiction:
ImproveEase of XR application creationVSAvoidSystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent merges the runtime container directly into the content generator toolchain. This integration allows terminal development engineers to create, validate, and package application content within a unified development environment, simplifying the development process. The content generator automatically handles the complexity of integrating application content with the runtime container, producing ready-to-deploy XR applications without requiring developers to manually manage the underlying system architecture.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP4708029A1XR application editing method, device, and storage medium
Publication Date: 2026.03.11 TAOBAO CHINA SOFTWARE
  • EP4708029A1 patent drawingFigure 1
  • EP4708029A1 patent drawingFigure 2
  • EP4708029A1 patent drawingFigure 3

AI summary

Embodiments of the present application provide an XR application editing method, an device, and a storage medium. In an embodiment of the present application, a runtime container is integrated in a content generator, and application content of an XR application is generated based on a runtime environment provided by the runtime container. When the application content is generated, the XR application is generated from the application content and the runtime container. The runtime container runs between the application content and an operating system to provide the runtime environment for the application content. Because the runtime container is added between the application content and the operating system, the running of the application content is no longer strongly dependent on the operating system, enabling the development and running of the XR application to be cross-platform and cross-device. This makes the development of the XR application simple and easy to implement, solving problems of XR application development and cross-device running.