Vehicle software upgrading method and device, vehicle and storage medium

In vehicle software upgrade, the target upgrade time is determined based on the timestamp of user authorization, and OTA upgrade is achieved, which solves the problems of insufficient server performance and high operating costs caused by high concurrency, improves user experience and reduces operating costs.

CN119065693APending Publication Date: 2024-12-03ZHEJIANG GEELY HLDG GRP CO LTD +1
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411196824.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

When the vehicle software is upgraded, high concurrency leads to insufficient server performance and inability to effectively deal with it, resulting in increased operating costs and poor user experience.

Method used

By receiving update instructions sent by users, obtaining timestamps, determining the target upgrade time based on the timestamp, realizing OTA upgrades, reducing high concurrency peaks, postponing the upgrade time in non-use periods, and avoiding server idleness.

Benefits of technology

It reduces server operation costs, improves user experience, and realizes randomization and decentralization of upgrade time, avoiding performance bottlenecks caused by high concurrency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065693A_ABST
    Figure CN119065693A_ABST
Patent Text Reader

Abstract

The invention provides a vehicle software upgrading method and device, a vehicle and a storage medium, and is applied to the technical field of vehicle control, and the method comprises the steps of receiving an updating instruction sent by a user, obtaining a timestamp of the updating instruction according to the updating instruction, determining target upgrading time based on the timestamp, and carrying out OTA upgrading according to the target upgrading time. Through the method, randomization and decentralization of the upgrading time are realized, so that the high-concurrency peak value of the server is reduced, the operation cost of the server is reduced, and meanwhile, the user experience is also improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of vehicle control technology, and in particular to a vehicle software upgrade method, device, vehicle and storage medium. Background Art

[0002] With the advancement of technology, cars are becoming more and more intelligent, and the software upgrades for vehicles are also becoming more intelligent. Over-the-Air Technology (OTA) remote download has gradually become a popular technology for vehicles. It is a technology that remotely manages mobile terminal devices and subscriber identity module (SIM) card data through the air interface of mobile communications. OTA can detect the upgrade of the vehicle's new system online and download the system upgrade package through the wireless network or mobile network to complete the upgrade.

[0003] In the prior art, when it is detected that the vehicle has an update or upgrade task, the user makes an appointment to set the upgrade time, or the user authorizes immediate upgrade, or the user authorizes the vehicle computer to automatically upgrade.

[0004] However, if the automatic upgrade time is relatively concentrated, the server cannot effectively cope with high concurrency, and immediate updates will also affect users' use of the car, resulting in a poor user experience. Summary of the invention

[0005] The present application provides a vehicle software upgrade method, device, vehicle and storage medium to solve the problem of how to efficiently utilize server performance to achieve vehicle software upgrade.

[0006] In a first aspect, the present application provides a vehicle software upgrade method, applied to a vehicle, the method comprising:

[0007] Receiving an update instruction sent by a user, wherein the update instruction is used to instruct the vehicle software to automatically update;

[0008] According to the update instruction, obtaining the timestamp of the update instruction;

[0009] Based on the timestamp, determining a target upgrade time;

[0010] Perform OTA upgrade according to the target upgrade time.

[0011] In combination with the first aspect, in some embodiments, determining the target upgrade time based on the timestamp includes:

[0012] Splitting the timestamp to obtain the hour and minute corresponding to the timestamp;

[0013] Determine the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and a preset hour conversion coefficient;

[0014] Determine the minute corresponding to the timestamp as the minute corresponding to the target upgrade time;

[0015] The target upgrade time is obtained by combining the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time.

[0016] In combination with the first aspect, in some embodiments, determining the time corresponding to the target upgrade time according to the time corresponding to the timestamp and a preset hour conversion coefficient includes:

[0017] The hour corresponding to the timestamp is modulo the hour conversion coefficient and added with 1 to generate the hour corresponding to the target upgrade time.

[0018] In combination with the first aspect, in some embodiments, before receiving the update instruction sent by the user, the method further includes:

[0019] Receiving an upgrade task sent by a cloud device, wherein the upgrade task is used to instruct the vehicle to download an update software package;

[0020] The update software package is downloaded according to the upgrade task, and after the download is completed, an upgrade reminder is sent to the user.

[0021] In combination with the first aspect, in some embodiments, the upgrade task includes an identification of the vehicle, and the method further includes:

[0022] Determine, based on the identifier, whether the timestamp of the update instruction corresponding to the last upgrade task is updated;

[0023] If it is determined that the timestamp of the update instruction corresponding to the last upgrade task is not updated, the upgrade time corresponding to the last upgrade task is determined as the target upgrade time.

[0024] In combination with the first aspect, in some embodiments, performing OTA upgrade according to the target upgrade time includes:

