Traffic light indication system for a vehicle with suppressed notifications

Abstract

A vehicle includes a traffic light indication system (system) having one or more input devices to generate a state input signal associated with a traffic light state. The input devices also generate an override input signal associated with a hazardous driving condition. The system also includes a notification device to provide a traffic light notification to the user. The system also includes a computer having a processor and a non-transitory computer-readable storage medium (CRM) storing instructions. The processor is programmed to generate an actuation signal based on the state input signal. The processor is also programmed to inhibit generation of the actuation signal in response to the processor determining a predicted collision based on the state input signal and the override input signal. The notification device provides the traffic light notification to the user in response to the notification device receiving the actuation signal.

Description

Technical Field

[0001] This disclosure relates to a traffic light indication system that provides notifications of traffic light status associated with a vehicle, and more particularly, to a traffic light indication system that prohibits the provision of traffic light notifications so that users can focus their attention on dangerous driving situations. Background Technology

[0002] Traffic light indication systems for vehicles can have vehicle-to-infrastructure (V2I) connectivity to instruct users how to drive their vehicles based on traffic light status. For example, the system may include a notification device for providing notifications of traffic light status and associated instructions (e.g., a countdown of the amount of time a traffic light will remain in one color before changing to another, and associated instructions to operate the vehicle when the countdown expires; a warning to negligent drivers that the traffic light has changed color, and associated instructions to operate the vehicle immediately). However, the notification device can provide traffic light notifications when one or more dangerous driving situations may require the driver to refrain from driving according to associated instructions (e.g., the traffic light has turned green, but a pedestrian is blocking the vehicle's path on a crosswalk). Therefore, continuous notifications may cause user anxiety or annoyance, which in turn may lead to impulsive compliance with associated instructions. Furthermore, continuous notifications may increase the consumption of vehicle battery resources, processing resources, memory resources, time-domain resources, and / or frequency-domain resources.

[0003] Therefore, although existing traffic light systems have achieved their intended purpose, a new and improved traffic light system with suppression notification is needed to address these issues. Summary of the Invention

[0004] According to several aspects of this disclosure, a vehicle includes a traffic light indication system (the system) having one or more input devices for generating state input signals associated with traffic light states. The input devices also generate overriding input signals associated with dangerous driving conditions. The system further includes one or more notification devices for providing traffic light notifications to a user. The system also includes a computer having one or more processors electrically connected to the input devices and notification devices. The computer further includes a non-transitory computer-readable storage medium (CRM) storing instructions such that the processor is programmed to receive state input signals and overriding input signals from the input devices. The processor is also programmed to generate an actuation signal based on the state input signals. The processor is further programmed to determine a predicted collision with the vehicle in response to receiving the state input signals and overriding input signals from the input devices. The processor is also programmed to refrain the generation of the actuation signal in response to determining a predicted collision with the vehicle. In response to receiving the actuation signal from the processor, the notification device provides traffic light notifications to the user.

[0005] In one aspect, the input device includes a telematics module, and the override input signal includes vehicle-to-everything (V2X) messages associated with Personal Safety Messages (PS messages) transmitted from the telematics module to the processor. The PS messages are associated with the location of the pedestrian crossing, the location of the vulnerable road user (VRU) relative to the pedestrian crossing, the speed of the VRU, the heading of the VRU, and / or the status of pedestrian traffic lights.

[0006] In another aspect, the input device also includes an onboard objection detection device (OODD) that generates an override input signal, wherein the override input signal is associated with data indicating the position of the VRU relative to the vehicle, the heading of the VRU relative to the vehicle, and / or the rate of change of distance of the VRU relative to the vehicle.

[0007] In another aspect, OODD refers to short-range radar sensors, light detection and ranging sensors (LiDAR sensors), millimeter-wave radar sensors (MWR sensors), infrared cameras (IR cameras), and / or stereo vision cameras.

[0008] In another aspect, the input device also includes driver monitoring equipment for generating a override input signal, wherein the override input signal is associated with data indicating the direction of the user's gaze relative to the traffic light and / or VRU. In response to the processor determining, based on the override input signal, that the direction of the user's gaze is toward the traffic light and / or VRU, the processor determines a predicted collision with the vehicle.

[0009] In another aspect, the override input signal is correlated with the vehicle's speed. In response to the processor determining that the speed is below a speed threshold, the processor determines a predicted collision with the vehicle.

[0010] In another aspect, the overdrive input signal is correlated with changes in the brake pedal position. In response to the processor determining that the change in brake pedal position is below a brake pedal threshold, the processor determines a predicted collision with the vehicle.

[0011] In another aspect, the overdrive input signal is correlated with changes in the accelerator pedal position. In response to the processor determining that the change in the accelerator pedal position exceeds an accelerator pedal threshold, the processor determines a predicted collision with the vehicle.

[0012] In another aspect, the overdrive input signal is correlated with the rate of change of the steering wheel angle position. In response to the processor determining that the rate of change of the steering wheel angle position is below a steering rate threshold, the processor determines a predicted collision with the vehicle.

[0013] On the other hand, the override input signal is a V2X message associated with a road safety message (RS message) transmitted from the telematics module to the processor. The RS message is associated with the start position of the work zone, the end position of the work zone, lane closure, and / or the position of the worker.

[0014] On another front, OODD generates override input signals. These override input signals are associated with construction signs, construction buckets, and / or the position of workers relative to the vehicle, as well as the worker's heading relative to the vehicle.

[0015] In another aspect, the override input signal is a V2X message associated with vehicle messages transmitted from the telematics module to the processor. These vehicle messages are associated with the location, heading, speed, and acceleration of third-party vehicles, and / or with predicted collisions based on the heading and location of the third-party vehicles.

[0016] On another front, OODD generates a cancellation input signal. The cancellation input signal is associated with the position of a third-party vehicle relative to the vehicle, the heading of the third-party vehicle relative to the vehicle, the speed of the third-party vehicle relative to the vehicle, the acceleration of the third-party vehicle relative to the vehicle, the activation of the third-party vehicle and / or the vehicle's wiper equipment, the activation of the third-party vehicle and / or the vehicle's anti-lock braking system, and / or the predicted collision of the vehicle based on the heading and position of the third-party vehicle relative to the vehicle.

[0017] In another aspect, notification devices include augmented reality head-up display devices (ARHUD devices) and / or haptic steering wheels.

[0018] According to several aspects of this disclosure, a computer is provided for a traffic light indication system (system) for a vehicle. The system includes one or more input devices for generating state input signals associated with traffic light states. The input devices also generate override input signals associated with dangerous driving conditions. The system also includes one or more notification devices for providing traffic light notifications to a user. The computer includes one or more processors electrically connected to the input devices and the notification devices. The computer also includes a non-transitory computer-readable storage medium (CRM) storing instructions, such that the processor is programmed to receive state input signals and override input signals from the input devices. The processor is also programmed to generate an actuation signal based on the state input signals. The processor is further programmed to determine a predicted collision with a vehicle in response to receiving the state input signals and override input signals from the input devices. The processor is also programmed to disable the generation of the actuation signal in response to determining a predicted collision with a vehicle. In response to receiving the actuation signal from the processor, the notification device provides a traffic light notification to the user.

[0019] In one aspect, the overdrive input signal is a vehicle-to-everything (V2X) message associated with a Personal Safety Message (PS message) transmitted from the telematics module to the processor. The PS message is associated with the location of the pedestrian crossing, the position of the vulnerable road user (VRU) relative to the pedestrian crossing, the speed of the VRU, the heading of the VRU, and / or the status of the pedestrian signal light.

[0020] On the other hand, the overdrive input signal is associated with the position of the VRU relative to the vehicle, the heading of the VRU relative to the vehicle, and the rate of change of distance of the VRU relative to the vehicle.

[0021] According to several aspects of this disclosure, a method for operating a vehicle with a traffic light indication system is provided. The method includes generating a state input signal associated with a traffic light state using an input device. The method also includes generating a override input signal associated with a dangerous driving condition using the input device. The method further includes receiving the state input signal and the override input signal from the input device using a computer processor. The method also includes generating an actuation signal based on the state input signal using the processor. The method further includes providing a traffic light notification to a user using a notification device in response to receiving the actuation signal from the processor using a notification device. The method also includes determining a predicted collision with the vehicle using the processor in response to receiving the state input signal and the override input signal from the input device using the processor. The method further includes prohibiting the generation of the actuation signal using the processor in response to determining a predicted collision with the vehicle using the processor. The method also includes providing a traffic light notification to a user using a notification device in response to receiving the actuation signal from the processor using the notification device.

[0022] In one aspect, the method also includes transmitting a override input signal to the processor, in the form of a telematics module, as a vehicle-to-everything (V2X) message associated with a Personal Safety Message (PS message). The PS message is associated with the location of the pedestrian crossing, the location of the vulnerable road user (VRU) relative to the pedestrian crossing, the speed of the VRU, the heading of the VRU, and / or the status of the pedestrian signal light.

[0023] In another aspect, the method also includes using a telematics module to transmit V2X messages associated with vehicle messages to a processor. These vehicle messages are associated with the location, heading, speed, acceleration, and / or, based on the heading and location of the third-party vehicle, with predicted collisions of the vehicle.

[0024] Its application areas will become apparent from the description provided herein. It should be understood that the description and specific examples are intended for illustrative purposes only and are not intended to limit the scope of this disclosure. Attached Figure Description

[0025] The accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure in any way.

[0026] Figure 1 This is a schematic diagram of an example vehicle with a traffic light indication system with notification suppression, illustrating a traffic light indication system that provides traffic light status notifications.

[0027] Figure 2 yes Figure 1 A schematic diagram of an example vehicle illustrates how a system suppresses traffic light notifications in response to a system determination of a dangerous driving situation involving a pedestrian located in the vehicle's path.

[0028] Figure 3 yes Figure 1 A schematic diagram of an example vehicle illustrates how the system suppresses traffic light notifications in response to the system determining a dangerous driving situation in the form of a work area located in the vehicle's path.

[0029] Figure 4 yes Figure 1 A schematic diagram of an example vehicle illustrates how a system suppresses traffic light notifications in response to a dangerous driving situation of an emergency vehicle approaching the vehicle's path, as determined by the system.

[0030] Figure 5 yes Figure 1 A schematic diagram of an example vehicle illustrates how the system suppresses traffic light notifications in response to the system determining a dangerous driving situation in the form of another vehicle reversing within the vehicle's path.

[0031] Figure 6 yes Figure 1 A schematic diagram of an example vehicle illustrates how the system suppresses a traffic light notification in response to the system determining a dangerous driving situation in the form of another vehicle approaching the vehicle's path during inclement weather.

[0032] Figure 7 It is an operation Figure 1 A flowchart illustrating an example of the system's approach. Detailed Implementation

[0033] The following description is exemplary in nature and is not intended to limit this disclosure, application, or use.

[0034] This disclosure describes an example of a vehicle 100 having a traffic light indication system 102 (the system) that provides notification of the status of traffic lights 104 and suppresses traffic light notification in response to the system 102 determining a dangerous driving condition. As described in detail below, the system 102 includes a notification device 106 (e.g., an ARHUD 144, a haptic steering wheel 146, a driver information center (DIC), a speaker, any suitable human-machine interface (HMI), etc.) that provides traffic light notification to prompt a user (e.g., vehicle occupants, such as a driver and / or passenger, a remote operator, etc.) to manipulate or prepare to manipulate the vehicle 100 (e.g., a real-time countdown of the amount of time a traffic light remains in one color before changing to another, audio and / or haptic alerts indicating an impending change and / or a complete change from one color to another, etc.). In response to system 102 determining a dangerous driving situation (e.g., a vulnerable road user (VRU) is located or approaching the vehicle's path; a work area is located on the vehicle's path; another vehicle (such as an emergency vehicle (EV)) is located or approaching the vehicle's path; another vehicle is in the vehicle's path; another vehicle approaches the vehicle's path in slippery road conditions; fog density is above a predetermined fog threshold, etc.), notification device 106 prohibits the provision of traffic light notifications. Suppressing traffic light notifications allows users to focus their attention on the dangerous driving situation and take associated actions, which may contradict the instructions prompted by the traffic light notification. Therefore, suppressing traffic light notifications can prevent users from being distracted or disturbed by the system. Furthermore, suppressing traffic light notifications based on dangerous driving situations can result in reduced consumption of battery resources, processing resources, memory resources, and / or network resources (e.g., time domain resources and / or frequency domain resources) used to provide traffic light notifications.

[0035] refer to Figure 1A non-limiting example of a vehicle 100 equipped with a traffic light indication system 102 (the system) includes one or more input devices 108 (e.g., an onboard objection detection device 122 (OODD), a driver monitoring device 124 (DMD), an anti-lock braking system 138 (ABS), a traction control system 140 (TCS), a wiper device 152, etc.). Input devices 108 may include associated vehicle-to-everything (V2X) connectivity, vehicle-to-infrastructure (V2I) connectivity, vehicle-to-vehicle (V2V) connectivity, and / or onboard sensors for generating status input signals associated with the status of the traffic light 104. As described in detail below, system 102 provides a user with notification of the status of the traffic light 104 based on the status input signals. Input devices 108 may include a telematics module 110 wirelessly connected to a remote server 112 and / or one or more remote vehicles 114. The telematics module 110 may receive remote signals from the remote server 112 and / or one or more remote vehicles 114. Remote signals can be associated with SPaT messages (Signal Phase and Timing messages), which define the current intersection signal light phase, current signal state, and the current signal time until a change. Remote signals can also be associated with map messages that define the geometry of the associated intersection. The telematics module 110 can generate status input signals based on the remote signals.

[0036] refer to Figure 2Input device 108 can also generate a override input signal for suppressing traffic light notifications, as described in detail below. In a non-limiting example, the override input signal can be a vehicle-to-everything (V2X) message associated with a personal safety message (PS message) for vulnerable road users 116 (e.g., individuals located on or beside roads without protective rigid coverings for metal vehicles, such as pedestrians, road workers, individuals operating wheelchairs or other personal mobility devices (whether motorized or not), individuals operating electric scooters, individuals operating bicycles or other non-motorized vehicles, and individuals operating motorcycles, etc.). The PS message can be transmitted from telematics module 110 to processor 118, as described in detail below. The PS message can be associated with the position of crosswalk 120, the position of VRU 116 relative to crosswalk 120, the speed of VRU 116, the heading of VRU 116, and / or the status of pedestrian traffic lights, etc. Input device 108 may also include OODD 122 for generating an override input signal, wherein the override input signal is associated with data indicating the position of VRU 116 relative to vehicle 100, the heading of VRU 116 relative to vehicle 100, and / or the rate of change of distance of VRU relative to vehicle. Non-limiting examples of OODD 122 may include short-range radar sensors, light detection and ranging sensors (LiDAR sensors), millimeter-wave radar sensors (MWR sensors), infrared cameras (IR cameras), and stereo vision cameras, etc.

[0037] Input device 108 may also include driver monitoring device 124 (DMD) for generating override input signals, wherein the override input signals are associated with data indicating the direction of the user's gaze relative to traffic lights and / or VRU 116. The override input signals may also be associated with the speed of vehicle 100, changes in the position of the brake pedal of vehicle 100, changes in the position of the accelerator pedal of vehicle 100, the rate of change of the steering wheel angle position of vehicle 100, etc.

[0038] refer to Figure 3Input device 108 can also generate override input signals, which are V2X messages in the form of road safety messages (RS messages) transmitted from telematics module 110 to processor 118. RS messages can be associated with data indicating the presence of a work area (e.g., one or more construction cones, traffic cones, roadside flares, roadblocks, construction equipment, multi-purpose vehicles, emergency vehicles, one or more persons within the work area, such as construction workers, utility technicians, first responders, etc.). More specifically, RS messages can be associated with work area start position 126, work area end position 128, lane closure 130, and / or the position of one or more workers 132. OODD 122 can generate override input signals, which are associated with data indicating the position of construction sign 134, construction cone 136, the position of worker 132 relative to vehicle 100, and / or the heading of worker 132 relative to vehicle 100.

[0039] refer to Figures 4 to 6 In another non-limiting example, input device 108 may generate a override input signal, wherein the override input signal is a V2X message associated with vehicle messages transmitted from telematics module 110 to processor 118. The vehicle messages may be associated with the position of third-party vehicle 100, the heading of third-party vehicle 100, the speed of third-party vehicle 100, the acceleration of third-party vehicle 100, and a predicted collision of vehicle 100 based on the heading and position of third-party vehicle 100. OODD 122 can generate an override input signal, wherein the override input signal is associated with indications of the position of the third-party vehicle 100 relative to vehicle 100, the heading of the third-party vehicle 100 relative to vehicle 100, the speed of the third-party vehicle 100 relative to vehicle 100, the acceleration of the third-party vehicle 100 relative to vehicle 100, the activation of the wiper device of the third-party vehicle and / or vehicle 100, the activation of the anti-lock braking system 138 (ABS) of the third-party vehicle 100 and / or vehicle 100, the activation of the traction control system 140 (TCS) of the third-party vehicle and / or vehicle 100, and / or a predicted collision with vehicle 100 based on the heading and position of the third-party vehicle 100 relative to vehicle 100.

[0040] like Figure 4 As shown, third-party vehicle 100 can be an emergency vehicle 142 (EV) approaching the path of vehicle 100. A status input signal can be associated with data instructing traffic light 104 to display a green light for vehicle 100. A override input signal can be associated with data indicating that EV 142 is traveling at a measured speed and proceeding toward the path of vehicle 100, wherein emergency sirens and hazard lights are activated.

[0041] like Figure 5As shown, third-party vehicle 100 can be one or more remote vehicles 114 (RVs) located within the path of vehicle 100. Status input signals can be associated with data instructing traffic lights 104 to display a green light for vehicle 100. Override input signals can be RV messages associated with data instructing RV 114 to overflow from a downstream intersection located at or near the path of vehicle 100 (e.g., in heavily congested traffic).

[0042] like Figure 6 As shown, third-party vehicle 100 can be a remote vehicle 100' moving toward the path of vehicle 100. Status input signals can be associated with data instructing traffic light 104 to display a green light for vehicle 100. Override input signals can be associated with data instructing RV 114' and / or the wiper equipment of vehicle 100 to be activated, ambient temperature, and / or the speed of RV' and / or vehicle 100.

[0043] System 102 also includes a notification device 106 for providing traffic light notifications to a user. Notification device 106 may include an augmented reality head-up display 144 (ARHUD) for displaying the traffic light notification. For example, ARHUD 144 may display a real-time countdown of the amount of time a traffic light will remain in one color before changing to another (e.g., a real-time countdown may show that the traffic light will remain green for 15 seconds before changing to amber). The countdown can help the user determine whether the vehicle can proceed through the green light based on the distance D from the traffic light 104 and the mass of the vehicle 100, while maintaining or increasing the current speed of the vehicle 100. Alternatively, the countdown can help the user determine before the countdown expires that the vehicle 100 cannot proceed through the green light, allowing the user to apply the brakes to avoid running a red light. Notification device 106 may also include a haptic steering wheel 146 for providing haptic alerts to indicate to the user that a color change is imminent and / or that a change from one color to another has been completed. For example, the haptic steering wheel 146 can provide a haptic alert when the traffic light changes from red to green, the speed of vehicle 100 remains at zero, and / or system 102 does not detect RV 114 in front of the main vehicle 100. In other non-limiting examples, the notification device 106 may be a speaker that provides audible chimes, voice commands, etc.

[0044] System 102 also includes a computer 148 having one or more processors 118 electrically connected to the input device and notification device 106. Computer 148 also includes a non-transitory computer-readable storage medium 150 (CRM) storing instructions such that processor 118 is programmed to receive status input signals and override input signals from input device 108. In response to the processor wirelessly receiving the status input signals from a remote server 112 controlling traffic light 104, processor 118 can determine the current state of traffic light 104 and the amount of time traffic light 104 will remain in one color before changing to another color.

[0045] Processor 118 is also programmed to generate an actuation signal based on a status input signal. In response to receiving the actuation signal from processor 118, notification device 106 provides a traffic light notification to the user. Figure 1 In a non-limiting example, the ARHUD144 can display a real-time countdown of the amount of time a traffic light remains in one color before changing to another.

[0046] The processor 118 is also programmed to determine a predicted collision with the vehicle 100 in response to receiving a status input signal from the remote server 112 via the telematics module 110. In response to receiving a override input signal from the input device 108, the processor 118 further determines the predicted collision with the vehicle 100. Based on the override input signal, the processor 118 can determine that: the speed is below a speed threshold; the change in brake pedal position is below a brake pedal threshold; the change in accelerator pedal position is above an accelerator pedal threshold; and / or the rate of change of the steering wheel angle position is below a steering rate threshold, etc.

[0047] like Figure 2 As shown in a non-limiting example, processor 118 may determine a predicted collision between vehicle 100 and VRU 116 in response to processor 118 receiving state input signals (e.g., associated with data indicating that a traffic light is green to prompt a user to drive a vehicle along the path) and override input signals (e.g., associated with data indicating the position of crosswalk 120, the position of the VRU relative to crosswalk 120, the speed of the VRU, the heading of the VRU, and / or the status of pedestrian traffic lights, etc.). Processor 118 may also determine a predicted collision between vehicle 100 and VRU 116 in response to processor 118 receiving override input signals (e.g., associated with data indicating the position of the VRU relative to vehicle 100, the heading of the VRU relative to vehicle 100, and / or the rate of change of distance of the VRU relative to the vehicle, etc.) from OODD 122 (e.g., a short-range radar sensor, LiDAR sensor, MWR sensor, IR camera, stereo vision camera, etc.).

[0048] The processor 118 can also determine a predicted collision with the vehicle 100 in response to receiving a override input signal from the DMD 124. The override input signal may be associated with data indicating that the user is operating the vehicle to intentionally ignore traffic light conditions in order to avoid a predicted collision (e.g., the user's gaze is directed at an override road condition; the speed of the vehicle 100 is associated with a braking distance threshold that is less than the distance between the vehicle and the main road condition; the brake pedal position is changed to apply increased braking force; the accelerator pedal position is changed to reduce propulsion; and / or the rate of change of the steering wheel angle position is increased to avoid override road conditions, etc.).

[0049] like Figure 3 As shown in a non-limiting example, processor 118 may determine a predicted collision between vehicle 100 and lane closure 130 in response to receiving a status input signal (e.g., data associated with a traffic light indicating a green light to prompt a user to drive vehicle 100 along a path) and a override input signal. The override input signal may be a V2X message in the form of an RS message associated with data indicating the presence of lane closure 130 (e.g., one or more construction cones, traffic cones, roadside flares, roadblocks, construction equipment, multi-purpose vehicles, emergency vehicles, one or more persons within the work area, such as construction workers, utility technicians, first responders, etc.). More specifically, the RS message may be associated with the work area start position 126, work area end position 128, lane closure 130, and / or the position of one or more workers 132, etc. OODD 122 may generate the override input signal, which is associated with data indicating the position of construction sign 134, construction cone 136, the position of worker 132 relative to vehicle 100, and / or the heading of worker 132 relative to vehicle 100, etc.

[0050] like Figure 4 As shown in a non-limiting example, in response to receiving a status input signal and a override input signal, processor 118 can determine a predicted collision between vehicle 100 and EV 142. The override input signal can be a V2X message in the form of an EV message associated with data indicating that EV 142 is approaching vehicle 100. The override input signal can also be associated with data indicating that EV 142 is traveling along a path where emergency sirens and hazard lights are activated and it is moving toward vehicle 100 at a measured speed, such that the EV cannot stop before colliding with vehicle 100.

[0051] like Figure 5As shown in a non-limiting example, processor 118 may determine a predicted collision between vehicle 100 and a plurality of RVs 114 located on the path of vehicle 100 in response to receiving a status input signal (e.g., associated with data indicating that a traffic light is green to prompt a user to drive a vehicle along a path) and a override input signal (e.g., RV messages associated with data indicating that RV 114 overflows from a downstream intersection on or near the path of vehicle 100 (e.g., in heavy traffic congestion, etc.)).

[0052] like Figure 6 As shown in a non-limiting example, processor 118 may determine a predicted collision between vehicle 100 and RV 114 approaching the path of vehicle 100 in response to receiving state input signals (e.g., data associated with indicating that a traffic light displays a green light to prompt a user to drive the vehicle along the path) and override input signals (e.g., data associated with indicating that the wiper device 152 of RV 114' and / or vehicle 100 is activated, the ambient temperature is below freezing, and / or the speed of RV' and / or vehicle 100 is associated with a braking distance greater than the distance from one of RV 114' and vehicle 100 to the predicted collision location).

[0053] Processor 118 is also programmed to disable the generation of actuation signals in response to processor 118 determining a predicted collision with vehicle 100. Therefore, notification device 106 does not provide traffic light notifications, allowing the user to focus their attention on dangerous driving situations (e.g., a predicted collision). Suppressed notifications also result in reduced consumption of user device resources (e.g., battery resources, processing resources, and / or memory resources) and / or network resources (e.g., time-domain resources and / or frequency-domain resources) used to maintain the countdown and notifications.

[0054] In another non-limiting example, processor 118 may also be programmed to generate a warning signal in response to processor 118 determining a predicted collision with vehicle 100. Notification device 106 (e.g., ARHUD 144) can provide hazard notification (e.g., Figure 2 "VRU" Figure 3 "Work area" Figure 4 The "arrival" Figure 5 "Traffic congestion", Figure 6 (e.g., the "arrival" of a vehicle) to instruct users to focus their attention on dangerous driving situations.

[0055] refer to Figure 7 It provides a way to operate Figure 1 Method 200 of system 102. Method 200 begins at block 202 and uses one or more input devices 108 to generate a state input signal associated with the state of traffic light 104.

[0056] At box 204, method 200 also includes using one or more input devices to generate an overdrive input signal associated with a dangerous driving condition.

[0057] At block 206, method 200 also includes receiving status input signals and override input signals from associated input device 108 using processor 118 of computer 148.

[0058] Method 200 also includes using processor 118 to determine a predicted collision with vehicle 100 based on state input signals and override input signals. More specifically, in this non-limiting example, this can be accomplished via multiple boxes (e.g., boxes 208-212 and 216-230), where processor 118 compares measured data with thresholds. The measured data can be associated with vehicle 100, user, VRU, lane closure 130, EV 142, RV 114, 114', and weather-related vehicle components (e.g., ABS 138, TCS 140, wiper device 152, etc.).

[0059] At block 208, method 200 further includes using processor 118 to compare the position of pedestrian crossing 120 with the path of vehicle 100 predicted by processor 118 based on input signals. In response to processor 118 determining that pedestrian crossing 120 is located within the predicted path of vehicle 100, method 200 proceeds to block 210. In response to processor 118 determining that pedestrian crossing 120 is not located within the predicted path of vehicle 100, method 200 proceeds to block 220.

[0060] At block 210, the method further includes using processor 118 to compare the position of pedestrian crossing 120 with the position of VRU 116. In response to processor 118 determining that VRU 116 is within a predetermined distance of the intersection between pedestrian crossing 120 and the predicted path of vehicle 100, method 200 proceeds to block 212. In response to processor 118 determining that VRU 116 is not within the predetermined distance of the intersection between pedestrian crossing 120 and the predicted path of vehicle 100, method 200 proceeds to block 216.

[0061] At block 212, method 200 further includes using processor 118 to compare the speed of VRU 116 with a VRU speed threshold. In response to processor 118 determining that the speed of VRU 116 is below an escape speed threshold (e.g., where the VRU is traveling at a speed that would cause a vehicle to collide with the VRU), method 200 proceeds to block 214. In response to processor 118 determining that the speed of VRU 116 is above an escape speed threshold (e.g., where the VRU is traveling at a speed that would cause a vehicle to miss the VRU), method 200 proceeds to block 220.

[0062] At box 214, method 200 further includes using processor 118 to determine a predicted collision with the vehicle (e.g., a collision between vehicle 100 and VRU 116) and using processor 118 to prevent the generation of an actuation signal. In other non-limiting examples, the method may also include using processor 118 to generate a warning signal such that notification device 106 can provide a dangerous driving notification to a user (e.g., an ARHUD 144 display). Figure 2 "VRU" Figure 3 "Work area" Figure 4 The "arrival" Figure 5 "Traffic congestion", Figure 6 (such as the "arrival" of something).

[0063] At block 216, method 200 further includes using processor 118 to compare the heading of VRU 116 with the location of the intersection between pedestrian crossing 120 and the predicted path of vehicle 100. In response to processor 118 determining that VRU 116 is proceeding toward the intersection between pedestrian crossing 120 and the predicted path of vehicle 100, method 200 proceeds to block 218. In response to processor 118 determining that VRU 116 is not proceeding toward the intersection between pedestrian crossing 120 and the predicted path of vehicle 100, method 200 proceeds to block 220.

[0064] At box 218, method 200 further includes using processor 118 to compare the speed of VRU 116 with the distance between VRU 116 and the predicted path of vehicle 100. In response to processor 118 determining that the VRU and vehicle will intercept each other based on the speed of VRU 116, the speed of vehicle 100, the distance between VRU 116 and the predicted collision point, and the distance between vehicle 100 and the predicted collision point, method 200 proceeds to box 214. In response to processor 118 determining that the VRU and vehicle will not intercept each other, method 200 proceeds to box 220.

[0065] At box 220, method 200 further includes comparing the predicted path of vehicle 100 with the positions of work area start position 126, work area end position 128, lane closure 130, and / or one or more workers 132. Method 200 proceeds to box 214, where notification device 106 disables traffic light notification in response to processor 118 determining that the predicted path of vehicle 100 intersects with any part of lane closure 130 and / or one or more workers 132. In response to processor 118 determining that the predicted path of vehicle 100 does not intersect with any part of lane closure 130 and / or one or more workers 132, method 200 proceeds to box 222.

[0066] At block 222, method 200 further includes using processor 118 to compare the emergency siren and hazard lights of EV 142 with predetermined states. Method 200 also includes comparing the heading of EV 142 with the predicted path of vehicle 100. In response to processor 118 determining that EV 142 is proceeding toward the predicted path of vehicle 100, wherein the emergency siren and hazard lights are activated, method 200 proceeds to block 224. In response to processor 118 determining that EV 142 is not proceeding toward the predicted path of vehicle 100 and / or the emergency siren and hazard lights are not activated, method 200 proceeds to block 226.

[0067] At box 224, method 200 further includes using processor 118 to compare the speed of EV 142 with the distance between EV 142 and the predicted path of vehicle 100. Method 200 proceeds to box 214, where notification device 106, in response to processor 118 determining that EV 142 and vehicle 100 will intercept each other based on the speed of EV 142, the speed of vehicle 100, the distance between EV 142 and the predicted collision point, and the distance between vehicle 100 and the predicted collision point, disables the provision of traffic light notification. In response to processor 118 determining that EV 142 and vehicle 100 will not intercept each other, method 200 proceeds to box 226.

[0068] At block 226, method 200 further includes using processor 118 to compare the position of RV 114 with the predicted path of vehicle 100. Method 200 also includes using processor 118 to compare the position of vehicle 100 relative to the predicted collision point. Method 200 further includes using processor 118 to compare the speed of vehicle 100 with a vehicle speed threshold. Method 200 proceeds to block 214, where notifying device 106, in response to processor 118 determining that RV 114 is positioned within a predetermined distance from the predicted path of vehicle 100, vehicle 100 is positioned within a predetermined distance from the predicted collision point, and / or vehicle 100 is traveling at a speed exceeding the vehicle speed threshold, prohibits the provision of traffic light notification. In response to processor 118 determining that RV 114 is not positioned within a predetermined distance from the predicted path of vehicle 100, vehicle 100 is not positioned within a predetermined distance from the predicted collision point, and / or vehicle 100 is not traveling at a speed exceeding the vehicle speed threshold, method 200 proceeds to block 228.

[0069] At block 228, method 200 further includes using processor 118 to compare the speed of RV 114 with the distance between RV 114 and the predicted path of vehicle 100. Method 200 proceeds to block 214, where notification device 106, in response to processor 118 determining that the associated RV 114 and vehicle 100 will intercept each other based on the speed of RV 114, the speed of vehicle 100, the distance between RV 114 and the predicted collision point, and the distance between vehicle 100 and the predicted collision point, disables the provision of traffic light notification. In response to processor 118 determining that the VRU and vehicle will not intercept each other, method 200 proceeds to block 230.

[0070] At block 230, method 200 further includes using processor 118 to compare the ambient temperature with the freezing temperature. Method 200 also includes using processor 118 to compare the wiper device 152 of RV 114 and / or vehicle 100 with a predetermined wiper state. Method 200 further includes using processor 118 to compare ABS 138 with a predetermined ABS state. Method 200 further includes using processor 118 to compare TCS 140 of RV 114 and / or vehicle 100 with a predetermined traction control state. Method 200 proceeds to block 214, where notification device 106 disables traffic light notification in response to processor 118 determining that wiper device 152 is activated, the ambient temperature is below the freezing temperature, ABS 138 is activated, TCS 140 is activated, etc. In response to processor 118 determining that wiper device 152 is not activated, ambient temperature is not lower than freezing temperature, ABS 138 is not activated, TCS 140 is not activated, etc., method 200 proceeds to box 232.

[0071] At block 232, the method further includes using the processor to generate an actuation signal based on the state input signal and, in response to receiving the actuation signal from the processor 118, using the notification device 106 to provide a traffic light notification (e.g., as...). Figure 1 As shown, this refers to the "15 seconds" before the light changes from green to red.

[0072] Computers and computing devices generally include computer-executable instructions, which can be executed by one or more computing devices (such as those listed above). Computer-executable instructions can be compiled or interpreted from computer programs created using a variety of programming languages ​​and / or technologies, including but not limited to JAVA, C, C++, MATLAB, SIMULINK, STATEFLOW, VISUALBASIC, JAVASCRIPT, PERL, HTML, TENSORFLOW, PYTORCH, KERAS, etc., individually or in combination. Some of these applications can be compiled and executed on virtual machines (such as the Java Virtual Machine, Dalvik Virtual Machine, etc.). Generally, a processor (e.g., a microprocessor) receives instructions from memory, computer-readable media, etc., and executes those instructions, thereby performing one or more processes, including one or more processes described herein. These instructions and other data can be stored and transferred using a variety of computer-readable media. A file in a computing device is generally a collection of data stored on computer-readable media (such as storage media, random access memory, etc.).

[0073] Processor 130 may be communicatively coupled to one or more local processors (e.g., included in electronic processor units (ECUs) within vehicle 100) via, for example, a vehicle communication module, for monitoring and / or controlling various vehicle components. Processor 130 is generally arranged to communicate with the vehicle communication module via internal wired and / or wireless networks (e.g., buses within vehicle 100, such as controller area networks (CAN), and / or other wired and / or wireless mechanisms)). Via the vehicle communication module, processor 130 can transmit messages to and / or receive messages from various devices within vehicle 100, such as vehicle sensors, actuators, vehicle components, human-machine interfaces (HMIs), etc. Alternatively or additionally, where the processor includes multiple devices, the vehicle communication network may be used for communication between devices represented as computers in this disclosure. Furthermore, various processors and / or vehicle sensors may provide data to the computer. The processor may receive and analyze data from sensors substantially continuously and / or periodically. In addition, object classification or recognition technologies can be used in processors that use data from, for example, LiDAR sensors, camera sensors, etc., to identify lane markings, object types (e.g., vehicles, people, rocks, potholes, bicycles, motorcycles, etc.), and the physical characteristics of objects.

[0074] Memory can include computer-readable media (also known as processor-readable media), which includes any non-transitory (e.g., tangible) medium involved in providing data (e.g., instructions) that can be read by a computer (e.g., by the computer's processor). Such media can take many forms, including but not limited to non-volatile and volatile media. Non-volatile media can include, for example, optical discs or magnetic disks, and other persistent storage. Volatile media can include, for example, dynamic random access memory (DRAM), which typically constitutes main memory. Such instructions can be transmitted via one or more transmission media, including coaxial cables, copper wires, and optical fibers, including wires containing a system bus coupled to the ECU processor. Common forms of computer-readable media include, for example, floppy disks, hard disks, magnetic tape, any other magnetic media, CD-ROMs, DVDs, any other optical media, punched cards, paper tape, any other physical media with a perforated pattern, RAM, PROM, EPROM, flash EEPROM, any other memory chip or cassette tape, or any other computer-readable medium.

[0075] The databases, data repositories, or other data stores described herein can include various mechanisms for storing, accessing, and retrieving a wide range of data, including hierarchical databases, a set of files in a file system, application databases in proprietary formats, relational database management systems (RDBMS), and so on. Each such data store is generally contained on a computing device employing a computer operating system such as one of those described above and is accessed via a network in any one or more of a variety of ways. File systems can be accessed from a computer operating system and can include files stored in various formats. In addition to languages ​​used for creating, storing, editing, and executing stored procedures, RDBMS generally employs a structured query language (SQL), such as the PL / SQL language mentioned above.

[0076] In some examples, system elements may be implemented as computer-readable instructions (e.g., software) on one or more computing devices (e.g., servers, personal computers, etc.) and stored on an associated computer-readable medium (e.g., disks, storage, etc.). A computer program product may include such instructions stored on a computer-readable medium for performing the functions described herein.

[0077] Regarding the media, processes, systems, methods, trial-and-error methods, etc., described herein, it should be understood that although the steps of these processes are described as occurring according to an ordered sequence, these processes can be practiced with the described steps performed in a different order than that described herein. It should also be understood that some steps may be performed simultaneously, other steps may be added, or some steps described herein may be omitted. In other words, the process descriptions herein are provided for the purpose of illustrating certain embodiments and should not be construed as limiting the claims in any way.

[0078] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. Many embodiments and applications, in addition to the examples provided, will be apparent to those skilled in the art upon reading the above description. The scope of the invention should not be determined by reference to the above description, but rather by reference to the appended claims and the full scope of their equivalents. Future developments are anticipated and intended in the field discussed herein, and the disclosed systems and methods will be incorporated into such future embodiments. In summary, it should be understood that modifications and variations are possible with respect to the invention, and it is limited only by the appended claims.

[0079] All terms used in the claims are intended to give the simple and common meaning as understood by those skilled in the art, unless otherwise expressly indicated herein. In particular, the use of singular articles such as “a,” “the,” “the,” etc., should be understood to enumerate one or more of the indicated elements, unless the claims enumerate an express limitation to the contrary.

[0080] The description in this disclosure is merely exemplary in nature and variations are intended to remain within the scope of this disclosure without departing from its spirit and scope. Such changes should not be considered as departing from the spirit and scope of this disclosure.

Claims

1. A vehicle comprising: Traffic light indication system, the traffic light indication system comprising: At least one input device is configured to generate a status input signal associated with a traffic light status, and the at least one input device is further configured to generate an override input signal associated with a dangerous driving condition; At least one notification device for providing traffic light notifications to users; and A computer, the computer including at least one processor electrically connected to the at least one input device and the at least one notification device, and the computer further including a non-transitory computer-readable storage medium (CRM) storing instructions, such that the at least one processor is programmed to: Receive the status input signal and the override input signal from the at least one input device; An actuation signal is generated based on the state input signal; A predicted collision with the vehicle is determined based on the state input signal and the override input signal; and In response to the at least one processor determining the predicted collision with the vehicle, the generation of the actuation signal is prohibited; and In response to at least one notification device receiving the actuation signal from the at least one processor, the at least one notification device provides the traffic light notification to the user; The at least one input device includes a telematics module, and the overdrive input signal includes a vehicle-to-everything (V2X) message associated with a personal security PS message transmitted from the telematics module to the at least one processor, wherein the PS message is associated with at least one of the following: Location of pedestrian crossings; The position of the vulnerable road user (VRU) relative to the pedestrian crossing; The speed of the VRU; The VRU's heading; and Pedestrian traffic light status.

2. The vehicle of claim 1, wherein the at least one input device further comprises an on-board objection detection device (OODD) that generates the overdrive input signal, wherein the overdrive input signal is associated with data indicating at least one of the following: The position of the VRU relative to the vehicle; The VRU's heading relative to the vehicle; and The rate of change of distance of the VRU relative to the vehicle.

3. The vehicle of claim 2, wherein the OODD comprises at least one of a short-range radar sensor, a light detection and ranging LiDAR sensor, a millimeter-wave radar MWR sensor, an infrared IR camera, and a stereo vision camera.

4. The vehicle of claim 2, wherein the at least one input device further comprises a driver monitoring device for generating the override input signal, wherein the override input signal is associated with data indicating the direction of a user's gaze relative to at least one of the traffic light and the VRU, and the at least one processor is configured to disable the generation of the actuation signal in response to the at least one processor determining, based on the override input signal, that the direction of the user's gaze is toward at least one of the traffic light and the VRU.

5. The vehicle of claim 4, wherein the overdrive input signal is associated with the speed of the vehicle, wherein the at least one processor determines the predicted collision with the vehicle in response to the at least one processor determining that the speed is below a speed threshold.

6. The vehicle of claim 4, wherein the overdrive input signal is associated with a change in brake pedal position, wherein the at least one processor determines the predicted collision with the vehicle in response to the at least one processor determining that the change in brake pedal position is below a brake pedal threshold.

7. The vehicle of claim 4, wherein the overdrive input signal is associated with a change in accelerator pedal position, wherein the at least one processor determines the predicted collision with the vehicle in response to the at least one processor determining that the change in accelerator pedal position is above an accelerator pedal threshold.

8. The vehicle of claim 4, wherein the overdrive input signal is associated with the rate of change of the steering wheel angle position, wherein the at least one processor determines the predicted collision with the vehicle in response to the at least one processor determining that the rate of change of the steering wheel angle position is below a steering rate threshold.

9. The vehicle of claim 4, wherein the overdrive input signal includes the V2X message associated with a road safety RS message transmitted from the telematics module to the at least one processor, wherein the RS message is associated with at least one of: Work area start position; End point of the work area; Lane closure; and The worker's position.

Images