Prosecution Insights
Last updated: July 05, 2026
Application No. 19/063,208

Controlling Execution of Artificial Intelligence Pipelines for Data Retrieval Through Client Applications

Final Rejection §DP
Filed
Feb 25, 2025
Priority
May 15, 2024 — provisional 63/648,162 +1 more
Examiner
OBERLY, VAN HONG
Art Unit
2166
Tech Center
2100 — Computer Architecture & Software
Assignee
Airia LLC
OA Round
2 (Final)
75%
Grant Probability
Favorable
3-4
OA Rounds
1y 9m
Est. Remaining
91%
With Interview

Examiner Intelligence

Grants 75% — above average
75%
Career Allowance Rate
459 granted / 611 resolved
+20.1% vs TC avg
Strong +16% interview lift
Without
With
+15.5%
Interview Lift
resolved cases with interview
Typical timeline
3y 1m
Avg Prosecution
10 currently pending
Career history
621
Total Applications
across all art units

Statute-Specific Performance

§101
1.0%
-39.0% vs TC avg
§103
91.4%
+51.4% vs TC avg
§102
2.9%
-37.1% vs TC avg
§112
0.4%
-39.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 611 resolved cases

Office Action

§DP
DETAILED ACTION The Action is responsive to Applicant’s Application filed March 31, 2025. Please note claims 21-40 are pending. Terminal Disclaimer The Terminal Disclaimer has been disapproved. The person who signed the terminal disclaimer is not the applicant, the patentee or an attorney or agent of record. See 37 CFR 1.321(a) and (b). Please file a POA that gives power to the attorney and/or agent of record who is signing the TD, along with another copy of the TD form. Or file a TD form that is signed by the applicant. No Additional fee is required with the resubmission. Double Patenting The nonstatutory 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 nonstatutory 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 nonstatutory 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 nonstatutory 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 21, 39-40 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 16, 20 of U.S. Patent No. 12,235,882. Although the claims at issue are not identical, they are not patentably distinct from each other because: "A later patent claim is not patentably distinct from an earlier patent claim if the later claim is obvious over, or anticipated by, the earlier claim. In re Longi, 759 F.2d at 896, 225 USPQ at 651 (affirming a holding of obviousness-type double patenting because the claims at issue were obvious over claims in four prior art patents); In re Berg, 140 F.3d at 1437, 46 USPQ2d at 1233 (Fed. Cir. 1998) (affirming a holding of obviousness-type double patenting where a patent application claim to a genus is anticipated by a patent claim to a species within that genus)." ELI LILLY AND COMPANY v BARR LABORATORIES, INC., United States Court of Appeals for the Federal Circuit, ON PETITION FOR REHEARING EN BANC (DECIDED: May 30, 2001). "Claim 12 and Claim 13 are generic to the species of invention covered by claim 3 of the patent. Thus, the generic invention is "anticipated" by the species of the patented invention. Cf., Titanium Metals Corp. v. Banner, 778 F.2d 775, 227 USPQ 773 (Fed. Cir. 1985) (holding that an earlier species disclosure in the prior art defeats any generic claim). This court’s predecessor has held that, without a terminal disclaimer, the species claims preclude issuance of the generic application. In re Van Ornum, 686 F.2d 937, 944, 214 USPQ 761, 767 (CCPA 1982); Schneller, 397 F.2d at 354. Accordingly, absent a terminal disclaimer, claims 12 and 13 were properly rejected under the doctrine of obviosuness-type double patenting" (In re Goodman (CA FC) 29 USPQ2d 2010 (12/3/1993). Claims 21, 39-40 of the current application are generic to the species of invention covered by claims 1, 16, 20 of U.S. Patent No. 12,235,882. Therefore the current application is anticipated by the species of U.S. Patent No. 12,235,882. Instant Application 19/063208 US Patent No. 12,235,882 21. A method for controlling execution of artificial intelligence (AI) pipelines for semantic data retrieval through client applications, comprising: receiving, at a user device from a server, a first AI endpoint key and a second AI endpoint key; receiving an input at the user device; determining, by an application executing on the user device, a first status of the user device, wherein the application selects a first AI endpoint from a plurality of AI endpoints based on the first status of the device, wherein the selected first AI endpoint is local to the user device; authorizing access to the first AI endpoint using the first AI endpoint key; determining whether access to a local dataset is authorized for a user submitting the input; causing, based on the input, generation of input vectors for comparison to dataset vectors of a vector database, the dataset vectors corresponding to data chunks of the local dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database; identifying the data chunks that correspond to the identified similar vectors; identifying, by the application, a local AI model for use with the input based on an object selection rule; identifying first prompts for use with the local AI model, wherein at least one of the identified prompts relates to formatting specific to a graphical user interface ("GUI") at the user device; transmitting the first prompts and the identified data chunks to the local AI model; and causing results of the local AI model to be displayed on the GUI at the user device. 1. A method for controlling execution of artificial intelligence (AI) pipelines for semantic data retrieval through client applications, comprising: receiving, at an AI pipeline endpoint, an AI endpoint key and an AI pipeline input from a client application that executes on a user device, the user device being associated with a user; causing an AI pipeline execution engine to perform stages including: identifying a dataset associated with the AI pipeline input; based on a management policy, determining whether access to the dataset is authorized for a user submitting the AI pipeline input; causing, based on the AI pipeline input, generation of input vectors with an embedding model, wherein dataset vectors in a vector database were also generated with the embedding model, and wherein the dataset vectors correspond to data chunks of the identified dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database; identifying the data chunks that correspond to the identified similar vectors; identifying a first AI model for use with the AI pipeline input based on an object selection rule; generating prompts for use with the first AI model, wherein at least one of the generated prompts relates to formatting specific to the client application; transmitting the generated prompts and the identified data chunks to the first AI model; and receiving, from the first Al model, search results that correspond to the AI pipeline input; adding a hyperlink to the search results, the hyperlink being generated based at least in part on a location of text that corresponds to the identified data chunks; and causing the search results to be displayed on a user interface provided by the client application. 39. (New) A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, causes the processor to perform stages for controlling execution of artificial intelligence ("AI") pipelines for semantic data retrieval through client applications, the stages comprising: receiving, at a user device from a server, a first AI endpoint key and a second AI endpoint key; receiving an input at the user device; determining, by an application executing on the user device, a first status of the user device, wherein the application selects a first AI endpoint from a plurality of AI endpoints based on the first status of the device, wherein the selected first AI endpoint is local to the user device; validating access to the first Al endpoint using the first Al endpoint key; determining whether access to a local dataset is authorized for a user submitting the input; causing, based on the input, generation of input vectors for comparison to dataset vectors of a vector database, the dataset vectors corresponding to data chunks of the local dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database; identifying the data chunks that correspond to the identified similar vectors; identifying, by the application, a local AI model for use with the input based on an object selection rule; identifying first prompts for use with the local AI model, wherein at least one of the identified prompts relates to formatting specific to a graphical user interface ("GUI") at the user device; transmitting the first prompts and the identified data chunks to the local AI model; and causing results of the local AI model to be displayed on the GUI at the user device. 16. A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, causes the processor to perform stages for controlling execution of artificial intelligence (AI) pipelines for semantic data retrieval through client applications, the stages comprising: receiving, at an Al pipeline endpoint, an Al endpoint key and an Al pipeline input from an application that executes on a user device, the user device being associated with a user; causing an AI pipeline execution engine to perform search stages including: identifying a dataset associated with the AI pipeline input; based on a management policy, determining whether access to the dataset is authorized for a user submitting the AI pipeline input; causing generation of input vectors with an embedding model, wherein the embedding model is selected based on having generated dataset vectors in a vector database, the dataset vectors corresponding to the identified dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database, wherein the similar vectors include dataset vectors that are within a threshold distance or angle measurement to the input vectors; identifying data chunks that correspond to the identified similar vectors; identifying a first AI model for use with the AI pipeline input, including determining that user of the first AI model complies with an object selection rule that relates to compute performance cost, memory performance cost, or network component cost for using the first AI model; generating prompts for use with the first AI model, wherein the prompts are generated based on the application and a user selection from the application; transmitting the generated prompts and the identified data chunks to the first AI model; and receiving, from the first Al model, search results that correspond to the AI pipeline input; adding a hyperlink to the search results; and causing display of the search results within the application. 40. (New) A system for controlling execution of artificial intelligence (AI) pipelines for semantic data retrieval through client applications, comprising: a memory storage including a non-transitory, computer-readable medium comprising instructions; and at least one hardware-based processor that executes the instructions to carry out stages comprising: receiving, at a user device from a server, a first Al endpoint key and a second Al endpoint key; receiving an input at the user device; determining, by an application executing on the user device, a first status of the user device, wherein the application selects a first AI endpoint from a plurality of AI endpoints based on the first status of the device, wherein the selected first AI endpoint is local to the user device; validating access to the first AI endpoint using the first AI endpoint key; determining whether access to a local dataset is authorized for a user submitting the input; causing, based on the input, generation of input vectors for comparison to dataset vectors of a vector database, the dataset vectors corresponding to data chunks of the local dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database; identifying the data chunks that correspond to the identified similar vectors; identifying, by the application, a local AI model for use with the input based on an object selection rule; identifying first prompts for use with the local AI model, wherein at least one of the identified prompts relates to formatting specific to a graphical user interface ("GUI") at the user device; transmitting the first prompts and the identified data chunks to the local Al model; causing results of the local AI model to be displayed on the GUI at the user device. 20. A system for controlling execution of artificial intelligence (AI) pipelines for semantic data retrieval through client applications, comprising: a memory storage including a non-transitory, computer-readable medium comprising instructions; and at least one hardware-based processor that executes the instructions to carry out stages comprising: receiving, at an AI pipeline endpoint, an AI endpoint key and an AI pipeline input from a client application that executes on a user device, the user device being associated with a user; identifying a dataset associated with the AI pipeline input; based on a management policy, determining whether access to the dataset is authorized for a user submitting the AI pipeline input; causing generation of input vectors with an embedding model, wherein the embedding model is selected based on having generated dataset vectors in a vector database, the dataset vectors corresponding to the identified dataset; causing identification of similar vectors based on comparing the input vectors to the dataset vectors of the vector database, wherein the similar vectors include dataset vectors that are within a threshold distance or angle measurement to the AI pipeline input vectors; identifying data chunks that correspond to the identified similar vectors; identifying an AI model for use with the AI pipeline input, including determining that user of the AI model complies with an object selection rule that is based on user information and cost or performance thresholds of the AI model; generating prompts for use with the AI model, wherein the prompts are generatedbased on the application and a user selection from the application; transmitting the generated prompts and the identified data chunks to the Al model; and receiving, from the first AI model, search results that correspond to the AI pipeline input; adding a hyperlink to the search results; and causing display of the search results within the client application. Allowable Subject Matter Claims 22-38 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. Conclusion THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to VAN OBERLY whose telephone number is (571)272-7025. The examiner can normally be reached Monday - Friday, 7:30am-4pm MT. 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, Sanjiv Shah can be reached at (571) 272-4098. 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. /VAN H OBERLY/Primary Examiner, Art Unit 2166
Read full office action

Prosecution Timeline

Feb 25, 2025
Application Filed
Mar 31, 2025
Response after Non-Final Action
Jan 28, 2026
Non-Final Rejection mailed — §DP
Mar 13, 2026
Response Filed
Jun 04, 2026
Final Rejection mailed — §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12664129
Applying Rules to Client Updates on Shared Records to Trigger System-Generated Updates
6y 2m to grant Granted Jun 23, 2026
Patent 12664200
Centralized Resource Management for Disparate Communication Platforms
4y 7m to grant Granted Jun 23, 2026
Patent 12645424
METHODS AND SYSTEMS FOR IDENTIFYING A LEVEL OF SIMILARITY BETWEEN A PLURALITY OF DATA REPRESENTATIONS
1y 7m to grant Granted Jun 02, 2026
Patent 12639345
METHOD AND SYSTEM FOR GENERATING EXECUTIVE SUMMARIES AND DATA VISUALIZATIONS FOR ANNUAL PRODUCT QUALITY REPORTS
2y 0m to grant Granted May 26, 2026
Patent 12613894
INFORMATION PROCESSING APPARATUS, COMPUTER PROGRAM PRODUCT, AND INFORMATION PROCESSING METHOD
1y 4m to grant Granted Apr 28, 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
75%
Grant Probability
91%
With Interview (+15.5%)
3y 1m (~1y 9m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 611 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