Patent Pledge

A patent pledge (also called a non-assertion pledge, patent non-assertion covenant, open patent commitment, or PAX) is a voluntary, public commitment by a patent holder not to assert specified patents against defined classes of users or activities. Unlike a patent license (which grants affirmative rights to practice the patent), a pledge is typically structured as a 'covenant not to sue' — the patent holder promises not to bring an infringement action against qualifying users. Key characteristics of patent pledges: (1) Voluntary: no statute requires them. Patent holders make pledges for strategic reasons — to build community goodwill, accelerate adoption of their technology or standards, attract open-source developer ecosystems, or participate in defensive patent networks. (2) Unilateral: most pledges are one-way — the patent holder commits without requiring the recipient to do anything in return (though defensive termination clauses may condition the pledge on non-assertion by the recipient). (3) Public: pledges are typically announced publicly (blog posts, company websites, formal agreements) and often recorded or registered with networks like OIN or LOT. (4) Scope-limited: pledges cover defined patents (specific lists, 'Linux System' patents, patents related to a standard) and defined uses (open-source software, good-faith use, member-to-member use in a network). Patents outside scope remain assertable. (5) Survivability varies: whether a pledge binds subsequent patent purchasers depends on whether it is recorded, structured as a prior license, or part of a network agreement that the purchaser takes subject to. Famous examples: Google Open Patent Non-Assertion Pledge (specific listed patents, open-source use); Tesla patent pledge (all Tesla patents, good-faith EV use); IBM's 500-patent pledge; LOT Network (defensive against NPE assertions); Open Invention Network (Linux System patents cross-license).

The legal enforceability of patent pledges varies significantly depending on how they are structured. Legal theories for enforcement: (1) Promissory estoppel: a user who relied on a pledge to their detriment (e.g., invested resources in building on the pledged technology, declined alternative designs) may be able to invoke promissory estoppel to prevent the pledgor from asserting the pledged patents. This requires showing: (a) a clear promise not to sue; (b) reasonable and foreseeable reliance by the promisee; (c) detriment resulting from reliance. (2) Breach of contract: if the pledge was made as part of a formal agreement (as in OIN membership agreements or LOT Network membership), it is contractually binding on signatories. Well-structured programs like OIN have explicit license agreements that are legally binding. (3) Equitable estoppel: if the patent holder made a representation that the user would not be sued, the user relied on it, and the patent holder unreasonably waited before asserting the patents, equitable estoppel may bar the assertion. (4) Recorded license / prior encumbrance: a pledge structured as a recorded license (or covenant not to sue recorded with the USPTO) may bind subsequent purchasers who take with notice. Practical enforceability risks: (a) Informal pledges (like Tesla's) made via blog post without a formal agreement may be harder to enforce if the pledgor later asserts the patents — enforcement would depend on promissory estoppel or equitable estoppel, which require proof of reliance and detriment. (b) Pledges without specified duration may be revocable before reliance. (c) If the patent is sold to an entity that did not sign the pledge or take it with notice, the new owner may not be bound. Bottom line: formal program memberships (OIN, LOT) are the most legally durable. Informal corporate pledges vary — users relying on them should document their reliance and assess whether the pledgor has the legal structure in place to make the pledge durable.

The LOT Network (License on Transfer, lotnet.com) is a defensive patent program designed to prevent operating company patents from being sold to non-practicing entities (NPEs) and then asserted against other operating companies. How it works: (1) Membership: companies join LOT by signing the LOT Agreement — a standardized legal agreement. Over 3,600 companies are members as of recent data, including Google, Amazon, Microsoft, GitHub, Dropbox, TSMC, and Waymo. (2) The license-on-transfer mechanism: when a LOT member transfers any patent to a NON-LOT-member entity (including an NPE, patent aggregator, or any party not in the LOT community), all current LOT members automatically receive a royalty-free, worldwide license to that transferred patent for their products and services. The license attaches at the moment of transfer. (3) Result: the transferred patent cannot be used to sue other LOT members, even after it leaves the original member's hands. The NPE that acquires the patent has already-licensed LOT members — making assertion against LOT members commercially unattractive. (4) What LOT does NOT do: it is not a cross-license among members — operating company members can still sue each other (LOT only covers the NPE transfer scenario). It does not cover patents transferred within the LOT community (member-to-member transfers don't trigger the license-on-transfer mechanism for the entire community). It only applies to transfers occurring AFTER the patent holder joined LOT — patents transferred before membership was established are not covered. Cost: LOT membership is tiered by company revenue — free for companies under $25M revenue; fees for larger companies. The program is administered by LOT Network, Inc., a non-profit.

