Connected Vehicle Authentication Using Visible Codes and BLE
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional smartkey-free connected vehicle systems using BLE communication face security vulnerabilities due to short communication distances and the risk of unauthorized access, particularly when sharing remote control authority across multiple smartphones, which requires additional security measures and infrastructure like central servers for registration and management.
Innovation Solution
A system and method for connected vehicle control that employs a communication unit, head unit, and controller to generate authentication information combining user terminal and vehicle information, using visible codes and authentication keys, allowing secure registration and remote control without a central server, with features like master and guest terminal categorization and limited authority settings, enhancing security through unique terminal identification and temporal authentication keys.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If BLE communication is used for smartkey-free system, then convenience is improved, but security deteriorates
Solution Approach 1:
The authentication process is segmented into multiple independent stages: initial connection authentication, visible code verification, and registration authentication. Each stage performs a specific security function, preventing any single point of failure and maintaining security while preserving BLE convenience.
Solution Approach 2:
A visible code serves as an intermediary authentication element between the user terminal and the vehicle system. The visible code is generated by the vehicle and verified by the user terminal, acting as a secure mediator that prevents direct unauthorized access while maintaining the convenience of smartphone-based control.
2Reliability
If a separate central server is deployed for security management, then security is improved, but system complexity increases
Solution Approach 1:
The vehicle system performs authentication and registration functions autonomously without requiring a separate central server. The vehicle generates visible codes, verifies user terminal information, and manages authentication keys independently, eliminating the need for external server infrastructure while maintaining security.
Solution Approach 2:
The vehicle's existing communication unit and controller are extended to perform multiple functions including authentication, registration, and security management. This multi-functional approach eliminates the need for dedicated server infrastructure, reducing system complexity while maintaining security capabilities.
3Reliability
If authentication information is transmitted through visible code, then security is improved, but communication time increases
Solution Approach 1:
The vehicle generates and displays the visible code in advance before the user terminal needs to authenticate. This preliminary action allows the user terminal to capture and verify the code without time pressure, maintaining security while minimizing communication time overhead.
Data Source
AI summary
A system for connected vehicle control may include a communicator configured to connect with a user terminal though wireless communication, and generate authentication information by combining user terminal information and vehicle information, a head unit having a password for operation and configured to generate a visible code by converting the authentication information, a body controller configured to control the vehicle according to a remote control signal sent according to a remote control function of a user application installed in the user terminal, and a controller configured to connect the communicator, the head unit, and the user application through the wireless communication, authenticate, and register.