Vehicle control method, device and system based on safety belt and storage medium

Abstract

The invention discloses a vehicle control method, device and system based on a safety belt and a storage medium, and the method comprises the steps that after a vehicle is powered on, the state of the safety belt is monitored; when it is monitored that the safety belt is in the buckled state, control parameters of the safety belt are obtained, and the control parameters comprise at least one of pulling force or traction force borne by the safety belt, pulling or traction displacement, pulling or traction speed and the number of control action times in a preset time window; according to a mapping relationship between a pre-calibrated triggering threshold range and a target application scene, judging whether the control parameter meets a condition of triggering the target application scene; and when the control parameter meets a condition of triggering a target application scene, executing the target application scene corresponding to the control parameter. By adopting the scheme provided by the invention, rapid and private non-sensitive operation can be carried out on the equipment in the vehicle on the premise of ensuring the driving safety.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a vehicle control method, device, system and storage medium based on seat belts. Background Technology

[0002] As automotive intelligence continues to advance, in-vehicle equipment such as air conditioning systems, seats, windows, and multimedia systems are becoming increasingly sophisticated. Traditional methods of interacting with these devices primarily include physical switches, soft switches on touchscreens, smartphone applications, and voice recognition. However, physical switches and touchscreen operations require drivers or passengers to shift their gaze and attention from the road to the corresponding control panel, potentially posing safety hazards, especially while driving. While voice control frees up the hands, recognition rates may decrease in noisy environments, and it may not be the optimal choice for scenarios involving complex multi-step operations or privacy concerns (such as personalized settings for specific passengers). Application control typically requires a smartphone connection, making it cumbersome and reliant on external devices. Therefore, how to enable quick, private, and seamless operation of in-vehicle devices while ensuring driving safety has become a pressing technical challenge. Summary of the Invention

[0003] This application provides a vehicle control method, device, system, and storage medium based on seat belts, which enables quick, private, and seamless operation of in-vehicle equipment while ensuring driving safety.

[0004] This application provides a vehicle control method based on a seat belt, including: After the vehicle is powered on, monitor the seat belt status; When the seat belt is detected to be in a fastened state, the control parameters of the seat belt are acquired. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window. Based on the pre-defined mapping relationship between the trigger threshold range and the target application scenario, it is determined whether the control parameters meet the conditions for triggering the target application scenario; When the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed.

[0005] The beneficial effects of this application are as follows: After the vehicle is powered on, the seat belt status is monitored; when the seat belt is detected to be in a fastened state, the control parameters of the seat belt are acquired, wherein the control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window; based on the mapping relationship between a pre-calibrated trigger threshold range and a target application scenario, it is determined whether the control parameters meet the conditions for triggering the target application scenario; when the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed. This application uses the seat belt, an inherent and essential device in the vehicle, as an interaction medium, and realizes the control of in-vehicle devices by using the pulling force, speed, displacement, number of times, and their combinations as trigger signals without the need for eye shift, application operation, or voice control. This achieves quick, private, and seamless operation of in-vehicle devices while ensuring driving safety.

[0006] In one embodiment, the control parameters are the number of times the seat belt is pulled or pulled within a preset time, and the force value detected in each pulling or pulling action. The step of determining whether the control parameters meet the conditions for triggering the target application scenario includes: The number of pull or traction actions is combined and mapped with a specific force value range; If the number of times detected and the corresponding force value fall within the range of the combined mapping within the preset time, it is determined that the triggering condition is met.

[0007] In one embodiment, determining whether the control parameters meet the conditions for triggering the target application scenario includes: The parameter combination feature points are calculated based on the acquired control parameters; The feature points of the parameter combination are compared with a preset parameter threshold point matrix, where each point in the parameter threshold point matrix corresponds to one or more predefined target application scenarios. If the feature point of the parameter combination falls into a certain area of ​​the dot matrix, it is determined that the conditions for triggering the application scenario corresponding to that area are met.

[0008] In one embodiment, the method further includes the step of customizing scene manipulation actions: Receive custom action configuration commands from users via the in-vehicle human-machine interface to trigger specific application scenarios; The custom action configuration instruction includes at least: expected parameters for performing a target control action on the seat belt, the expected parameters including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action; Based on the custom action configuration instructions, establish and store the mapping relationship between the new combination of control parameters and the specific application scenario.

