A vehicle OTA registration method, device, equipment and medium

Abstract

The present application relates to the field of vehicle network technology, and discloses a vehicle OTA registration method, device, equipment and medium. The method includes: in response to the startup of the vehicle, detecting whether there is registration file information in the vehicle; if the registration file information does not exist in the vehicle, obtaining registration parameters; based on the registration parameters, sending a registration request to the OTA management platform, so that the OTA management platform generates registration file information according to the registration parameters; receiving the registration file information issued by the OTA management platform, and saving the registration file information to the designated directory of the vehicle to complete the OTA registration of the vehicle. After the vehicle of the present application is powered on, the registration operation is automatically performed when there is no registration file information, and the registration operation is automatically performed when the registration file information of the vehicle is abnormally lost.

Description

Technical Field

[0001] The present application relates to the field of vehicle network technology, and in particular, to a vehicle OTA registration method, device, equipment and medium. Background Art

[0002] OTA has become more and more common. Before OTA upgrade, the vehicle needs to complete registration and bind with the background to make the OTA vehicle within the legal and effective use range. In the prior art, there is no method for vehicle OTA registration.

[0003] As in the prior art, a comparative document with publication number CN112230966A discloses an OTA upgrade method and device, which is applied to an OTA server. By reasonably planning the upgrade path for each registered version according to the upgrade method of each registered version, a path information table is obtained. After receiving an upgrade request carrying the current version sent by the vehicle terminal, the latest version is determined in the registered version, and the target version corresponding to this upgrade is pushed to the vehicle terminal according to the path information table. This avoids the problem of low upgrade efficiency caused by upgrading in the order of registered versions when there is a skippable version between the current version and the latest version, and avoids upgrade errors caused by directly upgrading the current version to the target version when there is a non-skippable version between the current version and the latest version, thereby improving the OTA upgrade efficiency.

[0004] The OTA registration process is not reflected in the comparison document. When the vehicle registration information is lost, the vehicle OTA registration cannot be automatically performed. Summary of the invention

[0005] The purpose of this application is to provide a vehicle OTA registration method, device, equipment and medium, which automatically performs the OTA registration process when the registration file information is lost.

[0006] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0007] According to one aspect of an embodiment of the present application, a vehicle OTA registration method is provided, the method comprising: in response to starting the vehicle, detecting whether registration file information exists in the vehicle; if the registration file information does not exist in the vehicle, obtaining registration parameters; based on the registration parameters, sending a registration request to the OTA management platform, so that the OTA management platform generates registration file information according to the registration parameters; receiving the registration file information issued by the OTA management platform, and saving the registration file information to a designated directory of the vehicle, so as to complete the OTA registration of the vehicle.

[0008] In some embodiments, the vehicle includes a T-BOX device, and the T-BOX device includes an on-board information management module and a UC-Master module. The obtaining of registration parameters includes: obtaining a vehicle identification code of the vehicle from the on-board information management module; obtaining a UC-Master version number of the vehicle from the UC-Master module; obtaining a timestamp of a local system time from a local system of the vehicle; and encrypting the vehicle identification code, the UC-Master version number, and the timestamp by a pre-set key to obtain the registration parameters.

[0009] In some embodiments, obtaining the vehicle identification code of the vehicle from the on-board information management module includes: sending a vehicle identification code acquisition request from the UC-Master module in the T-BOX device to the on-board information management module in the T-BOX device; and receiving the vehicle identification code returned by the on-board information management module.

[0010] In some embodiments, the method further includes: if the vehicle identification code returned by the vehicle information management module is not received within a first preset time, terminating the registration process.

[0011] In some embodiments, based on the registration parameters, a registration request is sent to the OTA management platform so that the OTA management platform generates registration file information according to the registration parameters, including: sending the registration parameters to the OTA management platform so that the OTA management platform decrypts the registration parameters to obtain the vehicle identification code, the UC-Master version number, and the timestamp, and the OTA management platform matches its own vehicle identification code maintenance list based on the vehicle identification code. If an identification code corresponding to the vehicle identification code is matched in the vehicle identification code maintenance list, registration file information is generated according to the registration parameters.

[0012] In some embodiments, the method further includes: if an identification code corresponding to the vehicle identification code is not matched in the vehicle identification code maintenance list, generating registration failure information, and sending the registration failure information to the T-BOX device.

[0013] In some embodiments, the method further includes: if the registration file information sent by the OTA management platform is not received within a second preset time, terminating the registration process.

