IP Library Granted Patent US 12688773
Granted Patent B2
US 12688773 · App. 18/541,327 · Granted Jul 21, 2026

Initiating traffic signal timing plan generation

Inventors: Vivek Vijaya Kumar (Shelby Township, MI); Donald K. Grimm (Utica, MI); Fan Bai (Ann Arbor, MI)
Assignee: GM GLOBAL TECHNOLOGY OPERATIONS LLC
G08G1/08G08G1/0129G08G1/0133G08G1/095
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 12688773
App. No.
18/541,327
Granted
Jul 21, 2026
Kind
B2
Abstract

A method for generating a traffic signal timing plan may include determining a current traffic metric. The method further may include identifying a timing plan generation trigger. The method further may include determining at least one historic traffic metric. The method further may include generating the traffic signal timing plan based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric. The method further may include adjusting an operation of one or more traffic signals based at least in part on the traffic signal timing plan.

Claims (84)

1 . A method for generating a traffic signal timing plan, the method comprising:

determining a current traffic metric;

identifying a timing plan generation trigger, wherein identifying the timing plan generation trigger further comprises:

identifying a reactive timing plan generation trigger; and

identifying a proactive timing plan generation trigger;

determining at least one historic traffic metric, wherein determining the at least one historic traffic metric further comprises:

determining a plurality of long-term historic traffic metrics over a first time period; and

determining a plurality of short-term historic traffic metrics over a second time period, wherein the second time period is shorter than the first time period;

generating the traffic signal timing plan based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric;

adjusting an operation of one or more traffic signals based at least in part on the traffic signal timing plan; and

wherein identifying the reactive timing plan generation trigger further comprises:

determining a short-term traffic metric change based at least in part on the current traffic metric and one or more of the plurality of short-term historic traffic metrics;

comparing the short-term traffic metric change to a predetermined short-term traffic metric change threshold; and

identifying the reactive timing plan generation trigger in response to determining that the short-term traffic metric change is greater than or equal to the predetermined short-term traffic metric change threshold.

2 . The method of claim 1 , wherein determining the current traffic metric further comprises:

receiving telemetry data from one or more of a plurality of vehicles; and

determining the current traffic metric based at least in part on the telemetry data.

3 . The method of claim 1 , wherein identifying the proactive timing plan generation trigger further comprises:

receiving a proactive timing plan generation trigger request, wherein the proactive timing plan generation trigger request includes event data about an event; and

identifying the proactive timing plan generation trigger based on the event data.

4 . The method of claim 1 , wherein generating the traffic signal timing plan based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric further comprises:

generating a reactive traffic signal timing plan in response to identifying the reactive timing plan generation trigger; and

generating a proactive traffic signal timing plan in response to identifying the proactive timing plan generation trigger.

5 . The method of claim 4 , wherein generating the reactive traffic signal timing plan further comprises:

determining a predicted traffic metric change based at least in part on the current traffic metric and the plurality of long-term historic traffic metrics; and

generating the reactive traffic signal timing plan based at least in part on the predicted traffic metric change, wherein the reactive traffic signal timing plan includes at least a reactive traffic signal timing plan validity.

6 . The method of claim 5 , further comprising:

determining a rate of short-term traffic metric change based at least in part on the current traffic metric and one or more of the plurality of short-term historic traffic metrics; and

determining the reactive traffic signal timing plan validity based at least in part on the rate of short-term traffic metric change.

7 . The method of claim 4 , wherein generating the proactive traffic signal timing plan further comprises:

determining a predicted traffic metric change based at least in part on the current traffic metric, the plurality of long-term historic traffic metrics, and event data; and

generating the proactive traffic signal timing plan based at least in part on the predicted traffic metric change, wherein the proactive traffic signal timing plan includes at least a proactive traffic signal timing plan validity, and wherein the proactive traffic signal timing plan validity is determined based at least in part on the event data.

8 . A system for generating a traffic signal timing plan, the system comprising:

a server communication system;

a server controller in electrical communication with the server communication system, wherein the server controller is programmed to:

receive telemetry data from one or more of a plurality of vehicles using the server communication system;

determine a current traffic metric based at least in part on the telemetry data;

identify a timing plan generation trigger, wherein the timing plan generation trigger includes at least one of: a reactive timing plan generation trigger and a proactive timing plan generation trigger, wherein to identify the timing plan generation trigger, the server controller is further programmed to:

identify the reactive timing plan generation trigger, wherein the reactive timing plan generation trigger is identified based at least in part on at least one of: a traffic anomaly, a time of day, a periodic trigger, and a random trigger;

determine at least one historic traffic metric, wherein the at least one historic traffic metric includes at least one of: a plurality of long-term historic traffic metrics determined over a first time period and a plurality of short-term historic traffic metrics determined over a second time period, wherein the second time period is shorter than the first time period;

generate a reactive traffic signal timing plan in response to identifying the reactive timing plan generation trigger, wherein the reactive traffic signal timing plan is generated based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric;

