Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Protocol

GM

Grand Master

Protocol →

GM is the authoritative clock source in a time synchronization hierarchy, such as IEEE 1588 PTP or IEEE 802.1AS, that distributes reference time to all downstream clocks and provides timing for 3GPP TSN, 5G synchronization, and time-sensitive services.

Introduced
Rel-8
Where
Services › IMS
Specifications
3 specs
GM Description Purpose What changed Neighbours Specifications

Description

The Grand Master (GM) is the root of a time synchronization hierarchy. In a Precision Time Protocol (PTP) network defined by IEEE 1588, or in an IEEE 802.1AS (gPTP) network, the GM is the clock that serves as the ultimate reference time source for all other clocks in the synchronization domain. All downstream clocks — boundary clocks, transparent clocks, and ordinary clocks — synchronize their time to the GM, either directly or through intermediate nodes. The GM is typically a highly accurate clock, often disciplined by a Global Navigation Satellite System (GNSS) such as GPS, or by an atomic clock, ensuring traceability to a recognized time standard.

In the 3GPP context, the GM concept appears in several areas. First, in Time-Sensitive Networking (TSN) integration with the 5G System, the 5G System can act as a TSN bridge, and the GM provides the reference time for the TSN domain. The 3GPP specifications 23.255 (Application layer support for 5G media streaming), 29.199 (Open Service Access), and 38.825 (Study on 5G synchronization) address aspects of time synchronization and GM distribution. Second, in 5G radio access, the gNB and the core network require accurate time synchronization for features such as TDD, carrier aggregation, and coordinated multipoint; the GM provides this reference through the synchronization chain.

The synchronization hierarchy works as follows. The GM sends synchronization messages (Sync, Follow_Up, and optionally Announce messages in PTP) to its directly connected neighbors. These neighbors, acting as boundary clocks, recover the time and then re-distribute it to their own downstream neighbors. Each boundary clock may also serve as a GM for a subordinate domain. The Best Master Clock Algorithm (BMCA) is used to automatically select the GM among candidate clocks based on their quality attributes, such as clock class, accuracy, and priority. This automatic selection ensures that the network converges on the best available time source and can recover if the current GM fails.

The GM is characterized by its clock quality, which is described by attributes such as clockClass, clockAccuracy, and offsetScaledLogVariance. These attributes are carried in the Announce messages and are used by the BMCA. A GM with a direct GNSS reference typically has a high clock class (low numerical value), indicating high quality. The GM also defines the synchronization domain, and multiple domains can coexist in the same network, each with its own GM, to support different applications with different synchronization requirements.

In 5G and TSN deployments, the GM is often located at the network edge or in a centralized location, and its time is distributed through a combination of PTP and 5G synchronization mechanisms. The 3GPP has defined how the 5G System can propagate time synchronization from a GM to User Equipment (UE) and to TSN endpoints, enabling end-to-end deterministic communication. The accuracy of the GM directly affects the performance of time-sensitive applications, making the GM a critical component of the network infrastructure.

Purpose & Motivation

The Grand Master exists to provide a single, authoritative time reference for a synchronization domain. Without a common time reference, distributed systems cannot coordinate their operations — for example, TSN endpoints cannot schedule time-sensitive traffic, and 5G base stations cannot align their TDD frames. The GM solves this by serving as the root of a hierarchical synchronization tree, ensuring that all clocks in the domain are traceable to the same time source.

Historically, time synchronization was provided by dedicated synchronization networks (e.g., SDH/SONET synchronization chains) or by GNSS receivers at each node. These approaches were costly and inflexible. The introduction of PTP (IEEE 1588) and gPTP (IEEE 802.1AS) enabled time synchronization over packet networks, and the GM concept became central to these protocols. The BMCA allows automatic GM selection, improving resilience and reducing operational complexity.

In 3GPP networks, the need for a GM became more pronounced with the advent of 5G and TSN. 5G features such as TDD, coordinated multipoint, and URLLC require tight time synchronization, and TSN integration requires the 5G System to participate in a TSN synchronization domain with a GM. The 3GPP specifications in Releases 8, 9, 16, 19, and 20 address these requirements, defining how the GM time is distributed and how the 5G System can act as a TSN bridge or endpoint. The GM thus enables the convergence of 5G with industrial and time-sensitive networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define GM. Each summary describes the whole specification, not only this term.

TS 23.255Rel-18 → Rel-19

Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.

Full comparison in TS 23.255 →

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.

Rel-8 Initial

Initial introduction of the Grand Master concept in the context of 3GPP synchronization and application layer support, defining the GM as the authoritative time source for synchronization domains.

The term carried over unchanged in its core definition; Release 9 continued to reference the GM within the synchronization framework without redefining the concept itself.

The term carried over unchanged in its core definition; Release 16 expanded the role of the GM in the context of TSN integration and 5G synchronization, as studied in 38.825, without redefining the GM itself.

The term carried over unchanged in its core definition; Release 19 continued to reference the GM within the evolving synchronization and deterministic networking framework.

The term carried over unchanged in its core definition; Release 20 continued to reference the GM within the synchronization and time-sensitive networking context.

Defining Specifications

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

SpecificationTitleRelease
TS 23.255 vk10 UAS Application Enabler Architecture Rel-20 read
TS 29.199 3GPP TS 29.199 Rel-8 read
TR 38.825 vg00 Study on NR Industrial IoT Rel-16 read