Vehicle software upgrading method and device and computer equipment

Abstract

The invention relates to a vehicle software upgrading method and device, computer equipment and a storage medium. Belongs to the technical field of vehicle software updating. The method comprises the following steps: receiving a future version data packet for to-be-upgraded software sent by a user terminal; wherein the future version data packet comprises a data packet name; the data packet name comprises a software name, a software version and a to-be-detected field. And according to the software name, the software version and the to-be-detected field, carrying out legality verification on the future version data packet. And under the condition that the future version data packet passes verification, performing software upgrading on the to-be-upgraded software based on the future version data packet. According to the invention, the problems that the upgrading efficiency is low and the upgrading process is tedious due to the fact that the vehicle needs to be driven to an offline service store and the offline service store carries out upgrading through a diagnostic instrument in the prior art are effectively solved. The software upgrading efficiency is effectively improved, and the software upgrading cost is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of vehicle software updating, and in particular to a vehicle software upgrading method, device and computer equipment. Background Art

[0002] As software iterations in the automotive industry become more frequent, the demand for software upgrades is increasing. Currently, the main way to upgrade automotive software is by diagnostic instrument upgrades. Users are required to drive their vehicles to offline service stores, where relevant staff at offline service stores will use diagnostic instruments to upgrade the vehicle software.

[0003] Using a diagnostic instrument to upgrade not only requires connecting to the OBD (On-Board Diagnostics) line, which makes the upgrade process complicated, but also requires driving to an offline service store for the upgrade, which has high labor costs and low upgrade efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide a vehicle software upgrade method, device and computer equipment that can effectively improve the efficiency of vehicle software upgrades in response to the above technical problems.

[0005] In a first aspect, the present application provides a vehicle software upgrade method. The method comprises:

[0006] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0007] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0008] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0009] In one embodiment, the legitimacy of the future version data packet is verified based on the software name, software version and the field to be detected, including:

[0010] Generate a verification data acquisition request based on the software name and software version;

[0011] Sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request;

[0012] Based on the verification package and the fields to be detected, the legitimacy of future version data packets is verified.

[0013] In one embodiment, the authentication packet includes a decryption key and authentication data;

[0014] Accordingly, based on the verification package and the fields to be detected, the legitimacy of the future version data packet is verified, including:

[0015] Decrypt the field to be detected based on the decryption key to obtain decrypted data;

[0016] The legitimacy verification result of the future version data packet is determined according to the matching result between the decrypted data and the verification data.

[0017] In one embodiment, after performing software upgrade on the software to be upgraded based on the future version data package, the method further includes:

[0018] In the case that the upgrade of the software to be upgraded fails, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded;

[0019] When the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0020] In one embodiment, the method further comprises:

[0021] When the user terminal is connected to the vehicle routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data package is downloaded and sent to the vehicle terminal through the vehicle routing device.

[0022] In one embodiment, the method further comprises:

[0023] When the user terminal agrees to the software upgrade, a response message of agreeing to the upgrade is sent to the vehicle terminal;

[0024] When the upgrade consent response message is received, the vehicle-mounted routing device is controlled to enter the OTA ROTA mode, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

[0025] In a second aspect, the present application also provides a vehicle software upgrade device. The device comprises:

[0026] A receiving module, configured to receive a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0027] The verification module is used to verify the legitimacy of future version data packets based on the software name, software version and fields to be detected;

[0028] The upgrade module is used to upgrade the software to be upgraded based on the future version data package when the future version data package is verified to be successful.

[0029] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0030] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0031] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0032] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0033] In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0034] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0035] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0036] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0037] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0038] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0039] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0040] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0041] The above-mentioned vehicle software upgrade method, device and computer equipment receive a future version data packet for the software to be upgraded sent by the user terminal; wherein the future version data packet includes a data packet name; the data packet name includes the software name, software version and the field to be detected. According to the software name, software version and the field to be detected, the future version data packet is verified for legitimacy. In the case where the future version data packet is verified, the software to be upgraded is upgraded based on the future version data packet. In this application, the future version data packet can be sent based on the user terminal, and the vehicle-mounted terminal can verify the legitimacy of the future version data packet based on the software name, software version and the field to be detected. In the case where the future version data packet is verified, the software to be upgraded is automatically upgraded based on the future version data packet, which effectively solves the existing need to drive the vehicle to an offline service store, and the offline service store upgrades it through a diagnostic instrument, which not only has low upgrade efficiency, but also cumbersome upgrade process. This application effectively improves the efficiency of software upgrades and reduces the cost of software upgrades. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 An application environment diagram of the vehicle software upgrade method provided in this embodiment;