generate a proactive traffic signal timing plan in response to identifying the proactive timing plan generation trigger, wherein the proactive traffic signal timing plan is generated based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric;

adjust an operation of one or more traffic signals using the server communication system based at least in part on at least one of: the reactive traffic signal timing plan and the proactive traffic signal timing plan; and

wherein to identify the timing plan generation trigger based at least in part on the traffic anomaly, the server controller is further programmed to:

determine a short-term traffic metric change based at least in part on the current traffic metric and one or more of the plurality of short-term historic traffic metrics;

compare the short-term traffic metric change to a predetermined short-term traffic metric change threshold; and

identify the reactive timing plan generation trigger in response to determining that the short-term traffic metric change is greater than or equal to the predetermined short-term traffic metric change threshold.

9 . The system of claim 8 , wherein to generate the reactive traffic signal timing plan, the server controller is further programmed to:

determine a predicted traffic metric change based at least in part on the current traffic metric and the plurality of long-term historic traffic metrics; and

generate the reactive traffic signal timing plan based at least in part on the predicted traffic metric change, wherein the reactive traffic signal timing plan includes at least a reactive traffic signal timing plan validity.

10 . The system of claim 8 , wherein to identify the timing plan generation trigger, the server controller is further programmed to:

receive a proactive timing plan generation trigger request, wherein the proactive timing plan generation trigger request includes event data about an event, and wherein the event is at least one of: a road management event, a weather event, and a public event; and

identify the proactive timing plan generation trigger based on the event data.

11 . The system of claim 10 , wherein to generate the proactive traffic signal timing plan, the server controller is further programmed to:

determine a predicted traffic metric change based at least in part on the current traffic metric, the plurality of long-term historic traffic metrics, and event data; and

generate the proactive traffic signal timing plan based at least in part on the predicted traffic metric change, wherein the proactive traffic signal timing plan includes at least a proactive traffic signal timing plan validity, and wherein the proactive traffic signal timing plan validity is determined based at least in part on the event data.

12 . The system of claim 11 , wherein the server controller is further programmed to:

determine an event start time based at least in part on the event data;

determine an event end time based at least in part on the event data; and

determine the proactive traffic signal timing plan validity based at least in part on the event start time and the event end time.

13 . A system for generating a traffic signal timing plan, the system comprising:

a traffic signal control system;

a server communication system; and

a server controller in electrical communication with the traffic signal control system and the server communication system, wherein the server controller is programmed to:

receive telemetry data from one or more of a plurality of vehicles using the server communication system;

determine a current traffic metric based at least in part on the telemetry data;

identify a timing plan generation trigger, wherein to identify the timing plan generation trigger, the server controller is further programmed to:

identify a reactive timing plan generation trigger, wherein the reactive timing plan generation trigger is identified based at least in part on at least one of: a traffic anomaly, a time of day, a periodic trigger, and a random trigger;

receive a proactive timing plan generation trigger request, wherein the proactive timing plan generation trigger request includes event data about an event, and wherein the event is at least one of: a road management event, a weather event, and a public event; and

identify a proactive timing plan generation trigger based on the event data;

determine at least one historic traffic metric, wherein to determine the at least one historic traffic metric, the server controller is further programmed to:

determine a plurality of long-term historic traffic metrics over a first time period; and

determine a plurality of short-term historic traffic metrics over a second time period, wherein the second time period is shorter than the first time period;

generate at least one of: a reactive traffic signal timing plan and a proactive traffic signal timing plan based at least in part on at least one of: the current traffic metric, the timing plan generation trigger, and the at least one historic traffic metric in response to identifying the timing plan generation trigger;

adjust an operation of one or more traffic signals using the traffic signal control system based at least in part on at least one of: the reactive traffic signal timing plan and the proactive traffic signal timing plan; and

wherein identifying the reactive timing plan generation trigger further comprises:

determining a short-term traffic metric change based at least in part on the current traffic metric and one or more of the plurality of short-term historic traffic metrics;

comparing the short-term traffic metric change to a predetermined short-term traffic metric change threshold; and

identifying the reactive timing plan generation trigger in response to determining that the short-term traffic metric change is greater than or equal to the predetermined short-term traffic metric change threshold.

14 . The system of claim 13 , wherein to generate at least one of: the reactive traffic signal timing plan and the proactive traffic signal timing plan, the server controller is further programmed to:

determine a first predicted traffic metric change based at least in part on the current traffic metric and the at least one historic traffic metric;

generate the reactive traffic signal timing plan based at least in part on the first predicted traffic metric change, wherein the reactive traffic signal timing plan includes at least a reactive traffic signal timing plan validity;

determine a second predicted traffic metric change based at least in part on the current traffic metric, the at least one historic traffic metric, and event data; and

generate the proactive traffic signal timing plan based at least in part on the second predicted traffic metric change, wherein the proactive traffic signal timing plan includes at least a proactive traffic signal timing plan validity, and wherein the proactive traffic signal timing plan validity is determined based at least in part on the event data.