Remote vehicle locking method and system, electronic equipment, storage medium and computer program product

Abstract

The invention discloses a remote vehicle locking method, which belongs to the technical field of vehicle remote control, and comprises the following steps: after a vehicle controller and a vehicle-mounted remote controller terminal are bound and activated, a vehicle remote monitoring platform sends a vehicle locking instruction to the vehicle-mounted remote controller terminal, and the vehicle-mounted remote controller terminal forwards a vehicle locking request to the vehicle controller; and the vehicle controller carries out identity identification verification, and the actual vehicle locking operation is delayed to be executed when the vehicle is powered on and started next time. The invention further discloses a remote vehicle locking system, electronic equipment, a storage medium and a computer program product. Safety accidents caused by vehicle locking in the driving process can be avoided, meanwhile, vehicle locking failure caused by illegal equipment dismantling is prevented, and response timeliness and operation safety are both considered.

Description

Technical Field

[0001] This invention relates to the field of vehicle remote control technology. More specifically, this invention relates to a remote vehicle locking method and system, electronic equipment, storage medium, and computer program product. Background Technology

[0002] Off-highway dump trucks, as core equipment in open-pit mine transportation, including new energy vehicles (electric and hybrid vehicles) and fuel trucks, typically operate in remote areas. Effective remote control of these vehicles has become a pressing technical challenge. However, current vehicle remote control technologies suffer from inadequate identity verification mechanisms. Existing remote locking methods do not rigorously verify the identity of the sending device, leading to accidental locking or unauthorized control. This is due to the lack of an effective identity binding and comparison process, making it difficult to ensure the legitimacy of the command source. Furthermore, the timing of locking operations in existing remote locking methods is not ideal. Performing locking operations while the vehicle is in motion can easily cause safety accidents. Achieving delayed locking operations while ensuring accuracy presents technical difficulties. Moreover, if related equipment is intentionally removed, it not only causes the locking function to fail but also triggers offline locking, which can also easily lead to safety accidents. These problems hinder the reliable and secure application of remote locking functions. Summary of the Invention

[0003] This invention provides a remote vehicle locking method and system, electronic device, storage medium, and computer program product, which can avoid safety accidents caused by locking the vehicle while driving, and prevent vehicle locking failure caused by illegal removal of equipment, thus balancing timely response and operational safety.

[0004] To achieve these and other advantages of the present invention, a remote vehicle locking method is provided, including an active vehicle locking process: After the vehicle controller and the vehicle remote controller terminal are bound and activated, the vehicle remote monitoring platform sends a vehicle lock command to the vehicle remote controller terminal. After receiving the vehicle locking command, the vehicle remote controller terminal forwards the locking request to the vehicle controller; After receiving the vehicle lock request, the vehicle controller compares whether the identity ID of the vehicle remote controller terminal that sent the lock request is consistent with the unique identity ID of the pre-bound activated vehicle remote controller terminal. If the identity ID matches, the vehicle controller sets the current cycle to determine the vehicle locking status and displays the information that the vehicle is about to be locked on the instrument panel. If the identity ID does not match, the vehicle controller will set the current cycle to determine the vehicle locking status and display the identity ID mismatch information on the instrument panel. The vehicle controllers all delay the actual locking operation until the vehicle is powered on and started again; When the vehicle is a new energy vehicle, the vehicle controller is the whole vehicle controller; When the vehicle is an oil-powered vehicle, the vehicle controller is the engine controller.

[0005] Preferably, the method further includes a passive vehicle locking process: After the vehicle controller and the vehicle remote controller terminal are bound and activated, the vehicle controller will initiate a handshake verification immediately upon each power-on start-up, and will periodically initiate a handshake verification during subsequent operation. If the first handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. After the vehicle is powered off and powered on again, the handshake verification is successful. The vehicle controller does not actually lock the vehicle and automatically clears the current cycle to determine the vehicle lock status and the verification failure record. If the initial handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. If the handshake fails again after the vehicle is powered off and powered on again, the vehicle controller will actually lock the vehicle and display the verification failure information on the instrument panel.

[0006] Preferably, the handshake verification includes: The vehicle controller generates a random number seed and sends it to the on-board remote controller terminal. The vehicle-mounted remote controller terminal uses its own fixed key and the random number seed to calculate the key value through an encryption algorithm and returns it. The vehicle controller verifies whether the returned key value matches its own calculated value.

[0007] Preferably, the method further includes an activation process: The vehicle remote monitoring platform sends an activation command to the on-board remote controller terminal; After receiving the activation command, the vehicle remote controller terminal sends a vehicle locking function activation request to the vehicle controller; After receiving the vehicle locking function activation request, the vehicle controller stores the identity ID of the vehicle remote controller terminal that sent the request as a unique binding identity ID and a fixed key used for handshake verification, and returns activation success information to the vehicle remote controller terminal. The vehicle controller and the vehicle remote controller terminal complete the binding activation.

[0008] Preferably, the method further includes a deactivation process: The vehicle remote monitoring platform sends a deactivation command to the on-board remote controller terminal; After receiving the deactivation command, the vehicle remote controller terminal sends a deactivation request to the vehicle controller; After receiving the deactivation request, the vehicle controller compares the identity ID of the vehicle remote controller terminal that sent the request with the bound identity ID. If the identity ID matches, the vehicle controller will directly cancel the vehicle locking function activation state and clear the bound identity ID. If a vehicle is locked, the current cycle of locking status will be cleared and the actual locking status will be released.

