Background Activity Data Import for Location-Based Games

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Location-based games struggle to seamlessly integrate real-world activities into the virtual experience, leading to a disconnect between the real and virtual worlds, which reduces player engagement and immersion.

Innovation Solution

A system where client devices extract activity data from fitness applications and send it to a game server, allowing real-world actions to trigger in-game events and updates, even when the game is not actively being played, using a background process that synchronizes player positions and activities between the real and virtual worlds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If players actively play the location-based game to experience real-world activities, then player engagement with the game increases, but the game requires active player attention and time, preventing passive accumulation of activity benefits

Engineering Contradiction:
Improveactivity data accumulation rateVSAvoidplayer time investment
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by continuously collecting and storing activity data in the background before the player actually plays the game. The background process accumulates activity data from fitness applications, so when the player launches the game, the data is already ready to be processed and converted into in-game benefits without requiring the player to have been actively playing during the activity period.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically extracting activity data from integrated fitness applications without requiring player intervention. The background process autonomously monitors, collects, and processes activity data, and the system automatically converts this data into in-game rewards and updates, eliminating the need for players to manually transfer or input their activity information.

Inventive Principle:
Principle #25Self-service

2Productivity

If the game integrates with fitness applications to automatically collect activity data, then player engagement increases without additional time investment, but the system complexity increases due to background processes and data synchronization

Engineering Contradiction:
Improveactivity data collection efficiencyVSAvoidbackground process architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system merges the location-based game with existing fitness applications by integrating their data sources. The background process combines activity data from multiple fitness applications with game mechanics, creating a unified system where real-world physical activity automatically translates to in-game progress without requiring separate tracking systems or manual data entry.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The background process acts as an intermediary layer between fitness applications and the game. It extracts activity data from fitness applications, processes and validates the data, converts it into appropriate in-game metrics, and updates the game state accordingly. This intermediary simplifies the overall architecture by handling all data transformation logic in one centralized component rather than requiring direct integration between multiple applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20240399256A1Background process for importing real-world activity data into a location-based game
Publication Date: 2024.12.05 NIANTIC INC
  • US20240399256A1 patent drawing
  • US20240399256A1 patent drawing
  • US20240399256A1 patent drawing

AI summary

Events in an interactive application (e.g., a location-based parallel reality game) are triggered by a user's real-world activity meeting one or more criteria. A background process executing on the user's client device periodically extracts activity data from an activity monitoring application (e.g., a fitness application) and provides it to a server hosting the interactive application. The server determines whether received activity data triggers an event and, if so, sends a notification of the event to the client device.