New 1609 Project Proposal: Application Oriented Communications Management Comm Manager

1
New 1609 Project Proposal Application Oriented
Communications Management(Comm Manager)

• April/May 2008

John Moring [phone] jmoring_at_technocom-wirel
ess.com
2
Overview

• Propose a new 1609 standard for Application
  Oriented Communications Management
• Need
• Relationship to other standards and activities
• Features

3
Current Situation

• 1609 assumes an abstract Application layer
  above 1609.3
• But does not specify it
• 1609.1 was intended to provide guidance to
  application developers
• But has not succeeded
• Application developers left without a standard
  interface to 1609-compliant hardware-software
• Some critical system-level features were not
  appropriate to include in existing standards
• Application priority validation on registration
• Coordination among multiple simultaneous
  applications
• Session management in overlapping RSE coverage
  areas
• Inter-layer primitives are described in 1609 but
  not specified
• Etc.

4
Advantages of a Comm Manager

• Allows uniform application development regardless
  of the underlying hardware and software
  configuration
• Makes developers lives easier radio functions
  abstracted
• Provides multi-application coordination features
• E.g., two applications registered for one PSID
• Provides a place to specify other missing
  functionality
• E.g., validation of application priority on
  registration
• Removes some application-related complexity from
  1609.3
• Network Services spec should be communications
  oriented vs application oriented
• Simplifies stack and isolates it from
  requirements of future applications

5
Features of a Comm Manager

• Provides coordinated interface for WAVE functions
• 1609.3 control plane (WME)
• 1609.3 data plane (WSMP optionally UDP TCP)
• 1609.2 security
• Provides general application-level services,
  e.g.,
• Inter-application coordination
• Application notification/registration
• Remote, local
• Session persistence across RSEs
• Message queuing, replay/dispatch, and security
• Service discovery
• Link management
• Geo- and movement-based services
• Allows a partitioning between third party apps
  and device kernel
• A place to specify other necessary device
  features not part of a communications stack
• Comm Manager need not be required for every
  device/application
• E.g., a single application could run via
  vendor-specific device interface

6
Strawman Comm Manager
Existing SAPs
7
Comm Manager in VII

• Similar concept implemented, deployed, and tested
  in Proof of Concept
• Lessons learned reflected in this proposal

8
Potential Features

• Security features
• Validate application priority level on
  registration
• WBSS management features
• Manage multiple WBSS through multiplexing or
  preemption
• Message handling features
• Periodic repeated WSM transmission
• Location-aware communications
• Etc.

9
Proposed PAR

• The scope of this standard is to specify
  communication management services for Wireless
  Access in Vehicular Environments (WAVE).
• The purpose of this standard is to define
  communication management services in support of
  wireless connectivity among vehicle-based
  devices, and between fixed roadside devices and
  vehicle-based devices for Wireless Access in
  Vehicular Environments.

10
What Next?

• Working Group agreement
• PAR request
• Draft standard by next WG meeting