- Client
- Telecommunications product company with a strong patent portfolio
- Origin of the filing
- Technical proposal submitted at a 3GPP standardization meeting
- Engagement
- Claim scope optimization & continuation strategy
- Outcome
- 4 proposed continuation claims: 1 broader + 3 implementation-specific
Executive summary
Making sure the patent covers how the standard will actually be built
Patents filed alongside a standards contribution are usually written early, before anyone knows exactly how vendors will implement the feature. The claims tend to mirror the wording of the proposal, which can tie the protection to one way of doing things.
Our client, a telecommunications product company, had filed an application corresponding to a technical proposal it submitted at a 3GPP standardization meeting. As the technology moved toward implementation, the client asked IIPRD to look again at the existing claims and to design continuation applications that would cover a broader range of implementation scenarios.
IIPRD reviewed every keyword and technical expression in the claims, tested each limitation for its functional significance, compared the claims against the full disclosure, and designed a layered set of four continuation claims.
Background
Why standards-linked patents need a second look
3GPP specifications are developed through technical contributions that member companies submit to working-group meetings. Companies often file a patent application around the time a contribution is submitted, so the filing date precedes public disclosure of the proposal. The claims are therefore drafted from the proposal as it stood on that day.
Proposals change as they move through discussion, agreement and specification. Vendors then implement the agreed feature in their own products, often in ways the original drafter did not anticipate. A claim that recites the exact message, channel or entity named in the proposal may not reach equivalent implementations that use different signaling or a different network element.
A continuation application lets the applicant pursue new claims based on the same disclosure, with the benefit of the parent's filing date, while the parent is still pending. That makes it a practical tool for aligning claim scope with how the technology is actually deployed.
- Technical proposalContribution prepared for a 3GPP meeting
- Original filingClaims drafted around the proposal's wording
- Specification evolvesDiscussion, agreement and refinement
- ImplementationVendors realize the feature in different ways
- Continuation claimsScope realigned to the underlying technology
General illustration of the standards-to-implementation path; it does not describe the client's specific timeline.
Problem statement
Protection that stopped at one implementation
A telecommunications product company with a strong patent portfolio had filed a patent application corresponding to its technical proposal submitted during a 3GPP standardization meeting. As the technology evolved toward implementation, the client sought to strengthen its patent protection by developing continuation applications that could cover a broader range of implementation scenarios.
The client wanted its protection to extend beyond the specific implementation described in the original claims to encompass alternative ways of implementing the underlying technology.
Engagement objectives
- Revisit the existing claims and assess the contribution of every keyword and expression to the scope of protection.
- Identify unnecessarily restrictive terminology that could narrow the range of covered implementations.
- Uncover implementation details in the disclosure that could support additional claim coverage.
- Design continuation claims that reach alternative ways of implementing the underlying technology.
Key challenges
Four problems to solve at once
Restrictive claim terminology
Certain keywords and technical expressions in the existing claims could unnecessarily limit the scope of protection.
Why it mattersA single narrow noun, such as a specific message or network entity, can let an implementation that uses an equivalent element fall outside the claim.
Understanding functional significance
Determining which claim limitations were essential to the technology's operation and which could potentially be broadened or omitted.
Why it mattersRemoving a limitation the invention depends on invites prior-art and support problems; keeping one it does not need gives away scope.
Identifying implementation gaps
Detecting relevant technical details and alternative implementation scenarios not adequately captured by the original claims.
Why it mattersContinuation claims can only claim what the original disclosure supports, so the gaps have to be found in the specification itself.
Developing a layered protection strategy
Designing continuation claims that balanced broader coverage of the underlying technology with protection directed toward specific implementation scenarios.
Why it mattersA broad claim alone faces greater validity risk; narrow claims alone may be designed around. The portfolio needs both.
Solution approach
Claim scope optimization & continuation strategy
The work ran in six stages, moving from individual words to the architecture of the full claim set.
-
Detailed keyword-level claim analysis
Examined every keyword and technical expression featured in the existing claims to understand its contribution to the claimed invention and its potential impact on the scope of protection.
What we examined
- Each noun, verb and qualifier in every independent and dependent claim
- Standards-specific terms carried over from the proposal
- Quantifiers, sequence words and conditional language
Output
- A term-by-term inventory of the claims, with each term's role in defining scope
-
Interpretation of claim terminology
Reviewed how individual keywords and expressions could be interpreted in the context of the claims and the overall technical disclosure. Identified terminology that could potentially introduce unintended restrictions or narrow the range of covered implementations.
What we examined
- How the specification uses and defines each term
- Whether a term reads only on one release, entity or message type
- Terms whose ordinary meaning in the field is narrower than intended
Output
- A list of terms flagged as potentially restrictive, with the reason for each flag
-
Assessment of functional significance
Evaluated the significance of each claim limitation in the overall functioning of the system. Distinguished between features central to the underlying technical concept and details associated with particular implementation choices.
What we examined
- Whether the system still achieves its technical effect without the limitation
- Which limitations reflect the inventive concept and which reflect a design choice
Output
- Each limitation classed as core to the concept or implementation-specific
-
Broadening and refinement of claim language
Identified opportunities to broaden selected terms, remove non-essential limitations where supported by the original disclosure, and refine claim language to capture the underlying technical functionality more comprehensively.
What we examined
- Generic or functional alternatives for flagged terms
- Support in the original disclosure for each proposed change
Output
- Proposed broader wording for selected terms, tied to supporting passages
-
Identification of missing implementation details
Compared the existing claims against the disclosed technology and relevant implementation scenarios to identify technical aspects that were not adequately represented in the original claim set.
What we examined
- Embodiments and alternatives described but not claimed
- Implementation scenarios relevant to how the technology is being deployed
Output
- A gap list of disclosed but unclaimed technical aspects
-
Development of a multi-layered continuation claim strategy
Designed four continuation claims with complementary coverage objectives: one broader claim directed toward the underlying technology across a wider range of implementation scenarios, and three additional claims directed toward specific implementations. This approach sought to establish broader protection while retaining implementation-specific coverage.
What we examined
- How the claims would work together as a set
- The coverage objective of each claim, so the set has no overlapping purpose
Output
- Four proposed continuation claims with defined, complementary objectives
Inside the keyword review
What restrictive terminology looks like in telecom claims
The table shows the kinds of wording a keyword-level review looks for in standards-related claims, and the broader direction a continuation claim might take where the disclosure supports it.
| Pattern | Restrictive wording | Broader direction | Why it matters |
|---|---|---|---|
| Named network entity | eNodeB | network node / base station | Ties the claim to one radio generation; later generations use different entity names. |
| Named device type | user equipment (UE) recited with a specific category | wireless communication device | Category-specific wording can exclude other device types implementing the same feature. |
| Specific signaling message | RRC reconfiguration message | higher-layer signaling | An implementation may carry the same information in a different message. |
| Specific channel | PDCCH | downlink control channel | Equivalent control information can be delivered on other channels or formats. |
| Fixed sequence | first … and then … | Steps without an imposed order, where order is not essential | Reordering steps can avoid a claim that requires a fixed sequence. |
| Exact quantity | two / each | at least one / one or more | Exact counts are easy to design around. |
Illustrative examples of common patterns only. They are not the client's claim terms, and any broadening must be supported by the original disclosure.
Breakthrough insight
The original claims did not capture the full scope available
The key insight was that the original patent claims did not necessarily capture the full scope of protection potentially available from the disclosed technology.
A systematic review of claim terminology, functional limitations, and implementation details revealed opportunities to refine the claim structure and develop a more comprehensive continuation strategy.
Rather than simply reproducing the original claims with minor modifications, IIPRD developed a four-claim approach combining a broader claim directed toward the underlying technological concept with three implementation-specific claims.
- Broader claim: aims to reach the underlying technology however it is implemented, within what the disclosure supports.
- Implementation-specific claims: fallback positions that each target a particular configuration.
- Original claim: tied closely to the implementation described when the application was filed.
- Conceptual illustration. Areas are not to scale and do not represent measured claim scope.
This layered strategy was designed to extend protection across multiple implementation scenarios while preserving targeted coverage for specific technical configurations. If the broader claim is narrowed during examination or challenged later, the implementation-specific claims remain as independent positions.
Impact on client
What changed for the client's portfolio
- Broader protection strategyDeveloped a broader claim directed toward the underlying technology, subject to support in the original disclosure.
- Implementation-specific coverageDesigned three additional claims targeting distinct implementation scenarios.
- Reduced dependence on restrictive terminologyIdentified opportunities to remove or broaden non-essential claim language where legally and technically supportable.
- Improved claim architectureEstablished complementary coverage objectives across the proposed continuation claims.
- Stronger long-term portfolio positioningCreated a structured basis for pursuing protection across alternative implementations of the technology.
Legal guardrails
The rules a continuation strategy has to respect
Broadening claims in a continuation is powerful but bounded. Under US practice, these are the main constraints the strategy was built around.
Copendency
A continuation must be filed while the parent application is still pending, before it issues as a patent or is abandoned.
Written description support
Every continuation claim must be supported by the parent's disclosure as filed. A broader term is only available if the specification shows the applicant possessed it.
Same disclosure
A continuation cannot add new technical content. New content requires a continuation-in-part, and those new claims only get the later filing date.
Terminal disclaimers
Claims that are obvious variants of the parent's claims may need a terminal disclaimer, which ties the continuation's term and ownership to the parent.
Earlier arguments carry over
Statements and amendments made in the parent's prosecution can affect how related claims in the family are interpreted.
Declarations and licensing
Claims that read on a standard may bring IPR declaration and FRAND licensing obligations under the relevant standards body's policy.
General information on US practice for context. Requirements differ by jurisdiction, and this is not legal advice.
Key takeaways
Lessons for standards-linked portfolios
- Patent claims should be evaluated at the level of individual limitations, not merely as complete technical descriptions.
- The functional significance of each limitation can help identify opportunities for claim refinement.
- Continuation strategy can be used to pursue different claim scopes based on the original disclosure and the evolving prosecution context.
- A combination of broader and implementation-specific claims can provide complementary layers of protection.
- For telecommunications inventions associated with standards development, claim strategy should account for both the underlying technical concept and the different ways the technology may be implemented.
- Keep the parent application pending while the standard and its implementations are still taking shape, so that continuation options remain open.
- Draft the original specification with alternatives and generic terminology in mind; it is the only source of support for later continuation claims.
Value delivered
A deliberate route to wider protection
By conducting a detailed, keyword-level review of the client's telecommunications patent claims, IIPRD identified opportunities to refine claim language, address implementation gaps, and develop a structured continuation strategy.
The engagement resulted in four proposed continuation claims: one broader claim intended to cover a wider universe of implementations and three implementation-specific claims. This provided the client with a more deliberate approach to extending patent protection around its technology and strengthening its long-term intellectual property position.
Frequently asked questions
Continuations, CIPs and standards-related claims
What is a continuation application?
A continuation is a new application that uses the same specification as a pending parent application and claims the parent's filing date. It lets the applicant pursue different claims, often broader or differently focused, without adding new technical content.
How does a continuation differ from a continuation-in-part or a divisional?
A continuation keeps the parent's disclosure unchanged. A continuation-in-part adds new matter, and claims relying on that new matter only get the CIP's own filing date. A divisional is filed to pursue an invention the examiner required to be separated out through a restriction requirement.
When does a continuation have to be filed?
In the US, while the parent application is still pending, meaning before it issues as a patent or is abandoned. Many applicants keep one family member pending for this reason.
Why combine one broad claim with narrower ones?
The broad claim aims to cover the underlying technology across many implementations, but it carries more risk from prior art and support challenges. The narrower implementation-specific claims are harder to invalidate and give fallback positions if the broad claim is narrowed.
Is this the same as making a patent standard-essential?
No. This engagement focused on claim scope across implementation scenarios. Whether a claim is essential to a standard depends on a separate comparison of the claim against the final specification text.
Can a continuation be used to cover a competitor's product?
Continuation claims can be drafted with known implementations in mind, provided every claim is supported by the original disclosure and meets patentability requirements. The new claims cannot rely on technical content that was not in the parent.
