Vehicle Control SDK Encapsulation for Secure Open Platform Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle open platforms face significant information security risks as outside developers can crack the control protocol by converting it through a security gateway, making joint development challenging and insecure.
Innovation Solution
A vehicle security control method using a software development kit (SDK) that encapsulates the control protocol, providing an API function interface to convert call requests into control signals, which are then transmitted through a bus to a security gateway for protocol conversion, ensuring the control protocol remains confidential and enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the control protocol is converted through a security gateway, then outside developers can implement their own development control, but the control protocol information security is compromised and can be cracked
Solution Approach 1:
The system segments the protocol conversion function into two independent parts: the security gateway performs protocol format conversion, while the SDK performs protocol encapsulation and security protection. This segmentation allows outside developers to access converted protocols through the SDK without exposing the original control protocol, thus maintaining security while enabling joint development.
Solution Approach 2:
The SDK acts as an intermediary layer between the security gateway and outside developers. It receives the converted protocol from the security gateway, encapsulates it with security protection, and provides it to outside developers through API interfaces. This intermediary mechanism enables developers to access vehicle control functions without directly exposing the original control protocol.
2Reliability
If the control protocol is kept confidential, then information security is maintained, but outside developers cannot perform joint development
Solution Approach 1:
The system creates a secure copy of the control protocol functionality through the SDK. Instead of exposing the original control protocol, the SDK generates an encapsulated version that provides the same control capabilities to outside developers while maintaining the security and confidentiality of the original protocol through API interfaces.
3Ease of operation
If the security gateway converts the protocol for outside developers, then development control is enabled, but the converted protocol is not conducive to joint development
Solution Approach 1:
The SDK changes the interface parameters and communication protocol from the internal vehicle protocol to a standardized API interface format. This parameter transformation enables outside developers to access vehicle control functions through familiar API calling conventions, making the system more suitable for joint development while the underlying control protocol remains protected.
Data Source
Figure 1~3
Figure 4~5
Figure 6~7
AI summary
This application discloses a vehicle and a vehicle security control method and system based on an open platform. The open platform includes a software development kit in which a control protocol is encapsulated, the software development kit provides an API function interface, and the method includes the following steps: receiving a call request from a third-party device for a target API function interface of the open platform; converting the call request by using the software development kit to generate a control signal that meets a requirement of the control protocol and that is used for controlling a first vehicle component in a vehicle; and transmitting the control signal to a security gateway through a first bus, to enable the security gateway to perform protocol conversion on the control signal, and transmitting the control signal to an in-vehicle network to control the first vehicle component in the vehicle.