Time To First Fix

Description

Time To First Fix (TTFF) is a fundamental performance metric for Global Navigation Satellite System (GNSS) receivers, including those in mobile devices for 3GPP-based positioning. It quantifies the time elapsed from when a receiver is powered on or starts a positioning request until it outputs a valid position fix with a specified accuracy. This metric is crucial for evaluating the responsiveness and usability of location-based services (LBS). The TTFF is measured under different start conditions, which significantly impact its duration: Cold Start, Warm Start, and Hot Start.

A Cold Start represents the worst-case scenario where the receiver has no prior knowledge. It must perform a full sky search for satellites, download the complete almanac and ephemeris data (navigation messages) from each satellite, and then compute a position. This process can take 30 seconds to several minutes, depending on signal conditions and receiver sensitivity. The receiver sequentially searches for signals, decodes the slow 50 bps navigation data stream from each satellite to obtain orbital parameters (ephemeris), and requires signals from at least four satellites to compute a 3D position.

A Warm Start assumes the receiver has a valid, but not current, almanac (a coarse database of all satellite orbits) and approximate time and position. This allows it to predict which satellites should be visible, narrowing the search. However, it still needs to download fresh ephemeris data from each satellite, which takes 18-30 seconds per satellite as the data is broadcast in subframes. A Hot Start is the fastest condition, where the receiver has valid ephemeris data (less than 2-4 hours old), precise time, and an approximate position. It can immediately acquire the predicted satellites and compute a fix, often in under one second, as it only needs to synchronize with the satellite signals and measure pseudoranges.

Within 3GPP standards, TTFF is specified as a performance requirement for User Equipment (UE) supporting Assisted GNSS (A-GNSS). In A-GNSS, the network provides assistance data (like ephemeris, almanac, approximate time, and UE position) to the UE over cellular signaling. This assistance data dramatically reduces the TTFF by eliminating or shortening the time needed for the UE to decode this information from the satellites themselves. The 3GPP specifications define test procedures and minimum performance criteria for TTFF under various assisted and non-assisted scenarios to ensure a consistent user experience for emergency services (e.g., E-911) and commercial LBS.

Purpose & Motivation

TTFF exists as a critical metric to quantify and standardize the startup performance and responsiveness of positioning systems, which is directly tied to user experience. In early standalone GPS devices, long cold-start times were a significant usability issue, frustrating users who had to wait minutes for a navigation fix. For emergency services like Enhanced 911 (E-911), a long TTFF could be life-threatening, as the location of a caller needs to be determined as quickly as possible.

The creation and standardization of TTFF within 3GPP was motivated by the integration of positioning capabilities into cellular devices and the need to guarantee performance for regulatory and commercial services. 3GPP standards, such as those for A-GNSS, aimed to mitigate the inherent limitations of standalone GNSS reception in challenging environments (urban canyons, indoors) and to speed up the positioning process. By defining TTFF requirements and test methodologies, 3GPP ensures that UEs from different manufacturers provide a predictable and acceptable level of performance.

Furthermore, optimizing TTFF drives innovation in receiver design, signal processing algorithms, and network assistance protocols. It addresses the problem of the 'navigation data bottleneck'—the slow data rate broadcast from satellites. Solutions like A-GNSS, prediction of ephemeris, and use of other sensor data (sensor fusion) are all evaluated, in part, by their impact on reducing TTFF. Thus, TTFF serves as a key benchmark for the entire positioning technology ecosystem within mobile communications.

Key Features

• Defined for three start conditions: Cold, Warm, and Hot Start
• Key performance indicator (KPI) for GNSS and A-GNSS receiver performance
• Directly impacts user experience for location-based services and emergency calls
• Specified in 3GPP as a conformance test requirement for UE
• Greatly reduced by network-provided Assistance Data in A-GNSS
• Influenced by signal environment, receiver sensitivity, and assistance data freshness

Evolution Across Releases

Defining Specifications