Virtual Vehicle Telematics API for Third-Party Service Testing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional telematics services face limitations in connecting third-party services with actual vehicles before release, lack of means for third-party developers to test services, security issues due to open specifications, and difficulties in providing services to multiple users due to inadequate vehicle access control and user management.
Innovation Solution
A method utilizing a virtual vehicle ID and telematics server to create a token ID for third-party service-providing systems, allowing simulation of virtual vehicles and actual vehicle control through a telematics API, enabling testing and verification of services without exposing actual vehicle specifications and supporting multiple user access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If third-party services are connected with actual vehicles before release, then service verification is enabled, but security is compromised due to specification exposure
Solution Approach 1:
The patent creates a virtual vehicle that is a copy of the actual vehicle, allowing third-party services to be tested and verified on the virtual vehicle before deployment to the actual vehicle. This copying approach enables service verification without exposing the actual vehicle's specifications, as the virtual vehicle serves as a safe testbed that replicates the necessary functionality.
Solution Approach 2:
The virtual vehicle acts as an intermediary between the third-party service development environment and the actual vehicle. It mediates the testing process by providing a simulated environment that allows service verification while preventing direct access to the actual vehicle's specifications, thus maintaining security.
2Adaptability or versatility
If telematics service specifications are opened up for third-party linking, then service integration is improved, but security issues arise
Solution Approach 1:
Instead of opening up the actual vehicle's telematics specifications, the patent creates a virtual vehicle that replicates the necessary interfaces and functionalities. Third-party services can integrate with the virtual vehicle's copied specifications, achieving service integration without exposing the actual vehicle's security-critical specifications.
3Ease of manufacture
If virtual vehicle simulation is implemented, then service testing is enabled, but system complexity increases
Solution Approach 1:
The virtual vehicle is created as a simplified copy of the actual vehicle, replicating only the necessary telematics functionalities required for third-party service testing. This selective copying approach enables service testing while minimizing the added system complexity by including only essential simulated components.
4Adaptability or versatility
If multiple users are supported through third-party services, then service accessibility is improved, but access control management becomes difficult
Solution Approach 1:
The virtual vehicle serves as an intermediary that manages multiple user accesses to third-party services. It implements access control mechanisms that allow multiple users to interact with the simulated vehicle environment without requiring complex direct access control to the actual vehicle, thus improving service accessibility while simplifying access control management.
Data Source
AI summary
A method for providing a telematics service by using a virtual vehicle is provided. The method includes steps of: (a) a telematics server, if a request for registering the vehicle is acquired from a third-party system linked with the telematics service, creating a vehicle ID, and providing a telematics API to the third-party system; (b) the telematics server, if a request is received from the third-party system, creating a token ID corresponding to the system by referring to information on the system and the vehicle ID, and then transmitting it to the system; and (c) the telematics server, if a telematics service request using the token ID is transmitted from the system through the telematics API, confirming the vehicle ID corresponding to the token ID, simulating the virtual vehicle in response to the service request, and transmitting the simulation result to the third-party system.