Method for identity authentication and ECU software upgrade, vehicle-mounted TBOX and vehicle

Abstract

The application discloses a kind of identity authentication and ECU software upgrading method, vehicle TBOX, vehicle.For the method of identity authentication of vehicle TBOX, it includes: receiving the first message body including first vehicle information, first verification code and first calculation mode sent by OTA platform;Second verification code is calculated according to the first calculation mode and the first verification code, and when the first vehicle information is verified to pass, the second message body is sent to the platform, so that the platform sends the third message body including third vehicle information and the third verification code calculated according to the second calculation mode and the second verification code in the second message body when the second vehicle information and the second verification code in the second message body are verified to pass, wherein the first and second calculation modes are randomly selected from a plurality of pre-designed calculation modes;Receive the third message body, and verify the third vehicle information and the third verification code to determine whether the platform identity authentication passes.The method ensures that OTA and TBOX cannot be counterfeited.

Description

Technical Field

[0001] This invention relates to the field of information security, specifically to a method for identity verification and ECU software upgrade, an in-vehicle TBOX, and a vehicle. Background Technology

[0002] With the development of automotive electronics and intelligent connected vehicle technologies, communication between in-vehicle TBOX (Telematics BOX, vehicle networking terminal) and OTA (Over-the-Air Technology) platforms has become widespread. OTA upgrades have gradually become a standard feature of intelligent connected vehicles, and OTA data is downloaded via the cloud.

[0003] In related technologies, authentication is usually required before data interaction. OTA platforms identify vehicle-mounted TBOXes (TBOXes) using fixed information such as the vehicle's VIN, TBOX serial number (BOX ID), and SIM (Subscriber Identity Module) card number. The vehicle-mounted TBOX typically accesses the cloud system using a fixed IP address and port number. However, due to a lack of security considerations, both the OTA platform and the vehicle-mounted TBOX are vulnerable to malicious impersonation, or OTA data can be maliciously tampered with if the OTA platform is compromised. Vehicle-mounted OTA upgrades can lead to security risks in vehicle use, making the need for secure and reliable data protection extremely urgent. To improve data security and reliability, related technologies embed CA (Certificate Authority) certificates into the vehicle-mounted TBOX and build their own PKI (Public Key Infrastructure) / CA systems. However, this is overly cumbersome and relatively difficult to implement. Summary of the Invention

[0004] This invention aims to at least partially address one of the technical problems in related technologies. Therefore, the first objective of this invention is to provide an authentication method that ensures that the OTA platform and the vehicle-mounted TBOX cannot be impersonated.

[0005] The second objective of this invention is to propose a method for upgrading ECU (Electronic Control Unit) software.

[0006] The third objective of this invention is to provide an in-vehicle TBOX.

[0007] The fourth objective of this invention is to provide a vehicle.

[0008] To achieve the above objectives, a first aspect of the present invention provides an authentication method for an in-vehicle TBOX. The method includes: receiving a first message body sent by an OTA platform, wherein the first message body includes first vehicle information, a first verification code, and a first calculation method, the first calculation method being randomly selected from a plurality of preset calculation methods; verifying the first vehicle information and calculating a second verification code based on the first calculation method and the first verification code; when the first vehicle information is successfully verified, sending a second message body to the OTA platform, so that the OTA platform verifies the second vehicle information and the second verification code in the second message body, and calculates a third verification code based on the second calculation method in the second message body and the second verification code, the second calculation method being randomly selected from a plurality of preset calculation methods; receiving a third message body sent by the OTA platform, wherein the OTA platform sends the third message body when the second vehicle information and the second verification code are successfully verified, the third message body including third vehicle information and a third verification code; and verifying the third vehicle information and the third verification code to determine whether the authentication of the OTA platform is successful.

[0009] According to the authentication method of this invention, firstly, a first message body sent by an OTA platform is received. The first message body includes first vehicle information, a first verification code, and a first calculation method, which is randomly selected from multiple preset calculation methods. The first vehicle information is verified, and a second verification code is calculated based on the first calculation method and the first verification code. When the first vehicle information is successfully verified, a second message body is sent to the OTA platform, enabling the OTA platform to verify the second vehicle information and the second verification code in the second message body, and to calculate a third verification code based on the second calculation method and the second verification code in the second message body, where the second calculation method is randomly selected from multiple preset calculation methods. Then, a third message body sent by the OTA platform is received. The OTA platform sends the third message body when the second vehicle information and the second verification code are successfully verified. The third message body includes third vehicle information and a third verification code. Finally, the third vehicle information and the third verification code are verified to determine whether the authentication of the OTA platform is successful. Thus, mutual authentication between the OTA platform and the vehicle-mounted TBOX ensures that neither the OTA platform nor the vehicle-mounted TBOX can be impersonated.

