Concept Development and Needs Identification for Intelligent Network Flow Optimization (INFLO)
Functional and Performance Requirements and Data and Communication Needs Walkthrough Workbook
www.its.dot.gov
August 9, 2012
1.1.1.1.1.1
NoticeThis document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof.
ITS Joint Program Office
Research and Innovative Technology Administration
U.S. Department of Transportation
Table of Contents
1 Introduction 5
1.1 Walkthrough Objectives 5
1.2 Walkthrough Preparation 5
2 Agenda 6
3 INFLO Background and Methodology 7
4 Functional and Performance Requirements Mapped to User Needs 8
4.1 Dynamic Speed Harmonization (SPD-HARM) Requirements 8
4.1.1 SPD-HARM User Need 1 & 8: Know the recommended speed to travel & Communicate relevant information to vehicle operator 9
4.1.2 SPD-HARM User Need 2 & 8: Know which lane to be in & Communicate relevant information to vehicle operator 11
4.1.3 SPD-HARM User Need 3 & 8: Know why the given speed is being recommended & Communicate relevant information to vehicle operator 12
4.1.4 SPD-HARM User Need 4: Personal data to remain private and secure 13
4.1.5 SPD-HARM User Need 5: Collect relevant vehicle data 14
4.1.6 SPD-HARM User Need 6: Disseminate relevant vehicle data to other vehicles or systems 16
4.1.7 SPD-HARM User Need 7: Receive relevant information from other vehicles or systems 18
4.1.8 SPD-HARM User Need 9: Receive multi-source data 19
4.1.9 SPD-HARM User Need 10: Process multi-source data 21
4.1.10 SPD-HARM User Need 11: Generate speed harmonization strategies 27
4.1.11 SPD-HARM User Need 12: Disseminate speed harmonization recommendations and information to connected vehicles/devices 29
4.1.12 SPD-HARM User Need 13: Analyze performance of SPD-HARM system 31
4.1.13 SPD-HARM User Need 14: Collect SPD-HARM data and disseminate relevant information to other dynamic mobility applications 34
4.2 Queue Warning (Q-WARN) Requirements 35
4.2.1 Q-WARN User Need 1 & 8: Know of a downstream traffic queue in sufficient time to react safely & Communicate queue warning to vehicle operator 36
4.2.2 Q-WARN User Need 2 & 8: Know what actions to take to respond to an impending queue & Communicate queue warning to vehicle operator 38
4.2.3 Q-WARN User Need 3: Personal data to remain private and secure 40
4.2.4 Q-WARN User Need 4: Detect a queued state 41
4.2.5 Q-WARN User Need 5: Disseminate queued status alert to upstream vehicles and other systems 43
4.2.6 Q-WARN User Need 6: Receive relevant queue information from other vehicles or systems 44
4.2.7 Q-WARN User Need 7: Generate queue response strategies 45
4.2.8 Q-WARN User Need 9: Collect relevant traffic, road conditions, and weather data 47
4.2.9 Q-WARN User Need 10: Disseminate relevant traffic, road condition, and weather data to vehicles 49
4.2.10 Q-WARN User Need 11: Detect a formed queue 50
4.2.11 Q-WARN User Need 12: Predict impending queue formation 54
4.2.12 Q-WARN User Need 13: Generate queue warning response strategies for upstream vehicles 58
4.2.13 Q-WARN User Need 14: Disseminate queue warnings 61
4.2.14 Q-WARN User Need 15: Analyze performance of the Q-WARN system 62
4.2.15 Q-WARN User Need 17: Disseminate signal phasing information to approaching vehicles 64
4.2.16 Q-WARN User Need 18: Collect Q-WARN data and disseminate relevant information to other dynamic mobility applications 65
4.2.17 Q-WARN User Need 19: Collect and aggregate Q-WARN related data and disseminate to freeway and arterial traffic management entities 66
4.3 Cooperative Adaptive Cruise Control (CACC) Requirements 67
4.3.1 CACC User Need 1: Join a CACC platoon 68
4.3.2 CACC User Need 2: Establish or accept a speed and gap policy 70
4.3.3 CACC User Need 3: Exit a CACC platoon 71
4.3.4 CACC User Need 4: Personal data to remain private and secure 73
4.3.5 CACC User Need 5: Collect relevant vehicle data 74
4.3.6 CACC User Need 6: Disseminate relevant vehicle data to other vehicles or systems 76
4.3.7 CACC User Need 7: Receive relevant information from other vehicles or systems 77
4.3.8 CACC User Need 8: Communicate actions and other relevant information to vehicle operator 79
4.3.9 CACC User Need 9: Generate cruise control strategies 80
4.3.10 CACC User Need 10: Automatically engage vehicle throttle and other equipment to enact cruise control strategies 82
4.3.11 CACC User Need 11: Integrate external commands from traffic management entities with self- or platoon-generated cruise control strategies 83
4.3.12 CACC User Need 12: Receive multi-source data 84
4.3.13 CACC User Need 13: Process multi-source data 86
4.3.14 CACC User Need 14: Generate speed or gap strategies 87
4.3.15 CACC User Need 15: Disseminate speed and gap recommendations and other information to connected vehicles 89
4.3.16 CACC User Need 16: Analyze performance of CACC system 90
4.3.17 CACC User Need 17: Collect CACC data and disseminate relevant information to other dynamic mobility applications 92
5 Data and Communication Needs 93
5.1 SPD-HARM 93
5.2 Q-WARN 98
5.3 CACC 103
1 Introduction
This document is the Intelligent Network Flow Optimization (INFLO) Functional and Performance Requirements and Data and Communication Needs walkthrough workbook to be reviewed and updated by INFLO stakeholders participating in the August 9, 2012 Requirements walkthrough webinar.
1.1 Walkthrough Objectives
The objective of this walkthrough is to obtain INFLO stakeholder feedback on the draft Functional and Performance Requirements and Data and Communication Needs report from a functional, technical, management, and implementation perspective. Specifically, your input into the completeness, accuracy, and reasonableness of the requirements and data and communication needs identified is of particular value.
The requirements are intended to specify what the INFLO bundle must accomplish to produce the required behaviors and system results as described in the Concept of Operations. They were developed to be traceable to the user needs this stakeholder group developed during previous INFLO workshops.
Feedback from this walkthrough will be used to finalize the INFLO Functional and Performance Requirements and Data and Communication Needs report.
1.2 Walkthrough Preparation
This workbook has been structured to address key sections of the draft Functional and Performance Requirements and Data and Communication Needs document.
The research team requests walk through participants to review the sections of the workbook and corresponding sections of the document prior to the discussion on August 9. This workbook is organized into the following sections:
1. Introduction
2. Walkthrough Workshop Agenda
3. INFLO Background
4. Functional and Performance Requirements (SPD-HARM, Q-WARN, CACC)
5. Data and Communication Needs (SPD-HARM, Q-WARN, CACC)
Joint Program Office
U.S. Department of Transportation, Research and Innovative Technology Administration
INFLO Requirements Walkthrough Workbook | 30
Chapter 2 – Referenced Documents
2 Agenda
Intelligent Network Flow Optimization (INFLO)
Functional and Performance Requirements and Data and Communication Needs Walkthrough Webinar
Thursday, August 9, 2012, 1:00 p.m. – 4:00 p.m. (Eastern)
1:00 - 1:10 / 1. Welcome and Introductions2. Meeting Objectives
1:10 - 1:15 / 3. High-Level Discussion of INFLO Systems and Subsystems
1:15 - 1:45 / 4. SPD-HARM Functional and Performance Requirements
1:45 - 2:15 / 5. Q-WARN Functional and Performance Requirements
2:15 - 2:45 / 6. CACC Functional and Performance Requirements
2:45 - 3:00 / Break
3:00 - 3:20 / 7. SPD-HARM Data and Communication Needs
3:20 - 3:40 / 8. Q-WARN Data and Communication Needs
3:40 - 4:00 / 9. CACC Data and Communication Needs
4:00 / 10. Conclusion/Wrap-Up
Joint Program Office
U.S. Department of Transportation, Research and Innovative Technology Administration
INFLO Requirements Walkthrough Workbook | 30
3 INFLO Background and Methodology
In support of USDOT’s Intelligent Transportation Systems’ (ITS) Mobility Program, several of the Department’s agencies are fully engaged in exploiting active interaction between fixed and mobile transportation system entities both in the way new forms of data are being exchanged and in the opportunities that are afforded to extend the geographic scope, precision and control of our Nation’s surface transportation system. An important initiative within the framework of this strategic effort is the Dynamic Mobility Applications (DMA) program which, in part, seeks to create applications that fully leverage frequently collected and rapidly disseminated multi-source data gathered from connected travelers, vehicles and infrastructure, and that increase efficiency and improve individual mobility while reducing negative environmental impacts and safety risks. Under this program, the USDOT has identified a portfolio of ten high-priority mobility applications, including a common bundle collectively identified as Intelligent Network Flow Optimization, or INFLO.
The purpose of the INFLO project is to facilitate concept development and needs refinement for the INFLO applications and to assess their readiness for development and testing. The three applications under the INFLO bundle will ultimately help to maximize roadway system productivity, enhance roadway safety and capacity, and reduce overall fuel consumption. These three applications are:
· Queue Warning (Q-WARN);
· Dynamic Speed Harmonization (SPD-HARM); and
· Cooperative Adaptive Cruise Control (CACC).
In selecting these applications, the USDOT sought applications that have the potential to be transformative (i.e., that they result in substantial roadway mobility and safety improvements), that are achievable in the near-term, and that leverage the opportunities provided through connected entities.
This philosophy of identifying applications that can be deployed in the near-term is in keeping with the USDOT’s goals of quickly moving these applications from the research stage to adoption in the field.
The Functional and Performance Requirements and Data and Communication Needs document, which this walkthrough workbook will help to develop, is intended to communicate the requirements of the INFLO bundle of applications to the technical community who may develop and refine the applications or implement operational systems based on the concept. The Requirements are intended to support the development and eventual near-term deployment of subsets of or the entire INFLO application bundle. Moreover, the Requirements report is a living document and will be coordinated in a collaborative manner with agency, industry, and public stakeholders to ensure the viability of the concepts represented.
Once completed, the INFLO Requirements Report will be used to facilitate the identification and assessment of key technical and non-technical issues related to field-testing the INFLO bundle and its individual component applications.
Joint Program Office
U.S. Department of Transportation, Research and Innovative Technology Administration
INFLO Requirements Walkthrough Workbook | 30
4 Functional and Performance Requirements Mapped to User Needs
In this section, INFLO requirements are organized by user need addressed, as identified in the INFLO ConOps. Additionally, the near-, mid-, and long-term achievability of each requirement is indicated in the Application Evolution State columns, where near-term reflects a 1-10 year horizon, mid-term reflects a 10-20 year horizon, and long-term reflects a 20+ year horizon. Key systems and subsystems involved in the given requirement are indicated in the next column. Finally, the type of requirement (whether functional, performance, system-to-system interface, security, or privacy) is indicated in the second-to-last column.
You may indicate in the rightmost column whether the requirement is acceptable as written, requires modification, or should be removed completely. Finally, blank rows at the bottom of the matrices have been provided for you to fill in new requirements that you think should be included.
4.1 Dynamic Speed Harmonization (SPD-HARM) Requirements
The following is an overview of the key systems and subsystems that will be referenced by the SPD-HARM requirements:
· Connected Vehicle-based SPD-HARM Application – the core in-vehicle application that processes real-time data and makes speed harmonization decisions for the vehicle
· Connected Vehicle Driver Interface System – the in-vehicle system that displays system output and receives user input
· Connected Vehicle Communication System – the in-vehicle system that communicates wirelessly with infrastructure and other Connected Vehicles to send and receive data and instructions (may include DSRC, cellular communication, or WiFi)
· On-board Diagnostic (OBD) reader/Vehicle Bus System – the in-vehicle systems that read real-time vehicle data (speed, heading, temperature, etc.) to make available to the SPD-HARM Application
· Traffic Management Entity (TME) – the generalized system (which could refer to a TMC) that is responsible for making segment-specific and network-wide target speed recommendations for SPD-HARM-enabled Connected Vehicles and communicating these recommendations via I2V communications
· TME-based SPD-HARM Application – the core infrastructure-based application that processes real-time and historical transportation network data to determine network efficient speed harmonization recommendations
· V2I/I2V Roadside Equipment – the infrastructure-based communication systems that receive and send information between SPD-HARM-enabled Connected Vehicles and the TME (may include DSRC, cellular communication, or WiFi)
· TME Performance Monitoring Subsystem – the subsystem of the TME-based SPD-HARM Application that monitors the effectiveness of speed harmonization recommendations and policies on the transportation network using safety and mobility measures
· Data Environments – the systems that receive, store, and summarize real-time data gathered from Connected Vehicles and Infrastructure to be made available to various Dynamic Mobility Applications
4.1.1 SPD-HARM User Need 1 & 8: Know the recommended speed to travel & Communicate relevant information to vehicle operator
1. Know the recommended speed to travel, 8. Communicate relevant information to vehicle operator /Req ID / Application Evolution State / Systems/Subsystems Involved / Functional Requirement / Requirement Type / Accept / Modify / Delete /
Near / Mid / Long /
RS-1.1 / x / x / x / Connected Vehicle-based SPD-HARM application, Connected Vehicle driver interface system / The Connected Vehicle-based SPD-HARM application shall pass target speed recommendations to the driver interface system. / System-to-system Interface
RS-1.2 / x / x / x / Connected Vehicle driver interface system / The Connected Vehicle driver interface system shall communicate individualized target speed recommendations to the driver. / Functional
RS-1.2.1 / x / x / x / Connected Vehicle driver interface system / The Connected Vehicle driver interface system shall communicate individualized target speed recommendations to the driver utilizing auditory, visual, or haptic alerts and on-screen messages. / Human-Machine Interface