Remote upgrading method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a remote upgrading method and device, electronic equipment and a storage medium. A vehicle version number uploaded by a target vehicle is acquired. It is judged whether a successor node associated with an upgrading path exists for a vehicle version node corresponding to the vehicle version number. If yes, the successor node associated with the upgrading path is taken as a target node, and the target vehicle is upgraded according to a file to be upgraded of the target node. Embodiments of the present application improve vehicle upgrading efficiency.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to vehicle remote upgrading technology, and particularly relate to a remote upgrading method and device, electronic equipment and a storage medium. BACKGROUND

[0002] With the popularization of the concept of software-defined vehicles, software continues to iterate, which plays an important role in the development of vehicles.

[0003] In the prior art, vehicle software is defined by each software carrier electronic control unit (ECU), and the software version number of a single electronic control unit is changed at will, which cannot intuitively determine the compatibility problem of the overall function of the vehicle, resulting in low upgrading efficiency of the vehicle. SUMMARY

[0004] The present application provides a remote upgrading method, device, electronic equipment and storage medium to improve the upgrading efficiency of the vehicle.

[0005] In a first aspect, embodiments of the present application provide a remote upgrading method, which comprises:

[0006] obtaining a vehicle version number uploaded by a target vehicle;

[0007] determining whether a vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path;

[0008] If yes, the successor node associated with the upgrade path is taken as a target node, and the target vehicle is upgraded according to the upgrade file of the target node.

[0009] In a second aspect, embodiments of the present application further provide a remote upgrading device, which comprises:

[0010] a vehicle version number acquisition module configured to obtain a vehicle version number uploaded by a target vehicle;

[0011] a successor node determination module configured to determine whether a vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path;

[0012] a target vehicle upgrading module configured to, if yes, take the successor node associated with the upgrade path as a target node, and upgrade the target vehicle according to the upgrade file of the target node.

[0013] In a third aspect, embodiments of the present application further provide electronic equipment, which comprises:

[0014] one or more processors;

[0015] a storage device configured to store one or more programs;

[0016] When one or more programs are executed by one or more processors, the one or more processors realize any one of the remote upgrading methods provided by the embodiments of the present application.

[0017] In a fourth aspect, the embodiments of the present application further provide a storage medium comprising computer executable instructions for executing any one of the remote upgrading methods provided by the embodiments of the present application when executed by a computer processor.

[0018] The present application obtains the whole vehicle version number uploaded by the target vehicle, and obtains the whole vehicle version information of the vehicle. It is judged whether the whole vehicle version node corresponding to the whole vehicle version number has a successor node associated with an upgrade path. If yes, the successor node associated with the upgrade path is taken as a target node, and the target node can be accurately determined through the upgrade path judgment. The target vehicle is upgraded according to the to-be-upgraded file of the target node. The whole vehicle upgrade of the target vehicle can be quickly realized, the compatibility of the whole vehicle can be taken into account, and the whole vehicle upgrade efficiency is improved. Therefore, through the technical solution of the present application, the problem that the software version number of a single electronic control unit is changed at will, the compatibility of the whole vehicle function cannot be intuitively judged, and the whole vehicle upgrade efficiency is low is solved, and the effect of improving the whole vehicle upgrade efficiency is achieved. BRIEF DESCRIPTION OF DRAWINGS

[0019] Figure 1 is a flowchart of a remote upgrading method in the first embodiment of the present application;

[0020] Figure 2a is a whole vehicle version number schematic diagram in the first embodiment of the present application;

[0021] Figure 2b is a whole vehicle version upgrade path schematic diagram in the first embodiment of the present application;

[0022] Figure 2c is a test vehicle whole vehicle version upgrade path schematic diagram in the first embodiment of the present application;

[0023] Figure 3 is a flowchart of a remote upgrading method in the second embodiment of the present application;

[0024] Figure 4 is a flowchart of a remote upgrading method in the third embodiment of the present application

[0025] Figure 5 is a target node user configuration information schematic diagram in the third embodiment of the present application;

[0026] Figure 6 is a structure schematic diagram of a remote upgrading device in the fourth embodiment of the present application;

[0027] Figure 7 Fig. 1 is a structural schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the personnel in the technical field better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work should belong to the scope of protection of the present application.