[0009] In one embodiment, the method further includes an anti-accidental touch judgment step: During the normal use of the seat belt, the first set of characteristic parameters when the occupant is wearing the seat belt is calibrated, and the first set of characteristic parameters includes at least the first reference pull-out speed. When setting the scene trigger threshold, a second set of feature parameters is set for entering the target application scene. The second set of feature parameters corresponds to a reference pull speed. The second reference pull speed has a preset distinguishability with the first reference pull speed, so as to distinguish between normal use actions and scene control intention actions.

[0010] In one embodiment, obtaining the control parameters of the seat belt includes: The control parameters of the seat belt are obtained by force sensors and / or displacement sensors located on the seat belt latch, retractor, or webbing path.

[0011] In one embodiment, the target application scenario includes a control scenario for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system switch and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching.

[0012] This application also provides a vehicle control device based on a seat belt, comprising: The monitoring module is used to monitor the seat belt status after the vehicle is powered on; The acquisition module is used to acquire the control parameters of the seat belt when the seat belt is detected to be in a fastened state. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window. The judgment module is used to determine whether the control parameters meet the conditions for triggering the target application scenario based on the pre-calibrated mapping relationship between the trigger threshold range and the target application scenario. The execution module is used to execute the target application scenario corresponding to the control parameters when the control parameters meet the conditions for triggering the target application scenario.

[0013] In one embodiment, the control parameters are the number of times the seat belt is pulled or pulled within a preset time, and the force value detected in each pulling or pulling action. The judgment module includes: The mapping submodule is used to combine and map the number of pull or traction actions with a specific force value range; The first determination submodule is used to determine that the triggering condition is met if the number of times detected and the corresponding force value fall within the range of the combined mapping within a preset time.

[0014] In one embodiment, the determining module includes: The calculation submodule is used to calculate the parameter combination feature points based on the acquired control parameters; The comparison submodule is used to compare the feature points of the parameter combination with a preset parameter threshold point matrix, wherein each point in the parameter threshold point matrix corresponds to one or more predefined target application scenarios. The second determination submodule is used to determine that if the parameter combination feature point falls into a certain area of ​​the dot matrix, the conditions for triggering the application scenario corresponding to that area are met.

[0015] In one embodiment, the apparatus further includes: The receiving module is used to receive custom action configuration commands input by the user through the vehicle human-machine interface to trigger specific application scenarios; The custom action configuration instruction includes at least: expected parameters for performing a target control action on the seat belt, the expected parameters including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action; The storage module is used to establish and store the mapping relationship between the new combination of control parameters and the specific application scenario according to the custom action configuration instructions.

[0016] In one embodiment, the apparatus further includes: The calibration module is used to calibrate a first set of characteristic parameters when the occupant is wearing the seat belt during normal use of the seat belt. The first set of characteristic parameters includes at least a first reference pull-out speed. The setting module is used to set a second set of feature parameters for entering the target application scenario when setting the scene trigger threshold. The second set of feature parameters corresponds to a reference pull speed. The second reference pull speed has a preset distinguishability with the first reference pull speed, so as to distinguish between normal use actions and scene control intention actions.

[0017] In one embodiment, the acquisition module is further configured to: The control parameters of the seat belt are obtained by force sensors and / or displacement sensors located on the seat belt latch, retractor, or webbing path.

[0018] In one embodiment, the target application scenario includes a control scenario for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system switch and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching.

[0019] This application also provides a seatbelt-based vehicle control system, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to implement the seat belt-based vehicle control method described in any of the above embodiments.

[0020] This application also provides a computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor corresponding to a seatbelt-based vehicle control system, enables the seatbelt-based vehicle control system to implement the seatbelt-based vehicle control method described in any of the above embodiments.

[0021] Other features and advantages of this application will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings.

[0022] The technical solution of this application will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0023] The accompanying drawings are provided to further illustrate the present application and form part of the specification. They are used together with the embodiments of the present application to explain the application and do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart of a vehicle control method based on a seat belt in one embodiment of this application; Figure 2 This is a schematic diagram of a vehicle control device based on a seat belt according to an embodiment of this application; Figure 3 This is a schematic diagram of the hardware structure of a seat belt-based vehicle control system according to one embodiment of this application. Detailed Implementation

[0024] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application.