[0014] According to one aspect of an embodiment of the present application, an OTA registration device for a vehicle is provided, the device comprising: a detection unit, used to detect whether registration file information exists in the vehicle in response to the start-up of the vehicle; an acquisition unit, used to acquire registration parameters if the registration file information does not exist in the vehicle; a sending unit, used to send a registration request to the OTA management platform based on the registration parameters, so that the OTA management platform generates registration file information according to the registration parameters; a receiving unit, used to receive the registration file information issued by the OTA management platform, and save the registration file information to a designated directory of the vehicle, so as to complete the OTA registration of the vehicle.

[0015] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the OTA registration method as described in the above embodiment is implemented.

[0016] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; and a memory for storing executable instructions of the processors, wherein when the executable instructions are executed by the one or more processors, the one or more processors implement the OTA registration method as described in the above embodiment.

[0017] Compared with the prior art, the technical solution of the present application has the significant beneficial effect that before the vehicle uses the OTA function normally, it is necessary to activate the OTA function first and register the vehicle information on the OTA management platform. The present application is configured to initiate a platform connection request when the vehicle is powered on, and automatically detect the registration file information when the vehicle is connected to the OTA platform. When there is no registration file information, the registration operation is automatically performed, and when the registration file information of the vehicle is abnormally lost, the registration operation is automatically performed.

[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0020] Figure 1 A flowchart according to an embodiment of the present application is shown;

[0021] Figure 2 A flowchart of registration from a vehicle-side perspective according to an embodiment of the present application is shown;

[0022] Figure 3A flowchart of registration from a platform perspective according to an embodiment of the present application is shown;

[0023] Figure 4 A simplified diagram of an OTA registration device for a vehicle according to an embodiment of the present application is shown;

[0024] Figure 5 A schematic diagram of the structure of a computer system of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0025] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0026] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0027] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0028] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0029] According to some embodiments, the present application provides an OTA registration method for a vehicle, the method comprising: step 101, in response to the startup of the vehicle, detecting whether registration file information exists in the vehicle; step 102, if the registration file information does not exist in the vehicle, obtaining registration parameters; step 103, based on the registration parameters, sending a registration request to the OTA management platform, so that the OTA management platform generates registration file information according to the registration parameters; step 104, receiving the registration file information issued by the OTA management platform, and saving the registration file information to a designated directory of the vehicle to complete the OTA registration of the vehicle.

[0030] Based on the above embodiment, in step 101, before the vehicle uses the OTA function normally, it is necessary to activate the OTA function first, register the vehicle information in the OTA management platform, and automatically initiate a platform connection request when the vehicle is powered on. That is, when the vehicle is powered on, the UC-Master module detects whether there is registration file information. If there is registration file information, it means that the vehicle has been successfully registered and there is no need to initiate the registration process.

[0031] Among them, the UC-Master module is the core program for vehicle OTA upgrade, which implements the master control logic of OTA. It calls DM-Client to realize business communication and software package download with the server, and realizes the control and installation of other physical ECUs or virtual ECUs through the control and management of UC-Slave. Among them, UC-Slave is the upgraded ECU control program, which mainly realizes the control of a single ECU or upgrade object.

[0032] In step 102, if the UC-Master module detects that there is no registration file information in the vehicle, the registration parameters are first obtained.

[0033] In step 103, after the UC-Master module obtains the complete registration parameters, it sends a registration request to the OTA management platform. The registration request includes the registration parameters. After the OTA management platform receives the registration request sent by the UC-Master module, the OTA management platform generates registration file information according to the registration parameters.

[0034] In step 104, after the OTA management platform generates the registration file information according to the registration parameters, it sends the registration file information to the UC-Master module. After receiving the registration file information sent by the OTA management platform, the UC-Master module saves the registration file information to the designated directory of the vehicle to complete the OTA registration of the vehicle. The designated directory of the vehicle can be based on the actual needs and location.

[0035] According to some embodiments, the vehicle includes a T-BOX device, and the T-BOX device includes an on-board information management module and a UC-Master module. The obtaining of registration parameters includes: obtaining a vehicle identification code of the vehicle from the on-board information management module; obtaining a UC-Master version number of the vehicle from the UC-Master module; obtaining a timestamp of a local system time from a local system of the vehicle; and encrypting the vehicle identification code, the UC-Master version number, and the timestamp by a pre-set key to obtain the registration parameters.

