XR Website Handling Through Session-Aware Server Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing XR systems face delays and inefficiencies due to direct user-initiated connections with web servers, leading to suboptimal resource accessibility, concurrency, scalability, and error tolerance in virtual and physical reality environments.

Innovation Solution

The XR system is designed such that web servers initiate communication with the XR environment, providing additional information via an XR session identifier, allowing the XR server to generate and manage XR data without direct user interaction, thus optimizing resource accessibility and reducing server load.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If direct user-initiated connections are used between XR clients and web servers, then user control and direct access are improved, but server load and communication delays increase

Engineering Contradiction:
Improveuser controlVSAvoidserver load
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent introduces a server-side HTTP request handler that acts as an intermediary between web servers and XR clients. This handler receives HTTP requests from web servers, processes them, and sends responses back, eliminating the need for direct XR client-to-server connections. The intermediary maintains user control through session management while reducing the communication burden on XR clients and optimizing server resource utilization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple XR clients connect directly to web servers, then resource accessibility is improved, but concurrency and error tolerance deteriorate

Engineering Contradiction:
Improveresource accessibilityVSAvoidconcurrency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The server-side HTTP request handler serves as a central intermediary that manages all XR client connections. It maintains session states for multiple users, coordinates resource access, and handles concurrent requests systematically. This approach preserves resource accessibility for all users while improving concurrency handling and error tolerance through centralized session management and standardized request processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If XR clients initiate direct connections to web servers, then direct data access is improved, but scalability and security deteriorate

Engineering Contradiction:
Improvedata access speedVSAvoidscalability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements a server-side HTTP request handler that mediates all data access requests. This handler optimizes data retrieval and transmission processes, maintaining fast data access speeds while providing a standardized interface that improves system scalability. The intermediary can manage multiple web servers and XR clients uniformly, enabling the system to scale without requiring changes to client architecture or connection protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12406443B2System and a method for handling websites in an extended reality system
Publication Date: 2025.09.02 XR WIZARDS SP ZOO
  • US12406443B2 patent drawing
  • US12406443B2 patent drawing
  • US12406443B2 patent drawing

AI summary

An extended reality (XR) system includes an XR server for generating XR environment data for an XR session defined by an XR session identifier; and a client application for operating on an XR device to present an XR environment to a user based on the XR environment data received from the XR server. The client application has a web browser configured to communicate with at least one web server. The web browser of the client application sends to the web server a content request comprising a content identifier and the XR session identifier that defines the XR session presented by the client application. The XR server receives from the web server additional information for the XR session defined by the XR session identifier; and changes the XR environment corresponding to the XR session identifier received from the web server based on the additional information received from the web server.