Locking control method, device and equipment for leasing vehicle and storage medium

Abstract

This invention provides a method, apparatus, device, and storage medium for locking vehicles in rental vehicles, relating to the field of vehicle control technology. The locking control system includes: a display, a controller, and an onboard telematics terminal (TBOX), with the display and controller connected via a CAN bus. The method includes: when the locking control system is powered on, the controller and display perform mutual verification based on a bound vehicle identifier; if the vehicle identifier bound to the display and controller is inconsistent, the controller sends an operation restriction command to the vehicle power control system; otherwise, the controller determines the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is zero, sends an operation restriction command to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power. This invention can improve the accuracy of locking control.

Description

Technical Field

[0001] This invention relates to the field of vehicle control technology, particularly to the field of vehicle rental technology, and especially to a locking control method, device, equipment, and storage medium for rental vehicles. Background Technology

[0002] Because large specialized vehicles such as drilling rigs are valuable, their sales and operation methods include full payment, installment payments, and leasing. Therefore, for loan and leasing businesses, the usage period of the vehicles must be precisely controlled according to the sales contract, while ensuring that customers can take emergency evasive action in dangerous working conditions. Even in special working environments such as mining areas with no or poor network communication, the vehicles can still operate normally, providing property and technical security for loan and leasing customers.

[0003] For loan and leasing businesses, when the vehicle lock-up date arrives, a lock-up command is issued remotely via a Telematics Box (TBOX) platform. However, in special working environments such as mining areas with no or poor network connectivity, remote wireless locking may experience TBOX signal loss or offline malfunctions, making it impossible to accurately control the rental period and thus preventing the vehicle from operating normally. Furthermore, loan and leasing customers may privately replace displays and controllers without locking functionality during the lease term, resulting in the inability to lock the vehicle on the designated lock-up date. Therefore, a solution is needed to improve the accuracy of vehicle lock-up control for rental vehicles. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and storage medium for locking rental vehicles, in order to address the problem of improving the accuracy of locking control for rental vehicles.

[0005] In a first aspect, embodiments of the present invention provide a locking control method for rental vehicles. The locking control system includes: a display, a controller, and a TBOX, wherein the display and the controller are connected via a CAN bus communication connection; the method includes: When the vehicle locking control system is powered on, it performs mutual verification with the display based on the bound vehicle identifier; When the vehicle identifier bound to the display and the controller is inconsistent, an operation restriction command is sent to the vehicle power control system. When the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

[0006] In one possible implementation, before determining the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier, the method further includes: Determine if the local system time is the set standard time; When the local system time is not the set standard time, the standard time signal is obtained from the TBOX and the local system time is corrected to the standard time; otherwise, the operation of determining the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier is performed.

[0007] In one possible implementation, prior to mutual verification with the display based on the bound vehicle identifier, the method further includes: Determine whether the controller and the display are bound to a vehicle identifier; When both the controller and the display are bound to a vehicle identifier, a mutual verification operation based on the bound vehicle identifier is performed with the display; otherwise, the bound vehicle identifier is sent to the display, or the vehicle identifier bound to the display is obtained and the binding is completed.

[0008] One possible implementation also includes: When sending the bound vehicle identifier to the display, the agreed usage time corresponding to the vehicle identifier is also sent to the display; When the vehicle identifier bound to the display is obtained and the binding is completed, the agreed usage time corresponding to the vehicle identifier stored on the display is obtained.

[0009] One possible implementation also includes: Obtain rental day request information, generate a random verification code based on the rental day request information, send it to the display, and send the random verification code and vehicle identifier to the TBOX, which then forwards it to the remote management platform; In response to a key entered by a staff member via the display, the agreed usage time stored on the display and the controller is updated; wherein, the key is generated by the remote management platform based on the contractually agreed usage date corresponding to the random verification code and the vehicle identifier.

[0010] In one possible implementation, the types of operation restriction commands include rock drill power output restriction commands, air compressor power restriction commands, and travel pump power output restriction commands.

[0011] One possible implementation also includes: During the period when the operation restriction command is in effect, if an emergency avoidance command is received triggered by the physical emergency button or the set emergency password, the driving power output will be restored, and the vehicle will be locked again after a set time or after the vehicle has moved a preset distance.

[0012] One possible implementation also includes: When it is determined that the vehicle usage information corresponding to the vehicle identifier is a full payment purchase mode, the calculation of remaining usage time and the generation of operation restriction instructions are prohibited.

[0013] One possible implementation also includes: When the remaining usage time is less than or equal to a first threshold, the controller controls the display to issue an initial reminder; When the remaining usage time is less than or equal to the second threshold, the display is controlled to provide an enhanced reminder.

[0014] One possible implementation also includes: Upon receiving a vehicle unlocking command forwarded by the remote management platform via the TBOX, a mutual verification step is performed between the display and the controller based on the bound vehicle identifier. If the vehicle identifier bound to the display and the controller are consistent, the vehicle is unlocked. Upon receiving a vehicle locking command or operation restriction command forwarded by the TBOX from the remote management platform, the corresponding control command is executed.

[0015] Secondly, embodiments of the present invention provide a vehicle locking control device for rental vehicles. The vehicle locking control system includes: a display, a controller, and a TBOX, wherein the display and the controller are connected via a CAN bus communication connection; the device includes: The verification module is used to perform mutual verification with the display based on the bound vehicle identifier when the vehicle locking control system is powered on. The control module is used to send an operation restriction command to the vehicle power control system when the vehicle identifier bound to the display and the controller is inconsistent. When the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

[0016] Thirdly, embodiments of the present invention provide an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method described in the first aspect or any possible implementation thereof.

[0017] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect or any possible implementation thereof.

[0018] Fifthly, embodiments of the present invention provide a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect or any possible implementation thereof.

