Software version updating method and device of vehicle, equipment and medium

Abstract

The embodiment of the invention discloses a software version updating method and device of a vehicle, equipment and a medium. The method comprises the steps that if it is determined that the data monitoring result of the in-vehicle controller is abnormal, whether the current software version of the abnormal in-vehicle controller is the latest software version or not is judged; if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version, obtaining the latest software version of a target in-vehicle controller; the target in-vehicle controller comprises an abnormal in-vehicle controller; and updating the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller. According to the technical scheme, when the data monitoring result is abnormal, the software version of the target in-vehicle controller is updated, so that the situation that the whole vehicle system is updated in the past is avoided, the network flow is saved, and the updating rate is increased.

Description

Technical Field

[0001] The present invention relates to the field of vehicle OTA technology, and in particular to a vehicle software version updating method, device, equipment and medium. Background Art

[0002] With the development of society, the degree of intelligent networking of vehicles is rapidly increasing. With the continuous improvement of software complexity, the frequency of software updates in vehicle systems is getting higher and higher.

[0003] When the vehicle system performs software updates, multiple in-vehicle controllers are usually required to perform software updates. If an abnormality occurs in the software update of a certain controller, the vehicle system needs to be updated again. When the entire vehicle system is updated again, there is a problem of consuming network traffic and wasting user time. Summary of the invention

[0004] The present invention provides a vehicle software version updating method, device, equipment and medium, which can reduce the network traffic consumed when the software version of the vehicle system is updated again.

[0005] According to one aspect of the present invention, a method for updating software version of a vehicle is provided, the method comprising:

[0006] If it is determined that the data monitoring result of the in-vehicle controller is abnormal, determining whether the current software version of the abnormal in-vehicle controller is the latest software version;

[0007] If the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version, then obtaining the latest software version of the target in-vehicle controller; the target in-vehicle controller includes the abnormal in-vehicle controller;

[0008] The software version of the target in-vehicle controller is updated based on the latest software version of the target in-vehicle controller.

[0009] According to another aspect of the present invention, there is provided a vehicle software version updating device, comprising:

[0010] A software version judgment module is used to judge whether the current software version of the abnormal in-vehicle controller is the latest software version if it is determined that the data monitoring result of the in-vehicle controller is abnormal;

[0011] The latest software version acquisition module is used to acquire the latest software version of the target in-vehicle controller if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version; the target in-vehicle controller includes the abnormal in-vehicle controller;

[0012] The version update module is used to update the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] at least one processor; and

[0015] a memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle software version update method described in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the vehicle software version update method described in any embodiment of the present invention when executed.

[0018] The technical solution of the embodiment of the present application includes: if it is determined that the data monitoring result of the in-vehicle controller is abnormal, then determine whether the current software version of the abnormal in-vehicle controller is the latest software version; if the version determination result is that the current software version of the abnormal in-vehicle controller is not the latest software version, then obtain the latest software version of the target in-vehicle controller; the target in-vehicle controller includes the abnormal in-vehicle controller; based on the latest software version of the target in-vehicle controller, the software version of the target in-vehicle controller is updated. This technical solution updates the software version of the target in-vehicle controller when the data monitoring result is abnormal, thereby avoiding the previous situation of updating the entire vehicle system, saving network traffic, and improving the update rate.

[0019] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1is a flowchart of a vehicle software version update method provided according to Embodiment 1 of the present application;

[0022] Figure 2 is a flowchart of a vehicle software version update method provided according to Embodiment 2 of the present application;

[0023] Figure 3 It is a structural schematic diagram of a vehicle software version updating device provided according to Embodiment 3 of the present application;

[0024] Figure 4 It is a structural diagram of an electronic device that implements a vehicle software version update method according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only embodiments of a part of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0026] It should be noted that the terms "first", "second", "target", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] Embodiment 1

[0028] Figure 1 A flowchart of a vehicle software version update method is provided for the first embodiment of the present application. The embodiment of the present application is applicable to the case of performing software updates on vehicle systems. The method can be executed by a vehicle software version update device. The vehicle software version update device can be implemented in the form of hardware and / or software. The vehicle software version update device can be configured in an electronic device with data processing capabilities. Figure 1 As shown, the method includes:

[0029] S110: If it is determined that the data monitoring result of the in-vehicle controller is abnormal, it is determined whether the current software version of the abnormal in-vehicle controller is the latest software version.

