XR Runtime Container for Cross-Device App Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing game engines are not suitable for developing XR applications, posing challenges for terminal development engineers due to high entry barriers, resource management issues, and integration difficulties with 2D applications, leading to complex and inefficient XR application development and cross-device compatibility problems.

Innovation Solution

A runtime container provides a cross-platform and cross-device runtime environment for XR applications, integrating a content generator and application generation platform, allowing developers to create XR applications with a low barrier to entry and enabling seamless integration of 3D scenes in 2D applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If game engines are used for XR application development, then development functionality is provided, but entry barrier becomes high and development complexity increases

Engineering Contradiction:
ImproveXR application development easeVSAvoiddevelopment system complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The system is segmented into distinct components: a runtime container providing the execution environment, a content generator for creating XR content, and an application generation platform. This segmentation allows each component to be optimized independently and reduces the complexity burden on developers, as they only need to interact with the content generator rather than the entire complex engine system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The runtime container acts as an intermediary between the XR application content and the host application/operating system. It provides a standardized interface and abstraction layer that simplifies integration, eliminating the need for developers to directly handle complex system-level integration issues that would otherwise increase development complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional development approaches are used, then development can proceed, but cross-device compatibility problems arise

Engineering Contradiction:
Improvecross-device compatibilityVSAvoidintegration difficulty
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The runtime container is designed with universal functionality to support multiple device types and operating systems. It implements a standardized interface that works across different platforms (mobile devices, XR headsets, PCs), allowing the same XR application content to run on various devices without modification. This universality is achieved through abstracted system interactions and platform-agnostic content formats.

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

3Adaptability or versatility

If XR applications are developed separately from 2D applications, then XR functionality is achieved, but integration with 2D applications becomes complex

Engineering Contradiction:
Improveintegration capabilityVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The XR application content is nested within the host application's execution flow through the runtime container. The content generator produces XR content that can be embedded and executed within the existing 2D application structure. The runtime container manages the nested execution environment, handling resource allocation and coordination between the host application and XR content, thereby simplifying integration.

Inventive Principle:
Principle #7Nested doll (Nesting)

4Reliability

If resource management is handled by traditional engines, then resource allocation is performed, but resource management issues persist

Engineering Contradiction:
Improveresource management reliabilityVSAvoidresource management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The runtime container implements self-service resource management by automatically allocating and managing resources (memory, CPU, GPU) based on the requirements of the XR content and the capabilities of the host device. It includes built-in mechanisms for resource pooling, garbage collection, and adaptive resource allocation that eliminate the need for manual resource management by developers, thereby improving reliability while reducing complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP4708045A1XR application running method, XR content running method, device, and storage medium
Publication Date: 2026.03.11 TAOBAO CHINA SOFTWARE
  • EP4708045A1 patent drawingFigure 1
  • EP4708045A1 patent drawingFigure 2
  • EP4708045A1 patent drawingFigure 3

AI summary

Embodiments of the present application provide a method, an apparatus, and a storage medium for running an XR application and content. In the embodiments of the present application, application content of an XR application is generated based on a runtime environment provided by the runtime container; with the application content is generated, the XR application is generated according to 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.