[0043] Figure 2 A schematic diagram of a flow chart of a first vehicle software upgrade method provided in this embodiment;

[0044] Figure 3 A schematic diagram of a process for verifying the legitimacy of a future version data packet provided in this embodiment;

[0045] Figure 4 A schematic diagram of a flow chart of a second vehicle software upgrade method provided in this embodiment;

[0046] Figure 5 A schematic diagram of a flow chart of a third vehicle software upgrade method provided in this embodiment;

[0047] Figure 6 A structural block diagram of a vehicle software upgrade device provided in this embodiment;

[0048] Figure 7 This is a diagram of the internal structure of the computer device provided in this embodiment. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0050] The vehicle software upgrade method provided in the embodiment of the present application can be executed by the vehicle, specifically by a vehicle-mounted terminal configured on the vehicle or a controller on the vehicle. That is, the method can be applied to Figure 1 In the application environment shown. Taking the application in the vehicle terminal as an example, the vehicle terminal 104 receives the future version data packet for the software to be upgraded sent by the user terminal 102; wherein the future version data packet includes a data packet name; the data packet name includes the software name, software version and the field to be detected. The vehicle terminal 102 verifies the legitimacy of the future version data packet according to the software name, software version and the field to be detected. If the future version data packet is verified, the vehicle terminal 102 performs a software upgrade on the software to be upgraded based on the future version data packet.

[0051] The user terminal 2 refers to the user's terminal device, which can be a mobile phone, computer or other terminal device.

[0052] The vehicle terminal 104 refers to an electronic device on the target vehicle for collecting vehicle data, executing vehicle control instructions, communicating with the outside, and providing driving assistance information. The vehicle terminal 102 of the present application also integrates the function of the vehicle software upgrade method of the present application. The vehicle terminal of the present application can be a vehicle VDC (vehicle dynamic control, vehicle dynamic control system).

[0053] In one embodiment, if Figure 2 As shown, a vehicle software upgrade method is provided, which is applied to Figure 1 The vehicle terminal in the example is used to illustrate. Figure 2 As shown, the following steps are included:

[0054] S201, receiving a future version data packet for software to be upgraded sent by a user terminal.

[0055] Among them, the future version data packet includes a data packet name; the data packet name includes the software name, software version and the field to be detected. The user terminal sets the user's terminal device, which can be a mobile phone, computer and other terminal devices. The software to be upgraded refers to the application program that needs to be upgraded. The future version data packet refers to the software upgrade data packet that needs to be downloaded when the software to be upgraded is upgraded. For example, if the software to be upgraded is currently version 2.0 and needs to be upgraded to version 3.0, the data packet that upgrades the software to be upgraded from version 2.0 to version 3.0 is the future version data packet.

[0056] Optionally, in this embodiment, when the user terminal is connected to the vehicle-mounted routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data packet is downloaded, and the future version data packet is sent to the vehicle-mounted terminal through the vehicle-mounted routing device. Specifically, the vehicle-mounted routing device can transmit a WIFI signal, and the user terminal can access the vehicle-mounted routing device through the WIFI signal. The vehicle-mounted routing device is connected to the vehicle-mounted terminal. The vehicle-mounted routing device can be a vehicle CSC. The user terminal communicates with the vehicle-mounted routing device through the WIFI signal, and the vehicle-mounted routing device is connected to the vehicle-mounted terminal through Ethernet.

[0057] Optionally, in this embodiment, when the user terminal agrees to the software upgrade, an upgrade consent response message is sent to the vehicle terminal. When the upgrade consent response message is received, the vehicle routing device is controlled to enter the OTA ROTA mode, so that the vehicle routing device sends the future version data packet to the vehicle device in the OTA ROTA mode. When the vehicle routing device is in the OTA ROTA mode, the user terminal can interact with the vehicle terminal through the client application, and send the future version data packet to the vehicle terminal in the form of transparent transmission.

