Prosecution Insights
Last updated: October 04, 2026
Application No. 18/784,222

MACHINE LEARNING FOR PACKAGE VERSIONING AND USE

Non-Final OA §102
Filed
Jul 25, 2024
Examiner
KENDALL, CHUCK O
Art Unit
2192
Tech Center
2100 — Computer Architecture & Software
Assignee
Capital One Services LLC
OA Round
1 (Non-Final)
87%
Grant Probability
Favorable
1-2
OA Rounds
9m
Est. Remaining
95%
With Interview

Examiner Intelligence

Grants 87% — above average
87%
Career Allowance Rate
810 granted / 933 resolved
+31.8% vs TC avg
Moderate +8% lift
Without
With
+8.0%
Interview Lift
resolved cases with interview
Typical timeline
2y 11m
Avg Prosecution
27 currently pending
Career history
955
Total Applications
across all art units

Statute-Specific Performance

§101
12.9%
-27.1% vs TC avg
§103
22.2%
-17.8% vs TC avg
§102
50.6%
+10.6% vs TC avg
§112
1.4%
-38.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 933 resolved cases

Office Action

§102
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 . This is in response to Application filed 04/25/24. Claims 1 – 20 have been examined and are pending. Claim Rejections - 35 USC § 102 The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. Claim(s) 1 – 20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Lee et al. US 20250272216 A1. Regarding claim 1, Lee anticipates A system for using a machine learning model on code packages, the system comprising: one or more memories (FIG. 5, 530); and one or more processors, communicatively coupled to the one or more memories (FIG.5, 520, 540), configured to: receive a first version of a first code package (FIG.1, see First version of program 111 and change request as well as Second Version of program 112 – 114); compile, and perform a first set of tests on, the first version of the first code package [0047 – 0048, see compiling and First version of the program]; provide a first set of results from the first set of tests to the machine learning model in order to generate a first score for the first version of the first code package receive a second version of the first code package [0008 – 0012, shows machine learning language model and determining results as well as ranking and scores and comparing to previous version i.e. second version]; compile, and perform the first set of tests on, the second version of the first code package [0046 – 0048, see compiling and first version]; provide a second set of results from the first set of tests to the machine learning model in order to generate a second score for the second version of the first code package, wherein the second score is worse than the first score [0013, see second ranking and machine learning based probability scores]; receive, from a first user device, a request for the first code package; transmit, to the first user device and in response to the request for the first code package, an indication to use the first version of the first code package based on the second score being worse than the first score [00023 – 0026, see test cases and based on result as well as receiving change request and update a version]; receive a first version of a second code package; compile, and perform a second set of tests on, the first version of the second code package in order to determine that the first version of the second code package is defective [0027, see receiving error report]; and transmit, to a second user device, a message indicating that the first version of the second code package is defective [0026 – 0027, see test case failing to pass and receiving error report and updated version of the program]. Regarding claim 2, the system of claim 1, wherein the one or more processors are configured to: receive a second version of the second code package; compile, and perform the second set of tests on [0047 – 0049], the second version of the second code package in order to determine that the second version of the second code package is valid; and transmit, to the second user device, a message indicating that the second version of the second code package is accepted [0048 – 0052, shows first version and second version as well as test data, error detection including pass and fail and change request including determining verification i.e. validation]. Regarding claim 3, the system of claim 1, wherein the one or more processors, to receive the first version of the first code package, are configured to: receive a set of files including computer code for the first version of the first code package [0047 – 0052]. Regarding claim 4, the system of claim 1, wherein the first set of tests includes at least one debugging test or at least one security test [0050, see determining whether the program has a fault]. Regarding claim 5, the system of claim 1, wherein the one or more processors, to provide the first set of results to the machine learning model in order to generate the first score, are configured to: transmit, to a machine learning host associated with the machine learning model, a request including the first set of results; and receive, from the machine learning host and in response to the request, an indication of the first score [0008 – 0012, shows determining scores and results as well as change request and a machine learning model]. Regarding claim 6, the system of claim 1, wherein the one or more processors are configured to: refrain from storing the first version of the second code package based on the first version the second code package being defective [0009, shows determining based on rule based ranking and scoring and which test case passes]. Regarding claim 7, Lee anticipates a method of selecting versions from a package repository, comprising: transmitting, to the package repository and from a user device, a request for a code package [0045, see stored central repository]; receiving, from the package repository and at the user device, an indication of a plurality of versions of the code package [0045, see stored central repository]; receiving, from the package repository and at the user device, an indication of a suggested version from the plurality of versions, wherein the suggested version is based on automatic testing of the code package by the package repository [0008 – 0012, shows machine learning language model and determining results as well as ranking and scores and test cases]; transmitting, to the package repository and from the user device, a request for the suggested version; and receiving, from the package repository and at the user device, at least one file included in the suggested version [0045 – 0048]. Regarding claim 8, the method of claim 7, wherein the request for the code package includes an identifier associated with the code package [0052 – 0053 shows identifying]. Regarding claim 9, the method of claim 7, wherein the code package comprises a set of files including software code [0047 – 0052]. Regarding claim 10, the method of claim 7, wherein the code package comprises bytecode [0047, see high level language by compiler]. Regarding claim 11, the method of claim 7, wherein the code package comprises at least one library including executable functions [0046, see executing file]. Regarding claim 12, the method of claim 7, wherein the plurality of versions are associated with a respective plurality of scores, and the indication of the suggested version comprises an indication that the suggested version is associated with a highest score in the respective plurality of scores [0008 – 0012, see scores and versions]. Regarding claim 13, the method of claim 7, wherein the indication of the plurality of versions is represented in a user interface (UI), and the indication of the suggested version comprises a visual indicator included in the UI [0087, see visualizing]. Regarding claim 14, see rationale in claim 7. Regarding claim 15, the non-transitory computer-readable medium of claim 14, wherein the one or more instructions, when executed by the one or more processors, cause the device to: transmit, to the package repository, a set of credentials, wherein the request to store the first version of the code package is accepted based on the set of credentials being validated. Regarding claim 16, the non-transitory computer-readable medium of claim 14, wherein the request to store the first version of the code package comprises an application programming interface call [0047 – 0052]. Regarding claim 17, the non-transitory computer-readable medium of claim 14, wherein the one or more instructions, when executed by the one or more processors, cause the device to: transmit a request for a webpage associated with the package repository; and receive the webpage in response to the request for the webpage, wherein the request to store the first version of the code package is transmitted in response to interaction with the webpage [0047 – 0052]. Regarding claim 18, the non-transitory computer-readable medium of claim 14, wherein the request to re-assess the second version of the code package comprises an application programming interface call [0047 – 0052]. Regarding claim 19, the non-transitory computer-readable medium of claim 14, wherein the message indicating that the first version of the code package is defective comprises an email message or a push notification [0120, see communicator]. Regarding claim 20, the non-transitory computer-readable medium of claim 14, wherein the message indicating that the second version of the code package is accepted comprises an email message or a push notification [0120]. Correspondence Information 5. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Chuck Kendall whose telephone number is 571-272-3698. The examiner can normally be reached on 10:00 am - 6:30pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung Sough can be reached on 571-272-6799. 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 [0060 – 0080]. 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). /CHUCK O KENDALL/ Primary Examiner, Art Unit 2192
Read full office action

