OTA upgrading method and device of vehicle, electronic equipment and computer program product

Abstract

The invention discloses an OTA upgrading method and device of a vehicle, electronic equipment and a computer program product, and the method comprises the steps that the current driving state of the vehicle is monitored, and the current driving state comprises one of a power-on static state, a manual driving state and an automatic driving state; receiving and analyzing operation information reported by each domain system in the vehicle to obtain upgrading demand information of each domain system; determining a current upgrading strategy of the vehicle according to the current driving state and the upgrading demand information of each domain system; and obtaining an OTA upgrade package of the target domain system according to the current upgrade strategy, and carrying out OTA upgrade by using the OTA upgrade package. According to the method, the current driving state of the vehicle is monitored in real time, the upgradable domain system and the upgrading opportunity are intelligently selected, and the safety and stability of the upgrading process are improved; by analyzing the upgrading requirements of the domain systems, it is ensured that the upgrading content is highly matched with the actual requirements, and personalized upgrading is achieved.

Description

Technical Field

[0001] The present application relates to the field of autonomous driving technology, and in particular to a vehicle OTA upgrade method, device, electronic equipment, and computer program product. Background Art

[0002] With the rapid progress of modern automobile technology, the wave of automobile electrification and intelligence has swept across the automotive industry, bringing unprecedented changes. In this change, OTA (Over-The-Air) upgrade technology has quickly become a key means of post-maintenance and function iteration of autonomous vehicles with its advantages of remote update and immediate effect. OTA upgrades can not only significantly improve user experience, but also effectively reduce vehicle maintenance costs and accelerate the promotion and application of new functions.

[0003] However, the traditional OTA upgrade strategy often lacks detailed consideration of the actual use status of autonomous vehicles during implementation. In actual operation, autonomous vehicles will experience multiple states such as stationary, manual driving, and autonomous driving, and different states have different requirements for system resources and safety. At the same time, the autonomous driving system is complex and changeable, including multiple independent and interrelated subsystems such as the power domain, chassis domain, smart cockpit domain, smart driving domain, and body control domain. Each domain has its own unique operating logic and upgrade requirements.

[0004] Most of the OTA upgrade solutions widely used in the market currently adopt a "one-size-fits-all" strategy, that is, pushing a unified upgrade package to all vehicles. Although this approach is easy to manage, it ignores the diversity of vehicle usage status and personalized needs in different domains, which leads to a series of potential problems:

[0005] 1) Driving safety hazards: Upgrading while the vehicle is in motion or critical operations are in progress may interfere with normal driving functions and pose a threat to driving safety.

[0006] 2) System instability and resource waste: Upgrade packages that are not optimized for specific domains may contain updates that are unnecessary for specific domains. This not only increases the complexity and time cost of the upgrade process, but may also reduce system stability due to incompatibility or improper resource allocation.

[0007] 3) Lack of user autonomy: The unified push of upgrade packages deprives users of the right to selectively upgrade according to their own needs and preferences, reducing the personalization and flexibility of the user experience.

[0008] In view of at least one of the above-mentioned problems, it is urgent to develop a more sophisticated and intelligent OTA upgrade strategy to achieve accurate identification and response to vehicle usage status and different domain requirements, so as to improve the flexibility of OTA upgrades while ensuring driving safety and improving system stability. Summary of the invention

[0009] The embodiments of the present application provide a vehicle OTA upgrade method, device, electronic device, and computer program product to improve the security, system stability, and upgrade flexibility of the OTA upgrade process of an autonomous driving vehicle.

[0010] The present application embodiment adopts the following technical solutions:

[0011] In a first aspect, an embodiment of the present application provides an OTA upgrade method for a vehicle, wherein the OTA upgrade method for a vehicle includes:

[0012] Monitoring a current driving state of the vehicle, wherein the current driving state includes one of a powered-on static state, a manual driving state, and an automatic driving state;

[0013] Receive and analyze the operating information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system;

[0014] Determining a current upgrade strategy for the vehicle according to the current driving state of the vehicle and upgrade requirement information of each domain system;

[0015] An OTA upgrade package of the target domain system is obtained according to the current upgrade strategy of the vehicle, and the OTA upgrade package is used to perform OTA upgrade on the target domain system.

[0016] Optionally, monitoring the current driving state of the vehicle includes:

[0017] Obtain real-time vehicle operation data through on-board sensors and on-board diagnostic systems;

[0018] Monitor whether the vehicle is in a powered-on stationary state, a manual driving state, or an automatic driving state based on the real-time operating data of the vehicle.

[0019] Optionally, the receiving and analyzing the operation information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system includes:

[0020] Receiving operation information reported by each domain system in the vehicle, wherein the domain system includes at least one of a power domain system, a chassis domain system, an intelligent cockpit domain system, an intelligent driving domain system, and a body control domain system;

[0021] Analyze the operation information reported by each domain system to determine the working status of each domain system, wherein the working status includes a non-working status, a partial function abnormal status, a function to be optimized status, and a normal working status;

