A multi-state fusion monitoring and remote linkage control method for a vehicle window ventilation device

Abstract

The application discloses a kind of car window ventilation equipment multi-state fusion monitoring and remote linkage control method, it is related to vehicle ventilation equipment monitoring and control field, comprising: acquisition deployment, ventilation, operation control and historical monitoring data, the descending, ascending transition position of air deflector cover in the car window lifting cycle is extracted, and two-way deployment transition feature pair is formed;Based on historical data to establish deployment reference corridor, according to the co-directional offset, difference offset and cross-cycle change of feature pair to identify installation state;When meeting calibration condition, generate and verify candidate start-stop boundary, determine safety deployment boundary;Combined with ventilation response, installation state and operation control data to generate local allowed control range, adjudicate remote instruction and output fan control and alarm linkage result. Through two-way deployment transition feature to identify installation drift and calibrate safety control boundary, combined with ventilation response and operating state to adjudicate remote instruction, improve equipment monitoring, control and abnormal alarm capability.

Description

Technical Field

[0001] This invention relates to the field of vehicle ventilation equipment monitoring and control, specifically a method for multi-state fusion monitoring and remote linkage control of vehicle window ventilation equipment. Background Technology

[0002] Vehicle side window ventilation systems are typically installed near the window glass or window opening, forming a ventilation channel through the window's operation in conjunction with the air guide assembly. For devices that are attached to the window glass using an adhesive method, the installation location will affect the window position corresponding to the deployment and retraction of the air guide assembly and the start / stop of the fan.

[0003] Vehicle vibrations, changes in interior temperature, stress on the adsorption components, and repeated window raising and lowering can cause the equipment to slowly shift relative to the window glass. After this shift, the window position corresponding to the air guide assembly entering and exiting the working state will change accordingly. Existing position detection methods typically only determine whether the air guide assembly is currently in place, but cannot distinguish whether the positional change is caused by overall equipment installation drift or by abnormal operation of the air guide assembly. Furthermore, when controlling the fan using a fixed window position, there may be mismatches between the start or stop position and the actual deployment position.

[0004] Therefore, it is necessary to improve the ability of vehicle window ventilation equipment to identify changes in installation position, distinguish between calibrable stable installation drift, ongoing installation slip that is still expanding, and abnormal operation of air guide components, and keep the fan control boundary matched with the actual deployment position of the equipment, thereby reducing the impact of changes in installation position on the normal operation of the equipment. Summary of the Invention

[0005] Based on the shortcomings of the prior art described above, the purpose of this invention is to provide a method for multi-state fusion monitoring and remote linkage control of vehicle window ventilation equipment to solve the above-mentioned technical problems.

[0006] To achieve the above objectives, the present invention provides the following technical solution: a method for multi-state fusion monitoring and remote linkage control of vehicle window ventilation equipment, comprising: S1: Acquire deployment monitoring data, ventilation monitoring data, operation control data and historical monitoring data. Based on the deployment monitoring data, extract the downward deployment confirmation position corresponding to the air guide cover entering the working state and the upward back pressure start position corresponding to leaving the working state within the same window lifting cycle, and form the current two-way deployment change feature pair. S2: Establish a deployment baseline corridor based on historical monitoring data, and identify the installation status based on the co-directional offset, differential offset and cross-cycle change characteristics of the relative deployment baseline corridor according to the current bidirectional deployment transformation characteristics; S3: When the installation status meets the calibration conditions in the operation control data, candidate start boundary and candidate stop boundary are generated based on the current bidirectional deployment transformation characteristics. The candidate start boundary and candidate stop boundary are verified based on deployment monitoring data and ventilation monitoring data. The current safe deployment boundary is determined based on the installation status and verification results. S4: Determine the ventilation response status based on ventilation monitoring data and historical monitoring data, generate the local allowable control range by combining the current safety deployment boundary, installation status, ventilation response status and operation control data, adjudicate remote control commands based on the local allowable control range, and output fan control results and alarm linkage results.

[0007] The present invention is further configured such that the vehicle window ventilation device includes: a controller, a storage component, a status acquisition component, a communication component, a display area facing the outside of the vehicle, and a speaker component, wherein the status acquisition component includes: a vehicle window operation status acquisition component, an air guide cover status acquisition component, a fan operation status acquisition component, an environmental status acquisition component, and a power supply status acquisition component; Use the status acquisition component to obtain deployment monitoring data, ventilation monitoring data, and power supply status data; Use communication components to acquire communication control data; Read control configuration data and historical monitoring data from the storage component; The monitoring data includes: window operation data and air deflector status data; Ventilation monitoring data includes: fan operation data and environmental status data; Operational control data includes: power supply status data, communication control data, and control configuration data; Historical monitoring data includes: historical bidirectional deployment change characteristics and historical ventilation response data.

[0008] The present invention is further configured such that forming the current bidirectional deployment transition feature pair includes: Using the closed position of the window as the reference for the window position, the window position and direction of movement are determined based on the window operation data. During the window descent process, when the air guide cover forms a continuous working state sequence that satisfies the state confirmation rules in the control configuration data, the window position corresponding to the first working state in the continuous working state sequence is determined as the descent deployment confirmation position. During the window raising process, when the air guide cover forms a continuous non-working state sequence that satisfies the state confirmation rule, the window position corresponding to the first non-working state in the continuous non-working state sequence is determined as the starting position of the rising back pressure. Based on the collection time corresponding to the window operation data and the air guide cover status data, the descent deployment confirmation position and the rise back pressure start position within the same window lifting cycle are associated to form the current two-way deployment change feature pair.

[0009] The present invention is further configured such that establishing a deployment baseline corridor based on historical monitoring data includes: Based on historical monitoring data, multiple historical bidirectional deployment change feature pairs are selected according to the baseline establishment conditions in the control configuration data. The baseline establishment conditions include that the historical bidirectional deployment change feature pairs are formed in a complete window lifting cycle, and that both change positions are within the allowable window travel range defined by the control configuration data. Sort the multiple descent deployment confirmation positions and multiple rise backpressure start positions respectively. Select the descent deployment confirmation position and the rise backpressure start position from the sorting results according to the reference selection interval in the control configuration data. Determine the position interval covered by the selected descent deployment confirmation position as the descent position reference range and the position interval covered by the selected rise backpressure start position as the rise position reference range. By combining the descent position reference range and the ascent position reference range, a deployment reference corridor is generated.

