Cross-Domain and Iterative Detection
Why Integrate Detection With Decoding
The detectors of Sections 2-4 output hard or soft estimates of data symbols. In practice, a channel code (LDPC or Turbo in 5G NR) sits on top of these symbols. Iterative detection and decoding (IDD) loops information between the detector and the decoder: each pass refines the other. For OTFS, this structure yields the full ML performance at LCD-like complexity.
The point is that the detector provides symbol-level LLRs (log-likelihood ratios) to the decoder, which outputs extrinsic LLRs that the detector uses as priors in the next iteration. A handful of outer iterations is typically sufficient. The combined scheme is the standard operating point of 5G NR modems — and it ports directly to OTFS.
Definition: Iterative Detection and Decoding Loop
Iterative Detection and Decoding Loop
The IDD loop for OTFS:
- Detection pass: detector produces soft LLRs for each bit of each symbol, given received and the channel estimate.
- Decoding pass: channel decoder (LDPC/Turbo) processes the LLRs and produces extrinsic LLRs (information from the decoder about each bit, excluding the detector's input).
- Feedback: the detector uses as a prior for the next iteration.
- Stopping: loop until convergence (LLRs stable) or hit a maximum iteration count (– typically).
The final output is the decoded bits after the last decoding pass.
Theorem: The Turbo Principle Applied to OTFS
Let the detector produce LLRs and the decoder produce extrinsic LLRs per bit. Under mild regularity conditions (independent errors after detection, detector-decoder mutual information separation), the iterative scheme converges to a fixed point whose BER matches that of the joint ML detector-decoder within an -neighborhood — where shrinks exponentially in the iteration count.
EXIT chart analysis predicts convergence: plot the extrinsic-to- intrinsic-mutual-information transfer of each block; the iterated scheme converges iff the detector curve lies above the decoder curve in the relevant region.
The turbo principle is the standard iterative decoding framework from the late 1990s (turbo codes, iterative LDPC decoding). It applies directly to OTFS because the detector-decoder split is analogous to the turbo encoder-interleaver-decoder structure. The DD-domain detector is just one of the component decoders in a turbo-like loop.
EXIT analysis
Let denote the mutual information between the decoder's extrinsic LLR and the true bit. Let be the detector's extrinsic LLR information given input . Convergence requires for all .
OTFS-specific EXIT
The OTFS detector's curve is determined by the channel sparsity and SNR. At high SNR, it is close to 1 for (detector can resolve most symbols from noise). At low SNR, the curve sags, and convergence requires outer coding to lift above the detector's floor.
Practical convergence
In typical OTFS with LDPC outer coding, convergence is 2-3 iterations. Beyond that, diminishing returns.
BER achievability
At convergence, the BER is within 0.5 dB of the joint ML scheme for well-designed EXIT profiles. This is the operational OTFS receiver.
Key Takeaway
IDD closes the ML gap at linear complexity. LDPC + LCD with iterative feedback achieves BER within 0.5 dB of ML at complexity . For the 5G NR physical layer with , this is ops per frame — well within realtime budgets. The full OTFS receiver (CP removal, Wigner, SFFT, IDD) is a -ops-per-frame system, deployable on standard silicon.
OTFS Iterative Detection-Decoding (IDD)
Complexity:The inner LDPC decoder itself runs for several iterations (5-10) per outer pass. Total inner-loop complexity: ops per pass for standard 5G NR code rates. Over passes, the total is ops.
IDD vs Non-Iterative: Coded BER Comparison
Compare BER curves for (a) non-iterative: LCD + LDPC, and (b) iterative: LCD + LDPC with 3 outer iterations. At low SNR, IDD shows – dB gain; at high SNR, the gap closes as both reach the error floor. This illustrates the turbo-principle gain for OTFS.
Parameters
Definition: Cross-Domain Detection
Cross-Domain Detection
Cross-domain detection leverages complementary information from the TF and DD domains simultaneously. The receiver computes detection results in both domains and combines them:
- TF-domain detection: apply OFDM-like per-subcarrier MMSE on the TF grid. Accurate when is large; poor when it is small.
- DD-domain detection: apply LCD or MP on the DD grid. Accurate when the channel sparsity is effectively exploited.
- Fusion: combine TF and DD LLRs as weighted sum, with weights proportional to per-cell reliability.
The cross-domain fusion is a generalization of the iterative scheme: it lets each domain compensate for the other's weaknesses (TF handles well-conditioned cells; DD handles multipath-averaged cells).
When Cross-Domain Matters
Pure TF and pure DD detection have complementary failure modes:
- TF fails at deep fades where is small.
- DD fails at low SNR where the MP-OTFS algorithm has trouble distinguishing paths from noise.
Cross-domain detection wins when:
- The channel has both multipath (favoring DD) and deep fades (hurting both — cross-domain LLR averaging helps).
- The SNR is variable across cells (TF diversity + DD sparsity both needed).
In practice, pure LCD or MP with IDD outperforms cross-domain fusion for most deployment scenarios. Cross-domain is a research topic for rich-scattering environments (e.g., indoor mmWave) where the DD sparsity is less pronounced.
Complete OTFS Receiver Compute Budget
A complete OTFS receiver (5G NR-aligned, , ):
- CP removal + Wigner (OFDM demod): ops.
- SFFT: ops.
- Channel estimation (Chapter 7): ops.
- LCD detection (3 iter): ops.
- IDD feedback to LDPC (3 iter): ops.
- Total: ops per frame.
At 100 frames/sec, this is ops/sec — easily handled by an OFDM-class modem silicon. The implementation is primarily 2D FFTs and element-wise operations; no exotic hardware required.
This confirms the deployment argument: OTFS can run on existing 5G modem silicon with firmware changes only.
- •
Per-frame: ops
- •
Per-second (100 frames/s): ops — modest
- •
Implementable in software on existing OFDM modems
Distributed Message Passing for Cell-Free OTFS
The MP-OTFS detector of Raviteja-Viterbo (2018) was originally a single-link algorithm. The CommIT extension — developed by Mohammadi, Ngo, Matthaiou, and Caire for cell-free massive MIMO — is distributed MP-OTFS: the message-passing algorithm runs partly at the distributed access points (near the observations) and partly at the central processing unit (for global consensus across multiple APs and UEs).
The key insight is that the DD factor graph generalizes naturally to multi-AP scenarios: each AP contributes its own set of factor nodes representing its local DD observations, and the CPU aggregates beliefs via a global message-passing step. Per-AP computation is (same as single-link); CPU aggregation is for APs. Total: — linear in the system scale.
This distributed MP framework is the receiver-side half of the cell-free OTFS contribution; the pilot-design half (superimposed pilots) is in Chapter 7. Together they deliver the 25-35% throughput gain over OFDM cell-free at vehicular mobility. Full treatment is in Chapter 17.
Why This Matters: Diversity Analysis Makes This Rigorous
The claim that MP and LCD achieve "full diversity " is made rigorous in Chapter 9. There, Surabhi-Chockalingam show that the pairwise error probability of any ML-like detector in OTFS decays as , where equals the product of resolvable delay and Doppler bins occupied by the channel. For an integer- Doppler channel with distinct pairs, — matching the MP / LCD performance claims. The diversity-order result is the information-theoretic justification of the detectors in this chapter.