[0022] Determine the domain system that needs to be upgraded based on the working status of each domain system.

[0023] Optionally, determining a current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system includes:

[0024] According to the current driving state of the vehicle, determining an upgradeable domain system among the domain systems that need to be upgraded as a target domain system;

[0025] An upgrade priority corresponding to the target domain system is determined according to a working status corresponding to the target domain system.

[0026] Optionally, determining the current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system further includes:

[0027] Obtaining an OTA upgrade package corresponding to the target domain system, wherein the OTA upgrade package includes upgrade dependency information;

[0028] The upgrade priority is updated according to the upgrade dependency information corresponding to the target domain system to obtain an updated upgrade priority.

[0029] Optionally, obtaining an OTA upgrade package corresponding to the target domain system includes:

[0030] Determine upgrade function description information corresponding to the target domain system according to the upgrade requirement information corresponding to the target domain system;

[0031] According to the upgrade function description information corresponding to the target domain system, matching is performed in all OTA upgrade packages corresponding to the target domain system to obtain a target OTA upgrade package corresponding to the target domain system.

[0032] Optionally, acquiring an OTA upgrade package of the target domain system according to a current upgrade strategy of the vehicle, and performing OTA upgrade on the target domain system using the OTA upgrade package further includes:

[0033] Performing security verification on the OTA upgrade package of the target domain system;

[0034] If the security verification is passed, determine whether the OTA upgrade timing condition is triggered;

[0035] When the OTA upgrade opportunity condition is triggered, the target domain system is OTA upgraded using the OTA upgrade package of the target domain system.

[0036] In a second aspect, an embodiment of the present application further provides an OTA upgrade device for a vehicle, wherein the OTA upgrade device for the vehicle comprises:

[0037] A monitoring unit, used to monitor a current driving state of the vehicle, wherein the current driving state includes one of a power-on static state, a manual driving state, and an automatic driving state;

[0038] A demand analysis unit is used to receive and analyze the operation information reported by each domain system in the vehicle to obtain the upgrade demand information of each domain system;

[0039] A determination unit, configured to determine a current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system;

[0040] The upgrade unit is used to obtain an OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle, and use the OTA upgrade package to perform OTA upgrade on the target domain system.

[0041] In a third aspect, an embodiment of the present application further provides an electronic device, including:

[0042] A processor; and a memory arranged to store computer executable instructions, which, when executed, cause the processor to perform any of the aforementioned vehicle OTA upgrade methods.

[0043] In a fourth aspect, an embodiment of the present application further provides a computer program product, comprising a computer program or instructions, which, when executed by a processor, implements any of the aforementioned vehicle OTA upgrade methods.

[0044] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: the OTA upgrade method of the vehicle in the embodiments of the present application first monitors the current driving state of the vehicle, and the current driving state includes one of the power-on static state, the manual driving state and the automatic driving state; then receives and analyzes the operation information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system; then determines the current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system; finally, obtains the OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle, and uses the OTA upgrade package to perform OTA upgrade on the target domain system. The OTA upgrade method of the vehicle in the embodiments of the present application improves the security and stability of the upgrade process by monitoring the current driving state of the vehicle in real time, intelligently selecting the upgradeable domain system and the upgrade timing, and on the other hand, by analyzing the upgrade requirements of each domain system in the vehicle, ensures that the upgrade content is highly matched with the actual needs, realizes personalized upgrades, optimizes resource allocation, and improves user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0046] Figure 1 A schematic diagram of a flow chart of an OTA upgrade method for a vehicle in an embodiment of the present application;

[0047] Figure 2 This is a schematic diagram of the structure of an OTA upgrade device for a vehicle in an embodiment of the present application;

[0048] Figure 3 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field of the system without making creative work are within the scope of protection of this application.

[0050] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0051] The present application embodiment provides a vehicle OTA upgrade method, such as Figure 1As shown, a flow chart of an OTA upgrade method for a vehicle in an embodiment of the present application is provided, and the OTA upgrade method for the vehicle at least includes the following steps S110 to S140:

[0052] Step S110, monitoring the current driving state of the vehicle, wherein the current driving state includes one of a powered-on static state, a manual driving state, and an automatic driving state.

[0053] When performing an OTA upgrade of an autonomous driving vehicle, the embodiment of the present application needs to monitor the current driving state of the autonomous driving vehicle in real time. The current driving state defined in the embodiment of the present application mainly includes the power-on static state, the manual driving state, and the autonomous driving state. The power-on static state mainly refers to the state in which the vehicle has been powered on but has not yet started driving. At this time, the electronic systems, sensors, etc. inside the vehicle have been powered on and are in standby or initialization state, but the engine (or motor) has not been started and the vehicle remains stationary. In this state, the vehicle may be performing self-test, system initialization, and other operations.