[0010] The present invention is further configured such that the installation states include: stable installation state, overall installation offset state, abnormal state of air guide cover mechanism, incomplete deployment state, and abnormal recovery feedback state, wherein the overall installation offset state includes: stable installation drift, continuous installation slippage, and suspected installation drift. When both transformation positions in the current bidirectional deployment transformation feature pair are within the reference range corresponding to the deployment reference corridor, the installation status is determined to be the installation stable state. When both transition positions deviate from the reference range corresponding to the deployment reference corridor, have the same offset direction, and the difference in offset between the two transition positions does not exceed the common-direction consistency boundary in the control configuration data, the installation status is determined to be the overall installation offset status. If only one transformation position deviates from the corresponding reference range, or if the offset directions of the two transformation positions are inconsistent, the installation status is determined to be an abnormal state of the air guide cover mechanism. If the descent deployment confirmation position or the rise back pressure start position is not obtained, the installation status is determined to be either incomplete deployment or abnormal recovery feedback, respectively.

[0011] The present invention is further configured such that identifying the installation status based on cross-cycle variation characteristics includes: Based on the bidirectional deployment transformation feature pairs corresponding to the continuous window lifting cycle, the overall installation offset is tracked across cycles. When the overall installation offset remains within a stable fluctuation range in the control configuration data over multiple consecutive window lifting cycles, the overall installation offset is defined as stable installation drift. When the overall installation offset continues to increase in the same direction during multiple consecutive window lifting cycles, the overall installation offset is defined as continuous installation slip. When the overall installation offset occurs only in a single window lifting cycle, it is identified as a suspected installation drift and cross-cycle tracking continues. When the offset of stable installation drift does not exceed the calibrable drift boundary in the control configuration data, the installation status is determined to meet the calibration conditions; when the installation status is suspected installation drift or continuous installation slip, or when the offset of stable installation drift exceeds the calibrable drift boundary, the installation status is determined to not meet the calibration conditions.

[0012] The present invention is further configured such that generating candidate start boundaries and candidate stop boundaries includes: When the installation status meets the calibration conditions, along the direction of increasing window opening, reserve the first safe position margin in the control configuration data after the current confirmed descent deployment position to generate a candidate start boundary; Along the upward trajectory of the window, a second safety position margin from the control configuration data is reserved before the current upward back pressure starting position to generate a candidate stop boundary; The candidate start boundary and the candidate stop boundary are associated to form the candidate security deployment boundary.

[0013] The present invention is further configured to verify candidate start boundaries and candidate stop boundaries, and determine the current security deployment boundary by including: During the window lifting cycle after the candidate safety deployment boundary is generated, when the window position crosses the candidate start boundary, the air guide cover remains in working state, and the power supply status data meets the operating conditions specified by the boundary verification rule in the control configuration data, the control fan starts at the verification operation level specified by the boundary verification rule. During the verification observation period specified in the boundary verification rules, continuously monitor whether the air guide cover remains in working condition during fan operation and whether the fan generates start-up feedback corresponding to the verification operation level; When the window rises to the candidate stop boundary, the fan is controlled to stop, the fan stop feedback is monitored, and it is determined whether the fan stopped before the air guide cover was removed from the working state. After the window completes this lifting cycle, the installation status is updated based on the bidirectional deployment change characteristic pair formed during this lifting cycle and the historical bidirectional deployment change characteristic pair. When the air guide cover remains operational during fan operation, the fan start and stop feedback are normal, and the updated installation status still meets the calibration conditions, the candidate safe deployment boundary is determined as the current safe deployment boundary. If any candidate boundary verification fails or the updated installation state no longer meets the calibration conditions, the candidate security deployment boundary is revoked, the fan is prohibited from starting based on the candidate security deployment boundary, and a maintenance prompt corresponding to the verification failure reason is generated.

[0014] The present invention is further configured to determine the ventilation response state and generate a locally permissible control range, including: Based on ventilation monitoring data, determine the fan operation feedback and changes in environmental risk before and after fan operation, and compare the changes in environmental risk with historical ventilation response data under the corresponding operation level in historical monitoring data. When the fan operation feedback is abnormal, or when the environmental risk increases to the point that the conditions for rapid growth in the operation control data are met, the ventilation is determined to be ineffective. If the ventilation is not ineffective, and the fan operation feedback is normal and the change in environmental risk reaches the improvement level represented by the corresponding historical ventilation response data or becomes stable, the ventilation is determined to be effective; otherwise, if the fan operation feedback is normal, the ventilation is determined to be limited. When the current security deployment boundary is valid and the installation status meets the startup conditions, the fan startup permission, minimum safe operating level, and maximum allowed operating level are determined based on the ventilation response status and operation control data, and a local allowed control range is generated; otherwise, the local allowed control range is set to prohibit startup.

[0015] The present invention is further configured to adjudicate remote control commands and output fan control results and alarm linkage results, including: The remote control commands are compared with the local allowed control range. Remote start commands that do not meet the start permission are rejected. Other remote control commands that exceed the local allowed control range are executed according to the corresponding boundary. Remote control commands that meet the local allowed control range are executed according to the command content, and the fan control results are generated. When the environmental risk reaches the alarm conditions in the operation control data, or when the ventilation response status is a ventilation-limited state or a ventilation-ineffective state, the control outputs a help information on the display area facing outside the vehicle, controls the speaker components to output an alarm or remote voice, and sends at least one of the following graded alarms to the mobile terminal via the cloud: application message, SMS or telephone. When the operation control data characterization communication is offline, it continues to execute the control corresponding to the local allowed control range and caches the status summary and abnormal events. After communication is restored, the cached content is uploaded.