[0025] Countdown according to the target upgrade time;

[0026] After the countdown is completed, obtaining a vehicle status, wherein the vehicle status is used to indicate whether the vehicle is in use;

[0027] If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed for a preset period of time, and an upgrade postponement message is sent to the user.

[0028] In combination with the first aspect, in some embodiments, the method further includes:

[0029] If the vehicle status indicates that the vehicle is not in use, performing a software upgrade according to the update software package.

[0030] In a second aspect, the present application provides a vehicle software upgrade device, comprising:

[0031] A first receiving module, used for receiving an update instruction sent by a user, wherein the update instruction is used for instructing the vehicle software to automatically update;

[0032] An acquisition module, used for acquiring a timestamp of the update instruction according to the update instruction;

[0033] A first determining module, configured to determine a target upgrade time based on the timestamp;

[0034] The upgrade module is used to perform OTA upgrade according to the target upgrade time.

[0035] In conjunction with the second aspect, in some embodiments, the first determining module includes:

[0036] A splitting unit, used for splitting the timestamp to obtain the hour and minute corresponding to the timestamp;

[0037] A first determining unit, configured to determine the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and a preset hour conversion coefficient;

[0038] A second determining unit, configured to determine the minute corresponding to the timestamp as the minute corresponding to the target upgrade time;

[0039] The combining unit is used to combine the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time to obtain the target upgrade time.

[0040] In conjunction with the second aspect, in some embodiments, the first determining unit is specifically configured to:

[0041] The hour corresponding to the timestamp is modulo the hour conversion coefficient and added with 1 to generate the hour corresponding to the target upgrade time.

[0042] In conjunction with the second aspect, in some embodiments, the apparatus further includes:

[0043] A second receiving module, used to receive an upgrade task sent by a cloud device, wherein the upgrade task is used to instruct the vehicle to download an update software package;

[0044] The download sending module is used to download the update software package according to the upgrade task, and send an upgrade reminder to the user after the download is completed.

[0045] In conjunction with the second aspect, in some embodiments, the upgrade task includes an identification of the vehicle, and the device further includes:

[0046] A second determination module is used to determine whether the timestamp of the update instruction corresponding to the last upgrade task is updated according to the identifier;

[0047] The third determination module is used to determine the upgrade time corresponding to the last upgrade task as the target upgrade time if it is determined that the timestamp of the update instruction corresponding to the last upgrade task is not updated.

[0048] In conjunction with the second aspect, in some embodiments, the upgrade module includes:

[0049] A countdown unit, used to count down according to the target upgrade time;

[0050] An acquisition unit, used for acquiring a vehicle status after the countdown is completed, wherein the vehicle status is used to indicate whether the vehicle is in use;

[0051] A deferring unit is used to defer the target upgrade time by a preset time period if the vehicle status indicates that the vehicle is in use, and to send an upgrade deferring message to the user.

[0052] In conjunction with the second aspect, in some embodiments, the upgrade module further includes:

[0053] An upgrading unit is configured to perform a software upgrade according to the update software package if the vehicle status indicates that the vehicle is not in use.

[0054] In a third aspect, the present application provides a vehicle, comprising: a vehicle body, a storage unit disposed in the vehicle body, an electronic control unit, and a communication interface;

[0055] The storage unit stores computer-executable instructions;

[0056] The electronic control unit executes the computer-executable instructions stored in the storage unit to implement the vehicle software upgrade method described in any one of the first aspects.

[0057] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the vehicle software upgrade method described in any one of the first aspects.

[0058] In a fifth aspect, the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the vehicle software upgrade method described in any one of the first aspects.

[0059] The present application provides a vehicle software upgrade method, device, vehicle and storage medium, which receive an update instruction sent by a user, obtain the timestamp of the update instruction according to the update instruction, determine the target upgrade time based on the timestamp, and perform OTA upgrade according to the target upgrade time. Through the above method, the upgrade time is randomized and decentralized, thereby reducing the peak value of high concurrency of the server, reducing the operating cost of the server, and also improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0061] Figure 1 A schematic diagram of the application system architecture of the vehicle software upgrade method provided in the embodiment of the present application;

[0062] Figure 2 A flowchart of a first embodiment of a vehicle software upgrade method provided in an embodiment of the present application;

[0063] Figure 3 A flowchart of a second embodiment of a vehicle software upgrade method provided in an embodiment of the present application;

[0064] Figure 4 A flowchart of a third embodiment of a vehicle software upgrade method provided in an embodiment of the present application;

[0065] Figure 5 A flowchart of a fourth embodiment of a vehicle software upgrade method provided in an embodiment of the present application;

