《23795-200_cl Study on application layer support for V2X services;》由會員分享,可在線閱讀,更多相關《23795-200_cl Study on application layer support for V2X services;(77頁珍藏版)》請在裝配圖網上搜索。
3GPP TR 23.795 V2.0.0 (2018-09)
Technical Report
3rd Generation Partnership Project;
Technical Specification Group Services and System Aspects;
Study on application layer support for V2X services;
(Release 16)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Report is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.
Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices.
3GPP TR 23.795 V2.0.0 (2018-09)
77
Release 16
Keywords
3GPP
Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
2018, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS? is a Trade Mark of ETSI registered for the benefit of its members
3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM and the GSM logo are registered and owned by the GSM Association
Contents
Foreword 8
1 Scope 9
2 References 9
3 Definitions and abbreviations 11
3.1 Definitions 11
3.2 Abbreviations 11
4 Analysis of V2X standards 12
4.1 3GPP V2X service requirements 12
4.1.1 Description 12
4.1.2 Analysis 13
4.2 3GPP EPS architecture for V2X communications 15
4.2.1 Description 15
4.2.2 Analysis 15
4.3 ETSI ITS communication architecture and requirements 15
4.3.1 Description 15
4.3.2 Analysis 16
4.4 SAE and related standards communication architecture and requirements 16
4.4.1 Description 16
4.4.2 Analysis 16
5 Key issues 17
5.1 Key issue 1 - Communication of V2X application QoS requirements with 3GPP systems 17
5.1.1 General 17
5.1.2 Key issue 1a - Communication of V2X application network QoS requirements with 3GPP systems 17
5.1.3 Key issue 1b - Communication of V2X application PC5 QoS requirements with 3GPP systems 18
5.2 Key issue 2 - Monitoring network situation of 3GPP systems by V2X application 18
5.3 Key issue 3 - V2X USD provisioning via V1 reference point 18
5.4 Key issue 4 - Local service information 19
5.5 Key issue 5 - Service continuity during MBMS based V2X traffic 20
5.6 Key issue 6 - Handling MBMS bearer suspension 21
5.7 Key Issue 7 - V2X UE capabilities reporting 21
5.8 Key issue 8 - PC5 parameters provisioning over V1 22
5.9 Key issue 9 – V2X group communication 22
5.10 Key issue 10 – UE location report over V1 22
5.11 Key issue 11 - Support for uplink video streaming 23
5.12 Key issue 12 - Handling multiple V2X application priorities at the V2X UE 23
5.13 Key issue 13 - Communicating application requirements from the V2X application server 23
5.14 Key issue 14 - Network assistance for enhancing QoE in V2X applications 24
5.15 Key issue 15 - V2X USD provisioning using existing MBMS service announcement mechanisms 24
5.16 Key issue 16 - Supporting larger files or V2X messages 24
5.17 Key issue 17 - Determining UE location for a geographical area 25
5.18 Key issue 18 - Resolving UE address for ETSI ITS facility layer messages 25
5.19 Key issue 19 - Resolving security issues for ETSI ITS distribution 25
5.20 Key issue 20 – V2X dynamic groups 25
5.21 Key issue 21 – V2X application support for network slicing 26
5.22 Key issue 22 – Support for operation modes selection for V2V communications 26
5.23 Key issue 23 – Support for service continuity between Uu and UE-to-network relay for V2X communications 26
6 Assumptions and architectural requirements 27
6.1 Assumptions 27
6.2 Architectural requirements 27
6.2.1 General 27
6.2.1.1 Description 27
6.2.1.2 Requirements 27
6.2.2 Location 27
6.2.2.1 Description 27
6.2.2.2 Requirements 27
6.3 Network situation monitoring requirements 27
6.3.1 Description 27
6.3.2 Requirements 27
6.4 3GPP system related parameters provisioning 28
6.4.1 Description 28
6.4.2 Requirements 28
6.5 PC5 based V2X group communication 28
6.5.1 Description 28
6.5.2 Requirements 28
7 Solutions 28
7.1 Solution #1: V2X application layer functional model 28
7.1.1 Solution description 28
7.1.1.1 General 28
7.1.1.2 V2X application layer functional model 28
7.1.1.3 Functional entities description 29
7.1.1.3.1 General 29
7.1.1.3.2 V2X application specific client 30
7.1.1.3.3 V2X application enabler client 30
7.1.1.3.4 V2X application specific server 30
7.1.1.3.5 V2X application enabler server 30
7.1.1.4 Reference points 31
7.1.1.4.1 General 31
7.1.1.4.2 V1-AE 31
7.1.1.4.3 V1-APP 31
7.1.1.4.4 V5-AE 31
7.1.1.4.5 V5-APP 31
7.1.1.4.6 Vs 31
7.1.1.4.7 Vc 31
7.1.1.5 Reference points between the V2X application layer and the 3GPP network systems 31
7.1.1.5.1 General 31
7.1.1.5.2 V2 31
7.1.1.5.3 Rx 31
7.1.1.5.4 MB2 32
7.1.1.5.5 xMB 32
7.1.1.5.6 T8 32
7.1.1.6 Deployment models for the V2X application layer functional model 32
7.1.1.6.1 General 32
7.1.1.6.2 Centralized deployment 32
7.1.1.6.3 Distributed deployment 33
7.1.2 Solution evaluation 35
7.2 Solution #2: UE location report over V1 35
7.2.1 Solution description 35
7.2.1.1 General 35
7.2.1.2 Location reporting event triggers configuration procedure 35
7.2.1.3 Location reporting event triggers configuration cancel procedure 36
7.2.1.4 Location reporting procedure 36
7.2.2 Solution evaluation 37
7.3 Solution #3: Handling MBMS bearer suspension via V1 37
7.3.1 Solution description 37
7.3.1.1 General 37
7.3.1.2 Procedure 37
7.3.2 Solution evaluation 38
7.4 Solution #4: V2X USD provisioning via V1 reference point 38
7.4.1 Solution description 38
7.4.1.1 General 38
7.4.1.2 Procedure 38
7.4.2 Solution evaluation 39
7.5 Solution #5: V2X UE obtaining the local service information 39
7.5.1 Solution description 39
7.5.1.1 General 39
7.5.1.2 Procedure 39
7.5.2 Solution evaluation 40
7.6 Solution #6: PC5 parameters provisioning via V1 reference point 41
7.6.1 Solution description 41
7.6.1.1 General 41
7.6.1.2 Procedure 41
7.6.2 Solution evaluation 41
7.7 Solution #7: Network situation and QoS monitoring 42
7.7.1 Solution description 42
7.7.1.1 General 42
7.7.1.2 Network situation and QoS monitoring events 42
7.7.1.3 Procedure for network situation and QoS monitoring 42
7.7.1.4 Procedure for network situation and QoS monitor reporting 43
7.7.2 Solution evaluation 43
7.8 Solution #8: V2X USD provisioning using SACH 44
7.8.1 Solution description 44
7.8.1.1 General 44
7.8.1.2 Procedure 44
7.8.2 Solution evaluation 44
7.9 Solution #9: Abstraction of network QoS aspects for V2X communications 45
7.9.1 Solution description 45
7.9.1.1 General 45
7.9.1.2 Procedure 45
7.9.2 Solution evaluation 46
7.10 Solution #10: Communication of V2X application PC5 QoS requirements with 3GPP systems 46
7.10.1 Solution description 46
7.10.1.1 General 46
7.10.1.2 ProSe Per-Packet Priority values 46
7.10.1.3 Procedure 46
7.10.2 Solution evaluation 46
7.11 Solution #11: Switching from MBMS delivery to unicast delivery 47
7.11.1 Solution description 47
7.11.2 Solution evaluation 48
7.12 Solution #12: Supporting for V2X group communication 48
7.12.1 Solution description 48
7.12.1.1 General 48
7.12.1.2 VAE server pushes ProSe group communication parameters procedure 48
7.12.2 Solution evaluation 49
7.13 Solution #13: Group communication parameters provisioning via V5 49
7.13.1 Solution description 49
7.13.1.1 General 49
7.13.1.2 Procedure 50
7.13.2 Solution evaluation 51
7.14 Solution #14: Autonomous decision for assigning ProSe Layer-2 Group ID 51
7.14.1 Solution description 51
7.14.1.1 General 51
7.14.1.2 Procedure 51
7.14.2 Solution evaluation 52
7.15 Solution #15: Support for uplink video streaming using FLUS framework 52
7.15.1 Solution description 52
7.15.1.1 General 52
7.15.1.2 Procedure 52
7.15.2 Solution evaluation 53
7.16 Solution #16: Communicating application requirements from the V2X application server 53
7.16.1 Solution description 53
7.16.1.1 General 53
7.16.1.2 Procedure for subscription to the 3GPP network system 53
7.16.1.3 Procedure for communication of application requirements 54
7.16.1.4 Procedure for notification generation 54
7.16.2 Solution evaluation 54
7.17 Solution #17: Network assistance for enhancing QoE in V2X applications using SAND framework 55
7.17.1 Solution description 55
7.17.1.1 General 55
7.17.1.2 Procedure 55
7.17.2 Solution evaluation 55
7.18 Solution #18: Support for QoE reporting 56
7.18.1 Solution description 56
7.18.1.1 General 56
7.18.1.2 Procedure 56
7.18.2 Solution evaluation 56
7.19 Solution #19: Support for larger files using MBMS non-Transparent xMB Session Types 56
7.19.1 Solution description 56
7.19.1.1 General 56
7.19.1.2 Procedure 57
7.19.2 Solution evaluation 57
7.20 Solution #20: Support for file transfer 57
7.20.1 Solution description 57
7.20.1.1 General 57
7.20.1.2 Procedure for file upload using HTTP 57
7.20.1.3 Procedure for file download using HTTP 58
7.20.2 Solution evaluation 59
7.21 Solution #21: Resolving UE address for ETSI ITS facility layer messages 59
7.21.1 Solution description 59
7.21.1.1 General 59
7.21.1.2 Procedure for tracking geographical location at the VAE server 59
7.21.1.3 Procedure for message delivery to target geographical locations from the VAE server 60
7.21.2 Solution evaluation 61
7.22 Solution #22: Resolving security issues for ETSI ITS distribution 61
7.22.1 Solution description 61
7.22.1.1 General 61
7.22.1.2 Procedure for V2X UE to V2X application server communication scenario 61
7.22.1.3 Procedure for V2X application server to V2X UE communication scenario 62
7.22.2 Solution evaluation 62
7.23 Solution #23: Supporting V2X dynamic group communication over Uu 63
7.23.1 Solution description 63
7.23.1.1 General 63
7.23.1.2 VAE server configuring dynamic group parameters procedure 63
7.23.1.3 Enabling V2X UEs to join V2X dynamic group procedure 64
7.23.1.4 Switching from Uu to PC5 V2X communications controlled by UE procedure 64
7.23.2 Solution evaluation 65
7.24 Solution #24: Supporting V2X dynamic group communication over PC5 65
7.24.1 Solution description 65
7.24.1.1 General 65
7.24.1.2 Enabling dynamic group formation procedure 65
7.24.2 Solution evaluation 66
7.25 Solution #25: Dynamic group management 66
7.25.1 Solution description 66
7.25.1.1 Group creation 67
7.25.1.2 Group join controlled by the VAE server 67
7.25.1.3 Group join over PC5 controlled by the authorized VAE client 68
7.25.2 Solution evaluation 69
7.26 Solution #26: Abstraction and control of network slice instance for V2X communications 69
7.26.1 Solution description 69
7.26.1.1 General 69
7.26.1.2 Procedure 70
7.26.2 Solution evaluation 71
7.27 Solution #27: Switching the mode of operation for V2V communications controlled by network 71
7.27.1 Solution description 71
7.27.1.1 General 71
7.27.1.2 Switching from Direct (PC5) to Indirect (Uu) V2V communications 71
7.27.1.3 Switching from Indirect (Uu) to Direct (PC5) V2V communications 72
7.27.2 Solution evaluation 73
8 Overall evaluation 74
8.1 General 74
8.2 Architecture evaluation 74
8.3 Key issue and solution evaluation 74
9 Conclusions 76
Annex A: Change history 77
Foreword
This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
1 Scope
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.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to V2X in 3GPPTS22.185[2], 3GPPTS22.186[3] and 3GPPTS23.285[8], as well as V2X application standards defined outside 3GPP.
This document will provide recommendations for normative work.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPPTR21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPPTS22.185: "Service requirements for V2X services; Stage 1".
[3] 3GPPTS22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
[4] 3GPP TS 22.804: "Study on Communication for Automation in Vertical domains (CAV)".
[5] 3GPPTR22.886: "Study on enhancement of 3GPP Support for 5G V2X Services".
[6] 3GPPTS23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[7] 3GPPTS23.280: "Common functional architecture to support mission critical services; Stage 2".
[8] 3GPPTS23.285: "Architecture enhancements for V2X services".
[9] 3GPPTS23.303: "Proximity-based services (ProSe); Stage 2".
[10] 3GPPTS23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[11] 3GPPTS23.501: "System Architecture for the 5G System; Stage 2".
[12] 3GPPTS23.502: "Procedures for the 5G System; Stage 2"
[13] 3GPPTS23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[14] 3GPPTR23.780: "Study on Multimedia Broadcast and Multicast Service (MBMS) usage for mission critical communication services".
[15] 3GPPTS26.238: "Uplink Streaming".
[16] 3GPPTS24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3".
[17] 3GPPTS26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[18] 3GPPTS26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[19] 3GPPTS26.347: "Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL".
[20] 3GPPTS26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[21] 3GPPTS28.530: "Management of 5G networks and network slicing; Concepts, use cases and requirements".
[22] 3GPPTS29.214: "Policy and Charging Control over Rx reference point".
[23] 3GPPTS29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".
[24] 3GPPTS36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[25] 3GPPTS36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[26] 3GPPTS36.443: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M2 Application Protocol (M2AP)".
[27] ETSITS102723-8(V1.1.1): "Intelligent Transport Systems (ITS); OSI cross-layer topics; Part 8: Interface between security entity and network and transport layer".
[28] ETSITS102940(V1.3.1): "Intelligent Transport Systems (ITS); Security; ITS communications security architecture and security management".
[29] ETSITS103097(V1.3.1): "Intelligent Transport Systems (ITS); Security; Security header and certificate formats".
[30] ETSITS103301(V1.1.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services".
[31] ETSIEN302637-2(V1.3.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[32] ETSIEN302637-3(V1.2.1): "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service".
[33] ETSIEN302665(V1.1.1): "Intelligent Transport Systems (ITS); Communications Architecture".
[34] IEEE1609.0-2013: "IEEE Guide for Wireless Access in Vehicular Environments (WAVE) architecture".
[35] International Organization for Standards, ISO21217:2014: "Intelligent transport systems -- Communications access for land mobiles (CALM) – Architecture", https://www.iso.org/standard/61570.html.
[36] International Organization for Standards, ISO/DIS17515-3: " Intelligent transport systems -- Evolved-universal terrestrial radio access network -- Part 3: LTE-V2X", https://www.iso.org/standard/73238.html.
[37] SAE International, SAEJ3016: "Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles", https://www.sae.org/standards/content/j3016.
[38] SAE International, SAEJ2945/3: "Requirements for V2I Weather Applications", https://www.sae.org/standards/content/j2945/3.
[39] SAE International, SAEJ2945/4: "DSRC Messages for Traveler Information and Basic Information Delivery", https://www.sae.org/standards/content/j2945/4.
[40] SAE International, SAEJ2945/6: "Performance Requirements for Cooperative Adaptive Cruise Control and Platooning", https://www.sae.org/standards/content/j2945/6.
[41] SAE International, SAEJ3161: "On-Board System Requirements for LTE V2X V2V Safety Communications", https://www.sae.org/standards/content/j3161.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR21.905[1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR21.905[1].
Editors note: Definitions for terms used in this document are FFS.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR21.905[1] and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR21.905[1].
5G 5th Generation
5GS 5G System
AN Access Network
AS Application Server
BM-SC Broadcast-Multicast Service Centre
BTP Basic Transport Protocol
CAM Cooperative Awareness Message
CoR Category of Requirements
DANE DASH Aware Network Element
DENM Decentralized Environmental Notification Message
E-UTRAN Evolved Universal Terrestrial Radio Access Network
ECGI
鏈接地址:http://kudomayuko.com/p-3390843.html