Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 23.785  Word version:  14.0.0

Top   Top   Up   Prev   None
1…   4…

 

4  Architectural Assumptions and Requirements

5  Key Issues

6  SolutionsWord‑p. 16

6.1  Solution #1: V2X authorization

6.2  Solution #2: V2X message transmission/reception for V2V/P Services using PC5

6.3  Solution #3: V2X message transmission/reception for V2V/P Services via LTE-Uu

6.4  Solution #4: V2X broadcast with Local MBMS Entity (LME)

6.5  Solution #5: RSU based on V2V/V2P Message Offload function in eNB or on S1

6.6  Solution #6: QoS handling for PC5 based message

6.7  Solution #7: New QCI values for LTE-Uu based V2X message transmission/reception

6.8  Solution #8: V2X message transmission/reception for V2I Service

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 Anycast

6.12  Solution #12: V2X Server Discovery using broadcast mechanism

6.13  Solution #13: Privacy protection of UE in V2X communications

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 implementation

7  Conclusions

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

D  Localized MBMS deployment optionsWord‑p. 50

$  Change HistoryWord‑p. 52


Up   Top