[0019] In this embodiment of the invention, the vehicle locking control system establishes a communication connection between the display and the controller based on the CAN bus. Upon power-up, the system first performs mutual verification of the bound vehicle identifiers. If the identifiers are inconsistent, an operation restriction command is sent directly. If the identifiers are consistent, the remaining usage time is determined based on the system time and the agreed usage time. When the remaining time is zero, the operation restriction command is triggered. This solution effectively prevents customers from privately replacing the display or controller to circumvent the vehicle locking control through the binding and verification of the vehicle identifiers. At the same time, it does not rely on a stable network and can achieve precise control over the usage period of the rental vehicle through local logic interaction. The operation restriction command specifically restricts the relevant power output, which not only ensures precise vehicle locking control but also reserves space for emergency avoidance operations, thereby improving the safety of use. Attached Figure Description

[0020] Figure 1 This is an application scenario diagram of a vehicle locking control method for rental vehicles provided in an embodiment of the present invention; Figure 2 This is a flowchart illustrating the implementation of a vehicle locking control method for rental vehicles according to an embodiment of the present invention. Figure 3 This is an interactive flowchart of a vehicle locking control method for rental vehicles provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of a vehicle locking control device for rental vehicles provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0021] With the continuous expansion of leasing business in the engineering construction field, the leasing management of high-value engineering vehicles faces multiple challenges, including complex network environments such as mining areas and remote construction sites with poor network communication, the need for precise control over usage periods, and the need to ensure safety and risk avoidance in emergency situations. The vehicle locking control method for leased vehicles provided in this application primarily focuses on drilling rigs, addressing core requirements such as time management during leasing, prevention of unauthorized component replacement, and adaptation to harsh environments. In practical implementation, it is also applicable to various engineering leasing vehicles such as excavators, loaders, cranes, and engineering transport vehicles, as well as other high-value leasing vehicles requiring strict control over their leasing periods or other leasing items with display functions. This application primarily uses leased vehicles as an example for illustration.

[0022] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0023] Figure 1 This diagram illustrates an application scenario of the vehicle locking control method for rental vehicles provided in an embodiment of the present invention. Figure 1 As shown, the rental vehicle's driver's cab is equipped with a display (serving as an operation and notification terminal). The controller is integrated into the vehicle control system and communicates with the display via a CAN bus. The TBOX module is responsible for remote signal interaction, and the system is also linked with the vehicle's power control system (including power output units such as rock drills, air compressors, and travel pumps). The display and controller establish a communication connection via the CAN bus. Leveraging the CAN bus's strong anti-interference capabilities and stable data transmission, the system ensures reliable real-time interaction between the display and controller even with communication delays from the TBOX module in weak network environments. This eliminates the need for traditional TBOX module-based vehicle locking solutions and improves the accuracy of vehicle locking control.

[0024] During operation, after the drilling rig is powered on, the controller first verifies the bound vehicle identifier with the display. If not bound, it automatically synchronizes the identifier with the agreed usage time. For non-standard times, the system time is obtained and corrected via the TBOX to ensure accurate rental period calculation. Upon expiration, the system sends targeted operation restriction commands, cutting off core operational power output but retaining power for auxiliary actions such as hazard avoidance and rod disconnection. For renewal, staff initiate a rental days request via the display. The system generates a random verification code and forwards it to the remote management platform. Entering the exclusive key returned by the platform updates the usage time. Local autonomous control is supported in weak network environments. Locking and unlocking commands from the remote management platform can be received via the TBOX. Unlocking requires re-verification of the vehicle identifier to ensure security.

[0025] In addition, among other possible implementation methods, a physical emergency button is provided under the cab or on the outer panel of the slewing platform. In case of an emergency while the vehicle is locked, pressing the physical emergency button or entering the set emergency password can temporarily restore driving power. After the vehicle has moved a preset distance or a set time, the vehicle will automatically return to the locked state, fully adapting to the diverse control needs in engineering construction.

[0026] Figure 2 This is a flowchart illustrating the implementation of a vehicle locking control method for rental vehicles according to an embodiment of the present invention, as shown below. Figure 2 The steps shown are as follows: S201, when the vehicle locking control system is powered on, performs mutual verification with the display based on the bound vehicle identifier.

[0027] The execution entity in the various embodiments of this application can be a server, processor, microprocessor, or other device with data processing capabilities. In actual implementation, the specific implementation method of the execution entity can be selected according to actual needs, as long as it is a device with data processing capabilities. This embodiment uses... Figure 1 The controller shown is used as an example for explanation.

[0028] Upon initial power-on initialization or each subsequent power-on initialization, the controller and display synchronously enter the working state and initiate a mutual verification process. The verification process revolves around the pre-bound vehicle identifier, which uniquely identifies the corresponding rental vehicle and is pre-stored in the local storage units of both the controller and the display. The controller first sends its stored vehicle identifier to the display. The display receives this identifier and compares it with its locally stored identifier. Simultaneously, the display also sends its stored vehicle identifier back to the controller. The controller completes the comparison synchronously, ensuring the consistency of the identifier information through bidirectional verification.

[0029] Among them, the vehicle identifier is a unique identification information associated with the corresponding vehicle. It can be preset when the vehicle leaves the factory, or configured and entered into the system by staff during the leasing business process. Its function is to establish a unique correspondence between the controller, the display and the target vehicle.

[0030] S202, when the vehicle identifier bound to the display and the controller is inconsistent, an operation restriction command is sent to the vehicle power control system.

[0031] S203, when the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

[0032] When the two-way verification result shows that the vehicle identifier bound to the display and the controller is inconsistent, it indicates that there may be a component replacement or abnormal matching in the current system. The controller immediately generates an operation restriction command and sends it to the vehicle power control system to prevent the vehicle from being used illegally by limiting the relevant power output.

