Vehicle-mounted software upgrading method and device, equipment and medium

Abstract

The invention discloses a vehicle-mounted software upgrading method and device, equipment and a medium. The method comprises the following steps: receiving an upgrading task of a target vehicle type issued by a cloud; respectively updating script files in the communication master node and the communication slave node based on the script file information to obtain a first script file and a second script file; obtaining vehicle identification information from a vehicle-mounted client corresponding to the target vehicle model through a script engine based on the first script file, and reporting the vehicle identification information to the cloud; downloading a corresponding software upgrade package according to the first script file and the software package downloading information; and issuing the software upgrading package, the first script file and the second script file to the vehicle-mounted client so as to control the vehicle-mounted software upgrading operation of the vehicle-mounted client based on the first script file and the second script file. According to the technical scheme, the OTA software logic is optimized or the OTA software fault is repaired through the script file, the risk of OTA function failure caused by the software fault is avoided, and the optimization and repair timeliness is improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent vehicle technology, and in particular to a vehicle-mounted software upgrading method, device, equipment and medium. Background Art

[0002] Automotive OTA (Over-The-Air) software updates, or over-the-air (OTA), have become a key driver of progress in the automotive industry. Similar to smartphone system updates, OTA leverages wireless networks to deliver continuous improvements and upgrades to a vehicle's electronic control units (ECUs).

[0003] In the existing technology, OTA software is integrated into the overall vehicle software version. If there is a problem with the OTA software itself, the vehicle cannot be upgraded OTA and can only be upgraded offline at a 4S store. In addition, in order to be compatible with different car models, the complexity of OTA software is also increasing, posing a major challenge to the software development progress and quality. Summary of the Invention

[0004] The present invention provides a vehicle-mounted software upgrade method, device, equipment and medium, which optimizes OTA software logic or repairs OTA software faults through script files sent from the cloud, so that the upgrade logic on the vehicle side can be dynamically controlled by the server side, avoiding the risk of OTA function failure due to software faults and improving the timeliness of optimization and repair.

[0005] According to one aspect of the present invention, a method for upgrading in-vehicle software is provided. The method is applied to a communication transmission base station in an in-vehicle software upgrade system, wherein the communication transmission base station includes a communication master node and multiple communication slave nodes; the communication master node and the multiple communication slave nodes are both configured with a script engine. The method includes:

[0006] Receive an upgrade task for a target vehicle model issued by the cloud; wherein the upgrade task includes script file information;

[0007] Based on the script file information, the script files in the communication master node and the communication slave node are updated respectively to obtain a first script file and a second script file;

[0008] Obtaining vehicle identification information from the vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and reporting the vehicle identification information to the cloud;

[0009] Receiving software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and downloading the corresponding software upgrade package according to the first script file and the software package download information;

[0010] The software upgrade package, the first script file, and the second script file are sent to the vehicle-mounted client to control the vehicle-mounted software upgrade operation of the vehicle-mounted client based on the first script file and the second script file.

[0011] According to another aspect of the present invention, a vehicle-mounted software upgrade method is provided. The vehicle-mounted software upgrade method is applied to a vehicle-mounted client in a vehicle-mounted software upgrade system. The vehicle-mounted software upgrade method includes:

[0012] Receiving a software upgrade package, a first script file, and a second script file sent by a communication transmission base station;

[0013] The vehicle-mounted software is upgraded based on the software upgrade package, the first script file, and the second script file to obtain an upgrade result, and the upgrade result is fed back to the communication transmission base station.

[0014] According to another aspect of the present invention, a method for upgrading vehicle software is provided. The method is applied to a cloud in a vehicle software upgrade system. The method comprises:

[0015] When it is detected that the target vehicle model meets the upgrade conditions, an upgrade task corresponding to the target vehicle model is generated and sent to the communication transmission base station;

[0016] Receive the vehicle identification information sent by the communication transmission base station, and issue corresponding software upgrade package download information according to the vehicle identification information.

[0017] According to another aspect of the present invention, a vehicle-mounted software upgrade device is provided. The vehicle-mounted software upgrade device is configured in a communication transmission base station in a vehicle-mounted software upgrade system. The communication transmission base station includes a communication master node and multiple communication slave nodes. The communication master node and the multiple communication slave nodes are each configured with a script engine. The vehicle-mounted software upgrade device includes:

[0018] A task receiving module is used to receive the upgrade task of the target vehicle model issued by the cloud; wherein the upgrade task includes script file information;

[0019] A script updating module, configured to update the script files in the communication master node and the communication slave node respectively based on the script file information to obtain a first script file and a second script file;

[0020] An information reporting module, configured to obtain vehicle identification information from an in-vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and report the vehicle identification information to the cloud;

[0021] An upgrade package download module, configured to receive software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package according to the first script file and the software package download information;

[0022] The upgrade control module is used to send the software upgrade package, the first script file and the second script file to the vehicle client to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file.

[0023] According to another aspect of the present invention, a vehicle-mounted software upgrade device is provided. The vehicle-mounted software upgrade method is configured in a vehicle-mounted client in a vehicle-mounted software upgrade system. The vehicle-mounted software upgrade device includes:

[0024] A file receiving module, configured to receive a software upgrade package, a first script file, and a second script file sent by a communication transmission base station;

[0025] A software upgrade module is used to upgrade the vehicle-mounted software based on the software upgrade package, the first script file and the second script file to obtain an upgrade result, and to feed back the upgrade result to the communication transmission base station.

[0026] According to another aspect of the present invention, a vehicle-mounted software upgrade device is provided. The vehicle-mounted software upgrade method is configured in the cloud of a vehicle-mounted software upgrade system. The vehicle-mounted software upgrade device includes:

[0027] The upgrade task sending module is used to generate an upgrade task corresponding to the target vehicle model and send it to the communication transmission base station when detecting that the target vehicle model meets the upgrade conditions;