[0025] Figure 1 This is a flowchart of a vehicle control method based on a seat belt according to an embodiment of this application, such as... Figure 1 As shown, the method can be implemented as follows: S101-S104: In step S101, after the vehicle is powered on, the seat belt status is monitored; In step S102, when the seat belt is detected to be in a fastened state, the control parameters of the seat belt are acquired. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window. In step S103, based on the pre-defined mapping relationship between the trigger threshold range and the target application scenario, it is determined whether the control parameters meet the conditions for triggering the target application scenario. In step S104, when the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed.

[0026] After the vehicle is powered on, the seatbelt status is monitored. Powering on the vehicle means that its various electronic systems begin operating, and monitoring the seatbelt status at this time provides the basic data for subsequent operations. Therefore, after the vehicle is started, the system begins monitoring whether the seatbelts are fastened.

[0027] When the seatbelt is detected to be fastened, its control parameters are acquired. These parameters include at least one of the following: the pulling or traction force acting on the seatbelt, the displacement caused by pulling or traction, the speed of pulling or traction, and the number of control actions within a preset time window. Specifically, these control parameters can be acquired using force sensors and / or displacement sensors located on the seatbelt latch, retractor, or webbing path. The force sensor accurately senses the magnitude of the force acting on the seatbelt during pulling or traction, while the displacement sensor accurately measures the displacement distance of the seatbelt during pulling or traction. These sensors convert physical signals into electrical signals and transmit them to the vehicle's control system for analysis and processing.

[0028] Based on a pre-defined mapping relationship between trigger threshold ranges and target application scenarios, it is determined whether the control parameters meet the conditions for triggering the target application scenario. Specifically, the target application scenario includes control scenarios for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system on / off and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching. For example, when a passenger wants to adjust the air conditioning temperature, they can trigger the air conditioning system mode control scenario through a specific seatbelt operation.

[0029] In this application, to achieve this precise mapping relationship, the correspondence between control parameter combinations and specific application scenarios is established and stored in advance. Specifically, the system receives custom action configuration instructions input by the user through the in-vehicle human-machine interface to trigger specific application scenarios. These custom action configuration instructions include at least the expected parameters for performing a target control action on the seatbelt, including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action. Based on the custom action configuration instructions, a new mapping relationship between the control parameter combinations and the specific application scenario is established and stored. For example, the user can access the "Shortcut Key Learning" or "Action Recording" function through the "Vehicle Settings" menu on the central control screen. Upon prompting, the user first selects or names a target function for which a custom shortcut key is desired, such as "Play my favorite playlist." Subsequently, the system enters action learning mode. After hearing a prompt tone, the user performs a unique action (e.g., rapidly and with moderate force, pulls the seatbelt four times within 3 seconds), and confirms the completion on the touchscreen. The system analyzes the recorded control time window, number of actions, and force change curves to establish a unique mapping between this parameter combination and the scenario of "playing my favorite playlist," and stores this mapping in the controller. Subsequently, when the user reproduces this unique custom action, the system will accurately identify and execute the corresponding playback command. For example, a user can input a custom action configuration command through the in-vehicle human-machine interface, setting it to trigger the air conditioning system's cooling mode when the seatbelt is pulled twice within a 3-second time window, with each pull force between 10-20 Newtons and a displacement of 15-25 centimeters. The system establishes and stores the corresponding mapping relationship between this command, the corresponding control parameter combination, and the target application scenario of the air conditioning system's cooling mode activation.

[0030] In one embodiment, when determining whether the control parameters meet the conditions for triggering the target application scenario, the control parameters are the number of times the seat belt is pulled or tugged within a preset time, and the force value detected in each pull or tugged action. The number of pull or tugged actions is mapped to a specific force value range; if the number of pulls and the corresponding force value detected within the preset time fall within the mapped range, the triggering condition is determined to be met. As in the example above, when the vehicle is running, the system detects that the seat belt is in the fastened state and begins recording relevant control parameters. Assume that at a certain moment, the system detects that the seat belt is pulled twice within 3 seconds. Further detection of the force of each pull reveals that the first pull force is 12 Newtons and the second pull force is 18 Newtons, both within the 10-20 Newton range; simultaneously, detection of the displacement of each pull reveals that the first is 18 centimeters and the second is 22 centimeters, both within the 15-25 centimeter range. The system compares the acquired control parameters with the pre-stored mapping relationship and finds that it fully meets the conditions of pulling twice within a 3-second time window, with each pull force being 10-20 Newtons and the pull displacement being 15-25 centimeters. Therefore, it determines that the conditions for triggering the air conditioning system to start the cooling mode are met.