[0029] It should be noted that the terms "first" and "second" and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device including a series of steps or units does not necessarily have to include only those steps or units clearly listed, but can include other steps or units not clearly listed or inherent to the process, method, product or device.

[0030] Embodiment One

[0031] Figure 1 A flowchart of a remote upgrading method provided by the present application, the present embodiment can be applied to the case of remotely triggering software upgrading in a vehicle. The method can be performed by a remote upgrading device, which can be implemented by software and / or hardware and specifically configured on a server.

[0032] Referring to Figure 1 The remote upgrading method specifically includes the following steps:

[0033] S110, obtaining the whole vehicle version number uploaded by the target vehicle.

[0034] The software of each electronic control unit in the vehicle can be upgraded by over-the-air technology (OTA). In the over-the-air technology, the vehicle as a client obtains the corresponding upgrade data packet by communicating with the server.

[0035] The target vehicle can be a vehicle that communicates with the server, and can be understood as a vehicle managed by the server. The vehicle version number is the overall version number corresponding to the software versions of each electronic control unit in the target vehicle, used to represent the overall software version number of the target vehicle.

[0036] Currently, in existing technologies, vehicle software upgrade version numbers are defined separately for each electronic control unit (ECU), the carrier of the software. There is no real-time verification mechanism for the software functionalities between these ECUs, and no overall vehicle software version number is defined. The software version number of a single ECU can be changed arbitrarily, making it impossible to intuitively determine the compatibility issues of the vehicle's overall functions. Users cannot obtain comprehensive vehicle functional information through version numbers, thus degrading the user experience.

[0037] See Figure 2a The diagram illustrates the vehicle version number. The vehicle version number is defined based on the electronic control units (ECUs) of different domains within the vehicle. Specifically, the vehicle version number may include a vehicle identifier and a version number. The vehicle identifier can be used to represent the vehicle model and hardware identification, etc. For example, the vehicle version number could be FAW.OS.1.0. Here, FAW.OS represents the vehicle identification information, which can be used to identify whether it is the target vehicle; 1.0 represents the vehicle version number. The composition of the vehicle identifier and the number of digits in the version number can be adjusted according to actual needs, and this application does not impose specific limitations on this. The initial vehicle version number can be defined as FAW.OS.1.0. After an upgrade is completed for all domains of the ECUs in the target vehicle, which can be understood as a functional iteration of the ECUs of the entire target vehicle, the vehicle version number is upgraded to FAW.OS.2.0. If an upgrade is completed for some electronic control units in the target vehicle, it can be understood as a problem fix for some electronic control units of the whole vehicle. For example, if the connection domain ECU is upgraded from V3.0 to V3.1, the whole vehicle version number will be upgraded to FAW.OS.2.1.

[0038] S120. Determine whether the vehicle version node corresponding to the vehicle version number has a successor node with an upgrade path.

[0039] A vehicle version node represents a vehicle version number, and there is a unique correspondence between each vehicle version number and its associated node. That is, each vehicle version number corresponds to a unique vehicle version node. On the server side, a unique vehicle version node is created for each different vehicle version number. This node can be associated with an upgrade path, indicating the upgrade order for the vehicle version number. Simultaneously, each vehicle version node also associates with a unique file to be upgraded, used to upgrade the target vehicle.

[0040] The upgrade path can be a path that indicates the successor node to the vehicle's vehicle version node. The upgrade path is a directed path, and it is a one-way path. The successor node can be the node following the vehicle version node corresponding to the vehicle version number uploaded by the target vehicle.

[0041] After obtaining the vehicle version number uploaded by the target vehicle, determine the vehicle version node corresponding to the vehicle version number, and check whether the vehicle version node is associated with an upgrade path. If so, take the next node corresponding to the upgrade path as the successor node.

[0042] See Figure 2b The diagram shows the overall vehicle version upgrade path. Figure 2b In this context, 1.0.0, 1.0.1, 1.1.0, and 2.0.0 represent the vehicle version numbers. Each vehicle version number corresponds to a vehicle version node associated with an upgrade path. The successor node for that vehicle version node can be obtained through the upgrade path. For example, the vehicle version node with version number 1.0.0 is associated with an upgrade path, and the next node corresponding to this upgrade path is the vehicle version node with version number 1.01. This node is then used as the successor node for the vehicle version node with version number 1.00.