[0028] The download information sending module is used to receive the vehicle identification information sent by the communication transmission base station and send the corresponding software upgrade package download information according to the vehicle identification information.

[0029] According to another aspect of the present invention, there is provided a communication transmission device, the communication transmission device comprising:

[0030] a communication master node and at least one communication slave node; and

[0031] a memory in communication connection with the one communication master node and the at least one communication slave node; wherein,

[0032] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the one communication master node and the at least one communication slave node, so that the one communication master node and the at least one communication slave node can execute the vehicle-mounted software upgrade method described in any one of Embodiment 1 or Embodiment 2 of the present invention.

[0033] According to another aspect of the present invention, a vehicle is provided, wherein the vehicle is used to execute the vehicle software upgrade method as described in the third embodiment of the present invention.

[0034] 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 upgrade method described in any embodiment of the present invention when executed.

[0035] The technical solution of the embodiment of the present invention is to receive an upgrade task of a target vehicle model sent from the cloud; wherein the upgrade task includes script file information; based on the script file information, the script files in the communication master node and the communication slave node are updated respectively to obtain a first script file and a second script file; based on the first script file, the vehicle identification information is obtained from the vehicle client corresponding to the target vehicle model through a script engine, and the vehicle identification information is reported to the cloud; the software upgrade package download information corresponding to the vehicle identification information is received from the cloud, and the corresponding software upgrade package is downloaded according to the first script file and the software package download information; the software upgrade package, the first script file and the second script file are sent to the vehicle client to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file. This technical solution optimizes the OTA software logic or repairs the OTA software fault through the script file sent from the cloud, so that the upgrade logic of the vehicle side can be dynamically controlled by the server side, avoiding the risk of OTA function failure due to software fault, and improving the timeliness of optimization and repair.

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

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. 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.

[0038] Figure 1 This is a flow chart of a vehicle software upgrade method provided according to the first embodiment of the present invention;

[0039] Figure 2 This is a flow chart of a vehicle software upgrade method provided according to the second embodiment of the present invention;

[0040] Figure 3 This is a flow chart of a vehicle software upgrade method provided according to a third embodiment of the present invention;

[0041] Figure 4 This is a flow chart of a vehicle software upgrade method provided according to a fourth embodiment of the present invention;

[0042] Figure 5 This is an example diagram of the overall architecture of a vehicle software upgrade method provided according to a fourth embodiment of the present invention;

[0043] Figure 6 This is a structural diagram of a vehicle-mounted software upgrade device provided according to a fifth embodiment of the present invention;

[0044] Figure 7 This is a structural diagram of a vehicle-mounted software upgrade device provided according to a sixth embodiment of the present invention;

[0045] Figure 8 This is a structural diagram of a vehicle-mounted software upgrade device provided according to a seventh embodiment of the present invention;

[0046] Figure 9 It is a structural diagram of a communication transmission device provided according to embodiment eight of the present invention. DETAILED DESCRIPTION

[0047] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions 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 embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0048] It should be noted that the terms "first", "second", etc. in the description 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 numbers 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.

[0049] Example 1

[0050] Figure 1 This is a flow chart of a vehicle software upgrade method provided according to the first embodiment of the present invention. This embodiment is applicable to the case where a communication transmission base station updates or repairs the vehicle software. The method can be executed by a vehicle software upgrade device. The vehicle software upgrade device can be implemented in the form of hardware and / or software. The vehicle software upgrade device can be configured in a communication transmission device with data processing capabilities. Figure 1 As shown, the method includes:

[0051] The vehicle software upgrade method of this embodiment is applied to a communication transmission base station in a vehicle software upgrade system. The communication transmission base station includes a communication master node and multiple communication slave nodes; both the communication master node and the multiple communication slave nodes are configured with a script engine. The vehicle software upgrade system of the present invention may include a communication transmission base station, a vehicle client, and a cloud. Throughout the vehicle software upgrade system, the communication transmission base station facilitates data exchange between the vehicle client and the cloud, allowing the cloud to upgrade the vehicle client's vehicle software.

[0052] Among them, the communication transmission base station can be an automobile over-the-air technology (OTA) base station. The communication master node can refer to the OTA Master node. The communication slave node can refer to each OTA Slave. The communication master node in this embodiment can be used to control the entire network communication of the vehicle and manage the communication of each slave node. In the automobile network, the communication master node is usually responsible for communication with the external network (such as the CAN bus), responsible for managing the communication and data exchange of the entire network, and ensuring that each slave node can work normally. The communication slave node can be responsible for the communication of different control units ECU in the corresponding vehicle. The communication transmission base station in this embodiment may include a communication master node and multiple communication slave nodes, wherein the number of multiple communication slave nodes is related to the control unit ECU to be upgraded on the vehicle. The script engine can provide an environment for the operation of the script file, so that the entire OTA process can be implemented according to the logic described in the script file. The script file in this embodiment is an interpretive language file.

[0053] S110: Receive the upgrade task of the target vehicle model sent from the cloud.

[0054] Among them, the upgrade task includes script file information. The script file information may refer to the version information and download address of the script file required for this upgrade task. The upgrade task may include information such as the specific content or scope that needs to be upgraded for the target vehicle model. The cloud may refer to the OTA management platform. In this embodiment, the OTA management platform provides OTA services for the vehicle terminal, mainly managing the original firmware upgrade software of each software provider. The target vehicle model can be understood as the specific vehicle model or vehicle model configuration that needs to receive and execute the upgrade task when the automobile manufacturer issues the upgrade task through the cloud. In this embodiment, the software differences between vehicle models can be solved by issuing different script files according to different vehicle models through the cloud. There is no need to do platform adaptation from the vehicle-side software level, which reduces the complexity of the vehicle-side software and thus improves the stability of the software.

[0055] In this embodiment, the OTA management platform sends an upgrade task for a specified vehicle model to the OTA client in the master node OTA Master of the communication transmission base station. The upgrade task includes at least information such as the version information and download address of the script file required for this upgrade task.

