Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TR 23.795SA6
Study on
Application Layer support
for V2X Services

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.1.0 (Wzip)  2018/12  77 p.

Rapporteur:  Mr. Amogh, Niranth

The present document is a technical report which identifies the application architecture aspects to support V2X services, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems.

full Table of Contents for  TR 23.795  Word version:   16.1.0

this ToC is filtered in order to show the essential title levels only
Here   Top
1  ScopeWord-p. 9
2  ReferencesWord-p. 9
3  Definitions and abbreviationsWord-p. 11
4  Analysis of V2X standardsWord-p. 12
4.1  3GPP V2X service requirementsWord-p. 12
4.2  3GPP EPS architecture for V2X communicationsWord-p. 15
4.3  ETSI ITS communication architecture and requirementsWord-p. 15
4.4  SAE and related standards communication architecture and requirementsWord-p. 16
5  Key issuesWord-p. 17
5.1  Key issue 1 - Communication of V2X application QoS requirements with 3GPP systemsWord-p. 17
5.2  Key issue 2 - Monitoring network situation of 3GPP systems by V2X applicationWord-p. 18
5.3  Key issue 3 - V2X USD provisioning via V1 reference pointWord-p. 18
5.4  Key issue 4 - Local service informationWord-p. 19
5.5  Key issue 5 - Service continuity during MBMS based V2X trafficWord-p. 19
5.6  Key issue 6 - Handling MBMS bearer suspensionWord-p. 21
5.7  Key Issue 7 - V2X UE capabilities reportingWord-p. 21
5.8  Key issue 8 - PC5 parameters provisioning over V1Word-p. 21
5.9  Key issue 9 - V2X group communicationWord-p. 22
5.10  Key issue 10 - UE location report over V1Word-p. 22
5.11  Key issue 11 - Support for uplink video streamingWord-p. 22
5.12  Key issue 12 - Handling multiple V2X application priorities at the V2X UEWord-p. 23
5.13  Key issue 13 - Communicating application requirements from the V2X application serverWord-p. 23
5.14  Key issue 14 - Network assistance for enhancing QoE in V2X applicationsWord-p. 23
5.15  Key issue 15 - V2X USD provisioning using existing MBMS service announcement mechanismsWord-p. 23
5.16  Key issue 16 - Supporting larger files or V2X messagesWord-p. 24
5.17  Key issue 17 - Determining UE location for a geographical areaWord-p. 24
5.18  Key issue 18 - Resolving UE address for ETSI ITS facility layer messagesWord-p. 24
5.19  Key issue 19 - Resolving security issues for ETSI ITS distributionUpWord-p. 24
5.20  Key issue 20 - V2X dynamic groupsWord-p. 25
5.21  Key issue 21 - V2X application support for network slicingWord-p. 25
5.22  Key issue 22 - Support for operation modes selection for V2V communicationsWord-p. 26
5.23  Key issue 23 - Support for service continuity between Uu and UE-to-network relay for V2X communicationsWord-p. 26
6  Assumptions and architectural requirementsWord-p. 26
6.1  AssumptionsWord-p. 26
6.2  Architectural requirementsWord-p. 26
6.3  Network situation monitoring requirementsWord-p. 27
6.4  3GPP system related parameters provisioningWord-p. 27
6.5  PC5 based V2X group communicationUpWord-p. 27
7  SolutionsWord-p. 28
7.1  Solution #1: V2X application layer functional modelWord-p. 28
7.2  Solution #2: UE location report over V1Word-p. 35
7.3  Solution #3: Handling MBMS bearer suspension via V1Word-p. 37
7.4  Solution #4: V2X USD provisioning via V1 reference pointWord-p. 38
7.5  Solution #5: V2X UE obtaining the local service informationWord-p. 39
7.6  Solution #6: PC5 parameters provisioning via V1 reference pointWord-p. 40
7.7  Solution #7: Network situation and QoS monitoringWord-p. 41
7.8  Solution #8: V2X USD provisioning using SACHWord-p. 43
7.9  Solution #9: Abstraction of network QoS aspects for V2X communicationsWord-p. 44
7.10  Solution #10: Communication of V2X application PC5 QoS requirements with 3GPP systemsWord-p. 46
7.11  Solution #11: Switching from MBMS delivery to unicast deliveryWord-p. 46
7.12  Solution #12: Supporting for V2X group communicationWord-p. 47
7.13  Solution #13: Group communication parameters provisioning via V5Word-p. 49
7.14  Solution #14: Autonomous decision for assigning ProSe Layer-2 Group IDWord-p. 50
7.15  Solution #15: Support for uplink video streaming using FLUS frameworkWord-p. 52
7.16  Solution #16: Communicating application requirements from the V2X application serverWord-p. 53
7.17  Solution #17: Network assistance for enhancing QoE in V2X applications using SAND frameworkWord-p. 54
7.18  Solution #18: Support for QoE reportingWord-p. 55
7.19  Solution #19: Support for larger files using MBMS non-Transparent xMB Session TypesWord-p. 56
7.20  Solution #20: Support for file transferWord-p. 57
7.21  Solution #21: Resolving UE address for ETSI ITS facility layer messagesWord-p. 59
7.22  Solution #22: Resolving security issues for ETSI ITS distributionWord-p. 61
7.23  Solution #23: Supporting V2X dynamic group communication over UuWord-p. 63
7.24  Solution #24: Supporting V2X dynamic group communication over PC5Word-p. 65
7.25  Solution #25: Dynamic group managementWord-p. 66
7.26  Solution #26: Abstraction and control of network slice instance for V2X communicationsWord-p. 69
7.27  Solution #27: Switching the mode of operation for V2V communications controlled by networkUpWord-p. 71
8  Overall evaluationWord-p. 74
9  ConclusionsWord-p. 76
A  Change historyWord-p. 77

Up   Top