[0043] Optionally, the upgrade path associated with the vehicle version node corresponding to the vehicle version number of the test vehicle includes directional attributes, which include forward and reverse attributes, and the vehicle version node may not be associated with an upgrade path of the forward attribute.

[0044] The upgrade path associated with the vehicle version node corresponding to the vehicle version number of the test vehicle has both forward and reverse attributes. The test vehicle can be upgraded using either a forward or reverse upgrade path. Each node can correspond to at most one forward upgrade path and one reverse upgrade path.

[0045] See Figure 2c The diagram shows the upgrade path for the entire test vehicle. Figure 2c The vehicle version numbers 1.0.1, 2.0.2, and 4.0.0 for the test vehicles are not associated with positive attribute upgrade paths; that is, the overall upgrade process for the test vehicles may be discontinuous.

[0046] The upgrade path associated with the vehicle version node of the test vehicle includes both forward and reverse attributes, allowing for multiple iterations of upgrade testing on the same test vehicle, thus saving on upgrade testing costs.

[0047] S130. If so, the successor node with the associated upgrade path will be used as the target node, and the target vehicle will be upgraded according to the upgrade file of the target node.

[0048] If so, that is, the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path. The target node can be a successor node of the vehicle version node determined according to the upgrade path, and can be used to provide the upgrade file to the target vehicle. The upgrade file can be a file for upgrading at least one electronic control unit in the target vehicle. For example, the upgrade file includes the vehicle model, electronic control unit identifier, electronic control unit name, and software version number. After designating the successor node associated with the upgrade path as the target node, the upgrade file of the target node is obtained and sent to the target vehicle to trigger the target vehicle to automatically upgrade the corresponding electronic control unit. Specifically, the target vehicle instructs the target vehicle to upgrade the corresponding electronic control unit according to the upgrade file.

[0049] Optionally, if the upgrade path has a reverse attribute, the file to be upgraded in the target node is the reverse file to be upgraded. The content of the reverse file to be upgraded differs from and is unrelated to the file to be upgraded. It should be noted that there are also cases where a file to be upgraded can simultaneously be both a reverse file to be upgraded and a file to be upgraded.

[0050] By using the reverse upgrade file, corresponding files can be associated with nodes whose upgrade path attribute is reversed. The target vehicle, based on the reverse upgrade file, is instructed to upgrade the corresponding electronic control unit.

[0051] The technical solution of this embodiment obtains the overall vehicle version information by acquiring the vehicle version number uploaded by the target vehicle. It determines whether the vehicle version node corresponding to the vehicle version number has a successor node with an associated upgrade path. If so, the successor node with the associated upgrade path is taken as the target node. The target node can be accurately determined by judging the upgrade path. The target vehicle is then upgraded according to the upgrade file of the target node. This allows for a rapid overall upgrade of the target vehicle, taking into account the compatibility of the entire vehicle and improving the efficiency of the overall vehicle upgrade. Therefore, the technical solution of this application solves the problem of arbitrary changes to the software version number of a single electronic control unit, making it impossible to intuitively determine the compatibility of the overall vehicle functions, resulting in low upgrade efficiency for the entire vehicle, thus achieving the effect of improving the overall vehicle upgrade efficiency.

[0052] Example 2

[0053] Figure 3 This is a flowchart of a remote upgrade method provided in Embodiment 2 of this application. The technical solution of this embodiment is further refined based on the above technical solution.

[0054] Furthermore, before obtaining the vehicle version number uploaded by the target vehicle, add the following: "Obtain the uploaded file to be upgraded; based on the uploaded file to be upgraded, establish a new successor node with an associated upgrade path after the newly established latest vehicle version node" to create a new successor node.

[0055] See Figure 3 A remote upgrade method shown includes:

[0056] S210. Obtain the uploaded file to be upgraded.

[0057] The server monitors in real time whether any files to be upgraded have been uploaded. When an upgrade file is detected, it retrieves the file.

[0058] The software maintenance personnel for the electronic control unit (ECU) periodically upload new versions of the ECU software to resolve issues in the existing software or to upgrade the software functionality based on new usage requirements. The maintenance personnel upload the new version of the ECU software as the upgrade file to the server so that the server can obtain the upgrade file.

[0059] S220. Based on the uploaded upgrade file, create a new successor node with an upgrade path after the existing latest vehicle version node.

