WO2024051385A1 - 远程升级方法、装置、电子设备和存储介质 - Google Patents

远程升级方法、装置、电子设备和存储介质 Download PDF

Info

Publication number
WO2024051385A1
WO2024051385A1 PCT/CN2023/109990 CN2023109990W WO2024051385A1 WO 2024051385 A1 WO2024051385 A1 WO 2024051385A1 CN 2023109990 W CN2023109990 W CN 2023109990W WO 2024051385 A1 WO2024051385 A1 WO 2024051385A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
vehicle
upgrade
node
file
Prior art date
Application number
PCT/CN2023/109990
Other languages
English (en)
French (fr)
Inventor
柳旭
刘子玄
李长龙
张建平
Original Assignee
中国第一汽车股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国第一汽车股份有限公司 filed Critical 中国第一汽车股份有限公司
Publication of WO2024051385A1 publication Critical patent/WO2024051385A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • the embodiments of the present application relate to vehicle remote upgrade technology, for example, to a remote upgrade method, device, electronic equipment and storage medium.
  • vehicle software is defined by the electronic control unit (ECU) that is the carrier of each software.
  • ECU electronice control unit
  • the software version number of a single electronic control unit can be changed at will, making it impossible to intuitively judge the compatibility issues of the overall functions of the vehicle, resulting in the overall Car upgrade efficiency is low.
  • This application provides a remote upgrade method, device, electronic equipment and storage medium to improve the upgrade efficiency of the entire vehicle.
  • the embodiment of the present application provides a remote upgrade method.
  • the remote upgrade method includes:
  • the successor node associated with the upgrade path is used as the target node, and the target vehicle is upgraded according to the file to be upgraded of the target node.
  • the embodiment of the present application also provides a remote upgrade device, which includes:
  • the vehicle version number acquisition module is set to obtain the vehicle version number uploaded by the target vehicle;
  • the successor node judgment module is configured to determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path;
  • the target vehicle upgrade module is configured to respond to the determination result that there is a successor node associated with an upgrade path, use the successor node associated with the upgrade path as the target node, and upgrade the target vehicle according to the file to be upgraded of the target node.
  • Embodiments of the present application also provide electronic equipment, which includes:
  • processors one or more processors
  • a storage device configured to store one or more programs
  • one or more processors are caused to implement any remote upgrade method as provided by the embodiments of this application.
  • Embodiments of the present application also provide a storage medium including computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform any remote upgrade method as provided by the embodiments of the present application.
  • Figure 1 is a flow chart of a remote upgrade method in Embodiment 1 of the present application.
  • Figure 2a is a schematic diagram of a vehicle version number in Embodiment 1 of the present application.
  • Figure 2b is a schematic diagram of a vehicle version upgrade path in Embodiment 1 of the present application.
  • Figure 2c is a schematic diagram of the vehicle version upgrade path of a test vehicle in Embodiment 1 of the present application.
  • Figure 3 is a flow chart of a remote upgrade method in Embodiment 2 of the present application.
  • Figure 4 is a flow chart of a remote upgrade method in Embodiment 3 of the present application.
  • Figure 5 is a schematic diagram of user configuration information of a target node in Embodiment 3 of the present application.
  • Figure 6 is a schematic structural diagram of a remote upgrade device in Embodiment 4 of the present application.
  • Figure 7 is a schematic structural diagram of an electronic device in Embodiment 5 of the present application.
  • Figure 1 is a flow chart of a remote upgrade method provided in Embodiment 1 of the present application. This embodiment can be applied to the situation of remotely triggering software upgrade in the vehicle. The method can be executed by a remote upgrade device, and the device can use software and /Or implemented in hardware and configured on the server.
  • OTA Over-the-Air Technology
  • 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 multiple electronic control units in the target vehicle.
  • the vehicle version number is used to represent the overall version number of the multiple software versions of the target vehicle.
  • the software function correlation between multiple electronic control units can be calibrated in real time, the software function information of the entire vehicle can be obtained, and the compatibility of the software function of the entire vehicle can be judged, thereby improving user experience.
  • the vehicle version number may include vehicle identification and version number.
  • Vehicle identification can be used to indicate vehicle model and hardware identification, etc.
  • the vehicle version number can be FAW.OS.1.0.
  • FAW.OS in the vehicle version number can represent the vehicle identification and can be used to identify whether it is a target vehicle; 1.0 in the vehicle version number is used to represent the version number of the vehicle version number.
  • the composition of the vehicle logo and the number of digits in the version number can be adjusted according to actual needs.
  • the initial vehicle version number can be defined as FAW.OS.1.0.
  • the vehicle version node may be a node representing the vehicle version number, and there is a unique correspondence between the vehicle version node and the vehicle version number. That is, a vehicle version number corresponds to a unique vehicle version node. A unique corresponding vehicle version node is established in the server for different vehicle version numbers.
  • the vehicle version node can be associated with an upgrade path, and the upgrade path represents the upgrade sequence of the vehicle version number.
  • the vehicle version node is also associated with a file to be upgraded that uniquely corresponds to the vehicle version node, and the file to be upgraded is used to upgrade the target vehicle.
  • the upgrade path may be a path used to instruct the vehicle to obtain a successor node of the complete vehicle version node.
  • upgrade The path is a directed path and a one-way path.
  • the successor node may be the node after the vehicle version node corresponding to the vehicle version number uploaded by the target vehicle.
  • the vehicle version node corresponding to the vehicle version number After obtaining the vehicle version number uploaded by the target vehicle, determine the vehicle version node corresponding to the vehicle version number, and determine whether the vehicle version node is associated with an upgrade path. If there is an upgrade path associated with the vehicle version node, the next node corresponding to the upgrade path will be used as the successor node.
  • the vehicle version node corresponding to each vehicle version number is associated with an upgrade path, and the successor node corresponding to the vehicle version node can be obtained through the upgrade path.
  • the vehicle version node with version number 1.0.0 is associated with an upgrade path.
  • the next node corresponding to the upgrade path is the vehicle version node with version number 1.0.1. This node is regarded as The vehicle version number is the successor node of the vehicle version node whose version number is 1.0.0.
  • the upgrade path associated with the vehicle version node corresponding to the vehicle version number of the test vehicle includes a direction attribute.
  • the direction attribute includes a forward attribute and a reverse attribute, and the vehicle version node may not be associated with an upgrade path of a forward attribute. .
  • the upgrade path associated with the vehicle version node corresponding to the vehicle version number of the test vehicle has forward attributes and reverse attributes.
  • the test vehicle can be upgraded according to the upgrade path of forward attributes or the upgrade path of reverse attributes.
  • Each vehicle version node corresponds to at most one forward attribute upgrade path and one reverse attribute upgrade path.
  • the same test vehicle can be upgraded and tested multiple times, saving the cost of upgrade testing.
  • the target node may be a successor node of the vehicle version node determined according to the upgrade path, and the target node may be used to provide files to be upgraded for the target vehicle.
  • the file to be upgraded may be a file that upgrades at least one electronic control unit in the target vehicle.
  • the file to be upgraded includes the vehicle model, electronic control unit identification, electronic control unit name, software version number, etc.
  • the file to be upgraded on the target node is the reverse file to be upgraded, and the contents of the reverse file to be upgraded and the file to be upgraded are different and unrelated.
  • the files to be upgraded can be used as reverse files to be upgraded and files to be upgraded.
  • the file to be upgraded by reverse can be the file associated with the vehicle version node whose attribute of the upgrade path is the reverse attribute.
  • the target vehicle upgrades the corresponding electronic control unit according to the reverse to-be-upgraded file.
  • the technical solution of this embodiment is to obtain the vehicle version information of the entire vehicle by obtaining the vehicle version number uploaded by the target vehicle. Determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path. If there is a successor node associated with an upgrade path, use the successor node associated with the upgrade path as the target node. Judging by the upgrade path, you can Accurately determine the target node. Upgrading the target vehicle according to the files to be upgraded on the target node can quickly realize the overall upgrade of the target vehicle, take into account the compatibility of the entire vehicle, and improve the efficiency of the entire vehicle upgrade.
  • Figure 3 is a flow chart of a remote upgrade method provided in Embodiment 2 of the present application.
  • the target vehicle Before obtaining the vehicle version number uploaded by the target vehicle, it also includes: obtaining the uploaded file to be upgraded; based on the uploaded file to be upgraded, establishing a new successor node with an associated upgrade path after the latest vehicle version node that has been established. , to create a new successor node.
  • the server detects in real time whether files to be upgraded are uploaded to the server. When it is detected that files to be upgraded are uploaded to the server, the files to be upgraded are obtained.
  • the software maintenance personnel of the electronic control unit will upload new versions of the electronic control unit software from time to time to overcome problems in the used electronic control unit software, or to improve the functions of the electronic control unit software according to new usage requirements. upgrade.
  • the maintenance personnel uploads the new version of the electronic control unit's software to the server as a file to be upgraded, so that the server obtains the file to be upgraded.
  • the server After the server obtains the file to be upgraded, it establishes the successor node of the latest vehicle version node that has been established.
  • the upgrade path from the latest vehicle version node to the new successor node is associated with the latest vehicle version node. pass Establish a new successor node associated with the upgrade path, and establish a corresponding vehicle version node for the uploaded file to be upgraded.
  • a new successor node associated with the upgrade path is established, including: generating a corresponding upgrade package according to the uploaded file to be upgraded. vehicle version number; after the established latest vehicle version node, add a new successor node associated with the upgrade path; establish an association between the new successor node and the upgraded vehicle version number of the uploaded file to be upgraded.
  • the upgraded vehicle version number is the upgraded vehicle version number determined based on the file to be upgraded.
  • the file to be upgraded may include the version number of the entire vehicle to be upgraded, and the version number of the entire vehicle to be upgraded may be read from the file to be upgraded.
  • the file to be upgraded may not include the upgraded vehicle version number.
  • the upgrade file includes the upgrade information of the electronic control unit to be upgraded.
  • the server generates the upgraded vehicle version number according to the preset vehicle version naming rules. .
  • the preset vehicle version number naming rule may be that when the number of electronic control units included in the file to be upgraded is greater than or equal to the preset threshold, the vehicle version number corresponding to the latest established vehicle version node will be added.
  • the file to be upgraded includes two electronic control units: engine controller and transmission controller.
  • the version number of the engine controller is 3.0
  • the version number of the transmission controller is 4.0
  • the preset threshold is 3. It has been established
  • the vehicle version number corresponding to the latest vehicle version node is FAW.OS.3.0
  • the upgraded vehicle version number is FAW.OS.3.1.
  • the preset vehicle version number naming rule can also be that when the file to be upgraded includes a preset electronic control unit, the first digit of the vehicle version number corresponding to the latest established vehicle version node is increased by 1. , get the upgraded vehicle version number; when the file to be upgraded does not include the preset electronic control unit, add 1 to the second digit of the vehicle version number corresponding to the latest established vehicle version node to get the upgraded vehicle version number .
  • the preset rules can be set according to the characteristics of the vehicle, which is not specifically limited in this application.
  • a new successor node is added, and an upgrade path between the established latest vehicle version node and the added new successor node is established.
  • the direction of the upgrade path points to the new successor node.
  • Establish an association between the 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 serial number of the new successor node.
  • the association relationship may also include the storage location of the uploaded file to be upgraded.
  • a corresponding vehicle version number is generated for the file to be upgraded.
  • a corresponding vehicle version node is established for the file to be upgraded, and an upgrade integration between the new successor node and the uploaded file to be upgraded is established.
  • the relationship between car version numbers can be determined through the new The successor node obtains the upgraded vehicle version number of the uploaded file to be upgraded, and determines the vehicle version number corresponding to the new successor node.
  • S240 Determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path.
  • upgrading the target vehicle according to the file to be upgraded of the target node includes: using the file to be upgraded corresponding to the upgraded vehicle version number of the target node as the target upgrade file, and updating the target vehicle according to the target node. Upgrade file to upgrade the target vehicle.
  • the target upgrade file is a file to be upgraded associated with the target node and is used to instruct the target vehicle to upgrade. After establishing the association between the new successor node and the upgraded vehicle version number of the uploaded file to be upgraded, obtain the vehicle version node corresponding to the vehicle version number uploaded by the target vehicle. If there is a new vehicle version node in the vehicle version node, is associated with a successor node of the upgrade path, then the 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 corresponding to the target node. Sending the target upgrade file to the target vehicle can instruct the target vehicle to upgrade according to the target upgrade file.
  • the target vehicle can be provided with the to-be-upgraded file corresponding to the upgraded vehicle version number in a timely manner, instructing the target vehicle to upgrade in a timely manner according to the target upgrade file. Increase the speed of vehicle upgrades.
  • the server monitors in real time whether there are uploaded files to be upgraded. If the uploaded files to be upgraded are detected, S210 and S220 are executed sequentially, that is, S210 and S220 can occur at any time in any step of S230, S240, and S250. The steps adopted in this embodiment are only an optional sequence.
  • the technical solution of this embodiment is to obtain the uploaded file to be upgraded; according to the uploaded file to be upgraded, after the latest vehicle version node that has been established, a new successor node with an associated upgrade path is established, and the order is:
  • the file to be upgraded establishes a new associated successor node with an upgrade path to ensure the correctness of the connection relationship of the new node and the accuracy of the target vehicle upgrade.
  • 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; and determining the upgrade path to be deleted based on the identification information of the successor node to be deleted. ;Delete the upgrade path to be deleted.
  • the upgrade path deletion request may be a request to delete an existing upgrade path. After uploading the file to be upgraded, if it is found that there is a vulnerability in the software upgrade information in the file to be upgraded, you can delete the upgrade path corresponding to the vehicle version node corresponding to the file to be upgraded to avoid not obtaining the vulnerability.
  • the target vehicle of the file to be upgraded is upgraded according to the file to be upgraded with vulnerabilities, so as to avoid the vehicle upgrade from malfunctioning due to the vulnerabilities of the file to be upgraded itself.
  • the successor node to be deleted may be the node pointed by the upgrade path to be deleted.
  • the identification information of the successor node to be deleted may be the vehicle version number associated with the successor node to be deleted. According to the identification information of the successor node to be deleted, an upgrade path pointing to the successor node to be deleted is determined as the upgrade path to be deleted, and the upgrade path to be deleted is deleted.
  • the successor node to be deleted still has a new upgrade path for establishing a connection with the new successor node to indicate that the vehicle has completed the upgrade according to the upgrade path to be deleted.
  • the new The upgrade path upgrades to the vehicle version corresponding to the new successor node.
  • the upgrade path deletion request includes the identification information of the successor node to be deleted, and the upgrade path to be deleted is determined based on the identification information of the successor node to be deleted, and the upgrade path to be deleted can be quickly determined based on the identification information of the successor node to be deleted. Upgrade path. Deleting the upgrade path to be deleted can prevent the target vehicle from being upgraded based on the upgrade path to be deleted.
  • Figure 4 is a flow chart of a remote upgrade method provided in Embodiment 3 of the present application.
  • upgrading the target vehicle according to the file to be upgraded of the target node includes: querying whether the target node contains user configuration information; generating a target upgrade file based on the query result and the file to be upgraded of the target node; 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 to perform personalized upgrades to the target vehicle.
  • S320 Determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path.
  • the user configuration information may be information that needs to be configured by the user.
  • set the user configuration information identifier corresponding to the user configuration information on the target node to quickly query whether the target node includes user configuration information.
  • FIG. 5 See Figure 5 for a schematic diagram of user configuration information of a target node.
  • PZ_00, PZ_01 and PZ_02 configured on node 2.0.0.
  • the target node is node 2.0.0, the corresponding user configuration can be quickly queried based on the user configuration information identification PZ_00, PZ_01 and PZ_02. configuration information.
  • S350 Generate a target upgrade file based on the query result and the file to be upgraded on the target node.
  • the query result can be that the target node contains user configuration information or the target node does not contain user configuration information. If the query result is that the target node contains 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 result is that the target node does not contain user configuration information, the target upgrade file is generated based on the file to be upgraded on the target node.
  • generating a target upgrade file based on the query result and the file to be upgraded on the target node includes: if the target node does not contain user configuration information, using the file to be upgraded on the target node as the target upgrade file.
  • the target node does not contain user configuration information, it means that no user configuration is required, and the file to be upgraded on the target node is directly used as the target upgrade file.
  • the file to be upgraded of the target node is used as the target upgrade file, so that the target upgrade file can be quickly generated and the upgrade efficiency of the target vehicle can be improved.
  • generating a target upgrade file based on the query result and the target node's file to be upgraded includes: if the target node contains user configuration information, sending configuration query information of the user configuration information to the target vehicle, and obtaining the target The target configuration item of the user configuration information fed back by the vehicle; the target upgrade file is generated based on the file to be upgraded and the target configuration item of the target node.
  • the target node contains user configuration information, it means that the user needs to configure it.
  • the user can perform personalized configuration on the user configuration information in the configuration query information.
  • After the user completes the configuration of the user configuration information confirm the user configuration information and upload the target configuration items to the server.
  • the target configuration item may be a configuration option selected by the user based on user configuration information. Obtain the target configuration items of the user configuration information fed back by the target vehicle, and generate the target upgrade file based on the file generation rules based on the files to be upgraded and the target configuration items of the target node.
  • the configuration inquiry information of 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 the user's personalized configuration information can be obtained according to the target node's to-be-upgraded Files and target configuration items generate target upgrade files, which can make the target upgrade files meet the personalized needs of users and improve user experience.
  • S360 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.
  • Distributing the target upgrade file to the target vehicle can instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file. After the target vehicle upgrades the electronic control unit in the target vehicle according to the target upgrade file, the complete vehicle version number of the target vehicle is updated according to the complete vehicle version number included in the target upgrade file.
  • the technical solution of this embodiment enriches the content of the target upgrade file by querying whether the target node contains user configuration information.
  • the target upgrade file is generated, which can realize personalized customization of 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 to achieve personalized upgrade of the target vehicle. Update the vehicle version number of the target vehicle to ensure the real-time nature of the vehicle version number of the target vehicle.
  • FIG. 6 shows a schematic structural diagram of a remote upgrade device provided in Embodiment 4 of the present application.
  • the remote upgrade device is configured on the server.
  • the structure of the remote upgrade device It includes: the vehicle version number acquisition module 410, which is configured to obtain the vehicle version number uploaded by the target vehicle; the successor node judgment module 420, which is configured to determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path. ;
  • the target vehicle upgrade module 430 is configured to respond to the determination result that there is a successor node associated with the upgrade path, use the successor node associated with the upgrade path as the target node, and upgrade the target vehicle according to the file to be upgraded of the target node.
  • the technical solution of this embodiment is to obtain the vehicle version information of the entire vehicle by obtaining the vehicle version number uploaded by the target vehicle. Determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path. If there is a successor node associated with an upgrade path, use the successor node associated with the upgrade path as the target node. Judging by the upgrade path, you can Accurately determine the target node. Upgrade the target vehicle according to the file to be upgraded on the target node. It can quickly realize the overall upgrade of the target vehicle, take into account the compatibility of the entire vehicle, and improve the efficiency of the entire vehicle upgrade.
  • the remote upgrade device also includes: a file acquisition module to be upgraded, which is configured to obtain the uploaded file to be upgraded; a successor node establishment module, which is configured to create the latest vehicle version node based on the uploaded file to be upgraded. , establish a new associated successor node with an upgrade path.
  • a file acquisition module to be upgraded which is configured to obtain the uploaded file to be upgraded
  • a successor node establishment module which is configured to create the latest vehicle version node based on the uploaded file to be upgraded. , establish a new associated successor node with an upgrade path.
  • the successor node establishment module includes: an upgrade vehicle version number generation unit, which is set to generate the corresponding upgrade vehicle version number based on the uploaded file to be upgraded; a successor node addition unit, which is set to generate the latest vehicle version number that has been created After the version node, a new successor node associated with the upgrade path is added; the association relationship establishment unit is configured to establish an association relationship between the new successor node and the upgraded vehicle version number of the uploaded file to be upgraded.
  • the target vehicle upgrade module 430 includes: a target upgrade file determination unit configured to use 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 remote upgrade device also includes: a deletion request acquisition module, configured to obtain an upgrade path deletion request; wherein the upgrade path deletion request includes the identification information of the successor node to be deleted; a path determination module, configured to obtain the upgrade path deletion request based on the successor node to be deleted.
  • the identification information of the node determines the upgrade path to be deleted; the path deletion module is set to delete the upgrade path to be deleted.
  • the target vehicle upgrade module 430 also includes: a user configuration information query unit, configured to query whether the target node contains user configuration information; a target upgrade file generation unit, configured to generate a file according to the query result and the file to be upgraded of the target node.
  • Target upgrade file; the target upgrade file delivery unit is set to deliver the target upgrade file to the target vehicle, and is used to instruct the target vehicle to upgrade the electronic control unit in the target vehicle according to the target upgrade file, and update the overall configuration of the target vehicle. Car version number.
  • the target upgrade file generation unit includes: a target upgrade file generation subunit, which is set 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.
  • the target upgrade file generation unit also includes: a target configuration item acquisition subunit, which is set to send configuration query information of the user configuration information to the target vehicle if the target node contains user configuration information, and obtain user feedback from the target vehicle.
  • the target configuration item of the configuration information is set to generate a target upgrade file based on the target node's file to be upgraded and the target configuration item.
  • the remote upgrade device provided by the embodiments of this application can execute the remote upgrade method provided by any embodiment of this application, and has the corresponding functional modules and effects for executing the remote upgrade method.
  • Figure 7 is a schematic structural diagram of an electronic device provided in Embodiment 5 of the present application.
  • the electronic device includes a processor 510, a memory 520, an input device 530 and an output device 540; The number may be one or more.
  • one processor 510 is taken as an example; the processor 510, memory 520, input device 530 and output device 540 in the electronic device may be connected through a bus or other means.
  • a processor 510 is used as an example. Take bus connection as an example.
  • the memory 520 can be used to store software programs, computer executable programs and modules, such as program instructions/modules corresponding to the remote upgrade method in the embodiment of the present application (for example, the vehicle version number acquisition module 410 , successor node judgment module 420 and target vehicle upgrade module 430).
  • the processor 510 executes the software programs, instructions and modules stored in the memory 520 to execute multi-function applications and data processing of the electronic device, that is, to implement the above-mentioned remote upgrade method.
  • the memory 520 may mainly include a stored program area and a stored data area, where the stored program area may store an operating system and an application program required for at least one function; the stored data area may store data created based on the use of the terminal, etc.
  • 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 memory. Solid state storage devices.
  • memory 520 may include memory located remotely from processor 510, and these remote memories may be connected to the electronic device through a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations of the Internet, intranets, local area networks, and mobile communication networks.
  • the input device 530 may be configured to receive input character information and generate key signal input related to user settings and function control of the electronic device.
  • the output device 540 may include a display device such as a display screen.
  • Embodiment 6 of the present application also provides a storage medium containing computer-executable instructions.
  • the 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 uploaded by the target vehicle. number; determine whether the vehicle version node corresponding to the vehicle version number has a successor node associated with an upgrade path; in response to the determination result that there is a successor node associated with an upgrade path, use the successor node associated with the upgrade path as the target node, and Upgrade the target vehicle according to the file to be upgraded on the target node.
  • the embodiments of the present application provide a storage medium containing computer-executable instructions.
  • the computer-executable instructions are not limited to the above-mentioned method operations, and can also perform related tasks in the remote upgrade method provided by any embodiment of the application. operate.
  • the technical solution of this application can be embodied in the form of a software product.
  • the computer software product can be stored in a computer-readable storage medium, such as a computer's floppy disk, read-only memory (Read-Only Memory, ROM), random access memory ( Random Access Memory (RAM), flash memory (FLASH), hard disk or optical disk, etc.
  • the computer-readable storage medium includes multiple instructions to cause an electronic device (which can be a personal computer, server, or network device, etc.) to execute this application Methods described in various embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

