Transit Signal Priority Architecture. Under the proposed TSP system architecture, buses are equipped with both GPS & RF based on-bus systems that communicate with the intersection controllers. Once in the corridor, TSP-equipped buses request priority by sending specific check-in, position update, and checkout messages to the intersections. The traffic controllers then process the messages and implement priority for the buses according to criteria set for granting such priority. The TSP Parameters would be jointly determined by Omnitrans and each City along the corridor prior to deploying the system. Priority may be requested at signalized intersections equipped with the TSP Components and granted based on parameters determined by Omnitrans and the City. When the decision to request priority has been made by the on-bus system, communications are initiated with the intersection where priority is requested. The system architecture provides for health and performance monitoring of the TSP systems by the Omnitrans and each City where the system is located. Data is extracted from the signal priority data network and sent to the TSP Network Monitor data server. The TSP Network Monitor provides for network monitoring, maintenance planning, and historical data reporting. For health monitoring purposes, network devices can be accessed once they are on the network by sending requests to the signal priority data network. The proposed system architecture would employ a communications between mobile network clients that is, TSP-equipped BRT vehicle, and intersection traffic signal controllers. The WLAN consists of a network of devices known as access points (AP) that are connected together using both wired, where available, and wireless communications. Each AP manages a number of wireless mobile and intersection clients associated to it by authenticating a client’s right to be utilizing the network and to broker network communications between the client and other network devices.