[0033] When the bidirectional verification result shows that the vehicle identifier matches, the controller enters the usage time management process. The controller obtains the locally stored system time and simultaneously retrieves the agreed usage time corresponding to the vehicle identifier. The agreed usage time is the clearly defined usage period of the vehicle in the leasing business. Through logical operations between the system time and the agreed usage time, the current remaining usage time of the vehicle is determined, specifically by subtracting the used time from the agreed usage time. The controller monitors the changes in the remaining usage time in real time. When the remaining usage time decreases to zero, it indicates that the vehicle has exceeded the agreed usage period. The controller then generates an operation restriction command and sends it to the vehicle power control system.

[0034] Operational restriction commands are used to specifically limit the power output of vehicles. Depending on actual usage needs, users can choose to restrict the vehicle's driving power output, or restrict other operating power outputs besides driving power, or restrict both types of power outputs simultaneously. This achieves the purpose of controlling the rental period while reserving flexible space for necessary operations in special scenarios, ensuring the safety and rationality of the usage process.

[0035] For example, for engineering rental vehicles such as drilling rigs, their driving power mainly relies on the power output of the travel pump, while the working power corresponds to the power supply of the rock drill and air compressor. In this case, if only the working power output is restricted, the drilling rig will not be able to carry out core operations such as rock drilling and hole drilling, but the basic power of the travel pump can be retained to achieve short-distance movement for hazard avoidance or equipment repositioning. If only the driving power output is restricted, the drilling rig cannot move, but a small working power can be temporarily used to complete the finishing operations of the started process. If both types of power are restricted at the same time, the drilling rig can neither work nor move. This is suitable for scenarios where the rental period has completely expired, ensuring the safety of company property.

[0036] For engineering rental vehicles such as forklifts, the driving power corresponds to the hydraulic power of the walking system, and the working power is the hydraulic power for lifting and tilting the bucket. When the working power is restricted alone, the forklift cannot perform loading and unloading operations, but can move a short distance to a safe area. When the driving power is restricted alone, the forklift can adjust the bucket status to complete the temporary organization of the current materials. Restricting both types of power at the same time achieves complete operation and movement control, matching the needs of different rental control stages.

[0037] For car rental vehicles, the driving power comes from the engine or electric drive system. If it is a regular rental car, the operation restriction commands will mostly restrict the driving power output, cut off the drive system power to make it unable to move, while retaining basic in-vehicle functions such as air conditioning and window control. If it is a special rental car equipped with testing equipment, the operating power corresponds to the power supply of the testing equipment. In this case, the power output of the testing equipment can be restricted separately, so that the vehicle can be moved normally but cannot carry out testing operations, which is suitable for the control needs of temporarily adjusting the use of the vehicle.

[0038] In this embodiment, the vehicle locking control system establishes a communication connection between the display and the controller via a CAN bus. Upon power-up, it first performs mutual verification of the bound vehicle identifiers. If the identifiers do not match, it directly sends an operation restriction command. If the identifiers match, it determines the remaining usage time based on the system time and the agreed usage time. When the remaining time is zero, it triggers the operation restriction command. This solution effectively prevents customers from privately replacing the display or controller to circumvent the vehicle locking control by binding and verifying the vehicle identifiers. At the same time, it does not rely on a stable network and can achieve precise control over the usage period of the rental vehicle through local logic interaction. The operation restriction command specifically restricts the relevant power output, which not only ensures precise vehicle locking control and protects the company's property, but also reserves space for emergency avoidance operations, thereby improving the safety of use.

[0039] In one possible implementation, before determining the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier, the following is also included: Determine if the local system time is the set standard time; When the local system time is not the set standard time, the standard time signal is obtained from the TBOX and the local system time is corrected to the standard time; otherwise, the operation of determining the remaining usage time is performed based on the agreed usage time corresponding to the system time and the vehicle identifier.

[0040] After the controller and display complete bidirectional verification of the vehicle identifier and the results are consistent, the remaining usage time calculation is not initiated directly. Instead, the local system time verification process is started first. The controller calls the built-in time verification module to compare the current local system time with the preset standard time base to determine whether the local system time is the set standard time. The standard time base is a time base configured during system initialization that conforms to the timekeeping specifications of the leasing business, ensuring the consistency of the timekeeping logic.

[0041] If the comparison result shows that the local system time is not the set standard time, it indicates that the current local time may be deviated. Using it directly to calculate the remaining usage time may lead to abnormal locking timing. For example, if the user manually adjusts the local system time forward, the vehicle may not be locked in time when the agreed locking time arrives.

[0042] When the local system time is not the set standard time, the controller sends a standard time acquisition request to the TBOX via a preset communication link. Upon receiving the request, the TBOX obtains a reliable standard time signal through its built-in time acquisition unit. This standard time signal comes from a remote management platform or positioning satellite and has high timeliness and accuracy. The TBOX feeds back the acquired standard time signal to the controller, which automatically corrects its local system time to the standard time and synchronously updates the locally stored time data to ensure the accuracy of subsequent timing.

[0043] If the comparison result shows that the local system time is the set standard time, it means that the current time base is reliable and no correction operation is required. The controller directly executes the subsequent steps, that is, it calculates the remaining usage time of the vehicle according to the current local system time and the agreed usage time corresponding to the vehicle identifier through a preset algorithm, and continuously monitors the changes in the remaining usage time until the remaining usage time reaches zero, at which point it triggers the operation restriction command.

[0044] Optionally, the standard time can be set to Beijing time, BeiDou Navigation Satellite System (BDS) time, or Global Positioning System (GPS) time. In practice, a regional standard time can be determined based on the specific area where the rental vehicle is used.

[0045] In this embodiment, the time verification and correction process avoids time deviation issues caused by factors such as user modification of local time, local system time drift, and power outage restart. The standard time obtained through TBOX ensures the uniformity of the time benchmark, ensuring that the remaining usage time calculation result fully matches the contract agreement, avoiding rental disputes caused by locking the car too early or too late due to time deviation, and further improving the accuracy of rental period management.

