Description
Relative Position is a positioning concept introduced in 3GPP Release 17 within the framework of NR positioning enhancements. Unlike absolute positioning, which yields geographic coordinates (latitude, longitude, altitude) in a global reference frame, relative position describes where a UE is with respect to other entities — other UEs, network nodes such as gNBs or transmission-reception points, or reference points in a local coordinate system. This distinction is important because many applications only need to know spatial relationships (for example, whether two devices are within a certain distance, or the direction from one device to another) rather than global coordinates.
The concept is closely associated with sidelink positioning, where UEs communicate directly with each other to exchange ranging and positioning signals. In such scenarios, a target UE's position can be estimated relative to anchor UEs whose positions may be known absolutely, partially known, or even unknown. Relative positioning thus extends location services to environments where GNSS is unavailable (indoors, in tunnels, in coverage holes) and where the network may not have enough infrastructure to compute absolute positions. It also supports use cases such as public safety (locating team members relative to each other), industrial IoT (asset proximity), and vehicular applications (relative spacing between vehicles).
Architecturally, relative position is supported through the location services (LCS) framework defined in specifications such as 23.700 (study of positioning enhancements), 38.305 (NG-RAN positioning stage 2), and 38.845 (sidelink positioning study). The LCS architecture includes the LMF (Location Management Function) in the core network, which coordinates positioning procedures, and the UE, which may perform measurements and, in sidelink scenarios, participate directly in ranging. Positioning methods that can produce relative results include sidelink round-trip time, angle-based measurements, and hybrid approaches combining multiple signal types.
A key aspect of relative positioning is that it relaxes requirements on absolute accuracy and infrastructure knowledge. Because the output is a relationship rather than a coordinate, the estimation can often be performed with fewer anchors and lower signaling overhead. However, it introduces its own challenges: defining a consistent local reference frame, handling mobility of anchors, and ensuring that relative results can be transformed into absolute positions when needed (for example, when one entity's absolute position becomes known).
For engineers, Relative Position represents a shift in how positioning is conceptualized — from a network-centric absolute coordinate service to a flexible, relationship-based capability that can operate device-to-device. It is foundational for emerging sidelink and cooperative positioning use cases in 5G-Advanced and beyond.
Purpose & Motivation
Relative Position was created to address a gap in traditional cellular positioning, which was designed around producing absolute geographic coordinates. Many emerging use cases do not require global coordinates and cannot rely on GNSS — indoor robots, public safety teams, vehicle platoons, and industrial assets often need to know only how far apart or in what direction devices are from each other. Requiring absolute positioning in these scenarios would demand more infrastructure, more anchors, and more signaling than necessary.
The concept also enables positioning in environments where absolute references are unavailable. In sidelink scenarios, UEs can range each other directly, and a device with a known position can serve as an anchor to convert relative measurements into absolute ones. This flexibility was a key motivation for Release 17 positioning enhancements, which extended NR positioning beyond network-based methods to device-to-device cooperation.
Historically, earlier releases focused on absolute positioning methods such as OTDOA, E-CID, and later NR multi-RTT and AoD/AoA. These methods assume network infrastructure and known anchor locations. Relative Position broadens the positioning toolbox to cover cooperative and infrastructure-light scenarios, reflecting the growing importance of sidelink communication and the diverse requirements of vertical industries.
What changed in its specifications
The latest release-to-release comparison of specifications that define Relative Position. Each summary describes the whole specification, not only this term.
Rel-19 adds enhanced NR topology support to TS 38.305, including WAB-gNB, updated definitions and gNB-to-LMF information transfer. It also includes two further related items.
Full comparison in TS 38.305 →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 Relative Position, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |
| TR 38.845 vh00 | NR Positioning Use Cases Study | Rel-17 read |