Vehicle controller detection method, device, equipment and computer readable storage medium

Abstract

The application relates to the technical field of vehicle safety, and discloses a vehicle controller detection method, device, equipment and computer readable storage medium, wherein the method comprises the following steps: after the whole vehicle low voltage of a vehicle is powered on, a first vehicle identification code stored in a server is acquired through a vehicle-mounted intelligent terminal in the vehicle; each second vehicle identification code stored in each controller in the vehicle is acquired; the first vehicle identification code is compared with each second vehicle identification code; if the first vehicle identification code is inconsistent with at least one second vehicle identification code, a preset fault measure is controlled to be performed on the vehicle; and if the first vehicle identification code is consistent with any second vehicle identification code, the vehicle is controlled to enter a whole vehicle starting state. The application provides a vehicle controller detection scheme to prevent the situation that vehicle-mounted controllers except the whole vehicle controller and the vehicle-mounted intelligent terminal in the vehicle are privately replaced.

Description

Technical Field

[0001] This invention relates to the field of vehicle safety technology, and in particular to a vehicle controller detection method, apparatus, device, and computer-readable storage medium. Background Technology

[0002] With the increasing number of new energy vehicles on the market, the role of controllers is becoming more and more important. In order to comply with legal and regulatory requirements, and also to ensure the information security of OEMs, it is necessary to prevent unauthorized replacement or disassembly of controllers. The mainstream solution on the market is that the vehicle-mounted intelligent terminal and the vehicle controller send encrypted data to each other for authentication after the vehicle is powered on, so as to prevent the vehicle-mounted intelligent terminal and the vehicle controller from being disassembled. However, this cannot prevent unauthorized replacement of other vehicle controllers such as BCM (body control module) and BMS (battery management system). Summary of the Invention

[0003] The main objective of this invention is to provide a vehicle controller detection method, apparatus, device, and computer-readable storage medium, aiming to provide a vehicle controller detection solution to prevent unauthorized replacement of vehicle controllers other than the vehicle controller and vehicle intelligent terminal, such as BCM and BMS.

[0004] To achieve the above objectives, the present invention provides a vehicle controller detection method, the method comprising:

[0005] After the vehicle is powered on at low voltage, the first vehicle identification code stored in the server is obtained through the vehicle's on-board intelligent terminal.

[0006] Obtain each second vehicle identification code stored in each controller in the vehicle, and compare the first vehicle identification code with each of the second vehicle identification codes;

[0007] If the first vehicle identification code does not match at least one of the second vehicle identification codes, the vehicle is controlled to perform a preset fault measure.

[0008] If the first vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

[0009] Optionally, the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle includes:

[0010] The vehicle-mounted intelligent terminal sends an identification code acquisition request to the server, so that the server can respond with the first vehicle identification code corresponding to the terminal serial number of the vehicle-mounted intelligent terminal based on the identification code acquisition request.

[0011] Receive the first vehicle identification code forwarded by the in-vehicle intelligent terminal.

[0012] Optionally, the method further includes:

[0013] After the vehicle is powered on at low voltage, it is checked whether the vehicle-mounted intelligent terminal can communicate with the server.

[0014] If it is determined that the in-vehicle intelligent terminal can communicate with the server, then the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle is executed.

[0015] Optionally, after the step of detecting whether the in-vehicle intelligent terminal can communicate with the server, the method further includes:

[0016] If it is determined that the in-vehicle intelligent terminal cannot communicate with the server, then after obtaining the second vehicle identification code stored in each controller, the third vehicle identification code stored in the vehicle controller in the vehicle is compared with the second vehicle identification code.

[0017] If the third vehicle identification code does not match at least one of the second vehicle identification codes, then the vehicle is controlled to perform the preset fault measures.

[0018] If the third vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

[0019] Optionally, the preset fault measures include at least one or more of the following: limiting the vehicle's driving speed, displaying information on the vehicle's dashboard to indicate that the controller has a fault, and uploading fault information to the vehicle management platform through the in-vehicle intelligent terminal.

[0020] Optionally, the step of obtaining the respective second vehicle identification codes stored in each controller of the vehicle includes:

[0021] Send an identification code acquisition request to each controller so that each controller can respond with its own stored second vehicle identification code;

[0022] Upon receiving the second vehicle identification code, the step of comparing the first vehicle identification code with each of the second vehicle identification codes is performed;

[0023] If any of the controllers fails to return the second vehicle identification code, the vehicle is controlled to perform the preset fault measures.