[0016] This invention provides a multi-state fusion monitoring and remote linkage control method for vehicle window ventilation equipment. The method comprises: S1: acquiring deployment monitoring data, ventilation monitoring data, operation control data, and historical monitoring data; extracting the descent deployment confirmation position corresponding to the wind guide cover entering the working state and the rise back pressure start position corresponding to the exiting the working state within the same window lifting cycle based on the deployment monitoring data, forming a current bidirectional deployment transition feature pair; S2: establishing a deployment benchmark corridor based on historical monitoring data; identifying the installation state based on the co-directional offset, differential offset, and cross-cycle change characteristics relative to the deployment benchmark corridor according to the current bidirectional deployment transition features; S3: when the installation state meets the calibration conditions in the operation control data, generating candidate start boundaries and candidate stop boundaries based on the current bidirectional deployment transition feature pair; verifying the candidate start boundaries and candidate stop boundaries based on the deployment monitoring data and ventilation monitoring data; determining the current safe deployment boundary based on the installation state and verification results; S4: determining the ventilation response state based on ventilation monitoring data and historical monitoring data; generating a local permissible control range by combining the current safe deployment boundary, installation state, ventilation response state, and operation control data; adjudicating remote control commands based on the local permissible control range; and outputting fan control results and alarm linkage results. The beneficial effects include: Enhance installation displacement identification capability: By jointly analyzing the co-directional offset, differential offset, and cross-cycle changes of the confirmed position of descent deployment and the starting position of rise back pressure, it can help distinguish between stable installation drift, continuous installation slippage, and abnormalities in the air guide cover mechanism, reducing misjudgments caused by relying solely on a single position status.

[0017] Enhanced safety control boundary adaptation: Candidate start-up and stop boundaries are generated for calibrable stable installation drift, and the current safety deployment boundary is determined after verification by actual lifting and lowering operation, which helps to keep the fan control position matching the actual deployment position of the air guide cover.

[0018] Enhance local and remote linkage control capabilities: By combining ventilation response status, installation status, power supply status, and security deployment boundaries to limit the local allowable control range, it can make safe decisions on remote control commands, and enhance the information transmission effect in abnormal states through external displays, sound prompts, and mobile terminal alarms.

[0019] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings: Figure 1 The flowchart illustrates a multi-state fusion monitoring and remote linkage control method for a vehicle window ventilation device, which is an exemplary embodiment of the present invention. Detailed Implementation

[0021] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0022] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0023] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0024] Example: A method for multi-state fusion monitoring and remote linkage control of vehicle window ventilation equipment, such as... Figure 1 As shown, it includes: S1: Acquire deployment monitoring data, ventilation monitoring data, operation control data, and historical monitoring data. Based on the deployment monitoring data, extract the downward deployment confirmation position corresponding to the air guide cover entering the working state and the upward back pressure start position corresponding to leaving the working state within the same window lifting cycle, forming the current two-way deployment change feature pair.

[0025] Specifically, this invention applies to an automatically deployed window ventilation system installed on the side windows of vehicles. The ventilation system is fixed to the window glass by suction cups. The mechanical constraint created when the window is closed keeps the air guide cover closed. After the window is lowered to release the mechanical constraint, the air guide cover unfolds under the action of a spring preload mechanism. The window ventilation system includes a controller, storage components, status acquisition components, communication components, an external display area, and a speaker component. The external display area shows the interior environmental risks, ventilation status, or emergency assistance information. The speaker component outputs audible alarms or voice messages sent from mobile terminals and can cooperate with a pickup component to establish voice calls.

[0026] The air deflector cover status acquisition component can employ a Hall effect sensor structure, a magnetic induction structure formed by combining a magnet and a magnetic response element, a microswitch structure, or a photoelectric induction structure. Alternatively, it can use a functional structure capable of distinguishing between the working and non-working states of the air deflector cover. The window operation status acquisition component can connect to the vehicle window control interface to acquire the window position and direction of movement. Alternatively, it can be detachably installed on a fixed part of the door, using the edge of the window glass as the measurement object to acquire the window position and determine the direction of movement based on changes in window position, making the window position reference independent of the installation position of the window ventilation equipment.

[0027] The deployed monitoring data includes window operation data and air deflector status data. Window operation data includes window position, direction of movement, and acquisition time. Air deflector status data includes the working status of the air deflector and the time of status change. Ventilation monitoring data includes fan operation data and environmental status data. The fan operation status acquisition component acquires at least one of the following: fan speed feedback and operating current, forming fan operation data. The environmental status acquisition component acquires the vehicle interior temperature, vehicle interior humidity, and acquisition time, forming environmental status data.

[0028] Operational control data includes power supply status data, communication control data, and control configuration data. The power supply status acquisition component acquires at least one of battery voltage and remaining power to form power supply status data. Communication control data includes communication online status, remote control commands, and corresponding times. Historical monitoring data includes historical bidirectional deployment change characteristic pairs and historical ventilation response data. Historical ventilation response data records fan operating levels, environmental status data before and after fan operation, direction of environmental status change, and corresponding observation periods.

[0029] The control configuration data includes status confirmation rules, baseline establishment conditions, baseline selection range, allowable window travel, co-directional consistency boundary, stable fluctuation range, calibration conditions, calibrable drift boundary, first safe position margin, second safe position margin, boundary verification rules, initial safe deployment boundary, and local control rules. Boundary verification rules include power supply operation conditions, verification operation level, verification observation period, start feedback confirmation conditions, and stop feedback confirmation conditions. Local control rules include start conditions, environmental risk classification conditions, rapid growth conditions, stability judgment conditions, alarm conditions, low voltage descent conditions, low voltage stop conditions, minimum safe operation level, and maximum allowable operation level.

[0030] The data acquisition period for window operation data, air deflector status data, and fan operation data can be set from 50 milliseconds to 200 milliseconds; in this embodiment, 100 milliseconds is used by default. The data acquisition period for environmental status data and power supply status data can be set from 0.5 seconds to 2 seconds; in this embodiment, 1 second is used by default. The acquisition period should be shortened when the window operation speed is high or when high positional accuracy is required, and extended when power consumption needs to be reduced.

[0031] The communication online status check cycle can be set from 3 seconds to 15 seconds, and 5 seconds is used by default in this embodiment. If no valid communication response is received for 2 to 5 consecutive communication check cycles, the communication is determined to be offline. In this embodiment, 3 consecutive communication check cycles are used by default. If a valid communication response is received for 1 to 3 consecutive communication check cycles, the communication online status is restored. In this embodiment, 2 consecutive communication check cycles are used by default.

[0032] The controller synchronizes various types of data according to the acquisition time. The window position data is filtered using median filtering with 3 or 5 consecutive sampled values. In this embodiment, 3 consecutive sampled values ​​are used by default; 5 consecutive sampled values ​​are used when the acquisition noise is high. Data from different acquisition cycles are correlated using a proximity time matching method, with the matching time difference not exceeding one acquisition cycle of the window operation data.

