Prosecution Insights
Last updated: October 02, 2026
Application No. 18/897,619

METHOD, DEVICE, AND COMPUTER PROGRAM PRODUCT FOR BACKUP

Non-Final OA §103
Filed
Sep 26, 2024
Priority
Mar 21, 2024 — CN 202410333677.0
Examiner
GUSTAFSON, MATHEW DONALD
Art Unit
2113
Tech Center
2100 — Computer Architecture & Software
Assignee
Dell Products L.P.
OA Round
3 (Non-Final)
83%
Grant Probability
Favorable
3-4
OA Rounds
5m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 83% — above average
83%
Career Allowance Rate
5 granted / 6 resolved
+28.3% vs TC avg
Strong +42% interview lift
Without
With
+41.7%
Interview Lift
resolved cases with interview
Typical timeline
2y 5m
Avg Prosecution
20 currently pending
Career history
38
Total Applications
across all art units

Statute-Specific Performance

§101
9.7%
-30.3% vs TC avg
§103
65.2%
+25.2% vs TC avg
§102
23.2%
-16.8% vs TC avg
§112
1.9%
-38.1% vs TC avg
Black line = Tech Center average estimate • Based on career data from 6 resolved cases

Office Action

§103
Detailed Action This action is in response to the application filed on 06/15/2026. Claims 1-2, 4-11, and 13-20 are pending and have been fully examined. 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 the Claims Claims 1-2, 7-11, and 16-19 are rejected under 35 U.S.C. 103 Claims 4-6, 13-15, and 20 contain allowable subject matter but are objected to as being dependent upon rejected independent claims 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, 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-2, 7-8, 10-11, 16-17, and 19 are rejected under 35 U.S.C. 103 as being unpatentable over Du et al. (U.S. Publication No. 2020/0133804 A1), hereinafter referred to as Du, in view of Tang et al. (U.S. Publication No. 2021/0117280 A1), hereinafter referred to as Tang. Regarding Claim 1, Du teaches: A method for backup, comprising: determining a plurality of parameters of a plurality of replication sessions in a waiting queue in response to a backup execution command being triggered, ([0043]; regarding, “a replication session (i.e., the synchronization session)”; [0060]; regarding, “The method 300 shown in FIG. 3 may be executed periodically or upon the arrival of a new synchronization job.”; [0048]; regarding, “the scheduler 130 obtains, at block 310, respective synchronization characteristics of a group of synchronization jobs to be processed.”); the determining of the plurality of parameters comprising: …and a predicted execution time of the replication session, ([0051]; regarding, “the scheduler 130 determines, based on the expected completion time instant of the synchronization job, the length of available time for executing the synchronization job until the expected completion time instant”); determining a plurality of weights of the plurality of replication sessions based on the plurality of parameters of the plurality of replication sessions, ([0050]; regarding, “The scheduler 130 prioritizes, at block 320, the group of synchronization jobs based on the obtained respective synchronization characteristics”); selecting at least one replication session from the plurality of replication sessions to enter the running queue based on the plurality of weights of the plurality of replication sessions; ([0059]; regarding, “the scheduler 130 may select, from the group of synchronization jobs, a synchronization job with the highest priority as a synchronization job to be executed based on the result of prioritization;”); and performing a backup task with respect to the at least one replication session in the running queue. ([0059]; regarding, “…and execute the selected synchronization job.”). Du fails to explicitly disclose but Tang teaches: the determining of the plurality of parameters comprising: determining a waiting time of each replication session in the waiting queue, ([0034]; regarding, “the scheduling device 110 may further determine a waiting time period of the existing backup job in the waiting queue.”); a total waiting time of the replication session corresponding to a difference between an execution start time of arrival of the replication session at a running queue, and an arrival time of the replication session at the waiting queue; ([0033]; regarding, “the predetermined execution information of the existing backup job may be a predetermined priority and/or a predetermined execution interval”; [0047]; regarding, “the scheduling device 110 may determine a value related to the predetermined execution information of the existing backup job in advance, and then only calculate the term related to the waiting time period of the existing backup job… This is because the predetermined execution information for each backup job is predetermined and unchanged, whereas the waiting time period in the waiting queue changes as time elapses”); the determining of the plurality of weights comprising: determining a weight of each replication session based at least on the waiting time of the replication session, and the predicted execution time of the replication session; ([0036]). Therefore, it would have been obvious before the effective filing date of the claimed invention to one of ordinary skill in the art to which said subject matter pertains to combine Du with the teachings of Tang. Doing so ensures that… system resources are better utilized to achieve the Recover Point Objective (RPO) for important data, thereby ensuring a Service Level Agreement (SLA). (Tang, [0019]). Regarding Claim 2, Du in view of Tang teaches the method of claim 1 as referenced above. Du in view of Tang further teaches: wherein determining a plurality of parameters of a plurality of replication sessions in a waiting queue comprises: determining a sum of the waiting time and the predicted execution time; (Tang, [0033]; regarding, “the predetermined execution information of the existing backup job may be a predetermined priority and/or a predetermined execution interval”; [0047]; regarding, “the scheduling device 110 may determine a value related to the predetermined execution information of the existing backup job in advance, and then only calculate the term related to the waiting time period of the existing backup job… This is because the predetermined execution information for each backup job is predetermined and unchanged, whereas the waiting time period in the waiting queue changes as time elapses”); determining a data recovery point objective level of said each replication session; (Tang, [0043]; regarding, “a backup job with a higher execution priority may be executed earlier, enabling as much data as possible to reach the Recover Point Objective (RPO)”); and determining a user-defined level of said each replication session; (Tang, [0027]; regarding, “the predetermined execution information may be a predetermined priority of the target backup job specified by the user.”). Regarding Claim 7, Du in view of Tang teaches the method of claim 1 as referenced above. Du in view of Tang further teaches: wherein selecting at least one replication session from the plurality of replication sessions to enter the running queue comprises: detecting whether the running queue is full; (Du, [0038]; regarding, “the execution of synchronization jobs is limited by the maximum number of active synchronization jobs… Any of the incoming synchronization jobs will be pushed into an active job list or a waiting job list, depending on whether the number of the current active jobs reaches the maximum number of the active jobs.”) waiting for a vacancy in the running queue in response to the running queue being full; (Du, [0040]; regarding, “If the predetermined maximum number is not reached, the initiated synchronization job is executed at block 230; otherwise, the initiated synchronization job waits to be processed at block 240.”) and selecting at least one replication session from the plurality of replication sessions to enter the running queue in response to the running queue not being full. (Du, [0059]; regarding, “when the number of current active synchronization jobs is below a threshold (e.g., the maximum number of the active synchronization jobs allowed), the scheduler 130 may select… a synchronization job with the highest priority as a synchronization job to be executed based on the result of prioritization…”). Regarding Claim 8, Du in view of Tang teaches the method of claim 1 as referenced above. Du in view of Tang further teaches: wherein selecting at least one replication session from the plurality of replication sessions to enter the running queue in response to the running queue not being full comprises: determining the number of vacancies in the running queue in response to the running queue not being full; (Du, [0040]; regarding, “the scheduler determines, at block 220, whether the number of the active synchronization jobs reaches a predetermined maximum number.”); ranking the replication sessions in the waiting queue in ascending order of weights; (Du, [0073]; regarding, “the scheduler 130 may respectively normalize the remaining time and the incremental data size, and determine the priority of each of the waiting synchronization jobs by using the normalized remaining time and the normalized incremental data size as weight values.”); and selecting replication sessions ranked lower of which the quantity is the number of vacancies to enter the running queue. (Du, [0059]; regarding, “when the number of current active synchronization jobs is below a threshold (e.g., the maximum number of the active synchronization jobs allowed), the scheduler 130 may select, from the group of synchronization jobs, a synchronization job with the highest priority as a synchronization job to be executed based on the result of prioritization”). Claims 10-11, 16-17 are rejected under 35 U.S.C. 103 under the same grounds of rejection as claims 1-2, 7-8 respectively. Claim 19 is rejected under 35 U.S.C. 103 under the same grounds of rejection as claim 1. Claims 9 and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Du et al. (U.S. Publication No. 2020/0133804 A1), hereinafter referred to as Du, in view of Tang et al. (U.S. Publication No. 2021/0117280 A1), hereinafter referred to as Tang, in further view of Knechtel et al. (U.S. Publication No. 2019/0034285 A1), hereinafter referred to as Knechtel. Regarding Claim 9, Du in view of Tang further teaches the method of claim 1 as referenced above. Du in view of Tang further fails to explicitly disclose but Knechtel teaches: detecting whether the waiting queue is an empty queue; and determining that the backup task is complete in response to the waiting queue being an empty queue. ([0034]; regarding, “Once all queued backup candidates have been stored, the backup thread 215 may enter into a sleep interval during which the backup thread 215 is refrained from backing up data. Method 200 may go back to 202 and wait until it receives another backup trigger at 204 to repeat the process.”). Therefore, it would have been obvious before the effective filing date of the claimed invention to one of ordinary skill in the art to which said subject matter pertains to combine Du and Tang with the teachings of Knechtel. Doing so can minimize or reduce performance impact to the application (Knechtel, [0016]). Claim 18 is rejected under 35 U.S.C. 103 under the same grounds of rejection as claim 9. Allowable Subject Matter Claims 4-6, 13-15, and 20 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 claims and any intervening claims. The following is a statement of reasons for the indication of allowable subject matter: Regarding Claims 4-6 and similarly claims 13-15, and 20, Du discloses (Fig. 6, [0055-0057]; regarding “wherein R.sub.min represents the shortest time of RPO of all synchronization jobs, i.e., R.sub.min=min (R.sub.i,r), where R.sub.i,r represents the RPO set for the replication session R.sub.i. R.sub.max represents the longest time of RPO of all synchronization jobs, i.e., R.sub.max=max (R.sub.i,r). Dmin represents the smallest incremental data size, i.e., D.sub.min=min (R.sub.i,d), where R.sub.i,d represents the incremental data size between synchronizations of the replication session R.sub.i. D.sub.max represents the largest incremental data size of all synchronization jobs, i.e., D.sub.max=max (R.sub.i,d).”). Further, Tang discloses ([0035-0038]; regarding, “when Pc is an integer, the resulting interval of values of Pc×10 is 10, and the resulting maximum value of a*log R+b log B−c log W is less than 10. Therefore, a higher predetermined priority results in a higher execution priority. Only when a plurality of backup jobs have the same predetermined priority, the scheduling device 110 determines the execution priorities of the plurality of backup jobs according to the predetermined execution interval, the predicated execution duration and the waiting time period.”). The previously cited prior art fails to teach alone or in combination the claimed subject matter of claims 4-6, 13-15, and 20. Response to Arguments Applicant’s arguments filed 06/15/2026 have been fully considered. Applicant’s arguments 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 Any inquiry concerning this communication or earlier communications from the examiner should be directed to MATHEW GUSTAFSON whose telephone number is (571)272-5273. The examiner can normally be reached Monday-Friday 8:00-4:00. 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, Bryce Bonzo can be reached at (571) 272-3655. 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. /M.D.G./Examiner, Art Unit 2113 /BRYCE P BONZO/Supervisory Patent Examiner, Art Unit 2113
Read full office action

