Vehicle window breaking control method and system and vehicle

Abstract

The invention discloses a vehicle window breaking control method and system and a vehicle, relates to the technical field of vehicle control, and can comprehensively analyze various data to determine the window breaking requirement according to the real situation, improve the accuracy and success rate of window breaking execution and guarantee the safety of drivers and passengers, and the idea of the vehicle window breaking control method is as follows: obtaining multi-source heterogeneous data; the multi-source heterogeneous data is used for reflecting vehicle state information, environment perception information and safety state information; based on the multi-source heterogeneous data, whether a window breaking action needs to be executed or not is determined; under the condition that it is determined that the window breaking action needs to be executed, target window breaking force is determined based on the design parameters of the to-be-broken vehicle window; and generating a window breaking control instruction based on the target window breaking force, and sending the window breaking control instruction to a window breaking execution unit of the vehicle to control the window breaking execution unit to execute a window breaking action.

Description

Technical Field

[0001] This application relates to the field of vehicle control technology, and in particular to a vehicle window breaking control method, system and vehicle. Background Technology

[0002] Current vehicle window breaking systems have significant safety shortcomings: they mostly rely on manual triggering or single-scenario triggering, making it difficult to activate in time when the door is deformed after a collision, people are unconscious, or the windows are locked due to water pressure from drowning, thus missing an escape window; the window breaking parameters are fixed and cannot be adapted to different window materials, thicknesses, and environments such as low-temperature embrittlement and high-temperature softening, which easily leads to window breaking failure or glass shards injuring people; and they are independent of the vehicle system, with a high risk of accidental triggering, failing to guarantee the safe escape of people in emergency situations. Summary of the Invention

[0003] The purpose of this application is to provide a vehicle window breakage control method, system, and vehicle, which aims to solve the problem that the accuracy of window breakage judgment in the prior art is low and cannot guarantee the safety of personnel escape.

[0004] In a first aspect, this application provides a vehicle window breaking control method comprising: acquiring multi-source heterogeneous data; using the multi-source heterogeneous data to reflect the risk level of the vehicle in a dangerous scenario; determining whether a window breaking action needs to be performed based on the multi-source heterogeneous data; if it is determined that a window breaking action needs to be performed, determining a target window breaking force based on the design parameters of the window to be broken; generating a window breaking control command based on the target window breaking force, and sending the window breaking control command to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action.

[0005] The vehicle window breaking control method provided in this application collects multi-source heterogeneous data to perceive the risk level of the vehicle in a dangerous scenario. It then determines whether window breaking is necessary based on preset logic, accurately calculates the target window breaking force by combining the design parameters of the window to be broken, and finally generates a control command to send to the execution unit to complete the window breaking, forming a closed-loop process. This method can comprehensively analyze multi-source data, reducing the risk of misjudgment and improving the accuracy and flexibility of window breaking decisions, thereby reducing human intervention and increasing the success rate of occupants' escape in emergency situations.

[0006] In some embodiments, multi-source heterogeneous data includes, but is not limited to, at least one of the following: vehicle status data, environmental perception data, and safety status data.

[0007] In some embodiments, determining whether to perform a window-breaking action based on multi-source heterogeneous data includes: assigning corresponding weights to each type of data in the multi-source heterogeneous data; determining a comprehensive score based on each type of data and its corresponding weight; determining that a window-breaking action needs to be performed if the comprehensive score is greater than a preset threshold; and determining that a window-breaking action does not need to be performed if the comprehensive score is less than or equal to the preset threshold.

[0008] In some embodiments, determining whether a window-breaking action needs to be performed based on multi-source heterogeneous data includes: determining that no window-breaking action needs to be performed in the event of a false triggering event; the false triggering event includes at least one of the following: the multi-source heterogeneous data includes a vehicle collision signal, and the duration of the vehicle collision signal is less than a preset duration; or a manual cancellation instruction is received.

[0009] In some embodiments, the design parameters of the window to be broken include, but are not limited to, at least one of the following: window type, window size, and window material.

[0010] In some embodiments, the method further includes: sending a cooperation request to a target device during the window-breaking action performed by the window-breaking execution unit; wherein the target device includes at least one of the following: a car door, a cloud server, and a lighting system; the cooperation request is used to request the target device to cooperate with the window-breaking execution unit to assist the user in escaping.

[0011] In some embodiments, the method further includes: after the window breaking execution unit performs the window breaking action for the first time, acquiring the window stress change of the window to be broken; and determining whether the window breaking is successful based on the window stress change of the window to be broken.

[0012] In some embodiments, the method further includes: adjusting the target window breaking force and / or adjusting the window breaking action time if the initial window breaking fails; regenerating the window breaking control command based on the adjusted target window breaking force and / or adjusted window breaking action time, and sending the regenerated window breaking control command to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action again.

[0013] Secondly, this application provides a vehicle window breaking control system, which includes: a sensing unit, a domain controller, and a window breaking execution unit. The sensing unit is used to collect multi-source heterogeneous data; the multi-source heterogeneous data reflects the risk level of the vehicle in a dangerous scenario. The domain controller is used to determine whether a window breaking action needs to be performed based on the multi-source heterogeneous data; if it is determined that a window breaking action needs to be performed, it determines the target window breaking force based on the design parameters of the window to be broken; it generates a window breaking control command based on the target window breaking force and sends the window breaking control command to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action. The window breaking execution unit is used to perform the window breaking action according to the window breaking execution control command.

[0014] Thirdly, this application provides a vehicle window breaking control device, which includes an acquisition unit and a control unit; the acquisition unit is used to acquire multi-source heterogeneous data; the multi-source heterogeneous data is used to reflect the risk level of the vehicle in a dangerous scenario; the control unit is used to determine whether a window breaking action needs to be performed based on the multi-source heterogeneous data; if it is determined that a window breaking action needs to be performed, a target window breaking force is determined based on the design parameters of the window to be broken; a window breaking control command is generated based on the target window breaking force, and the window breaking control command is sent to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action.

[0015] In some embodiments, multi-source heterogeneous data includes, but is not limited to, at least one of the following: vehicle status data, environmental perception data, and safety status data.