[0033] The closed window position is used as the window position reference, and the direction of window descent is determined as the direction of window opening increase. The direction of movement is confirmed when the window position change reaches 2 to 5 times the position resolution; in this embodiment, 3 times the position resolution is used by default. The allowable range of the closed position can be set to 1 to 3 times the position resolution; in this embodiment, 2 times the position resolution is used by default. The stable period of the closed position can be set to 300 milliseconds to 800 milliseconds; in this embodiment, 500 milliseconds is used by default.

[0034] The controller uses a finite state machine to record the closed state, lowered state, raised state, cycle completed state, and cycle invalid state. During the window lowering process, if the air guide cover state continuously represents the working state and meets the state confirmation rule, the window position corresponding to the first working state in the continuous working state sequence is determined as the lowering deployment confirmation position. During the window raising process, if the air guide cover state continuously represents the non-working state and meets the state confirmation rule, the window position corresponding to the first non-working state in the continuous non-working state sequence is determined as the rising backpressure start position. The state confirmation rule can be set to consistent sampling results from 2 to 5 consecutive times; in this embodiment, consistent sampling results from 3 consecutive times are used by default.

[0035] The descent deployment confirmation position and the rise return pressure start position within the same window lifting cycle are associated according to the data collection time to form a current bidirectional deployment transition feature pair. A complete window lifting cycle includes the window starting to descend from the closed position, forming the descent deployment confirmation position, transitioning to rising, forming the rise return pressure start position, and returning to the closed position. The allowed duration of the window lifting cycle can be set from 10 seconds to 60 seconds; in this embodiment, 30 seconds is used by default.

[0036] If deployment monitoring data is continuously missing for 3 to 10 collection cycles, it is determined that deployment monitoring data is continuously missing. In this embodiment, 5 collection cycles are used by default. If no change position is obtained, the window position exceeds the allowable window travel, or deployment monitoring data is continuously missing, the window raising and lowering cycle is marked as invalid, and the current bidirectional deployment change feature pair is not generated.

[0037] During the initial installation phase, the current bidirectional deployment transition feature pairs formed by the effective window raising and lowering cycles are stored sequentially. After the ventilation response status is identified, the corresponding results are written to the historical ventilation response data. The next step is executed once the number of historical records meets the baseline establishment conditions; otherwise, the initial safe deployment boundary is used.

[0038] The complete calculation process is as follows: Assume the window position is represented by the window travel count value, and the closed window position is recorded as zero. During the window descent, the air deflector status acquisition component outputs a working status three times consecutively, corresponding to window positions 178, 181, and 184. The window position 178 corresponding to the first working status is determined as the descent deployment confirmation position. During the window ascent, the air deflector status acquisition component outputs a non-working status three times consecutively, corresponding to window positions 169, 166, and 163. The window position 169 corresponding to the first non-working status is determined as the descent backpressure start position. After the window returns to the closed position, the descent deployment confirmation position 178 and the descent backpressure start position 169 are associated as the current bidirectional deployment transition feature pair.

[0039] S2: Establish a deployment baseline corridor based on historical monitoring data, and identify the installation status by analyzing the co-directional offset, differential offset, and cross-cycle change characteristics relative to the deployment baseline corridor according to the current bi-directional deployment transition characteristics. Specifically, acquire the current bi-directional deployment transition characteristic pair, window lifting cycle validity identifier, deployment monitoring data, and historical monitoring data output from the previous steps, and read the baseline establishment conditions, baseline selection interval, allowable window travel, co-directional consistency boundary, stable fluctuation range, calibration conditions, and calibrable drift boundary from the control configuration data.

[0040] The controller employs a conditional filtering algorithm to select historical bidirectional deployment change feature pairs from historical monitoring data. These pairs are formed within a complete window lifting cycle, with both transition positions within the allowable window travel distance, and there are no consecutive missing deployment monitoring data. The number of baseline samples can be set from 5 to 11; this embodiment uses 5 by default. The number of baseline samples can be increased when the window position fluctuates significantly.

[0041] The controller employs an insertion sort algorithm to sort the descent deployment confirmation positions and rise backpressure start positions in the benchmark samples in ascending order. In this embodiment, when using 5 benchmark samples, the benchmark selection interval is set to the 2nd to 4th positions in the sorting result; when increasing the number of benchmark samples, at least 3 consecutive positions in the middle of the sorting result are selected. The position interval covered by the selected descent deployment confirmation positions is determined as the descent position benchmark range, and the position interval covered by the selected rise backpressure start positions is determined as the rise position benchmark range. Combining the two benchmark ranges forms a deployment benchmark corridor.

[0042] Once the deployment baseline corridor is established, it remains unchanged. Bidirectional deployment change characteristics identified as installation drift or abnormal air guide cover mechanism are not written into the deployment baseline corridor. After reinstallation or mechanical maintenance is completed, the deployment baseline corridor is re-established according to the recalibration instructions.

[0043] When both the current descent deployment confirmation position and the current rise retracement starting position are within the corresponding reference range, the installation is considered stable. If either position exceeds the corresponding reference range, the direction of the exceedance is determined as the offset direction, and the position count distance between the current position and the nearest boundary of the corresponding reference range is determined as the offset.

[0044] When both the descent deployment confirmation position and the rise backpressure start position deviate from the corresponding reference range, have the same offset direction, and the difference in offset amount does not exceed the common-direction consistency boundary, it is determined to be an overall installation offset state. The common-direction consistency boundary can be set to 2 to 5 times the window position resolution; in this embodiment, 3 times the window position resolution is used by default.

[0045] If only one position deviates from the corresponding reference range, the two offset directions are inconsistent, or the two offset directions are the same but the difference in offset exceeds the co-directional consistency boundary, the air guide cover mechanism is identified as being in an abnormal state. When the current window lifting cycle has not formed the current bidirectional deployment transition characteristic pair, the missing position is identified based on the window lifting cycle validity identifier and deployment monitoring data; if a descent deployment confirmation position has not been formed, it is determined to be in an incomplete deployment state; if an upward backpressure starting position has not been formed, it is determined to be in an abnormal recovery feedback state.

[0046] For overall installation misalignment, the controller uses a sliding periodic window algorithm for cross-cycle tracking. The number of cross-cycle confirmations can be set to 3 to 5 consecutive window raising and lowering cycles; in this embodiment, 3 consecutive window raising and lowering cycles are used by default. When the overall installation misalignment first occurs or before the cross-cycle confirmation count is reached, it is determined to be a suspected installation drift.

