Vehicle Software Deployment via Segmented Data Chunks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The deployment of vehicle software applications in modern vehicles is complicated by the presence of multiple electronic control units (ECUs) with varying configurations and dependencies, which requires a specific sequence and optimal resource allocation, and is further hindered by the size of the software and communication format limitations.
Innovation Solution
A vehicle software deployment management system that sends signed serialized data chunks of the software application and generates deployment plans dynamically based on vehicle data, using a protocol-agnostic transmission format to ensure efficient and optimal deployment across various ECUs, with an in-vehicle application deployment planner orchestrating the deployment according to the plan.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If vehicle software application is deployed to multiple ECUs with varying configurations, then software compatibility and reliability are improved, but deployment complexity increases
Solution Approach 1:
The patent segments the software application into multiple packages, each tailored for specific ECU configurations. The deployment system divides the overall deployment task into smaller sub-tasks, assigning appropriate software packages to different ECUs based on their configurations, thereby managing complexity while ensuring compatibility
Solution Approach 2:
The patent implements dynamic deployment planning that adapts to real-time ECU configuration data. The system dynamically generates deployment plans based on received ECU configurations, selecting appropriate software packages for each ECU, which allows the system to handle varying configurations without fixed complex pre-programming
2Adaptability or versatility
If software application size is increased to include more features, then functionality is improved, but transmission time and communication bandwidth are worsened
Solution Approach 1:
The patent divides large software applications into smaller packages that can be transmitted separately. Each package contains only the necessary components for specific ECU configurations, reducing individual transmission sizes while maintaining overall functionality across the vehicle system
Solution Approach 2:
The system transmits only the necessary portions of software packages required for each specific ECU configuration rather than transmitting complete software suites to all ECUs. This partial transmission approach reduces communication bandwidth consumption and transmission time while delivering sufficient functionality
3Reliability
If communication format restrictions are applied to ensure protocol compatibility, then communication reliability is improved, but transmission speed and flexibility are reduced
Solution Approach 1:
The patent employs a universal communication framework that can handle multiple data formats and protocols. The system processes software packages and ECU configuration data through a unified interface that adapts to different communication requirements, maintaining reliability through standardized validation while enabling flexible and efficient data exchange
4Reliability
If deployment sequence is strictly controlled to ensure correct installation order, then deployment reliability is improved, but deployment time increases
Solution Approach 1:
The patent performs preliminary analysis of ECU configurations and software package dependencies before deployment. The system pre-determines the optimal deployment sequence based on configuration matching and dependency relationships, allowing for efficient execution without time-consuming runtime decisions while ensuring correct installation order
Data Source
AI summary
A system comprising one or more computing devices implements a vehicle software deployment management system. The vehicle software deployment management system enables clients to send signed serialized data chunks of a vehicle software application and a deployment plan for the software application to vehicles using a protocol agnostic transmission format. The vehicle software deployment management system may generate a deployment plan that may be processed by an in-vehicle application deployment planner/orchestrator of the vehicle to deploy the particular vehicle software application. The vehicle software deployment management system may send the vehicle software application using containers to be used by ECU agents of various ECUs of the vehicle. Furthermore, the vehicle software deployment management system may utilize received vehicle information to dynamically generate one or more updated vehicle deployment plans to send to respective vehicles.