Tag Archives: Microsoft

Rise of OpenAI in the Patent System

by Dennis Crouch

The chart below is on a log scale to help fit the pieces together, but it is interesting to see how OpenAI has risen so rapidly in patent applications. Because of the publication delay, the solid lines run through the end of 2024. The dotted segments that follow cover filing months where publication is still incomplete.

Percentage of published U.S. utility patent applications naming Microsoft, Google, IBM, Hewlett-Packard, Adobe, and OpenAI, by filing month, 2005 through 2025

Reference to Microsoft has remained at roughly 4% of all utility applications for twenty straight years, a nearly flat line running through the mobile transition, the decline of Windows as a share of computing, and the shift to cloud services. Google starts at 0.15% in 2005, passes IBM around 2011, and closes most of the remaining gap on Microsoft by the end of the series. IBM peaks near 2.2% in 2008 and drifts down to about 1.2%. Adobe peaks around 2011 and falls off from there. Hewlett-Packard runs the opposite path, starting near 0.9% in 2005, dropping below Adobe around 2009, and ending at about 0.2%. OpenAI went from nothing to passing both Adobe and Hewlett-Packard in about six years of measurable activity.


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Cleaning House: Director Squires Responds to Examiner Conflict-of-Interest Scandal

by Dennis Crouch

Last week I reported on the $500,000 settlement between the Department of Justice and patent examiner Daxin Wu, who allegedly examined at least nine patent applications from companies in which she held substantial stock positions—including holdings exceeding $300,000 in one company—and reviewed applications from competitors of a company in which she held more than $900,000 in stock. Dennis Crouch, Patent Examiner Pays $500K for Financial Conflicts — But the Real Story may be Systemic, Patently-O (Feb. 26, 2026). That post traced the enforcement action back to a damning 2024 Inspector General report estimating that roughly 2,100 patent examiners—about 30% of those required to file financial disclosures—had potential financial conflicts that went undetected. U.S. Dep't of Commerce, Office of Inspector General, The Department Needs to Strengthen Its Ethics Oversight for USPTO Patent Examiners, Final Report No. OIG-24-013-I (Feb. 14, 2024). Today, Director John Squires has responded. In a memorandum dated March 2, 2026 and addressed to all employees in the Office of the Commissioner for Patents, Director Squires directs that any Patents employee who participates in deciding the scope of patent rights must affirmatively recuse from examining any application where they hold stock or bonds—publicly traded or privately held—in any listed applicant, regardless of the dollar value of those holdings. Director Squires' memo on examiner stock ownership.


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Who Decides When Construction Is Needed? Comcast Seeks Supreme Court Review of O2 Micro’s Limits

by Dennis Crouch

Comcast has asked the Supreme Court to review whether the Federal Circuit violated fundamental principles of party presentation when it held that a district court "legally erred" by not construing patent claim terms that the patentee had successfully argued required no construction. The petition in Comcast Cable Communications, LLC v. WhereverTV, Inc., No. 25-___ (filed Jan. 2026), frames the issue as a conflict between the Federal Circuit's O2 Micro doctrine and the Supreme Court's recent reaffirmations of adversarial limits on judicial power. At its core, the case presents a doctrinally neutral question: when a party deliberately waives an issue before the district court, can the appellate court override that strategic choice and decide the issue anyway?  


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Federal Circuit Vacates Denial of Anti-Suit Injunction in FRAND Dispute, Clarifying “Dispositive” Analysis

Dennis Crouch

The Federal Circuit has vacated the E.D.N.C. Judge Boyle’s denial of an anti-suit injunction in a major FRAND licensing dispute between Ericsson and Lenovo. Telefonaktiebolaget LM Ericsson v. Lenovo (United States), Inc., No. 24-1515 (Fed. Cir. Oct. 24, 2024). The decision provides important guidance on when U.S. courts should issue anti-suit injunctions to prevent SEP holders from enforcing foreign injunctions while FRAND obligations are being adjudicated domestically.  Importantly, the Federal Circuit adopted the Ninth Circuit test from Microsoft Corp. v. Motorola, Inc., 696 F.3d 872 (9th Cir. 2012), and added some further refinement making anti-suit injunctions easier to obtain. (more…)

