阅读说明：本技术 基于天气条件的车辆前照光的控制 (Control of vehicle front lighting based on weather conditions ) 是由 马哈茂德·尤瑟夫·加纳姆 布莱恩·本尼 艾德·M·杜道尔 于 2019-08-19 设计创作，主要内容包括：本公开提供了“基于天气条件的车辆前照光的控制”。公开了用于基于天气条件控制车辆前照光的方法和设备。示例车辆包括前照灯,所述前照灯包括近光灯和远光灯。示例车辆还包括光传感器、相机和控制器。控制器用于在光传感器检测到低环境光时将近光灯设置为激活模式,经由相机监测低环境光下的降水,识别降水和由所述前照灯发射的光之间的入射角(AOI),并基于AOI控制远光灯。(The present disclosure provides "control of vehicle headlights based on weather conditions". Methods and apparatus for controlling vehicle front lighting based on weather conditions are disclosed. An example vehicle includes a headlamp that includes a low beam and a high beam. The example vehicle also includes a light sensor, a camera, and a controller. The controller is configured to set the high beam to an active mode when the light sensor detects low ambient light, monitor precipitation under the low ambient light via the camera, identify an angle of incidence (AOI) between the precipitation and light emitted by the headlamp, and control the high beam based on the AOI.)

1. A vehicle, comprising:

a headlamp comprising a low beam and a high beam;

a light sensor;

a camera; and

a controller to:

setting the low beam light to an active mode when the light sensor detects low ambient light;

monitoring precipitation under the low ambient light via the camera;

identifying an angle of incidence (AOI) between the precipitation and light emitted by the headlamp; and

controlling the high beam based on the AOI.

2. The vehicle of claim 1, wherein the controller is to:

monitoring, via the camera, for smoke in the low ambient light; and

identifying the AOI between the smoke and the light emitted by the headlamp.

3. The vehicle of claim 1, wherein to control the high beam based on the AOI, the controller sets the low beam to an inactive mode in response to detecting a precipitation flow stream perpendicular or parallel to light emitted by the headlamps.

4. The vehicle of claim 1, wherein to control the high-beam based on the AOI, the controller is to adjust the high-beam to emit high-beam in a direction corresponding to a flow stream of precipitation of a crosswind.

5. The vehicle of claim 1, wherein the controller is to:

identifying a clear line of sight within the precipitation based on images captured by the camera; and

so that the high beam emits high beams in the direction of the clear line of sight.

6. The vehicle of claim 1, wherein the controller is to:

detecting at least one of a nearby pedestrian and an oncoming vehicle based on at least one of the camera and proximity sensor; and

setting the low beam light to an inactive mode in response to detecting the at least one of the nearby pedestrian and the oncoming vehicle.

7. The vehicle of claim 1, wherein the controller is to:

detecting a line of sight of a vehicle operator; and

controlling the high beam based on the line of sight of the vehicle operator.

8. The vehicle of claim 1, wherein each of the high beams includes a plurality of LEDs, and the controller adjusts which of the plurality of LEDs is active to adjust the direction in which the high beams emit high beams.

9. The vehicle of claim 1, wherein each of the high-beam headlights includes a rotatable frame, and the controller rotates the rotatable frame to adjust a direction in which the high-beam headlights emits high-beam light.

10. A vehicle, comprising:

a headlamp comprising a low beam and a high beam;

a communication module; and

a controller to:

setting the low beam light to an active mode in response to detecting low ambient light via the communication module;

monitoring precipitation under the low ambient light via the communication module;

identifying an angle of incidence (AOI) between the precipitation and light emitted by the headlamp; and

controlling the high beam based on the AOI.

11. The vehicle of claim 10, wherein the controller identifies the AOI between the precipitation and the light emitted by the headlamp based on a direction of travel and a wind direction.

12. The vehicle of claim 10, further comprising a GPS receiver for identifying a current vehicle location.

13. The vehicle of claim 12, wherein the communication module is to obtain weather conditions for the current vehicle location from a remote weather service.

14. The vehicle of claim 13, wherein the controller is to identify a predicted travel route based at least in part on the current vehicle location, and the communication module is to obtain weather conditions for the predicted travel route from the remote weather service.

15. A method, comprising:

detecting, via a light sensor, an ambient light level of a vehicle;

setting a low beam of the headlamps to an active mode when the light sensor detects low ambient light;

monitoring, via a processor, precipitation under the low ambient light;

identifying, via the processor, an angle of incidence (AOI) between the precipitation and light emitted by the headlamp; and

controlling a high beam of the headlamp based on the AOI.

Technical Field

The present disclosure relates generally to vehicle headlights and, more particularly, to control of vehicle headlights based on weather conditions.

Background

Typically, a vehicle includes a headlamp to illuminate an area in front of the vehicle. Generally, a vehicle includes a low beam headlamp for illuminating a side of a road on which the vehicle travels. Additionally, vehicles typically include high-beam lights for illuminating a large portion of the road (e.g., illuminating one side of the road on which the vehicle is traveling and one side of the road on which the oncoming vehicle is traveling). Some regulations dictate that high-beam lights not be used when a vehicle is approaching a pedestrian and/or another vehicle to prevent the high-beam lights from reducing visibility of the pedestrian and/or vehicle operator.

Disclosure of Invention

The appended claims define the application. This disclosure summarizes aspects of the embodiments and should not be used to limit the claims. Other implementations are contemplated as the techniques described herein and are intended to be within the scope of the present application as will be apparent to one of ordinary skill in the art upon examination of the following figures and detailed description.

An example embodiment for controlling vehicle front lighting based on weather conditions is shown. A disclosed example vehicle includes a headlamp that includes a low beam and a high beam. The disclosed example vehicle also includes a light sensor, a camera, and a controller. The controller is configured to set the high beam to an active mode when the light sensor detects low ambient light, monitor precipitation under the low ambient light via the camera, identify an angle of incidence (AOI) between the precipitation and light emitted by the headlamp, and control the high beam based on the AOI.