一种远程升级方法、装置、电子设备和存储介质，远程升级方法包括：获取目标车辆上传的整车版本号(S110)；判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点(S120)；响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级(S130)。

Description

远程升级方法、装置、电子设备和存储介质
本申请要求在2022年09月09日提交中国专利局、申请号为202211104068.5的中国专利申请的优先权，以上申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及车辆远程升级技术，例如涉及一种远程升级方法、装置、电子设备和存储介质。
背景技术
随着软件定义汽车的理念的普及以及软件持续迭代，软件在车辆的发展中具有重要作用。
相关技术中，车辆软件是以每个软件的载体电子控制单元(Electronic Control Unit，ECU)定义的，单个电子控制单元的软件版本号随意变更，无法直观判断车辆整体功能的兼容性问题，导致整车的升级效率低。
发明内容
本申请提供一种远程升级方法、装置、电子设备和存储介质，以提高整车的升级效率。
本申请实施例提供了一种远程升级方法，该远程升级方法包括：
获取目标车辆上传的整车版本号；
判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；
响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
本申请实施例还提供了一种远程升级装置，该远程升级装置包括：
整车版本号获取模块，设置为获取目标车辆上传的整车版本号；
后继节点判断模块，设置为判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；
目标车辆升级模块，设置为响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
本申请实施例还提供了电子设备，该电子设备包括：
一个或多个处理器；
存储装置，设置为存储一个或多个程序；
当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现如本申请实施例提供的任意一种远程升级方法。
本申请实施例还提供了一种包括计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行如本申请实施例提供的任意一种远程升级方法。
附图说明
图1是本申请实施例一中的一种远程升级方法的流程图；
图2a是本申请实施例一中的一种整车版本号示意图；
图2b是本申请实施例一中的一种整车版本升级路径示意图；
图2c是本申请实施例一中的一种测试车辆整车版本升级路径示意图；
图3是本申请实施例二中的一种远程升级方法的流程图；
图4是本申请实施例三中的一种远程升级方法的流程图；
图5是本申请实施例三中的一种目标节点用户配置信息示意图；
图6是本申请实施例四中的一种远程升级装置的结构示意图；
图7是本申请实施例五中的一种电子设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行说明。
本申请的说明书和权利要求书及上述附图中的术语“第一”和“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
实施例一
图1为本申请实施例一提供的一种远程升级方法的流程图，本实施例可适用于远程触发车辆中的软件升级的情况，该方法可以由远程升级装置执行，该装置可以采用软件和/或硬件实现，并配置于服务端。
参见图1所示的远程升级方法，包括如下步骤：
S110、获取目标车辆上传的整车版本号。
通过空中下载技术(Over-the-Air Technology，OTA)可以实现对车辆中的多个电子控制单元的软件进行升级。空中下载技术中车辆作为客户端通过与服务端通信获取多个电子控制单元相应的升级数据包。
目标车辆可以为与服务端进行通信的车辆，可以理解为服务端所管理的车辆。整车版本号为目标车辆中的多个电子控制单元的软件版本对应的整体版本号，整车版本号用于表示目标车辆的多个软件版本的整体版本号。
通过本申请定义的整车版本号，能够对多个电子控制单元之间的软件功能关联性进行实时校对，能够获得车辆整体的软件功能信息且能判断车辆整体的软件功能的兼容性，提升用户体验。
参见图2a所示的整车版本号示意图。根据车辆中不同域的电子控制单元，定义整车版本号。整车版本号可以包括车辆标识和版本编号。车辆标识可以用于表示车辆型号和硬件标识等。例如，整车版本号可以为FAW.OS.1.0。整车版本号中的FAW.OS可以表示车辆标识，可以用于识别是否为目标车辆；整车版本号中的1.0用于表示整车版本号的版本编号。车辆标识的组成和版本编号的位数可以根据实际需要进行调整。可以定义初始整车版本号为FAW.OS.1.0。当对目标车辆中所有域的电子控制单元都完成一次软件升级后，可以理解为对目标车辆的全部电子控制单元完成一次功能迭代后，整车版本号升级为FAW.OS.2.0。若对目标车辆中的部分电子控制单元完成一次升级后，可以理解为对目标车辆的部分电子控制单元完成一次问题修复，例如，将连接域ECU从V3.0升级为V3.1，这时整车版本号升级为FAW.OS.2.1。
S120、判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点。
整车版本节点可以为表示整车版本号的节点，整车版本节点与整车版本号存在唯一对应关系。也即一个整车版本号对应唯一的整车版本节点。在服务端中为不同的整车版本号建立唯一对应的整车版本节点，整车版本节点可以关联升级路径，升级路径表示整车版本号的升级顺序。整车版本节点还关联有与该整车版本节点唯一对应的待升级文件，待升级文件用于对目标车辆进行升级。
升级路径可以为用于指示车辆获取整车版本节点的后继节点的路径。升级 路径为有向路径，且为单向路径。后继节点可以为目标车辆上传的整车版本号对应的整车版本节点之后的节点。
在获取到目标车辆上传的整车版本号后，确定整车版本号对应的整车版本节点，判断整车版本节点是否关联有升级路径。若整车版本节点关联有升级路径，将升级路径对应的下一节点作为后继节点。
参见图2b所示的整车版本升级路径示意图。图2b中的1.0.0、1.0.1、1.1.0和2.0.0为整车版本号的版本编号。每一个整车版本号对应的整车版本节点关联有升级路径，通过升级路径可以获取该整车版本节点对应的后继节点。示例性的，整车版本号的版本编号为1.0.0的整车版本节点后关联有升级路径，升级路径对应的下一节点为版本编号为1.0.1的整车版本节点，将该节点作为整车版本号的版本编号为1.0.0的整车版本节点的后继节点。
可选的，测试车辆的整车版本号对应的整车版本节点关联的升级路径包括方向属性，方向属性包括正向属性和反向属性，且整车版本节点可以不关联正向属性的升级路径。
测试车辆的整车版本号对应的整车版本节点关联的升级路径具有正向属性和反向属性。对于测试车辆可以按照正向属性的升级路径进行升级，也可以按照反向属性的升级路径进行升级。每一个整车版本节点至多对应一条正向属性的升级路径和一条反向属性的升级路径。
参见图2c所示的测试车辆整车版本升级路径示意图。图2c中测试车辆整车版本号的版本编号为1.0.1、2.0.2和4.0.0的整车版本节点不关联正向属性的升级路径，也即，测试车辆的整体升级过程可以是不连续的。
通过测试车辆的整车版本节点关联的升级路径包括正向属性和反向属性，可以多次循环对同一测试车辆进行升级测试，节约升级测试的成本。
S130、响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
若存在关联有升级路径的后继节点，也即整车版本号对应的整车版本节点存在关联有升级路径的后继节点。目标节点可以为根据升级路径确定的整车版本节点的后继节点，目标节点可以用于为目标车辆提供待升级文件。待升级文件可以为对目标车辆中的至少一个电子控制单元进行升级的文件。示例性的，待升级文件包括车型、电子控制单元标识、电子控制单元名称和软件版本号等。将关联有升级路径的后继节点作为目标节点后，获取目标节点的待升级文件，并将待升级文件发送给目标车辆，以触发目标车辆自动升级相应的电子控制单 元。目标车辆根据待升级文件对相应电子控制单元进行升级。
可选的，若升级路径具有反向属性，则目标节点的待升级文件为反向待升级文件，反向待升级文件与待升级文件的内容有差别且无关联。也存在待升级文件可以做反向待升级文件和待升级文件的情况。
通过反向待升级文件可以为升级路径的属性为反向属性的整车版本节点关联的文件。目标车辆根据反向待升级文件实现对相应电子控制单元的升级。
本实施例的技术方案，通过获取目标车辆上传的整车版本号，获取车辆整体的整车版本信息。判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点，若存在关联有升级路径的后继节点，则将关联有升级路径的后继节点作为目标节点，通过升级路径判断，可以准确的确定目标节点。根据目标节点的待升级文件，对目标车辆进行升级，可以快速实现对目标车辆的整体升级，能够兼顾整车的兼容性，提高整车升级效率。因此通过本申请的技术方案，解决了单个电子控制单元的软件版本号随意变更，无法直观判断车辆整体功能的兼容性问题，导致整车的升级效率低的问题，达到了提高整车升级效率的效果。
实施例二
图3为本申请实施例二提供的一种远程升级方法的流程图。
在获取目标车辆上传的整车版本号之前，还包括：获取上传的待升级文件；根据上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点，以建立新的后继节点。
参见图3所示的一种远程升级方法，包括：
S210、获取上传的待升级文件。
服务端实时的检测是否有待升级文件上传到服务端，当检测到有待升级文件上传到服务端时，获取待升级文件。
电子控制单元的软件维护人员，会不定期的上传电子控制单元的软件的新版本，以克服已使用的电子控制单元的软件中的问题，或者根据新的使用需求对电子控制单元的软件进行功能升级。维护人员将电子控制单元的软件的新版本作为待升级文件上传到服务端，以使服务端获取待升级文件。
S220、根据上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点。
服务端获取到待升级文件后，建立已建立的最新整车版本节点的后继节点。在最新整车版本节点关联最新整车版本节点到新的后继节点的升级路径。通过 建立新的关联有升级路径的后继节点，为上传的待升级文件建立对应的整车版本节点。
在一个可选实施例中，根据上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点，包括：根据上传的待升级文件生成对应的升级整车版本号；在已建立的最新整车版本节点之后，添加新的关联有升级路径的后继节点；建立该新的后继节点与上传的待升级文件的升级整车版本号之间的关联关系。
升级整车版本号为根据待升级文件确定的升级后的整车版本号。示例性的，待升级文件中可以包括升级整车版本号，通过待升级文件读取升级整车版本号。示例性的，待升级文件中也可以不包括升级整车版本号，升级文件中包括待升级的电子控制单元的升级信息，服务端根据预设的整车版本命名规则，生成升级整车版本号。示例性的，预设的整车版本号命名规则可以是当待升级文件包括的电子控制单元的数量大于等于预设阈值时，将已建立的最新整车版本节点对应的整车版本号的第一位增加1，得到升级整车版本号；当待升级文件包括的电子控制单元的数量小于预设阈值时，将已建立的最新整车版本节点对应的整车版本号的第二位增加1，得到升级整车版本号。例如，待升级文件中包括发动机控制器和变速箱控制器2个电子控制单元，其中，发动机控制器的版本号为3.0，变速箱控制器的版本号为4.0，预设阈值为3，已建立的最新整车版本节点对应的整车版本号为FAW.OS.3.0，则升级整车版本号为FAW.OS.3.1。示例性的，预设的整车版本号命名规则还可以是当待升级文件包括预设的电子控制单元时，将已建立的最新整车版本节点对应的整车版本号的第一位增加1，得到升级整车版本号；当待升级文件不包括预设的电子控制单元时，将已建立的最新整车版本节点对应的整车版本号的第二位增加1，得到升级整车版本号。预设规则可以根据车辆的特性进行设定，本申请对此不做具体限定。
在服务端已建立的最新整车版本节点之后，添加新的后继节点，并建立已建立的最新整车版本节点与添加的新的后继节点的升级路径，升级路径的方向指向新的后继节点。建立该新的后继节点与上传的待升级文件的升级整车版本号之间的关联关系。示例性的，可以将上传的待升级文件的升级整车版本号作为新的后继节点的序号。示例性的，关联关系还可以包括上传的待升级文件的存储位置。
通过根据上传的待升级文件生成对应的升级整车版本号，为待升级文件生成对应的整车版本号。通过在已建立的最新整车版本节点之后，添加新的关联有升级路径的后继节点，为待升级文件建立对应的整车版本节点，建立该新的后继节点与上传的待升级文件的升级整车版本号之间的关联关系，可以通过新 的后继节点获取上传的待升级文件的升级整车版本号，确定新的后继节点对应的整车版本号。
S230、获取目标车辆上传的整车版本号。
S240、判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点。
S250、响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
在一个可选实施例中，相应的，根据目标节点的待升级文件，对目标车辆进行升级，包括：将目标节点的升级整车版本号对应的待升级文件，作为目标升级文件，并根据目标升级文件，对目标车辆进行升级。
目标升级文件为目标节点关联的待升级文件，用于指示目标车辆进行升级。在建立新的后继节点与上传的待升级文件的升级整车版本号之间的关联关系后，获取的目标车辆上传的整车版本号对应的整车版本节点，若该整车版本节点存在新的关联有升级路径的后继节点，则将该后继节点作为目标节点，目标升级文件为目标节点对应的升级整车版本号对应的待升级文件。将目标升级文件发送给目标车辆，可以指示目标车辆根据目标升级文件进行升级。
通过将目标节点的升级整车版本号对应的待升级文件，作为目标升级文件，可以及时地为目标车辆提供升级整车版本号对应的待升级文件，指示目标车辆根据目标升级文件及时进行升级，提高车辆升级的速度。
服务端实时监测是否有上传的待升级文件，若监测到上传的待升级文件则顺序执行S210和S220，也即S210和S220可以发生在S230、S240和S250中任意步骤的任意时刻。本实施例所采用的步骤仅为一个可选的顺序。
本实施例的技术方案，通过获取上传的待升级文件；根据上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点，顺序的为获取到的待升级文件建立新的关联有升级路径的后继节点，保障新的节点的连接关系的正确性，保证目标车辆升级的准确性。
在一个可选实施例中，远程升级方法，还包括，获取升级路径删除请求；其中升级路径删除请求中包括待删除后继节点的标识信息；根据待删除后继节点的标识信息，确定待删除升级路径；删除待删除升级路径。
升级路径删除请求可以为删除已经存在的升级路径的请求。在上传待升级文件后，如果发现待升级文件中的软件升级信息存在漏洞时，可以删除存在漏洞的待升级文件对应的整车版本节点对应的升级路径，避免还未获取存在漏洞 的待升级文件的目标车辆，根据存在漏洞的待升级文件进行升级，避免车辆的整车升级由于待升级文件自身存在的漏洞而出现故障。待删除后继节点可以是待删除升级路径指向的节点。待删除后继节点的标识信息可以为待删除后继节点关联的整车版本号。根据待删除后继节点的标识信息，将指向该待删除后继节点的升级路径确定为待删除升级路径，删除待删除升级路径。
根据升级路径删除请求，删除待删除升级路径后，待删除后继节点仍然存在用于与新的后继节点建立连接的新的升级路径，以指示已经根据待删除升级路径完成升级的车辆，根据新的升级路径升级到新的后继节点对应的整车版本。
通过获取升级路径删除请求；其中升级路径删除请求中包括待删除后继节点的标识信息，根据待删除后继节点的标识信息，确定待删除升级路径，可以快速根据待删除后继节点的标识信息确定待删除升级路径。删除待删除升级路径可以避免目标车辆根据待删除升级路径进行整车升级。
实施例三
图4为本申请实施例三提供的一种远程升级方法的流程图方法的流程图。
可选的，本实施例中，根据目标节点的待升级文件，对目标车辆进行升级，包括：查询目标节点是否包含用户配置信息；根据查询结果和目标节点的待升级文件，生成目标升级文件；将目标升级文件下发至目标车辆，用于指示目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级，并更新目标车辆的整车版本号，以对目标车辆进行个性化升级。
参见图4所示的一种远程升级方法，包括：
S310、获取目标车辆上传的整车版本号。
S320、判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点。
S330、响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点。
S340、查询目标节点是否包含用户配置信息。
用户配置信息可以为需要用户进行配置的信息。当目标节点对应的待升级文件中包括用户配置信息时，在目标节点设置用户配置信息对应的用户配置信息标识，以快速查询到目标节点是否包括用户配置信息。
参见图5所示的一种目标节点用户配置信息示意图。在节点2.0.0上配置有3个用户配置信息标识PZ_00、PZ_01和PZ_02。当目标节点为节点2.0.0时，可以根据用户配置信息标识PZ_00、PZ_01和PZ_02快速查询到对应的用户配 置信息。
S350、根据查询结果和目标节点的待升级文件，生成目标升级文件。
查询结果可以是目标节点包含用户配置信息或者目标节点不包含用户配置信息。若查询结果是目标节点包含用户配置信息，将用户配置信息与目标节点的待升级文件进行组合，生成目标升级文件。若查询结果是目标节点不包含用户配置信息，则根据目标节点的待升级文件，生成目标升级文件。
在一个可选实施例中，根据查询结果和目标节点的待升级文件，生成目标升级文件，包括：若目标节点不包含用户配置信息，则将目标节点的待升级文件作为目标升级文件。
若目标节点不包含用户配置信息，表示不需要用户进行配置，则直接将目标节点的待升级文件作为目标升级文件。
通过若目标节点不包含用户配置信息，则将目标节点的待升级文件作为目标升级文件，可以快速生成目标升级文件，提高目标车辆的升级效率。
在一个可选实施例中，根据查询结果和目标节点的待升级文件，生成目标升级文件，包括：若目标节点包含用户配置信息，则向目标车辆发送用户配置信息的配置询问信息，并获取目标车辆反馈的用户配置信息的目标配置项；根据目标节点的待升级文件和目标配置项生成目标升级文件。
若目标节点包含用户配置信息，表示需要用户进行配置。向目标车辆发送用户配置信息的配置询问信息。用户可以对配置询问信息中的用户配置信息进行个性化配置。用户完成用户配置信息的配置后，确认用户配置信息并上传目标配置项到服务端。目标配置项可以是用户根据用户配置信息选择的配置选项。获取目标车辆反馈的用户配置信息的目标配置项，将目标节点的待升级文件和目标配置项，根据文件生成规则生成目标升级文件。
若目标节点包含用户配置信息，则向目标车辆发送用户配置信息的配置询问信息，并获取目标车辆反馈的用户配置信息的目标配置项，可以获取用户的个性化配置信息，根据目标节点的待升级文件和目标配置项生成目标升级文件，可以使得目标升级文件满足用户的个性化需求，提高用户体验。
S360、将目标升级文件下发至目标车辆，用于指示目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级，并更新目标车辆的整车版本号。
将目标升级文件下发至目标车辆，可以指示目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级。在目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级后，根据目标升级文件中包括的整车版本号更新目标车辆的整车版本号。
本实施例的技术方案，通过查询目标节点是否包含用户配置信息，丰富目标升级文件的内容，当目标节点存在用户配置信息时，用户根据自身的需求，设定用户配置信息。根据查询结果和目标节点的待升级文件，生成目标升级文件，可以实现目标升级文件的个性化定制。根据将目标升级文件下发至目标车辆，用于指示目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级，实现目标车辆的个性化升级。更新目标车辆的整车版本号，保障目标车辆整车版本号的实时性。
实施例四
图6所示为本申请实施例四提供的一种远程升级装置的结构示意图，本实施例可适用于远程触发车辆中软件升级的情况，远程升级装置配置于服务端，该远程升级装置的结构包括：整车版本号获取模块410，设置为获取目标车辆上传的整车版本号；后继节点判断模块420，设置为判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；目标车辆升级模块430，设置为响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
本实施例的技术方案，通过获取目标车辆上传的整车版本号，获取车辆整体的整车版本信息。判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点，若存在关联有升级路径的后继节点，则将关联有升级路径的后继节点作为目标节点，通过升级路径判断，可以准确的确定目标节点。根据目标节点的待升级文件，对目标车辆进行升级。可以快速实现对目标车辆的整体升级，能够兼顾整车的兼容性，提高整车升级效率。因此通过本申请的技术方案，解决了单个电子控制单元的软件版本号随意变更，无法直观判断车辆整体功能的兼容性问题，导致整车的升级效率低的问题，达到了提高整车升级效率的效果。
可选的，远程升级装置，还包括：待升级文件获取模块，设置为获取上传的待升级文件；后继节点建立模块，设置为根据上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点。
可选的，后继节点建立模块，包括：升级整车版本号生成单元，设置为根据上传的待升级文件生成对应的升级整车版本号；后继节点添加单元，设置为在已建立的最新整车版本节点之后，添加新的关联有升级路径的后继节点；关联关系建立单元，设置为建立所述新的后继节点与上传的待升级文件的升级整车版本号之间的关联关系。目标车辆升级模块430，包括：目标升级文件确定单元，设置为将目标节点的升级整车版本号对应的待升级文件，作为目标升级文件，并根据目标升级文件，对目标车辆进行升级。
可选的，远程升级装置，还包括：删除请求获取模块，设置为获取升级路径删除请求；其中，升级路径删除请求中包括待删除后继节点的标识信息；路径确定模块，设置为根据待删除后继节点的标识信息，确定待删除升级路径；路径删除模块，设置为删除待删除升级路径。
可选的，目标车辆升级模块430，还包括：用户配置信息查询单元，设置为查询目标节点是否包含用户配置信息；目标升级文件生成单元，设置为根据查询结果和目标节点的待升级文件，生成目标升级文件；目标升级文件下发单元，设置为将目标升级文件下发至目标车辆，用于指示目标车辆根据目标升级文件，对目标车辆中的电子控制单元进行升级，并更新目标车辆的整车版本号。
可选的，目标升级文件生成单元，包括：目标升级文件生成子单元，设置为若目标节点不包含用户配置信息，则将目标节点的待升级文件作为目标升级文件。
可选的，目标升级文件生成单元，还包括：目标配置项获取子单元，设置为若目标节点包含用户配置信息，则向目标车辆发送用户配置信息的配置询问信息，并获取目标车辆反馈的用户配置信息的目标配置项；目标升级文件组合子单元，设置为根据目标节点的待升级文件和目标配置项生成目标升级文件。
本申请实施例所提供的远程升级装置可执行本申请任意实施例所提供的远程升级方法，具备执行远程升级方法相应的功能模块和效果。
实施例五
图7为本申请实施例五提供的一种电子设备的结构示意图，如图7所示，该电子设备包括处理器510、存储器520、输入装置530和输出装置540；电子设备中处理器510的数量可以是一个或多个，图7中以一个处理器510为例；电子设备中的处理器510、存储器520、输入装置530和输出装置540可以通过总线或其他方式连接，图7中以通过总线连接为例。
存储器520作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请实施例中的远程升级方法对应的程序指令/模块(例如，整车版本号获取模块410、后继节点判断模块420和目标车辆升级模块430)。处理器510通过运行存储在存储器520中的软件程序、指令以及模块，从而执行电子设备的多功能应用以及数据处理，即实现上述的远程升级方法。
存储器520可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器520可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失 性固态存储器件。在一些实例中，存储器520可包括相对于处理器510远程设置的存储器，这些远程存储器可以通过网络连接至电子设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及互联网、企业内部网、局域网、移动通信网之间的组合。
输入装置530可设置为接收输入的字符信息，以及产生与电子设备的用户设置以及功能控制有关的键信号输入。输出装置540可包括显示屏等显示设备。
实施例六
本申请实施例六还提供一种包含计算机可执行指令的存储介质，计算机可执行指令在由计算机处理器执行时用于执行一种远程升级方法，该方法包括：获取目标车辆上传的整车版本号；判断整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据目标节点的待升级文件，对目标车辆进行升级。
当然，本申请实施例所提供的一种包含计算机可执行指令的存储介质，计算机可执行指令不限于如上所述的方法操作，还可以执行本申请任意实施例所提供的远程升级方法中的相关操作。
通过以上关于实施方式的描述，所属领域的技术人员可以清楚地了解到，本申请可借助软件及必需的通用硬件来实现，当然也可以通过硬件实现。本申请的技术方案可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、闪存(FLASH)、硬盘或光盘等，计算机可读存储介质中包括多个指令用以使得一台电子设备(可以是个人计算机，服务器，或者网络设备等)执行本申请多个实施例所述的方法。
值得注意的是，上述装置的实施例中，所包括的多个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，每个功能单元的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。