[0066] Figure 6 A flowchart of a fifth embodiment of a vehicle software upgrade method provided in an embodiment of the present application;

[0067] Figure 7 A schematic diagram of the structure of a first embodiment of a vehicle software upgrade device provided in an embodiment of the present application;

[0068] Figure 8 A schematic diagram of the structure of a second embodiment of a vehicle software upgrade device provided in an embodiment of the present application;

[0069] Fig. 9 A schematic diagram of the structure of a third embodiment of a vehicle software upgrade device provided in an embodiment of the present application;

[0070] Fig.10 A schematic diagram of the structure of a fourth embodiment of a vehicle software upgrade device provided in an embodiment of the present application;

[0071] Fig.11A schematic diagram of the structure of a vehicle provided in an embodiment of the present application.

[0072] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0073] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0074] With the advancement of technology, cars are becoming more and more intelligent, and the software upgrades for vehicles are also gradually becoming intelligent. OTA remote download has gradually become a popular technology for vehicles. It is a technology that remotely manages mobile terminal devices and SIM card data through the air interface of mobile communications. OTA can detect the upgrade of the new system of the vehicle online and complete the upgrade by downloading the system upgrade package through a wireless network or a mobile network. In the prior art, when it is detected that the vehicle has an update and upgrade task, the user sets the upgrade time by appointment, or the user authorizes the immediate upgrade. However, during the OTA upgrade process, the upgraded vehicle will establish and maintain communication with the cloud, and continue to exchange information. For example, the cloud sends control instructions to the vehicle side, and the vehicle side reports the upgrade status, results, abnormalities and other data. If the upgrade time is concentrated at a certain moment, there will be a large number of uplink / downlink interaction instructions and server analysis work at that moment. To ensure the smooth upgrade of all vehicles, the server must have sufficient performance to receive and send all instructions, and complete the necessary analysis work in a very short time. However, the performance of the server is limited. In order to cope with high concurrency, additional servers need to be purchased / leased, resulting in increased operating costs. However, during low-concurrency periods, the server is idle, resulting in cost waste and poor user experience.

[0075] In view of the above problems, the present application provides a vehicle software upgrade method, device, vehicle and storage medium, which evenly disperses the high-concurrency moments of vehicle software upgrade into a time period, thereby reducing the peak value and reducing the operating cost of the server. Specifically, the existing method for vehicle software upgrade can be to notify the user after the update is detected in the cloud, and the user can choose to upgrade immediately. The user cannot use the vehicle during the upgrade period, so the immediate upgrade method may cause inconvenience to the user. The user can also make an appointment for the upgrade, and make an appointment for an upgrade time with the vehicle computer. The upgrade will be carried out when the user's appointment time is reached, but this method may cause the upgrade time of multiple vehicles to be at the same time, which will lead to a large number of uplink / downlink interaction instructions and server analysis work at this time, but the performance of the server is limited. In order to cope with high concurrency, additional servers need to be purchased / leased, resulting in increased operating costs. However, in the low-concurrency time period, the server is idle again, resulting in cost waste. In view of these problems, the inventor studied whether it is possible to generate a target upgrade time based on the timestamp authorized by the user when the user authorizes the vehicle to automatically update and upgrade, so as to evenly disperse the high-concurrency moments into a time period, reduce the peak value, and reduce the operating cost of the server. Based on this, the technical solution of the present application is proposed.

[0076] Figure 1 A schematic diagram of the vehicle software upgrade method application system architecture provided in the embodiment of the present application, such as Figure 1 As shown, the system includes a cloud-side OTA management module, a vehicle-side task download module, a vehicle-side user interaction module, a vehicle-side countdown module and a vehicle-side upgrade module, wherein the cloud-side OTA management module is used to create tasks, solve single-vehicle tasks, distribute tasks, and save vehicle-side main controller data; the vehicle-side task download module is used to request tasks and download software packages; the vehicle-side user interaction module is used to display task details, support user command input, and display installation status and results; the vehicle-side countdown module is used to receive the target upgrade time, and notify the upgrade module to start the upgrade when the countdown time is up; the vehicle-side upgrade module is used to control the vehicle main controller software flashing process.

[0077] Optionally, the cloud OTA management module pushes the upgrade task to the vehicle-side task download module, and the vehicle-side task download module automatically downloads the software package. After the download is complete, the vehicle-side user interaction module is notified to prompt the user that there is an updateable task, and guide the user to authorize the upgrade. For automatic upgrades, the upgrade time will be sent to the vehicle-side countdown module, which will count the time. When the time is up, the vehicle-side upgrade module will be notified to perform the software upgrade. Among them, the upgrade time is calculated by the vehicle-side user interaction module based on the timestamp of the user's authorization upgrade.

