Ota upgrade control method for autonomous driving operation vehicle and related device

Abstract

This disclosure provides a method and related apparatus for controlling OTA upgrades of autonomous operating vehicles. This disclosure relates to the field of computer technology, and particularly to the fields of artificial intelligence, autonomous driving, and intelligent transportation. The specific implementation scheme is as follows: Detecting an upgrade task for the autonomous operating vehicle and obtaining a first detection result; if the first detection result indicates that there is an OTA upgrade task, notifying the operation cloud to update the status of the autonomous operating vehicle to a pending upgrade state so that the operation cloud stops assigning additional operating tasks to the autonomous operating vehicle; if the autonomous operating vehicle has processed the first detection result, notifying the operation cloud to update the status of the autonomous operating vehicle to a no-upgrade-task state so that the operation cloud assigns additional operating tasks to the autonomous operating vehicle.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to the fields of artificial intelligence, autonomous driving, and intelligent transportation. Background Technology

[0002] OTA (Over-The-Air Technology) vehicle upgrades refer to the technology of remotely updating and upgrading a vehicle's software system or firmware via a wireless network. This technology can continuously fix software defects, add new features, improve vehicle performance, and even enhance vehicle safety.

[0003] OTA technology can also monitor the vehicle's health status, promptly identify and resolve issues, and reduce the likelihood of vehicle malfunctions.

[0004] As vehicles become increasingly intelligent, OTA technology has become an indispensable part of the automotive industry. Summary of the Invention

[0005] This disclosure provides an OTA upgrade control method and related device for autonomous driving operating vehicles.

[0006] According to one aspect of this disclosure, an OTA upgrade control method for an autonomous driving operating vehicle is provided, comprising:

[0007] The upgrade task for detecting autonomous driving operation vehicles was completed, and the first test results were obtained.

[0008] If the first detection result indicates that there is an OTA upgrade task, the operation cloud is notified to update the status of the autonomous driving operation vehicle to the pending upgrade status so that the operation cloud stops assigning operation tasks to the autonomous driving operation vehicle.

[0009] After the autonomous driving operation vehicle has processed the first detection result, the operation cloud is notified to update the status of the autonomous driving operation vehicle to a no-upgrade-task status so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle.

[0010] According to another aspect of this disclosure, an OTA upgrade control device for an autonomous driving operating vehicle is provided, comprising:

[0011] The detection module is used to detect the upgrade tasks of autonomous driving operation vehicles and obtain the first detection result;

[0012] The first control module is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to the status of pending upgrade when the first detection result indicates that there is an OTA upgrade task, so that the operation cloud stops assigning operation tasks to the autonomous driving operation vehicle.

[0013] The second control module is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to a no-upgrade-task status after the autonomous driving operation vehicle has processed the first detection result, so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle.

[0014] According to another aspect of this disclosure, an electronic device is provided, comprising:

[0015] At least one processor; and

[0016] The memory is communicatively connected to the at least one processor; wherein,

[0017] The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform any of the methods described in the present disclosure.

[0018] According to another aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions, wherein the computer instructions are used to cause the computer to perform any of the methods according to embodiments of this disclosure.

[0019] According to another aspect of this disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements any of the methods according to embodiments of this disclosure.

[0020] According to another aspect of this disclosure, a vehicle is also provided, including the electronic devices described above.

[0021] In this embodiment, the autonomous driving operation vehicle can detect and process OTA upgrade tasks, ensuring that the operation cloud is promptly notified to stop task assignment during the upgrade process, and notifying again to resume task assignment after processing the first detection result. This mechanism avoids conflicts between operation tasks and upgrade tasks, improves operational efficiency, reduces manpower consumption, and enhances upgrade flexibility.

[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0023] The accompanying drawings are provided to better understand this solution and do not constitute a limitation of this disclosure. Wherein:

[0024] Figure 1 This is a schematic flowchart of an OTA upgrade control method for an autonomous driving operating vehicle according to an embodiment of the present disclosure;

[0025] Figure 2 This is a schematic flowchart of an OTA upgrade control method according to another embodiment of the present disclosure;

[0026] Figure 3 This is a schematic diagram of the state transition of an autonomous driving operating vehicle according to an embodiment of the present disclosure;

[0027] Figure 4 This is a schematic diagram of the OTA upgrade control device for an autonomous driving operating vehicle according to an embodiment of the present disclosure;

[0028] Figure 5 This is a block diagram of an electronic device used to implement the OTA upgrade control method for autonomous driving operating vehicles according to embodiments of the present disclosure. Detailed Implementation

[0029] The exemplary embodiments of this disclosure are described below with reference to the accompanying drawings, including various details of the embodiments to aid understanding, and should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of this disclosure. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0030] Current OTA upgrades still require long-term human monitoring, which not only consumes additional manpower but also lacks flexibility. Especially for autonomous vehicles capable of 24 / 7 operation, balancing operational efficiency with successful OTA upgrades is a critical issue.

[0031] In view of this, embodiments of this disclosure provide an OTA upgrade control method for autonomous driving operating vehicles. This method can be executed by a Panel Server built into the autonomous driving operating vehicle. A Panel Server typically refers to a server or system within the vehicle used to manage and control various displays and control panels. The Panel Server is responsible for handling the vehicle's user interface (UI) and user experience (UX), including but not limited to real-time monitoring of the vehicle's status, such as engine performance, battery status, tire pressure, etc., and providing necessary diagnostic information. The Panel Server can also manage the vehicle's network connections, such as vehicle-to-everything (V2X) services, OTA updates, and remote monitoring.

[0032] Panel servers are typically tightly integrated with the vehicle's Central Control Unit (CCU) or Vehicle Control Unit (VCU) to ensure the coordination and optimization of all functions. As vehicles become increasingly intelligent, the role of panel servers becomes more and more important, not only improving driving convenience and comfort but also enhancing vehicle safety and connectivity.

[0033] like Figure 1 The diagram shown is a schematic flowchart of an OTA upgrade control method for autonomous driving operating vehicles provided in this embodiment of the present disclosure, including:

[0034] S101, the upgrade task for detecting autonomous driving operation vehicles, yielded the first test result.

[0035] In this embodiment of the disclosure, the autonomous driving operating vehicle can autonomously sense whether an upgrade task exists and obtain a first detection result for the upgrade task accordingly. Based on the first detection result, it balances and coordinates the conflict between operational business and OTA upgrade tasks.

