BDS

BeiDou Navigation Satellite System

Other →
Introduced in Rel-8 Also in: User Equipment, Services, Testing

BDS is the Chinese global satellite navigation system integrated into 3GPP standards to provide positioning, navigation, and timing services for mobile devices, enhancing cellular network capabilities.

Category
Other
Introduced
Rel-8
Where
Radio Access Network › NG-RAN (5G)
Also touches
3 segments
Specifications
23 specs
BDS Description Purpose Related Classification Detected Changes Specifications

Description

The BeiDou Navigation Satellite System (BDS) is a satellite-based radio navigation system owned and operated by China. Within the 3GPP framework, BDS is standardized as a Global Navigation Satellite System (GNSS) for user equipment (UE) positioning. The system architecture comprises three segments: the space segment (satellites), the ground control segment (master control stations, upload stations, monitoring stations), and the user segment (receivers in UEs). The space segment includes a constellation of satellites in geostationary Earth orbit (GEO), inclined geosynchronous orbit (IGSO), and medium Earth orbit (MEO), providing global coverage with enhanced regional service over Asia-Pacific.

BDS operates by transmitting precise timing signals and navigation messages from its satellites. A UE with a BDS receiver measures the time of arrival of signals from multiple visible satellites. Using these measurements and the known satellite positions (ephemeris data from navigation messages), the UE calculates its position via trilateration. The system provides multiple service signals across different frequency bands (e.g., B1, B2, B3), offering open (civilian) and authorized (military/secure) services. The signals use Code Division Multiple Access (CDMA) modulation with specific pseudo-random noise (PRN) codes for satellite identification.

In the 3GPP architecture, BDS is integrated through control plane and user plane positioning protocols defined in specifications such as TS 36.355 (LTE Positioning Protocol - LPP) and TS 38.455 (NR Positioning Protocol A - NRPPa). The network can assist the UE by providing assistance data like satellite ephemeris, almanac, and timing information via the LTE Positioning Protocol (LPP) or NRPPa, which reduces Time To First Fix (TTFF) and improves power efficiency. The Location Management Function (LMF) in the 5G core network or the Enhanced Serving Mobile Location Centre (E-SMLC) in LTE manages these positioning sessions, requesting BDS measurements from the UE or gNB/ng-eNB.

BDS's role is critical for fulfilling regulatory requirements (e.g., emergency caller location), enabling location-based services (LBS), and supporting applications like vehicle tracking, IoT asset monitoring, and navigation. Its integration allows hybrid positioning with other GNSS (like GPS, Galileo) and terrestrial methods (OTDOA, E-CID), enhancing accuracy, availability, and reliability. Performance is characterized by parameters such as accuracy (meter-level for open service), integrity, and continuity, specified in test requirements documents like TS 37.571.

Purpose & Motivation

BDS was created to provide China with an independent, global satellite navigation capability, reducing reliance on foreign systems like GPS (USA) and GLONASS (Russia). Its integration into 3GPP standards addresses the need for diversified and resilient Positioning, Navigation, and Timing (PNT) sources in mobile networks. Prior to its inclusion, cellular positioning primarily depended on GPS, which posed risks related to availability, sovereignty, and service continuity in certain regions or during conflicts.

The motivation for standardizing BDS in 3GPP, starting from Release 8, was to enable worldwide interoperability and support for Chinese satellite signals in commercial mobile devices. This allows network operators and device manufacturers to leverage BDS for improved positioning performance, especially in the Asia-Pacific region where its signals are stronger due to regional satellite augmentation. It solves problems of single-point failure in PNT services and enhances location accuracy in urban canyons or challenging environments through multi-constellation GNSS receivers.

Historically, early cellular positioning methods like Cell-ID offered low accuracy, while later techniques like Assisted-GPS (A-GPS) improved precision but were tied to specific GNSS constellations. BDS integration, alongside other GNSS, provides a more robust and accurate solution, supporting emerging demands from autonomous vehicles, drone navigation, and precise timing for network synchronization. It also fulfills Chinese regulatory mandates for emergency services and national security, ensuring domestic control over critical infrastructure.

Classification

Part ofGNSS

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (22 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 12 changes

In Release 16, 3GPP introduced support for the BeiDou B1C signal in Assisted GNSS (A-GNSS) across both LTE (TS36.171) and NR (TS38.171) specifications. The release also updated the reference documentation for the existing B1I signal to its Interface Control Document (ICD) version 3.0. Furthermore, corrections and additions were made to BDS data models, including updates to the B2I clock model and the addition of missing parameters like TGD2.

  • 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
  • Addition of missing data for BDS B1C TS 36.171CR0021

+ 6 more changes

Rel-17 5 changes

In Release 17, the BeiDou Navigation Satellite System (BDS) support was enhanced through the introduction of new signals and clarified requirements. Specifically, the release introduced the B2a and B3I signals for BDS and addressed GNSS positioning integrity. Furthermore, it defined requirements for the relative signal power levels of BDS for both LTE (TS 36.171) and NR (TS 38.171) and provided clarifications and corrections for SSR (State Space Representation) assistance data, including orbit ephemeris alignment with RTCM standards and transmission based on the B1C signal.

  • Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity TS 36.305CR0107
  • CR on TS 36.171 requirements for relative signal power levels of BDS TS 36.171CR0030
  • GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM TS 37.355CR0461
  • Correction on transmission of SSR Assistance Data based on BDS B1C TS 37.355CR0485
  • CR on TS 38.171 requirements for relative signal power levels of BDS TS 38.171CR0024
Rel-19 5 changes

In Release 19, the key enhancement for the BeiDou Navigation Satellite System (BDS) function was the formal introduction of the B2b signal for Assisted GNSS (A-GNSS) positioning. This update was standardized across multiple technical specifications, including those for LTE (TS 36.171) and NR (TS 38.171 and TS 38.305), to enable user equipment to utilize this specific BDS signal. The change therefore expanded the supported signals for BDS within the A-GNSS framework, improving positioning capabilities.

  • CR for TS 36.171 to introduce BDS B2b signal in A-GNSS TS 36.171CR0032
  • Introduction of BDS B2b in A-GNSS TS 36.305CR0121
  • 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
  • Introduction of BDS B2b in A-GNSS for TS 38305 TS 38.305CR0180

Explore further

Broader topics and technologies where BDS plays a role.

Defining Specifications

3GPP specifications that define or reference BDS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 22.071 vj00 3GPP TS 22.071: Location Services (LCS) Stage 1 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.305 vj00 UTRAN UE Positioning Stage 2 Rel-19
TS 25.306 vj00 UE Radio Access Capabilities Specification Rel-19
TS 25.331 vj00 UTRAN RRC Protocol Specification Rel-19
TS 25.413 vj00 Radio Access Network Application Part (RANAP) Rel-19
TS 25.423 vj00 UTRAN RNSAP Specification Rel-19
TS 25.433 vj00 Node B Application Part (NBAP) Protocol Rel-19
TS 25.453 vj00 PCAP Protocol Specification Rel-19
TS 32.808 v1800 Common User Profile Storage Framework Rel-8
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.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 38.305 vj00 NG-RAN UE Positioning Stage 2 Rel-19
TS 38.455 vj10 NR Positioning Protocol A (NRPPa) Rel-19
TS 43.059 vj00 GERAN LCS Stage 2 Specification Rel-19
TS 44.031 vj00 Radio Resource LCS Protocol (RRLP) Rel-19
TS 45.005 vj00 GSM RF Requirements for MS and BSS Rel-19
TS 51.010 vj00 SIM Application Toolkit Conformance Testing Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.