[0056] S120 . Update the script files in the communication master node and the communication slave node respectively based on the script file information to obtain a first script file and a second script file.

[0057] Among them, the first script file can be understood as the updated script file in the communication master node. The second script file can be understood as the updated script file in the communication slave node. In this embodiment, there can be multiple second script files, corresponding to each communication slave node. In this embodiment, the communication master node and the communication slave node may include preset script files. The vehicle in this embodiment will be pre-installed with script files in the communication master node OTA Master and the communication slave node OTA Slave when leaving the factory. The OTA client on the vehicle side determines whether the script files in the OTAMaster and / or OTA Slave on the current vehicle side need to be updated based on the required script file version information in the upgrade task. If the script files in the OTA Master and / or OTA Slave need to be updated, the script files that need to be updated by the communication master node OTA Master and / or the communication slave node OTA Slave are downloaded based on the corresponding download address in the script file information, and the downloaded script files are decrypted and signed. The script files that have passed decryption and signature verification are then distributed to the corresponding communication master node OTA Master and each communication slave node OTA Slave, and the script files in each OTA node (OTA Master and each OTA Slave) are updated to obtain the corresponding first script file and second script file after the update. If the script files in the OTA Master and / or OTASlave on the current vehicle side do not need to be updated, the preset script files in the communication master node OTA Master and the communication slave node OTA Slave when the vehicle leaves the factory can be used as the first script file and the second script file. Specifically, in the current vehicle of this embodiment, there may be a situation where the preset script file in the communication master node needs to be updated, while the preset script file in the communication slave node does not need to be updated. In this case, it is only necessary to update the preset script file in the communication master node to obtain the first script file, and then use the preset script file in the communication slave node as the second script file; there may also be a situation where the preset script file in the communication master node does not need to be updated, while the preset script file in the communication slave node needs to be updated. In this case, the preset overtime file in the communication slave node can be updated to obtain the second script file, and the preset script file in the communication master node can be used as the first script file; there may also be a situation where both the preset script file in the communication master node and the preset script file in the communication slave node need to be updated. In this case, the preset script file in the communication master node and the preset script file in the communication slave node are updated respectively to obtain the corresponding first script file and second script file.

[0058] S130: Obtain vehicle identification information from the vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and report the vehicle identification information to the cloud.

[0059] The vehicle identification information can be understood as relevant data information that uniquely identifies and describes the vehicle. In this embodiment, the vehicle identification information can include identification information such as the vehicle identification, the vehicle ECU identification, and the vehicle ECU software version information.

[0060] In this embodiment, after obtaining the first script file and the second script file, the OTA client can trigger the script engine in OTAMaster to load and execute the first script file in OTA Master. Then, the first script file in OTA Master will call the interface of the platform adaptation layer through the script engine to obtain vehicle identification related information (such as vehicle identification, vehicle ECU identification, and vehicle ECU software version information, etc.), and report the vehicle identification to the OTA management platform, so that the OTA management platform can issue the corresponding upgrade package download information according to the vehicle identification related information.

[0061] S140: Receive software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package according to the first script file and the software package download information.

[0062] The software upgrade package can be understood as the specific file package required to upgrade the vehicle software. In this embodiment, the communication transmission base station can receive the software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package from the content distribution network according to the download policy in the first script file in the OTA Master and the issued upgrade package download information. The upgrade policy can refer to the specific download object and download method of the upgrade package. The upgrade policy can be determined by the logic in the first script file, and different download policies can be set according to actual needs.

[0063] S150: Send the software upgrade package, the first script file, and the second script file to the vehicle client, so as to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file.

[0064] In this embodiment, the communication transportation base station can send the software upgrade package, the first script file and the second script file to the vehicle client, and control the vehicle client's vehicle software to perform upgrade operations according to the upgrade logic in the first script file and the second script file.

[0065] The technical solution of the embodiment of the present invention is to receive an upgrade task for a target vehicle model sent from the cloud; wherein the upgrade task includes script file information; based on the script file information, the script files in the communication master node and the communication slave node are updated respectively to obtain a first script file and a second script file; based on the first script file, the vehicle identification information is obtained from the vehicle client corresponding to the target vehicle model through the script engine, and the vehicle identification information is reported to the cloud; the software upgrade package download information corresponding to the vehicle identification information is received from the cloud, and the corresponding software upgrade package is downloaded according to the first script file and the software package download information; the software upgrade package, the first script file and the second script file are sent to the vehicle client to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file. This technical solution optimizes the OTA software logic or repairs the OTA software fault through the script file sent from the cloud, so that the upgrade logic of the vehicle side can be dynamically controlled by the server side, avoiding the risk of OTA function failure due to software fault, and improving the timeliness of optimization and repair.

[0066] Example 2

[0067] Figure 2 This is a flowchart of a vehicle software upgrade method provided according to the second embodiment of the present invention, and this embodiment is optimized based on the above embodiment. The specific optimization is: the script file information includes the first version information, the second version information and the corresponding script file download address of the script file; based on the script file information, the script files of the communication master node and the communication slave node are updated respectively to obtain the first script file and the second script file, including: judging whether the first preset script file in the communication master node needs to be updated based on the first version information, and judging whether the second preset script file in the communication slave node needs to be updated based on the second version information; if the first preset script file and the second preset script file need to be updated, the first script file to be updated and the second script file to be updated are downloaded respectively according to the script file download address; based on the first script file to be updated and the second script file to be updated, the first preset script file and the second preset script file are updated respectively to obtain the corresponding first script file and the second script file. As Figure 2 As shown, the method includes:

[0068] The vehicle software upgrade method in this embodiment is applied to a communication transmission base station in a vehicle software upgrade system. The communication transmission base station includes a communication master node and multiple communication slave nodes. Both the communication master node and the multiple communication slave nodes are configured with a script engine.

