Reference Plane / Episode 1

HARQ in non-terrestrial links

Watch the ACK/NACK pipeline. Stretch the link. See where it stalls.

LEO 1200 km · RTT 8 ms BLER 10%
gNB UE UPLINK UE → gNB DOWNLINK gNB → UE t=0 τ UE WAITING
Scenario controls

Link scenario

Block error rate (BLER)

10%

HARQ processes

HARQ process bank

UE-side process IDs, one TB each

in flight awaiting ACK NACK, retx

Each cell is one HARQ process. A TB occupies it from first transmission until ACK or max retx.

Event log

UE perspective, last events first

Pipeline utilization

Fraction of Shannon limit achieved

100%

N · t_slot / RTT = 1.000

Pipe depth needed

4 processes

One slot = 1 ms. To keep the link full, processes must equal or exceed RTT in slots.

Session totals

TBs transmitted

0

ACKs received

0

NACKs / retx

0

Stall slots

0

How the protocol works

The UE sends a transport block (TB) on a free HARQ process. The block flies up for one one-way delay (τ). The gNB decodes, then sends an ACK if the CRC passes, or a NACK if it fails. The feedback flies back for another τ, so the UE learns the outcome 2τ after first transmission. While waiting, the UE can use other HARQ processes to keep sending. If N processes × slot time is shorter than the round-trip, the UE runs out of free processes and the link sits idle. That is the NTN HARQ stall.