[0058] S202, verify the legitimacy of the future version data packet according to the software name, software version and the field to be detected.

[0059] The software name refers to the software name of the software to be upgraded, the software version refers to the upgraded version of the software to be upgraded corresponding to the future version data package, and the field to be tested refers to the field available for verification.

[0060] As an optional implementation of the embodiment of the present application, the software name and software version are first verified, and if the verification is passed, the field to be detected is then verified based on the locally stored verification field, thereby realizing the legitimacy verification of the future version data packet.

[0061] S203: When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0062] Optionally, when the future version data packet is verified, the vehicle terminal parses the future version data packet based on the future version data packet, obtains the upgrade file, and performs software upgrade on the software to be upgraded based on the upgrade file. The specific upgrade method can be implemented using existing technologies and will not be described in detail here.

[0063] The above-mentioned vehicle software upgrade method receives a future version data packet for the software to be upgraded sent by the user terminal; wherein the future version data packet includes a data packet name; the data packet name includes the software name, software version and the field to be detected. According to the software name, software version and the field to be detected, the future version data packet is verified for legitimacy. In the case where the future version data packet is verified, the software to be upgraded is upgraded based on the future version data packet. In the present application, the future version data packet can be sent based on the user terminal, and the vehicle-mounted terminal can verify the legitimacy of the future version data packet based on the software name, software version and the field to be detected. In the case where the future version data packet is verified, the software to be upgraded is automatically upgraded based on the future version data packet, which effectively solves the existing need to drive the vehicle to an offline service store, and the offline service store upgrades it through a diagnostic instrument, which not only has low upgrade efficiency, but also cumbersome upgrade process. The present application effectively improves the efficiency of software upgrades and reduces the cost of software upgrades.

[0064] In one embodiment, in order to more accurately verify the legitimacy of future version data packets, such as Figure 3 As shown, an optional implementation of S202 includes:

[0065] S301, generating a verification data acquisition request according to the software name and software version.

[0066] The verification data acquisition request refers to a request message for acquiring verification data.

[0067] Optionally, in this embodiment, in the request message template, an identifier corresponding to the software name and software version is added, and the template with the added identifier is used as a verification data acquisition request.

[0068] S302, sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request.

[0069] The Internet of Vehicles platform refers to a comprehensive system that integrates multiple technologies and services to connect vehicles, drivers, pedestrians and traffic infrastructure. It uses the Internet and wireless communication technologies to achieve information exchange and communication between vehicles (V2V), vehicles and infrastructure (V2I), vehicles and pedestrians (V2P) and vehicles and networks (V2N). Verification packages refer to data packages used to verify future versions of data packages.

[0070] Optionally, in this embodiment, the Internet of Vehicles platform obtains a verification package corresponding to the software name and software version from a database based on the software name and software version.

[0071] S303, determining the legitimacy verification result of the future version data packet according to the matching result of the decrypted data and the verification data.

[0072] Optionally, in this embodiment, the verification package includes a decryption key and verification data.

[0073] Optionally, in this embodiment, the field to be detected is decrypted based on the decryption key to obtain decrypted data. Based on the matching result of the decrypted data and the verification data, the future version data packet is verified for legitimacy. Specifically, if the decrypted data matches the verification data successfully, the verification result of the legitimacy verification of the future version data packet is passed. If the decrypted data does not match the verification data successfully, the verification result of the legitimacy verification of the future version data packet is failed.

[0074] In this embodiment, a verification data acquisition request is generated according to the software name and software version. The verification data acquisition request is sent to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request. Based on the verification package and the field to be detected, the legitimacy of the future version data packet is verified. Based on this embodiment, the validity of the future version data packet can be verified more accurately, and whether the future version data packet has been maliciously tampered with or destroyed can be effectively verified.

[0075] In one embodiment, if Figure 4 As shown, after the software to be upgraded is upgraded based on the future version data package, an optional implementation of a vehicle software upgrade method includes:

[0076] S401, when the software to be upgraded fails to be upgraded, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded.

[0077] The current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded. The current version of the software to be upgraded refers to the software version before the software to be upgraded is upgraded based on the future version data packet. That is, the software version of the software to be upgraded at the current moment.

