Description
SV, or Space Vehicle Identification, is a numeric identifier assigned to each satellite within a Global Navigation Satellite System (GNSS) constellation. In 3GPP specifications, this identifier is used within positioning protocols and measurement reports to unambiguously refer to a specific satellite. The UE, when performing location measurements, uses the SV ID to correlate observed satellite signals with assistance data provided by the network or to report measurements for specific satellites back to the network. The specifications, such as TS 36.355 (LTE Positioning Protocol) and TS 37.571 (UE conformance for positioning), detail how SV IDs are formatted and used in messages between the UE and the Location Server (e.g., E-SMLC or LMF).
The architecture involves the UE's GNSS receiver, the serving mobile network, and the GNSS constellations themselves. The network's Location Server can provide assistance data to the UE, which includes almanac and ephemeris information keyed by SV ID, to help the UE acquire satellites faster (A-GNSS). When the UE performs measurements—such as code phase, Doppler, or carrier phase—it reports these measurements in a structure that includes the corresponding SV ID for each measured satellite. Different GNSS constellations have different SV ID numbering schemes. For example, GPS SV IDs range from 1 to 32, while Galileo uses a different range. The 3GPP specs define mappings and information elements to handle these various systems.
How it works is integral to positioning procedures. For instance, in an LTE Positioning Protocol (LPP) Provide Assistance Data message, the server may send ephemeris data for SVs 5, 12, and 19 (GPS). The UE then attempts to acquire signals from those specific satellites. In a subsequent LPP Provide Location Information message, the UE reports measured pseudoranges for the satellites it detected, again using their SV IDs. The network-side positioning algorithm uses these tagged measurements to compute the UE's location. The SV ID is therefore a critical piece of metadata that links raw signal measurements to the orbital dynamics of a specific satellite, enabling precise geometric calculations for positioning.
Purpose & Motivation
The SV identification system exists to enable standardized and efficient satellite-based positioning within 3GPP networks. Its primary purpose is to solve the problem of unambiguous communication between the UE and the network regarding which satellites are being used for location calculations. Without a common identifier, the network could not provide targeted assistance data or correctly interpret the UE's measurement reports, rendering Assisted GNSS (A-GNSS) ineffective.
Historically, as mobile networks began integrating location-based services (LBS) in 3GPP Release 99 and later, there was a need to support emerging consumer and regulatory requirements like E-911. Early methods like Cell-ID were insufficiently accurate. The integration of GNSS capabilities required a way to bridge the world of satellite navigation (with its own identification schemes) with the world of cellular signaling protocols. The adoption of SV ID within 3GPP specs provided this bridge, allowing cellular networks to leverage the high accuracy of GNSS.
The motivation was driven by the demand for precise location services for emergency calls, navigation, asset tracking, and location-based applications. By standardizing the use of SV IDs across all UE and network vendor implementations, 3GPP ensured interoperability. It allowed any compliant UE to work with any compliant network's location server, regardless of the underlying GNSS chipset or constellation preferences. This was crucial for the global rollout of reliable, network-assisted positioning, which reduces UE power consumption and time-to-first-fix compared to standalone GNSS operation.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (11 CRs across 6 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the newly introduced SV function involved the partitioning of the identifier space to ensure the success of context retrieval for EPS interworking. This enhancement specifically addressed the logical identification used for a radio link within a sector to facilitate proper inter-system operations. Additionally, the release included the identification and update of the UE-derived QoS rule, relating to the negotiated QoS attributes managed by the network.
In Release 16, the new work for the SV function involved updating the identification of LTE-M (eMTC) traffic and removing the previous requirement to use the TAC+SV combination for UE model identification within the manufacturer assigned ID. These changes refined the procedures for network connection and user identification without altering the fundamental concepts of a logical identification for a radio link or a secured packet information flow.
In Release 17, the new SV (Space Vehicle Identification) function introduced specific identification and mobility restrictions for satellite access. This allowed a satellite, acting as a radio network object uniquely identifiable from a broadcasted cell identification, to be explicitly managed within the network. The enhancements provided a framework for the secure association and identification of these satellite-based access points.
- Identification and mobility restrictions for satellite access TS 23.501CR2538
In Release 18, the enhancements to the SV (ID Space Vehicle Identification) function specifically provided clarifications on the applicability of the Protocol Description within a Packet Data Router (PDR) for the identification of End of Data Block (EoDB) in the Downlink (DL). This update focused on refining the procedural details for EoDB identification, ensuring clearer implementation guidance. The changes were confined to the technical mechanisms within the specified protocol description framework for this identification process.
- Clarifications on applicability of Protocol Description in PDR for EoDB identification in DL TS 23.501CR5295
In Release 19, the SV function introduced new capabilities for PDU Set information identification specifically for end-to-end encrypted traffic, supporting both MoQ-based identification and identification using connect-UDP. These enhancements were complemented by architectural updates and corrections to multiplexed media identification information to improve the handling of secured packets.
In Release 20, the SV (ID Space Vehicle Identification) function introduced the capability for the identification of an INS case and a hosting operator. This provides explicit identification for network data transmissions involving space vehicles within the negotiated services framework. The update leverages the existing framework for logical identification within a sector and the concept of a network connection.
- Identification of INS case and hosting operator TS 23.501CR6423
Explore further
Broader topics and technologies where SV plays a role.
Defining Specifications
3GPP specifications that define or reference SV, 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 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| 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.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| 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 44.031 vj00 | Radio Resource LCS Protocol (RRLP) | Rel-19 |
| TS 51.010 vj00 | SIM Application Toolkit Conformance Testing | Rel-19 |