Prosecution Insights
Last updated: July 17, 2026
Application No. 18/769,715

SERVICE CALL TOPIC PREDICTION

Non-Final OA §101
Filed
Jul 11, 2024
Examiner
WASAFF, JOHN S.
Art Unit
3629
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Dell Products L.P.
OA Round
3 (Non-Final)
33%
Grant Probability
At Risk
3-4
OA Rounds
1y 6m
Est. Remaining
78%
With Interview

Examiner Intelligence

Grants only 33% of cases
33%
Career Allowance Rate
128 granted / 383 resolved
-18.6% vs TC avg
Strong +44% interview lift
Without
With
+44.4%
Interview Lift
resolved cases with interview
Typical timeline
3y 6m
Avg Prosecution
34 currently pending
Career history
418
Total Applications
across all art units

Statute-Specific Performance

§101
12.2%
-27.8% vs TC avg
§103
73.5%
+33.5% vs TC avg
§102
3.8%
-36.2% vs TC avg
§112
5.2%
-34.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 383 resolved cases

Office Action

§101
DETAILED ACTION 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 . Claims 1-9 and 11-21 are pending. 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-9 and 11-21 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception without significantly more. Step 1 (The Statutory Categories): Is the claim to a process, machine, manufacture or composition of matter? MPEP 2106.03. Per Step 1, claim 1 is to a system (i.e., a machine), claim 9 to a method (i.e., a process), and claim 15 to a non-transitory computer-readable medium (i.e., a manufacture or machine). Thus, the claims are directed to statutory categories of invention. However, the claims are rejected under 35 U.S.C. 101 because they are directed to an abstract idea, a judicial exception, without reciting additional elements that integrate the judicial exception into a practical application. The analysis proceeds to Step 2A Prong One. Step 2A Prong One: Does the claim recite an abstract idea, law of nature, or natural phenomenon? MPEP 2106.04. The abstract idea of claim 1 is: receiving an indication regarding operation of a computer system; querying a database a first time, wherein the database comprises a dataset of issues that satisfies a first criterion of completeness and a second criterion of relevance, to receive a response to the query that identifies a group of potential issues for the computer system, wherein the group of potential issues for the computer system comprises a subset of the dataset of issues; ranking potential issues of the group of potential issues based on respective frequencies of occurrence during a prior time period, to produce a first ranking; caching the respective frequencies of occurrence during the prior time period, to produce respective cached frequencies, wherein the caching comprises storing an indication of the cached frequencies in a cache that is separate from the database; revising the first ranking based on characteristics of the computer system, to produce a second ranking; revising the second ranking based on metadata of the indication, to produce a third ranking; presenting at least part of the third ranking; updating how to rank potential issues based on feedback data received as input in response to the presenting; and performing a subsequent ranking for a second indication regarding operation of the computing equipment or other computing equipment based on the respective cached frequencies, and independently of querying the database a second time. The abstract idea of claim 9 is: querying a database a first time, wherein the database comprises a dataset of issues that satisfies a first criterion of completeness and a second criterion of relevance, to receive a response to the query that identifies a group of potential issues for computing equipment based on receiving an indication regarding operation of the computing equipment, wherein the group of potential issues for the computing equipment comprises a subset of the dataset of issues; ranking potential issues of the group of potential issues based on respective frequencies of occurrence during a prior time period, to produce a first ranking; caching the respective frequencies of occurrence during the prior time period, to produce respective cached frequencies, wherein the caching comprises storing an indication of the cached frequencies in a cache that is separate from the database; revising the first ranking based on characteristics of the computing equipment, to produce a second ranking; revising the second ranking based on metadata of the indication, to produce a third ranking; presenting at least a part of the third ranking; updating a process used to rank potential issues based on feedback data received in response to the presenting; and performing a subsequent ranking for a second indication regarding operation of the computing equipment or other computing equipment based on the respective cached frequencies, and independently of querying the database a second time. The abstract idea of claim 15 is: querying a data store a first time, wherein the database comprises a dataset of issues that satisfies a first criterion of completeness and a second criterion of relevance, to receive a response to the query that identifies a group of potential issues for a computing device based on receiving an indication regarding operation of the computing device, wherein the group of potential issues for the computing device comprises a subset of the dataset of issues; ranking potential issues of the group of potential issues based on respective frequencies of occurrence during a prior time period, based on characteristics of the computing device, and based on metadata of the indication, to produce a ranking; caching the respective frequencies of occurrence during the prior time period, to produce respective cached frequencies, wherein the caching comprises storing an indication of the cached frequencies in a cache that is separate from the data store; presenting at least a part of the ranking; and updating a technique for ranking potential issues based on feedback data received in response to the presenting; and performing a subsequent ranking for a second indication regarding operation of the computing equipment or other computing equipment based on the respective cached frequencies, and independently of querying the database a second time. The abstract idea steps italicized above describe the rules or instructions for ranking potential issues for a computing device, performed in a customer service context, which constitutes a process that, under its broadest reasonable interpretation, covers managing personal behavior relationships, interactions between people. This is further supported by [0001] of applicant’s specification as filed. If a claim limitation, under its broadest reasonable interpretation, covers managing personal behavior relationships, interactions between people, including social activities, teaching, and/or following rules or instructions, then it falls within the Certain Methods of Organizing Human Activity – Managing Personal Behavior Relationships, Interactions Between People grouping of abstract ideas. Accordingly, the claim recites an abstract idea. Examiner notes that MPEP 2106.04(a)(2), subsection II articulates that sub-groupings encompass certain activity between a person and a computer (e.g., a user querying a database): Finally, the sub-groupings encompass both activity of a single person (for example, a person following a set of instructions or a person signing a contract online) and activity that involves multiple people (such as a commercial interaction), and thus, certain activity between a person and a computer (for example a method of anonymous loan shopping that a person conducts using a mobile phone) may fall within the “certain methods of organizing human activity” grouping. Step 2A Prong Two: Does the claim recite additional elements that integrate the judicial exception into a practical application? MPEP 2106.04. Claim 1 recites the following additional elements: at least one processor; at least one memory that stores executable instructions; user interface. Claim 9 recites the following additional elements: system comprising at least one processor; user interface. Claim 15 recites the following additional elements: non-transitory computer-readable medium comprising instructions; system comprising at least one processor; user interface. These elements are merely instructions to apply the abstract idea to a computer, per MPEP 2106.05(f). Applicant has only described generic computing elements in their specification, as seen in [00152] of applicant’s specification as filed. Further, the combination of these elements is nothing more than a generic computing system. Because the additional elements are merely instructions to apply the abstract idea to a computer, as described in MPEP 2106.05(f), they do not integrate the abstract idea into a practical application. Therefore, per Step 2A Prong Two, the additional elements, alone and in combination, do not integrate the judicial exception into a practical application. The claim is directed to an abstract idea. Step 2B (The Inventive Concept): Does the claim recite additional elements that amount to significantly more than the judicial exception? MPEP 2106.05. Step 2B involves evaluating the additional elements to determine whether they amount to significantly more than the judicial exception itself. The examination process involves carrying over identification of the additional element(s) in the claim from Step 2A Prong Two and carrying over conclusions from Step 2A Prong Two pertaining to MPEP 2106.05(f). The additional elements and their analysis are therefore carried over: applicant has merely recited elements that facilitate the tasks of the abstract idea, as described in MPEP 2106.05(f). Further, the combination of these elements is nothing more than a generic computing system. When the claim elements above are considered, alone and in combination, they do not amount to significantly more. Therefore, per Step 2B, the additional elements, alone and in combination, are not significantly more. The claims are not patent eligible. The analysis takes into consideration all dependent claims as well: Dependent claims 2-8, 11-14, 16-19, and 21 include additional abstract steps and/or information that narrow the abstract idea(s) above. There are no further additional elements to consider, beyond those highlighted above. This narrowing of the abstract idea does not integrate into practical application and/or add significantly more. These claims are also ineligible. Dependent claim 20 includes additional abstract steps and/or information that narrow the abstract idea(s) above, in addition to reciting further additional elements (cloud computing equipment of a cloud computing platform). Similar to above, these generically recited computing components are simply being used to facilitate the tasks of the abstract idea. Whether viewed alone or in combination, this does not integrate the abstract idea into practical application and/or add significantly more. See MPEP 2106.05(f). Accordingly, claims 1-9 and 11-21 are rejected under 35 USC § 101 as being directed to non-statutory subject matter. Response to Arguments Applicant's RCE submission filed 3/20/26 contained no additional arguments. For the purposes of compact prosecution, however, examiner will address remarks from the 2/23/26 after-final response. Rejection of Claims 1-9 and 11-21 under 35 U.S.C. § 101 Applicant offers, after restating claim amendments and highlighting supporting portions in the specification (bracketed portions correspond to citations to applicant’s specification that have been omitted for brevity): As captured in the language of claim 1, the Specification describes a technical problem relating to slow computer processing of analyzing information in a database to predict a computer issue, and caching certain information outside of that database to expedite this computation in subsequent uses: […] The technical problem is slow computer processing, and the technical solution comprises a way to expedite this computer processing. Additionally, inasmuch as claim 1 makes specific recitations to when and how a database is used and when and how a cache is used, these recitations amount to "significantly more" than an abstract idea itself. Examiner disagrees. The additional elements, which are considered at Step 2A Prong Two and Step 2B, appear to be nothing more than generic computing components that facilitate the tasks of the abstract idea. Applicant has not provided for a technical improvement, as described in MPEP 2106.05(a), with reference to MPEP 2106.05(f). The “technical improvements” referenced by applicant in the remarks pertain to the benefits of automating a previously manual task. However, mere automaton of manual tasks does not automatically demonstrate an improvement to technology, as suggested by applicant. MPEP 2106.05(a) is informative: Examples that the courts have indicated may not be sufficient to show an improvement in computer-functionality: […] iii. Mere automation of manual processes, such as using a generic computer to process an application for financing a purchase, Credit Acceptance Corp. v. Westlake Services, 859 F.3d 1044, 1055, 123 USPQ2d 1100, 1108-09 (Fed. Cir. 2017) or speeding up a loan-application process by enabling borrowers to avoid physically going to or calling each lender and filling out a loan application, LendingTree, LLC v. Zillow, Inc., 656 Fed. App'x 991, 996-97 (Fed. Cir. 2016) (non-precedential). (Examiner’s highlight.) For these reasons, examiner maintains the rejections under 35 U.S.C. § 101. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure: US 20050160330, which teaches: A computer-implemented method processes issue data pertaining to a system. Issue data is received from a reporting entity, the issue data identifying an issue pertaining to the system and the reporting entity. A database is accessed to retrieve performance data regarding the reporting entity. The performance data is indicative of a past performance of the reporting entity in reporting issues pertaining to the system. A response activity, responsive to the issue, is automatically prioritized utilizing the performance data regarding the reporting entity. US 20220245647, which teaches: Systems for and methods of assessing the priority of a customer reported issue include receiving input regarding a customer issue experienced by a customer; calculating an incident grievance score by inserting the received input into a machine learning model; assigning a priority to the customer issue based on the calculated incident grievance score; receiving updated input regarding the customer issue; periodically recalculating the incident grievance score for the customer issue by inserting the received input and the updated input into the machine learning model; changing the priority of the customer issue when the recalculated incident grievance score differs from the calculated incident grievance score; and notifying a team assigned to fix the customer issue when the priority of the customer issue changes. US 20240211963, which teaches: Methods and systems for managing customer-encountered issues are disclosed. To manage the customer-encountered issues, a multiphase optimization process may be implemented to select a service agent to resolve each customer-encountered issue. The multiphase analysis may include a process of identifying service agents qualified to attempt to resolve each customer-encountered issue. The multiphase optimization may also include a process of ranking the qualified service agents based on their past performance and experience. The multiphase optimization may also include a process for estimating the likelihood of each of the qualified service agents resolving each customer-encountered issue within prescribed goals. Any inquiry concerning this communication or earlier communications from the examiner should be directed to JOHN SAMUEL WASAFF whose telephone number is (571)270-5091. The examiner can normally be reached Monday through Friday 8:00 am to 6: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, SARAH MONFELDT can be reached at (571) 270-1833. 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. JOHN SAMUEL WASAFF Primary Examiner Art Unit 3629 /JOHN S. WASAFF/Primary Examiner, Art Unit 3629
Read full office action