[0031] Furthermore, parameter combination feature points can be calculated based on the acquired control parameters. These feature points are then compared with a preset parameter threshold matrix, where each point corresponds to one or more predefined target application scenarios. If a parameter combination feature point falls into a region within the matrix, the conditions for triggering the corresponding application scenario for that region are met. For example, a parameter threshold matrix can be pre-constructed to control the volume adjustment of a multimedia system. Different regions within the matrix correspond to different volume adjustment increments; for instance, one region might correspond to a 5-level increase in volume, with parameters ranging from 8-12 Newtons to 10-15 centimeters, pulled twice within a 2-second time window. When a passenger wants to adjust the multimedia system volume, they operate the seatbelt. The system detects that the seatbelt was pulled twice within 2 seconds, with pull forces of 10 and 11 Newtons and displacements of 12 and 13 centimeters respectively. The system calculates parameter combination feature points based on these control parameters and then compares these feature points with the preset parameter threshold matrix. The feature point was found to fall within the area corresponding to a 5-level volume increase, so it was determined that the condition for triggering a 5-level volume increase scene was met, and the multimedia system was controlled to increase the volume by 5 levels.

[0032] Furthermore, this application also includes anti-accidental touch control. To more accurately distinguish between normal use actions and scenario-based control intention actions, during the normal use of the seatbelt phase, a first set of characteristic parameters is calibrated when the occupant fastens the seatbelt. This first set of characteristic parameters includes at least a first reference pull-out speed. When setting the scenario trigger threshold, a second set of characteristic parameters is set to enter the target application scenario. The reference pull-out speed corresponding to this second set of characteristic parameters has a preset distinguishability with the first reference pull-out speed, thus differentiating between normal use actions and scenario-based control intention actions. For example, during vehicle manufacturing setup or when a user performs personalized learning for the first time, the system guides the occupant to perform a typical "normal seatbelt fastening" action. During this process, the system records the entire process of the user smoothly pulling the seatbelt from the retractor to a suitable fixed length, calculating the average pull-out speed V1 as a reference. Subsequently, when setting trigger thresholds for each target application scenario, the required reference pull-out speed V2 is set to be much greater than V1. For example, it requires two pull-out actions to be completed within 1 second (corresponding to V2), while a normal seatbelt usually takes 2-3 seconds (corresponding to V1). In this way, the system can clearly distinguish between two distinct action modes: "daily seatbelt tightening" (slow, gentle force) and "intended vehicle control" (fast, forceful, or repeated).

[0033] In one embodiment of this application, the system can also analyze a large amount of seatbelt-wearing behavior data of occupants with different heights, body types, and weights to statistically obtain reference values ​​for the pull-out speed and pull-out length of seatbelts for occupants of different heights and weights. When a passenger is not calibrating the first set of characteristic parameters for seatbelt use during normal vehicle use, the system collects the passenger's image and weight information, analyzes and obtains the passenger's height and weight information, determines the corresponding pull-out speed and pull-out length reference values ​​based on the passenger's height and weight information, and determines the first set of characteristic parameters for seatbelt use during normal vehicle use.

[0034] When the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed. For example, if the seat posture adjustment scenario is triggered by the operation of the seat belt, the system will quickly control the seat motor and adjust the seat angle, height, and other parameters according to a preset program to make the seat reach the passenger's desired comfort state.

[0035] In one specific embodiment, the complete process of this method is as follows: Step 1: Start the vehicle and power it on; system initialization.

[0036] Step 2: Monitor the status of the master switch for seatbelt-based control functions (user-configurable). If the function is "off", the system will not enable this method or will maintain standby monitoring; if it is "on", proceed to the next step.

[0037] Step 3: Monitor the seatbelt buckle status of the target seat, i.e., whether the seatbelt latch is inserted into the buckle and in the buckled state. If it is not buckled, continue monitoring.

[0038] Step 4: When the seat belt is detected to be fastened, activate this control method for the seat and continuously monitor the sensor signal from the seat belt.

[0039] Step 5: Acquire and process the seat belt control parameters in real time. The system calculates based on sensor readings, for example: within the most recent preset time window T (e.g., 5 seconds), it acquires the time t of a complete "pull-rewind" action, calculates the instantaneous speed V, records the peak force value F in the action, and accumulates the number C of complete pull-out actions completed within the window T with force exceeding the minimum detection threshold.