[0069] S210: Receive the upgrade task of the target vehicle model sent from the cloud.

[0070] Among them, the upgrade task includes script file information. In this embodiment, the script file information may include the first version information, the second version information and the corresponding script file download address of the script file. Among them, the first version information may refer to the version information required by the communication master node in this upgrade task. The second version information may refer to the version information required by the communication slave node in this upgrade task. The script file download address can be understood as the address where the corresponding version of the script file can be downloaded. The script task in the upgrade task in this embodiment may include the version information of the script file required for this task upgrade and its corresponding download address.

[0071] S220: Determine whether the first preset script file in the communication master node needs to be updated based on the first version information, and determine whether the second preset script file in the communication slave node needs to be updated based on the second version information.

[0072] The first preset script file can be understood as the original script file that is preset for the OTA Master node when the vehicle leaves the factory. The second preset script file can be understood as the original script file that is preset for the OTA Slave node when the vehicle leaves the factory.

[0073] In this embodiment, whether the first preset script file in the communication master node corresponding to the current vehicle end needs to be updated can be determined based on whether the first version information required for this upgrade task is consistent with the version information in the first preset script file, and whether the script file in the communication slave node needs to be updated can be determined based on whether the second version information required for this upgrade task is consistent with the version information in the second preset script file.

[0074] In this embodiment, optionally, whether the first preset script file in the communication master node needs to be updated is determined based on the first version information, including: obtaining the third version information corresponding to the first preset script file in the communication master node; if the third version information is different from the first version information, the first preset script file in the communication master node needs to be updated; if the third version information is the same as the first version information, the first preset script file in the communication master node does not need to be updated.

[0075] Among them, the third version information can be understood as the version information corresponding to the first preset script file in the communication master node. In this embodiment, the third version information corresponding to the first preset script file in the communication master node can be obtained. If the third version information is different from the first version information required for this upgrade task, it can be considered that the first preset script file in the communication master node needs to be updated; if the first preset script file is the same as the first version information required for this upgrade task, it can be considered that the first preset script file in the communication master node does not need to be updated, and the first preset script file can be used as the first script file.

[0076] It should be noted that the specific method of judging whether the second preset script file in the communication slave node needs to be updated based on the second version information in this embodiment is consistent with the specific judgment method of judging whether the first preset script file in the communication master node needs to be updated based on the first version information, and will not be repeated here.

[0077] Through such a setting in this embodiment, the required script version information in the upgrade task can be compared with the version information of the preset script file in the communication master node and the communication slave node to determine whether the preset script file needs to be updated, thereby improving the reliability of the script file update.

[0078] S230: If the first preset script file and the second preset script file need to be updated, download the first script file to be updated and the second script file to be updated respectively according to the script file download address.

[0079] The first script file to be updated can be understood as a script file downloaded from the script download address in the current upgrade task. In this embodiment, the first script file to be updated can update the first preset script file in the communication master node. The second script file to be updated can be understood as a script file downloaded from the script download address in the current upgrade task. In this embodiment, the second script file to be updated can update the second preset script file in the communication slave node.

[0080] In this embodiment, if the first preset script file and the second preset script file need to be updated, the first script file to be updated required by the communication master node and the second script file to be updated required by the communication slave node can be downloaded respectively according to the corresponding script file download addresses.

[0081] In this embodiment, after downloading the first script file to be updated and the second script file to be updated respectively according to the script file download address, the first script file to be updated and the second script file to be updated can also be decrypted and signed respectively, and the script files that have been successfully decrypted and signed are distributed to the corresponding communication master node and each communication slave node.

[0082] In this embodiment, if the first preset script file and the second preset script file do not need to be updated, the vehicle identification related information can be obtained directly through the script engine calling the interface of the platform adaptation layer according to the first preset script file in the communication main node and reported to the OTA management platform, so that the OTA management platform can issue the corresponding software upgrade package download information according to the vehicle identification related information.

[0083] S240: Update the first preset script file and the second preset script file based on the first script file to be updated and the second script file to be updated respectively to obtain corresponding first script file and second script file.

[0084] In this embodiment, the first preset script file in the communication master node can be updated according to the first script file to be updated to obtain an updated first script file; and the second preset script file in each communication slave node can be updated according to the second script file to be updated to obtain an updated second script file.

[0085] S250: Obtain vehicle identification information from the vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and report the vehicle identification information to the cloud.

[0086] S260: Receive software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package according to the first script file and the software package download information.

[0087] In this embodiment, optionally, downloading the corresponding software upgrade package according to the first script file and the software package download information includes: determining a download strategy for the software upgrade package according to the first script file; and downloading the corresponding software upgrade package according to the download strategy and the software package download information.

[0088] The download strategy can be a specific download method for the software upgrade package controlled by logic in the first script file. In this embodiment, the download strategy can include the communication master node downloading all upgrade packages, or the communication master node downloading a portion of the upgrade packages, while the communication slave nodes download upgrade packages within their own domains. The specific download logic can be pre-set in the first script file based on actual needs. In this embodiment, the specific download strategy for the software upgrade package can be determined based on the first script file in the communication master node, and then the corresponding software upgrade package can be downloaded from the software package download information based on the determined download strategy.

[0089] In this embodiment, according to the specific download strategy, the download action can be unified by the OTA Master end, and then the downloaded software upgrade package can be distributed to other communication slave nodes, or the OTA Master end can send the corresponding software upgrade package, and then send the download information to the OTA Slave node, and the OTA Slave end can download the software upgrade package within its own domain.

[0090] In this embodiment, through such a setting, the specific download strategy is determined by the script file in the communication master node, so that the corresponding software upgrade package is downloaded from the software package download information, which improves the flexibility of the download method and further improves the download efficiency.

[0091] S270: Send the software upgrade package, the first script file, and the second script file to the vehicle-mounted client, so as to control the vehicle-mounted software upgrade operation of the vehicle-mounted client based on the first script file and the second script file.