[0054] Manual driving refers to the state where the autonomous vehicle is completely controlled and operated by the driver. In this state, the driver is responsible for the vehicle's acceleration, braking, steering and other driving actions, and needs to pay attention to road conditions, traffic signals and the surrounding environment at all times to ensure driving safety. The assisted driving systems of autonomous vehicles (such as lane keeping, automatic braking, etc.) may still be available in the manual driving state, but the driver needs to maintain control of the vehicle and be ready to take over the driving rights of the vehicle at any time.

[0055] The autonomous driving state refers to the state in which the autonomous driving vehicle can complete the driving task autonomously without the direct control of the driver. In this state, the vehicle perceives the surrounding environment through built-in sensors, cameras, radars and other equipment, and uses advanced algorithms and artificial intelligence technology to analyze and make decisions to control the vehicle's driving direction and speed. Autonomous driving vehicles can automatically adjust their driving strategies based on road conditions, traffic signals, and the behavior of surrounding vehicles and pedestrians to ensure safe and efficient driving.

[0056] It should be noted that the performance of autonomous driving status of autonomous vehicles will be different at different autonomous driving levels. For example, at level L0 (manual driving), the vehicle is completely controlled by the driver, that is, the above-mentioned manual driving state; while at level L5 (fully autonomous driving), the vehicle can drive autonomously on any road and in any environment without the intervention of the driver.

[0057] The monitoring and judgment of the above status information is the basis for determining whether and when to perform an OTA upgrade. Of course, the specific driving statuses included can be flexibly set by technicians in this field according to the actual scenario, and will not be listed here one by one.

[0058] Step S120, receiving and analyzing the operation information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system.

[0059] Autonomous driving vehicles generally include multiple independent but interrelated domain systems such as the power domain, chassis domain, smart cockpit domain, smart driving domain, and body control domain. Different domain systems are responsible for realizing different vehicle functions and have different upgrade requirements. Therefore, the embodiment of the present application also requires each domain system to report its own operating information, and then perform upgrade demand analysis on the operating information reported by each domain system to obtain the upgrade demand information of each domain system. The upgrade demand analysis mainly analyzes whether each domain system currently needs to be upgraded and the urgency and importance of the upgrade.

[0060] Step S130, determining the current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system.

[0061] The driving state of an autonomous vehicle is crucial to the formulation of its upgrade strategy. For example, when the vehicle is powered on and stationary, it is an ideal time to perform software upgrades and system maintenance because the vehicle is not driving. The upgrade strategy adopted at this time can be a comprehensive upgrade of multiple domain systems, including those that take a long time or may affect the driving safety of the vehicle. In the manual driving state, the driver is responsible for the driving safety of the vehicle. Therefore, the upgrade strategy adopted should try to avoid interfering with the driver's driving operation, such as avoiding upgrades at critical driving moments. Upgrades that have little impact on vehicle driving can be selected, such as software updates or performance optimizations of non-critical systems. In the autonomous driving state, the vehicle is controlled by the autonomous driving system. The upgrade strategy adopted needs to ensure that the upgrade process will not have a serious impact on the normal operation of the autonomous driving system. Upgrades that have little impact on the autonomous driving system can be selected, such as fine-tuning of non-core algorithms or calibration of sensor data.

[0062] In addition to considering the driving status of the vehicle, the upgrade strategy also needs to be determined based on the upgrade requirements of each domain system. For example, if a domain system has serious safety hazards or performance issues and needs to be upgraded immediately, the upgrade of this domain system should be prioritized regardless of the driving status of the vehicle. For upgrade requirements that do not affect the driving safety or performance of the vehicle, they can be arranged based on the driving status of the vehicle and the upgrade priority.

[0063] When determining the current upgrade strategy of the autonomous driving vehicle, the embodiment of the present application comprehensively considers the driving status of the vehicle and the upgrade requirement information of each domain system, so as to formulate the best upgrade strategy and ensure the security of the upgrade process and the stability of the system.

[0064] Step S140: acquiring an OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle, and performing OTA upgrade on the target domain system using the OTA upgrade package.

[0065] After determining the currently adopted upgrade strategy, it is necessary to obtain the corresponding OTA upgrade package according to the upgrade requirement information of the domain system to be upgraded contained in the upgrade strategy, and use the OTA upgrade package to upgrade the domain system.

[0066] The OTA upgrade method for a vehicle in the embodiment of the present application improves the security and stability of the upgrade process by, on the one hand, real-time monitoring of the current driving status of the autonomous driving vehicle and intelligently selecting upgradeable domain systems and upgrade timings. On the other hand, by analyzing the upgrade requirements of each domain system in the autonomous driving vehicle, it ensures that the upgrade content is highly matched with actual needs, thereby achieving personalized upgrades, optimizing resource allocation, and improving user experience.

[0067] In some embodiments of the present application, monitoring the current driving status of the vehicle includes: acquiring real-time operating data of the vehicle through on-board sensors and an on-board diagnostic system; and monitoring whether the vehicle is in a powered-on stationary state, a manually driven state, or an automatically driving state based on the real-time operating data of the vehicle.