[0040] Step 6: Trigger condition judgment. Combine the "force F" and "number of times C" parameters obtained in Step 5 and compare them with the preset threshold conditions (such as the matrix of force value interval [Y1, Y2] and number of times C) stored in the controller.

[0041] Step 7: If the comparison result does not match any of the preset trigger conditions, the system determines that the operation is an unconscious daily action or improper operation, and returns to step 5 to continue monitoring.

[0042] Step 8: If the comparison is successful, that is, the obtained parameter combination accurately matches a certain predefined trigger zone, the controller determines that the trigger condition is met, and immediately generates and sends the corresponding control command, such as sending the command "turn on and set to cooling mode" to the air conditioner controller.

[0043] Step 9: After waiting for feedback on command execution or a short delay, the controller returns to Step 5 and continues to prepare to receive the next control command.

[0044] The beneficial effects of this application are as follows: After the vehicle is powered on, the seat belt status is monitored; when the seat belt is detected to be in a fastened state, the control parameters of the seat belt are acquired, wherein the control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window; based on the mapping relationship between a pre-calibrated trigger threshold range and a target application scenario, it is determined whether the control parameters meet the conditions for triggering the target application scenario; when the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed. This application uses the seat belt, an inherent and essential device in the vehicle, as an interaction medium, and realizes the control of in-vehicle devices by using the pulling force, speed, displacement, number of times, and their combinations as trigger signals without the need for eye shift, application operation, or voice control. This achieves quick, private, and seamless operation of in-vehicle devices while ensuring driving safety.

[0045] In one embodiment, the control parameters are the number of pull or traction actions of the seat belt monitored within a preset time, and the force value monitored in each pull or traction action; the above step S103 can be implemented as the following steps A1-A2: In step A1, the number of pull or traction actions is mapped to a specific force value range; In step A2, if the number of times detected and the corresponding force value fall within the range of the combined mapping within a preset time, it is determined that the triggering condition is met.

[0046] In one embodiment, step S103 above can be implemented as steps B1-B3 as follows: In step B1, parameter combination feature points are calculated based on the acquired control parameters; In step B2, the parameter combination feature points are compared with a preset parameter threshold point matrix, where each point in the parameter threshold point matrix corresponds to one or more predefined target application scenarios. In step B3, if the parameter combination feature point falls into a certain area of ​​the dot matrix, it is determined that the conditions for triggering the application scenario corresponding to that area are met.

[0047] In one embodiment, the method may also be implemented as follows: C1-C2: In step C1, a custom action configuration command for triggering a specific application scenario is received from the user through the in-vehicle human-machine interface; The custom action configuration instruction includes at least: expected parameters for performing a target control action on the seat belt, the expected parameters including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action; In step C2, a mapping relationship between the new combination of control parameters and the specific application scenario is established and stored according to the custom action configuration instructions.

[0048] In one embodiment, the method may also be implemented as follows: steps D1-D2: In step D1, during the normal use of the seat belt, a first set of characteristic parameters is calibrated when the occupant is wearing the seat belt. The first set of characteristic parameters includes at least a first reference pull-out speed. In step D2, when setting the scene trigger threshold, a second set of feature parameters is set for entering the target application scene. The second set of feature parameters corresponds to a reference pull speed. The second reference pull speed has a preset distinguishability with the first reference pull speed, so as to distinguish between normal use actions and scene control intention actions.

[0049] In one embodiment, step S102 above can also be implemented as the following steps: The control parameters of the seat belt are obtained by force sensors and / or displacement sensors located on the seat belt latch, retractor, or webbing path.

[0050] In one embodiment, the target application scenario includes a control scenario for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system switch and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching.

[0051] Figure 2 This is a schematic diagram of a vehicle control device based on a seat belt according to one embodiment of this application, as shown below. Figure 2 As shown, the device includes: The monitoring module 201 is used to monitor the seat belt status after the vehicle is powered on; The acquisition module 202 is used to acquire the control parameters of the seat belt when the seat belt is detected to be in a fastened state. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of pulling or traction, the speed of pulling or traction, and the number of control actions within a preset time window. The judgment module 203 is used to determine whether the control parameters meet the conditions for triggering the target application scenario based on the pre-calibrated mapping relationship between the trigger threshold range and the target application scenario. The execution module 204 is used to execute the target application scenario corresponding to the control parameters when the control parameters meet the conditions for triggering the target application scenario.

