Vehicle software upgrade method, device, electronic equipment and storage medium

Abstract

The present disclosure provides a vehicle software upgrade method, device, electronic device and storage medium. The method includes: receiving a data packet for upgrading the software version of a target model vehicle and log information of the data packet; obtaining the number of times each vehicle software of the target model vehicle under each user name is used and the usage time period; determining the upgrade content corresponding to each user according to the number of times each vehicle software of the target model vehicle under each user name is used and the log information; determining the upgrade time corresponding to each user according to the usage time period of each vehicle software of the target model vehicle under each user name, wherein the upgrade time is the time for performing the software version upgrade; performing the software version upgrade of the target model vehicle under each user name according to the upgrade content and upgrade time corresponding to each user. The above technical means are adopted to solve the problem that the prior art cannot provide personalized upgrade strategies for different users.

Description

Technical Field

[0001] The present disclosure relates to the field of automobile technology, and in particular to a vehicle-mounted software upgrade method, device, electronic device and storage medium. Background Art

[0002] In order to ensure the safety of the car and improve the user experience, the in-vehicle software needs to be upgraded frequently. Currently, when receiving a push notification for an in-vehicle software upgrade, the user can only decide whether to participate in the upgrade, and if participating in the upgrade, all the contents of the upgrade data package need to be updated. Different household owners have different dependence and preferences on different in-vehicle software. In one upgrade, the household owner may need to upgrade some in-vehicle software, while some in-vehicle software does not need to be upgraded. In this regard, there is a lack of intelligent decision-making methods to determine whether different users participate in the upgrade and provide personalized upgrade strategies for different users. Summary of the invention

[0003] In view of this, the embodiments of the present disclosure provide a vehicle-mounted software upgrade method, device, electronic device and storage medium to solve the problem in the prior art that personalized upgrade strategies cannot be provided for different users.

[0004] According to a first aspect of an embodiment of the present disclosure, a method for upgrading vehicle-mounted software is provided, comprising: receiving a data packet for upgrading the software version of a target model vehicle and log information of the data packet; obtaining the number of times each vehicle-mounted software of the target model vehicle under each user is used and the usage time period; determining the upgrade content corresponding to each user according to the number of times each vehicle-mounted software of the target model vehicle under each user is used and the log information, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade; determining the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user, wherein the upgrade time is the time for performing the software version upgrade; and upgrading the software version of the target model vehicle under each user according to the upgrade content and upgrade time corresponding to each user.

[0005] According to a second aspect of an embodiment of the present disclosure, a vehicle-mounted software upgrade device is provided, including: a receiving module, configured to receive a data packet for performing a software version upgrade on a target model vehicle and log information of the data packet; an acquisition module, configured to obtain the number of times each vehicle-mounted software of a target model vehicle under each user is used and the usage time period; a first determination module, configured to determine the upgrade content corresponding to each user according to the number of times each vehicle-mounted software of a target model vehicle under each user is used and the log information, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade; a second determination module, configured to determine the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user, wherein the upgrade time is the time for performing the software version upgrade; an upgrade module, configured to perform a software version upgrade on the target model vehicle under each user according to the upgrade content and upgrade time corresponding to each user.

[0006] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0007] According to a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any one of the methods described above are implemented.

[0008] Compared with the prior art, the beneficial effects of the disclosed embodiment include at least: determining the upgrade content corresponding to each user according to the number of times each vehicle-mounted software of the target model vehicle under the name of each user is used and the log information, determining the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under the name of each user, and upgrading the software version of the target model vehicle under the name of each user according to the upgrade content and upgrade time corresponding to each user. Therefore, the above-mentioned technical means can solve the problem that the prior art cannot provide personalized upgrade strategies for different users, and then provide corresponding upgrade strategies for different users, thereby improving software service quality and user satisfaction. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0010] Figure 1is a flowchart of a vehicle software upgrade method provided by an embodiment of the present disclosure;

[0011] Figure 2 is a flowchart of another vehicle software upgrade method provided by an embodiment of the present disclosure;