[0024] Optionally, before the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle, the method further includes:

[0025] After the vehicle is powered on at low voltage, it performs a handshake authentication with the in-vehicle intelligent terminal. After the handshake authentication is successful, the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle is executed.

[0026] To achieve the above objectives, the present invention also provides a vehicle controller detection device, the device comprising:

[0027] The acquisition module is used to acquire the first vehicle identification code stored in the server through the vehicle-mounted intelligent terminal after the vehicle is powered on at low voltage.

[0028] The comparison module is used to obtain each second vehicle identification code stored by each controller in the vehicle, and compare the first vehicle identification code with each second vehicle identification code.

[0029] The control module is configured to control the vehicle to perform preset fault measures if the first vehicle identification code does not match at least one of the second vehicle identification codes; and to control the vehicle to enter the vehicle start-up state if the first vehicle identification code matches any of the second vehicle identification codes.

[0030] To achieve the above objectives, the present invention also provides a vehicle controller detection device, which includes: a memory, a processor, and a vehicle controller detection program stored in the memory and executable on the processor. When the vehicle controller detection program is executed by the processor, it implements the steps of the vehicle controller detection method described above.

[0031] In addition, to achieve the above objectives, the present invention also proposes a computer-readable storage medium storing a vehicle controller detection program, which, when executed by a processor, implements the steps of the vehicle controller detection method described above.

[0032] In this embodiment of the invention, by pre-backing up the vehicle identification number (VIN) in the server, after the vehicle is powered on at low voltage, the vehicle's onboard intelligent terminal obtains the first VIN stored in the server and the second VIN stored in each controller in the vehicle. The first VIN is compared with each of the second VINs to detect whether the controllers have been privately replaced, maliciously tampered with, or incorrectly written to the VIN after replacement. Then, if the first VIN does not match with at least one second VIN, the vehicle is controlled to execute preset fault measures. This allows the user to be prompted or warned if the controller has been privately replaced, maliciously tampered with, or incorrectly written to the VIN after replacement, so that the user can take timely measures to avoid safety accidents. If the first VIN matches any of the second VINs, the vehicle is controlled to enter the vehicle start-up state, ensuring normal vehicle start-up if the controller has not been privately replaced, maliciously tampered with, or incorrectly written to the VIN after replacement. Attached Figure Description

[0033] Figure 1 This is a schematic flowchart of the first embodiment of the vehicle controller detection method of the present invention;

[0034] Figure 2 This is a schematic diagram of a process involved in an embodiment of the vehicle controller detection of the present invention;

[0035] Figure 3 This is a schematic diagram of the functional modules of a preferred embodiment of the vehicle controller detection device of the present invention;

[0036] Figure 4 This is a schematic diagram of the hardware operating environment involved in the embodiments of the present invention.

[0037] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0038] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0039] Reference Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the vehicle controller detection method of the present invention.

[0040] This invention provides an embodiment of a vehicle controller detection method. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order. In this embodiment, the vehicle controller detection method includes steps S10 to S40:

[0041] Step S10: After the vehicle is powered on at low voltage, the first vehicle identification code stored in the server is obtained through the vehicle-mounted intelligent terminal in the vehicle.

[0042] In this embodiment, the vehicle controller detection method can be executed by the vehicle controller (or power domain controller) in the vehicle, or by adding a module to the vehicle to execute the vehicle controller detection method. No specific limitation is made in this embodiment. Since the vehicle controller is an essential unit in the vehicle, its failure or absence will prevent the vehicle from starting. When the vehicle controller is used to execute the vehicle controller detection method, the functions implemented by the method can be guaranteed to operate normally, provided the vehicle controller is functioning correctly. The following description uses the vehicle controller as the execution subject to illustrate the solution in this embodiment.

[0043] The vehicle controller in a vehicle primarily manages the battery system, electric drive system, and thermal management system via the vehicle bus or hardwired connections. This includes controlling gear shifting, accelerator pedal operation, and brake pedal operation; calculating the required torque output based on real-time battery charge; and controlling the vehicle's low-voltage and high-voltage power supply and energy recovery. The onboard intelligent terminal (also known as a TBOX) serves as the vehicle's network exit, connecting the independent vehicle network environment to the internet, providing services such as driving data collection, remote querying and control, and fault monitoring.

[0044] In this embodiment, the Vehicle Identification Number (VIN) of each vehicle is pre-backed up in the server. The in-vehicle intelligent terminal can establish a communication connection with the server and obtain the VIN from the server. This server can be a server specifically added for this embodiment, or it can be a service that provides VINs added to an existing server that provides services for vehicles.