[0036] Based on the above embodiment, the vehicle includes a T-BOX device, and the T-BOX device includes an on-board information management module and a UC-Master module. Obtaining the registration parameters includes: obtaining the vehicle identification code of the vehicle from the on-board information management module; obtaining the UC-Master version number of the vehicle from the UC-Master module; obtaining the timestamp of the local system time from the local system of the vehicle; encrypting the vehicle identification code, UC-Master version number, and the timestamp by a pre-set secret key to obtain the registration parameters. In some embodiments, UC-Master uses a public key to encrypt the vehicle identification code, UC-Master version number, and the timestamp, and obtains the registration parameters after encryption, and sends the registration parameters to the OTA management platform. After the OTA management platform receives the registration parameters, the OTA management platform decrypts the registration parameters by a private key to obtain the vehicle identification code, UC-Master version number, and the timestamp. Communication through encryption methods prevents information from being stolen or replaced after leakage.

[0037] According to some embodiments, obtaining the vehicle identification code of the vehicle from the on-board information management module includes: the UC-Master module in the T-BOX device sends a vehicle identification code acquisition request to the on-board information management module in the T-BOX device; and receiving the vehicle identification code returned by the on-board information management module.

[0038] Based on the above embodiment, the detailed method of obtaining the vehicle identification code of the vehicle from the vehicle information management module includes:

[0039] The UC-Master module in the T-BOX device sends a request for obtaining the vehicle identification code to the vehicle information management module in the T-BOX device;

[0040] After the vehicle information management module receives the vehicle identification code acquisition request sent by the UC-Master module, it forwards the vehicle identification code acquisition request to the MCU management module;

[0041] After receiving the vehicle identification code acquisition request sent by the vehicle information management module, the MCU management module forwards the vehicle identification code acquisition request to the MCU;

[0042] The MCU stores the vehicle identification code. After receiving the vehicle identification code acquisition request sent by the MCU management module, the MCU sends the vehicle identification code to the MCU management module;

[0043] After receiving the vehicle identification code sent by the MCU, the MCU management module sends the vehicle identification code to the vehicle information management module;

[0044] After the vehicle information management module receives the vehicle identification code sent by the MCU management module, the vehicle information management module sends the vehicle identification code to the UC-Master module;

[0045] The UC-Master module receives the vehicle identification code returned by the vehicle information management module.

[0046] According to some embodiments, the method further includes: if the vehicle identification code returned by the vehicle information management module is not received within a first preset time, terminating the registration process.

[0047] Based on the above embodiments, Figure 2 As shown, Figure 2 A flowchart 200 of registration from the vehicle side perspective is presented. When the UC-Master module in the T-BOX device sends a request to obtain the vehicle identification code to the vehicle information management module in the T-BOX device, if the vehicle information management module times out and does not return the vehicle identification code, the registration process is terminated and the registration process is automatically performed when the vehicle is powered on again next time before the operation is repeated.

[0048] According to some embodiments, based on the registration parameters, a registration request is sent to the OTA management platform so that the OTA management platform generates registration file information according to the registration parameters, including: sending the registration parameters to the OTA management platform so that the OTA management platform decrypts the registration parameters to obtain the vehicle identification code, the UC-Master version number, and the timestamp, the OTA management platform matches its own vehicle identification code maintenance list based on the vehicle identification code, and if an identification code corresponding to the vehicle identification code is matched in the vehicle identification code maintenance list, the registration file information is generated according to the registration parameters.

[0049] According to some embodiments, the method further comprises: if an identification code corresponding to the vehicle identification code is not matched in the vehicle identification code maintenance list, generating registration failure information, and sending the registration failure information to the T-BOX device.

[0050] Based on the above embodiment, after the registration parameters are sent to the OTA management platform, the OTA management platform decrypts the registration parameters to obtain the vehicle identification code, the UC-Master version number and the timestamp.

[0051] The OTA management platform matches the vehicle identification code in its own vehicle identification code maintenance list. If the identification code corresponding to the vehicle identification code is matched in the vehicle identification code maintenance list, the registration file information is generated according to the registration parameters and sent to UC-Master. If the identification code corresponding to the vehicle identification code cannot be matched in the vehicle identification code maintenance list, the OTA platform will return a registration failure code to UC-Master. If you want to register later, you need to add the vehicle identification code information of the vehicle to the platform for successful registration.

[0052] According to some embodiments, the method further includes: if the registration file information sent by the OTA management platform is not received within a second preset time, terminating the registration process.