[0092] The technical solution of the embodiment of the present invention is to send a script file based on an interpreted language to the vehicle side for execution, so that the upgrade logic of the vehicle side can be dynamically controlled by the cloud, avoiding the risk of OTA function failure due to software failure; and optimizing OTA software logic or repairing OTA software failures through the script file sent from the cloud, thereby further improving the robustness, flexibility and timeliness of the OTA software itself.

[0093] Example 3

[0094] Figure 3 This is a flow chart of a vehicle software upgrade method provided according to the third embodiment of the present invention. This embodiment is applicable to the case where a vehicle client upgrades the vehicle software. The method can be executed by a vehicle software upgrade device. The vehicle software upgrade device can be implemented in the form of hardware and / or software. The vehicle software upgrade device can be configured in a vehicle with data processing capabilities. Figure 3 As shown, the method includes:

[0095] S310. Receive a software upgrade package, a first script file, and a second script file sent by a communication transmission base station.

[0096] The vehicle software upgrade method of this embodiment is applied to a vehicle client in a vehicle software upgrade system. In this embodiment, the vehicle client can receive a software upgrade package, a first script file, and a second script file sent by a communication transmission base station.

[0097] S320: Upgrade the vehicle-mounted software based on the software upgrade package, the first script file, and the second script file to obtain an upgrade result, and feed the upgrade result back to the communication transmission base station.

[0098] The upgrade result can be either upgrade completion or script file decryption or signature verification failure. In this embodiment, the corresponding software upgrade strategy can be determined based on the first script file and the second script file, and then the vehicle software is upgraded according to the determined software upgrade strategy and software upgrade package to obtain the corresponding upgrade result. The upgrade result is then fed back to the communication transmission base station, so that the upgrade result can be reported to the OTA management platform through the first script file in the OTA Master.

[0099] In this embodiment, optionally, the vehicle-mounted software is upgraded based on the software upgrade package, the first script file and the second script file to obtain an upgrade result, including: determining the corresponding first software upgrade strategy and second software upgrade strategy according to the first script file and the second script file respectively; wherein the first software upgrade strategy includes the overall upgrade strategy of the vehicle end; the second software upgrade strategy includes the upgrade strategy within each control unit area; the corresponding control units in the vehicle-mounted software are upgraded according to the software upgrade package, the first software upgrade strategy and the second software upgrade strategy respectively to obtain an upgrade result.

[0100] The first software upgrade strategy may specifically include the upgrade sequence and upgrade progress of the entire vehicle end. The second software upgrade strategy may specifically include the upgrade sequence and upgrade method of the control unit where the software slave node is located.

[0101] In this embodiment, the upgrade of the vehicle client is triggered by the first script file in the OTA Master, the corresponding upgrade strategy for controlling the entire vehicle is determined by the first script file in the OTAMaster, and the overall upgrade strategy for the control unit ECU or domain in which it is responsible is determined by the second script file in the OTA Slave. Then, the determined upgrade strategy and software upgrade package respectively upgrade the corresponding control units in the vehicle software, thereby obtaining the corresponding upgrade completion result.

[0102] The technical solution of an embodiment of the present invention is to receive a software upgrade package, a first script file and a second script file sent by a communication transmission base station; upgrade the vehicle-mounted software based on the software upgrade package, the first script file and the second script file to obtain an upgrade result, and feed back the upgrade result to the communication transmission base station. This technical solution sends the script file in an interpreted language to the vehicle client for execution through communication transmission, so that the upgrade logic of the vehicle client can be dynamically controlled by the cloud, avoiding the risk of OTA function failure due to software failure, and optimizing the OTA software logic or repairing OTA software failures through the script files sent by the cloud, thereby improving the timeliness of optimization and repair.

[0103] Example 4

[0104] Figure 4 This is a flow chart of a vehicle software upgrade method provided according to the fourth embodiment of the present invention. This embodiment is applicable to the case where the vehicle software is upgraded in the cloud. The method can be executed by a vehicle software upgrade device. The vehicle software upgrade device can be implemented in the form of hardware and / or software. The vehicle software upgrade device can be configured in an electronic device with data processing capabilities. In this embodiment, the vehicle software upgrade method is applied to the cloud in the vehicle software upgrade system. Figure 4 As shown, the method includes:

[0105] S410: When it is detected that the target vehicle model meets the upgrade conditions, an upgrade task corresponding to the target vehicle model is generated and sent to the communication transmission base station.

[0106] The upgrade condition may be a condition that triggers an upgrade of the vehicle's software. In this embodiment, the upgrade condition may be pre-set. The upgrade condition may be new software update information for the target vehicle model, or a notification issued by the target vehicle model indicating a need for an upgrade due to a problem with the vehicle's software. The upgrade task may include script file information. The script file information may include information such as the version and download address of the script file required for the upgrade task. The upgrade task may include information such as the specific content or scope of the upgrade required for the target vehicle model.

[0107] In this embodiment, if the software of the target vehicle model fails, the corresponding upgrade information is sent to the communication transmission base station OTA, so that the communication transmission base station reports to the OTA management platform. The OTA management platform generates an upgrade task corresponding to the target vehicle model and sends it to the communication transmission base station. Therefore, in this embodiment, the specific way of detecting that the target vehicle model meets the upgrade conditions can be that the OTA management platform detects that the target vehicle model has a new software version that needs to be updated, or it can be that the OTA software itself has failed as reported by the communication transmission base station. In this embodiment, when the cloud detects that the target vehicle model meets the pre-set upgrade conditions, it will generate the upgrade task corresponding to the target program and send it to the communication transmission base station.

[0108] S420: Receive vehicle identification information sent by the communication transmission base station, and issue corresponding software upgrade package download information according to the vehicle identification information.