[0045] After the vehicle is powered on at low voltage, the vehicle controller can obtain the vehicle identification code (hereinafter referred to as the first vehicle identification code for distinction) stored in the server through the on-board intelligent terminal. In a specific implementation, the rules required for the communication between the intelligent on-board terminal and the server to obtain the vehicle identification code can be preset. For example, the format of the identification code acquisition request sent by the intelligent on-board terminal to the server and the information to be carried can be standardized. The specific settings can be configured as needed, and there are no restrictions on this in this embodiment.

[0046] In one feasible implementation, prior to step S10, the method further includes:

[0047] Step a: After the vehicle is powered on at low voltage, a handshake authentication is performed with the vehicle-mounted intelligent terminal. After the handshake authentication is successful, step S10 is executed.

[0048] After the vehicle is powered on at low voltage, the vehicle controller first performs a handshake authentication with the onboard intelligent terminal to ensure that the vehicle controller and the onboard intelligent terminal have not been tampered with and can communicate normally. After the handshake authentication is successful, the onboard intelligent terminal obtains the first vehicle identification code stored in the server and then compares the vehicle identification codes.

[0049] The handshake authentication process is not limited in this embodiment. For example, in one feasible embodiment, the in-vehicle intelligent terminal can send an authentication request to the vehicle controller after the vehicle is powered on at low voltage. After receiving the authentication request, the vehicle controller encrypts its stored vehicle identification code according to a pre-set encryption algorithm and then sends it to the in-vehicle intelligent terminal. The in-vehicle intelligent terminal encrypts its stored vehicle identification code according to a pre-set encryption algorithm and then compares it with the encrypted vehicle identification code received from the vehicle controller. If the comparison matches, the in-vehicle intelligent terminal sends authentication success information back to the vehicle controller. After receiving the authentication success information, the vehicle controller obtains the first vehicle identification code from the server through the in-vehicle intelligent terminal.

[0050] Step S20: Obtain each second vehicle identification code stored in each controller of the vehicle, and compare the first vehicle identification code with each of the second vehicle identification codes.

[0051] The various controllers in a vehicle may include, for example, BCM and BMS controllers. In this embodiment, where the vehicle controller detection method is executed by the vehicle controller, each controller can refer to all controllers in the vehicle other than the vehicle controller and the on-board intelligent terminal.

[0052] During the electrical testing of vehicles before they leave the production line, the VIN code of the vehicle can be written into the storage (such as flash) of each controller using an EOL (End of Line Testing Tool) electrical testing device. The EOL electrical testing device is an off-line testing device used on the automobile production line to meet the functional testing and product configuration requirements before the product leaves the production line.

[0053] The vehicle controller can retrieve the vehicle identification number (hereinafter referred to as the second vehicle identification number) stored by each controller in the vehicle. It is understood that since there are multiple controllers, there will be multiple second vehicle identification numbers retrieved. The vehicle controller then compares the first vehicle identification number with each retrieved second vehicle identification number.

[0054] In a specific implementation, the second vehicle identification code can be obtained by: each controller actively reporting its stored second vehicle identification code to the vehicle controller after the vehicle is powered on at low voltage; or the vehicle controller can send an identification code acquisition request to each controller, and each controller can send its stored second vehicle identification code to the vehicle controller after receiving the identification code acquisition request.

[0055] Step S30: If the first vehicle identification code does not match at least one second vehicle identification code, then control the vehicle to perform a preset fault measure.

[0056] If the first vehicle identification code does not match at least one second vehicle identification code, it indicates that the controller corresponding to the inconsistent second vehicle identification code may have been privately replaced with a controller obtained through irregular channels, or may have been replaced without having the correct vehicle identification code written through a diagnostic tool, or may have had the vehicle identification code in the controller maliciously tampered with.

[0057] The preset fault measures can be measures set in advance as needed, used to remind or warn users that the controller may have been replaced without authorization, the VIN code may have been maliciously tampered with, or the vehicle identification code may not have been correctly written after replacement. If the first vehicle identification code does not match at least one second vehicle identification code, the vehicle can be controlled to execute the preset fault measures. This embodiment does not limit the specific measures included in the preset fault measures.

[0058] In one feasible implementation, the preset fault measures may include at least one or more of the following: limiting the vehicle's speed, displaying information indicating a controller fault on the vehicle's dashboard, and uploading fault information to the vehicle management platform via an in-vehicle intelligent terminal. For example, limiting the speed to below 20 km / h. The fault information uploaded to the vehicle management platform may include the time and location of the vehicle identification code mismatch, the identifier information of the controller corresponding to the mismatched second vehicle identification code, etc. The specific information included in the fault information can be preset as needed and is not limited in this embodiment.

