Prosecution Insights
Last updated: July 17, 2026
Application No. 19/185,236

AI AGENT FOR PRE-BUILD CONFIGURATION OF CLOUD SERVICES

Non-Final OA §DP
Filed
Apr 21, 2025
Priority
Oct 13, 2023 — continuation of 12/298,880
Examiner
MEKY, MOUSTAFA M
Art Unit
Tech Center
Assignee
Microsoft Technology Licensing, LLC
OA Round
1 (Non-Final)
93%
Grant Probability
Favorable
1-2
OA Rounds
1y 0m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 93% — above average
93%
Career Allowance Rate
682 granted / 730 resolved
+33.4% vs TC avg
Moderate +5% lift
Without
With
+5.2%
Interview Lift
resolved cases with interview
Typical timeline
2y 3m
Avg Prosecution
10 currently pending
Career history
733
Total Applications
across all art units

Statute-Specific Performance

§101
3.2%
-36.8% vs TC avg
§103
18.2%
-21.8% vs TC avg
§102
37.4%
-2.6% vs TC avg
§112
3.8%
-36.2% vs TC avg
Black line = Tech Center average estimate • Based on career data from 730 resolved cases

Office Action

§DP
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 . Detailed Action Claims 2-21 are presenting for examination. non-statutory double patenting rejection The non-statutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A non-statutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on non-statutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a non-statutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. Claims 2, 5, 7-9, 12, 14-16, 19, and 21 are rejected on the ground of non-statutory double patenting as being unpatentable over claims 1-4, 8-9, 12-13, 15, and 17 of U.S. Patent No. 12,298,880. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-4, 8-9, 12-13, 15, and 17 of the patent 880 anticipates claims 2, 5, 7-9, 12, 14-16, 19, and 21 of the application as been shown in the table below. 19.185,236 12,298,880 2. (New) A system comprising: a processor; and a computer-readable medium storing instructions that are operative upon execution by the processor to: receive prior-existing utilization data, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources; create, using the utilization data, a capacity prediction model for generating a pre-build configuration that minimizes expected throttling and slack for a first computational resource; generate, using the capacity prediction model, the pre-build configuration for the first computational resource; and build the first computational resource in accordance with the pre-build configuration. 1. A system comprising: a processor; and a computer-readable medium storing instructions that are operative upon execution by the processor to: receive prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; create, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generate, using the capacity prediction model, the pre-build configuration for the first computational resource; and tune the pre-build configuration using a selected cost and performance balance point and prior-existing project history data. 2. The system of claim 1, wherein the instructions are further operative to: build the first computational resource in accordance with the pre-build configuration, the pre-build configuration comprising a processor count, amount of memory, and/or storage capacity for the first computational resource. 5. (New) The system of claim 2, wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; and wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources. 4. The system of claim 1, wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources; and wherein the project history data comprises requested changes or reported incidents for the prior-existing computational resources. 7. (New) The system of claim 2, wherein the instructions are further operative to: tune the pre-build configuration using a selected cost and performance balance point, wherein the cost and performance balance point are selected by a user based on a preferences of the user. 1. A system comprising: a processor; and a computer-readable medium storing instructions that are operative upon execution by the processor to: receive prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; create, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generate, using the capacity prediction model, the pre-build configuration for the first computational resource; and tune the pre-build configuration using a selected cost and performance balance point and prior-existing project history data. 8. (New) The system of claim 2, wherein the first computational resource is configured to generate output data from input data while minimizing expected throttling and slack. 3. The system of claim 2, wherein the instructions are further operative to: receive input data by the first computational resource; and generate output data using the first computational resource, based on at least the input data. 9. (New) A computer-implemented method comprising: receiving prior-existing utilization data, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources; creating, using the utilization data, a capacity prediction model for generating a pre- build configuration that minimizes expected throttling and slack for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource; and building the first computational resource in accordance with the pre-build configuration. 8. A computer-implemented method comprising: receiving prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; creating, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource, the pre-build configuration comprises processor count, amount of memory, and/or storage capacity for the first computational resource; and tuning the pre-build configuration using a selected cost and performance balance point and prior-existing project history data. 9. The computer-implemented method of claim 8, further comprising: building the first computational resource in accordance with the pre-build configuration; receiving input data by the first computational resource; and generating output data using the first computational resource, based on at least the input data. 12. (New) The computer-implemented method of claim 9, wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; and wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources. 10. The computer-implemented method of claim 8, wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources; and wherein the project history data comprises requested changes or reported incidents for the prior-existing computational resources. 14. (New) The computer-implemented method of claim 9, further comprising: presenting a user interface (UI);receiving, through the UI, an initial build target selection, wherein generating the pre- build configuration for the first computational resource comprises generating the pre-build configuration for the first computational resource based on at least the initial build target selection; receiving, through the UI, a selected cost and performance balance point; displaying, in the UI, at least a portion of a hierarchy of the capacity prediction model; displaying, in the UI, information for a prior-existing computational resource used in generating the capacity prediction model; and displaying, in the UI, at least a portion of the pre-build configuration. 12. The computer-implemented method of claim 8, further comprising: presenting a user interface (UI); receiving, through the UI, an initial build target selection, wherein generating the pre-build configuration for the first computational resource comprises generating the pre-build configuration for the first computational resource based on at least the initial build target selection; receiving, through the UI, the selected cost and performance balance point; and displaying, in the UI, at least a portion of the pre-build configuration. 13. The computer-implemented method of claim 12, further comprising: displaying, in the UI, at least a portion of a hierarchy of the capacity prediction model; and displaying, in the UI, information for a prior-existing computational resource used in generating the capacity prediction model. 15. (New) The computer-implemented method of claim 9, further comprising: tuning the pre-build configuration using a selected cost and performance balance point, wherein the cost and performance balance point are selected by a user based on a preferences of the user. 8. A computer-implemented method comprising: receiving prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; creating, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource, the pre-build configuration comprises processor count, amount of memory, and/or storage capacity for the first computational resource; and tuning the pre-build configuration using a selected cost and performance balance point and prior-existing project history data. 16. (New) A computer storage device having computer-executable instructions stored thereon, which, on execution by a computer, cause the computer to perform operations comprising: receiving prior-existing utilization data, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources; creating, using the utilization data, a capacity prediction model for generating a pre- build configuration that minimizes expected throttling and slack for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource; and building the first computational resource in accordance with the pre-build configuration. 15. A computer storage device having computer-executable instructions stored thereon, which, on execution by a computer, cause the computer to perform operations comprising: receiving prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; creating, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource; tuning the pre-build configuration using a selected cost and performance balance point and prior-existing project history data; and building the first computational resource in accordance with the pre-build configuration, the pre-build configuration comprising a processor count, amount of memory, and/or storage capacity for the first computational resource. 19. (New) The computer storage device of claim 16, wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; and wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources. 17. The computer storage device of claim 15, wherein the operations further comprise: wherein the capacity information comprises processor count, amount of memory, and/or storage capacity for the prior-existing computational resources; wherein the resource consumption information comprises slack information and throttling information for the prior-existing computational resources; and wherein the project history data comprises requested changes or reported incidents for the prior-existing computational resources. 21. (New) The computer storage device of claim 20, wherein the operations further comprise: tuning the pre-build configuration using a selected cost and performance balance point, wherein the cost and performance balance point are selected by a user based on a preferences of the user. 15. A computer storage device having computer-executable instructions stored thereon, which, on execution by a computer, cause the computer to perform operations comprising: receiving prior-existing utilization data and project metadata, wherein the utilization data comprises capacity information and resource consumption information for prior-existing computational resources, and wherein the project metadata includes information for hierarchically categorizing the prior-existing computational resources; creating, using the utilization data and project metadata, a capacity prediction model for generating a pre-build configuration for a first computational resource; generating, using the capacity prediction model, the pre-build configuration for the first computational resource; tuning the pre-build configuration using a selected cost and performance balance point and prior-existing project history data; and building the first computational resource in accordance with the pre-build configuration, the pre-build configuration comprising a processor count, amount of memory, and/or storage capacity for the first computational resource. Claims 3-4, 6, 10-1, 13, 17-18, 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 claim and any intervening claims. The prior art of record doesn’t teach the limitations of claims 3-4, 6, 10-1, 13, 17-18, and 20. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Moustafa M Meky whose telephone number is (571)272-4005. The examiner can normally be reached Monday-Friday 9AM-5PM. 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, Ario Etienne can be reached at 571-272-4001. 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. MOUSTAFA M. MEKY Primary Patent Examiner Art Unit 2457 /MOUSTAFA M MEKY/Primary Examiner, Art Unit 2457 06/27/2026
Read full office action