[0068] The monitoring of the current driving status of the autonomous driving vehicle in the embodiment of the present application mainly relies on on-board sensors and on-board diagnostic systems. The real-time operation data of the autonomous driving vehicle is obtained through the on-board sensors and on-board diagnostic systems, and based on these data, it is determined whether the vehicle is currently in a powered-on stationary state, a manually driven state, or an autonomous driving state.

[0069] Specifically, autonomous vehicles are equipped with a variety of sensors, such as cameras, LiDAR, GPS, and INS. These sensors can capture real-time information about the vehicle's surroundings, including road conditions, traffic conditions, obstacle locations, and the vehicle's own motion status. By analyzing these sensor data, key information such as the vehicle's speed, acceleration, steering angle, position coordinates, and relative distance to other vehicles and pedestrians can be obtained.

[0070] The on-board diagnostic system (OBD) is a system used to monitor vehicle performance and diagnose potential faults. It can collect and analyze data from various vehicle systems, including the engine, transmission, braking system, steering system, and body control system. Through the OBD system, you can obtain information about the working status, performance parameters, and fault warnings of various vehicle systems.

[0071] After obtaining the real-time operating data of the autonomous driving vehicle, the data can be used to monitor the driving status of the vehicle. For example, by analyzing the data of the vehicle's power system (such as battery voltage, current, etc.), it can be determined whether the vehicle is powered on. At the same time, combined with the vehicle's motion status data (such as speed, acceleration, etc.), it can be determined whether the vehicle is stationary. When the vehicle is powered on and stationary, it can be considered that the vehicle is in a powered-on stationary state.

[0072] By analyzing the interaction data between the driver and the vehicle (such as steering wheel rotation angle, accelerator pedal position, brake pedal pressure, etc.), it can be determined whether the driver is controlling the vehicle. At the same time, combined with the status data of the autonomous driving system (such as the activation status and working mode of the autonomous driving system, etc.), it can be further confirmed whether the vehicle is in a manual driving state. When the driver is controlling the vehicle and the autonomous driving system is not enabled or is in auxiliary mode, it can be considered that the vehicle is in a manual driving state.

[0073] By analyzing the status data of the autonomous driving system (such as the activation status, working mode, path planning results, etc. of the autonomous driving system), it can be determined whether the vehicle is being controlled by the autonomous driving system. At the same time, combined with the vehicle's motion status data (such as speed, acceleration, steering angle, etc.) and the perception data of the surrounding environment (such as radar and camera detection results, etc.), the control effect of the autonomous driving system can be further verified. When the autonomous driving system is enabled and is controlling the vehicle's driving, it can be considered that the vehicle is in the autonomous driving state.

[0074] Therefore, the embodiment of the present application obtains the real-time operation data of the autonomous driving vehicle through the vehicle-mounted sensors and the vehicle-mounted diagnostic system, and monitors the driving status of the vehicle based on these data, so as to accurately judge the current driving status of the autonomous driving vehicle. This is of great significance for formulating reasonable upgrade strategies, ensuring vehicle driving safety, and improving user experience.

[0075] In some embodiments of the present application, the receiving and analyzing operating information reported by each domain system in the vehicle to obtain upgrade requirement information of each domain system includes: receiving operating information reported by each domain system in the vehicle, the domain system including at least one of a power domain system, a chassis domain system, an intelligent cockpit domain system, an intelligent driving domain system and a body control domain system; analyzing the operating information reported by each domain system to determine the working status of each domain system, the working status including a non-working status, a partial function abnormal status, a function to be optimized status and a normal working status; determining the domain system that needs to be upgraded according to the working status of each domain system.

[0076] The domain systems in the autonomous driving vehicle of the embodiment of the present application include but are not limited to the power domain (such as the engine control unit), chassis domain (such as the suspension system), smart cockpit domain (such as the infotainment system), smart driving domain (such as the autonomous driving software) and body control domain (such as the window control). The purpose of domain demand analysis is to identify which domain systems currently need to be upgraded, as well as the urgency and importance of the upgrade.

[0077] Different domain systems report different specific operating information. For example, the power domain can report the following information:

[0078] 1) Powertrain status: including the operating status and performance parameters of the engine, motor, battery, etc.

[0079] 2) Fault diagnosis information: fault diagnosis results and fault codes of each subsystem in the power domain.

[0080] 3) Energy consumption information: vehicle energy consumption, including fuel consumption, electricity consumption, etc.

[0081] The chassis domain can report the following information:

[0082] 1) Chassis control system status: including the operating status of the transmission system, driving system, steering system and braking system.

[0083] 2) Sensor information: data from various sensors within the chassis domain, such as wheel speed sensors, steering angle sensors, etc.

[0084] 3) Chassis control system fault information: fault diagnosis results and fault codes of each subsystem within the chassis domain.

