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 . Claims 1, 3-4, and 7-18 are pending.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 07/10/2026 has been entered.
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.
Claims 1, 3-4, and 7-18 are rejected under 35 USC § 101 because the claimed invention is directed to an abstract idea without significantly more.
Step 1 (The Statutory Categories): Is the claim to a process, machine, manufacture or composition of matter? MPEP 2106.03.
Per Step 1, claim 1 is directed to a device (i.e., a machine), claim 17 is directed to a method (i.e., process), and claim 18 is directed to a device (i.e., machine). Thus, the claims are directed to statutory categories of invention. However, the claims are rejected under 35 U.S.C. § 101 because they are directed to an abstract idea, a judicial exception, without reciting additional elements that integrate the judicial exception into a practical application.
The analysis proceeds to Step 2A Prong One.
Step 2A Prong One: Does the claim recite an abstract idea, law of nature, or natural phenomenon? MPEP 2106.04.
The abstract idea of claim 1 is:
store a registered site having a first location, wherein the registered site is registered based on a travel history of the vehicle, wherein the first location is a point of interest with a high frequency of travel or drop-by;
acquire an input of data indicating an abnormal level associated with a predetermined abnormality of the vehicle, wherein the input of data is time-series data comprising engine rotation speeds and engine temperatures obtained from one or more parts of the vehicle;
acquire repair site data of a repair site where a part of the vehicle in which the predetermined abnormality is detected is to be repaired or to be replaced, wherein an inventory status of a replacement part for the target part or a reservation status of the repair site is acquired;
the repair site data is acquired according to the abnormal level and the inventory status or the reservation status;
acquire a current location of the vehicle;
determine, based on the abnormal level, whether to acquire the repair site data of the repair site starting from the registered site at the first location or to acquire the repair site data of the repair site starting from the current location, which is a second location different from the first location;
when the abnormal level is less than a predetermined value, acquire the repair site data of the repair site starting from the registered site at the first location;
when the abnormal level is equal to or more than a predetermined value, acquire the repair site data of the repair site starting from the current location at the second location;
transmit the acquired repair site data;
based on the acquired repair site data, determine a repair route to the repair site for the vehicle according to the abnormal level, wherein the repair route starts at either the registered site at the first location or the current location at the second location.
The abstract idea of claim 17 is:
storing a registered site registered having a first location, wherein the registered site is based on a travel history of the vehicle, wherein the first location is a point of interest with a high frequency of travel or drop-by;
acquiring an inventory status of a replacement part for a target part or a reservation status of a repair site where the target part of the vehicle in which a predetermined abnormality is detected is to be repaired or to be replaced;
acquiring an input of data indicating an abnormal level associated with a predetermined abnormality of the vehicle, wherein the input of data is time-series data comprising engine rotation speeds and engine temperatures obtained from one or more parts of the vehicle;
acquiring repair site data of the repair site according to the abnormal level and the inventory status or the reservation status;
acquiring a current location of the vehicle;
determining, based on the abnormal level, whether to acquire the repair site data of the repair site starting from the registered site at the first location or to acquire the repair site data of the repair site starting from the current location, which is a second location different from the first location;
when the abnormal level is less than a predetermined value, acquiring the repair site data of the repair site starting from the registered site at the first location;
when the abnormal level is equal to or more than a predetermined value, acquiring the repair site data of the repair site starting from the current location at the second location;
transmitting the acquired repair site data;
based on the acquired repair site data, determine a repair route for the vehicle to the repair site according to the abnormal level,
wherein the repair route starts at either the registered site at the first location or the current location at the second location.
The abstract idea of claim 18 is:
store a registered site having a first location, wherein the registered site is registered based on a travel history of the vehicle, wherein the first location is a point of interest with a high frequency of travel or drop-by;
acquire an input of data indicating an abnormal level associated with a predetermined abnormality of the vehicle, wherein the input of data is time-series data comprising engine rotation speeds and engine temperatures obtained from one or more parts of the vehicle;
acquire repair site data of a repair site where a part of the vehicle in which the predetermined abnormality is detected is to be repaired or to be replaced;
transmit the acquired repair site data;
acquire a current location of the vehicle;
determine, based on the abnormal level, whether to acquire the repair site data of the repair site starting from the registered site at the first location or to acquire the repair site data of the repair site starting from the current location, which is a second location different from the first location;
when the abnormal level is less than a predetermined value, acquire the repair site data of the repair site starting from the registered site at the first location;
when the abnormal level is equal to or more than a predetermined value, acquire the repair site data of the repair site starting from the current location at the second location;
based on the acquired repair site data, determine a repair route for the vehicle to the repair site according to the abnormal level,
wherein the repair route starts at either the registered site at the first location or the current location at the second location.
The abstract idea steps italicized above recite matching equipment with repair sites based on issue severity and inventory/reservation data, which could be performed mentally, including with pen and paper. This is further supported by paragraph [0007] of applicant’s specification as filed. If a claim limitation, under its broadest reasonable interpretation (BRI), covers performance of the limitation in the mind, including observations, evaluations, judgements, and/or opinions, then it falls within the Mental Processes – Concepts Performed in the Human Mind grouping of abstract ideas. Accordingly, the claim recites an abstract idea.
Additionally and alternatively, the claim is directed to coordination between users and repair sites, and actions based on user input, which constitutes a process that, under its BRI, covers managing personal behavior relationships, interactions between people. This is further supported by paragraph [0007] of applicant’s specification as filed. If a claim limitation, under its BRI, covers managing personal behavior relationships, interactions between people, including social activities, teaching, and/or following rules or instructions, then it falls within the Certain Methods of Organizing Human Activity – Managing Personal Behavior Relationships, Interactions Between People grouping of abstract ideas. Accordingly, the claim recites an abstract idea.
Step 2A, Prong 2: Does the claim recite additional elements that integrate the judicial exception into a practical application? MPEP §2106.04.
This judicial exception is not integrated into a practical application because the additional elements are merely instructions to apply the abstract idea to a computer, described in MPEP 2106.05(f), and/or are insignificant extra-solution activity, described in MPEP 2106.05(g).
Claims 1 and 18 recite the following additional elements: repair site transmission device; abnormality detection unit of the repair site transmission device; one or more sensors installed; to an external device; cause the vehicle to automatically travel the determined repair route to the repair site.
Claim 17 recites the following additional elements: abnormality detection unit of the repair site transmission device; one or more sensors installed; to an external device; causing the vehicle to automatically travel the determined repair route to the repair site.
The elements “repair site transmission device; abnormality detection unit of the repair site transmission device; one or more sensors installed; and to an external device” represent merely instructions to apply the abstract idea to a computer, per MPEP §2106.05(f). Applicant has only described generic computing elements in their specification, as seen in paragraphs [0010] – [0015] of applicant’s specification as filed, for example.
Additionally and alternatively, the element “cause the vehicle to automatically travel the determined repair route to the repair site” is an example of an insignificant extra- solution activity, described in MPEP 2106.05(g), given that it simply relates to 1) making a routing decision; and 2) insignificant application. The combination of these elements is nothing more than a generic computing system. Because the additional elements are merely instructions to apply the abstract idea to a computer and/or are no more than an idea of a solution or outcome, as described in MPEP 2106.05(f), and/or are insignificant extra-solution activity, as described in MPEP 2106.05(g), they do not integrate the abstract idea into a practical application.
Accordingly, these additional elements, alone and in combination, do not integrate the judicial exception into a practical application. The claim is directed to an abstract idea.
Step 2B (The Inventive Concept): Does the claim recite additional elements that amount to significantly more than the judicial exception? MPEP §2106.05.
Step 2B involves evaluating the additional elements to determine whether they amount to significantly more than the judicial exception itself.
The examination process involves carrying over identification of the additional element(s) in the claim from Step 2A Prong Two and carrying over conclusions from Step 2A Prong Two on the considerations discussed in MPEP §2106.05(f).
The additional elements and their analysis are therefore carried over: applicant has merely recited elements that facilitates the tasks of the abstract idea, as described in MPEP §2106.05(f).
The considerations under MPEP 2106.05(g) are reevaluated; however, they're still not significantly more. Para. [0041] of applicant's specification as filed indicate the activity is well- understood, routine, and conventional, given that applicant has not described the features in any detail. See MPEP 2106.05(d). Para. [0041] are reproduced here:
[0041] Next, the vehicle2 will be described. The vehicle2 is an automobile with a navigation device installed, and is also a manned automobile for which travel control is performed automatically or manually. Further, in a case where the vehicle 2 is a vehicle managed by a business operator that is a user, such as a car-share vehicle, it may be an unmanned vehicle that can be controlled to travel automatically. Thevehicle2 includes the navigation device, which based on the current location of the vehicle 2 and a user's input, sets a travel route from a departure site to a destination, and presents route guidance to the user. For example, the navigation device displays a map, the current location of the vehicle2, the location of the destination, and the travel route on a display provided in the navigation device.
Further, the combination of these elements is nothing more than a generic computing system. When the claim elements above are considered, alone and in combination, they do not amount to significantly more.
Therefore, per Step 2B, the additional elements, alone and in combination, are not significantly more. The claims are not patent eligible.
Further, the analysis takes into consideration all dependent claims as well:
Regarding claims 3-4, 7-9, and 15-16, applicant further narrows the abstract idea with additional step(s). There are no further additional elements to consider, beyond those highlighted above. This further narrowing of the abstract idea, similar to above, is also not patent eligible.
Claim 10 includes further additional elements with additional tasks that narrow the abstract idea: transmit a control instruction to display the target part to the external device. Similar to above, these additional elements do no more than apply the abstract idea to a computer, per MPEP 2106.05(f). When viewed alone or in combination, this does not integrate the abstract idea into practical application and is not significantly more.
Claim 11 includes further additional elements with additional tasks that narrow the abstract idea: from a device or database outside of the vehicle. Similar to above, these additional elements do no more than apply the abstract idea to a computer, per MPEP 2106.05(f). When viewed alone or in combination, this does not integrate the abstract idea into practical application and is not significantly more.
Claim 12 includes further additional elements with additional tasks that narrow the abstract idea: transmit a control instruction to display the registered site to the external device. Similar to above, these additional elements do no more than apply the abstract idea to a computer, per MPEP 2106.05(f). When viewed alone or in combination, this does not integrate the abstract idea into practical application and is not significantly more.
Claim 13 includes further additional elements with additional tasks that narrow the abstract idea: transmit a display instruction to display the repair site to the external device. Similar to above, these additional elements do no more than apply the abstract idea to a computer, per MPEP 2106.05(f). When viewed alone or in combination, this does not integrate the abstract idea into practical application and is not significantly more.
Claim 14 includes further additional elements with additional tasks that narrow the abstract idea: transmit a stop instruction to stop at the emergency stop site to the external device. Similar to above, these additional elements do no more than apply the abstract idea to a computer, per MPEP 2106.05(f). When viewed alone or in combination, this does not integrate the abstract idea into practical application and is not significantly more.
Accordingly, claims 1, 3-4, and 7-18 are rejected under 35 USC § 101 as being directed to non-statutory subject matter.
No Prior Art Applied to Claims 1, 3-4, and 7-18
Claims 1, 17, and 18
There is no prior art applied to claims 1, 17, and 18 (claim 1 being representative) because the cited prior art fails to disclose or suggest the complete feature set recited in the claims. Arantes (US 20200075027), considered the closest prior art, discloses:
(claim 1) A repair site transmission device for an automatically controllable vehicle configured to: {The system includes service computing device(s) that function as a repair site transmission device, being configured to acquire, process, and transmit repair site data (paragraphs 0022, 0077-0079).}
(claim 17) A repair site transmission method comprising {“Some implementations include arrangements and techniques (i.e., methods) for managing equipment.” (paragraph 0002).}
(claim 18) A repair site transmission device configured to {The system includes service computing device(s) that function as a repair site transmission device, being configured to acquire, process, and transmit repair site data (paragraphs 0022, 0077-0079).}
acquire repair site data of a repair site where a part of the vehicle in which the predetermined abnormality is detected is to be repaired or to be replaced {The system detects a vehicle abnormality (e.g., from sensor data) and, in response, acquires repair site data where the faulty part is to be repaired (paragraphs 0049, 0063, 0105).}
wherein an inventory status of a replacement part for the target part or a reservation status of the repair site is acquired; and {The system acquires inventory status of parts, repair site reservation status, and repair site data to determine optimal repair timing and location (paragraphs 0063, 0105, 0107).}
transmit the acquired repair site data to an external device {The system acquires repair site data (e.g., site name, GPS coordinates) and transmits it to external devices such as a technician device or operator device (paragraphs 0049, 0105).}
Bachant (US 20200364950) teaches:
the repair site data is acquired according to the abnormal level and the inventory status or the reservation status {The system determines the criticality level of an issue and, depending on the severity, selects and appropriate maintenance facility considering capacity, availability, and part specialization (i.e., inventory/reservation status) (paragraphs 0037, 0040-0042, 0049).}
acquire a current location of the vehicle {The autonomous vehicle determines and/or uses its location based on diagnostic data captured by sensors and further uses the vehicle’s current position in maintenance facility selection and routing (paragraphs 0014, 0031, 0042).}
cause the vehicle to automatically travel the determined repair route to the repair site {Upon determining the need for maintenance, the autonomous vehicle is instructed to autonomously drive to the selected maintenance facility (paragraphs 0039, 0051-0052).}
Ota (US 20200049524) teaches:
store a registered site having a first location, wherein the registered site is registered based on a travel history of the vehicle, wherein the first location is a point of interest with a high frequency of travel or drop-by {The system supports generating and storing vehicle travel history and registering a candidate estimated destination, including a POI, based on trip end positions in the vehicle’s travel history. [0035], [0041] – [0042], [0056]}
However, nor Arantes, Bachant, or Ota disclose or suggest “determine, based on the abnormal level, whether to acquire the repair site data of the repair site starting from the registered site at the first location or to acquire the repair site data of the repair site starting from the current location, which is a second location different from the first location; when the abnormal level is less than a predetermined value, acquire the repair site data of the repair site starting from the registered site at the first location; when the abnormal level is equal to or more than a predetermined value, acquire the repair site data of the repair site starting from the current location at the second location; based on the acquired repair site data, determine a repair route to the repair site for the vehicle according to the abnormal level, wherein the repair route starts at either the registered site at the first location or the current location at the second location.”
Examiner also considered the following additional references:
US 20160078695 A1, which teaches: Indicating a repair to perform on an asset based on historic data related to a repair on the asset and/or sensor data associated with the asset.
US 20060052921 A1, which teaches: The enhanced diagnostic software is downloaded to a mobile device if the software is not available in the mobile device. The software is executed for detecting an error condition in the mobile device. Several alternative actions are presented for solving the identified error condition. The alternative action is performed in response to selection by a user of mobile device.
US 20220318766 A1, which teaches: An information processing device includes a control unit that executes: selecting a single or plurality of shops where inspection or repair of a vehicle is capable of being performed; acquiring a single or plurality of destinations; and calculating a total time length of a first time length, a second time length and a third time length, about all combinations of a first shop and a first destination, the first shop being one of the single or plurality of shops, the first destination being one of the single or plurality of destinations, the first time length being a time length for movement of the vehicle from a departure point to the first shop, the second time length being a time length for the inspection or repair at the first shop, the third time length being a time length for movement from the first shop to the first destination.
US 20090157289 A1, which teaches: Navigation systems and services are described. The navigation services can include obtaining a route or route segment based on a location of a vehicle and a destination. Based on the route, a current fuel supply of the vehicle, and a number of factors related to fuel consumption, a refueling location can be estimated. A number of locations of fuel stations in proximity to the refueling location can be determined and presented to a user, for example, on a map showing the route.
Accordingly, there is no prior art applied to claims 1, 17, and 18. The rest of the claims, by virtue of their dependency, also have no prior art applied.
Response to Arguments
Applicant’s arguments filed on 07/10/2026 have been carefully considered.
Claim Objections
Claims objections are withdrawn in view of applicant’s amendments.
Rejections under 35 U.S.C. §101
Applicant’s arguments are not persuasive. The amendment requiring sensors to obtain time-series engine rotation speed and engine temperature data does not integrate the judicial exception into a practical application, as the sensors merely collect data used in performing the claimed determination and routing process. The fact that the claimed process may not practically be performed mentally does not, by itself, establish patent eligibility. Further, causing the vehicle to automatically travel the determined repair route merely implements the result of the abstract determination using vehicle components without providing an improvement to vehicle, sensor, or computing technology. Accordingly, when considered individually or in combination, the additional elements do not amount to significantly more than the judicial exception, and the rejection under 35 USC §101 is maintained.
Rejections under 35 U.S.C. §103
Applicant’s arguments with respect to patentability under 35 U.S.C. §103 have
been considered but are moot because there is no prior art applied to claims 1, 3-4, and 7-18.
In summary, examiner has responded to all arguments and found them unpersuasive.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CARLOS F MONTALVO whose telephone number is (703)756-5863. The examiner can normally be reached Monday - Friday 8:00AM - 5:30PM; First Fridays OOO.
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, Sarah Monfeldt can be reached at 571-270-1833. 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.
/C.F.M./Examiner, Art Unit 3629 /SARAH M MONFELDT/Supervisory Patent Examiner, Art Unit 3629
Prosecution Insights