A Dual-Input Behavioral Model is a black-box modeling framework that accepts two independent inputs—the instantaneous complex baseband RF signal and the dynamic drain supply voltage—to predict the nonlinear output of an envelope tracking (ET) power amplifier. Unlike single-input models that assume a fixed supply, this structure explicitly captures the supply-dependent gain compression and ET-induced AM/PM distortion caused by the interaction between the modulated supply and the RF drive.
Glossary
Dual-Input Behavioral Model

What is Dual-Input Behavioral Model?
A mathematical framework that characterizes a power amplifier's nonlinear response by treating the RF input signal and the dynamic supply voltage as two independent, interacting variables.
The model is essential for ET-DPD co-design because it characterizes the PA's behavior across its full two-dimensional operating space. Implementations often extend the Volterra series or memory polynomial with cross-terms of the supply voltage, creating a 3D correction surface. This allows the digital predistorter to apply a unique complex gain correction for every combination of instantaneous input power and supply voltage, linearizing the transmitter under dynamic modulation.
Key Characteristics of Dual-Input Models
Dual-input behavioral models treat the RF input and dynamic supply voltage as independent variables, enabling precise characterization of envelope tracking power amplifiers where traditional single-input models fail.
Two-Dimensional Basis Function Space
Unlike conventional single-input models that map only |x(n)| to output, dual-input models construct a 2D nonlinear basis indexed by instantaneous input magnitude and supply voltage V<sub>DD</sub>(n). This captures the supply-dependent gain surface where amplifier behavior shifts as the drain voltage modulates. Common basis functions include products of monomials: |x(n)|<sup>k</sup> · V<sub>DD</sub>(n)<sup>m</sup>, creating a rich function space that spans the full operating envelope.
Cross-Term Memory Effects
Dual-input models explicitly capture cross-memory between the RF and supply paths—a phenomenon absent in single-input frameworks. When the supply modulator's bandwidth is limited, the actual V<sub>DD</sub>(t) lags the ideal envelope, creating memory in the supply dimension. The model includes terms like:
- x(n-l) · V<sub>DD</sub>(n-m) for l ≠ m
- |x(n-l)|<sup>k</sup> · V<sub>DD</sub>(n-m)<sup>p</sup> These cross-tap products characterize the interaction between RF memory and supply memory, critical for wideband signals where both paths exhibit significant dynamics.
Augmented Volterra Series Formulation
The Augmented Volterra for ET extends the classical Volterra series by introducing a second input dimension for the supply voltage. The general form is:
y(n) = Σ h<sub>k,m</sub>(l<sub>1</sub>,...,l<sub>k</sub>; q<sub>1</sub>,...,q<sub>m</sub>) · Π x(n-l<sub>i</sub>) · Π V<sub>DD</sub>(n-q<sub>j</sub>)
where kernels h<sub>k,m</sub> weight products of k RF terms and m supply terms at various delays. Truncation to low nonlinearity orders (typically k+m ≤ 7) and short memory depths keeps the model computationally tractable while maintaining excellent prediction accuracy for ET PAs.
3D Look-Up Table Implementation
For memoryless or weakly-memory dual-input predistortion, a 3D LUT provides an efficient hardware implementation. The table is indexed by:
- Instantaneous input power |x(n)|<sup>2</sup> (or magnitude)
- Instantaneous supply voltage V<sub>DD</sub>(n)
Each table entry stores a complex gain correction G(|x|<sup>2</sup>, V<sub>DD</sub>). The predistorted output is x<sub>DPD</sub>(n) = x(n) · G(|x(n)|<sup>2</sup>, V<sub>DD</sub>(n)). Bilinear interpolation between table entries ensures smooth correction across the continuous 2D operating space. This structure maps efficiently to FPGA block RAM with dual-port addressing.
Iso-Gain Contour-Based Model Extraction
Model coefficients are extracted from iso-gain contour measurements taken across the PA's 2D operating plane. The characterization process sweeps:
- Input power from small-signal to deep compression
- Supply voltage from minimum to maximum rated V<sub>DD</sub>
At each (P<sub>in</sub>, V<sub>DD</sub>) point, complex gain is measured, creating a gain surface. Least-squares fitting then extracts the dual-input model parameters. This data-driven approach captures the supply-dependent AM-AM and AM-PM characteristics without requiring detailed physics-based PA models.
Separation of Static and Dynamic Nonlinearities
Advanced dual-input models decompose the PA behavior into:
- Static nonlinearity: A memoryless 2D function f(|x(n)|, V<sub>DD</sub>(n)) capturing instantaneous compression
- Dynamic nonlinearity: Linear filters or low-order Volterra terms capturing memory effects in both dimensions
This Hammerstein-Wiener inspired decomposition reduces parameter count while maintaining accuracy. The static block handles the dominant supply-dependent gain compression, while dynamic blocks model thermal trapping and modulator bandwidth limitations. The structure enables independent optimization of each sub-model during coefficient extraction.
Frequently Asked Questions
Essential questions and answers about the dual-input behavioral modeling framework used to characterize and linearize envelope tracking power amplifiers.
A dual-input behavioral model is a mathematical framework that characterizes a power amplifier's nonlinear response by treating both the RF input signal and the dynamic supply voltage as independent input variables. Unlike conventional single-input models that assume a fixed drain bias, the dual-input approach captures the complex interaction between the modulated RF envelope and the time-varying supply voltage in an envelope tracking system. The model maps the instantaneous complex baseband input and the instantaneous supply voltage to the complex baseband output, enabling accurate prediction of supply-dependent gain compression, ET-induced AM/PM distortion, and memory effects. This framework is essential for designing digital predistorters that can linearize the PA across its full dynamic operating range.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the foundational concepts and advanced techniques that underpin the dual-input behavioral model, a critical framework for characterizing and linearizing envelope tracking power amplifiers.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us