Cyclic Prefix and Pulse Shaping
Making the Theory Practical
The Heisenberg transform of Section 2 assumes an idealized bi-orthogonal pulse. In practice we must choose a concrete pulse and add a cyclic prefix to absorb the channel's delay spread. These two choices — pulse shape and CP — determine how closely the deployed OTFS system tracks the clean theoretical input-output relation of Chapter 4. Both choices directly affect pilot design (Chapter 7) and detection (Chapter 8).
The point is that OTFS's CP and pulse-shape trade-offs mirror OFDM's — same hardware, same engineering levers — with one crucial twist: OTFS uses a whole-frame CP (or a per-symbol CP with block structure), and the pulse's DD-domain properties (via the Zak transform of ) determine the residual off-diagonal errors.
Definition: Cyclic Prefix for OTFS
Cyclic Prefix for OTFS
The cyclic prefix (CP) prepends the last samples of each OFDM symbol before transmission, exactly as in OFDM. Two CP strategies exist for OTFS:
- Per-symbol CP: each of the OFDM symbols has its own CP of length . Overhead: samples per frame. Compatible with 5G NR OFDM resource grids.
- Frame-level CP (reduced CP): a single CP at the start of the frame of length . Reduces overhead to samples per frame. Requires a different detector (Chapter 20) but saves samples per frame.
Per-symbol CP is the baseline. Frame-level CP is a more advanced design covered in Chapter 20.
Theorem: Minimum Cyclic-Prefix Length
For the discrete DD input-output relation of Chapter 4 to hold exactly (doubly-circular, no inter-block interference), the CP length must satisfy When , residual inter-block interference contaminates the first delay bins.
Same requirement as OFDM: the CP must absorb the channel memory so that the linear convolution within each OFDM symbol becomes circular. For OTFS the requirement is per OFDM symbol, and it is identical to OFDM's — OTFS inherits CP dimensioning from OFDM with no change.
Channel memory
The discrete channel has taps up to delay . Within one OFDM symbol, the channel output is the circular convolution only if the previous samples from the neighboring symbol are included — that is, the CP provides this context.
Insufficient CP
If , the first delay bins receive input from the previous symbol's last samples (inter-block interference). The circular convolution identity fails for these cells.
Consequence
In the DD channel matrix view (Chapter 4), insufficient CP produces off-block-diagonal terms in , breaking the clean Kronecker-product structure. The ISFFT no longer diagonalizes exactly; detection loses dB per unit of missing CP at typical parameters.
CP Overhead in 5G NR
5G NR specifies two CP configurations:
- Normal CP (numerology-dependent): is chosen to give roughly overhead for each numerology. Supports s at numerology 0.
- Extended CP: longer CP at the cost of shorter symbol duration. Supports s, with overhead.
OTFS inherits these configurations directly. For deployment scenarios with s (rural macro, hills, hilly terrain in HST), extended CP is needed. For indoor / urban micro with s, normal CP suffices.
The CP overhead is independent of — it is fixed by the physical delay spread and the symbol duration. Making the OTFS frame longer (larger ) does not increase per-symbol CP overhead. This is an advantage over per-frame pilot schemes.
- •
for valid doubly-circular structure
- •
Normal CP: overhead; Extended CP: overhead
- •
Frame-level CP (Chapter 20): up to savings in overhead but requires advanced detector
Definition: Common OTFS Prototype Pulses
Common OTFS Prototype Pulses
Four prototype pulses are standard in OTFS:
- Rectangular: . Simple, bi-orthogonal at critical density. Poor spectral containment (high side lobes). The default in most literature.
- Root-raised-cosine (RRC): is the impulse response of an RRC filter with roll-off . Better spectral containment; not strictly bi-orthogonal.
- Gaussian: . Good simultaneous time-frequency localization (optimal for ). Not compactly supported.
- Designed (optimized) pulses: numerically optimized for specific channel statistics (Chapter 20).
The choice affects: (i) spectral containment at band edges, (ii) PAPR, (iii) off-diagonal residuals in the DD channel matrix, (iv) pilot region leakage (Chapter 7).
OTFS Prototype Pulses: Trade-offs
| Pulse | Time support | Freq. containment | DD grid cleanness | Default use |
|---|---|---|---|---|
| Rectangular | Compact | Poor (sinc side lobes) | Exact (bi-ortho) | Theoretical analysis |
| Raised-cosine | Extended (truncated) | Good | Near-exact | Practical OFDM |
| RRC | Extended (truncated) | Very good | Good | Advanced OTFS |
| Gaussian | Infinite tails | Good | Good w/ large | Information-theoretic proofs |
| Designed | Optimized | Optimized | Optimized | 6G research |
Theorem: Residual DD Cross-Talk From Non-Bi-Orthogonal Pulses
For a prototype pulse that does not satisfy the strict bi-orthogonality condition, the DD channel matrix acquires off-diagonal "cross-talk" entries whose magnitudes are bounded by where is the ideal bi-orthogonal dual window. The bound is zero iff (perfect bi-orthogonality).
The DD domain is where bi-orthogonality "lives" — the Zak transform's bounded, bounded-below condition from Chapter 2 exactly specifies it. A non-bi-orthogonal pulse has non-flat on the fundamental domain, and the deviation from flatness quantifies the cross-talk.
Gabor-dual pair
The bi-orthogonal dual window satisfies .
Cross-talk estimate
The deviation from the identity multiplier on the Gabor system bounds the off-diagonal error. Under the sup-norm bound above, the DD-cell coupling is of order .
For rectangular $g$
, (self-dual), on — perfect bi-orthogonality, zero cross-talk.
For Gaussian $g$
is periodized Gaussian; is at most for — moderate cross-talk.
How Pulse Choice Affects the DD Cross-Talk
For each prototype pulse (rectangular, RRC, Gaussian), plot (i) the time-domain pulse, (ii) its Zak transform magnitude on the fundamental domain, and (iii) the resulting DD cross-talk magnitude on a sample OTFS frame. Observe that rectangular pulses give exact bi-orthogonality (flat Zak, zero cross-talk), while RRC and Gaussian trade some cross-talk for spectral containment.
Parameters
Common Mistake: Don't Assume CP Size Equals Channel Memory
Mistake:
Allocating as if the channel's maximum delay is known exactly. In deployment, is an upper bound; the actual channel fluctuates.
Correction:
Allocate as a safety factor, where is the 99th percentile over the deployment environment. This is the OFDM practice adopted in 5G NR. For OTFS the same applies — do not under-allocate CP based on typical delay, over-allocate based on worst-case delay.