[0016] In some embodiments, the control unit is specifically used to assign corresponding weights to various types of data in multi-source heterogeneous data; determine a comprehensive score based on various types of data and their corresponding weights; determine that a window-breaking action needs to be performed if the comprehensive score is greater than a preset threshold; and determine that a window-breaking action does not need to be performed if the comprehensive score is less than or equal to the preset threshold.

[0017] In some embodiments, the control unit is specifically configured to determine, in the event of a false triggering event, that a window-breaking action does not need to be performed; the false triggering event includes at least one of the following: multi-source heterogeneous data including a vehicle collision signal, and the duration of the vehicle collision signal is less than a preset duration; or a manual cancellation instruction is received.

[0018] In some embodiments, the design parameters of the window to be broken include, but are not limited to, at least one of the following: window type, window size, and window material.

[0019] In some embodiments, the control unit is further configured to send a cooperation request to a target device during the window-breaking action performed by the window-breaking execution unit; wherein the target device includes at least one of the following: a vehicle door, a cloud server, and a lighting system; the cooperation request is used to request the target device to cooperate with the window-breaking execution unit to assist the user in escaping.

[0020] In some embodiments, the control unit is further configured to acquire the window stress change of the window to be broken after the window breaking execution unit performs the window breaking action for the first time; and determine whether the window breaking is successful based on the window stress change of the window to be broken.

[0021] In some embodiments, the control unit is further configured to adjust the target window breaking force and / or adjust the window breaking action time if the initial window breaking fails; based on the adjusted target window breaking force and / or adjusted window breaking action time, regenerate the window breaking control command, and send the regenerated window breaking control command to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action again.

[0022] Fourthly, this application provides an electronic device comprising: a processor and a memory; the memory storing processor-executable instructions; when the processor is configured to execute the instructions, causing the electronic device to implement the method of the first aspect described above.

[0023] Fifthly, this application provides a computer-readable storage medium comprising: computer software instructions; which, when executed in an electronic device, cause the electronic device to implement the method described in the first aspect.

[0024] In a sixth aspect, the present invention provides a vehicle that includes the electronic equipment described in the fourth aspect, or the vehicle that includes the computer-readable storage medium described in the fifth aspect.

[0025] In a seventh aspect, this application provides a computer program product comprising a computer program; when the computer program is run in an electronic device, it causes the electronic device to implement the method described in the first aspect.

[0026] The beneficial effects of the second to seventh aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a schematic diagram of a vehicle window breaking control system provided in an embodiment of this application; Figure 2 A flowchart of a vehicle window breaking control method provided in an embodiment of this application; Figure 3 A flowchart of another vehicle window breaking control method provided in this application embodiment; Figure 4 A flowchart illustrating yet another vehicle window breaking control method provided in this application embodiment; Figure 5 A flowchart illustrating yet another vehicle window breaking control method provided in this application embodiment; Figure 6 A flowchart illustrating yet another vehicle window breaking control method provided in this application embodiment; Figure 7 A flowchart illustrating yet another vehicle window breaking control method provided in this application embodiment; Figure 8 A flowchart illustrating yet another vehicle window breaking control method provided in this application embodiment; Figure 9 This is a schematic diagram of a vehicle window breaking control device provided in an embodiment of this application; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0029] Reference numerals: Vehicle window breaking control system 100, sensing module 101, domain controller 102, window breaking execution module 103, auxiliary coordination module 104. Detailed Implementation

[0030] In the embodiments of this application, the terms "first," "second," "third," "fourth," "fifth," and "sixth" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first," "second," "third," "fourth," "fifth," and "sixth" may explicitly or implicitly include one or more of that feature.

[0031] In embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0032] "A and / or B" includes the following three combinations: A only, B only, and a combination of A and B.

[0033] In the embodiments of this application, "parallel," "perpendicular," and "equal" include the described situation and situations similar to the described situation, where the range of similarity is within an acceptable deviation range, which is determined by those skilled in the art taking into account the measurement under discussion and the error associated with the measurement of a particular quantity (i.e., the limitations of the measurement system). For example, "parallel" includes absolute parallelism and approximate parallelism, where the acceptable deviation range for approximate parallelism can be, for example, a deviation within 5°; "perpendicular" includes absolute perpendicularity and approximate perpendicularity, where the acceptable deviation range for approximate perpendicularity can also be, for example, a deviation within 5°. "Equal" includes absolute equality and approximate equality, where the acceptable deviation range for approximate equality can be, for example, a difference between the two equals being less than or equal to 5% of either one.

[0034] In terms of vehicle safety, window breaking systems are emergency escape-related devices, but existing technologies have many safety shortcomings and are difficult to adapt to the needs of complex emergency scenarios.

[0035] Existing window breaking systems are mostly manually triggered or triggered in a single scenario. Manual triggering fails when the door is deformed or occupants are unconscious after a collision. In scenarios involving falling into water, relying solely on a water level sensor can easily lead to false triggering during rain splashes or car washes. Furthermore, the corresponding window breaking parameters are often fixed values, failing to adapt to diverse scenarios and potentially resulting in window breaking failure or shattered glass. Additionally, existing systems are often independently configured, and the door unlocking system may not respond synchronously after a window is broken, potentially leaving the doors locked and compromising the safety of occupants.

[0036] To address the aforementioned technical problems, this application provides a vehicle window breaking control method, system, and vehicle. This method comprehensively analyzes various data points to determine window breaking requirements based on real-world situations, improving the accuracy and success rate of window breaking execution and ensuring the safety of passengers. The approach of this vehicle window breaking control method is as follows: acquiring multi-source heterogeneous data; using this multi-source heterogeneous data to reflect vehicle status information, environmental perception information, and safety status information; determining whether a window breaking action is necessary based on the multi-source heterogeneous data; if a window breaking action is determined, determining the target window breaking force based on the design parameters of the window to be broken; generating a window breaking control command based on the target window breaking force, and sending the command to the vehicle's window breaking execution unit to control the unit to perform the window breaking action.

[0037] The vehicle attitude control method, system, and vehicle provided in this application are described below with reference to the accompanying drawings.

[0038] Figure 1 This application provides a vehicle window breaking control system that can be applied to real vehicles, such as... Figure 1 As shown, the vehicle window breaking control system 100 includes a sensing module 101, a domain controller 102, a window breaking execution module 103, and an auxiliary coordination module 104, wherein the domain controller 102 is connected to the sensing module 101, the window breaking execution module 103, and the auxiliary coordination module 104 respectively.

