《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页珍藏版）》请在金锄头文库上搜索。
1、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 Gene
2、ration 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 Org
3、anizational 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,
4、 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 th
5、e 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 a
6、nd 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.1Definitions1
7、13.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.2Ke
8、y 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
9、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 description
10、155.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
11、 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: Suppor
12、t 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
13、 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
14、 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
15、 #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 Communi