[0010] In addition, the authentication method proposed in the above embodiments of the present invention may also have the following additional technical features: In one embodiment of the present invention, the first message body further includes an authentication address, and sending the second message body to the OTA platform includes sending the second message body to the OTA platform through the authentication address.

[0011] In one embodiment of the present invention, the first message body further includes an authentication validity period, and the step of sending the second message body to the OTA platform further includes: sending the second message body to the OTA platform within the authentication validity period.

[0012] In one embodiment of the present invention, the first message body and the third message body are both encrypted by the OTA platform using the first public key of the vehicle TBOX, and the second message body is encrypted by the vehicle TBOX using the second public key of the OTA platform. The method further includes: decrypting the first message body using the first private key of the vehicle TBOX to obtain the first vehicle information, the authentication address, the first verification code, and the first calculation method; decrypting the third message body using the first private key to obtain the third vehicle information and the third verification code; wherein, the OTA platform uses the second private key of the OTA platform to decrypt the second message body to obtain the second vehicle information, the second verification code, and the second calculation method.

[0013] In one embodiment of the present invention, the method further includes: receiving a trigger signal sent by an EOL (End-of-life) device, generating a first public key and a first private key according to the trigger signal, and synchronizing the first public key to the OTA platform through the EOL device; receiving a second public key sent by the EOL device, wherein the second public key is obtained by the EOL device accessing the OTA platform; and synchronizing the vehicle information of the vehicle to the OTA platform through a TSP (Telematics Service Provider) platform.

[0014] In one embodiment of the present invention, the vehicle information includes the vehicle frame number and the serial number of the vehicle-mounted TBOX, the first verification code is a random code, and the first calculation method and the second calculation method include at least one of the following: cyclic displacement operation method, inversion operation method, and XOR operation method.

[0015] To achieve the above objectives, a second aspect of the present invention provides an ECU software upgrade method for an in-vehicle TBOX. The method includes: performing authentication using the authentication method described in any of the preceding claims; when authentication with an OTA platform is successful and an ECU software upgrade task message sent by the OTA platform is received, decrypting the ECU software upgrade task message using the private key of the in-vehicle TBOX to obtain a download address for the OTA data packet, and downloading the OTA data packet according to the download address; unpacking the OTA data packet to obtain ECU software upgrade data and a digital signature, and verifying the digital signature using the SM2 algorithm to determine whether the ECU software upgrade data has been tampered with; when it is determined that the ECU software upgrade data has not been tampered with, performing an ECU software upgrade based on the ECU software upgrade data.

[0016] The ECU software upgrade method according to embodiments of the present invention is used in an in-vehicle TBOX. First, authentication is performed using the aforementioned authentication method. When the OTA platform's authentication is successful and the ECU software upgrade task information sent by the OTA platform is received, the ECU software upgrade task information is decrypted using the private key of the in-vehicle TBOX to obtain the download address of the OTA data packet, and the OTA data packet is downloaded according to the download address. Then, the OTA data packet is unpacked to obtain the ECU software upgrade data and a digital signature, and the digital signature is verified using the SM2 algorithm to determine whether the ECU software upgrade data has been tampered with. If it is determined that the ECU software upgrade data has not been tampered with, the ECU software upgrade is performed based on the ECU software upgrade data. Thus, authentication is performed first to ensure that the OTA platform and the in-vehicle TBOX cannot be impersonated, and then the ECU software upgrade method is used to ensure the integrity and tamper-proof nature of the OTA data, guaranteeing data security during the OTA upgrade process.

[0017] In addition, the ECU software upgrade method proposed in the above embodiments of the present invention may also have the following additional technical features: In one embodiment of the present invention, the digital signature is obtained by the OTA platform encrypting the message digest using the SM2 algorithm, and the message digest is obtained by the OTA platform performing SHA256 operation on the ECU software upgrade data.

