Vehicle software upgrading method, electronic equipment and vehicle

Abstract

The embodiment of the invention provides a vehicle software upgrading method, electronic equipment and a vehicle, and relates to the technical field of Internet of Vehicles. The vehicle software upgrading method is applied to a server, and the vehicle software upgrading method comprises the steps that an upgrading demand portrait is generated according to historical operation data corresponding to a target vehicle, and the upgrading demand portrait is used for describing upgrading demands of the target vehicle from multiple dimensions; according to the upgrading demand portrait, at least one to-be-upgraded target software package is determined from a software pool corresponding to the target vehicle, and the software pool comprises a plurality of upgradable software packages corresponding to software and hardware configuration of the target vehicle; and sending the target upgrading task to the target vehicle based on the target software package, so that the target vehicle executes vehicle software upgrading on the target software package. The technical problem that the user experience is affected due to the fact that vehicle software upgrading is lack of personalization in the related technology is solved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of Internet of Vehicles, and in particular to a vehicle software upgrading method, an electronic device and a vehicle. BACKGROUND

[0002] Vehicle OTA (Over-the-Air) upgrading technology aims to realize remote updating and optimization of vehicle software through wireless communication technology, so as to improve vehicle performance and user experience.

[0003] However, in the traditional OTA upgrading practice, the upgrading strategy often follows a unified standard, lacks consideration of user individualized needs and vehicle specific situations, and pushes irrelevant or low-priority software packages, resulting in inconsistency between the upgrading content and the actual needs of users, thereby affecting user experience. Therefore, how to realize individualized upgrading of vehicle software and further improve user experience is one of the important technical problems in the related technical field.

[0004] At present, no effective solution has been proposed for the above problems. SUMMARY

[0005] Embodiments of the present application provide a vehicle software upgrading method, an electronic device and a vehicle, aiming to solve the technical problem of lack of individualization in vehicle software upgrading in related technologies, thereby affecting user experience.

[0006] According to an aspect of an embodiment of the present application, a vehicle software upgrading method is provided, the vehicle software upgrading method being applied to a server, and the vehicle software upgrading method comprising: generating an upgrading demand portrait according to historical running data corresponding to a target vehicle, wherein the upgrading demand portrait is used to describe the upgrading demand of the target vehicle from multiple dimensions; determining at least one target software package to be upgraded from a software pool corresponding to the target vehicle according to the upgrading demand portrait, wherein the software pool comprises a plurality of upgradable software packages corresponding to the hardware and software configuration of the target vehicle; and sending a target upgrading task to the target vehicle based on the target software package, so that the target vehicle performs vehicle software upgrading on the target software package.

[0007] The vehicle software upgrading method provided by the embodiments of the present application achieves the following technical effects: first, the present application generates an upgrading demand portrait according to the personalized historical running data of the target vehicle. The portrait can comprehensively describe the upgrading demand of the target vehicle from multiple dimensions, ensuring that the subsequent software package pushing is more in line with user demand and avoiding unnecessary upgrades. Second, according to the upgrading demand portrait, a software package that is adapted to the user demand is selected from the software pool of the target vehicle as the target software package. Further, based on the target software package, the server sends a personalized target upgrading task to the target vehicle, so that the target vehicle can perform vehicle software upgrading based on the personalized demand of the user, and the upgrading content is highly matched with the user demand. Therefore, the embodiments of the present application can realize vehicle software personalized upgrading, thereby improving the user experience, and solve the technical problem that the vehicle software upgrading lacks personalization in the related art, thereby affecting the user experience.

[0008] Optionally, according to the historical running data corresponding to the target vehicle, the upgrading demand portrait is generated, including: preprocessing the historical running data to obtain preprocessed data; performing feature extraction on the preprocessed data according to a preset extraction dimension to obtain a feature matrix, wherein the preset extraction dimension includes a driving style dimension, a function preference dimension, a scene adaptation dimension, and a safety demand dimension; performing feature mapping on a plurality of features contained in the feature matrix according to a preset feature demand mapping rule to obtain a plurality of feature demand labels; determining a plurality of label weights corresponding to the plurality of feature demand labels according to a preset weight determination algorithm, wherein the plurality of feature demand labels and the plurality of label weights are one-to-one corresponding; sorting the plurality of feature demand labels according to the plurality of label weights to obtain a demand sorting result; and generating the upgrading demand portrait according to the demand sorting result.

[0009] The above optional embodiments of the present application can achieve the following technical effects: first, the historical operation data of the target vehicle is preprocessed, and this preprocessing process ensures the accuracy of data analysis, avoids portrait deviation caused by data quality problems, and improves the reliability and effectiveness of subsequent analysis. Then, according to the preset extraction dimension, the feature extraction is performed on the preprocessed data to form a feature matrix, and these dimensions include driving style, function preference, scene adaptation and safety demand, which can comprehensively depict the use characteristics and user demand of the vehicle from multiple angles. Compared with single-dimensional analysis, the multi-dimensional feature matrix provides more rich and comprehensive information, which helps to generate more accurate upgrade demand portrait. Then, according to the preset feature demand mapping rule, the multiple features contained in the feature matrix are mapped to obtain multiple feature demand labels, which enables the server to intuitively identify the user demand represented by each feature. According to the preset weight determination algorithm, the multiple label weights corresponding to the multiple feature demand labels are determined. By introducing the concept of weight, different weights are given to different demand labels, so as to highlight those more urgent and important upgrade demands. The introduction of label weight makes the construction of portrait more hierarchical and targeted, and improves the guiding value of the portrait. Further, according to the multiple label weights, the multiple feature demand labels are sorted to obtain a demand sorting result, which ensures that the upgrade demands with higher weights are preferentially met under limited upgrade resources, thereby improving the efficiency and satisfaction of the upgrade strategy. Finally, according to the demand sorting result, an upgrade demand portrait is generated, and the server can accurately select a software package that meets the individual needs of the target vehicle from the software pool according to the upgrade demand portrait, and realize accurate pushing.

[0010] Optionally, according to the upgrade demand portrait, at least one target software package to be upgraded is determined from the software pool corresponding to the target vehicle, comprising: according to the upgrade demand portrait, a plurality of initial upgrade software packages are selected from the software pool; and at least one target software package is determined from the plurality of initial upgrade software packages by using a preset screening rule.

[0011] The above optional embodiments of the present application can achieve the following technical effects: first, according to the upgrade demand portrait, a plurality of initial upgrade software packages are selected from the software pool, which preliminarily filters out software packages that are not related to the target vehicle or have low demand matching degree, greatly improving the efficiency and accuracy of the upgrade package selection, avoiding the interference of irrelevant upgrade information to the user, and improving the user experience. Secondly, at least one target software package is further determined from the plurality of initial upgrade software packages by using a preset screening rule, which is usually based on the priority of each demand label in the individual demand portrait, to ensure that the selected software package meets the individual upgrade demand of the user to the greatest extent while ensuring the efficiency of the upgrade.

