23795-200_cl Study on application layer support for V2X services;

3GPP TR 23.795 V2.0.0 (2018-09)Technical Report3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Study on application layer support for 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 23.795 V2.0.0 (2018-09)77Release 16Keywords3GPPPostal 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.2Abbreviations114Analysis of V2X standards124.13GPP V2X service requirements124.1.1Description124.1.2Analysis134.23GPP EPS architecture for V2X communications154.2.1Description154.2.2Analysis154.3ETSI ITS communication architecture and requirements154.3.1Description154.3.2Analysis164.4SAE and related standards communication architecture and requirements164.4.1Description164.4.2Analysis165Key issues175.1Key issue 1 - Communication of V2X application QoS requirements with 3GPP systems175.1.1General175.1.2Key issue 1a - Communication of V2X application network QoS requirements with 3GPP systems175.1.3Key issue 1b - Communication of V2X application PC5 QoS requirements with 3GPP systems185.2Key issue 2 - Monitoring network situation of 3GPP systems by V2X application185.3Key issue 3 - V2X USD provisioning via V1 reference point185.4Key issue 4 - Local service information195.5Key issue 5 - Service continuity during MBMS based V2X traffic205.6Key issue 6 - Handling MBMS bearer suspension215.7Key Issue 7 - V2X UE capabilities reporting215.8Key issue 8 - PC5 parameters provisioning over V1225.9Key issue 9 V2X group communication225.10Key issue 10 UE location report over V1225.11Key issue 11 - Support for uplink video streaming235.12Key issue 12 - Handling multiple V2X application priorities at the V2X UE235.13Key issue 13 - Communicating application requirements from the V2X application server235.14Key issue 14 - Network assistance for enhancing QoE in V2X applications245.15Key issue 15 - V2X USD provisioning using existing MBMS service announcement mechanisms245.16Key issue 16 - Supporting larger files or V2X messages245.17Key issue 17 - Determining UE location for a geographical area255.18Key issue 18 - Resolving UE address for ETSI ITS facility layer messages255.19Key issue 19 - Resolving security issues for ETSI ITS distribution255.20Key issue 20 V2X dynamic groups255.21Key issue 21 V2X application support for network slicing265.22Key issue 22 Support for operation modes selection for V2V communications265.23Key issue 23 Support for service continuity between Uu and UE-to-network relay for V2X communications266Assumptions and architectural requirements276.1Assumptions276.2Architectural requirements276.2.1General276.2.1.1Description276.2.1.2Requirements276.2.2Location276.2.2.1Description276.2.2.2Requirements276.3Network situation monitoring requirements276.3.1Description276.3.2Requirements276.43GPP system related parameters provisioning286.4.1Description286.4.2Requirements286.5PC5 based V2X group communication286.5.1Description286.5.2Requirements287Solutions287.1Solution #1: V2X application layer functional model287.1.1Solution description287.1.1.1General287.1.1.2V2X application layer functional model287.1.1.3Functional entities description297.1.1.3.1General297.1.1.3.2V2X application specific client307.1.1.3.3V2X application enabler client307.1.1.3.4V2X application specific server307.1.1.3.5V2X application enabler server307.1.1.4Reference points317.1.1.4.1General317.1.1.4.2V1-AE317.1.1.4.3V1-APP317.1.1.4.4V5-AE317.1.1.4.5V5-APP317.1.1.4.6Vs317.1.1.4.7Vc317.1.1.5Reference points between the V2X application layer and the 3GPP network systems317.1.1.5.1General317.1.1.5.2V2317.1.1.5.3Rx317.1.1.5.4MB2327.1.1.5.5xMB327.1.1.5.6T8327.1.1.6Deployment models for the V2X application layer functional model327.1.1.6.1General327.1.1.6.2Centralized deployment327.1.1.6.3Distributed deployment337.1.2Solution evaluation357.2Solution #2: UE location report over V1357.2.1Solution description357.2.1.1General357.2.1.2Location reporting event triggers configuration procedure357.2.1.3Location reporting event triggers configuration cancel procedure367.2.1.4Location reporting procedure367.2.2Solution evaluation377.3Solution #3: Handling MBMS bearer suspension via V1377.3.1Solution description377.3.1.1General377.3.1.2Procedure377.3.2Solution evaluation387.4Solution #4: V2X USD provisioning via V1 reference point387.4.1Solution description387.4.1.1General387.4.1.2Procedure387.4.2Solution evaluation397.5Solution #5: V2X UE obtaining the local service information397.5.1Solution description397.5.1.1General397.5.1.2Procedure397.5.2Solution evaluation407.6Solution #6: PC5 parameters provisioning via V1 reference point417.6.1Solution description417.6.1.1General417.6.1.2Procedure417.6.2Solution evaluation417.7Solution #7: Network situation and QoS monitoring427.7.1Solution description427.7.1.1General427.7.1.2Network situation and QoS monitoring events427.7.1.3Procedure for network situation and QoS monitoring427.7.1.4Procedure for network situation and QoS monitor reporting437.7.2Solution evaluation437.8Solution #8: V2X USD provisioning using SACH447.8.1Solution description447.8.1.1General447.8.1.2Procedure447.8.2Solution evaluation447.9Solution #9: Abstraction of network QoS aspects for V2X communications457.9.1Solution description457.9.1.1General457.9.1.2Procedure457.9.2Solution evaluation467.10Solution #10: Communication of V2X application PC5 QoS requirements with 3GPP systems467.10.1Solution description467.10.1.1General467.10.1.2ProSe Per-Packet Priority values467.10.1.3Procedure467.10.2Solution evaluation467.11Solution #11: Switching from MBMS delivery to unicast delivery477.11.1Solution description477.11.2Solution evaluation487.12Solution #12: Supporting for V2X group communication487.12.1Solution description487.12.1.1General487.12.1.2VAE server pushes ProSe group communication parameters procedure487.12.2Solution evaluation497.13Solution #13: Group communication parameters provisioning via V5497.13.1Solution description497.13.1.1General497.13.1.2Procedure507.13.2Solution evaluation517.14Solution #14: Autonomous decision for assigning ProSe Layer-2 Group ID517.14.1Solution description517.14.1.1General517.14.1.2Procedure517.14.2Solution evaluation527.15Solution #15: Support for uplink video streaming using FLUS framework527.15.1Solution description527.15.1.1General527.15.1.2Procedure527.15.2Solution evaluation537.16Solution #16: Communicating application requirements from the V2X application server537.16.1Solution description537.16.1.1General537.16.1.2Procedure for subscription to the 3GPP network system537.16.1.3Procedure for communication of application requirements547.16.1.4Procedure for notification generation547.16.2Solution evaluation547.17Solution #17: Network assistance for enhancing QoE in V2X applications using SAND framework557.17.1Solution description557.17.1.1General557.17.1.2Procedure557.17.2Solution evaluation557.18Solution #18: Support for QoE reporting567.18.1Solution description567.18.1.1General567.18.1.2Procedure567.18.2Solution evaluation567.19Solution #19: Support for larger files using MBMS non-Transparent xMB Session Types567.19.1Solution description567.19.1.1General567.19.1.2Procedure577.19.2Solution evaluation577.20Solution #20: Support for file transfer577.20.1Solution description577.20.1.1General577.20.1.2Procedure for file upload using HTTP577.20.1.3Procedure for file download using HTTP587.20.2Solution evaluation597.21Solution #21: Resolving UE address for ETSI ITS facility layer messages597.21.1Solution description597.21.1.1General597.21.1.2Procedure for tracking geographical location at the VAE server597.21.1.3Procedure for message delivery to target geographical locations from the VAE server607.21.2Solution evaluation617.22Solution #22: Resolving security issues for ETSI ITS distribution617.22.1Solution description617.22.1.1General617.22.1.2Procedure for V2X UE to V2X application server communication scenario617.22.1.3Procedure for V2X application server to V2X UE communication scenario627.22.2Solution evaluation627.23Solution #23: Supporting V2X dynamic group communication over Uu637.23.1Solution description637.23.1.1General637.23.1.2VAE server configuring dynamic group parameters procedure637.23.1.3Enabling V2X UEs to join V2X dynamic group procedure647.23.1.4Switching from Uu to PC5 V2X communications controlled by UE procedure647.23.2Solution evaluation657.24Solution #24: Supporting V2X dynamic group communication over PC5657.24.1Solution description657.24.1.1General657.24.1.2Enabling dynamic group formation procedure657.24.2Solution evaluation667.25Solution #25: Dynamic group management667.25.1Solution description667.25.1.1Group creation677.25.1.2Group join controlled by the VAE server677.25.1.3Group join over PC5 controlled by the authorized VAE client687.25.2Solution evaluation697.26Solution #26: Abstraction and control of network slice instance for V2X communications697.26.1Solution description697.26.1.1General697.26.1.2Procedure707.26.2Solution evaluation717.27Solution #27: Switching the mode of operation for V2V communications controlled by network717.27.1Solution description717.27.1.1General717.27.1.2Switching from Direct (PC5) to Indirect (Uu) V2V communications717.27.1.3Switching from Indirect (Uu) to Direct (PC5) V2V communications727.27.2Solution evaluation738Overall evaluation748.1General748.2Architecture evaluation748.3Key issue and solution evaluation749Conclusions76Annex A: Change history77ForewordThis 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.1Scope The present document is a technical report which identifies the application architecture aspects to support V2X services, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems.The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to V2X in 3GPPTS22.1852, 3GPPTS22.1863 and 3GPPTS23.2858, as well as V2X application standards defined outside 3GPP.This document will provide recommendations for normative work.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.23GPPTS22.185: Service requirements for V2X services; Stage 1.33GPPTS22.186: Enhancement of 3GPP support for V2X scenarios; Stage 1.43GPP TS 22.804: Study on Communication for Automation in Vertical domains (CAV).53GPPTR22.886: Study on enhancement of 3GPP Support for 5G V2X Services.63GPPTS23.246: Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description.73GPPTS23.280: Common functional architecture to support mission critical services; Stage 2.83GPPTS23.285: Architecture enhancements for V2X services.93GPPTS23.303: Proximity-based services (ProSe); Stage 2.103GPPTS23.468: Group Communication System Enablers for LTE (GCSE_LTE); Stage 2.113GPPTS23.501: System Architecture for the 5G System; Stage 2.123GPPTS23.502: Procedures for the 5G System; Stage 2133GPPTS23.682: Architecture enhancements to facilitate communications with packet data networks and applications.143GPPTR23.780: Study on Multimedia Broadcast and Multicast Service (MBMS) usage for mission critical communication services.153GPPTS26.238: Uplink Streaming.163GPPTS24.386: User Equipment (UE) to V2X control function; protocol aspects; Stage 3.173GPPTS26.247: Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH).183GPPTS26.346: Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs.193GPPTS26.347: Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL.203GPPTS26.348: Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point.213GPPTS28.530: Management of 5G networks and network slicing; Concepts, use cases and requirements.223GPPTS29.214: Policy and Charging Control over Rx reference point.233GPPTS29.468: Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3.243GPPTS36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2.253GPPTS36.321: Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification.263GPPTS36.443: Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application Protocol (M2AP).27ETSITS102723-8(V1.1.1): Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 8: Interface between security entity and network and transport layer.28ETSITS102940(V1.3.1): Intelligent Transport Systems (ITS); Security; ITS communications security architecture and security management.29ETSITS103097(V1.3.1): Intelligent Transport Systems (ITS); Security; Security header and certificate formats.30ETSITS103301(V1.1.1): Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services.31ETSIEN302637-2(V1.3.1): Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service.32ETSIEN302637-3(V1.2.1): Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service.33ETSIEN302665(V1.1.1): Intelligent Transport Systems (ITS); Communications Architecture.34IEEE1609.0-2013: IEEE Guide for Wireless Access in Vehicular Environments (WAVE) architecture.35International Organization for Standards, ISO21217:2014: Intelligent transport systems - Communications access for land mobiles (CALM) Architecture, https:/www.iso.org/standard/61570.html.36International Organization for Standards, ISO/DIS17515-3: Intelligent transport systems - Evolved-universal terrestrial radio access network - Part 3: LTE-V2X, https:/www.iso.org/standard/73238.html.37SAE International, SAEJ3016: Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles, https:/www.sae.org/standards/content/j3016.38SAE International, SAEJ2945/3: Requirements for V2I Weather Applications, https:/www.sae.org/standards/content/j2945/3.39SAE International, SAEJ2945/4: DSRC Messages for Traveler Information and Basic Information Delivery, https:/www.sae.org/standards/content/j2945/4.40SAE International, SAEJ2945/6: Performance Requirements for Cooperative Adaptive Cruise Control and Platooning, https:/www.sae.org/standards/content/j2945/6.41SAE International, SAEJ3161: On-Board System Requirements for LTE V2X V2V Safety Communications, https:/www.sae.org/standards/content/j3161.3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in 3GPP 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 3GPP TR21.9051.Editors note:Definitions for terms used in this document are FFS.3.2AbbreviationsFor the purposes of the present document, the abbreviations given in 3GPP 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 3GPP TR21.9051.5G5th Generation5GS5G SystemANAccess NetworkASApplication ServerBM-SCBroadcast-Multicast Service CentreBTPBasic Transport ProtocolCAMCooperative Awareness MessageCoRCategory of RequirementsDANEDASH Aware Network ElementDENMDecentralized Environmental Notification MessageE-UTRANEvolved Universal Terrestrial Radio Access NetworkECGI