[0009] Preferably, the actual vehicle locking operation is as follows: The vehicle controller limits the vehicle speed to 0 km / h or the vehicle controller limits the vehicle speed to a low speed range, wherein the low speed range refers to the speed range that affects the normal operation of the vehicle and is lower than the normal operation speed of the vehicle.

[0010] Preferably, the method further includes an unlocking process: The vehicle remote monitoring platform sends an unlock command to the on-board remote controller terminal; After receiving the unlock command, the vehicle remote controller terminal sends an unlock request to the vehicle controller; After receiving the unlock request, the vehicle controller compares the identity ID of the vehicle remote controller terminal that sent the request with the bound identity ID. If the identification ID matches, the vehicle controller clears the current cycle of locking and unlocking, and delays the actual unlocking operation until the vehicle is powered on and started again.

[0011] Preferably, the method further includes a status feedback process: During the power-on operation of the vehicle controller, the vehicle controller periodically generates status messages, which include function activation status or deactivation status, current cycle lock status or current cycle unlock status, actual lock status or unlock status, identity ID matching status or mismatch status, handshake verification success status or failure status, and identity ID matching status or mismatch status. The vehicle controller sends the status message to the on-board remote controller terminal; The vehicle-mounted remote controller terminal forwards the status message to the vehicle remote monitoring platform for display.

[0012] The remote vehicle locking system includes a vehicle remote monitoring platform, an on-board remote controller terminal, a vehicle controller, and an instrument panel; The vehicle remote monitoring platform is configured to send activation commands, vehicle lock commands, vehicle unlock commands, and deactivation commands to the vehicle remote controller terminal. The vehicle-mounted remote controller terminal is configured to: receive instructions from the vehicle remote monitoring platform and forward them to the vehicle controller, and forward the status messages of the vehicle controller to the vehicle remote monitoring platform. The vehicle controller is configured as follows: Upon receiving an activation request, the system stores the identity ID of the vehicle remote controller terminal that sent the request as the unique binding identity ID, thus completing the binding activation. Upon receiving a vehicle lock request, the system compares the identity ID of the vehicle remote controller terminal that sent the request with the uniquely bound identity ID. If the identity IDs match, the system sets the current cycle for determining the vehicle lock status and triggers the instrument panel to display information that the vehicle is about to be locked. If the identity IDs do not match, the system sets the current cycle for determining the vehicle lock status and triggers the instrument panel to display information that the identity IDs do not match. In both cases, the actual vehicle lock operation is delayed until the vehicle is powered on and started again. If the current cycle for determining the vehicle lock status is detected when the vehicle is powered on and started, the vehicle speed is limited. During the power-on operation of the vehicle controller, the vehicle controller periodically generates status messages including function activation or deactivation status, current cycle lock status or current cycle unlock status, actual lock status or unlock status, ID matching status or mismatch status, handshake verification success status or failure status, and ID matching status or mismatch status, and sends them to the vehicle remote controller terminal. The instrument panel is configured to receive commands from the vehicle controller and display vehicle lock status information.

[0013] Preferably, the vehicle controller is also configured as follows: After binding and activation, a handshake verification is initiated immediately upon each power-on startup, and a handshake verification is initiated periodically during operation; The handshake verification includes: generating a random number seed and sending it to the vehicle remote controller terminal; verifying whether the key value returned by the vehicle remote controller terminal matches its own calculated value; If the first handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. After the vehicle is powered off and powered on again, the handshake verification is successful. The vehicle controller does not actually lock the vehicle and automatically clears the current cycle to determine the vehicle lock status and the verification failure record. If the initial handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. If the handshake fails again after the vehicle is powered off and powered on again, the vehicle controller will actually lock the vehicle and display the verification failure information on the instrument panel. That is, if the current cycle to determine the vehicle lock status is detected when the vehicle is powered on and started, the vehicle speed will be limited.

[0014] Preferably, the vehicle controller is also configured as follows: Upon receiving an unlock request and matching the identity ID, the current cycle for determining the vehicle lock status is cleared, and the actual unlocking operation is delayed until the vehicle is powered on and started again. Upon receiving a deactivation request and a matching identity ID, the vehicle locking function activation status is directly canceled, and the bound identity ID is cleared. If a vehicle locking status exists, the current cycle of determining the vehicle locking status is cleared, and the actual vehicle locking status is released.

[0015] An electronic device, characterized in that it comprises: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method.

[0016] A storage medium having a computer program stored thereon, characterized in that, when the program is executed by a processor, it implements the method described thereon.

[0017] A computer program product comprising a computer program, characterized in that, when executed by a processor, the program implements the method described.

[0018] The present invention has at least the following beneficial effects: First, in the active locking process of the remote vehicle locking method of this application, strict identity identification ID comparison ensures the legality of the command source, avoids unauthorized device control, and delays locking until the next power-on to prevent the safety hazard of sudden locking while driving; the passive locking process, through periodic handshake verification, can promptly detect communication anomalies and trigger locking, filling the gap in active locking scenarios; at the same time, the status feedback process periodically generates messages containing multiple statuses, allowing the platform to monitor vehicle dynamics in real time, solving the problem of delayed status information in traditional methods, and facilitating timely management.