[0012] According to another aspect of the embodiments of the present application, a vehicle software upgrading method is also provided. The vehicle software upgrading method is applied to a target vehicle. The vehicle software upgrading method comprises: sending historical running data of the target vehicle to a server; receiving a target upgrading task issued by the server, wherein the target upgrading task is generated by the server based on at least one target software package to be upgraded, the target software package is determined from a software pool corresponding to the target vehicle according to an upgrading demand portrait, the upgrading demand portrait is generated according to the historical running data, the software pool comprises a plurality of upgradeable software packages corresponding to the hardware and software configuration of the target vehicle, and the upgrading demand portrait is used to describe the upgrading demand of the target vehicle from multiple dimensions; and performing vehicle software upgrading on the target software package according to the target upgrading task.

[0013] The vehicle software upgrading method provided by the embodiments of the present application achieves the following technical effects: first, the historical running data of the target vehicle is sent to the server, which enables the server to generate a personalized target upgrading task based on the historical running data. Then, the target upgrading task issued by the server is received, and vehicle software upgrading is performed on the target software package according to the target upgrading task. The target vehicle can perform vehicle software upgrading based on the personalized demand of the user, thereby achieving high matching between the upgrading content and the user demand. Thus, the embodiments of the present application can achieve vehicle software personalized upgrading, thereby improving the user experience, and solve the technical problem in the related art that vehicle software upgrading lacks personalization and thus affects the user experience.

[0014] Optionally, performing vehicle software upgrading on the target software package according to the target upgrading task comprises: task scheduling on the target upgrading task to generate an upgrading sequence list, wherein the upgrading sequence list is used to determine the execution order of the target upgrading task; determining a plurality of alternative upgrading time periods in a preset time period based on the historical vehicle use time data of the user of the target vehicle and the estimated time consumption of the target upgrading task, to form an alternative upgrading time period list; displaying the upgrading sequence list and the alternative upgrading time period list as display content on a vehicle-side display interface, and performing vehicle software upgrading on the target software package according to the decision information of the user on the display content.

[0015] The optional embodiments described above achieve the following technical effects: First, the target upgrade task is orchestrated to generate an upgrade sequence list, avoiding confusion in the subsequent upgrade order. Simultaneously, based on the target vehicle's historical user usage time data and the estimated time of the target upgrade task, multiple alternative upgrade time slots within a preset time period are determined, forming an alternative upgrade time slot list. This step fully considers the user's usage time, ensuring that the upgrade operation is performed during the user's most convenient time, greatly enhancing user satisfaction. Finally, the upgrade sequence list and the alternative upgrade time slot list are displayed on the vehicle's display interface, and the vehicle software upgrade is executed based on the user's decision information regarding the displayed content. This interactive design empowers the user with autonomy in upgrade decisions, making the entire upgrade process more user-friendly, while also ensuring that the user has full understanding and control over the upgrade content and time, thereby improving the upgrade success rate and user acceptance.

[0016] Optionally, the target upgrade task includes multiple target software packages. The target upgrade task is orchestrated to generate an upgrade order list, including: determining the degree of impact of multiple vehicle use corresponding to multiple target software packages; sorting the multiple target software packages in descending order according to the degree of impact of multiple vehicle use to obtain the software package sorting result; and generating an upgrade order list according to the software package sorting result.

[0017] The above-described optional embodiments of this application achieve the following technical effects: First, by evaluating the impact of multiple vehicle usage scenarios on multiple target software packages, refined management of target upgrade tasks is achieved. Second, based on the impact of multiple vehicle usage scenarios, the multiple target software packages are sorted in descending order, further refining the priority of the multiple target software packages, so that target software packages with a high impact on vehicle usage can be processed first within a limited time. Finally, an upgrade order list is generated based on the software package sorting results. This list clearly guides the vehicle onboarding on how to execute upgrade tasks in an orderly manner, especially when there are many software packages, avoiding resource waste and user experience degradation caused by random upgrades.

[0018] Optionally, based on the user's historical vehicle usage time data of the target vehicle and the estimated time of the target upgrade task, multiple alternative upgrade time periods within a preset time period are determined, including: predicting multiple potential idle time periods of the target vehicle within the preset time period based on the user's historical vehicle usage time data; and selecting multiple alternative upgrade time periods from the multiple potential idle time periods based on the estimated time of the target upgrade task and preset time period filtering rules.

[0019] The above-mentioned optional embodiments of this application can achieve the following technical effects: First, by collecting and analyzing the user's historical vehicle usage time data for the target vehicle, the potential idle time periods of the user within a preset time period are predicted, so as to avoid the upgrade process from conflicting with the user's vehicle usage needs, reduce the interference of the upgrade on the user's daily vehicle use, and improve user satisfaction. Second, by combining the estimated time consumption of the target upgrade task and the preset time period filtering rules, multiple alternative upgrade time periods are selected from the predicted potential idle time periods, so as to ensure that the target upgrade task can be completed during the user's non-use time periods, avoiding possible emergency vehicle usage needs during the upgrade process, and further improving the user experience.

[0020] Optionally, the vehicle software upgrade method further includes: in response to starting the vehicle software upgrade, determining upgrade prompt information based on the upgrade progress of multiple target software packages and the degree of impact on multiple vehicle uses, and displaying the upgrade prompt information through the vehicle-side display interface; in response to a vehicle use request, determining an upgrade strategy based on the upgrade prompt information, wherein the upgrade strategy is used to determine whether to continue the current vehicle software upgrade.

[0021] The above-described optional embodiments of this application achieve the following technical effects: During the vehicle software upgrade process, upgrade prompts are determined based on the upgrade progress of multiple target software packages and the degree of impact on vehicle use. These prompts are then displayed on the vehicle's display interface, allowing users to clearly understand the current vehicle status and make informed decisions about whether to use the vehicle. When a vehicle use request occurs, the system determines whether to continue the current vehicle software upgrade based on the upgrade prompts, reducing user confusion caused by information asymmetry.

[0022] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to execute the program stored in the memory to implement the vehicle software upgrade method of any of the above.

[0023] The electronic device provided in this application embodiment achieves the following technical effects: the computer program corresponding to the vehicle software upgrade method in any of the above is stored in the memory, and the processor executes the computer program stored in the memory to realize the personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that the lack of personalization in vehicle software upgrades affects the user experience.

[0024] According to another aspect of the embodiments of this application, a vehicle is also provided, the vehicle including an on-board memory and an on-board processor, wherein the on-board memory is used to store computer programs; the on-board processor is used to execute the computer programs stored on the on-board memory to implement the vehicle software upgrade method applied to the target vehicle as described in any of the above.

[0025] The vehicle provided in this application embodiment achieves the following technical effects: the computer program corresponding to the vehicle software upgrade method in any of the above is stored in the vehicle memory, and the computer program stored in the vehicle memory is executed by the vehicle processor to realize the personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that the lack of personalization in vehicle software upgrades affects the user experience.

[0026] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the vehicle software upgrade method described in any of the above embodiments when run on a computer or processor.

[0027] The computer-readable storage medium provided in this application embodiment achieves the following technical effects: it stores the computer program corresponding to the vehicle software upgrade method in any of the above into the computer-readable storage medium, and uses the processor to execute the computer program stored in the computer-readable storage medium to achieve personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that vehicle software upgrades lack personalization, thus affecting the user experience. Attached Figure Description

