IP Library Granted Patent US 12,431,017
Granted Patent B2
US 12,431,017 · App. 18/109,012 · Granted Sep 30, 2025

Electrical data processing system for monitoring or affecting movement of a vehicle using a traffic device

Inventors: Regina Madigan (Mountain View, CA); Timothy W. Gibson (Barrington, IL); Howard Hayes (Glencoe, IL); Surender Kumar (Palatine, IL)
Assignee: Allstate Insurance Company
G08G1/095B60W40/09G08B25/016G08G1/005G08G1/0112G08G1/0116G08G1/012G08G1/0129G08G1/0133G08G1/0145G08G1/04G08G1/065G08G1/07G08G1/08G08G1/0965G08G1/096716G08G1/096725G08G1/096741G08G1/096775G08G1/096822G08G1/096838G08G1/096844G08G1/164G08G1/205H04W4/02G08B21/06
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,431,017
App. No.
18/109,012
Granted
Sep 30, 2025
Kind
B2
Abstract

Systems and methods are disclosed for monitoring or affecting movement of a vehicle using a traffic device. An event data source may have a processor and/or a transceiver. The event data source may transmit, via the transceiver and to a vehicle and infrastructure computing device, information indicative of an event affecting a portion of road. The vehicle and infrastructure computing device may comprise a vehicle and infrastructure control computer. The vehicle and infrastructure computing device may receive, from the event data source, the information indicative of the event affecting the portion of road. The computing device may determine one or more traffic devices associated with the portion of road and configured to control traffic for the portion of road. Based on the information indicative of the event affecting the portion of road, the computing device may send, to the one or more traffic devices associated with the portion of road, instructions to change one or more characteristics of the one or more traffic devices.

Claims (53)

1. A system comprising

a first computing device configured to:

send, via a transceiver, data indicative of one or more traffic conditions associated with an intersection of one or more roads, the data deriving from a traffic device fixed proximate to the intersection; and

a second computing device configured to:

receive, from the first computing device, the data indicative of the one or more traffic conditions associated with the intersection;

calculate, based on the data, a risk score for the intersection;

determine, based on the risk score, a modified operating condition;

determine one or more vehicles within a predetermined distance of the intersection; and

transmit, to one or more computing device associated with the one or more vehicles, data associated with the modified operating condition,

wherein the modified operating condition is at least one of:

a recommendation regarding a driving action to be taken by one of the one or more vehicles, the recommendation being based on an intersection path risk map that is generated based on the risk score;

an instruction to turn right at the intersection, turn left at the intersection, go straight at the intersection, or execute a U-turn before the intersection;

an indicia received at the one or more vehicles to not to drive through the intersection and the modified operating condition includes an instruction to increase an insurance premium in response the one or more vehicles drive through the intersection after receiving the indicia; or

an instruction that the one or more vehicles change a driving route to avoid the intersection.

2. The system of claim 1 , wherein the risk score for the intersection is calculated based on one or more factors selected from the group consisting of a complexity of the intersection, a number of accidents historically occurring at the intersection, weather at the intersection, and a degree of traffic congestion at the intersection.

3. The system of claim 1 , wherein the second computing device configured to:

determine whether the one or more vehicles are autonomous vehicles and whether the intersection does not permit the autonomous vehicles, thereby generating determinations regarding the autonomous vehicles, and

calculate the risk score for the intersection based on the determinations regarding the autonomous vehicles.

4. The system of claim 3 , wherein, when the determinations regarding the autonomous vehicles is that the one or more vehicles are autonomous vehicles and the intersection does not permit the autonomous vehicles, the modified operating condition comprises an instruction to deactivate autonomous-vehicle features while traversing the intersection.

5. A computing device comprising:

a transceiver;

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, configure the computing device to:

receive, from a second computing device, data indicative of one or more traffic conditions associated with an intersection of one or more roads, the data deriving from a traffic device fixed proximate to the intersection;

calculate, based on the data, a risk score for the intersection;

determine, based on the risk score, a modified operating condition;

determine one or more vehicles within a predetermined distance of the intersection; and

transmit, to one or more computing devices associated with the one or more vehicles, data associated with the modified operating condition,

wherein the modified operating condition is at least one of:

a recommendation regarding a driving action to be taken by one of the one or more vehicles, the recommendation being based on an intersection path risk map that is generated based on the risk score;

an instruction to turn right at the intersection, turn left at the intersection, go straight at the intersection, or execute a U-turn before the intersection;