[0078] Optionally, in this embodiment, when the upgrade of the software to be upgraded fails, the current version data package is obtained from the historical file, and the software to be upgraded is restored based on the current version data package to obtain the current version of the software to be upgraded.

[0079] S402, when the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0080] Optionally, in this embodiment, when the software to be upgraded is successfully upgraded, the current version data package is deleted from the history file, and the future version data package is saved in the history file.

[0081] In this embodiment, in the case that the software to be upgraded fails to be upgraded, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded. In the case that the software to be upgraded is successfully upgraded, the current version data packet is deleted and the future version data packet is saved. In this embodiment, in the case that the software to be upgraded fails to be upgraded based on the future version data packet, the software to be upgraded can also be restored based on the current version data packet of the current version, which effectively avoids the situation that the software to be upgraded is unavailable when the software to be upgraded fails to be upgraded.

[0082] In one embodiment, if Figure 5 As shown, an optional implementation of the vehicle software upgrade method is:

[0083] S501, when the user terminal is connected to the vehicle-mounted routing device, a software upgrade request is sent to the user terminal.

[0084] S502: When the user terminal agrees to the software upgrade, an upgrade agreement response message is sent to the vehicle terminal.

[0085] S503: When receiving the upgrade consent response message, control the vehicle-mounted routing device to enter the OTA ROTA mode, so that the vehicle-mounted routing device is in the OTA ROTA mode.

[0086] S504, receiving a future version data packet for the software to be upgraded sent by the user terminal through the vehicle-mounted routing device, wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version and a field to be detected.

[0087] S505: Generate a verification data acquisition request according to the software name and software version.

[0088] S506, sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request, wherein the verification package includes a decryption key and verification data.

[0089] S507, decrypt the field to be detected based on the decryption key to obtain decrypted data.

[0090] S508, based on the matching result of the decrypted data and the verification data, the legitimacy of the future version data packet is verified.

[0091] S509: When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0092] S510, when the software to be upgraded fails to be upgraded, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded. The current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded.

[0093] S511, when the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0094] In this embodiment, a future version data packet for the software to be upgraded is received from a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected. The future version data packet is verified for legitimacy based on the software name, software version, and field to be detected. If the future version data packet is verified to be successful, the software to be upgraded is upgraded based on the future version data packet. In this application, a future version data packet can be sent based on a user terminal, and the vehicle-mounted terminal can verify the legitimacy of the future version data packet based on the software name, software version, and field to be detected. If the future version data packet is verified to be successful, the software to be upgraded is automatically upgraded based on the future version data packet, which effectively solves the existing problem of driving the vehicle to an offline service store, which is upgraded by the offline service store through a diagnostic instrument, which not only has low upgrade efficiency, but also cumbersome upgrade process. This application effectively improves the efficiency of software upgrades and reduces the cost of software upgrades.

[0095] Based on the same inventive concept, the embodiment of the present application also provides a vehicle software upgrade device for implementing the vehicle software upgrade method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiment of a vehicle software upgrade device provided below can refer to the limitations of the vehicle software upgrade method above, and will not be repeated here.

[0096] In one embodiment, if Figure 6 As shown, a vehicle software upgrade device 1 is provided, comprising:

[0097] The receiving module 10 is used to receive a future version data packet for the software to be upgraded sent by the user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version and a field to be detected;

[0098] Verification module 20, used to verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0099] The upgrade module 30 is used to upgrade the software to be upgraded based on the future version data package when the future version data package is verified to be successful.

[0100] In one embodiment, the Figure 6 The verification module 20 is further specifically used for:

[0101] Generate a verification data acquisition request based on the software name and software version;

[0102] Sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request;

[0103] Based on the verification package and the fields to be detected, the legitimacy of future version data packets is verified.

[0104] In one embodiment, the Figure 6 The verification module 20 is further specifically used to: verify that the package includes a decryption key and verification data;

[0105] Accordingly, based on the verification package and the fields to be detected, the legitimacy of the future version data packet is verified, including:

[0106] Decrypt the field to be detected based on the decryption key to obtain decrypted data;

[0107] According to the matching result of the decrypted data and the verification data, the legitimacy verification result of the future version of the data packet is determined.

[0108] In one embodiment, the Figure 6 The vehicle software upgrade device further comprises:

[0109] A restoration module is used to restore the software to be upgraded based on the current version data packet to obtain the current version of the software to be upgraded when the upgrade of the software to be upgraded fails; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded;

[0110] The deletion module is used to delete the current version data package and save the future version data package when the software to be upgraded is successfully upgraded.

[0111] In one embodiment, the Figure 6 The vehicle software upgrade device further comprises:

[0112] The first sending module is used to send a software upgrade request to the user terminal when the user terminal is connected to the vehicle routing device, so that when the user terminal agrees to the software upgrade, the future version data packet is downloaded and sent to the vehicle terminal through the vehicle routing device.

[0113] In one embodiment, the Figure 6 The vehicle software upgrade device further comprises:

[0114] The second sending module is used to send an upgrade consent response message to the vehicle terminal when the user terminal agrees to the software upgrade;

[0115] The control module is used to control the vehicle-mounted routing device to enter the OTA ROTA mode when receiving the upgrade consent response message, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

[0116] Each module in the above vehicle software upgrade device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0117] In one embodiment, a computer device is provided, whose internal structure diagram can be as follows: Figure 7As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a vehicle software upgrade method is realized. The display unit of the computer device is used to form a visually visible picture, which can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0118] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0119] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0120] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0121] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0122] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0123] In one embodiment, when the processor executes the computer program, the following steps are further implemented: according to the software name, software version and the field to be detected, the legitimacy of the future version data packet is verified, including:

[0124] Generate a verification data acquisition request based on the software name and software version;

[0125] Sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request;

[0126] Based on the verification package and the fields to be detected, the legitimacy of future version data packets is verified.

[0127] In one embodiment, when the processor executes the computer program, the following steps are further implemented: the verification package includes a decryption key and verification data;

[0128] Accordingly, based on the verification package and the fields to be detected, the legitimacy of the future version data packet is verified, including:

[0129] Decrypt the field to be detected based on the decryption key to obtain decrypted data;

[0130] According to the matching result of the decrypted data and the verification data, the legitimacy verification result of the future version of the data packet is determined.

[0131] In one embodiment, when the processor executes the computer program, the following steps are further implemented: after performing a software upgrade on the software to be upgraded based on the future version data package, the method further includes:

[0132] In the case that the upgrade of the software to be upgraded fails, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded;

[0133] When the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0134] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0135] When the user terminal is connected to the vehicle routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data package is downloaded and sent to the vehicle terminal through the vehicle routing device.

[0136] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0137] When the user terminal agrees to the software upgrade, a response message of agreeing to the upgrade is sent to the vehicle terminal;

[0138] When the upgrade consent response message is received, the vehicle-mounted routing device is controlled to enter the OTA ROTA mode, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

[0139] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0140] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0141] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0142] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0143] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: according to the software name, software version and the field to be detected, the legitimacy of the future version data packet is verified, including:

[0144] Generate a verification data acquisition request based on the software name and software version;

[0145] Sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request;

[0146] Based on the verification package and the fields to be detected, the legitimacy of future version data packets is verified.

[0147] In one embodiment, the computer program, when executed by a processor, further implements the following steps: the verification package includes a decryption key and verification data;

[0148] Accordingly, based on the verification package and the fields to be detected, the legitimacy of the future version data packet is verified, including:

[0149] Decrypt the field to be detected based on the decryption key to obtain decrypted data;

[0150] According to the matching result of the decrypted data and the verification data, the legitimacy verification result of the future version of the data packet is determined.

[0151] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: after performing a software upgrade on the software to be upgraded based on the future version data package, the method further includes:

[0152] In the case that the upgrade of the software to be upgraded fails, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded;

[0153] When the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0154] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0155] When the user terminal is connected to the vehicle routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data package is downloaded and sent to the vehicle terminal through the vehicle routing device.

[0156] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0157] When the user terminal agrees to the software upgrade, a response message of agreeing to the upgrade is sent to the vehicle terminal;

[0158] When the upgrade consent response message is received, the vehicle-mounted routing device is controlled to enter the OTA ROTA mode, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

[0159] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0160] Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected;

[0161] Verify the legitimacy of future version data packets based on software name, software version and fields to be detected;

[0162] When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