[0039] In some embodiments, the sensing module 101 is used to collect multi-source heterogeneous data, which reflects vehicle status information, environmental perception information, and safety status information. The sensing module 101 includes at least one sensor component, and the sensor type and deployment location can be expanded according to vehicle configuration requirements.

[0040] For example, the sensor components of the sensing module 101 include an inertial measurement unit (IMU), a supplemental restraint system (SRS), a water pressure sensor, a temperature sensor, a smoke sensor, a stress sensor, and a manual switch. The IMU sensor is deployed at key locations on the vehicle body to collect real-time motion data such as vehicle acceleration and angular velocity. The SRS provides collision information such as collision intensity and location. The water pressure sensor is deployed below the doors or in easily flooded areas at the bottom of the vehicle to detect the vehicle's wading depth. The temperature and smoke sensors are deployed in the driver's and passenger compartments to collect interior temperature and smoke concentration information, respectively. The stress sensor is integrated into the window breaking execution module 103 or the window edge to detect the real-time stress state of the window. The manual switch is deployed in easily accessible locations for occupants, such as the doors and center console, to receive manual window breaking trigger signals from occupants.

[0041] In some embodiments, the domain controller 102 serves as the core control unit of the vehicle window breaking control system. It is used to determine whether a window breaking action needs to be performed based on multi-source heterogeneous data and a preset algorithm model. If it is determined that a window breaking action needs to be performed, it dynamically determines the target window breaking force by combining the design parameters of the window to be broken, real-time environmental parameters, and personnel safety status. Based on the target window breaking force, it generates a window breaking control command that includes a window breaking pressure threshold, execution duration, and coordinated action instructions, and sends the window breaking control command to the window breaking execution module 103 and the auxiliary coordination module 104. At the same time, it receives status information from each module to achieve closed-loop control.

[0042] In some embodiments, the window breaking execution module 103 is used to execute window breaking actions according to window breaking control instructions, and has a status feedback function, which can feed back the execution status and real-time status data of the window during the window breaking process to the domain controller 102.

[0043] The window breaking execution module 103 can be adapted to different types of window breaking execution devices to meet the window breaking needs of different vehicle window structures. For example, the window breaking execution module 103 can be an electromagnetic window breaker. The electromagnetic window breaker has a built-in stress sensor. After receiving the window breaking control command, it generates an instantaneous thrust through an electromagnetic coil to drive the striker to strike the window to be broken.

[0044] In some embodiments, the auxiliary coordination module 104 is used to respond to the coordination instructions of the domain controller 102, execute escape assistance operations that are associated with the window breaking action, and ensure the safe escape of personnel.

[0045] For example, the auxiliary coordination module includes a door control submodule (interfacing with the vehicle body control system), a voice alarm submodule (integrated into the in-vehicle audio system), an emergency lighting submodule (using independently powered LED emergency lights), and a communication submodule (integrating GPS positioning and 4G / 5G communication modules). After the domain controller 102 sends a coordination control command, the door control submodule controls all doors to unlock, the voice alarm submodule plays emergency prompts in a loop, the emergency lighting automatically turns on, the communication submodule obtains the vehicle's real-time GPS location and pushes it to the preset emergency contact's mobile phone, and simultaneously dials the local emergency rescue number.

[0046] It should be noted that the application scenarios of the embodiments in this application are not limited. The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of vehicle technology and the emergence of new business scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0047] Figure 2 A flowchart of a vehicle window breaking control method provided in this application embodiment is shown below. Figure 2 As shown, the method includes the following steps: S101. Obtain multi-source heterogeneous data.

[0048] Among them, multi-source heterogeneous data is used to reflect the risk level of a vehicle in a dangerous scenario. By fusing multi-dimensional data, dangerous scenarios can be perceived, providing data support for subsequent window-breaking actions and other safety measures.

[0049] In some embodiments, multi-source heterogeneous data includes, but is not limited to, at least one of vehicle status data, environmental perception data, and safety status data, with each data dimension providing a three-dimensional perception of dangerous scenarios from different perspectives. Specifically, vehicle status data reflects the real-time operating status of the vehicle and is directly related to the vehicle's own safety hazards; environmental perception data encompasses both internal and external environmental data, used to capture potential hazards around and inside the vehicle; and safety status data reflects the current physical condition and safety protection status of the occupants.

[0050] For example, the multi-source heterogeneous data may specifically include: water pressure data, temperature data, and smoke concentration data inside the vehicle compartment; vehicle speed data and acceleration data during vehicle operation; and collision force data and collision angle data when a collision occurs. The above data can be collected in real time through the vehicle's built-in sensors (such as pressure sensors, temperature sensors, smoke sensors, vehicle speed sensors, acceleration sensors, and collision sensors) or external detection equipment to ensure the authenticity and timeliness of the data.

[0051] In some embodiments, the data acquisition process is as follows: the vehicle starts automatically within 50ms-200ms (preferably 100ms) after power-on, without manual intervention. Before starting, the domain controller kernel initialization (such as loading memory, peripheral interface drivers, etc.) must be completed. A communication link with the sensor and window breaker is established based on the CANFD protocol. The basic parameters of the window (such as material and thickness) are retrieved from the local database through the vehicle identification number (VIN) to provide basic data for subsequent target window breaking force calculation.

[0052] In some embodiments, after initialization, multi-source heterogeneous data are synchronously collected at a period of 10ms-50ms. For example, the IMU collects acceleration and combines it with the airbag system data to determine whether a collision has occurred; the water pressure sensor collects water level data for drowning determination (e.g., water level greater than 50cm is determined to be a drowning scenario); the temperature and smoke sensor collects data for fire determination (e.g., temperature greater than 80℃ and smoke concentration greater than 0.1mg / m³ is determined to be a fire inside the vehicle); and the window status signal is collected (the window stress sensor collects edge stress values, with a range of 0N-5000N).

[0053] In some embodiments, the acquired multi-source heterogeneous data is filtered by using a 3rd to 8th order (preferably 5th order) low-pass filter to filter the IMU acceleration signal, with the cutoff frequency set to 800Hz-1500Hz (preferably 1kHz) to filter out high-frequency noise.

[0054] S102. Based on multi-source heterogeneous data, determine whether a window-breaking action needs to be performed.

