Content for TR 23.785 Word version: 14.0.0
4 Architectural Assumptions and Requirements
5 Key Issues
6 Solutions
7 Conclusions
A Enhancements to ProSe architectures for PC5 based V2X
B Road Side Unit (RSU) considerations
C Example hybrid deployment options using LTE-Uu based architecture and PC5 based architecture
D Localized MBMS deployment options
$ Change History
4 Architectural Assumptions and Requirements
4.1 Architectural Assumptions
4.1.1 PC5 and LTE-Uu based V2X architecture reference model Word‑p. 9
4.1.2 eMBMS and LTE-Uu based V2X architecture reference model Word‑p. 10
4.2 Architectural Requirements Word‑p. 11
5 Key Issues
5.1 Key Issue #1: Service authorization for V2X
5.2 Key Issue #2: V2X message transmission/reception for V2V Service and V2P Service
5.3 Key Issue #3: Policy/Parameter provisioning for V2V Service, V2P Service and V2I Service
5.4 Key Issue #4: V2X message prioritization for V2V Service and V2P Service Word‑p. 12
5.5 Key Issue #5: V2X message transmission/reception between a vehicle and an RSU for V2I
5.6 Key Issue #6: V2X message transmission/reception with eMBMS architecture for V2X Word‑p. 13
5.6.1 General description
5.6.2 Issue #6a: MBMS service area mapping
5.6.3 Issue #6b: Latency improvements for eMBMS for V2X Service
5.6.4 Issue #6c: Local V2X server discovery
5.6.5 Issue #6d: Distribution of V2X messages to V2X servers Word‑p. 15
5.7 Key Issue #7: QoS for V2X Service
5.8 Key Issue #8: Inter-PLMN operation for V2X
5.9 Key Issue #9: Privacy for V2X communications
6 Solutions Word‑p. 16
6.1 Solution #1: V2X authorization
6.1.1 Functional Description
6.1.2 Procedures
6.1.2.1 Service authorization procedures
6.1.2.2 Policy/Parameter provisioning Word‑p. 17
6.1.2.3 Service authorization update procedures Word‑p. 18
6.1.3 Impact on existing entities and interfaces
6.1.4 Topics for further study
6.1.5 Conclusions
6.2 Solution #2: V2X message transmission/reception for V2V/P Services using PC5
6.2.1 Functional Description
6.2.2 Procedures
6.2.3 Impact on existing entities and interfaces Word‑p. 20
6.2.4 Topics for further study
6.2.5 Conclusions
6.3 Solution #3: V2X message transmission/reception for V2V/P Services via LTE-Uu
6.3.1 Functional Description
6.3.2 Procedures Word‑p. 22
6.3.3 Impact on existing entities and interfaces
6.3.4 Topics for further study
6.3.5 Conclusions Word‑p. 23
6.4 Solution #4: V2X broadcast with Local MBMS Entity (LME)
6.4.1 Functional Description
6.4.2 Procedures Word‑p. 24
6.4.2.1 V2X Server Initiated Procedure (option 1)
6.4.2.2 Void
6.4.2.3 Void
6.4.2.4 BM-SC Initiated Procedure (option 4) Word‑p. 25
6.4.3 Impact on existing entities and interfaces Word‑p. 26
6.4.4 Topics for further study Word‑p. 27
6.4.5 Conclusions
6.5 Solution #5: RSU based on V2V/V2P Message Offload function in eNB or on S1
6.5.1 Functional Description
6.5.2 Procedures Word‑p. 29
6.5.3 Impact on existing entities and interfaces Word‑p. 30
6.5.4 Topics for further study
6.5.5 Conclusions
6.6 Solution #6: QoS handling for PC5 based message
6.6.1 Functional Description
6.6.2 Procedure Word‑p. 31
6.6.3 Impact on existing entities and interfaces Word‑p. 32
6.6.4 Topics for further study
6.6.5 Conclusions
6.7 Solution #7: New QCI values for LTE-Uu based V2X message transmission/reception
6.7.1 Functional Description
6.7.2 Procedures Word‑p. 33
6.7.3 Impact on existing entities and interfaces
6.7.4 Topics for further study
6.7.5 Conclusions
6.8 Solution #8: V2X message transmission/reception for V2I Service
6.8.1 Functional Description
6.8.2 Procedures Word‑p. 34
6.8.3 Impact on existing entities and interfaces
6.8.4 Topics for further study
6.8.5 Conclusions
6.9 Solution #9: MBMS service area mapping using MB2-C procedures Word‑p. 35
6.9.0 General
6.9.1 Functional Description
6.9.2 Procedure
6.9.3 Impact on existing entities and interfaces
6.9.4 Topics for further study
6.9.5 Conclusions
6.10 Solution #10: BM-SC based solution for MBMS service area mapping Word‑p. 36
6.10.1 Functional Description
6.10.2 Procedures
6.10.3 Impact on existing entities and interfaces Word‑p. 37
6.10.4 Topics for further study
6.10.5 Conclusions
6.11 Solution #11: Local V2X server discovery using Anycast
6.11.1 Functional Description
6.11.2 Procedures Word‑p. 38
6.11.3 Impact on existing entities and interfaces
6.11.4 Topics for further study
6.11.5 Conclusions
6.12 Solution #12: V2X Server Discovery using broadcast mechanism
6.12.0 General
6.12.1 Functional Description Word‑p. 39
6.12.2 Procedures Word‑p. 40
6.12.3 Impact on existing entities and interfaces
6.12.4 Configuration example
6.12.5 Conclusions Word‑p. 41
6.13 Solution #13: Privacy protection of UE in V2X communications
6.13.1 Functional Description
6.13.2 Procedures
6.13.2.1 UE identity concealment from mobile operators
6.13.2.2 Avoid long term tracking of UE Word‑p. 42
6.13.3 Impact on existing entities and interfaces
6.13.4 Topics for further study
6.13.5 Conclusions
6.14 Solution #14: Path selection for Uplink V2V message transmission Word‑p. 43
6.14.1 Functional Description
6.14.2 Procedures
6.14.3 Impact on existing entities and interfaces
6.14.4 Topics for further study
6.14.5 Conclusions
6.15 Solution #15: Latency improvements for eMBMS with L.MBMS based on implementation
7 Conclusions
A Enhancements to ProSe architectures for PC5 based V2X Word‑p. 46
B Road Side Unit (RSU) considerations Word‑p. 47
C Example hybrid deployment options using LTE-Uu based architecture and PC5 based architecture Word‑p. 49
C.1 PC5 based V2X communication with eMBMS reception
C.2 Simultaneous LTE-Uu based and PC5 based V2X communication without eMBMS
D Localized MBMS deployment options Word‑p. 50
D.1 General Description
D.2 Option of localized MBMS CN functions
D.3 Option of localized user plane of MBMS CN functions Word‑p. 51
$ Change History Word‑p. 52