[0109] The vehicle identification information may include the vehicle identification, vehicle ECU identification, and vehicle ECU software version information. In this embodiment, upon receiving the script file in the OTA Master from the communication transmission base station, the cloud will invoke the vehicle identification information sent by the platform adaptation layer interface through the script engine, and will issue the corresponding software package upgrade download information based on the vehicle identification, vehicle ECU identification, and vehicle ECU software version information.

[0110] As can be understood, in this embodiment, the cloud can issue different software package upgrade download information based on different vehicle identification information. This allows the OTA management platform to dynamically control the vehicle-side OTA logic through script files based on interpreted languages without modifying the source code on the vehicle side, greatly enhancing the flexibility, scalability, and timeliness of OTA functions. In this embodiment, the fixed software of all vehicle models is consistent, and the software differences between vehicle models can be placed in the script files, reducing the complexity of the vehicle-side fixed software and thus improving the stability of the software.

[0111] The technical solution of an embodiment of the present invention detects that a target vehicle model meets the upgrade conditions, generates an upgrade task corresponding to the target vehicle model, and sends it to a communication transmission base station. The base station then receives vehicle identification information and sends corresponding software upgrade package download information based on the vehicle identification information. This technical solution issues the corresponding upgrade task and software upgrade package download information to the target vehicle model, which the base station then sends to the vehicle client for execution. This allows the upgrade logic of the vehicle client to be dynamically controlled by the cloud, avoiding the risk of OTA function failure due to software failure and improving the timeliness of optimization and repair.

[0112] An example of the overall architecture of a vehicle software upgrade method in this embodiment is shown in FIG. Figure 5 As shown. The OTA service end includes an OTA management platform (cloud), a push server and a content distribution network. The vehicle end may include various OTA nodes of a communication transmission base station, specifically including a communication master node OTA Master and various communication slave nodes OTA Slave; each OTA node includes a main control module, a script engine and a platform adaptation layer. In this embodiment, the OTA management platform (cloud) mainly sends script files and upgrade packages to the OTA master node (OTA Master) and each OTA slave node (OTA Slave) corresponding to the vehicle end. The OTA client (inside the OTA Master) and the main control module (inside the OTA Slave) will send their script files to the script engine. The script engine provides an environment for the operation of the script file, so that the entire OTA process can be implemented according to the logic described in the script file. The script file is written in an interpreted language (Lua / JS, etc.), and the corresponding virtual machine is integrated in the script engine to ensure that the code of the interpreted language can be executed and interact with the underlying platform adaptation layer. Without changing the vehicle-side software version, the OTA management platform can implement different OTA functional logics by sending script files with different logics.

[0113] The technical solution of the embodiment of the present invention is to write the script file in an interpretive language. Without modifying the source code on the vehicle side, the OTA management platform can dynamically control the OTA logic on the vehicle side through the script file based on the interpretive language, which greatly enhances the flexibility, scalability and timeliness of the OTA function. At the same time, the software solidified on all vehicle models on the vehicle side is consistent, and the software differences between the vehicle models can be placed in the script file, reducing the complexity of the vehicle-side solidified software and thereby improving the stability of the software.

[0114] Furthermore, this embodiment also provides another alternative embodiment, and the specific process is as follows:

[0115] Step 1: The OTA management platform pushes an upgrade task to the OTA client in the vehicle - end OTA Master, notifying the OTA client of a new OTA task. Step 2: The OTA client on the vehicle end reports vehicle - related information (vehicle identification, vehicle ECU identification, vehicle ECU software version information, etc.) to the OTA management platform, and the OTA management platform issues the download information of the upgrade package and the upgrade script file according to the vehicle - related information. Step 3: The OTA client downloads the upgrade package and the upgrade script file from the content distribution network according to the issued upgrade package download information. Step 4: The OTA client decrypts and verifies the signature of the downloaded upgrade package and script file. If the decryption and signature verification are successful, go to Step 5; otherwise, go to Step 9. Step 5: The OTA client determines whether the upgrade script file has been downloaded. If so, go to Step 6; otherwise, go to Step 7. Step 6: The OTA client updates the script files in the OTA Master and OTA Slave with the downloaded script file. Step 7: The OTA client triggers the script engine in the OTA Master to load and execute the script file in the OTA Master. Step 8: The script file in the OTA Master triggers the upgrade of the vehicle end. The script file in the OTA Master controls the overall upgrade strategy, and the script file in the OTA Slave is responsible for the overall upgrade strategy within its corresponding ECU or domain. Step 9: After the upgrade is completed (or when the decryption or signature verification of the upgrade package / script file fails), the OTA client is responsible for reporting the upgrade result to the OTA management platform.

[0116] In this embodiment, in the solution replacing the embodiment, the upgrade script only takes care of the upgrade logic and does not involve other processes (such as interacting with the OTA management platform to obtain upgrade package information, downloading the upgrade package, reporting the upgrade result to the OTA management platform, etc.).

[0117] Embodiment 5

[0118] Figure 6 It is a schematic structural diagram of an in - vehicle software upgrade device provided according to Embodiment 5 of the present invention. The in - vehicle software upgrade device is configured in the communication transmission base station in the in - vehicle software upgrade system. The communication transmission base station includes a communication master node and multiple communication slave nodes; a script engine is configured in both the communication master node and the multiple communication slave nodes. As Figure 6 shown, the device includes:

[0119] A task receiving module 610, configured to receive an upgrade task of a target vehicle model sent from the cloud; wherein, the upgrade task includes script file information;

[0120] A script update module 620, configured to update the script files in the communication master node and the communication slave node respectively based on the script file information, to obtain a first script file and a second script file;

[0121] An information reporting module 630 is configured to obtain vehicle identification information from an in-vehicle client corresponding to a target vehicle model through a script engine based on the first script file, and report the vehicle identification information to the cloud;

[0122] The upgrade package download module 640 is configured to receive software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package according to the first script file and the software package download information;

[0123] The upgrade control module 650 is used to send the software upgrade package, the first script file and the second script file to the vehicle client to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file.