[0059] Step S40: If the first vehicle identification code matches any of the second vehicle identification codes, then control the vehicle to enter the vehicle start-up state.

[0060] If the first vehicle identification code matches all the second vehicle identification codes, it means that the vehicle identification codes stored in each controller are consistent with the vehicle identification codes backed up in the server. This confirms that the controllers have not been privately replaced, maliciously tampered with, or had their VIN codes not correctly written after replacement. In this case, the vehicle can be controlled to enter the vehicle start-up state to ensure that the user can drive the vehicle normally.

[0061] It should be noted that the vehicle controller in the vehicle may also be replaced without authorization, have its VIN code maliciously altered, or have its vehicle identification number not correctly written after replacement. By backing up the vehicle identification number on the server and comparing it with the VIN codes in each controller, we can avoid the inability to detect whether the VIN code of each controller has been replaced without authorization, maliciously altered, or has not been correctly written after replacement when the vehicle controller has been replaced without authorization, thus ensuring the accuracy of detection.

[0062] In one feasible implementation, it can be done according to... Figure 2The process described above is for vehicle controller testing. During the electrical testing of vehicles after production, the Vehicle Identification Number (VIN) is written into the flash memory of each controller for storage. After the vehicle is powered on at low voltage, the vehicle controller authenticates with the onboard intelligent terminal. If authentication fails, the vehicle speed is limited, the instrument panel displays the vehicle's fault status, and the onboard intelligent terminal reports fault information. If authentication is successful, the vehicle controller further obtains the VIN stored in the cloud through the onboard intelligent terminal. Each controller in the vehicle sends its own VIN, written in its flash memory, to the vehicle controller via a message. The vehicle controller compares the VIN sent by the controller with the VIN backed up in the cloud by the onboard intelligent terminal. If the comparison matches, the vehicle is powered on normally. If the comparison does not match, the vehicle speed is limited, the instrument panel displays the vehicle's fault status, and the onboard intelligent terminal reports fault information.

[0063] In this embodiment, by pre-backing up the vehicle's vehicle identification number (VIN) in the server, after the vehicle is powered on at low voltage, the vehicle's onboard intelligent terminal obtains the first VIN stored in the server and the second VIN stored in each controller within the vehicle. The first VIN is compared with each of the second VINs to detect whether any controller has been privately replaced, maliciously tampered with, or incorrectly written to the vehicle identification number after replacement. If the first VIN does not match at least one of the second VINs, the vehicle is controlled to execute preset fault measures. This allows the user to be alerted or prompted if a controller has been privately replaced, maliciously tampered with, or incorrectly written to the vehicle identification number after replacement, enabling the user to take timely action to avoid safety accidents. If the first VIN matches any of the second VINs, the vehicle is controlled to enter the vehicle startup state, ensuring normal vehicle startup if no controller has been privately replaced, maliciously tampered with, or incorrectly written to the vehicle identification number after replacement.

[0064] Based on the first embodiment described above, a second embodiment of the vehicle controller detection method of the present invention is proposed. In this embodiment, step S10 includes steps S101 to S102:

[0065] Step S101: The vehicle-mounted intelligent terminal sends an identification code acquisition request to the server, so that the server can respond with the first vehicle identification code corresponding to the terminal serial number of the vehicle-mounted intelligent terminal based on the identification code acquisition request.

[0066] In this embodiment, the vehicle controller can send an identification code retrieval request to the server via the in-vehicle intelligent terminal. The identification code retrieval request may carry the terminal serial number of the in-vehicle intelligent terminal. The server can associate and store the vehicle identification codes of each vehicle with the terminal serial numbers of the in-vehicle intelligent terminals, thus allowing the corresponding vehicle identification code to be found using the terminal serial number. Upon receiving the identification code retrieval request, the server searches for the corresponding vehicle identification code based on the terminal serial number carried in the request. The found vehicle identification code is the first vehicle identification code, which is then sent back to the in-vehicle intelligent terminal.

[0067] Step S102: Receive the first vehicle identification code forwarded by the vehicle-mounted intelligent terminal.

[0068] After receiving the first vehicle identification code from the server, the in-vehicle intelligent terminal forwards the first vehicle identification code to the vehicle controller. Upon receiving the first vehicle identification code forwarded by the in-vehicle intelligent terminal, the vehicle controller can then compare it with the second vehicle identification codes of each controller.