[0046] In one possible implementation, before mutual verification with the display based on the bound vehicle identifier, the following is also included: Determine whether the controller and display are bound to a vehicle identifier; When both the controller and the display are bound to a vehicle identifier, perform a mutual verification operation with the display based on the bound vehicle identifier; otherwise, send the bound vehicle identifier to the display, or obtain the vehicle identifier bound to the display and complete the binding.

[0047] The vehicle identifier is a unique identifier associated with the corresponding vehicle. It can be preset when the vehicle leaves the factory or configured and entered into the system by staff during the rental process. If the user replaces the controller or display during the rental period, there may be a situation where the vehicle identifier binding information is missing.

[0048] If the judgment result shows that both the controller and the display have been bound to the vehicle identifier, it means that the initial association configuration has been completed. At this time, the subsequent vehicle identifier mutual verification process will be directly entered to ensure that the subsequent logic such as usage time control and power limitation based on the identifier can proceed normally.

[0049] If it is determined that either the controller or the display is not bound to a vehicle identifier, the corresponding binding operation is performed according to the actual binding situation: when the controller is bound to a vehicle identifier but the display is not bound, the controller sends its stored vehicle identifier to the display via the CAN bus, the display receives it and stores it in its local storage unit, thus completing the identifier binding with the controller; when the display is bound to a vehicle identifier but the controller is not bound, the display sends the identifier to the controller via the CAN bus, the controller stores the vehicle identifier in its local storage unit, thus completing the binding.

[0050] In other possible implementations, if neither is bound, a prompt message for inputting the vehicle identifier can be displayed on the screen, and the staff can input the preset vehicle identifier through the screen. This identifier is synchronously transmitted to the controller and stored by both parties, thus completing the binding.

[0051] In this embodiment, before performing mutual verification of vehicle identifiers, it is first determined whether the controller and the display have been bound to the identifier. If not bound, the binding is completed by sending or receiving the identifier. This step ensures that the controller and the display are associated with the same vehicle identifier, guarantees the configuration process of the vehicle locking control system after equipment replacement during the rental period, avoids control logic confusion caused by unbound identifiers, and ensures timely vehicle locking when the agreed usage time arrives.

[0052] One possible implementation also includes: When sending the bound vehicle identifier to the display, the agreed usage time corresponding to the vehicle identifier is also sent to the display; When obtaining the vehicle identifier bound to the display and completing the binding, obtain the agreed usage time corresponding to the vehicle identifier stored on the display.

[0053] While the controller and display are binding the vehicle identifier, the transmission and synchronization of the agreed usage time are simultaneously initiated. The agreed usage time is a uniquely corresponding information about the vehicle's usable period, determined based on the rental agreement. This information has been pre-configured and entered into the local storage units of the bound controller and display. If either party is replaced during the rental period, the agreed usage time can be quickly synchronized, ensuring that the vehicle can be locked when the agreed usage time arrives.

[0054] When the binding operation is manifested as the controller binding a vehicle identifier and sending that identifier to an unbound display, the controller, while transmitting the vehicle identifier via the CAN bus, also packages and sends the agreed usage time corresponding to that vehicle identifier stored within its own memory. Upon receiving the vehicle identifier, the display synchronously receives the agreed usage time and stores it in its local dedicated storage area, establishing an association mapping with the vehicle identifier to ensure a one-to-one correspondence between the two.

[0055] When the binding operation is manifested as the display showing that the vehicle identifier has been bound, the display sending the vehicle identifier to the controller, and the controller receiving the vehicle identifier from the display, synchronously receiving the agreed usage time sent by the display via the CAN bus and storing it in the local storage unit, the association mapping between the identifier and the agreed usage time is also established.

[0056] In one possible implementation, after the agreed-upon usage time is synchronized and stored, the controller and the display will perform a consistency check on this time information to ensure that the content stored by both parties is completely identical. Subsequently, regardless of whether the display or controller is replaced due to equipment maintenance or other reasonable needs, the newly replaced component will automatically retrieve the agreed-upon usage time from the other party's stored information and write it into its own storage area while completing the vehicle identifier binding, without requiring reconfiguration by staff.

[0057] In this embodiment, the corresponding agreed usage time is transmitted synchronously while binding the vehicle identifier, so that both the controller and the display store complete key control information. This ensures the consistency of the control benchmark between the controller and the display. Even if one of the components is replaced later, the new component can directly obtain the stored agreed usage time without resetting the rental period. This not only improves the efficiency of service spare parts replacement, but also prevents customers from using the opportunity of replacing components to circumvent vehicle locking control, thus ensuring the efficiency and stability of the rental business operation.

[0058] One possible implementation also includes: Obtain rental day request information, generate a random verification code based on the rental day request information, send it to the display, and send the random verification code and vehicle identifier to the TBOX, which then forwards them to the remote management platform; In response to the key entered by the staff through the display, the agreed usage time stored on the display and controller is updated; the key is generated by the remote management platform based on the contractual usage date corresponding to the random verification code and vehicle identifier.

[0059] When a user rents a vehicle or needs to extend the rental period, they can initiate a rental days request through the interactive interface on the display. The display transmits this rental days request information to the controller in real time via the CAN bus. Upon receiving the request, the controller immediately initiates the verification process, generating a random verification code. This random verification code is time-sensitive and unique, valid only for the current renewal request.

[0060] The controller sends the generated random verification code to the display, which clearly shows it on the interactive interface for on-site staff to view. Simultaneously, the controller sends this random verification code along with the vehicle's identifier to the TBOX via the communication link. Upon receiving the relevant information, the TBOX will promptly forward the random verification code and vehicle identifier to the remote management platform as soon as a signal is available, regardless of network stability, ensuring that remote administrators receive complete renewal application information.

