In the previous installments of this series, we discussed general drafting strategies for standard-essential patent (SEP) applications and explored considerations related to inventive step. This third article addresses another powerful tool in the SEP drafter’s toolkit: the use of parallel technical solutions. Given the inherent uncertainty in standard-setting processes—where multiple competing proposals may be considered, and the final adopted solution remains unknown for years—drafting claims to cover multiple potential implementation options can significantly enhance the likelihood of achieving essentiality.
What Are Parallel Technical Solutions?
Parallel technical solutions refer to multiple alternative technical approaches that address the same problem, written into a single patent application. In the context of standards-related drafting, these are often expressed using language such as “at least one of: A, B, C, D” or “selected from the group consisting of.” A seemingly simple list of four elements can generate over a dozen distinct technical combinations, providing broad coverage of potential standardization directions. This drafting technique is particularly valuable in telecommunications, where standards bodies may ultimately select any one of several competing technical solutions to include in the final specification.
Why Use Parallel Technical Solutions in Standards-Related Applications?
The primary advantage of incorporating parallel technical solutions lies in flexibility. As a standard evolves through proposal, drafting, and approval stages, the technical direction may shift. By including multiple potential solutions in the original application, the applicant preserves the ability to later amend claims to match the final adopted standard without adding new matter or losing earlier priority dates.
Parallel solutions also provide significant benefits during post-grant proceedings. Under applicable patent office guidelines, one permitted amendment in invalidity proceedings is the deletion of a technical solution from a claim that contains multiple parallel alternatives. If a particular embodiment is challenged as unsupported or invalid, the patentee can delete that solution while maintaining the validity of the remaining ones. This structural flexibility helps preserve patent robustness over time.
Additionally, drafting parallel solutions within a single application reduces overall filing costs compared to filing multiple separate applications covering the same inventive concept. This efficiency is particularly attractive when building a portfolio around a standard where multiple technical directions remain plausible.
Managing the Quantity of Parallel Solutions
While it may be tempting to include every conceivable alternative, excessive parallel solutions can introduce significant drawbacks. Overly complex claim structures become difficult to read, confusing for examiners, and challenging to enforce. Nesting multiple “at least one of” clauses within each other, combined with “and/or” expressions, can produce claims that are logically intricate and prone to ambiguity.
Therefore, applicants should exercise judgment in selecting which parallel solutions to include. The goal is not maximum quantity but reasonable coverage of technically plausible standardization paths. Solutions that lack technical merit, are unlikely to be adopted, or are already covered by prior art can be safely omitted. A focused set of well-considered alternatives is far more valuable than an exhaustive but unwieldy list.
Structuring Claims for Parallel Solutions
Where possible, applicants should first attempt to capture parallel solutions through appropriate generalization or abstraction. A well-drafted independent claim can cover multiple specific implementations through a single broader limitation, provided the specification supports the generalization. This approach avoids the complexity of enumerating numerous specific alternatives while still preserving coverage.
When generalization is not feasible, the drafter must consider whether the parallel solutions share a single inventive concept sufficient to satisfy unity of invention requirements. If the alternatives address the same technical problem and are linked by a common inventive concept, they can be included in the same application. In such cases, the drafter may choose to present each parallel solution as a separate independent claim or combine them within a single claim using disjunctive language.
Regarding claim dependency, tree-like referencing is generally preferred over chain-like referencing when multiple parallel solutions are involved. Tree dependencies—where multiple dependent claims each directly refer to the same independent claim—create clear branch structures that are easy to navigate. Chain dependencies, where each claim references the previous one in sequence, can become overly complex and increase the risk of logical errors when parallel solutions are numerous.
Drafting the Specification to Support Parallel Solutions
A specification that adequately supports parallel technical solutions requires careful planning. Each alternative solution should be described with sufficient detail, including its specific technical implementation and the resulting technical effects. The specification should also highlight the differences and similarities among the alternatives, explaining when one solution might be preferred over another based on application scenarios or performance considerations.
However, not every alternative requires equal treatment. Drafters should allocate more detailed description to solutions that are more likely to be adopted or that represent the core inventive concept, while giving leaner support to less probable alternatives. This differentiated approach prevents the specification from becoming overly long, repetitive, or difficult to read, while still ensuring that each claimed solution has proper support in the original disclosure.
Where multiple embodiments can be combined, the specification should make the basis for such combinations clear. General statements such as “embodiments may be combined unless incompatible” provide some flexibility, but for important combinations, a more explicit description is advisable—perhaps presenting the combination as a separate embodiment. This proactive approach reduces the risk of later amendments being rejected for adding new matter.
Practical Example
Consider a patent application relating to a signaling field in a control message. The standard may ultimately adopt one of several approaches: using a dedicated field for a first parameter, reusing an existing field with a new interpretation, or encoding the parameter jointly with another value. A well-drafted application might include all three approaches as parallel solutions in a single claim, supported by corresponding embodiments in the specification. As the standard evolves and the adopted approach becomes clear, the applicant can amend the claims to focus on that specific solution—or maintain the broader claim if it still reads on the standard—without losing the benefit of the original filing date.
Coming Up in This Series
In the next installment of this series, we will address drafting considerations related to amendments that go beyond the original disclosure—a critical issue when adjusting claims to align with a final standard. We will explore common pitfalls such as improper term substitutions, combining embodiments without basis, and introducing new technical features. Future articles will also cover the importance of claim clarity in standards-related applications, particularly when emerging technologies such as artificial intelligence are incorporated into communication systems. Stay tuned for practical guidance aimed at helping applicants build robust, adaptable, and standards-ready patent portfolios.
Source: Guidelines for Invention Patent Applications Involving Standards, China National Intellectual Property Administration (CNIPA).
鄂公网安备 42010402001546号