[0030] Existing vehicle system updates are also called vehicle OTA (Over-the-Air Technology). When the vehicle system is updated, it is actually the multiple in-vehicle controllers of the vehicle that are undergoing software updates. In some cases, there are problems with the updates of some in-vehicle controllers, that is, the updates fail. In this case, one possible situation is that the vehicle can still be used normally, another possible situation is that the vehicle issues an abnormal alarm, and another possible situation is that the vehicle issues an abnormal alarm during subsequent use. The technical solution of the embodiment of the present application can update the software version of the relevant controller when an abnormal alarm occurs in the vehicle.

[0031] Among them, the data monitoring result refers to the result obtained by the vehicle's data monitoring module when performing data monitoring. The data monitoring module can monitor the in-vehicle controller, including but not limited to monitoring memory usage, CPU usage, DTC faults, current and voltage and other information. If the data monitoring result triggers the manufacturer's customized rules, it means that the data monitoring result is abnormal. In a specific example, if the CPU usage is greater than the threshold, the voltage is greater than the voltage threshold, or the current is greater than the current threshold, it means that the data monitoring result is abnormal.

[0032] Specifically, if it is determined that there is an abnormality in the data monitoring result of the in-vehicle controller (i.e., information about the abnormal in-vehicle controller sent by the data monitoring module is received), the current software version of the abnormal in-vehicle controller is read through the CAN bus, and the current software version of the abnormal in-vehicle controller is compared with the latest software version recorded in the cloud. If the two versions are the same, it means that the current software version of the abnormal in-vehicle controller is the latest software version; otherwise, the current software version of the abnormal in-vehicle controller is not the latest software version.

[0033] S120, if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version, then obtain the latest software version of the target in-vehicle controller; the target in-vehicle controller includes the abnormal in-vehicle controller.

[0034] Among them, the target in-vehicle controller is an in-vehicle controller associated with the abnormal in-vehicle controller and whose software version is not the latest software version. The in-vehicle controller associated with the abnormal in-vehicle controller can be determined in advance, from which the target in-vehicle controller whose software version is not the latest software version can be identified.

[0035] It should be noted that when an abnormal in-vehicle controller malfunctions, it may be caused by outdated versions of multiple in-vehicle controllers. Therefore, when a problem occurs in the abnormal in-vehicle controller, it is necessary to update the software version of at least one in-vehicle controller.

[0036] In a specific example, the target in-vehicle controller includes the abnormal in-vehicle controller and the in-vehicle controller other than the abnormal in-vehicle controller.

[0037] Specifically, after determining the target in-vehicle controller, the target in-vehicle controller is reported to the OTA download module, and the latest software version of the target in-vehicle controller is obtained through the OTA download module. It should be noted that the latest software version of the target in-vehicle controller is inconsistent with the software package during the OTA upgrade under normal circumstances. This is because the software package during the OTA upgrade includes multiple in-vehicle controllers (the in-vehicle controllers may or may not be associated with each other), and the latest software version of the target in-vehicle controller only corresponds to the target in-vehicle controller. Usually, the data volume of the latest software version of the target in-vehicle controller is smaller than the data volume of the software package during the OTA upgrade.

[0038] S130: updating the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller.

[0039] For example, while obtaining the latest software version of the target in-vehicle controller, the user can be prompted with an upgrade message through the in-vehicle instrument (mobile phone APP). After the user agrees to the upgrade, the OTA download module routes the upgrade package pre-downloaded in the cloud to the in-vehicle controller for centralized upgrade. After the upgrade is completed, the OTA download module feeds back a progress message, and then determines whether the current software version of the abnormal in-vehicle controller is the latest software version. If the upgrade fails, a secondary upgrade is performed until all core controllers are upgraded to the latest version. After the upgrade is completed, the user is notified to restart the vehicle.

[0040] The technical solution of the embodiment of the present application includes: if it is determined that the data monitoring result of the in-vehicle controller is abnormal, then determine whether the current software version of the abnormal in-vehicle controller is the latest software version; if the version determination result is that the current software version of the abnormal in-vehicle controller is not the latest software version, then obtain the latest software version of the target in-vehicle controller; the target in-vehicle controller includes the abnormal in-vehicle controller; based on the latest software version of the target in-vehicle controller, the software version of the target in-vehicle controller is updated. This technical solution updates the software version of the target in-vehicle controller when the data monitoring result is abnormal, thereby avoiding the previous situation of updating the entire vehicle system, saving network traffic, and improving the update rate.