The AGI Lawsuit: Elon Musk vs. OpenAI and the Quest for Artificial General Intelligence that Benefits Humanity

By Dennis Crouch

Elon Musk was instrumental in the initial creation of OpenAI as a nonprofit with the vision of responsibly developing artificial intelligence (AI) to benefit humanity and to prevent monopolistic control over the technology. After ChatGPT went viral in late 2022, the company began focusing more on revenue and profits.  It added a major for-profit subsidiary and completed a $13+ billion deal with Microsoft -- entitling the industry giant to a large share of OpenAI's future profits and a seat on the Board. 

In a new lawsuit, Elon Musk alleges that OpenAI and its CEO Sam Altman have breached the organization's founding vision. [Musk vs OpenAI]. 


To continue reading, become a Patently-O member. Already a member? Simply log in to access the full post.

Microsoft, Corel, and the “Article of Manufacture”

Guest Post by Sarah Burstein, Associate Professor of Law at the University of Oklahoma College of Law (Tweet @design_law)

Microsoft v. Corel, Order Regarding Post-Trial Motions (N.D. Cal. 2018)

A district judge recently issued a decision that—if affirmed by the Federal Circuit—could have major implications for design patent law and policy.

Microsoft accused Corel of infringing five utility patents and four design patents. The four design patents all claimed designs for particular elements of the Microsoft Office graphical user interface (GUI). The images below show each of the claimed designs, along with a corresponding image of an accused product (images source: Microsoft’s complaint):

Corel initially denied infringing these design patents but, early last year, it amended its answer to admit infringement and dismiss most of its defenses, stating that, “to properly develop and prove out those defenses will simply cost more than the damages could rationally be in this case.” By the time of trial, the only remaining issues were damages, whether Corel had pre-suit notice of three of the design patents, and willfulness.

In its Rule 50 motions, Corel argued that Microsoft was not entitled to recover its “total profits” under 35 U.S.C. § 289 because Corel had not applied the patented designs to any articles of manufacture.

Section 289 provides a special disgorgement remedy for certain acts of design patent infringement. (For more on what § 289 does and doesn’t cover, see FN 74 here.) It provides that:

Whoever during the term of a patent for a design, without license of the owner, (1) applies the patented design, or any colorable imitation thereof, to any article of manufacture for the purpose of sale, or (2) sells or exposes for sale any article of manufacture to which such design or colorable imitation has been applied shall be liable to the owner to the extent of his total profit, but not less than $250, recoverable in any United States district court having jurisdiction of the parties.

Nothing in this section shall prevent, lessen, or impeach any other remedy which an owner of an infringed patent has under the provisions of this title, but he shall not twice recover the profit made from the infringement.

35 U.S.C. § 289.

Corel noted that each of Microsoft’s design patents claimed an “ornamental design for a user interface for a portion of a display screen, as shown and described…” Corel argued that the relevant article of manufacture for each of the design patents was, therefore, a display screen. Sine Corel had not sold any display screens, it argued, there were no applicable profits for Microsoft to recover.

Corel also argued that its software products did not themselves constitute “articles of manufacture.”

Microsoft argued that each of its patents claimed a design “for a user interface for a portion of a display screen” and argued that, in its stipulation of infringement, Corel had “admitted that its products include[] the claimed interface.” Microsoft also argued that software does qualify as an “article of manufacture,” relying mainly on the Supreme Court’s statement in Samsung v. Apple that “[a]n article of manufacture . . . is simply a thing made by hand or machine.” Therefore, according to Microsoft, it was entitled to recover the “total profits” from Corel’s infringing software pursuant to § 289.

The district court agreed with Microsoft. According to Judge Davila, Corel waived its “article of manufacture” arguments because it “already admitted that its products. . . infringe” the design patents. Judge Davila further decided that, even if the arguments weren’t waived, “[s]oftware is a ‘thing made by hand or machine,’ and thus can be an ‘article of manufacture,” citing Samsung. The judge further stated that Corel’s arguments about the claim language were “misplaced” because the claimed design was “broad enough that it could be ‘applie[d]’ to software.”

