Acceptance Test Report. C CVII Task 2

Transcription

1 Feb (30) Customer Contract Number C Customer Contract Start/Finish Dates 21-Jan-2009 to 31-Dec-2010 C CVII Task 2 Task 2 provides the base VII infrastructure in the commercial vehicle on which the remaining tasks will develop commercial applications. Responsible Established Date Archived until Classification Tom Richter 29-Oct Feb-2020 OPEN

2 Feb (30) Contents 1 General Information Document Contacts Revision History Reference Documents Abbreviations Acceptance Criteria Identification Acceptance Criteria Results General Anonymous Probe Data Service Traveler Advisory Service... 8 Appendix A Pre-Test Data A.1 Test Hardware Configuration A.1.1 CVII Test Network Architecture A.1.2 Hardware Identification A.2 RSE Service Configuration Parameters A.3 Traveler Advisory Definitions Appendix B Communications Test Data B.1 Communications Coverage Map B.2 Raw Communications Data Appendix C Test Execution Data C.1 Executed Test Events C.2 Displayed Traveler Advisories C.3 Test Execution Maps C.3.1 Surface Roads Test Execution Map C.3.2 I-40 West Test Execution Map C.3.3 I-40 East Test Execution Map C.4 Collected Probe Vehicle Data

3 Feb (30) 1 General Information This document provides the acceptance test results for Task 2 of the NYSDOT CVII Project. 1.1 Document Contacts Company Name Phone VTEC Mike Siebert +1 (336) mike.siebert@volvo.com VTEC Tom Richter +1 (336) tom.richter@volvo.com 1.2 Revision History Issue Date Author Changes Jan 2010 Mike Siebert Initial Jan 2010 Mike Siebert - Paragraph 1.3 [1] Removed Astrid Glynn, Commissioner - Paragraph 1.4 Added definitions for CCH, SCH, WSM - Criteria TASK2-001 Added be - Appendix A.3 Added screen shot of the BAH web site. - Appendix C.2 Changed ID M to N in table (typographical error) - Appendix C.4 Added screen shot of the BAH web site. 1.3 Reference Documents [1] Contract #C PIN: CC Commercial Vehicle Infrastructure Integration New York State Department of Transportation 3

4 Feb (30) [2] C CVII Program Plan Volvo Technology Tom Richter Issue Sep 2009 [3] C CVII Task 2 Concept of Operations Volvo Technology Mike Siebert Issue Dec 2009 [4] C CVII Task 2 Acceptance Test Plan Volvo Technology Mike Siebert Issue Dec Abbreviations ABS Anti-Lock Brake System ATP Acceptance Test Plan (Reference [4]) BAH CCH CVII CVO DMZ DOT DMCU DSRC EM GPS IP IT IS KTC MCNU MCU N/A NYS NYSDOT OBE PPP PSID Booz Allen Hamilton Inc. Control Channel Commercial Vehicle to Infrastructure Integration Commercial Vehicle Operations Demilitarized Zone Department of Transportation 5.9 GHz DSRC Mobile Communications Unit Dedicated Short-Range Communications Emergency Management Global Positioning System Internet Protocol International Traveler Information Systems Kapsch TrafficCom Inc. Multiband Configurable Networking Unit Mobile Communications Unit Not Applicable New York State New York State Department of Transportation On Board Equipment Point to Point Protocol Provider Service Identifier 4

5 Feb (30) RSE RSSI SCH SwRI TA TCP TGW TTC VII VTEC WAVE WSM XML Roadside Equipment Received Signal Strength Indicator Service Channel Southwest Research Institute Traveler Advisory Transmission Control Protocol Telematics GateWay Temporary Traffic Control Vehicle to Infrastructure Integration Volvo Technology Wireless Access in a Vehicular Environment Wave Short Message Extensible Markup Language 1.5 Acceptance Criteria Identification All acceptance criteria referenced in this specification shall utilize the following notation: Criteria TASK2-nnn/i.i: <Criteria Title> <Criteria Specification> Where: nnn Serial number: i.i Issue of the ATP in which the criteria was added or modified 5

6 Feb (30) 2 Acceptance Criteria Results 2.1 General The acceptance test for Task 2 was executed on Wednesday, 06 Jan All of the criteria defined in the ATP were fully met. Details of the results can be found in the following subparagraphs. The hardware configuration used in the acceptance test can be found in Appendix A. The measured communications test data supporting the following acceptance criteria results can be found in Appendix B. Criteria TASK2-001/1.0: DSRC Range Statistics The usable DSRC range area for the successful transmission of DSRC data shall be a minimum distance of 300 meters between the DMCU and the RSE. Measured: 700 meters Criteria TASK2-002/1.0: RSE to DMCU Loss Statistics The RSE to DMCU packet loss within the DSRC range shall be a maximum of 10% in relation to the total DSRC packet transmission. Measured: 0% Criteria TASK2-003/1.0: DMCU to RSE Loss Statistics The DMCU to RSE packet loss within the DSRC range shall be a maximum of 10% in relation to the total DSRC packet transmission. Measured: 0% Criteria TASK2-004/1.0: Received Signal Strength The DSRC received signal strength shall be a minimum of 10 dbm at 300 meters. Measured: 20 dbm at 300 meters 2.2 Anonymous Probe Data Service The measured communications test data supporting the following acceptance criteria can be found in Appendix C except where noted. 6