In some examples, the controller is to monitor, via the camera, smoke in the low ambient light and identify an AOI between the smoke and the light emitted by the headlamp. In some examples, the controller utilizes image recognition to identify the AOI based on images captured by the camera.

In some examples, to control the high beam based on AOI, the controller sets the high beam to an inactive mode in response to detecting a flow of precipitation perpendicular or parallel to light emitted by the headlamps. In some examples, to control the high beam based on AOI, the controller will adjust the high beam to emit high beams in a precipitation flow stream direction corresponding to crosswind. In some examples, the controller identifies a clear line of sight within the precipitation based on an image captured by the camera and causes the high beam to emit high beams in a direction of the clear line of sight.

In some examples, the controller detects at least one of a nearby pedestrian and an oncoming vehicle based on at least one of the camera and the proximity sensor, and sets the proximity light to the inactive mode in response to detecting at least one of a nearby pedestrian and an oncoming vehicle.

In some examples, the controller is to detect a line of sight of a vehicle operator and control the high beam based on the line of sight of the vehicle operator. In some such examples, the controller is configured to detect the line of sight via at least one of an interior camera, a seat position sensor, and a restraint control module.

In some examples, each of the high beams includes a plurality of LEDs, and the controller adjusts which of the plurality of LEDs is active to adjust the direction in which the high beams emit high beams. In some examples, each of the high-beam lamps includes a rotatable frame, and the controller rotates the rotatable frame to adjust a direction in which the high-beam lamp emits the high-beam light.

A disclosed example vehicle includes a headlamp that includes a low beam and a high beam. The disclosed example vehicle also includes a communication module and a controller. The controller sets a high beam to an active mode in response to detecting low ambient light via the communication module, monitors precipitation under the low ambient light via the communication module, identifies an angle of incidence (AOI) between the precipitation and light emitted by the head lamp, and controls the high beam based on the AOI.

In some examples, the communication module comprises a dedicated short-range communication module. In some examples, the controller identifies an AOI between precipitation and light emitted by the headlamp based on a direction of travel and a wind direction.

Some examples also include a GPS receiver for identifying the current vehicle location. In some such examples, the communication module is to obtain weather conditions for the current vehicle location from a remote weather service. Further, in some such examples, the controller is to identify a predicted travel route based at least in part on a current vehicle location, and the communication module is to obtain weather conditions for the predicted travel route from a remote weather service.

In some examples, to control the high beam based on AOI, the controller sets the high beam to an inactive mode in response to detecting a flow of precipitation perpendicular or parallel to light emitted by the headlamps. In some examples, to control the high beam based on AOI, the controller will adjust the high beam to emit high beams in a precipitation flow stream direction corresponding to crosswind.

A disclosed example method includes detecting an ambient light level of a vehicle via a light sensor, and setting a low beam of headlamps to an active mode when the light sensor detects low ambient light. The disclosed example method also includes monitoring, via a processor, precipitation under low ambient light, and identifying, via the processor, an angle of incidence (AOI) between the precipitation and light emitted by the headlamp. The disclosed example method also includes controlling a high beam of the headlamp based on the AOI.

Drawings

For a better understanding of the invention, reference may be made to the embodiments illustrated in the following drawings. The components in the figures are not necessarily to scale and related elements may be omitted or, in some cases, the scale may have been exaggerated in order to emphasize and clearly illustrate the novel features described herein. In addition, the system components may be arranged in different ways, as is known in the art. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 illustrates an example vehicle according to the teachings herein.

FIG. 2 illustrates an example headlamp for the vehicle of FIG. 1.

Fig. 3A-3B illustrate example adjustments of a high beam of the vehicle of fig. 1.

Fig. 4A-4D depict example weather conditions in which the vehicle of fig. 1 is configured to travel.

Fig. 5 is a block diagram of electronic components of the vehicle of fig. 1.

Fig. 6 is a flow chart for adjusting a high beam of a vehicle based on weather conditions according to the teachings herein.

Detailed Description

While the present invention may be embodied in various forms, there is shown in the drawings and will hereinafter be described some exemplary and non-limiting embodiments, with the understanding that the present disclosure is to be considered an exemplification of the invention and is not intended to limit the invention to the specific embodiments illustrated.

Typically, a vehicle includes a headlamp to illuminate an area in front of the vehicle. Generally, a vehicle includes a low beam headlamp for illuminating a side of a road on which the vehicle travels. Additionally, vehicles typically include high-beam lights for illuminating a large portion of the road (e.g., illuminating one side of the road on which the vehicle is traveling and one side of the road on which the oncoming vehicle is traveling). In some cases, high beams of light directed at a pedestrian and/or the driver of another vehicle can potentially reduce visibility of the pedestrian and/or other driver. Further, some rules dictate that high beam headlamps not be used when the vehicle is in proximity to a pedestrian and/or other vehicle. Furthermore, in some cases, precipitation and/or other conditions (e.g., rain, snow, smoke, fog, etc.) cause the high-beam light to reflect off the driver's eyes (rather than being scattered and reflected back to the driver's eyes by the road in dry conditions), thereby creating glare, which potentially makes it more difficult for the driver to see the road.

Example methods and apparatus disclosed herein autonomously adjust a high beam of a vehicle to increase visibility of a vehicle operator based on ambient light levels and ambient weather conditions. Examples disclosed herein include a system for controlling a high beam of a vehicle. The system detects whether the ambient light around the vehicle is low. If the ambient light level is low, the system detects whether there are reduced visibility weather conditions (e.g., dust, sand, precipitation such as rain, snow, fog, etc.) in the surrounding area of the vehicle. If the system detects a weather condition with reduced visibility, the system (1) identifies a streaming flow of the weather condition and (2) adjusts an angle of incidence of the high beam based on the streaming flow to increase visibility within the weather condition. For example, the system (1) deactivates the high beam when a streaming flow is detected that is perpendicular and/or parallel to the high beam, or (2) adjusts the direction of the high beam when a streaming flow is detected that corresponds to a crosswind relative to the vehicle. Further, the system deactivates the high beam when nearby pedestrian(s) and/or oncoming vehicle(s) are detected.

