DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
Election/Restrictions
Applicant’s election of Group I, corresponding to Claims 1-17, and Species I, corresponding to Claims 1-2, 6-9, and 14-17, in the reply filed on 08/10/2026 is acknowledged. Because applicant did not distinctly and specifically point out the supposed errors in the restriction requirement, the election has been treated as an election without traverse (MPEP § 818.01(a)).
Applicant asserts claims 6-9 read on the elected species. However, claims 6-9 respectively depend upon unelected claim 5 and are thereby also withdrawn.
Claims 3-15 and 18-20 are withdrawn from further consideration pursuant to 37 CFR 1.142(b) as being drawn to a nonelected group and/or species, there being no allowable generic or linking claim. Election was made without traverse in the reply filed on 08/10/2026.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – 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.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
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.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are:
“input unit … configured to receive an input signal … and to issue a propeller speed reference” in at least claim 1.
“a control unit … configured to control the propulsion system” in at least claim 1.
“a propeller speed controller … configured to control” in at least claim 2.
“an engine controller … configured to control” in at least claim 14.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-2 and/or 14-17 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
In accordance with MPEP 2163, “when a means-plus-function claim limitation is found to be indefinite based on failure of the specification to disclose sufficient corresponding structure, materials, or acts that perform the entire claimed function, then the claim limitation necessarily lacks an adequate written description. Thus, when a claim is rejected as indefinite under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph because there is no corresponding structure, materials, or acts, or an inadequate disclosure of corresponding structure, materials, or acts, for a means- (or step-) plus-function claim limitation, then the claim must also be rejected under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, for lack of an adequate written description.” (emphasis added)
In the instant case, each of the “input unit,” “control unit,” “propeller speed controller,” and/or “engine controller” of corresponding Claims 1-2 and 14-17 are not properly described in the application as filed because no structure or material is described which is capable of performing the recited functions of the means-plus-function claim limitations. For instance, the figures merely show boxes for the corresponding input unit 14, control unit 7, propeller speed controller 21, and/or engine controller 40, and are otherwise devoid of detail regarding the structure. The Abstract and Specification are similarly devoid of structure, and only disclose details regarding function and/or mirror the claimed limitations. Therefore, the claim limitations regarding the “input unit,” “control unit,” “propeller speed controller,” and/or “engine controller” respectively lack an adequate written description.
In the interest of compact prosecution, in the instance that each of the “input unit,” “control unit,” “propeller speed controller,” and/or “engine controller” of corresponding Claims 1-2 and 14-17 are directed to either CPUs or controlling software, it is remains that the elements do not comply with the written description requirement in accordance with MPEP 2161.
MPEP 2161 states: “It is “not enough that one skilled in the art could write a program to achieve the claimed function because the specification must explain how the inventor intends to achieve the claimed function to satisfy the written description requirement. See, e.g., Vasudevan Software, Inc. v. MicroStrategy, Inc., 782 F.3d 671, 681-683, 114 USPQ2d 1349, 1356, 1357 (Fed. Cir. 2015) (reversing and remanding the district court’s grant of summary judgment of invalidity for lack of adequate written description where there were genuine issues of material fact regarding "whether the specification show[ed] possession by the inventor of how accessing disparate databases is achieved"). If the specification does not provide a disclosure of the computer and algorithm in sufficient detail to demonstrate to one of ordinary skill in the art that the inventor possessed the invention a rejection under 35 U.S.C. 112(a) or pre-AIA 35 U.S.C. 112, first paragraph, for lack of written description must be made.” (emphasis added)
For example, the Specification substantially mirrors the language of the claim, and is otherwise entirely devoid of any algorithm, steps, procedure, or flowchart which would detail the software and/or algorithm required by the claim. Therefore, in the instance that the identified elements are directed to either CPUs or controlling software, “the algorithm or steps/procedure taken to perform the function are not described with sufficient detail so that one of ordinary skill in the art would understand how the inventor intended the function to be performed” (MPEP 2161(I)).
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-2 and/or 14-17 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claims 1-2 and/or 14-17 respectively recite, “input unit,” “control unit,” “propeller speed controller,” and/or “engine controller”, and the metes and bounds of the claim are indeterminate in accordance with MPEP 2163. There is neither corresponding structure, materials, or acts, nor an inadequate disclosure of corresponding structure, materials, or acts, for the means-plus-function claim limitation, and one of ordinary skill in the art is not apprised of the scope of the claim.
Claim 15 recites “near”, which is a relative term which renders the claim indefinite. The term “near” is not defined by the claim, the specification does not provide a standard for ascertaining the requisite degree, and one of ordinary skill in the art would not be reasonably apprised of the scope of the invention.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-2 and 14-17 are rejected under 35 U.S.C. 102(a)(1) as being clearly anticipated by Yamazaki (US 2010/0121505).
As noted in the 35 USC 112 clarity rejections elsewhere above, a great deal of confusion and uncertainty exists as to the proper metes and bounds of numerous claim limitations. In the interest of compact prosecution, the examiner has applied the prior art under 35 U.S.C. 102 and/or 103 in as best as the claims can be understood. However, in accordance with MPEP §2173, the Office is not held to any undue speculation on the scope of the claims. See In re Wilson, 424 F.2d 1382, 1385 (CCPA 1970); In re Steele, 305 F.2d 859, 134 USPQ 292 (CCPA 1962).
The current application is related to EPO Application No. 23205493.2 and the current claims 1-2 and 14-17 are substantially similar in scope to the corresponding EPO claims 1-2 and 11-14. By adopting and incorporating herein by reference the explanations of the closest prior art as set forth in the Search Report, 1 the examiner meets the burdens of 35 U.S.C. 132(a)2 [e.g., insomuch as the reasons for rejection and references are stated and the Search Report provides such information as may be useful in judging the propriety of continuing the prosecution of this application] and 37 CFR 1.104(c)(2)3 [e.g., insomuch as the explanations of the Search Report are sufficient to make the pertinence of each reference apparent]. See the copy of the Search Report filed in this current application on 10/29/2024.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to T. S. FIX whose telephone number is (571)272-8535. The examiner can normally be reached M-Th 10a-3p.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Minnah Seoh can be reached at 5712707778. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/T. SCOTT FIX/Primary Examiner, Art Unit 3618
1 See MPEP 1893.03(e)(II) which permits the examiner to adopt any portion or all of any report on patentability of the IPEA or ISA that would be relevant to U.S. practice, e.g., explanations of prior art, etc.
235 U.S.C.132(a): Whenever, on examination, any claim for a patent is rejected, or any objection or requirement made, the Director shall notify the applicant thereof, stating the reasons for such rejection, or objection or requirement, together with such information and references as may be useful in judging of the propriety of continuing the prosecution of his application; and if after receiving such notice, the applicant persists in his claim for a patent, with or without amendment, the application shall be re-examined. No amendment shall introduce new matter into the disclosure of the invention. [emphasis added]
3 37 CFR 1.104(c)(2): In rejecting claims for want of novelty or for obviousness, the examiner must cite the best references at his or her command. When a reference is complex or shows or describes inventions other than that claimed by the applicant, the particular part relied on must be designated as nearly as practicable. The pertinence of each reference, if not apparent, must be clearly explained and each rejected claim specified. [emphasis added]
Prosecution Insights