Assistance Data Management for Mobile Navigation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing location-based assistance data management systems for mobile devices lack efficient methods to track and utilize quality information of assistance data, leading to potential inaccuracies and inefficiencies in providing navigation assistance.

Innovation Solution

A system that tracks quality information of assistance data, including current and previous versions, and determines when to provide assistance data to mobile devices based on this information and device-specific handling parameters, using a processor and memory to execute computer program code for managing and updating this data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If assistance data is delivered using request-response signaling, then the server does not need memory to store data, but the system cannot track quality information of different data versions

Engineering Contradiction:
Improvequality information trackingVSAvoidserver memory requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server pre-generates and stores multiple versions of assistance data with associated quality information before actual delivery. This preliminary action enables the server to track quality metrics across different data versions and selectively deliver appropriate versions based on terminal capabilities and conditions, resolving the contradiction between reliability through quality tracking and device complexity through memory usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where terminals report their assistance data usage results and quality metrics back to the server. This feedback loop allows the server to continuously update and refine its quality information tracking for different data versions, enabling improved reliability while managing memory resources efficiently through selective data retention based on actual performance feedback.

Inventive Principle:
Principle #23Feedback

2Productivity

If assistance data is broadcast to all terminals, then the same data reaches multiple terminals, but the system cannot provide personalized or selective data delivery

Engineering Contradiction:
Improvedata delivery efficiencyVSAvoidselective data delivery
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The assistance data is segmented into multiple versions with different quality levels, formats, or content subsets. The server maintains a structured catalog of these segmented versions with associated quality information, enabling selective delivery to different terminal types based on their specific capabilities and needs, thus achieving both efficient broadcast-style delivery and personalized adaptation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different versions of assistance data are optimized for specific terminal types, locations, or service requirements. The server uses quality information tracking to identify which segmented data version best matches each terminal's local conditions and capabilities, delivering personalized data through targeted unicast or groupcast transmissions rather than uniform broadcast to all terminals.

Inventive Principle:
Principle #3Local quality

3Reliability

If the server delivers current version assistance data to all terminals, then data currency is maintained, but unnecessary data transmission consumes network resources

Engineering Contradiction:
Improvedata currencyVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The server delivers only the necessary portion of assistance data to each terminal based on quality information tracking and terminal-specific needs. Rather than universally delivering all current version data, the system performs partial deliveries tailored to each terminal's actual requirements, maintaining data currency where needed while minimizing unnecessary network resource consumption through selective, optimized data transmission.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9297902B2Assistance data management
Publication Date: 2016.03.29 NOKIA TECHNOLOGIES OY
  • US9297902B2 patent drawing
  • US9297902B2 patent drawing
  • US9297902B2 patent drawing

AI summary

It is disclosed to keep a track of quality information of at least one assistance data, the track of quality information being associated with a current version and at least one previous version of the at least one assistance data, and to determine whether to provide assistance data information associated with at least one assistance data of the at least one assistance data to a mobile device based on tracked quality information of the at least one assistance data of the at least one assistance and based on assistance data handling parameters associated with the mobile device.