Can you license a post-quantum cryptography patent after NIST's royalty-free precedent?

NIST was explicit about which of those two choices it preferred. Its call said royalty-free availability had helped cryptographic standards get adopted in the past and that it would weigh intellectual property in the evaluation, with a strong preference for commitments to license without compensation. It said it did not object in principle to an algorithm that needed a patent claim, but that it would weigh anything that could hinder adoption.

For an owner, the consequence is that the submitters of the selected algorithms and the owners of the patents they identified made written commitments. Whether those commitments reach any particular patent depends on who signed, what they listed, and what they bound their successors to, which is why your counsel will want the statements themselves.

Two features of those licenses matter for every other owner. First, they are limited to a field of use: implementing the selected algorithm as published. They do not free the patents for every purpose. Second, they show what the market now expects. A buyer who implements a federal post-quantum standard will assume the standard is free to implement, and will treat any claim that reads on it as a question for its counsel rather than a licensing opportunity.

The precedent does not mean every post-quantum patent is worthless or free. It means the standardized core is the wrong place to look for royalties. The right places are the things the standards do not specify.

A schedule changes the buying conversation. Product teams at security vendors, cloud providers, payment networks, and device makers now have a dated requirement, an executive sponsor, and a budget line for meeting it. A patent that helps them meet the requirement faster, at lower cost, or with less risk speaks to a problem someone already owns.

The transition report is also candid about what it does not cover. Its patent notice says no patent claims had been identified to NIST as of publication, and that NIST makes no representation that licenses are not needed. Buyers' counsel read that the same way you should: as a reason to check, not as a clearance.

Each of these is a place a buyer has work to do on a schedule and may prefer a license to a build. Whether your claims actually reach one of them, and whether they also read on a standard, are questions for your counsel, asked separately. The commercial question is which buyer has the problem your claims solve, and how soon.

A good first message names the buyer's migration task, such as getting signatures onto a constrained device or carrying larger keys through an existing protocol, and the result the claimed method delivers. It does not lead with the patent number or claim that the patent covers a standard. The standards relationship belongs in the second conversation, in counsel's words.

Expect the buyer to compare licensing with building. Post-quantum engineering talent is scarce and the deadlines are fixed, which works in an owner's favor when the method saves real time. It works against an owner whose method a capable team could design around in a quarter.

The order matters because the second answer depends on the first. An owner who maps buyers before the standards question is settled can spend months on a use case the buyer's counsel will dismiss in a single call. An owner who settles the standards question first usually finds that a smaller set of use cases is clearly outside the standards, and that those are the ones worth leading with.

The buyer map for a post-quantum patent is also unusually concrete. The migration has named tasks, named deadlines, and named owners inside each buyer: the team responsible for the cryptographic inventory, the team responsible for certificates and keys, the team that ships the hardware or the protocol stack. A use case that maps to one of those owners and one of those deadlines is a use case a buyer can say yes to.

That is why we treat the standards question as the first commercial question for any security patent, not a legal footnote. The policies differ by body, and the answer for any particular patent turns on facts about its owners and its claims. Our checklist guide for the FIDO Alliance and web standards bodies sets out those facts.

Patenture works with owners of post-quantum and other cryptography patents whose product already ships, or whose claims reach well beyond their own product. The Licensing Reach Read maps where the claims reach beyond the owner's market, screens each opportunity against the owner's customers, partners, roadmap, and existing licenses, sets out a license structure per opportunity, and ranks the licensees, with questions for patent counsel on the standards relationship and a table of what the read did not settle.