Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.786  Word version:  16.1.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Architectural Assumptions and Requirements  4.1 Architectural Assumptions  4.2 Architectural Requirements 
...

 

1  Scope  p. 11

The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and 5G System design needed to support advanced V2X services identified in TR 22.886, based on vehicular services requirements defined in TS 22.185 and TS 22.186 and determine which of the solutions can proceed to normative specifications.
In Rel-15, the study focuses on EPS.
Up

2  References  p. 11

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 non-specific.
  • 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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TR 22.886: "Study on enhancement of 3GPP Support for 5G V2X Services".
[3]
TS 22.185: "Service requirements for V2X services; Stage 1".
[4]
TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
[5]
TS 23.285: "Architecture enhancements for V2X services".
[6]
TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[7]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[8]
TS 23.303: "Proximity-based Services (ProSe); Stage 2".
[9]
TS 23.502: "Procedures for the 5G System; Stage 2".
[10]
TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[11]
TS 33.303: "Proximity-based Services (ProSe); Security aspects".
[12]
TS 23.203: "Policy and charging control architecture".
[13]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
[14]
TS 36.440: "General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN".
[15]
TR 23.724: "Study on Cellular IoT support and evolution for the 5G System".
[16]
TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".
[17]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[18]
TS 25.446: "MBMS synchronisation protocol (SYNC)".
[19]  Void.
[20]  Void.
[21]
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[22]
TS 22.261: "Service requirements for next generation new services and markets".
[23]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[24]
TS 28.552: "Management and orchestration; 5G performance measurements".
Up

3  Definitions and abbreviations  p. 12

3.1  Definitions  p. 12

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 23.285 and TS 23.501 apply.

3.2  Abbreviations  p. 12

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.285, TS 23.501 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
CoR
Categories of Requirements
LoA
Level of Automation
RN
Rank Notification
V2X AS
V2X Application Server
V2XCF
V2X Control Function
VQI
V2X 5QI
Up

4  Architectural Assumptions and Requirements  p. 12

4.1  Architectural Assumptions  p. 12

4.1.1  General  p. 12

  • Architecture reference models defined in TS 23.285 (i.e. PC5 and LTE-Uu based V2X architecture reference model and MBMS for LTE-Uu based V2X architecture reference model) are used as basis architecture for supporting eV2X services in EPS.
  • For EPS based enhancement, it is assumed that AS layer impact for solutions in this TR should be avoided as much as possible.
  • eV2X Groups are handled within the V2X application which is out of scope of 3GPP.
  • Architecture reference models defined in TS 23.501 are used as baseline architecture for supporting eV2X services in 5GS.
  • For V2X configuration of parameters known as Service Authorization and Provisioning of the UE, the architecture is based on Alternative #1 (V2XCF as part of the PCF) of Annex A.1 and parameters are provided by the PCF to the UE via the AMF based on procedure in clause 4.2.4.3 of TS 23.502 'UE Configuration Update procedure for transparent UE Policy delivery'.
  • The provisioning mechanism also includes pre-configuration in the UE (via UICC or ME) and, either via V1 directly or via AF/PCF, parameter provisioning to the UE from the V2X Application Server.
Up

4.1.2  PC5 and NG-RAN Uu based V2X architecture reference model  p. 13

The high-level view of the non-roaming, roaming and inter-PLMN 5G System architecture for PC5 and Uu based V2X communication are depicted in Figure A.1.1.3-1, Figure A.1.1.3-2 and Figure A.1.1.3-3, respectively.

4.2  Architectural Requirements  p. 13

Up   Top   ToC