[0041] Embodiment 2

[0042] Figure 2 A flowchart of a vehicle software version update method provided in Embodiment 2 of the present application, which is optimized based on the above-mentioned embodiment.

[0043] like Figure 2 As shown, the method of the embodiment of the present application specifically includes the following steps:

[0044] S210: If it is determined that the data monitoring result of the in-vehicle controller is abnormal, it is determined whether the current software version of the abnormal in-vehicle controller is the latest software version.

[0045] S220: If the version determination result is that the current software version of the abnormal in-vehicle controller is not the latest software version, obtain information of a preset set of in-vehicle controllers that have an impact on the abnormal in-vehicle controller.

[0046] It should be noted that there may be multiple in-vehicle controller sets. Since an in-vehicle controller may correspond to multiple abnormal situations, each abnormal situation corresponds to multiple in-vehicle controllers, and multiple in-vehicle controllers are determined as one in-vehicle controller set. In a specific example, the key nodes on the link where various abnormal situations of abnormal in-vehicle controllers are located can be determined, and the in-vehicle controllers on the key nodes corresponding to one abnormal situation can be determined as one in-vehicle controller set. In another specific example, different in-vehicle controller sets corresponding to in-vehicle controllers can be pre-calibrated.

[0047] Specifically, if it is determined that the current software version of the abnormal in-vehicle controller is not the latest software version, then in the correspondence between the in-vehicle controller and the in-vehicle controller set, information of each in-vehicle controller set corresponding to the abnormal in-vehicle controller is determined.

[0048] S230, determining a target in-vehicle controller set in each in-vehicle controller set that can resolve the current abnormality of the abnormal in-vehicle controller; or, determining a target in-vehicle controller set in each in-vehicle controller set according to the number of in-vehicle controllers in each in-vehicle controller set.

[0049] The current abnormality is determined based on the data monitoring result of the abnormal in-vehicle controller; the current abnormality is the abnormal information of the abnormal in-vehicle controller reflected by the data monitoring result.

[0050] Specifically, the historical data of each vehicle can be read from the cloud, wherein the historical data includes the in-vehicle controller set information that solves the current abnormality of the abnormal in-vehicle controller, and the target in-vehicle controller set is determined according to the set information. Alternatively, the target in-vehicle controller set is determined in each in-vehicle controller set according to the number of in-vehicle controllers in each in-vehicle controller set.

[0051] In an embodiment of the present application, optionally, a target in-vehicle controller set that can resolve the current abnormality of the abnormal in-vehicle controller is determined among each in-vehicle controller set, including: if it is determined that the current abnormality is a historical abnormality that has already occurred, determining that the current abnormality can be resolved by performing a software upgrade on the in-vehicle controller set, and determining the in-vehicle controller set in this case as the target in-vehicle controller set.

[0052] Specifically, it can be determined from historical data in the cloud that other vehicles have resolved the current abnormal situation by performing software upgrades on the in-vehicle controller set, and the in-vehicle controller set in this situation is determined as the target in-vehicle controller set.

[0053] In an embodiment of the present application, optionally, it is determined that a situation in which a software upgrade is required to resolve the current abnormality by means of a set of in-vehicle controllers, and the set of in-vehicle controllers in this situation is determined as a target set of in-vehicle controllers, including: if it is determined that the number of sets of in-vehicle controllers in which a software upgrade is required to resolve the current abnormality is greater than one, then the set of in-vehicle controllers with the highest success rate in resolving the current abnormality through software upgrade is determined as the target set of in-vehicle controllers.

[0054] It should be noted that, in one possible scenario, the current exception was resolved by updating the in-vehicle controller set A in the past, and the current exception was also resolved when the in-vehicle controller set B was updated. That is, the number of in-vehicle controller sets that resolve the current exception through software upgrades of the in-vehicle controller sets is greater than one. The success rate of resolving the current exception after updating the software version of each in-vehicle controller set can be calculated, and the in-vehicle controller set with the highest success rate can be determined as the target in-vehicle controller set.

[0055] The scheme is configured in this way, so that a target in-vehicle controller set with a high success rate can be quickly determined.

[0056] Exemplarily, in a specific example, a target in-vehicle controller set that can solve the current abnormality of the abnormal in-vehicle controller is determined among each in-vehicle controller set, including: confirming the key node on the link where the current abnormality of the abnormal in-vehicle controller is located by calling a built-in algorithm model, and determining the in-vehicle controller set located at the key node as the target in-vehicle controller set.

