IP Library Granted Patent US 12,347,313
Granted Patent B2
US 12,347,313 · App. 18/587,421 · Granted Jul 1, 2025

Vehicle to vehicle event notification system and method

Inventor: Peter Kulakov (Kharkov, UA)
Assignee: DISH Ukraine L.L.C.
G08G1/096741G08G1/093G08G1/09675G08G1/096775G08G1/096791H04W4/46
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,347,313
App. No.
18/587,421
Granted
Jul 1, 2025
Kind
B2
Abstract

A facility for providing vehicle to vehicle event notification for connected and/or unconnected vehicles is disclosed. The facility enables a vehicle to detect an occurrence of a vehicle status trigger event and identify information describing an event type. The facility determines a priority of the vehicle status event based at least in part on the type of the vehicle status event. When the vehicle status event is to be reported to at least one other vehicle, the facility enables the vehicle to generate a vehicle status event message that includes the priority of the vehicle status event and at least a portion of the information describing the type of the vehicle status event. The vehicle status event message is then transmitted/broadcasted to at least one other vehicle.

Claims (68)

1. A vehicle, in communication with a remote system for managing vehicle-to-vehicle communication of vehicle status events, the vehicle being configured to perform operations comprising:

receiving a vehicle status event message, wherein the vehicle status event message is generated by the remote system based on a vehicle status event relating to a status of a second vehicle that is connected to the vehicle in the remote system, and the status of the second vehicle is an application of brakes, change in speed, change in acceleration, change in driving lane, turning on/off of headlights, turning on/off of fog lights, turning on/off of wiper blades, fuel indicator, other car fluids indicator, or an operating parameter; and

notifying one or more non-connected vehicles of the vehicle status event.

2. The vehicle of claim 1 , wherein the vehicle status event message includes priority of the vehicle status event and information describing a type of the vehicle status event.

3. The vehicle of claim 2 , wherein the type of the vehicle status event is based on the status of the second vehicle.

4. The vehicle of claim 2 , wherein the type of the vehicle status event is based on a status of a third vehicle.

5. The vehicle of claim 2 , wherein the type of the vehicle status event is based on at least one of:

a condition of a roadway on which the second vehicle is present,

an obstacle or obstruction,

an environmental condition,

an emergency event,

or a combination thereof.

6. The vehicle of claim 5 , wherein the environmental condition describes poor traction due to a weather condition.

7. The vehicle of claim 2 , wherein the operations further comprise:

transmitting a response message to the vehicle status event message.

8. The vehicle of claim 2 , wherein the priority of the vehicle status event is based on one or more of the following:

the type of the vehicle status event,

an environmental factor,

a weather factor,

a history of event,

user history,

vehicle history,

vehicle health-status,

a default setting,

identity of the vehicle,

location of the vehicle,

distance between the vehicle and the second vehicle,

or any combination thereof.

9. The vehicle of claim 1 , wherein notifying the one or more non-connected vehicles of the vehicle status event comprises:

operating vehicle lights of the vehicle.

10. The vehicle of claim 9 , wherein operating the vehicle lights of the vehicle comprises:

flashing brake lights of the vehicle in a pattern.

11. The vehicle of claim 1 , wherein the remote system includes a mobile device associated with a driver or passenger of the vehicle or the second vehicle, or implemented in a distributed computing environment.

12. A method implemented on a vehicle that is in communication with a remote system for managing vehicle-to-vehicle communication of vehicle status events, the method comprising:

receiving a vehicle status event message, wherein the vehicle status event message is generated by the remote system based on a vehicle status event relating to a status of a second vehicle that is connected to the vehicle in the remote system, and the status of the second vehicle is an application of brakes, change in speed, change in acceleration, change in driving lane, turning on/off of headlights, turning on/off of fog lights, turning on/off of wiper blades, fuel indicator, other car fluids indicator, or an operating parameter; and

notifying one or more non-connected vehicles of the vehicle status event.

13. The method of claim 12 , wherein the vehicle status event message includes priority of the vehicle status event and information describing a type of the vehicle status event.

14. The method of claim 13 , wherein the type of the vehicle status event is based on at least one of:

the status of the second vehicle,

a condition of a roadway on which the second vehicle is present,

an obstacle or obstruction,

an environmental condition,

an emergency event,

or any combination thereof.

15. The method of claim 13 , wherein the priority of the vehicle status event is based on one or more of the following:

the type of the vehicle status event,

an environmental factor,

a weather factor,

a history of event,

user history,

vehicle history,

vehicle health-status,

a default setting,

identity of the vehicle,

location of the vehicle,

distance between the vehicle and the second vehicle,

or any combination thereof.

16. The method of claim 12 , further comprising:

operating vehicle lights of the vehicle.

17. The method of claim 16 , wherein operating the vehicle lights of the vehicle comprises:

flashing brake lights of the vehicle in a pattern.

18. One or more non-transitory computer-readable storage media whose contents are capable of causing a vehicle to perform a method, wherein the vehicle is in communication with a remote system for managing vehicle-to-vehicle communication of vehicle status events, the method comprising:

receiving a vehicle status event message, wherein the vehicle status event message is generated by the remote system based on a vehicle status event relating to a status of a second vehicle that is connected to the vehicle in the remote system, and the status of the second vehicle is an application of brakes, change in speed, change in acceleration, change in driving lane, turning on/off of headlights, turning on/off of fog lights, turning on/off of wiper blades, fuel indicator, other car fluids indicator, or an operating parameter; and

notifying one or more non-connected vehicles of the vehicle status event.

19. The one or more non-transitory computer-readable storage media of claim 18 , wherein notifying the one or more non-connected vehicles of the vehicle status event comprises:

operating vehicle lights of the vehicle.

20. The one or more non-transitory computer-readable storage media of claim 18 , wherein the method further comprises:

transmitting a response message to the vehicle status event message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 27, 2024
From: KULAKOV, PETER
To: DISH UKRAINE L.L.C.
Reel/Frame 066569/0084 →
Continuity (3)
Continuation 18153294 · Jan 11, 2023
Continuation 17259830
Related Publication 20240194066A1 · Jun 13, 2024
References Cited (20)
US 11562649B2 · Kulakov · 2023 [cited by examiner]
US 11915586B2 · Kulakov · 2024 [cited by examiner]
US 20050088318A1 · Liu · 2005 [cited by examiner]
US 20060097224A1 · Hanelt · 2006 [cited by examiner]
US 20110060496A1 · Nielsen et al. · 2011 [cited by applicant]
US 20110257869A1 · Kumar et al. · 2011 [cited by applicant]
US 20120003921A1 · Scopigno et al. · 2012 [cited by applicant]
US 20120249343A1 · Thomas · 2012 [cited by examiner]
US 20130279491A1 · Rubin · 2013 [cited by examiner]
US 20140310702A1 · Ricci et al. · 2014 [cited by applicant]
US 20150123778A1 · Konet · 2015 [cited by examiner]
US 20150183284A1 · Kim · 2015 [cited by examiner]
US 20150310742A1 · Albornoz · 2015 [cited by examiner]
US 20160097224A1 · Fernandez-Aguilera et al. · 2016 [cited by applicant]
US 20170316691A1 · Miller · 2017 [cited by examiner]
US 20170361835A1 · Tarte et al. · 2017 [cited by applicant]
US 20180326994A1 · Sakai · 2018 [cited by applicant]
US 20210312806A1 · Kulakov · 2021 [cited by applicant]
WO 2020013796A1 · 2020 [cited by applicant]
PCT/UA2018/000076 International Search Report and Written Opinion mailed Apr. 17, 2018, 14 pgs. total. [cited by applicant]