[0163] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: according to the software name, software version and the field to be detected, the legitimacy of the future version data packet is verified, including:

[0164] Generate a verification data acquisition request based on the software name and software version;

[0165] Sending a verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle terminal based on the verification data acquisition request;

[0166] Based on the verification package and the fields to be detected, the legitimacy of future version data packets is verified.

[0167] In one embodiment, the computer program, when executed by a processor, further implements the following steps: the verification package includes a decryption key and verification data;

[0168] Accordingly, based on the verification package and the fields to be detected, the legitimacy of the future version data packet is verified, including:

[0169] Decrypt the field to be detected based on the decryption key to obtain decrypted data;

[0170] According to the matching result of the decrypted data and the verification data, the legitimacy verification result of the future version of the data packet is determined.

[0171] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: after performing a software upgrade on the software to be upgraded based on the future version data package, the method further includes:

[0172] In the case that the upgrade of the software to be upgraded fails, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded;

[0173] When the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

[0174] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0175] When the user terminal is connected to the vehicle routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data package is downloaded and sent to the vehicle terminal through the vehicle routing device.

[0176] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0177] When the user terminal agrees to the software upgrade, a response message of agreeing to the upgrade is sent to the vehicle terminal;

[0178] When the upgrade consent response message is received, the vehicle-mounted routing device is controlled to enter the OTA ROTA mode, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

[0179] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0180] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0181] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A vehicle software upgrade method, characterized in that: Applied to a vehicle-mounted terminal, the method comprises: Receiving a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected; Performing legitimacy verification on the future version data packet according to the software name, the software version and the field to be detected; When the future version data package is verified to be successful, the software to be upgraded is upgraded based on the future version data package.

2. The method according to claim 1, characterized in that The step of verifying the legitimacy of the future version data packet according to the software name, the software version and the field to be detected includes: Generate a verification data acquisition request according to the software name and the software version; Sending the verification data acquisition request to the Internet of Vehicles platform, so that the Internet of Vehicles platform feeds back a verification package to the vehicle-mounted terminal based on the verification data acquisition request; Based on the verification packet and the field to be detected, the legitimacy of the future version data packet is verified.

3. The method according to claim 2, characterized in that The verification package includes a decryption key and verification data; Accordingly, the verification of the legitimacy of the future version data packet based on the verification packet and the field to be detected includes: Decrypting the field to be detected based on the decryption key to obtain decrypted data; The legitimacy verification result of the future version data packet is determined according to the matching result of the decrypted data and the verification data.

4. The method according to claim 1, characterized in that After performing software upgrade on the software to be upgraded based on the future version data package, the method further includes: In the case that the software to be upgraded fails to be upgraded, the software to be upgraded is restored based on the current version data packet to obtain the current version of the software to be upgraded; wherein the current version data packet refers to the data packet used when upgrading the software to be upgraded to the current version of the software to be upgraded; When the software to be upgraded is successfully upgraded, the current version data package is deleted and the future version data package is saved.

5. The method according to claim 1, characterized in that The method further comprises: When the user terminal is connected to the vehicle routing device, a software upgrade request is sent to the user terminal, so that when the user terminal agrees to the software upgrade, the future version data packet is downloaded, and the future version data packet is sent to the vehicle terminal through the vehicle routing device.

6. The method according to claim 5, characterized in that The method further comprises: If the user terminal agrees to the software upgrade, sending an upgrade agreement response message to the vehicle terminal; When the upgrade consent response message is received, the vehicle-mounted routing device is controlled to enter the OTA ROTA mode, so that the vehicle-mounted routing device sends the future version data packet to the vehicle-mounted device in the OTA ROTA mode.

7. A vehicle software upgrade device, characterized in that: The device comprises: A receiving module, configured to receive a future version data packet for the software to be upgraded sent by a user terminal; wherein the future version data packet includes a data packet name; the data packet name includes a software name, a software version, and a field to be detected; A verification module, used to verify the legitimacy of the future version data packet according to the software name, the software version and the field to be detected; The upgrade module is used to upgrade the software to be upgraded based on the future version data packet when the future version data packet is verified.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the vehicle software upgrade method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the vehicle software upgrade method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the vehicle software upgrade method according to any one of claims 1 to 6 are implemented.

Images