7 Feb (30) Probe Data Message Loss By design, acknowledgements for probe data messages are not supported by the VII Probe Data Service which guarantees that a percentage of the caches of probe data messages (up to 30 messages at a time) will be completely lost. During the acceptance test run, approximately 66% of the generated probe data messages were lost. The 33% of the probe data messages that were received have proven to be adequate to evaluate the acceptance test criteria. Criteria TASK2-005/1.0: Probe Vehicle Service Configuration The logged RSE probe data service configuration shall be verified for consistency with the test hardware configuration. Measured: The test network architecture (Appendix A.1), hardware identification (Appendix A.1.2), and the service configuration parameters for the Probe Data Application (Appendix A.2) are consistent with the definition in the ATP Criteria TASK2-006/1.0: Probe Vehicle Data Content A statistically significant sample of the probe data shall be analyzed to ensure that it is consistent and accurate. Measured: All of the received probe time, heading, speed, vehicle type, height, mass, temperature, ABS, and light information was consistent with the ATP Criteria TASK2-007/1.0: Probe Vehicle Data Change The probe data shall change appropriately at the executed locations of Test Events 3, 5, and 7 (vehicle probe data changes and vehicle start) as defined in the ATP. Measured: - Following Test Event 3, Lights status shows high-beam lights on - Following Test Event 5, Lights status shows high-beam lights off - Probe data for Test Event 7 was lost (see sub-paragraph introduction) Criteria TASK2-008/1.0: Probe GPS Data Content All of the GPS data shall be mapped to ensure that positions, times, and road speeds are consistent with the test route and the executed test event data. Measured: All of the probe data message positions, times, and road speeds were consistent with the test route and executed test events 7

8 Feb (30) Criteria TASK2-009/1.0: Probe Data Periodic Trigger The periods between each of the probe data messages shall be consistent with the periodic trigger requirements based on the associated probe data road speed values. Measured: Out of 33 received periodic probe data messages: 22 Within 1 second of requirements 8 Between 1 and 2 seconds of the requirements 3 Between 2 and 3 seconds of the requirements Criteria TASK2-010/1.0: Probe Data Stop Trigger A probe data sample shall exist consistent with the executed time and location of Test Event 6 (vehicle stop) as defined in the ATP. Measured: Probe data for Test Event 6 was lost (see sub-paragraph introduction), however, probe data samples were received for the stops at Pegg Road, National Service Road, Sandy Ridge Road, and Gallimore Dairy Road Criteria TASK2-011/1.0: Probe Data Start Trigger The first time-ordered probe data sample following the probe data stop trigger sample shall be consistent with the executed time and location of Test Event 7 (vehicle start) as defined in the ATP. Measured: Probe data for Test Event 7 was lost (see sub-paragraph introduction), however, probe data samples were received for each of the starts associated with the stops described in Criteria TASK2-010 above Criteria TASK2-012/1.0: Probe Data Dynamic Vehicle Event Trigger Probe data samples shall exist consistent with the executed time and location of Test Events 2 and 4 (vehicle dynamic events) as defined in the ATP. Measured: - Following Test Event 2 a probe data sample was received - Probe data for Test Event 4 was lost (see sub-paragraph introduction) 2.3 Traveler Advisory Service The measured communications test data supporting the following acceptance criteria can be found in Appendix C except where noted. 8

9 Feb (30) Criteria TASK2-013/1.0: Traveler Advisory Definitions The traveler advisories for transmission to the vehicle shall be verified for consistency with the ATP. Measured: The traveler advisory XML definition files (Appendix A.3) were consistent with the content defined in the ATP Criteria TASK2-014/1.0: Traveler Advisory Display Consistency All of the displayed advisory s content, display area, and travel direction shall be consistent with the ATP. Measured: All of the traveler advisories were observed to be consistent with the defined content, display area, and travel direction. Criteria TASK2-015/1.0: Traveler Advisory Display Completeness All advisories defined in the ATP shall be displayed with the exception of advisories D and M. Measured: All of the traveler advisories were observed to display except for D and M Criteria TASK2-016/1.0: Invalid Travel Advisory Direction Advisory D, defined in the ATP to cross the test route, shall not be displayed because the travel direction is invalid. Measured: Traveler advisory D was not displayed Criteria TASK2-017/1.0: Multiple Travel Advisory Direction Display Advisory F, defined in the ATP to be valid in both travel directions, shall be displayed during both the outbound and return of the test route. Measured: Advisory F was observed to display on both the outbound and return trips Criteria TASK2-018/1.0: Single Travel Advisory Direction Display Advisory G, defined in the ATP to be valid in the northerly direction, shall be shown only on the outbound portion of the test route. Measured: Traveler advisory G was observed to only display on the outbound trip 9

