WIND MONITORING SYSTEM FOR A VEHICLE

The wind monitoring system uses ultrasonic sensors to enhance vehicle stability and safety by monitoring crosswinds and executing adaptive controls and warnings, addressing the lack of effective crosswind monitoring in existing vehicle systems.

DE102025100464A1Pending Publication Date: 2026-05-21GM GLOBAL TECHNOLOGY OPERATIONS LLC
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
DE · DE
Patent Type
Applications
Current Assignee / Owner
GM GLOBAL TECHNOLOGY OPERATIONS LLC
Filing Date
2025-01-08
Publication Date
2026-05-21

AI Technical Summary

Technical Problem

Existing vehicle systems lack the capability to effectively monitor and respond to the impact of crosswinds, which can affect vehicle stability and safety, particularly when towing trailers.

Method used

A wind monitoring system using ultrasonic sensors to define detection zones, acquire wind data, determine wind direction and speed, and execute crosswind support functions, including lateral controls and warnings, based on fused wind and vehicle dynamics data.

Benefits of technology

Enhances vehicle stability and safety by providing real-time crosswind assistance, adjusting vehicle controls, and issuing warnings to mitigate the effects of crosswinds, especially when towing trailers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A computer-implemented procedure, when executed by data processing hardware, causes the data processing hardware to perform operations. These operations include defining, via a plurality of ultrasonic sensors, a plurality of detection zones; acquiring, via the plurality of ultrasonic sensors, wind data from one or more of the plurality of detection zones; and determining, via a wind monitoring application, a wind direction and a wind speed based on the wind data.The operations also include receiving weather data on the wind monitoring application, executing a fusion function on the wind data, weather data and vehicle dynamics to define fused wind data via the wind monitoring application, executing a crosswind support function of the wind monitoring application based on the fused wind data, and executing the side controls of the crosswind support function via the wind monitoring application.
Need to check novelty before this filing date? Find Prior Art

Description

INTRODUCTION

[0001] The information contained in this section serves to present the general context of the disclosure. Works of the inventors mentioned herein, insofar as they are described in this section, as well as aspects of the description that may not otherwise be considered prior art at the time of filing, are neither expressly nor implicitly admitted as prior art contrary to the present disclosure.

[0002] The present disclosure relates generally to a wind monitoring system for a vehicle.

[0003] Vehicles are often equipped with various sensors to monitor their surroundings. For example, vehicles may be equipped with image sensors, proximity sensors, or other sensors that can detect changes in the vehicle's environment. In some cases, vehicles may be equipped with sensors that detect rain and / or changes in daylight conditions. Vehicles may also communicate with off-board systems that can provide weather data to the vehicle's control unit. While weather data can provide the control unit with generalized information about the environment, there is a need for an improved vehicle system that monitors the effects of weather events, such as crosswinds, on the vehicle. SUMMARY

[0004] In some aspects, a computer-implemented procedure, when executed by the data processing hardware, causes the data processing hardware to perform operations. These operations include defining, via a multitude of ultrasonic sensors, a multitude of detection zones; acquiring, via the multitude of ultrasonic sensors, wind data from one or more of the multitude of detection zones; and determining, via a wind monitoring application, a wind direction and wind speed based on the wind data.The operations also include receiving weather data on the wind monitoring application, executing a fusion function on the wind data, weather data and vehicle dynamics to define fused wind data via the wind monitoring application, executing a crosswind support function of the wind monitoring application based on the fused wind data, and executing the side controls of the crosswind support function via the wind monitoring application.

[0005] In some examples, executing the crosswind assist function might involve issuing a warning to a vehicle's user interface. The operations might also include receiving object data on the wind monitoring application. The object data might include vehicle and trailer data, with the trailer data including one or more trailer dimensions, trailer mass, and axle count, while the vehicle data might include vehicle speed and steering angle. The operations might further include executing a criticality function based on the fused wind and object data, and generating a criticality value based on the object data via this criticality function. Optionally, executing the crosswind assist function might include adjusting the lateral controls based on the criticality value.The processes can also include determining, based on the merged wind data, that at least one of the wind directions and wind speeds exceeds the criticality threshold. The processes further include issuing a warning in response to either the wind direction or the wind speed exceeding the criticality threshold.

