Patent Layout for Future Standards: How to Strategically Position Claims Before Standards are Set

The High-Stakes Race to the Standard: Why Your Patent Strategy Must Lead the Committee

The most expensive mistake a technology leader can make is waiting for a technical standard to be finalized before filing their most important patent claims. By the time a standard is published, the window to secure a Standard Essential Patent (SEP) has usually slammed shut, leaving you with a "nice-to-have" patent that the rest of the industry can simply ignore or design around.

Strategic patent positioning for future standards requires shifting from "protecting what we built" to "protecting where the industry is forced to go." Success depends on filing broad, flexible specifications early and using a rigorous divisional application strategy to refine claims as the Standard Setting Organization (SSO) debates evolve.

The "Standard First, Patent Later" Fallacy

In the world of 5G, Wi-Fi 7, or EV charging protocols, technical superiority does not guarantee market dominance. Influence does. Many founders believe that if their engineers win the debate at the SSO (like 3GPP or IEEE), the patents will naturally follow.

The reality is harsher. If you disclose your "killer feature" during a working group meeting to get it adopted into the standard before your priority date is secured, you have likely committed intellectual property suicide. You’ve created your own prior art. "Patent-first, standard-second" isn't just a catchy phrase; it is a defensive necessity to ensure that when your technology becomes the industry requirement, you hold the keys to the gate.

Timing the Golden Window: The SSO Proposal Cycle

Standardization is not a single event; it’s a multi-year marathon of proposals, debates, and revisions. To position your portfolio, you must map your filing activity to the SSO’s lifecycle:

1. The Study Item Phase: This is the "blue sky" period where the industry identifies a problem (e.g., "how do we reduce latency in VR?"). Your filings here should be broad, focusing on the fundamental architecture of the solution.
2. The Work Item Phase: This is the "Golden Window." Proposals are being debated. This is when you must file multiple embodiments covering not just your preferred method, but the alternative methods your competitors are proposing.
3. The Frozen Stage: Once the standard is "frozen," the technical specifications are set. Your job here is no longer innovating; it is "claim grooming"—using pending applications to ensure your claim language matches the final terminology of the standard.

The Multi-Route Drafting Technique

When you are filing a patent for a technology that might become a standard, you cannot afford to be precise about the final implementation. You need a "hydra" approach to claim drafting.

I often see founders file a patent that describes one perfect way to solve a problem. That is a mistake in the SEP world. If the committee chooses a slightly different path—say, using a 16-bit header instead of an 8-bit header, or a different polling frequency—your patent becomes non-essential.

How to fix this:

• Parallel Embodiments: Your specification must describe three or four different ways to achieve the same result.
• Functional Claiming: Use functional language in your independent claims (e.g., "a means for synchronizing data") while providing specific, varied examples in the description.
• The "Or" Strategy: Use dependent claims to cover every foreseeable variation the committee might vote for. If you think the standard might use Option A, B, or C, you should have dependent claims for A, B, and C.

The Power of the Divisional: Tracking the Evolution

In standard-heavy industries, the original "parent" patent application is rarely the one that ends up being the SEP. The real work happens through Divisional Applications.

Think of the parent application as a reservoir of technical ideas. As the standard evolves over two or three years, the language used by the engineers in the committee will change. They will invent new terms for old concepts. By keeping a "family" of divisional applications alive, you can wait until the standard is nearly finished, then draft a new set of claims that uses the exact terminology of the final standard (provided those concepts were supported in your original filing).

Strategist’s Note: Never let your patent family die while the standard is still in flux. Once the last application in a chain is granted or abandoned, your ability to "pivot" your claims to match the standard vanishes.

Risk Management: The Disclosure Trap

There is a natural tension between an engineer's desire to "win" a technical debate at an SSO and a strategist's desire to keep the IP secure. Most SSOs have strict "IPR Disclosure Policies."

If you propose a technology for a standard, you are often required to disclose any patents or pending applications you have that might be "essential." Furthermore, many SSOs require you to commit to FRAND (Fair, Reasonable, and Non-Discriminatory) licensing terms.

The Danger Zone: If you disclose a core technical secret in a proposal before your patent application is filed, you lose the ability to claim that secret globally. Even if you have filed, once you propose it to the standard, you may be locked into FRAND rates, which limits your "monopoly" pricing power. You must weigh the benefit of having your tech in the standard against the cost of losing exclusive control over it.

A Checklist for Standard-Ready Patents

Before your team heads to the next committee meeting, run your IP through this filter:

1. Support Check: Does our specification contain enough "alternative embodiments" to cover the competitor's likely counter-proposals?
2. Continuity Check: Do we have at least one pending application (a "placeholder") in this family to allow for future divisional filings?
3. Terminology Check: Are we using generic technical terms that can be mapped to the specific jargon the SSO eventually adopts?
4. Disclosure Check: Has the legal team reviewed the technical proposal to ensure every "secret" mentioned is already covered by a filed priority date?

Frequently Asked Questions

Q1: If my technology is better, won't it just be chosen for the standard anyway?

Not necessarily. Standards are often the result of political compromise and "patent counting" between giant players. A "good enough" technology with a strong coalition often beats a "perfect" technology that is siloed. Your patent strategy must account for the "good enough" path as well.

Q2: What is the benefit of a Patent Pool in this process?

A Patent Pool (like MPEG LA or Via LA) allows multiple SEP holders to license their patents as a single bundle. If your patent is truly essential to a standard, joining a pool can provide a steady stream of royalty revenue without you having to sue every individual implementer. However, you must first prove your patent is "essential" through an independent technical review.

Q3: Can I change my claims after the patent is granted to match the standard?

Generally, no. In most jurisdictions (like the US or Europe), you cannot broaden your claims after a patent is granted (with very limited exceptions in the US within the first two years). This is why the divisional strategy is so critical—you need a pending application to adjust your claims to the final standard.

Q4: Does filing a patent mean I have to share my technology with everyone?

If your patent becomes a "Standard Essential Patent," you generally have a legal obligation to license it to anyone who wants to implement the standard, provided they pay a FRAND rate. You can't "block" people from using the standard; you can only ensure you are paid fairly for their use of it.

---

Disclaimer: This article provides strategic oversight based on industry practice. Patent laws vary by jurisdiction and technical field. Always consult with a registered patent attorney to review your specific filings and SSO disclosure obligations before participating in standard-setting activities.