[0055] In some embodiments, the vehicle is equipped with a window breaking execution module, which can apply pressure to the four corners or edges of the vehicle's side windows (avoiding the windshield and rear windshield) to cause the window glass to quickly disintegrate into small particles, thus completing the window breaking action.

[0056] In some embodiments, the specific implementation of determining whether to perform a window-breaking action based on multi-source heterogeneous data can be found in S301-S302, and will not be elaborated here.

[0057] S103. If it is determined that a window breaking action needs to be performed, the target window breaking force shall be determined based on the design parameters of the window to be broken.

[0058] In some embodiments, the design parameters of the window to be broken include, but are not limited to, at least one of the following: window type, window size, and window material.

[0059] Examples include: windshield, side windows, and rear window; window dimensions including length, width, area, and thickness; and window materials such as tempered glass, laminated tempered glass, and acrylic glass.

[0060] In some embodiments, when calculating the target window breaking force, the corresponding benchmark window breaking force is first retrieved from a preset database based on the design parameters of the window to be broken, and then the calculation is optimized in combination with the actual scenario requirements.

[0061] In some embodiments, a preset database stores basic window parameters and corresponding benchmark window breaking forces for various types of passenger vehicles. The benchmark parameters are stored in categories according to window material and window size (such as thickness) to ensure accurate retrieval.

[0062] For example, the pre-stored parameters in the database include: the benchmark breaking force of 5mm thick tempered glass is 5000N, and the benchmark breaking force of 5mm thick laminated glass is 6500N.

[0063] In some embodiments, the determination of the target window breaking force may also be modified in conjunction with the real-time environment (such as a low-temperature environment) or the window status.

[0064] S104. Generate a window breaking control command based on the target window breaking force, and send the window breaking control command to the window breaking execution unit of the vehicle to control the window breaking execution unit to perform the window breaking action.

[0065] In some embodiments, a corresponding Pulse Width Modulation (PWM) control command is generated based on the target window breaking force. The control command is sent to the window breaking execution unit via the CANFD bus, and the working status data (such as drive current) fed back by the window breaking execution unit is received. The feedback data is compared with the target value to calculate the deviation, and the duty cycle of the PWM is adjusted in real time according to the deviation to ensure that the actual window breaking force reaches the target window breaking force.

[0066] For example, if the actual current value of the drive current deviates from the target value by more than 10%, such as a target value of 1A and an actual value of 0.8A, then the PWM duty cycle is adjusted.

[0067] The vehicle window breaking control method provided in this application collects multi-source heterogeneous data to perceive the risk level of the vehicle in a dangerous scenario. It then determines whether window breaking is necessary based on preset logic, accurately calculates the target window breaking force by combining the design parameters of the window to be broken, and finally generates a control command to send to the execution unit to complete the window breaking, forming a closed-loop process. This method can comprehensively analyze multi-source data, reducing the risk of misjudgment and improving the accuracy and flexibility of window breaking decisions, thereby reducing human intervention and increasing the success rate of occupants' escape in emergency situations.

[0068] Since the acquisition of multi-source heterogeneous data depends on various sensing elements of the sensing module, such as collision sensors, water level sensors, temperature sensors, smoke sensors, and window stress sensors, it is necessary to test the working status of each sensing element and the data acquisition loop before making a judgment to ensure the effectiveness of the data collection source and guarantee the safety of drivers and passengers.

[0069] Based on the above, this embodiment further optimizes the implementation of acquiring multi-source heterogeneous data (S101). Specifically, the on / off state of the acquisition loop of multi-source heterogeneous data is detected; when the on / off state of the acquisition loop is normal, multi-source heterogeneous data is acquired; when the on / off state of the acquisition loop is abnormal, an abnormal prompt message is issued.

[0070] In some embodiments, a sensor self-test is initiated to detect the continuity of circuits. After the vehicle system starts, a self-test is first performed on all critical sensing components, checking the continuity of each sensor's data acquisition circuit one by one. If a fault such as an open circuit is detected in a sensor, the corresponding fault code (e.g., "collision sensor communication fault") is recorded immediately. If no abnormality such as an open circuit is detected, the continuity of the circuit is temporarily determined to be normal. After completing the continuity test, the results are processed according to the situation to ensure that data acquisition or emergency response capabilities are not interrupted.

[0071] In some embodiments, if all sensor circuit continuity tests are normal, the system enters normal operation mode and continuously acquires multi-source heterogeneous data according to preset acquisition logic. This provides effective data support for subsequent related actions (such as breaking windows) and achieves reliable data acquisition. If one or more sensor circuits are abnormal, an error message is triggered, and a specific fault code is displayed on the vehicle's dashboard. This informs the user that there is a problem with the data acquisition circuit, clarifies the fault type, and reminds the user to have the vehicle inspected in a timely manner. This ensures that the system still has basic emergency capabilities in the event of a fault, while retaining the function of manually triggering the window-breaking action. For example, a physical button can be set up to trigger the window-breaking action, and a trigger logic can be set up to activate it by pressing and holding (e.g., for more than 1 second).

[0072] By using the above method, the data acquisition loop is first detected before acquiring multi-source heterogeneous data. The decision on whether to continue acquiring multi-source heterogeneous data is made based on the detection results. This ensures the reliability of acquiring multi-source heterogeneous data when the loop is normal, and provides timely alerts when the loop is abnormal, thus avoiding security risks caused by data acquisition failure.

[0073] Figure 3 A flowchart of another vehicle window breaking control method provided in the embodiments of this application is shown below. Figure 3 As shown, S101 can be implemented as S201-S203 as follows: S201. Obtain the original multi-source heterogeneous data.

[0074] In some embodiments, raw multi-source heterogeneous data refers to raw data directly acquired through various sensing devices, including but not limited to data collected by various sensing devices mounted on the vehicle such as temperature sensors, water level sensors, and stress sensors. The data types cover physical quantity data (such as temperature, water level, and stress values) and state data.

[0075] S202. Identify outliers in the original multi-source heterogeneous data that exceed the preset range.

[0076] In some embodiments, the preset range is a physically reasonable range or normal working range set for different types of raw data. The range is determined based on the performance parameters of the sensing device, the actual working scenario requirements of the vehicle, and the data validity threshold. The preset range for different types of data can be configured independently.

