Intelligent traffic control mesh

• US 8,554,456 B2
• Filed: 07/05/2011
• Issued: 10/08/2013
• Est. Priority Date: 07/05/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Brant, Charles David, Burwell, Esther Marie, Orr, Robert Lee, Wood, Douglas Andrew
• Primary Examiner(s): Cheung, Mary
• Assistant Examiner(s): BUTLER, RODNEY ALLEN
• Application Number:
  US13/176,622
• Publication Number:
  US 20130013178A1
• Time in Patent Office: 826 Days
• Field of Search: 701/117, 701/118, 701/119, 701/120, 340/906, 340/907, 340/909, 340/910, 340/911, 340/919, 340/918, 340/917, 340/933, 340/934, 340/936
• US Class Current: 701/117
• CPC Class Codes: G08G 1/0116 from roadside infrastructure, e.g. beacons
• CPC Class Codes: G08G 1/0133 for classifying traffic situation
• CPC Class Codes: G08G 1/0145 for active traffic flow control
• CPC Class Codes: G08G 1/083 Controlling the allocation of time between phases of a cycle

Abstract

An approach is provided that gathers observational traffic data at traffic controller nodes. Each of the traffic controller nodes communicates observational traffic data to other traffic controller nodes via a network. The traffic controller nodes negotiate traffic control parameters. The negotiating process receives timing proposals from the other traffic controller nodes included in the related set. The nodes analyze the proposed timings based on the traffic controller'"'"'s gathered observational traffic data. The traffic controller node prepares responses in response to the analysis. The traffic controller node sends the negotiation responses to the other traffic controller nodes. The traffic controller node also adjusts its traffic control parameters that control the node'"'"'s cycle times based on the analysis.

Claims

1. A computer implemented method comprising:

gathering observational traffic data at each of a plurality of traffic controller nodes, wherein each of the traffic controller nodes communicates the gathered observational traffic data with one or more other traffic controller nodes via a network, wherein the observational traffic data includes one or more vehicle packets traveling on one or more routes that are managed by each of the corresponding traffic controller nodes, wherein the vehicle packets are identified based upon gaps between the packets;

negotiating a plurality of traffic control parameters between a selected one of the plurality of traffic controller nodes and a related set of one or more traffic controller nodes, wherein the negotiating further comprises;

receiving a timing proposal from each of the traffic controller nodes included in the related set;

analyzing, by one or more processors, at the selected traffic controller node, the received timing proposals based on the selected traffic controller'"'"'s gathered observational traffic data;

preparing a plurality of negotiation responses in response to the analysis;

sending the negotiation responses to the traffic controller nodes included in the related set; and

adjusting the traffic control parameters that control a current cycle time that corresponds to the selected traffic controller node, wherein the adjusting is based on the analysis.

2. The method of claim 1 wherein the observational traffic data further includes a current queued number of vehicles that are waiting in each of one or more queues that are managed by each of the corresponding traffic controller nodes, a routed number of vehicles that are traveling in each of one or more routes that are managed by each of the corresponding traffic controller nodes, and an average speed of each of the routes that are managed by each of the corresponding traffic controller nodes.

3. The method of claim 2 further comprising:

adjusting, by the selected traffic controller node, a size of each of the gaps, wherein the adjusted gap size is large enough to allow cross traffic to flow at the adjusted gaps;

synchronizing the vehicle packets at the selected traffic controller node traveling in opposite directions;

creating a proposed set of timing data based on the synchronizing; and

transmitting the proposed set of timing data to the related set of traffic controller nodes.

4. The method of claim 1 further comprising:

receiving, at the selected traffic controller node, a priority value;

identifying a vehicle wait time from the selected traffic controller node'"'"'s gathering observational traffic data;

transmitting the identified vehicle wait time to the related set of traffic controller nodes;

receiving one or more packet wait times from the related set of traffic controller nodes;

applying a weight factor to the received packet wait times; and

