Subtree Data Structure for Map-Agnostic Traffic Transmission

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current navigation systems face challenges in providing up-to-date traffic data across different map versions, leading to performance and maintenance issues due to the need for multiple map versions on servers, which consume significant storage space and hinder rapid updates.

Innovation Solution

The implementation of a subtree data structure that encodes traffic data using map version agnostic identifiers, allowing for bandwidth-efficient transmission and decoding of traffic data, independent of specific map versions, enabling clients to receive up-to-date traffic information without requiring the most recent map version.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the server maintains multiple map versions to provide traffic data for clients with different map versions, then compatibility with clients using different map versions is improved, but server storage space is consumed and maintenance complexity increases

Engineering Contradiction:

Improvecompatibility with different map versionsVSAvoidserver storage space

Core Design Contradiction:

Adaptability or versatilityVSVolume of stationary object

Solution Approach 1:

The patent extracts the version-specific road segment information from the complete map data and transmits only the necessary traffic data for road segments that exist in both server and client map versions. This is achieved by comparing road segment identifiers between server and client, then transmitting traffic data only for matching road segments, thereby eliminating the need to store multiple complete map versions on the server.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments the traffic data transmission process into two parts: first transmitting a subset of road segment identifiers that exist in both server and client map versions, then transmitting traffic data only for those matching road segments. This segmentation allows the system to provide version-agnostic traffic data without requiring the server to maintain multiple complete map versions.

Inventive Principle:

Principle #1Segmentation

2Reliability

If the server maintains multiple map versions to provide identifiable traffic data, then traffic data availability for clients with older map versions is improved, but performance and maintenance issues arise due to storing a large number of map versions

Engineering Contradiction:

Improvetraffic data availabilityVSAvoidmaintenance complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and transmits only the essential traffic data for road segments that can be identified by both server and client map versions. By comparing road segment identifiers and transmitting only matching data, the system ensures traffic data availability without requiring the server to maintain multiple complete map versions, thereby reducing maintenance complexity.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a virtual copy of the necessary road segment information by transmitting a subset of road segment identifiers that exist in both server and client versions. This virtual copying approach allows clients to receive accurate traffic data for their local road segments without the server storing multiple complete map versions, simplifying maintenance while ensuring data availability.

Inventive Principle:

Principle #26Copying

3Productivity

If the server stores a large number of map versions to support rapid refreshing, then update frequency is improved, but storage space requirements increase

Engineering Contradiction:

Improvemap update frequencyVSAvoidserver storage space

Core Design Contradiction:

ProductivityVSVolume of stationary object

Solution Approach 1:

The patent extracts only the necessary traffic data for road segments that exist in both server and client map versions and transmits this subset data. This extraction approach enables frequent updates of traffic data without requiring the server to store multiple complete map versions, thereby achieving rapid refresh capability with minimal storage space requirements.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS11675819B2Method, system, and computer program product for providing traffic data using subtree data structure

Publication Date: 2023.06.13 HERE GLOBAL BV

AI summary

A method, a system, and a computer program product may be provided for providing traffic data to a client device. The system may receive from the client device, a request for traffic data corresponding to road segments of at least one map area, said request identifying the at least one map area and determine road segment identifiers corresponding to each of the road segments of the at least one map area and determine traffic data for at least a portion of the road segment identifiers, said traffic data obtained from a traffic data source. The system may further determine a plurality of traffic ranges based on the obtained traffic data and generate a subtree data structure set, each subtree data structure of the subtree data structure set corresponding to a traffic range of the plurality of traffic ranges, wherein each subtree data structure encodes road segment identifiers corresponding to the respective traffic range.