DFN

Direct Frame Number

Radio Access Network →
Introduced in Rel-12

DFN is a frame numbering mechanism used in LTE and 5G NR sidelink to provide a common time reference for Device-to-Device and Vehicle-to-Everything communications, enabling synchronization without continuous network coverage.

Category
Radio Access Network
Introduced
Rel-12
Where
Radio Access Network › NG-RAN (5G)
Specifications
3 specs
DFN Description Purpose Detected Changes Specifications

Description

Direct Frame Number (DFN) is a critical timing reference mechanism specified in 3GPP standards for sidelink communications, primarily documented in TS 36.331 (LTE) and TS 38.331/38.355 (5G NR). DFN operates as an independent frame numbering system that provides a common time reference for devices engaged in direct communication outside the traditional uplink/downlink framework. Unlike the System Frame Number (SFN) used in cellular communications between base stations and UEs, DFN is specifically designed for Device-to-Device (D2D) scenarios where devices need to coordinate directly with each other.

The DFN architecture operates within the sidelink interface, which is a direct radio link between user equipment without traversing network infrastructure. Each device maintains its own DFN counter that increments with each radio frame, typically spanning 10 milliseconds. The DFN value ranges from 0 to 1023 in LTE and is extended in 5G NR to accommodate more complex synchronization scenarios. Devices synchronize their DFN counters through synchronization signals transmitted by synchronization reference sources, which can be eNBs/gNBs, Global Navigation Satellite System (GNSS) timing, or other UEs acting as synchronization sources.

Key components of the DFN system include the DFN counter itself, synchronization signal blocks (SSBs) for timing reference distribution, and resource allocation mechanisms that use DFN as a timing anchor. In operation, devices use DFN to determine when to transmit and receive sidelink channels including Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Broadcast Channel (PSBCH). The DFN value helps devices identify specific subframes or slots allocated for sidelink communication within the overall frame structure.

DFN plays a crucial role in resource allocation for sidelink communications through mechanisms like Mode 2 resource allocation in LTE and NR sidelink. Devices use DFN-based timing to implement sensing procedures, where they monitor resources over multiple DFN cycles to identify available transmission opportunities. The DFN provides the temporal framework for resource reservation intervals, where devices can reserve resources for future transmissions by indicating the DFN offset between reservation and actual transmission. This enables efficient resource utilization and minimizes collisions in distributed scheduling environments.

In advanced implementations, particularly for 5G NR V2X, DFN supports enhanced synchronization accuracy requirements for high-speed vehicle communications. The system incorporates mechanisms for DFN adjustment and maintenance during mobility scenarios, including handovers between different synchronization sources. DFN also interfaces with higher-layer protocols for sidelink discovery, communication, and broadcast services, providing the fundamental timing foundation that enables reliable direct communication between devices in both in-coverage and out-of-coverage scenarios.

Purpose & Motivation

DFN was created to address the fundamental challenge of establishing a common time reference for direct device-to-device communications in LTE and 5G networks. Prior to DFN implementation, cellular systems relied exclusively on base station timing (SFN) for all communications, which prevented reliable direct communication between devices without continuous network coverage. This limitation was particularly problematic for public safety scenarios where first responders need to communicate directly during network outages or in remote areas without cellular infrastructure.

The development of DFN was motivated by the growing need for proximity-based services and the emergence of V2X communications requirements. Traditional cellular timing mechanisms were insufficient for sidelink operations because they required devices to maintain synchronization with potentially distant base stations, which was impractical for direct communications between nearby devices. DFN provided an independent timing framework that could be maintained through various synchronization sources including GNSS, other UEs, or residual network timing, enabling robust direct communications even in challenging environments.