10 Feb (30) Criteria TASK2-019/1.0: Invalid Travel Advisory Date/Time Advisory M, defined in the ATP to be valid at a date/time after the test route is run, shall not be shown. Measured: Traveler advisory M was not displayed Criteria TASK2-020/1.0: Traveler Advisory Driver Distraction Advisory N, defined in ATP to be low priority advisory, shall not be shown until the vehicle slows to a stop at Test Event 6 in accordance with driver distraction requirements. Measured: Traveler advisory N was observed to not display until the vehicle came to a complete stop 10

11 Feb (30) Appendix A Pre-Test Data A.1 Test Hardware Configuration A.1.1 CVII Test Network Architecture The following figure defines the test network at the time of the acceptance test. A.1.2 Hardware Identification The following table provides the 5.9 MHz DSRC hardware identification information at the time of the acceptance test. Hardware Description Model Number 5.9 Multiband Configurable Networking Unit (MCNU) R1500 Mobile Communications Unit (MCU) MCU-01 11

12 Feb (30) A.2 RSE Service Configuration Parameters The following table provides the RSE s service configuration parameters for the DSRC WAVE service announcement mapping to backhaul applications. Applications Messages VII POC Service Category PSID ITIS Probe Data Application Collection Communication Protocol Communication Nodes RSE IP Port Probe Data Information 0x TCP-IP/SCH OBE-Servers Traveler Information (General) Travel Time from VII Probe Data Conditions Advisories (General Advisories) Conditions Advisories (Traffic Delays and Status) 0x WSM/CCH RSE OBE x WSM/CCH RSE OBE A.3 Traveler Advisory Definitions A screen shot of the BAH Traveler Advisory Definition web site used in the acceptance test can be seen in the figure below. 12

13 Feb (30) A summary of the XML definition files used in the acceptance test to define the traveler advisories transmitted to the vehicle can be found in the table below. The geo-zones for each traveler advisory defined in the XML files can be seen plotted on the maps in Appendix C.3. The XML files have not been included in the appendices due the size of the files. ID Category Title/Text Priority Valid A [Warning Sign] B [Warning Sign] C [Regulatory Sign] D [Regulatory Sign] E [Construction Sign] F [Construction Sign] G [Regulatory Sign] H [Information Sign] I [Warning Sign] J [Warning Sign] K [Information Sign] Warning! Dangerous Curve Ahead Rollover Potential Proceed with Caution Warning! No Trucks Allowed Next Right Notice! No Trucks Allowed On Thorndike Rd Notice! Road Closed To Thru Traffic Work Zone! Low Clearance Ahead 12ft 6in Work Zone! Work Zone Ahead Along Tyner Rd Notice! Weight Limit Ahead Max 10 Tons on Overpass Travel Time To I-73 4 miles 5 minutes Warning! Merging Traffic Ahead Warning! Low Clearance Low Overpass Ahead 12ft 6in CVO Advisory Border Crossing Times Available Mon - Fri Warning-High 03 Dec :23:33 to 29 Aug :23:33 Warning-High 03 Dec :23:33 to 29 Aug :23:33 Regulatory-High 03 Dec :23:33 to 29 Aug :23:33 Regulatory-High 03 Dec :23:33 to 29 Aug :23:33 TTC-EM-High 03 Dec :23:33 to 29 Aug :23:33 TTC-EM-High 03 Dec :23:33 to 29 Aug :23:33 Regulatory-High 03 Dec :23:33 to 29 Aug :23:33 TA-High 03 Dec :23:33 to 29 Aug :23:33 Warning-High 03 Dec :23:33 to 29 Aug :23:33 Warning-High 03 Dec :23:33 to 29 Aug :23:33 TA-High 03 Dec :23:33 to 29 Aug :23:33 13

14 Feb (30) ID Category Title/Text Priority Valid L [Warning Sign] Warning! Merging Traffic Warning-High 03 Dec :23:33 to M [Information Sign] N [Information Sign] Ahead Travel Time To Sandy Ridge Road 1 mile 5 minutes CVO Advisory Truck Parking Info Parking Available Next Exit 29 Aug :23:33 TA-High 08 Jan :23:33 to 29 Aug :23:33 TA-Low 03 Dec :23:33 to 29 Aug :23:33 14