[0012] Figure 3 is a structural schematic diagram of a vehicle software upgrade device provided by an embodiment of the present disclosure;

[0013] Figure 4 It is a structural schematic diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0014] In the following description, specific details such as specific system structures and technologies are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present disclosure. However, it should be clear to those skilled in the art that the present disclosure may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obstructing the description of the present disclosure with unnecessary details.

[0015] Figure 1 It is a flowchart of a vehicle software upgrade method provided by an embodiment of the present disclosure. Figure 1 The vehicle software upgrade method can be executed by a computer or a server, or a processor provided on the computer or the server, or software on a computer or a common server. The vehicle software upgrade method includes:

[0016] S101, receiving a data packet for upgrading the software version of a target model vehicle and log information of the data packet;

[0017] S102, obtaining the usage times and usage time periods of each vehicle-mounted software of the target model vehicle under each user's name;

[0018] S103, determining the upgrade content corresponding to each user according to the usage times and log information of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade;

[0019] S104, determining the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade time is the time for performing software version upgrade;

[0020] S105, upgrading the software version of the target model vehicle under each user's name according to the upgrade content and upgrade time corresponding to each user.

[0021] The data packet is the upgrade data required for the target model vehicle to upgrade the software version this time, such as the data packet, including: the latest version of the vehicle application and various security patches. The log information of the data packet is a description of the data in the data packet, which can explain the content of the software version upgrade, such as which vehicle applications will be upgraded in this software version upgrade. The characteristics of the vehicle software upgrade of the target model vehicle under the user's name can be mainly represented by the number of uses and usage time periods of each vehicle software in the target model vehicle under the user's name, that is, the number of uses and usage time periods of each vehicle software used by different users are different. The number of uses of each vehicle software can indicate the user's preference or dependence on each vehicle software. The more times a certain vehicle software is used, the higher the user's preference or dependence on the vehicle software, and the more the user pays attention to the upgrade of the vehicle software. For example, if user A uses vehicle software B more times, it means that user A is very dependent on vehicle software B, and user A will participate in each upgrade of vehicle software B. On the contrary, if user A uses vehicle software B less times, it means that user A does not rely on vehicle software B, and user A may not participate in the upgrade of vehicle software B. In order to ensure that the software version upgrade does not affect the user's normal use of each in-vehicle software, the time period when the user participates in the upgrade of each in-vehicle software should avoid the user's use time period of each in-vehicle software.

[0022] According to the technical solution provided by the embodiment of the present disclosure, a data packet for upgrading the software version of a target model vehicle and log information of the data packet are received; the number of times each vehicle-mounted software of the target model vehicle under each user name is used and the time period of use are obtained; the upgrade content corresponding to each user is determined according to the number of times each vehicle-mounted software of the target model vehicle under each user name and the log information, wherein the upgrade content is the vehicle-mounted software involved in the software version upgrade; the upgrade time corresponding to each user is determined according to the time period of use of each vehicle-mounted software of the target model vehicle under each user name, wherein the upgrade time is the time for performing the software version upgrade; the software version of the target model vehicle under each user name is upgraded according to the upgrade content and upgrade time corresponding to each user. The above technical means can solve the problem that the prior art cannot provide personalized upgrade strategies for different users, and then provide corresponding upgrade strategies for different users, thereby improving software service quality and user satisfaction.

[0023] Furthermore, based on the usage counts and log information of each vehicle-mounted software of the target model vehicle under each user's name, the upgrade content corresponding to each user is determined, including: based on the log information, one or more target vehicle-mounted software are determined from multiple vehicle-mounted software of the target model vehicle, wherein the data packet contains upgrade data corresponding to the target vehicle-mounted software; based on the usage counts of the target vehicle-mounted software of the target model vehicle under each user's name, it is determined whether each target vehicle-mounted software of the target model vehicle under each user's name participates in the software version upgrade.