[0077] In some embodiments, identifying outliers in the original multi-source heterogeneous data that exceed a preset range involves comparing each type of original data with its corresponding preset range. If the value of a certain original data exceeds the upper limit of the preset range of its type or is lower than the lower limit of the preset range, then the data is determined to be an outlier.

[0078] For example, different types of data may include temperature data, water level data, and stress data.

[0079] S203. Remove or correct outliers to obtain multi-source heterogeneous data.

[0080] In some embodiments, outliers are removed or corrected, and a differentiated processing strategy is adopted according to the type of the original data and the outlier: for data with historical data reference and which can be corrected by reasonable interpolation or mean calculation after an anomaly, correction processing is adopted; for data without effective correction basis and which will interfere with scene judgment or parameter calculation after an anomaly, removal processing is adopted and the data is marked as invalid data.

[0081] For example, the handling methods for outliers corresponding to different types of data are as follows: Temperature data: The default normal operating range is -40℃ to 85℃. When the raw data collected by the temperature sensor exceeds this range, it is judged as an outlier. At this time, the mean of the valid data collected by the temperature sensor in the previous N times (N is a preset positive integer, preferably N=5) is used to calculate the mean value. This mean value is used to replace the outlier value to ensure the validity of subsequent window breaking parameters (such as the window breaking force coefficient based on temperature adjustment).

[0082] Water level data: The preset physical reasonable range is 0cm-200cm (corresponding to the effective monitoring range for vehicle wading scenarios). When the raw data collected by the water level sensor is less than 0cm or greater than 200cm, it is judged as an outlier. Since there is no effective basis for correcting such data after it becomes abnormal, and it may interfere with the judgment of emergency wading scenarios, such outliers are removed and directly marked as invalid data.

[0083] Stress data (pre-collected data during the non-window breaking action execution phase): The preset physical reasonable range is 0N-10000N. When the raw data collected by the stress sensor exceeds this range, it is judged as an outlier, and is discarded and marked as invalid data to avoid affecting the accuracy of emergency scenario judgment.

[0084] In some embodiments, after outlier removal or correction, all valid data (including the original data without outliers and the corrected valid data) are integrated to form the final multi-source heterogeneous data used to determine whether window breaking is necessary.

[0085] Figure 4 A flowchart of another vehicle window breaking control method provided in the embodiments of this application is shown below. Figure 4 As shown, S102 can be implemented as follows: S301-S302: S301. Assign corresponding weights to each type of data in the multi-source heterogeneous data.

[0086] In some embodiments, when determining whether a window-breaking action needs to be performed, different types of data in the multi-source heterogeneous data have different degrees of influence on the necessity of determining whether a window-breaking action needs to be performed. Therefore, corresponding weights can be assigned according to the degree of influence of different types of data on the determination result, and comprehensive analysis can be carried out in combination with the multi-source heterogeneous data.

[0087] For example, the multi-source heterogeneous data includes collision signals, water level / fire signals, and trapped personnel signals. Collisions are the most direct and high-risk emergency scenario, potentially causing door deformation and unconsciousness, requiring priority response. Drowning and fire scenarios develop rapidly; missing the window-breaking opportunity can lead to suffocation or burns, making them the second most dangerous after collisions. Information from other systems is used to determine if occupants are attempting to escape (e.g., opening doors or windows), ensuring that window breaking is only triggered when occupants are truly trapped. Therefore, the collision signal weight is set to 60%, the water level / fire signal weight to 30%, and the trapped personnel signal weight to 30%.

[0088] S302. Determine the comprehensive score based on various types of data and their corresponding weights.

[0089] Furthermore, if the overall score is greater than a preset threshold (e.g., 60 points), it is determined that a window-breaking action needs to be performed; if the overall score is less than or equal to the preset threshold, it is determined that no window-breaking action needs to be performed.

[0090] In some embodiments, the scores of each type of data in the multi-source heterogeneous data are calculated by multiplying each type of data by its corresponding weight, and finally the scores of each type of data are added together to obtain a comprehensive score.

[0091] In real-world scenarios, multi-source heterogeneous data is susceptible to complex environmental factors such as road bumps and instantaneous vibrations, as well as the sensitivity of the sensors themselves, which can lead to false triggering signals. Therefore, a false triggering identification mechanism can be set up to ensure the reliability and practicality of the system response.

[0092] In some embodiments, the determination result of whether to perform a window-breaking action based on multi-source heterogeneous data (step S102) can be specifically implemented as follows: in the event of a false triggering event, it is determined that no window-breaking action needs to be performed; Among them, the falsely triggered events include at least one of the following: (1) The multi-source heterogeneous data includes vehicle collision signals, and the duration of the vehicle collision signals is less than the preset duration.

[0093] In some embodiments, in the event of a false triggering event (1), the vehicle collision signal can be considered as an interference signal in a non-real collision scenario, such as instantaneous interference caused by factors such as road bumps, which is a false triggering event.

[0094] This application does not impose a single limit on the specific value of the preset duration. It can be flexibly set according to the vehicle type (passenger car, commercial vehicle, etc.). For example, it can be set to 100ms. In actual applications, it can also be adjusted to other reasonable values ​​through statistical analysis of a large amount of experimental data or according to actual needs.

[0095] (2) Received manual cancellation instruction.

[0096] In some embodiments, the manual cancellation command is triggered by a person inside the vehicle through a preset operation. Upon receiving the command, it is determined to be a false triggering event, and the subsequent execution of the window breaking action is terminated.

[0097] In some embodiments, after collecting multi-source heterogeneous vehicle data through multi-source sensors and initiating the window-breaking action judgment process, the system first identifies false triggering events in the data and external commands: On one hand, it detects whether the multi-source heterogeneous data contains a vehicle collision signal. If such a collision signal exists, its duration is further extracted and compared with a preset duration (such as 100ms as mentioned above, the specific value of which can be flexibly adjusted). If the duration of the collision signal is less than the preset duration, it is determined to be a false triggering event caused by factors such as road bumps or instantaneous vibrations. On the other hand, it monitors in real time whether a manual cancellation command is received from the driver or authorized personnel. If such a command is received, it is also determined to be a false triggering event. When any of the above false triggering events is identified, the judgment result "no need to perform window-breaking action" is output, and the subsequent window-breaking execution process is terminated; if no false triggering event is detected, the window-breaking execution process continues.

