DETAILED ACTION
The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action.
Claim Interpretation
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:
“command and control module” in, for example, Claim 1.
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
Claims 1, 4-13, and 15-18 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.
The corresponding means-plus-function limitation(s) were analyzed in accordance with MPEP 2163, e.g. “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), and in accordance with MPEP 2161.01, e.g. “[e]ven if a claim is not construed as a means-plus-function limitation under 35 U.S.C. 112(f), computer-implemented functional claim language must still be evaluated for sufficient disclosure under the written description and enablement requirements of 35 U.S.C. 112(a)” and “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).
As such, the instant disclosure was analyzed for any controlling algorithm. The disclosure does describe a “command and control module 130” (e.g., para. 40), with a “CPU 134” and “stored operating instructions” (para. 37), which is interpreted as the claimed “command and control module.” However, fig. 5 does not show any explicit detail to the module 130 and only shows black boxes representing common/known structure; and although para. 37 references “stored operating instructions,” the controlling algorithm is only nominally disclosed, the Specification is entirely devoid of any algorithm, steps, procedure, or flowchart which would detail the “stored operating instructions,” and is likewise absent any substantial discussion of the claimed “command and control module.” Therefore, the algorithm or steps/procedure taken to perform the claimed computerized functions 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 in accordance with MPEP 2161.
Following from the above analysis, the claim limitations regarding the “command and control module” lack an adequate written description in accordance with MPEP 2163 and/or MPEP 2161.
Claim Rejections - 35 USC § 112
Claims 1, 4-13, and 15-18 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.
The claims respectively recite, a “command and control module,”, e.g. which requires controlling software which is only nominally disclosed, and thereafter the metes and bounds of the claim are indeterminate in accordance with MPEP 2163. There is an inadequate disclosure of corresponding structure, materials, or acts for the means-plus-function claim limitations, and one of ordinary skill in the art is not apprised of the scope of the claim. Prior art is not provided regarding said limitations.
Claim Rejections - 35 USC § 102
Claim 19 is rejected under 35 U.S.C. 102(a)(1) as being anticipated by Ben-Tzvi et al. (US 2013/0062153)
Regarding the claims, the prior art discloses the following:
19. A robotic crawler comprising: a first crawler system (1) configured to engage and selectively couple with a surface; a second crawler system (either of 1, by fig. 21, 2 by fig. 8, or 4 by fig. 3) spaced apart from the first crawler system and configured to engage and selectively couple with the surface; a linkage (43, 39, 41 by para. 84) coupled between the first crawler system and the second crawler system, the linkage having an actuator (including 40, 42) and a bar member (any of 43, 39, 41), the actuator comprises a lead screw (40) coupled to a motor (42), wherein the bar member is a multi-bar linkage that rotates (i.e., 41 rotates about 40, causing 39 to pivot about 41) in response to rotation of the lead screw (40); wherein the actuator (including 40, 42) is configured to selectively disengage (e.g., drive fig. 16, clamp fig. 17, neutral fig. 18) one of the first crawler system or the second crawler system from the surface.
Response to Arguments
Applicant’s arguments with respect to the claims have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.
Applicant's arguments specifically regarding the amended language of “command and control module” have been fully considered but they are not persuasive. In accordance with MPEP 2163 and/or MPEP 2161, the claimed limitations require controlling software which is not adequately disclosed. Specifically with respect to MPEP 2161.01, “[i]t 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 “ and “[i]f 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). Please see rejections under 35 U.S.C. 112 in the body of the rejection above.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
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
Prosecution Insights