[0019] Secondly, the remote vehicle locking system of this application includes a vehicle remote monitoring platform, an on-board remote controller terminal, a vehicle controller, and an instrument panel. The vehicle remote monitoring platform is responsible for issuing commands, the on-board remote controller terminal is responsible for command forwarding and status uploading, the vehicle controller performs core control and status acquisition, and the instrument panel provides intuitive display. The division of labor is clear, and the system uses encrypted communication to send and receive commands, ensuring efficient transmission of commands and status messages, thereby improving the overall system's controllability and security.

[0020] Other advantages, objectives and features of the present invention will become apparent in part from the following description, and in part from those skilled in the art through study and practice of the invention. Attached Figure Description

[0021] Figure 1 This is a schematic diagram illustrating the process of remotely locking a new energy vehicle, which is one technical solution of the present invention. Detailed Implementation

[0022] The present invention will now be described in further detail with reference to the accompanying drawings, so that those skilled in the art can implement it based on the description.

[0023] It should be understood that terms such as “having,” “comprising,” and “including” as used herein do not exclude the presence or addition of one or more other elements or combinations thereof.

[0024] It should be noted that, unless otherwise specified, the experimental methods described in the following embodiments are conventional methods, and the reagents and materials mentioned are commercially available. In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "setting" should be interpreted broadly. For example, they can refer to fixed connection or setting, detachable connection or setting, or integral connection or setting. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances. The terms "lateral," "longitudinal," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing this invention and simplifying the description. They do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this invention.

[0025] Existing remote vehicle locking methods suffer from lax authentication, leading to unauthorized locking. Furthermore, the timing of locking operations can be inappropriate, potentially affecting normal vehicle operation or posing safety risks. This invention provides a remote vehicle locking method applicable to both new energy vehicles and gasoline vehicles. New energy vehicles include electric vehicles and hybrid vehicles. In this application, when the vehicle is a new energy vehicle, the vehicle controller is a Vehicle Control Unit (VCU); when the vehicle is a gasoline vehicle, the vehicle controller is an Engine Control Unit (MCU). Its functions encompass both the Vehicle Control Unit (VCU) and the Engine Control Unit (ECU). For clarity, the term "vehicle controller" will be referred to as "VCU" / "engine controller" in the following text, and the term "telematicsBOX" (T-BOX) will be referred to as "T-BOX".

[0026] Remote vehicle locking methods include the active vehicle locking process: After the vehicle control unit (VCU) / engine control unit (MCU) and the vehicle remote controller terminal (T-BOX) are bound and activated, the vehicle remote monitoring platform sends a vehicle lock command to the vehicle remote controller terminal (T-BOX); After receiving the vehicle locking command, the vehicle remote controller terminal (T-BOX) forwards the vehicle locking request to the vehicle controller (VCU) / engine controller (MCU); After receiving the vehicle lock request, the vehicle controller (VCU) / engine controller (MCU) will retrieve the unique ID of the pre-stored bound and activated vehicle remote controller terminal (T-BOX) and compare whether the identity ID of the vehicle remote controller terminal (T-BOX) that sent the vehicle lock request is consistent with the unique identity ID of the pre-bound activated vehicle remote controller terminal (T-BOX). If the identification ID matches, the vehicle controller (VCU) / engine controller (MCU) sets the current cycle to determine the vehicle locking status, that is, in the current cycle, it is determined that the vehicle should be locked (but it is not actually locked). At the same time, a control signal is sent to the instrument panel via the CAN bus, and the information that the vehicle is about to be locked is displayed on the instrument panel to remind the user. If the identification ID does not match, the vehicle controller (VCU) / engine controller (MCU) sets the current cycle to determine the vehicle locking status. That is, in the current cycle, it is determined that the vehicle should be locked (but it is not actually locked). At the same time, a control signal is sent to the instrument panel via the CAN bus, and the identification ID mismatch information is displayed on the instrument panel to remind the user. Regardless of whether the identification IDs match, the Vehicle Control Unit (VCU) / Engine Control Unit (MCU) will not immediately perform the actual locking operation. Instead, the VCU / MCU will delay the actual locking operation until the vehicle is powered on and started again. When the vehicle is in motion or off, even if the VCU / MCU has set the current cycle for locking, it will not immediately restrict vehicle power or movement. When the vehicle is powered on again—that is, when the user inserts the key or presses the start button to turn on the vehicle—the VCU / MCU will check the current cycle for locking. If the check is present, the actual locking operation will be performed, and the VCU / MCU will control the speed within the speed limit.

[0027] The above technical solution standardizes the active vehicle locking process. Through strict identity verification, it ensures the legitimacy of the locking command source, effectively preventing illegal locking. The actual locking operation is delayed until the next power-on start-up, avoiding the safety hazards caused by sudden locking while the vehicle is in motion. At the same time, relevant information is displayed on the instrument panel, allowing users to understand the vehicle status in a timely manner, thus improving the security and reliability of remote vehicle locking.