[0098] It is understandable that by further clarifying the specific judgment logic for determining whether to perform a window-breaking action based on multi-source heterogeneous data, and identifying false triggering events, unnecessary window-breaking operations in false triggering scenarios can be avoided, ensuring the reliability and rationality of window-breaking control.

[0099] To ensure successful window breaking, a process for determining success can be set after the window breaking execution unit performs the window breaking action for the first time.

[0100] like Figure 5 As shown, the steps include S401-S402: S401. After the window breaking unit performs the window breaking action for the first time, obtain the window stress change of the window to be broken.

[0101] In some embodiments, the stress change of the vehicle window to be broken is obtained by acquiring the stress signal of the vehicle window before and after the window breaking action through a vehicle window stress sensor. The stress signal includes the real-time stress value and the stress change rate.

[0102] S402. Based on the stress changes of the window to be broken, determine whether the window breaking was successful.

[0103] In some embodiments, the success of breaking a window is determined based on the stress change of the window, using a preset stress change judgment rule. The judgment rule may include a stress drop amplitude threshold and a stress drop time threshold. When the stress value is detected to drop to or exceed the stress drop amplitude threshold within the stress drop time threshold, the window is determined to be broken successfully; otherwise, the window is determined to be broken unsuccessfully.

[0104] For example, the stress drop time threshold is set to 10ms, and the stress drop amplitude threshold is set to 50%. When the window stress sensor detects that the stress value of the window to be broken drops by more than 50% within 10ms from the initial stress level (such as any value in the range of 2000N-5000N) (for example, from 3000N to 1200N), the window is determined to be broken successfully. If the stress drop amplitude does not reach 50% within 10ms, the window is determined to be broken unsuccessfully.

[0105] In some embodiments, the detection period for obtaining the stress change of the vehicle window is set to a preset fixed period to achieve rapid feedback of the window breaking result. The value range of the preset fixed period is 30ms-100ms, preferably 50ms, to ensure that sufficient escape window period is reserved for possible secondary window breaking actions and to avoid missing the best window breaking opportunity due to detection delay.

[0106] Based on the above, if breaking the window fails, relevant remedial measures should be implemented to attempt a second window breaking.

[0107] Combination Figure 5 ,like Figure 6 As shown, it also includes the following S501-S502: S501. If the initial window breaking attempt fails, adjust the target window breaking force and / or adjust the window breaking action time.

[0108] In some embodiments, scenarios that lead to failure of the first window breakage attempt include, but are not limited to, only the outer layer of the laminated glass breaking, or the low-temperature environment causing the glass to become more ductile and not completely break.

[0109] In some embodiments, adjusting the target window breaking force includes adjusting the window breaking pressure parameter of the window breaking execution unit. The adjustment method is to determine the target window breaking force by multiplying the initial parameter at the time of the first window breaking by a preset adjustment coefficient. The preset adjustment coefficient ranges from 1.1 to 1.5 times, preferably 1.2 times. That is, the adjusted target window breaking force P' = P × k, where k is the preset adjustment coefficient and P is the initial pressure at the time of the first window breaking. By enhancing the parameter, the window breaking energy of the second window breaking is improved, ensuring the success of the window breaking.

[0110] In some embodiments, the window-breaking action time is adjusted, and the adjusted action time T' = T × n, where n is a preset adjustment coefficient (n ranges from 1.1 to 1.5 times, preferably 1.2 times), and T is the initial action time for the first window breaking.

[0111] In some embodiments, the window-breaking force and the window-breaking time can be adjusted simultaneously or separately.

[0112] S502. Based on the adjusted target window breaking force and / or the adjusted window breaking action time, regenerate the window breaking control command and send the regenerated window breaking control command to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action again.

[0113] In some embodiments, when the window-breaking execution unit performs the window-breaking action again, an execution interval is set between the first window-breaking action and the second window-breaking action. The value of the execution interval is in the range of 0.8s-1.5s, preferably 1s, so as to avoid the window-breaking execution unit from overheating and being damaged due to continuous high-load operation, extend the service life of the execution unit and ensure its working stability.

[0114] In some embodiments, the window breaking execution unit adopts PWM closed-loop control. During the first and second window breaking processes, the operating current of the window breaking execution unit is detected in real time, and the current deviation value is calculated. When the current deviation value exceeds the preset deviation threshold (preferably 10%), the duty cycle of the PWM control signal is automatically adjusted to compensate for the influence of current fluctuation on the window breaking force, thereby further improving the reliability and success rate of the window breaking action.

[0115] To improve the efficiency and safety of vehicle window breaking escape, multiple devices in the vehicle can work together to provide auxiliary support for the user's escape during the window breaking action, maximizing the smoothness and safety of the escape.

[0116] like Figure 7 As shown, the vehicle window breaking control method also includes S601: S601. During the window breaking action performed by the window breaking execution unit, a coordination request is sent to the target device.

[0117] The target device includes at least one of the following: a car door, a cloud server, or a lighting system; the coordination request is used to request the target device to coordinate with the window-breaking execution unit to assist the user in escaping.

[0118] In some embodiments, the window breaking execution unit performs the window breaking action in a process that includes a pre-break window preparation stage, a window breaking execution stage, and an escape and rescue stage after the window is broken. According to the escape needs of different stages, coordination requests are sent in time. The sending sequence is coordinated and scheduled by the vehicle domain controller to ensure that the actions of each target device are synchronized and accurately matched with the window breaking process, so as to realize the full-process coordinated closed loop of "window breaking-escape-rescue".

[0119] In some embodiments, the collaboration request is sent to each target device via a high-speed communication bus preset by the vehicle. The high-speed communication bus includes, but is not limited to, the CANFD bus, to ensure the real-time transmission and execution response of the collaboration command and avoid the collaboration effect being affected by communication delay.

[0120] I. Collaboration requests during the preparation phase before breaking the window (corresponding to the initiation of the window breaking action) In some embodiments, when the system determines that the emergency scenario is real (i.e. before the window breaking execution unit is started, the trigger timing can be set to the window breaking action start time t=0ms), it sends a first type of cooperation request to target devices such as car doors, window motors, and voice alarm modules. The first type of cooperation request is used to clear escape obstacles and avoid potential risks in the window breaking process.