[0028] Figure 1 This is a flowchart of a vehicle software upgrade method provided in an embodiment of this application;

[0029] Figure 2 This is a flowchart of another vehicle software upgrade method provided in an embodiment of this application;

[0030] Figure 3 This is a flowchart illustrating a vehicle software upgrade method provided in an embodiment of this application. Detailed Implementation

[0031] To make the technical problems, technical solutions, and beneficial effects solved by this application clearer, the following detailed description is provided in conjunction with embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0033] This application provides a vehicle software upgrade method, which is applied to a server. Figure 1 This is a flowchart of a vehicle software upgrade method provided in an embodiment of this application, such as... Figure 1 As shown, the vehicle software upgrade method includes the following steps:

[0034] Step S110: Generate an upgrade requirement profile based on the historical operating data of the target vehicle. The upgrade requirement profile is used to describe the upgrade requirements of the target vehicle from multiple dimensions.

[0035] Step S120: Based on the upgrade requirement profile, determine at least one target software package to be upgraded from the software pool corresponding to the target vehicle, wherein the software pool includes multiple upgradeable software packages corresponding to the hardware and software configuration of the target vehicle.

[0036] Step S130: Based on the target software package, send a target upgrade task to the target vehicle so that the target vehicle can perform a vehicle software upgrade on the target software package.

[0037] The aforementioned historical operating data refers to the recorded data on the operating status of the target vehicle at different points in time, such as navigation system usage data and entertainment system preference settings data.

[0038] The upgrade requirement profile mentioned above refers to a description of upgrade requirements generated based on the target vehicle's historical operating data. The upgrade requirement profile describes the target vehicle's upgrade needs from multiple dimensions.

[0039] In one optional embodiment, a machine learning algorithm is used to extract features from historical operating data, and based on the extracted features, a profile of the target vehicle's upgrade needs is constructed.

[0040] The aforementioned software pool refers to a collection that stores multiple upgradeable software packages corresponding to the target vehicle. Each upgradeable software package targets different functional modules and includes software version information, update content, compatibility, etc.

[0041] Optionally, based on the hardware and software configuration information of the target vehicle, multiple upgradeable software packages corresponding to the target vehicle are determined from multiple software packages provided by the server.

[0042] The aforementioned target software package refers to the software package selected from the software pool that meets the current requirements of the target vehicle. The target software package is used for vehicle software upgrades.

[0043] In one optional embodiment, based on the upgrade requirement profile, software packages matching the target vehicle's requirements are selected from the software pool as target software packages. There may be one or more target software packages.

[0044] Optionally, vehicle software upgrade refers to vehicle OTA (Over-the-Air) upgrade, which is the process of remotely updating the software or configuration of the vehicle system via a wireless network.

[0045] Optionally, the aforementioned target upgrade task includes at least one target software package, which is used to guide the target vehicle to perform specific software upgrade operations.

[0046] In one optional embodiment, the target upgrade task is sent to the target vehicle via vehicle-to-everything (V2X) technology, ensuring data security and integrity during transmission. Upon receiving the upgrade task, the target vehicle verifies and parses it, then executes the software package upgrade operation according to a preset strategy.

[0047] The vehicle software upgrade method provided in this application achieves the following technical effects: First, this application generates an upgrade requirement profile based on the target vehicle's personalized historical operating data. This profile comprehensively describes the target vehicle's upgrade requirements from multiple dimensions, ensuring that subsequent software package pushes are more aligned with user needs and avoiding unnecessary upgrades. Second, based on the upgrade requirement profile, software packages that match user needs are selected from the target vehicle's software pool as target software packages. Further, based on the target software packages, the server sends a personalized target upgrade task to the target vehicle, enabling the target vehicle to upgrade its software based on the user's personalized needs, achieving a high degree of matching between the upgrade content and user requirements. Therefore, this application embodiment can achieve personalized vehicle software upgrades, thereby improving the user experience and solving the technical problem in related technologies where vehicle software upgrades lack personalization, thus affecting user experience.

[0048] Optionally, an upgrade requirement profile is generated based on the historical operating data of the target vehicle, including the following steps:

[0049] Step S1101: Preprocess the historical running data to obtain preprocessed data;

[0050] Step S1102: Perform feature extraction on the preprocessed data according to the preset extraction dimensions to obtain a feature matrix. The preset extraction dimensions include: driving style dimension, function preference dimension, scenario adaptation dimension, and safety requirement dimension.

[0051] Step S1103: Based on the preset feature requirement mapping rules, perform feature mapping on multiple features contained in the feature matrix to obtain multiple feature requirement labels.

[0052] Step S1104: Based on the preset weight determination algorithm, determine the multiple label weights corresponding to the multiple feature requirement labels, wherein the multiple feature requirement labels and the multiple label weights correspond one-to-one.

[0053] Step S1105: Sort the multiple feature requirement labels according to the multiple label weights to obtain the requirement ranking result;

[0054] Step S1106: Generate an upgrade requirement profile based on the requirement sorting results.

[0055] Optionally, preprocessing is a necessary step before data analysis, aiming to clean and organize the raw data to ensure its quality and applicability. Preprocessing historical data includes denoising (removing outliers), imputing missing values ​​(filling missing data with statistical or predictive methods), and also involves data format conversion and data type standardization to ensure data consistency for subsequent analysis.

[0056] In one alternative embodiment, the driving style dimension considers acceleration behavior, braking frequency, steering angle, etc., reflecting the driver's driving habits and preferences.

[0057] In one alternative embodiment, the feature preference dimension considers the frequency and duration of use of each feature module, such as navigation, entertainment system, and safety assistance system, to understand the degree of user dependence on different features.

[0058] In one optional embodiment, the scenario adaptation dimension considers the climate conditions, traffic conditions, road types, etc. of the target vehicle's location to determine the challenges and needs that the vehicle may encounter in a specific environment.

[0059] In one alternative embodiment, the safety requirements dimension considers vehicle fault records, warning signals, safety system activation status, etc., to assess the vehicle's safety status and potential risks.

[0060] Optionally, the system can statistically analyze the target vehicle's average acceleration, average deceleration, and number of sharp turns over different time periods to create quantitative indicators of driving habits. It can also record the number of times each function is activated and its usage duration, calculating its usage rate and its correlation with other functions. By combining vehicle location and meteorological data, the system can analyze function usage under different weather conditions and the traffic characteristics of specific areas that influence vehicle function needs. Finally, it can collect vehicle malfunction reports, statistically analyze the frequency of safety warnings and the number of times safety systems are activated, and assess the necessity of upgrading the safety systems.

[0061] Feature matrix is ​​obtained by extracting features from the preprocessed data according to the dimensions of driving style, functional preference, scenario adaptation, and safety requirements.

[0062] Optionally, based on the feature matrix, a machine learning or deep learning model can be used to generate a profile describing the vehicle upgrade needs, i.e., an upgrade needs profile.