[0057] In an embodiment of the present application, optionally, a target in-vehicle controller set is determined in each in-vehicle controller set based on the number of in-vehicle controllers in each in-vehicle controller set, including: before the vehicle system performs the next software version update, counting the number of times the same data monitoring result for the same abnormal in-vehicle controller has been received; sorting the number of in-vehicle controllers from small to large, and determining the in-vehicle controller set whose sorting number is equal to the statistical number as the target in-vehicle controller set.

[0058] Exemplarily, in a feasible solution, if there is no situation in the historical data where the current abnormality of the abnormal in-vehicle controller can be resolved by updating the software version, then before the vehicle system performs the next software version update, the number of times the same data monitoring result has been received for the same abnormal in-vehicle controller is counted; the number of in-vehicle controllers is sorted from small to large, and the set of in-vehicle controllers whose sorting number is equal to the statistical number is determined as the target in-vehicle controller set.

[0059] The scheme is configured in this way, so that the current anomaly can be resolved by trying to update each in-vehicle controller set one by one according to the number of in-vehicle controllers in each in-vehicle controller set from small to large. Since the number of in-vehicle controllers in the in-vehicle controller set tried each time is as small as possible, the update time is shortened and the user experience is improved.

[0060] S240: Determine an in-vehicle controller whose software version is not the latest software version in the target in-vehicle controller set as the target in-vehicle controller.

[0061] Specifically, in the target in-vehicle controller set, some in-vehicle controllers may have the latest version. Regardless of whether the in-vehicle controller is not the latest version, the in-vehicle controller whose software version is not the latest software version is determined as the target in-vehicle controller, and the target in-vehicle controller is subsequently updated. Compared with updating the entire target in-vehicle controller set, this scheme is set up in this way, which reduces the data volume of the software package for the software version update as much as possible and shortens the update time.

[0062] S250, obtaining the latest software version of a target in-vehicle controller; the target in-vehicle controller includes an abnormal in-vehicle controller.

[0063] Exemplarily, the latest software version can be pre-downloaded, for example, the cloud periodically pre-downloads the latest version of the in-vehicle controller, and pre-sets the latest version numbers of each controller. The latest software version of the target in-vehicle controller can be directly determined from the pre-downloaded latest software version.

[0064] In an embodiment of the present application, optionally, obtaining the latest software version of the target in-vehicle controller includes: sending information of the target in-vehicle controller to an over-the-air download module; and determining the latest software version of the target in-vehicle controller in a pre-downloaded vehicle software update package through the over-the-air download module.

[0065] Exemplarily, the name of the target in-vehicle controller is fed back to an over-the-air download module (the over-the-air download module is an OTA download module), and the OTA download module obtains the latest software version of the target in-vehicle controller and performs subsequent updates.

[0066] S260: updating the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller.

[0067] In an embodiment of the present application, optionally, the software version of the target in-vehicle controller is updated based on the latest software version of the target in-vehicle controller, including: if a message agreeing to perform the software update is received, the latest software version is sent to the target in-vehicle controller through the air download module for software update; if an update completion message is received from the air download module, it is determined whether the current software version of the target in-vehicle controller is the latest software version; if not, the latest software version is sent to the target in-vehicle controller through the air download module for software update again.

[0068] Exemplarily, the OTA download module pulls the latest software version preset in the cloud to the local computer and distributes it to the target in-vehicle controller through the gateway. The in-vehicle controller will feedback the completion status after executing the update. When all target in-vehicle controllers are upgraded, the OTA download module triggers the next operation, that is, to determine whether the current software version of the abnormal in-vehicle controller is the latest software version. If not, it will retry until the upgrade is completed.

[0069] During this process, the data monitoring module focuses on monitoring whether the current anomaly has recurred (for example, for a continuous period of 12 weeks). If the anomaly does not occur, it means that the problem has been solved, and the relevant information for solving the current anomaly (such as the target in-vehicle controller cluster information) is synchronized to the cloud as historical data, so that the target in-vehicle controller set can be quickly and accurately determined later.

[0070] The technical solution of the embodiment of the present application can more accurately resolve the current anomaly of the abnormal in-vehicle controller by determining the in-vehicle controller set with the highest success rate in resolving the current anomaly as the target in-vehicle controller set. When updating the software version, the target in-vehicle controller is updated, and the source of the problem is dealt with. In this process, since the number of target in-vehicle controllers is usually smaller than the number of in-vehicle controllers when the vehicle system is upgraded as a whole, network traffic consumption is reduced, update time is reduced, and the latest software version is obtained by pulling the preset version, so that the time to obtain the latest software version is very short, thereby improving the user experience.

