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 .
Remarks
This Office Action is in response to amendment and remarks filed on 07/07/2026.
Claims 1, 10 and 19 are currently amended via Applicant’s amendment.
Claims 1-27 are pending.
Claims 1, 10 and 19 are independent claims.
This Office Action is made final.
Examiner Notes
Examiner cites particular columns and line numbers in the references as applied to the claims below for the convenience of the applicant. Although the specified citations are representative of the teachings in the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested that, in preparing responses, the applicant fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the examiner.
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 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.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The claims in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The broadest reasonable interpretation of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification when 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph:
(A) the claim limitation uses the term “means” or “step” or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means” or “step” or the generic placeholder is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means” or “step” or the generic placeholder is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step”) in a claim with functional language creates a rebuttable presumption that the claim limitation is to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites sufficient structure, material, or acts to entirely perform the recited function.
Absence of the word “means” (or “step”) in a claim creates a rebuttable presumption that the claim limitation is not to be treated in accordance with 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. The presumption that the claim limitation is not interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, is rebutted when the claim limitation recites function without reciting sufficient structure, material or acts to entirely perform the recited function.
Claim limitations in this application that use the word “means” (or “step”) are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action. Conversely, claim limitations in this application that do not use the word “means” (or “step”) are not being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “a frequency governor configured to…”, “a thermal-balancing scheduler configured to…” in claim 1-9.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 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 of this title, 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.
Claims 1-3, 10-12 and 19-21 are rejected under AIA 35 U.S.C. 103 as being unpatentable over Majumdar et al. (US 2017/0371719 A1) (hereinafter Majumdar) in view of Saravana Krishnan Kannan (US 2017/0075733 A1) (hereinafter Kannan).
As per claim 1, A computing device (e.g. Majumdar: [Fig. 1] [0016] discloses computing system. [Abstract] [0013] system, apparatus and method for performing temperature-aware task scheduling and proactive power management. [0056] discloses non-transitory storage medium comprising instructions that implements the method. Also see [Figs. 5-8] methods for performing temperature-aware task scheduling and power proactive management.) comprising: a plurality of processor clusters, each processor cluster comprising a temperature sensor (e.g. Majumdar: [Fig. 1] [0016-0022] discloses computing system comprising SOC that includes a plurality of processor cores 110A-N and number of sensors 170A-N that are spread throughout the SOC. In one embodiment, each sensor tracks the temperature of corresponding component. In another embodiment, there is a sensor for the different regions of SoC, where sensors are spread throughout SOC and located so as to track the temperature in different areas of SOC to monitor hot spots in SOC. [Fig. 2] [0029-0030] discloses sensors are spread throughout APU rather than in one region. For example, each compute unit of GPU and core of CPU includes a sensor to monitor the temperature of each compute unit. Majumdar discloses APU including dual-core CPU 228 and dual-core CPU 230, wherein each CPU includes a plurality of processor cores. Also see [0047]. Thus, Majumdar’s dual-core CPUs, each comprising multiple processor cores and associated temperature sensors, reasonably corresponds to the claimed plurality of processor cluster, each cluster comprising a temperature sensor.); a frequency governor configured to scale a frequency of each of the plurality of processor clusters (e.g. Majumdar: [0021] discloses power management unit uses dynamic voltage and frequency scaling (DVFS) to change the frequency and/or voltage of a processing unit. [0025-0026] SoC includes a phase-locked loop (PLL) unit configured to individually control and alter the frequency of each of the clock signals provides to respective ones of processor cores independently. [0043] if measured processing unit temperature is greater than or equal to the thermal limit, then the power management unit reduces the voltage and frequency supplied to the given processing unit.); and a thermal-balancing scheduler (e.g. Majumdar: [0013] discloses SoC includes a scheduler and a power management unit to schedule tasks. Scheduler schedules tasks to the processing units in a manner that minimizes non-uniform heat generation on the SoC. The scheduler prevents thermal limits from being exceeded by the SoC. Also see [0019] [Fig. 2] [0029] [Fig. 3][0031-0032] [0035-0037] [0039-0040] [0043] [0050-0051].) configured to: receive, from each temperature sensor, a temperature indication that indicates a temperature of a corresponding processor cluster to obtain an indication of thermal conditions of the plurality of processor clusters (e.g. Majumdar: [0022] [0030] discloses sensors tracks the temperature of corresponding component to monitor whether there are any hot spots in SoC. [0032] the task scheduler and proactive power manger utilize the measured temperature as inputs for determining thermal margin and temperature gradient, to schedule tasks. [Figs. 2, 3 and related description] the task scheduler receives temperature margins, temperature gradients and thermal metrics. Also see [0034-0036] [0047]. Thus, Majumdar expressly discloses receiving temperature indications from sensors corresponding to the respective processing units to determine thermal conditions.); schedule tasks to the plurality of processor clusters based upon the thermal conditions of the plurality of processor clusters (e.g. Majumdar: [0013] discloses system/apparatus/method for performing temperature aware task scheduling to plurality of processing units. The scheduler schedules pending tasks to the processing units to prevent thermal limits from being exceeded. [0015] [0019] discloses minimizing non-uniform heat generation on the SoC by scheduling tasks to the plurality of processing units based on the thermal gradients and the thermal margin. [0032] [0035] task scheduler and power manger utilize temperature margin and temperature gradient as input to determine how to schedule tasks. The task scheduler assigns task to a plurality of compute units of a SoC based on thermal margins and thermal gradient. [0037] the task scheduler schedules tasks such that the temperature increase of the compute units executing their assigned tasks stay below the temperature margin. Also see [0038-0040] [0043] [0048] [0051] [0053]. Thus, Majumdar teaches scheduling tasks to the plurality of multi-core processor units/processor clusters based upon thermal conditions); and request the frequency governor to scale a frequency of one or more of the plurality processor clusters based upon the scheduled tasks (e.g. Majumdar: [0021] discloses power management unit uses dynamic voltage and frequency scaling (DVFS) to change the frequency and/or voltage of a processing unit. [0025-0026] SoC includes a phase-locked loop (PLL) unit configured to individually control and alter the frequency of each of the clock signals provides to respective ones of processor cores independently. [0043] if measured processing unit temperature is greater than or equal to the thermal limit, then the power management unit reduces the voltage and frequency supplied to the given processing unit. Also see [0031, 0038-0040] [0053] that disclose scheduling scheme includes scheduling pending tasks to processing units and assigning/adjusting power states for the plurality of processing units.).
As discussed above, Majumdar discloses requesting/scaling a frequency of one or more of the plurality of processor cluster but does not expressly disclose that “request to scale a frequency is based upon a task load of the scheduled tasks.”
However, Kannan expressly discloses request the frequency governor to scale a frequency of one or more of the plurality processor clusters based upon a task load of the scheduled tasks (e.g. Kannan: [Fig. 1] [0020] disclose application processor including a plurality of processor cores 116, scheduler 110, and frequency governor 112. [0025] discloses frequency governor adjusting operating frequency of each core based upon workload performed by that processor core and receiving additional information from scheduler about workload groups scheduled for execution on a processor and how much load each workload group contributes. [0027] discloses scheduler scheduling tasks among processor cores and workload monitoring module providing frequency governor information identifying what amount of the reported load originates from respective workload groups. [0028-0030] disclose scheduler receiving requests to process tasks, classifying the tasks into workload groups, monitoring a load placed on the processor due to each workload group, determining each workload group’s contribution to the total workload of tasks on the processor, and frequency governor controlling frequency of the processor based upon the total workload and each workload group’s contribution to the total workload of the tasks on the processor. [0034-0041] further disclose applying load-to-frequency function to workload information to determine processor frequency and sending a notification to frequency governor to recompute CPU frequency when a workload group’s contribution to total workload exceeds a threshold. [0020] the frequency governor monitors a load on the application processor, and determines an operating frequency to operate the processor cores. [0025] the frequency governor operates to adjust the operating frequency of each cores based upon the workload that each processor core is performing Thus, Kannan expressly discloses a scheduler providing scheduled-task workload/load-contribution information to a frequency governor requesting scaling of frequency, which scales frequency of one or more processor based upon a task load of scheduled tasks. Applying Kannan’s task-load-based frequency governor technique to Majumdar’s multi-core CPUs, which reasonably correspond to the claimed processor clusters, results in requesting a frequency governor to scale a frequency of one or more of the plurality of processor clusters based upon a task load of the scheduled tasks.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify Majumdar’s thermally aware task scheduling and proactive power-management system with Kannan’s workload-differentiated processor-frequency-scaling technique because both references concern managing operating frequency in multicore computing systems to balance processing performance against power consumption and thermal effects. Majumdar expressly coordinates scheduling of pending tasks with assignment of compute-unit power states to prevent thermal violations and reduce non-uniform heat generation. Kannan teaches that a scheduler may monitor the load attributes of scheduled tasks, provide workload information to a frequency governor, and cause the governor to select frequency based upon total task workload and task-group workload contributions. Incorporating Kannan’s known workload-responsive frequency control into Majumdar’s known thermal-aware task scheduler and power manager would have predictably improved processor power/performance/thermal management by selecting the operating frequency for the processor cluster based upon the processing workload of the tasks scheduled to it, while continuing to use Majumdar’s thermal metrics, thermal gradients, and thermal margins in selectin task placement and power state. The combination would merely have involved applying Kannan’s known task-load-based frequency-governor technique to Majumdar’s known thermally aware multicore task scheduling system to obtain predictable results.
Furthermore, it would have been obvious to a POSITA before the effective filing date of the claimed invention to modify Majumdar with Kannan because Kannan’s techniques significantly reduce processor frequency ramp-up time and provides noticeable performance improvement without significant power increase (see Kannan [0042-0044]).
As per claim 2, the combination of Majumdar and Kannan discloses The computing device of claim 1 [See rejection to claim 1 above], wherein the thermal-balancing scheduler is configured to schedule tasks to the plurality of processor clusters to keep a thermal balance between the plurality of processor clusters (e.g. Majumdar: [Abstract] discloses minimizing non-uniform heat generation on the SoC by scheduling tasks to processing units based on the thermal conditions of processing units. [0013] discloses a scheduler schedules tasks to the processing units in a manner that minimizes non-uniform heat generation, and prevents thermal limits from being exceeded. [0019] discloses scheduler is configured to schedule tasks to cores and compute units so as to minimize, or otherwise reduce, non-uniform heat generation on SoC based on thermal conditions. [0048] discloses scheduling/assigning tasks to processing units to minimize non-uniform heat generation while preventing the thermal limits of the processing units from being exceeded. Also see [0015]).
As per claim 3, the combination of Majumdar and Kannan discloses The computing device of claim 1 [See rejection to claim 1 above], wherein the thermal-balancing scheduler is configured to characterize each of the plurality of processor clusters as one of a plurality of thermal states and the thermal-balancing scheduler is configured to schedule tasks based upon the thermal states of the plurality of processor clusters (e.g. Majumdar: [Abstract] [0014-0015] discloses monitoring a thermal margin available on each processing unit and determining thermal gradients of each processing unit; and discloses scheduling tasks based on the thermal metric, thermal gradients and thermal margin of the processing units. The SoC allows a given pending task to be scheduled on a given processing unit if the thermal gradient of the processing unit is less than or equal to the thermal margin of the given processor. [0019] discloses scheduler schedules tasks to cores and compute units based on the thermal metrics, the thermal gradients of each processing unit, and the thermal margin available on each processing unit. [0022] furthermore, Majumdar also discloses tracking temperature in different areas of SoC to monitor whether there are any hot spots in SoC. Thus, by determining thermal margin and thermal gradient of the processor or identifying any hot spots, Majumdar implicitly characterizes a thermal state for each processing unit. Since, margin is calculated as thermal limit minus current temperature of the components—this directly implies a state relative to thresholds.).
As per claims 10-12, these are method claims having similar limitations cited in device/system claims 1-3, respectively. Thus, claims 10-12 are also rejected under the same rationale as cited in the rejection of rejected claims 1-3, respectively.
As per claims 19-21, these are non-transitory processor readable storage medium claims having similar limitations as cited in device/system claims 1-3, respectively. Thus, claims 19-21 are also rejected under the same rationale as cited in the rejection of rejected claims 1-3, respectively.
Allowable Subject Matter
Claims 4-9, 13-18 and 22-27 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims, after addressing any claim objections/rejections detailed above.
Response to Arguments
Applicant’s arguments with respect to 35 U.S.C. § 112 (a) and (b) have been fully considered and are persuasive. Accordingly, the rejections of claims 1-9 under 35 U.S.C. § 112 (a) and (b) are withdrawn. However, 112 (f) interpretation is maintained. Although the claims do not expressly recite the work “means,” the limitations “a frequency governor configured to…” and “a thermal-balancing scheduler configured to…” employ generic functional terms that serve as placeholders for the structure that perform the recited functions. The generic terms are modified by functional language, including the phrase “configured to,” and the claim language that itself does not recite sufficient structure for performing the claimed functionality. Therefore, the limitations are properly interpreted under 35 U.S.C. § 112 (f). See MPEP 2181.
Applicant’s arguments with respect to 35 U.S.C. § 103 have been fully considered but they are moot in view of new grounds of rejections necessitated by the amendment.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
On (US 2016/0342191 A1) is relevant because it teaches a multicore CPU frequency-scaling system that calculates an average load across and determines a new operating frequency based on that load and current power consumption. Its frequency determination unit applies the selected frequency to each core (see [0014-0017, 0023-0030 and 0058-0062]).
Park (US 2014/0173311 A1) discloses a multi-core processor having a low-power cluster and a high-performance cluster. Park further teaches assigning a task to a core through task scheduling, measuring CPU load at the task-assigned core, and adjusting core operating frequency upward or downward as CPU load increases or decreases (See [0061-0064 and 0085-0087]).
Chen (US 2025/0231779 A1) expressly defines “task load” as a computing amount or consumed time and teaches adjusting CPU frequency based on that task load. It describes increasing CPU frequency when a render tree task load exceeds a threshold, with higher task-load ranges resulting in higher CPU frequency settings. (see [0032-0033] and [0229-023])
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Hiren Patel whose telephone number is (571) 270-3366. The examiner can normally be reached on Monday-Friday 9:30 AM to 6: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) Form at https://www.uspto.gov/patents/uspto-automated- interview-request-air-form.
If attempts to reach the above noted Examiner by telephone are unsuccessful, the Examiner’s supervisor, April Y. Blair, can be reached at the following telephone number: (571) 270-1014. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from Patent Center and the Private Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from Patent Center or Private PAIR. Status information for unpublished applications is available through Patent Center or Private PAIR to authorized users only. Should you have questions on access to Patent Center or the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
September 9, 2026
/HIREN P PATEL/Primary Examiner, Art Unit 2196