Non-time Reference Cell

Description

The non-time reference cell is a concept introduced in 3GPP Release 11 in the context of HSDPA Multiflow (also known as Multiflow HSDPA or MF-HSDPA) as specified in TS 25.211 and TS 25.214. In Multiflow operation, a UE simultaneously receives HS-DSCH (High-Speed Downlink Shared Channel) transmissions from two cells: the Serving HS-DSCH cell and the Assisting Serving HS-DSCH cell. These two cells can be geographically separated, resulting in different propagation delays and potentially asynchronous timing. To manage this, 3GPP defines one of the two cells as the time reference cell and the other as the non-time reference cell.

The time reference cell provides the timing reference for the UE's HS-DSCH reception. All uplink HS-DPCCH (High-Speed Dedicated Physical Control Channel) feedback and downlink scheduling timing is aligned to this cell. The non-time reference cell, by contrast, has a different timing than the time reference cell, so the UE must apply a timing offset to correctly receive, demodulate, and combine HS-DSCH transmissions from both cells. The assignment of which cell is the time reference is network-controlled: if the time reference cell is the Assisting Serving HS-DSCH cell, then the non-time reference cell is the Serving HS-DSCH cell, and vice versa. This flexibility lets operators choose the timing that is most robust or aligned with uplink transmissions.

In Multiflow mode, the two cells may belong to the same NodeB (intra-NodeB, synchronous) or to different NodeBs (inter-NodeB, potentially asynchronous). The non-time reference cell is especially important in inter-NodeB scenarios, where propagation delays can differ significantly. The UE needs to maintain separate receive timing for the non-time reference cell, and the network must coordinate scheduling and HARQ (Hybrid Automatic Repeat Request) processes across both cells to avoid collisions and to ensure that acknowledgements are correctly mapped. The HS-DPCCH timing is anchored to the time reference cell, so the UE's feedback for the non-time reference cell must be adjusted accordingly.

From a performance perspective, Multiflow HSDPA with a non-time reference cell provides macro diversity gain at the downlink: a UE at the cell edge can receive independent data streams from two cells, increasing throughput and reliability. The non-time reference cell's timing offset does not prevent coherent combining because HSDPA uses separate HARQ processes per cell; rather, the two streams are decoded separately but combined at the higher layer or via coordinated scheduling. This is distinct from soft handover in Release 99, where the same data is transmitted from multiple cells — Multiflow transmits different data from each cell.

The concept is tied to the physical layer specifications TS 25.211 (Physical channels and mapping of transport channels onto physical channels) and TS 25.214 (Physical layer procedures). These define the timing relationships, the HS-DPCCH feedback, and the UE procedures for handling cells with different timing. Over subsequent releases, Multiflow and the non-time reference cell concept remained stable and were carried forward with only editorial changes. In later releases with the introduction of further enhancements such as 4C-HSDPA and 8C-HSDPA, timing reference concepts remained central, though the specific non-time reference cell definition as used for Multiflow retained its original scope.

Purpose & Motivation

The non-time reference cell concept exists to solve a fundamental problem in Multiflow HSDPA: how to let a UE receive high-speed downlink data from two cells that are not synchronised to each other. In earlier HSDPA releases, a UE could only receive HS-DSCH from a single Serving HS-DSCH cell, which limited cell-edge throughput. Soft handover allowed multiple cells to transmit the same data in the downlink, but HSDPA did not initially support simultaneous reception from multiple cells with different data. Multiflow changed that by enabling two-cell HS-DSCH reception, but it introduced the challenge of differing timing between the two cells.

The purpose of designating one cell as the time reference and the other as the non-time reference is to provide a single, unambiguous timing anchor for the UE's control channels and feedback. Without this anchor, the UE would not know which cell's timing to use for HS-DPCCH transmission, HARQ feedback, and scheduling grants. The non-time reference cell is then explicitly treated as having a timing offset relative to the time reference, so the UE can apply the appropriate receive processing and feedback timing adjustments.

Historically, Multiflow was motivated by the need to improve cell-edge user experience in HSPA networks, which were still widely deployed when Release 11 was being developed. With the rise of LTE, HSPA operators sought cost-effective upgrades to remain competitive. Multiflow provided a way to boost peak and cell-edge throughput without new spectrum, and the time reference/non-time reference framework was essential to make that feature work in realistic, non-synchronised deployments.