Patents

Microsoft v. Motorola: The Ninth Circuit Builds the First Judicial Blueprint for a RAND Royalty

The Ninth Circuit affirmed the first judge-set RAND rate for standard-essential patents and a jury's $14.5 million breach-of-contract verdict against the patent holder.

February 17, 2025
Wireless router and laptop illustrating Wi-Fi and video-codec standard-essential patents
Microsoft v. Motorola produced the first courtroom methodology for valuing a standard-essential patent on RAND terms. Shutterstock
Educational content, not legal advice. This article explains general legal concepts. It does not create an attorney–client relationship. For your specific situation, consult a licensed attorney.

When a patent holder promises a standard-setting organization that it will license its essential patents on reasonable and non-discriminatory (RAND) terms, what does “reasonable” actually mean in dollars per unit? Before Microsoft Corp. v. Motorola, Inc., No. 14-35393 (9th Cir. July 30, 2015), no American court had answered that question with a full trial methodology. The Ninth Circuit’s decision — affirming Judge James L. Robart’s landmark bench-trial rate determination and a jury’s $14.5 million breach-of-contract award — remains the foundational U.S. authority on how to translate a RAND commitment into an enforceable number.

The panel of Chief Judge Sidney R. Thomas and Circuit Judges J. Clifford Wallace and Marsha S. Berzon, in an opinion by Judge Berzon, affirmed across the board on appeal from the U.S. District Court for the Western District of Washington.

At a glance

  • Case: Microsoft Corp. v. Motorola, Inc., No. 14-35393 (9th Cir. July 30, 2015); appeal from the Western District of Washington (Robart, J.).
  • Panel: Thomas, C.J., Wallace and Berzon, JJ.; opinion by Berzon, J.
  • Posture: Appeal from a jury verdict awarding Microsoft $14.5 million for Motorola’s breach of its RAND commitments, following a separate bench trial that fixed the RAND rate and range.
  • Holding 1 (jurisdiction): A suit alleging breach of a RAND contract “sounds in contract”; the appeal therefore went to the regional circuit, not the Federal Circuit, even though the contract concerned patents.
  • Holding 2 (methodology): Judge Robart’s modified Georgia-Pacific analysis — adapted to account for royalty stacking and patent hold-up — was a permissible way to set a RAND rate.
  • Holding 3 (breach): Substantial evidence supported the jury’s finding that Motorola breached its duty of good faith and fair dealing, and Microsoft could recover its costs of defending against Motorola’s injunction actions.
  • Why it matters: It is the first U.S. decision to supply a courtroom framework for valuing a SEP and to treat a RAND promise as an enforceable contract owed to third-party-beneficiary implementers.

From standard-setting promise to enforceable contract

Motorola held patents it had declared essential to the H.264 video-compression standard (administered by the ITU) and the 802.11 Wi-Fi standard (administered by the IEEE). As a participant in those bodies, Motorola committed to license its essential patents on RAND terms. In 2010, Motorola sent Microsoft two letters offering to license those portfolios at 2.25% of the price of the end product — a figure that, applied to Xbox consoles and Windows PCs, ran to billions of dollars per year.

Microsoft sued, not for patent infringement, but for breach of contract. Its theory, which the courts accepted, was that Motorola’s RAND declarations to the ITU and IEEE created binding contracts and that Microsoft — as a standard implementer — was a third-party beneficiary entitled to enforce them. That reframing is the doctrinal pivot of the entire case. By casting the dispute in contract, Microsoft converted Motorola’s standard-setting promise into an obligation a court could measure and enforce, and it placed the duty of good faith and fair dealing at the center of the analysis.

The Ninth Circuit first confirmed its own jurisdiction. Motorola argued that the patent-licensing subject matter routed the appeal to the Federal Circuit. The panel disagreed: “a complaint that alleges breach of contract and seeks damages sounds in contract; its nature does not change because the contract is a patent license.” That holding matters beyond procedure — it locates RAND enforcement squarely in the law of contracts and the regional circuits.

A modified Georgia-Pacific framework

The valuation methodology is the decision’s most cited contribution. Patent damages have long been estimated through a hypothetical negotiation guided by the fifteen Georgia-Pacific factors. Judge Robart recognized that several of those factors assume an ordinary, unencumbered patent and make little sense for a SEP. A RAND-committed patentee cannot demand the full leverage its essentiality confers, because the entire point of the commitment is to neutralize that leverage.

