The Wiener Model is a block-structured behavioral model consisting of a linear time-invariant (LTI) dynamic filter followed by a static memoryless nonlinearity. This cascade structure is specifically used to model power amplifiers (PAs) where the physical memory effects—such as those caused by bias circuit impedance or thermal dynamics—occur before the transistor's nonlinear gain compression, making it the structural complement to the Hammerstein Model.
Glossary
Wiener Model

What is the Wiener Model?
A foundational block-oriented model for power amplifiers where linear memory effects precede the static nonlinear distortion.
In digital predistortion (DPD) applications, the Wiener model's parameter extraction is more complex than a simple memory polynomial because the nonlinearity is applied to the filtered signal, not the raw input. Coefficient estimation often requires iterative optimization or specialized algorithms like the Narendra-Gallman method to decouple the linear and nonlinear blocks, as the static nonlinearity's inverse must be synthesized after the dynamic filter to construct an effective predistorter.
Key Characteristics of the Wiener Model
The Wiener model is a foundational block-structured architecture that decomposes power amplifier behavior into a linear dynamic filter followed by a static memoryless nonlinearity, specifically capturing scenarios where memory effects precede nonlinear distortion.
Cascade Structure: LTI Filter First
The defining architecture of the Wiener model is a linear time-invariant (LTI) dynamic filter cascaded with a static memoryless nonlinearity. The input signal first passes through the linear filter, which shapes the signal's temporal characteristics and introduces memory effects. The filtered output then feeds into the static nonlinear block, which applies amplitude-dependent distortion. This ordering is critical: it models power amplifiers where bias circuit dynamics and thermal effects create memory in the signal envelope before the transistor's nonlinear gain compression occurs.
Mathematical Formulation
The Wiener model is expressed mathematically as:
- Linear filter output:
v(n) = Σ h(k) * x(n-k)for k=0 to M-1, whereh(k)are the filter coefficients and M is the memory depth - Nonlinear output:
y(n) = f(v(n)), wheref(·)is a static nonlinear function, typically a complex polynomial:f(v) = Σ a_p * v * |v|^(p-1)for odd p
The combined model captures frequency-dependent memory effects that manifest before the nonlinear gain compression, making it suitable for PAs with significant input matching network dynamics.
Inverse Model for Predistortion
For digital predistortion, the Wiener predistorter is typically implemented as the inverse structure: a static nonlinearity followed by a linear filter (a Hammerstein model). This is because the predistorter must invert the PA's Wiener characteristic:
- The static nonlinear block pre-distorts the signal amplitude to counteract the PA's gain compression
- The linear filter then compensates for the PA's input memory effects
This inverse relationship is derived using the pth-order inverse theory, which provides a systematic method for computing the predistorter coefficients from the extracted PA model.
Parameter Extraction via Least Squares
Coefficient extraction for the Wiener model typically employs batch least squares (LS) estimation on measured input-output data:
- The linear filter coefficients
h(k)are first estimated by fitting the model to small-signal S-parameter measurements, where the PA operates linearly - The static nonlinearity coefficients
a_pare then extracted by applying a polynomial fit to the AM-AM and AM-PM characteristics measured under large-signal excitation - Alternatively, iterative optimization can jointly estimate both blocks by minimizing the error between modeled and measured output waveforms
Limitations and Applicability
The Wiener model has specific limitations that define its applicability:
- Unidirectional memory: It only captures memory effects that precede nonlinearity, not cases where nonlinearity generates memory (e.g., dynamic thermal effects in the transistor channel)
- No cross-terms: Unlike the Generalized Memory Polynomial, it lacks envelope memory cross-terms that model interactions between the signal and its lagging envelope
- Best suited for: PAs with significant input matching network dynamics or bias tee filtering before the active device, where linear filtering dominates the memory behavior
For PAs where memory and nonlinearity are deeply intertwined, the Wiener-Hammerstein cascade or Parallel Hammerstein models offer superior accuracy.
Comparison with Hammerstein Model
The Wiener and Hammerstein models are complementary block structures distinguished by block ordering:
- Wiener: Linear filter → Static nonlinearity (memory before distortion)
- Hammerstein: Static nonlinearity → Linear filter (distortion before memory)
The choice depends on the physical origin of memory effects in the PA:
- Use Wiener when input-side parasitics and bias network filtering dominate
- Use Hammerstein when output-side thermal effects and drain bias modulation dominate
- For complex PAs exhibiting both, the Wiener-Hammerstein cascade combines both structures in series
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.
Frequently Asked Questions
Explore the structure, application, and mathematical foundations of the Wiener model for power amplifier behavioral modeling and digital predistortion.
A Wiener model is a block-structured nonlinear system model consisting of a linear time-invariant (LTI) dynamic filter followed by a static memoryless nonlinearity. In the context of power amplifier (PA) modeling, the input signal first passes through the linear filter, which captures frequency-dependent memory effects such as bias circuit impedance and thermal dynamics. The filtered signal then enters the static nonlinear block, which models the amplifier's instantaneous gain compression and AM/AM and AM/PM distortion. This cascade structure makes the Wiener model particularly effective for PAs where the memory effects precede the nonlinear distortion generation, such as in certain transistor configurations where input matching network dynamics dominate. The model is mathematically expressed as a linear convolution followed by a polynomial evaluation, offering a compact parameterization compared to full Volterra series models.
Related Terms
Explore the family of block-structured models used to decompose power amplifier behavior into cascaded linear and nonlinear elements for efficient predistorter design.
Parallel Hammerstein
A multi-branch architecture composed of multiple Hammerstein models operating in parallel, where each branch contains a unique static nonlinearity followed by a dedicated linear filter. This structure generalizes the Hammerstein model to represent complex nonlinear dynamics that cannot be captured by a single branch. It is functionally equivalent to a Volterra series with diagonal kernel structure and is widely used for modeling PAs with strong frequency-dependent nonlinear behavior, such as GaN HEMT amplifiers under wideband modulation.
Generalized Memory Polynomial (GMP)
An enhanced memory polynomial model that includes cross-terms between the signal and its lagging or leading envelope samples. These cross-terms capture complex memory effects that the standard MP model misses, such as those arising from bias circuit modulation and thermal dynamics. The GMP adds two types of cross-term clusters: lagging envelope terms (capturing long-term memory) and leading envelope terms (capturing non-causal effects from measurement alignment). It provides significantly improved modeling accuracy for Doherty and envelope tracking PAs.
Basis Function Orthogonalization
A numerical conditioning process that transforms correlated polynomial basis functions into an orthogonal set to improve the stability and convergence speed of coefficient estimation. In Wiener and MP models, the polynomial terms of the input signal are highly correlated, leading to ill-conditioned data matrices. Orthogonalization techniques such as Gram-Schmidt or using orthonormal basis functions (Laguerre, Kautz) decorrelate the regressors, enabling faster and more robust least squares solutions during real-time DPD adaptation.

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