[0024] The upgrade content corresponding to the user is the vehicle-mounted software that the user is participating in the software version upgrade this time. The log information is a description of the data in the data packet. For example, if the log information indicates that the vehicle-mounted software for this software version upgrade are B, C, and D, then B, C, and D among the multiple vehicle-mounted software of the target model vehicle are used as the target vehicle-mounted software. The number of times each vehicle-mounted software is used can indicate the user's degree of dependence on each vehicle-mounted software, and the target vehicle-mounted software with a number of uses greater than a preset value can be used as the vehicle-mounted software participating in the software version upgrade. For example, if the number of uses of B and C in a user's vehicle-mounted software is greater than the preset value, and the number of uses of D is less than the preset value, it is determined that the user's B and C participate in the software version upgrade, and D does not participate in the software version upgrade.

[0025] Furthermore, based on the number of times the target vehicle software of the target model vehicle under each user's name is used, it is determined whether each target vehicle software of the target model vehicle under each user's name participates in the software version upgrade, including: obtaining historical upgrade information corresponding to the target vehicle software of the target model vehicle under each user's name; based on the number of times the target vehicle software of the target model vehicle under each user's name is used and the historical upgrade information, it is determined whether each target vehicle software of the target model vehicle under each user's name participates in the software version upgrade.

[0026] The historical upgrade information may be the log information of the corresponding data package when the user has upgraded the target vehicle software. The historical upgrade information indicates that the user upgraded the software version when the push data package contains the upgrade data type of the target vehicle software. The historical upgrade information can represent the characteristics of the user's past software version upgrades. Based on the number of times the user has used the target vehicle software and the historical upgrade information, it can be determined whether the user's target vehicle software participates in the software version upgrade.

[0027] Furthermore, based on the usage count and historical upgrade information of the target vehicle software of the target model vehicles under the name of each user, it is determined whether each target vehicle software of the target model vehicles under the name of each user participates in the software version upgrade, including: determining the upgrade description information corresponding to each target vehicle software from the log information; calculating the Euclidean distance between the upgrade description information and the historical upgrade information of the target vehicle software of the target model vehicles under the name of each user; determining one or more first users from multiple users whose usage count of the target vehicle software of the target model vehicles is greater than a preset number of times; determining one or more second users from the one or more first users whose corresponding Euclidean distance of the target vehicle software of the target model vehicles is greater than a preset threshold; and determining that each target vehicle software of the target model vehicles under the name of one or more second users participates in the software version upgrade.

[0028] The upgrade description information of the target vehicle software is a description of the upgrade data type of the target vehicle software in the data package pushed for the current software version upgrade. The historical upgrade information of the target vehicle software is a description of the upgrade data type of the target vehicle software in the data package pushed for the past software version upgrade. The historical upgrade information of the target vehicle software is determined from the historical log information, which is the log information of the data package that has participated in the software version upgrade in the past. The upgrade data type includes software version update, new security patch, fix of a certain problem, and addition or update of firmware content.

[0029] The Euclidean distance between the upgrade description information and the historical upgrade information of the target vehicle software of each user is calculated, and a first user whose number of uses of the target vehicle software is greater than a preset number of times is determined from all users. A second user whose Euclidean distance corresponding to the target vehicle software is greater than a preset threshold is determined from the first user, and the target vehicle software of the second user is determined to participate in the software version upgrade.

[0030] Furthermore, the Euclidean distance between the upgrade description information and the historical upgrade information of the target vehicle software of the target model vehicle under each user name is calculated, including: respectively extracting the embedded features of the upgrade description information and the historical upgrade information of the target vehicle software of the target model vehicle under each user name; calculating the Euclidean distance between the embedded features of the upgrade description information and the historical upgrade information of the target vehicle software of the target model vehicle under each user name.

[0031] The embedded features of the upgrade description information and the embedded features of the historical upgrade information of the user's target vehicle software are extracted, and the Euclidean distance between the embedded features of the upgrade description information and the historical upgrade information of the user is calculated.