Robart therefore conducted a bench trial and rewrote the Georgia-Pacific inquiry, discarding or adjusting factors inconsistent with a RAND obligation and adding two structural constraints:

  • Patent hold-up. Because a standard’s adoption locks implementers in, an essential-patent owner could extract royalties reflecting the cost of switching standards rather than the value of the invention. A proper RAND analysis must value the patented technology itself, ex ante, before the standard conferred market power.
  • Royalty stacking. A single standard may read on thousands of patents. If every holder demanded an outsized share, the aggregate royalty would exceed the product’s value. A RAND rate must account for the total stack so that all essential patents together command a reasonable share.

Applying that adapted framework, Robart set the RAND rate for Motorola’s H.264 patents at 0.555 cents per unit and for its 802.11 patents at 3.471 cents per unit — orders of magnitude below the 2.25% Motorola had demanded. The Ninth Circuit declined Motorola’s invitation to require “rigid adherence to the Georgia-Pacific factors, without accounting for the particulars of RAND agreements,” and held the modified approach permissible. The court also tolerated Robart’s partial reliance on present-day valuations rather than strictly historical ones, finding the hypothetical-negotiation analysis sound.

The breach verdict and the cost of seeking injunctions

The RAND rate did more than settle a price; it supplied the yardstick for measuring Motorola’s conduct. With a court-determined RAND range in hand, a jury could assess whether Motorola’s 2.25% demand and its subsequent injunction campaigns violated the duty of good faith and fair dealing implied in every contract.

The jury found a breach and awarded Microsoft $14.5 million. The bulk of that award compensated Microsoft for the cost of relocating a distribution facility out of Germany to avoid a Motorola injunction there, plus the attorneys’ fees and litigation costs Microsoft incurred defending against Motorola’s injunction actions in the United States and abroad. The Ninth Circuit affirmed, holding that substantial evidence supported the breach finding and that seeking injunctive relief on RAND-committed patents could itself be evidence of bad faith when used as leverage to extract a supra-RAND rate. The court rejected Motorola’s Noerr-Pennington argument that its injunction suits were protected petitioning activity immune from liability.

Open questions

  • How transferable is the rate methodology? Robart’s numbers were tailored to specific portfolios and a specific record. Later courts have adapted, but not mechanically adopted, his framework, and no single canonical RAND formula has emerged.
  • When does seeking an injunction cross into bad faith? The decision treats injunction-seeking as potential evidence of breach, but it does not draw a bright line between legitimate enforcement and coercive leverage.
  • Does the contract framing always control? Treating RAND enforcement as state-law contract leaves room for divergent results across jurisdictions and standard bodies with differently worded commitments.
  • How should courts size the total royalty stack? Robart estimated the stack, but reliable, evidence-based aggregate figures remain difficult to assemble.

Implications

  • RAND promises are enforceable contracts. Implementers can sue as third-party beneficiaries and recover damages for supra-RAND demands and coercive enforcement.
  • Valuation must strip out essentiality. Courts must value the technology on its merits, ex ante, and account for hold-up and stacking rather than the leverage the standard created.
  • Injunctions carry contractual risk. A SEP holder that pursues injunctions to pressure a higher rate may be liable in damages for the implementer’s defense costs.
  • Forum and choice of law matter. Because RAND enforcement sounds in contract, regional-circuit and state-law principles govern, not Federal Circuit patent doctrine alone.
  • The decision is a floor, not a formula. It legitimizes judge-set rates but leaves substantial methodological discretion to trial courts.

Frequently asked questions

Was this a patent-infringement case? No. Microsoft sued for breach of contract, alleging that Motorola violated its RAND commitments to the ITU and IEEE. That framing is why the Ninth Circuit — not the Federal Circuit — heard the appeal.

What is the difference between hold-up and royalty stacking? Hold-up is the risk that an essential-patent owner extracts royalties reflecting an implementer’s lock-in costs rather than the invention’s value. Stacking is the risk that the combined royalties of all patents reading on a standard exceed the product’s worth. A RAND analysis must guard against both.

Why was Motorola liable for $14.5 million if it merely made a high offer? The damages were not for the offer alone but for Motorola’s broader conduct, including pursuing injunctions in Germany and the United States to pressure Microsoft, which the jury found breached the duty of good faith and fair dealing. The award covered Microsoft’s resulting relocation and litigation costs.

Authorities and sources