TR 22.886 V16.2.0 (2018-12) Study on enhancement of 3GPP Support for 5G V2X Services

3GPP TR 22.886 V16.2.0 (2018-12)Technical Report3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Study on enhancement of 3GPP Support for 5G V2X Services(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.886 V16.2.0 (2018-12)76Release 16KeywordsV2X, eV2X, Vehicular communication3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2018, 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 members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsForeword81Scope92References93Definitions and abbreviations113.1Definitions113.2Abbreviations124Overview125Use cases135.1eV2X support for vehicle platooning135.1.1Description135.1.2Potential requirements135.2Information exchange within platoon145.2.1Description145.2.1.1General145.2.1.2Pre-conditions155.2.1.3Service flows155.2.1.4Post-conditions155.2.2Potential requirements155.3Automotive: sensor and state map sharing155.3.1Description155.3.1.1General155.3.1.2Pre-conditions165.3.1.3Service flows165.3.1.4Post-conditions165.3.2Potential requirements165.4eV2X support for remote driving175.4.1Description175.4.2Potential requirements175.5Automated cooperative driving for short distance grouping185.5.1Description185.5.1.1General185.5.1.2Pre-conditions195.5.1.3Service flows195.5.1.4Post-conditions205.5.2Potential requirements205.6Collective perception of environment205.6.1Description205.6.1.1General205.6.1.2Pre-conditions215.6.1.3Service flows225.6.1.4Post-conditions225.6.2Potential requirements225.7Communication between vehicles of different 3GPP RATs225.7.1Description225.7.2Potential requirements245.8Multi-PLMN environment245.8.1Description245.8.1.1General245.8.1.2Pre-conditions245.8.1.3Service flows245.8.1.4Post-conditions245.8.2Potential requirements245.9Cooperative collision avoidance (CoCA) of connected automated vehicles255.9.1Description255.9.1.1General255.9.1.2Pre-conditions255.9.1.3Service flows255.9.1.4Post-conditions255.9.2Potential requirements255.10Information sharing for partial/ conditional automated driving265.10.1Description265.10.1.1General265.10.1.2Pre-conditions265.10.1.3Service flows275.10.1.4Post-conditions275.10.2Potential requirements275.11Information sharing for high/full automated driving285.11.1Description285.11.1.1General285.11.1.2Pre-conditions285.11.1.3Service flows285.11.1.4Post-conditions295.11.2Potential requirements295.12Information sharing for partial/ conditional automated platooning295.12.1Description295.12.1.1General295.12.1.2Pre-conditions305.12.1.3Service flows305.12.1.4Post-conditions305.12.2Potential requirements315.13Information sharing for high/full automated platooning315.13.1Description315.13.1.1General315.13.1.2Pre-conditions325.13.1.3Service flows325.13.1.4Post-conditions325.13.2Potential requirements325.14Dynamic ride sharing335.14.1 Description335.14.1.1General335.14.1.2Pre-conditions335.14.1.3Service flows335.14.1.4Post-conditions345.14.2Potential requirements345.15Use case on multi-RAT345.15.1Description345.15.2 Potential requirements345.16Video data sharing for assisted and improved automated driving (VaD)345.16.1Description345.16.1.1General345.16.1.2Pre-conditions355.16.1.3Service flows355.16.1.4Post-conditions355.16.2Potential requirements355.17Changing driving-mode365.17.1Description365.17.1.1General365.17.1.2Pre-conditions365.17.1.3Service flows375.17.1.4Post-conditions375.17.2Potential requirements375.18Tethering via Vehicle385.18.1 Description385.18.1.1General385.18.1.2Pre-conditions385.18.1.3Service flows385.18.1.4Post-conditions395.18.2Potential requirements395.19Use case out of 5G coverage395.19.1Description395.19.2 Potential requirements405.20Emergency trajectory alignment405.20.1Description405.20.1.1General405.20.1.1Pre-conditions405.20.1.2Service flows405.20.1.3Post-conditions415.20.2Potential requirements415.21Teleoperated support (TeSo)415.21.1Description415.21.1.1General415.21.1.2Pre-conditions415.21.1.3Service flows425.21.1.4Post-conditions425.21.2Potential requirements425.22Intersection safety information provisioning for urban driving425.22.1Description425.22.1.1General425.22.1.2Pre-conditions435.22.1.3Service flows435.22.1.4Post-conditions445.22.1.5Potential impacts or interactions with existing services/features445.22.2Potential requirements445.23Cooperative lane change (CLC) of automated vehicles445.23.1Description445.23.1.1General445.23.1.2Pre-conditions455.23.1.3Service flows455.23.1.4Post-conditions455.23.2Potential requirements455.24Proposal for secure software update for electronic control unit455.24.1Description455.24.1.1General455.24.1.1Pre-conditions455.24.1.2Service flows465.24.1.3Post-conditions465.24.2Potential requirements:465.253D video composition for V2X scenario465.25.1Description465.25.2 Potential requirements475.26QoS aspect of vehicles platooning475.26.1General description475.26.2Adjustment of gaps for platooning475.26.2.1Description475.26.2.2Potential requirements485.27QoS aspects of advanced driving485.27.1General485.27.2Assistance to automated driving495.27.2.1Service flows495.27.2.2Potential Requirements495.27.3Authorization to support automated driving495.27.3.1Service flows495.27.3.2Potential Requirements505.27.4Notification of updated information to support automated driving505.27.4.1Service flows505.27.4.2Potential Requirements505.27.5Support for adjustment and big data transport515.27.5.1Service flows515.27.5.2Potential Requirements515.27.6Support of automated driving in multi-PLMN environments515.27.6.1Service flows515.27.6.2Potential Requirements525.27.7Reliable and guaranteed connectivity service525.27.7.1Service flows525.27.7.2Potential Requirements535.28QoS aspect of remote driving535.28.1Notification of QoS change for remote driving application535.28.1.1Description535.28.1.2Pre-conditions535.28.1.3Service Flows545.28.1.4Post-conditions545.28.1.5Potential Requirements545.28.2Support of remote Driving545.28.2.1General545.28.2.2Disengagement of autonomous driving545.28.2.3Provision of freedom of mobility555.28.2.4Potential requirements555.29QoS Aspect for extended sensor565.29.1 Description565.29.1.1 Pre-conditions565.29.1.2Service Flow575.29.1.3Post-conditions575.29.2 Potential Requirements575.30Different QoS estimation for different V2X applications575.30.1 Description575.30.1.1 Pre-conditions585.30.1.2Service Flow585.30.1.3Post-conditions595.30.2 Potential Requirements596Considerations606.1Considerations on network slicing606.2Considerations on deployment and mobility606.3Considerations on relation to requirements of LTE V2X607Potential requirements617.1General617.2Consolidated requirements617.2.1General requirements617.2.2Requirements for platooning627.2.3Requirements for advanced driving647.2.4Requirements for extended sensors657.2.5Requirements for remote driving657.2.6Requirements for vehicle quality of service support668Conclusion and recommendations68Annex A:Mapping of use cases to use case group69Annex B:Mapping table between PRs and CPRs71Annex C:Other considered use cases74C.1Interoperability with other V2X schemes74C.1.1Description74C.1.1.1General74C.1.1.2Pre-conditions74C.1.1.3Service flows74C.1.1.4Post-conditions74Annex D:Change history75ForewordThis 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.zwhere:xthe first digit:1presented to TSG for information;2presented to TSG for approval;3or greater indicates TSG approved document under change control.ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incorporated in the document.1ScopeThe objective of this document is to identify use cases and potential service requirements to enhance 3GPP support for V2X service in the following areas:-Support for non-safety V2X services (also, referred to as comfort service) (e.g. connected vehicle, mobile high data rate entertainment, mobile hot-spot/office/home, dynamic digital map update)-Support for safety-related V2X services (e.g. autonomous driving, car platooning, priority handling between safety-related V2X services and other services) -Support for V2X services in multiple 3GPP RATs (e.g. LTE, New RAT (NR) and networks environment, including aspects such as interoperability with non-3GPP V2X technology (e.g. ITS-G5, DSRC, ITS-Connect) In this document, V2X-related use cases and potential requirements already included in TR 22.891 are considered and new ones are introduced. The identification of use cases and potential requirements covers both evolved LTE RAT and new 3GPP RAT (e.g. NR) and also covers V2X operation using 3GPP RATs where there are non-3GPP V2X technologies (e.g. ITS-G5, DSRC, ITS-Connect) in use. 2ReferencesThe 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.13GPPTR21.905: Vocabulary for 3GPP Specifications.25G-PPP-White-Paper-on-Automotive-Vertical-Sectors. 3 ETSI TR 103 299 (V0.0.10): Intelligent Transport System, Cooperative Adaptive Cruise Control (CACC).4ADASIS, http:/adasis.org5ETSI TR 102 863 (V1.1.1): Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Local Dynamic Map (LDM); Rationale for and guidance on standardization.6 Draft ETSI EN 302 895 (V1.0.0): Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Local Dynamic Map (LDM) Concept for Local Dynamic Maps.7 ISO/TS 18750:2015 Intelligent transport systems - Cooperative systems - Definition of a global concept for Local Dynamic Maps.8Nan Hu, Hamid Aghajan, Tianshi Gao, Jaime Camhi, Chu Hee Lee and Daniel Rosario Smart Node: Intelligent Traffic Interpretation, World Congress on Intelligent Transport Systems, New York, 2008.9TNO, Truck Platooning; driving the future of transportation TNO Whitepaper, 2015.10S. Shladover, PATH at 20 - History and Major Milestones, Inteligent Transportation Systems, vol. 8, 2007.11Multi channel operation, ETSI ITS Workshop 2016, https:/docbox.etsi.org/Workshop/2016/201603_ITS_WORKSHOP/S02_ITS_NEXT_CHALLENGES/MULTI_CHANNEL_OPERATION_spaanderman_paulsconsultancy.pdf12Bergenhem C., Shladover S., Coelingh E., Englund C., andTsugawa S., Overview of platooning systems, in Proceedings of the 19th ITS World Congress, Oct 22-26, Vienna, Austria (2012), 2012.13V2V Communication Quality: Measurements in a Cooperative Automotive Platooning Application, Carl Bergenhem Qamcom Research and Technology AB, Erik Coelingh Volvo Car Corp.Rolf Johansson SP Technical Research Inst of Sweden, Ali Tehrani Qamcom Research & Technology, https:/www.researchgate.net/profile/Carl_Bergenhem/publication/262451443_V2V_Communication_Quality_Measurements_in_a_Cooperative_Automotive_Platooning_Application/links/0f317537c05258c754000000.pdf14S. W. Kim et al., Multivehicle Cooperative Driving Using Cooperative Perception: Design and Experimental Validation, in IEEE Transactions on Intelligent Transportation Systems, vol. 16, no. 2, pp. 663-680, April 2015.15A. Rauch, F. Klanner and K. Dietmayer, Analysis of V2X communication parameters for the development of a fusion architecture for cooperative perception systems, Intelligent Vehicles Symposium (IV), 2011 IEEE, Baden-Baden, 2011, pp. 685-690.16METIS-II_D1.1_v1.0 Refined scenarios and requirements, consolidated use cases, and qualitative techno-economic feasibility assessment.17L. Licciardi, M. P. Galante : 5G CRITICAL COMMUNICATION USE CASES, ETSI 5G: From Myth to Reality, 2016, http:/www.etsi.org/news-events/events/1025-2016-04-5g-from-myth-to-reality18 Ford: From Autonomy to Snowtonomy: How Ford Fusion Hybrid Autonomous Reasearch Vehicle can Navigate in Winter, http:/www.at.ford.com/SiteCollectionImages/2016_NA/March/From%20Autonomy%20to%20Snowtonomy.pdf195G Infrastructure Public Private Partnership (5G-PPP) (2015): 5G automotive vision, 65 p., https:/5g-ppp.eu/, September 2015.20NGMN Perspectives on Vertical Industries and Implications for 5G, https:/www.ngmn.org/uploads/media/160610_NGMN_Perspectives_on_Vertical_Industries_and_Implications_for_5G_v1_0.pdf21ITS Japan, http:/www.kantei.go.jp/jp/singi/it2/senmon_bunka/douro/dai2/siryou4_8.pdf22NEDOs Energy ITS Project in Japan for Automated Truck Platooning, http:/www.nedo.go.jp/content/100541227.pdf23NHTSA Human Factors Evaluation of Level 2 and Level 3 Automated Driving Concepts, http:/www.nhtsa.gov/DOT/NHTSA/NVS/Crash%20Avoidance/Technical%20Publications/2015/812182_HumanFactorsEval-L2L3-AutomDrivingConcepts.pdf24M. Althoff, O. Stursberg, and M. Buss, Safety assessment of driving behavior in multi-lane traffic for autonomous vehicles, in Proc. IEEE Intelligent Vehicles Symposium, pp. 893-900, June 2009.253GPPTS22.185: Service requirements for V2X services.26P. Gomes, F. Vieira and M. Ferreira, The See-Through System: From implementation to test-drive, Vehicular Networking Conference (VNC), 2012 IEEE, Seoul, 2012, pp. 40-47.27J. Choi, N. Gonzlez-Prelcic, R. Daniels, C. R. Bhat, and R. W. Heath, Jr., Millimeter Wave Vehicular Communication to Support Massive Automotive Sensing, submitted to IEEE Communications Magazine, Jan. 2016.28N. Andersen, C2C-Consortium Towards Accident Free Driving, ETSI Summit 5G from Myth to Reality, 2016.29M. Amoozadeh, H. Deng, C.-N. Chuah, H. M. Zhang, and D. Ghosal, Platoon management with cooperative adaptive cruise control enabled by VANET, ELSEVIER Vehicular Communications, vol. 2. no. 2, pp. 110-123, Apr. 2015.30R. Alieiev, A. Kwoczek and T. Hehn, Automotive requirements for future mobile networks, Microwaves for Intelligent Mobility (ICMIM), 2015 IEEE MTT-S International Conference on, Heidelberg, 2015, pp. 1-4.31M. Dring, K. Franke, et al., Adaptive cooperative manoeuvre planning algorithm for conflict resolution in diverse traffic situations, 2014 International Conference on Connected Vehicles and Expo (ICCVE), Vienna, 2014, pp. 242-249.323GPPTR22.885: Study on LTE support for V2X services.33DOT HS 811 492B, Vehicle Safety Communications Applications (VSC-A) Final Report: Appendix Volume 1, System Design and Objective Test, pp C-2-4 and C-2-5.34A. Kwoczek (Volkswagen AG), Automotive Requirements for Future Networks, Information Technology Society (ITG), Communication Technology, May, 2016.35Void365G-PPP Project on 5G Air Interface Below 6 GHz, Deliverable D2.1: Air interface framework and specification of system level simulations, http:/fantastic5g.eu/wp-content/uploads/2016/06/FANTASTIC-5G_D2_1_final_modified.pdf.37ETSI TS 102 894-2 V1.2.1, Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionary.38SAE International, AUTOMATED DRIVING LEVELS OF DRIVING AUTOMATION ARE DEFINED IN NEW SAE INTERNATIONAL STANDARD J3016; US Homeland Security Digital Library, Self-Driving Cars: Levels of Automation, March 2017 https:/www.hsdl.org/?view&did=801463.39U.S. Department of Transportation, Federal Automated Vehicles Policy, Sept. 2016. https:/one.nhtsa.gov/nhtsa/av/av-policy.html3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in TR21.9051 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR21.9051.End-to-end latency: time it takes to transfer a given piece of information from a source to a destination, measured at the application level, from the moment it is transmitted by the source to the moment it is received at the destination.Road Side Unit: A stationary infrastructure entity supporting V2X applications that can exchange messages with other entities supporting V2X applications.NOTE: RSU is a term frequently used in existing ITS specifications, and the reason for introducing the term in the 3GPP specifications is to make the documents easier to read for the ITS industry. RSU is a logical entity that supports V2X application logic using the functionality providedby either a 3GPP network or an UE (referred to as UE-type RSU).3.2AbbreviationsFor the purposes of the present document, the abbreviations given in TR21.9051 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR21.9051.CACCCooperative Adaptive Cruise Control LoALevel of AutomationRSURoad Side UnitV2IVehicle to InfrastructureV2VVehicle to Vehicle4OverviewA basic set of requirements for EPS to support V2X applications have been specified in 25. These requirements are considered suff