|
Hardware | Functions Performed
Hardware
Figure 3-1 VII California World Congress
Demo Architecture
Part of Figure 3-1 is an architectural configuration
of roadside equipment (RSE), which will be developed prior to the
World Congress but are intended for use for VII California past that
milestone. At the heart of the RSE are again WRM, a port or router
to landside operations and a specialized local safety processor with
interface into the controller, e.g., Type 170 traffic signal controller.
Outside
the WRM, the RSU may also include other potential principal components:
- DSRC amp and antenna
o MCX coaxial DSRC antenna connector
- Other wireless transceivers: radio card plus amp and antenna
(e.g., 802.11b/g)
o MCX coaxial 802.11b/g antenna
- Connection to backhaul (e.g., 802.11-type wireless connection,
(General Packet Radio Service or GPRS modem, hardwire)
- Router/hub for network access and component integration
- Separate processor and/or connection to existing controller
o Serial connector for intersection controller or other processor,
as needed
- GPS for positioning and UTC time synchronization
o Including MCX coaxial GPS antenna connector
- Power
o 110 Volt power
o AC to DC power supply
- Connection point for ground
- Separate enclosure (potential): tradeoff between Type
332 cabinets or additional watertight unit
This is a joint PATH
and Caltrans activity. The above list of components is not yet
complete; therefore, RSU components and configuration will be defined
by PATH in conjunction with other VII California stakeholders.
Functions Performed
Development and Protoyping
This is a joint PATH and Caltrans activity, with significant stakeholder
input. PATH will acquire and install a Type 332A cabinet and
associated hardware at the University of California Richmond
Field Station (RFS) “intelligent intersection” facility.
The 332A cabinet is commonly found at Caltrans intersections and
roadsides and will serve as a prototype unit. From this unit,
stakeholders will have access to nominal RSU to develop their
interfaces.
Specific prototype development directions will include:
- Design of autonomous processors for each RSU to allow
minimal existing
infrastructure modification. This is will necessitate a robust
computational
platform, most likely a PC/104.
- Design of DSRC antenna and WRM integrated as transceiver subsystem
for
optimal performance and installation ease, connected by ethernet
to processor. Prior antenna design has not been optimized for
RSU.
- 802.11b/g amplifier and antenna coupled to the processor,
in anticipation of a collateral requirement that will require
provision of WiFi functionality for some VII services.
- GPRS serial port modem connection to processor for backhaul
connection, for data as well as RSU maintenance purposes.
- Disk storage, with requirement heavily dependent on use case
development.
- Embedded operating system for real-time communication response
and small software footprint. While at this (ConOps) stage, design
options are open; because VII involves safety-critical applications,
we will likely eschew the use of MS Windows, opting for a reliable,
robust RTOS.
Installation
This will be a Caltrans activity, supported
by PATH. Documentation will be developed to show prototype RSU
design and bill of materials, to include antennae, WAVE radios
and PC/104 processors in order to replicate basic elements of the
RFS prototype. At Caltrans’ discretion, Caltrans and PATH
will implement the first 1 – 2 RSU locations, and Caltrans
will implement the remaining testbed. There will be many site-specific
considerations in applying RSUs, e.g., antenna placement and optimization,
varying amounts available space within cabinets. Hence, while our
prototyping may specify the basic configuration, the field application
will require work and ingenuity from our Caltrans partners.
Maintenance
This will be a Caltrans activity, supported
by PATH for troubleshooting consultation.
Archiving
Data archiving will not be a requirement
of the roadside components. All archiving will be a center-based
activity.
Hardware | Functions
Performed |