[0032] Furthermore, the software version of the target model vehicles under the name of each user is upgraded according to the upgrade content and upgrade time corresponding to each user, including: obtaining historical log information of data packets of the target model vehicles under the name of each user that have undergone software version upgrades in history; obtaining statistical results corresponding to the target model vehicles under the name of each user by counting the historical log information corresponding to the target model vehicles under the name of each user; classifying the target model vehicles under the name of each user into corresponding upgrade stages based on the log information and the statistical results corresponding to the target model vehicles under the name of each user; and upgrading the software version of the target model vehicles under the name of each user according to the upgrade content, upgrade time and upgrade stage corresponding to each user.

[0033] By counting the historical log information corresponding to the user, the statistical results corresponding to the user are obtained. The statistical results can indicate the upgrade frequency of the user and the conditions under which the user will participate in the software version upgrade. The upgrade stage includes the trial stage, the formal stage or the stable stage. The upgrade time in the trial stage is earlier than the formal stage, and the upgrade time in the formal stage is earlier than the stable stage. For example, if user A has a high upgrade frequency, and the Euclidean distance between the upgrade data or upgrade data type in the statistical results and the upgrade data or upgrade data type in the log information is greater than the set distance, then user A is considered to be more active in software version upgrades, and user A is judged to be a user in the trial stage, that is, user A is one of the first users to participate in this software version upgrade. The judgment of users in the formal stage and the stable stage is similar.

[0034] Figure 2 is a flow chart of another vehicle software upgrade method provided by an embodiment of the present disclosure, such as Figure 2 As shown, including:

[0035] S201, record the users in the early adopter stage, the formal stage or the stable stage as the third user, the fourth user and the fifth user respectively;

[0036] S202, in the trial stage: according to the upgrade content and upgrade time corresponding to each third user, the software version of the target model vehicle under each third user is upgraded using the data package;

[0037] S203, obtaining first feedback information after the software version of each target model vehicle under the name of the third user is upgraded;

[0038] S204, optimizing the data packet according to the plurality of first feedback information;

[0039] S205, in the formal stage: according to the upgrade content and upgrade time corresponding to each fourth user, the software version of the target model vehicle under each fourth user is upgraded by using the data packets optimized by the multiple first feedback information;

[0040] S206, obtaining second feedback information after the software version of each target model vehicle under the name of the fourth user is upgraded;

[0041] S207, optimizing the data packet according to the plurality of pieces of second feedback information;

[0042] S208, in the stable stage: according to the upgrade content and upgrade time corresponding to each fifth user, the software version of the target model vehicle under each fifth user is upgraded using the data packets optimized by the multiple second feedback information.

[0043] In the trial stage: at the upgrade time corresponding to the third user, use the data packet to upgrade the software version of the vehicle-mounted software in the upgrade content corresponding to the third user. In order to improve user satisfaction, the upgrade data in the data packet can be optimized using the feedback from users who have participated in the software version upgrade, such as optimizing the data packet based on the first feedback information of the third user. In the formal stage: at the upgrade time corresponding to the fourth user, use the data packet to upgrade the software version of the vehicle-mounted software in the upgrade content corresponding to the fourth user, and optimize the data packet based on the second feedback information of the fourth user. In the stable stage: at the upgrade time corresponding to the fifth user, use the data packet to upgrade the software version of the vehicle-mounted software in the upgrade content corresponding to the fifth user.

[0044] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present disclosure, and will not be described in detail here.

[0045] The following are embodiments of the device disclosed herein, which can be used to execute the method embodiments disclosed herein. For details not disclosed in the device embodiments disclosed herein, please refer to the method embodiments disclosed herein.

[0046] Figure 3 Schematic diagram of a vehicle software upgrade device provided by an embodiment of the present disclosure. Figure 3 As shown, the vehicle software upgrade device includes:

[0047] The receiving module 301 is configured to receive a data packet for performing a software version upgrade on a target model vehicle and log information of the data packet;

[0048] The acquisition module 302 is configured to acquire the usage times and usage time periods of each vehicle-mounted software of the target model vehicle under each user name;

