Pilot Project on the Design, Implementation and Execution of the Transfer of GNSS Data During an E112 Call to the PSAP Contract No 440/PP/GRO/PPA/15/8308

Pilot Project on the Design, Implementation and Execution of the Transfer of GNSS Data During an E112 Call to the PSAP Contract No 440/PP/GRO/PPA/15/8308

Ref. Ares(2017)3702085 - 24/07/2017 Pilot project on the design, implementation and execution of the transfer of GNSS data during an E112 call to the PSAP Contract No 440/PP/GRO/PPA/15/8308 Deliverable D3.1 – Description of the scenarios Loïc Bellon July – 2017 Reference: HELP112-D3.1-TPZ Date: 08/06/2016 Version: 1.8 Contract No 440/PP/GRO/PPA/15/8308 Deliverable D3.1 – Description of the scenarios Pilot project on the design, implementation and execution of the transfer of GNSS data during an E112 call to the PSAP Responsibility-Office- Date Signature Company Prepared by Loïc Bellon 08 Jun 2016 Verified by Matthieu Forte 08 Jun 2016 Approved by Matthieu Forte 08 Jun 2016 LEGAL NOTICE This document has been prepared for the European Commission however it reflects the views only of the authors, and the Commission cannot be held responsible for any use which may be made of the information contained therein. 2/107 Reference: HELP112-D3.1-TPZ Date: 08/06/2016 Version: 1.8 ENREGISTREMENT DES EVOLUTIONS / CHANGE RECORDS ISSUE DATE § : DESCRIPTION DES EVOLUTIONS REDACTEUR § : CHANGE RECORD AUTHOR 1.0 03/02/2016 Deliverable outline L. Bellon 1.1 19/02/2016 Draft of sections 1, 2 (Analysis of D1.1) L. Bellon M. Forté 1.2 07/03/2016 Draft of sections 3, 4, 5 L. Bellon M. Forté 1.3 11/03/2016 Draft of sections 6 L. Bellon M. Forté 1.4 15/03/2016 Revision of all sections L. Bellon M. Forté 1.5 22/03/2016 Revisions based on comments from HELP112 consortium members L. Bellon I. Embaby M. Forté 1.6 08/04/2016 Revisions based on comments from Checkpoint 2 conference call L. Bellon as documented in the minutes with ids: EC-CKP2-7 (Sections 5.1 & M. Forté 5.2), EC-CKP2-8 (whole document & Section 5.2.1), EC-CKP2-9 (Section 6.1), EC-CKP2-10 (Section 6.1) 1.7 14/04/2016 Revisions based on minor comments from consortium members. L. Bellon Add of the HELP112 work flow in section 1.1 1.8 08/06/2016 Revisions based on comments from Checkpoint 2-bis conference L. Bellon call as documented in the minute with ids: EC-CKP2-11, EC-CKP2- 12, EC-CKP2-13. 3/107 Reference: HELP112-D3.1-TPZ Date: 08/06/2016 Version: 1.8 TABLE OF CONTENTS 1. INTRODUCTION ........................................................................................................ 10 1.1 PLACE OF THIS DOCUMENT AND OBJECTIVES....................................................................... 10 1.2 FOREWORD ................................................................................................................ 11 1.3 APPLICABLE DOCUMENTS ............................................................................................... 11 1.4 REFERENCE DOCUMENTS ............................................................................................... 12 2. ANALYSIS OF USER REQUIREMENTS AND USER SCENARIOS .................................. 13 2.1 USER REQUIREMENTS ................................................................................................... 13 2.1.1 Accuracy/Precision and Reliability requirements ................................................................. 14 2.1.2 Response time requirements ............................................................................................ 14 2.1.3 Presentation of the caller location in the PSAP ................................................................... 15 2.1.4 Privacy requirements ....................................................................................................... 15 2.1.5 Acceptance of the solution requirements ........................................................................... 16 2.1.6 Security requirements ...................................................................................................... 16 2.1.7 Method of estimating the location information requirements ............................................... 17 2.1.8 Battery life requirements .................................................................................................. 17 2.1.9 Incurring charges requirements ........................................................................................ 18 2.1.10 Data transmission requirements ........................................................................................ 18 2.1.11 Roaming requirements ..................................................................................................... 19 2.1.12 Improvement of AML specific requirements ....................................................................... 19 2.2 USER SCENARIOS ......................................................................................................... 19 3. CANDIDATE FOR E112 DESIGNING METHODOLOGY ................................................ 21 4. LOCATION METHODS ................................................................................................ 23 4.1 NETWORK BASED SOLUTION ........................................................................................... 23 4.1.1 Existing technologies ....................................................................................................... 23 4.1.2 Accuracy/Precision and response time of network based location solutions ........................... 26 4.2 HANDSET BASED SOLUTION ........................................................................................... 27 4.2.1 WiFi Positioning System ................................................................................................... 27 4.2.2 Standalone GNSS ............................................................................................................ 29 4.2.3 A-GNSS .......................................................................................................................... 29 4.2.4 Accuracy and response time of handset based location methods ......................................... 32 5. ACTIVATION AND TRANSMISSION METHODS .......................................................... 35 5.1 ACTIVATION METHODS .................................................................................................. 35 5.1.1 Automated activation process ........................................................................................... 35 5.1.2 Activation process using App ............................................................................................ 36 5.2 TRANSMISSION METHODS .............................................................................................. 38 5.2.1 HELP112 Minimum Set of Data ......................................................................................... 38 5.2.2 Transmission using SMS ................................................................................................... 40 4/107 Reference: HELP112-D3.1-TPZ Date: 08/06/2016 Version: 1.8 5.2.3 Transmission using the data channel ................................................................................. 40 5.2.4 Transmission using IMS/SIP ............................................................................................. 41 5.2.5 Transmission using in-band modem .................................................................................. 43 6. HELP112 ARCHITECTURE DESCRIPTIONS ................................................................ 45 6.1 INTRODUCTION ........................................................................................................... 45 6.2 ARCHITECTURE 1: HANDSET BASED HYBRID POSITIONING METHOD USING SUPL SERVER + AUTOMATED ACTIVATION + SMS TRANSMISSION ........................................................................... 48 6.2.1 Architecture .................................................................................................................... 48 6.2.2 I/F description................................................................................................................. 49 6.2.3 Covered requirements ...................................................................................................... 50 6.2.4 Covered user scenarios .................................................................................................... 55 6.3 ARCHITECTURE 2: HANDSET BASED HYBRID POSITIONING METHOD + AUTOMATED ACTIVATION + SMS TRANSMISSION ROAMING ENABLED ...................................................................................... 58 6.3.1 Architecture .................................................................................................................... 58 6.3.2 I/F description................................................................................................................. 60 6.3.3 Covered requirements ...................................................................................................... 61 6.3.4 Covered user scenarios .................................................................................................... 65 6.4 ARCHITECTURE 3: HANDSET BASED HYBRID POSITIONING METHOD + AUTOMATED ACTIVATION + SMS TRANSMISSION + ENHANCED NETWORK POSITIONING METHOD AS SAFETY NET .............................. 68 6.4.1 Architecture .................................................................................................................... 68 6.4.2 I/F description................................................................................................................. 69 6.4.3 Covered requirements ...................................................................................................... 70 6.4.4 Covered user scenarios ...................................................................................................

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    107 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us