[0053] Based on the above embodiments, Figure 2 As shown, Figure 2 A flowchart 200 of registration from the vehicle side perspective is presented. After UC-Master encrypts the vehicle identification code, UC-Master version number and the timestamp, obtains the registration parameters after encryption, and sends the registration parameters to the OTA management platform, if the registration file information issued by the OTA management platform is not received within the second preset time, the registration process is terminated to prevent UC-Master from being in a waiting state.

[0054] Furthermore, in order to enable those skilled in the art to more clearly understand the technical solution of the present application, the following will be described according to Figure 2 and Figure 3 The content of this application is described in more detail.

[0055] Figure 2 A flowchart 200 of registration from a vehicle-side perspective is shown. Figure 3 A flow chart 300 of registration from a platform perspective is shown.

[0056] like Figure 2 As shown, when performing the registration process from the vehicle side perspective:

[0057] The vehicle power position changes from OFF or ACC to ON;

[0058] After turning ON, the UC-Master module of T-BOX detects whether there is a vehicle registration information file;

[0059] If the vehicle registration information file exists, it means that the registration has been successful and the process stops;

[0060] If the vehicle registration information file does not exist, the UC-Master module of T-BOX sends a request to obtain the vehicle VIN code to the internal VIN management interface, where the VIN code is the vehicle identification number and the VIN management interface is the vehicle information management module;

[0061] After successfully obtaining VIN, UC-Master obtains the UC-Master version number from itself. The UC-Master version number has been generated during compilation and will not be unavailable.

[0062] UC-Master in T-BOX initiates a registration request to the OTA platform, carrying the VIN code, UC-Master version number, and local system timestamp, using a secret key to generate a signature from the VIN, UCMaster version, and timestamp as parameters for encryption verification with the OTA platform;

[0063] T-BOX starts the response timeout waiting, waiting for the OTA platform to feedback information. If the waiting timeout occurs, the fault code of not receiving the background registration response will be recorded;

[0064] If it does not time out, and T-BOX receives the registration information returned by the OTA platform, it will save the registration information to UC-Master, and the registration is successful.

[0065] Furthermore, after the UC-Master module sends a request to obtain the vehicle VIN code to the internal VIN management interface, if the UC-Master module times out and fails to obtain the VIN, the UC-Master module resends a request to obtain the vehicle VIN code to the internal VIN management interface.

[0066] Furthermore, after the number of failed attempts to obtain the VIN reaches the set number, if the response times out, the controller will detect whether the VIN has been written into the controller. If it has been written into the controller, the VIN acquisition failure fault code will be recorded. If it has not been written into the controller, the VIN unwritten fault code will be recorded. If the recording of the VIN acquisition failure fault code and the recording of the VIN unwritten fault code also time out, the T-BOX will terminate the registration process, the registration will fail, and the registration process will be re-initiated when the vehicle is powered on or the detection is triggered.

[0067] The following is based on Figure 2 and Figure 3 Further explanation of this application:

[0068] 1. New car registration OTA

[0069] Before the vehicle uses the OTA function normally, it is necessary to activate the OTA function first and register the vehicle information on the OTA management platform.

[0070] Therefore, when the vehicle connects to the OTA platform for the first time (a platform connection request will be initiated when powered on).

[0071] 1) When the vehicle connects to the OTA management platform for the first time, it is necessary to activate the function and register the vehicle information on the OTA platform.

[0072] 2) After the vehicle is successfully registered, the OTA platform assigns the vehicle device ID and device key. To avoid the VIN code being directly exposed in the business, the subsequent vehicle business interactions use the device ID as the unique identification code.

[0073] 3) The information required for registration includes: VIN, SDK version.

[0074] 4) VIN acquisition method: IVI provides a corresponding interface for UC-Master to use to obtain the vehicle's VIN information;

[0075] 2. Abnormal vehicle registration OTA

[0076] It is automatically triggered when the vehicle's local activation information (i.e. the registration information file in UC-Master) is lost.

[0077] 1) The vehicle needs to detect local registration information every time it is powered on. When the vehicle's local registration information is lost, it is necessary to perform function activation and register vehicle information on the OTA platform.

[0078] 2) After the vehicle is successfully registered, the OTA platform assigns the vehicle device ID and device key. To avoid the VIN code being directly exposed in the business, the subsequent vehicle business interactions use the device ID as the unique identification code.

[0079] 3) The information required for registration includes: VIN, UC-Master version.

[0080] 4) VIN acquisition method: Acquire through the VIN acquisition interface (such as connecting the acquisition interface with the MCU to obtain the VIN written into the MCU when the vehicle is offline), for UC-Master to use to obtain the vehicle's VIN information.

