Content for TR 23.795 Word version: 16.1.0
4 Analysis of V2X standards
5 Key issues
6 Assumptions and architectural requirements
7 Solutions
8 Overall evaluation
9 Conclusions
$ Change History
4 Analysis of V2X standards p. 12
4.1 3GPP V2X service requirements p. 12
4.1.1 Description p. 12
4.1.2 Analysis p. 13
4.2 3GPP EPS architecture for V2X communications p. 15
4.2.1 Description p. 15
4.2.2 Analysis p. 15
4.3 ETSI ITS communication architecture and requirements p. 15
4.3.1 Description p. 15
4.3.2 Analysis p. 16
4.4 SAE and related standards communication architecture and requirements p. 16
4.4.1 Description p. 16
4.4.2 Analysis p. 16
5 Key issues p. 17
5.1 Key issue 1 - Communication of V2X application QoS requirements with 3GPP systems p. 17
5.1.1 General p. 17
5.1.2 Key issue 1a - Communication of V2X application network QoS requirements with 3GPP systems p. 17
5.1.3 Key issue 1b - Communication of V2X application PC5 QoS requirements with 3GPP systems p. 18
5.2 Key issue 2 - Monitoring network situation of 3GPP systems by V2X application p. 18
5.3 Key issue 3 - V2X USD provisioning via V1 reference point p. 18
5.4 Key issue 4 - Local service information p. 19
5.5 Key issue 5 - Service continuity during MBMS based V2X traffic p. 19
5.6 Key issue 6 - Handling MBMS bearer suspension p. 21
5.7 Key Issue 7 - V2X UE capabilities reporting p. 21
5.8 Key issue 8 - PC5 parameters provisioning over V1 p. 21
5.9 Key issue 9 - V2X group communication p. 22
5.10 Key issue 10 - UE location report over V1 p. 22
5.11 Key issue 11 - Support for uplink video streaming p. 22
5.12 Key issue 12 - Handling multiple V2X application priorities at the V2X UE p. 23
5.13 Key issue 13 - Communicating application requirements from the V2X application server p. 23
5.14 Key issue 14 - Network assistance for enhancing QoE in V2X applications p. 23
5.15 Key issue 15 - V2X USD provisioning using existing MBMS service announcement mechanisms p. 23
5.16 Key issue 16 - Supporting larger files or V2X messages p. 24
5.17 Key issue 17 - Determining UE location for a geographical area p. 24
5.18 Key issue 18 - Resolving UE address for ETSI ITS facility layer messages p. 24
5.19 Key issue 19 - Resolving security issues for ETSI ITS distribution p. 24
5.20 Key issue 20 - V2X dynamic groups p. 25
5.21 Key issue 21 - V2X application support for network slicing p. 25
5.22 Key issue 22 - Support for operation modes selection for V2V communications p. 26
5.23 Key issue 23 - Support for service continuity between Uu and UE-to-network relay for V2X communications p. 26
6 Assumptions and architectural requirements p. 26
6.1 Assumptions p. 26
6.2 Architectural requirements p. 26
6.2.1 General p. 26
6.2.1.1 Description p. 26
6.2.1.2 Requirements p. 26
6.2.2 Location p. 26
6.2.2.1 Description p. 26
6.2.2.2 Requirements p. 27
6.3 Network situation monitoring requirements p. 27
6.3.1 Description p. 27
6.3.2 Requirements p. 27
6.4 3GPP system related parameters provisioning p. 27
6.4.1 Description p. 27
6.4.2 Requirements p. 27
6.5 PC5 based V2X group communication p. 27
6.5.1 Description p. 27
6.5.2 Requirements p. 27
7 Solutions p. 28
7.1 Solution #1: V2X application layer functional model p. 28
7.1.1 Solution description p. 28
7.1.1.1 General p. 28
7.1.1.2 V2X application layer functional model p. 28
7.1.1.3 Functional entities description p. 29
7.1.1.3.1 General p. 29
7.1.1.3.2 V2X application specific client p. 29
7.1.1.3.3 V2X application enabler client p. 29
7.1.1.3.4 V2X application specific server p. 30
7.1.1.3.5 V2X application enabler server p. 30
7.1.1.4 Reference points p. 30
7.1.1.4.1 General p. 30
7.1.1.4.2 V1-AE p. 30
7.1.1.4.3 V1-APP p. 30
7.1.1.4.4 V5-AE p. 30
7.1.1.4.5 V5-APP p. 31
7.1.1.4.6 Vs p. 31
7.1.1.4.7 Vc p. 31
7.1.1.5 Reference points between the V2X application layer and the 3GPP network systems p. 31
7.1.1.5.1 General p. 31
7.1.1.5.2 V2 p. 31
7.1.1.5.3 Rx p. 31
7.1.1.5.4 MB2 p. 31
7.1.1.5.5 xMB p. 31
7.1.1.5.6 T8 p. 31
7.1.1.6 Deployment models for the V2X application layer functional model p. 31
7.1.2 Solution evaluation p. 34
7.2 Solution #2: UE location report over V1 p. 35
7.2.1 Solution description p. 35
7.2.1.1 General p. 35
7.2.1.2 Location reporting event triggers configuration procedure p. 35
7.2.1.3 Location reporting event triggers configuration cancel procedure p. 35
7.2.1.4 Location reporting procedure p. 36
7.2.2 Solution evaluation p. 36
7.3 Solution #3: Handling MBMS bearer suspension via V1 p. 37
7.3.1 Solution description p. 37
7.3.1.1 General p. 37
7.3.1.2 Procedure p. 37
7.3.2 Solution evaluation p. 37
7.4 Solution #4: V2X USD provisioning via V1 reference point p. 38
7.4.1 Solution description p. 38
7.4.1.1 General p. 38
7.4.1.2 Procedure p. 38
7.4.2 Solution evaluation p. 38
7.5 Solution #5: V2X UE obtaining the local service information p. 39
7.5.1 Solution description p. 39
7.5.1.1 General p. 39
7.5.1.2 Procedure p. 39
7.5.2 Solution evaluation p. 40
7.6 Solution #6: PC5 parameters provisioning via V1 reference point p. 40
7.6.1 Solution description p. 40
7.6.1.1 General p. 40
7.6.1.2 Procedure p. 40
7.6.2 Solution evaluation p. 41
7.7 Solution #7: Network situation and QoS monitoring p. 41
7.7.1 Solution description p. 41
7.7.1.1 General p. 41
7.7.1.2 Network situation and QoS monitoring events p. 41
7.7.1.3 Procedure for network situation and QoS monitoring p. 42
7.7.1.4 Procedure for network situation and QoS monitor reporting p. 43
7.7.2 Solution evaluation p. 43
7.8 Solution #8: V2X USD provisioning using SACH p. 43
7.8.1 Solution description p. 43
7.8.1.1 General p. 43
7.8.1.2 Procedure p. 43
7.8.2 Solution evaluation p. 44
7.9 Solution #9: Abstraction of network QoS aspects for V2X communications p. 44
7.9.1 Solution description p. 44
7.9.1.1 General p. 44
7.9.1.2 Procedure p. 44
7.9.2 Solution evaluation p. 46
7.10 Solution #10: Communication of V2X application PC5 QoS requirements with 3GPP systems p. 46
7.11 Solution #11: Switching from MBMS delivery to unicast delivery p. 46
7.12 Solution #12: Supporting for V2X group communication p. 47
7.12.1 Solution description p. 47
7.12.1.1 General p. 47
7.12.1.2 VAE server pushes ProSe group communication parameters procedure p. 48
7.12.2 Solution evaluation p. 48
7.13 Solution #13: Group communication parameters provisioning via V5 p. 49
7.13.1 Solution description p. 49
7.13.1.1 General p. 49
7.13.1.2 Procedure p. 49
7.13.2 Solution evaluation p. 50
7.14 Solution #14: Autonomous decision for assigning ProSe Layer-2 Group ID p. 50
7.14.1 Solution description p. 50
7.14.1.1 General p. 50
7.14.1.2 Procedure p. 51
7.14.2 Solution evaluation p. 52
7.15 Solution #15: Support for uplink video streaming using FLUS framework p. 52
7.15.1 Solution description p. 52
7.15.1.1 General p. 52
7.15.1.2 Procedure p. 52
7.15.2 Solution evaluation p. 52
7.16 Solution #16: Communicating application requirements from the V2X application server p. 53
7.16.1 Solution description p. 53
7.16.1.1 General p. 53
7.16.1.2 Procedure for subscription to the 3GPP network system p. 53
7.16.1.3 Procedure for communication of application requirements p. 53
7.16.1.4 Procedure for notification generation p. 54
7.16.2 Solution evaluation p. 54
7.17 Solution #17: Network assistance for enhancing QoE in V2X applications using SAND framework p. 54
7.17.1 Solution description p. 54
7.17.1.1 General p. 54
7.17.1.2 Procedure p. 54
7.17.2 Solution evaluation p. 55
7.18 Solution #18: Support for QoE reporting p. 55
7.18.1 Solution description p. 55
7.18.1.1 General p. 55
7.18.1.2 Procedure p. 55
7.18.2 Solution evaluation p. 56
7.19 Solution #19: Support for larger files using MBMS non-Transparent xMB Session Types p. 56
7.19.1 Solution description p. 56
7.19.1.1 General p. 56
7.19.1.2 Procedure p. 56
7.19.2 Solution evaluation p. 57
7.20 Solution #20: Support for file transfer p. 57
7.20.1 Solution description p. 57
7.20.1.1 General p. 57
7.20.1.2 Procedure for file upload using HTTP p. 57
7.20.1.3 Procedure for file download using HTTP p. 58
7.20.2 Solution evaluation p. 59
7.21 Solution #21: Resolving UE address for ETSI ITS facility layer messages p. 59
7.21.1 Solution description p. 59
7.21.1.1 General p. 59
7.21.1.2 Procedure for tracking geographical location at the VAE server p. 59
7.21.1.3 Procedure for message delivery to target geographical locations from the VAE server p. 60
7.21.2 Solution evaluation p. 61
7.22 Solution #22: Resolving security issues for ETSI ITS distribution p. 61
7.22.1 Solution description p. 61
7.22.1.1 General p. 61
7.22.1.2 Procedure for V2X UE to V2X application server communication scenario p. 61
7.22.1.3 Procedure for V2X application server to V2X UE communication scenario p. 62
7.22.2 Solution evaluation p. 62
7.23 Solution #23: Supporting V2X dynamic group communication over Uu p. 63
7.23.1 Solution description p. 63
7.23.1.1 General p. 63
7.23.1.2 VAE server configuring dynamic group parameters procedure p. 63
7.23.1.3 Enabling V2X UEs to join V2X dynamic group procedure p. 64
7.23.1.4 Switching from Uu to PC5 V2X communications controlled by UE procedure p. 64
7.23.2 Solution evaluation p. 65
7.24 Solution #24: Supporting V2X dynamic group communication over PC5 p. 65
7.25 Solution #25: Dynamic group management p. 66
7.25.1 Solution description p. 66
7.25.1.1 Group creation p. 67
7.25.1.2 Group join controlled by the VAE server p. 67
7.25.1.3 Group join over PC5 controlled by the authorized VAE client p. 68
7.25.2 Solution evaluation p. 69
7.26 Solution #26: Abstraction and control of network slice instance for V2X communications p. 69
7.26.1 Solution description p. 69
7.26.1.1 General p. 69
7.26.1.2 Procedure p. 70
7.26.2 Solution evaluation p. 71
7.27 Solution #27: Switching the mode of operation for V2V communications controlled by network p. 71
8 Overall evaluation p. 74
9 Conclusions p. 76
$ Change History p. 77
