The objective of this document is to identify use cases and potential service requirements to enhance 3GPP support for V2X service in the following areas:

• Support for non-safety V2X services (also, referred to as "comfort service") (e.g. connected vehicle, mobile high data rate entertainment, mobile hot-spot/office/home, dynamic digital map update)
• Support for safety-related V2X services (e.g. autonomous driving, car platooning, priority handling between safety-related V2X services and other services)
• Support for V2X services in multiple 3GPP RATs (e.g. LTE, New RAT (NR)) and networks environment, including aspects such as interoperability with non-3GPP V2X technology (e.g. ITS-G5, DSRC, ITS-Connect)

In this document, V2X-related use cases and potential requirements already included in TR 22.891 are considered and new ones are introduced. The identification of use cases and potential requirements covers both evolved LTE RAT and new 3GPP RAT (e.g. NR) and also covers V2X operation using 3GPP RATs where there are non-3GPP V2X technologies (e.g. ITS-G5, DSRC, ITS-Connect) in use.

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.

A basic set of requirements for EPS to support V2X applications have been specified in [25]. These requirements are considered sufficient for vehicles (i.e., UEs supporting V2X applications) to exchange their own status information, such as position, speed and heading, with other nearby vehicles, infrastructure nodes and/or pedestrians. Also, these requirements fulfil the need to disseminate imminent warning messages to nearby entities in time. The capability of EPS to support these requirements will expedite the adoption of 3GPP connectivity by vehicles. Despite the basic set of requirements for 3GPP system to support V2X service, it is considered growingly important among telecommunication industry and automotive industry that its evolution is necessary. Because automotive industries have begun to see V2X applications beyond unidirectional distribution of status information of vehicles, the 3GPP system needs to increase its capability enough to meet KPIs that emerging V2X applications require. That is, as V2X applications advance, transmission of short messages about vehicles' own status data will be complemented with transmission of larger messages containing raw sensor data, vehicles' intention data, coordination and confirmation of future manoeuvre and so on. For these advanced applications, the expected requirements to meet the needed data rate, reliability, latency, communication range and speed are made more stringent. A relevant aspect of advanced V2X applications is the Level of Automation (LoA), which reflects the functional aspects of the technology and affects the system performance requirements. In accordance with the levels from SAE [X1] and NHTSA [X2], the LoA are: 0 - No Automation, 1 - Driver Assistance, 2 - Partial Automation, 3 - Conditional Automation, 4 - High Automation, 5 - Full Automation. A distinction is drawn between Levels 0-2 (Driver Control) and 3-5 (Vehicle Control) based on whether the human operator or the automated system is primarily responsible for monitoring the driving environment.