[0036] S102, if the first detection result indicates that there is an OTA upgrade task, notify the operation cloud to update the status of the autonomous driving operation vehicle to the pending upgrade status so that the operation cloud stops assigning additional operation tasks to the autonomous driving operation vehicle.

[0037] In this embodiment of the disclosure, the operations cloud, as the name suggests, is a service remotely responsible for managing and controlling operational tasks. The operations cloud can manage multiple autonomous driving vehicles, assign tasks to each autonomous driving vehicle, and monitor the task execution status of each autonomous driving vehicle. For example, for autonomous taxis, the operations cloud can receive passenger ride requests and dispatch autonomous taxis to pick up and drop off passengers.

[0038] In implementation, the state transitions of autonomous vehicles can be achieved through state machines. A state machine is a computational model that can operate in different states based on inputs or triggering events. The state machines of the autonomous vehicles are maintained in the cloud, and state transitions are triggered based on notifications from the autonomous vehicles.

[0039] When an OTA upgrade task is required, the autonomous driving operation vehicle notifies the operation cloud to update the state machine to the pending upgrade state.

[0040] S103: After the autonomous driving operation vehicle has processed the first detection result, the operation cloud is notified to update the status of the autonomous driving operation vehicle to a no-upgrade-task status so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle.

[0041] In other words, when an OTA (Over-The-Air) upgrade task is available, the autonomous vehicle notifies the operations cloud so that the operations cloud can suspend assigning additional operational tasks to the autonomous vehicle. Simultaneously, the autonomous vehicle processes the initial detection result and attempts to perform the upgrade. After processing the initial detection result, it notifies the operations cloud again to update the autonomous vehicle's status, enabling the operations cloud to utilize the autonomous vehicle promptly and improve operational efficiency.

[0042] It is understood that processing the first detection result does not equate to a successful OTA upgrade. In this embodiment, whether an OTA upgrade can be performed and whether it can be completed requires additional control strategies. Therefore, the processing result of the first detection result can be a successful OTA upgrade, an OTA upgrade failure, or an OTA upgrade pause.

[0043] In summary, in this embodiment, the autonomous driving vehicle can detect whether an OTA upgrade task is available and obtain a first detection result. When an OTA upgrade task is available, the autonomous driving vehicle's status can be updated in advance by notifying the operations cloud, allowing the operations cloud to promptly stop assigning tasks to the autonomous driving vehicle, making necessary preparations for the OTA upgrade, and also meeting the management needs of the operations cloud. After processing the first detection result, the autonomous driving vehicle can also promptly notify the operations cloud, allowing the operations cloud to assign tasks to the autonomous driving vehicle again, improving the operational efficiency of the autonomous driving vehicle. Therefore, when an OTA upgrade task is available, the autonomous driving vehicle no longer performs operational tasks but performs the OTA upgrade task, automatically and orderly handling vehicle operation tasks and upgrade tasks, avoiding conflicts between OTA upgrade tasks and operational tasks, and better coordinating and scheduling the autonomous driving vehicle. Furthermore, through the state transition of the autonomous driving vehicle, the timing of processing OTA upgrade tasks can be automatically controlled, eliminating the need for OTA operation personnel to constantly monitor upgrade tasks, thereby reducing manpower consumption and improving upgrade flexibility.

[0044] In this embodiment of the disclosure, detecting the upgrade task of the autonomous driving operation vehicle and obtaining the first detection result can be implemented by polling the task messages of the OTA client according to a preset polling period to obtain the first detection result; wherein, the upgrade task of the OTA client is allocated and sent to the OTA client by the OTA cloud.

[0045] For example, the OTA cloud can assign OTA upgrade tasks to autonomous vehicles as required. After receiving the OTA upgrade task, the OTA client of the autonomous vehicle retains it but does not execute it immediately. Once the Panel Server detects the OTA upgrade task, it can determine whether to execute it based on the upgrade policy. If not executed, the OTA upgrade task remains on the OTA client and will automatically trigger the process again during the next polling, actively attempting to complete the OTA upgrade task. The entire process is automated, requiring no continuous attention or intervention from OTA upgrade operations personnel, reducing manpower consumption and improving upgrade efficiency.

[0046] Accordingly, it is understandable that if the first detection result indicates that there is no OTA upgrade task, the status of the autonomous driving operation vehicle in the operation cloud remains unchanged, i.e., no upgrade task. Based on this, the operation cloud will assign additional operation tasks to the autonomous driving operation vehicle according to the normal operation process to ensure the operational efficiency of the autonomous driving operation vehicle.

[0047] In this embodiment of the disclosure, when the first detection result indicates that an OTA upgrade task is required, the system can first detect whether the upgrade conditions are met. If the upgrade conditions are met, the OTA upgrade process can then be executed to complete the OTA upgrade task as quickly as possible. Considering that the OTA upgrade of an autonomous driving vehicle may be affected by the vehicle's status and the operational task status in the cloud, this embodiment of the disclosure exemplarily detects whether the autonomous driving vehicle meets the upgrade conditions from two dimensions. The following describes how to process the first detection result. Figure 2 As shown, it includes:

[0048] S201, in response to the first detection result, detects the first vehicle state of the autonomous driving operation vehicle and obtains the second detection result.

[0049] The initial vehicle status of an autonomous driving operation vehicle can be obtained through the monitoring information of that autonomous driving operation vehicle, so as to facilitate the detection of that initial vehicle status.

[0050] In practice, when the autonomous driving operation vehicle detects the state of the first vehicle, step S201 can be executed as follows:

[0051] Detect at least one of the following first vehicle states, and if at least one of the first vehicle states is met, determine a second detection result indicating that the autonomous driving operation vehicle does not meet the upgrade requirements:

[0052] 1) Autonomous vehicles are performing operational tasks.

[0053] The operational tasks being performed by autonomous vehicles can be obtained through the vehicle's current task order information. For example, for fully driverless autonomous taxis, their order information can be retrieved to determine whether they are currently performing an operational task.

[0054] In this embodiment, it is detected whether the autonomous driving operation vehicle is currently performing an operational task. If it is performing a task, the conditions for OTA upgrade are not met, and the autonomous driving operation vehicle can continue to perform the current task normally without affecting the normal operation of the vehicle. Therefore, the impact of OTA upgrade tasks on the vehicle's operational tasks can be avoided.

