Review of Open Platform Meeting at Volpe NTSC

1
Review of Open Platform Meeting at Volpe NTSC

• Presented at 1609 Meeting
• August 2008

2
Overview of Meeting

• Held August 5 at Volpe Center in Cambridge, MA
• Follow-up to Communications Roundtable held at
  DOT on May 22
• Mix of Participants
• Some involved in DSRC and VII
• Some Other Communications and General Industry
• Not All Were Familiar with VII or DSRC
• Mike Schagrin of RITA Discussed New VII Goals
• Reduce crash rate by 90 by 2040
• Total 360 situational awareness
• Goals of Meeting
• Define Open Platform
• How to create 360 situational awareness
• Identify interfaces needed for interoperability
  and safety
• Discuss how to encourage innovation by industry
• Discuss how to accommodate technology evolution

3
General Communications Goals Going Forward

• Want open protocols based on industry standards
• Have to assume islands of RSE coverage, without a
  centralized network infrastructure
• May need to support passing data V-V-I for some
  applications (MANET, CARNET, mesh, and other
  mobile network concepts)
• Need to support factory installed, retrofit
  (dealer installed), and after-market applications
• Need to support near-term deployment of selected
  VII capabilities

4
VII Communications Objectives Discussed

• Based on open standards
• Need an open, flexible API
• API needs to define Quality of Service (QoS)
  parameters applicable to each communications path
• Needs to be based on standards for categories of
  apps

5
Discussions Around DSRC

• DSRC has the required capacity, latency,
  security, and other technical characteristics to
  support safety applications. DSRC will be used
  for V-V and V-I safety applications.
• Other communications media may be used for
  non-safety applications
• May want to re-examine DSRC channel plan to have
  one safety channel and one non-safety channel
• Avoid channel switching on the fly
• Conformance testing and certification critical to
  evolutionary deployment

6
VII Network Discussions

• No nationwide Federally funded network of RSEs
• Need revised VII Architecture
• Entire architecture has to support future apps
  not now envisioned
• Will need more state and local input
• Must support 3-5 year deployment
• Need ways to capture probe data and provide data
  to vehicles in this environment
• Need to address issues affected by a less-dense,
  islands of RSE coverage approach
• Security implementation
• Configuration management
• Maintenance
• Others

7
Other Issues Discussed

• Need new business model for VII deployment
• Need standards for classes of applications,
  especially safety applications
• Liability issues under different deployment
  scenarios
• Integrated vs. retrofit vs. after-market
• Impediments to achieving safety goal
• Business model for infrastructure deployment
• Completion of DSRC standards
• Documentation of specific safety requirements
• Positioning accuracy and integrity
• Accurate roadway maps
• Security and privacy implementation
• Impact of V-V penetration rate
• Need for standards or regulations related to HMI
• Options for development of standards and scope of
  standards needed

8
Potential Impacts on 1609

• May want to expand stack to work with other than
  802.11p
• Need to develop approaches for security
  implementation under this scenario
• Network management and CM also a challenge
• Need an API that supports variety of apps and
  variety of comms paths
• Expansion of Comms Mgr or separate?