DFN solves several critical problems in modern wireless systems: it enables efficient resource allocation for sidelink communications by providing a common temporal reference for distributed scheduling algorithms; it supports synchronization in out-of-coverage scenarios where traditional cellular timing is unavailable; and it facilitates advanced V2X applications requiring precise timing coordination between high-speed vehicles. By decoupling sidelink timing from cellular network timing, DFN enables the coexistence of traditional cellular communications and direct device communications within the same spectrum, maximizing spectral efficiency while supporting diverse communication paradigms.

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-12, normative work from Rel-15.

Rel-15 7 changes

In Release 15, the DFN (Direct Frame Number) function was not explicitly mentioned in the provided grounding context or change request titles. The listed CRs and specification excerpts focus on other areas such as corrections for EN-DC, system information scheduling based on SFN, and uplink TX direct current reporting, but do not contain technical details describing a newly introduced DFN function. Therefore, based solely on the provided materials, no specific new introduction for DFN can be described.

  • Introduction of increased number of E-UTRAN data bearers TS 36.331CR3446
  • CR to direct current report for UL and SUL TS 38.331CR1013
  • Correction on measurement triggering based on number of cells TS 36.331CR3657
  • Corrections for EN-DC (Note: the clause numbering between 15.0.0 and 15.1.0 has changed in some cases). TS 38.331CR0008
  • Corrections on number of RadioLinkMonitoringRS condifuration TS 38.331CR0587
  • CR on the number of bits of downlink NAS COUNT value TS 38.331CR0913

+ 1 more changes

Rel-16 4 changes

In Release 16, the enhancements for the Direct Frame Number (DFN) function specifically addressed scheduling for NB-IoT in TDD mode, ensuring system information transmission robustness. The specification introduced defined handling for when the first SI message transmission or its repetitions would fall on invalid non-downlink subframes, mandating a postponement to the next valid downlink subframe within the SI-window. This change provided clearer rules for direct scheduling alignment in discontinuous coverage scenarios for IoT NTN operations.

  • Configuration for directional collision handling between reference cell and other cell for half-duplex operation in CA TS 38.331CR2017
  • Correction to 36.331 on UE capability of direct SCell activation TS 36.331CR4456
  • Extending number of cells for search space switching trigger configuration TS 38.331CR2702
  • Corrections on the number of DRBs TS 36.331CR4321
Rel-17 4 changes

In Release 17, the new feature for the DFN (Direct Frame Number) function is not explicitly detailed in the provided grounding context. The listed Change Requests primarily concern other areas, such as removing MIMO layer restrictions for SUL and corrections to the unified TCI framework. Therefore, based solely on the given materials, no specific technical update to the DFN function itself can be described.

  • Remove the maximum number of MIMO layers restrictions for SUL TS 38.331CR2465
  • Addition of extended number range for NS value TS 36.331CR4917
  • Corrections on R17 unified TCI framework TS 38.331CR4100
  • Addition of extended number range for NS value TS 38.331CR3900
Rel-18 11 changes

In Release 18, the DFN function itself is not mentioned in the provided grounding context or Change Request titles. The listed corrections and introductions for this release focus on other areas, including uplink power control within the unified TCI framework, network signaling for the maximum number of UL segments, and corrections to parameters for random access reports and NZP CSI-RS resources.

  • Correction on the maximum number of SSB rsources for L1 measurement without gaps in LTM TS 38.331CR5302
  • Correction to startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition in RA-report TS 38.331CR5456
  • Missing rate of change direction of azimuth/elevation for relative velocity TS 38.355CR0015
  • Introduction of network signalling of maximum number of UL segments [Max-RRC-SegUL] TS 36.331CR5084
  • Corrections on network signalling of maximum number of UL segments [Max-RRC-SegUL] TS 36.331CR5089
  • Corrections on uplink power control in unified TCI framework TS 38.331CR4559

+ 5 more changes

Explore further

Broader topics and technologies where DFN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19
TS 38.331 vj00 NR Radio Resource Control (RRC) Protocol Specification Rel-19
TS 38.355 vj00 Sidelink Positioning Protocol (SLPP) Rel-19