Prosecution Insights
Last updated: July 17, 2026
Application No. 18/021,849

MOTION EVALUATION METHOD, COMPUTER PROGRAM, AND MOTION EVALUATION SYSTEM

Final Rejection §101§103
Filed
Feb 17, 2023
Priority
Sep 03, 2020 — nonprovisional of PCTJP2020033449
Examiner
MELHUS, BENJAMIN S
Art Unit
3791
Tech Center
3700 — Mechanical Engineering & Manufacturing
Assignee
Nippon Telegraph and Telephone Corporation
OA Round
2 (Final)
60%
Grant Probability
Moderate
3-4
OA Rounds
0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 60% of resolved cases
60%
Career Allowance Rate
242 granted / 400 resolved
-9.5% vs TC avg
Strong +44% interview lift
Without
With
+43.5%
Interview Lift
resolved cases with interview
Typical timeline
3y 4m
Avg Prosecution
29 currently pending
Career history
442
Total Applications
across all art units

Statute-Specific Performance

§101
10.7%
-29.3% vs TC avg
§103
73.7%
+33.7% vs TC avg
§102
10.9%
-29.1% vs TC avg
§112
3.7%
-36.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 400 resolved cases

Office Action

§101 §103
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 . Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claim(s) 1-7 is/are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Representative claim(s) 7 recites A motion evaluation system comprising: a plurality of sensors configured to acquire a plurality of time-series data related to a motion of a person; a memory storing instructions; and at least one processor connected to the memory and executes the instructions to: remove noise in each of the plurality of the time- series data; extract data of an on-set section in which the motion of the person is performed from each of the plurality of the time-series data from which the noise has been removed; through performing down-sampling processing in which data of the on-set sections overlapped with each other or included in a certain time period in the plurality of the time-series data are defined as a plurality of data groups, data lengths of the data in each of the data groups are unified, and the plurality of data whose lengths have been unified are combined, compress the data groups; evaluate the motion of the person on the basis of the compressed data groups; and transmit an evaluation result obtained by evaluation of the motion to a receiving device held by the person so as to notify the evaluation result to the person. (abstract portions shown in emphasis) Step 2A Prong One The recitation of removing noise, extracting data, aligning and compression data, and then evaluating motion encompasses performance of the limitation in the mind but for the recitation of mere extrasolutionary activity (i.e., mere data gathering and/or nominal output) and/or otherwise nominal and generic computer elements (2019 Patent Eligibility Guidance – hereafter ‘2019 PEG’ - p. 55; see also MPEP § 2106.05(a), (d) and (g)) (e.g., processing ‘units’). For example, but for the recitation of obtaining/acquiring data and/or generic processing ‘units’ / functional steps to perform abstract limitations, the steps of ‘extracting’, ‘aligning’ and then ‘evaluating’ encompasses a clinician (mentally) reviewing sensor data to then (through a mental series of steps) evaluate a motion of a person. If a claim, under BRI, covers performance of the limitations in the mind but for the mere recitation of extrasolutionary activity (and/or otherwise generic computing elements) then the claim falls within the “Mental Processes” grouping of abstract ideas. Accordingly, the claim recites an abstract idea under step 2A prong one of the Mayo framework as set forth in the 2019 PEG. Step 2A Prong Two This judicial exception is not integrated into a practical application. Claim 7 only recites additional elements of extrasolutionary activity — in particular, a sensor — and/or generic computing structures / elements without further sufficient detail that would tie the abstract portions of the claim into a specific practical application (2019 PEG p. 55 - the instant claim, for example, does not tie into a particular machine, a sufficiently particular form of data or signal collection — via the claimed data obtaining, or a sufficiently particular form of display or computing/processing architecture / structure). Independent claim(s) 1 and 6 encounter the same issues as claim(s) 7 mutatis mutandis. Dependent claim(s) 2-5 merely add detail to the abstract portions of the claim but do not otherwise encompass any additional elements which tie the claim(s) into a particular application / integration (the dependent claim(s) reciting generic ‘units’ or ‘steps’ which encompass mere computer instructions to carry out an otherwise wholly abstract idea). Accordingly, the claim(s) are not integrated into a practical application under step 2A prong two. Step 2B The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of extrasolutionary activity (data gathering and display outputting) and generic computing elements cannot amount to significantly more than an abstract idea. For the independent claim portions and dependent claims which provide additional elements of extrasolutionary data gathering, MPEP § 2106.05(g) establishes that mere data gathering for determining a result does not amount to significantly more: 2106.05(g) Insignificant Extra-Solution Activity Another consideration when determining whether a claim integrates the judicial exception into a practical application in Step 2A Prong Two or recites significantly more in Step 2B is whether the additional elements add more than insignificant extra-solution activity to the judicial exception. The term "extra-solution activity" can be understood as activities incidental to the primary process or product that are merely a nominal or tangential addition to the claim. Extra-solution activity includes both pre-solution and post-solution activity. An example of pre-solution activity is a step of gathering data for use in a claimed process, e.g., a step of obtaining information about credit card transactions, which is recited as part of a claimed process of analyzing and manipulating the gathered information by a series of steps in order to detect whether the transactions were fraudulent. An example of post-solution activity is an element that is not integrated into the claim as a whole, e.g., a printer that is used to output a report of fraudulent transactions, which is recited in a claim to a computer programmed to analyze and manipulate information about credit card transactions in order to detect whether the transactions were fraudulent. As explained by the Supreme Court, the addition of insignificant extra-solution activity does not amount to an inventive concept, particularly when the activity is well-understood or conventional. Parker v. Flook, 437 U.S. 584, 588-89, 198 USPQ 193, 196 (1978). In Flook, the Court reasoned that "[t]he notion that post-solution activity, no matter how conventional or obvious in itself, can transform an unpatentable principle into a patentable process exalts form over substance. A competent draftsman could attach some form of post-solution activity to almost any mathematical formula". 437 U.S. at 590; 198 USPQ at 197; Id. (holding that step of adjusting an alarm limit variable to a figure computed according to a mathematical formula was "post-solution activity"). See also Mayo Collaborative Servs. v. Prometheus Labs. Inc., 566 U.S. 66, 79, 101 USPQ2d 1961, 1968 (2012) (additional element of measuring metabolites of a drug administered to a patient was insignificant extra-solution activity). Examiners should carefully consider each claim on its own merits, as well as evaluate all other relevant considerations, before making a determination of whether an element (or combination of elements) is insignificant extra-solution activity. In particular, evaluation of the particular machine and particular transformation considerations (see MPEP § 2106.05(b) and (c), respectively), the well-understood, routine, conventional consideration (see MPEP § 2106.05(d)), and the field of use and technological environment consideration (see MPEP § 2106.05(h)) may assist examiners in making a determination of whether an element (or combination of elements) is insignificant extra-solution activity. Note, however, that examiners should not evaluate the well-understood, routine, conventional consideration in the Step 2A Prong Two analysis, because that consideration is only evaluated in Step 2B. This consideration is similar to factors used in past Office guidance (for example, the now superseded Bilski and Mayo analyses) that were described as mere data gathering in conjunction with a law of nature or abstract idea. When determining whether an additional element is insignificant extra-solution activity, examiners may consider the following: (1) Whether the extra-solution limitation is well known. See Bilski v. Kappos, 561 U.S. 593, 611-12, 95 USPQ2d 1001, 1010 (2010) (well-known random analysis techniques to establish the inputs of an equation were token extra-solution activity); Flook, 437 U.S. at 593-95, 198 USPQ at 197 (a formula would not be patentable by only indicating that is could be usefully applied to existing surveying techniques); Intellectual Ventures I LLC v. Erie Indem. Co., 850 F.3d 1315, 1328-29, 121 USPQ2d 1928, 1937 (Fed. Cir. 2017) (the use of a well-known XML tag to form an index was deemed token extra-solution activity). Because this overlaps with the well-understood, routine, conventional consideration, it should not be considered in the Step 2A Prong Two extra-solution activity analysis. (2) Whether the limitation is significant (i.e. it imposes meaningful limits on the claim such that it is not nominally or tangentially related to the invention). See Ultramercial, Inc. v. Hulu, LLC, 772 F.3d 709, 715-16, 112 USPQ2d 1750, 1755 (Fed. Cir. 2014) (restricting public access to media was found to be insignificant extra-solution activity); Apple, Inc. v. Ameranth, Inc., 842 F.3d 1229, 1242, 120 USPQ2d 1844, 1855 (Fed. Cir. 2016) (in patents regarding electronic menus, features related to types of ordering were found to be insignificant extra-solution activity). This is considered in Step 2A Prong Two and Step 2B. (3) Whether the limitation amounts to necessary data gathering and outputting, (i.e., all uses of the recited judicial exception require such data gathering or data output). See Mayo, 566 U.S. at 79, 101 USPQ2d at 1968; OIP Techs., Inc. v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1092-93 (Fed. Cir. 2015) (presenting offers and gathering statistics amounted to mere data gathering). This is considered in Step 2A Prong Two and Step 2B. Below are examples of activities that the courts have found to be insignificant extra-solution activity: Mere Data Gathering: i. Performing clinical tests on individuals to obtain input for an equation, In re Grams, 888 F.2d 835, 839-40; 12 USPQ2d 1824, 1827-28 (Fed. Cir. 1989); Some cases have identified insignificant computer implementation as an example of insignificant extra-solution activity. See e.g., Fort Props., Inc. v. Am. Master Lease LLC, 671 F.3d 1317, 1323-24, 101 USPQ2d 1785, 1789-90 (Fed. Cir. 2012); Bancorp Servs., LLC v. Sun Life Assur. Co. of Canada, 687 F.3d 1266, 1280-81, 103 USPQ2d 1425, 1434-35 (Fed. Cir. 2012). Other cases have considered these types of limitations as mere instructions to apply a judicial exception. See MPEP § 2106.05(f) for more information about insignificant computer implementation. For claim limitations that add insignificant extra-solution activity to the judicial exception (e.g., mere data gathering in conjunction with a law of nature or abstract idea), examiners should explain in an eligibility rejection why they do not meaningfully limit the claim. For example, an examiner could explain that adding a final step of storing data to a process that only recites computing the area of a space (a mathematical relationship) does not add a meaningful limitation to the process of computing the area. For more information on formulating a subject matter eligibility rejection, see MPEP § 2106.07(a). The extrasolutionary activity/step(s) of sensing to acquire data as presently recited, cannot provide an inventive concept which amounts to significantly more than the recited abstract idea. For the independent claims as well as the dependent claims merely reciting generic computer elements and activity (memory/storage, processing units), MPEP § 2106.05(d)(II) establishes computer-based elements which are considered to be well-understood, routine, and conventional when recited at a high level of generality II. ELEMENTS THAT THE COURTS HAVE RECOGNIZED AS WELL-UNDERSTOOD, ROUTINE, CONVENTIONAL ACTIVITY IN PARTICULAR FIELDS Because examiners should rely on what the courts have recognized, or those of ordinary skill in the art would recognize, as elements that describe well‐understood, routine activities, the following section provides examples of elements that have been recognized by the courts as well-understood, routine, conventional activity in particular fields. It should be noted, however, that many of these examples failed to satisfy other considerations (e.g., because they were recited at a high level of generality and thus were mere instructions to apply an exception, or were insignificant extra-solution activity). Thus, examiners should carefully analyze additional elements in a claim with respect to all relevant Step 2B considerations, including this consideration, before making a conclusion as to whether they amount to an inventive concept. The courts have recognized the following computer functions as well‐understood, routine, and conventional functions when they are claimed in a merely generic manner (e.g., at a high level of generality) or as insignificant extra-solution activity. i. Receiving or transmitting data over a network, e.g., using the Internet to gather data, Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362 (utilizing an intermediary computer to forward information); TLI Communications LLC v. AV Auto. LLC, 823 F.3d 607, 610, 118 USPQ2d 1744, 1745 (Fed. Cir. 2016) (using a telephone for image transmission); OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015) (sending messages over a network); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network); but see DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1258, 113 USPQ2d 1097, 1106 (Fed. Cir. 2014) ("Unlike the claims in Ultramercial, the claims at issue here specify how interactions with the Internet are manipulated to yield a desired result‐‐a result that overrides the routine and conventional sequence of events ordinarily triggered by the click of a hyperlink." (emphasis added)); ii. Performing repetitive calculations, Flook, 437 U.S. at 594, 198 USPQ2d at 199 (recomputing or readjusting alarm limit values); Bancorp Services v. Sun Life, 687 F.3d 1266, 1278, 103 USPQ2d 1425, 1433 (Fed. Cir. 2012) ("The computer required by some of Bancorp’s claims is employed only for its most basic function, the performance of repetitive calculations, and as such does not impose meaningful limits on the scope of those claims."); iii. Electronic recordkeeping, Alice Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. 208, 225, 110 USPQ2d 1984 (2014) (creating and maintaining "shadow accounts"); Ultramercial, 772 F.3d at 716, 112 USPQ2d at 1755 (updating an activity log); iv. Storing and retrieving information in memory, Versata Dev. Group, Inc. v. SAP Am., Inc., 793 F.3d 1306, 1334, 115 USPQ2d 1681, 1701 (Fed. Cir. 2015); OIP Techs., 788 F.3d at 1363, 115 USPQ2d at 1092-93; v. Electronically scanning or extracting data from a physical document, Content Extraction and Transmission, LLC v. Wells Fargo Bank, 776 F.3d 1343, 1348, 113 USPQ2d 1354, 1358 (Fed. Cir. 2014) (optical character recognition); and vi. A Web browser’s back and forward button functionality, Internet Patent Corp. v. Active Network, Inc., 790 F.3d 1343, 1348, 115 USPQ2d 1414, 1418 (Fed. Cir. 2015). Accordingly, the computer elements, as presently limited, cannot provide an inventive concept since they fall under a generic structure and/or function that does not add a meaningful additional feature to the judicial exception(s) of the claim(s). The claim(s) are not patent eligible under step 2B. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claim(s) 1-7 is/are rejected under 35 U.S.C. 103 as being unpatentable over Mahoor (US 20170156622 A1) in view of Elwood (US 20220346695 A1). For claim 1, Mahoor teaches A motion evaluation method comprising: acquiring a plurality of time-series data related to a motion of a person by means of a plurality of sensors; removing noise in each of the a plurality of the time-series data; [step 115] extracting data of an on-set section in which the motion of the person is performed from each of the plurality of the time-series data from which the noise has been removed; [verbatim in ¶65, more generally regression and PCA to find movement event in ¶¶49-65] through performing down-sampling processing in which data of the on-set sections overlapped with each other or included in a certain time period in the plurality of the timeseries data are defined as a plurality of data groups, data lengths of the data in each of the data groups are unified, and the plurality of data whose lengths have been unified are combined, compressing the data groups; [¶32 ¶34 ¶43 ¶48 ¶56 ¶72] evaluating the motion of the person on the basis of the compressed data groups: [event detection and analysis at end of Figs. 1-3, ¶¶73-74 et seq.] Mahoor fails to teach transmitting a result to a handheld device. Elwood teaches a motion evaluation method [abstract, ¶35] including a step of transmitting an evaluation result to a patient’s handheld device. [¶38 ¶48 ¶52] It would have been obvious to one of ordinary skill at the time the invention was filed to modify the method of Mahoor to incorporate the result transmission of Elwood in order to aid in care for the person (e.g., clinical care or self care). As motivated by Elwood ¶38 ¶48 ¶52 ¶76. For claim 2, Mahoor teaches The motion evaluation method according to claim 1, wherein in the extracting, a section from a start point where the person is assumed to have started the motion to an end point where the person is assumed to have ended the motion is extracted as the on-set section on each of the time-series data. [¶65] For claim 3, Mahoor teaches The motion evaluation method according to claim 2, wherein, in the extracting, a value of the time-series data is compared with a value of a certain section before and the on-set section is extracted from each of the time-series data with a point at which the value of the time-series data increases or decreases by a threshold value or more as the start point and a point that approaches an average value again at a time after the start point as the end point. [¶54] For claim 4, Mahoor teaches The motion evaluation method according to claim 2, wherein, in the aligning, with data of a plurality of the on-set sections extracted in the extracting, the length of the data of the on-set section included in the data groups is aligned by matching start points of the data of all the on-set sections with data having the earliest time at the start point and matching end points of the data of all the on-set sections with data having the latest time at the end point. [¶65] For claim 5, Mahoor teaches The motion evaluation method according to claim 1, wherein, in the evaluating, the motion of the person is evaluated using a trained model trained to output an evaluation score by inputting the compressed data groups. [¶¶50-52, ¶74, ¶77, ¶88] Response to Arguments Applicant's 12/30/25 arguments with respect to § 101 have been fully considered but they are not persuasive. Applicant argues in remarks p. 6-8 that the claim(s) are eligible as they encompass an improvement to the technology. However, Applicant’s supposed improvement would be to the analytical and thus abstract portions of the claim (the data handling, the analyses of the data) where MPEP § 2106.05(a)(II) establishes “[I]t is important to keep in mind that an improvement in the abstract idea itself…is not an improvement in technology.” Applicant argues in remarks p. 8 that the transmission of the result to a handheld device encompasses a practical integration of the claim(s). Examiner respectfully disagrees. The transmission step and the device are recited with inadequate specificity to constitute a particular machine / practical integration under step 2A prong two. The device is described as merely a device ‘held by the person’ and the result is not displayed or otherwise presented with any tangible particularity. Applicant argues in remarks p. 9-10 that Mahoor does not teach a downsampling step akin to that detailed in this application’s spec ¶40. In response to applicant's argument that the references fail to show certain features of the invention, it is noted that the features upon which applicant relies (i.e., the specific language of spec ¶40) are not recited in the rejected claim(s). Although the claims are interpreted in light of the specification, limitations from the specification are not read into the claims. See In re Van Geuns, 988 F.2d 1181, 26 USPQ2d 1057 (Fed. Cir. 1993). Other than the citation to specification ¶40 which is not reflected in the claim(s), Applicant has not shown how the claimed downsampling differs from the downsampling taught by Mahoor. 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). Any inquiry concerning this communication or earlier communications from the examiner should be directed to BENJAMIN S MELHUS whose telephone number is (571)272-5342. The examiner can normally be reached Monday - Friday | 9:00 AM - 5:00 PM. 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, Robert Chen can be reached on 571-272-3672. 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. /BENJAMIN S MELHUS/ Primary Examiner, Art Unit 3791
Read full office action

Prosecution Timeline

Feb 17, 2023
Application Filed
Oct 01, 2025
Non-Final Rejection mailed — §101, §103
Dec 30, 2025
Response Filed
Jun 12, 2026
Final Rejection mailed — §101, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12667270
CABLE FOR USE WITH PRESSURE MONITORING CATHETERS
3y 0m to grant Granted Jun 30, 2026
Patent 12642453
CALCULATION DEVICE, CALCULATION METHOD, AND PROGRAM RECORDING MEDIUM
3y 4m to grant Granted Jun 02, 2026
Patent 12635957
METHODS AND KITS FOR ASSESSING NEUROLOGICAL AND OPHTHALMIC FUNCTION AND LOCALIZING NEUROLOGICAL LESIONS
5y 3m to grant Granted May 26, 2026
Patent 12629501
MEDICAL DEVICE WITH SUPPORT MEMBER
4y 9m to grant Granted May 19, 2026
Patent 12633401
MODULAR AUTOMATED PHYSICAL HEALTH TESTING SYSTEMS AND ASSOCIATED DEVICES AND METHODS
2y 9m to grant Granted May 19, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
60%
Grant Probability
99%
With Interview (+43.5%)
3y 4m (~0m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 400 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month