[0047] Centered on the initial confirmation position of the descent deployment and the starting position of the upward backpressure, which indicate the initial overall installation offset, the stable fluctuation ranges are expanded to form the descent position tracking range and the upward position tracking range, respectively. The stable fluctuation range can be set to 2 to 5 times the window position resolution; in this embodiment, 3 times the window position resolution is used by default.

[0048] If, in multiple consecutive window lifting cycles, both the descent deployment confirmation position and the rise back pressure initiation position move away from the deployment reference corridor in the same direction, and the positional change in adjacent window lifting cycles exceeds the position resolution of one window, it is determined to be a continuous installation slip. If no continuous installation slip occurs, and both positions remain within the corresponding position tracking range, it is determined to be a stable installation drift. Upon re-entering the deployment reference corridor after a suspected installation drift, the current bidirectional deployment change characteristic restores the stable installation state. If the cross-cycle confirmation quantity is reached, but the continuous installation slip or stable installation drift determination criteria are not met, the suspected installation drift is maintained, and cross-cycle tracking continues.

[0049] After a stable installation drift is established, the larger of the two offset values ​​is determined as the change in installation position. The calibrable drift boundary can be set to 5% to 10% of the effective window travel; in this embodiment, 8% of the effective window travel is used by default, and it is reduced based on the remaining safe distance between the normal working position of the air guide cover and the mechanical interference position. When the change in installation position does not exceed the calibrable drift boundary, the installation state is determined to meet the calibration conditions. When the change in installation position during stable installation drift exceeds the calibrable drift boundary, or when the installation state is suspected installation drift, continuous installation slippage, abnormal state of the air guide cover mechanism, incomplete deployment state, or abnormal recovery feedback state, the installation state is determined to not meet the calibration conditions.

[0050] The complete calculation process is as follows: Assume that step S1 generates 5 valid historical bidirectional deployment transition feature pairs, with the confirmed deployment positions for descent being 176, 178, 179, 180, and 182, and the starting positions for retracement being 168, 169, 170, 171, and 173. After sorting, positions 2 to 4 are selected to obtain the baseline range for descent positions (178 to 180) and the baseline range for retracement positions (169 to 171).

[0051] Assume the confirmed downward deployment positions for the subsequent three consecutive window raising and lowering cycles are 188, 189, and 188, and the initial upward backpressure positions are 179, 180, and 179. Both positions deviate from the corresponding reference range in the same direction and remain within a stable fluctuation range; therefore, this is determined to be stable installation drift. The change in installation position is counted by 8 positions. Assuming the calibrable drift boundary is 64 positions, the installation state meets the calibration conditions.

[0052] S3: When the installation status meets the calibration conditions in the operation control data, candidate start-up boundaries and candidate stop boundaries are generated based on the current bidirectional deployment transition characteristics. These candidate start-up boundaries and candidate stop boundaries are verified based on deployment monitoring data and ventilation monitoring data. The current safe deployment boundary is determined based on the installation status and verification results. Specifically, the installation status, current bidirectional deployment transition characteristics, and calibration condition judgment results output from the previous steps are obtained. The first safe position margin, second safe position margin, and boundary verification rules are read from the deployment monitoring data, ventilation monitoring data, power supply status data, and control configuration data.

[0053] When the calibration condition is met, a first safety margin is reserved after the current descent deployment confirmation position along the direction of increasing window opening, generating a candidate start boundary; a second safety margin is reserved before the current upward backpressure start position along the window's upward trajectory, generating a candidate stop boundary. The first and second safety margins can be set to 1% to 3% of the effective window travel, respectively; in this embodiment, 2% of the effective window travel is used by default. The corresponding safety margin is increased when the window operates at a faster speed or the fan stops responding slowly, and decreased when the remaining mechanical safety distance is small. When the remaining mechanical safety distance is small, the corresponding safety margin is decreased within a range not lower than the lower limit of the safety margin; no candidate boundary is generated if the lower limit of the safety margin cannot be retained.

[0054] When both the candidate start boundary and the candidate stop boundary are within the allowable window travel distance, and the candidate start boundary is not less than the candidate stop boundary, a candidate safe deployment boundary is formed. The controller uses a finite state machine to sequentially execute candidate start boundary verification, candidate stop boundary verification, and installation status update. During verification, the candidate safe deployment boundary only triggers fan verification operation.

[0055] When using battery voltage, the power supply operation conditions can be set to a stop condition where the battery voltage is higher than the low voltage condition, and a 5% to 10% operating margin of the rated voltage should be retained. In this embodiment, the default is to retain 8%. When using remaining power, the lower limit of remaining power can be set to 15% to 30%. In this embodiment, the default is 20%. If the power supply status data does not meet the power supply operation conditions, the candidate safety deployment boundary remains in a state of pending verification.

[0056] The verification operation level can be set to 30% to 50% of the highest allowed fan operation level; in this embodiment, 40% is used by default. The verification observation period can be set to 3 to 10 seconds; in this embodiment, 5 seconds is used by default. When the window descends past the candidate start boundary, the air guide cover remains in working condition, and the power supply status data meets the power supply operation conditions, the fan is started according to the verification operation level.

[0057] When using fan speed feedback, fan start feedback is established when the fan speed feedback reaches 70% to 90% of the reference speed corresponding to the verification operating level and remains continuously for 2 to 5 acquisition cycles. In this embodiment, 80% and 3 acquisition cycles are used by default. When using operating current, fan start feedback is established when the operating current is within the rated operating current range after a startup stabilization period of 0.2 to 1 second. In this embodiment, a startup stabilization period of 0.5 seconds is used by default.

[0058] If the air guide cover remains operational during the verification observation period and the fan generates fan start feedback, the candidate start boundary verification passes. If the air guide cover exits operational status during the verification observation period or the fan fails to generate fan start feedback, the candidate start boundary verification fails. The fan stops when the window rises to the candidate stop boundary. Fan stop feedback is confirmed when the fan speed feedback drops to 5% to 15% of the reference speed, or when the operating current drops to the standby current range. In this embodiment, 10% of the reference speed is used by default. The allowable stop feedback period can be set from 1 second to 3 seconds; in this embodiment, 2 seconds is used by default.

