TR 22.872 V2.0.0 (2018-05) Study on positioning use cases

《TR 22.872 V2.0.0 (2018-05) Study on positioning use cases》由會(huì)員分享，可在線閱讀，更多相關(guān)《TR 22.872 V2.0.0 (2018-05) Study on positioning use cases（74頁(yè)珍藏版）》請(qǐng)?jiān)谘b配圖網(wǎng)上搜索。

3GPP TR 22.872 V2.0.0 (2018-05) Technical Report 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on positioning use cases; Stage 1 (Release 16) The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Report is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices. 3GPP TR 22.872 V2.0.0 (2018-05) 74 Release 16 Keywords Fifth generation, 5G, Positioning, use cases 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All rights reserved. UMTS? is a Trade Mark of ETSI registered for the benefit of its members 3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association Bluetooth is a Trade Mark of the Bluetooth SIG registered for the benefit of its members Contents Foreword 7 1 Scope 8 2 References 8 3 Definitions, symbols and abbreviations 8 3.1 Definitions 8 3.2 Symbols 9 3.3 Abbreviations 9 4 Overview 9 5 Use cases 10 5.1 Foreword 10 5.1.1 Key Performance Indicators and Key attributes for positioning use cases 10 5.2 LBS-related use cases 12 5.2.1 Accurate positioning for shared bikes 12 5.2.1.1 Description 12 5.2.1.2 Pre-conditions 12 5.2.1.3 Service Flows 12 5.2.1.4 Post-conditions 13 5.2.1.5 Potential Impacts or Interactions with Existing Services/Features 13 5.2.1.6 Potential Requirements 13 5.2.2 Accurate positioning to support Augmented Reality (AR) 13 5.2.2.1 Description 13 5.2.2.2 Pre-conditions 13 5.2.2.3 Service Flows 13 5.2.2.4 Post-conditions 14 5.2.2.5 Potential Impacts or Interactions with Existing Services/Features 14 5.2.2.6 Potential Requirements 14 5.2.3 Power saving mechanism of wearable devices 14 5.2.3.1 Description 14 5.2.3.2 Pre-conditions 14 5.2.3.3 Service Flows 15 5.2.3.4 Post-conditions 15 5.2.3.5 Potential Impacts or Interactions with Existing Services/Features 15 5.2.3.6 [Potential] Requirements 15 5.2.4 Location-based advertising push 16 5.2.4.1 Description 16 5.2.4.2 Pre-conditions 16 5.2.4.3 Service Flows 16 5.2.4.4 Post-conditions 16 5.2.4.5 Potential Impacts or Interactions with Existing Services/Features 16 5.2.4.6 [Potential] Requirements 16 5.2.5 Flow management in large transportation hubs 17 5.2.5.1 Description 17 5.2.5.2 Pre-conditions 17 5.2.5.3 Service Flows 17 5.2.5.4 Post-conditions 17 5.2.5.5 Potential Impacts or Interactions with Existing Services/Features 18 5.2.5.6 Potential Requirements 18 5.3 Industry and eHealth related use cases 18 5.3.1 Person and medical equipment location in hospitals 18 5.3.1.1 Description 18 5.3.1.2 Pre-conditions 18 5.3.1.3 Service Flows 18 5.3.1.4 Post-conditions 19 5.3.1.5 Potential Requirements 19 5.3.2 Patient location outside hospitals 19 5.3.2.1 Description 19 5.3.2.2 Pre-conditions 19 5.3.2.3 Service Flows 19 5.3.2.4 Post-conditions 20 5.3.2.5 [Potential] Requirements 20 5.3.3 Trolley location in factories 20 5.3.3.1 Description 20 5.3.3.2 Pre-conditions 20 5.3.3.3 Service Flows 20 5.3.3.4 Post-conditions 20 5.3.3.5 [Potential] Requirements 20 5.3.4 Waste Management & Collection 21 5.3.4.1 Description 21 5.3.4.2 Pre-conditions 21 5.3.4.3 Service Flows 21 5.3.4.4 Post-conditions 22 5.3.4.5 Potential Impacts or Interactions with Existing Services/Features 22 5.3.4.6 [Potential] Requirements 22 5.4 Emergency and Mission Critical related use cases 22 5.4.1 Accurate positioning for emergency services 22 5.4.1.1 Description 22 5.4.1.2 Pre-conditions 22 5.4.1.3 Service Flows 23 5.4.1.4 Post-conditions 23 5.4.1.5 Potential Impacts or Interactions with Existing Services/Features 23 5.4.1.6 Potential Requirements 23 5.4.2 Accurate Positioning for First Responders 24 5.4.2.1 Description 24 5.4.2.2 Pre-conditions 24 5.4.2.3 Service Flows 24 5.4.2.4 Post-conditions 24 5.4.2.5 Potential Impacts or Interactions with Existing Services/Features 24 5.4.2.6 Potential Requirements 25 5.4.3 Alerting nearby emergency responders 25 5.4.3.1 Description 25 5.4.3.2 Pre-conditions 25 5.4.3.3 Service Flows 26 5.4.3.4 Post-conditions 26 5.4.3.5 Potential Impacts or Interactions with Existing Services/Features 26 5.4.3.6 [Potential] Requirements 26 5.4.4 Emergency equipment location outside hospitals 26 5.4.4.1 Description 26 5.4.4.2 Pre-conditions 27 5.4.4.3 Service Flows 27 5.4.4.4 Post-conditions 27 5.4.4.5 [Potential] Requirements 27 5.5 Road-related use cases 28 5.5.1 Accurate positioning to support Traffic Monitoring, Management and Control 28 5.5.1.1 Description 28 5.5.1.2 Pre-conditions 28 5.5.1.3 Service Flows 29 5.5.1.4 Post-conditions 29 5.5.1.5 Potential Impacts or Interactions with Existing Services/Features 29 5.5.1.6 Potential Requirements 29 5.5.2 Road-User Charging (RUC) 30 5.5.2.1 Description 30 5.5.2.2 Pre-conditions 30 5.5.2.3 Service Flows 30 5.5.2.4 Post-conditions 31 5.5.2.5 Potential Impacts or Interactions with Existing Services/Features 31 5.5.2.6 Potential Requirements 31 5.6 Rail and Maritime related use cases 31 5.6.1 Asset and freight tracking (wagon, container) 31 5.6.1.1 Description 31 5.6.1.2 Pre-conditions 32 5.6.1.3 Service Flows 32 5.6.1.4 Post-conditions 33 5.6.1.5 Potential Impacts or Interactions with Existing Services/Features 33 5.6.1.6 Potential Requirements 33 5.7 Aerial-related use cases 34 5.7.1 Accurate positioning to support Unmanned Aerial Vehicle (UAV) missions and operations 34 5.7.1.1 Description 34 5.7.1.2 Pre-conditions 34 5.7.1.3 Service Flows 34 5.7.1.4 Post-conditions 34 5.7.1.5 Potential Impacts or Interactions with Existing Services/Features 35 5.7.1.6 Potential Requirements 35 5.7.2 Transport and inspection by drones for medical purposes 35 5.7.2.1 Description 35 5.7.2.2 Pre-conditions 36 5.7.2.3 Service Flows 36 5.7.2.4 Post-conditions 36 5.7.2.5 [Potential] Requirements 36 5.8 Other use cases 37 5.8.1 Support of multiple different location services 37 5.8.1.1 Description 37 5.8.1.2 Pre-conditions 37 5.8.1.3 Service Flows 37 5.8.1.4 Post-conditions 38 5.8.1.5 Potential Impacts or Interactions with Existing Services/Features 38 5.8.1.6 [Potential] Requirements 38 5.8.2 Support location method negotiation 38 5.8.2.1 Description 38 5.8.2.2 Pre-conditions 38 5.8.2.3 Service Flows 38 5.8.2.4 Post-conditions 39 5.8.2.5 Potential Impacts or Interactions with Existing Services/Features 39 5.8.2.6 [Potential] Requirements 39 6 Synthesis of the use cases performances targets 40 6.1 Foreword 40 6.2 Considerations on the commonalities of performances targets among use cases 41 6.2.1 Time to first fix (TTFF) 41 6.2.2 Latency 41 6.2.3 3D-position and velocity measurements 42 6.2.4 Accuracy and availability 42 6.2.5 Consideration on relative positioning 43 6.2.6 Respect of the user’s privacy 44 6.2.7 Flexibility, versatility and configurability of the positioning services 44 6.3 Considerations on the grouping of use cases 45 7 Considerations on the suitability of positioning technologies for use cases 47 7.1 Introduction and proposed approach 47 7.2 Suitability of existing positioning technologies for different KPIs 48 7.2.1 Horizontal accuracy KPI 48 7.2.2 Technologies capabilities for vertical accuracy KPI 49 7.2.3 Technologies capabilities for relative positioning accuracy KPI 50 7.2.4 Technologies capabilities for velocity accuracy KPI 50 7.3 Summary 51 8 Consolidated potential positioning requirements 53 8.1 Overall Positioning Services requirements 53 8.2 Positioning performance requirements 53 8.3 Operational Requirements 55 8.4 Security-related Requirements 55 9 Conclusions and recommendations 56 Annex A: Mapping matrices between use cases’ potential requirements and potential consolidated positioning requirements 57 Annex B: Change history 74 Foreword This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 1 Scope This technical report relates to a study on positioning use cases for both outdoor and indoor environments. It analyses positioning use cases and complements existing work on 5G use cases involving positioning needs in order to identify potential requirements for 5G positioning services. This document also identifies new use cases, their scope and environment of use along with the related KPIs. For use cases already addressed (fully or partially) in other 3GPP studies, it consolidates and validates the KPI and assumptions. The document further develops the identified use cases by providing some considerations on the suitability of positioning technologies to these use cases. These considerations support the identification of potential requirements that can be achieved with 3GPP positioning technologies or with a combination of 3GPP and non-3GPP positioning technologies. The use cases and performance targets are independent of specific solutions even though, in order to support these considerations, the report provides some illustrative allocation between existing positioning technologies and 3GPP new positioning technologies (e.g. NR-based). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPPTR21.905: "Vocabulary for 3GPP Specifications". [2] 3GPP TS 38.805: “NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN” [3] ISO-CD 19363.2 20180120:Electrically propelled vehicles [4] IEC TS 61980-3 ED1:Electric vehicle wireless power transfer (WPT) systems – Part 3 Specific requirements for the magnetic field wireless power transfer systems [5] NGMN Alliance: “5G White Paper” [6] ETSI TS 103 246-1 V2.0.13 (2016-10): “Satellite Earth Stations and Systems (SES); GNSS based location systems. Part 1: Functional Requirements” [7] FCC CSRIC WORKING GROUP 3 “E911 Location Accuracy - Indoor Location Test Bed Report” 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR21.905[1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR21.905[1]. 3.2 Symbols For the purposes of the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR21.905[1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR21.905[1]. 2D: 2-dimensions 3D: 3-dimemsions CDF: Cumulative Distribution Function HA-GNSS: High Accuracy GNSS FTM: Fine-Time Measurement (as defined in 802.11-2016) IMU: Inertial Measurement Unit KPI: Key Performance Indicator RTK: Real Time Kinematic UAV: Unmanned Aerial Vehicle UAS: Unmanned Aerial System 4 Overview Clause 5 describes the positioning use cases, categorized by verticals, as follows: - Regulatory (e.g. emergency call, LI) - Mission Critical - Location-Based Services (e.g. LCS, gaming, social networking, position-enabled advertisement) - Industry and eHealth (e.g. automation, asset management and tracking, device telemetry – metering, patient monitoring) - Road (e.g. vehicle environment, road-user charging) - Railway - Maritime - Aerials (e.g. UAV/UAS) - Others A synthesis of all the use cases requirements is provided in Clause 6 summarising targets for positioning services along with a grouping of some use cases, when this grouping is possible and relevant. Clause 7 develops some considerations on the suitability of positioning technologies for the identified use cases, considering both 3GPP and non-3GPP positioning technologies. The related mapping builds on a background material to reveal the use cases that can be covered by existing technologies (standalone or combined) and the use cases for which 3GPP new positioning technologies (e.g. NR-enabled) are needed to cope with the shortcomings of existing technologies. Clause 8 identifies initial potential requirements for 5G positioning services based on the considerations developed in Clause 7. 5 Use cases 5.1 Foreword 5.1.1 Key Performance Indicators and Key attributes for positioning use cases The following KPI apply to the definition of the use-cases positioning requirements: - Position accuracy: describes the closeness of the measured position of the UE to its true position value. The accuracy can describe the accuracy either of an absolute position or of a relative position. It can be further derived into a horizontal position accuracy – referring to the position error in a 2D reference or horizontal plane, and into a vertical position accuracy – referring to the position error on the vertical axis or altitude. - Speed accuracy: describes the closeness of the measured magnitude of the UE’s velocity to the true magnitude of the UE’s velocity. - Bearing accuracy: describes the closeness of the measured bearing of the UE to its true bearing. Both the measured and the true bearing are defined in a common base coordinate system, using yaw-pitch-roll as for aircraft principal axes. For a moving UE, the bearing is a measure of the velocity’s direction and this KPI can be combined with speed accuracy into the velocity’s accuracy. - Timestamp accuracy: the position-related data (e.g. position, velocity) are usually associated to a timestamp, marking the time when the position-related data has been determined. The timestamp accuracy describes the closeness of the timestamp value to the true instant when the related data was computed. - Availability: percentage of time when a positioning system is able to provide the required position-related data within the performance targets or requirements. - Latency: time elapsed between the event that triggers the determination of the position-related data and the availability of the position-related data at the positioning system interface. At initialisation of the positioning system, the latency is also defined as the Time to First Fix. - Time to First Fix (TTFF): time elapsed between the event triggering for the first time the determination of the position-related data and the availability of the position-related data at the positioning system interface. TTTF is greater or equal to Latency. - Update rate: rate at which the position-related data is generated by the positioning system. It is the inverse of the time elapsed between two successive position-related data. - Power consumption: electrical power (usually in mW) used by the positioning system to produce the position-related data. - Energy per Fix: electrical energy (usually in mJ per fix) used by the positioning system to produce the position-related data. It represents the integrated power consumption of the positioning system over the required processing interval. It considers both the processing energy and the energy used during the idle state between two successive productions of position-related data. This KPI can advantageously replace the power consumption when the positioning system is not active continuously (e.g. device tracking). - System scalability: amount of devices for which the positioning system can determine the position-related data in a given time unit, and/or for a specific update rate. The aforementioned Key Performance Indicators can be dependent of the UE’s dynamic and/or dependent of its location in the cell. The KPI defines a target either for each dependence, or for the worst-case. Furthermore, some applications can have specific needs in terms of insurance of the quality of service, usually addressed in dedicated certification process and standards outside 3GPP. Most of the time, these applications are safety-critical or liability-critical applications. For the purpose of this document, the following additional KPIs can be considered on a case-by-case basis. - Continuity: likelihood that the positioning system functionality will be available during the complete duration of the intended operation if the positioning system is operational at the beginning of the operation. - Reliability: measure of the ability of a positioning system to provide the position-related data under stated conditions for a specified period. - Integrity: measure of the trust in the accuracy of the position-related data provided by the positioning system and the ability to provide timely and valid warnings to the UE and/or the user when the positioning system does not fulfil the condition for intended operation. - Time to alert: time elapsed between a change of the integrity (as defined above) and the information to the UE and/or the user. - Authentication: provision of assurance that the position-related data associated with the UE has been derived from trusted and authorised sources (e.g. real signals and not falsified signals). This KPI is different from security, which defines the measures to ensure that the position-related data is safeguarded against unapproved disclosure or usage inside or outside the positioning-system. Because it cannot be summarised and quantified as a scalar target, this KPI is managed as a binary field in the present report: yes or no provision of positioning authentication is needed. - Security / Privacy: measures to ensure that the position-related data is safeguarded against unapproved disclosure or usage inside or outside the positioning system and/or to ensure that a non-authorized party cannot access information relating to the privacy of the user. Because it cannot be summarised and quantified as a scalar target, this KPI is managed as a binary field in the present report: yes or no security and/o