[0124] Optionally, the script file information includes the first version information and the second version information of the script file and the corresponding script file download address;

[0125] The script update module 620 includes:

[0126] An update judgment unit, configured to judge whether a first preset script file in the communication master node needs to be updated based on the first version information, and to judge whether a second preset script file in the communication slave node needs to be updated based on the second version information;

[0127] The script to be updated downloading unit is used to download the first script file to be updated and the second script file to be updated respectively according to the script file download address if the first preset script file and the second preset script file need to be updated;

[0128] The updating unit is configured to update the first preset script file and the second preset script file based on the first script file to be updated and the second script file to be updated respectively, to obtain corresponding first script file and second script file.

[0129] Optionally, the update judgment unit is specifically used to:

[0130] Obtaining third version information corresponding to the first preset script file in the communication master node;

[0131] If the third version information is different from the first version information, the first preset script file in the communication master node needs to be updated;

[0132] If the third version information is the same as the first version information, the first preset script file in the communication master node does not need to be updated.

[0133] Optionally, the upgrade package download module 640 is specifically configured to:

[0134] Determining a download strategy for the software upgrade package according to the first script file;

[0135] Download the corresponding software upgrade package according to the download policy and software package download information.

[0136] An in-vehicle software upgrade device provided by an embodiment of the present invention can execute an in-vehicle software upgrade method provided by any one of the first and second embodiments of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0137] Example 6

[0138] Figure 7 Schematic diagram of the structure of a vehicle software upgrade device according to the sixth embodiment of the present invention. The vehicle software upgrade method is configured in the vehicle client in the vehicle software upgrade system. Figure 7 As shown, the device includes:

[0139] The file receiving module 710 is configured to receive a software upgrade package, a first script file, and a second script file sent by a communication transmission base station;

[0140] The software upgrade module 720 is used to upgrade the vehicle-mounted software based on the software upgrade package, the first script file and the second script file to obtain an upgrade result, and feed back the upgrade result to the communication transmission base station.

[0141] Optionally, the software upgrade module 720 is specifically configured to:

[0142] Determine the corresponding first software upgrade strategy and second software upgrade strategy respectively according to the first script file and the second script file; wherein the first software upgrade strategy includes the upgrade strategy of the entire vehicle end; and the second software upgrade strategy includes the upgrade strategy within each control unit area;

[0143] According to the software upgrade package, the first software upgrade strategy and the second software upgrade strategy, corresponding control units in the vehicle software are upgraded respectively to obtain upgrade results.

[0144] An in-vehicle software upgrade device provided in an embodiment of the present invention can execute an in-vehicle software upgrade method provided in the third embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0145] Example 7

[0146] Figure 8 This is a structural diagram of a vehicle software upgrade device according to embodiment 7 of the present invention. The vehicle software upgrade method is configured in the cloud in the vehicle software upgrade system. Figure 8 As shown, the device includes:

[0147] The upgrade task sending module 810 is used to generate an upgrade task corresponding to the target vehicle type and send it to the communication transmission base station when detecting that the target vehicle type meets the upgrade conditions;

[0148] The download information sending module 820 is used to receive the vehicle identification information sent by the communication transmission base station, and send the corresponding software upgrade package download information according to the vehicle identification information.

[0149] An in-vehicle software upgrade device provided in an embodiment of the present invention can execute an in-vehicle software upgrade method provided in a fourth embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0150] Example 8

[0151] Figure 9 is a structural diagram of a communication transmission device provided according to embodiment eight of the present invention. The communication transmission device 10 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 communication transmission 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.

[0152] like Figure 9 As shown, the communication transmission device 10 includes a communication master node 20 and at least one communication slave node 11, as well as a memory, such as a read-only memory (ROM) 12 and a random access memory (RAM) 13, communicatively connected to the communication master node 20 and the at least one communication slave node 11. The memory stores a computer program executable by at least one processor. The communication master node 20 and the communication slave node 11 can perform various appropriate actions and processes based on the computer program stored in the read-only memory (ROM) 12 or loaded from the storage unit 18 into the random access memory (RAM) 13. The RAM 13 can also store various programs and data required for the operation of the communication transmission device 10. The communication master node 20 and the communication slave node 11, the ROM 12, and the RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0153] Multiple components in the communication transmission 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 magnetic 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 communication transmission device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0154] The communication master node 20 and the communication slave node 11 can be various general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of the communication master node 20 and the communication slave node 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, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The communication master node 20 and the communication slave node 11 perform the various methods and processes described above, such as the vehicle software upgrade method.

[0155] In some embodiments, the vehicle software upgrade method can be implemented as a computer program that is tangibly contained in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the communication transmission 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 communication master node 20 and the communication slave node 11, one or more steps of the vehicle software upgrade method described above can be performed. Alternatively, in other embodiments, the communication master node 20 and the communication slave node 11 can be configured to perform the vehicle software upgrade method in any other appropriate manner (e.g., by means of firmware).

[0156] Various embodiments of the systems and techniques described 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), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes 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.

[0157] 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, such that when the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0158] An embodiment of the present invention also provides a vehicle, which is used to implement the vehicle software upgrade method as described in Example 3 of the present application.

[0159] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0160] To provide interaction with a user, the systems and techniques described herein can be implemented on a communication transmission 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 pointing device (e.g., a mouse or trackball) through which the user can provide input to the communication transmission device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0161] The systems and techniques described herein can be implemented in a computing system that includes back-end 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 front-end components (e.g., a user computer with a graphical user interface or 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 back-end components, middleware components, or front-end components. The components of the system can 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.

[0162] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0163] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0164] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A vehicle software upgrade method, characterized in that: The vehicle software upgrade method is applied to a communication transmission base station in a vehicle software upgrade system, wherein the communication transmission base station includes a communication master node and a plurality of communication slave nodes; The communication master node and the plurality of communication slave nodes are both configured with a script engine, and the vehicle software upgrade method includes: Receive an upgrade task for a target vehicle model issued by the cloud; wherein the upgrade task includes script file information; Based on the script file information, the script files in the communication master node and the communication slave node are updated respectively to obtain a first script file and a second script file; Obtaining vehicle identification information from the vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and reporting the vehicle identification information to the cloud; Receiving software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and downloading the corresponding software upgrade package according to the first script file and the software package download information; The software upgrade package, the first script file, and the second script file are sent to the vehicle-mounted client to control the vehicle-mounted software upgrade operation of the vehicle-mounted client based on the first script file and the second script file.