[0028] When communication between the vehicle control unit (VCU) / engine controller (MCU) and the on-board remote controller terminal (T-BOX) malfunctions, the vehicle locking operation cannot be automatically triggered, potentially affecting normal vehicle operation or posing safety risks. In another technical solution, the method also includes a passive locking process. This passive locking process, as opposed to the active locking process, is not triggered by the vehicle remote monitoring platform actively sending a locking command, but rather by a communication anomaly between the vehicle control unit (VCU) / engine controller (MCU) and the on-board remote controller terminal (T-BOX). After the vehicle controller (VCU) / engine controller (MCU) and the vehicle remote controller terminal (T-BOX) are bound and activated, the vehicle controller (VCU) / engine controller (MCU) immediately initiates a handshake verification upon each power-on start-up to verify each other's identity and communication validity. During subsequent operation, it periodically initiates handshake verification, such as every 30 minutes, to continuously confirm whether the communication between the two is normal. If no response is received within the time limit or the response does not meet the requirements, it is recorded as a handshake failure. If the initial handshake fails, meaning the vehicle controller (VCU) / engine controller (MCU) does not receive a valid response from the on-board remote controller terminal (T-BOX) or the response is not satisfactory, the VCU / MCU sets the current cycle to determine the vehicle lock status. In other words, the current cycle determines that the vehicle should be locked. When the vehicle is powered on again, the VCU / MCU will immediately initiate a handshake verification. If the handshake verification is successful, the VCU / MCU will not actually lock the vehicle and will automatically clear the current cycle of determining the vehicle lock status and the verification failure record, so that the vehicle returns to normal. If the initial handshake fails, meaning the Vehicle Controller Unit (VCU) / Engine Controller Unit (MCU) does not receive a valid response from the Onboard Remote Controller Terminal (T-BOX) or the response is not satisfactory, the VCU / MCU sets the current cycle to determine the vehicle locking status. In other words, the current cycle determines that locking should be performed. When the vehicle is powered on again, the VCU / MCU will immediately initiate a handshake verification. If the handshake verification still fails, the VCU / MCU will perform the actual vehicle locking and simultaneously send a control signal to the instrument cluster via the CAN bus, displaying the verification failure information on the instrument cluster.

[0029] The above technical solution includes a passive vehicle locking process. By initiating a handshake verification immediately upon power-on and periodically during operation, communication anomalies between the vehicle controller (VCU) / engine controller (MCU) and the on-board remote controller terminal (T-BOX) can be detected in a timely manner. Based on the handshake verification results, appropriate processing is performed, and vehicle locking is triggered when multiple failures occur. This improves the accuracy and reliability of passive vehicle locking and enhances vehicle safety.

[0030] To further enhance the security of the handshake verification method, in another technical solution, the handshake verification includes: The vehicle controller (VCU) / engine controller (MCU) generates a random number seed and sends it to the vehicle remote controller terminal (T-BOX). The value of this seed is random and unique. The seed value generated for each handshake verification is different. During the transmission process, it is necessary to ensure that the seed is not tampered with. After receiving the seed, the vehicle remote controller terminal (T-BOX) will call its own stored fixed key, use its own fixed key and the random number seed to calculate the key value through an encryption algorithm, and return it to the vehicle controller (VCU) / engine controller (MCU). The encryption algorithm can be AES (Advanced Encryption Standard). The vehicle control unit (VCU) / engine control unit (MCU) verifies whether the returned key value matches its own calculated value to determine the success or failure of the handshake verification. If they match, the handshake verification is successful; if they do not match, the verification fails, and the verification result is recorded for subsequent vehicle locking process.

[0031] In the above technical solution, a dynamic encryption algorithm based on a random number seed and a fixed key is used for handshake verification, which improves the security and anti-cracking ability of the verification process, ensures the authenticity of the communication between the vehicle controller (VCU) / engine controller (MCU) and the vehicle remote controller terminal (T-BOX), effectively prevents illegal devices from spoofing communication, and ensures the reliability of handshake verification.

[0032] To avoid confusion caused by multiple vehicle remote controller terminals (T-BOX) operating the same vehicle, another technical solution includes an activation process: The vehicle remote monitoring platform sends an activation command to the vehicle remote controller terminal (T-BOX) based on the user's operation or system settings. This command is transmitted through a secure communication channel and contains relevant activation parameters and verification information. After receiving the activation command, the vehicle remote controller terminal (T-BOX) will parse the command, confirm its validity, and then send a vehicle locking function activation request to the vehicle controller (VCU) / engine controller (MCU). A frame check code is added to the request to ensure data integrity. After receiving the vehicle locking function activation request, the vehicle controller (VCU) / engine controller (MCU) verifies the information in the request to confirm its legality. If the verification is successful, it stores the identity ID of the vehicle remote controller terminal (T-BOX) that sent the request as a unique binding identity ID and a fixed key used for handshake verification, and returns activation success information to the vehicle remote controller terminal (T-BOX). The vehicle remote controller terminal (T-BOX) then forwards the information to the vehicle remote monitoring platform, and the vehicle controller (VCU) / engine controller (MCU) and the vehicle remote controller terminal (T-BOX) complete the binding activation.

[0033] The above technical solution standardizes the activation process and uses the unique identifier of the vehicle remote controller terminal (T-BOX) as the binding identifier to achieve a unique binding between the vehicle controller (VCU) / engine controller (MCU) and the specific vehicle remote controller terminal (T-BOX). This avoids confusion caused by multiple devices controlling the vehicle and provides a reliable identity basis for subsequent operations such as locking and unlocking the vehicle.

