2.6 TSP Detection Architectures, Conditional Priority & Freight Priority
Key Takeaways
- Priority detection ranges from line-of-sight optical emitters through GPS/AVL requests routed over the agency network to short-range radio; each moves the decision point further from the intersection and adds latency that must be built into the request timing.
- Conditional priority screens requests on schedule adherence, passenger load, and headway, so an on-time bus receives nothing and only a late or crowded vehicle spends arterial capacity.
- Freight signal priority targets heavy vehicles on steep grades and at high-cost stop locations, where the fuel and emissions penalty of a stop is far larger than for a passenger car.
- Field verification is a wiring and programming task: confirm the priority input is landed on the correct terminal, that the controller priority plan is enabled for the right time-of-day pattern, and that the confirmation indicator lights only on a granted call.
2.6 TSP Detection Architectures, Conditional Priority & Freight Priority
Detection Architectures & Vehicle-to-Infrastructure Systems
Active priority relies on detecting transit vehicles at precise upstream locations. Common physical architectures include:
+-----------------------------------------------------------------------------+
| TRANSIT PRIORITY ADVANCE CHECK-IN & CHECK-OUT |
+-----------------------------------------------------------------------------+
| |
| [Bus Approach Route] |
| | |
| v (Travel Speed V = 35 mph / ~51 ft/sec) |
| +-------------------------------------------------------------+ |
| | ADVANCE CHECK-IN DETECTOR | |
| | Location: 15 to 30 seconds upstream (~800 to 1,500 ft) | |
| | - Transmits Signal Request Message (SRM) / Priority Call | |
| | - Controller evaluates schedule adherence & splits | |
| | - Controller initiates early green or plans green extension | |
| +-------------------------------------------------------------+ |
| | |
| v (Transit Bus In Travel) |
| +-------------------------------------------------------------+ |
| | INTERMEDIATE RE-CHECK DETECTOR (Optional) | |
| | Location: ~5 to 8 seconds upstream (~250 to 400 ft) | |
| | - Updates estimated time of arrival (ETA) at stop bar | |
| +-------------------------------------------------------------+ |
| | |
| v |
| +-------------------------------------------------------------+ |
| | STOP BAR CHECK-OUT DETECTOR | |
| | Location: Immediately downstream of stop line or far-side | |
| | - Cancels active priority call immediately | |
| | - Prevents extending green after bus has cleared | |
| +-------------------------------------------------------------+ |
+-----------------------------------------------------------------------------+
Detection Hardware Implementations
- Optical Strobe / Infrared Emitters: Vehicle-mounted emitters pulse at coded frequencies. High-frequency pulsing (e.g., 14.0 Hz) is reserved for emergency vehicle preemption, while low-frequency pulsing (e.g., 10.0 Hz) triggers transit priority channels on cabinet optical discriminator modules.
- RFID Transponders & Inductive Loops: Pavement loops with specialized digital classification loop amplifiers detect embedded transponders or identify the unique metallic inductance signature profile of heavy buses.
- GPS / Automated Vehicle Location (AVL): Modern transit fleets use onboard GPS units coupled with cellular or DSRC/C-V2X wireless links. The bus tracks its geographic position against virtual "geofences" programmed in its onboard navigation computer. When crossing an upstream geofence, the onboard unit automatically transmits a Signal Request Message (SRM) to the intersection RSU or central ATMS.
- Placement Spatial Rules: The advance Check-In detector must be located 15 to 30 seconds of travel time upstream of the stop bar. If placed too close (<10 seconds), the controller lacks sufficient time to truncate conflicting phases cleanly without violating minimum clearance intervals. The Check-Out detector must be situated immediately past the stop bar (or at the far-side bus stop) to terminate the priority request instantly, preventing green waste.
Conditional Priority & Scheduling Logic
Early TSP deployments granted priority unconditionally whenever a bus arrived. However, granting priority to empty buses or buses already running ahead of schedule creates unnecessary cross-street delays and breaks corridor coordination. Modern systems enforce Conditional TSP:
+-----------------------------------------------------------------------------+
| CONDITIONAL TSP DECISION TREE LOGIC |
+-----------------------------------------------------------------------------+
| |
| [Bus Crosses Advance Check-In Geofence] |
| | |
| v |
| [Evaluate Schedule Adherence via CAD/AVL] |
| | |
| +---------------------+---------------------+ |
| | | |
| v (Bus is ON-TIME or AHEAD) v (Bus LATE) |
| [Schedule Delay < 3.0 Mins] [Schedule Delay >= 3.0 Mins|
| | | |
| v v |
| [SUPPRESS PRIORITY] [Evaluate Passenger Load] |
| - Do not adjust splits - Automated Count (APC) |
| - Maintain normal coordination | |
| +-----------------+---------------+
| | |
| v (< 15 Passengers) v
| [LOW PASSENGER LOAD] [HIGH LOAD|
| - Suppress Priority - GRANT |
| PRIORITY |
| |
+-----------------------------------------------------------------------------+
Key Evaluation Criteria for Conditional TSP
- Schedule Adherence: Priority is granted only if the transit vehicle is operating behind its published timetable. A standard threshold requires the bus to be running at least 3 to 5 minutes late. If the vehicle is on time, the request is suppressed.
- Passenger Occupancy: Onboard Automated Passenger Counters (APC) tally boarding and alighting passengers. Priority requests are weighted based on total passenger load, favoring crowded buses over nearly empty vehicles.
- Headway Regularity: On high-frequency transit lines (where buses arrive every 5 to 8 minutes), schedule adherence is less important than maintaining uniform spacing between buses. Conditional priority slows down lead buses and accelerates trailing buses to eliminate hazardous bus bunching.
- Cross-Street Saturation Guard: Advanced controllers monitor vehicle queues on conflicting cross streets via advance presence detectors. If opposing approaches exceed an 80% split utilization threshold, the controller temporarily overrides or suppresses incoming TSP calls to prevent gridlock.
Freight Signal Priority (FSP)
Freight Signal Priority (FSP) adapts priority principles to the physical operational realities of heavy commercial motor vehicles (CMVs) carrying up to 80,000 lbs (36,300 kg) gross vehicle weight.
+-----------------------------------------------------------------------------+
| HEAVY VEHICLE STOPPING DYNAMICS & DILEMMA ZONE |
+-----------------------------------------------------------------------------+
| |
| Approaching Heavy Truck (80,000 lbs) |
| Speed: V = 50 mph (73.3 ft/sec) |
| Approach Grade: G = -4.0% (-0.04 Steep Downgrade) |
| |
| Stopping Sight Distance Physics (AASHTO / FHWA Formulation): |
| |
| (V)^2 |
| d = 1.47*V*t + ------------------- |
| 30 * ( f +/- G ) |
| |
| Where: |
| - Perception-Reaction Time: t = 2.0 seconds |
| - Pavement Friction Factor: f = 0.30 (Wet / Worn Pavement) |
| - Grade: G = -0.04 (Downgrade subtracts friction) |
| |
| d_perception = 1.47 * 50 * 2.0 = 147.0 ft |
| d_braking = (50)^2 / [ 30 * (0.30 - 0.04) ] = 2,500 / 7.80 = 320.5 ft |
| Total Stopping Distance = 147.0 + 320.5 = 467.5 FEET! |
| |
| Passenger Car Equivalent at 50 mph (Flat Grade): ~220 Feet |
| RESULT: Heavy trucks require MORE THAN TWICE the stopping distance! |
| |
+-----------------------------------------------------------------------------+
Why Freight Priority is Critical to Field Operations
- Severe Stopping Kinematics: Because truck braking distance scales with the square of velocity and inversely with grade ($f - G$), a loaded tractor-trailer descending a steep downgrade ($G < 0$) cannot stop within standard passenger vehicle clearance intervals. Abrupt stops cause brake fade, cargo shifting, and jackknife collisions.
- Dilemma Zone Mitigation: High-speed heavy trucks are highly susceptible to the Type II dilemma zone—the roadway segment where a driver can neither stop comfortably before the stop line nor clear the intersection before the red display. FSP dynamically extends the green phase when a truck is detected within its dilemma zone window (typically 3 to 6 seconds upstream).
- Pavement Rutting & Infrastructure Preservation: Heavy trucks stopping and starting repeatedly at red signals exert immense horizontal shear forces on intersection pavement. Under high temperatures, this causes severe asphalt shoving and rutting. FSP maintains truck momentum, preserving pavement assets and reducing municipal maintenance costs.
- Air Quality & Fuel Economy: A stopped 80,000 lb truck consumes over 0.5 gallons of diesel fuel simply accelerating back to 45 mph. Granting green extension to freight vehicles dramatically cuts corridor greenhouse gas and particulate emissions.
Cabinet Wiring, Controller Programming & Field Verification
Senior technicians must be proficient in configuring TSP/FSP logic within NEMA TS2 and ATC controller assemblies:
- Hardware Detector Inputs: Dedicated priority detector channels are wired to the controller's auxiliary input terminals or mapped via NEMA TS2 SDLC Bus 1 to input assembly slots. Technicians configure these channels in the controller firmware as Priority Call Inputs (Priority 1 through 6), assigning lower priority ranking than Emergency Preemption inputs.
- Priority Split Configuration: For coordinated phases, technicians program the Maximum Priority Extension (typically 10 to 15 seconds) and define the Reservice Time (the minimum elapsed time required between consecutive priority grants on the same phase, preventing a single bus route from dominating the intersection).
- Pedestrian Safety Verification: Technicians must verify that pedestrian clearance intervals are fully protected. Under no circumstances should the controller truncate a Flashing Don't Walk interval during a TSP call. Field tests must confirm that if a pedestrian call is active, an approaching bus receives early green only after the pedestrian walk and clearance timers reach zero.
What primary operational condition is evaluated under "conditional TSP" logic to prevent unnecessary delay to general cross-street traffic?