[0049] The first determination module 303 is configured to determine the upgrade content corresponding to each user according to the usage times and log information of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade;

[0050] The second determination module 304 is configured to determine the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade time is the time for performing software version upgrade;

[0051] The upgrade module 305 is configured to upgrade the software version of the target model vehicle under each user's name according to the upgrade content and upgrade time corresponding to each user.

[0052] According to the technical solution provided by the embodiment of the present disclosure, a data packet for upgrading the software version of a target model vehicle and log information of the data packet are received; the number of times each vehicle-mounted software of the target model vehicle under each user name is used and the time period of use are obtained; the upgrade content corresponding to each user is determined according to the number of times each vehicle-mounted software of the target model vehicle under each user name and the log information, wherein the upgrade content is the vehicle-mounted software involved in the software version upgrade; the upgrade time corresponding to each user is determined according to the time period of use of each vehicle-mounted software of the target model vehicle under each user name, wherein the upgrade time is the time for performing the software version upgrade; the software version of the target model vehicle under each user name is upgraded according to the upgrade content and upgrade time corresponding to each user. The above technical means can solve the problem that the prior art cannot provide personalized upgrade strategies for different users, and then provide corresponding upgrade strategies for different users, thereby improving software service quality and user satisfaction.

[0053] In some embodiments, the first determination module 303 is also configured to determine one or more target vehicle-mounted software from multiple vehicle-mounted software of the target model vehicle based on log information, wherein the data packet contains upgrade data corresponding to the target vehicle-mounted software; based on the number of times the target vehicle-mounted software of the target model vehicle under each user's name is used, determine whether each target vehicle-mounted software of the target model vehicle under each user's name participates in the software version upgrade.

[0054] In some embodiments, the first determination module 303 is also configured to obtain historical upgrade information corresponding to the target vehicle-mounted software of the target model vehicles under each user's name; based on the number of uses and historical upgrade information of the target vehicle-mounted software of the target model vehicles under each user's name, determine whether each target vehicle-mounted software of the target model vehicles under each user's name participates in the software version upgrade.

[0055] In some embodiments, the first determination module 303 is also configured to determine the upgrade description information corresponding to each target vehicle-mounted software from the log information; calculate the Euclidean distance between the upgrade description information and the historical upgrade information of the target vehicle-mounted software of the target model vehicle under each user; determine one or more first users from multiple users whose number of uses of the target vehicle-mounted software of the target model vehicle is greater than a preset number of times; determine one or more second users from one or more first users whose Euclidean distance corresponding to the target vehicle-mounted software of the target model vehicle is greater than a preset threshold; and determine that each target vehicle-mounted software of the target model vehicle under one or more second users participates in the software version upgrade.

[0056] In some embodiments, the first determination module 303 is also configured to respectively extract the embedded features of the upgrade description information and historical upgrade information of the target vehicle software of the target model vehicle under each user's name; and calculate the Euclidean distance between the embedded features of the upgrade description information and historical upgrade information of the target vehicle software of the target model vehicle under each user's name.

[0057] In some embodiments, the upgrade module 305 is also configured to obtain historical log information of data packets that have undergone software version upgrades in the history of target model vehicles under each user's name; obtain statistical results corresponding to the target model vehicles under each user's name by counting the historical log information corresponding to the target model vehicles under each user's name; classify the target model vehicles under each user's name into corresponding upgrade stages based on the log information and the statistical results corresponding to the target model vehicles under each user's name; and perform software version upgrades on the target model vehicles under each user's name according to the upgrade content, upgrade time and upgrade stage corresponding to each user.

