Prosecution Insights
Last updated: April 19, 2026
Application No. 18/622,141

SYSTEM AND METHOD FOR MANAGING UPDATES TO WEBPAGES

Non-Final OA §101
Filed
Mar 29, 2024
Examiner
ST LEGER, GEOFFREY R
Art Unit
2192
Tech Center
2100 — Computer Architecture & Software
Assignee
Infosys Limited
OA Round
1 (Non-Final)
82%
Grant Probability
Favorable
1-2
OA Rounds
2y 9m
To Grant
99%
With Interview

Examiner Intelligence

Grants 82% — above average
82%
Career Allow Rate
524 granted / 635 resolved
+27.5% vs TC avg
Strong +22% interview lift
Without
With
+21.6%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
28 currently pending
Career history
663
Total Applications
across all art units

Statute-Specific Performance

§101
16.6%
-23.4% vs TC avg
§103
48.2%
+8.2% vs TC avg
§102
14.7%
-25.3% vs TC avg
§112
12.7%
-27.3% vs TC avg
Black line = Tech Center average estimate • Based on career data from 635 resolved cases

Office Action

§101
DETAILED ACTION The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Claims 1-20 have been submitted for examination and are pending further prosecution by the United States Patent & Trademark Office. Allowable Subject Matter With respect to independent claim 1, the prior art of record does not teach or suggest, either solely or in combination, the limitations "predicting, by the server, based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; and selecting, by the server, a first deployment strategy from a plurality of pre-defined deployment strategies based on the predicted first impact score and a set of rules, wherein the first deployment strategy is executed for the updating and the deployment of the first webpage based on the first set of updates." when considered in combination with the other limitations of claim 1. With respect to independent claim 10, the prior art of record does not teach or suggest, either solely or in combination, the limitations "predict, based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; and select a first deployment strategy from a plurality of pre-defined deployment strategies based on the predicted first impact score and a set of rules, wherein the first deployment strategy is executed for the updating and deployment of the first webpage based on the first set of updates." when considered in combination with the other limitations of claim 10. With respect to independent claim 19, the prior art of record does not teach or suggest, either solely or in combination, the limitations "predicting based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; and selecting a first deployment strategy from a plurality of pre-defined deployment strategies based on the predicted first impact score and a set of rules, wherein the first deployment strategy is executed for the updating and the deployment of the first webpage based on the first set of updates." when considered in combination with the other limitations of claim 19. Note, however, that claims 1-20 are rejected under 35 USC § 101 as being directed to an abstract idea. Claim Objections The following claims are objected to because of antecedence issues. It is suggested Applicants amend these claims as follows: Claim 1 -- predicting, by the server, based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; -- Claim 2 -- the first plurality of features include at least two or more of a page type of a webpage, a code structure of a webpage, a count of code snippets associated with a webpage, a locale associated with a webpage, a caching arrangement for loading a webpage, a versioning history of a webpage, a current average time taken for a webpage to load on a user device, a current average time taken for a webpage to activate interactive features post loading, a previous average time taken for a webpage to load on a user device, a previous average time taken for a webpage to activate interactive features post loading; -- -- training, by the server, using the first training dataset, the first ML model to predict an impact of updates on a performance of a webpage, wherein the trained first ML model is used for the prediction of the first impact score. -- Claim 7 -- the second plurality of features include at least two or more of a page type of a webpage, a type of content associated with a webpage, a locale associated with a webpage, an average time taken for a webpage to load on a user device, an average time taken for a webpage to activate interactive features post loading; -- -- training, by the server, using the second training dataset, the second ML model to predict an impact of updates on conversion corresponding to a webpage, wherein the trained second ML model is used for the prediction of the second impact score. -- Claim 9 -- an average time taken for a webpage to load on a user device and an average time taken for a webpage to activate interactive features post loading. -- Claim 10 -- predict, based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; and -- Claim 11 -- the first plurality of features include at least two or more of a page type of a webpage, a code structure of a webpage, a count of code snippets associated with a webpage, a locale associated with a webpage, a caching arrangement for loading a webpage, a versioning history of a webpage, a current average time taken for a webpage to load on a user device, a current average time taken for a webpage to activate interactive features post loading, a previous average time taken for a webpage to load on a user device, a previous average time taken for a webpage to activate interactive features post loading; -- -- train, using the first training dataset, the first ML model to predict an impact of updates on a performance of a webpage, wherein the trained first ML model is used for the prediction of the first impact score. -- Claim 16 -- the second plurality of features include at least two or more of a page type of a webpage, a type of content associated with a webpage, a locale associated with a webpage, a positioning of content in a webpage, an average time taken for a webpage to load on a user device, an average time taken for a webpage to activate interactive features post loading; -- -- train, using the second training dataset, the second ML model to predict an impact of updates on conversion corresponding to a webpage, wherein the trained second ML model is used for the prediction of the second impact score. -- Claim 18 -- an average time taken for a webpage to load on a user device and an average time taken for a webpage to activate interactive features post loading. -- Claim 19 -- predicting based on the first set of elements and using a first machine learning (ML) model, a first impact score indicative of an impact of the first set of updates on a set of performance metrics associated with the first webpage, wherein the first impact score is predicted prior to deployment of an [[the]] updated first webpage; and -- Claims 2-9 and 11-18 are additionally objected to due to their dependence on objected parent claim(s). Appropriate correction is required. Claim Rejections - 35 USC § 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. Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Claim 1 recites a method for managing updates to webpages. Under a broadest reasonable interpretation, claim 1 would fall under the category of mental processes as the claim features limitations performable as mental steps, with the assistance of pen & paper, but without additional elements that integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. An analysis of claim 1 according to the 2019 Revised Patent Subject Matter Eligibility test follows: Step 1: Is the claim directed to a process, machine, manufacture or composition of matter? Yes, claim 1 is directed to a method and, therefore, a process. Step 2A Prong 1: Does the claim recite an Abstract Idea, Law of Nature, or Natural Phenomenon? Yes, claim 1 recites an abstract idea as the following limitations are performable as mental processes with the assistance of pen & paper: receiving- A software developer can receive a printout of proposed updates, containing program code, for updating a deployed webpage; predictingan [[the]] updated first webpage; - The software developer can manually analyze the proposed updates and derive, using a formula, an impact score reflecting the impact the proposed updates could have on performance metrics if the updates were applied to the webpage. selectingThe developer can decide not to apply the proposed updates to the webpage upon determining that application of the updates would degrade performance metrics associated with the webpage beyond acceptable thresholds. Step 2A Prong 2: Does the Claim Recite Additional Elements That Integrate The Judicial Exception Into A Practical Application? Claim 1 recites the additional element of a server for performing the receiving, predicting and performing steps. However, as recited, the server is merely used as a tool for performing the abstract idea and, therefore, does not integrate the abstract idea into a practical application. Claim 1 also recites the additional element of using a first machine learning (ML) model to predict the first impact score. However, since the claim does not provide any detail regarding how the ML model predicts the impact score, the additional element can be considered a generic machine learning technique for performing the abstract idea. Consequently, the additional element does not integrate the abstract idea into a practical application. Step 2B: Does the Claim Recite Additional Elements That Amount To Significantly More Than The Judicial Exception? Claim 1 recites the additional element of a server for performing the receiving, predicting and performing steps. However, as recited, the server is merely used as a tool for performing the abstract idea and, therefore, is not significantly more than the abstract idea. Claim 1 also recites the additional element of using a first machine learning (ML) model to predict the first impact score. However, since the claim does not provide any detail regarding how the ML model predicts the impact score, the additional element can be considered a generic machine learning technique for performing the abstract idea. Consequently, the additional element is not significantly more than the abstract idea. Claim 10 is rejected for the same reasons given for analogous claim 1. While claim 10 recites other additional elements, including a processor, and a memory storing instructions executable by the processor, these additional elements merely constitute generic computing components for performing the abstract idea and, therefore, do not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claim 19 is rejected for the same reasons given for analogous claim 1. While claim 19 recites other additional elements, including a non-transitory computer readable medium, computer executable instructions, and a computer, these additional elements merely constitute generic computing components for performing the abstract idea and, therefore, do not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claims 2 and 11 are also directed to the abstract idea as determining two or more features, and corresponding feature values, for training the first ML model, and generating a training dataset, can be performed as mental steps with the assistance of pen & paper. While the claims also recite the additional element of training, by the server, using the first training dataset, the first ML model to predict an impact of updates on a performance of a webpage, wherein the trained first ML model is used for the prediction of the first impact score (claim 2), since the claims provide no detail regarding how the first ML model is trained by the server, the additional element can be considered a generic machine learning technique for performing the abstract idea. Consequently, the additional element does not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claims 3 and 12 are also directed to the abstract idea as generating a second plurality of feature values can be performed as mental steps with the assistance of pen & paper. While the claims also recite the additional element of providing, by the server, the second plurality of feature values as input to the first ML model, wherein the first impact score is outputted by the first ML model in response to the provided input (claim 3), since the claim provides no detail regarding how the first ML model outputs the first impact score responsive to the server providing the second plurality of feature values, the additional element can be considered a generic machine learning technique for performing the abstract idea. Consequently, the additional element does not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claims 4, 13 and 20 recite the additional element of wherein the plurality of deployment strategies corresponds to a plurality of integration/continuous deployment (CI/CD) pipelines and wherein a first CI/CD pipeline of the plurality of CI/CD pipelines is executed for the updating and the deployment of the first webpage (claim 4). However, the additional element merely links use of the abstract idea to the particular technological environment of CI/CD pipelines and, therefore, does not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claims 5 and 14 recite an additional iteration of the receiving, predicting and selecting steps from claims 1 and 10, respectively, using a second set of updates. Since the claims do not recite further additional elements that integrate the abstract idea into a practical application or amount to significantly more than the abstract idea, the claims are rejected for the same reasons given for claims 1 and 10. Claims 6 and 15 recite an additional iteration of the predicting step and an elaboration of the selecting step from claims 1 and 10, respectively, using a second ML model to predict a second impact score, from which the first deployment strategy is additionally based upon. Since the claims do not recite further additional elements that integrate the abstract idea into a practical application or amount to significantly more than the abstract idea, the claims are rejected for the same reasons given for claims 1 and 10. Claims 7 and 16 are also directed to the abstract idea as determining two or more features, and corresponding feature values, for training the second ML model, and generating a second training dataset, can be performed as mental steps with the assistance of pen & paper. While the claims also recite the additional element of training, by the server, using the second training dataset, the second ML model to predict an impact of updates on conversion corresponding to a webpage, wherein the trained second ML model is used for the prediction of the second impact score (claim 7), since the claims provide no detail regarding how the second ML model is trained by the server, the additional element can be considered a generic machine learning technique for performing the abstract idea. Consequently, the additional element does not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claims 8 and 17 are also directed to the abstract idea as the developer can manually assign weights to the impact scores, determine an aggregate impact score and use the aggregated impact score for determining the first deployment strategy. While the claims recite the additional element of using a server or processor for performing the determining steps, as recited, the additional element simply amounts to using a computer as a tool to perform the abstract idea. Consequently, the additional element does not integrate the abstract idea into a practical application or amount to significantly more than the abstract idea. Claim 9 and 18 are also directed to the abstract idea as they merely elaborate upon limitations found abstract in independent claims 1 and 10, respectively. Since the claims lack additional elements that integrate the abstract idea into a practical application or amount to significantly more than the abstract idea, the claims are ineligible. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. US 20200034135 A1 discloses a machine learning-based method to measure and evaluate the impact of software changes on components of cloud computing platforms. US 20200134457 A1 discloses a method for using machine learning to determine indications of change in software. US 20230088784 A1 discloses a method and system for using a machine learning model to predict a risk associated with deploying an impending code change. US 20250085967 A1 discloses a method and system for using a machine learning-based impact model for determining whether a code change impacts a documentation set requiring an update to the documentation set. The NPL document "Predicting Software Maintenance Type, Change Impact, and Maintenance Time Using Machine Learning Algorithms" proposes a method for predicting maintenance type, impacts of changes, and maintenance time for requested software changes using machine learning. The NPL document "A Prediction Model for Software Requirements Change Impact" discusses research to use a combination of Machine Learning and Natural Language Processing for performing change impact analysis on software requirements. Any inquiry concerning this communication or earlier communications from the examiner should be directed to GEOFFREY R ST LEGER whose telephone number is (571)270-7720. The examiner can normally be reached M-F (IFP) ~9:00-5: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) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung S Sough can be reached at 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 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. /GEOFFREY R ST LEGER/Primary Examiner, Art Unit 2192
Read full office action

Prosecution Timeline

Mar 29, 2024
Application Filed
Mar 10, 2026
Non-Final Rejection — §101 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12602214
DYNAMIC EVALUATION AND IMPROVEMENT OF ENERGY EFFICIENCY OF COMPUTER CODE
2y 5m to grant Granted Apr 14, 2026
Patent 12596939
AUTOMATIC LABELING OF DATA BY AN ENTITY GATHERING THE DATA
2y 5m to grant Granted Apr 07, 2026
Patent 12591716
METHODS AND APPARATUS FOR SECURE EXECUTION ON SMART NETWORK INTERFACE CARDS
2y 5m to grant Granted Mar 31, 2026
Patent 12572829
MONITORING MACHINE LEARNING MODELS IN RESOURCE CONSTRAINED SETTINGS
2y 5m to grant Granted Mar 10, 2026
Patent 12572628
SYSTEMS AND METHODS FOR EXECUTABLE GRAPH-BASED MODEL OWNERSHIP
2y 5m to grant Granted Mar 10, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

1-2
Expected OA Rounds
82%
Grant Probability
99%
With Interview (+21.6%)
2y 9m
Median Time to Grant
Low
PTA Risk
Based on 635 resolved cases by this examiner. Grant probability derived from career allow 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