Prosecution Insights
Last updated: May 29, 2026
Application No. 18/319,565

METHOD AND SYSTEM FOR DISASTER RECOVERY POLICY MANAGEMENT

Final Rejection §101
Filed
May 18, 2023
Examiner
AHMED, ENAM
Art Unit
2112
Tech Center
2100 — Computer Architecture & Software
Assignee
DELL PRODUCTS, L.P.
OA Round
4 (Final)
82%
Grant Probability
Favorable
5-6
OA Rounds
2m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 82% — above average
82%
Career Allowance Rate
600 granted / 731 resolved
+27.1% vs TC avg
Strong +20% interview lift
Without
With
+19.8%
Interview Lift
resolved cases with interview
Typical timeline
3y 2m
Avg Prosecution
6 currently pending
Career history
738
Total Applications
across all art units

Statute-Specific Performance

§101
8.6%
-31.4% vs TC avg
§103
62.6%
+22.6% vs TC avg
§102
20.9%
-19.1% vs TC avg
§112
1.8%
-38.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 731 resolved cases

Office Action

§101
DETAILED ACTION This office action is in response to the RCE filed 4/14/26. The Examiner is respectfully maintaining the 35 U.S.C 101 Rejections on Final Rejection, mailed 1/14/26, with details noted below. 35 U.S.C 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claim 1 is rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. The Abstract idea is, determining, by a data center module, a priority level, performance metrics, data center infrastructure, a snapshot, prediction of disaster recovery resources based on priority level and the performance metrics, wherein the disaster recovery resource comprise a computing resource and networking resource, sending by the data center module the priority level, the performance metrics, the data center infrastructure information, and the snapshot to the cloud module, assigning, by the cloud module, disaster recovery resources to obtain assigned disaster recover resources based on the priority level, the performance metrics, the data center infrastructure information and the prediction. Further, wherein the cloud module is configured to activate the assigned disaster recovery resources by determining that the data center has experienced a failure by determining that expected heartbeat signal was not received, identifying and establishing a connection with a replication site: deploying the snapshot by downloading and sending to the replication site, determining, by the data center module, an updated priority level for at least one application associated with the data center, and sending an activation signal to the disaster recovery resources whereby the disaster recovery resources will enable the switch from a standby mode to active mode; initiating, by the disaster recovery resources, a plurality of applications using the snapshot and in response to switching to the active mode, wherein initiating comprises executing the plurality of applications with the disaster recovery resources; determining, by the data center module, updated performance metrics, generating a second prediction of the disaster recovery resources based on the updated priority level and the updated performance metrics; and updating, by the cloud module, the assigned disaster recovery resources based on the second prediction. Thus, the Examiner points out that these steps merely gather information by a data center, on data center module, a priority level, performance metrics, data center infrastructure, a snapshot, prediction of disaster recovery resources based on priority level and the performance metrics. For, example determining that the data center has experienced a failure by determining that expected heartbeat signal was not received and sending an activation signal to the disaster recovery resources whereby the disaster recovery resources will enable the switch from a standby mode to active mode and initiates application using the snapshot. However, there is no concrete result or any real world result in the sense that the data center may fail if no heartbeat signal is received but there is no further action taken to rectify the issue, and merely receiving or not receiving a heartbeat signal is not necessarily more or give the claim patentable weight. The same can be said for sending an activation signal to the disaster recovery resources whereby the disaster recovery resources will enable the switch from a standby mode to active mode, however enabling switch to the active mode is still lacking the real world result, in the sense that enabling to an active mode is lacking details. Further, initiating, by the disaster recovery resources, a plurality of applications using the snapshot and in response to switching to the active mode, wherein initiating comprises executing the plurality of applications with the disaster recovery resources, is lacking detail in the sense that there is no practical real world result. For example, merely executing the plurality of applications or taking snapshot of plurality of applications or based on modes, such as active mode or standby mode, does not necessarily make the claims significant more, unless it can be shown what are the specific functions of the resources and how a technology can be improved. Further, sending by the data center module the priority level, the performance metrics, the data center infrastructure information, and the snapshot to the cloud module, assigning, by the cloud module, disaster recovery resources to obtain assigned disaster recover resources based on the priority level, the performance metrics, the data center infrastructure information and the prediction does not significantly amount to something more either for example, merely sending information such as performance metrics, priority level or data center infrastructure to the cloud module, wherein the cloud module may assign disaster recovery resources does not make the claim significantly more in the sense that a prediction may be given of the disaster recovery resources, however it is not concrete and there is no real world result. Also merely having computing resource and a networking resource does not necessarily make the claims significant more, unless it can be shown what are the specific functions of the resources and how a technology can be improved. Further, wherein the cloud module is configured to activate the assigned disaster recovery resources by identifying and establishing a connection with a replication site: deploying the snapshot to the replication site, determining, by the data center module, an updated priority level for at least one application associated with the data center, and sending an activation signal to the disaster recovery resources, initiating, by the disaster recovery resources, a plurality of applications using the snapshot and in response to switching to the active mode, wherein initiating comprises executing the plurality of applications with the disaster recovery resources; determining, by the data center module, updated performance metrics, generating a second prediction of the disaster recovery resources based on the updated priority level and the updated performance metrics; and updating, by the cloud module, the assigned disaster recovery resources based on the second prediction are also mere predictions to activate disaster recovery based on snapshot, updated priority level, updated performance metrics, however there is nothing concrete here nor is there any tangible real world result. Accordingly, the claim recites an abstract idea. This judicial exception is not integrated into a practical application. In particular, the claim only recites data center module, disaster recovery resource, computing resource, networking resource, replication site and cloud module. However, based on the specification, there is no specific structure for these units or modules, nor are they clearly defined. The data center module, disaster recovery resource, computing resource, networking resource, replication site and cloud module are merely used as generic tools to perform the abstract idea, and are cited at a high-level of generality. Accordingly, these additional elements do not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. The claim is directed to an abstract idea. The claim does not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements data center module, disaster recovery resource, computing resource, networking resource, replication site and cloud module amounts to no more than using generic components or units within a data center to apply the exception using the generic components or units. Merely using generic components or units within a data center to apply an exception cannot provide an inventive concept. The claim is not patent eligible. Independent claim 9 and 15 are also rejected under 35 U.S.C. 101 for being directed to non-statutory subject matter. The same or similar reasoning is given as applied above for claim 1. The Dependent claims 2-3, 5-9, 11-14 and 17-20 are rejected under 35 U.S.C. 101 for being directed to non-statutory subject matter as they fail to remedy the independent claims. Or Please cancel the previous Abstract and replace it with the following rewritten abstract. If the abstract is being substantially rewritten, submit a new abstract in clean text (no markings) accompanied by an instruction for the cancellation of the previous abstract. Amendments to the Drawings: The attached sheets of drawings include changes to Figures . These sheets, which include Figures , replace the original sheets including Figures . Attachment: Replacement Sheets Any replacement drawing sheet including amended figures must include all of the figures appearing on the immediate prior version of the sheet (i.e., if the previous drawing sheet included Figures 1 and 2, but you've only amended figure 1, the Replacement Sheet of drawings should still include Figures 1 and 2). "Replacement Sheet" must be identified in the top, center margins, as such. If submitted, annotated sheets must be identified in the top center margin as "Annotated Sheet Showing Changes." Or Please cancel the previous Abstract and replace it with the following rewritten abstract. If the abstract is being substantially rewritten, submit a new abstract in clean text (no markings) accompanied by an instruction for the cancellation of the previous abstract. Amendments to the Drawings: The attached sheets of drawings include changes to Figures . These sheets, which include Figures , replace the original sheets including Figures . Attachment: Replacement Sheets Any replacement drawing sheet including amended figures must include all of the figures appearing on the immediate prior version of the sheet (i.e., if the previous drawing sheet included Figures 1 and 2, but you've only amended figure 1, the Replacement Sheet of drawings should still include Figures 1 and 2). "Replacement Sheet" must be identified in the top, center margins, as such. If submitted, annotated sheets must be identified in the top center margin as "Annotated Sheet Showing Changes." Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to Enam Ahmed whose telephone number is 571-270-1729. The examiner can normally be reached on Mon-Fri from 8:30 A.M. to 5:30 P.M. If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Albert Decady, can be reached on 571-272-3819. 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 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 unpublished 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). /ENAM AHMED/ Patent Examiner, Art Unit 2112 5/13/26 /ESAW T ABRAHAM/Primary Examiner, Art Unit 2112
Read full office action