[0121] For example, the specific execution process of the first type of collaborative request includes: (1) Send an unlocking coordination request to the door unlocking motor. The request includes an unlocking command for a preset duration (the preset duration ranges from 100ms to 300ms, preferably 200ms), which drives the door lock mechanism to ensure that the door is unlocked after the window is broken, thus preventing the door from being locked and hindering the escape of personnel.

[0122] (2) Send a power-off coordination request to the window lift motor to cut off the power supply circuit of the window lift motor and prevent the motor from being accidentally triggered during the window breaking process, which could lead to short circuit or mechanical damage.

[0123] (3) Send a voice prompt coordination request to the voice alarm module and control the in-vehicle audio equipment to play the preset escape reminder voice in a loop (the voice volume is preset to 70dB-90dB, preferably 80dB, to ensure that the ambient noise in the vehicle is covered). The reminder voice includes content such as "The window is about to break, please stay away from the window", which is used to warn the people in the vehicle to avoid the window area and reduce the risk of glass fragments injuring people when the window breaks.

[0124] II. Coordination requests during the escape and rescue phase after breaking a window (after the window-breaking action is successful) In some embodiments, when the window breaking execution unit successfully breaks the window (the trigger timing can be set to t=1000ms-2000ms after the successful window breaking, preferably 1500ms), a second type of cooperation request is sent to target devices such as lighting systems, cloud servers, and safety auxiliary devices. The second type of cooperation request is used to optimize the escape environment and accelerate the external rescue response.

[0125] For example, the specific execution process of the second type of collaborative request includes: (1) Send an emergency lighting coordination request to the vehicle lighting system to control the emergency lights inside the vehicle to turn on and illuminate the escape route inside the vehicle. This is suitable for low light or dark environments such as nighttime and tunnels, and improves escape efficiency.

[0126] (2) Send a distress request to the cloud server and push the distress information to the cloud platform through the vehicle network terminal (T-BOX). The distress information should include at least the real-time location information of the vehicle (the positioning accuracy is preset to within ±10m) and the cause of the broken window (such as collision, drowning, fire, etc.) to shorten the response time of rescue personnel.

[0127] (3) Send an unlocking coordination request to safety auxiliary equipment (such as airbag-related equipment) to control the unlocking of the airbag-related locking mechanism, further opening up the escape route and improving the safety of personnel evacuation.

[0128] In some embodiments, after the collaborative action is completed, the system automatically shuts off the unnecessary power supply to the window-breaking related modules and collaborative devices, so that the system returns to a low-power standby state (standby power consumption is preset to <10mA), avoiding continuous power consumption from affecting the vehicle's battery charge.

[0129] In some embodiments, the target device may also include a vehicle voice alarm module, a window motor, an airbag control module, a vehicle networking terminal (T-BOX), etc. The specific content of the coordination request is customized according to the functional characteristics of the target device to ensure that the coordinated actions of each device are highly compatible with the window breaking process and escape needs, so as to achieve full coverage from window breaking preparation to escape and rescue, rather than a single window breaking action.

[0130] The vehicle window breaking control method provided in this application is described below through a complete embodiment, such as... Figure 8 As shown, the process includes the following: S1. The vehicle is powered on, and the system initializes.

[0131] S2. Determine if the multi-source heterogeneous data acquisition loop is normal.

[0132] If not, then execute S3; If so, proceed with S4 and subsequent steps.

[0133] S3. Display an error message.

[0134] S4. Obtain multi-source heterogeneous data.

[0135] S5. Determine whether to perform a window-breaking action based on multi-source heterogeneous data.

[0136] If not, then execute S5 repeatedly; If so, proceed with S6 and subsequent steps.

[0137] S6. Determine if it was triggered accidentally.

[0138] If so, return to execute S5; If not, proceed to step S7 and subsequent steps.

[0139] S7. Calculate the target window breaking force based on the design parameters of the window to be broken.

[0140] S8. Execute the window-breaking action based on the target window-breaking force control.

[0141] S9 is executed simultaneously with S8.

[0142] S9, multi-module collaboration.

[0143] S10. Determine whether the window was successfully broken.

[0144] If so, the window breaking is complete; If not, proceed to S11 and subsequent steps.

[0145] S11, Adjust the target window breaking force.

[0146] S12. Perform secondary window breaking based on the adjusted target window breaking force.

[0147] As can be seen, the above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, the embodiments of this application provide corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention.

[0148] This application embodiment can divide the vehicle window breaking control device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0149] Figure 9 This is a schematic diagram of a vehicle window breaking control device provided in an embodiment of this application, used to implement the vehicle window breaking control method provided in the above embodiments, such as... Figure 9As shown, the vehicle window breaking control device 600 includes an acquisition unit 601 and a control unit 602. The acquisition unit 601 is used to acquire multi-source heterogeneous data. The multi-source heterogeneous data is used to reflect the risk level of the vehicle in a dangerous scenario. The control unit 602 is used to determine whether a window breaking action needs to be performed based on the multi-source heterogeneous data. If it is determined that a window breaking action needs to be performed, a target window breaking force is determined based on the design parameters of the window to be broken. A window breaking control command is generated based on the target window breaking force, and the window breaking control command is sent to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action.

[0150] In some embodiments, multi-source heterogeneous data includes, but is not limited to, at least one of the following: vehicle status data, environmental perception data, and safety status data.

[0151] In some embodiments, the control unit 602 is specifically used to assign corresponding weights to various types of data in multi-source heterogeneous data; determine a comprehensive score based on various types of data and their corresponding weights; determine that a window-breaking action needs to be performed if the comprehensive score is greater than a preset threshold; and determine that a window-breaking action does not need to be performed if the comprehensive score is less than or equal to the preset threshold.

[0152] In some embodiments, the control unit 602 is specifically configured to determine, in the event of a false triggering event, that there is no need to perform the window-breaking action; the false triggering event includes at least one of the following: multi-source heterogeneous data includes a vehicle collision signal, and the duration of the vehicle collision signal is less than a preset duration; or a manual cancellation instruction is received.

[0153] In some embodiments, the design parameters of the window to be broken include, but are not limited to, at least one of the following: window type, window size, and window material.

