In the previous installments of this series, we discussed general drafting strategies, inventive step considerations, parallel technical solutions, and amendments beyond the original disclosure. This fifth article addresses a fundamental requirement that underpins all patent drafting: claim clarity. For standards-related patent applications, ensuring that claims are clear and definite takes on added importance because claims must ultimately be compared against technical specifications that may use different terminology, evolve over time, or introduce new concepts. An unclear claim cannot be properly evaluated for essentiality, nor can it be reliably enforced.
The Legal Standard for Claim Clarity
Under applicable patent law, claims must clearly and concisely define the matter for which protection is sought. The definiteness requirement ensures that the scope of exclusive rights is ascertainable by the public, including competitors, licensees, and courts. A claim is considered unclear if its boundaries cannot be determined with reasonable certainty based on the patent disclosure and the understanding of a person skilled in the art.
For standards-related applications, the definiteness analysis must account for the fact that technical terms may have different meanings in different contexts—and that standardization bodies often use terms in specific ways that may not yet be universally established at the time of filing. The drafter must strike a balance between using terminology that will align with future standards and ensuring that the claims are clear based on the application as filed.
Handling Technical Terms in Claims
One of the most common clarity issues in standards-related applications involves the use of technical terms that have not yet been formally adopted into a standard. The general rule is straightforward: terms that have been adopted by national or industry technical standards generally do not require definition; they are understood by those skilled in the art. However, terms that appear only in proposals or draft documents—and have not yet gained recognized meaning—may be considered unclear if used without explanation.
When drafting, if a term lacks a generally accepted meaning in the art, the drafter should either limit the term in the claim (e.g., by providing a functional definition) or define the term clearly in the specification. This is particularly important for terms relating to scenario names, network entity names, communication signals, and resource identifiers. A term that seems clear to the inventor based on internal discussions may be ambiguous to a skilled person reading the application years later.
For example, early in the development of fifth-generation (5G) technology, the term “5G NR” appeared in technical proposals. Before its formal adoption into standards, an applicant using this term in claims would need to ensure that the specification provides a clear definition or that the term had already acquired a recognized meaning in the field. The safer approach is to include a definition in the specification, even if the term later becomes standardized. This proactive step avoids later disputes over claim interpretation.
Ensuring Method Steps Are Technically Clear
For method claims, clarity requires that each step be technically definite and that the relationship among steps be ascertainable. When the method involves sending or receiving messages, the content of those messages and the technical feasibility of the transmission should be clear. The order of steps—whether sequential, parallel, or conditional—should be understandable from the claim language or the context provided by the specification.
Ambiguities arise when the claim language suggests contradictory actions or when it is unclear which steps are performed by which entity. Single-sided drafting, discussed in the first article of this series, helps avoid confusion by consistently describing actions from the perspective of a single device. Multi-sided claims, while permissible, require careful attention to ensure that the reader can determine which steps correspond to which actor.
Avoiding Contradictions and Ambiguities
Claims that contain internally contradictory limitations are inherently unclear. This can occur when two mutually exclusive operations are written into the same claim without a clear condition for selecting between them. For instance, a claim that recites both “transmitting a signal” and “refraining from transmitting the signal” without a condition that determines when each applies would be contradictory and thus indefinite.
Another source of contradiction involves mismatched actors. A claim directed to a method performed by a base station should not include a step described as being performed by a user equipment unless the claim clearly indicates that the base station is causing or facilitating that step. Similarly, a claim that first states a parameter is selected by the base station and later states that the same parameter is selected by the user equipment—without any transition or condition—contains an irreconcilable contradiction.
Logical ambiguities also arise when multiple conditions overlap. Consider a claim that selects a first calculation method when “any one condition is satisfied” and a second calculation method when “at least one condition is not satisfied.” Under a set of three conditions, satisfying exactly one condition would satisfy both criteria, leaving the reader uncertain which method applies. Such overlapping conditions render the claim unclear.
Special Considerations for Artificial Intelligence and Machine Learning
As communication systems increasingly incorporate artificial intelligence (AI) and machine learning (ML) techniques, claims in standards-related applications may involve features such as neural networks, models, or inference engines. For these claims to be clear, the relationship between the AI/ML elements and the underlying communication technology must be explicitly defined.
The input data to the model should be clearly described in terms of communication parameters, signals, or messages. The output data should similarly be tied to specific communication actions or decisions. A claim that simply recites “applying a machine learning model to determine a parameter” without specifying what the model inputs are, how the model is trained, or what the output represents may be rejected as indefinite. The specification should provide sufficient detail to enable a skilled person to understand what the model does in the context of the communication system.
Leveraging the Specification to Support Claim Clarity
When the original application is derived from a technical proposal submitted to a standardization body, special care is needed. Technical proposals often assume familiarity with concepts and terminology discussed in previous meetings, and they may not define all terms. In converting such a proposal into a patent application, the drafter should expand the description to define key terms and explain technical concepts that would otherwise be assumed. Proactively defining terms and providing examples of their usage helps avoid later clarity challenges.
If a clarity objection is raised during prosecution, the applicant may respond by explaining the technical meaning of the disputed term, citing evidence such as common general knowledge or content from national or industry technical standards. When the objection is justified, the appropriate response is to amend the claim to remove the ambiguity—for example, by adding a clear condition to resolve overlapping scope or by correcting contradictory language.
Practical Example
Consider an application involving a method for discontinuous reception. An initial draft contains a claim step: “selecting a discontinuous reception cycle specific to the user equipment.” Later in the same claim, another step recites: “sending a paging message based on the discontinuous reception cycle selected by the user equipment.” Because the claim is directed to a method performed by a base station, the first step indicates the base station selects the cycle, while the second step indicates the user equipment selects the cycle. This contradiction renders the claim unclear. The proper correction is to ensure that both steps attribute the selection action to the same entity—typically the base station in a single-sided claim—or to rewrite the claim to clearly distinguish between two different cycles if that is intended.
Wrapping Up This Series
This article concludes the detailed exploration of the major drafting topics introduced in our first installment. Throughout this series, we have covered general drafting strategies, inventive step considerations, parallel technical solutions, amendments beyond the original disclosure, and claim clarity. Together, these topics provide a comprehensive framework for preparing high-quality, standards-ready patent applications. Future supplemental articles may address additional practical topics such as best practices for preparing claim charts, strategies for prosecuting SEP applications before different patent offices, and emerging trends in SEP litigation and licensing. Stay tuned for further guidance designed to help applicants navigate the complex intersection of patent law and technical standardization.
Source: Guidelines for Invention Patent Applications Involving Standards, China National Intellectual Property Administration (CNIPA).
鄂公网安备 42010402001546号