[0061] After receiving the data, the remote management platform uses the vehicle identifier, the rental contract's agreed usage date, and the received random verification code to generate a unique key using a preset encryption algorithm. On-site staff then obtain this key through a corresponding work terminal or platform, enter it into the designated input area on the display, and update the agreed usage time stored on the display and controller.

[0062] In practice, after the staff inputs the key through the display, the controller verifies the key's validity. Once it confirms that the key perfectly matches the random verification code, vehicle identifier, and contract information, the verification is considered successful. At this point, the controller automatically updates its stored agreed-upon usage time corresponding to the vehicle identifier and simultaneously sends a time update command to the display via the CAN bus. Upon receiving the command, the display synchronously updates its locally stored agreed-upon usage time, ensuring that the time information stored in both is consistent.

[0063] If verification fails, the display will show a prompt message, allowing staff to re-verify the information and resubmit the application. The entire process uses two-way verification between a random verification code and a dedicated key to ensure the security of the renewal operation and prevent unauthorized extensions of usage time. It also adapts to renewal needs in weak network environments, requiring only a brief period of signal connectivity during key transmission, without relying on a continuous and stable network connection. This balances security and operational flexibility.

[0064] In this embodiment, after receiving the rental days request, a random verification code is generated and forwarded to the remote management platform. The platform generates a unique key based on the verification code and contract information. After the key is entered on-site, the agreed usage time is updated. This process, through the combination of the random verification code and the unique key, ensures the security and uniqueness of the renewal operation. The key is used only once to effectively prevent customers from repeatedly using the same key to extend the usage time, standardizes the rental renewal operation process, ensures that the company can accurately control the extension of the rental period, and protect the company's property rights.

[0065] In one possible implementation, the types of operation restriction commands include rock drill power output restriction commands, air compressor power restriction commands, and travel pump power output restriction commands.

[0066] For engineering rental vehicles such as drilling rigs, the driving power mainly relies on the power output of the travel pump, while the operating power corresponds to the power supply of the rock drill and air compressor. Therefore, when restricting the power of engineering rental vehicles such as drilling rigs, the operation restriction commands can be set according to the power source, such as rock drill power output restriction commands, air compressor power restriction commands, and travel pump power output restriction commands, to generate corresponding operation restriction commands that adapt to the rental agreement and different usage times.

[0067] For example: if only a power output limit command for the rock drill or a power limit command for the air compressor is generated to restrict the power output for operation, the drilling rig will be unable to carry out core operations such as drilling and rock drilling or to drive the operating mechanism through compressed air. However, the basic power of the travel pump can be retained to achieve short-distance movement to avoid danger or to adjust the position of the equipment. If only a power output limit command for the travel pump is generated to restrict the power output for travel, the drilling rig will be unable to move but can temporarily use small operating power to complete the finishing operations of the started process.

[0068] In this embodiment, by setting different types of operation restriction instructions, the power output related to the core operation is restricted in a targeted manner, while not affecting the power supply required for auxiliary actions such as disconnection rods and equipment transfer. This achieves the core purpose of prohibiting illegal operations after locking the vehicle, while also meeting the needs of emergency avoidance operations, avoiding potential safety accidents caused by completely restricting power output, and improving the safety of use when the vehicle is locked.

[0069] One possible implementation also includes: During the period when the operation restriction command is in effect, if an emergency avoidance command is received via the physical emergency button or a set emergency password, the driving power output will be restored, and the vehicle will be locked again after a set time or after the vehicle has moved a preset distance.

[0070] During the period when the above-mentioned operational restrictions are in effect, if the vehicle faces an emergency situation such as collapse, landslide, or equipment jamming and needs to be temporarily moved to a safe area, the emergency evacuation command can be triggered in two ways. One is to press the physical emergency button at a preset location on the vehicle. This button establishes a direct signal connection with the controller, and the trigger signal generated by pressing the button can be quickly transmitted to the controller. The other is to enter a preset emergency password through the interactive interface on the display. After the password is verified, an emergency evacuation command is generated and sent to the controller.

[0071] Upon receiving an emergency avoidance command, the controller immediately activates its emergency response logic, sending a temporary power restoration command to the vehicle's power control system via the CAN bus. Prioritizing the restoration of power output related to driving, such as the travel pump, ensures the vehicle's mobility. Simultaneously, the controller begins timing or monitoring the vehicle's displacement: if time-triggered locking is used, the controller starts accumulating time after temporary power restoration, automatically terminating the temporary power restoration command after the set duration and resending the original operational restriction command; if distance-triggered locking is used, the controller monitors the movement distance through the vehicle's onboard position detection unit, automatically resuming locking once the vehicle has moved a preset distance.

[0072] Throughout the entire emergency response process, the controller continuously records information such as the time and location of emergency operations. Once the vehicle is locked again, the relevant records can be uploaded to the remote management platform via the TBOX when network signal is available, facilitating subsequent traceability. This process not only ensures the safety of personnel and equipment in emergency situations but also prevents the abuse of emergency operations through the automatic vehicle locking mechanism, ensuring the continuity of rental period management.

[0073] In this embodiment, the emergency avoidance command triggered by the physical emergency button or the set emergency password solves the need for avoidance in emergency situations after the vehicle is locked. It allows the vehicle to be moved to a safe area in dangerous situations, avoiding the occurrence of safety accidents. At the same time, the automatic restoration of the locked state ensures that the locking control will not fail due to the emergency avoidance operation. It takes into account both safety and control over the rental period, and improves the practicality and reliability of the system.

[0074] One possible implementation also includes: When the vehicle usage information corresponding to the vehicle identifier is determined to be a full payment purchase mode, the calculation of remaining usage time and the generation of operation restriction instructions are prohibited.

[0075] Once the drilling rig purchased in full is identified by the system, it will automatically skip the remaining time calculation and vehicle locking restrictions, and can carry out rock drilling operations normally.