[0018] To achieve the above objectives, a third aspect of the present invention provides an in-vehicle TBOX, including a memory, a processor, and a computer program stored in the memory. When the computer program is executed by the processor, it implements the authentication method described above, and / or implements the ECU software upgrade method described above.

[0019] According to an embodiment of the present invention, when the computer program on the in-vehicle TBOX is executed by the processor, the above-described authentication method can be implemented to authenticate both the OTA platform and the in-vehicle TBOX. When the authentication of the OTA platform is successful, the ECU software upgrade can be performed. Thus, prior authentication ensures that the OTA platform and the in-vehicle TBOX cannot be impersonated. By implementing the above-described ECU software upgrade method, the integrity and tamper-proof nature of OTA data are ensured, guaranteeing data security during the OTA upgrade process.

[0020] To achieve the above objectives, a fourth aspect of the present invention provides a vehicle including the aforementioned vehicle-mounted TBOX.

[0021] According to embodiments of the present invention, the vehicle-mounted TBOX, through the aforementioned authentication method, can perform authentication on both the OTA platform and the vehicle-mounted TBOX. When the OTA platform authentication is successful, ECU software upgrades can be performed. Thus, prior authentication ensures that the OTA platform and the vehicle-mounted TBOX cannot be impersonated. Furthermore, by implementing the aforementioned ECU software upgrade method, OTA data integrity and tamper-proofing are ensured, guaranteeing data security during the OTA upgrade process.

[0022] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0023] The above and additional aspects and advantages of the present invention will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which: Figure 1 This is a flowchart of an authentication method according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the structure of an example of a vehicle-mounted TBOX according to the present invention; Figure 3 This is a schematic diagram of the first message body of an example of the present invention; Figure 4 This is a schematic diagram of the second message body of an example of the present invention; Figure 5 This is a schematic diagram of the third message body of an example of the present invention; Figure 6 This is a flowchart of an ECU software upgrade method according to an embodiment of the present invention; Figure 7 This is a structural block diagram of a vehicle according to an embodiment of the present invention. Detailed Implementation

[0024] Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.

[0025] The following description, with reference to the accompanying drawings, describes an embodiment of the present invention, including a method for identity verification and ECU software upgrade, an in-vehicle TBOX, and a vehicle.

[0026] Figure 1 This is a flowchart of an authentication method according to an embodiment of the present invention.

[0027] In this embodiment of the invention, the authentication method is used for an in-vehicle TBOX, which can be referred to as... Figure 2 The specific example shown.

[0028] like Figure 1 As shown, the authentication method of this invention includes the following steps: S101, receive the first message body sent by the OTA platform, wherein the first message body includes the first vehicle information, the first verification code and the first calculation method, and the first calculation method is randomly selected from multiple preset calculation methods.

[0029] Specifically, the OTA platform initiates authentication by sending a first message body to the vehicle TBOX through the TSP platform. This first message body is specifically an OTA-required authentication message body generated for the vehicle corresponding to the TBOX.

[0030] The aforementioned first vehicle information includes the vehicle's VIN and the vehicle-mounted TBOX's BOX ID. The first verification code is a random code. The first calculation method is randomly selected from multiple preset calculation methods, including at least one of cyclic bitwise operations, inversion operations, and XOR operations. The first calculation method is at least one of these methods and is used to calculate the verification code, so that the vehicle-mounted TBOX can calculate the second verification code after receiving the first message body. The aforementioned first message body also includes an authentication address and an authentication validity period. The authentication address is an OTA cloud authentication address, so that the vehicle-mounted TBOX can use this authentication address to access the OTA platform in the cloud. The OTA platform obtains the above information and encrypts it using the vehicle-mounted TBOX's first public key to obtain the first message body, thereby sending the first message body to the vehicle-mounted TBOX.

[0031] Optionally, the first message body also includes a message ID, which is the startup authentication message ID required by the OTA platform. The first message body can be seen as follows: Figure 3 The specific example shown.

[0032] It should be noted that before the OTA platform initiates authentication, a key pair needs to be generated in advance using the EOL device, and information exchange and storage are also required. Specifically, when the vehicle rolls off the production line, the on-board TBOX receives a trigger signal sent by the EOL device and generates a first public key and a first private key based on the trigger signal. The EOL device then collects the first public key from the on-board TBOX and synchronizes it to the OTA platform so that the OTA platform can securely store the first public key from the on-board TBOX. Additionally, the on-board TBOX receives the second public key from the OTA platform sent by the EOL device and securely stores it. The second public key is obtained by the EOL device accessing the OTA platform.