Claims (11)

  1. 一种远程升级方法，包括：
    获取目标车辆上传的整车版本号；
    判断所述整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；
    响应于存在关联有升级路径的后继节点的判断结果，将所述关联有升级路径的后继节点作为目标节点，并根据所述目标节点的待升级文件，对所述目标车辆进行升级。
  2. 根据权利要求1所述的方法，还包括：
    获取上传的待升级文件；
    根据所述上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点。
  3. 根据权利要求2所述的方法，还包括：
    获取升级路径删除请求；其中，所述升级路径删除请求中包括待删除后继节点的标识信息；
    根据所述待删除后继节点的标识信息，确定待删除升级路径；
    删除所述待删除升级路径。
  4. 根据权利要求2所述的方法，其中，所述根据所述上传的待升级文件，在已建立的最新整车版本节点之后，建立新的关联有升级路径的后继节点，包括：
    根据所述上传的待升级文件生成对应的升级整车版本号；
    在所述已建立的最新整车版本节点之后，添加新的关联有升级路径的后继节点；
    建立所述新的后继节点与所述上传的待升级文件的升级整车版本号之间的关联关系。
  5. 根据权利要求4所述的方法，其中，所述根据所述目标节点的待升级文件，对所述目标车辆进行升级，包括：
    将所述目标节点的升级整车版本号对应的待升级文件，作为目标升级文件，并根据所述目标升级文件，对所述目标车辆进行升级。
  6. 根据权利要求1所述的方法，其中，所述根据所述目标节点的待升级文件，对所述目标车辆进行升级，包括：
    查询所述目标节点是否包含用户配置信息；
    根据查询结果和所述目标节点的待升级文件，生成目标升级文件；
    将所述目标升级文件下发至所述目标车辆，用于指示所述目标车辆根据所述目标升级文件，对所述目标车辆中的电子控制单元进行升级，并更新所述目标车辆的整车版本号。
  7. 根据权利要求6所述的方法，其中，所述根据查询结果和所述目标节点的待升级文件，生成目标升级文件，包括：
    在所述目标节点不包含所述用户配置信息的情况下，将所述目标节点的待升级文件作为目标升级文件。
  8. 根据权利要求6所述的方法，其中，所述根据查询结果和所述目标节点的待升级文件，生成目标升级文件，包括：
    在所述目标节点包含所述用户配置信息的情况下，向所述目标车辆发送所述用户配置信息的配置询问信息，并获取所述目标车辆反馈的所述用户配置信息的目标配置项；
    根据所述目标节点的待升级文件和所述目标配置项生成目标升级文件。
  9. 一种远程升级装置，包括：
    整车版本号获取模块，设置为获取目标车辆上传的整车版本号；
    后继节点判断模块，设置为判断所述整车版本号对应的整车版本节点是否存在关联有升级路径的后继节点；
    目标车辆升级模块，设置为响应于存在关联有升级路径的后继节点的判断结果，将关联有升级路径的后继节点作为目标节点，并根据所述目标节点的待升级文件，对所述目标车辆进行升级。
  10. 一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如权利要求1-8任一所述的远程升级方法。
  11. 一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时实现如权利要求1-8任一项所述的远程升级方法。