Turning to the drawings, FIG. 1 illustrates an example vehicle 100 according to the teachings herein. The vehicle 100 may be a standard gasoline powered vehicle, a hybrid vehicle, an electric vehicle, a fuel cell vehicle, and/or any other mobility-enabling type of vehicle. The vehicle 100 includes mobility-related components such as a powertrain with an engine, a transmission, a suspension, a drive shaft, and/or wheels, etc. The vehicle 100 may be non-autonomous, semi-autonomous (e.g., some routine power functions are controlled by the vehicle 100), or autonomous (e.g., power functions are controlled by the vehicle 100 without direct driver input).

In the illustrated example, the vehicle 100 includes a windshield 102 and a cabin 104 at least partially defined by the windshield 102. For example, the windshield 102 is formed of laminated glass or safety glass to prevent the windshield 102 from shattering during a collision event. The cabin 104 includes a driver seat 106, and an operator (e.g., driver) of the vehicle 100 will be seated in the driver seat 106. The windshield 102 enables an operator sitting in the operator's seat 106 to view the surrounding area in front of and/or to the sides of the vehicle 100.

As shown in fig. 1, the vehicle 100 also includes a headlamp 108. Further, each of the headlamps 108 includes a low beam 110 and a high beam 112. For example, each of the low beam lights 110 and the high beam lights 112 includes a plurality of Light Emitting Diodes (LEDs). In some examples, the LEDs of the low beam lights 110 and the high beam lights 112 are configured to be fully illuminated, fully dimmed, and/or partially illuminated. For example, the headlamps 108 produce a low beam setting when the low beam lamps 110 are fully illuminated and the high beam lamps 112 are fully dimmed. Further, the headlamps 108 produce a high beam setting when the high beams 112 are fully illuminated. In some examples, the orientation of one or more LEDs of the high-beam light 112 is adjustable to enable the high-beam light 112 to adjustably emit high-beam light in different directions.

Further, the vehicle 100 of the illustrated example includes an exterior camera 114, a proximity sensor 116, and a light sensor 118. The exterior camera 114 is configured to capture image(s) and/or video of an exterior area surrounding the vehicle 100. For example, the exterior camera 114 is a forward-looking camera that captures image(s) and/or video of the area in front of and/or to the side of the vehicle 100. The proximity sensor 116 is configured to collect data that enables detection, location, and/or identification of object(s) near the vehicle 100. The proximity sensors 116 include radar sensors, lidar sensors, ultrasonic sensors, and/or any other sensors configured to collect data for detecting, utilizing, and/or identifying nearby objects. For example, a radar sensor detects and locates an object via radio waves, a laser radar sensor detects and locates an object via laser light, and an ultrasonic sensor detects and locates an object via ultrasonic waves. The light sensor 118 is configured to measure an ambient light level of ambient light surrounding the vehicle 100. For example, the light sensor 118 detects low ambient light levels when it is dark (e.g., at night, in a tunnel, in severe weather conditions, etc.), and/or detects high ambient light levels when it is lit (e.g., during the day).

In the illustrated example, the vehicle of the illustrated example includes an interior camera 120, a seat position sensor 122, and a restraint control module 124. The interior camera 120 captures image(s) and/or video of the cabin 104 of the vehicle 100. For example, the internal camera 120 captures: (1) a driver seat 106; and/or (2) image(s) and/or video(s) of an operator sitting in the operator's seat 106 to facilitate identification of: (a) the position and/or inclination of the operator's seat 106; (b) the location of the operator; and/or (c) a line of sight of an operator. In addition, the seat position sensor 122 is configured to detect the position and/or recline angle of the operator's seat to facilitate identifying the position and/or line of sight of the operator.

The restraint control module 124 (also referred to as RCM) is an electronic control unit (also referred to as ECU) of the vehicle 100. The ECU monitors and controls the subsystems of the vehicle 100. For example, an ECU is a collection of discrete electronic devices that include their own circuit(s) (e.g., integrated circuit, microprocessor, memory, storage, etc.) and firmware, sensors, actuators, and/or mounting hardware. The ECUs are configured to communicate and exchange information via a vehicle data bus (e.g., vehicle data bus 508 of fig. 5). For example, the ECUs may communicate characteristics (e.g., ECU status, sensor readings, control status, errors, diagnostic codes, etc.) to each other and/or receive requests from each other. The vehicle 100 may have tens of ECUs located at various locations around the vehicle 100 and communicatively coupled via a vehicle data bus.

The constraint control module 124 of the illustrated example is configured to: (1) detecting when the vehicle 100 is involved in a collision and/or hard braking event; and (2) deploy device(s) to restrain the position(s) of occupant(s) within the vehicle 100 upon detection of such an event. For example, upon detecting that the vehicle 100 is involved in a collision and/or a hard braking event, the restraint control module 124 deploys the airbag(s), activates the seatbelt pretensioner(s), and/or activates the seatbelt buckle device(s) to restrain the occupant(s) within the cabin 104 of the vehicle 100. In some examples, the restraint control module 124 includes an accelerometer and/or other crash sensor(s) to monitor for crash and/or hard braking events. For example, an accelerometer measures acceleration and/or vibration of the vehicle 100 to monitor the occurrence, location, and/or severity of a crash and/or hard braking event. Further, the restraint control module 124 of the illustrated example is configured to monitor the position and/or tilt angle of the operator's seat to facilitate identifying the position and/or line of sight of the operator.

In the illustrated example, the vehicle further includes a Global Positioning System (GPS) receiver 126, a communication module 128, and another communication module 130. For example, the GPS receiver 126 receives signals from a global positioning system to determine the location of the vehicle 100.