[0076] After the controller and display complete CAN bus communication establishment, vehicle identifier binding and verification, and before starting the system time verification and remaining usage time calculation process, the controller will first perform vehicle usage information acquisition and identification operations. Vehicle usage information is key data representing the vehicle ownership mode, including types such as full payment purchase, leasing, and loan. This information can be pre-entered into the local storage units of the controller and display during vehicle factory configuration, or it can be synchronously obtained from the remote management platform via TBOX to ensure the accuracy and consistency of the information.

[0077] The controller retrieves vehicle usage information from locally stored data or sends a query command to the display or TBOX to obtain this information. It then parses and identifies this information to determine if the vehicle is currently in a full-payment purchase mode. If the identification result indicates that the vehicle usage information corresponds to a full-payment purchase mode, it means that the vehicle does not require rental period management. The controller will automatically disable the subsequent calculation of remaining usage time and turn off the generation of operation restriction commands, thus preventing any further restrictions on vehicle power output.

[0078] At this point, the vehicle only needs to meet the basic conditions of normal communication between the controller and the display, and consistent identifier verification, to fully release all power output permissions. Whether it is core operational power (such as rock drills) or driving power, it can respond normally to operating commands, ensuring that fully paid users can carry out various compliant operations without restrictions. If the identification result indicates that the vehicle usage information is not a fully paid purchase model (such as leasing or loan model), the controller will continue to proceed with subsequent operations such as system time verification and remaining usage time calculation according to the original process, strictly enforcing the corresponding vehicle locking control logic.

[0079] In this embodiment, when the vehicle usage information is determined to be in the full payment purchase mode, the calculation of remaining usage time and the generation of operation restriction instructions are prohibited. This allows vehicles with full payment to operate freely and normally without being subject to the constraints of rental vehicle locking control, thus meeting the usage needs of full payment customers. At the same time, by distinguishing the control logic of rental and full payment vehicles, the control system avoids miscontrol of vehicles of different types of customers, improves the applicability and flexibility of the control system, and takes into account the usage scenarios under different business models.

[0080] One possible implementation also includes: When the remaining usage time is less than or equal to the first threshold, control the display to issue an initial reminder; When the remaining usage time is less than or equal to the second threshold, control the display to issue an enhanced reminder.

[0081] After the controller completes vehicle identifier verification, system time correction, and determines that the vehicle is not purchased in full, the controller will calculate and monitor the remaining usage time of the vehicle in real time, and load preset two-level reminder thresholds. The first threshold is greater than the second threshold. The two thresholds are preset time nodes based on the regular needs of the rental business and are used to distinguish different reminder intensities.

[0082] When the controller detects that the remaining usage time has decreased to less than or equal to a first threshold, it determines that the first reminder phase has begun. The controller sends the first reminder command to the display via the CAN bus. After receiving the command, the display presents the reminder information in an intuitive way, such as displaying a text prompt indicating the remaining usage time in a prominent position on the interactive interface and illuminating a preset reminder icon, ensuring that the user can clearly perceive the reminder during work breaks. At this time, the vehicle still maintains normal operation and movement rights, and only gently reminds the user of the need for renewal.

[0083] If a user fails to renew their subscription in a timely manner, the controller continuously monitors the remaining usage time. When the remaining usage time further decreases to less than or equal to a second threshold, an enhanced reminder process is triggered. The controller sends an enhanced reminder command to the display, which switches to a more prominent reminder mode. This could involve repeatedly flashing the remaining time indicator on the interface, accompanied by intermittent sound prompts, or locking certain non-core operation interfaces until the user confirms the reminder. By increasing the intensity of the reminder, the controller effectively draws the user's attention and prevents them from neglecting to renew their subscription.

[0084] During the initial and enhanced reminder periods, users can initiate a renewal request via the display. The subsequent process will connect to the relevant operations for increasing the rental days. After completing key verification, the agreed usage time can be updated, and the reminder status will be automatically lifted. If the user does not initiate a renewal, when the remaining usage time drops to zero, the controller will send an operation restriction command according to the established process to realize power output control.

[0085] For example: During the rental period, the drilling process is normal; if there are 7 days left until the rental date, an interface reminder will appear, and within 3 days, the interface will flash to prompt the customer to renew; if the rental period expires and the customer does not renew, the drilling action will be restricted.

[0086] In this embodiment, by using progressively stronger reminders, customers can be effectively made to pay attention to the renewal, avoiding situations where customers forget to renew and the vehicle suddenly becomes unusable. This reduces customer dissatisfaction caused by locking the vehicle, while also allowing customers sufficient time to prepare for the renewal, ensuring the smooth progress of the rental business and improving the customer's user experience.

[0087] One possible implementation also includes: When a vehicle unlocking command is received from the remote management platform forwarded by TBOX, a mutual verification step is performed between the display and the controller based on the bound vehicle identifier. If the vehicle identifiers bound to the display and the controller are consistent, the vehicle is unlocked. Upon receiving a vehicle locking command or operation restriction command sent by the remote management platform via TBOX, execute the corresponding control command.

[0088] During the operation of the vehicle locking control system, TBOX maintains constant signal interaction with the remote management platform, monitoring in real time for various control commands issued by the platform, including vehicle unlocking commands, vehicle locking commands, and operation restriction commands. Upon receiving any command from the remote management platform, TBOX immediately forwards it to the controller via a pre-set communication link, ensuring timely command transmission.

[0089] If the controller receives a remote unlock command, to ensure the security and accuracy of the unlocking operation, it will first initiate a two-way vehicle identifier verification process with the display. The controller and the display exchange their stored vehicle identifiers via the CAN bus to complete a consistency comparison. If the verification result shows that the vehicle identifiers bound to both are consistent, it means that the vehicle corresponding to the unlock command matches the currently controlled vehicle. The controller then sends an unlock command to the vehicle power control system to remove the previous power output restriction and restore the vehicle's normal operation and movement rights. If the verification result is inconsistent, the controller refuses to execute the unlocking operation and reports the verification failure information to the remote management platform through the TBOX, so that management personnel can verify the situation.