[0006] In other aspects, a wind monitoring system comprises data processing hardware and storage hardware that communicate with the data processing hardware. The storage hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. These operations include defining, via a variety of ultrasonic sensors, a variety of detection zones; acquiring, via the variety of ultrasonic sensors, wind data from one or more of the variety of detection zones; determining, via a wind monitoring application, a wind direction and wind speed based on the wind data; and receiving weather data on the wind monitoring application.The operations also include executing, via the wind monitoring application, a fusion function on the wind data, weather data and vehicle dynamics to define fused wind data, executing, based on the fused wind data, a crosswind support function of the wind monitoring application, and executing, via the wind monitoring application, the side controls of the crosswind support function.

[0007] In some examples, executing the crosswind assist function might involve issuing a warning to a vehicle's user interface. The operations might also include receiving object data on the wind monitoring application. Optionally, the object data might include vehicle and trailer data, with the trailer data including one or more trailer dimensions, trailer mass, and axle count, while the vehicle data might include vehicle speed and steering angle. The operations might also include executing a criticality function based on the fused wind and object data, and generating a criticality value based on the object data via this criticality function. In some cases, executing the crosswind assist function might include adjusting the lateral controls based on the criticality value.The processes can also include determining, based on the merged wind data, that at least one of the wind directions and wind speeds exceeds the criticality threshold. The processes can further include issuing a warning in response to either the wind direction or the wind speed exceeding the criticality threshold.

[0008] In other aspects, a wind monitoring system comprises data processing hardware and storage hardware that communicate with the data processing hardware. The storage hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. These operations include defining, via a variety of ultrasonic sensors, a variety of detection zones; acquiring, via the variety of ultrasonic sensors, wind data from one or more of the variety of detection zones; determining, via a wind monitoring application, a wind direction and wind speed based on the wind data; and receiving weather data on the wind monitoring application.The processes also include executing, via the wind monitoring application, a fusion function on the wind data, the weather data and the vehicle dynamics to define fused wind data; receiving, via the wind monitoring application, object data; executing, based on the fused wind data and the object data, a criticality function; and generating, via the criticality function, a criticality value based on the object data.The operations further include determining, based on the fused wind data, that the wind direction and / or wind speed exceeds the critical value; executing, based on the fused wind data and the wind direction or wind speed exceeding the critical value, a crosswind support function of the wind monitoring application; executing, via the wind monitoring application, the side controls of the crosswind support function; and issuing an alert in response to either the wind direction or wind speed exceeding the critical value.

[0009] In some examples, the object data can include vehicle data and trailer data, where the trailer data includes one or more trailer dimensions, the trailer mass, and the number of axles, and the vehicle data includes the vehicle speed and steering angle. Optionally, executing the crosswind assist function can include adjusting the lateral controls based on the criticality value. The operations can also include issuing a warning in response to either the wind direction or the wind speed exceeding the criticality value. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings described herein serve only to illustrate selected configurations and are not intended to limit the scope of the present disclosure. Fig. Figure 1 is a schematic representation of a vehicle equipped with a wind monitoring system according to the present disclosure; Fig. Figure 2 is an exemplary block diagram for a wind monitoring system according to the present disclosure; Fig. Figure 3 is a schematic representation of a vehicle equipped with a plurality of ultrasonic sensors according to the present disclosure in order to define a plurality of detection zones; Fig. 4A is a schematic representation of a vehicle equipped with a wind monitoring system according to the present disclosure, wherein the vehicle is exposed to a crosswind; Fig. 4B is a further schematic representation of a vehicle equipped with a wind monitoring system according to the present disclosure, wherein the vehicle is exposed to an impact wind when overtaking another vehicle; Fig. 4C is a further schematic representation of a vehicle equipped with a wind monitoring system according to the present disclosure, wherein the vehicle is subjected to an impact wind while being overtaken by another vehicle; Fig. 4D is yet another schematic representation of a vehicle equipped with a wind monitoring system according to the present disclosure, wherein the vehicle is exposed to an impact wind when passing an oncoming vehicle; Fig. Figure 5 is an exemplary flowchart for a wind monitoring system according to the present disclosure; Fig. 6 is another exemplary flowchart for a wind monitoring system according to the present disclosure; Fig. 7 is another exemplary flowchart for a wind monitoring system according to the present disclosure; and Fig. Figure 8 is an exemplary process diagram for a wind monitoring system according to the present disclosure.

[0011] In the drawings, corresponding reference symbols denote corresponding parts. DETAILED DESCRIPTION