[0063] The aforementioned feature-demand mapping rules refer to the algorithmic rules that convert features extracted from vehicle data (such as driving style features, functional preference features, etc.) into specific requirements (such as navigation system updates, battery management optimizations, etc.). This conversion process aims to determine the feature-demand labels of the target vehicle to ensure that the upgrade strategy accurately reflects user needs.

[0064] The aforementioned feature matrix contains quantified values ​​of vehicle usage characteristics, such as usage frequency, regional characteristics, and vehicle status.

[0065] The aforementioned feature mapping refers to associating feature values ​​of different dimensions with corresponding upgrade requirements through preset feature requirement mapping rules. For example, a higher frequency of use of driver assistance systems is mapped to the requirement label of "driver assistance system update".

[0066] Optionally, the feature requirement mapping rules are set based on empirical data. For example, vehicles that frequently drive on icy and snowy roads are given priority for the requirement of "winter driving mode optimization".

[0067] In one alternative embodiment, each feature in the feature matrix is ​​matched with a feature requirement mapping rule to generate a corresponding feature requirement label.

[0068] The aforementioned weighting algorithm is used to quantify the importance of different feature requirement tags, so as to prioritize the functions that users care about most when generating upgrade requirement profiles.

[0069] The above tag weights reflect the priority of feature demand tags in the personalized upgrade strategy. The larger the weight value, the higher the priority that demand will be considered for upgrade.

[0070] In one alternative embodiment, a time-series weighting algorithm is used to determine multiple label weights corresponding to multiple feature requirement labels.

[0071] Optionally, a simple sorting algorithm (such as bubble sort or quick sort) can be used to sort the feature requirement labels according to their label weights to obtain the requirement sorting results.

[0072] Furthermore, the results of the demand ranking are displayed in graphical or list form to obtain a profile of the upgrade demand.

[0073] The optional embodiments described above achieve the following technical effects: First, the historical operating data of the target vehicle is preprocessed. This preprocessing process ensures the accuracy of data analysis, avoids profile bias caused by data quality issues, and improves the reliability and effectiveness of subsequent analysis. Next, features are extracted from the preprocessed data according to preset extraction dimensions to form a feature matrix. These dimensions include driving style, functional preferences, scenario adaptation, and safety requirements, comprehensively depicting the vehicle's usage characteristics and user needs from multiple perspectives. Compared to single-dimensional analysis, the multi-dimensional feature matrix provides richer and more comprehensive information, helping to generate a more accurate upgrade requirement profile. Then, based on preset feature requirement mapping rules, multiple features contained in the feature matrix are mapped to obtain multiple feature requirement labels. This process allows the server to intuitively identify the user needs represented by each feature. Based on a preset weight determination algorithm, multiple label weights corresponding to the multiple feature requirement labels are determined. By introducing the concept of weight, different requirement labels are given different levels of importance, thereby highlighting those more urgent and important upgrade needs. The introduction of label weights makes the profile construction more hierarchical and targeted, enhancing the guiding value of the profile. Furthermore, based on multiple tag weights, multiple feature requirement tags are sorted to obtain a requirement ranking result. This ranking process ensures that, with limited upgrade resources, upgrade requirements with higher weights are prioritized, thereby improving the efficiency and satisfaction of the upgrade strategy. Finally, based on the requirement ranking result, an upgrade requirement profile is generated. The server can then accurately select software packages that meet the personalized needs of the target vehicle from the software pool based on the upgrade requirement profile, achieving precise delivery.

[0074] Optionally, the vehicle software upgrade method also includes the following steps:

[0075] Step S1301: Generate a target upgrade list based on the target software package;

[0076] Step S1302: Package the target software package and the target upgrade manifest to generate the target upgrade task.

[0077] Optionally, the aforementioned target upgrade list is a detailed description document of the target software packages, containing key information such as version information, functional descriptions, comparisons of the impact before and after the upgrade, and required storage space for each target software package. Generating the upgrade list involves integrating the metadata and descriptive data of the target software packages into a clear and easy-to-understand list, facilitating comprehension of the specific upgrade content by both the vehicle and the user.

[0078] The encapsulation process described above refers to integrating multiple target software packages and their corresponding target upgrade manifests into a single data packet, forming a complete target upgrade task. This encapsulation process involves not only packaging the data but also adjusting the data structure and generating checksums to ensure the integrity and security of the target upgrade task's data during transmission.

[0079] A checksum is a numerical value used to verify data integrity, typically calculated from data packets using a specific algorithm. The generation and comparison of checksums ensure that data has not been tampered with or corrupted during transmission.

[0080] The above-described optional embodiments of this application achieve the following technical effects: First, the generation of the target upgrade list allows users to clearly understand the content of the upgrade, enhancing user trust and satisfaction. Second, by encapsulating the target software package with the target upgrade list, the generated target upgrade task ensures data consistency and integrity.

[0081] Optionally, based on the upgrade requirement profile, at least one target software package to be upgraded is determined from the software pool corresponding to the target vehicle, including the following steps:

[0082] Step S1201: Based on the upgrade requirement profile, select multiple initial upgrade packages from the software pool;

[0083] Step S1202: Using preset filtering rules, at least one target package is determined from multiple initial upgrade packages.

[0084] In one optional embodiment, the automaker maintains a database on its software upgrade server that integrates all available software upgrade packages. These upgrade packages cover various functional modules of the vehicle, such as entertainment systems, navigation systems, and driver assistance systems, aiming to provide users with the latest and safest software versions at all times. Based on the target vehicle's hardware and software configuration, multiple upgradeable software packages corresponding to the target vehicle are determined from the aforementioned database, forming a software pool for the target vehicle.

[0085] Optionally, based on the upgrade requirement profile, multiple initial upgrade packages are obtained by selecting packages that match the user's needs from the multiple upgradeable packages included in the software pool.

[0086] Furthermore, at least one target package is determined from multiple initial upgrade packages using preset filtering rules (such as priority filtering rules).

[0087] The above-described optional embodiments of this application achieve the following technical effects: First, based on the upgrade requirement profile, multiple initial upgrade packages are selected from the software pool, initially filtering out packages that are irrelevant to the target vehicle or have low requirement matching, greatly improving the efficiency and accuracy of upgrade package selection, avoiding interference from irrelevant upgrade information to the user, and enhancing the user experience. Second, using preset filtering rules, at least one target package is further determined from the multiple initial upgrade packages. This rule is typically based on the priority of various requirement tags in the personalized requirement profile, ensuring that the selected package best meets the user's personalized upgrade requirements while guaranteeing the efficiency of the upgrade.

[0088] In one optional embodiment, the server orchestrates the generated target upgrade tasks to generate an upgrade sequence list, which is used to determine the execution order of the target upgrade tasks. Furthermore, based on the target vehicle's historical user usage time data and the estimated time consumption of the target upgrade tasks, the server determines multiple alternative upgrade time periods within a preset time period, forming an alternative upgrade time period list.

[0089] For example, the server determines multiple vehicle usage impact levels corresponding to multiple target software packages; sorts the multiple target software packages in descending order according to the multiple vehicle usage impact levels to obtain the software package sorting result; and generates an upgrade order list based on the software package sorting result.