[0059] The candidate stop boundary verification passes when the fan generates fan stop feedback before the air guide cover leaves the working state. The candidate stop boundary verification fails when the fan fails to generate fan stop feedback before the air guide cover leaves the working state. After the window completes the current window lifting cycle, the installation status is updated according to step S2. If both the candidate start boundary and candidate stop boundary verification pass, and the updated installation status still meets the calibration conditions, the candidate safety deployment boundary is determined as the current safety deployment boundary; if the verification fails or the updated installation status no longer meets the calibration conditions, the candidate safety deployment boundary is revoked and a corresponding maintenance prompt is generated.

[0060] The complete calculation process is as follows: Assume the current confirmed descent deployment position is 188, the current upward retracement starting position is 179, and the first and second safety position margins are both 16 position counts. The candidate start boundary is determined to be 204, and the candidate stop boundary is determined to be 195.

[0061] Assuming the reference rotational speed corresponding to the verification operation level is 1000 rpm, and the lower limit for startup feedback confirmation is 800 rpm, after the window descends past the candidate startup boundary 204, the fan speed feedback generated in three consecutive data acquisition cycles is 820 rpm, 835 rpm, and 828 rpm. The air guide cover remains in an active state for 5 seconds, therefore the candidate startup boundary verification is passed. After the window rises to the candidate stop boundary 195, the fan stops. The fan speed feedback drops below 100 rpm within 2 seconds, and fan stop feedback is generated before the air guide cover leaves the active state, therefore the candidate stop boundary verification is passed. The updated installation state still meets the calibration conditions, and the candidate safe deployment boundary is determined as the current safe deployment boundary.

[0062] S4: Determine the ventilation response status based on ventilation monitoring data and historical monitoring data. Combine the current safety deployment boundary, installation status, ventilation response status, and operation control data to generate the local permissible control range. Based on the local permissible control range, adjudicate remote control commands and output fan control results and alarm linkage results. Specifically, acquire fan operation data, environmental status data, historical ventilation response data, power supply status data, communication control data, the current safety deployment boundary and installation status output from previous steps, and read environmental risk classification conditions, rapid growth conditions, stability judgment conditions, start-up conditions, low voltage downgrading conditions, low voltage stop conditions, and alarm conditions.

[0063] The controller employs a threshold-based grading algorithm to determine the environmental risk level based on the vehicle's interior temperature and humidity, selecting the higher risk level as the current environmental risk level. Taking a high-temperature stay scenario as an example, the temperature warning boundary can be set to 30℃ to 35℃, with 32℃ as the default in this embodiment; the temperature critical boundary can be set to 34℃ to 40℃, with 36℃ as the default in this embodiment; the humidity warning boundary can be set to 70% to 85%, with 80% as the default in this embodiment; and the humidity critical boundary can be set to 85% to 95%, with 90% as the default in this embodiment. The critical boundary is higher than the corresponding warning boundary, and the specific values ​​can be adjusted according to the stay object and the vehicle's operating environment.

[0064] The controller establishes observation periods before and after the fan starts operating, comparing the environmental risk level, the direction of change in in-vehicle temperature, and the direction of change in in-vehicle humidity to generate an environmental change status. The observation period can be set from 3 minutes to 10 minutes; in this embodiment, 5 minutes is used by default.

[0065] The rapid temperature increase threshold can be set to 1°C to 3°C, and the rapid humidity increase threshold can be set to 5% to 15%. In this embodiment, 2°C and 10% are used by default. When any change reaches the corresponding threshold within an observation period, the rapid increase condition is determined to be met. The temperature stability threshold can be set to 0.3°C to 1°C, and the humidity stability threshold can be set to 2% to 5%. In this embodiment, 0.5°C and 3% are used by default. When neither the absolute change in in-vehicle temperature nor the absolute change in in-vehicle humidity exceeds the corresponding stability threshold, the environmental change state is determined to have stabilized.

[0066] The controller employs a grouping and sequential statistical algorithm to select historical ventilation response data corresponding to the current fan operating level, arranging them in the order of continuous rapid growth, continuous growth, weakening growth, stabilization, and risk reduction. The number of historical samples can be set from 3 to 9; in this embodiment, the 5 most recently generated historical ventilation response data are used by default, and the degree of environmental improvement corresponding to the middle position of the sorted results is determined as the historical ventilation response benchmark. When the number of historical samples is insufficient, rapid growth and stability judgment conditions are used for judgment.

[0067] Following the feedback confirmation method in step S3, the fan operation data is compared with the reference operation data corresponding to the current fan operation level to determine whether the fan operation feedback is normal or abnormal. If the fan operation feedback is abnormal, or the environmental change meets the rapid growth condition, it is determined to be a ventilation ineffective state. If the ventilation ineffective state is not met, but the fan operation feedback is normal, and the environmental change reaches the historical ventilation response benchmark or becomes stable, it is determined to be a ventilation effective state. If it is not classified as a ventilation effective state and the fan operation feedback is normal, it is determined to be a ventilation limited state. If the installation status is a stable installation state, or a stable installation drift verified by the boundary in step S3, the installation status is determined to meet the activation conditions. If the installation status is suspected installation drift, continuous installation slippage, abnormal state of the air guide cover mechanism, incomplete deployment state, or abnormal recovery feedback state, the installation status is determined to not meet the activation conditions.

[0068] When the current safety deployment boundary is valid and the installation status meets the startup conditions, a local permissible control range is generated based on the ventilation response status and operation control data; otherwise, startup is prohibited. The normal level corresponds to a stop state; the minimum safe operating level corresponding to the warning level can be set to 30% to 50% of the fan's rated maximum operating level, with 40% being the default in this embodiment; the minimum safe operating level corresponding to the critical level can be set to 50% to 70%, with 60% being the default in this embodiment. When the power supply status data is lower than the power supply operation conditions in step S3 but higher than the battery discharge protection lower limit, it is determined that the low voltage downgrading condition has been reached; when the power supply status data reaches the battery discharge protection lower limit, it is determined that the low voltage stop condition has been reached.

[0069] When the power supply status data does not meet the low voltage descent condition, the highest permissible operating level is the fan's rated maximum operating level. When the power supply status data meets the low voltage descent condition but not the low voltage stop condition, the highest permissible operating level can be limited to 40% to 60% of the fan's rated maximum operating level; in this embodiment, 50% is used by default. When the power supply status data meets the low voltage stop condition, startup is prohibited. When the power supply status data meets the low voltage descent condition and the highest permissible operating level is lower than the lowest safe operating level, the lowest safe operating level is corrected to the highest permissible operating level, and the alarm level is increased.