[0078] This application does not specifically limit the form and type of the physical devices mentioned above.

[0079] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0080] Figure 2 A flow chart of a first embodiment of a vehicle software upgrade method provided in an embodiment of the present application, such as Figure 2 As shown, the method is mainly applied to vehicles, and the method specifically includes:

[0081] S201: receiving an update instruction sent by a user.

[0082] In this step, when there is an upgrade task for the vehicle, the vehicle will download the corresponding update software package according to the upgrade task. After the download is completed, the user will be notified that the vehicle has an update and needs to be authorized by the user. After the user authorizes the update, the vehicle will receive the update instruction sent by the user.

[0083] Specifically, the user may send an update instruction to the vehicle through a user terminal, or may send the instruction directly through a vehicle computer operation, which is not specifically limited in the embodiments of the present application.

[0084] For example, the user can directly select to authorize the upgrade in the vehicle's control interface or system. The vehicle's upgrade process can also be remotely controlled through an application on a terminal device. The user can find the upgrade option on the application and send an instruction to authorize the upgrade.

[0085] On the vehicle's central control screen, there is usually a special menu or option for software updates. Users can enter the menu through the touch screen, knob, button, etc., and then choose to authorize the update.

[0086] Some vehicles provide a remote service platform, and users can send instructions to the vehicle through cloud services. Users can log in to the online service platform provided by the vehicle manufacturer or operate through a dedicated mobile phone application.

[0087] Optionally, authorization can be achieved through voice control systems, where the user can authorize automatic software updates through verbal commands. This method usually requires the vehicle to be equipped with appropriate voice recognition technology and network connectivity.

[0088] It should be noted that the update instruction is used to instruct the vehicle software to update automatically.

[0089] Optionally, the update instruction can also be used to instruct the vehicle to update immediately. When the update instruction instructs the vehicle to update immediately, the vehicle is directly upgraded according to the downloaded update software package. The update instruction can also be used to instruct the vehicle to schedule an update. When the update instruction instructs the vehicle to schedule an update, the update instruction also includes the upgrade time scheduled by the user. When the user's scheduled time is reached, the vehicle wakes up for the upgrade and update.

[0090] S202: According to the update instruction, obtain the timestamp of the update instruction.

[0091] In this step, in order not to affect the user's use of the car and to reduce the high concurrency of the cloud device at a certain moment, after receiving the user's update instruction, the timestamp of the update instruction is obtained.

[0092] The specific implementation of obtaining the timestamp can be achieved in any of the following ways:

[0093] 1. Logging: The vehicle system can generate log entries each time an OTA update starts or completes, recording the timestamp of the user's operation. These logs can be stored in the vehicle's storage system, so the timestamp of the user's authorized update can be found through the timestamp of the user's operation in the log record in the storage system.

[0094] 2. Cloud storage: To ensure data backup and security, and to allow vehicle manufacturers to remotely access vehicle update data, the vehicle uploads update-related events and timestamps to cloud storage. The timestamp of the update instruction can be obtained through cloud storage.

[0095] 3. Local storage: Timestamp information can also be stored locally in the vehicle's control unit or internal storage, ensuring that updated timestamp information is still available even without a network connection.

[0096] S203: Determine the target upgrade time based on the timestamp.

[0097] In this step, since the timestamps of the update instructions are randomly dispersed, the time of the update instructions can be converted into a certain moment in the preset upgrade period as the target upgrade time. Therefore, the target upgrade time is also randomly dispersed, which can reduce the problem of increased operating costs caused by high concurrency compared to fixed automatic time upgrades.

[0098] Specifically, the timestamp is split to obtain the hour and minute corresponding to the timestamp, the modulus of one-third of the time corresponding to the timestamp is taken and 1 is added to generate the hour corresponding to the target upgrade time, the minute corresponding to the timestamp is determined as the minute corresponding to the target upgrade time, and the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time are combined to obtain the target upgrade time.

[0099] S204: Perform OTA upgrade according to the target upgrade time.

[0100] In this step, after the target upgrade time is obtained, the vehicle performs OTA upgrade when the target upgrade time is reached.

[0101] Specifically, a countdown is performed according to the target upgrade time, and after the countdown is completed, the vehicle status is obtained. If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed for a preset period of time, and an upgrade postponement message is sent to the user; if the vehicle status indicates that the vehicle is not in use, the software is upgraded according to the update software package.

[0102] Optionally, the vehicle status obtained may be in any one or more of the following forms:

[0103] Vehicle driving status, vehicle speed, vehicle gear, charging status, vehicle high voltage status, door lock status, seat sensor status, etc.

[0104] 1. Vehicle driving status: If the vehicle is in a driving state (such as "driving" or "drive mode"), then it is obvious that the vehicle is being used.