[0034] To prevent unauthorized deactivation, another technical solution includes a deactivation process. This deactivation process, in contrast to the activation process, terminates the remote vehicle locking function and releases the binding between the vehicle controller (VCU) / engine controller (MCU) and the onboard remote controller terminal (T-BOX). The vehicle remote monitoring platform sends a deactivation command to the vehicle remote controller terminal (T-BOX). This command is also transmitted through a secure communication channel and includes relevant deactivation parameters and verification information. After receiving the deactivation command, the vehicle remote controller terminal (T-BOX) will parse the command, confirm its validity, and send a deactivation request to the vehicle controller (VCU) / engine controller (MCU). The request includes a frame checksum to ensure data integrity. After receiving a deactivation request, the vehicle control unit (VCU) / engine control unit (MCU) will verify the information in the request to confirm its legality. If the verification is successful, it will compare the identity ID of the vehicle remote controller terminal (T-BOX) that sent the request with the bound identity ID. If the identity ID matches, the Vehicle Controller Unit (VCU) / Engine Controller Unit (MCU) will directly cancel the vehicle locking function activation state, meaning the remote vehicle locking function will no longer be effective. The VCU / MCU will also directly clear the bound identity ID and unbind the VCU / MCU from the vehicle remote controller terminal (T-BOX). If a vehicle is locked, whether it is currently in a loop to determine the locking state or is actually locked, the VCU / MCU will directly clear the current loop to determine the locking state and release the actual locking state, restoring the vehicle to a normal usable state.

[0035] The above technical solution standardizes the deactivation process, prevents unauthorized deactivation by strictly comparing identity information, and completely removes binding information and vehicle lock status during deactivation to ensure the vehicle returns to normal status and guarantee the safety and standardization of vehicle use.

[0036] To balance the effectiveness and security of vehicle locking, another technical solution involves the actual locking operation as follows: the vehicle controller limits the vehicle speed to 0 km / h or restricts the vehicle speed to a low speed range. This low speed range refers to the speed range below the normal operating speed of the vehicle, affecting its normal operation. Specifically, the vehicle control unit (VCU) / engine control unit (MCU) limits the vehicle speed, controlling it to stop or restrict its speed to a range below normal operating speed. Preferably, the VCU / MCU limits the speed to 5-10 km / h. During this restriction process, the VCU / MCU monitors the vehicle speed in real time and dynamically adjusts the control of the power system based on speed changes, ensuring the speed remains stable within the set range. This preserves the vehicle's basic mobility, meeting the needs of moving the vehicle while preventing normal operations, thus improving the practicality of the locking operation.

[0037] To prevent unauthorized unlocking, another technical solution includes an unlocking process, which, in contrast to the locking process, involves releasing the vehicle from its locked state and restoring its normal driving capability. The vehicle remote monitoring platform sends an unlock command to the on-board remote controller terminal (T-BOX). This command is also transmitted through a secure communication channel and may include the vehicle's unique identifier (ID) and timestamp. After receiving the unlock command, the vehicle remote controller terminal (T-BOX) will parse the command, confirm its validity, and send an unlock request to the vehicle controller (VCU) / engine controller (MCU). A frame check code is added to the request to ensure data integrity. After receiving the unlock request, the vehicle control unit (VCU) / engine control unit (MCU) will verify the information in the request to confirm its legality. If the verification is successful, it will compare the identity ID of the vehicle remote controller terminal (T-BOX) that sent the request with the bound identity ID. If the identification ID matches, the Vehicle Controller Unit (VCU) / Engine Controller Unit (MCU) clears the current cycle of locking status, indicating that the unlocking request is valid. Similar to the locking operation, the actual unlocking operation is not executed immediately, but is delayed until the next time the vehicle is powered on and started. When the vehicle is powered on and started again, the VCU / MCU will check the flag indicating the current cycle of unlocking status. If the flag exists, the actual locking operation is executed, and the vehicle returns to normal driving status, and the vehicle speed is no longer limited as before.

[0038] The above technical solution standardizes the unlocking process, ensures the legality of the unlocking command through identity verification, and delays the actual unlocking operation until the next power-on startup, thus ensuring the security and rationality of the unlocking operation and preventing the risks caused by unauthorized unlocking.

[0039] In existing remote vehicle locking methods, the vehicle remote monitoring platform and the user cannot obtain timely information about the vehicle's various statuses. In another technical solution, such as... Figure 1 As shown (taking a new energy vehicle as an example, the vehicle controller is the vehicle control unit (VCU)), the method also includes a status feedback process, where the vehicle control unit (VCU) / engine control unit (MCU) sends various status information of the vehicle to the remote monitoring platform: During the power-on operation of the vehicle controller (VCU) / engine controller (MCU), the VCU / engine controller (MCU) periodically generates status messages, for example every 100ms, which are assembled according to a preset format (such as frame header, data segment, check bit). The status messages include function activation or deactivation status, current cycle determination of vehicle locking or current cycle determination of vehicle unlocking status, actual vehicle locking or unlocking status, ID matching or mismatch status, handshake verification success or failure status, and ID matching or mismatch status. In other words, whether the remote vehicle locking function is activated, whether the vehicle should be locked or unlocked in the current cycle; whether the vehicle is actually locked; whether the bound vehicle remote controller terminal (T-BOX) is matched; and whether the communication between the VCU / engine controller (MCU) and the vehicle remote controller terminal (T-BOX) is normal. The vehicle control unit (VCU) / engine control unit (MCU) sends the status message to the on-board remote controller terminal (T-BOX); The vehicle-mounted remote controller terminal (T-BOX) forwards the status messages to the vehicle remote monitoring platform for display, such as through text (e.g., activated, currently in a cycle of locking) or charts (e.g., a red indicator light for the actual locking status), making it convenient for platform administrators to view.