[0085] The smart cockpit domain can report the following information:

[0086] 1) Entertainment system status: operating status of the in-vehicle infotainment system, multimedia system, etc.

[0087] 2) Human-computer interaction information: records of interactions between users and the intelligent cockpit system, such as touch screen operations, voice commands, etc.

[0088] 3) System performance parameters: operating efficiency, response time, etc. of the smart cockpit system.

[0089] The intelligent driving domain can report the following information:

[0090] 1) Autonomous driving status: the activation status and working mode of the autonomous driving system.

[0091] 2) Sensor data: Sensor data used by the autonomous driving system, such as cameras, lidar, etc.

[0092] 3) Performance parameters of the autonomous driving system: path planning capability, decision-making capability, motion control capability, etc. of the autonomous driving system.

[0093] The body control domain can report the following information:

[0094] 1) Vehicle body electronic system status: including the operating status of lights, windows, door locks, etc.

[0095] 2) Safety system status: the status of the vehicle's safety system, such as airbags, seat belts, etc.

[0096] 3) Body control system fault information: fault diagnosis results and fault codes of each subsystem within the body domain.

[0097] It should be noted that the specific operating information to be reported can be flexibly set by those skilled in the art according to actual needs, and no specific limitation is made here.

[0098] Based on the above operation information, the upgrade demand analysis can be performed by preprocessing the received operation information, such as data cleaning and format conversion. Then the working status of each domain system can be analyzed to determine whether there are abnormalities or potential faults. The working status can be specifically divided into completely inoperable status, partially abnormal function status, function to be optimized status, and normal working status. The performance parameters of each domain system can also be evaluated to determine whether they meet the expected standards. Based on the operation status analysis and performance evaluation results, it can be determined whether each domain system needs to be upgraded, the urgency and importance of the upgrade can be evaluated, and the upgrade priority can be determined.

[0099] In some embodiments of the present application, determining the current upgrade strategy of the vehicle based on the current driving state of the vehicle and the upgrade requirement information of each domain system includes: determining an upgradeable domain system among the domain systems that need to be upgraded as the target domain system based on the current driving state of the vehicle; and determining the upgrade priority corresponding to the target domain system based on the working state corresponding to the target domain system.

[0100] When determining the current upgrade strategy based on the current driving status of the autonomous driving vehicle and the upgrade requirement information of each domain system, there are mainly two key steps involved: one is to determine the domain system that can be upgraded (target domain system) according to the current driving status of the vehicle; the other is to determine its upgrade priority according to the working status of the target domain system.

[0101] Specifically, the driving state of the autonomous vehicle (such as powered-on static state, manual driving state, and autonomous driving state) has a direct impact on which domain systems can be upgraded. For example, when the vehicle is powered-on static state, since the vehicle is not driving, almost all domain systems can be upgraded. When the vehicle is in manual driving or autonomous driving state, the upgraded domain system needs to be carefully selected to avoid interfering with the driver's driving operation or the normal operation of the autonomous driving system.

[0102] Therefore, the embodiment of the present application can first screen out domain systems that can be upgraded in the current state according to the current driving state of the vehicle and the upgrade requirement information of each domain system. These domain systems should meet the following conditions: the upgrade requirement is urgent or important, and the upgrade process will not have a serious impact on the driving safety of the vehicle.

[0103] After determining the currently upgradeable target domain system, the upgrade priority or upgrade order of the domain system can be further determined in combination with the working status of the target domain system. The working status of the target domain system in the embodiment of the present application can be divided into a non-working state, a partially functional abnormal state, a function to be optimized state, and a normal working state.

[0104] Inoperable state: If the target domain system is in an inoperable state, that is, completely failed, then its upgrade priority should be the highest, because such failures may directly affect the safety or functionality of the vehicle.

[0105] Partially functional abnormal state: If the target domain system is in a partially functional abnormal state, that is, some functions fail or performance degrades, but its core functions are still available, then its upgrade priority is the second. This type of failure may not have a direct impact on the safety of the vehicle, but it will reduce the user experience or vehicle performance.

[0106] Functionality to be optimized: If the target domain system is in a functionality to be optimized state, that is, its performance or functionality still has room for improvement, then its upgrade priority can be relatively low. This type of upgrade is usually to improve user experience or vehicle performance, rather than to solve fault problems.

[0107] Normal working status: If the target domain system is in normal working status, that is, its performance and functions meet the expected standards, then its upgrade priority can be the lowest. Unless there are specific upgrade requirements (such as new functions, performance improvements, etc.), the upgrade can be postponed.

[0108] When determining the upgrade priority, in addition to considering the working status of the target domain system, other factors can also be considered comprehensively, such as the urgency of the upgrade, the impact of the upgrade on vehicle driving safety, the time and resources required for the upgrade, etc.

[0109] By comprehensively considering these factors, a reasonable upgrade strategy can be formulated to ensure that the most important upgrade needs are met first without affecting vehicle driving safety.

