1. Test and Interation Review 16th of December 2013 D4.6 AGNSS Server /Client Tests Strategy

2. RID ∙ Description: The document is complete. However a more descriptive conclusion would be appreciated, highlighting the outcomes of the tests in a qualitative way. The document is very technical and it is not very easy for a reader to read through the code lines, "how good" are the results obtained in the test campaign ∙ Answer: a section will be added at the beginning of the document with a qualitative test description (see following slides) 2

3. 3 Tests plan two-fold technical drivers (1) Inter components protocol verification : check that all protocol stacks are working and compliant with their interface definition : ∙ Between LOCS Server / Himalaya Client Application ∙ SMS Push Initiation (SRTX mediator) ∙ SUPL V2 focusing on SUPL V2 extension usingLPP GANSS Payload (GPS+Glonass+Galileo) ∙ Between LOCS Server / SkySoft application driver ∙ RESTfull Terminal Location Net-Initiated API ∙ Between Himalaya Client and Himalaya Tesseo board ∙ STM NMEA Interface for messaging / commanding 316/12/2013

4. 4 Tests plan two-fold technical drivers (2) Hybridation algorithm implementation verification (link with D4.7 Aiding technologies subsystem unitary test report) : verification against reference system test scenarios for each functional sub-modules : ∙ Scenarios breakdown following main distinct sub-cases family ∙ MEMS hybridation taking into account GNSS position information only ∙ MEMS hybridation taking into account GNSS position and velocity ∙ Verification expected pass criteria for each sub modules : ∙ Initial attitude computation ∙ Mechanization Equation ∙ Multi-constellation PVT ∙ Hybridation filter 416/12/2013

5. 5 Tests implementation incremental logic (1) AGNSS Server Features validation, using SUPL Client V2 and TerminalLocation Client Emulator ∙ Mainly protocol testing scenarios verifying ∙ Multiple GANSS SUPL V2 Support ∙ Periodic and Area Event Trigger Features / Trigger Cancellation ∙ Precise Timing Support ∙ Wifi Positioning ∙ RESTfull Location interface for LocationQuery, Periodic and Area Event Subscription, Trigger Cancellation 516/12/2013

6. 6 Tests implementation incremental logic (2) Himalaya client validation, using Himalaya Tesseo board Emulator ∙ Interface unitary testing (messages and commands) for ∙ board configuration commanding ∙ GNSS and MEMS data messages sentences handling ∙ Assistance data providing and commanding ∙ Algorithm implementation testing using expected system test results 616/12/2013

7. 7 Tests implementation incremental logic (3) End-to-end Server/Himalaya client integration, with TerminalLocation Client Emulator, using GPS Android location provider as fallback ∙ Client scenario configuration integration and associated board commanding ∙ Client SUPL stack implementation verification ∙ Qualitative verification of SUPL Trigger periodic and geofencing client implementation features ∙ Tesseo assistance commanding workflow 716/12/2013