Report on Road User Needs and Requirements
Total Page:16
File Type:pdf, Size:1020Kb
REPORT ON ROAD USER NEEDS AND REQUIREMENTS 1 Report on Road User Needs and Requirements Outcome of the European GNSS’ User Consultation Platform Reference: GSA-MKD-RD-UREQ-250283 Issue/Revision: 2.0 Date: 01/07/2019 Change record Issue/ Revision Changes Date 1.0 First issue 18/10/2018 2.0 Refer to Annex 6 01/07/2019 REPORT ON ROAD USER NEEDS AND REQUIREMENTS 3 Table of Contents 1 INTRODUCTION AND CONTEXT OF THE REPORT 5 1.1 Methodology 6 1.2 Scope 8 2 EXECUTIVE SUMMARY 9 3 REFERENCE DOCUMENTS 12 4 GNSS MARKET OVERVIEW AND TRENDS FOR ROAD 14 4.1 Market Evolution and Key Trends 14 4.2 Main Market Players 16 4.3 Main User Groups 17 5 GNSS USER REQUIREMENTS ANALYSIS 18 5.1 GNSS Use in Road 18 5.2 Prospective Use of GNSS in Road 26 5.3 GNSS Limitations for Road 29 5.4 Drivers for User Requirements in Road 33 5.5 Conclusions 35 6 USER REQUIREMENTS SPECIFICATION 36 6.1 Synthesis of UR Analysis 36 7 ANNEXES 39 Annex 1: Major Projects V2X Underway in the World 39 Annex 2: Synthesis of Road User Requirements 39 Annex 3: Key Standardization Bodies and Organizations 39 Annex 4: Definition of Key GNSS Performance Parameters 41 Annex 5: List of Acronyms 43 Annex 6: Updates following the User Consultation Platform 2018 48 4 01 TableS AND FIGURES Tables Table 1: Performance parameters 10 Table 2: Safety Critical Applications 22 Table 3: Payment Critical Applications 23 Table 4: Regulatory Critical Applications 23 Table 5: Smart mobility for traffic managers and transport companies 24 Table 6: Smart mobility for safety and comfort of drivers 25 Table 7: Example of identification of reference scenarios for testing purposes 32 Table 8: Requirements for Traffic and Safety Warning applications 36 Table 9: Requirements for automated interventions and autonomous driving 37 Table 10: Requirements for payment critical applications 37 Table 11: Requirements for smart mobility applications 38 Table 12: Requirements for smart mobility applications 39 Figures Figure 1: Iter Avto – The world’s first automobile navigation system (1930) 5 Figure 2: Road User Requirements Methodology 7 Figure 3: Historical GNSS Road market data – shipments 14 Figure 4: Forecast GNSS Road market data – shipments 15 Figure 5: GNSS Road Value Chain 16 Figure 6: Car2Car V2X applications roadmap 27 Figure 7: Komatsu began trials of its Autonomous Haulage Systems (AHS) in a partnership with mining company Rio Tinto in 2008 28 Figure 8: An autonomous vehicle during the 2015 ITS World Congress in Bordeaux guided by RTK GNSS. After 5 days of operation we can note the accuracy of the guiding thanks to the traces left by tires 29 Figure 9: Block diagram from [RD6], showing the relationship between performance at PVT and application levels 30 Figure 10: The logical breakdown and PVT interface between GNSS-based positioning terminal and road-domain application, as adopted in [RD14] 30 Figure 11: Block diagram of the GBLS (level 2) [RD13], showing details of the Positioning Module (a). Block diagram of the GBLS (level 3) [RD13], showing possible sensors of the Positioning Module (b) 31 REPORT ON ROAD USER NEEDS AND REQUIREMENTS 5 introduction and context 01 of the report ven if the first prototypes of automobile navigation The next step will be the intensive use of GNSS in vehi- systems were available in the first half of the Twentieth cle-to-vehicle and vehicle-to-infrastructure communications Ecentury (see “Iter Avto”, the world’s first automobile that will pave the way to Automated vehicles. Advanced navigator, created in 1930 on Figure 1 here after), millions of Driver Assistance Systems (ADAS) currently used to improve drivers discovered the benefits of in car navigation systems the safety or mobility of the driver, are being further devel- in the 90s when GNSS road navigation systems appeared on oped as precursor to automated vehicles. Industry players dashboards. Road traffic information and guidance services such as Tesla, Baidu, Honda, Toyota, Uber and more are took off at the same time. already rushing to bring the first commercial vehicle to market. Since R&D technical details may reveal the under- Figure 1: Iter Avto – The world’s first automobile lining strategy, industry players are not willing to share navigation system (1930) information about their requirements. Nonetheless, the identification of a set of commonly accepted technical user requirements could provide a number of benefits Nowadays to the entire industry. In this sense, this document includes a first set of GNSS service technical User Requirements related to the in-vehicle positioning system is an option with special regards to the perfor- selected by mance of the GNSS receiver. Some of the requirements of the in- vehi- a significant cles Positioning, Velocity and Tim- ing (PVT) system directly apply to number of GNSS receivers, while others are the result of a data fusion process, which car buyers depends on all connected sensors, communication technologies, and PVT processing algorithms. It should be intended as a first step towards the definition of commonly accepted technical user requirements, which should be validated periodically by GNSS technical experts from both the scientific community Nowadays GNSS service is an option selected by a significant and the industry. It should also be updated on a regular basis number of car buyers. Nevertheless, due to the cost of this to guarantee adherence to the technology evolution, the option, which is very often associated with other devices evolving normative frameworks and/or the certification/ (like radio or mobile phones) many customers prefer to use type approval procedures. a personal navigation device or their familiar smartphones. Consequently, GNSS is present in almost all cars and service The User Consultation Platform (UCP) is a periodic forum providers have developed a long list of services dedicated organised by the European Commission and the GSA involv- to comfort, entertainment and safety. ing end users, user associations and representatives of the value chain, such as receiver and chipset manufacturers, Public authorities also embarked on the new possibilities application developers and the organisations and insti- brought by GNSS. Regulations in Europe for interoperabil- tutions dealing, directly and indirectly, with Galileo and ity of Road User Charges, the deployment of eCall on all EGNOS. The event is a part of the process developed at the new types of vehicles from 2018 and the control of digital GSA to collect user needs and requirements and take them tachograph on trucks and passenger vehicles with more 9 as inputs for provision of user driven Galileo and EGNOS seats are the most outstanding examples. services. In this context, the objective of this document is 6 1/ INTRODUCTION AND CONTEXT OF THE REPORT to provide a reference for the European GNSS Programmes 1.1 Methodology and for the automotive community reporting periodically the most up-to-date GNSS user needs and requirements The following figure details the methodology adopted for in the Road market segment. This report is considered a the analysis of the Road user requirements. “living document” in the sense that it will serve as a key input to the next UCP event where it will be reviewed and The analysis is split into two main steps including a “desk subsequently updated. The UCP will be held periodically research”, to gather main insights, and a “stakeholders con- (e.g. once per year) and this report will be also periodically sultation”, to validate main outcomes. updated, to reflect the evolution in the user needs, market and technology captured during the UCP. More in details, “desk research” was based on a secondary research and aimed at providing a preliminary structured The report aims to provide the GSA with a clear and up-to- analysis: date view of the current and potential future user needs and y leveraging on the Road applications’ segmentation as requirements in order to serve as an input to the continuous included in the GSA GNSS market report, additional rele- improvement of the services provided by the European vant applications have been identified and included; and GNSS systems and their evolutions. y for each application identified, the function and level of Finally, as the report is publicly available, it serves also as a performance required has been determined. reference for users and industry, supporting planning and decision-making activities for those concerned with the use As a result of this activity, a first draft of the Road User of location technologies. Requirements document has been produced. It must be noted that the listed user needs and requirements In the second step, the “stakeholder consultation” one, cannot usually be addressed by a single technological solu- main outcomes included in the document have been val- tion but rather by combination of several signals and sensors. idated and updated. In this regard, preliminary validation Therefore the report does not represent any commitment interviews with selected stakeholders have produced the of the European GNSS Programmes to address or satisfy the current document to be used as a input for the UPC review listed user needs and requirements in the current or future and finalisation. versions of the EGNSS services. REPORT ON ROAD USER NEEDS AND REQUIREMENTS 7 Figure 2: Road User Requirements Methodology OVERALL METHODOLOGY 1 Identification of all existing Road applications User level dimension and characterisation along with the function that they perform y Identification of the key GNSS