[0105] 2. Vehicle speed: If the vehicle speed is greater than zero (within a certain error range), it indicates that the vehicle is moving and is likely to be in use. However, it is also necessary to pay attention to the situation when the engine is idling or coasting at low speed when it is stationary. At this time, although the speed is close to zero, the vehicle may still be in use.

[0106] 3. Vehicle gear position: Gear position information is also an important reference for determining whether the vehicle is in use. If the gear position is not in "park" (P) or "neutral" (N), but in "forward" (D), "reverse" (R) or other driving gear positions, then the vehicle is likely to be driven.

[0107] 4. Charging status: If the vehicle is charging and is in other non-use states (such as doors closed, engine off, etc.), it may indicate that the vehicle is not currently in use.

[0108] 5. Vehicle high voltage status: If the high voltage system is activated, the vehicle is charging, driving, or preparing to drive.

[0109] 6. Door lock status: The door lock status can indirectly reflect the vehicle usage. If all doors are locked and not opened for a long time, it may indicate that the vehicle is not currently in use. However, this also needs to take into account that the owner may have only left the vehicle for a short time without turning off the engine, so this status needs to be judged in conjunction with other statuses.

[0110] 7. Seat sensor status: The seat sensor can detect whether there is a passenger in the seat. If the seat sensor shows that there is a passenger and other vehicle systems are also active (such as engine running, audio playing, etc.), the vehicle is being used.

[0111] The above data can be obtained in the following ways:

[0112] 1. Vehicle driving status: obtained through the on-board diagnostics (OBD) system, vehicle application or third-party management platform.

[0113] 2. Vehicle speed: obtained through the OBD system, vehicle application or vehicle dashboard display.

[0114] 3. Vehicle gear position: obtained through the OBD system, vehicle application or vehicle dashboard display.

[0115] 4. Charging status: obtained through the in-vehicle application, charging pile display or charging gun indicator light.

[0116] 5. Vehicle high-voltage status: usually needs to be obtained through professional diagnostic tools or systems.

[0117] 6. Door lock status: obtained through the vehicle's central control system, remote control key or physical inspection.

[0118] 7. Seat sensor status: obtained through the in-vehicle application (if supported) or physical inspection.

[0119] The vehicle software upgrade method provided in this embodiment receives an update instruction sent by a user, obtains a timestamp of the update instruction according to the update instruction, determines a target upgrade time based on the timestamp, and performs an OTA upgrade according to the target upgrade time. Through the above method, the upgrade time is randomized and decentralized, thereby reducing the peak value of high concurrency of the server, reducing the operating cost of the server, and also improving the user experience.

[0120] Figure 3 A flow chart of a second embodiment of the vehicle software upgrade method provided in the present application is shown in FIG. Figure 3 As shown, based on the above embodiment, step S203 specifically includes:

[0121] S301: Split the timestamp to obtain the hour and minute corresponding to the timestamp.

[0122] S302: Determine the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and a preset hour conversion coefficient.

[0123] S303: Determine the minute corresponding to the timestamp as the minute corresponding to the target upgrade time.

[0124] S304: Combine the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time to obtain the target upgrade time.

[0125] After obtaining the timestamp of the update instruction, since the timestamp is randomly dispersed, the target upgrade time can be generated according to the timestamp conversion, that is, the generated target upgrade time is also randomly dispersed, which can solve the problem of high concurrency of cloud devices at a certain moment.

[0126] Specifically, the timestamp can be converted to the target upgrade time using the following formula:

[0127]

[0128] Among them, A is the hour of the target upgrade time, B is the minute of the target upgrade time, C is the second of the target upgrade time, H is the hour of the timestamp, and M is the minute of the timestamp. is the hour conversion coefficient, which can be 3, and % represents the remainder.

[0129] For example, it is necessary to pre-set the upgrade period, such as 1:00:00-3:59:00. After obtaining the timestamp, the hour conversion coefficient is set according to the above formula, and the timestamp is converted to a moment between 1:00:00-3:59:00 as the target upgrade time. For example, if the timestamp is 8:15:9 and the hour conversion coefficient is 3, the target upgrade time is 03:15:00.

[0130] Optionally, the timestamp can be converted into a randomly distributed target upgrade time window through an algorithm. Taking the upgrade period of 1:00:00-3:59:00 as an example, first, midnight is used as the base time, the time offset is calculated, the offset is mapped to a random point in the upgrade period, and a random number of minutes is generated in the upgrade period to obtain the target upgrade time.

[0131] A distributed processing algorithm can also be used to implement decentralized processing of upgrade time based on timestamps, such as a consistent hashing algorithm, a distributed cache consistency algorithm, a distributed task scheduling algorithm, and the like.

