Library
Research Reports | Technical | Basic
DSRC and Proof of Concept Test
DSRC Frequently Asked Questions
A clear explanation of DSRC technology and why it is the most feasible current communications technology for IntelliDriveSM active safety applications.
2010
IntelliDriveSM Enabling Devices with DSRC Workshop
The workshop was held on May 6, 2010 following the closing plenary session of the ITSA 20th Annual Meeting & Exposition at the Hilton Americas in Houston, TX from 1:00pm - 5:00pm CST. The workshop was open to all interested parties in the automotive, telecommunications, consumer electronics, and other industries. It attracted over 60 participants, including device manufacturers, applications developers, and industry representatives. Below is a copy of the presentation, workshop summaries and a summary of Input from industry stakeholders:
2009
Noblis. March 2009.
This White Paper presents "order of magnitude" estimates of the number of roadside DSRC locations that would be required for three different deployment scenarios:
- To support only V2V safety applications
- To support V2I intersection safety applications
- To equip toll roads and HOT lanes
The number of roadside DSRC locations required in each case is referred to as the DSRC footprint requirement.
VII Consortium. May 2009. FHWA-JPO-09-003.
The executive summary is intended for executives and managers of organizations interested in the deployment of IntelliDriveSM. This report summarizes a program of work resulting from a Cooperative Agreement between USDOT and the VII Consortium to develop and test a Proof of Concept VII system based on DSRC wireless communication between an infrastructure and mobile terminals. It supports applications for improvement in safety and mobility and enables other commercial applications. Key findings and recommendations for further work are presented.
VII Consortium. May 2009. FHWA-JPO-09-043.
This final report describes the objectives and the approach to the testing of the VII Proof of Concept system. Summaries of the vehicle-related test results and findings for both the major system functions and the applications designed for the system are presented, along with recommendations for system improvements.
VII Consortium. May 2009. FHWA-JPO-09-017.
This report provides the technical description of the VII system developed for the Cooperative Agreement VII Program between the USDOT and the VII Consortium. The basic architectural elements are summarized, and detailed descriptions of the hardware and software systems are provided, along with the descriptions of the applications used to assess the system performance and operation.
Booz Allen Hamilton. Feb. 2009.
This document provides an overview of the key infrastructure-related findings and recommendations from the POC testing. This volume is intended for executives and managers of organizations interested in the deployment of IntelliDriveSM.
Booz Allen Hamilton. Feb. 2009.
This report describes the overall approach undertaken to prove the infrastructure-related VII concepts through a structured testing program. It describes the overall experimental design used in proving the VII concept by providing an overview of the system architecture and design of systems, subsystems, and components, as well as the public sector applications developed to prove some of the system concepts. This volume is intended for engineering managers and practicing engineers interested in the design and development of IntelliDriveSM systems and applications.
2008
USDOT ITS Joint Program Office. Apr. 2008.
This document will continue to evolve as clearer answers to basic questions about capabilities and operation concepts are developed, and key issues are resolved.
2007
System Requirements
Booz Allen Hamilton. Apr. 2007.
This document addresses the functional and facilities requirements for the Network Subsystem. The main focus of this document is the Proof of Concept system functionality.
Booz Allen Hamilton. Feb. 2007.
This document addresses the top-level software interface requirements for the I-06 interface as specified in the VII National System Requirements.
Booz Allen Hamilton. Feb. 2007.
This document addresses the top-level software interface requirements for the X-031, X-032 and X-033 interfaces as specified in the VII National System Requirements.
Booz Allen Hamilton. Feb. 2007.
This document provides the formal definitions for terms used in the Interface Requirement Specifications for the VII infrastructure.
Booz Allen Hamilton. Feb. 2007.
This document provides the forma definitions for terms used in the Subsystem Specifications and subsequent Design Documents for the VII infrastructure.
Enterprise Network Operations Center (ENOC) Subsystem
The following ENOC subsystem requirements were developed by Booz Allen Hamilton, for proof of Concept Testing.
- ENOC System Specification (SSS)
- ENOC to Administrative User [X-011] Software Interface Requirements Specification
- ENOC to Managed Entity (ME) [Managed Entity] Software Interface Requirements Specification
- ENOC to Managed Network Element (MNE) [I-08 and I-11] Software Interface Requirements Specification
- ENOC to Service Delivery Node (SDN) Subsystem [1-11] Software Interface Requirements Specification
Application Requirements
The following application requirements were developed by Booz Allen Hamilton, for proof of concept testing.
- POC Applications Concept of Operations Version 1.4
- Corridor Management Load Balancing POC Application Requirements Version 1.2
- Corridor Management Planning Assistance POC Application Requirements Version 1.2
- Pothole Detection POC Application Requirements Version 1.2
- Ramp Metering POC Application Requirements Version 1.2
- Signal Timing Operation POC Application Requirements Version 1.2
- Traveler Information POC Application Requirements Version 1.2
2006
Booz Allen Hamilton. Sept. 2006.
The purpose of this document is to provide a basis for the planning, design, implementation and operation of the national IntelliDriveSM (VII) system. The Concept of Operations (ConOps) is the first step in the systems engineering process. It lists the functions to be performed by the envisioned system, and identifies the roles and responsibilities of the project stakeholders in the operation of the system.
Booz Allen Hamilton. Jul. 2006.
This report documents the results of the VII Communications Analysis task. The objective of this task was to explore available backhaul options for the USDOT's VII network, on a national and regional scale, and determine rough order magnitude cost estimates for those options that were found to be most appropriate.
Booz Allen Hamilton. May 2006.
This document presents 11 Day-1 use case scenarios.
2005
SIRIT Technologies. Jan. 2005.
A White Paper making the case for use of DSRC communication technology in ITS system deployments.