Both of these conclusions deserve closer attention.

The admission of infringement

As noted above, Corel admitted that its software infringed Microsoft’s design patents. According to the court, this meant that “Corel has already admitted there exists an ‘article of manufacture’ to which the patented designs . . . have been applied.” It’s not entirely clear why the court reached this conclusion. But, reading the discussion as a whole, it appears that the court may have been laboring under the (unfortunately, somewhat widespread) misapprehension that § 289 sets forth the standard for design patent infringement. In other words, it appears that the court may have been under the mistaken impression that design patent infringement occurs only when the patented design is applied to an article of manufacture.

To be fair to the court, there is some dicta floating around to that effect. But, as Microsoft argued, it is § 271 that sets forth the standard for infringement of design patents – just like it does for utility patents.

In theory, someone could infringe a design patent by, for example, inducing someone else to use a patented design without themselves applying the design to any “article of manufacture” or selling an article to which the design has been applied. One reason for this is that we don’t yet have a clear conception of what it means for a design to be “applied” to an article. This decision highlights the need for more clarity in this area. (For my own views on what “applied” should mean, see here.)

The court also seems to conflate the digital instructions for rendering a design from the actual visual design itself. In copyright law, we distinguish between the code (a literary work) and the visual design displayed by the work (an audiovisual or PGS work). That distinction might be helpful in understanding the issues in these GUI design patent cases. Effectively, Judge Davila’s ruling allows for the protection of the process used to display these designs, as opposed to the designs themselves. If upheld, this could have major implications for the protection of CAD files used in 3D printing.

Software as an “article of manufacture”

The court’s alternate conclusion—that software can be an “article of manufacture”—is both surprising and, if upheld on appeal, could have far-reaching implications.

Section 171 provides for the grant of a design patent for “any new, original and ornamental design for an article of manufacture.” There does not seem to be any good reason to interpret the phrase “article of manufacture” differently in § 289 than in § 171. (While some scholars have argued that the scope of GUI design patents should not be limited based on their verbal claims, the—admittedly scarce—case law suggests otherwise. This article collects all the relevant cases I could find as of 2015; here is another, more recent, decision.)

The question of whether a GUI design is, in fact, a “design for an article of manufacture” has never actually been decided by a court. According to the USPTO, a GUI claim “complies with the ‘article of manufacture’ requirement” if the GUI is claimed as “shown on a computer screen, monitor, other display panel, or a portion thereof.” MPEP § 1501.(a). At least in the view of the USPTO, the relevant article is the screen. Of course, this interpretation has not, however, been considered—let alone ratified—by any court. And Corel didn’t mention any of this to Judge Davila. But it’s notable how starkly the court’s reasoning in Microsoft contrasts with the USPTO’s reasoning in allowing this type of patent in the first place.

The Microsoft ruling also stands in striking contrast with Apple’s arguments in its currently-pending retrial against Samsung. Apple is arguing that the relevant article for its GUI patent is the complete Samsung phone, not the software installed thereon. It would seem odd to say that the relevant article of manufacture for a GUI is the software unless the defendant happens to sell its software bundled with a piece of hardware—especially since the Supreme Court rejected the Federal Circuit’s rule that the relevant article is whatever the defendant sells. And if it seems strange to treat Corel and Samsung differently with respect to § 289, that may suggest a deeper flaw in the reasoning the USPTO used to grant design patents for GUIs in the first place.

In any case, if the Federal Circuit affirms the decision that software can be an “article of manufacture,” that would be a major change to U.S. design patent law.

It could also have implications for utility patent law. The phrase “article of manufacture” in the design patent statutory subject matter provision has long been understood to be synonymous with the term “manufacture” in the utility patent subject matter provision. (For more on the longstanding equation of these terms, see here.) One notable exception is In re Nuijten, where the majority rather clumsily tried to distinguish a CCPA design patent case, In re Hruby, on the way to deciding that only tangible items can be “manufactures” under § 101. (Neither Corel nor Microsoft mentioned Nuijten in their “article of manufacture” briefing.)

Eventually, the Federal Circuit will need to sort all of these issues out. But this decision demonstrates how urgent the need is for clarity—and clear thinking—in this space.