PCT/CN2023/109990 2022-09-09 2023-07-28 远程升级方法、装置、电子设备和存储介质 WO2024051385A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211104068.5A CN115328520A (zh) 2022-09-09 2022-09-09 远程升级方法、装置、电子设备和存储介质
CN202211104068.5 2022-09-09

Publications (1)

Publication Number Publication Date
WO2024051385A1 true WO2024051385A1 (zh) 2024-03-14

Family

ID=83929407

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/109990 WO2024051385A1 (zh) 2022-09-09 2023-07-28 远程升级方法、装置、电子设备和存储介质

Country Status (2)

Country Link
CN (1) CN115328520A (zh)
WO (1) WO2024051385A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115328520A (zh) * 2022-09-09 2022-11-11 中国第一汽车股份有限公司 远程升级方法、装置、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150082294A1 (en) * 2012-05-28 2015-03-19 Huawei Device Co., Ltd. Method and Apparatus for Generating Firmware Over the Air Upgrade Package
CN110377306A (zh) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 用于车载设备升级包的管理方法及装置、介质、服务器
CN114398060A (zh) * 2022-01-12 2022-04-26 中国第一汽车股份有限公司 车载控制器软件升级方法、装置、电子设备及存储介质
CN114675855A (zh) * 2021-12-16 2022-06-28 北京新能源汽车股份有限公司 整车软件远程升级方法、装置及平台设备
CN115328520A (zh) * 2022-09-09 2022-11-11 中国第一汽车股份有限公司 远程升级方法、装置、电子设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150082294A1 (en) * 2012-05-28 2015-03-19 Huawei Device Co., Ltd. Method and Apparatus for Generating Firmware Over the Air Upgrade Package
CN110377306A (zh) * 2019-07-18 2019-10-25 上海擎感智能科技有限公司 用于车载设备升级包的管理方法及装置、介质、服务器
CN114675855A (zh) * 2021-12-16 2022-06-28 北京新能源汽车股份有限公司 整车软件远程升级方法、装置及平台设备
CN114398060A (zh) * 2022-01-12 2022-04-26 中国第一汽车股份有限公司 车载控制器软件升级方法、装置、电子设备及存储介质
CN115328520A (zh) * 2022-09-09 2022-11-11 中国第一汽车股份有限公司 远程升级方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN115328520A (zh) 2022-11-11