[0069] In one feasible embodiment, the method further includes steps S50 to S60:

[0070] Step S50: After the vehicle is powered on at low voltage, check whether the vehicle-mounted intelligent terminal can communicate with the server.

[0071] In a specific implementation, the in-vehicle intelligent terminal communicates with the server through a built-in IoT card and signal receiving and transmitting device. In real-world applications, there may be situations where the in-vehicle intelligent terminal cannot communicate with the server. After the vehicle is powered on at low voltage, the vehicle controller can first check whether the in-vehicle intelligent terminal can communicate with the server. For example, in a specific implementation, if the in-vehicle intelligent terminal fails to establish a communication connection with the server, it sends a network connection timeout prompt to the vehicle controller. Upon receiving this prompt, the vehicle controller can determine that the in-vehicle intelligent terminal cannot communicate with the server.

[0072] Step S60: If it is determined that the vehicle-mounted intelligent terminal can communicate with the server, then step S10 is executed.

[0073] Once the vehicle controller determines that the on-board intelligent terminal can communicate with the server, it obtains the first vehicle identification code from the server through the on-board intelligent terminal.

[0074] In this embodiment, the vehicle controller is not limited to the handling method when it determines that the vehicle-mounted smart terminal cannot communicate with the server. In specific embodiments, it can be set as needed, for example, it can be set to display a network connection failure prompt on the vehicle's dashboard.

[0075] In one feasible implementation, after step S50, steps S70 to S90 are further included:

[0076] Step S70: If it is determined that the vehicle-mounted intelligent terminal cannot communicate with the server, then after obtaining the second vehicle identification code stored in each controller, the third vehicle identification code stored in the vehicle controller in the vehicle is compared with the second vehicle identification code.

[0077] If it is determined that the vehicle-mounted intelligent terminal cannot communicate with the server, the vehicle controller can obtain the second vehicle identification code stored in each controller and then compare the vehicle identification code stored in the vehicle controller (referred to as the third vehicle identification code for distinction) with the second vehicle identification code to detect whether each controller has been privately replaced, maliciously tampered with, or has not been correctly written to the vehicle identification code after replacement.

[0078] Step S80: If the third vehicle identification code does not match at least one of the second vehicle identification codes, then control the vehicle to execute the preset fault measures.

[0079] If the third vehicle identification code does not match at least one second vehicle identification code, it indicates that the individual controllers may have been replaced without authorization, the VIN code may have been maliciously tampered with, or the vehicle identification code may not have been correctly written after replacement. Alternatively, the vehicle controller may have been replaced without authorization, the VIN code may have been maliciously tampered with, or the vehicle identification code may not have been correctly written after replacement. In this case, the vehicle can be controlled to execute preset fault measures to remind or warn the user that the controller may have been replaced without authorization, the VIN code may have been maliciously tampered with, or the vehicle identification code may not have been correctly written after replacement.

[0080] Step S90: If the third vehicle identification code matches any of the second vehicle identification codes, then control the vehicle to enter the vehicle start-up state.

[0081] If the third vehicle identification code matches at least one second vehicle identification code, it means that if the vehicle controller has not been replaced without authorization, the VIN code has not been maliciously tampered with, or the vehicle identification code has not been correctly written after replacement, then the controller in the vehicle has not been replaced without authorization, the VIN code has not been maliciously tampered with, or the vehicle identification code has not been correctly written after replacement. In this case, the vehicle can be controlled to enter the vehicle start state to ensure that the user can drive the vehicle normally.

[0082] In one feasible implementation, the step of obtaining the respective second vehicle identification codes stored by each controller in the vehicle in step S20 includes steps S201 to S203:

[0083] Step S201: Send an identification code acquisition request to each controller so that each controller can return its stored second vehicle identification code.

[0084] After the vehicle is powered on at low voltage, the vehicle controller can send an identification code retrieval request to each controller. Upon receiving the request, each controller can send its stored second vehicle identification code back to the vehicle controller. It should be noted that if a controller malfunctions or is removed, the vehicle controller will not receive the second vehicle identification code sent by that controller.

[0085] Step S202: After receiving the second vehicle identification code, perform the step of comparing the first vehicle identification code with each of the second vehicle identification codes in step S20.

