Litigation Details for Oracle America, Inc. v. Google Inc. (N.D. Cal. 2010)

« Back to Dashboard

Oracle America, Inc. v. Google Inc. (N.D. Cal. 2010)

Docket		Date Filed	2010-08-12
Court	District Court, N.D. California	Date Terminated	2016-07-05
Cause	35:271 Patent Infringement	Assigned To	William Haskell Alsup
Jury Demand	Both	Referred To	Donna M. Ryu
Parties	GOOGLE, LLC
Patents	11,338,011; 12,023,328; 12,280,024; 8,552,002; 9,018,192
Attorneys	Matthias Andreas Kamber
Firms	Greenberg Traurig, LLP
Link to Docket	External link to docket

Details for Oracle America, Inc. v. Google Inc. (N.D. Cal. 2010)

Date Filed	Document No.	Description	Snippet	Link To Document
2010-08-12				External link to document

Oracle America, Inc. v. Google Inc. Litigation Summary and Patent-Copyright Analysis

Last updated: October 5, 2026

Oracle America, Inc. v. Google Inc., No. 3:10-cv-03561-WHA, was a major software intellectual-property dispute over Google’s use of Java-related code and APIs in Android. Oracle acquired the Java business through its 2010 acquisition of Sun Microsystems and sued Google in the Northern District of California on August 12, 2010. The case ended when the U.S. Supreme Court held in 2021 that Google’s copying of portions of the Java SE API constituted fair use. Oracle recovered no damages, and the dispute produced no settlement, license agreement, injunction, or ongoing litigation exposure.

The case had two distinct components:

1. Patent claims involving Java virtual-machine technology.
2. Copyright claims involving Java API declarations, implementing code, and documentation.

The patent claims were largely resolved before the final Supreme Court proceedings. The copyright fair-use issue controlled the ultimate outcome.

What was Oracle America v. Google about?

Oracle alleged that Android copied protected elements of Java, including Java application programming interface packages and code associated with the Java virtual machine. Google argued that the copied material was either not copyrightable or was used lawfully under the fair-use doctrine.

Oracle’s original complaint asserted claims under:

• U.S. patent law;
• Copyright law;
• Patent-related state-law theories.

The complaint initially identified seven Java patents. By the principal trial, the patent case had narrowed substantially. The surviving dispute focused on U.S. Patent Nos. 6,061,520 and 7,426,720, while copyright claims concerning 37 Java API packages became the central commercial issue.

Field	Case detail
Case	Oracle America, Inc. v. Google Inc.
District docket	No. 3:10-cv-03561-WHA
Court	U.S. District Court for the Northern District of California
Filed	August 12, 2010
District judge	William H. Alsup
Plaintiff	Oracle America, Inc.
Defendant	Google Inc., later Google LLC
Technology	Java SE APIs, Android operating system, Java virtual-machine technology
Main legal issues	Patent infringement, copyrightability, fair use
Federal Circuit decision	2014
Supreme Court decision	April 5, 2021
Final result	Judgment for Google on fair use; no damages awarded

What patents did Oracle assert against Google?

Oracle initially asserted seven Java-related patents. The most important patents identified in the litigation were:

Patent	Subject matter	Litigation status
U.S. Patent No. 5,966,702	Static initialization and related Java execution techniques	Claims were affected by validity and reexamination issues and did not control the final appeal
U.S. Patent No. 6,061,520	Resolving symbolic references in computer programs	Tried at the 2012 district-court trial
U.S. Patent No. 7,426,720	Protection and execution of Java-related code	Tried at the 2012 district-court trial

The Federal Circuit’s 2014 opinion described the patent phase as involving claims from the ’520, ’720, and ’702 patents. The district court later held that the asserted patent claims were invalid or otherwise did not support a monetary recovery sufficient to drive the case forward. The patent issues did not reach the Supreme Court’s 2021 fair-use decision.