[0012] Exemplary configurations are now described in more detail with reference to the accompanying drawings. Since exemplary configurations are provided, this is a careful disclosure that conveys the full scope of the disclosure to those skilled in the art. Specific details are included, such as examples of specific components, devices, and processes, to provide an accurate understanding of the configurations of the present disclosure. Those skilled in the art will recognize that specific details need not be used, that exemplary configurations can be embodied in many different forms, and that the specific details and the exemplary configurations should not be interpreted in such a way as to limit the scope of the disclosure.

[0013] The terminology used herein serves only to describe certain exemplary configurations and is not to be understood as restrictive. As used herein, the singular articles "a," "an," and "the" can also include the plural forms unless the context clearly indicates otherwise. The terms "comprise," "comprehensive," "contain," and "exhibit" are inclusive and thus specify the presence of features, steps, processes, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, processes, elements, components, and / or groups thereof. The steps, processes, and operations described herein are not to be interpreted as necessarily being carried out in the particular order discussed or illustrated, unless they are expressly identified as a sequence of execution.Additional or alternative steps can be applied.

[0014] When an element or layer is described as being "on" or "interacting with" another element or layer, or as being "connected" or "coupled" to or "attached" to the same, it may be directly on or interacting with, connected with, or coupled to the other element or layer, or there may be intervening elements or layers. However, when an element is described as being "directly on" or "directly interacting with" another element or layer, or as being "directly connected" or "directly coupled" to or "directly attached" to the same, there must be no intervening elements or layers. Other words used to describe the relationship between elements should be interpreted similarly (e.g.,“Between” as opposed to “directly between”, “neighboring” or “adjacent” as opposed to “directly adjacent” or “directly bordering”, etc.). As used herein, the term “and / or” includes all combinations of one or more of the related listed items.

[0015] The terms "first," "second," "third," etc., may be used herein to describe different elements, components, areas, layers, and / or sections. These elements, components, areas, layers, and / or sections should not be restricted by these terms. These terms may only be used to distinguish one element, component, area, layer, or section from another. Terms such as "first," "second," and other numerical terms do not imply any sequence or order unless the context clearly indicates otherwise.Thus, one could refer to a first element, a first component, a first area, a first layer or a first section discussed below as a second element, second component, second area, second layer or second section, without deviating from the lessons of the exemplary configurations.

[0016] In this application, which includes the definitions below, the term "module" may be replaced by the term "circuit". The term "module" may refer to, be part of, or include: an application-specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field-programmable gate array (FPGA); a processor (common, dedicated, or group) that executes code; a memory (common, dedicated, or group) that stores code executed by a processor; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-a-chip.

[0017] The term "code," as used above, can include software, firmware, and / or microcode, and can refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor that, in combination with additional processors, executes some or all of the code from one or more modules. The term "shared memory" includes a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory that, in combination with additional memory, stores some or all of the code from one or more modules. The term "memory" is a subset of the term "computer-readable medium."The term "computer-readable medium" excludes transitory electrical and electromagnetic signals propagating through a medium and can therefore be considered tangible and non-transient. Non-restrictive examples of non-transient storage include tangible, computer-readable media, including non-volatile memory, magnetic memory, and optical memory.

[0018] The devices and methods described in this application can be implemented in whole or in part by one or more computer programs executed by one or more processors. The computer programs comprise processor-executable instructions stored on at least one non-transient, tangible, computer-readable medium. The computer programs may also include and / or be based on stored data.

[0019] A software application (i.e., a software resource) can refer to computer software that causes a computer device to perform a task. In some examples, a software application may be called an "application," "app," or "program." Examples of applications include system diagnostics applications, system administration applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0020] Non-transitory memory can be physical devices used to store programs (e.g., sequences of instructions) or data (e.g., information about the program state) on a temporary or permanent basis for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., typically used for firmware, such as boot programs).Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and floppy disks or tapes.

[0021] These computer programs (also referred to as programs, software, software applications, or code) comprise machine instructions for a programmable processor and may be implemented in a procedural and / or object-oriented high-level programming language and / or in assembly / machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, any non-transitory computer-readable medium, any device, and / or apparatus (e.g., magnetic disks, optical disks, memory, programmable logic devices (PLDs)) used to supply machine instructions and / or data to a programmable processor, including any machine-readable medium that receives machine instructions as a machine-readable signal.The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0022] Various implementations of the systems and techniques described herein may be carried out in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application-specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and / or interpretable on a programmable system comprising at least one programmable processor, which may be a special-purpose or general-purpose processor, and coupled such that it receives data and instructions from and transmits data and instructions to a storage system, at least one input device, and at least one output device.