Prosecution Timeline

Show 2 earlier events
Jan 12, 2026
Interview Requested
Jan 22, 2026
Applicant Interview (Telephonic)
Jan 22, 2026
Examiner Interview Summary
Jan 23, 2026
Response Filed
Apr 17, 2026
Final Rejection mailed — §103
Jun 15, 2026
Request for Continued Examination
Jun 22, 2026
Response after Non-Final Action
Sep 23, 2026
Non-Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12724661
CIRCUIT FOR STATUS MONITORING, AND FAULT RECOVERY AND ISOLATION FOR INTER-INTEGRATED CIRCUIT (I2C) BUS, AND METHOD IMPLEMENTED BY THE SAME
2y 2m to grant Granted Sep 01, 2026
Patent 12664065
COLLECTING, STORING, AND REPORTING ACCIDENT DATA IN AN INFORMATION HANDLING SYSTEM (IHS)
2y 6m to grant Granted Jun 23, 2026
Patent 12572400
DATABASE SWITCHOVER IN A DISTRIBUTED DATABASE SYSTEM
2y 3m to grant Granted Mar 10, 2026
Patent 12461830
RESOURCE-AWARE WORKLOAD REALLOCATION ACROSS CLOUD ENVIRONMENTS
1y 6m to grant Granted Nov 04, 2025
Patent 12332719
POWER SUPPLY REDUNDANCY CONTROL SYSTEM AND METHOD FOR GPU SERVER AND MEDIUM
1y 10m to grant Granted Jun 17, 2025
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

3-4
Expected OA Rounds
83%
Grant Probability
99%
With Interview (+41.7%)
2y 5m (~5m remaining)
Median Time to Grant
High
PTA Risk
Based on 6 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