Similar Documents

Publication Publication Date Title
WO2021012568A1 (zh) 一种数据处理方法及相关设备
JP5096680B2 (ja) ファームウェアコンポーネントのステータスの発行およびファームウェアコンポーネントのアップデート
WO2024051385A1 (zh) 远程升级方法、装置、电子设备和存储介质
WO2017049550A1 (zh) 适配器和适配器升级的方法
CN104699511B (zh) 插件升级方法及装置
CN109729183A (zh) 请求处理方法、装置、设备及存储介质
WO2018033094A1 (zh) 富通信套件发布平台、版本更新方法及系统、移动终端
WO2021142822A1 (zh) 一种车辆诊断方法及一种车辆诊断设备和存储介质
CN111045893B (zh) 监控任务的执行方法、装置及系统、存储介质、电子装置
CN115525302B (zh) 一种大规模数字对象仓库集群的部署方法及装置
WO2013097481A1 (zh) 一种文件类型识别方法及系统
CN103176811A (zh) 第三方应用安装方法和系统
CN102929661A (zh) 一种功能组件的处理方法、装置及服务器
CN114422436A (zh) 网关、网关控制方法、装置、电子设备和存储介质
CN113542022A (zh) 组网系统的组网管理方法、装置、终端设备及存储介质
CN104717280B (zh) 数据同步的标记方法和装置
CN103795739A (zh) 一种应用推广方法、装置及系统
CN104104701A (zh) 在线服务的配置更新的方法和系统
CN102902579A (zh) 一种功能组件的处理系统
CN111008023B (zh) 一种实例部署方法及系统
CN112968793A (zh) 基于物联网的设备升级方法、装置、设备及存储介质
CN109144520B (zh) Android中不同对象间的信息交互方法、装置、设备和存储介质
CN109815202B (zh) 日志编辑方法及相关装置
CN111338758A (zh) 资源管理方法、装置和电子设备
CN110557656A (zh) 个性化内容分发方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23862086

Country of ref document: EP

Kind code of ref document: A1