Spatial Map Readiness Notification for Reliable Localization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack mechanisms for indicating when a spatial map is ready for employment in localization services, leading to potential service failures and user experience interruptions in metaverse applications.

Innovation Solution

Implement systems and methods for a first entity to send a subscribe request to a second entity for a spatial map employed event, receiving a success response and notifications when the spatial map is ready to provide localization services, using a spatial map employment controller to manage communication and security parameters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system waits for spatial map processing to complete before notifying the application, then service reliability is improved, but service response time increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidservice response time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by subscribing to spatial map employment events in advance and preparing the notification mechanism before the map is ready. This allows the system to immediately notify the application as soon as the map becomes available, eliminating waiting time while ensuring reliability through pre-validated subscription processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the application layer subscribes to spatial map employment events and receives real-time notifications when the map becomes ready. This continuous feedback loop ensures the application is immediately informed of map availability status changes, maintaining both reliability and rapid response time.

Inventive Principle:
Principle #23Feedback

2Reliability

If the system implements a subscription mechanism for spatial map events, then service reliability is improved, but system complexity increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The notification mechanism is designed with multi-functionality to serve various spatial map events and different application layer needs through a unified subscription interface. This universal approach reduces overall system complexity by avoiding multiple specialized mechanisms while maintaining reliability through consistent event notification across different scenarios.

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

3Ease of operation

If real-time notification of spatial map readiness is implemented, then user experience is improved, but communication overhead increases

Engineering Contradiction:
Improveuser experienceVSAvoidcommunication overhead
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

Instead of continuous polling, the system uses event-driven periodic notification where the application layer receives updates only when spatial map employment status changes. This periodic action based on actual events maintains excellent user experience by providing timely notifications while minimizing communication overhead by avoiding unnecessary transmissions during unchanged states.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS20260039723A1Systems and methods for indicating spatial map employment for localization services
Publication Date: 2026.02.05 SAMSUNG ELECTRONICS CO LTD
  • US20260039723A1 patent drawing
  • US20260039723A1 patent drawing
  • US20260039723A1 patent drawing

AI summary

Embodiments herein disclose methods for indicating a spatial map employment for a localization service. The method includes sending, by a first entity (102), a subscribe request to subscribe for a spatial map employed event to a second entity (112). The subscribe request may include a map identity, an identity associated with a requestor, and at least one security parameter. The method further includes receiving, by the first entity (102), a success response from the second entity (112) based on the subscribe request. The success response may include a subscription identity.