2. The method according to claim 1, characterized in that The script file information includes the first version information and the second version information of the script file and the corresponding script file download address; The script files of the communication master node and the communication slave node are updated based on the script file information to obtain a first script file and a second script file, including: Determining whether a first preset script file in the communication master node needs to be updated based on the first version information, and determining whether a second preset script file in the communication slave node needs to be updated based on the second version information; If the first preset script file and the second preset script file need to be updated, download the first script file to be updated and the second script file to be updated respectively according to the script file download address; The first preset script file and the second preset script file are updated respectively based on the first script file to be updated and the second script file to be updated to obtain corresponding first script file and second script file.

3. The method according to claim 2, characterized in that Determining whether the first preset script file in the communication master node needs to be updated based on the first version information includes: Obtaining third version information corresponding to the first preset script file in the communication master node; If the third version information is different from the first version information, the first preset script file in the communication master node needs to be updated; If the third version information is the same as the first version information, the first preset script file in the communication master node does not need to be updated.

4. The method according to claim 1, wherein Downloading the corresponding software upgrade package according to the first script file and the software package download information includes: Determining a download strategy for the software upgrade package according to the first script file; Download the corresponding software upgrade package according to the download strategy and the software package download information.

5. A vehicle software upgrade method, characterized in that: The vehicle software upgrade method is applied to a vehicle client in a vehicle software upgrade system, and the vehicle software upgrade method includes: Receiving a software upgrade package, a first script file, and a second script file sent by a communication transmission base station; The vehicle-mounted software is upgraded based on the software upgrade package, the first script file, and the second script file to obtain an upgrade result, and the upgrade result is fed back to the communication transmission base station.

6. The method according to claim 5, characterized in that The vehicle software is upgraded based on the software upgrade package, the first script file, and the second script file to obtain an upgrade result, including: Determine the corresponding first software upgrade strategy and second software upgrade strategy respectively according to the first script file and the second script file; wherein the first software upgrade strategy includes the upgrade strategy of the entire vehicle end; and the second software upgrade strategy includes the upgrade strategy within each control unit area; According to the software upgrade package, the first software upgrade strategy and the second software upgrade strategy, the corresponding control units in the vehicle-mounted software are upgraded respectively to obtain an upgrade result.

7. A vehicle software upgrade method, characterized in that: The vehicle software upgrade method is applied to the cloud in the vehicle software upgrade system, and the vehicle software upgrade method includes: When it is detected that the target vehicle model meets the upgrade conditions, an upgrade task corresponding to the target vehicle model is generated and sent to the communication transmission base station; Receive the vehicle identification information sent by the communication transmission base station, and issue corresponding software upgrade package download information according to the vehicle identification information.

8. A vehicle software upgrade device, characterized in that: The vehicle-mounted software upgrade device is configured in a communication transmission base station in the vehicle-mounted software upgrade system. The communication transmission base station includes a communication master node and multiple communication slave nodes. The communication master node and the multiple communication slave nodes are both configured with a script engine. The vehicle-mounted software upgrade device includes: A task receiving module is used to receive the upgrade task of the target vehicle model issued by the cloud; wherein the upgrade task includes script file information; A script updating module, configured to update the script files in the communication master node and the communication slave node respectively based on the script file information to obtain a first script file and a second script file; An information reporting module, configured to obtain vehicle identification information from an in-vehicle client corresponding to the target vehicle model through a script engine based on the first script file, and report the vehicle identification information to the cloud; An upgrade package download module, configured to receive software upgrade package download information corresponding to the vehicle identification information issued by the cloud, and download the corresponding software upgrade package according to the first script file and the software package download information; The upgrade control module is used to send the software upgrade package, the first script file and the second script file to the vehicle client to control the vehicle software upgrade operation of the vehicle client based on the first script file and the second script file.

9. A vehicle software upgrade device, characterized in that: The vehicle software upgrade method is configured on a vehicle client in a vehicle software upgrade system, and the vehicle software upgrade device includes: A file receiving module, configured to receive a software upgrade package, a first script file, and a second script file sent by a communication transmission base station; A software upgrade module is used to upgrade the vehicle-mounted software based on the software upgrade package, the first script file and the second script file to obtain an upgrade result, and to feed back the upgrade result to the communication transmission base station.

10. A vehicle software upgrade device, characterized in that: The vehicle software upgrade method is configured in the cloud of the vehicle software upgrade system, and the vehicle software upgrade device includes: The upgrade task sending module is used to generate an upgrade task corresponding to the target vehicle model and send it to the communication transmission base station when detecting that the target vehicle model meets the upgrade conditions; The download information sending module is used to receive the vehicle identification information sent by the communication transmission base station and send the corresponding software upgrade package download information according to the vehicle identification information.

11. A communication transmission device, characterized in that: The communication transmission equipment includes: a communication master node and at least one communication slave node; and a memory in communication connection with the one communication master node and the at least one communication slave node; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the one communication master node and the at least one communication slave node so that the one communication master node and the at least one communication slave node can execute the vehicle software upgrade method described in any one of claims 1-4.

12. A vehicle, characterized in that: The vehicle is used to execute the vehicle software upgrade method according to any one of claims 5-6.

13. 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 upgrade method according to any one of claims 1 to 4 or 7 when executed.

Images