[0090] If there is a breach of contract or other situation requiring early vehicle locking, the controller will receive a vehicle locking command or operation restriction command sent by the remote management platform. In this case, no additional identifier verification process is needed; the controller directly responds to the command content. Upon receiving a remote locking command, the controller generates a corresponding power restriction command and sends it to the vehicle power control system, restricting the vehicle's operating or driving power as required by the command. Upon receiving a remote operation restriction command, the controller directly forwards the command to the vehicle power control system, precisely executing the corresponding power control operation.

[0091] In this embodiment, the controller receives unlock and lock commands from the remote management platform forwarded by the TBOX. When unlocking, the vehicle identifier is first verified to ensure that the unlocking operation corresponds to the correct vehicle. When locking, the command is executed directly. This design not only expands the control methods of the control system, supporting remote locking and unlocking operations, and is suitable for scenarios that require remote management, but also ensures the security of remote unlocking operations through identifier verification, preventing mis-locking or illegal unlocking, further strengthening the control of rental vehicles and safeguarding the company's property.

[0092] See Figure 3The diagram illustrates an interactive flowchart of a vehicle locking control method for rental vehicles provided in an embodiment of the present invention, including the following steps: S301: The controller and the display perform mutual verification of the vehicle identifier; if the verification is consistent, proceed to step S303; if the display is not bound to a vehicle identifier, proceed to step S302; if the controller is not bound to a vehicle identifier, proceed to step S303. S302: The controller sends the vehicle identifier to the display; S302': The display sends the vehicle identifier back to the controller; S303: The controller determines whether the local system time is the set standard time; if the local system time is the set standard time, proceed to step S306; otherwise, proceed to step S304. S304: The controller obtains the standard time signal from the TBOX; S305: TBOX feeds back a standard time signal to the controller; S306: The controller determines that the remaining usage time is less than or equal to the first threshold, and executes step S307, whereby the controller controls the display to issue an initial reminder. S308: The controller determines that the remaining usage time is less than or equal to the second threshold, and executes step S309, whereby the controller controls the display to provide an enhanced reminder. S310: When the controller determines that the remaining usage time is zero, it sends an operation restriction command to the vehicle power control system.

[0093] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0094] The following are device embodiments of the present invention. For details not described in detail, please refer to the corresponding method embodiments described above.

[0095] Figure 4 A schematic diagram of a vehicle locking control device for rental vehicles provided in an embodiment of the present invention is shown. For ease of explanation, only the parts relevant to the embodiment of the present invention are shown, and are described in detail below: like Figure 4 As shown, the vehicle locking control device 4 for rental vehicles includes: The verification module 401 is used to perform mutual verification with the display based on the bound vehicle identifier when the vehicle locking control system is powered on. Control module 402 is used to send an operation restriction command to the vehicle power control system when the vehicle identifier bound to the display and the controller is inconsistent. When the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier. When the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system. The operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

[0096] In one possible implementation, the control module 402 is further configured to determine whether the local system time is the set standard time before determining the remaining usage time based on the agreed usage time corresponding to the system time and the vehicle identifier. When the local system time is not the set standard time, the standard time signal is obtained from the TBOX and the local system time is corrected to the standard time; otherwise, the operation of determining the remaining usage time is performed based on the agreed usage time corresponding to the system time and the vehicle identifier.

[0097] In one possible implementation, the verification module 401 is further configured to determine whether the controller and the display are bound to a vehicle identifier before performing mutual verification with the display based on the bound vehicle identifier. When both the controller and the display are bound to a vehicle identifier, perform a mutual verification operation with the display based on the bound vehicle identifier; otherwise, send the bound vehicle identifier to the display, or obtain the vehicle identifier bound to the display and complete the binding.

[0098] In one possible implementation, the control module 402 is further configured to send the agreed usage time corresponding to the vehicle identifier to the display when sending the bound vehicle identifier to the display; When obtaining the vehicle identifier bound to the display and completing the binding, obtain the agreed usage time corresponding to the vehicle identifier stored on the display.

[0099] In one possible implementation, the control module 402 is also used to obtain rental day request information, generate a random verification code based on the rental day request information, send it to the display, and send the random verification code and vehicle identifier to the TBOX, which then forwards them to the remote management platform. In response to the key entered by the staff through the display, the agreed usage time stored on the display and controller is updated; the key is generated by the remote management platform based on the contractual usage date corresponding to the random verification code and vehicle identifier.

[0100] In one possible implementation, the control module 402 is also used to restore driving power output and restore the vehicle locking state after a set time or after the vehicle has moved a preset distance when an emergency avoidance command is received during the operation restriction command period.

[0101] In one possible implementation, the control module 402 is also used to prohibit the calculation of remaining usage time and the generation of operation restriction instructions when the vehicle usage information corresponding to the vehicle identifier is a full payment purchase mode.

[0102] In one possible implementation, the control module 402 is further configured to control the display to issue an initial reminder when the remaining usage time is less than or equal to a first threshold, and to control the display to issue an enhanced reminder when the remaining usage time is less than or equal to a second threshold.

[0103] In one possible implementation, the verification module 401 is further configured to perform a mutual verification step with the display based on the bound vehicle identifier when the control module 402 receives the vehicle unlocking command sent by the remote management platform forwarded by the TBOX. The control module 402 is also used to control the vehicle to unlock when the vehicle identifier bound to the display and the controller are consistent; and to execute the corresponding control command when it receives the vehicle locking command or operation restriction command sent by the remote management platform forwarded by TBOX.