Prosecution Timeline

Show 4 earlier events
Aug 27, 2025
Non-Final Rejection mailed — §101
Sep 24, 2025
Interview Requested
Nov 25, 2025
Response Filed
Jan 14, 2026
Final Rejection mailed — §101
Mar 20, 2026
Interview Requested
Apr 14, 2026
Request for Continued Examination
Apr 23, 2026
Response after Non-Final Action
May 15, 2026
Non-Final Rejection mailed — §101 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12639166
VALLEY CHECK MEMORY SYSTEM COMMAND
1y 10m to grant Granted May 26, 2026
Patent 12632172
SELF-CORRECTED LOW-DENSITY PARITY CHECK (LDPC) WITH INDEX MATCH
2y 0m to grant Granted May 19, 2026
Patent 12632334
DATA TRANSMISSION SYSTEM, VERIFICATION METHOD AND SLAVE DEVICE
1y 10m to grant Granted May 19, 2026
Patent 12626776
SEMICONDUCTOR MEMORY DEVICE
2y 0m to grant Granted May 12, 2026
Patent 12608273
RAS TRIGGERS L2P TABLE MOVEMENT IN CXL DEVICES WITH COMPRESSION
1y 9m to grant Granted Apr 21, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

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

Prosecution Projections

5-6
Expected OA Rounds
82%
Grant Probability
99%
With Interview (+19.8%)
3y 2m (~2m remaining)
Median Time to Grant
High
PTA Risk
Based on 731 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

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

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

Free tier: 3 strategy analyses per month