Description
Time to Collision (TTC) is a key performance metric used in vehicular communication and advanced driver assistance systems (ADAS), introduced in 3GPP Release 14 specifications 22.885 and 23.737. TTC is defined as the time it would take for two vehicles to collide if they continue on their current trajectories at their current speeds. It is a critical parameter for safety applications in V2X (Vehicle-to-Everything) communication, where vehicles exchange information to avoid accidents.
In the 3GPP context, TTC is used to characterize the latency and reliability requirements of V2X services. For example, a forward collision warning application may require that vehicles exchange messages with sufficient timeliness to allow the driver or autonomous system to react before the TTC falls below a threshold. The 3GPP specifications define performance requirements for V2X communication based on TTC, ensuring that the network can support the necessary message exchange within the required time.
The calculation of TTC involves the relative position and velocity of two vehicles. If vehicle A is approaching vehicle B from behind, the TTC is the distance between them divided by the relative speed. In more complex scenarios, such as intersections, TTC is calculated based on the projected paths of the vehicles. The 3GPP V2X architecture supports the exchange of basic safety messages (BSMs) or cooperative awareness messages (CAMs) that contain the necessary kinematic data for TTC calculation.
TTC is closely related to the latency requirements of V2X communication. For a TTC-based safety application to be effective, the end-to-end latency of the V2X message exchange must be significantly less than the TTC. 3GPP specifies latency requirements for V2X services, such as 100 ms for basic safety messages and lower for more critical applications. The network must ensure that messages are delivered within these bounds, which requires careful design of the radio access network, core network, and V2X application layer.
In Release 14, TTC was introduced as part of the study on V2X services, which laid the foundation for cellular V2X (C-V2X). Subsequent releases, including Release 16 and 17, expanded the V2X architecture to support advanced use cases such as platooning, extended sensors, and remote driving, all of which rely on TTC and other safety metrics to ensure reliable operation.
Purpose & Motivation
Time to Collision was introduced in 3GPP to provide a standardized metric for evaluating the performance of V2X safety applications. Before its introduction, V2X communication was largely based on IEEE 802.11p (DSRC), which had limited range and reliability. 3GPP sought to develop cellular V2X (C-V2X) as a more robust alternative, and TTC provided a way to quantify the safety benefits of the technology.
The TTC metric helps network designers and application developers understand the latency and reliability requirements for different safety use cases. For example, a collision warning at high speeds requires very low latency, while a warning at low speeds can tolerate higher latency. By defining TTC-based requirements, 3GPP ensures that the network can support the most critical applications.
TTC also addresses the need for interoperability between different V2X systems. By standardizing the metric and the message formats that carry the kinematic data, 3GPP enables vehicles from different manufacturers to exchange information and calculate TTC consistently. This is essential for the widespread deployment of V2X and for achieving the safety benefits that the technology promises.
Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference TTC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.885 ve00 | LTE Support for V2X Services | Rel-14 read |
| TR 23.737 vh20 | Satellite Access in 5G Architecture Study | Rel-17 read |