[0058] In some embodiments, the upgrade module 305 is further configured to record users belonging to the trial stage, the formal stage or the stable stage as the third user, the fourth user and the fifth user respectively; in the trial stage: according to the upgrade content and upgrade time corresponding to each third user, the software version of the target model vehicle under the name of each third user is upgraded using a data packet; the first feedback information after the software version of the target model vehicle under the name of each third user is obtained; the data packet is optimized according to multiple first feedback information; in the formal stage: according to the upgrade content and upgrade time corresponding to each fourth user, the software version of the target model vehicle under the name of each fourth user is upgraded using a data packet optimized by multiple first feedback information; the second feedback information after the software version of the target model vehicle under the name of each fourth user is obtained; the data packet is optimized according to multiple second feedback information; in the stable stage: according to the upgrade content and upgrade time corresponding to each fifth user, the software version of the target model vehicle under the name of each fifth user is upgraded using a data packet optimized by multiple second feedback information.

[0059] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

[0060] Figure 4 Schematic diagram of an electronic device 4 provided in an embodiment of the present disclosure. Figure 4 As shown, the electronic device 4 of this embodiment includes: a processor 401, a memory 402, and a computer program 403 stored in the memory 402 and executable on the processor 401. When the processor 401 executes the computer program 403, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 401 executes the computer program 403, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0061] The electronic device 4 may include but is not limited to a processor 401 and a memory 402. Those skilled in the art will appreciate that Figure 4 The electronic device 4 is merely an example and does not limit the electronic device 4 , and may include more or less components than those shown in the figure, or different components.

[0062] The processor 401 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0063] The memory 402 may be an internal storage unit of the electronic device 4, for example, a hard disk or memory of the electronic device 4. The memory 402 may also be an external storage device of the electronic device 4, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. The memory 402 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 402 is used to store computer programs and other programs and data required by the electronic device.

[0064] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0065] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present disclosure implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0066] The above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should all be included in the protection scope of the present disclosure.

Claims

1. A vehicle software upgrade method, characterized in that: include: Receiving a data packet for performing a software version upgrade on a target model vehicle and log information of the data packet; Obtain the usage times and usage time periods of each vehicle software of the target model vehicle under each user name; Determine the upgrade content corresponding to each user according to the number of times each vehicle-mounted software of the target model vehicle under each user's name is used and the log information, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade; Determine the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade time is the time when the software version is upgraded; By counting the historical log information of the data packets of the target model vehicles under the names of each user that have undergone software version upgrades, the statistical results corresponding to the target model vehicles under the names of each user are obtained, and based on the log information and the statistical results corresponding to the target model vehicles under the names of each user, the target model vehicles under the names of each user are classified into corresponding upgrade stages, and the upgrade stages include a trial stage, a formal stage or a stable stage; The software version of the target model vehicle under each user's name is upgraded according to the upgrade content, upgrade time and upgrade stage corresponding to each user, including: Record the users in the trial stage, the formal stage or the stable stage as the third user, the fourth user and the fifth user respectively; In the trial stage: according to the upgrade content and upgrade time corresponding to each third user, the software version of the target model vehicle under each third user is upgraded by using the data package; Obtaining first feedback information after the software version upgrade is performed on the target model vehicles under the name of each third user; Optimizing the data packet according to the plurality of first feedback information; In the formal stage: according to the upgrade content and upgrade time corresponding to each fourth user, the software version of the target model vehicle under each fourth user is upgraded using the data packets optimized by the multiple first feedback information; Obtaining second feedback information after the software version upgrade is performed on the target model vehicles under the name of each fourth user; Optimizing the data packet according to the plurality of pieces of second feedback information; In the stable stage: according to the upgrade content and upgrade time corresponding to each fifth user, the software version of the target model vehicle under each fifth user is upgraded using the data package optimized by multiple second feedback information.

2. The method according to claim 1, characterized in that According to the usage times of each vehicle software of the target model vehicle under each user name and the log information, the upgrade content corresponding to each user is determined, including: Based on the log information, one or more target vehicle-mounted software are determined from a plurality of vehicle-mounted software of the target model vehicle, wherein the data packet includes upgrade data corresponding to the target vehicle-mounted software; Based on the usage count of the target vehicle software of the target model vehicle under the name of each user, it is determined whether each target vehicle software of the target model vehicle under the name of each user participates in the software version upgrade.