15 Feb (30) Appendix B Communications Test Data The following communications test data was obtained from the KTC COMM_TEST utility s log files collected during the acceptance testing. B.1 Communications Coverage Map The communications coverage map below, which summarizes the overall coverage obtained between the RSE and the OBE, was used to determine the effective range and RSSI levels. The map was generated from the raw communications data found in the following sub-paragraph. The RSSI is represented by the size of the green circles. 15

16 Feb (30) B.2 Raw Communications Data The table below provides the raw communications data collected from the COMM_TEST log files

17 Feb (30)

18 Feb (30)

19 Feb (30)

20 Feb (30)

21 Feb (30)

22 Feb (30)

23 Feb (30)

24 Feb (30) Appendix C Test Execution Data C.1 Executed Test Events The following table contains the execution times for each test event. The execution location for each test event can be seen plotted on the maps in Appendix C.3. ID Test Event Time 1 4:50:52 2 4:53:15 3 4:59:23 4 4:59:58 5 5:01:09 6 5:05:15 7 5:06:46 8 5:12:03 C.2 Displayed Traveler Advisories The following table contains the starting and ending display times as well as the status of the displayed content for each traveler advisory. The starting and ending display locations and travel direction for each traveler advisory can be seen plotted on the maps in Appendix C.3. Traveler Advisory ID Start Content End A 4:51:27 Correct 4:51:50 B 4:51:58 Correct 4:52:13 C 4:52:23 Correct 4:52:39 E 4:54:25 Correct 4:54:47 F 4:55:12 Correct 4:56:45 G 4:57:17 Correct 4:57:58 H 4:58:26 Correct 4:59:05 I 4:59:58 Correct 5:00:13 24

25 Feb (30) Traveler Advisory ID Start Content End J 5:00:30 Correct 5:01:06 K 5:02:26 Correct 5:02:40 L 5:02:55 Correct 5:03:21 N 5:05:15 Correct 5:06:50 F 5:08:52 Correct 5:09:59 F 5:10:21 Correct 5:11:06 C.3 Test Execution Maps The following notation is used for the test execution maps: Traveler Advisory Definition Plotted by importing the Traveler Advisory XML files into MapPoint Traveler Advisory Beginning A Observed vehicle location when Traveler Advisory A began displaying Traveler Advisory Ending A Observed vehicle location when Traveler Advisory A stopped displaying Test Event Execution 1 Note Observed vehicle location when Test Event 1 was executed The travel direction for the traveler advisory and test event markers is implied by the side of the road on which the marker is located (e.g. a marker on the south side of an east-west road implies east bound). 25

26 Feb (30) C.3.1 Surface Roads Test Execution Map E E 8 1 E A A D 2 A B B C C C B 26

27 Feb (30) C.3.2 I-40 West Test Execution Map N 7 6 N G H N G H G F F F H 3 F M F C.3.3 I-40 East Test Execution Map M 4 I L L I L I K J J K K 5 J 27

28 Feb (30) C.4 Collected Probe Vehicle Data A screen shot of the BAH Probe Vehicle Data web site used in the acceptance test can be seen in the figure below. A summary of all of the collected probe vehicle data which was used for the criteria analysis can be found in the table on the following page. 28

29 Feb (30) 29

30 Feb (30) Table of Criteria Results Criteria TASK2-001/1.0: DSRC Range Statistics... 6 Criteria TASK2-002/1.0: RSE to DMCU Loss Statistics... 6 Criteria TASK2-003/1.0: DMCU to RSE Loss Statistics... 6 Criteria TASK2-004/1.0: Received Signal Strength... 6 Criteria TASK2-005/1.0: Probe Vehicle Service Configuration... 7 Criteria TASK2-006/1.0: Probe Vehicle Data Content... 7 Criteria TASK2-007/1.0: Probe Vehicle Data Change... 7 Criteria TASK2-008/1.0: Probe GPS Data Content... 7 Criteria TASK2-009/1.0: Probe Data Periodic Trigger... 8 Criteria TASK2-010/1.0: Probe Data Stop Trigger... 8 Criteria TASK2-011/1.0: Probe Data Start Trigger... 8 Criteria TASK2-012/1.0: Probe Data Dynamic Vehicle Event Trigger... 8 Criteria TASK2-013/1.0: Traveler Advisory Definitions... 9 Criteria TASK2-014/1.0: Traveler Advisory Display Consistency... 9 Criteria TASK2-015/1.0: Traveler Advisory Display Completeness... 9 Criteria TASK2-016/1.0: Invalid Travel Advisory Direction... 9 Criteria TASK2-017/1.0: Multiple Travel Advisory Direction Display... 9 Criteria TASK2-018/1.0: Single Travel Advisory Direction Display... 9 Criteria TASK2-019/1.0: Invalid Travel Advisory Date/Time Criteria TASK2-020/1.0: Traveler Advisory Driver Distraction