[0071] Embodiment 3

[0072] Figure 3 This is a schematic diagram of the structure of a vehicle software version update device provided in the third embodiment of the present application. The device can execute the vehicle software version update method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method. Figure 3 As shown, the device comprises:

[0073] The software version determination module 310 is used to determine whether the current software version of the abnormal in-vehicle controller is the latest software version if it is determined that the data monitoring result of the in-vehicle controller is abnormal;

[0074] The latest software version acquisition module 320 is used to acquire the latest software version of the target in-vehicle controller if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version; the target in-vehicle controller includes the abnormal in-vehicle controller;

[0075] The version updating module 330 is used to update the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller.

[0076] The technical solution of the embodiment of the present application includes: a software version judgment module 310, which is used to judge whether the current software version of the abnormal in-vehicle controller is the latest software version if it is determined that the data monitoring result of the in-vehicle controller is abnormal; a latest software version acquisition module 320, which is used to obtain the latest software version of the target in-vehicle controller if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version; the target in-vehicle controller includes the abnormal in-vehicle controller; a version update module 330, which is used to update the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller. This technical solution updates the software version of the target in-vehicle controller when the data monitoring result is abnormal, thereby avoiding the previous situation of updating the entire vehicle system, saving network traffic, and improving the update rate.

[0077] In the embodiment of the present application, optionally, the device further includes: a target in-vehicle controller determination module, the module including:

[0078] A set information acquisition unit, used to acquire information of a preset set of in-vehicle controllers that have an impact on the abnormal in-vehicle controller;

[0079] a target in-vehicle controller set determining unit, configured to determine a target in-vehicle controller set in each in-vehicle controller set that can resolve the current abnormality of the abnormal in-vehicle controller; or, determining a target in-vehicle controller set in each in-vehicle controller set according to the number of in-vehicle controllers in each in-vehicle controller set; the current abnormality is determined according to a data monitoring result of the abnormal in-vehicle controller;

[0080] The target in-vehicle controller determining unit is used to determine an in-vehicle controller whose software version is not the latest software version in the target in-vehicle controller set as the target in-vehicle controller.

[0081] In the embodiment of the present application, optionally, the target in-vehicle controller set determination unit includes:

[0082] The target in-vehicle controller set determination subunit is used to determine whether to resolve the current abnormality by performing a software upgrade on the in-vehicle controller set if it is determined that the current abnormality is a historical abnormality that has already occurred, and determine the in-vehicle controller set in this case as the target in-vehicle controller set.

[0083] In the embodiment of the present application, optionally, the target in-vehicle controller set determines a subunit, which is specifically used to include:

[0084] If it is determined that the number of in-vehicle controller sets that can resolve the current anomaly by performing software upgrade on the in-vehicle controller sets is greater than one, the in-vehicle controller set with the highest success rate of resolving the current anomaly by software upgrade is determined as the target in-vehicle controller set.

[0085] In the embodiment of the present application, optionally, the target in-vehicle controller set determination unit includes:

[0086] A statistical number determination subunit, used for counting the number of times the same data monitoring result for the same abnormal in-vehicle controller has been received before the vehicle system performs the next software version update;

[0087] The target in-vehicle controller set determination subunit is used to sort the number of in-vehicle controllers from small to large, and determine the in-vehicle controller set whose sorting sequence number is equal to the statistical number as the target in-vehicle controller set.

[0088] In the embodiment of the present application, optionally, the latest software version acquisition module 320 includes:

[0089] The information sending unit of the target in-vehicle controller is used to send the information of the target in-vehicle controller to the over-the-air download module;

[0090] The latest software version determination subunit is used to determine the latest software version of the target in-vehicle controller in the pre-downloaded vehicle software update package through the over-the-air download module.

[0091] In the embodiment of the present application, optionally, the version update module 330 includes:

[0092] A software update unit, for sending the latest software version to the target in-vehicle controller through an over-the-air download module for software update if a message agreeing to perform software update is received;

[0093] A version determination unit, configured to determine whether the current software version of the target in-vehicle controller is the latest software version upon receiving an update completion message fed back by the over-the-air download module;

[0094] The secondary software updating unit is used to send the latest software version to the target in-vehicle controller through the air download module to perform software updating again if not.