[0060] After the server obtains the file to be upgraded, it creates a successor node to the existing latest vehicle version node. It then associates the latest vehicle version node with the upgrade path from the new successor node. By creating a new successor node with the associated upgrade path, a corresponding vehicle version node is created for the uploaded file to be upgraded.

[0061] In one optional embodiment, based on the uploaded file to be upgraded, a new successor node with an associated upgrade path is established after the established latest vehicle version node, including: generating a corresponding upgrade vehicle version number based on the uploaded file to be upgraded; adding a new successor node with an associated upgrade path after the established latest vehicle version node; and establishing an association between the new successor node and the upgrade vehicle version number of the uploaded file to be upgraded.

[0062] The upgraded vehicle version number is the upgraded vehicle version number determined based on the file to be upgraded. For example, the file to be upgraded may include the upgraded vehicle version number, which is read from the file. Alternatively, the file to be upgraded may not include the upgraded vehicle version number, but may include upgrade information for the electronic control units (ECUs) to be upgraded. The server generates the upgraded version number according to a preset vehicle version naming rule. For example, the preset vehicle version naming rule might be: when the number of ECUs included in the file to be upgraded is greater than or equal to a preset threshold, increment the first digit of the vehicle version number by 1; when the number of ECUs included in the file to be upgraded is less than the preset threshold, increment the second digit of the vehicle version number by 1. For instance, if the file to be upgraded includes two ECUs: an engine controller and a transmission controller, where the engine controller's version number is 3.0 and the transmission controller's version number is 4.0, and the latest established vehicle version node corresponds to the vehicle version number FAW.OS.3.0, then the upgraded vehicle version number would be FAW.OS.3.1. For example, the preset vehicle version naming rule could also be that when the file to be upgraded includes a preset electronic control unit, the first digit of the vehicle version number is incremented by 1; when the file to be upgraded does not include a preset electronic control unit, the second digit of the vehicle version number is incremented by 1. The preset rule can be set according to the characteristics of the vehicle, and this application does not impose any specific limitations on it.

[0063] After the latest vehicle version node has been established on the server, a new successor node is added, and an upgrade path is established between the existing latest vehicle version node and the newly added successor node, with the upgrade path pointing to the new successor node. An association is established between this new successor node and the upgraded vehicle version number of the uploaded file to be upgraded. For example, the upgraded vehicle version number of the uploaded file to be upgraded can be used as the sequence number of the new successor node. For example, the association may also include the storage location of the uploaded file to be upgraded.

[0064] The process involves generating a corresponding vehicle version number based on the uploaded file to be upgraded. This is achieved by adding a new successor node with an associated upgrade path after the existing latest vehicle version node. This establishes a connection between the new successor node and the upgraded vehicle version number of the uploaded file. The upgraded vehicle version number of the uploaded file can then be retrieved through the new successor node, thus determining the vehicle version number corresponding to the new successor node.

[0065] S230, Obtain the vehicle version number uploaded by the target vehicle.

[0066] S240. Determine whether the vehicle version node corresponding to the vehicle version number has a related successor node with an upgrade path.

[0067] S250 If so, the successor node with the associated upgrade path will be used as the target node, and the target vehicle will be upgraded according to the upgrade file of the target node.

[0068] In one optional embodiment, the target vehicle is upgraded according to the upgrade file of the target node, including: taking the upgrade file corresponding to the upgraded vehicle version number of the target node as the target upgrade file, and upgrading the target vehicle according to the target upgrade file.

[0069] The target file is the file to be upgraded associated with the target node, used to instruct the target vehicle to perform an upgrade. After establishing the association between the new successor node and the upgraded vehicle version number of the uploaded file to be upgraded, the vehicle version node corresponding to the target vehicle's uploaded vehicle version number is obtained. If a new successor node with an associated upgrade path exists, that successor node is used as the target node, and the target upgrade file is the file to be upgraded corresponding to the upgraded vehicle version number of the target node. Sending the target file to the target vehicle instructs the target vehicle to perform an upgrade based on the target file.

[0070] By using the upgrade file corresponding to the vehicle version number of the target node as the target upgrade file, the target vehicle can be provided with the upgrade file corresponding to the vehicle version number in a timely manner, instructing the target vehicle to upgrade in a timely manner according to the target file, thereby improving the speed of vehicle upgrade.