[0154] In some embodiments, the control unit 602 is further configured to send a cooperation request to a target device during the window-breaking action performed by the window-breaking execution unit; wherein the target device includes at least one of the following: a car door, a cloud server, and a lighting system; the cooperation request is used to request the target device to cooperate with the window-breaking execution unit to assist the user in escaping.

[0155] In some embodiments, the control unit 602 is further configured to acquire the window stress change of the window to be broken after the window breaking execution unit performs the window breaking action for the first time; and determine whether the window breaking is successful based on the window stress change of the window to be broken.

[0156] In some embodiments, the control unit 602 is further configured to adjust the target window breaking force and / or adjust the window breaking action time if the first window breaking fails; based on the adjusted target window breaking force and / or adjusted window breaking action time, regenerate the window breaking control command, and send the regenerated window breaking control command to the window breaking execution unit of the vehicle to control the window breaking execution unit to perform the window breaking action again.

[0157] When implementing the functions of the integrated modules described above in hardware, this embodiment of the invention provides a possible structural diagram of the electronic device involved in the above embodiments. For example... Figure 10 As shown, the electronic device 700 includes: a processor 702, a communication interface 703, and a bus 704. Optionally, the electronic device 700 may also include a memory 701.

[0158] Processor 702 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 702 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 702 may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0159] The communication interface 703 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0160] The memory 701 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0161] As one possible implementation, the memory 701 can exist independently of the processor 702. The memory 701 can be connected to the processor 702 via a bus 704 and is used to store instructions or program code. When the processor 702 calls and executes the instructions or program code stored in the memory 701, it can implement the vehicle window breaking control method provided in this embodiment of the invention.

[0162] In another possible implementation, the memory 701 can also be integrated with the processor 702.

[0163] The 704 bus can be an extended industry standard architecture (EISA) bus, etc. The 704 bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0164] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.

[0165] This application also provides a computer-readable storage medium. All or part of the processes in the above method embodiments can be instructed by computer program instructions to be completed by related hardware. This program can be stored in the aforementioned computer-readable storage medium. When the computer program instructions are executed on a computer, the computer causes the computer to perform the vehicle window breaking control method as described in any of the above embodiments.

[0166] Exemplary examples of computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0167] This application also provides a vehicle that includes the above-described electronic device, or the vehicle that includes the above-described computer-readable storage medium.

[0168] This application also provides a computer program product comprising a computer program that, when run on a computer, causes the computer to execute any of the vehicle window breaking control methods provided in the above embodiments.

[0169] In the description of the embodiments of this application, specific features, structures, materials or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0170] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for controlling vehicle window breakage, characterized in that, The method includes: Acquire multi-source heterogeneous data; the multi-source heterogeneous data is used to reflect the risk level of a vehicle in a dangerous scenario; Based on the aforementioned multi-source heterogeneous data, determine whether a window-breaking action needs to be performed; If it is determined that a window-breaking action needs to be performed, the target window-breaking force is determined based on the design parameters of the window to be broken; A window breaking control command is generated based on the target window breaking force, and the window breaking control command is sent to the window breaking execution unit of the vehicle to control the window breaking execution unit to perform the window breaking action.

2. The vehicle window breakage control method according to claim 1, characterized in that, The multi-source heterogeneous data includes, but is not limited to, at least one of the following: vehicle status data, environmental perception data, and safety status data.

3. The vehicle window breakage control method according to claim 2, characterized in that, The step of determining whether to perform a window-breaking action based on the multi-source heterogeneous data includes: Each type of data in the multi-source heterogeneous data is assigned a corresponding weight; Based on the various types of data and their corresponding weights, a comprehensive score is determined. If the overall score is greater than a preset threshold, it is determined that a window-breaking action needs to be performed; If the overall score is less than or equal to the preset threshold, it is determined that no window-breaking action needs to be performed.

4. The vehicle window breakage control method according to claim 2, characterized in that, The step of determining whether to perform a window-breaking action based on the multi-source heterogeneous data includes: In the event of a false trigger, it is determined that there is no need to perform the window-breaking action; The false triggering event includes at least one of the following: The multi-source heterogeneous data includes vehicle collision signals, and the duration of the vehicle collision signals is less than a preset duration. Received manual cancellation instruction.

5. The vehicle window breakage control method according to claim 1, characterized in that, The design parameters of the window to be broken include, but are not limited to, at least one of the following: window type, window size, and window material.

6. The vehicle window breakage control method according to claim 1, characterized in that, The method further includes: During the window-breaking action performed by the window-breaking execution unit, a cooperation request is sent to the target device; wherein, the target device includes at least one of the following: a car door, a cloud server, and a lighting system; the cooperation request is used to request the target device to cooperate with the window-breaking execution unit to assist the user in escaping.

7. The vehicle window breakage control method according to any one of claims 1-6, characterized in that, The method further includes: After the window breaking unit performs the window breaking action for the first time, the stress change of the window to be broken is obtained; Based on the stress changes in the vehicle window to be broken, it is determined whether the window breaking was successful.

8. The vehicle window breakage control method according to claim 7, characterized in that, The method further includes: If the initial window breaking attempt fails, adjust the target window breaking force and / or adjust the window breaking action time; Based on the adjusted target window breaking force and / or the adjusted window breaking action time, a new window breaking control command is generated and sent to the vehicle's window breaking execution unit to control the window breaking execution unit to perform the window breaking action again.

9. A vehicle window breaking control system, characterized in that, The system includes: Sensing unit, domain controller, window breaking execution unit; The sensing unit is used to collect and acquire multi-source heterogeneous data; the multi-source heterogeneous data is used to reflect the risk level of the vehicle in a dangerous scenario; The domain controller is used to determine whether a window-breaking action needs to be performed based on the multi-source heterogeneous data. If it is determined that a window-breaking action needs to be performed, the target window-breaking force is determined based on the design parameters of the window to be broken; A window breaking control command is generated based on the target window breaking force, and the window breaking control command is sent to the window breaking execution unit of the vehicle to control the window breaking execution unit to perform the window breaking action; The window breaking execution unit is used to execute window breaking actions according to the window breaking execution control command.

10. A vehicle, characterized in that, The vehicle implements the vehicle window breaking control method as described in any one of claims 1 to 8, or includes the vehicle window breaking control system as described in claim 9.

Images