Vehicle Infrastructure Integration (VII)

Access to the VII MICHIGAN TESTBED

November 2008
Version 1.1

1 Introduction

This document, Access to the VII Michigan Testbed, sets the procedure for Third Parties to request access to the environment to conduct VII related Tests.  This is part of the U.S. Department of Transportation’s Vehicle Infrastructure Integration (VII) Post Proof of Concept activities.  It is intended as a living document, which will be continually edited and updated to reflect operational realities.

1.1 Scope

The purpose of this document is to provide an overview of the Michigan Testbed service capabilities and describe how Third Parties will request access to the environment to conduct their own tests.  Booz Allen Hamilton will minimize scheduling conflicts such that Researcher can be assured to have as clean a test environment as possible for the duration of their tests.  Booz Allen will notify Researchers of all Network Maintenance scheduled to take place within the environment, such that Researcher can plan accordingly. This document lays out expectations, organizational roles and responsibilities, as well as the policies and procedures required to Test within the Michigan Testbed.
Requesting Access to the VII Michigan Testbed is intended to be a living document which will be modified, as necessary, in light of operational experience to more fully support the needs of the US DOT and Third Parties wishing to test in the environment.

1.2 Document Overview

The document is organized as follows:

• Section 2 - Overview of services provided, including architectural overview of Michigan Testbed, location of the Michigan Testbed and its Network Components, and the capabilities of the network.
• Section 3 - Michigan Testbed Test Support, provides an overview of the support available to Researchers as they carry-out their Tests within the Michigan Testbed.
• Section 4 - Requesting Access to the  Michigan Testbed, provides procedures to be use, forms to be filled out, and  Michigan Testbed contact information.
• Section 5 - Network User Access, this section provides an overview of user requirements for connecting to the Network Services, such as sending messages to vehicles and subscribing to Probe Data.
• Section 6 - Principles of Operation, defines the ground rules and basic expectations for Michigan Testbed access and utilization.
• Section 7 - Liability
• Appendices - Include an RSE Net work Map, Request form, RSE List, and additional information.

2 Network Overview

2.1 Architectural overview of  Michigan Testbed Elements

The diagram below provides an architectural overview of the Michigan Testbed components.  These components include 55 Roadside Equipment (RSE) Units, 11 along freeways and 44 along Arterials, the Michigan Service Delivery Node (MI SDN) and the Michigan Network Access Point (MI NAP).   The Enterprise Network Operation Center (ENOC), located in Herndon VA, will monitor and Manage the  Michigan Testbed components.

RSE’s are connected to the SDN via one of the following three (3) Backhaul Communications Technologies:

• WiMax: 19 sites
• Wireline: 20 sites
• 3G: 16 sites

WiMAX provides a maximum backhaul speed of 6 Mbps.  Speeds very based on the distance between the RSE and the WiMAX Base Station.  Also, since it operates in the 5.8 GHz unlicensed band, WiMAX is somewhat susceptible to interference, though the network has not experienced any major interference issues in the past 5 months.  Wireline (T1) provides consistent backhauls speeds of between 1 and 1.5 Mbps.  (Sprint) 3G provides an average backhaul speed of 850Kbps, but varies based on the distance between the RSE and the serving Sprint tower as well as the number of users on the serving Sprint towers at any given time.

2.2 Network Services and capibilities

The  Michigan Testbed provides the following services and\or capabilities:

• IEEE: 1609.3, 1609.4, and 802.11p are implemented in all RSE's at various Draft levels
• SAE: All data exchanged between RSE and OBE are in a slightly modified revision of J2735 Version 1
• Advisory Message Distribution Service (AMDS): Enables “Network Users” to send SAE J2735 compliant Road Sign, Advisory, and Probe Data Management Messages to Vehicles.
• Probe Data Service (PDS): Enables the distribution of SAE J2735 compliant Probe Data from RSE to “Network User” subscribers.  The RSE to OBE Interface is encrypted using Vehicular Datagram Transaction Level Security (V-DTLS), which was specifically designed for this application.
• Information Lookup Service (ILS): Enables Network Users to look up RSE IP, Location, Status, etc, information.
• Communication Service (Comms): Enables IPv6 communications between vehicles and Network Servers\Services
• Vehicular Host Identity Protocol (V-HIP): Select RSE's are capable of maintaining a data session as vehicles pass from 1 RSE to another
• Tolling: 1 RSE is capable of simulating a tolling transaction (Note: This is a VIIC developed application and may not be supported in the future)
• Signal Phase and Timing\Geographic Information Description (SPAT\GID): 1 RSE is connected to a Signal Controller and broadcasts Signaling information and a canned GID Map. (Note: This is a VIIC developed application and may not be supported in the future)

2.3 Location of the Michigan Testbed