[0090] For example, the server predicts multiple potential idle time periods for the target vehicle within a preset time period based on the user's historical vehicle usage time data; and selects multiple alternative upgrade time periods from the multiple potential idle time periods based on the estimated time consumption of the target upgrade task and preset time period filtering rules.

[0091] The server sends the upgrade sequence list and the list of alternative upgrade time slots to the target vehicle. The target vehicle displays the upgrade sequence list and the list of alternative upgrade time slots on its in-vehicle display interface, and performs a vehicle software upgrade on the target software package based on the user's decision information displayed.

[0092] According to another aspect of the embodiments of this application, a vehicle software upgrade method is also provided, which is applied to a target vehicle. Figure 2 This is a flowchart of another vehicle software upgrade method provided in an embodiment of this application, such as... Figure 2 As shown, the vehicle software upgrade method includes the following steps:

[0093] Step S210: Send the historical operating data of the target vehicle to the server;

[0094] Step S220: Receive the target upgrade task sent by the server. The target upgrade task is generated by the server based on at least one target software package to be upgraded. The target software package is determined from the software pool corresponding to the target vehicle according to the upgrade requirement profile. The upgrade requirement profile is generated based on historical operation data. The software pool includes multiple upgradeable software packages corresponding to the hardware and software configuration of the target vehicle. The upgrade requirement profile is used to describe the upgrade requirements of the target vehicle from multiple dimensions.

[0095] Step S230: Perform vehicle software upgrade on the target software package according to the target upgrade task.

[0096] Optionally, before sending historical operational data to the server, the data can be preprocessed, including data cleaning, unit unification, and privacy data desensitization (using technologies such as data encryption, anonymization, and obfuscation to protect user privacy).

[0097] Encrypted network protocols are used to upload processed historical operational data to the server. The transmission process must ensure data integrity and security to prevent data leakage.

[0098] Furthermore, it receives the target upgrade task issued by the server and performs a vehicle software upgrade on the target software package according to the target upgrade task.

[0099] The vehicle software upgrade method provided in this application achieves the following technical effects: First, the historical operating data of the target vehicle is sent to the server, enabling the server to generate a personalized target upgrade task based on the historical operating data. Next, the target upgrade task is received from the server, and the vehicle software is upgraded according to the target software package. The target vehicle can undergo vehicle software upgrades based on the user's personalized needs, achieving a high degree of matching between the upgrade content and user requirements. Therefore, this application embodiment can achieve personalized vehicle software upgrades, thereby improving the user experience and solving the technical problem in related technologies where vehicle software upgrades lack personalization, thus affecting the user experience.

[0100] Optionally, based on the target upgrade task, a vehicle software upgrade is performed on the target software package, including the following steps:

[0101] Step S2301: Arrange the target upgrade tasks and generate an upgrade order list, wherein the upgrade order list is used to determine the execution order of the target upgrade tasks;

[0102] Step S2302: Based on the user's historical vehicle usage time data of the target vehicle and the estimated time consumption of the target upgrade task, determine multiple alternative upgrade time periods within the preset time period and form a list of alternative upgrade time periods;

[0103] In step S2303, the upgrade order list and the alternative upgrade time period list are displayed on the vehicle display interface, and the vehicle software upgrade is performed on the target software package based on the user's decision information on the displayed content.

[0104] Optionally, the target upgrade task can be orchestrated to generate an upgrade sequence list, clearly displaying the upgrade order of the target software package. Simultaneously, based on the target vehicle's historical user usage time data and the estimated time of the target upgrade task, multiple alternative upgrade time slots within a preset time period are determined, forming an alternative upgrade time slot list. This ensures that vehicle software upgrades do not disrupt users' daily driving. Finally, the upgrade sequence list and alternative upgrade time slot list are displayed on the vehicle's interface (such as the in-vehicle infotainment system), and based on the user's decision-making information regarding the displayed content, the vehicle software package is upgraded, granting the user autonomy in their upgrade decision-making.

[0105] Optionally, upon completion of the upgrade, an upgrade report is automatically generated, summarizing all details of the upgrade process, including the number of successfully upgraded software packages, failed packages, and the reasons for the failures. This report is uploaded to the automaker's software upgrade server and is also displayed to users through the vehicle's infotainment system and the user's mobile app. Users can view the report to understand the specific effects of the upgrade, confirm that the vehicle has reached the latest version, and enhance safety, performance, and user experience.

[0106] The vehicle software upgrade method provided in this application achieves the following technical effects: First, the target upgrade task is orchestrated to generate an upgrade sequence list, avoiding confusion in the subsequent upgrade order. Simultaneously, based on the target vehicle's historical user usage time data and the estimated time of the target upgrade task, multiple alternative upgrade time slots within a preset time period are determined, forming an alternative upgrade time slot list. This step fully considers the user's usage time, ensuring that the upgrade operation is performed during the most convenient time for the user, greatly enhancing user satisfaction. Finally, the upgrade sequence list and the alternative upgrade time slot list are displayed on the vehicle's display interface, and the vehicle software upgrade is executed based on the user's decision information regarding the displayed content. This interactive design empowers the user with autonomy in upgrade decisions, making the entire upgrade process more user-friendly, while also ensuring that the user has full understanding and control over the upgrade content and time, thereby improving the upgrade success rate and user acceptance.

[0107] Optionally, the target upgrade task includes multiple target software packages. The target upgrade task is orchestrated to generate an upgrade sequence list, including the following steps:

[0108] Step S23011: Determine the degree of impact of multiple vehicle usages corresponding to multiple target software packages;

[0109] Step S23012: Based on the degree of impact of multiple vehicle usage, sort the multiple target software packages in descending order to obtain the software package sorting result;

[0110] Step S23013: Generate an upgrade order list based on the package sorting results.

[0111] The aforementioned impact on vehicle use refers to the immediate effect of software package upgrades on vehicle functionality and the user's driving experience. Optionally, the impact on vehicle use can be categorized into three levels: no impact, minor impact, and severe impact.

[0112] "No impact" means that the software package upgrade can be completed silently in the background without affecting the normal use of any vehicle functions, such as theme updates and minor adjustments to the user interface.

[0113] Minor impact refers to the temporary unavailability of certain functions during the software upgrade process, but without affecting the overall operation and safety of the vehicle, such as entertainment system upgrades and navigation interface adjustments.

[0114] Serious impact refers to the temporary failure or weakening of certain key vehicle functions during the software upgrade process, which may affect the vehicle's handling performance and driving safety, such as upgrades to driver assistance systems or powertrain control software.

[0115] Optionally, based on a preset impact assessment table, the impact of multiple target software packages is assessed to obtain multiple vehicle usage impact levels corresponding to the multiple target software packages.

[0116] Furthermore, based on the degree of impact of multiple vehicle usage scenarios, the multiple target software packages are sorted in descending order (i.e., the target software packages are sorted from high to low according to the degree of impact of vehicle usage scenarios) to obtain the software package ranking results.

