Natural Language Telematics Queries for Targeted Fleet Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and retrieving telematics data from a fleet of vehicles is challenging due to the volume of data, time-consuming report reviews, and difficulty in identifying specific insights, particularly for users without technical expertise.

Innovation Solution

A system utilizing a large language model (LLM) generates executable queries based on natural language requests to retrieve specific telematics data without direct access to the databases, incorporating contextual prompts and example queries to enhance data retrieval efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If comprehensive reports of telematics data are retrieved to gain insights about vehicle fleet, then data completeness is improved, but time consumption and storage requirements increase

Engineering Contradiction:
Improvedata completenessVSAvoidreport review time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system extracts only the specific telematics data points that are relevant to the user's natural language question, rather than retrieving entire comprehensive reports. The query generation model translates user questions into targeted SQL queries that extract only necessary data fields, significantly reducing data volume while maintaining information completeness for the specific inquiry.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the large comprehensive telematics reports into smaller, question-specific data subsets. By breaking down the data retrieval process into targeted queries based on natural language questions, the system retrieves only the relevant portion of data needed for each specific insight, reducing overall review time while maintaining data completeness for each query.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If comprehensive reports of telematics data are retrieved to gain insights about vehicle fleet, then data completeness is improved, but storage space requirements increase

Engineering Contradiction:
Improvedata completenessVSAvoidstorage space
Core Design Contradiction:
Loss of informationVSVolume of stationary object

Solution Approach 1:

The system extracts only the specific telematics data points that are relevant to the user's natural language question, rather than retrieving entire comprehensive reports. This selective extraction reduces storage requirements by avoiding retrieval of unnecessary data while maintaining completeness for the specific inquiry.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If natural language processing is implemented for telematics data retrieval, then ease of operation is improved, but system complexity increases

Engineering Contradiction:
Improvedata retrieval easeVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces a query generation model as an intermediary between the user's natural language question and the database query execution. This intermediary translates human language into structured SQL queries automatically, improving ease of operation for non-technical users while managing system complexity through a specialized translation layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables users to perform data retrieval themselves using natural language without requiring technical expertise in SQL or data querying. The automated query generation allows users to serve their own information needs directly, improving ease of operation while the backend handles the complexity of query translation and execution.

Inventive Principle:
Principle #25Self-service

4Productivity

If natural language processing is implemented for telematics data retrieval, then productivity is improved, but device complexity increases

Engineering Contradiction:
Improvedata retrieval efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The query generation model acts as an intermediary that automatically translates natural language questions into executable SQL queries, significantly improving productivity by eliminating manual query writing. The system manages the added complexity through a dedicated translation layer that handles the conversion process.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces the mechanical process of manual SQL query writing and execution with an automated natural language processing system. This substitution improves productivity by allowing users to query data using everyday language, while the system automatically handles the complexity of translating and executing the appropriate database queries.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12481649B2Systems and methods for retrieving telematics data
Publication Date: 2025.11.25 GEOTAB INC
  • US12481649B2 patent drawing
  • US12481649B2 patent drawing
  • US12481649B2 patent drawing

AI summary

The present disclosure relates to systems and methods for retrieving telematics data. A method for retrieving telematics data may comprise operating at least one processor to: provide a plurality of databases, each database storing at least telematics data originating from a plurality of telematics devices installed in a plurality of vehicles; receive a natural language request from a user; generate, using a large language model (LLM) that does not have access to the plurality of databases, an executable query for retrieving a portion of the telematics data that is responsive to the natural language request from the database by inputting into the LLM at least: a contextual prompt, and the natural language request; execute the executable query; and return at least the portion of the telematics data to the user.