[0033] In addition, the vehicle information needs to be synchronized to the OTA platform through the TSP platform. Specifically, when the vehicle is off the production line, the vehicle TBOX will collect vehicle information and TBOX itself information. This information will be synchronized to the OTA platform through the TSP platform before the vehicle leaves the factory.

[0034] S102, verify the first vehicle information, and calculate the second verification code according to the first calculation method and the first verification code.

[0035] Specifically, the vehicle-mounted TBOX responds to the OTA platform's authentication, receives a first message body, and decrypts it using its first private key to obtain first vehicle information, an authentication address, a first verification code, and a first calculation method. The decrypted first vehicle information is compared with its own recorded information; if they match, the authentication of the first vehicle information is considered successful. The decrypted authentication address is used to access the OTA platform, and the vehicle-mounted TBOX can send a second message body to the OTA platform via this address. The decrypted first verification code and first calculation method are used to calculate the second verification code. The decrypted authentication validity period is used to limit the authentication time; the vehicle-mounted TBOX sends the second message body to the OTA platform within the authentication validity period.

[0036] After calculating the second verification code, the vehicle-mounted TBOX generates a second message body, which is a TBOX authentication response message body. This second message body includes second vehicle information, the second verification code, and a second calculation method. The second vehicle information includes the vehicle's VIN and the vehicle-mounted TBOX's BOX ID. The second calculation method is randomly selected from multiple preset calculation methods, including cyclic bitwise operations, inversion operations, and XOR operations. The second calculation method is at least one of these, enabling the OTA platform to calculate the third verification code. The vehicle-mounted TBOX obtains this information and encrypts it using the OTA platform's second public key to obtain the second message body.

[0037] Optionally, the second message body may further include a message ID, which is the message ID used by TBOX for authentication. The second message body can be seen as follows: Figure 4 The specific example shown.

[0038] S103, when the first vehicle information is verified, a second message body is sent to the OTA platform so that the OTA platform can verify the second vehicle information and the second verification code in the second message body, and calculate the third verification code according to the second calculation method and the second verification code in the second message body. The second calculation method is randomly selected from multiple preset calculation methods.

[0039] Specifically, the OTA platform authenticates the vehicle's TBOX. The OTA platform receives the second message body and then decrypts it using its second private key to obtain the second vehicle information, the second verification code, and the second calculation method. It then compares the decrypted second vehicle information and verification code with the second vehicle information and verification code calculated by the OTA platform itself. If they match completely, the OTA platform successfully authenticates the vehicle's TBOX; otherwise, the OTA platform fails to authenticate the vehicle's TBOX and disconnects communication with the OTA platform.

[0040] S104, Receive the third message body sent by the OTA platform, wherein the OTA platform sends the third message body when the second vehicle information and the second verification code are verified. The third message body includes the third vehicle information and the third verification code.

[0041] Specifically, if the OTA platform successfully authenticates the TBOX, it initiates an OTA authentication response, generating an OTA authentication response message body, i.e., the third message body. This message body includes: third vehicle information, including the vehicle identification number (VIN) and the TBOX serial number (BOXID); and a third verification code, calculated using the second verification code according to the second calculation method. The OTA platform obtains the above information, encrypts it using the first public key of the vehicle TBOX to obtain the third message body, and sends it to the TBOX terminal.

[0042] Optionally, the aforementioned third message body may further include a message ID, which is the message ID used by TBOX for authentication. The aforementioned third message body can be seen in... Figure 5 The specific example shown.

[0043] S105 verifies the third vehicle information and the third verification code to determine whether the identity verification of the OTA platform is successful.

[0044] Specifically, the vehicle-mounted TBOX receives the OTA authentication response message body, i.e., the third message body. It decrypts the third message body using the first private key to obtain the third vehicle information and the third verification code. The decrypted third vehicle information and third verification code are compared with the vehicle-mounted TBOX's own third vehicle information and the third verification code calculated by the vehicle-mounted TBOX. If they match completely, the vehicle-mounted TBOX successfully authenticates with the OTA platform; otherwise, the authentication fails, and communication between the vehicle-mounted TBOX and the OTA platform is terminated.