Oracle’s patent theory was based on Android’s implementation of Java-related functionality, not on a conventional pharmaceutical composition, formulation, manufacturing process, or method-of-treatment claim. The asserted patents therefore had no relevance to FDA approval, Orange Book listing, Hatch-Waxman paragraph IV litigation, biosimilar substitution, or drug exclusivity.

What happened in the 2012 trial?

The first trial began in April 2012 before Judge Alsup. The case was divided into patent, copyright, and damages phases.

The jury found that Google infringed some asserted Java patents, but patent validity and damages issues prevented Oracle from obtaining a meaningful patent recovery. The jury also found copyright infringement involving portions of Java code and API-related material, but it did not reach a definitive verdict on whether Google’s conduct was fair use.

The principal copyrighted material included:

• Declarations associated with 37 Java API packages;
• Nine lines of implementing code;
• The Java rangeCheck function;
• Certain organizational and structural elements of the Java platform.

The API declarations described method names, parameters, and organizational relationships. They allowed programmers familiar with Java to write code using the same commands and package structure in Android.

Oracle claimed that Google copied approximately 11,500 lines associated with the Java API structure. Google argued that the API declarations were methods of operation or otherwise lacked protectable expression under copyright law.

Why did the district court hold that Java APIs were not copyrightable?

In May 2012, Judge Alsup held that the structure, sequence, and organization of the 37 Java API packages were not protected by copyright to the extent asserted by Oracle. The court treated the declarations and command structure as functional elements that developers needed to use to access Java-related functions.

The decision distinguished between:

• The general organization and declarations required to use the Java API; and
• Implementing code that performs a function.

The district court held that the declarations were not copyrightable under the merger doctrine and the statutory exclusion for procedures, processes, systems, and methods of operation. The court also found that the relevant expression was constrained by functional requirements and compatibility considerations. The nine lines of code and rangeCheck function remained eligible for copyright protection, but the court determined that the infringement allegations did not justify Oracle’s broader damages theory. (Oracle America, Inc. v. Google Inc., 872 F. Supp. 2d 974 (N.D. Cal. 2012).)

How did the Federal Circuit change the case?

The Federal Circuit reversed the district court’s copyrightability ruling in 2014. It held that the Java API declarations and their structure, sequence, and organization could be protected by copyright, even though the APIs performed functional roles. The court sent the case back for a fair-use trial.

The Federal Circuit’s decision did not hold that Google infringed all protectable elements as a matter of law. It held that the material was eligible for copyright protection and that Google’s fair-use defense required a factual determination. (Oracle America, Inc. v. Google Inc., 750 F.3d 1339 (Fed. Cir. 2014).)

The Federal Circuit also rejected Google’s argument that the API material was categorically excluded from copyright protection as a method of operation. The court recognized that a functional work can contain protectable expression, although the scope of protection may be narrower than for highly creative works.

What was the 2016 fair-use verdict?

A second jury trial began in May 2016. The jury found that Google’s use of the Java API material in Android was fair use.

The fair-use analysis addressed the four statutory factors under 17 U.S.C. § 107:

1. The purpose and character of the use;
2. The nature of the copyrighted work;
3. The amount and substantiality of the portion used; and
4. The effect of the use on the potential market.

Google prevailed despite copying material that Oracle argued was commercially significant. The jury accepted Google’s position that Android transformed the role of the Java APIs by using them in a different operating system and mobile-device environment.

The verdict eliminated Oracle’s damages claim, which had been valued in the billions of dollars. Oracle had sought damages tied to Android’s commercial success, advertising revenue, licensing value, and Google’s alleged use of Java to accelerate Android development.

What did the Supreme Court decide in 2021?

The Supreme Court granted review on two questions:

1. Whether the Java API declarations were copyrightable; and
2. Whether Google’s copying was fair use.

The Court assumed, without deciding, that the copied API material was protected by copyright. It then held that Google’s use was fair use. The 6-2 decision, written by Justice Stephen Breyer, emphasized the functional nature of the declaring code, the value of interoperability and developer familiarity, and the different context in which Google used the material.

The Court relied on several points:

• Google copied only part of the Java platform;
• The copied material was primarily declarations and organizational structure;
• The material was bound to functional requirements;
• Android placed the APIs in a new operating environment;
• Google’s use served a transformative purpose;
• Oracle had not established that Android displaced a realistic market for the copied material.

The Court treated the amount copied as substantial in relation to developer utility but relatively limited compared with the Java platform as a whole. It also considered the public benefit of preserving a familiar programming environment for developers. (Google LLC v. Oracle America, Inc., 141 S. Ct. 1183 (2021).)

Justice Thomas, joined by Justice Alito, dissented. The dissent argued that the majority improperly discounted the value of the copied code and expanded fair use beyond the statutory framework.

When did the Oracle-Google litigation end?

The Supreme Court issued its decision on April 5, 2021. The ruling resolved the principal copyright dispute. Oracle did not receive damages, an injunction, or a continuing royalty stream.

The litigation timeline was:

Date	Event
August 12, 2010	Oracle filed suit in the Northern District of California
2011	Patent claims narrowed through validity and reexamination proceedings
April-May 2012	First jury trial
May 2012	Judge Alsup held the asserted API structure not copyrightable
May 2014	Federal Circuit reversed the copyrightability ruling
May-June 2016	Second jury trial on fair use
May 2016	Jury found Google’s use fair
2018	Federal Circuit revived Oracle’s damages dispute after post-trial proceedings
January 2020	Supreme Court granted review
April 5, 2021	Supreme Court held Google’s use was fair use

What damages did Oracle seek?

Oracle’s damages theory expanded as Android’s commercial success increased. Public filings and trial proceedings placed Oracle’s claimed damages in the multibillion-dollar range. Oracle argued that Google’s Java use affected:

• Android licensing value;
• Mobile advertising revenue;
• Google Play ecosystem value;
• Java licensing opportunities;
• Oracle’s ability to commercialize Java in mobile devices.

At different points, Oracle’s claimed damages were reported at approximately $8.8 billion to more than $9 billion. Those figures were litigation demands or expert-based estimates, not adjudicated damages.

Google’s final liability was zero. The fair-use verdict and Supreme Court decision eliminated Oracle’s copyright recovery. The patent claims did not produce a continuing royalty or injunction.

Was there a settlement agreement or Java license?

The parties did not publicly disclose a settlement resolving the case. The dispute proceeded through two district-court trials, Federal Circuit appeals, and Supreme Court review.

Google did not obtain a Java license from Oracle as part of a publicly reported resolution of the case. Android used a Java-compatible programming environment, but the Supreme Court decision established that the specific copying at issue was fair use. The decision did not create a broad license for all Java implementations or all API copying.

The ruling also did not invalidate Oracle’s Java copyrights generally. It resolved the particular copying and fair-use dispute involving the Java APIs used in Android.

How strong was Oracle’s patent and copyright position?

Oracle’s patent position was materially weaker than its copyright position by the end of the district-court proceedings. The patent claims faced validity problems, narrowing, and difficulties establishing recoverable damages. The copyright case was more significant because the copied API structure had substantial commercial value and was embedded in Android’s developer ecosystem.

Issue	Oracle position	Final outcome
Java patents	Android infringed Java execution and virtual-machine technology	No material final recovery
API copyrightability	Java API structure was protected expression	Supreme Court assumed protection for purposes of decision
Copying	Google copied API declarations and limited code	Copying accepted as relevant to fair-use analysis
Fair use	Google’s conduct was not fair use	Google prevailed at trial and Supreme Court
Damages	Billions of dollars tied to Android’s value	No damages
Injunction	Android distribution should be restricted or monetized	None issued
License remedy	Oracle should receive a Java-related royalty	None ordered

The Supreme Court ruling narrowed the practical value of Oracle’s copyright claim against platform developers that use limited API material for compatibility, interoperability, or a new technical environment. It did not eliminate copyright protection for software interfaces. The result depends on the nature of the interface, the amount copied, the purpose of the use, and market substitution evidence.

What generic-entry, biosimilar, and regulatory risks existed?

