5 Requirements
22.1853GPPRelease 17Service requirements for V2X servicesTS
5.1 Overall Requirements
[R-5.1-001] The message transmission shall be under control of the 3GPP network when the transmitting UE is served by the E-UTRAN.
[R-5.1-002] A UE supporting V2X application shall be able to be pre-configured by the 3GPP network with parameters to be used for the transmission and reception of messages when not served by E-UTRAN supporting V2X communication.
[R-5.1-003] A UE supporting V2X application shall be able to transmit and receive messages when served or not served by E-UTRAN supporting V2X communication.
[R-5.1-004] An RSU shall be able to transmit/receive messages to/from a UE supporting V2X application.
[R-5.1-005] The 3GPP system shall be able to support message transfer between UEs when served or not served by the same PLMN supporting V2X communications.
[R-5.1-006] The 3GPP system shall be able to provide means to prioritize message transmission among UEs supporting V2X application
[R-5.1-007] The 3GPP system shall be able to provide means to prioritize transmission of messages according to their type (e.g. safety vs. non-safety).
[R-5.1-008] The 3GPP system shall be able to vary the transmission rate and range of the V2X communication based on service conditions (e.g., UE speed, UE density).
[R-5.1-009] The 3GPP system shall be able to distribute information in a resource efficient way to large numbers of UEs supporting V2X application.
[R-5.1-010] A UE supporting V2X application shall be able to identify whether E-UTRAN supports V2X communication.
[R-5.1-011] The 3GPP system shall be able to provide means for an application server and the RSU to control the area and the size of the area where the messages are being distributed.
[R-5.1-011a] The 3GPP system shall be able to provide means for distribution of messages from a UE supporting V2X application to locally relevant application servers.
[R-5.1-012] The E-UTRA(N) shall be able to support a high density of UEs supporting V2X application.
[R-5.1-013] Both the HPLMN and VPLMN operators shall be able to charge for network resource usage when messages are transferred by a UE supporting V2X application.
[R-5.1-014] For UE supporting V2X application with limited resources (e.g., battery), the impact on its resources (e.g., battery consumption) due to message transfer should be minimized.
[R-5.1-015] The 3GPP network should make available any supported positional accuracy improvement techniques (e.g., DGPS and/or OTDOA) in a resource efficient way to a subscribed UE supporting V2X application.
5.2 Specific Service Requirements
5.2.1 Latency/ Reliability Requirements
[R-5.2.1-001] The E-UTRA(N) shall be capable of transferring messages between two UEs supporting V2V/P application, directly or via an RSU, with a maximum latency of 100ms.
[R-5.2.1-002] For particular usage (i.e., pre-crash sensing) only, the E-UTRA(N) should be capable of transferring messages between two UEs supporting V2V application with a maximum latency of 20ms.
[R-5.2.1-003] The E-UTRA(N) shall be capable of transferring messages between a UE supporting V2I application and an RSU with a maximum latency of 100ms.
[R-5.2.1-004] The E-UTRAN shall be capable of transferring messages via 3GPP network entities between a UE and an application server both supporting V2N application with an end-to-end delay no longer than 1000 ms.
[R-5.2.1-005] The E-UTRA(N) shall be able to support high reliability without requiring application-layer message retransmissions.
5.2.2 Message Size Requirements
[R-5.2. 2-001] The E-UTRA(N) shall be capable of transferring periodic broadcast messages between two UEs supporting V2X application with variable message payloads of 50-300 bytes, not including security-related message component.
[R-5.2. 2-002] The E-UTRA(N) shall be capable of transferring event-triggered messages between two UEs supporting V2X application with variable message payloads which can be up to 1200 bytes, not including security-related message component.
NOTE: 3GPP only handles the transport of messages for V2X services/applications based on message characteristics (e.g., latency, message size) and is agnostic to message types.
5.2.3 Frequency Requirements
[R-5.2.3-001] The E-UTRA(N) shall be able to support a maximum frequency of 10 messages per second per transmitting UE .
NOTE: It is assumed that V2X application provides messages to 3GPP layer for transport either periodically and/or triggered by certain events.
5.2.4 Range Requirements
[R-5.2.4-001] The E-UTRAN shall be capable of supporting a communication range sufficient to give the driver(s) ample response time (e.g. 4 seconds).
5.2.5 Speed Requirements
[R-5.2.5-001] The 3GPP system shall be capable of transferring messages between UEs supporting V2V application, while the maximum relative velocity of the UEs is 500 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication.
[R-5.2.5-002] The 3GPP system shall be capable of transferring messages between UEs supporting V2V and V2P application, respectively, while the UE’s maximum absolute velocity is 250 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication.
[R-5.2.5-003] The 3GPP system shall be capable of transferring messages between a UE and an RSU both supporting V2I application, while the UE’s maximum absolute velocity is 250 km/h, regardless of whether the UE or the RSU is served or not served by E-UTRAN supporting V2X communication.
5.3 Security Requirements
[R.5.3-001] The 3GPP network shall provide a means for the MNO to authorize a UE supporting V2X application to perform V2X communication when served by E-UTRAN supporting V2X communication.
[R.5.3-002] The 3GPP network shall provide a means (e.g., pre-authorization) for the MNO to authorize a UE supporting V2X application to perform V2X communication when not served by E-UTRAN supporting V2X communication.
[R.5.3-003] The 3GPP network shall provide a means for the MNO to authorize UEs supporting V2X application separately to perform V2N communication.
[R.5.3-004] The 3GPP system shall support integrity protection of the transmission for a V2X application.
[R.5.3-005] Subject to regional regulatory requirements and/or operator policy for a V2X application, the 3GPP system shall support pseudonymity and privacy of a UE using the V2X application, by ensuring that a UE identity cannot be tracked or identified by any other UE beyond a certain short time-period required by the V2X application.
[R.5.3-006] Subject to regional regulatory requirements and/or operator policy for a V2V/V2I application, the 3GPP system shall support pseudonymity and privacy of a UE in the use of a V2V/V2I application, such that no single party (operator or third party) can track a UE identity in that region.
Annex A (informative):
Background Information on Service Requirement
The basic categories of V2X services for V2X decribed in the TR 22.885 can be grouped into the following main categories based on ITS defintion of basic set of services [3] :
1) Road Safety Requirements e.g Queue warning use case related requirements
2) Mutual Vehicle Awarness – Information only e.g forward collision warning requirements
3) Vehicle Related Application Requirements e.g Automated parking system requirement
Clause 5.2 refers to specific service requirements which are categoried as:
Latency/Reliability Requirements: Maximum tolerable elapsed time from the instant a data packet is generated at the source application to the instant it is received by the destination application. Low Latency values are provided to support services in the case of mutual awareness of vehicle or to send warning messages as defined in the some use cases in TR22.885
Reliability: Maximum tolerable packet loss rate at the application layer, a packet is considered lost if it is not received by the destination application within the maximum tolerable end-to-end latency for that application.
Message Size Requirements: Messages sizes are important when multicast or broadcast messages are being sent to vehicles within range to either warn them for collision prevention or when an event occurs to inform other vehicle about an accident.
Frequency Requirements: Minimum required bit rate for the application to function correctly. The sending rates i.e frequency of messages is relatively important especially for critical vehicular safety application.
Range Requirements: Maximum distance between source and destination(s) of a radio transmission within which the application should achieve the specified reliability
Speed Requirements: Maximum relative and absolute speed under which the specified reliability should be achieved.
With this brief description of the service categories, the table suggested below is used to reference the specific requirements in clause 5.2 to some of the use cases in the TR which makes for easy understanding and for better clarification of the suggested application of the services:
|
TS requirement |
Requirement |
Potential V2X service |
Use case Requirement in TR 22.885 |
|
Latency Requirement |
|
|
|
|
[R-5.2.1-001] |
The E-UTRA(N) shall be capable of transferring messages between two UEs supporting V2V/P application, directly or via an RSU, with a maximum latency of 100ms. |
Typical use case is for Mutual Vehicle Awareness and Road safety |
[CPR-014] |
|
[R-5.2.1-002] |
For particular usage (i.e., pre-crash sensing) only, the E-UTRA(N) should be capable of transferring messages between two UEs supporting V2V application with a maximum latency of 20ms. |
Requirement applies in Road safety use cases |
[CPR-015] |
|
[R-5.2.1-003] |
The E-UTRA(N) shall be capable of transferring messages between a UE supporting V2I application and an RSU with a maximum latency of 100ms. |
Requirement applys in Road safety use cases |
[CPR-016] |
|
[R-5.2.1-004] |
The E-UTRAN shall be capable of transferring messages via 3GPP network entities between a UE and an application server both supporting V2N application with an end-to-end delay no longer than 1000 ms. |
Applys to Mutual Vehicle Awareness use case |
[CPR-017] |
|
[R-5.2.1-005] |
The E-UTRA(N) shall be able to support high reliability without requiring application-layer message retransmissions. |
Mutual Vehicle Awareness and Road safety cases |
[CPR-027] |
|
Message Size |
|
|
|
|
[R-5.2. 2-001] |
The E-UTRA(N) shall be capable of transferring periodic broadcast messages between two UEs supporting V2X application with variable message payloads of 50-300 bytes, not including security-related message component. |
Supports all three use case categories |
[CPR-019] |
|
[R-5.2. 2-002] |
The E-UTRA(N) shall be capable of transferring event-triggered messages between two UEs supporting V2X application with variable message payloads which can be up to 1200 bytes, not including security-related message component. |
Mostly Road safety applications |
[CPR-020] |
|
Frequency |
|
|
|
|
[R-5.2.3-001] |
The E-UTRA(N) shall be able to support a maximum frequency of 10 messages per second per UE or per RSU. |
Road safety and Mutual Vehicle Awareness |
[CPR-011] |
|
Range Requirement |
|
|
|
|
[R-5.2.4-001] |
The E-UTRAN shall be capable of supporting a communication range sufficient to give the driver(s) ample response time (e.g. 4 seconds). |
|
[CPR-005] |
|
Speed Requirement |
|
|
|
|
[R-5.2.5-001] |
The 3GPP system shall be capable of transferring messages between UEs supporting V2V application, while the maximum relative velocity of the UEs is 500 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication. |
Road Safety, Mutual Vehicle Awareness |
[CPR-030] |
|
[R-5.2.5-002] |
The 3GPP system shall be capable of transferring messages between UEs supporting V2V and V2P application, respectively, while the UE’s maximum absolute velocity is 250 km/h, regardless of whether the UE(s) are served or not served by E-UTRAN supporting V2X communication. |
Road Safety, Mutual Vehicle Awareness |
[CPR-031] |
|
[R-5.2.5-003] |
The 3GPP system shall be capable of transferring messages between a UE and an RSU both supporting V2I application, while the UE’s maximum absolute velocity is 250 km/h, regardless of whether the UE or the RSU is served or not served by E-UTRAN supporting V2X communication. |
Road Safety, Mutual Vehicle Awareness |
[CPR-031] |
Annex B (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
Work Item |
|
SP-71 |
SP-160099 |
Raised to v.14.0.0 following one-step-approval by SA |
1.1.0 |
14.0.0 |
V2XLTE |
||||||
|
SP-72 |
SP-160357 |
S1-161219 |
22.185 |
0004 |
Rel-14 |
F |
V2X: correction of missing figure 4.1.2-1 |
14.0.0 |
14.1.0 |
V2XLTE |
|
|
SP-72 |
SP-160357 |
S1-161426 |
22.185 |
3 |
1 |
Rel-14 |
F |
Clarification of transmission frequency requirement |
14.0.0 |
14.1.0 |
V2XLTE |
|
SP-72 |
SP-160357 |
S1-161517 |
22.185 |
5 |
Rel-14 |
F |
Inclusion of Informative Annex to TS 22 185 |
14.0.0 |
14.1.0 |
V2XLTE |
|
|
SP-72 |
SP-160357 |
S1-161518 |
22.185 |
1 |
2 |
Rel-14 |
F |
V2X priority to other services |
14.0.0 |
14.1.0 |
V2XLTE |
|
SP-73 |
SP-160540 |
S1-162507 |
22.185 |
0002 |
7 |
Rel-14 |
F |
Correction on V2X privacy |
14.1.0 |
14.2.0 |
V2XLTE |
|
SP-73 |
SP-160540 |
S1-162504 |
22.185 |
0009 |
2 |
Rel-14 |
F |
Distribution of V2X messages to locally relevant V2X application servers |
14.1.0 |
14.2.0 |
V2XLTE |
|
SP-73 |
SP-160540 |
S1-162503 |
22.185 |
0010 |
2 |
Rel-14 |
F |
Correction of speed parameter values |
14.1.0 |
14.2.0 |
V2XLTE |
|
– |
– |
– |
– |
– |
– |
– |
– |
Version 14.2.0 was mentioning "14.1.0" in the front page. This is corrected in 14.2.1 |
14.2.0 |
14.2.1 |
– |
|
SP-170152 |
0011 |
2 |
D |
Clarification on Definition for V2X |
14.2.1 |
14.3.0 |
|||||
|
SP-170152 |
0012 |
|
F |
Corrections to requirement numbers in sub-clause 5.22 and Annex A |
14.2.1 |
14.3.0 |
|||||
|
SP-180309 |
0013 |
1 |
F |
Update the note in the RSU definition |
14.3.0 |
14.4.0 |
|||||
|
2018-06 |
– |
– |
– |
– |
– |
Rel-15 |
– |
Raised to Rel-15 by MCC |
14.4.0 |
15.0.0 |
– |
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|