Vehicle software upgrading method and device, equipment and storage medium
By determining the target upgrade time in the cloud device and sending it to the vehicle, and determining whether to upgrade based on the vehicle status, the problem of high concurrency and waste of servers during vehicle software upgrade is solved, the upgrade efficiency and user experience are improved, and the system stability is enhanced .
Patent Information
- Application Number
- CN202411196822.1
- 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
In the prior art, when upgrading vehicle software, the upgrade time selected by the user is too concentrated, resulting in high concurrency of the server, which cannot be effectively dealt with, affecting the user experience, and the server is idle during the low concurrency period, causing waste of costs.
Receive upgrade instructions sent by vehicles through cloud devices, obtain the list of vehicles to be upgraded, the collection of vehicle information and the collection of upgrade information, determine the target upgrade time based on these data, and send the target upgrade time to the vehicle. The vehicle obtains the status after the countdown is over, If it is not used, perform OTA upgrades to avoid upgrading during high-frequency car use periods and balance system resource usage.
It reduces the impact of upgrades on users' daily car use, avoids server overload or upgrade failure, improves overall upgrade efficiency and success rate, predicts and identifies potential problems, and enhances the stability and reliability of the vehicle system.
Smart Images

Figure CN119065692A_ABST
Abstract
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, equipment 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 modules (SIM) data through the air interface of mobile communications. OTA can detect the upgrade of new vehicle systems online and complete the upgrade by downloading system upgrade packages through wireless networks or mobile networks.
[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 the immediate upgrade.
[0004] However, if the upgrade time selected by the user is relatively concentrated, the server cannot effectively cope with high concurrency, and immediate updates will also affect the user's 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, equipment and storage medium to solve the problem of how to efficiently implement vehicle software upgrade.
[0006] In a first aspect, the present application provides a vehicle software upgrade method, which is applied to a cloud device, and the method comprises:
[0007] Receiving an upgrade instruction sent by a vehicle, wherein the upgrade instruction is used to instruct the vehicle software to automatically upgrade;
[0008] According to the upgrade instruction, a list of vehicles to be upgraded, a vehicle usage information set and an upgrade information set of the vehicles are acquired, wherein the vehicle usage information set includes vehicle usage data of a plurality of the vehicles, and the upgrade information set includes upgrade data of a plurality of the vehicles;
[0009] Determining a target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set, and the upgrade information set;
[0010] The target upgrade time is sent to the vehicle, so that the vehicle performs OTA upgrade at the target upgrade time.
[0011] In combination with the first aspect, in some embodiments, determining the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set, and the upgrade information set includes:
[0012] According to the list of vehicles to be upgraded, the number of vehicles to be upgraded at each moment in a preset time period is counted, and according to the number of vehicles to be upgraded corresponding to each moment, a first recommendation index is determined for each moment;
[0013] According to the vehicle usage information set, counting the vehicle usage probability at each moment in the preset time period, and determining a second recommendation index for each moment according to the vehicle usage probability corresponding to each moment;
[0014] According to the upgrade information set, counting the number of upgrades at each moment in the preset time period, and determining a third recommendation index for each moment according to the number of upgrades corresponding to each moment;
[0015] For each moment, the target upgrade time is determined based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment.
[0016] In combination with the first aspect, in some embodiments, determining the target upgrade time based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment includes:
[0017] For each moment, weighted calculation is performed on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment to obtain a recommendation value corresponding to the moment;
[0018] The time corresponding to the maximum recommended value is determined as the target upgrade time.
[0019] In combination with the first aspect, in some embodiments, the method further includes:
[0020] According to the upgrade information set, counting the number of upgrade postponements at each moment in the preset time period;
[0021] Correspondingly, determining the third recommendation index for each moment according to the number of upgrades corresponding to each moment includes:
[0022] A third recommendation index is determined for each moment according to the number of upgrades corresponding to each moment and the number of upgrade deferrals at each moment.
[0023] In combination with the first aspect, in some embodiments, the method further includes:
[0024] Receiving the upgrade postponement number sent by the vehicle;
[0025] If the number of upgrade deferrals reaches a preset deferral threshold, the target upgrade time is re-determined and the new target upgrade time is sent to the vehicle.
[0026] In a second aspect, the present application provides a vehicle software upgrade method, applied to a vehicle, the method comprising:
[0027] Receive the target upgrade time sent by the cloud device;
[0028] Counting down according to the target upgrade, and obtaining a vehicle status after the countdown ends, wherein the vehicle status is used to indicate whether the vehicle is in use;
[0029] If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed by a preset time period, and the number of upgrade postponements is cumulatively counted;
[0030] The upgrade postponement number is sent to the cloud device.
[0031] In conjunction with the second aspect, in some embodiments, the method further includes:
[0032] If the vehicle status indicates that the vehicle is not in use, an OTA upgrade is performed.
[0033] In a third aspect, the present application provides a vehicle software upgrade device, comprising:
[0034] A first receiving module, used for receiving an upgrade instruction sent by a vehicle, wherein the upgrade instruction is used for instructing the vehicle software to automatically upgrade;
[0035] an acquisition module, configured to acquire, according to the upgrade instruction, a list of vehicles to be upgraded, a vehicle usage information set and an upgrade information set of the vehicles, wherein the vehicle usage information set includes vehicle usage data of a plurality of the vehicles, and the upgrade information set includes upgrade data of a plurality of the vehicles;
[0036] A determination module, configured to determine a target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set;
[0037] The first sending module is used to send the target upgrade time to the vehicle, so that the vehicle performs OTA upgrade at the target upgrade time.
[0038] In conjunction with the third aspect, in some embodiments, the determining module includes:
[0039] A first setting unit is used to count the number of vehicles to be upgraded at each moment in a preset time period according to the list of vehicles to be upgraded, and determine a first recommendation index for each moment according to the number of vehicles to be upgraded corresponding to each moment;
[0040] A second setting unit is used to count the probability of using the vehicle at each moment in the preset time period according to the vehicle use information set, and determine a second recommendation index for each moment according to the probability of using the vehicle corresponding to each moment;
[0041] A third setting unit, configured to count the number of upgrades at each moment in the preset period according to the upgrade information set, and determine a third recommendation index for each moment according to the number of upgrades corresponding to each moment;
[0042] The determination unit is used to determine the target upgrade time for each moment based on the first recommendation index, the second recommendation index and the third recommendation index corresponding to the moment.
[0043] In conjunction with the third aspect, in some embodiments, the determining unit includes:
[0044] A calculation subunit, configured to perform weighted calculation on the first recommendation index, the second recommendation index and the third recommendation index corresponding to each moment, to obtain a recommendation value corresponding to the moment;
[0045] The determination subunit is used to determine the time corresponding to the maximum recommended value as the target upgrade time.
[0046] In conjunction with the third aspect, in some embodiments, the determining module further includes:
[0047] A counting unit, configured to count the number of upgrade postponements at each moment in the preset time period according to the upgrade information set;
[0048] Accordingly, the third setting unit includes:
[0049] The setting subunit is used to determine a third recommendation index for each moment according to the number of upgrades corresponding to each moment and the number of upgrade deferrals at each moment.
[0050] In conjunction with the third aspect, in some embodiments, the device further includes:
[0051] A second receiving module is used to receive the upgrade postponement number sent by the vehicle;
[0052] The second sending module is used to redetermine the target upgrade time if the number of upgrade postponements reaches a preset postponement threshold, and send the new target upgrade time to the vehicle.
[0053] In a fourth aspect, the present application provides a vehicle software upgrade device, comprising:
[0054] A receiving module, used to receive the target upgrade time sent by the cloud device;
[0055] An acquisition module, used for performing a countdown according to the target upgrade, and acquiring a vehicle status after the countdown ends, wherein the vehicle status is used to indicate whether the vehicle is in use;
[0056] a postponement module, configured to postpone the target upgrade time by a preset time period if the vehicle status indicates that the vehicle is in use, and to accumulate and count the number of upgrade postponements;
[0057] A sending module is used to send the upgrade postponement number to the cloud device.
[0058] In conjunction with the fourth aspect, in some embodiments, the device further includes:
[0059] An upgrade module is used to perform an OTA upgrade if the vehicle status indicates that the vehicle is not in use.
[0060] In a fifth aspect, the present application provides a cloud device, comprising: a processor, and a memory and a communication interface communicatively connected to the processor;
[0061] The memory stores computer-executable instructions;
[0062] The processor executes the computer-executable instructions stored in the memory to implement the vehicle software upgrade method described in any one of the first aspects.
[0063] In a sixth 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;
[0064] The storage unit stores computer-executable instructions;
[0065] 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 second aspects.
[0066] In a seventh aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by a processor, they are used to implement the vehicle software upgrade method described in any one of the aspects.
[0067] In an eighth 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 aspects.
[0068] The vehicle software upgrade method, device, equipment and storage medium provided by the present application, the cloud device receives the upgrade instruction sent by the vehicle, and according to the upgrade instruction, obtains the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set of the vehicle, and then determines the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set, and finally sends the target upgrade time to the vehicle. The vehicle counts down according to the target upgrade, and after the countdown ends, the vehicle status is obtained. If the vehicle status indicates that the vehicle is not in use, an OTA upgrade is performed. Through the above method, the user's high-frequency vehicle use period is avoided for upgrading, which can minimize the impact of the upgrade on the user's daily use of the vehicle, and the upgrade is arranged according to the list of vehicles to be upgraded, which can balance the use of system resources, avoid server overload or upgrade failure caused by the simultaneous upgrade of a large number of vehicles during peak hours, and can improve the overall upgrade efficiency and success rate. Based on the upgrade information set, it is possible to predict and identify problems or risk points that may occur during the upgrade process, and take measures in advance to prevent and respond, which helps to enhance the stability and reliability of the vehicle system. BRIEF DESCRIPTION OF THE DRAWINGS
[0069] 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.
[0070] Figure 1 A schematic diagram of the application system architecture of the vehicle software upgrade method provided in the embodiment of the present application;
[0071] Figure 2 A flowchart of a first embodiment of a vehicle software upgrade method provided in an embodiment of the present application;
[0072] Figure 3 A flowchart of a second embodiment of a vehicle software upgrade method provided in an embodiment of the present application;
[0073] Figure 4 A flowchart of a third embodiment of a vehicle software upgrade method provided in an embodiment of the present application;
[0074] Figure 5 A schematic diagram of the structure of a first embodiment of a vehicle software upgrade device provided in an embodiment of the present application;
[0075] Figure 6 A schematic diagram of the structure of a second embodiment of a vehicle software upgrade device provided in an embodiment of the present application;
[0076] Figure 7 A schematic diagram of the structure of a third embodiment of a vehicle software upgrade device provided in an embodiment of the present application;
[0077] Figure 8A schematic diagram of the structure of a fourth embodiment of a vehicle software upgrade device provided in an embodiment of the present application;
[0078] Fig. 9 A schematic diagram of the structure of a cloud device provided in an embodiment of the present application;
[0079] Fig.10 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application.
[0080] 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
[0081] 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.
[0082] 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 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.
[0083] In response to the above problems, the present application provides a vehicle software upgrade method, device, equipment and storage medium, which realizes efficient vehicle software upgrade. Specifically, when it is detected that the vehicle has an update and upgrade task, the user usually makes an appointment to set the upgrade time, or the user authorizes an immediate upgrade. However, during the OTA upgrade process, the upgraded vehicle will establish and maintain communication with the cloud, and continuously exchange information, which will cause the cloud server to be in a high concurrency state at a certain moment. In order to cope with high concurrency, it is necessary to purchase / lease additional servers, resulting in increased operating costs. However, during the low concurrency period, the server is idle again, resulting in a waste of cost and a poor user experience. Taking these issues into consideration, the inventor studied whether it is possible to detect that the vehicle has an update task in the cloud, and after the user authorizes the automatic upgrade, the target upgrade time is determined according to the performance of the cloud server, the user's vehicle information, and the historical OTA upgrade information, thereby achieving efficient vehicle software upgrades. Based on this, the technical solution of the present application is proposed.
[0084] 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.
[0085] Optionally, the cloud-side 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 down. When the time is up, the vehicle-side upgrade module will be notified to perform the software upgrade. Among them, the upgrade time is determined by the cloud-side OTA management module based on the vehicle-side user interaction module reporting that the user has turned on the automatic upgrade to the cloud-side OTA management module, and the target upgrade time is obtained through multi-dimensional analysis and sent to the vehicle.
[0086] This application does not specifically limit the form and type of the physical devices mentioned above.
[0087] 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.
[0088] 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 specifically includes:
[0089] S201: The cloud device receives an upgrade instruction sent by the vehicle.
[0090] 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 complete, the user will be notified that the vehicle has an update and needs to authorize the update. After the user authorizes the update, the vehicle will send an upgrade instruction to the cloud device.
[0091] Specifically, the user can authorize the update to the vehicle through the user terminal, and then the vehicle sends the upgrade instruction to the cloud device. The user can also directly authorize through the vehicle computer operation, and then the vehicle sends the upgrade instruction to the cloud device. The embodiments of this application do not make specific limitations.
[0092] For example, the user can directly select the authorized upgrade in the vehicle's control interface or system. The vehicle's upgrade process can also be remotely controlled through the terminal device's application. The user can find the upgrade option on the application, select the upgrade method, and then the vehicle responds to the user's operation and generates a corresponding upgrade instruction and sends it to the cloud device.
[0093] Optionally, there is usually a special menu or option for software updates on the vehicle's central control display. The user can enter the menu through a touch screen, knob, button, etc., and then choose to authorize the update.
[0094] Some vehicles provide a remote service platform, and users can send authorization 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.
[0095] 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.
[0096] It should be noted that the upgrade instruction is used to instruct the vehicle software to upgrade automatically.
[0097] Optionally, the upgrade instruction can also be used to instruct the vehicle to upgrade immediately. When the upgrade instruction instructs the vehicle to upgrade immediately, the vehicle is upgraded directly according to the downloaded update software package. The upgrade instruction can also be used to instruct the vehicle to make an appointment for an upgrade. When the upgrade instruction instructs the vehicle to make an appointment for an upgrade, the upgrade instruction also includes the upgrade time scheduled by the user. When the time scheduled by the user is reached, the vehicle wakes up for the upgrade.
[0098] S202: The cloud device obtains a list of vehicles to be upgraded, a vehicle usage information set, and an upgrade information set according to the upgrade instruction.
[0099] In this step, in order to achieve accurate scheduling, improve the efficiency of vehicle upgrades, not affect user vehicle use, and balance cloud device resources, after receiving the upgrade instruction sent by the vehicle, the vehicle usage information set and upgrade information set of the vehicle can be obtained, and the list of vehicles to be upgraded can also be obtained. Among them, the vehicle usage information set includes the vehicle usage data of multiple vehicles, and the upgrade information set includes the upgrade data of multiple vehicles.
[0100] Specifically, the cloud device can communicate with multiple vehicles, and thus can manage multiple vehicles. The vehicles will report vehicle information in real time, such as vehicle model, software version, current status, etc. The vehicle reports its own status to the cloud device regularly or in real time through the built-in communication module (such as SIM module, Wi-Fi module, etc.), including software version, hardware status, usage, etc. The cloud device can update the list of vehicles to be upgraded in real time based on the reported information. The cloud device can establish a database to store the list of vehicles to be upgraded, and the cloud device can retrieve the list of vehicles currently in the state of upgrading from the database by writing query statements.
[0101] Vehicles are generally equipped with driving data recording systems (such as OBD systems), which can record the vehicle's driving trajectory, speed, fuel consumption and other information in real time. Through the communication between the vehicle and the cloud device, these data can be uploaded to the cloud to form a user's car usage data set. The cloud device can then obtain the user's car usage information set within a preset period of time from the user's car usage data set, where the obtained car usage information set includes the number of times the user used the car and the timestamp of each car usage.
[0102] To obtain the upgrade information set, you can use any of the following methods:
[0103] 1. Cloud device log records:
[0104] The cloud device will record detailed log information during each OTA upgrade process, including upgrade time, upgrade version, upgrade result (success / failure), etc. By querying these log records, you can obtain the historical OTA upgrade data of the vehicle, that is, you can obtain the upgrade information collection of the vehicle within a preset period of time.
[0105] 2. Vehicle local storage:
[0106] Some vehicles will retain the history of OTA upgrades in the local storage system, including upgrade packages, upgrade process logs, etc. Through the communication between the vehicle and the cloud device, these historical data can be uploaded to the cloud for centralized storage and analysis.
[0107] S203: The cloud device determines a target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set, and the upgrade information set.
[0108] In this step, after obtaining the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set, in order to flexibly obtain the target upgrade time, so as to meet the balance of cloud resources and not affect the user's use of the vehicle, the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set can be analyzed in multiple dimensions to obtain the target upgrade time.
[0109] Specifically, according to the list of vehicles to be upgraded, the number of vehicles to be upgraded at each moment in a preset time period is counted, and a first recommendation index is determined for each moment according to the number of vehicles to be upgraded corresponding to each moment; according to the vehicle usage information set, the probability of vehicle usage at each moment in the preset time period is counted, and a second recommendation index is determined for each moment according to the probability of vehicle usage corresponding to each moment; according to the upgrade information set, the number of upgrades at each moment in the preset time period is counted, and a third recommendation index is determined for each moment according to the number of upgrades corresponding to each moment; and / or according to the upgrade information set, the number of upgrade postponements at each moment in the preset time period is counted, and a third recommendation index is determined for each moment according to the number of upgrades corresponding to each moment and the number of upgrade postponements at each moment; for each moment, the first recommendation index, the second recommendation index and the third recommendation index corresponding to the moment are weightedly calculated to obtain the recommendation value corresponding to the moment, and the moment corresponding to the largest recommendation value is determined as the target upgrade time.
[0110] S204: The cloud device sends the target upgrade time to the vehicle.
[0111] In this step, after the cloud device generates the target upgrade time, it sends the target upgrade time to the vehicle so that the vehicle can perform OTA upgrade according to the target upgrade time.
[0112] Specifically, the cloud device sends the target upgrade time to the vehicle through specific communication protocols and channels, where the communication method and protocol can be a mobile communication network (such as 4G / 5G). The vehicle is connected to the mobile communication network through a built-in SIM card or eSIM and other modules, and the cloud device sends data to the vehicle through the mobile communication network. It can also be vehicle-to-everything (V2X) technology. If the vehicle supports vehicle-to-everything technology, the cloud device can send data to the vehicle through the vehicle-to-everything platform. Vehicle-to-everything technology provides communication capabilities between vehicles and the cloud, vehicles and vehicles, and vehicles and infrastructure, which helps to achieve more efficient upgrade task issuance and execution. It can also be Wi-Fi or other wireless communication technologies. In specific scenarios (such as vehicles parked in parking lots or homes that support Wi-Fi), vehicles can connect to the Internet via Wi-Fi and receive data sent from the cloud.
[0113] S205: The vehicle counts down according to the target upgrade, and after the countdown ends, the vehicle status is obtained.
[0114] In this step, after the vehicle receives the target upgrade time sent by the cloud device, in order to accurately monitor the upgrade, the target upgrade time is counted down and monitored in real time until the timing ends, and the vehicle status is obtained, where the vehicle status is used to indicate whether the vehicle is in use.
[0115] Specifically, the vehicle status can be judged in the following ways:
[0116] 1. Vehicle power status
[0117] ON gear but not READY state: The vehicle power is on, but the engine is not started, and the vehicle is not ready to drive. This is the ideal state for OTA upgrades, because the vehicle will not move at this time, and the system is powered on, and data transmission and upgrade operations can be performed. OFF gear: The vehicle power is completely turned off, and OTA upgrades cannot be performed at this time.
[0118] 2. Vehicle driving status
[0119] Stationary state: Determine whether the vehicle is stationary through the vehicle's GPS positioning, wheel speed sensor, etc. If the vehicle is stationary, it means that it is not currently in use and is suitable for OTA upgrade.
[0120] Driving status: If the vehicle is driving, the system should automatically determine that it is not suitable for OTA upgrade, because the upgrade process may affect the normal driving of the vehicle.
[0121] 3. Vehicle fault status
[0122] No fault status: Use the vehicle's fault diagnosis system (such as the OBD system) to determine whether the vehicle has a fault. If the vehicle has a fault, the fault should be resolved before performing the OTA upgrade to avoid problems during the upgrade process.
[0123] Fault light status: Observe whether the fault light on the dashboard is on. If it is on, it means that there is a fault or abnormality in the vehicle and it is not suitable for OTA upgrade.
[0124] 4. Vehicle safety system status
[0125] Safety system is normal: Ensure that the vehicle's safety system (such as ABS, ESP, etc.) is in normal working condition to avoid safety problems caused by system abnormalities during the upgrade process.
[0126] 5. Other factors
[0127] Vehicle charging status: If the vehicle is charging, you may need to pause charging or wait until charging is complete before performing an OTA upgrade to avoid current fluctuations during charging that may affect the upgrade process.
[0128] Vehicle network status: Ensure that the vehicle's network connection is stable to ensure smooth download and installation of the upgrade package.
[0129] S206: If the vehicle status indicates that the vehicle is not in use, perform an OTA upgrade.
[0130] In this step, if it is determined through the above steps that the vehicle status indicates that the vehicle is not in use, an OTA upgrade can be performed.
[0131] Specifically, before the OTA upgrade, the vehicle needs to do some preparation work, for example, to ensure that the vehicle battery is fully charged, generally requiring the battery to be no less than 30%, and the battery voltage to be higher than 12.1V. Ensure that the vehicle is properly connected to the external network, which can be Wi-Fi or mobile data. Some models may need to manually turn on the Wi-Fi function of the vehicle network.
[0132] After the preparation work is completed, the upgrade will be performed according to the pre-downloaded update software package. During the upgrade process, the user can view the vehicle status in real time and understand the upgrade progress.
[0133] Optionally, during the upgrade process, avoid performing any form of operation on the vehicle, such as starting the engine, disconnecting the power supply or network connection, etc., to avoid upgrade failure or vehicle malfunction.
[0134] In the vehicle software upgrade method provided in this embodiment, the cloud device receives the upgrade instruction sent by the vehicle, and obtains the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set according to the upgrade instruction, and then determines the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set, and finally sends the target upgrade time to the vehicle. The vehicle counts down according to the target upgrade, and after the countdown ends, the vehicle status is obtained. If the vehicle status indicates that the vehicle is not in use, an OTA upgrade is performed. Through the above method, the user's high-frequency vehicle use period is avoided for upgrading, which can minimize the impact of the upgrade on the user's daily vehicle use, and the upgrade is arranged according to the list of vehicles to be upgraded, which can balance the use of system resources, avoid server overload or upgrade failure caused by a large number of vehicles being upgraded at the same time during peak hours, and can improve the overall upgrade efficiency and success rate. Based on the upgrade information set, it is possible to predict and identify problems or risk points that may occur during the upgrade process, and take measures in advance to prevent and respond, which helps to enhance the stability and reliability of the vehicle system.
[0135] 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, the method specifically includes:
[0136] S301: The cloud device receives an upgrade instruction sent by the vehicle.
[0137] S302: The cloud device obtains a list of vehicles to be upgraded, a vehicle usage information set, and an upgrade information set according to the upgrade instruction.
[0138] S303: The cloud device determines the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set.
[0139] S304: The cloud device sends the target upgrade time to the vehicle.
[0140] S305: The vehicle counts down according to the target upgrade, and after the countdown ends, the vehicle status is obtained.
[0141] The specific implementation of steps S301 to S305 in this embodiment is the same as the implementation of steps S201 to S205 in the above embodiment, and will not be repeated here.
[0142] S306: If the vehicle status indicates that the vehicle is in use, the target upgrade time is postponed by a preset time, and the number of upgrade postponements is accumulated and sent to the cloud device.
[0143] In this step, by obtaining the vehicle status, if the vehicle status indicates that the vehicle is in use, OTA upgrade cannot be performed, so the upgrade is postponed, the target upgrade time is postponed by the preset duration, and the number of postponements of this upgrade task is accumulated and counted, and the number of upgrade postponements is fed back to the cloud device in real time.
[0144] S307: If the number of upgrade postponements reaches a preset postponement threshold, the cloud device redetermines the target upgrade time and sends the new target upgrade time to the vehicle.
[0145] In this step, after the cloud device receives the number of upgrade postponements reported by the vehicle, a postponement threshold is pre-set in order to efficiently implement the vehicle software upgrade. If the number of upgrade postponements reaches the pre-set postponement threshold, it means that the target upgrade time conflicts with the user's vehicle usage time, and the upgrade time needs to be reallocated to the user, and the new target upgrade time will be sent to the vehicle.
[0146] It should be noted that when the cloud device determines that the target upgrade time needs to be changed, the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set are re-acquired, and the new target upgrade time is determined by the method of determining the target upgrade time in the above embodiment.
[0147] It should be noted that when determining whether the number of upgrade postponements reaches a preset postponement threshold, the number of upgrade postponements within a period of time needs to be preset. For example, if the number of upgrade postponements reaches 3 times within a week, the target upgrade time is re-determined. The number of postponements within a week reaching 3 times can be continuous or discontinuous, which is not specifically limited in the embodiments of the present application.
[0148] In the vehicle software upgrade method provided in this embodiment, the cloud device receives the upgrade instruction sent by the vehicle, and obtains the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set according to the upgrade instruction, and then determines the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set, and finally sends the target upgrade time to the vehicle. The vehicle then counts down according to the target upgrade, and after the countdown ends, 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 the number of upgrade postponements is accumulated and sent to the cloud device. If the number of upgrade postponements reaches a pre-set postponement threshold, the cloud device redetermines the target upgrade time and sends the new target upgrade time to the vehicle. Through the above method combining intelligent scheduling and actual user usage, the flexibility and efficiency of vehicle OTA upgrades are achieved, the user experience and system stability are improved, and the continuous optimization and development of the system are promoted.
[0149] Figure 4A 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, steps S203 and S303 specifically include:
[0150] S401: According to the list of vehicles to be upgraded, the number of vehicles to be upgraded at each moment in a preset period is counted, and a first recommendation index is determined for each moment according to the number of vehicles to be upgraded corresponding to each moment.
[0151] S402: According to the vehicle usage information set, the vehicle usage probability at each moment in the preset time period is counted, and according to the vehicle usage probability corresponding to each moment, a second recommendation index is determined for each moment.
[0152] S403: Counting the number of upgrades at each moment in a preset period according to the upgrade information set, and determining a third recommendation index for each moment according to the number of upgrades corresponding to each moment.
[0153] In order to analyze the target upgrade time of vehicle software upgrade in multiple dimensions, after obtaining the existing list of vehicles to be upgraded in the cloud device, the vehicles to be upgraded at different times are divided into preset time periods, and then the number of vehicles waiting for upgrade at each time in different preset time periods is counted. The first recommendation index is set low for a large number of vehicles to be upgraded, and the first recommendation index is set high for a small number of vehicles to be upgraded. For example, there are 500 vehicles with an automatic upgrade time set to 1:00:00, 400 vehicles with an automatic upgrade time set to 1:01:00, and 600 vehicles with an automatic upgrade time set to 1:02:00. Then, the time with fewer vehicles is recommended first, that is, the first recommendation index corresponding to 1:01:00 is high, the first recommendation index corresponding to 1:02:00 is low, and the first recommendation index corresponding to 1:00:00 is in the middle.
[0154] Similarly, in order to ensure that the vehicle software upgrade does not affect the user's use of the vehicle, the probability of the user using the vehicle at each time in each preset time period can be counted based on the data in the acquired vehicle use information set, and then the second recommendation index can be set according to the size of the vehicle use probability. For example, by counting the user's historical data in the vehicle use information set, it is found that the user has multiple vehicle use behaviors at night, often from 1:00:00 to 1:30:00, then priority is given to non-vehicle use time, that is, the second recommendation index corresponding to 1:00:00-1:30:00 is low.
[0155] The accuracy of the target upgrade time can also be further optimized by combining the historical OTA upgrade data of the vehicle. According to the data in the upgrade information set, the number of upgrades of the vehicle at different times in each preset time period is counted, and then the third recommendation index is set according to the number of upgrades. For example, if the user has completed multiple OTA upgrades and the installation was completed at 1:30:00 many times, the completion time will be recommended first, that is, the third recommendation index corresponding to 1:30:00 is high.
[0156] S404: For each moment, determine a target upgrade time based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment.
[0157] In this step, after completing the recommendation index setting for each dimension data in the above steps, the recommendation value at each moment can be calculated based on the three recommendation indexes.
[0158] Exemplarily, for each moment, a weighted calculation is performed on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment to obtain a recommendation value corresponding to the moment. The moment corresponding to the maximum recommendation value is determined as the target upgrade time.
[0159] According to the different degrees of influence of each dimension data on vehicle OTA upgrade, a corresponding weight coefficient is set for each recommendation index, and then weighted calculation is performed to obtain the recommended value at each moment, for example: recommended value = first recommendation index × first weight + second recommendation index × second weight + third recommendation index × third weight. Then the recommended values at each moment are compared, and the moment corresponding to the maximum recommended value is set as the target upgrade time.
[0160] Optionally, according to the upgrade information set, the number of upgrade postponements at each moment in a preset time period is counted;
[0161] Accordingly, according to the number of upgrades corresponding to each moment, a third recommendation index is determined for each moment, including:
[0162] A third recommendation index is determined for each moment according to the number of upgrades corresponding to each moment and the number of upgrade deferrals at each moment.
[0163] When setting the third recommendation index based on the historical OTA upgrade data of the vehicle, the number of OTA upgrade failures in the upgrade information set can also be considered to more accurately adjust the target upgrade time. The number of OTA upgrade postponements at each moment in the preset time period is counted based on the data in the acquired upgrade information set, and the third index is recommended based on the number of upgrade postponements and the number of upgrades. For example, if the installation is postponed multiple times at 1:00:00 and the installation is completed multiple times at 1:30:00, the completion time is recommended first, and the recommended installation postponement time is avoided. That is, the third recommendation index corresponding to 1:00:00 is low, and there are 4 installation postponements and 2 completions at 1:40:00. The number of postponements at this moment is greater than the number of successful installations, and the third recommendation index is set low.
[0164] It should be noted that the vehicle usage information set and upgrade information set obtained are the vehicle usage information data and upgrade information data of the vehicle within at least one month. For the upgrade information set, the data collection time can be selected according to the frequency of vehicle upgrades. If the vehicle upgrade frequency is low, the upgrade information set can be the upgrade information data of the vehicle within at least half a year.
[0165] The vehicle software upgrade method provided in this embodiment counts the number of vehicles to be upgraded at each moment in a preset period according to the list of vehicles to be upgraded, and determines a first recommendation index for each moment according to the number of vehicles to be upgraded corresponding to each moment, counts the probability of using the vehicle at each moment in the preset period according to the vehicle use information set, and determines a second recommendation index for each moment according to the probability of using the vehicle corresponding to each moment, counts the number of upgrades at each moment in the preset period according to the upgrade information set, and determines a third recommendation index for each moment according to the number of upgrades corresponding to each moment, and for each moment, weighted calculations are performed on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment to obtain the recommendation value corresponding to the moment, and the moment corresponding to the maximum recommendation value is determined as the target upgrade time. The determination of the target upgrade time through the above multi-dimensional analysis provides a scientific basis for the determination of the upgrade time, helps to reduce the error of human judgment, and improves the accuracy of decision-making. And by avoiding the user's high-frequency vehicle use period for upgrading, the impact of the upgrade on the user's daily vehicle use can be minimized to the greatest extent, avoiding the interruption of the trip due to the upgrade. In addition, by arranging upgrade tasks according to the server load at different time periods, the use of system resources can be balanced to avoid server overload or upgrade failure caused by a large number of vehicles upgrading at the same time during peak hours. Through intelligent scheduling and priority sorting, network congestion and upgrade conflicts caused by concentrated vehicle upgrades can be reduced, which helps to improve the overall efficiency and success rate of upgrades.
[0166] Figure 5 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 5As shown, the vehicle software upgrade device 500 includes:
[0167] The first receiving module 501 is used to receive an upgrade instruction sent by a vehicle, where the upgrade instruction is used to instruct the vehicle software to automatically upgrade.
[0168] The acquisition module 502 is used to acquire a list of vehicles to be upgraded, a vehicle usage information set and an upgrade information set of the vehicles according to the upgrade instruction, wherein the vehicle usage information set includes vehicle usage data of multiple vehicles, and the upgrade information set includes upgrade data of multiple vehicles.
[0169] The determination module 503 is used to determine the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set.
[0170] The first sending module 504 is used to send the target upgrade time to the vehicle, so that the vehicle performs OTA upgrade at the target upgrade time.
[0171] Figure 6 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 6 As shown, based on the above embodiment, the determination module 503 includes:
[0172] The first setting unit 601 is used to count the number of vehicles to be upgraded at each moment in a preset period according to the list of vehicles to be upgraded, and determine a first recommendation index for each moment according to the number of vehicles to be upgraded corresponding to each moment.
[0173] The second setting unit 602 is used to count the vehicle usage probability at each moment in a preset time period according to the vehicle usage information set, and determine a second recommendation index for each moment according to the vehicle usage probability corresponding to each moment.
[0174] The third setting unit 603 is used to count the number of upgrades at each moment in a preset time period according to the upgrade information set, and determine a third recommendation index for each moment according to the number of upgrades corresponding to each moment.
[0175] The determination unit 604 is configured to determine, for each moment, a target upgrade time based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment.
[0176] Optionally, the determining unit 604 specifically includes:
[0177] The calculation subunit is used to perform weighted calculation on the first recommendation index, the second recommendation index and the third recommendation index corresponding to each moment, so as to obtain the recommendation value corresponding to the moment.
[0178] The determination subunit is used to determine the time corresponding to the maximum recommended value as the target upgrade time.
[0179] Optionally, the determining module 503 further includes:
[0180] A counting unit 605 is used to count the number of upgrade postponements at each moment in a preset time period according to the upgrade information set;
[0181] Accordingly, the third setting unit 603 includes:
[0182] The setting subunit is used to determine a third recommendation index for each moment according to the number of upgrades corresponding to each moment and the number of upgrade deferrals at each moment.
[0183] Figure 7 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 7. Based on the above embodiment, the vehicle software upgrade device 500 further includes:
[0184] The second receiving module 701 is used to receive the upgrade postponement times sent by the vehicle.
[0185] The second sending module 702 is used to redetermine the target upgrade time if the number of upgrade postponements reaches a preset postponement threshold, and send the new target upgrade time to the vehicle.
[0186] The vehicle software upgrade device provided in the above embodiment is used to execute the vehicle software upgrade method on the cloud device side in any of the above method embodiments. Its implementation principle and technical effects are similar and will not be repeated here.
[0187] Figure 8 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 Figure 8 As shown, the vehicle software upgrade device 800 specifically includes:
[0188] The receiving module 801 is used to receive the target upgrade time sent by the cloud device.
[0189] The acquisition module 802 is used to count down according to the target upgrade, and after the countdown ends, obtain the vehicle status, which is used to indicate whether the vehicle is in use.
[0190] The postponement module 803 is used to postpone the target upgrade time by a preset time if the vehicle status indicates that the vehicle is in use, and to accumulate and count the number of upgrade postponements.
[0191] The sending module 804 is used to send the upgrade postponement times to the cloud device.
[0192] Optionally, the vehicle software upgrading device 800 further includes:
[0193] The upgrade module 805 is used to perform OTA upgrade if the vehicle status indicates that the vehicle is not in use.
[0194] The vehicle software upgrade device provided in the above embodiment is used to execute the vehicle software upgrade method on the vehicle side in any of the above method embodiments. Its implementation principle and technical effect are similar and will not be repeated here.
[0195] Fig. 9 A schematic diagram of the structure of the cloud device provided in the embodiment of the present application, such as Fig. 9 As shown, the cloud device 900 includes: a processor 902, a memory 901 connected to the processor 902 for communication, and a classmate interface 903;
[0196] Memory 901 stores computer-executable instructions.
[0197] The processor 902 executes the computer-executable instructions stored in the memory 901 to implement the vehicle mileage pricing method on the cloud device side in any of the aforementioned embodiments.
[0198] The communication interface 903 is used to implement data communication with the vehicle.
[0199] Fig.10 A schematic diagram of the structure of a vehicle provided in an embodiment of the present application, such as Fig.10 As shown, including:
[0200] A vehicle body 1000, a storage unit 1001 disposed in the vehicle body, an electronic control unit 1002, and a communication interface 1003;
[0201] The storage unit 1001 stores computer-executable instructions;
[0202] The electronic control unit 1002 executes the computer-executable instructions stored in the storage unit 1001 to implement the vehicle software upgrade method on the vehicle side in any of the aforementioned embodiments.
[0203] The communication interface 1003 is used to implement data communication with the cloud server.
[0204] 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.
[0205] 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.
[0206] 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.
[0207] 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, it can implement the technical solution provided by any of the above method embodiments.
[0208] 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.
[0209] 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, characterized in that: Applied to a cloud device, the method includes: Receiving an upgrade instruction sent by a vehicle, wherein the upgrade instruction is used to instruct the vehicle software to automatically upgrade; According to the upgrade instruction, a list of vehicles to be upgraded, a vehicle usage information set and an upgrade information set of the vehicles are acquired, wherein the vehicle usage information set includes vehicle usage data of a plurality of the vehicles, and the upgrade information set includes upgrade data of a plurality of the vehicles; Determining a target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set, and the upgrade information set; The target upgrade time is sent to the vehicle, so that the vehicle performs an over-the-air OTA upgrade at the target upgrade time.
2. The method according to claim 1, characterized in that The determining the target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set includes: According to the list of vehicles to be upgraded, the number of vehicles to be upgraded at each moment in a preset time period is counted, and according to the number of vehicles to be upgraded corresponding to each moment, a first recommendation index is determined for each moment; According to the vehicle usage information set, counting the vehicle usage probability at each moment in the preset time period, and determining a second recommendation index for each moment according to the vehicle usage probability corresponding to each moment; According to the upgrade information set, counting the number of upgrades at each moment in the preset time period, and determining a third recommendation index for each moment according to the number of upgrades corresponding to each moment; For each moment, the target upgrade time is determined based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment.
3. The method according to claim 2, characterized in that The determining the target upgrade time based on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment includes: For each moment, weighted calculation is performed on the first recommendation index, the second recommendation index, and the third recommendation index corresponding to the moment to obtain a recommendation value corresponding to the moment; The time corresponding to the maximum recommended value is determined as the target upgrade time.
4. The method according to claim 2, characterized in that: The method further comprises: According to the upgrade information set, counting the number of upgrade postponements at each moment in the preset time period; Correspondingly, determining the third recommendation index for each moment according to the number of upgrades corresponding to each moment includes: A third recommendation index is determined for each moment according to the number of upgrades corresponding to each moment and the number of upgrade deferrals at each moment.
5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Receiving the upgrade postponement number sent by the vehicle; If the number of upgrade deferrals reaches a preset deferral threshold, the target upgrade time is re-determined and the new target upgrade time is sent to the vehicle.
6. A vehicle software upgrade method, characterized in that: Applied to a vehicle, the method comprises: Receive the target upgrade time sent by the cloud device; Counting down according to the target upgrade, and obtaining a vehicle status after the countdown ends, 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 by a preset time period, and the number of upgrade postponements is cumulatively counted; The upgrade postponement number is sent to the cloud device.
7. The method according to claim 6, characterized in that The method further comprises: If the vehicle status indicates that the vehicle is not in use, an OTA upgrade is performed.
8. A vehicle software upgrade device, characterized in that: include: A first receiving module, used for receiving an upgrade instruction sent by a vehicle, wherein the upgrade instruction is used for instructing the vehicle software to automatically upgrade; An acquisition module, used to acquire a list of vehicles to be upgraded, a vehicle usage information set and an upgrade information set of the vehicles according to the upgrade instruction, wherein the vehicle usage information set includes a plurality of vehicle usage data, and the upgrade information set includes a plurality of upgrade data of the vehicles; A determination module, configured to determine a target upgrade time based on the list of vehicles to be upgraded, the vehicle usage information set and the upgrade information set; The first sending module is used to send the target upgrade time to the vehicle, so that the vehicle performs an over-the-air (OTA) upgrade at the target upgrade time.
9. A vehicle software upgrade device, characterized in that: include: A receiving module, used to receive the target upgrade time sent by the cloud device; An acquisition module, used for performing a countdown according to the target upgrade, and acquiring a vehicle status after the countdown ends, wherein the vehicle status is used to indicate whether the vehicle is in use; A postponement module, configured to postpone the target upgrade time by a preset time period if the vehicle status indicates that the vehicle is in use, and to accumulate and count the number of upgrade postponements; A sending module is used to send the upgrade postponement number to the cloud device.
10. A cloud device, characterized in that: include: A processor, a memory and a communication interface connected to the processor in communication; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the vehicle software upgrade method as described in any one of claims 1 to 5 above.
11. A vehicle, 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 6 to 7.
12. A computer-readable storage medium, 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.
Citation Information
Cited By
Vehicle task pushing method, system, equipment and medium
CN120263849A
OTA upgrading method and equipment of intelligent equipment, medium and program product
CN120730291A
Vehicle software upgrade method, system and device, and storage medium
WO2026045725A1