[0110] The embodiment of the present application determines the target domain system according to the current driving status of the autonomous driving vehicle and the upgrade requirement information of each domain system, and determines its upgrade priority according to the working status of the target domain system, thereby formulating a more reasonable and effective upgrade strategy, which is of great significance for improving the safety, reliability and user experience of autonomous driving vehicles.

[0111] In some embodiments of the present application, determining the current upgrade strategy of the vehicle based on the current driving state of the vehicle and the upgrade requirement information of each domain system also includes: obtaining an OTA upgrade package corresponding to the target domain system, the OTA upgrade package including upgrade dependency information; updating the upgrade priority according to the upgrade dependency information corresponding to the target domain system to obtain an updated upgrade priority.

[0112] When determining the current upgrade strategy of the autonomous driving vehicle, the embodiment of the present application may further consider the upgrade dependency information in the OTA upgrade package corresponding to the target domain system in addition to considering the current driving state of the vehicle and the working state of the target domain system, and update the upgrade priority based on this information.

[0113] An OTA upgrade package is a software upgrade package downloaded to an autonomous vehicle via a wireless network (such as 4G / 5G, Wi-Fi, etc.), which contains all or part of the code, configuration files, resource files, etc. required for the target domain system upgrade. After determining the target domain system, the autonomous vehicle can obtain the OTA upgrade package corresponding to the target domain system from a cloud server or other reliable upgrade source.

[0114] Upgrade dependency information refers to the information contained in the OTA upgrade package about the prerequisites or dependencies required for the target domain system upgrade. This information may include version requirements of other domain systems, configuration requirements of hardware resources, version requirements of software dependency libraries, etc. After obtaining the OTA upgrade package, the autonomous driving vehicle can parse the upgrade dependency information.

[0115] After obtaining the upgrade dependency information through parsing, the upgrade priority of the target domain system can be updated based on the information. Specifically, if the upgrade of the target domain system depends on the upgrade of other domain systems, or requires the support of specific hardware resources or software dependency libraries, then these dependencies may affect the upgrade sequence and feasibility.

[0116] Therefore, the embodiment of the present application can adaptively adjust the upgrade priority of the target domain system according to the upgrade dependency information. For example, if the upgrade of the target domain system depends on the upgrade of another domain system, then it may be necessary to upgrade the dependent domain system first, and then upgrade the target domain system. Alternatively, if the upgrade of the target domain system requires the support of specific hardware resources or software dependency libraries, and the current vehicle does not meet these requirements, then it may be necessary to postpone the upgrade until these requirements are met.

[0117] The embodiment of the present application obtains the OTA upgrade package corresponding to the target domain system and parses the upgrade dependency information therein to update the upgrade priority, so as to more accurately determine the current upgrade strategy, ensure that the most important upgrade requirements are resolved first and the dependencies in the upgrade process are met without affecting the vehicle driving safety.

[0118] In some embodiments of the present application, obtaining the OTA upgrade package corresponding to the target domain system includes: determining the upgrade function description information corresponding to the target domain system according to the upgrade requirement information corresponding to the target domain system; matching among all OTA upgrade packages corresponding to the target domain system according to the upgrade function description information corresponding to the target domain system to obtain the target OTA upgrade package corresponding to the target domain system.

[0119] When obtaining the OTA upgrade package corresponding to the target domain system, the specific upgrade requirements of the target domain system can be analyzed first. These requirements can come from multiple aspects such as system internal diagnosis, user feedback, security updates, performance optimization, etc. Based on the upgrade requirement information obtained by analysis, the corresponding upgrade function description information can be generated, for example, it can include the problems that need to be fixed, the functions to be implemented, the specific content of performance improvement, etc.

[0120] In actual upgrade scenarios, a domain system may involve upgrades in many aspects, and there will be multiple upgrade packages. Based on all available OTA upgrade packages, these upgrade packages are matched one by one according to the above upgrade function description information. This matching process may involve comparison and analysis of metadata, version information, function lists, etc. in the upgrade packages, so as to find the OTA upgrade package that best matches the upgrade requirements of the target domain system for subsequent upgrade operations to meet the upgrade requirements of the target domain system.

[0121] In some embodiments of the present application, obtaining the OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle and performing OTA upgrade on the target domain system using the OTA upgrade package also includes: performing security verification on the OTA upgrade package of the target domain system; if the security verification passes, determining whether the OTA upgrade timing condition is currently triggered; if the OTA upgrade timing condition is triggered, performing OTA upgrade on the target domain system using the OTA upgrade package of the target domain system.

[0122] Before executing the upgrade, the embodiment of the present application may also first perform a security assessment on the upgrade package to further ensure that the upgrade will not affect vehicle safety. The security assessment may include checking the digital signature of the upgrade package to verify its source, checking the compatibility and integrity of the upgrade package, and simulating the upgrade process to predict possible problems. The specific security verification method to be adopted can be flexibly set by those skilled in the art according to actual needs, and is not specifically limited here.

