Tech-invite  3GPPspecsRELsGlossariesSIP
21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TR 23.785SA2
Study on Architecture enhancements
for LTE support of V2X Services

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V14.0.0 (Wzip)  2016/09  52 p.

WI Acronym:  FS_V2XARC
Rapporteur:  Dr. Kim, Laeyoung

The objective of this Technical Report is to identify and evaluate potential architecture enhancements needed to operate LTE-based V2X (V2V, V2I, V2N, and V2P), based on vehicular services requirements defined in SA WG1 V2XLTE (TS 22.185 and TS 22.278) and determine which of the solutions can proceed to normative specifications.

full Table of Contents for  TR 23.785  Word version:   14.0.0

this ToC is filtered in order to show the essential title levels only
Here   Top
1  ScopeWord-p. 7
2  ReferencesWord-p. 7
3  Definitions and abbreviationsWord-p. 8
4  Architectural Assumptions and RequirementsWord-p. 8
4.1  Architectural AssumptionsWord-p. 8
4.1.1  PC5 and LTE-Uu based V2X architecture reference modelWord-p. 9
4.1.2  eMBMS and LTE-Uu based V2X architecture reference modelWord-p. 10
4.2  Architectural RequirementsWord-p. 11
5  Key IssuesUpWord-p. 11
5.1  Key Issue #1: Service authorization for V2XWord-p. 11
5.2  Key Issue #2: V2X message transmission/reception for V2V Service and V2P ServiceWord-p. 11
5.3  Key Issue #3: Policy/Parameter provisioning for V2V Service, V2P Service and V2I ServiceWord-p. 11
5.4  Key Issue #4: V2X message prioritization for V2V Service and V2P ServiceWord-p. 12
5.5  Key Issue #5: V2X message transmission/reception between a vehicle and an RSU for V2IWord-p. 12
5.6  Key Issue #6: V2X message transmission/reception with eMBMS architecture for V2XWord-p. 13
5.7  Key Issue #7: QoS for V2X ServiceWord-p. 15
5.8  Key Issue #8: Inter-PLMN operation for V2XWord-p. 15
5.9  Key Issue #9: Privacy for V2X communicationsWord-p. 15
6  SolutionsWord-p. 16
6.1  Solution #1: V2X authorizationWord-p. 16
6.2  Solution #2: V2X message transmission/reception for V2V/P Services using PC5Word-p. 18
6.3  Solution #3: V2X message transmission/reception for V2V/P Services via LTE-UuWord-p. 20
6.4  Solution #4: V2X broadcast with Local MBMS Entity (LME)Word-p. 23
6.5  Solution #5: RSU based on V2V/V2P Message Offload function in eNB or on S1Word-p. 27
6.6  Solution #6: QoS handling for PC5 based messageWord-p. 30
6.7  Solution #7: New QCI values for LTE-Uu based V2X message transmission/receptionWord-p. 32
6.8  Solution #8: V2X message transmission/reception for V2I ServiceUpWord-p. 33
6.9  Solution #9: MBMS service area mapping using MB2-C proceduresWord-p. 35
6.10  Solution #10: BM-SC based solution for MBMS service area mappingWord-p. 36
6.11  Solution #11: Local V2X server discovery using AnycastWord-p. 37
6.12  Solution #12: V2X Server Discovery using broadcast mechanismWord-p. 38
6.13  Solution #13: Privacy protection of UE in V2X communicationsWord-p. 41
6.14  Solution #14: Path selection for Uplink V2V message transmissionWord-p. 43
6.15  Solution #15: Latency improvements for eMBMS with L.MBMS based on implementationUpWord-p. 43
7  ConclusionsWord-p. 45
A  Enhancements to ProSe architectures for PC5 based V2XWord-p. 46
B  Road Side Unit (RSU) considerationsWord-p. 47
C  Example hybrid deployment options using LTE-Uu based architecture and PC5 based architectureWord-p. 49
C.1  PC5 based V2X communication with eMBMS receptionWord-p. 49
C.2  Simultaneous LTE-Uu based and PC5 based V2X communication without eMBMSWord-p. 49
D  Localized MBMS deployment optionsWord-p. 50
D.1  General DescriptionWord-p. 50
D.2  Option of localized MBMS CN functionsWord-p. 50
D.3  Option of localized user plane of MBMS CN functionsWord-p. 51
E  Change historyWord-p. 52

Up   Top