Vehicle OTA Cloud Architecture for Precise Fleet Software Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional over-the-air (OTA) systems for vehicles face scalability issues, lack flexibility, imprecise data management, and security vulnerabilities, leading to inefficiencies and extended downtime when updating a fleet of vehicles.
Innovation Solution
A microservices architecture with dedicated OTA operations, utilizing a unique database management system and granular functionalities within each service, reduces inter-service communication, enabling precise targeting and efficient software updates across a fleet of vehicles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional OTA systems are used to manage fleet updates, then the system can perform software updates, but scalability and reliability deteriorate due to imprecise data management
Solution Approach 1:
The system divides the OTA update platform into independent microservices (upload service, deployment service, vehicle service, file server) that can be scaled and managed separately. Each microservice handles specific functionality with dedicated compute resources, improving reliability while reducing overall system complexity through modular architecture.
Solution Approach 2:
A database is introduced as an intermediary component to manage the association between packaged computer programs and vehicle identification numbers. This centralized data storage resolves the scalability issue by providing structured data management that enables precise targeting and tracking of updates across the fleet.
2Loss of time
If traditional OTA systems upload and manage software packages, then updates can be deployed, but downtime increases due to lack of precise targeting
Solution Approach 1:
The deployment service enables selective targeting of specific vehicles or vehicle groups based on their identification numbers stored in the database. This allows update campaigns to be customized for specific segments of the fleet, minimizing downtime by updating only affected vehicles rather than the entire fleet simultaneously.
Solution Approach 2:
The system stores pre-signed single-use URLs for uploaded packages in the database before deployment. When a vehicle requests an update, the system retrieves the pre-prepared package and URL, allowing the vehicle to download and install updates without requiring real-time package generation, thus reducing downtime.
3Adaptability or versatility
If a monolithic OTA system is used, then the system structure is simple, but flexibility and adaptability deteriorate
Solution Approach 1:
The OTA update system is segmented into independent microservices that can be developed, deployed, and scaled separately. The upload service handles package uploads, the deployment service manages update campaigns, the vehicle service communicates with vehicles, and the file server stores packages. This modular architecture provides flexibility and adaptability while managing complexity through standardization.
Solution Approach 2:
The microservices architecture creates a universal platform where each service can serve multiple purposes. For example, the database serves multiple microservices for data storage and retrieval, and the pre-signed URL mechanism provides both security and access control across all services, reducing overall system complexity.
4Reliability
If extensive data is stored and managed in traditional OTA systems, then update tracking is possible, but security vulnerabilities increase
Solution Approach 1:
The database acts as a secure intermediary that stores sensitive data (package IDs, vehicle VINs, update status) in a centralized and controlled environment. This allows proper authentication and authorization mechanisms to be implemented, reducing security vulnerabilities while maintaining accurate update tracking.
Solution Approach 2:
The system uses pre-signed single-use URLs as secure copies of access information. These URLs contain encoded authentication data that expires after use, allowing the system to track and manage updates without storing sensitive authentication information in plain text, thus improving security while maintaining tracking accuracy.
Data Source
AI summary
In one aspect, a system for supporting over-the-air (OTA) software updates is configured to transmit, over a network, an upload network address for the uploading a packaged computer program, in response to receiving a first request. The system stores an association between the packaged computer program and a UUID. In response to receiving a second request that includes one or more VINs associated with respective one or more vehicles targeted to update software to a specified UUID, the system stores records that associate the one or more VINs with the specified UUID. In response to receiving a third request from a control unit of the vehicle, the system transmits a download network address for the vehicle to use to download the packaged computer program from the file server, when it is determined that the vehicle is associated with one VINs stored in the database.