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

Glossary term · Core Network

TDR

Time Dependent Routing

Core Network →

TDR is a 3GPP routing mechanism that selects network destinations based on time-of-day and date conditions, enabling operators to steer traffic dynamically according to schedules, tariffs, or load patterns.

Introduced
Rel-8
Where
Core Network › 5G Core
Specifications
2 specs
TDR Description Purpose What changed Neighbours Specifications

Description

Time Dependent Routing (TDR) is a routing capability in which the selection of a destination — such as a gateway, server, or network node — depends on the current time and date rather than solely on static configuration. In 3GPP specifications, TDR appears in the context of management and routing configuration, notably in TS 32.808 (which addresses, among other things, routing configuration management) and in TS 24.193, which covers the Access Network Discovery and Selection Function (ANDSF) and related traffic steering mechanisms. The underlying idea is that network operators frequently need traffic to follow different paths at different times: for example, routing calls or data through a particular interconnect or gateway during business hours and through another during off-peak periods, or applying different routing policies on weekends and holidays.

Operationally, TDR works by associating routing rules with time conditions. A routing configuration contains a set of rules, each combining a destination (or set of candidate destinations) with a schedule — time ranges, days of the week, and calendar dates. When a routing decision must be made, the network element evaluates the current time against the configured schedules and selects the matching rule. This can be used for load balancing across time zones, for tariff-driven routing where different carriers offer different rates at different times, or for maintenance windows during which traffic is diverted away from nodes being upgraded.

In the management domain, TDR is closely related to the configuration of routing tables and policies that network management systems push to network elements. TS 32.808 provides the framework for managing such routing configurations, including the ability to define time-dependent entries and to activate or deactivate them according to schedules. This allows operators to automate what would otherwise be manual reconfiguration at specific times, reducing operational errors and enabling consistent policy enforcement across many nodes.

In the ANDSF context (TS 24.193), time-dependent aspects appear in the policies that guide user equipment in selecting access networks and routing traffic. While ANDSF itself is primarily about access network discovery and inter-system mobility, the policies it delivers can include validity conditions, and the general concept of time-conditioned routing policies is part of the broader traffic steering toolkit. TDR thus spans both the core/management plane, where it governs node-to-node routing, and the policy plane, where it can influence how traffic is steered.

TDR matters because static routing cannot adapt to the temporal patterns inherent in real networks: peak versus off-peak load, scheduled maintenance, time-zone-dependent traffic distribution, and commercial arrangements that vary by time. By making routing decisions time-aware, TDR improves resource utilization, supports differentiated commercial offerings, and enables automated, policy-driven network operations.

Purpose & Motivation

TDR exists to solve the problem that network routing requirements are rarely constant over time. Operators need to shift traffic between interconnects, gateways, or servers according to peak and off-peak load, scheduled maintenance windows, time-zone differences across a multi-region network, and commercial agreements that specify different rates or capacities at different times of day. Static routing tables cannot express these temporal policies, forcing operators to manually reconfigure nodes at specific times — an error-prone and labor-intensive process.

By introducing time conditions into routing rules, TDR allows routing behavior to be defined declaratively and enforced automatically. This reduces operational overhead, ensures that time-based policies are applied consistently across many network elements, and lowers the risk of human error during critical transitions such as maintenance cutovers. It also supports tariff-driven and load-driven routing strategies that can yield cost savings and better performance.

In 3GPP, TDR is embedded in the management and policy frameworks (notably TS 32.808 and TS 24.193) so that routing configurations can be provisioned, scheduled, and audited through standardized interfaces. This standardization ensures multi-vendor interoperability and gives operators a common model for expressing time-dependent routing across heterogeneous networks.

What changed in its specifications

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

TS 24.193Rel-18 → Rel-19

Rel-19 adds MPQUIC-IP and MPQUIC-E steering, an ATSSS status parameter, non-3GPP access path switching, and ATSSS rule provisioning with MPQUIC-IP signalling over EPC-connected 3GPP access.

Full comparison in TS 24.193 →

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 specification of Time Dependent Routing concepts within 3GPP management and policy frameworks, providing the basic model of routing rules associated with time schedules.

The term carried over unchanged; the definition text was not revised in this release.

The term carried over unchanged; the definition text was not revised in this release.

The term carried over unchanged; the definition text was not revised in this release.

Defining Specifications

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

SpecificationTitleRelease
TS 24.193 vk10 ATSSS Stage 3 Procedures Rel-20 read
TS 32.808 v800 Common Profile Storage Framework for User Data Rel-8 read