VII California Team Meeting

1
VII California Team Meeting

• May 1, 2007
• Richmond Field Station (PATH)

2
Agenda Items

• Federal Message
• We are an official site - what that may mean 
  (discussion)
• Demos 
• ITSA
• Demo Video
• Booth
• TRB Summer Meeting
• 24 July
• Testbed Build Items
• Recent ITS JPO Visit and Lessons Learned
  (especially with system reliability)
• Build Status / Progress
• Lessons Learned in Prepping for ITS JPO Visit
• Brief progress reports on
• Intersection build
• Maintenance
• Backhaul
• To include discussion on Wireless Silicon Valley
• WiMax installation
• MCNU order

3
Federal Message We are official

• Discussion

4
DemosITSA Video Handout (Joel) Booth
Discussion (Bill, Jim)TRB Summer Meeting
5
TRB Summer Meeting

• Three TRB Committees ? 100 200 Attendees
• ITS Committee
• Vehicle-Highway Automation Committee (V-HA)
• Traffic Signal Systems Committee (TSSC)
• Important Government Stakeholders
• US DOT (RITA - ITS JPO, FHWA)
• Caltrans
• Other
• Detailed Arrangements Still in Process
• Hotel TBD
• Exact Itineraries for V-HA and TSSC
• Demo
• However
• Fulcrum and Attraction is 24 July Demo
• Sunday, July 22 - TSSC subcommittee meetings
• Monday, July 23 - Full-day TSSC workshop on VII
  for traffic signal control
• Tuesday, July 24

6
Build Status / Progress

• Ashkan Sharafsaleh
• Joel VanderWerf
• Others

7
First, a Congratulations

• This was an opportunity captured
• For VII California
• For each of the participating organizations
• For VII

8
Maintenance Issues

• California Ave T1 went down frequently
• Router replaced more than once
• Has been ok for several weeks
• Re-ran fiber at Page Mill Charleston
• Broken by video installers
• New fiber converters at Quarry
• Curtner and Quarry have Denso issues
• May need to swap out WRMs

9
Signal Strength Issues

• Radios on 101 don't have good range
• Can't hear them in SB direction (RSUs are on NB
  direction)
• Had to change demo route
• Page Mill RSU signal weak
• Soft-reboot seemed to fix it at least once

10
Software Issues

• Need better signage filtering in vehicle
• Too many messages
• Directionality is not always clear
• E.g. travel time from freeway exit to arterial
• Broadcast rate is not the same as display rate
• Looping vehicle confused the demo probe server
• Use the 511 server in future
• 511 probe server is in active development

11
Recommended List For 10 New MCNUs
12
New Installations on US-101

• Brittan and Marsh Road
• PATH RSEs
• Digi-Router at Marsh Road
• T1 at Brittan
• Marsh Road will be used for Curve Over-Speed
  experiments

13
WiMax Installation at Page Mill and El Camino Real

• Progress and Plans
• DCX identified network switch with copper and
  fiber network ports, to be purchased and bench
  tested
• Pole identified for subscriber unit, wireless
  power verified
• Base station needs to be mounted on mast arm due
  to antenna radiation pattern, subscriber unit at
  the top.
• Network switch and power distribution placed on
  pole (not mast arm) midway between subscriber and
  base station (in separate enclosures)
• The antennas and RF unit need to be mounted on
  fixed base due to the 9" lead limit

14
Nominal Design
15
Next Steps

• Gather equipment for bench test and
  bracket/mount/enclosure design and fabrication
• Verify Caltrans jurisdiction over pole
• Verify power and fiber pull distances from signal
  cabinet to top of pole and position of access
  port out of pole
• Check on the need to pull fiber from top of pole
  to mast arm (or outside conduit to allow copper
  network cabling to switch)
• Purchase AC to DC power supply (to reside in the
  signal cabinet) and bench test
• DCX to provide addresses and access to the
  Internet, PATH to develop backhaul software for
  the RSU
• DCX to arbitrate bandwidth usage internally
  (current backhaul application very small
  bandwidth, future applications unknown)

16
Other

• Additional Backhaul Discussion
• Interface to Wireless Silicon Valley?
• MCNU Order

17
Website A Work in Progress / Needs Information

• www.viicalifornia.org

18
Research Status

• Tolling (Telvent)
• Radio Field Measurements (PATH)

19
Bay Area 511 VII

• Near Term tasks
• Probe Visualizer
• Link data source
• Virtual Toll Plaza
• Longer Term Options
• Virtual HOT lanes

20
Bay Area 511 VII