[0045] This enables mutual verification between the OTA platform and the in-vehicle TBOX, preventing the in-vehicle TBOX or OTA platform from being impersonated.

[0046] It should be noted that the authentication method in the above embodiments is only a preferred embodiment, and it is not limited to this in practical applications. For example, the OTA platform can be configured to encrypt the first message body using the second private key of the OTA platform, the vehicle-mounted TBOX can decrypt the first message body using the second public key of the OTA platform and encrypt it using the first private key of the vehicle-mounted TBOX to obtain the second message body, and the OTA platform can decrypt the second message body using the first public key of the vehicle-mounted TBOX.

[0047] It should also be noted that the second public key and the second private key of the aforementioned OTA platform are generated by other preset key generation systems and distributed to the OTA platform.

[0048] In summary, the authentication method of this embodiment first receives a first message body sent by an OTA platform, wherein the first message body includes first vehicle information, a first verification code, and a first calculation method, the first calculation method being randomly selected from multiple preset calculation methods; the first vehicle information is verified, and a second verification code is calculated based on the first calculation method and the first verification code; when the first vehicle information is verified successfully, a second message body is sent to the OTA platform, so that the OTA platform verifies the second vehicle information and the second verification code in the second message body, and calculates a third verification code based on the second calculation method and the second verification code in the second message body, wherein the second calculation method is randomly selected from multiple preset calculation methods; then, a third message body is received from the OTA platform, wherein the OTA platform sends the third message body when the second vehicle information and the second verification code are verified successfully, the third message body including third vehicle information and a third verification code; finally, the third vehicle information and the third verification code are verified to determine whether the authentication of the OTA platform is successful. Thus, through mutual authentication between the OTA platform and the vehicle-side TBOX, it is ensured that the OTA platform and the vehicle-side TBOX cannot be impersonated.

[0049] Figure 6 This is a flowchart of an ECU software upgrade method according to an embodiment of the present invention.

[0050] In this embodiment of the invention, the ECU software upgrade method is used for an in-vehicle TBOX.

[0051] like Figure 6 As shown, the ECU software upgrade method includes the following steps: S106 utilizes authentication methods for OTA platform and in-vehicle TBOX authentication.

[0052] Specifically, the authentication method is the authentication method described in the above embodiments.

[0053] It should be noted that when a vehicle rolls off the production line, the onboard TBOX needs to collect vehicle information and information from the national cryptographic security chip within the TBOX, such as the vehicle's VIN, the TBOX's serial number (BOX ID), and the public key based on the SM2 algorithm in the national cryptographic security chip. This information is registered with the TSP platform before the vehicle leaves the factory and synchronized to the OTA platform via the TSP platform. The national cryptographic security chip refers to a high-speed, high-performance 32-bit high-speed stream encryption chip, certified by the State Cryptography Administration, integrating multiple information security algorithms such as SM1, SM2, SM3, SM4, DES, and RSA. The ECU software upgrade method in this embodiment is based on the SM2 algorithm.

[0054] S107: When the authentication of the OTA platform is successful and the ECU software upgrade task information sent by the OTA platform is received, the ECU software upgrade task information is decrypted using the private key of the vehicle TBOX to obtain the download address of the OTA data package, and the OTA data package is downloaded according to the download address.

[0055] Specifically, the OTA platform issues OTA upgrade tasks to vehicles through the TSP platform. First, it needs to create an OTA data packet. The creation process includes: obtaining the ECU software upgrade data to be upgraded; performing a SHA256 operation on the ECU software upgrade data to obtain a message digest; encrypting the message digest using the OTA platform's private key based on the SM2 algorithm; the encrypted message is called a digital signature. Furthermore, it also needs to obtain the OTA platform's public key and add it to the OTA data packet. In summary, the OTA data packet specifically includes: ECU software upgrade data, digital signature, and the OTA platform's public key.

[0056] Secondly, each OTA data packet created in the OTA platform is stored in a unique storage and a random download address is generated. At the same time, the ECU software version information is obtained. Thus, the original upgrade task information is composed of the download address, the vehicle's VIN, the vehicle TBOX serial number (BOX ID), and the ECU software version information. The original upgrade task information is encrypted using the public key of the vehicle TBOX's Chinese cryptographic security chip based on the national cryptographic SM2 algorithm, becoming ciphertext ECU software upgrade task information. The OTA platform then sends the ECU software upgrade task information to the vehicle TBOX through the TSP platform.