[0023] The processes and logical sequences described in this patent can be performed by one or more programmable processors, also known as data processing hardware, which execute one or more computer programs to perform functions by processing input data and generating outputs. The processes and logical sequences can also be performed by specialized logic circuits, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). Processors suitable for executing a computer program include, for example, both general-purpose and specialized microprocessors, and one or more processors of all types of digital computers. Generally, a processor receives instructions and data from read-only memory, random-access memory, or both.The essential elements of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Generally, a computer also includes one or more mass storage devices for storing data, such as magnetic, magneto-optical, or optical disks, or is functionally coupled to them to receive data from or transmit data to them, or both. However, a computer does not necessarily have to have these devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.The processor and memory can be supplemented by special logic circuits or integrated into them.

[0024] To enable interaction with a user, one or more aspects of the revelation can be implemented on a computer that has a display device, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touchscreen, to display information to the user, and optionally a keyboard and pointing device, such as a mouse or trackball, through which the user can input information into the computer. Other types of devices can also be used for interaction with a user; for example, the feedback provided to the user can be any form of sensory feedback, such as visual, auditory, or tactile feedback; and the user's input can be received in any form, including acoustic, verbal, or tactile input.Furthermore, a computer can interact with a user by sending and receiving documents to a device used by the user, for example by sending web pages to a web browser on a user's client device in response to documents requested by the web browser.

[0025] With reference to Fig. 1-4D, a wind monitoring system 10 comprises an electronic control unit (ECU) 12 of a vehicle 100, which is communicatively coupled to an off-board server 200 via a network 210. The off-board server 200 can be configured as a back-office server, a third-party server, or any other server that can be used to communicate with the electronic control unit 12 of the vehicle 100, either directly or via the network 210. The off-board server 200 is configured to communicate weather data 202 to the vehicle 100, which is used as part of a wind monitoring application 14 of the electronic control unit 12, described in more detail below.

[0026] The vehicle 100 is also equipped with a sensor system 110 that defines a plurality of detection zones 112 around the vehicle 100. Each detection zone 112 contains at least one ultrasonic sensor 114 designed to detect wind data 116. The wind data 116, detected by the ultrasonic sensors 114, includes wind direction 118 and wind speed 120. The wind data 116 is transmitted to the wind monitoring application 14 of the electronic control unit 12. The wind monitoring application 14 is executed by the data processing hardware 16 of the electronic control unit 12. The electronic control unit 12 also includes memory hardware 18 that communicates with the data processing hardware 16. The memory hardware 18 stores instructions which, when executed on the data processing hardware 16, cause the data processing hardware 16 to perform the operations described herein.

[0027] The data processing hardware 16 also executes an automatic driving function 20 of the vehicle 100 and an estimation model 22. The automatic driving function 20 can include automated operation of the vehicle 100, such as the use of a cruise control function or other automated driving functions. The estimation model 22 is designed to generate the vehicle dynamics 24 used by the wind monitoring application 14 described herein. The wind monitoring application 14 includes object data 30, which can be designed with the wind monitoring application 14, acquired by the sensor system 110, and / or entered by a user. The object data 30 includes, for example, vehicle data 32 and trailer data 34.

[0028] The vehicle data 32 can be acquired by the sensor system 110 and includes a vehicle speed 32a and a steering angle 32b. The vehicle data 32 can change during the operation of the vehicle 100, so that the vehicle data 32 can be continuously updated to acquire a current vehicle speed 32a and a current steering angle 32b. The trailer data 34 can be entered by a user and includes trailer dimensions 34a, trailer mass 34b, and number of axles 34c. In some examples, the vehicle data 32 and the trailer data 34 may also include other components or data characteristics.

[0029] The wind monitoring application 14 is also designed with a fusion function 40. The fusion function 40 is designed to fuse the vehicle dynamics 24 from the estimation model 22, the wind data 116 from the sensor system 110, and the weather data 202 from the off-board server 200 to produce fused wind data 42, which is used by the wind monitoring application 14. The wind monitoring application 14 continuously receives the wind data 116 and the weather data 202, so that the fused wind data 42 can be continuously updated to reflect changes in the wind data 116 and the weather data 202.