Prosecution Timeline

Apr 21, 2025
Application Filed
Jul 01, 2026
Non-Final Rejection mailed — §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12676904
CONFERENCE OPERATOR
3y 4m to grant Granted Jul 07, 2026
Patent 12665873
NAT ROUTE DISTRIBUTION BASED ON TAG INFORMATION IN AN SDWAN OVERLAY NETWORK
1y 8m to grant Granted Jun 23, 2026
Patent 12659239
CONFIGURATION OF COMPUTING DEVICES BASED ON GEOGRAPHIC PATTERN DETECTION
2y 0m to grant Granted Jun 16, 2026
Patent 12652329
DEVICE AND METHOD FOR MERGING DATA FRAMES FOR VEHICLE NETWORK SYSTEM, AND STORAGE MEDIUM STORING INSTRUCTIONS TO PERFORM METHOD FOR MERGING DATA FRAMES
1y 10m to grant Granted Jun 09, 2026
Patent 12652249
Egress and private router detection in Internet Protocol Version 6 (IPV6)
1y 9m to grant Granted Jun 09, 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

1-2
Expected OA Rounds
93%
Grant Probability
99%
With Interview (+5.2%)
2y 3m (~1y 0m remaining)
Median Time to Grant
Low
PTA Risk
Based on 730 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