[0086] After receiving the second vehicle identification code, the vehicle controller can compare the second vehicle identification code with the first vehicle identification code. If at least one of the received second vehicle identification codes does not match the first vehicle identification code, it indicates that the controller in the vehicle has been replaced without authorization, the VIN code has been maliciously tampered with, or the vehicle identification code has not been correctly written after replacement. In this case, the controller will execute preset fault measures.

[0087] Step S203: If any of the controllers fails to return the second vehicle identification code, control the vehicle to execute the preset fault measures.

[0088] If the vehicle controller detects that at least one controller has not fed back a second vehicle identification code, it can control the vehicle to execute preset fault measures. The failure of a controller to feed back a vehicle identification code to the vehicle controller indicates that the controller may be faulty or has been removed. By controlling the vehicle to execute preset fault measures, the system can alert or warn the user and prevent safety accidents caused by controller failure during vehicle operation (such as rear-end collisions caused by the failure of turn signals, brake lights, and other lighting functions due to BCM failure to start normally).

[0089] In a specific implementation, the vehicle controller may start timing after sending an identification code acquisition request to each controller. If the second vehicle identification code is not received from the controller after the timing reaches a preset time, it is determined that the controller has not received the second vehicle identification code.

[0090] Furthermore, embodiments of the present invention also propose a vehicle controller detection device, referring to... Figure 4 The vehicle controller detection device includes:

[0091] The acquisition module 10 is used to acquire the first vehicle identification code stored in the server through the vehicle-mounted intelligent terminal in the vehicle after the vehicle is powered on at low voltage.

[0092] The comparison module 20 is used to obtain each second vehicle identification code stored by each controller in the vehicle, and compare the first vehicle identification code with each second vehicle identification code.

[0093] The control module 30 is configured to control the vehicle to perform preset fault measures if the first vehicle identification code does not match at least one of the second vehicle identification codes; and to control the vehicle to enter the vehicle start-up state if the first vehicle identification code matches any of the second vehicle identification codes.

[0094] In one feasible embodiment, the acquisition module 10 is further configured to:

[0095] The vehicle-mounted intelligent terminal sends an identification code acquisition request to the server, so that the server can respond with the first vehicle identification code corresponding to the terminal serial number of the vehicle-mounted intelligent terminal based on the identification code acquisition request.

[0096] Receive the first vehicle identification code forwarded by the in-vehicle intelligent terminal.

[0097] In one feasible embodiment, the vehicle controller detection device further includes:

[0098] The detection module is used to detect whether the vehicle-mounted intelligent terminal can communicate with the server after the vehicle is powered on at low voltage.

[0099] The acquisition module 10 is further configured to, if it is determined that the in-vehicle intelligent terminal can communicate with the server, perform the operation of acquiring the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle.

[0100] In one feasible implementation, after the operation of detecting whether the vehicle-mounted intelligent terminal can communicate with the server, the comparison module 20 is further configured to, if it is determined that the vehicle-mounted intelligent terminal cannot communicate with the server, compare the third vehicle identification code stored in the vehicle controller with the second vehicle identification code after obtaining the second vehicle identification code stored in each controller.

[0101] The control module 30 is further configured to control the vehicle to perform the preset fault measures if the third vehicle identification code does not match at least one of the second vehicle identification codes.

[0102] If the third vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

[0103] In one feasible implementation, the preset fault measures include at least one or more of the following: limiting the vehicle's driving speed, displaying information on the vehicle's dashboard to indicate that the controller has a fault, and uploading fault information to the vehicle management platform through the in-vehicle intelligent terminal.

[0104] In one feasible embodiment, the comparison module 20 is further configured to:

[0105] Send an identification code acquisition request to each controller so that each controller can respond with its own stored second vehicle identification code;

[0106] Upon receiving the second vehicle identification code, the operation of comparing the first vehicle identification code with each of the second vehicle identification codes is performed;

[0107] If any of the controllers fails to return the second vehicle identification code, the vehicle is controlled to perform the preset fault measures.

[0108] In one feasible embodiment, the vehicle controller detection device further includes:

[0109] The authentication module is used to perform a handshake authentication with the vehicle-mounted intelligent terminal after the vehicle is powered on at low voltage. After the handshake authentication is successful, the operation of obtaining the first vehicle identification code stored in the server through the vehicle-mounted intelligent terminal in the vehicle is executed.

[0110] Furthermore, embodiments of the present invention also propose a vehicle controller detection device, such as... Figure 4 As shown, Figure 4 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention. It should be noted that the vehicle controller detection device in the embodiments of the present invention can be the vehicle controller in the vehicle.