The Open Invention Network (openinventionnetwork.com) is the largest patent non-aggression community in the world, focused specifically on protecting the Linux ecosystem from patent assertion. Founded in 2005 by IBM, Novell, Philips, Red Hat, Sony, and Google, OIN now has over 3,000 members. How OIN works: (1) Any company or individual can join OIN at no cost by signing the OIN License Agreement. (2) All OIN members grant all other OIN members a royalty-free, worldwide, non-exclusive license to their patents that read on the 'Linux System' — a defined set of open-source software packages that OIN maintains and updates. The Linux System definition includes the Linux kernel, core GNU utilities, major Linux distributions, and hundreds of other open-source packages. (3) In exchange, each member receives royalty-free licenses from all other members for the same Linux System patents. The result is a large commons of Linux-related patents that all members can use without paying each other. (4) Non-members are NOT covered — OIN members retain the right to assert their Linux-related patents against non-members. Companies that use Linux commercially without joining OIN have no OIN protection. (5) OIN itself acquires patents and licenses them royalty-free to members, adding to the commons. What OIN does NOT cover: patents outside the defined 'Linux System' scope; OIN members can still assert non-Linux patents against anyone, including other OIN members; OIN does not cover Windows, macOS, Android (Android has its own separate patent ecosystem), or proprietary software. Strategic relevance: any company using Linux in commercial products should evaluate OIN membership — particularly companies in automotive (Linux is widely used in vehicle infotainment), IoT, servers, and cloud infrastructure.

Companies make patent pledges for several strategic reasons, even though pledges represent a limitation on their ability to assert their patent portfolio: (1) Ecosystem development: tech companies with platform businesses (Google Android, Tesla EV technology, IBM mainframes) benefit from a broad developer and adopter ecosystem. Pledging patents removes the fear of assertion that might otherwise deter developers from building on the platform. Tesla's 2014 pledge was explicitly designed to accelerate overall EV adoption — Tesla benefited from a larger EV market even if competitors used their technology, because a bigger EV market increased charging infrastructure, favorable regulations, and consumer acceptance that benefited Tesla too. (2) Standards participation: contributing to technical standards (Wi-Fi, LTE, Bluetooth, USB, Ethernet) often requires agreeing to license essential patents on FRAND terms. Pledges formalize this commitment and encourage standards adoption. (3) Defensive positioning: LOT Network and OIN are explicitly defensive — they reduce the risk of NPE assertion against the member by reducing the supply of patents available to NPEs (LOT) or by creating a protected commons (OIN). A company that joins LOT is essentially agreeing not to feed NPEs with its patents, in exchange for protection from other members' patents falling into NPE hands. (4) Public relations and recruiting: pledging patents signals goodwill toward open-source communities, which can improve developer relations and recruiting. Google and IBM have benefited reputationally from open patent programs. (5) Competitive strategy against incumbents: companies with disruptive technologies may pledge patents to encourage adoption against established incumbents — removing IP risk lowers the barrier for customers and partners to switch. (6) Regulatory risk management: in industries under antitrust scrutiny, patent pledges can demonstrate that the company's IP strategy is not exclusionary.