[0071] It should be noted that the server monitors in real time whether there are any uploaded files to be upgraded. If so, steps S210 and S220 are executed sequentially. That is, steps S210 and S220 can occur at any time in any of steps S230, S240, and S250. The steps used in this embodiment are only one optional order.

[0072] The technical solution of this embodiment obtains the uploaded file to be upgraded; based on the uploaded file to be upgraded, after the established latest vehicle version node, a new successor node with an upgrade path is established, and new successor nodes with upgrade paths are established sequentially for the obtained file to be upgraded, ensuring the correctness of the connection relationship of the new nodes and ensuring the accuracy of the target vehicle upgrade.

[0073] In an optional embodiment, the remote upgrade method further includes: obtaining an upgrade path deletion request; wherein the upgrade path deletion request includes identification information of the successor node to be deleted; determining the upgrade path to be deleted associated with the vehicle version node based on the identification information of the successor node to be deleted; and deleting the upgrade path to be deleted.

[0074] An upgrade path deletion request can be a request to delete an existing upgrade path. After uploading the file to be upgraded, if a vulnerability is found in the software upgrade information within the file, the upgrade path corresponding to the vehicle version node of the vulnerable upgrade file can be deleted. This prevents target vehicles that have not yet obtained the vulnerable upgrade file from performing an upgrade based on it, thus avoiding vehicle upgrade failures due to vulnerabilities in the upgrade file itself. The successor node to be deleted can be the node pointed to by the upgrade path to be deleted. The identifier information of the successor node to be deleted can be the vehicle version number associated with the successor node. Specifically, based on the identifier information of the successor node to be deleted, the upgrade path pointing to that successor node is identified as the upgrade path to be deleted, and the upgrade path to be deleted is then deleted.

[0075] It should be noted that after deleting the upgrade path according to the upgrade path deletion request, the successor node to be deleted still exists to establish a new upgrade path with the new successor node, so as to indicate that vehicles that have completed the upgrade according to the upgrade path to be deleted can upgrade to the vehicle version corresponding to the new successor node according to the new upgrade path.

[0076] By obtaining the upgrade path deletion request, which includes the identifier information of the successor node to be deleted, the upgrade path associated with the vehicle version node can be determined based on the identifier information of the successor node. This allows for the rapid identification of the upgrade path to be deleted. Deleting the upgrade path can prevent the target vehicle from undergoing a vehicle upgrade based on the deleted upgrade path.

[0077] Example 3

[0078] Figure 4 This is a flowchart of a remote upgrade method provided in Embodiment 3 of this application. The technical solution of this embodiment is further refined based on the above technical solution.

[0079] Furthermore, the phrase "upgrade the target vehicle based on the upgrade file of the target node" is further refined into: "query whether the target node contains user configuration information; generate a target upgrade file based on the query results and the upgrade file of the target node; and send the target upgrade file to the target vehicle to instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file and update the vehicle version number of the target vehicle" in order to perform a personalized upgrade of the target vehicle.

[0080] See Figure 4 A remote upgrade method shown includes:

[0081] S310. Obtain the vehicle version number uploaded by the target vehicle.

[0082] S320. Determine whether the vehicle version node corresponding to the vehicle version number has a related successor node with an upgrade path.

[0083] S330. If so, then the successor node with the associated upgrade path will be used as the target node.

[0084] S340. Query whether the target node contains user configuration information.

[0085] User configuration information can be information that requires user configuration. Specifically, when the upgrade file corresponding to the target node includes user configuration information, a user configuration information identifier is set on the target node to quickly determine whether the target node contains user configuration information.

[0086] See Figure 5 The diagram illustrates user configuration information for a target node. Three user configuration information identifiers P are configured on node 2.0.0. Z _00、P Z _01 and P Z _02. When the target node is node 2.0.0, P can be identified based on the user configuration information. Z _00、P Z _01 and P Z _02 Quickly retrieve the corresponding user configuration information.

[0087] S350. Generate the target upgrade file based on the query results and the file to be upgraded for the target node.

[0088] The query results may or may not contain user configuration information. If the query results contain user configuration information, the user configuration information is combined with the file to be upgraded on the target node to generate the target upgrade file. If the query results do not contain user configuration information, the target upgrade file is generated based on the file to be upgraded on the target node.

[0089] In an optional embodiment, generating a target upgrade file based on the query results and the upgrade file of the target node includes: if the target node does not contain user configuration information, then the upgrade file of the target node is used as the target upgrade file.

