STTI

Short Transmission Time Interval

Physical Layer →
Introduced in Rel-15

STTI is a reduced-duration Transmission Time Interval in LTE that shortens the basic scheduling unit to enable faster link adaptation and data transmission for low-latency services like URLLC.

Category
Physical Layer
Introduced
Rel-15
Where
User Equipment
Specifications
2 specs
STTI Description Purpose Related Classification Detected Changes Specifications

Description

Short Transmission Time Interval (sTTI) is a feature introduced in LTE to reduce user-plane latency by defining Transmission Time Intervals shorter than the legacy 1 ms subframe. The Transmission Time Interval is the minimum time unit over which a user can be scheduled for data transmission and is tied to the timing of Hybrid Automatic Repeat Request (HARQ) processes. The legacy LTE TTI is one subframe (1 ms, consisting of two 0.5 ms slots). sTTI reduces this to durations such as 2-symbol (approximately 0.143 ms), 1-slot (0.5 ms), or a 7-symbol configuration, depending on the subcarrier spacing and deployment scenario.

Architecturally, sTTI impacts multiple layers of the LTE protocol stack. At the physical layer, it requires new channel structures for data (sPDSCH, sPUSCH) and control (sPDCCH). These channels are mapped to the shortened time resources within a subframe. The reduced TTI length necessitates faster processing timelines for both the UE and the eNodeB. This includes faster channel coding/decoding, faster generation and reception of uplink control information (UCI) and downlink control information (DCI), and significantly reduced HARQ round-trip time (RTT). The HARQ process timeline is compressed, allowing for acknowledgment feedback (ACK/NACK) to be received much sooner after a transmission.

How it works involves dynamic or semi-static configuration by the network. The eNodeB can configure a UE for sTTI operation based on its service requirements (e.g., for URLLC). When scheduled using an sTTI, the UE transmits or receives data over the shortened duration. The associated control information, which schedules this data, is also transmitted within a similarly shortened sPDCCH. This tight coupling of scheduling and data transmission within a very short window is key to achieving low latency. sTTI operation can be multiplexed with legacy UEs using normal 1 ms TTIs within the same carrier through careful resource allocation in the time-frequency grid.

Purpose & Motivation

sTTI was created to address the stringent latency requirements for new use cases like industrial automation, vehicle-to-everything (V2X) communication, and real-time gaming, which emerged with the roadmap towards 5G. Legacy LTE's 1 ms TTI and associated HARQ timing resulted in a minimum theoretical user-plane latency of around 10 ms, which was insufficient for services requiring latencies of 1 ms or less. sTTI was a key LTE evolution feature to bridge this performance gap before the full deployment of 5G NR.

It solved the fundamental scheduling granularity bottleneck. A shorter TTI allows data packets to be transmitted, acknowledged, and potentially retransmitted in a much shorter total time. This directly reduces radio interface latency. Furthermore, it enables faster link adaptation because the channel quality can be measured and the modulation and coding scheme (MCS) updated more frequently, improving reliability for bursty transmissions. sTTI was a critical component in enabling LTE to support the Ultra-Reliable Low Latency Communication (URLLC) service class defined by 3GPP.

The motivation was driven by industry demand for pre-5G low-latency solutions. It allowed network operators to upgrade existing LTE infrastructure to support latency-critical applications without waiting for a full 5G NR rollout. Its introduction in Rel-15 (as part of the LTE evolution for 5G) positioned LTE as a complementary radio access technology to NR, capable of supporting a wide range of 5G use cases.

Classification

Part ofTTI
Related approachesURLLC

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-15 24 changes

In Release 15, the Short Transmission Time Interval (sTTI) function was introduced for LTE, including UE capability reporting for short TTI and corrections to sTTI-specific parameters and procedures. The release also introduced Semi-Persistent Scheduling (SPS) for TDD sTTI and made clarifications for HARQ-ACK feedback configurations related to sTTI. Furthermore, it defined support for skipUplinkTxSPS for short TTI and included various corrections to ensure proper sTTI operation.

  • Introduction of shortened TTI and processing time for LTE TS 36.306CR1542
  • Introduction of shortened TTI and processing time for LTE TS 36.331CR3202
  • UE capabilities for short TTI TS 36.306CR1644
  • Make additional SIB transmission an optional feature with capability reporting TS 36.306CR1636
  • Various sTTI corrections TS 36.306CR1659
  • Corrections to sTTI-SPT band parameters capabilities TS 36.306CR1692

+ 18 more changes

Rel-16 6 changes

In Release 16, the STTI function was enhanced with clarifications and corrections to existing capabilities. Specifically, the release provided a clarification on the **codebook-HARQ-ACK-r13 capability for CA with more than 5CCs**, mandating support for DAI-based and configured-CCs-based HARQ ACK codebook size determination. Additionally, it included corrections to the **AUL HARQ process** and addressed the transmission of specific signaling messages like **InDeviceCoexistence** and **UEAssistanceInformation** after conditional handover.

  • Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability TS 36.306CR1803
  • Dummifying intraFreqMultiUL-TransmissionDAPS-r16 capability TS 36.331CR4562
  • Transmission of InDeviceCoexistence, UEAssistanceInformation, MBMSInterestIndication, or SidelinkUEInformation after conditional handover TS 36.331CR4644
  • Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs TS 36.306CR1750
  • Addition of missing NZP CSI-RS transmission capabilities TS 36.306CR1801
  • Correction of AUL HARQ process TS 36.331CR4343
Rel-17 1 change

In Release 17, the specification introduced new UE capability fields for sidelink communication and V2X, defining specific SL-C-RX and SL-C-TX categories that UEs must support. This release also included a correction for the transmission of SSR assistance data based on the BDS B1C signal. Furthermore, it added clarifications and requirements for various existing capabilities, such as those related to PUCCH on SCell and HARQ codebook determination.

  • Correction on transmission of SSR Assistance Data based on BDS B1C TS 36.331CR4979
Rel-18 1 change

In Release 18, the STTI function introduced specific enhancements for IoT Non-Terrestrial Networks (NTN), including corrections to UE capabilities for GNSS and Hybrid Automatic Repeat Request (HARQ). These updates were defined within the UE radio transmission and reception specifications to improve performance in satellite access scenarios.

  • IoT NTN UE capabilities correction for GNSS and HARQ enhancements TS 36.306CR1902

Explore further

Broader topics and technologies where STTI plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 36.306 vj00 E-UTRA UE Radio Access Capability Parameters Rel-19
TS 36.331 vj00 LTE RRC Protocol Specification Rel-19