adjusting the priority value based on based on the vehicle wait time and the received packet wait times, wherein the identifying, transmitting, receiving, applying, and adjusting steps are performed repeatedly.

5. The method of claim 4 wherein the analysis of the received timing proposals is also based on the adjusted priority value.

6. The method of claim 1 further comprising:

repeatedly gathering the observational traffic data at the selected traffic controller node,

appending a timestamp to each of the observational traffic data gathered at the selected traffic controller node;

storing the gathered observational traffic data with appended timestamps in a historical traffic data store;

analyzing the historical traffic data store based on one or more timing factors resulting in a trend analysis;

transmitting the trend analysis to the related set of traffic controller nodes; and

receiving a trend analysis from each of the related set of traffic controller nodes, wherein the analysis of the received timing proposals is also based on the trend analysis and the received trend analyses.

7. An information handling system comprising:

a plurality of traffic controller nodes, wherein each of the traffic controller nodes comprises;

one or more processors;

a memory coupled to at least one of the processors;

one or more traffic sensors accessible by at least one of the processors; and

one or more traffic signals controlled by the traffic controller node;

a network that interconnects the plurality of traffic controller nodes; and

a program that is executed by each of the plurality of traffic controller nodes, wherein the program includes a set of computer program instructions stored in the memory and executed by at least one of the processors included in each of the plurality of traffic controller nodes in order to perform actions of;

gathering observational traffic data at each of a plurality of traffic controller nodes using the traffic controller node'"'"'s sensors, wherein the observational traffic data includes one or more vehicle packets traveling on one or more routes that are managed by each of the corresponding traffic controller nodes, wherein the vehicle packets are identified based upon gaps between the packets;

communicating the gathered observational traffic data with one or more other traffic controller nodes via the network;

negotiating a plurality of traffic control parameters between the traffic controller node and a related set of one or more traffic controller nodes, wherein the negotiating further comprises;

receiving a timing proposal from each of the traffic controller nodes included in the related set;

analyzing, at the traffic controller node, the received timing proposals based on the traffic controller'"'"'s gathered observational traffic data;

preparing a plurality of negotiation responses in response to the analysis;

sending the negotiation responses to the traffic controller nodes included in the related set; and

adjusting the traffic control parameters that control a current cycle time that corresponds to traffic signals controlled by the selected traffic controller node, wherein the adjusting is based on the analysis.

8. The information handling system of claim 7 wherein the observational traffic data further includes a current queued number of vehicles that are waiting in each of one or more queues that are managed by each of the corresponding traffic controller nodes, a routed number of vehicles that are traveling in each of one or more routes that are managed by each of the corresponding traffic controller nodes, and an average speed of each of the routes that are managed by each of the corresponding traffic controller nodes.

9. The information handling system of claim 8 wherein at least one of the processors performs additional actions comprising:

adjusting, by the selected traffic controller node, a size of each of the gaps, wherein the adjusted gap size is large enough to allow cross traffic to flow at the adjusted gaps;

synchronizing the vehicle packets at the selected traffic controller node traveling in opposite directions;

creating a proposed set of timing data based on the synchronizing; and

transmitting the proposed set of timing data to the related set of traffic controller nodes.

10. The information handling system of claim 7 wherein at least one of the processors performs additional actions comprising:

receiving, at the selected traffic controller node, a priority value;

identifying a vehicle wait time from the selected traffic controller node'"'"'s gathering observational traffic data;

transmitting the identified vehicle wait time to the related set of traffic controller nodes;

receiving one or more packet wait times from the related set of traffic controller nodes;

applying a weight factor to the received packet wait times; and

adjusting the priority value based on based on the vehicle wait time and the received packet wait times, wherein the identifying, transmitting, receiving, applying, and adjusting steps are performed repeatedly.

11. The information handling system of claim 10 wherein the analysis of the received timing proposals is also based on the adjusted priority value.

12. The information handling system of claim 7 wherein at least one of the processors performs additional actions comprising:

repeatedly gathering the observational traffic data at the selected traffic controller node;

appending a timestamp to each of the observational traffic data gathered at the selected traffic controller node;

storing the gathered observational traffic data with appended timestamps in a historical traffic data store;

analyzing the historical traffic data store based on one or more timing factors resulting in a trend analysis;

transmitting the trend analysis to the related set of traffic controller nodes; and

receiving a trend analysis from each of the related set of traffic controller nodes, wherein the analysis of the received timing proposals is also based on the trend analysis and the received trend analyses.

13. A computer program product stored in a computer readable storage medium, comprising computer program code that, when executed by an information handling system, causes the information handling system to perform actions comprising:

gathering observational traffic data at each of a plurality of traffic controller nodes, wherein each of the traffic controller nodes communicates the gathered observational traffic data with one or more other traffic controller nodes via a network, wherein the observational traffic data includes one or more vehicle packets traveling on one or more routes that are managed by each of the corresponding traffic controller nodes, wherein the vehicle packets are identified based upon gaps between the packets;

negotiating a plurality of traffic control parameters between a selected one of the plurality of traffic controller nodes and a related set of one or more traffic controller nodes, wherein the negotiating further comprises;

receiving a timing proposal from each of the traffic controller nodes included in the related set;

analyzing, at the selected traffic controller node, the received timing proposals based on the selected traffic controller'"'"'s gathered observational traffic data;

preparing a plurality of negotiation responses in response to the analysis;

sending the negotiation responses to the traffic controller nodes included in the related set; and

adjusting the traffic control parameters that control a current cycle time that corresponds to the selected traffic controller node, wherein the adjusting is based on the analysis.

14. The computer program product of claim 13 wherein the observational traffic data further includes a current queued number of vehicles that are waiting in each of one or more queues that are managed by each of the corresponding traffic controller nodes, a routed number of vehicles that are traveling in each of one or more routes that are managed by each of the corresponding traffic controller nodes, and an average speed of each of the routes that are managed by each of the corresponding traffic controller nodes.

15. The computer program product of claim 14 further comprising additional computer program code that, when executed by the information handling system, causes the information handling system to perform additional actions comprising:

adjusting, by the selected traffic controller node, a size of each of the gaps, wherein the adjusted gap size is large enough to allow cross traffic to flow at the adjusted gaps;

synchronizing the vehicle packets at the selected traffic controller node traveling in opposite directions;

creating a proposed set of timing data based on the synchronizing; and

transmitting the proposed set of timing data to the related set of traffic controller nodes.

16. The computer program product of claim 13 wherein the analysis of the received timing proposals is also based on the adjusted priority value and further comprising additional computer program code that, when executed by the information handling system, causes the information handling system to perform additional actions comprising:

receiving, at the selected traffic controller node, a priority value;

identifying a vehicle wait time from the selected traffic controller node'"'"'s gathering observational traffic data;

transmitting the identified vehicle wait time to the related set of traffic controller nodes;

receiving one or more packet wait times from the related set of traffic controller nodes;

applying a weight factor to the received packet wait times; and

adjusting the priority value based on based on the vehicle wait time and the received packet wait times, wherein the identifying, transmitting, receiving, applying, and adjusting steps are performed repeatedly.

17. The computer program product of claim 13 further comprising additional computer program code that, when executed by the information handling system, causes the information handling system to perform additional actions comprising:

repeatedly gathering the observational traffic data at the selected traffic controller node;

appending a timestamp to each of the observational traffic data gathered at the selected traffic controller node;

storing the gathered observational traffic data with appended timestamps in a historical traffic data store;

analyzing the historical traffic data store based on one or more timing factors resulting in a trend analysis;

transmitting the trend analysis to the related set of traffic controller nodes; and

receiving a trend analysis from each of the related set of traffic controller nodes, wherein the analysis of the received timing proposals is also based on the trend analysis and the received trend analyses.