Traffic Information Client Device Using Relational Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional navigation devices using traffic message channel (TMC) and transport protocol experts group (TPEG) protocols face inefficiencies due to static map data, difficulty in updating and expanding event and location code tables, and high memory usage, leading to inflexible and slow performance in processing traffic information.
Innovation Solution
An electronic device with a relational database that associates location and event codes with corresponding information, allowing for easy updates and expansions, reducing storage space and memory requirements by only accessing necessary information, and improving retrieval speed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If event code table and location code table are stored as binary large objects in database or embedded in software, then the device can store traffic information data, but updating and expanding the tables becomes difficult and requires software re-installation
Solution Approach 1:
The patent segments the event code table and location code table into separate, independently updateable components. Instead of storing them as monolithic binary large objects embedded in software, the tables are divided into discrete data structures that can be individually modified, added, or removed without affecting the entire software system. This allows updates and expansions to be performed independently of software re-installation.
2Adaptability or versatility
If TMC tables are pre-installed with event codes and location codes, then the device can process traffic information, but the tables are restricted to the market of manufacture and cannot be easily updated or expanded with new user languages
Solution Approach 1:
The patent implements a universal table structure that can accommodate multiple user languages and regional variations. The event code table and location code table are designed with extensible schemas that support adding new languages, countries, and regional-specific data without requiring fundamental system changes. This multi-functional design allows the same database structure to serve multiple markets and language requirements.
3Quantity of substance
If event code table and location code table are stored as binary large objects, then the data can be stored, but a relatively large amount of space is required and the whole object needs to be loaded into main memory
Solution Approach 1:
The patent extracts the event code table and location code table from the monolithic binary large object structure and stores them as separate, optimized database tables. This extraction allows the system to load only the specific tables or table portions needed for current operations into main memory, rather than loading the entire binary object. This significantly reduces memory requirements and improves loading efficiency.
4Productivity
If the whole binary large object needs to be loaded into main memory for accessing information, then data can be retrieved, but it reduces the performance of the device and access is slow
Solution Approach 1:
The patent segments the data storage structure into separate, independently accessible tables that can be queried directly from the database without loading the entire dataset into memory. This segmentation enables the system to retrieve only the specific records needed for current traffic information processing, significantly reducing data retrieval time and improving device performance.
Data Source
AI summary
The invention provides an electronic device configured to operate as a traffic information client. The traffic information client device comprises an interface adapted to receive traffic information messages, where a traffic information message comprises a location code which identifies a location of a traffic event. The traffic information client device further comprises a memory and a relational database stored in the memory, the relational database comprising at least a first set of relations including at least one relation which directly or indirectly associates location codes with location information.