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 .
Priority
1. Acknowledgment is made of applicant’s claim foreign priority based on application filed in the Republic of India on 06/26/2024.
Information Disclosure Statement
2. The information disclosure statement (IDS) submitted on 12/27/2025 was filed. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Rejections - 35 USC § 103
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.
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-20 are rejected under 35 U.S.C. 103 as being unpatentable over Olsen et al (2009/0254240) , Hawley et al (U.S 2020/0391884) and further in view of Schmidt et al (U.S. 2021/0390803).
3. As per claims 1,9 and 20 Olsen disclosed a computer-implemented method, comprising:
initializing, in at least one data store, a respective count of occurrences of a respective event associated with at least one event condition for a plurality of components installed on a vehicle [the Data Collection Module 255 instructs the ECMs 110 to record data measurements from certain sensors, at certain periods of time, when certain criteria have been satisfied, or any combination thereof. In addition, the Data Collection Module 255 receives sensor signal data from the ECMs 110 over a period of time (e.g., a moderate duration, such as 3 months, 6 months, 1 year, or a shorter or longer duration), shown as Step 610. The period of time of collection, according to various embodiments, depends on the length deemed necessary or desirable by the fleet operator to collect a representative amount of data about the fleet vehicles.] (Paragraph. 0038), wherein the respective count of occurrences of the respective event is maintained at the data store for a lifecycle of respective components [In addition, in one embodiment, a threshold value is related to the occurrence of an event such that the event occurring is indicative of a potential fault. For example, in regard to a dead or dying battery, a threshold value is an ECM 110 fault with a signal sensor.] (Paragraph. 0052);
storing, in the at least one data store, a respective definition for the at least one event condition [the statistical algorithm stored procedures are applied by the Fault Prediction Module 260 in a substantially real-time manner. Alternatively, the statistical algorithm stored procedures are applied by the Fault Prediction Module 260 to the data collected by the Data Collection Module 255 at a subsequent time after the data is collected by the Data Collection Module 255 and transmitted to the Fault Prediction Module 260. For example, the statistical algorithm stored procedures are applied by the Fault Prediction Module 260 at periodic intervals, at predetermined periods of time, upon the collection of a predetermined amount of data, or based upon various other conditions. Once the statistical algorithm stored procedures are applied to the data, the Fault Prediction Module 260 determines if any of the data has surpassed an earmark, whether the earmark is a threshold value or an acceptable operating range] (Paragraph. 0072);
obtaining, from at least one sensor or system aboard the vehicle, vehicle data associated with operation of the vehicle [data collected by the ECM 110 and transmitted to the Data Collection Module 255 includes, for example, data from sensors in communication with various components of an engine or vehicle] (Paragraph. 0039);
determining that at least a subset of the vehicle data meets the at least one event condition for at least one of the plurality of components [The method continues by determining a first statistical distribution of the sensor signal data from substantially all of the plurality of vehicles, determining a second statistical distribution for each of the plurality of vehicles of the sensor signal data from the first type of sensor from each of the plurality of vehicles, and statistically comparing each second statistical distribution for each of the plurality of vehicles to the first statistical distribution related to substantially all of the plurality of vehicles to determine a degree of difference between the statistical distributions. In response to the degree of difference being outside of a predetermined range based on the first statistical distribution for substantially all of the plurality of vehicles, the method generates an alert code for the particular vehicle. In response to generating the alert code] (Paragraph. 0011);
in response to the determination, updating, at least one data store, the respective count of occurrences of the respective event for the at least one data store, the respective count of occurrences of the respective event for the at least one of the plurality of components [algorithms are developed for identifying the number of cycle counts of the starter exceeding a threshold value of starts, a battery voltage at startup that is lower than a threshold value of battery voltage at startup, and/or a battery voltage that is lower than a threshold value of battery voltage in combination with the number of cycle counts of the starter exceeding a threshold value of starts, Additionally, algorithms are developed for identifying various earmarks that are predictive of a dead or dying alternator.] (Paragraph. 0061);
However, Olsen did not explicitly disclose, generating a ranking of the plurality of components; generating a ranking of the plurality of components based at least in part on the respective count of occurrences for the respective components;
In the same field of endeavor Hawley disclosed, “In some embodiments, the maintenance record 107 for a given APU may be utilized to subdivide the operating record 105 for that APU into different lifecycles. For example, in exemplary embodiments, an APU lifecycle is realized as the period of time between maintenance visits (or the period of time between initial deployment and an initial maintenance visit), with the maintenance data being utilized to subdivide the performance measurement data and contextual data captured throughout the lifetime of that APU into discrete lifecycles (Paragraph. 0031).
It would have been obvious to one having ordinary skill in the art before the effective filing was made to have incorporated in some embodiments, the maintenance record 107 for a given APU may be utilized to subdivide the operating record 105 for that APU into different lifecycles. For example, in exemplary embodiments, an APU lifecycle is realized as the period of time between maintenance visits (or the period of time between initial deployment and an initial maintenance visit), with the maintenance data being utilized to subdivide the performance measurement data and contextual data captured throughout the lifetime of that APU into discrete lifecycles as taught by Hawley in the method and system of Olsen to optimize the maintenance of the vehicles by reducing cost.
However, Olsen and Hawley did not explicitly disclose causing rendering of the ranking of the plurality of components on a computing device external to the vehicle to enable maintenance monitoring of the plurality of components.
In the same field of endeavor Schmidt disclosed, “With reference now to FIG. 2, flow diagram 200 illustrates a process for performing predictive maintenance and diagnostics for an electronic module 204 of an autonomous vehicle 206. In an example, an autonomous vehicle 206 may require periodic inspections to confirm that the autonomous vehicle 206 and electronic modules thereof are in a desirable condition for continued operation. A data logger 202 can be used to monitor damage accumulation to the electronic module 204 based upon conditions such as temperature cycles or duty cycles, wherein data is stored by the data logger 202 and accessed during the periodic inspections. The data logger 202 may be a battery powered device that is retrofitted to, or disposed in proximity of, the electronic module 204. The data logger 202 can be removed from the autonomous vehicle 206 or accessed in-place to retrieve damage accumulation information stored thereon” (Schmidt, Paragraph. 0032).
It would have been obvious to one having ordinary skill in the art before the effective filing date was made to have incorporated With reference now to FIG. 2, flow diagram 200 illustrates a process for performing predictive maintenance and diagnostics for an electronic module 204 of an autonomous vehicle 206. In an example, an autonomous vehicle 206 may require periodic inspections to confirm that the autonomous vehicle 206 and electronic modules thereof are in a desirable condition for continued operation. A data logger 202 can be used to monitor damage accumulation to the electronic module 204 based upon conditions such as temperature cycles or duty cycles, wherein data is stored by the data logger 202 and accessed during the periodic inspections. The data logger 202 may be a battery powered device that is retrofitted to, or disposed in proximity of, the electronic module 204. The data logger 202 can be removed from the autonomous vehicle 206 or accessed in-place to retrieve damage accumulation information stored thereon as taught by Schmidt in the method and system of Olsen-Hawley to optimize the maintenance of the vehicles by reducing cost.
4. As per claim 2 Olsen-Hawley-Schmidt disclosed further comprising:
resetting the respective count of occurrences of the respective event in the at least one data store in response to replacement of a respective component of the plurality of components (Olsen, Paragraph. 0060).
5. As per claim 3 Olsen-Hawley-Schmidt disclosed further comprising:
obtaining a value of at least one historical count of occurrences of the respective event for a replacement component (Olsen, Paragraph. 0060); and updating the respective count of occurrences of the respective event based at least in part on the value of the at least one historical count of occurrences (Olsen, Paragraph. 0035).
6. As per claim 4 Olsen-Hawley-Schmidt disclosed wherein:
the at least one data store comprises a first data store aboard the vehicle and a second data store remote to the vehicle; the first data store comprises the respective definition for the at least one event condition; and the second data store comprises the respective count of occurrences of the respective count of occurrences of the respective event for a respective component of the plurality of components (Olsen, Paragraph. 0026).
7. As per claim 5 Olsen-Hawley-Schmidt disclosed further comprising:
provisioning to the vehicle the respective definition for the at least one event condition; and receiving from the vehicle at least the subset of the vehicle data determined to meet the at least one event condition for the respective component (Olsen, Paragraph. 0023).
8. As per claim 6 Olsen-Hawley-Schmidt disclosed further comprising:
determining the updated respective count of occurrences for the respective event for a respective component of the plurality of components meets a replacement threshold; and in response to the determination, provisioning to the computing device an instruction to replace the respective component (Olsen, Paragraph. 0060-0061).
9. As per claim 7 Olsen-Hawley-Schmidt disclosed further comprising:
receiving from the computing device a request comprising at least one of an increment or a decrement to the updated respective count of occurrences; and modifying the updated respective count of occurrences based at least in part on the request (Hawley, Paragraph. 0044). Claim 7 has the same motivation as claim 1.
10. As per claim 8 Olsen-Hawley-Schmidt disclosed further comprising:
receiving from the computing device a request comprising at least one modification to the respective definition for the at least one event condition; and updating the respective definition based at least in part on the at least one modification (Hawley, Paragraph. 0030). Claim 8 has the same motivation as to claim 1.
11. As per claim 10 Olsen-Hawley-Schmidt disclosed wherein: the at least one data store comprises a first data store aboard the vehicle and a second data store remote to the vehicle (Olsen, Paragraph. 0035); the first data store comprises the respective definition for the at least one event condition; and the second data store comprises the count of occurrences of the respective event for a respective component of the plurality of components (Olsen, Paragraph. 0061); and the computer-coded instructions, in execution with the at least one processor, further cause the apparatus to: initialize the respective definition at the first data store to cause a vehicle management system aboard the vehicle to provision the vehicle data to the apparatus in response to the vehicle data meeting a least a portion of the respective definition for the at least one event condition (Olsen, Paragraph. 0011-0012).
12. As per claim 11 Olsen-Hawley-Schmidt disclosed wherein: the respective definition indicates at least one threshold for at least one component parameter (Olsen, Paragraph. 0060-0061).
13. As per claim 12 Olsen-Hawley-Schmidt disclosed wherein: the at least one component parameter comprises a fault state for a respective component of the plurality of components (Olsen, Paragraph. 0023).
14. As per claim 13 Olsen-Hawley-Schmidt disclosed wherein: the fault state comprises at least one of depowered, underpowered, or clogged (Olsen, Paragraph. 0031).
15. As per claim 14 Olsen-Hawley-Schmidt disclosed wherein: the at least one component parameter comprises at least one of hydraulic pressure, oil pressure, moisture level, or temperature (Olsen, Paragraph. 0024).
16. As per claim 15 Olsen-Hawley-Schmidt disclosed wherein: the at least one component parameter comprises at least one of applied load, torque, shock intensity, vibration intensity, vibration frequency, or vibration duration (Olsen, Paragraph. 0024).
17. As per claim 16 Olsen-Hawley-Schmidt disclosed wherein: the respective definition indicates at least one threshold for at least one of vehicle attitude, vehicle speed, or braking (Olsen, Paragraph. 0024).
18. As per claim 17 Olsen-Hawley-Schmidt disclosed wherein: the computer-coded instructions, in execution with the at least one processor, further cause the apparatus to: provision to the vehicle the updated count of occurrences (Olsen, Paragraph. 0026).
19. As per claim 18 Olsen-Hawley-Schmidt disclosed wherein: the computer-coded instructions, in execution with the at least one processor, further cause the apparatus to: receive from the computing device at least one of a vehicle identifier or a system identifier (Olsen, Paragraph. 0042); determine a plurality of components associated with the vehicle identifier or the system identifier; retrieve, from the at least one data store, a current count of occurrences for at least one event condition associated with a respective component (Olsen, Paragraph. 0058); and provision to the computing device a report comprising the respective current counts of occurrences of the at least one event condition for the plurality of components (Schmidt, Paragraph. 0008-0009). Claim 18 has the same motivation as to claim 1.
20. As per claim 19 Olsen-Hawley-Schmidt disclosed wherein: a top-ranked entry of the ranking comprises a component associated with a greatest quantity of occurrences of the at least one event condition; and the computer-coded instructions, in execution with the at least one processor further cause apparatus to: provision to the computing device a respective component identifier for a top-ranked subset of the ranking (Schmidt, Paragraph. 0025). Claim 19 has the same motivation as to claim 1.
Response to Arguments
21. Applicant’s arguments with respect to claim(s) 1-20 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.
Conclusion
22. THIS ACTION IS MADE FINAL. 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.
23. Any inquiry concerning this communication or earlier communication from the
examiner should be directed to Adnan Mirza whose telephone number is (571)-272-3885.
24. The examiner can normally be reached on Monday to Friday during normal
business hours. If attempts to reach the examiner by telephone are unsuccessful, the
examiner’s supervisor, Faris Almatrahi can be reached on (313)-446-4821.
25. Information regarding the status of an application may be obtained from the
Patent Application Information Retrieval (PAIR) system. Status information for published
applications may be obtained from either Private PAIR or Public PAIR. Status
information for un published applications is available through Private PAIR only. For
more information about the PAIR system, see http://pair-direct.uspto.gov. Should you
have questions on access to the Private PAIR system, contact the Electronic Business
Center (EBC) at (866)-217-9197 (toll-free).
/ADNAN M MIRZA/Primary Examiner, Art Unit 3667
Prosecution Insights