The communication module 128 of the illustrated example is a Dedicated Short Range Communication (DSRC) module that includes antenna(s), radio(s), and software to broadcast messages and establish connections between the vehicle 100 and other vehicle(s), infrastructure-based module(s), and/or mobile device-based module(s). That is, the communication module 128 is configured for vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and/or vehicle-to-ambient (V2X) communication. DSRC systems can be installed on vehicles as well as on infrastructure along the roadside. DSRC systems incorporating infrastructure information are referred to as "roadside" systems. DSRC may be combined with other technologies such as Global Positioning System (GPS), Visible Light Communication (VLC), cellular communication, and short range radar to facilitate a vehicle communicating its position, speed, heading, relative position to other objects, and exchanging information with other vehicles or external computer systems. The DSRC system may be integrated with other systems, such as mobile phones. Currently, DSRC networks are denoted by DSRC abbreviations or names. However, other names are sometimes used that are typically associated with networked vehicle programs and the like. Most of these systems are pure DSRC or variations of the IEEE802.11 wireless standard. However, in addition to pure DSRC systems, it is also intended to cover dedicated wireless communication systems between automobiles and roadside infrastructure systems that are integrated with GPS and based on IEEE802.11 protocols (e.g., 802.11p, etc.) for wireless local area networks.

The communication module 130 of the illustrated example includes a wired or wireless network interface to enable communication with external network(s) and/or other device(s). The external network may be public network(s), such as the internet; private networks, such as intranets; or a combination thereof and may utilize various networking protocols now available or later developed including, but not limited to, TCP/IP based networking protocols. The communication module 130 also includes hardware (e.g., processor, memory, storage, antenna, etc.) and software for controlling wired or wireless network interfaces. For example, the communication module 130 includes one or more communication controllers for a cellular network, such as global system for mobile communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Code Division Multiple Access (CDMA). In some examples, communication module 130 includes a Wireless Personal Area Network (WPAN) module configured to wirelessly communicate with mobile devices via short-range wireless communication protocol(s). For example, the communication module 130 implements

And/or

A low power consumption (BLE) protocol. Further, in some examples, the communication module 130 is configured to be communicatively coupled to the occupant's mobile device of the vehicle 100 via enabling the communication module 130 to communicate

Near Field Communication (NFC), ultra-wideband (UWB) communication, ultra-high frequency (UHF) communication, Low Frequency (LF) communication, and/or any other communication protocol to communicate wirelessly.

As shown in fig. 1, the vehicle 100 includes a headlamp controller 132, the headlamp controller 132 configured to control operation of the headlamp 108. For example, the headlamp controller 132 includes hardware (e.g., a processor, memory, storage, etc.) and software for controlling operation of the headlamps 108 of the vehicle 100.

In operation, the headlamp controller 132 detects an ambient light level of the vehicle 100. For example, the headlamp controller 132 detects the ambient light level based on: (1) data collected by the light sensor 118; (2) image(s) and/or video collected by external camera 114; (3) V2V, V2I, and/or V2X communications collected by the communications module 128; and/or (4) information collected by the communication module 130 and/or stored in an onboard database that identifies ambient light levels based on location, date, and time of day. Further, the headlamp controller 132 determines whether there is low ambient light by comparing the measured ambient light level to a predetermined threshold. For example, when the measured ambient light level is less than a predetermined threshold, the headlamp controller 132 determines that low ambient light is present. In response to the headlamp controller 132 determining that low ambient light is present, the headlamp controller 132 sets the low beam lamps 110 to an active mode (e.g., the headlamp controller 132 turns on the low beam lamps 110) to increase visibility of an operator of the vehicle 100.

Further, the headlamp controller 132 identifies weather conditions at the vehicle location as the vehicle travels through low ambient light. For example, the headlamp controller 132 monitors precipitation (e.g., rain, snow, fog, sleet, hail, etc.), smoke, dust, and/or other particulates that potentially reduce the visibility of the vehicle operator. In the illustrated example, the headlamp controller 132 is configured to identify precipitation and/or air particles based on: (1) image(s) and/or video captured by external camera 114; (2) data collected from vehicle sensor(s); (3) data collected from remote weather services via the communication module 130; (4) data collected from nearby vehicle(s), infrastructure module(s), mobile device(s) via communication module 128; (5) a current vehicle position identified via the GPS receiver 126; (6) a predicted travel path identified by the headlamp controller 132; and/or (7) any other collected data. For example, the headlamp controller 132 is configured to collect weather conditions for the current location of the vehicle 100 from a remote weather service for a selected and/or predicted travel path of the vehicle 100. In some examples, the headlamp controller 132 determines the predicted travel route based on the current location of the vehicle 100, the time of day, the day of the week, a route history of the vehicle 100, a route history of an operator of the vehicle 100, and the like.

Upon detecting precipitation and/or other reduced visibility airborne particles, the headlamp controller 132 identifies an angle of incidence between (1) the precipitation and/or airborne particles and (2) the light emitted by the headlamps 108. For example, the headlamp controller 132 utilizes image recognition software to identify the angle of incidence based on the image(s) and/or video captured by the external camera 114. Additionally or alternatively, the headlamp controller 132 determines the angle of incidence based on the direction of travel and the wind direction of the vehicle 100. For example, the GPS receiver 126 enables the headlamp controller 132 to identify the direction of travel of the vehicle 100. Further, the headlamp controller 132 identifies the wind direction based on weather data collected from a remote weather server, nearby vehicle(s), nearby infrastructure module(s), nearby mobile device(s), and the like.

Upon recognizing the incident angle, the headlamp controller 132 controls the high beam 112 based on the incident angle to increase visibility of an operator of the vehicle 100 in low light conditions. For example, in response to detecting a vertical flow of precipitation and/or a flow parallel to the direction of travel of the vehicle 100, the headlamp controller 132 sets the high-beam 112 to an inactive mode (e.g., turns off the high-beam 112) to prevent the high-beam from reducing visibility of the vehicle operator. In response to detecting a crosswind flow stream of precipitation, the headlamp controller 132: (1) setting the high-beam light 112 to an active mode (e.g., turning on the high-beam light 112); and (2) rotating the direction in which high beam 112 emits light to increase the visibility of the vehicle operator. For example, the headlamp controller 132 detects the direction of the flow stream of precipitation based on the image(s) and/or video captured by the external camera 114. Additionally or alternatively, the headlamp controller 132 detects the direction of the flow stream based on the direction of travel of the vehicle (e.g., as determined by the GPS receiver 126) and weather data (e.g., collected from a remote weather server and/or via V2X communication) including the precipitation wind direction of the vehicle location.