The  Michigan Testbed is located in Oakland County MI, centered in the cities of Novi, Farmington, Farmington Hills, and Livonia.  The RSE network covers 45 Square miles; comprising 75 Center-Line Miles made up of 32 Interstate and Divided Highway and 43 Arterial miles.

 2.4 Michigan Testbed Standard Hours of Operation

Both the ENOC and the  Michigan Testbed are part of a research and development system, not a live, production system which needs to be operational 24 hours a day, 7 days a week, 365 days a year.
In recognition of this reality, the standard hours for personnel supporting the ENOC and the  Michigan Testbed are Monday through Friday, 8 a.m. through 5 p.m., Eastern Time.   During these hours, personnel will be available to operate and maintain the ENOC and the  Michigan Testbed to ensure all communication networks and associated servers, services, and applications are functioning normally and are able to support the test activities within the environment.  This includes ensuring the connections between the  RSE’s and the Michigan SDN are operational, the connection between the Michigan SDN and the ENOC is operational, as well as ensuring all components are functioning properly.

The network and all of its services are available and operational outside of the hours mentioned above, however, support personnel will not be available should a problem occur.

Special arrangements can be made between the Researcher and the Support Staff should testing be required outside of the standard hours of operation.

2.4.1 Scheduled Maintenance

In order to maintain and provide enhancements to the Michigan Testbed Network and Services, the Michigan Testbed may need to be taken off line to perform upgrades.  In the event of such a situation, all Researchers will be given as much notification as possible as to the Date, Time, and duration of the outage.

3 Michigan Testbed Test Support

Booz Allen Hamilton personnel will be available Monday through Friday between the hours of 8am and 5pm to support all testing activities.

3.1 Operation and Maintenance

As part of the Operation and Maintenance of the  Michigan Testbed, Booz Allen Hamilton will ensure the SDN and all RSEs are operational and equipped with the correct software versions.  Researchers will be given as much notice as possible when upgrades are required to RSE’s or the SDN.

3.2 Scheduling

Booz Allen will schedule Researchers to use the Michigan Testbed to ensure the activities of multiple Researchers do not interfere with each other.  In the event of conflicting requests, or if the Michigan Testbed is oversubscribed, Booz Allen will attempt to arrange a compromise acceptable to all parties.  If this cannot be done, the USDOT ITS JPO will make a final decision, based on their judgment of what is in the best interests of the VII program in general.

3.3 Basic Technical Support

Booz Allen will provide basic technical support to Researchers including answering questions regarding system configuration, investigating potential system problems, providing assistance in setting any system parameters that are under user control, etc. 

3.4 Trouble Reports

In the event that network problems arise while testing, submit a “Trouble Report” to GGM VIIDTESupport@bah.com.  The Trouble Report should contain the following information:

• Nature of Problem (i.e. did not receive expected message(s) in vehicle, did not receive Probe Data when expected, etc)
• Street\Intersection of where problem occurred
• Time the problem occurred

Trouble Reports will be investigated in a timely manner. If an RSE or software component is found to not be operating properly, it will be resolved as soon as possible.

3.5 Logs

As part of this support, RSE and SDN Logs can be captured and provided to the Researcher for data analysis.  RSE Logs contain changes to AMDS Messages being Broadcast (i.e. when a message expires, is canceled, or a new message is added) and Probe Data received by the RSE.  Both raw and parsed RSE logs can be made available.  SDN Network Sniffer logs contain all network traffic, however, a parser may or may not be available.   Raw Probe Data Received by the SDN are also available.  Formats for all logs are available upon request.

If Logs are to be captured, the researcher shall provide an FTP, or equivalent, site for which to upload the Logs.  Logs captured on a given day will be parsed and uploaded on the next Business day during normal business hours.

3.6 Defining Test Routes

Booz Allen can assist Researchers with defining Drive Routes and determining which RSEs should be used or turned off depending on the tests being executed.

3.7 Network Access

Network access will be provided to enable Researchers to send AMDS (i.e. Signage) Messages such that RSE’s broadcast the messages to vehicles.  Researchers will also be able to subscribe to vehicle Probe Data.

3.8 Proprietary Data

All proprietary data will be handled according to Researchers requirements and instructions.  However, the USDOT would like to use any and all captured anonymous data, and data that has been anonymized to the Researchers satisfaction, for additional Vehicle Infrastructure Integration related research.

3.9 Vehicles

The USDOT will have a certain amount of vehicles available equipped with On-Board Equipment (OBE) for use within the Environment.  Researchers can use the existing POC applications or install their own applications in these vehicle.  USDOT vehicles must be signed out and are on a first-come first-serve bases (See Appendix C for the Vehicle Request Form).