[0055] 2) The autonomous driving operation vehicle is in autonomous driving mode.

[0056] Whether an autonomous driving vehicle is in autonomous driving mode or manual driving mode can be determined by the currently selected operating mode of the vehicle.

[0057] In autonomous driving mode, the vehicle is operating automatically under the control of the autonomous driving system. Performing an OTA upgrade in this mode may interfere with the autonomous driving system. Therefore, in this case, it is determined that the conditions for OTA upgrade are not met, which can improve the stability and safety of vehicle operation.

[0058] 3) The autonomous driving operation vehicle is in motion;

[0059] Whether an autonomous driving vehicle is in motion can be determined by information such as the vehicle's current speed and location.

[0060] OTA upgrades may affect normal driving or even pose safety hazards when the vehicle is in motion. Therefore, if the vehicle is in motion, it is determined that the upgrade is not feasible and normal driving can continue to improve the safety of the vehicle.

[0061] 4) Autonomous driving vehicles are parked in non-compliant areas;

[0062] It can identify traffic requirements near autonomous driving vehicles to determine whether the vehicles are parked in non-compliant parking areas.

[0063] In non-compliant parking areas, autonomous vehicles may leave the area at any time due to various factors, or the vehicles may intentionally make a temporary stop. Regardless of the reason, the duration of parking in non-compliant areas is usually too short to complete OTA upgrades. Therefore, classifying locations in non-compliant parking areas as unsuitable for upgrades can effectively filter out locations unsuitable for OTA upgrades, thus improving the success rate of OTA upgrades.

[0064] 5) The parking status of autonomous driving operation vehicles in the compliant parking area does not comply with the parking rules.

[0065] Vehicle parking rules refer to a set of regulations governing vehicle parking behavior in specific areas or situations to ensure traffic safety, smooth flow, and order. These parking rules may vary from region to region, country, or even city to city. In practice, parking information can be collected by sensors on autonomous vehicles to identify the relative position of the vehicle and its surroundings, and then matched against local parking rules to determine whether the parking rules are met.

[0066] For the Panel Server, the upstream module can also determine the docking rules and then notify the Panel Server of the result of whether the docking rules are met.

[0067] In this embodiment, if autonomous driving vehicles do not comply with parking rules, it will affect traffic safety, forcing them to adjust their parking locations. This may negatively impact OTA upgrades, for example, changes in the autonomous driving vehicle's mode or operating status may cause OTA upgrades to be interrupted, or network signal fluctuations may occur due to changes in parking locations. Therefore, parking rules can help select suitable upgrade locations and times for OTA upgrade tasks, improving upgrade efficiency.

[0068] 6) The remaining battery power of the autonomous driving operation vehicle is less than the set threshold;

[0069] In this embodiment of the disclosure, when the remaining power is insufficient, it is determined that the autonomous driving operation vehicle does not meet the upgrade conditions. This ensures that the OTA upgrade is completed when the power is sufficient, so as to provide sufficient energy for the OTA upgrade task, avoid OTA upgrade failure due to insufficient energy, and thus improve the success rate of the upgrade.

[0070] 7) The autonomous driving operation vehicle triggered a fault alarm message of a preset level or higher.

[0071] If a vehicle has fault alarm messages of a preset level or higher, it indicates that the vehicle is currently experiencing an abnormal condition, and OTA upgrades are not suitable in this situation. Therefore, if fault alarm messages of a preset level or higher are present, it will be determined that the upgrade is not feasible, which can improve upgrade efficiency.

[0072] 8) The gear position of the autonomous driving operation vehicle is not set to parking.

[0073] OTA upgrades may require software or firmware upgrades for autonomous vehicles. If the vehicle is not in the parking position, OTA upgrades may pose safety hazards. Therefore, determining that an autonomous vehicle is not in the parking position is considered ineligible for upgrades, which can improve upgrade efficiency while ensuring vehicle safety.

[0074] In summary, by detecting whether the above-mentioned multiple first vehicle states are valid in this embodiment, factors that are unfavorable to OTA upgrades can be eliminated as comprehensively as possible from multiple perspectives, thereby ensuring the success rate of OTA upgrades.

[0075] In summary, for autonomous driving operational vehicles, if they meet the following conditions based on the test results, they can be considered as having the conditions for upgrading:

[0076] The autonomous driving vehicles were not performing their operational tasks;

[0077] The autonomous driving operation vehicle is in manual driving mode and is in P gear;

[0078] The autonomous driving vehicles are currently stationary.

[0079] The autonomous driving vehicles are currently in compliant parking areas at all times;

[0080] The autonomous driving vehicles comply with the parking rules of the current parking area;

[0081] The remaining battery power of the autonomous driving operation vehicle is greater than a set threshold.

[0082] There are no fault alarm messages of a preset level or higher that need to be processed in the autonomous driving operation vehicles.

[0083] In implementation, when multiple first vehicle states are involved, each first vehicle state can be checked sequentially. During the checking process, if any first vehicle state is established, it can be determined that the upgrade conditions are not met, and thus the checking can be stopped. For example, it can be implemented as follows:

[0084] Based on the status of the autonomous driving operation vehicle, determine whether the autonomous driving operation vehicle is currently performing an operation task;

[0085] If, during the execution of operational tasks, it is determined that the conditions for upgrading are not met, the testing for whether the conditions for upgrading are met will be terminated.

[0086] If the autonomous driving vehicle is not performing an operational task at the current moment, determine whether the autonomous driving vehicle is in autonomous driving mode based on the current driving mode;

[0087] If the system is in autonomous driving mode and it is determined that the conditions for upgrading are not met, the detection of whether the conditions for upgrading are met will end.

[0088] When the current driving mode is manual driving mode, determine whether the autonomous driving vehicle is currently in a parked state based on the gear selected by the autonomous driving vehicle.

[0089] If the vehicle is in motion and it is determined that the conditions for upgrading are not met, the test to determine whether the conditions for upgrading are met ends.

[0090] When the vehicle is parked, determine whether it is within a legal parking area;

[0091] If the vehicle is located in a non-compliant parking area, and it is determined that the conditions for upgrading are not met, the testing for whether the conditions for upgrading are met will be terminated.