[0030] The wind monitoring application 14 is also designed with a criticality function 50. The criticality function 50 uses the fused wind data 42 and the object data 30 to generate a criticality value 52. The wind monitoring application 14 can execute the criticality function 50 based on the object data 30. The criticality value 52 is related to the object data 30, so the criticality function 50 uses the object data 30 to determine the criticality value 52. For example, the criticality function 50 can determine that the trailer data 34 is vulnerable to impact based on the fused wind data 42, so the criticality value 52 can exceed a criticality threshold 54 based on the object data 30 (i.e., trailer dimensions 34a, trailer mass 34b, and / or number of axles 34c).The criticality value 52 can be used by the wind monitoring application 14 to determine whether a crosswind support function 60 should be executed.

[0031] The crosswind assist function 60 can, for example, include lateral controls 62 based on the wind type 64 identified from the fused wind data 42. The lateral controls 62 include, among others, lane keeping assist 62a, steering assist 62b, brake assist 62c, and / or disturbance compensation 62d. The crosswind assist function 60 can also issue a warning 70 at a user interface 150 ( Fig. 1) of the vehicle 100, in addition to executing the lateral control 62 of the crosswind support function 60. The wind monitoring application 14 can use the fused wind data 42 to determine which of the lateral controls 62 should be executed as part of the crosswind support function 60.

[0032] The wind data 116 can change or be otherwise altered during the operation of the vehicle 100. Possible changes to the wind data 116 can cause the criticality function 50 to adjust or otherwise modify the criticality value 52. For example, the wind direction 118 can change, so that the fused wind data 42 relative to the object data 30 can lead to an alarmed criticality value 52. As a result, the criticality value 52 can further increase above and / or decrease below the criticality threshold 54. In response, the wind monitoring application 14 can adjust the side controls 62. In some cases, the wind monitoring application 14 can execute additional side controls 62 and / or deactivate the side controls 62 based on the criticality value 52.

[0033] The wind monitoring application 14 is designed to compare the wind direction 118 and the wind force 120 with the criticality value 52, which can also be used to determine whether to execute the side controls 62 and / or issue the warning 70. For example, the wind monitoring application 14 may determine that at least one of the wind direction 118 and the wind force 120 exceeds the criticality value 52, which in turn would mean that the criticality value 52 exceeds the criticality threshold 54. In response, the wind monitoring application 14 may execute the side wind support function 60 to execute one or more of the side controls 62. In some cases, the wind monitoring application 14 may issue the warning 70 and wait for a user input response before executing the side controls 62.When the automatic driving function 20 of the vehicle 100 is activated, the wind monitoring application 14 can automatically execute the side controls 62 and issue the warning 70.

[0034] Warning 70 can be designed as a haptic warning, an acoustic warning and / or as a symbol on the user interface 150 ( Fig. 1) Warning 70 can, for example, be issued as an audible signal in the vehicle 100, include a written warning on the user interface 150, and / or cause the steering wheel of the vehicle 100 to vibrate. Warning 70 is designed to inform the user (i.e., a driver and / or occupants) of the vehicle 100 that the wind conditions are unfavorable based on object data 30. Thus, based on the fused wind data 42, object data 30, and criticality value 52, Warning 70 can recommend to the driver that the vehicle 100 stop or reduce its speed. As mentioned earlier, when the automatic driving functions 20 of the vehicle 100 are activated, the wind monitoring application 14 can automatically adjust the operation of the vehicle 100 by executing the side controls 62 while continuing to provide Warning 70.

[0035] With further reference to Fig. 2-4D, the wind monitoring application 14 is designed to detect an impact wind 300 that may result from a crosswind and / or a pulling force from passing vehicles 302. For example, illustrates Fig. 4A a vehicle 100 exposed to a crosswind of 300, and Fig. Figures 4B-4D illustrate an impact wind 300 generated by a vehicle 100 passing and / or being overtaken by another vehicle 302 (e.g., a semi-trailer truck). The impact wind 300 is detected by the ultrasonic sensors 114. While the impact wind 300 may be directed towards one side of the vehicle 100, it can also originate from different directions. The ultrasonic sensors 114 are arranged around the vehicle 100 to define the detection zones 112.