[0090] If the target node does not contain user configuration information, no user configuration is required, and the file to be upgraded on the target node will be used as the target upgrade file.

[0091] If the target node does not contain user configuration information, the file to be upgraded on the target node will be used as the target upgrade file to quickly generate the target upgrade file, thereby improving the upgrade efficiency of the target vehicle.

[0092] In an optional embodiment, generating a target upgrade file based on the query results and the upgrade file of the target node includes: if the target node contains user configuration information, sending configuration query information for the user configuration information to the target vehicle and obtaining the target configuration items of the user configuration information fed back by the target vehicle; generating the target upgrade file based on the upgrade file of the target node and the target configuration items.

[0093] If the target node contains user configuration information, user configuration is required. A configuration query message for the user configuration information is sent to the target vehicle. The user can personalize the user configuration information in the configuration query message. After the user completes the configuration, the user configuration information is confirmed and uploaded to the server. The target configuration item can be the configuration option selected by the user based on the user configuration information. The target configuration item in the user configuration information returned by the target vehicle is obtained, and the target upgrade file is generated by combining the target node's upgrade file and the target configuration item according to the file generation rules.

[0094] If the target node contains user configuration information, a configuration query message for the user configuration information is sent to the target vehicle, and the target configuration items of the user configuration information fed back by the target vehicle are obtained. The user's personalized configuration information can be obtained, and a target upgrade file can be generated based on the upgrade file to be upgraded and the target configuration items of the target node. This can make the target upgrade file meet the user's personalized needs and improve the user experience.

[0095] S360: The target upgrade file is sent to the target vehicle to instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file and update the vehicle version number of the target vehicle.

[0096] Sending the target upgrade document to the target vehicle instructs the vehicle to upgrade its electronic control unit (ECU) according to the document. After the target vehicle upgrades its ECU, the vehicle's version number is updated based on the version number included in the upgrade document.

[0097] The technical solution of this embodiment enriches the content of the target upgrade file by querying whether the target node contains user configuration information. When user configuration information exists, the user sets the user configuration information according to their own needs. Based on the query results and the upgrade file to be upgraded on the target node, a target upgrade file is generated, enabling personalized customization of the target upgrade file. The target upgrade file is then sent to the target vehicle, instructing the target vehicle to upgrade its electronic control unit according to the target upgrade file, thus achieving personalized upgrades for the target vehicle. The vehicle version number of the target vehicle is updated to ensure its real-time performance.

[0098] Example 4

[0099] Figure 6 The diagram shown is a schematic representation of a remote upgrade device according to Embodiment 4 of this application. This embodiment is applicable to situations where software upgrades in a vehicle are remotely triggered. It is configured on a server side, and the specific structure of the remote upgrade device is as follows:

[0100] The vehicle version number acquisition module 410 is used to acquire the vehicle version number uploaded by the target vehicle.

[0101] The successor node judgment module 420 is used to determine whether there is a successor node with an upgrade path associated with the vehicle version number corresponding to the vehicle version number.

[0102] The target vehicle upgrade module 430 is used to, if so, take the successor node with the associated upgrade path as the target node, and upgrade the target vehicle according to the upgrade file of the target node.

[0103] The technical solution of this embodiment obtains the overall vehicle version information by acquiring the vehicle version number uploaded by the target vehicle. It determines whether the vehicle version node corresponding to the vehicle version number has a successor node with an associated upgrade path. If so, the successor node with the associated upgrade path is taken as the target node. The target node can be accurately determined by judging the upgrade path. The target vehicle is then upgraded according to the upgrade file of the target node. This allows for a rapid overall upgrade of the target vehicle, taking into account the compatibility of the entire vehicle and improving the efficiency of the overall vehicle upgrade. Therefore, the technical solution of this application solves the problem of arbitrary changes to the software version number of a single electronic control unit, making it impossible to intuitively determine the compatibility of the overall vehicle functions, resulting in low upgrade efficiency for the entire vehicle, thus achieving the effect of improving the overall vehicle upgrade efficiency.

[0104] Optional, the remote upgrade device also includes:

[0105] The module for obtaining files to be upgraded is used to obtain uploaded files to be upgraded.

[0106] The successor node creation module is used to create a new successor node with an upgrade path after the existing latest vehicle version node, based on the uploaded file to be upgraded.