[0092] If the vehicle is located within a compliant parking area, determine whether the autonomous driving vehicle complies with the parking rules of the current parking area.

[0093] If the parking rules are not met, it is determined that the conditions for upgrading are not met, and the test for whether the conditions for upgrading are met ends.

[0094] If the parking rules are met, the system determines the remaining battery power of the autonomous driving vehicle, whether it is not in Park (P) gear, and whether it has triggered a fault alarm message of a preset level or higher. If all of these conditions are met, the system determines that the vehicle meets the upgrade requirements. If any one of these conditions is met, the system determines that the vehicle does not meet the upgrade requirements, and the upgrade requirement test ends.

[0095] Of course, the detection of remaining battery power, whether it is not in P mode, and the detection of fault alarm information can be performed at any time, depending on actual needs.

[0096] Furthermore, by following the above process to check whether autonomous driving operation vehicles meet the upgrade requirements, unnecessary tests can be omitted, improving testing efficiency and saving processing resources for autonomous driving operation vehicles.

[0097] S202, obtain the third detection results of autonomous driving operation vehicles from the operation cloud.

[0098] The detection of autonomous driving vehicles by the operation cloud can be achieved through vehicle information provided by the operation cloud's operational tasks and the detection results of relevant detection modules.

[0099] During implementation, if the operations cloud detects at least one of the following second vehicle states, the third detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements, including:

[0100] 1) The last operational task performed by the autonomous driving vehicle was not completed properly;

[0101] In other words, the previous operation task of the autonomous driving vehicle order has not been completed normally, and the next operation task has not yet started or has not yet been assigned.

[0102] If the operational tasks of autonomous vehicles are not completed normally, it indicates an operational malfunction and potential operational issues that need to be addressed. In such cases, the operational situation may be unclear. To avoid conflicts between OTA upgrade tasks and operational tasks and to improve upgrade efficiency, it can be determined that if the operational tasks are not completed normally, the conditions for upgrading are not met.

[0103] 2) Autonomous driving vehicles have operational tasks to be processed.

[0104] In other words, autonomous vehicles have pending tasks, which have already been assigned and are waiting to be operated. Taking autonomous taxis as an example, after a customer places a ride order, they wait for an autonomous taxi to pick them up. Therefore, when autonomous vehicles have pending operational tasks, these tasks need to be prioritized to ensure normal operation. Thus, classifying autonomous vehicles with pending operational tasks as not meeting the upgrade requirements helps alleviate conflicts between OTA upgrade tasks and operational tasks, improving the stability and efficiency of upgrades and operations.

[0105] 3) Autonomous driving vehicles have continuous tasks;

[0106] Continuous tasks refer to multiple sequential operational tasks assigned to autonomous vehicles by the cloud-based operations team. For example, a relay order might be assigned to an autonomous taxi, which would first pick up passenger A, and then pick up passenger B near passenger A's location.

[0107] In this embodiment of the disclosure, it is detected whether the autonomous driving operation vehicle has continuous tasks. If the vehicle has continuous tasks, the vehicle needs to maintain its current operating state and continue to complete the current continuous tasks. In the current state, it is determined that the vehicle does not have the conditions for OTA upgrade, which can avoid the OTA upgrade task from affecting the normal operation of the vehicle.

[0108] 4) The last destination of the task performed by the self-driving vehicle could not be found.

[0109] The endpoint status of the previous task for autonomous driving vehicles can be obtained through monitoring the current order execution status via the operations cloud.

[0110] In this embodiment, the endpoint status of the previous task of the autonomous driving operation vehicle is detected. If the endpoint is not found, the endpoint of the autonomous driving operation vehicle cannot be perceived, and it is impossible to further determine whether the upgrade conditions are met. Therefore, in this state, it is determined that the vehicle does not meet the conditions for OTA upgrade, which can avoid the failure of OTA upgrade due to vehicle abnormality.

[0111] 5) Autonomous driving vehicles are at temporary parking spots;

[0112] Temporary stopping points are locations where vehicles are allowed to park for short periods under specific circumstances. These locations are typically set up to meet needs such as passenger boarding and alighting, loading and unloading of goods, and emergency handling.

[0113] Temporary stopping points have time limits, such as "maximum 3 minutes" or "15 minutes for loading and unloading goods." Exceeding these limits may result in penalties. Vehicles must not obstruct the passage of other vehicles or pedestrians within the temporary stopping point.

[0114] Temporary parking spots have many limitations that hinder OTA (Over-The-Air) upgrades. For example, the duration of a vehicle's stay at a temporary parking spot is limited, and the need for the vehicle to leave within a short period may interrupt the OTA upgrade process. Therefore, to ensure smooth OTA upgrades, a vehicle at a temporary parking spot can be considered as not meeting the upgrade requirements.

[0115] 6) The prescribed stopping time for autonomous driving vehicles at designated stops is less than the time threshold;

[0116] The duration threshold can be dynamically determined based on the upgrade time required for this OTA upgrade task. For example, if the OTA upgrade task requires 8 minutes, the duration threshold can be set to 10 minutes. If the estimated time for the vehicle to be at the stop is 3 minutes, then it can be determined that the prescribed stop time for the autonomous driving operation vehicle at the stop is less than the duration threshold.

[0117] The duration threshold can also be set to a uniform threshold based on experience.

[0118] When implemented, the prescribed parking duration for vehicles at designated stops can be determined based on the parking requirements of those stops.

[0119] In this embodiment of the disclosure, the dwell time of the autonomous driving operation vehicle at the stop point is detected. If the dwell time of the vehicle does not meet the set threshold, the vehicle may not be able to complete the OTA upgrade task. Therefore, determining whether the upgrade conditions are met based on the dwell time and the duration threshold can avoid the OTA upgrade not being able to be executed normally due to the dwell time of the vehicle being too short.

[0120] 7) Receive abnormal information reported by autonomous driving operation vehicles;

[0121] Abnormal information reported by autonomous driving vehicles can be obtained through the operation cloud by monitoring the reported information of the current vehicles.

[0122] If a vehicle reports abnormal information, it indicates that the vehicle is currently experiencing an abnormal condition. The vehicle needs to be inspected to determine the cause of the abnormality and the appropriate repair method. Therefore, if the vehicle itself is malfunctioning, determining that it does not meet the requirements for OTA upgrades can prevent OTA upgrade failures due to vehicle abnormalities.