[0123] In addition, it is possible to further determine whether the current upgrade timing is met, and the upgrade process can be executed within a predetermined time, such as when the vehicle is stationary or during a user-specified non-peak period, so as to minimize the impact on the normal functions of the autonomous driving vehicle.

[0124] The embodiments of the present application can also monitor the upgrade process in real time to ensure the smooth progress of the upgrade, for example, it can track the progress of the upgrade, detect any abnormal situation, and abort or roll back the upgrade when necessary.

[0125] After the upgrade is complete, system verification and testing can be performed to ensure that the system is running stably, which may include starting the vehicle's self-test program to verify that all upgraded software and firmware work as expected. If the verification fails after the upgrade, the system may need to perform a rollback operation to restore to the state before the upgrade and notify a technician to troubleshoot the problem.

[0126] The present application also provides a vehicle OTA upgrade device 200, such as Figure 2 As shown, a schematic diagram of the structure of an OTA upgrade device for a vehicle in an embodiment of the present application is provided, wherein the OTA upgrade device 200 for a vehicle includes: a monitoring unit 210, a demand analysis unit 220, a determination unit 230, and an upgrade unit 240, wherein:

[0127] A monitoring unit 210, configured to monitor a current driving state of the vehicle, wherein the current driving state includes one of a power-on static state, a manual driving state, and an automatic driving state;

[0128] The demand analysis unit 220 is used to receive and analyze the operation information reported by each domain system in the vehicle to obtain the upgrade demand information of each domain system;

[0129] A determination unit 230, configured to determine a current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system;

[0130] The upgrading unit 240 is used to obtain an OTA upgrade package of the target domain system according to the current upgrading strategy of the vehicle, and perform OTA upgrading on the target domain system using the OTA upgrade package.

[0131] In some embodiments of the present application, the monitoring unit 210 is specifically used to: obtain real-time operation data of the vehicle through on-board sensors and an on-board diagnostic system; and monitor whether the vehicle is in a powered-on stationary state, a manually driven state, or an automatically driven state based on the real-time operation data of the vehicle.

[0132] In some embodiments of the present application, the demand analysis unit 220 is specifically used to: receive operating information reported by each domain system in the vehicle, the domain system including at least one of a power domain system, a chassis domain system, an intelligent cockpit domain system, an intelligent driving domain system, and a body control domain system; analyze the operating information reported by each domain system to determine the working status of each domain system, the working status including a non-working state, a partial functional abnormal state, a function to be optimized state, and a normal working state; determine the domain system that needs to be upgraded according to the working status of each domain system.

[0133] In some embodiments of the present application, the determination unit 230 is specifically used to: determine an upgradeable domain system among the domain systems that need to be upgraded as a target domain system according to the current driving state of the vehicle; and determine the upgrade priority corresponding to the target domain system according to the working state corresponding to the target domain system.

[0134] In some embodiments of the present application, the determination unit 230 is specifically used to: obtain an OTA upgrade package corresponding to the target domain system, the OTA upgrade package including upgrade dependency information; update the upgrade priority according to the upgrade dependency information corresponding to the target domain system to obtain an updated upgrade priority.

[0135] In some embodiments of the present application, the determination unit 230 is specifically used to: determine the upgrade function description information corresponding to the target domain system according to the upgrade requirement information corresponding to the target domain system; and match all OTA upgrade packages corresponding to the target domain system according to the upgrade function description information corresponding to the target domain system to obtain the target OTA upgrade package corresponding to the target domain system.

[0136] In some embodiments of the present application, the upgrade unit 240 is specifically used to: perform security verification on the OTA upgrade package of the target domain system; if the security verification passes, determine whether the OTA upgrade timing condition is currently triggered; if the OTA upgrade timing condition is triggered, use the OTA upgrade package of the target domain system to perform OTA upgrade on the target domain system.

[0137] It can be understood that the OTA upgrade device of the above-mentioned vehicle can implement the various steps of the OTA upgrade method of the vehicle provided in the aforementioned embodiments, and the relevant explanations about the OTA upgrade method of the vehicle are applicable to the OTA upgrade device of the vehicle, which will not be repeated here.

[0138] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 3 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0139] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0140] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0141] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming the vehicle's OTA upgrade device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0142] Monitoring a current driving state of the vehicle, wherein the current driving state includes one of a powered-on static state, a manual driving state, and an automatic driving state;

[0143] Receive and analyze the operating information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system;

[0144] Determining a current upgrade strategy for the vehicle according to the current driving state of the vehicle and upgrade requirement information of each domain system;

[0145] An OTA upgrade package of the target domain system is obtained according to the current upgrade strategy of the vehicle, and the OTA upgrade package is used to perform OTA upgrade on the target domain system.

