Vehicle Application Pre-installation Using User Weight Values
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing vehicle software management systems face inefficiencies due to the need for frequent OTA updates and data transmission overhead when different users access a vehicle, as each user's preferred applications differ, leading to increased server processing load and storage challenges.
Innovation Solution
A vehicle software management system that predicts and pre-installs applications based on usage history using weight values for each application, allowing for user-specific and group application matrices to determine the most frequently used apps, reducing the need for frequent updates and optimizing storage and transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If all available vehicle applications are installed in the vehicle, then application availability is improved, but storage capacity is exceeded
Solution Approach 1:
The system performs preliminary actions by pre-installing applications that are predicted to be needed before the user actually requests them. The server analyzes user profiles, usage patterns, and application dependencies in advance, then proactively downloads and installs these applications to the vehicle, eliminating the need for users to manually select and download applications during their journey.
2Adaptability or versatility
If user-specific applications are downloaded via OTA update each time a different user uses the vehicle, then application customization is improved, but data transmission overhead increases
Solution Approach 1:
The system performs preliminary actions by pre-installing applications that are predicted to be needed before the user actually requests them. The server analyzes user profiles, usage patterns, and application dependencies in advance, then proactively downloads and installs these applications to the vehicle, eliminating the need for users to manually select and download applications during their journey.
Solution Approach 2:
The system creates simplified copies of user profiles and application preferences that can be quickly transmitted and applied. Instead of transferring complete application packages repeatedly, the server transmits compact user profile data containing application preferences and usage patterns, which then triggers selective application installation, significantly reducing data transmission overhead.
3Adaptability or versatility
If user-specific applications are downloaded via OTA update each time a different user uses the vehicle, then application customization is improved, but installation time increases
Solution Approach 1:
The system performs preliminary actions by pre-installing applications that are predicted to be needed before the user actually requests them. The server analyzes user profiles, usage patterns, and application dependencies in advance, then proactively downloads and installs these applications to the vehicle, eliminating the need for users to manually select and download applications during their journey.
4Ease of operation
If server stores all software configuration information for each user, then application management is improved, but server processing load increases
Solution Approach 1:
The system segments the application management functionality by distributing processing tasks between the server and the vehicle. The server handles high-level user profile management and application selection logic, while the vehicle's onboard system handles application installation and execution. This segmentation reduces the server's processing load by delegating routine installation tasks to the vehicle's local system.
Data Source
AI summary
An apparatus and system for vehicle application management. The apparatus includes: at least one storage storing instructions; and at least one processor configured to execute the instructions to perform operations including: obtaining information identifying a first plurality of vehicle applications selected by a user of the vehicle and determining, for the user, a user-specific application matrix comprising first weight values. Each one of the first weight values is for a respective one of the first plurality of vehicle applications, and each one of the first weight values is determined based on at least a frequency of use, by the user, of the respective one of the first plurality of vehicle applications. The operations also include controlling, using the determined user-specific application matrix, downloading and installation, at the vehicle, of at least one of the first plurality of vehicle applications that is not currently installed in the vehicle.