Further, in response to detecting a clear line of sight through clouds of precipitation (e.g., fog) and/or other airborne particles (e.g., smoke), headlamp controller 132 adjusts high-beam headlamp 112 to emit high-beam 304 in the direction of the clear line of sight to increase visibility of the vehicle operator. For example, the headlamp controller 132 identifies a clear line of sight based on (1) the image(s) and/or video captured by the exterior camera 114 and/or (2) the detected operator position. In some examples, the headlamp controller 132 identifies the position of the vehicle operator based on (1) the image(s) and/or video captured by the interior camera 120, (2) data collected by the seat position sensor 122, and/or data collected by the restraint control module 124.

Additionally or alternatively, the headlamp controller 132 monitors nearby pedestrian(s) and/or oncoming vehicle(s). For example, the headlamp controller 132 detects the presence of nearby pedestrian(s) and/or oncoming vehicle(s) based on (1) data collected by the proximity sensor 116, (2) images and/or video collected by the external camera 114, and/or (3) V2V, V2I, and/or V2X communications collected by the communication module 128. Upon detection of a nearby pedestrian and/or an oncoming vehicle, headlamp controller 132 sets high-beam 112 to an inactive mode (e.g., headlamp controller 132 turns high-beam 112 off) to prevent high-beam 112 of the vehicle from reducing visibility of the nearby pedestrian and/or an operator of the oncoming vehicle.

Fig. 2 shows one of the headlamps 108 of the vehicle 100. In the illustrated example, the head lamp 108 includes a housing 202. In addition, the head lamp 108 includes a low beam 110, a high beam 112, and a turn signal 204 positioned within the housing 202. The low beam 110 is configured to emit low beams, the high beam 112 is configured to emit high beams, and the turn signal 204 is configured to emit a turn signal.

In the illustrated example, the head lamp 108 includes a rotatable frame 206 positioned within the housing 202. The rotatable frame 206 is configured to rotate vertically and/or laterally within the housing 202 of the headlamp 108. Further, the high-beam lamp 112 is fixed to the rotatable frame 206 such that when the rotatable frame 206 is rotated, the high-beam lamp 112 is rotated. For example, headlamp controller 132 of vehicle 100 causes rotatable frame 206 to rotate high beam 112 and thereby adjust the direction in which high beam 112 emits high beam.

Additionally or alternatively, each of the low beam lights 110, the high beam lights 112, and/or the turn signal lights 204 includes a plurality of LEDs configured to fully illuminate, fully dim, and/or partially illuminate. In some examples, the LEDs are configured to be controlled individually and/or in groups by the headlamp controller 132. In some examples, the headlamp controller 132 adjusts (1) which LEDs are active and/or (2) the lighting of one or more LEDs of the high beams 112 to adjust the direction in which the high beams 112 emit high beams. For example, the headlamp controller 132 is configured such that (1) the upper LEDs emit more light than the lower LEDs such that the high-beam light 112 emits high-beam light in an upward direction, (2) the lower LEDs emit more light than the upper LEDs such that the high-beam light 112 emits high-beam light in a downward direction, (3) the left LEDs emit more light than the right LEDs such that the high-beam light 112 emits high-beam light in a leftward direction, and/or (4) the right LEDs emit more light than the left LEDs such that the high-beam light 112 emits high-beam light in a rightward direction.

Fig. 3A-3B illustrate a headlamp 108 of the vehicle 100 that emits light to illuminate an area in front of the vehicle 100. In the illustrated example, the low beam lamps 110 of the headlamps 108 emit low beams 302, and the high beam lamps 112 of the headlamps emit high beams 304. For example, the low beam light 110 emits the low beam 302 when set to the active mode, and does not emit the low beam 302 when set to the inactive mode. Similarly, the high-beam lamp 112 emits the high beam 304 when set to the active mode, and does not emit the high beam 304 when set to the inactive mode.

As shown in fig. 3A to 3B, the high-beam lamp 112 is configured to adjust the direction in which the high-beam light 304 is emitted. More specifically, fig. 3A depicts that the high-beam lamp 112 is configured to laterally adjust the direction in which the high-beam light 304 is emitted. Further, fig. 3B depicts that the high-beam lamp 112 is configured to vertically adjust the direction in which the high-beam light 304 is emitted. For example, headlamp controller 132 causes the high-beams to adjust the direction in which high-beams 304 are emitted by high-beams 112 laterally and/or vertically based on the detected weather conditions.

Fig. 4A-4D depict example weather conditions in which the vehicle of fig. 1 is configured to travel. More specifically, fig. 4A shows precipitation 402 with vertical flow streams 404 (e.g., rain, snow, fog, sleet, hail, etc.), fig. 4B shows precipitation 402 with parallel flow streams 406 relative to the direction of travel of vehicle 100, fig. 4C shows precipitation 402 with crosswind flow streams 408 relative to the direction of travel of vehicle 100, and fig. 4D shows when precipitation 402 is fog 410.

In fig. 4A, precipitation 402 has a vertical flow stream 404 that is substantially perpendicular to the ground along which vehicle 100 travels. The headlamp controller 132 is configured to detect when precipitation 402 travels along the vertical flow stream 404. Further, to increase visibility of the road by the operator of the vehicle 100, the headlamp controller 132 is configured to control the high beam 112 based on the angle of incidence corresponding to the vertical flow stream 404. For example, when precipitation 402 has a vertical flow stream 404, the angle of incidence between high beam 304 emitted by high beam 112 and precipitation 402 potentially results in reduced visibility for the operator. To increase operator visibility in low ambient light conditions, the headlamp controller 132 sets the high-beam light 112 to an inactive mode (e.g., turns off the high-beam light 112) in response to detecting the vertical flow stream 404 of precipitation 402.