Researchers can also bring the own vehicles and OBE’s to the Environment.  Documentation outlining Network specifications will be made available such that Researchers can configure their OBE’s for the environment.

3.10 Network Modifications

Booz Allen can make minor network modifications, should the need arise, to support various testing activities and scenarios.  Network modifications will be limited to the following:

• Turning RSE’s off, to avoid overlapping coverage
• Turning portion of exiting RSE software on and off
• Installing tester specific S/W on select RSE’s and providing the tester login access to said RSE(s).

Network modifications will NOT include:

• Modifying exiting RSE and\or Network S/W code to accommodate a particular Test or Test Scenario.  All S/W development requires approval and authorization from the US DOT.

3.11 Methods of Contacting Michigan Testbed Personnel

Researchers may contact the  Michigan Testbed personnel by telephone or e-mail during the Hours of Operation and Maintenance Windows. 
Messages sent after hours are responded to on the next business day.
Telephone: 248.374.5094

E-mail: GGM VIIDTESupport@bah.com

4 Access to the Michigan Testbed

4.1 Michigan Testbed vehicle access

Researchers wishing to drive vehicles in the Michigan Testbed must fill out the forms contained in Appendix C-Vehicle Request Form, if applicable, Appendix D- Michigan Testbed Access Form, Appendix E-Principles of Operation Agreement, and Appendix F-Release of Liability Form and submit them to:

Booz Allen Hamilton
Attn: Frank Perry
39555 Orchard Hill Place
Suite 600
Novi, Mi 48375
GGM VIIDTESupport@bah.com

In addition to this form, providing the applicable Test Plan which outlines Test Objectives and execution procedures, will better help the Michigan Testbed Staff support various test activities.

4.2 Michigan Testbed Network User access

Users can connect to the Michigan Testbed to send messages to vehicles and receive Probe Data from vehicles.  Both connections require a static public IP Address from the User and require the user to setup a VPN connection to the respective servers.  Users will need to provide the IP Address from which they will be connecting from to Booz Allen Hamilton and Booz Allen Hamilton will provide the appropriate VPN Profile and credentials.

Send Messages:
To send messages to be displayed in a vehicle, a user must connect to the AMDS Web Service Interface and create the message and its broadcast strategy.  Users must have the appropriate Wed Service Definition Language (WSDL) and XSD files to access the Service.  RSE’s can be subscribed to based on the following criteria:

• List of RSE’s
• Geographic Region
• Logical RSE Group ID
• Political Boundary

Although all subscriptions methods are available, most are based on a list of RSE’s.

Users wishing to send messages can find additional information in VII Advisory Message Distribution, Service Users Guide.doc, which is available upon request. 

Receive Probe Data:
To receive Probe Data, a user must “subscribe” to the RSE’s and Data Elements they are interested in.  A Web Service Interface is used to create and maintain Probe Data Subscriptions.  Users must have the appropriate Wed Service Definition Language (WSDL) and XSD files to access the Service.  RSE’s can be subscribed to based on the following criteria:

• List of RSE’s
• Geographic Region
• Logical RSE Group ID
• Political Boundary

Although all subscriptions methods are available, most are based on a list of RSE’s

Users wishing to collect Probe Data can find additional information in VII Probe Data Service Users Guide.doc, which is available upon request.

Researchers needing to send Signage Messages or subscribe to Probe Data can create their own network application or purchase a copy of Soap Sonar, which was used for early testing by  Booz Allen Hamilton and the VIIC during the Proof-of-Concept.

5 Principles of Operation

See Appendix E for the Principles of Operation agreement. These Principles define the ground rules and basic expectations for Michigan Testbed access and utilization. Researchers must sign the agreement in Appendix D before being allowed to access\use the environment.

6 Liability

Nether the US DOT nor Booz Allen Hamilton assume any liability for Vehicles, Hardware, Software, or anything else that Researchers bring into and use within the  Environment.  Researchers test within the Michigan Testbed at their own Risk. A separate Liability Form, available upon request, must be signed prior to testing in the environment.

7 Check List

Appendix F contains a Check List to aid Researchers in ensuring all applicable documents are completed and available and all applicable forms are filled out when requesting access to the Michigan Testbed.

8 Forms

The Forms in Appendix C, D, E, and F are available in Access to Michigan Testbed Forms.xls.  The Liability Form, available separately, must also be signed.

9 Appendix A-Map of the  RSE Network

Click here for detailed view of image

10 Appendix B- RSE List

11 Appendix C-USDOT Vehicle Request Form

Detailed information contained in this form will not be shared with other Researchers

In addition to this information contained in this form, please provide a copy of the Test Route when submitting this form>

Please indicate any data residing on the Vehicles that are Proprietary in nature. Booz Allen Hamilton will handle it accordingly.