[0057] After receiving the ECU software upgrade task information, the vehicle TBOX uses the private key of the vehicle TBOX's Chinese cryptographic security chip to decrypt the ECU software upgrade task information, obtaining complete upgrade task information such as the download address of the OTA data package and the ECU software version information. Then, the vehicle TBOX accesses the OTA platform according to the download address and downloads the OTA data package.

[0058] S108 unpacks the OTA data packet to obtain the ECU software upgrade data and digital signature, and uses the SM2 algorithm to verify the digital signature to determine whether the ECU software upgrade data has been tampered with.

[0059] Specifically, the vehicle-mounted TBOX unpacks the OTA data packets to obtain the ECU software upgrade data, digital signature, and the OTA platform's public key. Based on the SM2 algorithm, the vehicle-mounted TBOX verifies the signature of the ECU software upgrade data to ensure its authenticity and integrity, and to ensure that the data has not been tampered with.

[0060] S109: When it is determined that the ECU software upgrade data has not been tampered with, the ECU software upgrade is performed based on the ECU software upgrade data.

[0061] In summary, the ECU software upgrade method of this invention first uses the aforementioned authentication method for identity verification. When the OTA platform's authentication is successful and the ECU software upgrade task information sent by the OTA platform is received, the ECU software upgrade task information is decrypted using the private key of the vehicle's TBOX to obtain the download address of the OTA data packet, and the OTA data packet is downloaded according to the download address. Then, the OTA data packet is unpacked to obtain the ECU software upgrade data and digital signature, and the digital signature is verified using the SM2 algorithm to determine whether the ECU software upgrade data has been tampered with. If it is determined that the ECU software upgrade data has not been tampered with, the ECU software upgrade is performed according to the ECU software upgrade data. Thus, identity verification is performed first to ensure that the OTA platform and the vehicle's TBOX cannot be impersonated, and then the ECU software upgrade method is used to ensure the integrity and tamper-proof nature of the OTA data, ensuring data security during the OTA upgrade process. Moreover, the use of a random download address in this embodiment further ensures data security during the OTA upgrade process. Furthermore, it eliminates the need to embed a CA certificate in the vehicle's TBOX and build a self-built PKI / CA system.

[0062] Furthermore, this invention proposes a vehicle-mounted TBOX.

[0063] In this embodiment of the invention, the vehicle-mounted TBOX includes a memory, a processor, and a computer program stored in the memory. When the computer program is executed by the processor, it implements the above-mentioned authentication method and / or the above-mentioned ECU software upgrade method.

[0064] The in-vehicle TBOX in this embodiment of the invention, by implementing the aforementioned authentication method, can perform authentication on both the OTA platform and the in-vehicle TBOX. When the authentication of the OTA platform is successful, the ECU software upgrade can proceed. Thus, prior authentication ensures that the OTA platform and the in-vehicle TBOX cannot be impersonated. By implementing the aforementioned ECU software upgrade method, the integrity and tamper-proof nature of OTA data are ensured, guaranteeing data security during the OTA upgrade process.

[0065] Furthermore, the present invention proposes a vehicle.

[0066] Figure 7 This is a structural block diagram of a vehicle according to an embodiment of the present invention.

[0067] like Figure 7 As shown, vehicle 1000 includes the aforementioned vehicle-mounted TBOX100.

[0068] In the vehicle of this embodiment of the invention, the aforementioned in-vehicle TBOX allows for authentication of both the OTA platform and the in-vehicle TBOX using the aforementioned authentication method. Once the OTA platform authentication is successful, the ECU software upgrade can proceed. This prior authentication ensures that the OTA platform and the in-vehicle TBOX cannot be impersonated. Furthermore, the aforementioned ECU software upgrade method ensures the integrity and tamper-proof nature of OTA data, guaranteeing data security during the OTA upgrade process.

[0069] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein can be considered as a ordered list of executable instructions for implementing logical functions, which can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0070] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0071] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0072] In the description of this specification, the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and should not be construed as limiting the present invention.

[0073] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0074] In this specification, unless otherwise stated, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise explicitly defined. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances.