In fig. 4B, precipitation 402 has parallel flow streams 406 relative to vehicle 100. For example, precipitation 402 has parallel flow streams 406 when vehicle 100 is traveling in the same or opposite direction as parallel flow streams 406. The headlamp controller 132 is configured to detect when precipitation 402 travels along the parallel flow stream 406. Further, to increase visibility of the road by the operator of the vehicle 100, the headlamp controller 132 is configured to control the high beam 112 based on the incident angle corresponding to the parallel flow stream 406. For example, when precipitation 402 has a parallel flow stream 406, the angle of incidence between high beam 304 emitted by high beam 112 and precipitation 402 potentially results in reduced visibility for the operator. To increase operator visibility in low ambient light conditions, the headlamp controller 132 sets the high-beam light 112 to the inactive mode (e.g., turns off the high-beam light 112) in response to detecting the parallel-flowing stream 406 of precipitation 402.

In fig. 4C, precipitation 402 has a crosswind flow stream 408 with respect to vehicle 100. For example, precipitation 402 has a crosswind flow stream 408 when precipitation 402 travels in a left-to-right and/or right-to-left direction relative to the direction of travel of the vehicle. That is, when there is a crosswind relative to the direction of travel of the vehicle 100, the precipitation 402 travels along the crosswind flow stream 408. The headlamp controller 132 is configured to detect when precipitation 402 travels along the crosswind flow stream 408. Further, the headlamp controller 132 is configured to detect a relative angle between the direction of the crosswind flow stream 408 and the direction of travel of the vehicle 100. To increase visibility of the road by the operator of the vehicle 100, the headlamp controller 132 is configured to control the high beam 112 based on the angle of incidence corresponding to the crosswind flow stream 408. For example, when precipitation 402 has a crosswind flow stream 408, the angle of incidence between high-beam 304 emitted by high-beam 112 and precipitation 402 potentially results in reduced visibility for the operator. To increase operator visibility, headlamp controller 132(1) sets high-beam 112 to an active mode (e.g., turns on high-beam 112) and (2) adjusts high-beam 112 to emit high-beam 304 in an angled direction in response to detecting crosswind flow 408 of precipitation 402. For example, in response to detecting precipitation 402 traveling in a direction corresponding to a left-to-right direction along crosswind flow stream 408, headlamp controller 132 causes high beam 112 to emit high beam 304 in a leftward direction. In response to detecting precipitation 402 traveling in the crosswind flow stream 408 corresponding to a right-to-left direction, headlamp controller 132 causes high beam 112 to emit high beam 304 in a right direction. The headlamp controller 132 adjusts the direction of emitting the high beam 304 based on the angle of incidence between the precipitation 402 and the light emitted by the high beam 304. That is, the headlamp controller 132 rotates the high beam based on the relative angle between the crosswind flow stream 408 and the direction of travel of the vehicle 100 to increase visibility of the operator of the vehicle 100 under low ambient light conditions.

In fig. 4D, precipitation 402 is fog 410. The headlamp controller 132 is configured to detect when the vehicle 100 is traveling through the fog 410. Upon detecting the fog 410, the headlamp controller 132 monitors a clear line of sight within the fog 410. For example, the headlamp controller 132 is configured to identify a clear line of sight within the fog 410 based on the image(s) and/or video captured by the exterior camera 114. In response to detecting a clear line of sight in the fog 410, the headlamp controller 132 adjusts the high beam 112 to emit the high beam 304 in the direction of the clear line of sight, thereby increasing the visibility of the operator when the vehicle is traveling through the fog 410 under low ambient light conditions. Similarly, the headlamp controller 132 is configured to identify a clear line of sight and cause the high beam 304 to be emitted in the direction of the clear line of sight as the vehicle 100 travels through smoke, dust, and/or other particulates that potentially obstruct visibility.

Fig. 5 is a block diagram of the electronic components 500 of the vehicle 100. As shown in fig. 5, the electronic components 500 include a front lighting control module 502 (also referred to as HCM), a GPS receiver 126, a communication module 128, a communication module 130, a camera 504, a sensor 506, and a restraint control module 124.

The front light control module 502 is an electronic control unit that controls the operation of the headlamps 108. The front light control module 502 includes a processor 510 (also referred to as a microcontroller unit and controller), a memory 512, and a database 514. In the illustrated example, the processor 510 of the front lighting control module 502 is configured to include the headlamp controller 132. In other examples, the headlamp controller 132 is incorporated into another ECU having its own processor, memory, and/or database. The database 514 is configured to include route histories for the vehicle 100 and/or a particular operator of the vehicle 100 to enable the headlamp controller 132 to identify a predicted travel route based on the current location of the vehicle 100, the time of day, the day of the week, etc.

Processor 510 may be any suitable processing device or group of processing devices, such as, but not limited to, a microprocessor, a microcontroller-based platform, an integrated circuit, one or more Field Programmable Gate Arrays (FPGAs), and/or one or more Application Specific Integrated Circuits (ASICs). The memory 512 may be volatile memory (e.g., RAM including non-volatile RAM, magnetic RAM, ferroelectric RAM, etc.), non-volatile memory (e.g., disk memory, flash memory, EPROM, EEPROM, memristor-based non-volatile solid-state memory, etc.), immutable memory (e.g., EPROM), read-only memory, and/or high capacity storage (e.g., hard disk drive, solid-state drive, etc.). In some examples, the memory 512 includes a variety of memories, particularly volatile and non-volatile memories.

The memory 512 is a computer-readable medium on which one or more sets of instructions, such as software for operating the methods of the present disclosure, may be embedded. The instructions may embody one or more of the methods or logic described herein. For example, the instructions reside, completely or at least partially, within any one or more of the memory 512, the computer-readable medium, and/or the processor 510 during execution thereof.