3. The method according to claim 2, characterized in that Determining whether each target vehicle software of the target vehicle model under each user name participates in the software version upgrade based on the usage count of the target vehicle software of the target vehicle model under each user name includes: Obtain the historical upgrade information corresponding to the target vehicle software of the target model vehicle under each user's name; Based on the usage times and historical upgrade information of the target vehicle software of the target model vehicles under the names of the respective users, it is determined whether each target vehicle software of the target model vehicles under the names of the respective users participates in the software version upgrade.

4. The method according to claim 3, characterized in that Based on the usage times and historical upgrade information of the target vehicle software of the target model vehicles under the names of the respective users, determining whether each target vehicle software of the target model vehicles under the names of the respective users participates in the software version upgrade includes: Determining upgrade description information corresponding to each target vehicle software from the log information; Calculate the Euclidean distance between the upgrade description information and the historical upgrade information of the target vehicle software of the target model vehicle under each user name; Determine one or more first users from among the plurality of users, whose number of times of using the target vehicle software of the target model vehicle is greater than a preset number; Determine, from the one or more first users, one or more second users whose Euclidean distance corresponding to the target vehicle software of the target model vehicle is greater than a preset threshold; Determine that each target vehicle-mounted software of a target model vehicle under one or more second users participates in the software version upgrade.

5. The method according to claim 4, characterized in that Calculate the Euclidean distance between the upgrade description information and historical upgrade information of the target vehicle software of the target model vehicle under each user name, including: Extracting the embedded features of the upgrade description information and historical upgrade information of the target vehicle software of the target model vehicle under each user name respectively; The Euclidean distance between the embedded features of the upgrade description information and historical upgrade information of the target vehicle software of the target model vehicle under each user name is calculated.

6. A vehicle software upgrade device, characterized in that: include: A receiving module, configured to receive a data packet for performing a software version upgrade on a target model vehicle and log information of the data packet; An acquisition module is configured to acquire the usage times and usage time periods of each vehicle-mounted software of a target model vehicle under each user name; The first determination module is configured to determine the upgrade content corresponding to each user according to the number of times each vehicle-mounted software of the target model vehicle under each user's name is used and the log information, wherein the upgrade content is the vehicle-mounted software participating in the software version upgrade; The second determination module is configured to determine the upgrade time corresponding to each user according to the usage time period of each vehicle-mounted software of the target model vehicle under each user's name, wherein the upgrade time is the time for performing the software version upgrade; The upgrade module is configured to obtain statistical results corresponding to the target model vehicles under the names of each user by counting historical log information of data packets that have undergone software version upgrades for the target model vehicles under the names of each user, and classify the target model vehicles under the names of each user into corresponding upgrade stages based on the log information and the statistical results corresponding to the target model vehicles under the names of each user, wherein the upgrade stages include a trial stage, a formal stage or a stable stage; and perform the software version upgrade on the target model vehicles under the names of each user according to the upgrade content, upgrade time and upgrade stage corresponding to each user; The upgrade module is further configured to: record users belonging to the trial stage, the formal stage or the stable stage as the third user, the fourth user and the fifth user respectively; in the trial stage: according to the upgrade content and upgrade time corresponding to each third user, use the data packet to upgrade the software version of the target model vehicle under the name of each third user; obtain the first feedback information after the software version of the target model vehicle under the name of each third user is upgraded; optimize the data packet according to multiple first feedback information; in the formal stage: according to the upgrade content and upgrade time corresponding to each fourth user, use the data packet optimized by multiple first feedback information to upgrade the software version of the target model vehicle under the name of each fourth user; obtain the second feedback information after the software version of the target model vehicle under the name of each fourth user is upgraded; optimize the data packet according to multiple second feedback information; in the stable stage: according to the upgrade content and upgrade time corresponding to each fifth user, use the data packet optimized by multiple second feedback information to upgrade the software version of the target model vehicle under the name of each fifth user.

7. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 5 when executing the computer program.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 5 are implemented.

Images