After Williamson, functional claiming faces greater scrutiny under 35 U.S.C. 112(f). Williamson eliminated the strong presumption that claim limitations without the word "means" are not subject to means-plus-function treatment. A claim limitation will be subject to means-plus-function analysis if it fails to recite sufficiently definite structure or recites a function without sufficient structure. The court applied this standard to invalidate claims using a "distributed learning control module" limitation as means-plus-function claiming because the term "module" was deemed a nonce word and the specification failed to disclose an algorithm for the "coordinating" function. Practitioners should tie claimed functions to specific structures or algorithms in the specification to avoid means-plus
Word choice matters a great deal in the world of patenting. Youre using the English language to draw a picture around highly technical concepts. The precision with which this is done, down to the semantic level, can make all of the difference when it comes to your patent application being rejected or granted and the future likelihood of your ability to assert your rights or defend against invalidation. Word choice too narrow or overly specific and you can easily be designed around by competitors. Word choice too broad and only describing what something is vs what it does and you risk rejection or invalidation for what will be ruled as linguistic tricks to get more coverage than what you actually invented. The tension is real and the case law interpretation is fluid, but it all still comes down to determining if the chosen words will enable a person of ordinary skill in the art to carry out an invention in the interest of other inventors being able to build on the idea, while also avoiding trespassing with infringement.
One very particular place this tension between breadth of coverage and specificity in enablement arises is with the concept of Means-Plus-Function claim language. In this months episode, Dr. Ashley Sloat, President and Director of Patent Strategy here at Aurora, leads a discussion, along with our all star patent panel, into the nuanced world of Means-Plus-Function claiming. The group digs into the statute, explores relevant case law in an analysis of the kinds of word choices that have and havent caused problems for inventors, and also provides some great drafting tips for de-risking the use of Means-Plus-Function claim language.
Ashley is joined today by our always exceptional group of IP experts including:
皃 Kristen Hansen, Patent Strategist at Aurora
皃 Dr. David Jackrel, President of Jackrel Consulting
皃 David Cohen, Principal at Cohen Sciences
皃 Shelley Couturier, Patent Strategist and Search Specialist
Before jumping into the deep with the panel, we also provide a quick primer on key concepts including specification vs claims, Section 112 enablement, functional claim language, and nonce words.
Knobbe Practice Japan Webinar Series
Partner Mauricio Uribe provided an overview of means plus function claim limitations, focusing on prosecution of patent applications before the United States Patent and Trademark Office (USPTO). The discussion covered a review of USPTO guidelines for characterizing and interpreting means plus function limitations in claims, tips for addressing USPTO interpretation of means plus function claims during prosecution, and sample claim language related to means plus function and covering various technology areas.
Speakers: Mauricio Uribe and Kenny Masaki
Agenda
Requirements
What are requirements?
Classifying the requirements
Characteristics of requirements
Requirements elicitation
Documenting the requirements
Requirements analysis and negotiation
Requirements validation
The document discusses system architecture and defines several key concepts:
- An architecture describes an operational concept, processes, components, and relationships among components. It includes functional and physical architectures.
- Structured analysis is a process-oriented approach that uses functional decomposition and models like activity, data, rule, and dynamics models.
- The object-oriented approach uses UML diagrams to model static and dynamic behavior.
- Architectures must be evaluated based on verification, consistency, correctness, performance, and requirements.
- The DoD architecture framework defines operational, system, and technical standard views with multiple representations. It uses functional decomposition.
The document discusses system architecture and functional analysis. It begins by defining system architecture as the process of creating complex, unprecedented systems. It then discusses defining architectures, including operational concepts, processes, components, and functional vs physical architectures. It covers structured analysis approaches, including functional decomposition models, data models, rule models, and performance evaluation. Object-oriented approaches and the DoD architecture framework are also summarized. The document then discusses functional analysis, including elements like functions, functional diagrams, processing instructions, and control flow. Methods like functional decomposition, simple vs complete functionalities, and evaluating functional architectures are also covered.
The document discusses system architecture and functional analysis. It covers:
1. The definition of system architecture as the process of creating complex, unprecedented systems to meet ill-defined requirements driven by evolving technology and globalization.
2. Key elements of architectures including the operational concept, processes, components, and selection of systems in a system of systems.
3. Functional analysis examines the activities a system must perform to achieve outputs by transforming inputs. It considers functions, data flows, processing instructions, and control logic.
4. Functional decomposition breaks down a top-level function into subordinate functions using a hierarchical tree structure. Composition builds up from simple functionalities to complete functionalities.
Core Wireless Licensing v. LG Electronics: User Interfaces & Patent-Eligible ...Workman Nydegger
油
The document summarizes a Federal Circuit court case regarding patent eligibility of two patents related to user interfaces on mobile devices. The court affirmed the district court's ruling, finding that the claims were not directed to an abstract idea, but rather an improved user interface for mobile devices. Specifically, the claims addressed problems with small screens by allowing quick access to common functions through an application summary window, improving efficiency of navigation on the device.
Legal Vocabulary and its Transformation Evaluation using Competency Questionslukeg5
油
This document discusses evaluating legal vocabularies using competency questions. It presents a model-driven architecture approach to represent legal knowledge using concepts, facts, and rules in a semi-formal language called SBVR. Competency questions are designed to verify the accuracy, completeness, and consistency of the legal vocabulary. The questions are translated into formal queries to check inferences from the ontology. Experimental results show how competency questions can identify incomplete or sensitive concepts. The legal rules represented in the vocabulary can then be used to generate arguments in a legal expert system.
Legal Vocabulary and its Transformation Evaluation using Competency Questionsshashi792
油
This document discusses evaluating legal vocabularies using competency questions. It presents a model-driven architecture approach to represent legal knowledge using concepts, facts, and rules in a semi-formal language called SBVR. Competency questions are designed to verify the accuracy, completeness, and consistency of the legal vocabulary. The questions are translated into formal queries to check inferences from the ontology. Experimental results show how competency questions can identify incomplete or sensitive concepts. The legal rules represented semi-formally can then be mapped to formal rule languages for implementation.
This presentation is aimed to stimulate improvement at requirements review, with the intent of improving defect injection. Some specific mention is made of non-functional requirements - specifically performance and security. This is one slide pack of a set.
Oracle v. Google: Deciphering the district courts decision of no copyright p...Marc Hubbard
油
An explanation of the district court's holding in Oracle v. Google that the Google's implementation in Android of a portion of the Java API specification did not infringe the copyright in Sun's/Oracle's implementation because the API was not copyrightable
- The document discusses challenges in building application frameworks and applications simultaneously. It argues that the framework must be built in parallel with the applications that will use it.
- It presents patterns for developing frameworks and applications together, including starting with pilot applications to help define the framework's abstractions, and evolving the framework based on feedback from application developers.
- Metrics like the "Rule of Three" and "Budget Factor 2.5" are introduced to help scope the framework and schedule its development.
This document summarizes the Supreme Court's Alice Corp. v. CLS Bank decision and the USPTO's new guidelines for examining patent applications under 35 U.S.C. 101. The USPTO now uses the same two-step test for all types of claims, determining if the claim is directed to an abstract idea and if the claim recites elements that amount to significantly more than the abstract idea. The document provides examples of claim elements that may or may not be enough to satisfy the second step. It concludes with practice tips, such as paying issue fees early for software applications.
This document discusses expert systems and their application in road transport. It begins with definitions of expert systems and how they emulate human decision making. It then outlines the typical design of rule-based expert systems, including the knowledge base and inference engine. Next, it describes the six phase development process for building an expert system and provides comments on each phase. It also discusses rule-based reasoning approaches, including goal-driven and data-driven reasoning. Finally, it lists some advantages of expert systems and examples of their applications.
This document discusses expert systems and their application in road transport. It begins with definitions of expert systems and how they emulate human decision making. It then outlines the typical design of rule-based expert systems, including the knowledge base and inference engine. Next, it describes the six phase development process for building an expert system and provides comments on each phase. It also discusses rule-based reasoning approaches, including goal-driven and data-driven reasoning. Finally, it lists some advantages of expert systems and potential applications in areas like diagnosis, planning, and monitoring.
The document provides guidance on writing good requirements, including:
- Using "shall" to indicate requirements and avoiding terms like "will" or "should".
- Writing requirements in an active voice stating who or what is responsible.
- Providing examples of well-written product requirements.
- Checking requirements for clarity, completeness, consistency, traceability, correctness and other attributes to ensure they are well-defined and testable.
For a full set of 350+ questions. Go to
https://skillcertpro.com/product/microsoft-sc-900-exam-questions/
SkillCertPro offers detailed explanations to each question which helps to understand the concepts better.
It is recommended to score above 85% in SkillCertPro exams before attempting a real exam.
SkillCertPro updates exam questions every 2 weeks.
You will get life time access and life time free updates
SkillCertPro assures 100% pass guarantee in first attempt.
The Federal Circuit Review is a monthly newsletter featuring the latest case summaries handed down from the U.S. Court of Appeals for the Federal Circuit.
In this issue:
Doctrine of Equivalents: What Constitutes a Disclosed but not Claimed Equivalent?
When Each Means Every: Apple Loses a Round in Its Ongoing Battle with Samsung
Capturing Advances in Technology Under the Doctrine of Equivalents
Is a Height Adjustment Mechanism a Definite Structure, or a Means-Plus- Function?
PTO Invalidity Ruling Stands Despite Prior Court Ruling of No Invalidity
The document discusses access control and authorization in distributed systems. It introduces role-based access control (RBAC) as a promising approach. RBAC separates the administration of principals and roles from the specification of authorization policy in terms of roles. This allows authorization policy to be expressed independently of changes to principal membership. RBAC also facilitates inter-domain authorization by allowing roles to span domains. The document presents an example RBAC implementation using the OASIS framework that specifies role activation and authorization policies using rules. It describes how roles can be activated and how certificates tied to roles can be used to enforce authorization across distributed services.
The document discusses access control and authorization in distributed systems. It introduces role-based access control (RBAC) as a promising approach. RBAC separates the administration of principals and roles from the specification of authorization policy in terms of roles. This allows authorization policy to be expressed independently of changes to principal membership. RBAC also facilitates inter-domain authorization by allowing roles to span domains. The document presents an example RBAC implementation using the OASIS framework that specifies role activation and authorization policies using rules. It also discusses engineering role certificates and maintaining credential state to support RBAC in a distributed environment.
The document discusses requirements gathering and writing better requirements. It defines what a requirement is, noting that a requirement specifies what a product must do while a specification is a collection of all requirements. It provides characteristics that make a good requirement, such as being understandable, unambiguous, and testable. The document distinguishes between functional and non-functional requirements and suggests using user stories for non-functional requirements. It offers tips for writing better requirements, such as keeping them implementation-neutral, including rationale, and using syntax patterns. The document stresses that proper requirements reduce project time and costs.
Software engineering by Dr. vishnu sharmaVishnu Sharma
油
The document discusses software engineering and related concepts. It defines software engineering as the application of scientific principles and methods to the development of software. It describes the different stages of software development like planning, requirements analysis, design, coding, testing and maintenance. It also discusses the qualities of good software like maintainability, correctness, reusability, reliability and portability. Finally, it outlines some common challenges in software development such as understanding complex requirements and dealing with changing requirements.
Casos de uso para aplicaciones tradicionales en un mundo de contenedoresSUSE Espa単a
油
This document discusses using stateful applications on Kubernetes. It describes how containers are inherently stateless but Kubernetes provides tools like volumes and StatefulSets to manage state. Volume plugins allow connecting containers to various storage backends. PersistentVolumes and PersistentVolumeClaims provide an API for storage requests. StatefulSets ensure ordered deployment and stable networking for stateful applications. Real-world examples from SUSE include containerizing OpenStack and Cloud Foundry platforms.
With sharing or without sharing... is that the question? Join us to better understand how to leverage the best Salesforce security features in code. Learn all the best practices for hardening your application and keeping your data secure. We'll cover sharing, FLS, CRUD, and all the most common mistakes and misconceptions about how these features work in Apex and Visualforce.
Core Wireless Licensing v. LG Electronics: User Interfaces & Patent-Eligible ...Workman Nydegger
油
The document summarizes a Federal Circuit court case regarding patent eligibility of two patents related to user interfaces on mobile devices. The court affirmed the district court's ruling, finding that the claims were not directed to an abstract idea, but rather an improved user interface for mobile devices. Specifically, the claims addressed problems with small screens by allowing quick access to common functions through an application summary window, improving efficiency of navigation on the device.
Legal Vocabulary and its Transformation Evaluation using Competency Questionslukeg5
油
This document discusses evaluating legal vocabularies using competency questions. It presents a model-driven architecture approach to represent legal knowledge using concepts, facts, and rules in a semi-formal language called SBVR. Competency questions are designed to verify the accuracy, completeness, and consistency of the legal vocabulary. The questions are translated into formal queries to check inferences from the ontology. Experimental results show how competency questions can identify incomplete or sensitive concepts. The legal rules represented in the vocabulary can then be used to generate arguments in a legal expert system.
Legal Vocabulary and its Transformation Evaluation using Competency Questionsshashi792
油
This document discusses evaluating legal vocabularies using competency questions. It presents a model-driven architecture approach to represent legal knowledge using concepts, facts, and rules in a semi-formal language called SBVR. Competency questions are designed to verify the accuracy, completeness, and consistency of the legal vocabulary. The questions are translated into formal queries to check inferences from the ontology. Experimental results show how competency questions can identify incomplete or sensitive concepts. The legal rules represented semi-formally can then be mapped to formal rule languages for implementation.
This presentation is aimed to stimulate improvement at requirements review, with the intent of improving defect injection. Some specific mention is made of non-functional requirements - specifically performance and security. This is one slide pack of a set.
Oracle v. Google: Deciphering the district courts decision of no copyright p...Marc Hubbard
油
An explanation of the district court's holding in Oracle v. Google that the Google's implementation in Android of a portion of the Java API specification did not infringe the copyright in Sun's/Oracle's implementation because the API was not copyrightable
- The document discusses challenges in building application frameworks and applications simultaneously. It argues that the framework must be built in parallel with the applications that will use it.
- It presents patterns for developing frameworks and applications together, including starting with pilot applications to help define the framework's abstractions, and evolving the framework based on feedback from application developers.
- Metrics like the "Rule of Three" and "Budget Factor 2.5" are introduced to help scope the framework and schedule its development.
This document summarizes the Supreme Court's Alice Corp. v. CLS Bank decision and the USPTO's new guidelines for examining patent applications under 35 U.S.C. 101. The USPTO now uses the same two-step test for all types of claims, determining if the claim is directed to an abstract idea and if the claim recites elements that amount to significantly more than the abstract idea. The document provides examples of claim elements that may or may not be enough to satisfy the second step. It concludes with practice tips, such as paying issue fees early for software applications.
This document discusses expert systems and their application in road transport. It begins with definitions of expert systems and how they emulate human decision making. It then outlines the typical design of rule-based expert systems, including the knowledge base and inference engine. Next, it describes the six phase development process for building an expert system and provides comments on each phase. It also discusses rule-based reasoning approaches, including goal-driven and data-driven reasoning. Finally, it lists some advantages of expert systems and examples of their applications.
This document discusses expert systems and their application in road transport. It begins with definitions of expert systems and how they emulate human decision making. It then outlines the typical design of rule-based expert systems, including the knowledge base and inference engine. Next, it describes the six phase development process for building an expert system and provides comments on each phase. It also discusses rule-based reasoning approaches, including goal-driven and data-driven reasoning. Finally, it lists some advantages of expert systems and potential applications in areas like diagnosis, planning, and monitoring.
The document provides guidance on writing good requirements, including:
- Using "shall" to indicate requirements and avoiding terms like "will" or "should".
- Writing requirements in an active voice stating who or what is responsible.
- Providing examples of well-written product requirements.
- Checking requirements for clarity, completeness, consistency, traceability, correctness and other attributes to ensure they are well-defined and testable.
For a full set of 350+ questions. Go to
https://skillcertpro.com/product/microsoft-sc-900-exam-questions/
SkillCertPro offers detailed explanations to each question which helps to understand the concepts better.
It is recommended to score above 85% in SkillCertPro exams before attempting a real exam.
SkillCertPro updates exam questions every 2 weeks.
You will get life time access and life time free updates
SkillCertPro assures 100% pass guarantee in first attempt.
The Federal Circuit Review is a monthly newsletter featuring the latest case summaries handed down from the U.S. Court of Appeals for the Federal Circuit.
In this issue:
Doctrine of Equivalents: What Constitutes a Disclosed but not Claimed Equivalent?
When Each Means Every: Apple Loses a Round in Its Ongoing Battle with Samsung
Capturing Advances in Technology Under the Doctrine of Equivalents
Is a Height Adjustment Mechanism a Definite Structure, or a Means-Plus- Function?
PTO Invalidity Ruling Stands Despite Prior Court Ruling of No Invalidity
The document discusses access control and authorization in distributed systems. It introduces role-based access control (RBAC) as a promising approach. RBAC separates the administration of principals and roles from the specification of authorization policy in terms of roles. This allows authorization policy to be expressed independently of changes to principal membership. RBAC also facilitates inter-domain authorization by allowing roles to span domains. The document presents an example RBAC implementation using the OASIS framework that specifies role activation and authorization policies using rules. It describes how roles can be activated and how certificates tied to roles can be used to enforce authorization across distributed services.
The document discusses access control and authorization in distributed systems. It introduces role-based access control (RBAC) as a promising approach. RBAC separates the administration of principals and roles from the specification of authorization policy in terms of roles. This allows authorization policy to be expressed independently of changes to principal membership. RBAC also facilitates inter-domain authorization by allowing roles to span domains. The document presents an example RBAC implementation using the OASIS framework that specifies role activation and authorization policies using rules. It also discusses engineering role certificates and maintaining credential state to support RBAC in a distributed environment.
The document discusses requirements gathering and writing better requirements. It defines what a requirement is, noting that a requirement specifies what a product must do while a specification is a collection of all requirements. It provides characteristics that make a good requirement, such as being understandable, unambiguous, and testable. The document distinguishes between functional and non-functional requirements and suggests using user stories for non-functional requirements. It offers tips for writing better requirements, such as keeping them implementation-neutral, including rationale, and using syntax patterns. The document stresses that proper requirements reduce project time and costs.
Software engineering by Dr. vishnu sharmaVishnu Sharma
油
The document discusses software engineering and related concepts. It defines software engineering as the application of scientific principles and methods to the development of software. It describes the different stages of software development like planning, requirements analysis, design, coding, testing and maintenance. It also discusses the qualities of good software like maintainability, correctness, reusability, reliability and portability. Finally, it outlines some common challenges in software development such as understanding complex requirements and dealing with changing requirements.
Casos de uso para aplicaciones tradicionales en un mundo de contenedoresSUSE Espa単a
油
This document discusses using stateful applications on Kubernetes. It describes how containers are inherently stateless but Kubernetes provides tools like volumes and StatefulSets to manage state. Volume plugins allow connecting containers to various storage backends. PersistentVolumes and PersistentVolumeClaims provide an API for storage requests. StatefulSets ensure ordered deployment and stable networking for stateful applications. Real-world examples from SUSE include containerizing OpenStack and Cloud Foundry platforms.
With sharing or without sharing... is that the question? Join us to better understand how to leverage the best Salesforce security features in code. Learn all the best practices for hardening your application and keeping your data secure. We'll cover sharing, FLS, CRUD, and all the most common mistakes and misconceptions about how these features work in Apex and Visualforce.
2. Functional claiming
What is it?
Claim language defining components by their function
configured to, adapted to, programmed to, to
or for
Why use functional claiming?
Allows for broader claiming
Avoids need to claim at an implementation level, which
may be easier to design-around
2
3. Functional claiming: Concerns
Means-plus-function treatment (則 112 其 6 / post-AIA f)
Focus of todays discussion and Williamson
Claim construction
Functional terms given patentable weight?
Art / infringer need only be capable of performing
function?
Not todays focus
Indefinite under written description or enablement (則
112, 其其 1, 2 or post AIA a,b)
Also addressed in Williamson for software
3
4. Functional claiming: Means-plus-function
Functional claim language at the precise point of
novelty may render a patent invalid as indefinite.
See Halliburton Oil Well Cementing Co. v. Walker, 329
U.S. 1, 12-13 (1946).
means associated with said pressure responsive device
for tuning said receiving means to the frequency of
echoes limitations at issue
means-plus-function, 則 112, 其6 enacted in response to
this decision
4
5. Functional claiming: Means-plus-function
35 U.S.C. 則 112, 其 6 (post-AIA (f))
An element in a claim for a combination may be expressed as a
means or step for performing a specified function without the
recital of structure, material, or acts in support thereof, and such
claim shall be construed to cover the corresponding structure,
material, or acts described in the specification and equivalents
thereof.
Historically could be disfavored to avoid being limited
by the specification (practitioners would avoid use of
means)
5
6. Functional claiming: Means-plus-function
What receives 則 112, 其 6 (post-AIA (f)) treatment
means for, element, device (Personalized Media)
Presumption that a term without means would not
receive 則 112, 其 6 treatment (Personalized Media)
Terms with no dictionary definition or understood
meaning in the art
Colorant selection mechanism (Abacus)
What does not
Terms with structure understood in art
Circuitry (Abacus, Linear, Apex)
6
7. Williamson removes strong presumption
Williamson removes strong presumption that a claim
without use of means is not a 則 112, 其 6 (post-AIA (f))
claim
The presumption is a strong one that is not readily
overcome. (Lighting World)
則 112, 其 6 (post-AIA (f)) treatment will be accorded a claim if
a challenger shows that:
the claim fails to recite sufficiently definite structure; (nonce
words are not sufficient structure) OR
the claim recites function without reciting sufficient structure for
performing that function.
7
8. Introductory Williamson Facts (6,155,840)
The 840 Patent describes methods and systems for
distributed learning that utilize industry standard
computer hardware and software linked by a network
to provide a virtual classroom.
Claim 8 is a system claim that included the limitation
at issue, which is:
a distributed learning control module
for receiving communications transmitted between the
presenter and the audience member computer systems; and
for relaying the communications to an intended receiving
computer system; and
for coordinating the operation of the streaming data module.
8
9. District Court Holding
District court found that the distributed learning
control module limitation of claim 8 was a means-
plus-function claim
District court further found the specification failed to
disclose structure for performing one of the functions,
rendering the claim invalid under 35 U.S.C. 則112, 其2.
The limitation includes three functions, and only one of
those functions was found to lack the necessary
algorithm the coordinating the operation of the
streaming data module function.
9
10. Courts analysis of past holdings footing
Past cases have emphasized that the essential inquiry
is not merely the presence or absence of the term
means but whether the words of the claim are
understood by persons of skill in the art to have a
sufficiently definite meaning as the name for
structure.
With or without the term means, the meaning of the
language of the claims is analyzed to determine if the
presumption is overcome as to whether 112,6 should or
should not apply
10
11. 11
Majority Holding in Williamson
All previous holdings of heightened presumption
explicitly overruled.
The new standard as to whether 112,6 should apply
when a claim limitation does not include means is:
Whether the words of the claim are understood by
persons of ordinary skill in the art to have a sufficiently
definite meaning as the name for structure. When a
claim lacks the word means, the presumption can be
overcome and 112,6 will apply if the challenger
demonstrates that the claim term fails to recite
sufficiently definite structure or else recites function
without reciting sufficient structure for performing that
function.
12. Majority Holding in Williamson, continued
Essentially, the holding eliminates the heightened
evidentiary showing
The presumption associated with the use of means
is unaffected
The presumption is that 112,6 applies with the use of
means, but the presumption is rebuttable
12
13. Courts Analysis of the distributed learning
control module limitation
The claim limitation is not merely the introductory phrase
but the entire provision.
The format of the clause is in a format that is consistent
with traditional means-plus-function claim limitations.
distributed learning control module for function(s).
Means is replaced by module.
Module is a well known nonce word that can operate as
a substitute for means.
Module is a generic description for software or hardware
that performs a specific function.
Module does not provide any indication of structure.
13
14. Courts Analysis of the distributed learning
control module limitation, continued
The prefix distributed learning control does not impart
structure into the term module.
The specification fails to impart any structural significance to
the term.
While the modifiers may alter the meaning of the term
module, there is nothing in the specification or prosecution
history that may help construe distributed learning control
module as the name of a sufficiently definite structure to
avoid 112,6.
The claim does not describe how the distributed learning control
module interacts with other components in the server in a way
that might inform the structure of the limitation or otherwise
impart structure to the limitation as recited in the claim.
14
15. Courts Analysis of the distributed learning
control module limitation, continued
Expert declaration cannot save the claim.
The expert declaration fails to describe how the
distributed learning control module, through
interactions with the other components of the claim,
is understood as the name for structure.
Structure cannot be created where none is disclosed
even if one skilled in the art would be able to program
a computer to perform the corresponding functions.
15
16. Construing means-plus-function claims
Construing a means-plus-function claim is a two step
process:
1. Identify the claimed function.
2. Determine what structure, if any, disclosed in the
specification corresponds to the claimed function.
When there are multiple claimed functions, corresponding
structure for each function must be included.
If the specification fails to disclose adequate
corresponding structure, the claim is indefinite.
16
17. Construing means-plus-function claims, contd
Structure disclosed in the specification qualifies as
corresponding structure if the intrinsic evidence
clearly links or associates that structure to the
function recited in the claim.
The corresponding disclosure must be adequate to
achieve the claimed function.
If one of ordinary skill in the art would be unable to
recognize the structure and associate it with the
corresponding function, a means-plus-function clause is
indefinite.
17
18. Construing means-plus-function claims, contd
Computer based limitations:
Claim limitations subject to 112,6 that must be
implemented in a special purpose computer require the
structure disclosed in the specification to be more than
simply a general purpose computer.
A special purpose computer is a general purpose computer
programmed to perform particular functions pursuant to
instructions form program software.
Algorithms are required in the specification for performing the
claimed functions, which may be mathematical formulas, in
prose, or as a flow chart, or in any other manner that provides
sufficient structure.
Functions do not disclose algorithms.
18
19. Construing means-plus-function claims, contd
Application of the analysis to the present facts:
The 840 Patent specification was clear that the
distributed learning control module cannot be
implemented on a general purpose computer, thus, an
algorithm must be disclosed.
Disclosing what the module does, e.g., the functions
performed, is not the same as disclosing the algorithm
needed to perform the functions.
A user interface is not an algorithm.
As previously noted, the testimony of one of ordinary
skill in the art cannot supplant the total absence of
structure from the specification.
19
20. Williamson Outcome
The distributed learning control module was
correctly determined to be a means-plus-function
limitation because:
The term module is a nonce word standing in for means,
and
The clause was in the form of a traditional means-plus-
function claim
Claims 8-16 are invalid for lack of disclosure
corresponding to the coordinating function of the
distributed learning control module.
20
21. Breakdown of the new 112,6 analysis when
means is absent from the claim
112,6 will not apply if the words of the claim are
understood by person of ordinary skill in the art to
have a sufficiently definite meaning as the name for
structure.
112,6 will apply If the claim:
Fails to recite sufficiently definite structure,
OR
Recites function without reciting sufficient structure
for performing that function.
21
22. What to do?
Be cognizant of whether you intend to avail yourself of
(則 112 其 6 / post-AIA (f))
Do you intend to claim a component performing a
function, where disparate structures may be used to
implement the component?
If yes, explicitly tie the claimed functions to example
structures / algorithms in the specification
If not, ensure actual structure is claimed
And explicitly tie arguable functional recitations to example
structures / algorithms in the specification
Insure against unfortunate outcome of 則 112 其 6, post-AIA (f)
treatment followed by 則 112 其 2 / post-AIA (b) invalidity
22
23. 23
What likely is/is not sufficiently definite
structure?
Sufficiently definite structure is:
Structure (e.g., mathematical formula, prose, flow diagram) that one skilled in the art
would understand to be adequate to perform the corresponding function
Detailed prose provided in the specification that described how specific software
products operate to implement the claimed functions.
TecSec, Inc. v. IBM, 731 F.3d 1336 (2013)
Distinguish between physical structure and algorithmic-type structure
Sufficiently definite structure is not:
Functions themselves
User interfaces
Expert opinion
In terms of one of ordinary skill in the art, the question is whether one of skill in the art would
understand the specification itself to disclose structure, not simply whether that person would
be capable of implementing that structure. See MPEP 2181 II A, quoting Biomedino, LLC v.
Waters Technologies Corp.
24. 24
Avoiding (則 112 其 6 / post-AIA (f))
If a means-plus-function claim is NOT desired, the following
recommendations may be helpful:
Avoid, to the extent possible, a claim format that could be deemed
consistent to a traditional means-plus-function claim:
Avoid terms that may be seen as nonce terms, e.g., module,
unit, apparatus, element, etc.
Avoid following up an introductory pseudo-structure term
with for
E.g., avoid pseudo-structure for performing function(s)
Use terms that have a known structural connotation
E.g., if a means-plus-function form is unavoidable, then use structural-based
modifiers before any potential nonce word
25. 25
Nonce Words MPEP 2181
MPEP 2181 governs identifying and interpreting claims as means-plus-
function claims.
MPEP 2181 A provides guidance on terms that have and have not been
deemed nonce terms.
Examples of nonce terms: mechanism for, module for, device for,
unit for, component for, element for, member for, apparatus for,
machine for, and system for
Examples of terms not deemed nonce terms: circuit, detent
mechanism, digital detector, reciprocating member, connector
assembly, perforation, sealingly connected joints, and eyeglass
hanger member.
Terms deemed nonce typically are less concrete and can cover a wide
array of structure, whereas the terms not deemed nonce appear more
concrete and may cover a limited variety of structure.
Keep in mind that all terms are read in light of the specification and the
surrounding claim language.
26. What to do? Software
Williamson did disclose that the modules could be
implemented using software programmed on a
computer. That wasnt enough.
26
27. (則 112 其 6/ post-AIA (f)) and software
When a software claim receives (則 112 其 6/ post-AIA (f))
treatment:
Structure must be more than a general purpose
computer. (Aristrocrat Techs.)
Specification must disclose an algorithm for
performing the claimed function (NetMoneyIN).
27
28. Practice Tips
28
Ensure specification includes flowchart, formula, or
prose that details a specific example of how each
function may be performed
Scientific disclosures/papers are usually replete with
algorithmic detail
Concern will be with tying the disclosed structures /
algorithms with the claimed functions, which are often
named or articulated at a later time