[0111] like Figure 4As shown, the vehicle controller detection device may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0112] Those skilled in the art will understand that Figure 4 The device structure shown does not constitute a limitation on the vehicle controller detection device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0113] like Figure 4 As shown, the memory 1005, as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a vehicle controller detection program. The operating system is a program that manages and controls the hardware and software resources of the device, supporting the operation of the vehicle controller detection program and other software or programs. Figure 4 In the device shown, the user interface 1003 is mainly used for data communication with the client; the network interface 1004 is mainly used for establishing a communication connection with the server; and the processor 1001 can be used to call the vehicle controller detection program stored in the memory 1005 and perform the following operations:

[0114] After the vehicle is powered on at low voltage, the first vehicle identification code stored in the server is obtained through the vehicle's on-board intelligent terminal.

[0115] Obtain each second vehicle identification code stored in each controller in the vehicle, and compare the first vehicle identification code with each of the second vehicle identification codes;

[0116] If the first vehicle identification code does not match at least one of the second vehicle identification codes, the vehicle is controlled to perform a preset fault measure.

[0117] If the first vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

[0118] In one feasible implementation, the operation of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle includes:

[0119] The vehicle-mounted intelligent terminal sends an identification code acquisition request to the server, so that the server can respond with the first vehicle identification code corresponding to the terminal serial number of the vehicle-mounted intelligent terminal based on the identification code acquisition request.

[0120] Receive the first vehicle identification code forwarded by the in-vehicle intelligent terminal.

[0121] In one feasible embodiment, the processor 1001 can also be used to call the vehicle controller detection program stored in the memory 1005 and perform the following operations:

[0122] After the vehicle is powered on at low voltage, it is checked whether the vehicle-mounted intelligent terminal can communicate with the server.

[0123] If it is determined that the in-vehicle intelligent terminal can communicate with the server, then the operation of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle is performed.

[0124] In one feasible implementation, after detecting whether the in-vehicle intelligent terminal can communicate with the server, the processor 1001 can also be used to call the vehicle controller detection program stored in the memory 1005 and perform the following operations:

[0125] If it is determined that the in-vehicle intelligent terminal cannot communicate with the server, then after obtaining the second vehicle identification code stored in each controller, the third vehicle identification code stored in the vehicle controller in the vehicle is compared with the second vehicle identification code.

[0126] If the third vehicle identification code does not match at least one of the second vehicle identification codes, then the vehicle is controlled to perform the preset fault measures.

[0127] If the third vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

[0128] In one feasible implementation, the preset fault measures include at least one or more of the following: limiting the vehicle's driving speed, displaying information on the vehicle's dashboard to indicate that the controller has a fault, and uploading fault information to the vehicle management platform through the in-vehicle intelligent terminal.

[0129] In one feasible implementation, the operation of obtaining each second vehicle identification code stored by each controller in the vehicle includes:

[0130] Send an identification code acquisition request to each controller so that each controller can respond with its own stored second vehicle identification code;

[0131] Upon receiving the second vehicle identification code, the operation of comparing the first vehicle identification code with each of the second vehicle identification codes is performed;

[0132] If any of the controllers fails to return the second vehicle identification code, the vehicle is controlled to perform the preset fault measures.

[0133] In one feasible implementation, before the operation of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle, the processor 1001 can also be used to call the vehicle controller detection program stored in the memory 1005 to perform the following operations:

[0134] After the vehicle is powered on at low voltage, it performs a handshake authentication with the in-vehicle intelligent terminal. After the handshake authentication is successful, it performs the operation of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle.

[0135] Furthermore, embodiments of the present invention also propose a computer-readable storage medium storing a vehicle controller detection program, which, when executed by a processor, implements the steps of the vehicle controller detection method described above.

[0136] The various embodiments of the vehicle controller detection device and computer-readable storage medium of the present invention can be referred to the various embodiments of the vehicle controller detection method of the present invention, and will not be repeated here.