[0123] 8) The autonomous driving operation vehicle is in the process of being withdrawn from service;

[0124] "Retrieve vehicle" usually refers to switching the vehicle from autonomous driving mode to manual driving mode and / or parking the vehicle in a designated location.

[0125] When autonomous driving vehicles are in the process of being decommissioned, some status changes may occur, affecting the smooth progress of OTA upgrades. Therefore, when an autonomous driving vehicle is in the decommissioning state, it is determined that the vehicle does not meet the conditions for OTA upgrades, thus avoiding OTA upgrade failures due to the vehicle performing the decommissioning task.

[0126] 9) The autonomous driving operation vehicle is in the battery swapping state.

[0127] Battery swapping technology is a way to replenish energy for new energy vehicles. It allows car owners to quickly replenish their energy by replacing the battery pack, instead of through traditional charging methods. Battery swapping stations are the key infrastructure for realizing this technology; they can store, charge, and provide battery replacement services. The basic components of a battery swapping station include a battery swapping system, a charging system, a battery swapping platform, and a control system.

[0128] If the vehicle is currently in a battery swapping state, it means that the current battery level is insufficient to maintain the vehicle's operation. Under the current condition, it is determined that the vehicle does not meet the conditions for OTA upgrade, so as to avoid the inability to upgrade OTA due to insufficient battery level or battery swapping state.

[0129] 10) No upgrade configuration information for autonomous driving operation vehicles was detected;

[0130] The upgrade configuration information is used to control the upgrades of autonomous driving vehicles. For example, operators managing OTA upgrades can use this configuration information to set the upgrade time period for vehicles, and vehicles will not be allowed to upgrade outside of this time period.

[0131] Without detecting upgrade configuration information for the vehicle, it's impossible to understand some of the requirements and limitations of OTA upgrades. In the current state, determining that the vehicle does not meet the conditions for OTA upgrades can prevent OTA upgrade failures or errors.

[0132] 11) The current time period exceeds the configuration time period of the upgrade configuration information.

[0133] In this embodiment of the disclosure, the current time period of the autonomous driving operation vehicle is detected. If the current time period of the vehicle does not match the configuration time period of the upgrade configuration information, it means that the vehicle does not meet the conditions required for the upgrade. In the current state, it is determined that the vehicle does not meet the conditions for OTA upgrade, which can avoid OTA upgrade failure.

[0134] 12) The remaining battery power of autonomous driving vehicles is less than the set threshold.

[0135] When the remaining battery power is insufficient, the autonomous driving operation vehicle is determined not to meet the upgrade conditions. This ensures that the OTA upgrade is completed when the battery power is sufficient, so as to provide sufficient energy for the OTA upgrade task, avoid OTA upgrade failure due to insufficient energy, and thus improve the success rate of the upgrade.

[0136] 13) The parking status of autonomous driving operation vehicles in the compliant parking area does not comply with the parking rules.

[0137] If autonomous vehicles do not comply with parking rules, they can impact traffic safety, forcing them to adjust their parking locations. This can negatively affect over-the-air (OTA) upgrades, such as causing upgrade interruptions due to the autonomous vehicle's software or network signal fluctuations caused by changing parking locations. Therefore, using parking rules can help select suitable upgrade locations and times for OTA upgrades, improving upgrade efficiency.

[0138] 14) The query result for the last operational task performed by the autonomous driving operation vehicle is an anomaly.

[0139] In other words, if the cloud-based operations system cannot find the last task performed by the autonomous driving vehicle, it is impossible to determine whether the conditions for upgrading are met. Therefore, in this case, it is determined that the conditions for upgrading are not met, which can improve the success rate of OTA upgrades and avoid anomalies caused by OTA upgrades.

[0140] 15) An error occurred when querying real-time sites for autonomous driving operating vehicles.

[0141] In this embodiment, multiple stations can be configured within the operating area of ​​the autonomous driving vehicle. Each station can be configured with information such as operating duration, whether it can stop, and maximum stopping time. In this embodiment, upgrades can be performed not only at the endpoint of the autonomous driving vehicle's last task, but also when the OTA upgrade task's priority reaches a preset priority and the autonomous driving vehicle has no operating task, and the first detection result indicates an OTA upgrade task, the autonomous driving vehicle can be dispatched to a station that meets the OTA upgrade requirements for upgrade by querying the stations surrounding its location.

[0142] When upgrades require reliance on nearby sites, an anomaly in the real-time site query will prevent the operations cloud from identifying the autonomous driving vehicles' real-time sites and thus hinder real-time dispatching of these vehicles to available upgrade locations. This can lead to OTA upgrade failures. Determining that upgrades are not feasible when real-time site queries are abnormal can improve the success rate.

[0143] It should be noted that, in this embodiment, the priority of operational tasks is generally higher than that of OTA upgrade tasks. To ensure the normal operation of operations and avoid frequent changes to the operational plan that could lead to alarms and blocked vehicle dispatch, in this embodiment, OTA upgrade tasks with extremely high priority will be completed before the execution of operational tasks on the same day.

[0144] In this embodiment of the disclosure, when the operation cloud detects multiple second vehicle states of the autonomous driving operation vehicle, it can understand the vehicle state of the autonomous driving operation vehicle from multiple perspectives to determine whether it can meet the requirements of OTA upgrade. This helps to improve the success rate of upgrade and avoid wasting processing resources.

[0145] In summary, in this embodiment, the autonomous driving vehicle monitors its own status and eliminates factors that could hinder OTA upgrades. Simultaneously, the cloud-based operations system also checks the vehicle's eligibility for upgrades based on its own data. By eliminating factors detrimental to OTA upgrades from different perspectives and performing double checks on key factors, a dual verification process is implemented, improving the reliability of the detection results and thus increasing the success rate of OTA upgrades.

[0146] S203: If both the second and third test results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the upgrade process is initiated to perform an OTA upgrade on the autonomous driving operation vehicle.

[0147] In this embodiment, the autonomous driving vehicle performs a first vehicle status detection, while the operation cloud simultaneously detects the second vehicle status of the autonomous driving vehicle. If both detections pass, the autonomous driving vehicle meets the conditions for OTA (Over-The-Air) upgrade and can initiate an OTA upgrade. At this point, the autonomous driving vehicle enters the OTA process. Because the detection aims to minimize interference from factors affecting the upgrade process, the success rate of the OTA upgrade will be improved.