The terms "non-transitory computer-readable medium" and "computer-readable medium" include a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. Furthermore, the terms "non-transitory computer-readable medium" and "computer-readable medium" include any tangible medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a system to perform any one or more of the methods or operations disclosed herein. As used herein, the term "computer-readable medium" is expressly defined to include any type of computer-readable storage and/or storage disk and to exclude propagating signals.

In the illustrated example, the communication module 128 is a DSRC module configured to collect weather, light, and/or other data via V2V, V2X, and/or V2I communications. Further, the communication module 130 of the illustrated example is configured to wirelessly communicate with a remote server 516 via an external network 518. For example, the remote server 516 includes a remote weather server from which the communication module 130 obtains the current weather conditions for the current location of the vehicle 100 (e.g., as determined by the GPS receiver 126).

The camera 504 collects image(s) and/or video of the area(s) within and/or around the vehicle 100. In the example shown, the cameras 504 include an exterior camera 114, the exterior camera 114 configured to capture image(s) and/or video of a front and/or side area of the vehicle 100. For example, the image(s) and/or video captured by the external camera 114 enable the headlamp controller 132 to identify ambient light levels, weather conditions, angles of incidence of light emitted by the headlamps 108, and so forth. Further, the camera 504 of the illustrated example includes an interior camera 120, the interior camera 120 configured to capture image(s) and/or video of the cabin 104 of the vehicle 100. For example, the image(s) and/or video captured by the interior camera 120 enable the headlamp controller 132 to identify the line of sight of the operator of the vehicle 100.

Sensors 506 are disposed within and/or about vehicle 100 to monitor characteristics of vehicle 100 and/or the environment in which vehicle 100 is located. One or more of the sensors 506 may be mounted to measure characteristics of the exterior surroundings of the vehicle 100. Additionally or alternatively, one or more of the sensors 506 may be mounted within a cabin of the vehicle 100 or in a body of the vehicle 100 (e.g., an engine compartment, a wheel well, etc.) to measure a characteristic in the interior of the vehicle 100. For example, sensors 506 include accelerometers, odometers, tachometers, pitch and yaw sensors, wheel speed sensors, microphones, tire pressure sensors, biosensors, and/or any other suitable type of sensor.

In the example shown, the sensors 506 include the proximity sensor 116, the light sensor 118, and the seat position sensor 122. For example, the proximity sensors are configured to collect data capable of detecting, locating, and/or identifying object(s) (e.g., precipitation, smoke, pedestrians, other vehicles, etc.) in the vicinity of the vehicle 100. The light sensor 118 is configured to measure an ambient light level of ambient light surrounding the vehicle 100. Further, the seat position sensor 122 is configured to detect the position of the driver seat so that the headlamp controller 132 can recognize the line of sight of the operator of the vehicle 100.

The vehicle data bus 508 communicatively couples the headlamps 108, the restraint control module 124, the GPS receiver 126, the communication module 128, the communication module 130, the front lighting control module 502, the camera 504, and the sensors 506. In some examples, the vehicle data bus 508 includes one or more data buses. The vehicle data bus 508 may be in accordance with a Controller Area Network (CAN) bus protocol, a media oriented transport (MOST) bus protocol, a CAN Flexible data (CAN-FD) bus protocol (ISO 11898-7), and/or a K-wire bus protocol (ISO 9141 and ISO 14230-1) and/or Ethernet as defined by International Standards Organization (ISO)11898-1^TMBus protocol IEEE 802.3 (2002) and the like.

FIG. 6 is a flow diagram of an example method 600 for adjusting headlamps of a vehicle based on weather conditions. The flowchart of fig. 6 represents machine readable instructions stored in a memory, such as memory 512 of fig. 5, and includes one or more programs that, when executed by a processor, such as processor 510 of fig. 5, cause the vehicle 100 to implement the example headlamp controller 132 of fig. 1 and 4. Although the example program is described with reference to the flowchart shown in fig. 6, many other methods of implementing the example headlamp controller 132 may alternatively be used. For example, the order of execution of the blocks may be rearranged, varied, eliminated, and/or combined to perform the method 600. Furthermore, because methods 1-5 are disclosed in connection with the components of fig. 1-5, some of the functions of those components will not be described in detail below.

Initially, at block 602, the headlamp controller 132 detects an ambient light level of the vehicle 100. At block 604, the headlamp controller 132 determines whether low ambient light is present. For example, when the measured ambient light level is less than a predetermined threshold, the headlamp controller 132 determines that low ambient light is present. In response to the headlamp controller 132 determining that low ambient light is not present, the method 600 returns to block 602. Otherwise, in response to the headlight controller 132 determining that low ambient light is present, the method 600 proceeds to block 606, at which block 606 the headlight controller 132 sets the headlights 110 to an active mode (e.g., the headlight controller 132 turns on the low beam 110).

At block 608, the headlamp controller 132 determines whether there are nearby pedestrians and/or oncoming vehicles. In response to the headlamp controller 132 determining that there is a nearby pedestrian and/or an oncoming vehicle, the method 600 proceeds to block 610, at which block 610 the headlamp controller 132 sets the high-beam lamp 112 to the inactive mode (e.g., the headlamp controller 132 turns off the high-beam lamp 112). Otherwise, in response to the headlamp controller 132 identifying the presence of a nearby pedestrian and/or an oncoming vehicle, the method 600 proceeds to block 612, at which block 612 the headlamp controller 132 identifies weather conditions for the vehicle location.

At block 614, the headlamp controller 132 determines whether the weather conditions include precipitation, smoke, and/or any other particulates that potentially impede visibility in low light conditions. In response to the headlamp controller 132 determining that the weather conditions do not include precipitation and/or visibility reducing particles, the method 600 proceeds to block 616, where the headlamp controller 132 sets the high-beams 112 to the active mode (e.g., the headlamp controller 132 turns on the high-beams 112) at block 616. Otherwise, in response to the headlamp controller 132 determining that the weather condition includes precipitation and/or reduced visibility particles, the method 600 proceeds to block 618.