No generic-entry or biosimilar issue existed. Oracle America v. Google was not a pharmaceutical or biologics case.

The case had:

• No FDA approval pathway;
• No Orange Book listing;
• No paragraph IV certification;
• No Hatch-Waxman exclusivity;
• No biosimilar interchangeability question;
• No formulation patent;
• No method-of-use patent;
• No manufacturing patent for an active pharmaceutical ingredient;
• No pharmaceutical settlement restricting generic entry.

The relevant commercial risk was Android ecosystem exposure. Oracle sought to convert alleged Java IP infringement into a royalty or damages claim against one of the world’s largest mobile platforms.

What was the commercial impact of the decision?

The decision reduced Google’s historical liability for Android and limited Oracle’s ability to monetize the Java APIs at issue through retroactive damages or an injunction.

For software companies, the case established several commercial points:

• API declarations may receive copyright protection even when they perform functional tasks.
• Copyrightability does not determine liability.
• Fair use can defeat a major API claim even after protectability is established.
• Compatibility and developer familiarity may support a fair-use defense.
• A large commercial platform does not automatically lose fair use because it earns substantial revenue.
• Damages evidence must connect the copied material to actual market harm, not simply to the overall value of the defendant’s product.

The case remains important for software licensing, open-source compliance, platform development, interoperability, reverse engineering, and API reuse. Its holding does not eliminate patent risk. A software interface may escape copyright damages while still implicating patent claims, trade-secret restrictions, contractual licenses, or open-source obligations.

Key Takeaways

• Oracle filed the case in 2010 after acquiring Sun Microsystems and Java.
• The dispute involved Java patents, API declarations, implementing code, and Android.
• The district court initially held that the asserted Java API structure was not copyrightable.
• The Federal Circuit reversed that ruling and ordered a fair-use trial.
• A 2016 jury found Google’s copying to be fair use.
• The Supreme Court affirmed Google’s victory in 2021.
• Oracle received no damages, royalty, injunction, or public settlement payment.
• The patent claims did not produce a final commercial remedy.
• The decision is a major precedent for software APIs, interoperability, and fair use.
• The case has no Orange Book, FDA, generic, biosimilar, or pharmaceutical exclusivity implications.

FAQs About Oracle America v. Google

Did Oracle win any part of the case against Google?

Oracle obtained favorable rulings on some intermediate issues, including the Federal Circuit’s 2014 holding that the Java API material could be copyrightable. Google ultimately prevailed on fair use, and Oracle recovered no damages.

How much did Google pay Oracle after the Java API lawsuit?

Google paid no publicly ordered damages in the case. The Supreme Court’s 2021 fair-use ruling eliminated Oracle’s claim for monetary recovery.

Did the Supreme Court hold that APIs are never copyrightable?

No. The Court assumed that the Java API declarations were protected for purposes of its decision and resolved the dispute on fair use. The ruling did not establish that all APIs are uncopyrightable.

Can companies copy Java APIs after the Supreme Court decision?

The decision does not authorize unrestricted copying. It supports a fact-specific fair-use analysis. The purpose of copying, amount used, functional constraints, interoperability value, and market effect remain relevant.

Did Oracle’s lawsuit affect Android distribution?

No injunction was issued. Android continued to be distributed, and the final judgment did not require Google to remove the Java APIs, pay a royalty, or redesign Android.

References

1. Google LLC v. Oracle America, Inc., 141 S. Ct. 1183 (2021).

2. Oracle America, Inc. v. Google Inc., 750 F.3d 1339 (Fed. Cir. 2014).

3. Oracle America, Inc. v. Google Inc., 872 F. Supp. 2d 974 (N.D. Cal. 2012).

4. Oracle America, Inc. v. Google Inc., No. 3:10-cv-03561-WHA, U.S. District Court for the Northern District of California, docket records.

5. U.S. Copyright Act, 17 U.S.C. § 107.

6. U.S. Patent and Trademark Office. (Various years). U.S. Patent Nos. 5,966,702, 6,061,520, and 7,426,720.