Inferensys

Glossary

I/Q Pipeline

An end-to-end data engineering architecture that handles the continuous ingestion, preprocessing, buffering, and batching of high-throughput IQ streams for real-time inference on a GPU or FPGA.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
DATA ENGINEERING ARCHITECTURE

What is I/Q Pipeline?

An end-to-end data engineering architecture that handles the continuous ingestion, preprocessing, buffering, and batching of high-throughput IQ streams for real-time inference on a GPU or FPGA.

An I/Q Pipeline is a high-throughput data engineering architecture designed to ingest, preprocess, buffer, and batch continuous streams of complex baseband samples for real-time machine learning inference. It bridges the gap between raw RF hardware output and the structured tensor inputs required by neural network classifiers, managing the deterministic flow of gigasamples per second through a sequence of signal conditioning stages.

The pipeline typically includes hardware driver interfaces for direct IQ sample acquisition, followed by GPU-accelerated preprocessing blocks that apply I/Q normalization, DC offset correction, and I/Q segmentation into fixed-length inference windows. A zero-copy buffering layer decouples the asynchronous ingest rate from the model's inference cadence, ensuring no samples are dropped before classification.

ARCHITECTURAL FOUNDATIONS

Key Characteristics of an I/Q Pipeline

An I/Q pipeline is a deterministic, high-throughput data engineering architecture that transforms raw, continuous complex baseband streams into standardized, batched tensors for real-time GPU or FPGA inference. The following characteristics define its operational integrity.

01

Streaming Ingestion & Buffering

The pipeline front-end must handle continuous, unbounded I/Q streams from software-defined radios (SDRs) without backpressure or sample loss. This requires a zero-copy ring buffer architecture in shared memory, allowing the radio driver to write samples directly while the preprocessing engine reads asynchronously. Key mechanisms include:

  • Lock-free queues to prevent thread contention between producer (radio) and consumer (GPU transfer).
  • Circular buffers sized to absorb bursty transfers, typically holding 100-500ms of samples to tolerate scheduling jitter.
  • Timestamp alignment using hardware PPS (Pulse Per Second) signals to maintain sample-accurate synchronization across multiple channels.
< 1 µs
Sample Jitter Tolerance
100+ MSPS
Typical Ingest Rate
02

Deterministic Preprocessing Graph

Raw I/Q samples undergo a fixed sequence of signal conditioning operations compiled into a directed acyclic graph (DAG). Each node in the graph applies a specific transformation—I/Q correction, DC offset removal, normalization, and resampling—with the output feeding the next stage. Determinism is critical: the same input must produce an identical output tensor for reproducible inference. The graph typically includes:

  • Gain normalization to scale amplitude to a fixed range (e.g., unit variance) regardless of receiver AGC state.
  • Carrier frequency offset (CFO) compensation via digital mixing to center the constellation.
  • Sample rate decimation using polyphase filters to match the classifier's native input rate.
03

Segmentation & Windowing Engine

The continuous preprocessed stream is partitioned into fixed-length, potentially overlapping segments that form individual inference examples. The segmentation engine applies a sliding window with configurable stride and length, typically 1024 or 2048 complex samples per segment. Each segment then receives a tapering window (Hamming, Blackman, or Kaiser) to minimize spectral leakage if a subsequent FFT-based transformation is used. Critical parameters include:

  • Segment duration: Must capture enough symbols for modulation discrimination (e.g., 256+ symbols).
  • Overlap factor: 50% overlap is common to avoid missing transient signals at segment boundaries.
  • Windowing function: Chosen based on the dynamic range requirements of downstream feature extraction.
04

Batched Tensor Assembly

Individual I/Q segments are aggregated into batched tensors to maximize GPU utilization during inference. The assembly stage stacks multiple segments along a batch dimension, producing a tensor of shape [batch_size, 2, num_samples] for dual-channel real-valued input or [batch_size, num_samples] for complex-valued input. This stage manages:

  • Dynamic batching: Accumulating segments until a target batch size (e.g., 64 or 128) is reached or a latency deadline expires.
  • Zero-padding: Handling variable-length segments by padding shorter sequences to a uniform length.
  • Memory pinning: Using CUDA-pinned host memory to enable direct memory access (DMA) transfers to the GPU without intermediate copies.
05

Hardware-Accelerated Transfer Path

The pipeline's final stage is a low-latency transfer path that moves batched tensors from CPU memory to the inference accelerator. For GPU targets, this uses RDMA (Remote Direct Memory Access) or GPUDirect to bypass the CPU entirely, streaming data directly from the SDR's PCIe interface to GPU memory. For FPGA targets, the pipeline may feed samples directly into a streaming AXI4-Stream interface on the fabric. Key performance metrics:

  • Transfer latency: Must be sub-millisecond to maintain real-time classification.
  • Throughput: Must sustain the full sample rate without dropping batches.
  • Double-buffering: Overlapping the transfer of batch N+1 with the inference of batch N.
< 1 ms
GPU Transfer Latency
Zero-Copy
Memory Architecture
06

Pipeline Telemetry & Backpressure

A production I/Q pipeline requires comprehensive observability to detect stalls, overflows, and timing violations. Each stage emits metrics—queue depth, processing latency, dropped sample count—to a monitoring backend. A backpressure mechanism propagates downstream congestion upstream: if the GPU inference queue is full, the batching stage slows ingestion, which signals the SDR buffer to throttle. This prevents unbounded memory growth and ensures graceful degradation under load. Common telemetry includes:

  • End-to-end latency histogram from antenna to classification output.
  • Buffer watermark levels to detect imminent overflows.
  • Sample drop counters with timestamps for root-cause analysis.
I/Q PIPELINE ARCHITECTURE

Frequently Asked Questions

Explore the critical data engineering patterns required to ingest, preprocess, and deliver high-throughput in-phase and quadrature (I/Q) sample streams for real-time machine learning inference on GPUs and FPGAs.

An I/Q pipeline is an end-to-end data engineering architecture that handles the continuous ingestion, preprocessing, buffering, and batching of high-throughput in-phase and quadrature (I/Q) sample streams for real-time inference on a GPU or FPGA. The pipeline begins at the analog-to-digital converter (ADC) interface, where raw complex baseband samples are streamed into a circular memory buffer. A digital down-converter (DDC) then translates the signal to zero frequency, followed by a series of preprocessing stages—including I/Q correction for hardware impairments, normalization to standardize amplitude, and segmentation into fixed-length tensors. These batches are transferred via direct memory access (DMA) to the compute accelerator, where a neural network classifier performs modulation recognition. The entire architecture must sustain deterministic latency, often processing hundreds of megasamples per second, requiring careful optimization of memory bandwidth and pipelined parallelism between data movement and computation.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.