[0117] Finally, based on the sorting results of the software packages, an upgrade order list is generated to clarify the upgrade order of different target software packages.

[0118] The above-described optional embodiments of this application achieve the following technical effects: First, by evaluating the impact of multiple vehicle usage scenarios on multiple target software packages, refined management of target upgrade tasks is achieved. Second, based on the impact of multiple vehicle usage scenarios, the multiple target software packages are sorted in descending order, further refining the priority of the multiple target software packages, so that target software packages with a high impact on vehicle usage can be processed first within a limited time. Finally, an upgrade order list is generated based on the software package sorting results. This list clearly guides the vehicle onboarding on how to execute upgrade tasks in an orderly manner, especially when there are many software packages, avoiding resource waste and user experience degradation caused by random upgrades.

[0119] Optionally, based on the user's historical vehicle usage time data for the target vehicle and the estimated time consumption of the target upgrade task, multiple alternative upgrade periods within a preset time period are determined, including the following steps:

[0120] Step S23021: Based on the user's historical vehicle usage time data, predict multiple potential idle periods for the target vehicle within a preset time period;

[0121] Step S23022: Based on the estimated time of the target upgrade task and the preset time period filtering rules, select multiple alternative upgrade time periods from multiple potential idle time periods.

[0122] The aforementioned user historical vehicle usage time data refers to the time distribution record of the target vehicle user's vehicle usage over a period of time, usually in hours, and includes vehicle usage habits on weekdays, weekends, and holidays.

[0123] The aforementioned potential idle periods refer to the periods when the probability of a user using a vehicle is lower than a set vehicle usage probability threshold (e.g., 10%).

[0124] In one optional embodiment, statistical or machine learning algorithms are used to predict the probability of user car usage time within a preset time period, thereby determining multiple potential idle time periods within the preset time period.

[0125] For example, the Prophet forecasting model is used to predict the probability of users' car usage time in the coming week. The Prophet model is a time series-based forecasting model suitable for handling trending and seasonal data.

[0126] Optionally, a vehicle usage probability threshold can be set, and all time periods below this threshold can be marked as potentially idle time periods. Considering the uncertainty of user vehicle usage, the selection of the threshold needs to balance the probability of false alarms and false negatives.

[0127] The estimated time for the aforementioned target upgrade task refers to the estimated duration required to complete the entire target upgrade task.

[0128] The above time slot filtering rules are used to select suitable time slots for performing upgrades from potential idle time slots. Time slot filtering rules typically include minimum time slot length, time slot continuity, and time slot security assessment.

[0129] In one alternative embodiment, a continuous period of time with a duration greater than 1.5 times the expected duration is selected from a plurality of potential idle periods as an alternative upgrade period.

[0130] Optionally, security and compliance checks may be conducted on the selected multiple alternative upgrade periods.

[0131] The above-mentioned optional embodiments of this application can achieve the following technical effects: First, by collecting and analyzing the user's historical vehicle usage time data for the target vehicle, the potential idle time periods of the user within a preset time period are predicted, so as to avoid the upgrade process from conflicting with the user's vehicle usage needs, reduce the interference of the upgrade on the user's daily vehicle use, and improve user satisfaction. Second, by combining the estimated time consumption of the target upgrade task and the preset time period filtering rules, multiple alternative upgrade time periods are selected from the predicted potential idle time periods, so as to ensure that the target upgrade task can be completed during the user's non-use time periods, avoiding possible emergency vehicle usage needs during the upgrade process, and further improving the user experience.

[0132] Optionally, the vehicle software upgrade method further includes: in response to starting a vehicle software upgrade, determining upgrade prompt information based on the upgrade progress of multiple target software packages and the degree of impact on multiple vehicle uses, and displaying the upgrade prompt information through a vehicle-side display interface; in response to a vehicle use request, determining an upgrade strategy based on the upgrade prompt information, wherein the upgrade strategy is used to determine whether to continue the current vehicle software upgrade.

[0133] The aforementioned upgrade progress refers to the completion rate or status of multiple target software packages during the installation process.

[0134] In one alternative embodiment, when a vehicle software upgrade is initiated, an upgrade prompt message is determined based on the upgrade progress of multiple target software packages and the degree of impact on multiple vehicle uses.

[0135] For example, if the target software package being upgraded is a navigation system and the impact on vehicle use is minor, an upgrade prompt message will be generated stating "The navigation system is being updated, estimated to take 5 minutes, please wait patiently," and this message will be displayed on the vehicle's display interface.

[0136] For example, if the target software package being upgraded is a driver assistance system and the impact of the driver assistance system on vehicle use is severe, then an upgrade prompt message "Driver assistance system upgrade in progress, vehicle cannot be started, please do not move the vehicle" is generated and displayed on the vehicle's display interface.

[0137] The vehicle-mounted display interface can be an instrument panel display, a central multimedia touchscreen, etc.

[0138] Furthermore, when a user has a need to use the vehicle, the system will determine whether to continue the current vehicle software upgrade based on the current upgrade prompt information.

[0139] The above-described optional embodiments of this application achieve the following technical effects: During the vehicle software upgrade process, upgrade prompts are determined based on the upgrade progress of multiple target software packages and the degree of impact on vehicle use. These prompts are then displayed on the vehicle's display interface, allowing users to clearly understand the current vehicle status and make informed decisions about whether to use the vehicle. When a vehicle use request occurs, the system determines whether to continue the current vehicle software upgrade based on the upgrade prompts, reducing user confusion caused by information asymmetry.

[0140] Figure 3 This is a flowchart illustrating a vehicle software upgrade method according to an embodiment of this application, as shown below. Figure 3 As shown, the specific implementation of the vehicle software upgrade method is as follows: vehicle-side data collection; privacy data anonymization processing; vehicle-side data transmission to the vehicle manufacturer's OTA server; generation of personalized upgrade requirement profile; matching and adapting software packages; generation of personalized target upgrade packages; pushing personalized target upgrade tasks to the vehicle-side; vehicle-side task orchestration; vehicle usage time prediction; calculation of alternative upgrade time periods; synchronization of upgradeable information and predicted time to the user; user decision-making regarding upgrade-related matters; execution of upgrade operations; and feedback of vehicle-side upgrade results.

[0141] The implementation process of the above-mentioned vehicle software upgrade method is explained in detail below.

[0142] Vehicle-side data collection: The vehicle uses built-in sensors and software monitoring modules to record real-time usage data of various functional modules, such as the number of times the navigation function is activated per hour, the daily usage time of the entertainment system, and the activation frequency of driver assistance functions. It also uses location services to obtain precise location information down to the street level. Status data is collected via the vehicle's CAN bus, including real-time battery or fuel percentage, tire pressure, engine speed, and coolant temperature. The data collection process strictly adheres to the principle of minimization, collecting only data relevant to upgrade needs and avoiding redundant information.

[0143] Privacy data anonymization: On the vehicle side, data anonymization technology is used to remove personally identifiable information such as the vehicle owner's name, ID number, and mobile phone number. Driving trajectory data is obfuscated, converting specific coordinates into area information. The vehicle identification number (VIN) is encrypted to ensure that the data cannot be traced back to a specific vehicle or user. It should be noted that the privacy data anonymization steps select appropriate obfuscation parameters to retain as much useful information for analysis as possible while anonymizing the data.