12 Appendix D- Access Request Form

Detailed information contained in this form will not be shared with other Researchers

Please indicate any data passing through the system (i.e. RSE and SDN) that are Proprietary in nature. Booz Allen Hamilton will handle it accordingly.

In addition to the information contained in this form, please provide a copy of the Test Route when submitting this form

Please attach the list of RSE’s to be used for Testing (Optional, derived f rom Test Route, see Appendix C for a list of available RSE's):

13 Appendix E-Principles of Operation agreement

1. Priority for use will be given to any efforts funded or sponsored by USDOT.
2. All other parties wishing to use the Michigan Testbed for testing purposes will have equal access to the facility.
3. In the event of conflicting requests, or if the Michigan Testbed is oversubscribed, the Michigan Testbed manager will attempt to arrange a compromise acceptable to all parties.  If this cannot be done, the USDOT ITS JPO will make a final decision, based on their judgment of what is in the best interests of the VII in general.
4. The Michigan Testbed manager will be responsible for implementing the Michigan Testbed access procedures. This will include the procedure for formally requesting access to the facility and the responsibilities of the requestor once use of the Michigan Testbed is complete (e.g., tear down of the test setup.).
5. A set of usage guidelines (rules) will be developed by the Michigan Testbed manager and made publicly available for all requestors.  The requestors are responsible for following the guidelines.  Failure to follow the guidelines may result in their lack of access to the Michigan Testbed.
6. If the security-enabled portion of the Testbed will be used, the requestor will be issued a security certificate by the Michigan Testbed manager, as required, for their vehicles.  This certificate must be used to gain access to the security-enabled portion of the Michigan Testbed and will be available free of charge to the requesting party.  Included in this is up to forty hours of technical support and troubleshooting from the Michigan Testbed manager, access to the VII SDN, utilizing appropriate protocols and security mechanisms, and provision of any data logs kept by the SDN or subscribing applications.  A limited number of OBE-equipped vehicles will be available for use during testing.  The requester may schedule use of these vehicles or provide their own equipped vehicles.  If the requesting party requires special services as part of their use of the Michigan Testbed, the requestor will contract directly with the Michigan Testbed manager for those services.  A list of available services and their cost/rates will be made publicly available.  All requesting parties will be charged the same for the available services.
7. Requesters will use the Michigan Testbed at their own risk.  Neither the Michigan Testbed manager nor the USDOT will be responsible for any costs or damages, etc. caused by use of the Michigan Testbed, nor will they be responsible for any costs caused by failure of the Michigan Testbed to operate or to operate correctly.
8. The requester will comply with any and all rules and regulations set down by the state and local jurisdictions in which the Michigan Testbed resides.  The requestor will demonstrate that they have sufficient liability insurance as part of requesting access to the Michigan Testbed.
9. The requesting party will assume all liability for damages, etc. resulting from their use of the Michigan Testbed or OBE-equipped vehicles.  The requesting party will pay for any damage they cause to the Michigan Testbed infrastructure or to any OBE-equipped vehicles that they use.  If there is a dispute as to whether this damage is due to the Michigan Testbed/OBE itself or to the actions of the requester, a third party arbitrator will determine responsibility.  The Michigan Testbed manager and the requestor will agree to the decision of the arbitrator.
10. At the end of a requestor’s testing activities, any OBE-equipped vehicles that were used must be re-fueled and returned to their state when the requestor’s testing began.
11. If the Michigan Testbed is not functioning or not functioning fully or correctly during the scheduled test time, negatively impacting the requester’s tests, the requester will, at their request, be given first priority access to any previously unscheduled test capacity.  No other compensation or consideration will be provided.
12. At the end of a requestor's testing activities, any OBE-equipped vehicles that were used must be re-fueled and returned to their state when the requestor's testing began.
13. If the Michigan Testbed is not functioning or not functioning fully or correctly during the scheduled test time, negatively impacting the requester's tests, the requester will, at their request, be given first priority access to any previously unscheduled test capacity.  No other compensation or consideration will be provided.
14. The manager of the Michigan Testbed will respect the confidentiality of the requestor's testing activities, and may enter into appropriate agreements to protect the requestor's intellectual property.
15. The Michigan Testbed manager will be responsible for maintaining and providing access to Michigan Testbed operational and technical manuals.  The requestor agrees that neither the Michigan Testbed manager nor any other party will be held financially responsible for any delays incurred due to errors in any of this technical documentation.

I  have read, understand, and will comply with the Principles of Operation for accessing and utilizing the  Development Test Environment as stated above.

_________________________
Company 

_________________________
Signature

_________________________
Date

14 Appendix F-Check List

This Check List is to aid researchers in ensuring all relevant documentation is available and filled out completly when requesting access to the Michigan Testbed