[0036] The detection zones 112 are designed to overlap each other, so that the impact wind 300 can be detected regardless of its approach angle. Furthermore, the ultrasonic sensors 114 are designed to detect the impact wind 300 regardless of its approach angle relative to the ultrasonic sensors 114. For example, while the impact wind 300 may have an approach angle perpendicular to the vehicle 100, the ultrasonic sensors 114 are designed to detect the impact wind 300 even if the approach angle of the impact wind is not perpendicular. For example, [illustrates...] Fig. 4D, an angular direction of the impact wind 300, which can be detected by the ultrasonic sensors 114. The impact wind 300 is recorded by the ultrasonic sensors 114 as wind data 116, so that the ultrasonic sensors 114 detect the wind direction 118 and the wind force 120.

[0037] As in Fig. 4B and Fig. As illustrated in Figure 4C, the impact wind 300 can further be defined by a low-pressure zone 304 between vehicle 100 and the passing vehicle 302. The impact wind 300 can be defined by a size difference between vehicle 100 and the passing vehicle 302. The passing vehicle 302 is illustrated, for example, as a semi-trailer truck, which can lead to a greater tractive force between vehicles 100 and 302. This defines the low-pressure zone 304 between vehicle 100 and the passing vehicle 302 when vehicle 100 passes or is overtaken by the passing vehicle 302. The low-pressure zone 304 is a result of higher pressure on an opposite side of the vehicle 100 and the passing vehicle 302, so that the area between the vehicle 100 and the passing vehicle 302 forms a low-pressure zone 304 through which the impact wind 300 flows.Furthermore, when the impact wind 300 passes through the low-pressure zone 304, the impact wind 300 can gain speed, thereby further defining the low-pressure zone 304.

[0038] Each of the in the Fig. The scenarios illustrated in Figures 4A-4D represent various scenarios in which the impact wind 300 can cause the wind monitoring application 14 to trigger the crosswind support function 60. Thus, the wind monitoring application 14 is designed to differentiate between various impact wind 300 scenarios based on the wind direction 118 and wind speed 120 detected in the wind data 116. Furthermore, the fusion function 40 uses the vehicle dynamics 24 and the weather data 202 from the off-board server to compare them with the wind data 116 and generate the fused wind data 42. The fused wind data 42 represents the wind monitoring application 14, which identifies different scenarios and adjusts the response (i.e., the side controls 62) based on the identified scenario.

[0039] Fig. Figure 5 illustrates an exemplary flowchart of the fusion function 40 of the wind monitoring application 14. The vehicle dynamics 24 are determined at 500, and the ultrasonic sensors 114 acquire the wind data 116 at 502. For high-sided vehicles 100, an open loop is executed at 504 between the acquired vehicle dynamics 24 and the acquired wind data 116. At 506, the weather data 202 are determined, and the wind monitoring application 14 executes the fusion function 40 at 508. The fusion function 40 receives the vehicle dynamics 24, the wind data 116, and the weather data 202 at 508 and outputs the fused wind data 42 at 510.

[0040] Fig. Figure 6 illustrates an example flowchart for the execution of the crosswind assist function 60. At 600, the ultrasonic sensors 114 acquire the wind data 116, and the wind monitoring application 14 monitors the wind data 116. At 602, the wind monitoring application 14 determines whether the wind speed 120 is high. If it is not, the wind monitoring application 14 continues to monitor the wind data 116 acquired by the ultrasonic sensors 114. If the wind speed 120 is high, the wind monitoring application 14 can identify the wind type 64 at 604 and the vehicle scenario at 606. The wind monitoring application 14 can then execute the crosswind assist function 60 at 608 and the lateral controls 62 at 610. In response, the wind monitoring application 14 issues the warning 70 at 612.

[0041] Fig. Figure 7 illustrates another exemplary flowchart for the wind monitoring application 14 for determining the criticality value 52. At 700, the ultrasonic sensors 114 acquire the wind data 116, and the wind monitoring application 14 monitors the wind data 116. At 702, the wind monitoring application 14 determines the wind direction 118 and at 704 determines the wind speed 120. The wind direction 118 and the wind speed 120 are compared at 706 with the vehicle dynamics 24 and the weather data 202, and at 708 the wind monitoring application 14 identifies the object data 30, including the vehicle data 32 and the trailer data 34. At 710, the wind monitoring application 14 generates the criticality value 52 via the criticality function 50. Based on the trailer data 34, the wind monitoring application 14 determines at 712 whether the criticality value 52 The criticality threshold of 54 is exceeded.If the criticality value 52 exceeds the criticality threshold 54, the wind monitoring application 14 issues warning 70 at 714. If this is not the case, the wind monitoring application 14 determines at 716, based on the vehicle data 32, whether the criticality value 52 exceeds the criticality threshold 54. If the criticality value 52 exceeds the criticality threshold 54, the wind monitoring application 14 issues warning 70 at 714. If this is not the case, the wind monitoring application 14 continues to receive and monitor the wind data 116.

