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

Glossary term · Radio Access Network

Unsynchronized operation

Unsynchronized Operation

Radio Access Network →

Unsynchronized operation is the condition where TDD systems in separate networks operate without meeting the synchronization requirements, allowing coexistence without strict frame coordination but risking interference.

Introduced
Rel-10
Where
Radio Access Network › Multi-RAT
Specifications
10 specs
Unsynchronized operation Description Purpose What changed Neighbours Specifications

Description

Unsynchronized operation is a mode of TDD (Time Division Duplex) operation defined in 3GPP specifications for radio access networks, including UTRAN TDD (TS 25.105, TS 25.142), E-UTRA TDD (TS 36.101, TS 36.104, TS 36.141), and NR TDD (TS 37.104, TS 37.105, TS 37.141, TS 37.145, TS 37.812). It describes the situation where two different TDD systems operate in the same or adjacent frequency bands but do not meet the conditions required for synchronized operation. In synchronized operation, base stations align their frame timing and DL/UL switching points to avoid cross-link interference. In unsynchronized operation, such alignment is absent, so one system may be transmitting downlink while the other is receiving uplink, causing interference.

The primary technical challenge addressed by unsynchronized operation is coexistence between TDD networks that are not under common control. This can occur when different operators deploy TDD networks in adjacent bands, or when a single operator runs multiple TDD systems with independent timing. Because TDD uses the same frequency for both downlink and uplink, separated in time, any misalignment of the DL/UL pattern creates cross-link interference: a base station's downlink transmission can overwhelm a nearby base station's uplink reception, and vice versa. Unsynchronized operation acknowledges this reality and defines the conditions and requirements under which such deployments can still function.

3GPP specifications define the conditions for synchronized operation — for example, common frame timing, aligned DL/UL configurations, and coordinated switching points. When these conditions are not met, the systems are in unsynchronized operation. The specifications then provide coexistence requirements, such as adjacent channel leakage ratio (ACLR) limits, blocking characteristics, and minimum coupling loss assumptions, to ensure that interference remains within acceptable bounds. These requirements are captured in the radio transmission and reception specifications (e.g., TS 36.104, TS 37.104) and in coexistence studies (e.g., TS 37.812).

In practice, unsynchronized operation is relevant to spectrum sharing, uncoordinated deployments, and scenarios where operators cannot or do not coordinate their TDD networks. It is also a consideration for NR TDD deployments in shared spectrum and for coexistence between LTE TDD and NR TDD. The specifications provide test cases and measurement procedures (e.g., TS 36.141, TS 37.141, TS 37.145) to verify that equipment meets the required performance under unsynchronized conditions.

For engineers, unsynchronized operation is a key concept in radio planning and interference management. It highlights the trade-off between deployment flexibility and spectral efficiency: synchronized operation enables tighter reuse and better performance but requires coordination, while unsynchronized operation allows independent deployment but demands more conservative RF design and guard bands. Understanding these conditions is essential for designing and operating TDD networks in multi-operator and multi-technology environments.

Purpose & Motivation

Unsynchronized operation exists to define and manage the reality that not all TDD networks can be synchronized. TDD systems rely on precise timing alignment to avoid cross-link interference, but in practice, different operators, different technologies (e.g., LTE and NR), or different administrative domains may operate independently. Requiring global synchronization is often impractical or impossible, especially in shared or adjacent spectrum. The concept was introduced to provide a formal framework for coexistence when synchronization conditions are not met.

Before this concept was formalized, coexistence between unsynchronized TDD systems was handled ad hoc, leading to unpredictable interference and unclear equipment requirements. By defining the conditions for synchronized operation and specifying requirements for unsynchronized operation, 3GPP gave equipment vendors and operators a clear basis for design, testing, and deployment. This reduced the risk of harmful interference and enabled regulators to set realistic coexistence rules.

The concept also supports spectrum policy. Regulators can allow unsynchronized TDD deployments in adjacent bands if equipment meets defined coexistence requirements, promoting competition and efficient spectrum use. As TDD became dominant in 5G NR, especially in mid-band spectrum, unsynchronized operation grew in importance, driving ongoing work in 3GPP on coexistence studies and RF requirements.

What changed in its specifications

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

TS 25.105Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.105: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.105 →
TS 25.142Rel-10 → Rel-11

Added MB-MSR multi-band/multi-carrier RF requirements and test configurations; updated E-UTRA and MSR medium range/local area BS class requirements; added eight-carrier HSDPA multi-carrier transmission statements and terms; added new TDD 1.28Mcps multiple-cell demodulation test terms.

Full comparison in TS 25.142 →

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-10 Initial

Initial definition introduced: 'Operation of TDD in two different systems, where the conditions for synchronized operation are not met.' Release 10 marked the first formal definition of the term in 3GPP specifications, coinciding with the maturation of LTE TDD and the need for coexistence rules.

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

The definition text was reworded slightly for formatting, but the technical meaning remained identical: 'Operation of TDD in two different systems, where the conditions for synchronized operation are not met.'

The definition text carried over unchanged from Release 10.

The definition text carried over unchanged from Release 10.

Defining Specifications

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

SpecificationTitleRelease
TS 25.105 vj00 UTRA TDD Base Station RF Requirements Rel-19 read
TS 25.142 vj00 UTRA TDD Base Station RF Test Methods Rel-19 read
TS 36.101 vk10 E-UTRA UE RF Requirements Rel-20 read
TS 36.104 vj20 E-UTRA/NB-IoT Base Station RF Requirements Rel-19 read
TS 36.141 vj10 RF Test Methods for LTE and NB-IoT Base Stations Rel-19 read
TS 37.104 vj40 NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio Rel-19 read
TS 37.105 vj40 AAS Base Station Radio Requirements Rel-19 read
TS 37.141 vj40 RF Test Methods and Conformance for Multi-Standard Radio Base Stations Rel-19 read
TS 37.145 vj40 AAS Base Station Radiated Requirements Rel-19 read
TS 37.812 vb30 Multi-band Multi-standard Radio BS Requirements Rel-11 read