[0040] In the above technical solution, a status feedback process is established. The vehicle controller (VCU) / engine controller (MCU) periodically generates messages containing multiple statuses and forwards them to the monitoring platform, enabling the platform and users to grasp the various statuses of the vehicle in real time, facilitating vehicle monitoring and management, and improving the controllability of the remote vehicle locking system.

[0041] The remote vehicle locking system includes a vehicle remote monitoring platform, an on-board remote controller terminal (T-BOX), a vehicle control unit (VCU) / engine controller (MCU), and an instrument cluster; The vehicle remote monitoring platform is configured to send activation commands, vehicle lock commands, unlock commands, and deactivation commands to the vehicle remote controller terminal (T-BOX) according to user operations or system settings. The vehicle-mounted remote controller terminal (T-BOX) is configured to: receive instructions from the vehicle remote monitoring platform via wireless communication, including activation instructions, vehicle locking instructions, unlocking instructions, and deactivation instructions; verify the instructions; and forward them to the vehicle controller (VCU) / engine controller (MCU) after confirming that they are correct; receive status messages sent by the vehicle controller (VCU) / engine controller (MCU); and forward the status messages of the vehicle controller (VCU) / engine controller (MCU) to the vehicle remote monitoring platform. The vehicle control unit (VCU) / engine control unit (MCU) is configured as follows: Upon receiving the activation request, the request will be verified. The identity ID of the vehicle remote controller terminal (T-BOX) that sent the request will be stored as the unique binding identity ID to complete the binding activation. Upon receiving a vehicle lock request, the system compares the identity ID of the vehicle remote controller terminal (T-BOX) that sent the request with the uniquely bound identity ID. If the identity IDs match, the system sets the current cycle to determine the vehicle lock status, meaning that the current cycle determines that locking should be performed (but the vehicle is not actually locked). At the same time, a control signal is sent to the instrument panel, and the instrument panel displays information indicating that the vehicle is about to be locked, alerting the user and triggering the instrument panel to display the information indicating that the vehicle is about to be locked. If the identity IDs do not match, the system sets the current cycle to determine the vehicle lock status, meaning that the current cycle determines that locking should be performed (but the vehicle is not actually locked). At the same time, a control signal is sent to the instrument panel, and the instrument panel displays information indicating that the identity IDs do not match, alerting the user. In both cases, the actual vehicle lock operation is delayed until the next time the vehicle is powered on and started. When the vehicle is powered on and started again, the vehicle controller (VCU) / engine controller (MCU) will detect the current cycle lock status flag. If the flag exists, the actual vehicle lock operation is performed, i.e., the vehicle speed is limited. During the power-on operation of the vehicle controller (VCU) / engine controller (MCU), the vehicle controller (VCU) / engine controller (MCU) periodically generates status messages including function activation or deactivation status, current cycle lock status or current cycle unlock status, actual lock status or unlock status, ID matching status or mismatch status, handshake verification success status or failure status, and ID matching status or mismatch status, and sends them to the vehicle remote controller terminal (T-BOX); The instrument panel is configured to receive commands from the vehicle control unit (VCU) / engine control unit (MCU) and display corresponding information, such as vehicle lock status information, based on the command content.

[0042] In the above technical solution, the various parts of the remote vehicle locking system work together to reliably realize the functions of remote vehicle locking activation, locking, unlocking, and deactivation, thereby improving the overall performance of the remote vehicle locking function and ensuring the safety and accuracy of remote vehicle locking operations.

[0043] In another technical solution, the vehicle control unit (VCU) / engine control unit (MCU) is also configured as follows: After binding and activation, a handshake verification is initiated immediately upon each power-on startup, and a handshake verification is initiated periodically during operation; The handshake verification includes: generating a random number seed and sending it to the vehicle-mounted remote controller terminal (T-BOX); verifying whether the key value returned by the vehicle-mounted remote controller terminal (T-BOX) matches its own calculated value; If the first handshake fails, the vehicle controller (VCU) / engine controller (MCU) sets the current cycle to determine the vehicle lock status. After the vehicle is powered off and powered on again, the handshake verification is successful. The vehicle controller (VCU) / engine controller (MCU) does not actually lock the vehicle and automatically clears the current cycle to determine the vehicle lock status and the verification failure record. If the initial handshake fails, the vehicle controller (VCU) / engine controller (MCU) sets the current cycle to determine the vehicle lock status. If the handshake fails again after the vehicle is powered off and powered on again, the vehicle controller (VCU) / engine controller (MCU) will perform the actual vehicle lock and display the verification failure information on the instrument panel. That is, if the current cycle to determine the vehicle lock status is detected when the vehicle is powered on and started, the vehicle speed will be limited.

[0044] The above technical solution can promptly detect communication anomalies between the vehicle controller (VCU) / engine controller (MCU) and the vehicle remote controller terminal (T-BOX). By verifying the communication using a random number seed and encryption algorithm, the security of the communication is improved. Based on the verification results, corresponding processing is performed, and the vehicle is locked when multiple failures occur, further ensuring the safety of the vehicle.

[0045] In another technical solution, the vehicle control unit (VCU) / engine control unit (MCU) is also configured as follows: Upon receiving an unlock request and matching the identity ID, the current cycle for determining the vehicle lock status is cleared, and the actual unlocking operation is delayed until the vehicle is powered on and started again. Upon receiving a deactivation request and a matching identity ID, the vehicle locking function activation status is directly canceled, and the bound identity ID is cleared. If a vehicle locking status exists, the current cycle of determining the vehicle locking status is cleared, and the actual vehicle locking status is released.