• Probe Data Needs
• Multiple Snapshots in messages (bread crumbs)
• Standardization in provided speed
• Average over time since last snapshot
• Speed at time of snapshot
• Recent/Smoothed average

21
Bay Area 511 VII

• Where will Probe Messages go? Near Term
• To CCIT
• To 511 TIC
• Which message set will we use?
• For Now
• Beyond

22
VII Tolling National Concept of Operations

• Effort underway by OmniAir, sponsored by USDOT
• Develop a Concept of Operations
• Supports the POC in SE Michigan
• Web Conference and workshop to get toll industry
  input

23
POC Goals Objectives (Tolling)

• Financial Transaction with Fast Moving Vehicle
  Fixed Infrastructure
• Securely Conduct Transaction with VII System User
  (Toll Agency) and Vehicle Driver
• Multiple Accounts (Including Debit Accounts) Can
  Be Used
• Record Travel Lane
• Report Vehicle Classification

24
VII Tolling Use Case in POC
25
POC VII Tolling

• Demonstrate how VII tolling will work
• Will not be connected to a back office
• Will not include enforcement

26
VII Tolling ConOps Status

• Detailed outline of ConOps
• Identified people who will review and provide
  input
• Draft ConOps due in June
• Second draft due in September
• Final document in October

27
How Does National Effort Relate to VII CA?

• ConOps will reflect stakeholder views of VII
  Tolling
• VII CA should be compatible
• Applications will be developed for POC
• How does VII CA application relate
• Is there still a need for VII CA application?
• POC does not incorporate back office
• POC does not address enforcement

28
Field Measurements of Vehicle to Roadside
Communication Performance

• Susan R. Dickey4/27/2007

29
Equipment Set-Up

• Assembly of three gumstix netduo expansion boards

• Antenna placement with 8 active OBUs on one
  vehicle

30
Location of RSU

• Test 1
• Fixed loads at receiver
• RSU _at_ 6th and Brannan in San Francisco
• Test 2
• Fixed sending interval
• RSU _at_ 3rd and Townsend in San Francisco

31
Experiment Results Test 1 (1)

• Average of remote and local RSSI by GPS location
• The recv RSSI is higher when vehicle is closer to
  RSU

32
Experiment Results Test 1 (2)

• Probability of successful round trip transmission
• as a function of the interval between packet
  sends, for 1, 2, 4 and 8 nodes
• with varying packet sizes of 200, 400 and 800
  Bytes

33
Experiment Results Test 1 (3)

• Time (in seconds) until the first 8000 bytes has
  been transmitted
• as a function of the interval between packet
  sends, for 1, 2, 4 and nodes
• with varying packet sizes of 200, 400 and 800
  Bytes

34
Experiment Results Test 2 (1)

• Transaction delay for 8000 byte transaction as a
  function of data rate
• for 9 nodes, packet size 200 bytes
• with various testing routes, 10 millisecond
  interval between packet sends
• Transaction jitter (standard deviation of delay)
  as a function of data rate
• for 9 nodes, packet size 200 bytes
• with various testing routes, 10 millisecond
  interval between packet sends

35
Experiment Results Test 2 (2)

• Transaction delay for 8000 byte transaction as a
  function of data rate
• for 9 nodes, packet size 1400 bytes
• with various testing routes, 10 millisecond
  interval between packet sends
• Transaction jitter (standard deviation of delay)
  as a function of data rate
• for 9 nodes, packet size 1400 bytes
• with various testing routes, 10 millisecond
  interval between packet sends

36
Analysis (1)
R1 Trans. time decreases as sending interval
increases. Reason If sending interval is too
short (rate is too high), there are many
collisions. R2 Trans. time increases as sending
interval increases. Reason Sending interval is
already long enough for contention resolution.
Thus, channel is not well utilized (bandwidth
lost). There is an optimal sending interval.
37
Analysis (2)
R1 Prob. of successful TX increases (up to a
bounded prob. p) as sending interval
increases. Reason As sending interval increases,
there are fewer collisions. R2 Prob. of
successful TX approaches a limit when sending
interval keeps increasing. Reason Sending
interval is already long enough for contention
resolution. Thus, prob. of successful TX will not
increase instead, it is bounded by p, which is
decided by PHY layer performance.
38
Future Work

• The disadvantages of application layer only
  studies are obvious
• Physical layer effects that may be contributing
  to poor performance must be inferred indirectly.
• It is necessary to be able to integrate data
  acquired at all layers of the network stack for
  complete understanding.
• We plan to use this equipment to carry out
  further vehicle to roadside and vehicle to
  vehicle tests at VII California RSUs, in
  conjunction with more physical layer testing.

39
Actions / Next Meeting?