an indicia received at the one or more vehicles to not to drive through the intersection and the modified operating condition includes an instruction to increase an insurance premium in response the one or more vehicles drive through the intersection after receiving the indicia; or

an instruction that the one or more vehicles change a driving route to avoid the intersection.

6. The computing device of claim 5 , wherein the risk score for the intersection is calculated based on one or more factors selected from the group consisting of a complexity of the intersection, a number of accidents historically occurring at the intersection, weather at the intersection, and a degree of traffic congestion at the intersection.

7. The computing device of claim 5 , wherein the second computing device configured to:

determine whether the one or more vehicles are autonomous vehicles and whether the intersection does not permit the autonomous vehicles, thereby generating determinations regarding the autonomous vehicles, and

calculate the risk score for the intersection based on the determinations regarding the autonomous vehicles.

8. The computing device of claim 7 , wherein, when the determinations regarding the autonomous vehicles is that the one or more vehicles are autonomous vehicles and the intersection does not permit the autonomous vehicles, the modified operating condition comprises an instruction to deactivate autonomous-vehicle features while traversing the intersection.

9. A method comprising:

receiving, at a second computing device, data sent from a transceiver of a first computing device, the data indicating one or more traffic conditions associated with an intersection of one or more roads, the data deriving from a traffic device fixed proximate to the intersection;

calculating, based on the data, a risk score for the intersection;

determining, based on the risk score, a modified operating condition;

determining one or more vehicles within a predetermined distance of the intersection; and

transmitting, to one or more computing devices associated with the one or more vehicles, data associated with the modified operating condition,

wherein the modified operating condition is at least one of:

a recommendation regarding a driving action to be taken by one of the one or more vehicles, the recommendation being based on an intersection path risk map that is generated based on the risk score;

an instruction to turn right at the intersection, turn left at the intersection, go straight at the intersection, or execute a U-turn before the intersection;

an indicia received at the one or more vehicles to not to drive through the intersection and the modified operating condition includes an instruction to increase an insurance premium in response the one or more vehicles drive through the intersection after receiving the indicia; and

an instruction that the one or more vehicles change a driving route to avoid the intersection.

10. The method of claim 9 , further comprising:

determining whether the one or more vehicles are autonomous vehicles and whether the intersection does not permit the autonomous vehicles, thereby generating determinations regarding the autonomous vehicles, and

calculating the risk score for the intersection based on the determinations regarding the autonomous vehicles.

