Description
Earth-Centered, Earth-Fixed (ECEF) is a three-dimensional, right-handed Cartesian coordinate system that serves as a fundamental geodetic reference frame within 3GPP specifications for positioning and location services. The origin (0,0,0) of the ECEF system is defined as the Earth's center of mass. The X-axis extends from the origin through the intersection of the Equator and the Prime Meridian (0° longitude). The Y-axis is orthogonal to the X-axis in the equatorial plane, extending through 90° East longitude. The Z-axis is aligned with the Earth's rotational axis, pointing towards the North Pole. Crucially, the coordinate axes are 'fixed' with respect to the Earth's body; they rotate along with the Earth, unlike an inertial space-fixed frame. This provides a stable, Earth-bound reference for describing locations of objects on or near the Earth's surface.
Within 3GPP architectures, ECEF coordinates (typically expressed in meters as X, Y, Z triplets) are used as a common format for exchanging high-precision location information between network entities. Key functional nodes that utilize ECEF include the Location Management Function (LMF) in 5G, the Enhanced Serving Mobile Location Centre (E-SMLC) in LTE, and the Standalone SMLC (SAS) in UMTS. These entities calculate or receive UE position estimates, often converting them from other formats (like ellipsoidal latitude/longitude/altitude) into ECEF for internal computations or signaling. For example, positioning methods like Observed Time Difference of Arrival (OTDOA) and Uplink Time Difference of Arrival (UTDOA) involve calculating hyperboloids based on time-difference measurements; these geometric calculations are often performed more efficiently in the Cartesian ECEF space.
The use of ECEF is integral to the operation of Assisted GNSS (A-GNSS), a primary high-accuracy positioning method. The network (e.g., LMF) provides assistance data to the UE, which can include the ECEF coordinates of GNSS satellites' positions and velocities, as well as the ECEF position of the reference location. This allows the UE's GNSS receiver to compute its own ECEF position directly. Subsequently, this position may be converted to a more user-friendly format like latitude, longitude, and altitude (LLA) based on a specific reference ellipsoid (e.g., WGS-84). The standardization of ECEF across 3GPP releases ensures unambiguous and mathematically consistent positioning across different network generations (UMTS, LTE, NR) and between network equipment and UEs from different vendors, forming the bedrock for reliable and interoperable location services.
Purpose & Motivation
The adoption of the ECEF coordinate system within 3GPP was motivated by the need for a precise, unambiguous, and computationally efficient reference frame for terrestrial positioning calculations. Early mobile location services often relied solely on cell identity or signal strength, which provided only coarse, network-centric location estimates. The drive for more accurate positioning for emergency services (e.g., E-911 in the US) and commercial Location-Based Services (LBS) necessitated the integration of geometric positioning methods like GNSS and OTDOA. These methods require a rigorous mathematical framework.
ECEF was chosen over other coordinate systems (like pure latitude/longitude) for several key reasons. First, it provides a true 3D framework essential for altitude determination and for calculations involving satellites whose orbits are naturally described in an Earth-centered frame. Second, Cartesian coordinates (X, Y, Z) are far more convenient for the vector mathematics involved in calculating distances, time-differences-of-arrival, and intersection points of hyperboloids or spheres—core operations in OTDOA and GNSS positioning. Performing these operations directly in ellipsoidal coordinates is complex and computationally intensive. By standardizing ECEF, 3GPP provided a common 'language' for high-accuracy location data that simplifies implementations, reduces errors in coordinate transformation, and ensures that positioning results are consistent and interoperable across the global network ecosystem.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (31 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-15.
In Release 15, support for ECEF was not explicitly mentioned in the provided context. The related enhancements primarily focused on positioning techniques, specifically introducing IMU support for OTDOA, adding OTDOA assistance data requests for NR, and including TDD UL/DL configuration within that assistance data.
- Introduction of IMU support for OTDOA TS 36.355CR0204
- OTDOA Assistance Data Request for NR TS 36.355CR0222
- Addition of TDD UL/DL configuration to OTDOA assistance data TS 36.355CR0213
- SFN offset for OTDOA TS 36.355CR0229
- CR on A-GNSS in 38.171 TS 38.171CR0001
- CR to TS 38.171: Corrections to A-GNSS requirements with NR TS 38.171CR0008
In Release 16, the key update for the ECEF function was the introduction of the BDS B1C signal for A-GNSS positioning, alongside an update to the B1I signal ICD file to version 3.0 for the BeiDou system. The release also added support for providing OTDOA assistance data in cases where the serving cell is NR (New Radio). Furthermore, it included necessary corrections to OTDOA positioning support descriptions and defined frequency bands for testing A-GNSS sensitivity requirements.
- CR for TS36.171, Introduction of BDS B1C in A-GNSS TS 36.171CR0020
- Introduction of B1C signal in BDS system in A-GNSS TS 36.305CR0083
- Introduction of B1C signal in BDS system in A-GNSS TS 37.355CR0248
- CR for TS38.171, Introduction of BDS B1C in A-GNSS TS 38.171CR0011
- Introduction of B1C signal in BDS system in A-GNSS TS 38.305CR0013
- Frequency bands for testing of A-GNSS sensitivity requirements TS 36.171CR0025
+ 6 more changes
In Release 17, the new ECEF-related functionality specifically introduced support for A-GNSS using the NavIC system, including its L5 frequency band. This required updates to the technical specifications for both LTE (TS 36.171) and NR (TS 38.171) to define the corresponding requirements. The release also included a correction to the unique GNSS-ID identifier used for the NavIC system within these A-GNSS procedures.
In Release 18, the update to the ECEF function specifically involved corrections to the support parameters for GNSS-Almanac and GNSS-UTC-Model within A-GNSS positioning procedures. This refinement ensures more accurate assistance data transfer between the network and the User Equipment for location services. The change directly impacts the technical capabilities for delivering positioning services irrespective of the user's access technology.
- Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning TS 37.355CR0518
In Release 19, the ECEF function was enhanced through the introduction of support for new global navigation satellite system signals in the Assisted-GNSS (A-GNSS) framework. Specifically, the release added support for the BDS B2b signal from the BeiDou system and the NavIC L1 SPS signal from the NavIC system across multiple specifications, including LTE Stage 2, NR Stage 2, and the LPP protocol. These updates extended A-GNSS capabilities to utilize these additional satellite constellations for improved positioning.
- CR for TS 36.171 to introduce BDS B2b signal in A-GNSS TS 36.171CR0032
- Introduction of NavIC L1 SPS A-GNSS in LTE Stage 2 specification TS 36.305CR0120
- Introduction of BDS B2b in A-GNSS TS 36.305CR0121
- Introduction of NavIC L1 SPS A-GNSS in LPP TS 37.355CR0532
- Introduction of B2b signal in BDS system in A-GNSS TS 37.355CR0545
- CR for TS 38.171 to introduce BDS B2b signal in A-GNSS TS 38.171CR0031
+ 2 more changes
Explore further
Broader topics and technologies where ECEF plays a role.
Defining Specifications
3GPP specifications that define or reference ECEF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 25.171 vj00 | A-GPS Minimum Performance Requirements for UTRA FDD UE | Rel-19 |
| TS 25.172 vj00 | A-GANSS UE Minimum Performance Requirements (FDD) | Rel-19 |
| TS 25.173 vj00 | A-GANSS Performance Requirements (TDD) | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 |
| TS 36.171 vj10 | A-GNSS Minimum Performance Requirements for UE | Rel-19 |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 |
| TS 38.171 vj10 | 5G A-GNSS UE Positioning Requirements | Rel-19 |
| TS 38.305 vj00 | NG-RAN UE Positioning Stage 2 | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.821 vg20 | NR Support for Non-Terrestrial Networks | Rel-16 |
| TS 44.031 vj00 | Radio Resource LCS Protocol (RRLP) | Rel-19 |
| TS 45.005 vj00 | GSM RF Requirements for MS and BSS | Rel-19 |