Prosecution Timeline

Jul 25, 2024
Application Filed
Aug 10, 2026
Non-Final Rejection mailed — §102
Oct 01, 2026
Interview Requested

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12748850
Application Aware Software Asset Inventory
4y 9m to grant Granted Sep 29, 2026
Patent 12730623
EXECUTION OF MEASURE COMMAND FOR FIRMWARE UPDATE AND FIRMWARE UPDATE
2y 9m to grant Granted Sep 08, 2026
Patent 12724607
AUTOMATED CODE DOCUMENTATION
2y 7m to grant Granted Sep 01, 2026
Patent 12724598
PREDICTION OF ENVIRONMENTAL BEHAVIOR AND AUTOMATIC ADJUSTMENT OF NETWORK POLICY GENERATION FOR EDGE INFRASTRUCTURE
2y 11m to grant Granted Sep 01, 2026
Patent 12705040
UPGRADING AN EXISTING STANDARD ELECTRIC VEHICLE (EV) CHARGER FROM GRID TO VEHICLE (V1G) TO V1G PLUS VEHICLE TO GRID (V2G) OPERATION
3y 7m to grant Granted Aug 11, 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
87%
Grant Probability
95%
With Interview (+8.0%)
2y 11m (~9m remaining)
Median Time to Grant
Low
PTA Risk
Based on 933 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