Common use of TESTING ENVIRONMENT Clause in Contracts

TESTING ENVIRONMENT. 1. Testing the eCall reception 1.1 Test the PSAP modem All the following tests will analyse the performance of the PSAP modem and its behaviour in different scenarios. • with or without the eCall flag These tests will show how the system will handle calls with or without the eCall flag. As the implementation of the eCall flag is the responsibility of the MNOs, we are not sure when we’ll be able to test this feature. • for standard eCall (the IVS calls the PSAP) These tests will provide information about the normal dataflow for eCall. • IVS redial These tests will be performed to observe the behaviour of the system when the IVS attempts a redial after the connection has been interrupted. • Call-back (the PSAP calls the IVS) These tests will analyse how the system behaves in case of a call-back. The call-back function will be used in case an on-going call is interrupted for D4.1 Draft KPIs, test specification and methodology various reasons. After the call is interrupted, the IVS will try to establish a connection with the PSAP and if the IVS won’t be able to so, the operator will have to use the call-back feature. • Redundancy We will test the redundancy of the PSAP modem and different failover strategies. • Test more calls coming at the same time These tests will analyse the behaviour of the PSAP modem in case of more eCalls at the same time. 1.2 Test the voice connection with the operator These tests will concentrate on the eCall voice path characteristics from the 112 operator’s point of view. These tests will include, but won’t be limited to: answering a call, transferring a call, ending a call. 1.3 Test the call-back feature from the operator’s point of view These tests will analyse the call-back functionality from the 112 operator’s point of view. These tests will observe the minimum and maximum wait time before attempting call-back. 1.4 Evaluate the defined KPIs We will evaluate all the defined KPISs using the data gathered during the tests for eCall reception. 2. Test the MSD reception from the point of view of the operator 2.1 Evaluate the usability of the operator interface This evaluation will help analyse if the proposed operator interface is user friendly. 2.2 Test the reception of the MSD in the 112 application We will test to see if the MSD is being decoded correctly and if the information is being presented to the operator. 2.3 Test the “resend MSD” functionality These tests will analyse the behaviour of the system in case the operator asks for a MSD resend. We will test different scenarios: resend MSD during a normal eCall, resend MSD during a call-back, consecutive resend MSD during the same call etc. 2.4 Test the automating positioning of the incident D4.1 Draft KPIs, test specification and methodology This will test the automatic positioning of an incident on a GIS map, based on the GPS coordinates from the MSD. We will evaluate the best representation method for presenting the recent vehicle position before the incident and the vehicle direction. 2.5 Evaluate KPIs We will evaluate all the defined KPIs using the data gathered from the MSD reception tests.

TESTING ENVIRONMENT. 1. Testing the eCall reception 1.1 Test the PSAP modem All the following tests will analyse the performance of the PSAP modem and its behaviour in different scenarios. • with or without the eCall flag These tests will show how the system will handle calls with or without the eCall flag. As the implementation of the eCall flag is the responsibility of the MNOs, we are not sure when we’ll be able to test this feature. • for standard eCall (the IVS calls the PSAP) These tests will provide information about the normal dataflow for eCall. • IVS redial These tests will be performed to observe the behaviour of the system when the IVS attempts a redial after the connection has been interrupted. • Call-back (the PSAP calls the IVS) These tests will analyse how the system behaves in case of a call-back. The call-back function will be used in case an on-going call is interrupted for D4.1 Draft KPIs, test specification and methodology various reasons. After the call is interrupted, the IVS will try to establish a connection with the PSAP and if the IVS won’t be able to so, the operator will have to use the call-back feature. • Redundancy We will test the redundancy of the PSAP modem and different failover strategies. • Test more calls coming at the same time These tests will analyse the behaviour of the PSAP modem in case of more eCalls at the same time. 1.2 Test the voice connection with the operator These tests will concentrate on the eCall voice path characteristics from the 112 operator’s point of view. These tests will include, but won’t be limited to: answering a call, transferring a call, ending a call. 1.3 Test the call-back feature from the operator’s point of view These tests will analyse the call-back functionality from the 112 operator’s point of view. These tests will observe the minimum and maximum wait time before attempting call-back. 1.4 Evaluate the defined KPIs We will evaluate all the defined KPISs using the data gathered during the tests for eCall reception. 2. Test the MSD reception from the point of view of the operator 2.1 Evaluate the usability of the operator interface This evaluation will help analyse if the proposed operator interface is user friendly. 2.2 Test the reception of the MSD in the 112 application We will test to see if the MSD is being decoded correctly and if the information is being presented to the operator. 2.3 Test the “resend MSD” functionality These tests will analyse the behaviour of the system in case the operator asks for a MSD resend. We will test different scenarios: resend MSD during a normal eCall, resend MSD during a call-back, consecutive resend MSD during the same call etc. 2.4 Test the automating positioning of the incident D4.1 Draft KPIs, test specification and methodology incident This will test the automatic positioning of an incident on a GIS map, based on the GPS coordinates from the MSD. We will evaluate the best representation method for presenting the recent vehicle position before the incident and the vehicle direction. 2.5 Evaluate KPIs We will evaluate all the defined KPIs using the data gathered from the MSD reception tests.