[0075] In this invention, unless otherwise explicitly specified and limited, "above" or "below" the second feature can mean that the first feature is in direct contact with the second feature, or that the first feature is in indirect contact with the second feature through an intermediate medium. Furthermore, "above," "over," and "on top" of the second feature can mean that the first feature is directly above or diagonally above the second feature, or simply that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature can mean that the first feature is directly below or diagonally below the second feature, or simply that the first feature is at a lower horizontal level than the second feature.

[0076] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for identity verification, characterized in that, For use in a vehicle-mounted TBOX, the method includes: The system receives a first message body sent by an OTA platform, wherein the first message body includes first vehicle information, a first verification code, and a first calculation method, wherein the first calculation method is randomly selected from a plurality of preset calculation methods; The first vehicle information is verified, and a second verification code is calculated based on the first calculation method and the first verification code. When the first vehicle information is verified, a second message body is sent to the OTA platform so that the OTA platform can verify the second vehicle information and the second verification code in the second message body, and calculate a third verification code according to the second calculation method and the second verification code in the second message body. The second calculation method is randomly selected from the plurality of preset calculation methods. The system receives a third message body sent by the OTA platform, wherein the OTA platform sends the third message body when the second vehicle information and the second verification code are verified successfully, and the third message body includes the third vehicle information and the third verification code; The third vehicle information and the third verification code are verified to determine whether the identity verification of the OTA platform is successful.

2. The authentication method according to claim 1, characterized in that, The first message body also includes an authentication address, and sending the second message body to the OTA platform includes: The second message body is sent to the OTA platform through the authentication address.

3. The authentication method according to claim 1 or 2, characterized in that, The first message body also includes an authentication validity period, and sending the second message body to the OTA platform further includes: During the validity period of the authentication, the second message body is sent to the OTA platform.

4. The authentication method according to claim 1, characterized in that, The first message body and the third message body are both encrypted by the OTA platform using the first public key of the vehicle TBOX, and the second message body is encrypted by the vehicle TBOX using the second public key of the OTA platform. The method further includes: The first message body is decrypted using the first private key of the vehicle TBOX to obtain the first vehicle information, the authentication address, the first verification code, and the first calculation method; The third message body is decrypted using the first private key to obtain the third vehicle information and the third verification code; The OTA platform uses its second private key to decrypt the second message body to obtain the second vehicle information, the second verification code, and the second calculation method.

5. The authentication method according to claim 4, characterized in that, The method further includes: Receive a trigger signal sent by an EOL device, generate the first public key and the first private key according to the trigger signal, and synchronize the first public key to the OTA platform through the EOL device; Receive the second public key sent by the EOL device, wherein the second public key is obtained by the EOL device by accessing the OTA platform; The vehicle information is synchronized to the OTA platform via the TSP platform.

6. The authentication method according to claim 1, characterized in that, The vehicle information includes the vehicle's chassis number and the serial number of the vehicle-mounted TBOX. The first verification code is a random code. The first calculation method and the second calculation method include at least one of the following: cyclic displacement operation, inversion operation, and XOR operation.

7. An ECU software upgrade method, characterized in that, For use in a vehicle-mounted TBOX, the method includes: Authentication is performed using the authentication method described in any one of claims 1-6; When the authentication of the OTA platform is successful and the ECU software upgrade task information sent by the OTA platform is received, the ECU software upgrade task information is decrypted using the private key of the vehicle TBOX to obtain the download address of the OTA data package, and the OTA data package is downloaded according to the download address; The OTA data packet is unpacked to obtain ECU software upgrade data and a digital signature. The digital signature is then verified using the SM2 algorithm to determine whether the ECU software upgrade data has been tampered with. When it is determined that the ECU software upgrade data has not been tampered with, the ECU software upgrade is performed based on the ECU software upgrade data.

8. The ECU software upgrade method according to claim 7, characterized in that, The digital signature is obtained by the OTA platform using the SM2 algorithm to encrypt the message digest, and the message digest is obtained by the OTA platform using SHA256 operation on the ECU software upgrade data.

9. A vehicle-mounted TBOX, comprising a memory, a processor, and a computer program stored in the memory, characterized in that, When the computer program is executed by the processor, it implements the authentication method as described in any one of claims 1-6, and / or the ECU software upgrade method as described in claim 7 or 8.

10. A vehicle, characterized in that, Including the vehicle-mounted TBOX as described in claim 9.

Images