[0081] 3. Flowchart Figure 2 and Figure 3 The detailed steps are as follows:

[0082] 1. Check whether the registration information file exists;

[0083] (1) After the vehicle is started, UC-Master detects whether there is a registration information file;

[0084] (2) If the registration information file exists, it means the vehicle has been successfully registered;

[0085] (3) If the registration information file does not exist, UC-Master will initiate a vehicle registration request and execute the following action flow;

[0086] 2. The UC-Master module in the T-BOX requests the vehicle VIN information from the IVI through the interface;

[0087] (1) If the response timeout expires and the VIN information is not obtained, the vehicle will terminate the registration process and wait for the next IVI power-on to re-initiate the registration request. There are generally two reasons for the failure to obtain the information:

[0088] a) The VIN code is not written on the vehicle itself;

[0089] b) There are problems with the VIN code acquisition interface provided by IVI;

[0090] (2) If the VIN is successfully obtained, the following action flow will be continued;

[0091] 3. UC-Master obtains the UC-Master version number from itself. The UC-Master version number has been generated during compilation and there will be no situation where it cannot be obtained;

[0092] 4. UC-Master uses the VIN code, UC-Master version number, and local system timestamp as parameters using the default key to generate a signature using VIN, UC-Master version, and timestamp, and initiates a registration request to the OTA platform;

[0093] 5. The OTA platform receives the UC-Master registration request;

[0094] 6. The OTA platform matches the received VIN with the VIN list maintained by the vehicle management department. If the corresponding VIN is found, the OTA platform will feedback the registration information to the vehicle-side UC-Master;

[0095] (1) If the VIN exists, the OTA platform will return the registration success status, vehicle device ID, and device key;

[0096] (2) If the VIN does not exist, the OTA platform will return a registration failure code to UC-Master;

[0097] a. When the vehicle does not exist, the platform needs to add the vehicle's VIN information to successfully register;

[0098] 7. UC-Master waits for feedback from the OTA platform;

[0099] 8. If UC-Master times out and does not receive feedback from the OTA platform, UC-Master will terminate the registration process and the registration will fail. It will wait for the next vehicle power-on or detection trigger to re-initiate the registration process.

[0100] 9. UC-Master receives feedback from the OTA platform and saves the registration information returned by the OTA platform to the specified directory;

[0101] 10. Registration successful;

[0102] 11. In particular, when the vehicle VIN is changed (the VIN code obtained by UC-Master is changed) and the locally saved registration information is lost, the registration will be re-initiated according to the default logic (vehicle power-on).

[0103] The following introduces an apparatus embodiment of the present application, which can be used to execute the OTA registration method in the above embodiment of the present application.

[0104] Figure 4 A simplified diagram of an OTA registration device 400 for a vehicle in an embodiment of the present application is shown, the device comprising: a detection unit 401, used to detect whether registration file information exists in the vehicle in response to the start of the vehicle; an acquisition unit 402, used to acquire registration parameters if the registration file information does not exist in the vehicle; a sending unit 403, used to send a registration request to the OTA management platform based on the registration parameters, so that the OTA management platform generates registration file information according to the registration parameters; a receiving unit 404, used to receive the registration file information issued by the OTA management platform, and save the registration file information to a designated directory of the vehicle, so as to complete the OTA registration of the vehicle.

[0105] Based on the above embodiment, in the detection unit 401, before the vehicle uses the OTA function normally, it is necessary to activate the OTA function first, register the vehicle information in the OTA management platform, and automatically initiate a platform connection request when the vehicle is powered on. That is, when the vehicle is powered on, the UC-Master module detects whether there is registration file information. If there is registration file information, it means that the vehicle has been successfully registered and there is no need to initiate the registration process.

[0106] Among them, the UC-Master module is the core program for vehicle OTA upgrade, which implements the master control logic of OTA. It calls DM-Client to realize business communication and software package download with the server, and realizes the control and installation of other physical ECUs or virtual ECUs through the control and management of UC-Slave. Among them, UC-Slave is the upgraded ECU control program, which mainly realizes the control of a single ECU or upgrade object.

[0107] In the acquisition unit 402, if the UC-Master module detects that the registration file information does not exist in the vehicle, the registration parameters are first acquired.

[0108] In the sending unit 403, after the UC-Master module obtains the complete registration parameters, it sends a registration request to the OTA management platform, and the registration request includes the registration parameters. After the OTA management platform receives the registration request sent by the UC-Master module, the OTA management platform generates registration file information according to the registration parameters.