[0148] During implementation, if both the vehicle's own status and the vehicle's operational status detected by the cloud platform meet the requirements for OTA upgrade, an upgrade command can be sent to the OTA client so that the OTA client can perform the upgrade operation based on the OTA upgrade task.

[0149] For example, if the Panel Server detects autonomous driving vehicles and determines that they meet the upgrade requirements based on the initial vehicle status, and the detection results from the operation cloud also confirm that the autonomous driving vehicles meet the upgrade requirements, the Panel Server can notify the OTA client of the autonomous driving vehicles to perform the upgrade operation, thereby executing the OTA upgrade task.

[0150] Therefore, when the OTA client receives an OTA upgrade task, it does not immediately execute the OTA upgrade operation. Instead, it continues to execute the OTA upgrade operation only after confirming that the upgrade is possible. This allows it to take into account both operational needs and vehicle upgrade requirements, and better coordinate OTA upgrade tasks and operational tasks.

[0151] Therefore, upgrade tasks can be issued at any time. Based on the solution provided in this disclosure, the timing of upgrades can be automatically and flexibly controlled, reducing the need for manual intervention and improving upgrade efficiency while reducing manpower input.

[0152] If both the second and third test results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the operation cloud will be notified to update the status of the autonomous driving operation vehicle to "upgrading in progress".

[0153] When autonomous vehicles are performing OTA upgrades, the state of the operation cloud remains in the upgrade state. After the autonomous vehicles have completed the OTA upgrade, the state machine is updated to no upgrade task.

[0154] In this embodiment, when it is determined that the autonomous driving operation vehicle meets the upgrade requirements, the operation cloud is notified to update the vehicle's status to "upgrading in progress." The operation cloud can determine that the vehicle is currently undergoing an upgrade based on this status. In this state, the operation cloud will not assign additional operational tasks to the autonomous driving operation vehicle, ensuring that the OTA upgrade process is not interrupted.

[0155] Of course, if either the second or third test result indicates that the autonomous driving operation vehicle does not meet the upgrade conditions, the OTA client will not be triggered to perform the OTA upgrade operation. The OTA upgrade task can still be retained in the OTA client so that the upgrade task can be actively polled again in the future and then the upgrade can be completed automatically.

[0156] This can be understood as follows: to balance operational considerations, if either the second or third detection result indicates that the autonomous driving vehicle does not meet the upgrade requirements, the upgrade fails, but the first detection result has already been processed. The OTA upgrade task remains on the OTA client, awaiting execution during the next polling. Therefore, if either detection result indicates that the autonomous driving vehicle does not meet the upgrade requirements, the autonomous driving vehicle will notify the operations cloud to update its status to "no upgrade task," thus returning the autonomous driving vehicle to the operations cloud for operational task allocation, thereby improving operational efficiency.

[0157] Furthermore, if at least one of the second and third test results indicates that the autonomous driving operation vehicle does not meet the upgrade requirements, the autonomous driving operation vehicle can also send an upgrade failure instruction to the OTA client, so that the OTA client sends an upgrade failure message to the OTA cloud.

[0158] Therefore, the information of the upgrade failure is synchronized to the OTA client. The OTA client does not execute the upgrade command, but notifies the OTA cloud of the upgrade failure information. The OTA cloud can obtain the upgrade failure information in a timely manner, and at the same time analyze and process the OTA upgrade failure information, which can provide a basis for the next OTA upgrade of autonomous driving operation vehicles.

[0159] In summary, the state machine in this embodiment includes three states: 1 represents the state with no upgrade task, 2 represents the state in progress, and 3 represents the state awaiting upgrade. For example... Figure 3As shown, the system actively polls the OTA client for task information according to a preset polling cycle, eliminating the need for manual intervention in checking for OTA upgrade information and thus minimizing manpower requirements. When an OTA upgrade task is periodically detected, the system notifies the operations cloud, updating the state machine to state 3 (awaiting upgrade). This prompts the operations cloud to suspend the use of the autonomous driving vehicles to facilitate the OTA upgrade task. Both the autonomous driving vehicles and the operations cloud jointly check if the upgrade conditions are met. If either fails the check, indicating that the upgrade conditions are not met, the state machine is updated to state 1 (no upgrade task), and the autonomous driving vehicles are handed over to the operations cloud for task allocation. If both checks pass, the state machine is updated to state 2 (upgrading in progress), allowing the operations cloud to monitor the upgrade process. The upgrade progress of the autonomous driving vehicles can be reported to the operations cloud, enabling the operations cloud to plan operational tasks for the vehicles based on this progress. In the event of an upgrade failure or success, the autonomous driving vehicles notify the operations cloud to update the state machine to state 1 (no upgrade task), allowing the operations cloud to allocate operational tasks to the vehicles and improve operational efficiency.

[0160] In summary, this embodiment of the disclosure enables the rational scheduling of OTA upgrade tasks and operational tasks through the interaction between autonomous driving vehicles and the operational cloud. This method is particularly suitable for 24-hour fully autonomous driving vehicles, as it can effectively coordinate OTA upgrades and operational tasks, thereby improving the utilization rate of autonomous driving vehicles.

[0161] Based on the same technical concept, this disclosure also provides an OTA upgrade control device 400 for autonomous driving operating vehicles, such as... Figure 4 As shown, it includes:

[0162] The detection module 401 is used to detect the upgrade task of the autonomous driving operation vehicle and obtain the first detection result;

[0163] The first control module 402 is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to a pending upgrade status so that the operation cloud stops assigning operation tasks to the autonomous driving operation vehicle when the first detection result indicates that there is an OTA upgrade task.

[0164] The second control module 403 is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to a no-upgrade-task status after the autonomous driving operation vehicle has finished processing the first detection result, so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle.

[0165] In some embodiments, a processing module is further included for processing the first detection result based on the following method:

[0166] In response to the first detection result, a first vehicle state of the autonomous driving operating vehicle is detected to obtain a second detection result; and,

[0167] Obtain the third detection result of the autonomous driving operation vehicle from the operation cloud;

[0168] If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the upgrade process is initiated to perform an OTA upgrade on the autonomous driving operation vehicle.

[0169] In some embodiments, the processing module is specifically used for:

[0170] Detect at least one of the following first vehicle states:

[0171] The autonomous driving vehicle is performing operational tasks;

[0172] The autonomous driving operation vehicle is in autonomous driving mode;

[0173] The autonomous driving vehicle is in motion;

[0174] The autonomous driving vehicle was parked in an unauthorized area.

[0175] The autonomous driving operation vehicle's parking status in the compliant parking area does not comply with the parking rules;

[0176] The remaining battery power of the autonomous driving operation vehicle is less than a set threshold;

[0177] The autonomous driving operation vehicle triggered a fault alarm message of a preset level or higher.

[0178] The gear of the autonomous driving vehicle was not set to park.

[0179] If at least one of the first vehicle states is established, the determined second detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements.

[0180] In some embodiments, if the operation cloud detects that at least one of the following second vehicle states are met, the third detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements:

[0181] The last operational task performed by the autonomous driving vehicle was not completed properly;

[0182] The autonomous driving operation vehicle has operational tasks to be processed;

[0183] The autonomous driving operation vehicle has continuous tasks;

[0184] The last destination of the autonomous driving vehicle was not found.

[0185] The autonomous driving vehicle was at a temporary parking spot;

[0186] The prescribed stopping time of the autonomous driving operation vehicle at the mission endpoint is less than the time threshold;

[0187] Receive the abnormal information reported by the autonomous driving operation vehicle;

[0188] The autonomous driving operation vehicle is in the process of being returned to service;

[0189] The autonomous driving operation vehicle is in a battery swapping state;

[0190] No upgrade configuration information was detected for the aforementioned autonomous driving operation vehicle;

[0191] The current time period exceeds the configuration time period specified in the upgrade configuration information;

[0192] The remaining battery power of the autonomous driving operation vehicle is less than a set threshold;

[0193] The autonomous driving vehicle's parking status in the compliant parking area did not comply with the parking rules.

[0194] The query result for the last operational task performed by the aforementioned autonomous driving vehicle was an anomaly.

[0195] An error occurred when querying the real-time stations of the aforementioned autonomous driving operating vehicles.

[0196] In some embodiments, the processing module is specifically used for:

[0197] If both the second and third detection results indicate that the autonomous driving operating vehicle meets the upgrade requirements, an upgrade command is sent to the OTA client so that the OTA client can perform an upgrade operation based on the OTA upgrade task.

[0198] In some embodiments, the second control module is further configured to:

[0199] If at least one of the second and third detection results indicates that the autonomous driving operating vehicle does not meet the upgrade requirements, an upgrade failure instruction is sent to the OTA client, so that the OTA client sends an upgrade failure message to the OTA cloud.

[0200] In some embodiments, the second control module is further configured to:

[0201] If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the operation cloud is notified to update the state machine of the autonomous driving operation vehicle to the upgrade-in progress state.

[0202] In some embodiments, the detection module is specifically used for:

[0203] According to the preset polling period, poll the task messages of the OTA client to obtain the first detection result;

[0204] The upgrade task for the OTA client is assigned and sent to the OTA client by the OTA cloud.

[0205] The specific functions and examples of each module and submodule of the apparatus in this disclosure can be found in the relevant descriptions of the corresponding steps in the above method embodiments, and will not be repeated here.

[0206] The acquisition, storage, and application of user personal information involved in the technical solution disclosed herein comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0207] According to embodiments of this disclosure, this disclosure also provides an electronic device, a readable storage medium, and a computer program product.

[0208] Figure 5 A schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0209] like Figure 5 As shown, device 500 includes a computing unit 501, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 502 or a computer program loaded from storage unit 508 into random access memory (RAM) 503. RAM 503 may also store various programs and data required for the operation of device 500. The computing unit 501, ROM 502, and RAM 503 are interconnected via bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0210] Multiple components in device 500 are connected to I / O interface 505, including: input unit 506, such as keyboard, mouse, etc.; output unit 507, such as various types of monitors, speakers, etc.; storage unit 508, such as disk, optical disk, etc.; and communication unit 509, such as network card, modem, wireless transceiver, etc. Communication unit 509 allows device 500 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0211] The computing unit 501 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 performs the various methods and processes described above, such as the OTA upgrade control method for autonomous driving operating vehicles. For example, in some embodiments, the OTA upgrade control method for autonomous driving operating vehicles can be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program can be loaded and / or installed on device 500 via ROM 502 and / or communication unit 509. When the computer program is loaded into RAM 503 and executed by the computing unit 501, one or more steps of the OTA upgrade control method for autonomous driving operating vehicles described above can be performed. Alternatively, in other embodiments, computing unit 501 may be configured by any other suitable means (e.g., by means of firmware) to perform OTA upgrade control methods for autonomous driving operating vehicles.

[0212] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0213] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0214] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0215] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0216] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0217] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0218] This disclosure also provides a vehicle including the electronic devices described above.

[0219] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0220] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. An OTA upgrade control method for an autonomous driving operating vehicle, comprising: The upgrade task for detecting autonomous driving operation vehicles was completed, and the first test results were obtained. If the first detection result indicates that there is an OTA upgrade task, the operation cloud is notified to update the status of the autonomous driving operation vehicle to the pending upgrade status so that the operation cloud stops assigning operation tasks to the autonomous driving operation vehicle. After the autonomous driving operation vehicle has processed the first detection result, the operation cloud is notified to update the status of the autonomous driving operation vehicle to a no-upgrade-task status so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle. The processing of the first detection result includes: In response to the first detection result, a first vehicle state of the autonomous driving operating vehicle is detected to obtain a second detection result; and, Obtain the third detection result of the autonomous driving operation vehicle from the operation cloud; If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the upgrade process is initiated to perform an OTA upgrade on the autonomous driving operation vehicle.

2. The method according to claim 1, wherein, The process of detecting the first vehicle state of the autonomous driving operating vehicle and obtaining the second detection result includes: Detect at least one of the following first vehicle states: The autonomous driving vehicle is performing operational tasks; The autonomous driving operation vehicle is in autonomous driving mode; The autonomous driving vehicle is in motion; The autonomous driving vehicle was parked in an unauthorized area. The autonomous driving operation vehicle's parking status in the compliant parking area does not comply with the parking rules; The remaining battery power of the autonomous driving operation vehicle is less than a set threshold; The autonomous driving operation vehicle triggered a fault alarm message of a preset level or higher. The gear of the autonomous driving vehicle was not set to park. If at least one of the first vehicle states is established, the determined second detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements.