[0107] Optional, the successor node creation module includes:

[0108] The vehicle version number generation unit is used to generate the corresponding vehicle version number based on the uploaded file to be upgraded.

[0109] The successor node addition unit is used to add a new successor node with an upgrade path after the newly established latest vehicle version node.

[0110] The association establishment unit is used to establish the association between the new successor node and the upgraded vehicle version number of the uploaded file to be upgraded;

[0111] Accordingly, the target vehicle upgrade module 430 includes:

[0112] The target upgrade file determination unit is used to take the upgrade file corresponding to the upgrade version number of the target node as the target upgrade file, and upgrade the target vehicle according to the target upgrade file.

[0113] Optional, remote upgrade devices include:

[0114] The deletion request acquisition module is used to acquire upgrade path deletion requests; the upgrade path deletion request includes the identification information of the successor node to be deleted;

[0115] The path determination module is used to determine the upgrade path associated with the vehicle version node to be deleted based on the identification information of the successor node to be deleted.

[0116] The path deletion module is used to delete upgrade paths that are to be deleted.

[0117] Optionally, the target vehicle upgrade module 430 includes:

[0118] The user configuration information query unit is used to query whether the target node contains user configuration information.

[0119] The target upgrade file generation unit is used to generate the target upgrade file based on the query results and the file to be upgraded of the target node;

[0120] The target upgrade document distribution unit is used to distribute the target upgrade document to the target vehicle, instructing the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade document, and update the vehicle version number of the target vehicle.

[0121] Optionally, the target upgrade file generation unit includes:

[0122] The target upgrade file generation subunit is used to use the target node's file to be upgraded as the target upgrade file if the target node does not contain user configuration information.

[0123] Optionally, the target upgrade file generation unit includes:

[0124] The target configuration item acquisition subunit is used to send configuration query information for user configuration information to the target vehicle if the target node contains user configuration information, and to obtain the target configuration item of the user configuration information returned by the target vehicle.

[0125] The target upgrade file combination subunit is used to generate target upgrade files based on the files to be upgraded and target configuration items of the target node.

[0126] The remote upgrade device provided in this application embodiment can execute the remote upgrade method provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing the remote upgrade method.

[0127] Example 5

[0128] Figure 7 This is a schematic diagram of the structure of an electronic device provided in Embodiment 5 of this application, as shown below. Figure 7 As shown, the electronic device includes a processor 510, a memory 520, an input device 530, and an output device 540; the number of processors 510 in the electronic device can be one or more. Figure 7 Taking a processor 510 as an example; the processor 510, memory 520, input device 530, and output device 540 in the electronic device can be connected via a bus or other means. Figure 7 Taking the example of a connection between China and Israel via a bus.

[0129] The memory 520, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the remote upgrade method in the embodiments of this application (e.g., the vehicle version number acquisition module 410, the successor node determination module 420, and the target vehicle upgrade module 430). The processor 510 executes various functional applications and data processing of the electronic device by running the software programs, instructions, and modules stored in the memory 520, thereby realizing the aforementioned remote upgrade method.

[0130] The memory 520 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function; the data storage area may store data created based on terminal usage. Furthermore, the memory 520 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include memory remotely located relative to the processor 510, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0131] Input device 530 can be used to receive input character information and generate key signal inputs related to user settings and function control of the electronic device. Output device 540 may include display devices such as a display screen.

[0132] Example 6

[0133] Embodiment 6 of this application also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform a remote upgrade method. The method includes: obtaining the vehicle version number uploaded by the target vehicle; determining whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path; if so, taking the successor node associated with the upgrade path as the target node, and upgrading the target vehicle according to the upgrade file of the target node.

[0134] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the method operations described above, but can also perform related operations in the remote upgrade method provided in any embodiment of this application.

[0135] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0136] It is worth noting that in the embodiments of the search device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0137] Note that the above are merely preferred embodiments and the technical principles employed in this application. Those skilled in the art will understand that this application is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this application. Therefore, although this application has been described in detail through the above embodiments, this application is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of this application, the scope of which is determined by the scope of the appended claims.

Claims