11. The method of claim 10 , wherein, when the determinations regarding the autonomous vehicles is that the one or more vehicles are autonomous vehicles and the intersection does not permit the autonomous vehicles, the modified operating condition comprises an instruction to deactivate autonomous-vehicle features while traversing the intersection.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2023
From: MADIGAN, REGINA; GIBSON, TIMOTHY G.; HAYES, HOWARD; KUMAR, SURENDER
To: ALLSTATE INSURANCE COMPANY
Reel/Frame 063103/0561 →
Continuity (5)
Continuation 16821078 · Mar 17, 2020
Continuation 16435844 · Jun 10, 2019
Continuation 16142163 · Sep 26, 2018
Continuation 15249556 · Aug 29, 2016
Related Publication 20230274640A1 · Aug 31, 2023
References Cited (102)
US 5031104A · Ikeda et al. · 1991 [cited by applicant]
US 5926113A · Jones et al. · 1999 [cited by applicant]
US 6100819A · White · 2000 [cited by applicant]
US 6111523A · Mee · 2000 [cited by applicant]
US 6321161B1 · Herbst et al. · 2001 [cited by applicant]
US 6415226B1 · Kozak · 2002 [cited by applicant]
US 6463900B1 · Wakabayashi et al. · 2002 [cited by applicant]
US 7113108B1 · Bachelder et al. · 2006 [cited by applicant]
US 7317406B2 · Wolterman · 2008 [cited by applicant]
US 7327280B2 · Bachelder et al. · 2008 [cited by applicant]
US 7647180B2 · Breed · 2010 [cited by applicant]
US 8031062B2 · Smith · 2011 [cited by applicant]
US 8576069B2 · Nadeem et al. · 2013 [cited by applicant]
US 8606512B1 · Bogovich · 2013 [cited by examiner]
US 8619082B1 · Ciurea et al. · 2013 [cited by applicant]
US 9047778B1 · Cazanas et al. · 2015 [cited by applicant]
US 9048960B2 · Li et al. · 2015 [cited by applicant]
US 9365213B2 · Stenneth et al. · 2016 [cited by applicant]
US 10127812B2 · Madigan et al. · 2018 [cited by applicant]
US 10366606B2 · Madigan et al. · 2019 [cited by applicant]
US 10417904B2 · Madigan et al. · 2019 [cited by applicant]
US 10515543B2 · Madigan et al. · 2019 [cited by applicant]
US 20050184860A1 · Taruki et al. · 2005 [cited by applicant]
US 20050187701A1 · Baney · 2005 [cited by applicant]
US 20060074553A1 · Foo et al. · 2006 [cited by applicant]
US 20090063030A1 · Howarter et al. · 2009 [cited by applicant]
US 20090174573A1 · Smith · 2009 [cited by applicant]
US 20090224931A1 · Dietz et al. · 2009 [cited by applicant]
US 20110018701A1 · Mizuno · 2011 [cited by applicant]
US 20110161119A1 · Collins · 2011 [cited by applicant]
US 20110213628A1 · Peak et al. · 2011 [cited by applicant]
US 20110246051A1 · Vang et al. · 2011 [cited by applicant]
US 20110269441A1 · Silver · 2011 [cited by applicant]
US 20120083995A1 · Vorona · 2012 [cited by applicant]
US 20120191343A1 · Haleem · 2012 [cited by applicant]
US 20120310465A1 · Boatright et al. · 2012 [cited by applicant]
US 20130162449A1 · Ginsberg · 2013 [cited by applicant]
US 20130178234A1 · Jones et al. · 2013 [cited by applicant]
US 20130219047A1 · Weismiller et al. · 2013 [cited by applicant]
US 20130222154A1 · Mori et al. · 2013 [cited by applicant]
US 20140214259A1 · Trepagnier et al. · 2014 [cited by applicant]
US 20140222280A1 · Salomonsson et al. · 2014 [cited by applicant]
US 20140303882A1 · Jang et al. · 2014 [cited by applicant]
US 20150035685A1 · Strickland et al. · 2015 [cited by applicant]
US 20150110344A1 · Okumura · 2015 [cited by applicant]
US 20150166059A1 · Ko · 2015 [cited by applicant]
US 20150235557A1 · Engelman et al. · 2015 [cited by applicant]
US 20150363886A1 · Fernandes et al. · 2015 [cited by applicant]
US 20160086391A1 · Ricci · 2016 [cited by applicant]
US 20160161271A1 · Okumura · 2016 [cited by applicant]
US 20160176398A1 · Prokhorov et al. · 2016 [cited by applicant]
US 20160231746A1 · Hazelton et al. · 2016 [cited by applicant]
US 20160278065A1 · Kim et al. · 2016 [cited by applicant]
US 20160351048A1 · Thompson · 2016 [cited by examiner]
US 20160379485A1 · Anastassov et al. · 2016 [cited by applicant]
US 20170050638A1 · Gordon et al. · 2017 [cited by applicant]
US 20170061561A1 · Cha · 2017 [cited by applicant]
US 20170123421A1 · Kentley et al. · 2017 [cited by applicant]
US 20170197617A1 · Penilla et al. · 2017 [cited by applicant]
US 20170213458A1 · Gordon et al. · 2017 [cited by applicant]
US 20170256147A1 · Shanahan · 2017 [cited by applicant]
US 20170364080A1 · Chintakindi · 2017 [cited by examiner]
US 20180157264A1 · Isaacs et al. · 2018 [cited by applicant]
US 20180184288A1 · De Lorenzo et al. · 2018 [cited by applicant]
US 20220194391A1 · Ferguson · 2022 [cited by examiner]
CN 103647953A · 2014 [cited by applicant]
EP 1643214A2 · 2006 [cited by applicant]
EP 2479538A2 · 2012 [cited by applicant]
KR 20110058279A · 2011 [cited by applicant]
WO WO2015040634A2 · 2015 [cited by applicant]
Oct. 13, 2017—(US) Office Action—U.S. Appl. No. 15/249,597, 13 Pages. [cited by applicant]
Jan. 12, 2018—(US) Non-Final Office Action—U.S. Appl. No. 15/249,556, 29 Pages. [cited by applicant]
Jul. 5, 2018—(US) Non-Final Office Action—U.S. Appl. No. 15/249,536, 40 Pages. [cited by applicant]
Jun. 26, 2018—(US) Notice of Allowance—U.S. Appl. No. 15/249,556, 7 Pages. [cited by applicant]
May 17, 2018—(US) Final Office Action—U.S. Appl. No. 15/249,597, 19 Pages. [cited by applicant]
Nov. 30, 2018—(US) Office Action—U.S. Appl. No. 16/142,163, 19 Pages. [cited by applicant]
Oct. 5, 2018—(US) Office Action—U.S. Appl. No. 15/249,597, 13 Pages. [cited by applicant]
Jan. 14, 2019—(US) Final Office Action—U.S. Appl. No. 15/249,536, 32 Pages. [cited by applicant]
Jul. 29, 2019—(US) Notice of Allowance—U.S. Appl. No. 15/249,536, 13 Pages. [cited by applicant]
Mar. 15, 2019—(US) Notice of Allowance—U.S. Appl. No. 16/142,163, 7 Pages. [cited by applicant]
May 8, 2019—(US) Notice of Allowance—U.S. Appl. No. 15/249,597, 8 Pages. [cited by applicant]
Dec. 3, 2020—(CA) Office Action—Application No. 3,034,441 (006591.02012), 4 Pages. [cited by applicant]
Dec. 17, 2020—(US) Final Office Action—U.S. Appl. No. 16/435,844, 20 Pages. [cited by applicant]
Feb. 7, 2020—(CA) Office Action—App. No. 3,034,441 (006591.02012), 6 pages. [cited by applicant]
Jan. 8, 2020—(US) Notice of Allowance—U.S. Appl. No. 16/435,844, 7 Pages. [cited by applicant]
Jun. 11, 2020—(US) Non-Final Office Action—U.S. Appl. No. 16/435,844 (6591.2179), 13 Pages. [cited by applicant]
Jun. 30, 2020—(US) Non-Final Office Action—U.S. Appl. No. 16/671,403 (6591.2269), 37 Pages. [cited by applicant]
Oct. 19, 2020—(US) Notice of Allowance—U.S. Appl. No. 16/671,403, 12 Pages. [cited by applicant]
Sep. 18, 2020—(US) Non-Final Office Action—U.S. Appl. No. 16/821,078 (006591.02416), 21 Pages. [cited by applicant]
Jan. 15, 2021—(US) Notice of Allowance—U.S. Appl. No. 16/671,403, 2 Pages. [cited by applicant]
Mar. 24, 2021—(US) Non-Final Office Action—U.S. Appl. No. 16/534,415, 36 Pages. [cited by applicant]
Mar. 4, 2021—(US) Non-Final Office Action—U.S. Appl. No. 16/821,078 (006591.02416), 17 Pages. [cited by applicant]
“AGT and Cisco's Smart Intersection Leverages IoT Edge Analytics to Improve Road Safety and Traffic Management,” AGT Web Team; Retrieved from URL: https://www.agtinterational.com/agt-and-ciscos-smart-intersection-levera… [cited by applicant]
Extended European Search Report for European Application No. 17847302.1 dated Jun. 26, 2020, 11 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2017/048882, mailed Mar. 14, 2019, 7 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2017/048882, mailed Nov. 20, 2017, 8 Pages. [cited by applicant]
Klein L.A, “Final Report: Mobile Surveillance and Wireless Communication Systems Field Operational Test,” vol. 2: FOT Objectives, Organization, System Design, Results, Conclusion, and Recommendations; California PATH Re… [cited by applicant]
Koumoullos M.G., et al., “The S.MAR.T. Intersection—Integrating Infrared Sensors with a Microcontroller: Automated Regulation of Traffic Flow,” Science and Mechatronics Aided Research for Teachers 2004; Aug. 2004, 17 Pa… [cited by applicant]
Kuriakose J., et al., Way To Green: Intelligent Traffic Control With Vanet, International Journal of Computer Engineering & Technology (IJCET); vol. 5 (12), Dec. 2014, pp. 99-104. [cited by applicant]
Partial Supplementary European Search Report for European Application No. 17847302.1, mailed Mar. 23, 2020, 12 Pages. [cited by applicant]
Dec. 13, 2023—(US) Non-Final Office Action—U.S. Appl. No. 17/828,486, 22 Pages. [cited by applicant]
Jan. 27, 2025—(US) Non-Final Office Action—U.S. Appl. No. 17/828,486, 10 Pages. [cited by applicant]