[0042] With reference to Fig.Figure 8 illustrates a procedure 800 for the wind monitoring system 10. At 802, the wind monitoring system 10 defines a plurality of detection zones 112 using a plurality of ultrasonic sensors 114. At 804, the plurality of ultrasonic sensors 114 acquire wind data 116 from one or more of the plurality of detection zones 112. At 806, the wind monitoring application 14 determines a wind direction 118 and a wind speed 120 based on the wind data 116 and receives weather data 202 at 808. At 810, the weather monitoring application 14 performs a fusion function 40 on the wind data 116, the weather data 202, and the vehicle dynamics 24 to define fused wind data 42. The wind monitoring application receives object data 30 at 812 and executes a criticality function 50 at 814 based on the fused wind data 42 and the object data 30. The criticality function 50 generates a criticality value 52 at 816 based on the object data 30.

[0043] At 818, the wind monitoring application 14 determines, based on the fused wind data 42, that at least one of the wind direction 118 and wind speed 120 exceeds the criticality value 52. At 820, based on the fused wind data 42 and the wind direction 118 or wind speed 120 exceeding the criticality value 52, the wind monitoring application 14 executes a crosswind support function 60. At 822, the wind monitoring application 14 executes the lateral controls 62 of the crosswind support function 60. At 824, the wind monitoring application 14 issues a warning 70 if either the wind direction or the wind speed exceeds the criticality value 52.

[0044] Several implementations have been described. However, it is understood that various modifications can be made without deviating from the spirit and scope of the revelation. Accordingly, other implementations also fall within the scope of the following claims.

[0045] The foregoing description serves only for illustration and description. It makes no claim to be complete or to limit the disclosure. Individual elements or features of a particular configuration are generally not restricted to that particular configuration, but are interchangeable and may be used in a selected configuration even if they are not specifically shown or described. They may also be modified in many ways. Such modifications are not to be considered a departure from the disclosure, and all such changes are intended to be contained within the scope of the disclosure. legend

[0046] In the drawing figures, N stands for no and Y for yes.

Claims

[1] A computer-implemented procedure which, when executed by data processing hardware, causes the data processing hardware to perform operations which include: Define, via a multitude of ultrasonic sensors, a multitude of detection zones; Capture, via the multitude of ultrasonic sensors, wind data from one or more of the numerous detection zones; Determine, via a wind monitoring application, a wind direction and a wind speed based on the wind data; Receiving weather data on the wind monitoring application; Execute, via the wind monitoring application, a fusion function on the wind data, the weather data and the vehicle dynamics to define fused wind data; Execute, based on the fused wind data, a crosswind support function of the wind monitoring application; and Execute, via the wind monitoring application, side controls of the crosswind assist function. [2] Method according to claim 1, wherein performing the crosswind assist function includes issuing a warning to a user interface of a vehicle. [3] Method according to claim 1, further comprising receiving object data on the wind monitoring application. [4] Method according to claim 3, wherein the object data includes vehicle data and trailer data, wherein the trailer data includes one or more of trailer dimensions, trailer mass and number of axles, and the vehicle data includes vehicle speed and steering angle. [5] The method of claim 3, further comprising performing a criticality function based on the fused wind data and the object data, and generating a criticality value based on the object data via the criticality function. [6] Method according to claim 5, wherein performing the crosswind assist function comprises adjusting the lateral controls based on the criticality value. [7] The method of claim 5, further comprising determining, on the basis of the fused wind data, that the wind direction and / or wind speed exceed the criticality value. [8] Method according to claim 7, further comprising issuing a warning in response to the fact that the wind direction or wind speed exceeds the criticality value. [9] Wind monitoring system designed to perform the method according to claim 1. [10] Vehicle equipped with the wind monitoring system according to claim 9.