[0109] In the receiving unit 404, after the OTA management platform generates the registration file information according to the registration parameters, it sends the registration file information to the UC-Master module. After receiving the registration file information sent by the OTA management platform, the UC-Master module saves the registration file information to the designated directory of the vehicle to complete the OTA registration of the vehicle. The designated directory of the vehicle can be based on the actual needs and location.

[0110] Figure 5 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.

[0111] It should be noted that Figure 5 The computer system 500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0112] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503, such as executing the OTA registration method described in the above embodiment. Various programs and data required for system operation are also stored in RAM503. CPU501, ROM502 and RAM503 are connected to each other through bus 504. Input / output (I / O) interface 505 is also connected to bus 504.

[0113] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

[0114] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 509, and / or installed from a removable medium 511. When the computer program is executed by a central processing unit (CPU) 501, various functions defined in the system of the present application are executed.

[0115] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0116] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0117] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0118] As another aspect, the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device performs the OTA registration method described in the above embodiment.

[0119] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the OTA registration method described in the above embodiment.

[0120] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0121] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation method of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the OTA registration method described in the above embodiment.

[0122] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0123] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A vehicle OTA registration method, characterized in that: The method comprises: In response to starting the vehicle, detecting whether registration file information exists in the vehicle; If the registration file information does not exist in the vehicle, obtain registration parameters, wherein the registration parameters include the encrypted vehicle identification code of the vehicle, the encrypted UC-Master version number of the vehicle, and the encrypted timestamp of the vehicle system time; Based on the registration parameters, sending a registration request to the OTA management platform, so that the OTA management platform generates registration file information according to the registration parameters; Receive the registration file information sent by the OTA management platform, and save the registration file information to a designated directory of the vehicle to complete the OTA registration of the vehicle.

2. The method according to claim 1, characterized in that The vehicle includes a T-BOX device, the T-BOX device includes a vehicle information management module and a UC-Master module, and the obtaining of registration parameters includes: Obtaining a vehicle identification code of the vehicle from the vehicle information management module; Obtaining the UC-Master version number of the vehicle from the UC-Master module; Obtaining a timestamp of a local system time from a local system of the vehicle; The vehicle identification code, the UC-Master version number, and the timestamp are encrypted by a preset key to obtain the registration parameters.

3. The method according to claim 2, characterized in that The obtaining the vehicle identification code of the vehicle from the vehicle information management module includes: The UC-Master module in the T-BOX device sends a vehicle identification code acquisition request to the vehicle information management module in the T-BOX device; Receive the vehicle identification code returned by the vehicle information management module.

4. The method according to claim 3, characterized in that The method further comprises: If the vehicle identification code returned by the vehicle information management module is not received within the first preset time, the registration process is terminated.

5. The method according to claim 2, characterized in that: The sending a registration request to the OTA management platform based on the registration parameters, so that the OTA management platform generates registration file information according to the registration parameters, includes: The registration parameters are sent to the OTA management platform so that the OTA management platform decrypts the registration parameters to obtain the vehicle identification code, the UC-Master version number, and the timestamp. The OTA management platform matches the vehicle identification code in its own vehicle identification code maintenance list based on the vehicle identification code. If an identification code corresponding to the vehicle identification code is matched in the vehicle identification code maintenance list, registration file information is generated according to the registration parameters.

6. The method according to claim 5, characterized in that The method further comprises: If an identification code corresponding to the vehicle identification code is not matched in the vehicle identification code maintenance list, a registration failure message is generated and sent to the T-BOX device.

7. The method according to claim 1, characterized in that The method further comprises: If the registration file information sent by the OTA management platform is not received within the second preset time, the registration process is terminated.

8. A vehicle OTA registration device, characterized in that: The device comprises: a detection unit, configured to detect whether registration file information exists in the vehicle in response to starting the vehicle; an acquisition unit, used to acquire registration parameters if the registration file information does not exist in the vehicle, wherein the registration parameters include an encrypted vehicle identification code of the vehicle, an encrypted UC-Master version number of the vehicle, and an encrypted timestamp of the vehicle system time; A sending unit, used to send a registration request to an OTA management platform based on the registration parameters, so that the OTA management platform generates registration file information according to the registration parameters; The receiving unit is used to receive the registration file information sent by the OTA management platform and save the registration file information to a designated directory of the vehicle to complete the OTA registration of the vehicle.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the at least one program code is loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: The electronic device includes one or more processors and one or more memories, wherein the one or more memories store at least one program code, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by the method according to any one of claims 1 to 7.

Images