At block 618, the headlamp controller 132 determines whether there is a clear line of sight for the operator through the precipitation and/or air particles. In response to the headlamp controller 132 determining that a clear line of sight exists, the method 600 proceeds to block 620, at which block 620 the headlamp controller 132 sets the high-beam 112 to the active mode (e.g., the headlamp controller 132 turns on the high-beam 112). Further, at block 622, the headlamp controller 132 adjusts the high beam 112 to emit the high beam 304 in a direction toward a clear line of sight.

Returning to block 618, the method 600 proceeds to block 624 in response to the headlamp controller 132 determining that a clear line of sight is not present. At block 624, the headlamp controller 132 determines whether there is a cross wind with respect to the direction of travel of the vehicle 100. In response to the headlamp controller 132 determining that there is a side wind of precipitation and/or other airborne particles, the method 600 proceeds to block 620, at which block 620 the headlamp controller 132 sets the high-beam light 112 to the active mode (e.g., the headlamp controller 132 turns on the high-beam light 112). Further, at block 622, headlamp controller 132 adjusts the direction in which high beam 304 is emitted by high beam 112 based on the angle of incidence of precipitation and/or airborne particles with the direction corresponding to the crosswind.

Returning to block 624, the method 600 proceeds to block 626 in response to the headlamp controller 132 determining that no crosswind is present. For example, if the precipitation has a vertical flow and/or a flow parallel to the direction of travel of the vehicle 100, the headlight controller 132 determines that no crosswind is present. At block 626, the headlamp controller 132 sets the high-beam 112 to the inactive mode (e.g., the headlamp controller 132 turns off the high-beam 112).

In this application, the use of antisense conjunctions is intended to include conjunctions. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, references to "the" object or "an" and "an" object are also intended to mean one of a possible plurality of such objects. Furthermore, the conjunction "or" may be used to convey simultaneous features, rather than mutually exclusive alternatives. In other words, the conjunction "or" should be understood to include "and/or". The terms "comprise, include and include" are inclusive and have the same scope as "comprise, include and include", respectively. Additionally, as used herein, the term "module" refers to hardware having circuitry that provides communication, control, and/or monitoring capabilities. A "module" may also include firmware that executes on a circuit.

The embodiments described above, particularly any "preferred" embodiments, are possible examples of implementations, and are merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the technology described herein. All such modifications are intended to be included herein within the scope of this disclosure and protected by the following claims.

According to the present invention, there is provided a vehicle having a headlamp comprising a low beam and a high beam, a light sensor, a camera and a controller for setting the low beam to an active mode when the light sensor detects low ambient light, monitoring precipitation under the low ambient light via the camera, identifying an angle of incidence (AOI) between the precipitation and light emitted by the headlamp and controlling the high beam based on the AOI.

According to one embodiment, the controller is configured to monitor smoke in low ambient light via the camera and identify an AOI between the smoke and light emitted by the headlamp.

According to one embodiment, the controller utilizes image recognition to identify the AOI based on images captured by the camera.

According to one embodiment, to control the high beam based on AOI, the controller sets the low beam to an inactive mode in response to detecting a flow of precipitation perpendicular or parallel to the light emitted by the headlamps.

According to one embodiment, to control the high beam based on AOI, the controller will adjust the high beam to emit high beam in the direction of the precipitation flow stream corresponding to the crosswind.

According to one embodiment, the controller identifies a clear line of sight within the precipitation based on an image captured by the camera and causes the high beam to emit high beams in the direction of the clear line of sight.

According to one embodiment, the controller detects at least one of a nearby pedestrian and an oncoming vehicle based on at least one of the camera and the proximity sensor, and sets the proximity light to the inactive mode in response to detecting at least one of a nearby pedestrian and an oncoming vehicle.

According to one embodiment, the controller is for detecting a line of sight of a vehicle operator and controlling the high beam based on the line of sight of the vehicle operator.

According to one embodiment, the controller is configured to detect the line of sight via at least one of an interior camera, a seat position sensor, and a restraint control module.

According to one embodiment, each of the high beams comprises a plurality of LEDs, and the controller adjusts which of the plurality of LEDs is active to adjust the direction in which the high beams emit high beams.

According to one embodiment, each of the high beams comprises a rotatable frame, and the controller rotates the rotatable frames to adjust the direction in which the high beams emit the high beams.

According to the present invention, there is provided a vehicle having a headlamp including low and high headlamps, a communication module, and a controller that sets the low headlamps to an active mode in response to low ambient light detected via the communication module, monitors precipitation under the low ambient light via the communication module, identifies an angle of incidence (AOI) between the precipitation and light emitted by the headlamp, and controls the high headlamps based on the AOI.

According to one embodiment, the communication module comprises a dedicated short-range communication module.

According to one embodiment, the controller identifies an AOI between precipitation and light emitted by the headlamps based on the direction of travel and the wind direction.

According to one embodiment, the invention also features a GPS receiver that identifies a current vehicle location.

According to one embodiment, the communication module is configured to obtain weather conditions for a current vehicle location from a remote weather service.

According to one embodiment, the controller is to identify a predicted travel route based at least in part on a current vehicle location, and the communication module is to obtain weather conditions for the predicted travel route from a remote weather service.

According to one embodiment, to control the high beam based on AOI, the controller sets the low beam to an inactive mode in response to detecting a flow of precipitation perpendicular or parallel to the light emitted by the headlamps.

According to one embodiment, to control the high beam based on AOI, the controller will adjust the high beam to emit high beam in the direction of the precipitation flow stream corresponding to the crosswind.

According to the invention, a method comprises: detecting, via a light sensor, an ambient light level of a vehicle; setting a low beam of headlamps to an active mode when the light sensor detects low ambient light; monitoring, via a processor, precipitation in low ambient light; identifying, via a processor, an angle of incidence (AOI) between precipitation and light emitted by the headlamp; and controlling a low beam of headlamps based on the AOI.