[0144] Vehicle-side data transmission to the OEM's OTA server: The vehicle uses encrypted transmission protocols (such as TLS / SSL) to securely transmit anonymized vehicle data to the OEM's OTA server data storage center, ensuring data integrity and confidentiality during transmission. It should be noted that the data transmission process requires the vehicle to be stationary and connected to the internet to initiate data transmission, avoiding bandwidth consumption during driving that could affect the vehicle's infotainment system; and the data transmission rate must be capped, and the number of retransmissions and the retransmission interval must be set.

[0145] Generating Personalized Upgrade Request Profiles: The data analysis engine of the OTA server further cleans the database data (outlier removal, missing value imputation) and then unifies the units of measurement to eliminate differences in the units of different data items. The processed data is then quantified according to four dimensions: driving style, functional preferences, scenario adaptation, and safety requirements. Each feature item is quantified using appropriate feature calculation methods to extract features across these four dimensions. Based on the extracted features, a hierarchical personalized request profile is constructed using "feature request mapping rules" and "tag weight calculation." Specifically, static information about the user and vehicle is used as the basic identifier for the profile. The extracted quantified feature values ​​are then converted into user requests according to the feature request mapping rules, generating functional tags that can be directly used for OTA upgrade pushes (e.g., users who frequently use navigation functions prioritize map update requests; cars in northern winters are more concerned with the impact of starting performance, power transmission, braking safety, and battery efficiency, prioritizing power and battery-related update requests). The priority of each tag is calculated using a time-series weighting algorithm. Optionally, the personalized request profile is dynamically iterated by combining periodic incremental updates with event-triggered updates, using a rolling time window to retain user data from the most recent six months. Each user's personalized needs profile can be generated based on their data. It should be noted that model calculations can only be initiated after a specified number of valid vehicle data records have been collected to ensure the accuracy of the upgrade needs profile.

[0146] Matching and Adapting Software Packages: The OTA server compares the hardware configuration and software version of each functional module in its own software upgrade pool with the hardware configuration and software version of the user's vehicle modules to confirm whether the user's vehicle has matching hardware that requires an upgrade. If so, an overall pool of upgradable software modules for the user's vehicle is formed. Then, based on the user's personalized upgrade needs profile, software packages that are compatible with the vehicle model, hardware configuration, and software version are selected from the upgradable software pool according to the priority of tags from high to low. Upgrade packages for functional modules with low tag priority that do not affect the user's normal vehicle use are excluded from this upgrade.

[0147] Generate personalized target upgrade packages: The OTA server integrates the software packages selected from the upgradeable software pool of the user's vehicle, compresses and packages them into target upgrade packages (including multiple software packages), and generates an upgrade list, which details the version number, upgrade content (such as optimizing navigation route planning algorithms and improving detour efficiency in congested areas), storage space occupied, and other information of each software package, and calculates the checksum of the upgrade package for vehicle-side verification.

[0148] Pushing personalized upgrade tasks to the vehicle: The OTA server's task scheduling center encapsulates the personalized upgrade package and upgrade list into an upgrade task, which is then pushed to the vehicle's communication module via a message queue. Upon receiving the task, the vehicle first verifies the checksum of the upgrade package. If correct, it parses the upgrade list, records information such as the task ID, reception time, and upgrade package size in the vehicle's backend database, and returns a confirmation message to the server confirming successful task reception.

[0149] Vehicle-side task orchestration: The vehicle-side task management module categorizes software packages in upgrade tasks and classifies them according to their impact on vehicle use: no impact (e.g., interface theme update, which can be silently upgraded in the background), minor impact (e.g., entertainment system function upgrade, which makes the function unusable during the upgrade), and severe impact (e.g., driver assistance system upgrade, which requires the vehicle to be stationary and the system to be unable to start during the upgrade). The upgrades are then sorted from highest to lowest impact, generating an upgrade order list.

[0150] Vehicle usage time prediction: The vehicle-side system calls the Prophet model, which can be used for time series forecasting. Based on the user's historical vehicle usage time data, it predicts the distribution of vehicle usage time for the next 7 days, generating an hourly usage probability curve (0-100%). Periods with a probability below 10% are marked as potentially idle periods. It should be noted that the Prophet model prediction period, time granularity, and user usage probability threshold need to be set.

[0151] Calculate alternative upgrade time slots: The vehicle-side system, based on the estimated time consumption of the upgrade task (estimated in advance according to factors such as upgrade package size and upgrade content complexity), and combined with the vehicle usage time prediction results, selects time slots with continuous idle duration greater than or equal to 1.5 times the estimated time consumption from potential idle time slots as alternative upgrade time slots. Optionally, an upper limit can be set on the number of alternative upgrade time slots.

[0152] Upgradeable information and estimated time are synchronized with the user: The vehicle system pops up an upgrade prompt window on the main interface, displaying a summary of the upgrade content, a list of alternative times, the estimated completion time, and three operation buttons: "Upgrade Now", "Select Time Period", and "Remind Me Later". At the same time, a notification is pushed through the mobile APP, with an attached link to the upgrade details. Users can click to view the complete upgrade list and time options.

[0153] User decision-making regarding upgrade matters: Based on the synchronized information, the user makes the final decision on whether to upgrade and select the specific upgrade time period, and then feeds back the decision results to the vehicle.

[0154] Execute the upgrade operation: After receiving the user's confirmed upgrade decision and upgrade time, the vehicle will execute the upgrade operation according to the user settings and upgrade order list. During the process, the vehicle's display interface needs to provide differentiated prompts based on the upgrade progress of the functional modules. If a functional module marked "Severely Affected" has not yet been upgraded, the user must be clearly informed that "There is a risk to current vehicle use, and the upgrade process cannot be interrupted"; if a functional module marked "Severely Affected" has been upgraded, but a functional module marked "Minorly Affected" has not yet been upgraded, the user must be clearly informed that "The vehicle can be used normally, but the functional modules that have not been upgraded are temporarily unavailable"; if only functional modules marked "No Impact" remain to be upgraded, the user must be clearly informed that "The upgrade is not yet complete, but it does not affect normal vehicle use."

[0155] Vehicle-side upgrade result feedback: After the upgrade is complete, the vehicle generates an upgrade report, recording the number of successfully upgraded software packages, the failed software packages and their reasons, and synchronizes the report to the OTA server's upgrade record database via the vehicle network. Simultaneously, a "Upgrade Complete" notification is displayed on the vehicle's infotainment screen, and a result notification is pushed to the user's mobile app. The user can click to view the detailed report. If the upgrade fails, the vehicle automatically schedules a next attempt and notifies the user.

[0156] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory is used to store a computer program; and the processor is used to execute the program stored in the memory to implement the vehicle software upgrade method of any of the above.

[0157] The electronic device provided in this application embodiment achieves the following technical effects: the computer program corresponding to the vehicle software upgrade method in any of the above is stored in the memory, and the processor executes the computer program stored in the memory to realize the personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that the lack of personalization in vehicle software upgrades affects the user experience.