1. A remote upgrade method, characterized in that, include: Obtain the vehicle version number uploaded by the target vehicle; wherein, the vehicle version number is the overall version number corresponding to the software version of each electronic control unit in the target vehicle; the vehicle version number includes the vehicle identifier and the version number; Determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path; wherein, the upgrade path includes a direction attribute, and the direction attribute includes a forward attribute and a reverse attribute; If so, the successor node associated with the upgrade path is taken as the target node, and the target vehicle is upgraded according to the upgrade file of the target node. The method further includes: Retrieve the uploaded file to be upgraded; Based on the uploaded file to be upgraded, a new successor node with an upgrade path is created after the existing latest vehicle version node. Based on the uploaded file to be upgraded, the process of establishing a new successor node with an associated upgrade path after the existing latest vehicle version node includes: Generate the corresponding vehicle upgrade version number based on the uploaded upgrade file; After the established latest vehicle version node, add a new successor node with an associated upgrade path; Establish an association between the new associated successor node with the upgrade path and the upgraded vehicle version number of the uploaded file to be upgraded; Accordingly, upgrading the target vehicle based on the upgrade file of the target node includes: The file to be upgraded corresponding to the upgraded vehicle version number of the target node is taken as the target upgrade file, and the target vehicle is upgraded according to the target upgrade file; The step of upgrading the target vehicle based on the upgrade file of the target node includes: Query whether the target node contains user configuration information; Based on the query results and the files to be upgraded for the target node, generate the target upgrade file; The target upgrade file is sent to the target vehicle to instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file and update the vehicle version number of the target vehicle.

2. The method according to claim 1, characterized in that, The method further includes: Obtain an upgrade path deletion request; wherein the upgrade path deletion request includes the identification information of the successor node to be deleted; Based on the identification information of the successor node to be deleted, determine the upgrade path to be deleted associated with the vehicle version node; Delete the upgrade path to be deleted.

3. The method according to claim 1, characterized in that, The step of generating the target upgrade file based on the query results and the target node's upgrade file includes: If the target node does not contain the user configuration information, then the file to be upgraded on the target node will be used as the target upgrade file.

4. The method according to claim 1, characterized in that, The step of generating the target upgrade file based on the query results and the target node's upgrade file includes: If the target node contains the user configuration information, then send the configuration query information of the user configuration information to the target vehicle, and obtain the target configuration item of the user configuration information fed back by the target vehicle; Generate a target upgrade file based on the target node's upgrade file and the target configuration items.

5. A remote upgrade device, characterized in that, include: The vehicle version number acquisition module is used to acquire the vehicle version number uploaded by the target vehicle; wherein, the vehicle version number is the overall version number corresponding to the software version of each electronic control unit in the target vehicle; the vehicle version number includes vehicle identifier and version number; The successor node determination module is used to determine whether there is a successor node associated with an upgrade path for the vehicle version number corresponding to the vehicle version number; wherein, the upgrade path includes a direction attribute, and the direction attribute includes a forward attribute and a reverse attribute; The target vehicle upgrade module is used to, if so, take the successor node with the associated upgrade path as the target node, and upgrade the target vehicle according to the upgrade file of the target node; The device further includes: The module for obtaining files to be upgraded is used to obtain uploaded files to be upgraded. The successor node creation module is used to create a new successor node with an associated upgrade path after the already established latest vehicle version node, based on the uploaded file to be upgraded. The successor node establishment module includes: The vehicle version number generation unit is used to generate the corresponding vehicle version number based on the uploaded file to be upgraded. The successor node adding unit is used to add a new successor node with an associated upgrade path after the established latest vehicle version node. The association relationship establishment unit is used to establish the association relationship between the new associated successor node with the upgrade path and the upgraded vehicle version number of the uploaded file to be upgraded; Accordingly, the target vehicle upgrade module includes: The target upgrade file determination unit is used to take the file to be upgraded corresponding to the upgraded vehicle version number of the target node as the target upgrade file, and upgrade the target vehicle according to the target upgrade file; The target vehicle upgrade module also includes: The user configuration information query unit is used to query whether the target node contains user configuration information; The target upgrade file generation unit is used to generate a target upgrade file based on the query results and the file to be upgraded of the target node; The target upgrade file distribution unit is used to distribute the target upgrade file to the target vehicle, and to instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file, and update the vehicle version number of the target vehicle.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the remote upgrade method as described in any one of claims 1-4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements a remote upgrade method as described in any one of claims 1-4.

Images