[0137] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0138] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0139] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0140] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A method for detecting a vehicle controller, characterized in that, The method includes the following steps: After the vehicle is powered on at low voltage, the vehicle controller encrypts its stored vehicle identification code according to a preset encryption algorithm and sends it to the vehicle intelligent terminal. The vehicle intelligent terminal encrypts its stored vehicle identification code using the same encryption algorithm. When the encrypted messages of both parties match, the handshake authentication is completed. After the handshake authentication is completed, it is checked whether the vehicle-mounted intelligent terminal can communicate with the server; If it is determined that the in-vehicle intelligent terminal can communicate with the server, then the first vehicle identification code stored in the server is obtained through the in-vehicle intelligent terminal in the vehicle. Obtain each second vehicle identification code stored in each controller in the vehicle, and compare the first vehicle identification code with each of the second vehicle identification codes; If the first vehicle identification code does not match at least one of the second vehicle identification codes, the vehicle is controlled to perform a preset fault measure. If the first vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state. If it is determined that the in-vehicle intelligent terminal cannot communicate with the server, then after obtaining the second vehicle identification code stored in each controller, the third vehicle identification code stored in the vehicle controller in the vehicle is compared with the second vehicle identification code. If the third vehicle identification code does not match at least one of the second vehicle identification codes, then the vehicle is controlled to perform the preset fault measures. If the third vehicle identification code matches any of the second vehicle identification codes, then the vehicle is controlled to enter the vehicle start-up state.

2. The vehicle controller detection method as described in claim 1, characterized in that, The step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle includes: The vehicle-mounted intelligent terminal sends an identification code acquisition request to the server, so that the server can respond with the first vehicle identification code corresponding to the terminal serial number of the vehicle-mounted intelligent terminal based on the identification code acquisition request. Receive the first vehicle identification code forwarded by the in-vehicle intelligent terminal.

3. The vehicle controller detection method as described in claim 1, characterized in that, The method further includes: If it is determined that the in-vehicle intelligent terminal can communicate with the server, then the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle is executed.

4. The vehicle controller detection method as described in claim 1, characterized in that, The preset fault measures include at least one or more of the following: limiting the vehicle's driving speed, displaying information on the vehicle's dashboard to indicate that the controller has a fault, and uploading fault information to the vehicle management platform through the in-vehicle intelligent terminal.

5. The vehicle controller detection method as described in claim 1, characterized in that, The step of obtaining the respective second vehicle identification codes stored in each controller of the vehicle includes: Send an identification code acquisition request to each controller so that each controller can respond with its own stored second vehicle identification code; Upon receiving the second vehicle identification code, the step of comparing the first vehicle identification code with each of the second vehicle identification codes is performed; If any of the controllers fails to return the second vehicle identification code, the vehicle is controlled to perform the preset fault measures.

6. The vehicle controller detection method according to any one of claims 1 to 5, characterized in that, Before the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle, the method further includes: After the vehicle is powered on at low voltage, it performs a handshake authentication with the in-vehicle intelligent terminal. After the handshake authentication is successful, the step of obtaining the first vehicle identification code stored in the server through the in-vehicle intelligent terminal in the vehicle is executed.

7. A vehicle controller detection device, characterized in that, The device includes: The acquisition module is used to, after the vehicle is powered on at low voltage, encrypt the vehicle identification code stored in its own storage according to a preset encryption algorithm and send it to the vehicle-mounted intelligent terminal. The vehicle-mounted intelligent terminal encrypts its own stored vehicle identification code using the same encryption algorithm. The encrypted messages of both parties are compared and matched to complete the handshake authentication. After the handshake authentication is completed, it is detected whether the vehicle-mounted intelligent terminal can communicate with the server. If it is determined that the vehicle-mounted intelligent terminal can communicate with the server, the first vehicle identification code stored in the server is obtained through the vehicle-mounted intelligent terminal in the vehicle. The comparison module is used to obtain each second vehicle identification code stored by each controller in the vehicle, and compare the first vehicle identification code with each second vehicle identification code. The control module is configured to control the vehicle to perform a preset fault measure if the first vehicle identification code does not match at least one of the second vehicle identification codes; and to control the vehicle to enter the vehicle start-up state if the first vehicle identification code matches any of the second vehicle identification codes. The device further includes: if it is determined that the in-vehicle intelligent terminal cannot communicate with the server, then after obtaining the second vehicle identification code stored in each controller, comparing the third vehicle identification code stored in the vehicle controller with the second vehicle identification code; if the third vehicle identification code does not match at least one second vehicle identification code, then controlling the vehicle to execute the preset fault measure; if the third vehicle identification code matches any of the second vehicle identification codes, then controlling the vehicle to enter the vehicle start-up state.

8. A vehicle controller testing device, characterized in that, The vehicle controller detection device includes: a memory, a processor, and a vehicle controller detection program stored in the memory and executable on the processor. When the vehicle controller detection program is executed by the processor, it implements the steps of the vehicle controller detection method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a vehicle controller detection program, which, when executed by a processor, implements the steps of the vehicle controller detection method as described in any one of claims 1 to 6.

Images