Trajectory Storage via Road Segment Entry and Exit Points
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The large volume of trajectory data generated by vehicles or entities poses a significant burden on storage resources and hampers real-time querying capabilities, especially when trying to retrieve specific information like arrival times or positions.
Innovation Solution
Mapping trajectory data to road segments in a road network, identifying entry and exit points, and storing data related to these points to represent road segments as part of the trajectory, reducing data volume by using offset distances instead of full coordinates and leveraging connectivity information between segments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If position data of multiple positions on a trajectory are directly stored in a database, then the trajectory information is complete and accurate, but the data volume becomes tremendous and storage burden increases significantly
Solution Approach 1:
The patent extracts only the essential information needed to represent trajectory - specifically the entry and exit points of road segments - rather than storing all intermediate position data. This extraction principle reduces data volume while preserving the ability to reconstruct and query trajectory information effectively.
Solution Approach 2:
The trajectory is segmented into discrete road segments with defined entry and exit points. By dividing the continuous trajectory into segment-based units, the system stores only the critical boundary points rather than all continuous position data, achieving compression while maintaining query capability.
2Measurement precision
If all position data are stored in detail, then query accuracy for specific positions is high, but real-time query performance deteriorates due to tremendous data size
Solution Approach 1:
The patent extracts only the critical entry and exit points of road segments from the full trajectory data. This extraction enables faster query response times while maintaining sufficient accuracy for determining whether a trajectory passes through specific locations or time periods.
Solution Approach 2:
The patent applies partial action by storing only the necessary subset of trajectory points (entry and exit points) rather than all position data. This partial storage approach achieves real-time query performance while providing sufficient information for most trajectory analysis needs.
3Loss of information
If full trajectory data are stored, then data completeness is maintained, but storage resource consumption increases significantly
Solution Approach 1:
The patent extracts only the essential entry and exit points of road segments from complete trajectory data. This extraction maintains the ability to represent and query trajectory information while dramatically reducing storage resource requirements by eliminating redundant intermediate position data.
Solution Approach 2:
By segmenting the trajectory into road segment units with defined entry and exit points, the system achieves efficient compression. The segmentation allows the trajectory to be represented by discrete points rather than continuous data, reducing storage needs while preserving information completeness for query purposes.
Data Source
AI summary
An embodiment of the present invention provides a method for storing trajectory. The method includes: mapping, based on a plurality of positions on a trajectory of an entity, the trajectory to at least one road segment in a road network; identifying an entry point and an exit point of one of the road segments, wherein the entry point is a point where the entity starts traveling along the road segment, and the exit point is a point where the entity ends traveling along the road segment; and storing data related to at least one of the entry point and the exit point, to store the road segment as a part of information of the trajectory.