Monitoring management and presentation of preemption control data of centrally managed traffic signals
First Claim
1. A method for managing traffic signal preemption data accumulated at a plurality of intersections, comprising:
- reading the preemption data stored by respective preemption controllers at the intersections, wherein the preemption data includes, for each preemption request, an emitter code, and a date and a time the preemption request was submitted by an emitter to the respective preemption controller;
storing the preemption data read from the intersections in a database;
associating each emitter code with a vehicle name in the database;
in response to a first user command identifying one or more emitter codes and an agency having one or more vehicles with one or more emitters that generate the one or more emitter codes, respectively, storing data in the database for each of the one or more emitter codes indicating the codes are associated with the agency;
reading selected preemption data and vehicle names from the database in response to a second user command; and
in the preemption data read from the database, counting for each emitter code in the preemption data, a total number of preemption requests having the emitter code; and
displaying the vehicle names, total numbers of preemption requests for the associated emitter codes, and agencies associated with the emitter codes;
wherein the reading of preemption data from the intersections, storing, associating, reading of preemption data from the database, and displaying are performed with a programmed computer; and
wherein storing the preemption data includes storing data identifying the intersection from which preemption data was read.
5 Assignments
0 Petitions
Accused Products
Abstract
Managing traffic signal preemption data accumulated at a plurality of intersections. In one approach a method includes reading the preemption data stored at each of the intersections. The preemption data includes for each preemption request an emitter code, and a date and a time the preemption request was submitted. The preemption data read from the intersections are stored in a database, and each emitter code is associated with a vehicle name in the database. Selected preemption data and associated vehicle names are read from the database in response to user input, and the selected preemption data and associated vehicle names are displayed. The database further stores data identifying the intersection from which the preemption data was read.
-
Citations
18 Claims
-
1. A method for managing traffic signal preemption data accumulated at a plurality of intersections, comprising:
-
reading the preemption data stored by respective preemption controllers at the intersections, wherein the preemption data includes, for each preemption request, an emitter code, and a date and a time the preemption request was submitted by an emitter to the respective preemption controller; storing the preemption data read from the intersections in a database; associating each emitter code with a vehicle name in the database; in response to a first user command identifying one or more emitter codes and an agency having one or more vehicles with one or more emitters that generate the one or more emitter codes, respectively, storing data in the database for each of the one or more emitter codes indicating the codes are associated with the agency; reading selected preemption data and vehicle names from the database in response to a second user command; and in the preemption data read from the database, counting for each emitter code in the preemption data, a total number of preemption requests having the emitter code; and displaying the vehicle names, total numbers of preemption requests for the associated emitter codes, and agencies associated with the emitter codes; wherein the reading of preemption data from the intersections, storing, associating, reading of preemption data from the database, and displaying are performed with a programmed computer; and wherein storing the preemption data includes storing data identifying the intersection from which preemption data was read. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. A system for managing traffic signal preemption data stored at a plurality of intersections by respective preemption controllers, comprising:
-
a processor, a memory arrangement coupled to the processor, wherein the memory arrangement is configured with instructions that when executed by the processor cause the processor to perform the operations of; reading the preemption data stored at each of the intersections, wherein the preemption data includes for each preemption request an emitter code, and a date and a time the preemption request was submitted by an emitter to the respective preemption controller at the intersection; storing the preemption data read from the intersections in a database; associating each emitter code with a vehicle name in the database; in response to a first user command identifying one or more emitter codes and an agency having one or more vehicles with one or more emitters that generate the one or more emitter codes, respectively, storing data in the database for each of the one or more emitter codes indicating the codes are associated with the agency; reading selected preemption data and vehicle names from the database in response to a second user command; and displaying the vehicle names, total numbers of preemption requests for the associated emitter codes, and agencies associated with the emitter codes; and wherein storing the preemption data includes storing data identifying the intersection from which preemption data was read.
-
-
18. A computer-readable medium, comprising:
a non-transitory storage device configured with processor executable instructions for managing traffic signal preemption data accumulated at a plurality of intersections, wherein the instructions, when executed by a computer, cause the computer to perform the operations of; reading the preemption data stored by respective preemption controllers at the intersections, wherein the preemption data includes for each preemption request an emitter code, and a date and a time the preemption request was submitted by an emitter to the respective preemption controller; storing the preemption data read from the intersections in a database; associating each emitter code with a vehicle name in the database; in response to a first user command identifying one or more emitter codes and an agency having one or more vehicles with one or more emitters that generate the one or more emitter codes, respectively, storing data in the database for each of the one or more emitter codes indicating the codes are associated with the agency; reading selected preemption data and vehicle names from the database in response to a second user command; in the preemption data read from the database, counting for each emitter code in the preemption data, a total number of preemption requests having the emitter code; displaying vehicle names, total numbers of preemption requests for the associated emitter codes, and agencies associated with the emitter codes; and wherein storing the preemption data includes storing data identifying the intersection from which preemption data was read.
Specification