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 gtxg_{tx}) determine the residual off-diagonal errors.

Definition:

Cyclic Prefix for OTFS

The cyclic prefix (CP) prepends the last LCPL_{CP} samples of each OFDM symbol before transmission, exactly as in OFDM. Two CP strategies exist for OTFS:

  1. Per-symbol CP: each of the NN OFDM symbols has its own CP of length LCPlmaxL_{CP} \geq l_{\max}. Overhead: NLCPN L_{CP} samples per frame. Compatible with 5G NR OFDM resource grids.
  2. Frame-level CP (reduced CP): a single CP at the start of the frame of length LCP,framelmaxL_{CP,\text{frame}} \geq l_{\max}. Reduces overhead to LCPL_{CP} samples per frame. Requires a different detector (Chapter 20) but saves (N1)LCP\sim (N-1)L_{CP} 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 LCP    lmax  =  τmaxW.L_{CP} \;\geq\; l_{\max} \;=\; \lceil \tau_{\max} W \rceil. When LCP<lmaxL_{CP} < l_{\max}, residual inter-block interference contaminates the first lmaxLCPl_{\max} - L_{CP} 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.

⚠️Engineering Note

CP Overhead in 5G NR

5G NR specifies two CP configurations:

  • Normal CP (numerology-dependent): LCPL_{CP} is chosen to give roughly 7%7\% overhead for each numerology. Supports τmax4.7μ\tau_{\max} \leq 4.7\,\mus at numerology 0.
  • Extended CP: longer CP at the cost of shorter symbol duration. Supports τmax16.7μ\tau_{\max} \leq 16.7\,\mus, with 25%25\% overhead.

OTFS inherits these configurations directly. For deployment scenarios with τmax>5μ\tau_{\max} > 5\,\mus (rural macro, hills, hilly terrain in HST), extended CP is needed. For indoor / urban micro with τmax<1μ\tau_{\max} < 1\,\mus, normal CP suffices.

The CP overhead is independent of NN — it is fixed by the physical delay spread and the symbol duration. Making the OTFS frame longer (larger NN) does not increase per-symbol CP overhead. This is an advantage over per-frame pilot schemes.

Practical Constraints
  • LCPlmax=τmaxWL_{CP} \geq l_{\max} = \lceil \tau_{\max} W\rceil for valid doubly-circular structure

  • Normal CP: 7%7\% overhead; Extended CP: 25%25\% overhead

  • Frame-level CP (Chapter 20): up to N×N\times savings in overhead but requires advanced detector

📋 Ref: 3GPP TS 38.211 §4.3

Definition:

Common OTFS Prototype Pulses

Four prototype pulses are standard in OTFS:

  • Rectangular: gtx(t)=(1/Ts)1[0,Ts)(t)g_{tx}(t) = (1/\sqrt{T_s})\mathbf{1}_{[0, T_s)}(t). Simple, bi-orthogonal at critical density. Poor spectral containment (high side lobes). The default in most literature.
  • Root-raised-cosine (RRC): gtx(t)g_{tx}(t) is the impulse response of an RRC filter with roll-off α\alpha. Better spectral containment; not strictly bi-orthogonal.
  • Gaussian: gtx(t)et2/(2σ2)g_{tx}(t) \propto e^{-t^2/(2\sigma^2)}. Good simultaneous time-frequency localization (optimal for σ=Ts/(2πΔf)\sigma = \sqrt{T_s/(2\pi\Delta f)}). 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

PulseTime supportFreq. containmentDD grid cleannessDefault use
RectangularCompactPoor (sinc side lobes)Exact (bi-ortho)Theoretical analysis
Raised-cosineExtended (truncated)GoodNear-exactPractical OFDM
RRCExtended (truncated)Very goodGoodAdvanced OTFS
GaussianInfinite tailsGoodGood w/ large σ\sigmaInformation-theoretic proofs
DesignedOptimizedOptimizedOptimized6G research

Theorem: Residual DD Cross-Talk From Non-Bi-Orthogonal Pulses

For a prototype pulse gg that does not satisfy the strict bi-orthogonality condition, the DD channel matrix HDD\mathbf{H}_{DD} acquires off-diagonal "cross-talk" entries whose magnitudes are bounded by cross-talk    max(t,ν)T2Zg(t,ν)Zg(t,ν)1,|\text{cross-talk}| \;\lesssim\; \max_{(t, \nu) \in \mathbb{T}^2}\left|Z_g(t, \nu) \overline{Z_{g^\perp}(t, \nu)} - 1\right|, where gg^\perp is the ideal bi-orthogonal dual window. The bound is zero iff g=gg = g^\perp (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 Zg|Z_g| on the fundamental domain, and the deviation from flatness quantifies the 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
0.25
0.5
16

Common Mistake: Don't Assume CP Size Equals Channel Memory

Mistake:

Allocating LCP=τmaxWL_{CP} = \tau_{\max} W as if the channel's maximum delay is known exactly. In deployment, τmax\tau_{\max} is an upper bound; the actual channel fluctuates.

Correction:

Allocate LCP=1.5τmaxmaxWL_{CP} = \lceil 1.5 \tau_{\max}^{\text{max}} W\rceil as a safety factor, where τmaxmax\tau_{\max}^{\text{max}} 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.