[0046] In the above technical solution, strict identity verification prevents unauthorized unlocking and deactivation operations, ensuring that only authorized vehicle remote controller terminals (T-BOX) can perform these operations, thus guaranteeing vehicle security.

[0047] The present invention also provides an electronic device, comprising: at least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described thereon. This electronic device can be any terminal device including mobile phones, laptops, desktop computers, tablets, PDAs (Personal Digital Assistants), POS (Point of Sales) terminals, in-vehicle computers, etc.

[0048] This invention also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the method described above. Through the above description of the embodiments, those skilled in the art can clearly understand that this invention can be implemented using software plus necessary general-purpose hardware, or it can be implemented using dedicated hardware including dedicated integrated circuits, dedicated CPUs, dedicated memory, dedicated components, etc. Generally, any function performed by a computer program can be easily implemented using corresponding hardware, and the specific hardware structure used to implement the same function can be diverse, such as analog circuits, digital circuits, or dedicated circuits. However, for this invention, software program implementation is often a better implementation method. Based on this understanding, the technical solution of this invention, 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 readable storage medium, such as a computer floppy disk, USB flash drive, portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this invention.

[0049] This invention also provides a computer program product comprising a computer program that, when executed by a processor, implements the method described. The computer program (which may also be referred to or described as a program, software, software application, module, software module, script, or code) can be written in any form of programming language, including compiled languages, interpreted languages, declarative languages, or procedural languages, and can be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program may, but does not necessarily, correspond to a file in a file system. The program can be stored as a portion of a file containing other programs or data, for example, as one or more scripts in a markup language document; in a single file dedicated to the related program; or in multiple co-files, for example, a file storing one or more modules, subroutines, or code portions. The computer program can be deployed to execute on one or more computers located in one place or distributed across multiple locations and interconnected via a communication network. The processing and logic flows described in this specification can be executed by one or more programmable computers that execute one or more computer programs by processing input data and generating output to run functions.

[0050] The number of devices and processing scale described herein are for the purpose of simplifying the description of the invention. Applications, modifications, and variations of the invention will be readily apparent to those skilled in the art.

[0051] Although embodiments of the present invention have been disclosed above, they are not limited to the applications listed in the specification and embodiments. They can be applied to various fields suitable for the present invention. For those skilled in the art, other modifications can be easily made. Therefore, without departing from the general concept defined by the claims and their equivalents, the present invention is not limited to the specific details and illustrations shown and described herein.

Claims

1. A remote vehicle locking method, characterized in that, Including the active vehicle locking process: After the vehicle controller and the vehicle remote controller terminal are bound and activated, the vehicle remote monitoring platform sends a vehicle lock command to the vehicle remote controller terminal. After receiving the vehicle locking command, the vehicle remote controller terminal forwards the locking request to the vehicle controller; After receiving the vehicle lock request, the vehicle controller compares whether the identity ID of the vehicle remote controller terminal that sent the lock request is consistent with the unique identity ID of the pre-bound activated vehicle remote controller terminal. If the identity ID matches, the vehicle controller sets the current cycle to determine the vehicle locking status and displays the information that the vehicle is about to be locked on the instrument panel. If the identity ID does not match, the vehicle controller will set the current cycle to determine the vehicle locking status and display the identity ID mismatch information on the instrument panel. The vehicle controllers all delay the actual locking operation until the vehicle is powered on and started again; When the vehicle is a new energy vehicle, the vehicle controller is the whole vehicle controller; When the vehicle is an oil-powered vehicle, the vehicle controller is the engine controller.

2. The remote vehicle locking method according to claim 1, characterized in that, The method also includes a passive vehicle locking process: After the vehicle controller and the vehicle remote controller terminal are bound and activated, the vehicle controller will initiate a handshake verification immediately upon each power-on start-up, and will periodically initiate a handshake verification during subsequent operation. If the first handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. After the vehicle is powered off and powered on again, the handshake verification is successful. The vehicle controller does not actually lock the vehicle and automatically clears the current cycle to determine the vehicle lock status and the verification failure record. If the initial handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. If the handshake fails again after the vehicle is powered off and powered on again, the vehicle controller will actually lock the vehicle and display the verification failure information on the instrument panel.

3. The remote vehicle locking method according to claim 2, characterized in that, The handshake verification includes: The vehicle controller generates a random number seed and sends it to the on-board remote controller terminal. The vehicle-mounted remote controller terminal uses its own fixed key and the random number seed to calculate the key value through an encryption algorithm and returns it. The vehicle controller verifies whether the returned key value matches its own calculated value.

4. The remote vehicle locking method according to claim 1 or 2, characterized in that, The method also includes an activation process: The vehicle remote monitoring platform sends an activation command to the on-board remote controller terminal; After receiving the activation command, the vehicle remote controller terminal sends a vehicle locking function activation request to the vehicle controller; After receiving the vehicle locking function activation request, the vehicle controller stores the identity ID of the vehicle remote controller terminal that sent the request as a unique binding identity ID and a fixed key used for handshake verification, and returns activation success information to the vehicle remote controller terminal. The vehicle controller and the vehicle remote controller terminal complete the binding activation.

