Examples
Worked examples
- Is an instance
A university engineering patent reading on a communications standard is licensed into a third-party-administered standard-essential-patent (SEP) pool alongside patents from other companies and institutions, so implementers get one license covering the whole standard.
- Is an instance
A university licenses a diagnostic-method patent into a humanitarian patent pool (e.g., the Medicines Patent Pool model) on a geography-limited basis for generic manufacture in lower-income markets, while retaining exclusive commercial rights elsewhere.
Counter-examples
Looks similar, but isn't
- Not an instance
A university licenses a single, freestanding patent family exclusively to one company worldwide, with no other rights-holder's patents implicated -- this is an ordinary bilateral exclusive license, not a patent pool.
Editorial commentary
A patent pool is an arrangement among two or more patent holders — which can include a university, a company, or several of each — to combine a defined set of patents into a single licensing package, usually administered by a common licensor or a separate pool-management entity, so that a prospective licensee can obtain rights to every pooled patent through one transaction instead of negotiating a separate license with each holder. In university technology licensing, this is a distinct arrangement from the far more common bilateral exclusive or non-exclusive license covered in CASRAI’s license agreement structure guide and the exclusive vs. non-exclusive license comparison: a pool exists specifically because no single patent holder, including the university, can grant a licensee everything it needs to actually use a technology.
What makes something an instance of a patent pool
Three elements together distinguish a patent pool from other multi-party IP arrangements:
- Multiple independent patent owners. The pooled patents are not all owned or co-owned by the same entity — they come from separate rights-holders (a university, one or more companies, sometimes other universities) who would otherwise each require a separate license negotiation.
- A single licensing point of entry. A licensee can acquire rights to the whole pool (or a defined subset needed for a particular use) through one agreement and one royalty stream, typically via a joint venture, an independent pool administrator, or a lead licensor acting on behalf of the group — rather than stacking separate bilateral licenses.
- A shared or coordinated royalty/allocation mechanism. Royalty income collected from licensees is divided among the pool members according to a pre-agreed formula (often weighted by patent essentiality, filing date, or negotiated share), distinguishing a pool from a simple patent-assignment or patent-sale transaction.
Patent pools are most often formed around standard-essential patents (SEPs) — patents that necessarily read on a technical standard, so that any implementer of the standard infringes all of them unless licensed. The best-known commercial examples are administered by licensing agents such as MPEG-LA and Via Licensing for video-codec and wireless standards. Universities participate in this model less often as pool founders and more often as patent contributors: a university holding a foundational patent that reads on an emerging standard (for example, in genomics sequencing methods, certain biotechnology platform technologies, or communications protocols) may license into an existing or newly forming pool rather than, or in addition to, licensing bilaterally.
A second, distinct category relevant to universities is the humanitarian or public-health patent pool, exemplified by the Medicines Patent Pool (established by UNITAID), which negotiates voluntary licenses — including from some university-owned patents on drug compounds and diagnostics — for generic manufacture and distribution in low- and middle-income countries under geography- and field-limited terms. This model is closer to a licensing-in mechanism for global-access terms than a royalty-sharing commercial pool, but it uses the same underlying pooled-license structure.
When cross-licensing multiple patents makes sense for a university TTO
A technology transfer office should generally consider a patent-pool or multi-party cross-license structure — rather than a standard bilateral license — when one or more of the following is true:
- Patent thickets block practical use of the technology. If a company cannot practice the university’s patent without also infringing patents held by other institutions or companies (a common situation in synthetic biology, gene-editing platform technology, and complex biotech tool patents built on layered, overlapping claims), licensing the university’s patent alone does not give the licensee freedom to operate. A pool or coordinated cross-license clears the whole thicket in one transaction.
- The technology is being positioned as, or has become, part of a formal standard. Once a technical standard incorporates patented methods from multiple contributors, the standard-setting organization typically requires FRAND (fair, reasonable, and non-discriminatory) licensing commitments from each patent holder, and a pool is the practical mechanism for implementers to actually obtain freedom to operate without dozens of separate negotiations.
- Transaction costs of separate bilateral deals would exceed the value captured. Negotiating, monitoring, and enforcing many small bilateral licenses across many rights-holders is expensive for both licensors and licensees; pooling amortizes that cost and can increase overall licensing uptake and royalty capture for a patent that, held back for exclusive bilateral deals, might otherwise go unlicensed.
- Broad, non-discriminatory access serves the university’s mission better than exclusivity. For platform or foundational technologies where broad downstream use (by many companies, or for humanitarian/public-health access) advances the university’s research and public-benefit mission more than a single exclusive licensee would, pooled or field-limited multi-party licensing can be the better institutional fit — a rationale CASRAI covers more generally in open innovation networks.
Conversely, a pool is generally the wrong structure — and a standard bilateral exclusive or non-exclusive license is preferable — when the university holds a single, freestanding patent family that a licensee can practice without needing rights from any other patent holder, or when the university’s licensing objective is to secure a single well-resourced exclusive partner to fund late-stage development (the scenario CASRAI’s exclusive vs. non-exclusive license comparison addresses directly).
Worked examples
Example 1 — standard-essential patent pool. A university’s engineering department holds a patent on a signal-compression method that a industry standards body later incorporates into a communications standard. Multiple other companies and institutions hold patents reading on the same standard. Rather than each company implementing the standard negotiating separately with every patent holder, the university joins an existing patent pool administered by a third-party licensing agent, which grants implementers a single license to the full standard-essential patent portfolio and distributes royalties among contributors according to an agreed allocation formula.
Example 2 — humanitarian licensing pool. A university holds a patent covering a diagnostic method relevant to a disease disproportionately affecting low-resource settings. The TTO licenses the patent into a public-health patent pool on a geography-limited, royalty-modest basis for generic manufacture in defined lower-income markets, while retaining the ability to license the same patent bilaterally and exclusively for commercial markets in higher-income countries — a field-of-use and territory split that a pooled structure makes administratively practical.
Counter-example
A university licenses a single patent family covering a specific small-molecule compound exclusively to one pharmaceutical company for worldwide development, with no other rights-holder’s patents implicated in practicing the invention. This is an ordinary bilateral exclusive license, not a patent pool — there is only one licensor, one licensee, and no shared royalty-allocation mechanism among independent rights-holders. See CASRAI’s license agreement structure guide for how this more common transaction is structured.
Related terms
- Open Innovation Networks — the broader multi-party knowledge-sharing category patent pools sit within.
- Exclusive License vs. Non-Exclusive License — the bilateral licensing structures a pool is an alternative to.
- License Agreement Structure — grant-of-rights and royalty mechanics for a standard single-licensor license.
- Research Collaboration Agreement (RCA) — governs joint research inputs, distinct from the resulting patents’ post-hoc pooled licensing.
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="Patent Pool"
vocab-term-identifier="https://casrai.org/dictionary/term/patent-pool" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/patent-pool",
"name": "Patent Pool",
"identifier": "https://casrai.org/dictionary/term/patent-pool",
"description": "A patent pool is an arrangement among two or more independent patent holders -- which can include a university technology transfer office -- to combine a defined set of patents into a single licensing package administered through one licensor or pool entity, so a licensee can obtain rights to every pooled patent in one transaction, with royalties divided among members by a pre-agreed allocation formula. Distinct from a standard bilateral exclusive or non-exclusive license, which involves a single licensor.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/tech-transfer#set",
"url": "https://casrai.org/dictionary/term/patent-pool",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"dateModified": "2026-07-24T06:38:18",
"inLanguage": "en"
}