[0070] When ventilation is effective, maintain the minimum safe operating level corresponding to the environmental risk level; when ventilation is limited, increase the minimum safe operating level; when ventilation is ineffective due to abnormal fan operation feedback, stop the fan and prohibit restarting; when ventilation is ineffective due to rapidly increasing conditions and the fan operation feedback is normal, increase the minimum safe operating level to the value corresponding to the critical level, and allow the fan to operate at the highest permissible operating level.

[0071] The controller uses a rule-based priority decision algorithm to compare remote control commands with the locally permitted control range. Remote start commands are rejected if they do not meet the fan start permission; remote speed control commands are executed at the highest permissible operating level if they exceed the highest permissible operating level, and at the lowest permissible operating level if they are below the lowest permissible operating level; when a remote stop command conflicts with the lowest permissible operating level, the lowest permissible operating level is maintained; remote control commands that comply with the locally permitted control range are executed according to the remote control command. Remote forced start is not performed if the mechanical deployment is unsafe or the power supply status data reaches the low voltage stop condition.

[0072] When the environmental risk level reaches the alarm condition, or the ventilation response status is limited or ineffective, the system controls the display area facing outwards to show the environmental risk level, ventilation response status, and assistance information, and controls the speaker components to output an audible alarm or remote voice message. A Level 1 alarm corresponds to a warning level or limited ventilation status, sending an application message via the cloud; a Level 2 alarm corresponds to a critical level or ineffective ventilation status, sending an application message and SMS; a Level 3 alarm corresponds to a critical level lasting 3 to 10 minutes, abnormal fan operation feedback, or installation status not meeting the startup conditions, and a telephone alarm is added. In this embodiment, a default 5-minute continuous confirmation duration is used.

[0073] When the communication status changes from online to offline, the controller continues to execute the locally permitted control range and uses a circular queue to cache status summaries, abnormal events, and fan control results. After communication is restored, the cached content is uploaded according to the formation time. The cloud updates the alarm level based on continuous environmental risk records and abnormal events, and resends alarm information to the mobile terminal.

[0074] The complete calculation process is as follows: Assuming the current safety deployment boundary is valid, the installation status meets the startup conditions, the power supply status data does not reach the low voltage derating condition, and the fan operates at 60% of its rated maximum operating level. Within the first 5 minutes of fan operation, the vehicle interior temperature rises from 34℃ to 35℃; the vehicle interior humidity remains at 65%. Within the next 5 minutes of fan operation, the vehicle interior temperature rises from 35℃ to 35.2℃, and the vehicle interior humidity decreases from 65% to 63%.

[0075] The current environmental risk level is determined to be at the warning level, and the environmental change status is determined to be a weakening growth. Assuming that the historical ventilation response baseline corresponding to 60% fan operation level is also a weakening growth, and that the fan operation feedback is normal, the ventilation response status is determined to be an effective ventilation status.

[0076] The minimum safe operating level is 40%, and the maximum allowed operating level is 100%. When the mobile terminal sends a remote speed adjustment command of 30%, the controller controls the fan at 40%; when it sends a remote speed adjustment command of 80%, the controller controls the fan at 80%; when it sends a remote stop command, the controller maintains 40% operation and returns an environmental risk warning.

[0077] The controller simultaneously outputs local distress signals and Level 1 alarms. When the communication online status changes to offline, it continues to execute the locally allowed control range and caches status summaries and abnormal events. Once communication is restored, the cached content is uploaded.

[0078] The above description is merely a specific embodiment 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 multi-state fusion monitoring and remote linkage control of vehicle window ventilation equipment, characterized in that, include: S1: Acquire deployment monitoring data, ventilation monitoring data, operation control data and historical monitoring data. Based on the deployment monitoring data, extract the downward deployment confirmation position corresponding to the air guide cover entering the working state and the upward back pressure start position corresponding to leaving the working state within the same window lifting cycle, and form the current two-way deployment change feature pair. S2: Establish a deployment baseline corridor based on historical monitoring data, and identify the installation status based on the co-directional offset, differential offset and cross-cycle change characteristics of the relative deployment baseline corridor according to the current bidirectional deployment transformation characteristics; S3: When the installation status meets the calibration conditions in the operation control data, candidate start boundary and candidate stop boundary are generated based on the current bidirectional deployment transformation characteristics. The candidate start boundary and candidate stop boundary are verified based on deployment monitoring data and ventilation monitoring data. The current safe deployment boundary is determined based on the installation status and verification results. S4: Determine the ventilation response status based on ventilation monitoring data and historical monitoring data, generate the local allowable control range by combining the current safety deployment boundary, installation status, ventilation response status and operation control data, adjudicate remote control commands based on the local allowable control range, and output fan control results and alarm linkage results.

2. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 1, characterized in that, The vehicle window ventilation equipment includes: a controller, a storage component, a status acquisition component, a communication component, a display area facing outwards, and a speaker component. The status acquisition component includes: a window operation status acquisition component, an air guide cover status acquisition component, a fan operation status acquisition component, an environmental status acquisition component, and a power supply status acquisition component. Use the status acquisition component to obtain deployment monitoring data, ventilation monitoring data, and power supply status data; Use communication components to acquire communication control data; Read control configuration data and historical monitoring data from the storage component; The monitoring data includes: window operation data and air deflector status data; Ventilation monitoring data includes: fan operation data and environmental status data; Operational control data includes: power supply status data, communication control data, and control configuration data; Historical monitoring data includes: historical bidirectional deployment change characteristics and historical ventilation response data.

3. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 2, characterized in that, The characteristics that have led to the current shift in two-way deployment include: Using the closed position of the window as the reference for the window position, the window position and direction of movement are determined based on the window operation data. During the window descent process, when the air guide cover forms a continuous working state sequence that satisfies the state confirmation rules in the control configuration data, the window position corresponding to the first working state in the continuous working state sequence is determined as the descent deployment confirmation position. During the window raising process, when the air guide cover forms a continuous non-working state sequence that satisfies the state confirmation rule, the window position corresponding to the first non-working state in the continuous non-working state sequence is determined as the starting position of the rising back pressure. Based on the collection time corresponding to the window operation data and the air guide cover status data, the descent deployment confirmation position and the rise back pressure start position within the same window lifting cycle are associated to form the current two-way deployment change feature pair.

4. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 2, characterized in that, Establishing deployment baseline corridors based on historical monitoring data includes: Based on historical monitoring data, multiple historical bidirectional deployment change feature pairs are selected according to the baseline establishment conditions in the control configuration data. The baseline establishment conditions include that the historical bidirectional deployment change feature pairs are formed in a complete window lifting cycle, and that both change positions are within the allowable window travel range defined by the control configuration data. Sort the multiple descent deployment confirmation positions and multiple rise backpressure start positions respectively. Select the descent deployment confirmation position and the rise backpressure start position from the sorting results according to the reference selection interval in the control configuration data. Determine the position interval covered by the selected descent deployment confirmation position as the descent position reference range and the position interval covered by the selected rise backpressure start position as the rise position reference range. By combining the descent position reference range and the ascent position reference range, a deployment reference corridor is generated.

5. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 4, characterized in that, The installation status includes: stable installation status, overall installation offset status, abnormal status of air guide cover mechanism, incomplete deployment status, and abnormal status of recovery feedback. Among them, the overall installation offset status includes: stable installation drift, continuous installation slippage, and suspected installation drift. When both transformation positions in the current bidirectional deployment transformation feature pair are within the reference range corresponding to the deployment reference corridor, the installation status is determined to be the installation stable state. When both transition positions deviate from the reference range corresponding to the deployment reference corridor, have the same offset direction, and the difference in offset between the two transition positions does not exceed the common-direction consistency boundary in the control configuration data, the installation status is determined to be the overall installation offset status. If only one transformation position deviates from the corresponding reference range, or if the offset directions of the two transformation positions are inconsistent, the installation status is determined to be an abnormal state of the air guide cover mechanism. If the descent deployment confirmation position or the rise back pressure start position is not obtained, the installation status is determined to be either incomplete deployment or abnormal recovery feedback, respectively.

6. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 5, characterized in that, Identifying installation status based on cross-cycle variation characteristics includes: Based on the bidirectional deployment transformation feature pairs corresponding to the continuous window lifting cycle, the overall installation offset is tracked across cycles. When the overall installation offset remains within a stable fluctuation range in the control configuration data over multiple consecutive window lifting cycles, the overall installation offset is defined as stable installation drift. When the overall installation offset continues to increase in the same direction during multiple consecutive window lifting cycles, the overall installation offset is defined as continuous installation slip. When the overall installation offset occurs only in a single window lifting cycle, it is identified as a suspected installation drift and cross-cycle tracking continues. When the offset of stable installation drift does not exceed the calibrable drift boundary in the control configuration data, the installation status is determined to meet the calibration conditions; when the installation status is suspected installation drift or continuous installation slip, or when the offset of stable installation drift exceeds the calibrable drift boundary, the installation status is determined to not meet the calibration conditions.

7. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 6, characterized in that, The generation of candidate start boundaries and candidate stop boundaries includes: When the installation status meets the calibration conditions, along the direction of increasing window opening, reserve the first safe position margin in the control configuration data after the current confirmed descent deployment position to generate a candidate start boundary; Along the upward trajectory of the window, a second safety position margin from the control configuration data is reserved before the current upward back pressure starting position to generate a candidate stop boundary; The candidate start boundary and the candidate stop boundary are associated to form the candidate security deployment boundary.

8. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 7, characterized in that, Verifying candidate start boundaries and candidate stop boundaries to determine the current security deployment boundaries includes: During the window lifting cycle after the candidate safety deployment boundary is generated, when the window position crosses the candidate start boundary, the air guide cover remains in working state, and the power supply status data meets the operating conditions specified by the boundary verification rule in the control configuration data, the control fan starts at the verification operation level specified by the boundary verification rule. During the verification observation period specified in the boundary verification rules, continuously monitor whether the air guide cover remains in working condition during fan operation and whether the fan generates start-up feedback corresponding to the verification operation level; When the window rises to the candidate stop boundary, the fan is controlled to stop, the fan stop feedback is monitored, and it is determined whether the fan stopped before the air guide cover was removed from the working state. After the window completes this lifting cycle, the installation status is updated based on the bidirectional deployment change feature pair formed during this lifting cycle and the historical bidirectional deployment change feature pair. When the air guide cover remains operational during fan operation, the fan start and stop feedback are normal, and the updated installation status still meets the calibration conditions, the candidate safe deployment boundary is determined as the current safe deployment boundary. If any candidate boundary verification fails or the updated installation state no longer meets the calibration conditions, the candidate security deployment boundary is revoked, the fan is prohibited from starting based on the candidate security deployment boundary, and a maintenance prompt corresponding to the verification failure reason is generated.

9. The method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 1, characterized in that, Determine the ventilation response status and generate the local permissible control range, including: Based on ventilation monitoring data, determine the fan operation feedback and changes in environmental risk before and after fan operation, and compare the changes in environmental risk with historical ventilation response data under the corresponding operation level in historical monitoring data. When the fan operation feedback is abnormal, or when the environmental risk increases to the point that the conditions for rapid growth in the operation control data are met, the ventilation is determined to be ineffective. If the ventilation is not ineffective, the ventilation is considered effective if the fan operation feedback is normal and the change in environmental risk reaches the improvement level represented by the corresponding historical ventilation response data or becomes stable; otherwise, the ventilation is considered limited. When the current security deployment boundary is valid and the installation status meets the startup conditions, the fan startup permission, minimum safe operating level, and maximum allowed operating level are determined based on the ventilation response status and operation control data, and a local allowed control range is generated; otherwise, the local allowed control range is set to prohibit startup.

10. A method for multi-state fusion monitoring and remote linkage control of a vehicle window ventilation device according to claim 9, characterized in that, The remote control command is adjudicated, and the output of fan control results and alarm linkage results includes: The remote control commands are compared with the local allowed control range. Remote start commands that do not meet the start permission are rejected. Other remote control commands that exceed the local allowed control range are executed according to the corresponding boundary. Remote control commands that meet the local allowed control range are executed according to the command content, and the fan control results are generated. When the environmental risk reaches the alarm conditions in the operation control data, or when the ventilation response status is a ventilation-limited state or a ventilation-ineffective state, the control outputs a help information on the display area facing outside the vehicle, controls the speaker components to output an alarm or remote voice, and sends at least one of the following graded alarms to the mobile terminal via the cloud: application message, SMS or telephone. When the operation control data characterization communication is offline, it continues to execute the control corresponding to the local allowed control range and caches the status summary and abnormal events. After communication is restored, the cached content is uploaded.

Images