Vehicle Middleware Installation Supervisor for Secure Component Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle bus protocols are inadequate for non-safety communications due to low bandwidth and transmission speed, limiting information flow, data security, and remote access while maintaining security against unauthorized parties.
Innovation Solution
A vehicle middleware system that includes a microprocessor executable installation supervisor to determine if a computational component meets requirements and bind it to the vehicle, restricting communication with other vehicles, and a network architecture enabling interoperability, data sharing, and secure remote access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If existing vehicle bus protocols are used, then device compatibility is maintained, but data transmission speed and bandwidth are limited
Solution Approach 1:
The patent introduces a gateway device as an intermediary between the existing vehicle bus protocol and modern high-speed communication protocols. The gateway translates and forwards data packets between protocols, enabling fast data transmission while maintaining compatibility with legacy vehicle systems. This resolves the contradiction by mediating between the old protocol constraints and new speed requirements.
Solution Approach 2:
The communication system is segmented into multiple protocol layers, with different protocols used for different communication needs. Critical safety data uses high-speed protocols where available, while non-critical data maintains compatibility with traditional bus protocols. This segmentation allows the system to achieve high transmission speeds for important data without sacrificing overall protocol compatibility.
2Adaptability or versatility
If computational components are installed in vehicles, then functionality is enhanced, but security risks from unauthorized access increase
Solution Approach 1:
The patent implements preliminary binding of computational components to specific vehicles during the installation process. The gateway device creates binding records that permanently associate each component with its authorized vehicle identifier. This preliminary security measure prevents unauthorized components from accessing the vehicle network, thereby maintaining reliability while allowing functional enhancement.
Solution Approach 2:
The system continuously monitors communication requests and verifies component bindings before allowing data transmission. The gateway device checks each data packet against the binding records, providing real-time feedback by blocking unauthorized access attempts. This feedback mechanism ensures security while permitting legitimate functional expansions.
3Adaptability or versatility
If data sharing between vehicles is enabled, then interoperability is improved, but data security and privacy protection become more difficult
Solution Approach 1:
The patent implements selective data sharing where different types of data are handled differently based on their sensitivity. Non-sensitive operational data is shared freely to improve interoperability, while sensitive personal or security-critical data remains protected and bound to specific vehicles. This local quality approach allows interoperability benefits without exposing the system to security risks.
Solution Approach 2:
The gateway device serves as an intermediary that filters and controls data sharing between vehicles. It anonymizes and aggregates data before transmission, removing personally identifiable information while preserving useful operational patterns. This intermediary function enables interoperability through data sharing while protecting security and privacy through automated filtering.
Data Source
AI summary
The present disclosure describes a microprocessor executable installation supervisor operable to determine, for a selected computational component to be installed in the vehicle, whether the selected computational component satisfies a requirement and/or restriction associated with the selected computational component, when installed, and, when the selected computational component can satisfy the requirement and/or restriction, create a set of data structures in the selected computational component and/or a computer readable medium on board the vehicle to bind the selected computational component to the vehicle.


