TR 23.786 V1.0.0 (2018-12) Study on architecture enhancements for EPS and 5G System to support advanced V2X services

3GPP TR 23.786 V1.0.0 (2018-12)Technical Report3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Study on architecture enhancements for EPS and 5G System to support advanced 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.786 V1.0.0 (2018-12)109Release 16Keywords3GPP, 5G, Architecture, EPS, V2X, services3GPPPostal 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 AssociationContentsForeword91Scope102References103Definitions and abbreviations113.1Definitions113.2Abbreviations114Architectural Assumptions and Requirements114.1Architectural Assumptions114.1.1General114.1.2PC5 and NG-RAN Uu based V2X architecture reference model124.2Architectural Requirements125Key Issues125.1Key Issue #1: Support of eV2X Group Communication125.1.1General description125.2Key Issue #2: 3GPP PC5 RAT selection for a V2X application125.2.1General description125.3Key Issue #3: QoS Support for eV2X over Uu interface135.3.1General description135.4Key Issue #4: Support of PC5 QoS framework enhancement for eV2X145.4.1General description145.5Key Issue #5: Service Authorization and Provisioning to UE for eV2X communications over PC5 reference point145.5.1General description145.6Key Issue #6: Service Authorization to NG-RAN for eV2X communications over PC5 reference point155.6.1General description155.7Key Issue #7: Network Slicing for eV2X Services155.7.1General description155.8Key Issue #8: Support of edge computing155.8.1General description155.9Key Issue #9: Support of unicast/multicast for sensor sharing over PC5165.9.1General description165.10Key Issue #10: eV2X message transmission and reception175.10.1General description175.11Key Issue #11: Service Authorization and Provisioning to UE over NG-Uu reference point175.11.1General description175.12Key Issue #12: System migration and interworking for eV2X175.12.1General description175.13Key Issue #13: Support NR based PC5 communication when UE connects to EPC185.13.1General description185.14Key Issue #14: Support of broadcast over NG-Uu185.14.1General description185.15Key Issue #15: Enhancements to assist Application Adjustment195.15.1General description196Solutions196.1Solution #1: Solution for Group Communication for eV2X196.1.1Functional Description196.1.2Procedures206.1.3Impact on existing entities and interfaces206.1.4Topics for further study206.1.5Conclusions206.2Solution #2: QoS Support for eV2X over Uu interface206.2.1Functional Description206.2.1.1General description206.2.1.2Necessary QoS Characteristics for Uu Interface206.2.1.3Necessary 5QI values216.3Solution #3: Service Authorization and Provisioning to UE for eV2X communications over PC5 and NG-Uu reference points226.3.1Functional Description226.3.2Procedures236.3.2aOption of UE triggered V2X Policy provisioning procedure236.3.3Impact on existing entities and interfaces236.3.4Topics for further study246.3.5Conclusions246.4Solution #4: Reusing solution of TS23.2855 for Key Issue #5246.4.1Functional Description246.4.2Procedures246.4.3Impact on existing entities and interfaces256.4.4Topics for further study256.4.5Conclusions256.5Solution #5: Service Provisioning to UE for eV2X communications over PC5 and NG-Uu reference points256.5.1General Description256.5.2Initial Provisioning of eV2X Communication Parameters266.5.3Update of eV2X Communication Parameters266.5.3.0General266.5.3.1UE triggered update of eV2X Communication Parameters276.5.3.2Network triggered update of eV2X Communication Parameters286.5.4Impact on existing entities and interfaces286.5.5Conclusions296.6Solution #6: eV2X impacts to 5GC procedures296.6.1Functional Description296.6.2Procedures296.6.2.1Registration procedure for UE296.6.2.2Service Request procedures for UE296.6.2.3N2 Handover procedures for UE306.6.2.4Xn Handover procedures for UE306.6.2.5Nudm_SDM_UpdateNotification procedure for UE306.6.2.6V2X capability indication and V2X related information per PC5 RAT316.6.3Impact on existing entities and interfaces316.6.4Topics for further study316.6.5Conclusions326.7Solution #7: Solution for Network Slicing for eV2X services326.7.1Functional Description326.7.2Procedures326.7.3Impact on existing entities and interfaces326.7.4Topics for further study326.7.5Conclusions326.8Solution #8: Application Function influence based edge computing for V2X326.8.1Functional Description326.8.2Procedures336.8.3Impact on existing entities and interfaces356.8.4Topics for further study356.8.5Conclusions356.9Solution #9: Interworking for eV2X356.9.1Introduction356.9.2Functional Description356.9.3Procedures366.9.4Impacts on existing entities and interfaces376.9.5Evaluation376.9.6Conclusions376.10Solution #10: Interworking solution based on Architecture in A.2376.10.1Introduction376.10.2Functional Description376.10.3Procedures386.10.4Impact on existing entities and interfaces396.10.5Conclusions396.11Solution #11: Solution for unicast or multicast for eV2X communication over PC5 reference point396.11.1Functional Description396.11.2Solution description396.11.2.1Identifiers for the unicast communication396.11.2.1.1Separate L2 ID address space for unicast and multicast from those for broadcast396.11.2.1.2Deciding the Destination L2 ID to use for unicast/multicast communication396.11.2.2Signalling protocol to support unicast/multicast communication406.11.2.3QoS support and AS layer configurations406.11.2.4Security associations416.11.2.5Procedures for the link establishment and maintenance416.11.3Procedures416.11.3.1Establishment of layer 2 link over PC5416.11.3.2Contents of the signalling message for link establishment426.11.3.3Link identifier update procedure for privacy protection of unicast communication436.11.3.4Security aspects for layer 2 link446.11.4Impact on existing entities and interfaces446.11.5Topics for further study446.11.6Conclusions446.12Solution #12: 3GPP PC5 RAT selection for a V2X application446.12.1Functional Description446.12.2Procedures456.12.3Impact on existing entities and interfaces456.12.4Topics for further study456.12.5Conclusions456.13Solution #13: Solution for PC5 RAT selection456.13.1Functional Description456.13.2Procedures466.13.3Impact on existing entities and interfaces466.13.4Topics for further study466.13.5Conclusions466.14Solution #14: Solution for eV2X system migration466.14.1Functional Description466.14.1.1General description466.14.1.2PC5 based V2X communication considerations466.14.1.3Additional consideration for PC5 Mode 3 operations476.14.1.4Uu based V2X communication considerations476.14.2Procedures476.14.3Impact on existing entities and interfaces476.14.4Topics for further study486.14.5Conclusions486.15Solution #15: Network-controlled QoS mechanism for PC5 communication486.15.1General Description486.15.2Proposed QoS model for PC5 communication486.15.3Procedures486.15.4Impact on existing entities and interfaces486.15.5Conclusions496.16Solution #16: Solution for QoS Support for eV2X over Uu Interface - Enhancements for QoS Monitoring and Control496.16.1Functional Description496.16.2Procedures506.16.2.1Application Function Request to Influence eV2X QoS506.16.2.2Application Function Request of QoS Level Change Notification506.16.2.3eV2X Service Session QoS Level Change and AF Notification506.16.2.3.1Option 1 - (R)AN based multi-QoS profile506.16.2.3.2Option 2 - CN based multi-QoS profile526.16.3Impact on existing entities and interfaces526.16.4Topics for further study536.16.5Conclusions536.17Solution #17: Solution for QoS Support for eV2X over Uu Interface536.17.1Functional Description536.17.2Procedures546.17.3Impact on existing entities and interfaces556.17.4Topics for further study556.17.5Conclusions556.18Solution #18: Non-IP based V2X message transmission and reception over Uu reference point in 5GS556.18.1Functional Description556.18.2Impact on existing entities and interfaces566.18.3Topics for further study576.18.4Conclusions576.19Solution #19: QoS Support for eV2X communication over PC5 interface576.19.1Functional Description576.19.1.1General description576.19.1.2Solution description576.19.1.3V2X 5QI (VQI) values for PC5 broadcast use586.19.2Procedures586.19.2.1QoS support for unicast communication over PC5 interface586.19.2.1.0General586.19.2.1.1QoS parameters provision to UE and NG-RAN586.19.2.1.2QoS parameters negotiation between UEs596.19.2.1.3QoS handling for eV2X communication596.19.2.2QoS support for broadcast communication over PC5 interface606.19.2.3QoS support for group communication over PC5 interface606.19.3Impact on existing entities and interfaces606.19.4Topics for further study606.19.5Conclusions606.20Solution #20: Authorization Policy for eV2X communication over PC5 interface606.20.1Functional Description606.20.2Authorization Policy parameters to UE Connected to 5GC616.20.2.1Authorization Policy parameters for PC5 Communication616.20.2.2Policy parameters for NG-Uu Communication626.20.2.3Policy parameters for both Uu and NG-Uu Communication626.20.3Impact on existing entities and interfaces626.20.4Topics for further study626.20.5Conclusions626.21Solution #21: Group communication enhancement for NR PC5636.21.1Functional Description636.21.1.1General description636.21.1.2Solution description636.21.2Procedures636.21.3Impact on existing entities and interfaces656.21.4Topics for further study656.21.5Conclusions656.22Solution #22: Authorization for NR based PC5 communication when the UE is served by EPS656.22.1Functional Description656.22.1.1General Description656.22.2Procedures666.22.2.1UE indicates its NR PC5 capability to the EPS network666.22.2.2Authorization for sending V2X message over PC5 using NR RAT666.22.2.3Provisioning of V2X configuration for NR based PC5 communication.666.22.3Impact on existing entities and interfaces666.22.4Topics for further study666.22.5Conclusions666.23Solution #23: Early notification for Dynamic Application Adjustment676.23.1Functional Description676.23.2Procedures686.23.3Impact on existing entities696.23.4Evaluation706.23.5Conclusions706.24Solution #24: Solution for AF-initiated UE provisioning706.24.1Functional Description706.24.1.1General Description706.24.1.2AF-initiated Service Parameter provisioning706.24.1.3NEF service for Service Parameter provisioning716.24.1.3.1General716.24.1.3.2Nnef_ServiceParameter_Create operation716.24.1.3.3Nnef_ServiceParameter_Update operation716.24.1.3.4Nnef_ServiceParameter_Delete operation716.24.1.4V2X service parameter delivery726.24.2Procedures726.24.3Impact on existing entities and interfaces726.24.4Topics for further study736.24.5Conclusions736.25Solution #25: Solution for Key Issue #13736.25.1Functional Description736.25.2Impacts on existing entities and interfaces736.25.3Conclusions746.26Solution #26: Path-based QoS booking for Application Adjustment746.26.1Functional Description746.26.2Procedures766.26.2.1V2X application Requested Booking766.26.2.2Network Initiated Booking Update776.26.2.3Details of system interactions for resources booking786.26.2.4Impact on other procedures796.26.3Impact on existing entities and interfaces796.26.4Topics for further study796.26.5Conclusions797Conclusions797.1Conclusions for EPS807.2Conclusions for 5G System807.3Interim Conclusions for EPS81Annex A:eV2X Architecture variants82A.0Description82A.1Alternative#1: eV2X Architecture Reference Model82A.1.1Description82A.1.1.1Description of existing V2X for EPS82A.1.1.25G Description83A.1.1.3PC5 and Uu based eV2X architecture reference model83A.1.2Procedures86A.1.3Impact on existing entities and interfaces86A.1.4Topics for further study86A.2Alternative#2: Reusing EPS V2X Architecture86A.2.1Description86A.3Alternative#3: V2X Control Function as a new CP entity in 5GC89A.3.1Description89A.3.2Procedures90A.3.3Impact on existing entities and interfaces90A.3.4Topics for further study90A.4Alternative#4: eV2X Architecture Reference Model91A.4.1Description91Annex B:Solutions for broadcast/multicast/group delivery over Uu93B.0Description93B.1Solution #B1: Support of broadcast in 5GS93B.1.1Functional Description93B.1.1.0General93B.1.1.15G-MBMS Architecture93B.1.1.2Service-based interfaces and Reference points94B.1.2Procedures94B.1.2.1Service Announcement94B.1.2.2TMGI Management94B.1.2.3MBMS Session Management94B.1.3Impact on existing entities and interfaces95B.1.4Topics for further study95B.1.5Conclusions95B.2Solution #B2: Support of broadcast/multicast/group delivery over Uu95B.2.1Introduction95B.2.2Architecture96B.2.3Support of EPC interworking96B.2.4Procedures96B.2.4.1Service announcement96B.2.4.2TMGI Management96B.2.4.2.1General96B.2.4.2.2TMGI Allocation97B.2.4.2.3TMGI Refresh97B.2.4.2.4TMGI deallocation98B.2.4.3Create, Update and Release a Group Session98B.2.4.3.1General98B.2.4.3.2Triggering of the Group Session Establishment99B.2.4.3.3Triggering of Session release100B.2.4.3.4Triggering of Session Modification101B.2.5Impacts on existing entities and interfaces/Functional Entities101B.2.5.1Impacts on existing entities102B.2.5.2Impacts on existing interfaces102B.2.6Evaluation103B.3Solution #B3: Support for eMBMS over EPS MBMS with independent unicast from 5GS103B.3.1Functional Description103B.3.1.1General description103B.3.1.2Solution description103B.3.1.2.1General solution for support of receiving eMBMS traffic for UE connected to 5GS103B.3.1.2.2Applying the general solution to eV2X104B.3.2Procedures105B.3.3Impact on existing entities and interfaces105B.3.4Topics for further study105B.3.5Conclusions105B.4Solution #B4: Support of multicast/groupcast/broadcast services in 5GS105B.4.1Functional Description105B.4.1.1Architecture105B.4.1.2Service-based interfaces and Reference points107B.4.2Procedures107B.4.3Impact on existing entities and interfaces107B.4.4Topics for further study107B.4.5Conclusions107Annex C:Change history108ForewordThis 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 Technical Report is to identify and evaluate potential architecture enhancements of EPS and 5G System design needed to support advanced V2X services identified in TR22.8862, based on vehicular services requirements defined in TS22.1853 and TS22.1864 and determine which of the solutions can proceed to normative specifications.In Rel-15, the study focuses on EPS.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.23GPPTR22.886: Study on enhancement of 3GPP Support for 5G V2X Services.33GPPTS22.185: Service requirements for V2X services; Stage 1.43GPPTS22.186: Enhancement of 3GPP support for V2X scenarios; Stage 1.53GPPTS23.285: Architecture enhancements for V2X services.63GPPTS22.278: Service requirements for the Evolved Packet System (EPS).73GPPTS23.501: System Architecture for the 5G System; Stage2.83GPPTS23.303: Proximity-based Services (ProSe); Stage 2.93GPPTS23.502: Procedures for the 5G System; Stage2.103GPPTS23.503: Policy and Charging Control Framework for the 5G System; Stage2.113GPPTS33.303: Proximity-based Services (ProSe); Security aspects.123GPPTS23.203: Policy and charging control architecture.133GPPTS24.334: Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3.143GPPTS36.440: General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN.153GPPTR23.724: Study on Cellular IoT support and evolution for the 5G System.163GPPTS23.246: Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description.173GPPTS26.346: Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs.183GPPTS25.446: MBMS synchronisation protocol (SYNC).193GPPTS36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2.203GPPTR23.791: Study of Enablers