Definition and Motivation
What Transform Do We Need?
Chapter 1 told us the channel lives naturally in the delay-Doppler plane. It did not tell us how to map an ordinary time-domain signal into that plane. This chapter builds that map. The answer is the Zak transform.
A naive guess would be the 2D Fourier transform of , but is a function of one variable, not two — we cannot simply 2D-Fourier-transform it. The Zak transform is, cleverly, a 1D transform of whose output is a function of two variables . It does this by folding onto itself at period and simultaneously collecting a Fourier series in that folding. The result lives on a 2D torus and has exactly the quasi-periodicity structure that the delay-Doppler plane needs.
The Zak transform was introduced by Joshua Zak in 1967 in the context of solid-state physics (Bloch functions in electron band theory). It was rediscovered in signal processing in the 1980s by Janssen, as the right tool for Gabor analysis. For OTFS, the Zak transform is how a continuous-time waveform meets the 2D DD grid.
Definition: Zak Transform
Zak Transform
Let be a sufficiently regular function (e.g., in ). For a parameter (the Zak period), the Zak transform of is where and are the time and Doppler variables on the delay-Doppler plane. The dual frequency period is .
Different authors use different sign conventions. Hadani–Rakib (2017) and Raviteja–Viterbo (2018) use — we adopt that convention throughout this book to match the OTFS literature. Some mathematical references (e.g., Folland 1989) use the opposite sign, which flips the role of the Doppler axis.
The Zak Transform Is a Fourier Series in Disguise
Fix . The sequence consists of samples of spaced by . The Zak transform in is exactly the Fourier series of this sequence. So takes a continuous function and encodes, at each time , the Fourier series of the infinite samples .
The reason this is useful: the sparse DD channel acts by delay and Doppler — exactly the two operations that the Zak transform naturally respects, as we now prove.
Theorem: Zak Transform of a Delay-and-Doppler-Shifted Signal
Let denote the delay-and-Doppler-shift operator: . Then That is: a delay and Doppler shift of becomes a translation in the DD plane of , up to a phase factor.
This is the defining "covariance property" of the Zak transform — and the reason it is the correct signal space for the DD domain. A channel that delays and Doppler-shifts the transmit signal by simply translates the DD-domain picture by . The input-output relation becomes a 2D convolution, as promised in Chapter 1.
Substitute the operator
. Apply the Zak transform:
Group the phase factors
Pull out (it does not depend on ), and combine the remaining exponentials:
Recognize the Zak transform
The sum is precisely . Hence .
Key Takeaway
The Zak transform is covariant under delay-Doppler translation. A time-domain signal that has been delayed by and Doppler-shifted by appears, in the DD domain, as the same DD picture shifted by . This single property is what makes the Zak transform the right signal space for the delay-Doppler channel. The rest of OTFS is, loosely, bookkeeping around this fact.
Example: Zak Transform of a Rectangular Pulse
Let be the rectangular pulse of unit height supported on , i.e., the indicator of the fundamental interval. Compute and interpret the result.
Evaluate the sum
For and any integer , equals precisely when (since lies inside the support) and for all other .
Read off the Zak transform
Therefore for and all . Outside the fundamental interval, quasi-periodicity (Section 2) determines the values.
Interpret
The rectangular pulse of width produces a Zak transform that is constant over the fundamental rectangle . This is the "prototype pulse" used in idealized OTFS — its flat Zak transform makes the DD grid perfectly orthonormal. In practice we use smoothed pulses (raised cosine, etc.), whose Zak transforms have slight ripple.
Zak Transform of a Rectangular Pulse of Variable Width
Plot for a rectangular pulse of variable width on a Zak grid with period . When the Zak transform is uniform and flat; when it exhibits fringes that signal aliasing in the DD grid. Slide the pulse width through one period to see the clean case and the aliased cases.
Parameters
Example: Zak Transform of a Dirac Impulse
Compute where is the Dirac impulse at the origin.
Apply the definition
. The delta vanishes except when .
Impulse train in the DD plane
The Zak transform is a train of impulses along the time axis, at positions :
Interpret
At each the Doppler factor is — a phase that rotates around the Doppler axis at rate . A time-domain Dirac becomes an impulse train on the DD plane. Dually, the Zak transform of a constant signal is a Dirac at (see exercises).
Building by Folding
The Zak Transform is a Unitary Map
One can show that the Zak transform extends to a unitary isomorphism between and , where is the fundamental rectangle (the "quasi-periodic cell"). Concretely, Unitarity is important because it means the Zak transform preserves signal energy (no free information loss). We will need unitarity in Chapter 6 when designing the OTFS transmitter.
Choosing the Zak Period
In OTFS, the Zak period is tied to the OTFS frame parameters: where is the frame duration and is the number of Doppler bins. Equivalently, is the OFDM symbol duration after Heisenberg embedding. Choosing determines the Doppler resolution (since the DD plane has Doppler bins over ).
Key rule: must satisfy to avoid Doppler aliasing (the Zak-plane analog of Nyquist). For vehicular channels ( Hz) this requires ms; LEO satellite channels ( kHz) require .
- •
to avoid Doppler aliasing
- •
Frame duration determines Doppler resolution
- •
Practical trade-off: smaller gives more Doppler slack but shorter frames
Common Mistake: When the Zak Sum Converges
Mistake:
Treating the Zak transform as "always well-defined" — the infinite sum can fail to converge for signals that do not decay, such as constant or slowly-varying signals.
Correction:
Strictly speaking, the Zak transform converges absolutely for in the -sense over the fundamental domain . Pointwise convergence for signals is guaranteed almost everywhere. For rigor in OTFS, treat the Zak transform as a map — the discrete version (Section 4) sidesteps these subtleties entirely.