[0052] In one embodiment, the control parameters are the number of times the seat belt is pulled or pulled within a preset time, and the force value detected in each pulling or pulling action. The judgment module includes: The mapping submodule is used to combine and map the number of pull or traction actions with a specific force value range; The first determination submodule is used to determine that the triggering condition is met if the number of times detected and the corresponding force value fall within the range of the combined mapping within a preset time.

[0053] In one embodiment, the determining module includes: The calculation submodule is used to calculate the parameter combination feature points based on the acquired control parameters; The comparison submodule is used to compare the feature points of the parameter combination with a preset parameter threshold point matrix, wherein each point in the parameter threshold point matrix corresponds to one or more predefined target application scenarios. The second determination submodule is used to determine that if the parameter combination feature point falls into a certain area of ​​the dot matrix, the conditions for triggering the application scenario corresponding to that area are met.

[0054] In one embodiment, the apparatus further includes: The receiving module is used to receive custom action configuration commands input by the user through the vehicle human-machine interface to trigger specific application scenarios; The custom action configuration instruction includes at least: expected parameters for performing a target control action on the seat belt, the expected parameters including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action; The storage module is used to establish and store the mapping relationship between the new combination of control parameters and the specific application scenario according to the custom action configuration instructions.

[0055] In one embodiment, the apparatus further includes: The calibration module is used to calibrate a first set of characteristic parameters when the occupant is wearing the seat belt during normal use of the seat belt. The first set of characteristic parameters includes at least a first reference pull-out speed. The setting module is used to set a second set of feature parameters for entering the target application scenario when setting the scene trigger threshold. The second set of feature parameters corresponds to a reference pull speed. The second reference pull speed has a preset distinguishability with the first reference pull speed, so as to distinguish between normal use actions and scene control intention actions.

[0056] In one embodiment, the acquisition module is further configured to: The control parameters of the seat belt are obtained by force sensors and / or displacement sensors located on the seat belt latch, retractor, or webbing path.

[0057] In one embodiment, the target application scenario includes a control scenario for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system switch and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching.

[0058] Figure 3 This is a schematic diagram of the hardware structure of a seatbelt-based vehicle control system according to one embodiment of this application, as shown below. Figure 3 As shown, the seatbelt-based vehicle control system includes: At least one processor 320; and, Memory 304 communicatively connected to the at least one processor 320; wherein, The memory 304 stores instructions that can be executed by the at least one processor 320 to implement the seat belt-based vehicle control method described in any of the above embodiments.

[0059] Reference Figure 3 The seatbelt-based vehicle control system 300 may include one or more of the following components: a processing component 302, a memory 304, a power supply component 306, an input / output (I / O) interface 308, a sensor component 310, and a communication component 312.

[0060] Processing component 302 typically controls the overall operation of the seatbelt-based vehicle control system 300. Processing component 302 may include one or more processors 320 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 302 may include one or more modules to facilitate interaction between processing component 302 and other components. The processor 320 may 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 may be a microprocessor or any conventional processor.

[0061] Memory 304 is configured to store various types of data to support the operation of the seatbelt-based vehicle control system 300. Examples of this data include instructions for any application or method operating on the seatbelt-based vehicle control system 300. Memory 304 can be an internal storage unit of the terminal device, such as a hard disk or memory of the terminal device. Memory 304 can also be an external storage device of the terminal device, such as a plug-in hard disk equipped on the terminal device. Memory 304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. Memory 304 is used to store programs and data required by this application. Memory 304 can also be used to temporarily store data that has been output or will be output.

[0062] Power supply assembly 306 provides power to various components of the seatbelt-based vehicle control system 300. Power supply assembly 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the seatbelt-based vehicle control system 300.

[0063] I / O interface 308 provides an interface between processing component 302 and peripheral interface modules, such as keyboards, click wheels, buttons, etc.

[0064] The sensor assembly 310 includes one or more sensors for providing status assessments of various aspects of the seatbelt-based vehicle control system 300. Additionally, the sensor assembly 310 can detect the on / off state of the seatbelt-based vehicle control system 300, the relative positioning of components, and the operational status of the seatbelt-based vehicle control system 300 or a component of the seatbelt-based vehicle control system 300. In some embodiments, the sensor assembly 310 may include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor, etc.

