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 .
Status of Claims
This Office action is in reply to filing by applicant on 07/22/2026.
Claims 1 and 11 were amended by Applicant.
Claims 2 – 10 and 12 – 20 were previously presented by Applicant.
Claims 1 – 20 are currently pending and have been examined.
The prior 35 USC 103 claim rejections set forth in the Non-Final rejection of 04/22/2026 as to claims 1 – 9 and 11 - 20 are maintained in view of Applicant's arguments and amendments.
THIS ACTION IS MADE FINAL.
Response to Arguments
There are no new grounds of rejection herein as to any of the claims.
Applicant argues per 35 USC 103 the amended portion of the claims of 07/22/2026. These amended portions of the claims however have not yet been addressed by examiner. That said, these several specific portions of the amended claims here argued by Applicant are specifically addressed in full in the following 35 USC 103 analysis.
Generally as to obviousness, examiner submits that it is determined on the basis of the evidence as a whole and the relative persuasiveness of the arguments. See In re Oetiker, 977 F.2d 1443, 1445, 24 USPQ2d 1443, 1444 (Fed. Cir. 1992); In re Hedges, 783 F.2d 1038, 1039, 228 USPQ 685,686 (Fed. Cir. 1992); In re Piasecki, 745 F.2d 1468, 1472, 223 USPQ 785,788 (Fed. Cir. 1984); and In re Rinehart, 531 F.2d 1048, 1052, 189 USPQ 143,147 (CCPA 1976). Using this standard, examiner submits that the burden of presenting a prima facie case of obviousness was successfully established in the prior Office Action of 04/22/2026, and also respecting the pending amended claim set of 07/22/2026, as seen below.
Examiner recognizes that references cannot be arbitrarily altered or modified, and that there must be some reason why a person having ordinary skill in the relevant art would be motivated to make the proposed modifications. Although the motivation or suggestion to make modifications must be articulated, it is respectfully submitted that there is no requirement that the motivation to make modifications must be expressly articulated within the references themselves. References are evaluated by what they suggest to one versed in the art, rather than by their specific disclosures, In re Bozek, 163 USPQ 545 (CCPA 1969).
Examiner also notes that the motivation to combine the applied references is, where appropriate in the below detailed analysis pursuant to 35 USC 103, additionally accompanied by select passages from the respective references which specifically support that particular motivation. It is also respectfully submitted that motivation based on the logic and scientific reasoning of one ordinarily skilled in the art at the time of the invention, which evidence can also support a finding of obviousness, is otherwise provided in the detailed 35 USC 103 analysis of the claim set below. In re Nilssen, 851 F.2d 1401, 1403, 7 USPQ2d 1500, 1502 (Fed. Cir. 1988) (references do not have to explicitly suggest combining teachings); Ex parte Clapp, 227 USPQ 972 (Bd. Pat. App. & Inter. 1985) (examiner must present convincing line of reasoning supporting rejection); and Ex parte Levengood, 28 USPQ2d 1300 (Bd. Pat. App. & Inter. 1993) (reliance on logic and sound scientific reasoning).
Examiner recognizes that obviousness can only be established by combining or modifying the teachings of the prior art to produce the claimed invention where there is some teaching, suggestion, or motivation to do so found either in the references themselves or in the knowledge generally available to a person of ordinary skill in the art. See In re Fine, 837 F.2d 1071, 5 USPQ2d 1596 (Fed. Cir. 1988) and In re Jones, 958 F.2d 347.
Claim Rejections – 35 USC 103
In the event the determination of the status of the application as subject to AIA 35 USC 102 and 103 is incorrect, any correction of the statutory basis 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 USC 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.
The factual inquiries set forth in Graham v. John Deere Co., 383 U.S. 1, 148 USPQ 459 (1966), that are applied for establishing a background for determining obviousness under 35 USC 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating
obviousness or nonobviousness.
Claims 1 – 5, 9, 11 – 15, 19, and 20 are rejected pursuant to 35 USC 103 as being unpatentable over Manoukian (US20190177000A1) in view of Horabin (US20170061295A1).
Regarding claims 1 and 11:
A method, comprising:
accessing sensor information from a plurality of sensors that monitor an aircraft propulsion system heat exchanger; (“In one aspect, there is provided a method for detecting a failure of a heat exchanger provided on an engine of an aircraft, the method comprising detecting an out-of-range fuel temperature downstream of an outlet of the heat exchanger, monitoring a health of a fuel tank temperature signal indicative of a temperature of at least one fuel tank of the aircraft, receiving a main oil temperature signal indicative of a temperature of oil in the engine, and detecting the failure based on the main oil temperature and on the health of the fuel tank temperature signal.”, [005]) and (“The heat exchanger failure detection unit 108 also receives input data from one or more aircraft sensors 110, which are configured to acquire measurements of one or more engine parameters including, but not limited to, a main oil temperature (MOT) indicative of the engine oil temperature and the fuel tank temperature (FTT) indicative of fuel temperature in the aircraft tank(s).”, [022]);
inputting sensed information corresponding to the sensor information into a control circuit configured to output virtual parameters corresponding to the aircraft propulsion system heat exchanger as a first function, at least in part, of the sensed information; determining a particular fault class from amongst a plurality of fault classes as a second function, at least in part, of the virtual parameters; Examiner notes that the broad “virtual” modifier to an aircraft “parameter,” may, when read in light of the Specification [42., 0054], [21.,0033], and [24., 0036], include a temperature sensor reading (virtual parameter) of a temperature sensor mounted so as to read a temperature of an aircraft heat exchanger; that said, this limitation, broadly interpreted and consistent with the light of the specification, is read on by any temperature sensor reading from any aircraft heat exchanger, which temperature sensor reading indicates an overheat temperature (classed as a “fault”) condition … (“When the MOT is above the second threshold for excessive heating (labeled MOT2 in FIG. 6) and the FTT is above the first threshold for excessive heating (labeled FTT1 in FIG. 6), the excessive heating condition (labeled “Fuel hot fault” in FIG. 6) is detected.”, [036]) and (“A system and a method for detecting a failure of a heat exchanger provided on an engine of an aircraft. An out-of-range fuel temperature downstream of an outlet of the heat exchanger is detected.”, [Abstract]);
Manoukian does not expressly disclose, but Horabin teaches.
responsive to determining the particular fault class, identifying at least one task regarding the aircraft propulsion system heat exchanger corresponding to the particular fault class; and Examiner interprets this limitation broadly to include that a “task” identified relative to the said heat exchanger is, for example, a way to cool it down, if necessary, (see below), and that a “fault” in that connection is simply detecting the overheating condition of said exchanger in the first place, …(“Furthermore, as degradation continues, the ram air inlet flap position may be moved towards a forty percent open position during cruise to try and increase cooling flow through the heat exchanger. … To ensure correct diagnosis of such heat exchanger issues, other features may be monitored to ensure that they are within the normal range and not the cause of the observed behavior.”, [033]), the “task” of increasing cooling flow to the heat exchanger due to a cooling fault is identified;
carrying out the at least one maintenance task regarding the aircraft propulsion system heat exchanger to remediate a fault with the aircraft propulsion system heat exchanger; (“More specifically, it has been determined that as the heat exchanger loses effectiveness, the compressor outlet temperature of the air-conditioning pack 22 may rise towards a limit of 180° C.”, [032]) and (“FIG. 2 illustrates an exemplary schematic view of a cold air unit also known as an air-conditioning pack 22 having a main heat exchanger 70, … and a controller 78, which may be located within the cockpit 16 of the aircraft 8 and may be operably coupled to the controller 34.”, [016]) and (“Furthermore, as degradation continues, the ram air inlet flap position may be moved towards a forty percent open position during cruise to try and increase cooling flow through the heat exchanger. … To ensure correct diagnosis of such heat exchanger issues, other features may be monitored to ensure that they are within the normal range and not the cause of the observed behavior.”, [033]), as above, air flow to the heat exchanger is tasked to be diverted as needed in response to a detection a fault (heat related) therein, thereby remediating the detected fault (excessive temperature situation),
wherein carrying out the at least one maintenance task includes repairing or replacing a component of the aircraft propulsion system heat exchanger. (“Furthermore, as degradation continues, the ram air inlet flap position may be moved towards a forty percent open position during cruise to try and increase cooling flow through the heat exchanger. … To ensure correct diagnosis of such heat exchanger issues, other features may be monitored to ensure that they are within the normal range and not the cause of the observed behavior.”, [033]), the item is repaired by moving it.
It would have been obvious to one of ordinary skill in the art before the effective filing date of this application to have modified Manoukian to incorporate the teachings of Horabin because Manoukian would be more efficient and versatile it could detect an impending failure of the heat exchanger as done in Horabin (“In this manner, the transmitted data may undergo statistical analysis in relation to themselves and to other parameters/features and this information may be used to determine impending faults and/or degradation and provide associated information such as severity and prognostic information by highlighting an impending failure of a particular component.”, see [036] of Horabin.
Regarding claims 2 and 12:
The combination of Manoukian and Horabin disclose the limitations of claims 1 and 11, respectively:
Manoukian further discloses:
wherein the plurality of sensors is insufficient to uniquely identify every failure mode of the aircraft propulsion system heat exchanger. (“FIG. 6 illustrates a plot of MOT versus FTT with various heat exchanger failure regions, when both the fuel tank temperature and the main oil temperature signals are healthy (i.e. valid). It can be seen that when the MOT is below the first threshold for insufficient heating (labeled MOT1 in FIG. 6), no heat exchanger failure detection occurs (labeled “No fault” in FIG. 6).”, [036]), the insufficient heating failure mode is not detected.
Regarding claims 3 and 13:
The combination of Manoukian and Horabin disclose the limitations of claims 1 and 11, respectively:
Manoukian further discloses:
wherein the sensor information represents at least one heat exchanger fluid flow, at least one heat exchanger temperature, and at least one heat exchanger pressure. (“As used herein, the term “conditioned fluid” is intended to include at least one of heated, cooled, and pressurized fluids. As will be understood by one skilled in the art, the engine's thermal management system communicates one or more conditioned fluids to various engine systems in order to minimize heat generation an dissipate the heat generated by the engine during its operation.”, [017]).
Regarding claims 4 and 14:
The combination of Manoukian and Horabin disclose the limitations of claims 1 and 11, respectively:
Manoukian further discloses:
wherein the sensor information comprises directly measurable physical parameters. Examiner notes that the temperature of a heat exchanger, or even the temperature downstream from a heat exchanger, may at least be gauged by one’s hand, as either hot or cold, and, therefore, directly measurable, just as the following temperature related to the heat exchange (HE) is directly measurable by a sensor … (“In particular, it is proposed to supplement the information provided by a sensing device 104 (e.g. fuel temperature switch or sensor) that monitors the fuel temperature downstream of the outlet of the FOHE 102 with additional inputs.”, [018]).
Regarding claims 5 and 15:
The combination of Manoukian and Horabin disclose the limitations of claims 1 and 11, respectively:
Manoukian further discloses:
wherein the virtual parameters comprise parameters that are not directly measurable. (“It should however be understood that, in an alternate embodiment, the OAT may be directly provided as an additional input parameter that is used in the computation of heat exchanger failure regions.”, [034]), certain heat exchanger failure regions cannot be directly measured/ sensed and are therefore calculated.
Regarding claim 20 (note that claim 20 reads on claims 9 and 19):
The combination of Manoukian and Horabin disclose the limitations of claim 19:
Horabin further discloses:
wherein at least some of the plurality of fault classes that each correspond to a plurality of the individual fault modes also each have at least one shared task associated therewith. The fault mode of high temp vis a vis heat exchanger as above is remediated by the shared task of cooling and of directing more air towards heat exchanger … (“Furthermore, as degradation continues, the ram air inlet flap position may be moved towards a forty percent open position during cruise to try and increase cooling flow through the heat exchanger. … To ensure correct diagnosis of such heat exchanger issues, other features may be monitored to ensure that they are within the normal range and not the cause of the observed behavior.”, [033]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of this application to have modified Manoukian to incorporate the teachings of Horabin because Manoukian would be more efficient and versatile it could detect an impending failure of the heat exchanger as done in Horabin (“In this manner, the transmitted data may undergo statistical analysis in relation to themselves and to other parameters/features and this information may be used to determine impending faults and/or degradation and provide associated information such as severity and prognostic information by highlighting an impending failure of a particular component.”, see [036] of Horabin.
Claims 6 and 16 are rejected pursuant to 35 USC 103 as being unpatentable over Manoukian (US20190177000A1) in view of Horabin (US20170061295A1), and in further view of Thumati (US9724979B1).
Regarding claims 6 and 16:
The combination of Manoukian and Horabin disclose the limitations of claims 5 and 15, respectively:
That combination does not expressly disclose, but Thumati teaches
wherein the virtual parameters include at least some parameters that are dimensionless. Examiner notes that a ratio is dimensionless parameter and that it’s measured as follows, … (“By adjusting a ratio of the diverted cold air to the remaining hot engine bleed air, the temperature of the air being provided to the cabin can be controlled and adjusted.”, [col. 3: 27 – 30]) and (“A computer-implemented method, environmental control system, and aircraft are provided. Environmental operating conditions data for a heat exchanger is received.”, [Abstract]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of this application to have modified Manoukian to incorporate the teachings of Thumati because Manoukian would be more efficient and versatile if expressly utilized dimensionless ratios in its analyses, as done in Thumati (“The air mix valve 112 adjusts the ratio of hot air (via duct 114) and cold air (via duct 154) to control the temperature of the air being provided to the aircraft cabin 118.”, [col. 3: 64 – 67]).
Claims 7, 8, 17, and 18 are rejected pursuant to 35 USC 103 as being unpatentable over Manoukian (US20190177000A1) in view of Horabin (US20170061295A1), and in further view of Hare (US20160306725A1)
Regarding claims 7 and 17:
The combination of Manoukian and Horabin disclose the limitations of claims 1 and 11, respectively:
That combination does not expressly disclose, but Hare teaches:
wherein the control circuit is configured, at least in part, as a neural network. (“training a plurality of neural networks for each subsystem and component within the complex networked system to detect and identify faults within the sensor data; and in response to the sub-set of best sensors being selected and the plurality of neural networks being trained for each subsystem and component, executing the algorithm to detect and isolate the faults within the sensor data.”, [004]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of this application to have modified Manoukian to incorporate the teachings of Hare because Manoukian would be more efficient and at least have enhanced processing driven detection skills if it opted for neural network assistance in its attention to a heat exchanger, as done in Hare (“This neural network model then acts as a binary classifier to detect if a fault is present within the subsystem/component.”, [016]).
Regarding claims 8 and 18:
The combination of Manoukian, Horabin and Hare disclose the limitations of claims 7 and 17, respectively:
Hare further teaches:
wherein the neural network is trained, at least in part, using data from other aircraft propulsion system heat exchangers that are not identical to the aircraft propulsion system heat exchanger. (“In one example of implementing the system level detection and isolation algorithm on the generated data sets after training the Neural Networks, 100 Monte Carlo runs were conducted using the 15 data sets of healthy and faulty data presented in Table 1 during each run. These data sets include the healthy system, two shutdown air cycle machines, four second heat exchangers fouling conditions, and four biased sensors for both flow and condenser inlet temperature. Additionally, additive white Gaussian noise is independently injected into each data set from run to run to mimic real life situations. Each data set is then passed through the diagnostic tree shown in FIG. 3 for the system level detection and isolation algorithm and through each component neural network 372-379 for the exhaustive search.”, [039]).
It would have been obvious to one of ordinary skill in the art before the effective filing date of this application to have modified Manoukian to incorporate the teachings of Hare because Manoukian would be more efficient and at least have enhanced processing driven detection skills if it opted for neural network assistance in its attention to a heat exchanger, as done in Hare (“This neural network model then acts as a binary classifier to detect if a fault is present within the subsystem/component.”, [016]).
Allowable Subject Matter
Claim 10 would be allowable if rewritten or amended to overcome additional objections/rejections herein, if any, and/or if rewritten in independent claim form. The following is a statement of reasons for the indication of allowable subject matter: Independently, while the claims' limitations most recently set forth herein may individually be disclosed by the prior art, the claims as a whole are not obvious because the examiner would have to improperly use their separate limitations as a road map to combine them.
CONCLUSION
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.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MATTHEW COBB whose telephone number is (571) 272-3850. The examiner can normally be reached 9 - 5, M - F.
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 call examiner Cobb as above, or 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, Peter Nolan, can be reached at (571) 270-7016. 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.
/MATTHEW COBB/Examiner, Art Unit 3661
/PETER D NOLAN/Supervisory Patent Examiner, Art Unit 3661