[0132] The vehicle software upgrade method provided in this embodiment splits the timestamp to obtain the hour and minute corresponding to the timestamp, determines the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and the pre-set hour conversion coefficient, determines the minute corresponding to the timestamp as the minute corresponding to the target upgrade time, and combines the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time to obtain the target upgrade time. Since the time when the user authorizes the vehicle upgrade is random and scattered, the target upgrade time is mapped to any time within a fixed time period for upgrading according to the time when the user authorizes the upgrade, thereby realizing the randomization and decentralization of the target upgrade time. Compared with the fixed automatic time upgrade, the problem of increased operating costs caused by high concurrency is reduced.

[0133] Figure 4 A flow chart of a third embodiment of the vehicle software upgrade method provided in the present application is shown in FIG. Figure 4 As shown, based on the above embodiments, the method further includes:

[0134] S401: Receive an upgrade task sent by a cloud device.

[0135] S402: Download the update software package according to the upgrade task, and send an upgrade reminder to the user after the download is complete.

[0136] Before the vehicle OTA upgrade, the cloud determines that the vehicle has an upgraded version based on the software data information reported by the vehicle, then creates an upgrade task and sends it to the vehicle. The vehicle receives the upgrade task sent by the cloud device.

[0137] The vehicle will download the update software package according to the upgrade task, specifically from the cloud device. During the download, the vehicle will maintain network connection and monitor the download progress. After the download is complete, the user will be prompted to authorize the upgrade.

[0138] For the security of data, a secure connection is established between the vehicle and cloud devices through wireless communication technologies such as 4G / 5G networks or Wi-Fi.

[0139] Optionally, an upgrade reminder may be sent to the user via a pop-up window on the vehicle computer's display to prompt the user that an upgrade task has been completed. The reminder may also be sent to the user's terminal device and displayed to the user through the terminal device interface. The reminder may also be sent via voice to prompt the user that an update task has been completed for the vehicle computer. The user may instruct the vehicle computer to authorize the upgrade through voice interaction with the vehicle computer, or may authorize the upgrade through manual operation.

[0140] The vehicle software upgrade method provided in this embodiment receives an upgrade task sent by a cloud device, downloads the update software package according to the upgrade task, and sends an upgrade reminder to the user after the download is completed. By notifying the user after the download is completed, it avoids the situation where the user authorizes the upgrade but the download is not completed and the upgrade cannot be performed, and it also saves the user's time and improves the upgrade efficiency.

[0141] Figure 5 A flowchart of a fourth embodiment of a vehicle software upgrade method provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, based on the above embodiments, the method further includes:

[0142] S501: Determine, according to the identifier, whether the timestamp of the update instruction corresponding to the last upgrade task is updated.

[0143] S502: If it is determined that the timestamp of the update instruction corresponding to the last upgrade task is not updated, the upgrade time corresponding to the last upgrade task is determined as the target upgrade time.

[0144] After the vehicle receives the upgrade task sent by the cloud device, in order to facilitate the user and improve the upgrade efficiency, the timestamp of the update instruction sent by the user can also be judged to determine whether the user has changed the timestamp of the update instruction after the last upgrade task was completed, that is, whether the user turned off the automatic upgrade function after the last upgrade task was completed. If there is no change, it means that the user did not change the automatic upgrade function after the last upgrade task authorized the automatic upgrade. In this case, the upgrade time of the last upgrade task will be determined as the target upgrade time.

[0145] Optionally, if the user changes the timestamp of the update instruction after the last upgrade task is completed, that is, the user turns off the automatic upgrade function after the last upgrade task is completed, the target upgrade time is determined according to the method of determining the target upgrade time in the above embodiment.

[0146] It should be noted that the way for the user to change the timestamp of the update instruction is through the automatic upgrade authorization switch. After the user turns on the automatic upgrade authorization switch, a timestamp will be generated. If the user turns off the automatic upgrade authorization switch and then turns on the automatic upgrade authorization switch again after a period of time, a new timestamp will be generated.

[0147] The vehicle software upgrade method provided in this embodiment determines whether the timestamp of the update instruction corresponding to the last upgrade task has been updated according to the identifier. If it is determined that the timestamp of the update instruction corresponding to the last upgrade task has not been updated, the upgrade time corresponding to the last upgrade task is determined as the target upgrade time. Through the above method, it is avoided that each upgrade task is upgraded through user authorization, and the upgrade and update are automatically completed according to the upgrade time corresponding to the latest authorization, which not only improves the upgrade efficiency, but also saves user time and is convenient for users.

[0148] Figure 6 A flowchart of a fifth embodiment of a vehicle software upgrade method provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, based on the above embodiments, step S204 specifically includes:

[0149] S601: Countdown according to the target upgrade time.

[0150] S602: After the countdown is completed, the vehicle status is obtained.

[0151] S603: If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed by a preset time period, and an upgrade postponement message is sent to the user.

[0152] S604: If the vehicle status indicates that the vehicle is not in use, perform a software upgrade according to the update software package.

[0153] After the vehicle generates a target upgrade time, it will count down until the countdown is completed and start preparing for the upgrade. In order to complete the upgrade efficiently, after the countdown is completed, the current vehicle status of the vehicle is obtained, where the vehicle status is used to indicate whether the vehicle is in use.

[0154] Since the vehicle upgrade needs to be performed when the vehicle is not in use, when the upgrade time arrives, the vehicle status is used to determine whether the vehicle is in use. If the vehicle is not in use, the vehicle is woken up for the upgrade. If the vehicle is in use, in order to reduce the impact on vehicle use and passenger experience, improve the safety and reliability of OTA updates, and ensure the continuous operation efficiency of the vehicle and user satisfaction. The target upgrade time is postponed for a preset period of time. The postponed time and reason are sent to the user.

[0155] Exemplarily, the preset duration may be 24 hours or 48 hours, that is, it may be the same time of any future day, and the present application embodiment does not make any specific limitation thereto.

[0156] It should be noted that the method for determining the vehicle status in this embodiment is the same as the method for determining the vehicle status in the aforementioned embodiment, and will not be repeated here.

[0157] The vehicle software upgrade method provided in this embodiment counts down according to the target upgrade time, and obtains the vehicle status after the countdown is completed. If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed for a preset period of time, and an upgrade postponement message is sent to the user; if the vehicle status indicates that the vehicle is not in use, the software is upgraded according to the update software package. Upgrade adjustment based on the vehicle status ensures the upgrade quality and thus the user experience, and avoids upgrading when the user is in use, which delays the user's use of the vehicle.

[0158] Figure 7 This is a structural diagram of a first embodiment of a vehicle software upgrade device provided in an embodiment of the present application, such as Figure 7 As shown, the vehicle software upgrade device 700 includes:

[0159] The first receiving module 701 is used to receive an update instruction sent by a user, where the update instruction is used to instruct the vehicle software to automatically update.

[0160] The acquisition module 702 is used to acquire the timestamp of the update instruction according to the update instruction.

[0161] The first determining module 703 is used to determine the target upgrade time based on the timestamp.

[0162] The upgrade module 704 is used to perform OTA upgrade according to the target upgrade time.

[0163] Figure 8 This is a structural diagram of a second embodiment of a vehicle software upgrade device provided in an embodiment of the present application, such as Figure 8 As shown, based on the above embodiment, the first determining module 703 includes:

[0164] The splitting unit 801 is used to split the timestamp to obtain the hour and minute corresponding to the timestamp.

[0165] The first determining unit 802 is used to determine the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and a preset hour conversion coefficient.

[0166] The second determining unit 803 is configured to determine the minute corresponding to the timestamp as the minute corresponding to the target upgrade time.

[0167] The combining unit 804 is used to combine the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time to obtain the target upgrade time.

[0168] Optionally, the first determining unit 802 is specifically configured to:

[0169] Take the modulus of the hour corresponding to the timestamp according to the hour conversion coefficient and add 1 to generate the hour corresponding to the target upgrade time.

[0170] Fig. 9 The structural diagram of the third embodiment of the vehicle software upgrade device provided in the embodiment of the present application is shown in Figure 9. Based on the above embodiment, the vehicle software upgrade device 700 further includes:

[0171] The second receiving module 901 is used to receive an upgrade task sent by a cloud device, where the upgrade task is used to instruct the vehicle to download an update software package.

[0172] The download sending module 902 is used to download the update software package according to the upgrade task, and send an upgrade reminder to the user after the download is completed.

[0173] The second determining module 903 is used to determine whether the timestamp of the update instruction corresponding to the last upgrade task is updated according to the identifier.

[0174] The third determining module 904 is configured to determine the upgrade time corresponding to the last upgrade task as the target upgrade time if it is determined that the timestamp of the update instruction corresponding to the last upgrade task is not updated.

[0175] Fig.10 This is a structural diagram of a fourth embodiment of a vehicle software upgrade device provided in an embodiment of the present application, such as Fig.10 As shown, based on the above embodiments, the upgrade module 704 specifically includes:

[0176] The countdown unit 1001 is used to count down according to the target upgrade time.

[0177] The acquisition unit 1002 is used to acquire the vehicle status after the countdown is completed, and the vehicle status is used to indicate whether the vehicle is in use.