[0104] In this embodiment, the vehicle locking control system establishes a communication connection between the display and the controller via a CAN bus. Upon power-up, it first performs mutual verification of the bound vehicle identifiers. If the identifiers do not match, it directly sends an operation restriction command. If the identifiers match, it determines the remaining usage time based on the system time and the agreed usage time. When the remaining time is zero, it triggers the operation restriction command. This solution effectively prevents customers from privately replacing the display or controller to circumvent the vehicle locking control by binding and verifying the vehicle identifiers. At the same time, it does not rely on a stable network and can achieve precise control over the usage period of the rental vehicle through local logic interaction. The operation restriction command specifically restricts the relevant power output, which not only ensures precise vehicle locking control but also reserves space for emergency avoidance operations, thereby improving the safety of use.

[0105] Figure 5 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. For example... Figure 5 As shown, the electronic device 5 of this embodiment includes a processor 50 and a memory 51. The memory 51 stores a computer program 52. When the processor 50 executes the computer program 52, it implements the steps in the various method embodiments described above. Alternatively, when the processor 50 executes the computer program 52, it implements the functions of each module / unit in the various device embodiments described above.

[0106] For example, computer program 52 may be divided into one or more modules / units, which are stored in memory 51 and executed by processor 50 to complete the present invention. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of computer program 52 in electronic device 5.

[0107] Electronic device 5 may include, but is not limited to, processor 50 and memory 51. Those skilled in the art will understand that... Figure 5 This is merely an example of electronic device 5 and does not constitute a limitation on electronic device 5. It may include more or fewer components than shown, or combine certain components, or different components. For example, electronic device 5 may also include input / output devices, network access devices, buses, etc.

[0108] The processor 50 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0109] The memory 51 can be an internal storage unit of the electronic device 5, such as a hard disk or RAM. The memory 51 can also be an external storage device of the electronic device 5, such as a plug-in hard disk, Smart Media Card (SMC), Secure Digital (SD) card, or Flash Card. Furthermore, the memory 51 can include both internal and external storage units of the electronic device 5. The memory 51 is used to store the computer program 52 and other programs and data required by the electronic device 5. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0110] For the sake of simplicity and clarity, only the above-described functional modules / units are used as examples. In practical applications, the functions described above can be assigned to different functional modules / units as needed. These modules / units can be implemented in hardware, software, or a combination of both.

[0111] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the methods described in the above-described method embodiments.

[0112] This invention also provides a computer program product, including a computer program. When the computer program is executed by a processor, it implements the methods described in the above-described method embodiments.

[0113] Computer programs include computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. Computer-readable media can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.

[0114] In the above embodiments, the descriptions of each embodiment have their own emphasis. Parts not detailed or described in a particular embodiment can be referred to in the relevant descriptions of other embodiments. Unless otherwise specified or in conflict with logic, the terminology and / or descriptions between different embodiments are consistent and can be referenced interchangeably. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0115] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for locking rental vehicles, characterized in that, The vehicle locking control system includes: a display, a controller, and an onboard telematics terminal (TBOX), wherein the display and the controller are connected via a CAN bus communication connection; the method includes: When the vehicle locking control system is powered on, it performs mutual verification with the display based on the bound vehicle identifier; When the vehicle identifier bound to the display and the controller is inconsistent, an operation restriction command is sent to the vehicle power control system. When the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

2. The method according to claim 1, characterized in that, Before determining the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier, the method further includes: Determine if the local system time is the set standard time; When the local system time is not the set standard time, the standard time signal is obtained from the TBOX and the local system time is corrected to the standard time; otherwise, the operation of determining the remaining usage time based on the system time and the agreed usage time corresponding to the vehicle identifier is performed.

3. The method according to claim 1, characterized in that, Before performing mutual verification with the display based on the bound vehicle identifier, the method further includes: Determine whether the controller and the display are bound to a vehicle identifier; When both the controller and the display are bound to a vehicle identifier, a mutual verification operation based on the bound vehicle identifier is performed with the display; otherwise, the bound vehicle identifier is sent to the display, or the vehicle identifier bound to the display is obtained and the binding is completed.

4. The method according to claim 3, characterized in that, Also includes: When sending the bound vehicle identifier to the display, the agreed usage time corresponding to the vehicle identifier is also sent to the display; When the vehicle identifier bound to the display is obtained and the binding is completed, the agreed usage time corresponding to the vehicle identifier stored on the display is obtained.

5. The method according to claim 1, characterized in that, Also includes: Obtain rental day request information, generate a random verification code based on the rental day request information, send it to the display, and send the random verification code and vehicle identifier to the TBOX, which then forwards it to the remote management platform; In response to a key entered by a staff member via the display, the agreed usage time stored on the display and the controller is updated; wherein, the key is generated by the remote management platform based on the contractually agreed usage date corresponding to the random verification code and the vehicle identifier.

6. The method according to claim 1, characterized in that, The types of operation restriction commands include rock drill power output restriction commands, air compressor power restriction commands, and travel pump power output restriction commands.

7. The method according to claim 1 or 6, characterized in that, Also includes: When it is determined that the vehicle usage information corresponding to the vehicle identifier is a full payment purchase mode, the calculation of remaining usage time and the generation of operation restriction instructions are prohibited.

8. A vehicle locking control device for rental vehicles, characterized in that, The vehicle locking control system includes: a display, a controller, and a TBOX, wherein the display and the controller are connected via CAN bus communication; the device includes: The verification module is used to perform mutual verification with the display based on the bound vehicle identifier when the vehicle locking control system is powered on. The control module is used to send an operation restriction command to the vehicle power control system when the vehicle identifier bound to the display and the controller is inconsistent. When the vehicle identifier bound to the display and the controller are consistent, the remaining usage time is determined according to the system time and the agreed usage time corresponding to the vehicle identifier, and when the remaining usage time is equal to zero, an operation restriction command is sent to the vehicle power control system; wherein, the operation restriction command is used to restrict the vehicle's driving power output and / or power output other than driving power.

9. An electronic device, characterized in that, It includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 7.

Images