[0158] According to another aspect of the embodiments of this application, a vehicle is also provided, the vehicle including an on-board memory and an on-board processor, wherein the on-board memory is used to store computer programs; the on-board processor is used to execute the computer programs stored on the on-board memory to implement the vehicle software upgrade method applied to the target vehicle as described in any of the above.

[0159] The vehicle provided in this application embodiment achieves the following technical effects: the computer program corresponding to the vehicle software upgrade method in any of the above is stored in the vehicle memory, and the computer program stored in the vehicle memory is executed by the vehicle processor to realize the personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that the lack of personalization in vehicle software upgrades affects the user experience.

[0160] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the vehicle software upgrade method described in any of the above embodiments when run on a computer or processor.

[0161] The computer-readable storage medium provided in this application embodiment achieves the following technical effects: it stores the computer program corresponding to the vehicle software upgrade method in any of the above into the computer-readable storage medium, and uses the processor to execute the computer program stored in the computer-readable storage medium to achieve personalized upgrade of vehicle software, thereby improving the user experience. This solves the technical problem in the related art that vehicle software upgrades lack personalization, thus affecting the user experience.

[0162] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0163] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0164] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0165] In this application, "multiple" refers to two or more.

[0166] In this application, unless otherwise expressly defined, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection between two components. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0167] The terms “first,” “second,” “third,” “fourth,” etc., in this application (if present) are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0168] In this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, in this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0169] Unless otherwise specified, all steps in this application may be performed sequentially or randomly. For example, if the method includes steps A and B, it means that the method may include steps A and B performed sequentially, or it may include steps B and A performed sequentially. For example, if the method may also include step C, it means that step C may be added to the method in any order. For example, the method may include steps A, B, and C, or it may include steps A, C, and B, or it may include steps C, A, and B, etc.

[0170] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A vehicle software upgrade method, characterized in that, The vehicle software upgrade method is applied to a server, and the vehicle software upgrade method includes: Based on the historical operating data of the target vehicle, an upgrade requirement profile is generated, wherein the upgrade requirement profile is used to describe the upgrade requirements of the target vehicle from multiple dimensions. Based on the upgrade requirement profile, at least one target software package to be upgraded is determined from the software pool corresponding to the target vehicle, wherein the software pool includes multiple upgradeable software packages corresponding to the hardware and software configuration of the target vehicle; Based on the target software package, a target upgrade task is sent to the target vehicle to enable the target vehicle to perform a vehicle software upgrade on the target software package.

2. The vehicle software upgrade method according to claim 1, characterized in that, Based on the historical operating data corresponding to the target vehicle, the upgrade requirement profile is generated, including: The historical operation data is preprocessed to obtain preprocessed data; According to the preset extraction dimensions, feature extraction is performed on the preprocessed data to obtain a feature matrix. The preset extraction dimensions include: driving style dimension, function preference dimension, scene adaptation dimension, and safety requirement dimension. Based on the preset feature requirement mapping rules, feature mapping is performed on multiple features contained in the feature matrix to obtain multiple feature requirement labels. Based on a preset weight determination algorithm, multiple tag weights corresponding to the multiple feature requirement tags are determined, wherein the multiple feature requirement tags and the multiple tag weights correspond one-to-one; Based on the weights of the multiple labels, the multiple feature requirement labels are sorted to obtain the requirement ranking result; Based on the sorting results of the requirements, the upgrade requirement profile is generated.

3. The vehicle software upgrade method according to claim 1, characterized in that, Based on the upgrade requirement profile, at least one target software package to be upgraded is determined from the software pool corresponding to the target vehicle, including: Based on the upgrade requirement profile, multiple initial upgrade packages are selected from the software pool; Using preset filtering rules, at least one target software package is determined from the plurality of initial upgrade software packages.

4. A vehicle software upgrade method, characterized in that, The vehicle software upgrade method is applied to a target vehicle, and the vehicle software upgrade method includes: Send the historical operating data of the target vehicle to the server; The server receives a target upgrade task, wherein the target upgrade task is generated by the server based on at least one target software package to be upgraded, the target software package is determined from the software pool corresponding to the target vehicle according to the upgrade requirement profile, the upgrade requirement profile is generated based on the historical operation data, the software pool includes multiple upgradeable software packages corresponding to the hardware and software configuration of the target vehicle, and the upgrade requirement profile is used to describe the upgrade requirements of the target vehicle from multiple dimensions. According to the target upgrade task, perform a vehicle software upgrade on the target software package.

5. The vehicle software upgrade method according to claim 4, characterized in that, According to the target upgrade task, perform a vehicle software upgrade on the target software package, including: The target upgrade task is orchestrated to generate an upgrade order list, wherein the upgrade order list is used to determine the execution order of the target upgrade task; Based on the user's historical vehicle usage time data of the target vehicle and the estimated time consumption of the target upgrade task, multiple alternative upgrade time periods are determined within a preset time period to form a list of alternative upgrade time periods; The upgrade order list and the alternative upgrade time period list are displayed on the vehicle display interface, and the vehicle software upgrade is performed on the target software package based on the user's decision information regarding the displayed content.

6. The vehicle software upgrade method according to claim 5, characterized in that, The target upgrade task includes multiple target software packages. The target upgrade task is orchestrated to generate the upgrade order list, including: Determine the degree of impact on vehicle usage corresponding to the multiple target software packages; Based on the degree of impact of the various vehicle usage scenarios, the various target software packages are sorted in descending order to obtain the software package ranking result; Based on the sorting results of the software packages, the upgrade order list is generated.

7. The vehicle software upgrade method according to claim 5, characterized in that, Based on the user's historical vehicle usage time data for the target vehicle and the estimated time consumption of the target upgrade task, the multiple alternative upgrade time periods within the preset time period are determined, including: Based on the user's historical vehicle usage time data, multiple potential idle periods of the target vehicle within the preset time period are predicted; Based on the estimated time consumption of the target upgrade task and the preset time period filtering rules, the multiple alternative upgrade time periods are selected from the multiple potential idle time periods.

8. The vehicle software upgrade method according to claim 6, characterized in that, Also includes: In response to the commencement of the vehicle software upgrade, an upgrade prompt message is determined based on the upgrade progress of the multiple target software packages and the degree of impact on vehicle use, and the upgrade prompt message is displayed through the vehicle-side display interface; In response to a vehicle use request, an upgrade strategy is determined based on the upgrade prompt information, wherein the upgrade strategy is used to determine whether to continue the current vehicle software upgrade.

9. An electronic device, characterized in that, Including memory and processor, among which, The memory is used to store computer programs; The processor is used to execute the program stored in the memory to implement the vehicle software upgrade method according to any one of claims 1 to 8.

10. A vehicle, characterized in that, The vehicle includes an on-board storage device and an on-board processor, wherein, The on-board storage device is used to store computer programs; The vehicle processor is used to execute the computer program stored in the vehicle memory to implement the vehicle software upgrade method according to any one of claims 4 to 8.

Images