[0065] Communication component 312 is configured to enable the seatbelt-based vehicle control system 300 to provide wired or wireless communication capabilities with other devices and cloud platforms. The seatbelt-based vehicle control system 300 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 316 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 316 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0066] In an exemplary embodiment, the seatbelt-based vehicle control system 300 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the seatbelt-based vehicle control method described in any of the above embodiments.

[0067] This application also provides a computer-readable storage medium, which, when the instructions in the storage medium are executed by a processor corresponding to a seatbelt-based vehicle control system, enables the seatbelt-based vehicle control system to implement the seatbelt-based vehicle control method described in any of the above embodiments.

[0068] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0069] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0070] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0071] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0072] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A vehicle control method based on seat belts, characterized in that, include: After the vehicle is powered on, monitor the seat belt status; When the seat belt is detected to be in a fastened state, the control parameters of the seat belt are acquired. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window. Based on the pre-defined mapping relationship between the trigger threshold range and the target application scenario, it is determined whether the control parameters meet the conditions for triggering the target application scenario; When the control parameters meet the conditions for triggering the target application scenario, the target application scenario corresponding to the control parameters is executed.

2. The method according to claim 1, characterized in that, The control parameters are the number of times the seat belt is pulled or pulled within a preset time, and the force value detected in each pulling or pulling action. The step of determining whether the control parameters meet the conditions for triggering the target application scenario includes: The number of pull or traction actions is combined and mapped with a specific force value range; If the number of times detected and the corresponding force value fall within the range of the combined mapping within the preset time, it is determined that the triggering condition is met.

3. The method according to claim 1, characterized in that, The step of determining whether the control parameters meet the conditions for triggering the target application scenario includes: The parameter combination feature points are calculated based on the acquired control parameters; The feature points of the parameter combination are compared with a preset parameter threshold point matrix, where each point in the parameter threshold point matrix corresponds to one or more predefined target application scenarios. If the feature point of the parameter combination falls into a certain area of ​​the dot matrix, it is determined that the conditions for triggering the application scenario corresponding to that area are met.

4. The method according to claim 1, characterized in that, The method also includes the step of customizing scene manipulation actions: Receive custom action configuration commands from users via the in-vehicle human-machine interface to trigger specific application scenarios; The custom action configuration instruction includes at least: expected parameters for performing a target control action on the seat belt, the expected parameters including the control time window, the number of pulls or tractions, and the force and / or displacement characteristics of the pull or traction action; Based on the custom action configuration instructions, establish and store the mapping relationship between the new combination of control parameters and the specific application scenario.

5. The method according to claim 1, characterized in that, The method also includes a step to prevent accidental touch detection: During the normal use of the seat belt, the first set of characteristic parameters when the occupant is wearing the seat belt is calibrated, and the first set of characteristic parameters includes at least the first reference pull-out speed. When setting the scene trigger threshold, a second set of feature parameters is set for entering the target application scene. The second set of feature parameters corresponds to a reference pull speed. The second reference pull speed has a preset distinguishability with the first reference pull speed, so as to distinguish between normal use actions and scene control intention actions.

6. The method according to claim 1, characterized in that, The acquisition of the seat belt control parameters includes: The control parameters of the seat belt are obtained by force sensors and / or displacement sensors located on the seat belt latch, retractor, or webbing path.

7. The method according to any one of claims 1-6, characterized in that, The target application scenarios include control scenarios for in-vehicle equipment or functions, specifically including at least one of the following: air conditioning system switch and mode control, seat posture adjustment, window control, sunroof control, multimedia system control, ambient lighting control, or driving mode switching.

8. A vehicle control device based on a seatbelt, characterized in that, include: The monitoring module is used to monitor the seat belt status after the vehicle is powered on; The acquisition module is used to acquire the control parameters of the seat belt when the seat belt is detected to be in a fastened state. The control parameters include at least one of the following: the pulling force or traction force on the seat belt, the displacement of the pulling or traction, the speed of the pulling or traction, and the number of control actions within a preset time window. The judgment module is used to determine whether the control parameters meet the conditions for triggering the target application scenario based on the pre-calibrated mapping relationship between the trigger threshold range and the target application scenario. The execution module is used to execute the target application scenario corresponding to the control parameters when the control parameters meet the conditions for triggering the target application scenario.

9. A vehicle control system based on a seatbelt, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor to implement the seatbelt-based vehicle control method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor corresponding to the seat belt-based vehicle control system, the seat belt-based vehicle control system is able to implement the seat belt-based vehicle control method as described in any one of claims 1-7.

Images