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

《TR 23.786 V1.0.0 (2018-12) Study on architecture enhancements for EPS and 5G System to support advanced V2X services》由會員分享，可在線閱讀，更多相關《TR 23.786 V1.0.0 (2018-12) Study on architecture enhancements for EPS and 5G System to support advanced V2X services（109頁珍藏版）》請在裝配圖網(wǎng)上搜索。

3GPP TR 23.786 V1.0.0 (2018-12) Technical Report 3rd 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) 109 Release 16 Keywords 3GPP, 5G, Architecture, EPS, V2X, services 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. 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 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 Contents Foreword 9 1 Scope 10 2 References 10 3 Definitions and abbreviations 11 3.1 Definitions 11 3.2 Abbreviations 11 4 Architectural Assumptions and Requirements 11 4.1 Architectural Assumptions 11 4.1.1 General 11 4.1.2 PC5 and NG-RAN Uu based V2X architecture reference model 12 4.2 Architectural Requirements 12 5 Key Issues 12 5.1 Key Issue #1: Support of eV2X Group Communication 12 5.1.1 General description 12 5.2 Key Issue #2: 3GPP PC5 RAT selection for a V2X application 12 5.2.1 General description 12 5.3 Key Issue #3: QoS Support for eV2X over Uu interface 13 5.3.1 General description 13 5.4 Key Issue #4: Support of PC5 QoS framework enhancement for eV2X 14 5.4.1 General description 14 5.5 Key Issue #5: Service Authorization and Provisioning to UE for eV2X communications over PC5 reference point 14 5.5.1 General description 14 5.6 Key Issue #6: Service Authorization to NG-RAN for eV2X communications over PC5 reference point 15 5.6.1 General description 15 5.7 Key Issue #7: Network Slicing for eV2X Services 15 5.7.1 General description 15 5.8 Key Issue #8: Support of edge computing 15 5.8.1 General description 15 5.9 Key Issue #9: Support of unicast/multicast for sensor sharing over PC5 16 5.9.1 General description 16 5.10 Key Issue #10: eV2X message transmission and reception 17 5.10.1 General description 17 5.11 Key Issue #11: Service Authorization and Provisioning to UE over NG-Uu reference point 17 5.11.1 General description 17 5.12 Key Issue #12: System migration and interworking for eV2X 17 5.12.1 General description 17 5.13 Key Issue #13: Support NR based PC5 communication when UE connects to EPC 18 5.13.1 General description 18 5.14 Key Issue #14: Support of broadcast over NG-Uu 18 5.14.1 General description 18 5.15 Key Issue #15: Enhancements to assist Application Adjustment 19 5.15.1 General description 19 6 Solutions 19 6.1 Solution #1: Solution for Group Communication for eV2X 19 6.1.1 Functional Description 19 6.1.2 Procedures 20 6.1.3 Impact on existing entities and interfaces 20 6.1.4 Topics for further study 20 6.1.5 Conclusions 20 6.2 Solution #2: QoS Support for eV2X over Uu interface 20 6.2.1 Functional Description 20 6.2.1.1 General description 20 6.2.1.2 Necessary QoS Characteristics for Uu Interface 20 6.2.1.3 Necessary 5QI values 21 6.3 Solution #3: Service Authorization and Provisioning to UE for eV2X communications over PC5 and NG-Uu reference points 22 6.3.1 Functional Description 22 6.3.2 Procedures 23 6.3.2a Option of UE triggered V2X Policy provisioning procedure 23 6.3.3 Impact on existing entities and interfaces 23 6.3.4 Topics for further study 24 6.3.5 Conclusions 24 6.4 Solution #4: Reusing solution of TS23.285[5] for Key Issue #5 24 6.4.1 Functional Description 24 6.4.2 Procedures 24 6.4.3 Impact on existing entities and interfaces 25 6.4.4 Topics for further study 25 6.4.5 Conclusions 25 6.5 Solution #5: Service Provisioning to UE for eV2X communications over PC5 and NG-Uu reference points 25 6.5.1 General Description 25 6.5.2 Initial Provisioning of eV2X Communication Parameters 26 6.5.3 Update of eV2X Communication Parameters 26 6.5.3.0 General 26 6.5.3.1 UE triggered update of eV2X Communication Parameters 27 6.5.3.2 Network triggered update of eV2X Communication Parameters 28 6.5.4 Impact on existing entities and interfaces 28 6.5.5 Conclusions 29 6.6 Solution #6: eV2X impacts to 5GC procedures 29 6.6.1 Functional Description 29 6.6.2 Procedures 29 6.6.2.1 Registration procedure for UE 29 6.6.2.2 Service Request procedures for UE 29 6.6.2.3 N2 Handover procedures for UE 30 6.6.2.4 Xn Handover procedures for UE 30 6.6.2.5 Nudm_SDM_UpdateNotification procedure for UE 30 6.6.2.6 V2X capability indication and V2X related information per PC5 RAT 31 6.6.3 Impact on existing entities and interfaces 31 6.6.4 Topics for further study 31 6.6.5 Conclusions 32 6.7 Solution #7: Solution for Network Slicing for eV2X services 32 6.7.1 Functional Description 32 6.7.2 Procedures 32 6.7.3 Impact on existing entities and interfaces 32 6.7.4 Topics for further study 32 6.7.5 Conclusions 32 6.8 Solution #8: Application Function influence based edge computing for V2X 32 6.8.1 Functional Description 32 6.8.2 Procedures 33 6.8.3 Impact on existing entities and interfaces 35 6.8.4 Topics for further study 35 6.8.5 Conclusions 35 6.9 Solution #9: Interworking for eV2X 35 6.9.1 Introduction 35 6.9.2 Functional Description 35 6.9.3 Procedures 36 6.9.4 Impacts on existing entities and interfaces 37 6.9.5 Evaluation 37 6.9.6 Conclusions 37 6.10 Solution #10: Interworking solution based on Architecture in A.2 37 6.10.1 Introduction 37 6.10.2 Functional Description 37 6.10.3 Procedures 38 6.10.4 Impact on existing entities and interfaces 39 6.10.5 Conclusions 39 6.11 Solution #11: Solution for unicast or multicast for eV2X communication over PC5 reference point 39 6.11.1 Functional Description 39 6.11.2 Solution description 39 6.11.2.1 Identifiers for the unicast communication 39 6.11.2.1.1 Separate L2 ID address space for unicast and multicast from those for broadcast 39 6.11.2.1.2 Deciding the Destination L2 ID to use for unicast/multicast communication 39 6.11.2.2 Signalling protocol to support unicast/multicast communication 40 6.11.2.3 QoS support and AS layer configurations 40 6.11.2.4 Security associations 41 6.11.2.5 Procedures for the link establishment and maintenance 41 6.11.3 Procedures 41 6.11.3.1 Establishment of layer 2 link over PC5 41 6.11.3.2 Contents of the signalling message for link establishment 42 6.11.3.3 Link identifier update procedure for privacy protection of unicast communication 43 6.11.3.4 Security aspects for layer 2 link 44 6.11.4 Impact on existing entities and interfaces 44 6.11.5 Topics for further study 44 6.11.6 Conclusions 44 6.12 Solution #12: 3GPP PC5 RAT selection for a V2X application 44 6.12.1 Functional Description 44 6.12.2 Procedures 45 6.12.3 Impact on existing entities and interfaces 45 6.12.4 Topics for further study 45 6.12.5 Conclusions 45 6.13 Solution #13: Solution for PC5 RAT selection 45 6.13.1 Functional Description 45 6.13.2 Procedures 46 6.13.3 Impact on existing entities and interfaces 46 6.13.4 Topics for further study 46 6.13.5 Conclusions 46 6.14 Solution #14: Solution for eV2X system migration 46 6.14.1 Functional Description 46 6.14.1.1 General description 46 6.14.1.2 PC5 based V2X communication considerations 46 6.14.1.3 Additional consideration for PC5 Mode 3 operations 47 6.14.1.4 Uu based V2X communication considerations 47 6.14.2 Procedures 47 6.14.3 Impact on existing entities and interfaces 47 6.14.4 Topics for further study 48 6.14.5 Conclusions 48 6.15 Solution #15: Network-controlled QoS mechanism for PC5 communication 48 6.15.1 General Description 48 6.15.2 Proposed QoS model for PC5 communication 48 6.15.3 Procedures 48 6.15.4 Impact on existing entities and interfaces 48 6.15.5 Conclusions 49 6.16 Solution #16: Solution for QoS Support for eV2X over Uu Interface - Enhancements for QoS Monitoring and Control 49 6.16.1 Functional Description 49 6.16.2 Procedures 50 6.16.2.1 Application Function Request to Influence eV2X QoS 50 6.16.2.2 Application Function Request of QoS Level Change Notification 50 6.16.2.3 eV2X Service Session QoS Level Change and AF Notification 50 6.16.2.3.1 Option 1 - (R)AN based multi-QoS profile 50 6.16.2.3.2 Option 2 - CN based multi-QoS profile 52 6.16.3 Impact on existing entities and interfaces 52 6.16.4 Topics for further study 53 6.16.5 Conclusions 53 6.17 Solution #17: Solution for QoS Support for eV2X over Uu Interface 53 6.17.1 Functional Description 53 6.17.2 Procedures 54 6.17.3 Impact on existing entities and interfaces 55 6.17.4 Topics for further study 55 6.17.5 Conclusions 55 6.18 Solution #18: Non-IP based V2X message transmission and reception over Uu reference point in 5GS 55 6.18.1 Functional Description 55 6.18.2 Impact on existing entities and interfaces 56 6.18.3 Topics for further study 57 6.18.4 Conclusions 57 6.19 Solution #19: QoS Support for eV2X communication over PC5 interface 57 6.19.1 Functional Description 57 6.19.1.1 General description 57 6.19.1.2 Solution description 57 6.19.1.3 V2X 5QI (VQI) values for PC5 broadcast use 58 6.19.2 Procedures 58 6.19.2.1 QoS support for unicast communication over PC5 interface 58 6.19.2.1.0 General 58 6.19.2.1.1 QoS parameters provision to UE and NG-RAN 58 6.19.2.1.2 QoS parameters negotiation between UEs 59 6.19.2.1.3 QoS handling for eV2X communication 59 6.19.2.2 QoS support for broadcast communication over PC5 interface 60 6.19.2.3 QoS support for group communication over PC5 interface 60 6.19.3 Impact on existing entities and interfaces 60 6.19.4 Topics for further study 60 6.19.5 Conclusions 60 6.20 Solution #20: Authorization Policy for eV2X communication over PC5 interface 60 6.20.1 Functional Description 60 6.20.2 Authorization Policy parameters to UE Connected to 5GC 61 6.20.2.1 Authorization Policy parameters for PC5 Communication 61 6.20.2.2 Policy parameters for NG-Uu Communication 62 6.20.2.3 Policy parameters for both Uu and NG-Uu Communication 62 6.20.3 Impact on existing entities and interfaces 62 6.20.4 Topics for further study 62 6.20.5 Conclusions 62 6.21 Solution #21: Group communication enhancement for NR PC5 63 6.21.1 Functional Description 63 6.21.1.1 General description 63 6.21.1.2 Solution description 63 6.21.2 Procedures 63 6.21.3 Impact on existing entities and interfaces 65 6.21.4 Topics for further study 65 6.21.5 Conclusions 65 6.22 Solution #22: Authorization for NR based PC5 communication when the UE is served by EPS 65 6.22.1 Functional Description 65 6.22.1.1 General Description 65 6.22.2 Procedures 66 6.22.2.1 UE indicates its NR PC5 capability to the EPS network 66 6.22.2.2 Authorization for sending V2X message over PC5 using NR RAT 66 6.22.2.3 Provisioning of V2X configuration for NR based PC5 communication. 66 6.22.3 Impact on existing entities and interfaces 66 6.22.4 Topics for further study 66 6.22.5 Conclusions 66 6.23 Solution #23: Early notification for Dynamic Application Adjustment 67 6.23.1 Functional Description 67 6.23.2 Procedures 68 6.23.3 Impact on existing entities 69 6.23.4 Evaluation 70 6.23.5 Conclusions 70 6.24 Solution #24: Solution for AF-initiated UE provisioning 70 6.24.1 Functional Description 70 6.24.1.1 General Description 70 6.24.1.2 AF-initiated Service Parameter provisioning 70 6.24.1.3 NEF service for Service Parameter provisioning 71 6.24.1.3.1 General 71 6.24.1.3.2 Nnef_ServiceParameter_Create operation 71 6.24.1.3.3 Nnef_ServiceParameter_Update operation 71 6.24.1.3.4 Nnef_ServiceParameter_Delete operation 71 6.24.1.4 V2X service parameter delivery 72 6.24.2 Procedures 72 6.24.3 Impact on existing entities and interfaces 72 6.24.4 Topics for further study 73 6.24.5 Conclusions 73 6.25 Solution #25: Solution for Key Issue #13 73 6.25.1 Functional Description 73 6.25.2 Impacts on existing entities and interfaces 73 6.25.3 Conclusions 74 6.26 Solution #26: Path-based QoS booking for Application Adjustment 74 6.26.1 Functional Description 74 6.26.2 Procedures 76 6.26.2.1 V2X application Requested Booking 76 6.26.2.2 Network Initiated Booking Update 77 6.26.2.3 Details of system interactions for resources booking 78 6.26.2.4 Impact on other procedures 79 6.26.3 Impact on existing entities and interfaces 79 6.26.4 Topics for further study 79 6.26.5 Conclusions 79 7 Conclusions 79 7.1 Conclusions for EPS 80 7.2 Conclusions for 5G System 80 7.3 Interim Conclusions for EPS 81 Annex A: eV2X Architecture variants 82 A.0 Description 82 A.1 Alternative#1: eV2X Architecture Reference Model 82 A.1.1 Description 82 A.1.1.1 Description of existing V2X for EPS 82 A.1.1.2 5G Description 83 A.1.1.3 PC5 and Uu based eV2X architecture reference model 83 A.1.2 Procedures 86 A.1.3 Impact on existing entities and interfaces 86 A.1.4 Topics for further study 86 A.2 Alternative#2: Reusing EPS V2X Architecture 86 A.2.1 Description 86 A.3 Alternative#3: V2X Control Function as a new CP entity in 5GC 89 A.3.1 Description 89 A.3.2 Procedures 90 A.3.3 Impact on existing entities and interfaces 90 A.3.4 Topics for further study 90 A.4 Alternative#4: eV2X Architecture Reference Model 91 A.4.1 Description 91 Annex B: Solutions for broadcast/multicast/group delivery over Uu 93 B.0 Description 93 B.1 Solution #B1: Support of broadcast in 5GS 93 B.1.1 Functional Description 93 B.1.1.0 General 93 B.1.1.1 5G-MBMS Architecture 93 B.1.1.2 Service-based interfaces and Reference points 94 B.1.2 Procedures 94 B.1.2.1 Service Announcement 94 B.1.2.2 TMGI Management 94 B.1.2.3 MBMS Session Management 94 B.1.3 Impact on existing entities and interfaces 95 B.1.4 Topics for further study 95 B.1.5 Conclusions 95 B.2 Solution #B2: Support of broadcast/multicast/group delivery over Uu 95 B.2.1 Introduction 95 B.2.2 Architecture 96 B.2.3 Support of EPC interworking 96 B.2.4 Procedures 96 B.2.4.1 Service announcement 96 B.2.4.2 TMGI Management 96 B.2.4.2.1 General 96 B.2.4.2.2 TMGI Allocation 97 B.2.4.2.3 TMGI Refresh 97 B.2.4.2.4 TMGI deallocation 98 B.2.4.3 Create, Update and Release a Group Session 98 B.2.4.3.1 General 98 B.2.4.3.2 Triggering of the Group Session Establishment 99 B.2.4.3.3 Triggering of Session release 100 B.2.4.3.4 Triggering of Session Modification 101 B.2.5 Impacts on existing entities and interfaces/Functional Entities 101 B.2.5.1 Impacts on existing entities 102 B.2.5.2 Impacts on existing interfaces 102 B.2.6 Evaluation 103 B.3 Solution #B3: Support for eMBMS over EPS MBMS with independent unicast from 5GS 103 B.3.1 Functional Description 103 B.3.1.1 General description 103 B.3.1.2 Solution description 103 B.3.1.2.1 General solution for support of receiving eMBMS traffic for UE connected to 5GS 103 B.3.1.2.2 Applying the general solution to eV2X 104 B.3.2 Procedures 105 B.3.3 Impact on existing entities and interfaces 105 B.3.4 Topics for further study 105 B.3.5 Conclusions 105 B.4 Solution #B4: Support of multicast/groupcast/broadcast services in 5GS 105 B.4.1 Functional Description 105 B.4.1.1 Architecture 105 B.4.1.2 Service-based interfaces and Reference points 107 B.4.2 Procedures 107 B.4.3 Impact on existing entities and interfaces 107 B.4.4 Topics for further study 107 B.4.5 Conclusions 107 Annex C: Change history 108 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 The 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.886[2], based on vehicular services requirements defined in TS22.185[3] and TS22.186[4] and determine which of the solutions can proceed to normative specifications. In Rel-15, the study focuses on EPS. 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] 3GPPTR22.886: "Study on enhancement of 3GPP Support for 5G V2X Services". [3] 3GPPTS22.185: "Service requirements for V2X services; Stage 1". [4] 3GPPTS22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1". [5] 3GPPTS23.285: "Architecture enhancements for V2X services". [6] 3GPPTS22.278: "Service requirements for the Evolved Packet System (EPS)". [7] 3GPPTS23.501: "System Architecture for the 5G System; Stage2". [8] 3GPPTS23.303: "Proximity-based Services (ProSe); Stage 2". [9] 3GPPTS23.502: "Procedures for the 5G System; Stage2". [10] 3GPPTS23.503: "Policy and Charging Control Framework for the 5G System; Stage2". [11] 3GPPTS33.303: "Proximity-based Services (ProSe); Security aspects". [12] 3GPPTS23.203: "Policy and charging control architecture". [13] 3GPPTS24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3". [14] 3GPPTS36.440: "General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN". [15] 3GPPTR23.724: "Study on Cellular IoT support and evolution for the 5G System". [16] 3GPPTS23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". [17] 3GPPTS26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". [18] 3GPPTS25.446: "MBMS synchronisation protocol (SYNC)". [19] 3GPPTS36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". [20] 3GPPTR23.791: "Study of Enablers