3. The method according to claim 1, wherein, If the operation cloud detects that at least one of the following second vehicle states are met, the third detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements: The last operational task performed by the autonomous driving vehicle was not completed properly; The autonomous driving operation vehicle has operational tasks to be processed; The autonomous driving operation vehicle has continuous tasks; The destination of the last task performed by the autonomous vehicle could not be found. The autonomous driving vehicle was at a temporary parking spot; The prescribed stopping time of the autonomous driving operation vehicle at the mission endpoint is less than the time threshold; Receive the abnormal information reported by the autonomous driving operation vehicle; The autonomous driving operation vehicle is in the process of being returned to service; The autonomous driving operation vehicle is in a battery swapping state; No upgrade configuration information was detected for the aforementioned autonomous driving operation vehicle; The current time period exceeds the configuration time period specified in the upgrade configuration information; The remaining battery power of the autonomous driving operation vehicle is less than a set threshold; The autonomous driving vehicle's parking status in the compliant parking area did not comply with the parking rules. The query result for the last operational task performed by the aforementioned autonomous driving vehicle was an anomaly. An error occurred when querying the real-time stations of the aforementioned autonomous driving operating vehicles.

4. The method according to claim 1, wherein, When both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the upgrade process is initiated, including: If both the second and third detection results indicate that the autonomous driving operating vehicle meets the upgrade requirements, an upgrade command is sent to the OTA client so that the OTA client can perform an upgrade operation based on the OTA upgrade task.

5. The method according to claim 1, further comprising: If at least one of the second and third detection results indicates that the autonomous driving operating vehicle does not meet the upgrade requirements, an upgrade failure instruction is sent to the OTA client, so that the OTA client sends an upgrade failure message to the OTA cloud.

6. The method according to claim 1, further comprising: If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the operation cloud is notified to update the status of the autonomous driving operation vehicle to "upgrading in progress".

7. The method according to claim 1, wherein, The upgrade task for detecting autonomous driving operating vehicles yields a first detection result, including: According to the preset polling period, poll the task messages of the OTA client to obtain the first detection result; The upgrade task for the OTA client is assigned and sent to the OTA client by the OTA cloud.

8. An OTA upgrade control device for an autonomous driving operating vehicle, comprising: The detection module is used to detect the upgrade tasks of autonomous driving operation vehicles and obtain the first detection result; The first control module is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to the status of pending upgrade when the first detection result indicates that there is an OTA upgrade task, so that the operation cloud stops assigning operation tasks to the autonomous driving operation vehicle. The second control module is used to notify the operation cloud to update the status of the autonomous driving operation vehicle to a no-upgrade-task status after the autonomous driving operation vehicle has finished processing the first detection result, so that the operation cloud can assign additional operation tasks to the autonomous driving operation vehicle. It also includes a processing module for processing the first detection result based on the following method: In response to the first detection result, a first vehicle state of the autonomous driving operating vehicle is detected to obtain a second detection result; and, Obtain the third detection result of the autonomous driving operation vehicle from the operation cloud; If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the upgrade process is initiated to perform an OTA upgrade on the autonomous driving operation vehicle.

9. The apparatus according to claim 8, wherein, The processing module is specifically used for: Detect at least one of the following first vehicle states: The autonomous driving vehicle is performing operational tasks; The autonomous driving operation vehicle is in autonomous driving mode; The autonomous driving vehicle is in motion; The autonomous driving vehicle was parked in an unauthorized area. The autonomous driving operation vehicle's parking status in the compliant parking area does not comply with the parking rules; The remaining battery power of the autonomous driving operation vehicle is less than a set threshold; The autonomous driving operation vehicle triggered a fault alarm message of a preset level or higher. The gear of the autonomous driving vehicle was not set to park. If at least one of the first vehicle states is established, the determined second detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements.

10. The apparatus according to claim 8, wherein, If the operation cloud detects that at least one of the following second vehicle states are met, the third detection result indicates that the autonomous driving operation vehicle does not meet the upgrade requirements: The last operational task performed by the autonomous driving vehicle was not completed properly; The autonomous driving operation vehicle has operational tasks to be processed; The autonomous driving operation vehicle has continuous tasks; The destination of the last task performed by the autonomous vehicle could not be found. The autonomous driving vehicle was at a temporary parking spot; The prescribed stopping time of the autonomous driving operation vehicle at the mission endpoint is less than the time threshold; Receive the abnormal information reported by the autonomous driving operation vehicle; The autonomous driving operation vehicle is in the process of being returned to service; The autonomous driving operation vehicle is in a battery swapping state; No upgrade configuration information was detected for the aforementioned autonomous driving operation vehicle; The current time period exceeds the configuration time period specified in the upgrade configuration information; The remaining battery power of the autonomous driving operation vehicle is less than a set threshold; The autonomous driving vehicle's parking status in the compliant parking area did not comply with the parking rules. The query result for the last operational task performed by the aforementioned autonomous driving vehicle was an anomaly. An error occurred when querying the real-time stations of the aforementioned autonomous driving operating vehicles.

11. The apparatus according to claim 8, wherein, The processing module is specifically used for: If both the second and third detection results indicate that the autonomous driving operating vehicle meets the upgrade requirements, an upgrade command is sent to the OTA client so that the OTA client can perform an upgrade operation based on the OTA upgrade task.

12. The apparatus of claim 8, wherein the second control module is further configured to: If at least one of the second and third detection results indicates that the autonomous driving operating vehicle does not meet the upgrade requirements, an upgrade failure instruction is sent to the OTA client, so that the OTA client sends an upgrade failure message to the OTA cloud.

13. The apparatus according to claim 8, wherein the second control module is further configured to: If both the second and third detection results indicate that the autonomous driving operation vehicle meets the upgrade requirements, the operation cloud is notified to update the state machine of the autonomous driving operation vehicle to the upgrade-in progress state.

14. The apparatus according to claim 8, wherein, The detection module is specifically used for: According to the preset polling period, poll the task messages of the OTA client to obtain the first detection result; The upgrade task for the OTA client is assigned and sent to the OTA client by the OTA cloud.

15. An electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

16. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-7.

17. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-7.

18. A vehicle comprising the electronic equipment of claim 15.

Images