[0178] The postponement unit 1003 is used to postpone the target upgrade time by a preset time period if the vehicle status indicates that the vehicle is in use, and send an upgrade postponement message to the user.

[0179] The upgrading unit 1004 is configured to perform a software upgrade according to the update software package if the vehicle status indicates that the vehicle is not in use.

[0180] The vehicle software upgrade device provided in the above embodiment is used to execute the vehicle software upgrade method in any of the above method embodiments. Its implementation principle and technical effect are similar and will not be repeated here.

[0181] Fig.11 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application, such as Figure 1 As shown, it includes: a vehicle body 1100, a storage unit 1101 arranged in the vehicle body, an electronic control unit 1102, and a communication interface 1103;

[0182] The storage unit 1101 stores computer-executable instructions;

[0183] The electronic control unit 1102 executes the computer-executable instructions stored in the storage unit 1101 to implement the vehicle software upgrade method in any of the aforementioned embodiments.

[0184] The communication interface 1103 is used to implement data communication with the cloud server.

[0185] An embodiment of the present application further provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method in any one of the embodiments.

[0186] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0187] Optionally, a readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0188] An embodiment of the present application also provides a computer program product, which includes a computer program. The computer program is stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium. When at least one processor executes the computer program, the technical solution provided by any of the above method embodiments can be implemented.

[0189] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0190] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A vehicle software upgrade method, It is characterized in that Applied to a vehicle, the method comprises: Receiving an update instruction sent by a user, wherein the update instruction is used to instruct the vehicle software to automatically update; According to the update instruction, obtaining the timestamp of the update instruction; Based on the timestamp, determining a target upgrade time; Perform an over-the-air OTA upgrade according to the target upgrade time.

2. The method according to claim 1, It is characterized in that The determining the target upgrade time based on the timestamp includes: Splitting the timestamp to obtain the hour and minute corresponding to the timestamp; Determine the hour corresponding to the target upgrade time according to the hour corresponding to the timestamp and a preset hour conversion coefficient; Determine the minute corresponding to the timestamp as the minute corresponding to the target upgrade time; The target upgrade time is obtained by combining the hour corresponding to the target upgrade time and the minute corresponding to the target upgrade time.

3. The method according to claim 2, It is characterized in that The determining the time corresponding to the target upgrade time according to the time corresponding to the timestamp and a preset hour conversion coefficient includes: The hour corresponding to the timestamp is modulo the hour conversion coefficient and added with 1 to generate the hour corresponding to the target upgrade time.

4. The method according to claim 1, It is characterized in that Before receiving the update instruction sent by the user, the method further includes: Receiving an upgrade task sent by a cloud device, wherein the upgrade task is used to instruct the vehicle to download an update software package; The update software package is downloaded according to the upgrade task, and after the download is completed, an upgrade reminder is sent to the user.

5. The method according to claim 4, It is characterized in that The upgrade task includes an identification of the vehicle, and the method further includes: Determine, based on the identifier, whether the timestamp of the update instruction corresponding to the last upgrade task is updated; If it is determined that the timestamp of the update instruction corresponding to the last upgrade task is not updated, the upgrade time corresponding to the last upgrade task is determined as the target upgrade time.

6. The method according to claim 1, It is characterized in that The performing OTA upgrade according to the target upgrade time includes: Countdown according to the target upgrade time; After the countdown is completed, obtaining a vehicle status, wherein the vehicle status is used to indicate whether the vehicle is in use; If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed for a preset period of time, and an upgrade postponement message is sent to the user.

7. The method according to claim 6, It is characterized in that The method further comprises: If the vehicle status indicates that the vehicle is not in use, performing a software upgrade according to the update software package.

8. A vehicle software upgrade device, It is characterized in that include: A first receiving module, used for receiving an update instruction sent by a user, wherein the update instruction is used for instructing the vehicle software to automatically update; An acquisition module, used for acquiring a timestamp of the update instruction according to the update instruction; A first determining module, configured to determine a target upgrade time based on the timestamp; The upgrade module is used to perform an over-the-air OTA upgrade according to the target upgrade time.

9. A vehicle, It is characterized in that include: A vehicle body, a storage unit disposed in the vehicle body, an electronic control unit, and a communication interface; The storage unit stores computer-executable instructions; The electronic control unit executes the computer-executable instructions stored in the storage unit to implement the vehicle software upgrade method according to any one of claims 1 to 7.

10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the vehicle software upgrade method according to any one of claims 1 to 7.

11. A computer program product, It is characterized in that It comprises a computer program, which is used to implement the vehicle software upgrade method according to any one of claims 1 to 7 when executed by a processor.

Citation Information

Cited By

  • Vehicle software upgrade method, system and device, and storage medium

    WO2026045725A1