Vehicle-to-infrastructure (V2I) safety applications : performance requirements, vol. 7, stop sign gap assist (SSGA).
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This report, Volume 7 of a seven-part series by the U.S. Department of Transportation, establishes the performance requirements for the Stop Sign Gap Assist (SSGA) Vehicle-to-Infrastructure (V2I) safety application. The research addresses the safety challenge at intersections where minor roads are controlled by stop signs while major roads have free-flowing traffic. The primary motivation is to assist drivers on minor roads in safely traversing or entering major roads by providing real-time information about approaching cross-traffic, thereby helping drivers identify unsafe gaps and prevent potential crashes. The document aims to ensure that roadside and in-vehicle advisories, alerts, and warnings are consistent, coordinated, and non-conflicting, despite the likelihood that infrastructure and vehicle components will be developed by different stakeholders, such as public agencies and private manufacturers. The methodology involves transforming previously developed Concepts of Operations and System Requirements into specific performance requirements for both infrastructure and vehicle application components. The report defines a V2I System Functional Architecture comprising infrastructure components (sensors, roadside signage, traffic signal controllers) and vehicle components (in-vehicle sensors, driver warning systems) that communicate via wireless data interfaces, primarily Dedicated Short Range Communications (DSRC). The authors developed a framework for coordinating message delivery, utilizing swim lane and sequence diagrams to illustrate data flow, hazard assessment decision trees, and the issuance of advisories, alerts, and warnings. The requirements are structured with unique identifiers and categorized by interfaces, functional needs, data inputs/outputs, and performance metrics. Verification methods for these requirements include analysis, demonstration, inspection, and testing. The findings detail the specific performance requirements for the SSGA application’s infrastructure and vehicle components. The infrastructure component is required to capture data from roadside sensors and process it to determine potential crash hazards, issuing messages through dynamic message signs visible to all approaching vehicles. The vehicle component processes in-vehicle data and wireless messages to issue driver-specific warnings. A critical finding is the requirement for message harmonization: vehicle-specific messages must never be less cautious than roadside messages and must never conflict with them. For instance, a vehicle with a high rollover risk may recommend a lower safe speed than the general infrastructure message, but a standard vehicle must not recommend a higher speed. The report also specifies candidate data elements for message exchanges to ensure synchronized data handling between the two components. The significance of this work lies in providing a standardized technical foundation for the deployment of connected vehicle safety applications. By defining clear performance requirements for both infrastructure and vehicle sides, the report facilitates interoperability and ensures that safety messages effectively capture driver attention without causing confusion. This coordination is essential for the successful implementation of V2I technologies, as it bridges the gap between public infrastructure development and private vehicle manufacturing. The document serves as a reference for developers, manufacturers, and transportation agencies to ensure that the SSGA application achieves its safety objectives by delivering timely, accurate, and consistent hazard warnings to drivers.
Key finding
The Stop Sign Gap Assist application requires coordinated infrastructure and vehicle components to deliver consistent advisories, alerts, and warnings that assist drivers in identifying unsafe gaps in cross-traffic at stop-controlled intersections.
Methodology
other
Provenance
The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 19 | 2026-06-11 |
| verify | success | — | — | — | 2 | 2026-06-10 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.
Topics
Ranked by relevance to this paper. Hover a topic for its definition.