[0095] A vehicle software version update device provided in an embodiment of the present application can execute a vehicle software version update method provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0096] Embodiment 4

[0097] Figure 4 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention 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 can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0098] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0099] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0100] The processor 11 may be a variety of general and / or dedicated processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a vehicle software version update method.

[0101] In some embodiments, the vehicle software version update method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the vehicle software version update method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the vehicle software version update method in any other appropriate manner (e.g., by means of firmware).

[0102] Various implementations 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 chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0103] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0104] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

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

[0106] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0107] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0108] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0109] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for updating the software version of a vehicle, characterized in that: include: If it is determined that the data monitoring result of the in-vehicle controller is abnormal, determining whether the current software version of the abnormal in-vehicle controller is the latest software version; If the version determination result is that the current software version of the abnormal in-vehicle controller is not the latest software version, then obtaining the latest software version of the target in-vehicle controller; The target in-vehicle controllers include abnormal in-vehicle controllers; The software version of the target in-vehicle controller is updated based on the latest software version of the target in-vehicle controller.

2. The method according to claim 1, characterized in that The process of determining the target in-vehicle controller includes: Acquire information of a preset set of in-vehicle controllers that have an impact on the abnormal in-vehicle controller; Determine a target in-vehicle controller set in each in-vehicle controller set that can solve the current abnormality of the abnormal in-vehicle controller; or determine a target in-vehicle controller set in each in-vehicle controller set according to the number of in-vehicle controllers in each in-vehicle controller set; the current abnormality is determined according to the data monitoring result of the abnormal in-vehicle controller; An in-vehicle controller whose software version is not the latest software version in the target in-vehicle controller set is determined as the target in-vehicle controller.

3. The method according to claim 2, characterized in that Determining a target in-vehicle controller set that can resolve the current abnormality of the abnormal in-vehicle controller from among the in-vehicle controller sets includes: If it is determined that the current abnormality is a historical abnormality that has occurred, it is determined that the current abnormality can be resolved by performing a software upgrade on the in-vehicle controller set, and the in-vehicle controller set in this case is determined as the target in-vehicle controller set.

4. The method according to claim 3, characterized in that Determining that a current abnormal situation can be solved by performing a software upgrade on the in-vehicle controller set, and determining the in-vehicle controller set in this situation as a target in-vehicle controller set, including: If it is determined that the number of in-vehicle controller sets that can resolve the current anomaly by performing software upgrade on the in-vehicle controller sets is greater than one, the in-vehicle controller set with the highest success rate of resolving the current anomaly by software upgrade is determined as the target in-vehicle controller set.

5. The method according to claim 2, characterized in that: Determining a target in-vehicle controller set in each in-vehicle controller set according to the number of in-vehicle controllers in each in-vehicle controller set includes: Before the vehicle system performs the next software version update, count the number of times the same data monitoring result for the same abnormal in-vehicle controller has been received; The number of in-vehicle controllers is sorted from small to large, and a set of in-vehicle controllers whose sorting sequence number is equal to the statistical number is determined as a target in-vehicle controller set.

6. The method according to claim 1, characterized in that Get the latest software version of the target in-vehicle controller, including: Send the information of the target in-vehicle controller to the over-the-air download module; The latest software version of the target in-vehicle controller is determined in the pre-downloaded vehicle software update package through the over-the-air download module.

7. The method according to claim 6, characterized in that Updating the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller includes: If a message agreeing to perform software update is received, the latest software version is sent to the target in-vehicle controller via the over-the-air download module for software update; If an update completion message fed back by the over-the-air download module is received, it is determined whether the current software version of the target in-vehicle controller is the latest software version; If not, the latest software version is sent to the target in-vehicle controller through the over-the-air download module to perform software update again.

8. A vehicle software version updating device, characterized in that: include: A software version judgment module is used to judge whether the current software version of the abnormal in-vehicle controller is the latest software version if it is determined that the data monitoring result of the in-vehicle controller is abnormal; The latest software version acquisition module is used to acquire the latest software version of the target in-vehicle controller if the version judgment result is that the current software version of the abnormal in-vehicle controller is not the latest software version; The target in-vehicle controllers include abnormal in-vehicle controllers; The version update module is used to update the software version of the target in-vehicle controller based on the latest software version of the target in-vehicle controller.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle software version updating method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the vehicle software version update method according to any one of claims 1 to 7 when executed.

Images