5. The remote vehicle locking method according to claim 4, characterized in that, The method also includes a deactivation process: The vehicle remote monitoring platform sends a deactivation command to the on-board remote controller terminal; After receiving the deactivation command, the vehicle remote controller terminal sends a deactivation request to the vehicle controller; After receiving the deactivation request, the vehicle controller compares the identity ID of the vehicle remote controller terminal that sent the request with the bound identity ID. If the identity ID matches, the vehicle controller will directly cancel the vehicle locking function activation state and clear the bound identity ID. If a vehicle is locked, the current cycle of locking status will be cleared and the actual locking status will be released.

6. The remote vehicle locking method according to claim 1 or 2, characterized in that, The actual vehicle locking operation is as follows: The vehicle controller limits the vehicle speed to 0 km / h or the vehicle controller limits the vehicle speed to a low speed range, wherein the low speed range refers to the speed range that affects the normal operation of the vehicle and is lower than the normal operation speed of the vehicle.

7. The remote vehicle locking method according to claim 1 or 2, characterized in that, The method also includes an unlocking process: The vehicle remote monitoring platform sends an unlock command to the on-board remote controller terminal; After receiving the unlock command, the vehicle remote controller terminal sends an unlock request to the vehicle controller; After receiving the unlock request, the vehicle controller compares the identity ID of the vehicle remote controller terminal that sent the request with the bound identity ID. If the identification ID matches, the vehicle controller clears the current cycle of locking and unlocking, and delays the actual unlocking operation until the vehicle is powered on and started again.

8. The remote vehicle locking method according to claim 1 or 2, characterized in that, The method also includes a status feedback process: During the power-on operation of the vehicle controller, the vehicle controller periodically generates status messages, which include function activation status or deactivation status, current cycle lock status or current cycle unlock status, actual lock status or unlock status, identity ID matching status or mismatch status, handshake verification success status or failure status, and identity ID matching status or mismatch status. The vehicle controller sends the status message to the on-board remote controller terminal; The vehicle-mounted remote controller terminal forwards the status message to the vehicle remote monitoring platform for display.

9. A remote vehicle locking system, characterized in that, This includes a vehicle remote monitoring platform, an on-board remote controller terminal, a vehicle controller, and instruments; The vehicle remote monitoring platform is configured to send activation commands, vehicle lock commands, vehicle unlock commands, and deactivation commands to the vehicle remote controller terminal. The vehicle-mounted remote controller terminal is configured to: receive instructions from the vehicle remote monitoring platform and forward them to the vehicle controller, and forward the status messages of the vehicle controller to the vehicle remote monitoring platform. The vehicle controller is configured as follows: Upon receiving an activation request, the system stores the identity ID of the vehicle remote controller terminal that sent the request as the unique binding identity ID, thus completing the binding activation. Upon receiving a vehicle lock request, the system compares the identity ID of the vehicle remote controller terminal that sent the request with the uniquely bound identity ID. If the identity IDs match, the system sets the current cycle for determining the vehicle lock status and triggers the instrument panel to display information that the vehicle is about to be locked. If the identity IDs do not match, the system sets the current cycle for determining the vehicle lock status and triggers the instrument panel to display information that the identity IDs do not match. In both cases, the actual vehicle lock operation is delayed until the vehicle is powered on and started again. If the current cycle for determining the vehicle lock status is detected when the vehicle is powered on and started, the vehicle speed is limited. During the power-on operation of the vehicle controller, the vehicle controller periodically generates status messages including function activation or deactivation status, current cycle lock status or current cycle unlock status, actual lock status or unlock status, ID matching status or mismatch status, handshake verification success status or failure status, and ID matching status or mismatch status, and sends them to the vehicle remote controller terminal. The instrument panel is configured to receive commands from the vehicle controller and display vehicle lock status information.

10. The remote vehicle locking system according to claim 9, characterized in that, The vehicle controller is also configured as follows: After binding and activation, a handshake verification is initiated immediately upon each power-on startup, and a handshake verification is initiated periodically during operation; The handshake verification includes: generating a random number seed and sending it to the vehicle remote controller terminal; verifying whether the key value returned by the vehicle remote controller terminal matches its own calculated value; If the first handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. After the vehicle is powered off and powered on again, the handshake verification is successful. The vehicle controller does not actually lock the vehicle and automatically clears the current cycle to determine the vehicle lock status and the verification failure record. If the initial handshake fails, the vehicle controller sets the current cycle to determine the vehicle lock status. If the handshake fails again after the vehicle is powered off and powered on again, the vehicle controller will actually lock the vehicle and display the verification failure information on the instrument panel. That is, if the current cycle to determine the vehicle lock status is detected when the vehicle is powered on and started, the vehicle speed will be limited.

11. The remote vehicle locking system according to claim 9, characterized in that, The vehicle controller is also configured as follows: Upon receiving an unlock request and matching the identity ID, the current cycle for determining the vehicle lock status is cleared, and the actual unlocking operation is delayed until the vehicle is powered on and started again. Upon receiving a deactivation request and a matching identity ID, the vehicle locking function activation status is directly canceled, and the bound identity ID is cleared. If a vehicle locking status exists, the current cycle of determining the vehicle locking status is cleared, and the actual vehicle locking status is released.

12. An electronic device, characterized in that, include: At least one processor, and a memory communicatively connected to the at least one processor, wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method according to any one of claims 1-8.

13. A storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 1-8.

14. A computer program product comprising a computer program, characterized in that, When the program is executed by the processor, it implements the method described in any one of claims 1-8.

Images