[0146] The above application Figure 1 The method performed by the OTA upgrade device of the vehicle disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in a decoding processor. The software module can be located in a storage medium with mature systems in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0147] The present application also provides a computer program product, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 1 The method performed by the OTA upgrade device of the vehicle in the illustrated embodiment is specifically used to perform:

[0148] Monitoring a current driving state of the vehicle, wherein the current driving state includes one of a powered-on static state, a manual driving state, and an automatic driving state;

[0149] Receive and analyze the operating information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system;

[0150] Determining a current upgrade strategy for the vehicle according to the current driving state of the vehicle and upgrade requirement information of each domain system;

[0151] An OTA upgrade package of the target domain system is obtained according to the current upgrade strategy of the vehicle, and the OTA upgrade package is used to perform OTA upgrade on the target domain system.

[0152] It should be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0153] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0154] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0156] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0157] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0158] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0159] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0160] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0161] The above description is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of the claims of the present application.

Claims

1. A vehicle OTA upgrade method, wherein: The OTA upgrade method of the vehicle includes: Monitoring a current driving state of the vehicle, wherein the current driving state includes one of a powered-on static state, a manual driving state, and an automatic driving state; Receive and analyze the operating information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system; Determining a current upgrade strategy for the vehicle according to the current driving state of the vehicle and upgrade requirement information of each domain system; An OTA upgrade package of the target domain system is obtained according to the current upgrade strategy of the vehicle, and the OTA upgrade package is used to perform OTA upgrade on the target domain system.

2. The OTA upgrade method for a vehicle as claimed in claim 1, wherein: The monitoring of the current driving state of the vehicle includes: Obtain real-time vehicle operation data through on-board sensors and on-board diagnostic systems; Monitor whether the vehicle is in a powered-on stationary state, a manual driving state, or an automatic driving state based on the real-time operating data of the vehicle.

3. The OTA upgrade method for a vehicle as claimed in claim 1, wherein: The receiving and analyzing the operation information reported by each domain system in the vehicle to obtain the upgrade requirement information of each domain system includes: Receiving operation information reported by each domain system in the vehicle, wherein the domain system includes at least one of a power domain system, a chassis domain system, an intelligent cockpit domain system, an intelligent driving domain system, and a body control domain system; Analyze the operation information reported by each domain system to determine the working status of each domain system, wherein the working status includes a non-working status, a partial function abnormal status, a function to be optimized status, and a normal working status; Determine the domain system that needs to be upgraded based on the working status of each domain system.

4. The OTA upgrade method for a vehicle as claimed in claim 3, wherein: Determining the current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system includes: According to the current driving state of the vehicle, determining an upgradeable domain system among the domain systems that need to be upgraded as a target domain system; An upgrade priority corresponding to the target domain system is determined according to a working status corresponding to the target domain system.

5. The OTA upgrade method for a vehicle as claimed in claim 4, wherein: Determining the current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system also includes: Obtaining an OTA upgrade package corresponding to the target domain system, wherein the OTA upgrade package includes upgrade dependency information; The upgrade priority is updated according to the upgrade dependency information corresponding to the target domain system to obtain an updated upgrade priority.

6. The OTA upgrade method for a vehicle as claimed in claim 5, wherein: The obtaining of the OTA upgrade package corresponding to the target domain system includes: Determine upgrade function description information corresponding to the target domain system according to the upgrade requirement information corresponding to the target domain system; According to the upgrade function description information corresponding to the target domain system, matching is performed in all OTA upgrade packages corresponding to the target domain system to obtain a target OTA upgrade package corresponding to the target domain system.

7. The OTA upgrade method for a vehicle as claimed in claim 1, wherein: The acquiring the OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle, and performing OTA upgrade on the target domain system using the OTA upgrade package further includes: Performing security verification on the OTA upgrade package of the target domain system; If the security verification is passed, determine whether the OTA upgrade timing condition is triggered; When the OTA upgrade opportunity condition is triggered, the target domain system is OTA upgraded using the OTA upgrade package of the target domain system.

8. An OTA upgrade device for a vehicle, wherein: The OTA upgrade device of the vehicle includes: A monitoring unit, used to monitor a current driving state of the vehicle, wherein the current driving state includes one of a power-on static state, a manual driving state, and an automatic driving state; A demand analysis unit is used to receive and analyze the operation information reported by each domain system in the vehicle to obtain the upgrade demand information of each domain system; A determination unit, configured to determine a current upgrade strategy of the vehicle according to the current driving state of the vehicle and the upgrade requirement information of each domain system; The upgrade unit is used to obtain an OTA upgrade package of the target domain system according to the current upgrade strategy of the vehicle, and use the OTA upgrade package to perform OTA upgrade on the target domain system.

9. An electronic device, comprising: processor; and a memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor executes the OTA upgrade method for the vehicle according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program or instructions, wherein when the computer program or instructions are executed by a processor, the OTA upgrade method for the vehicle according to any one of claims 1 to 7 is implemented.

Images