Prosecution Timeline

Show 6 earlier events
Jan 30, 2026
Applicant Interview (Telephonic)
Jan 30, 2026
Examiner Interview Summary
Feb 23, 2026
Response after Non-Final Action
Mar 30, 2026
Request for Continued Examination
Apr 13, 2026
Response after Non-Final Action
Apr 29, 2026
Non-Final Rejection mailed — §101
Jun 04, 2026
Examiner Interview Summary
Jun 04, 2026
Applicant Interview (Telephonic)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12608716
OWNERSHIP RESTRICTED ELECTRONIC TICKETING SYSTEM
4y 5m to grant Granted Apr 21, 2026
Patent 12602710
ENSEMBLE OF LANGUAGE MODELS FOR IMPROVED USER SUPPORT
2y 5m to grant Granted Apr 14, 2026
Patent 12555122
OMNI-CHANNEL CONTEXT SHARING
2y 3m to grant Granted Feb 17, 2026
Patent 12548095
Artificial Intelligence for Sump Pump Monitoring and Service Provider Notification
2y 7m to grant Granted Feb 10, 2026
Patent 12547996
COMPUTING SYSTEM FOR SHARING NETWORKS PROVIDING SHARED RESERVE FEATURES AND RELATED METHODS
2y 2m to grant Granted Feb 10, 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

3-4
Expected OA Rounds
33%
Grant Probability
78%
With Interview (+44.4%)
3y 6m (~1y 6m remaining)
Median Time to Grant
High
PTA Risk
Based on 383 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