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 .
Introduction
The following is a final Office Action in response to Applicant’s communications received on June 5, 2026. Claims 9-12 have been amended, claims 1-8 and 13-28 have been cancelled, and claims 29-43 have been added.
Currently claims 9-12 and 29-43 are pending with claims 9-12 and 29-34 under consideration and claims 35-43 being directed to no-elected invention. Claim 9 is independent.
Election/Restrictions
Since Applicant has received an action on the merits for the originally presented invention, this invention has been constructively elected by original presentation for prosecution on the merits. Accordingly, claims 35-43 are withdrawn from consideration as being directed to a non-elected invention. See 37 CFR 1.142(b) and MPEP § 821.03.
Claims 9-12 and 29-34 drawn to a subcombination for generating a software application for performing an enterprise function, classified in G06Q 10/0633, G06N 20/00.
Claims 35-43 drawn to a subcombination of a generative artificial intelligence (AI) system, classified in G06Q 10/06, G06N 3/08.
The newly amended claims directed to an invention that is independent or distinct from the invention originally claimed for the following reasons:
Inventions I and II are related as subcombinations disclosed as usable together in a single combination. The subcombinations are distinct if they do not overlap in scope and are not obvious variants, and if it is shown that at least one subcombination is separately usable. In this case, subcombination I has separate utility such as: automatically and without user intervention generating, via the processing circuitry, a localized runtime software container incorporating rule derived from the data extraction map; cryptographically obfuscating, via the processing circuitry, sensitive identification fields within data pulled via the data extraction map prior to executing an outbound transfer string from the localized runtime software container to an external processor resource; and updating, via the processing circuitry, the knowledge base with the cryptographically obfuscated data pulled via the data extraction map, and automatically training the foundational transformer model based on the updated knowledge base. Subcombination II has separate utility such as automatically, using an artificial intelligence (AI) agent executed by the processing circuitry, respond to the received conversational text playload by executing a response that queries the user device for the specific piece of information that is needed, and does not include the steps of cryptographically obfuscate sensitive identification fields within data pulled via the data extraction map prior to executing an outbound transfer string from the localized runtime software container to an external processor resource; and updating the knowledge base with the cryptographically obfuscated data pulled via the data extraction map, and automatically training the foundational transformer model based on the updated knowledge base, as required in claim 9. See MPEP § 806.05(d).
The examiner has required restriction between subcombinations usable together. Where applicant elects a subcombination and claims thereto are subsequently found allowable, any claim(s) depending from or otherwise requiring all the limitations of the allowable subcombination will be examined for patentability in accordance with 37 CFR 1.104. See MPEP § 821.04(a). Applicant is advised that if any claim presented in a continuation or divisional application is anticipated by, or includes all the limitations of, a claim that is allowable in the present application, such claim may be subject to provisional statutory and/or nonstatutory double patenting rejections over the claims of the instant application.
Restriction for examination purposes as indicated is proper because all these inventions listed in this action are independent or distinct for the reasons given above and there would be a serious search and/or examination burden if restriction were not required because one or more of the following reasons apply:
(a) the inventions have acquired a separate status in the art in view of their different classification;
(b) the inventions have acquired a separate status in the art due to their recognized divergent subject matter;
(c) the inventions require a different field of search (for example, searching different classes/subclasses or electronic resources, or employing different search queries);
(d) the prior art applicable to one invention would not likely be applicable to another invention;
(e) the inventions are likely to raise different non-prior art issues under 35 U.S.C. 101 and/or 35 U.S.C. 112, first paragraph.
Applicant(s) are reminded that upon the cancellation of claims to a non-elected invention, the inventorship must be amended in compliance with 37 CFR 1.48(b) if one or more of the currently named inventors is no longer an inventor of at least one claim remaining in the application. Any amendment of inventorship must be accompanied by a request under 37 CFR 1.48(b) and by the fee required under 37 CFR 1.17(i).
Response to Amendments
Applicant’s amendments necessitated the new ground(s) of rejection in this Office Action.
The 35 U.S.C. § 112(b) rejection as set forth in the previous Office Action is withdrawn in response to Applicant’s amendment.
The 35 U.S.C. § 101 rejection as set forth in the previous Office Action is withdrawn (conditional based on the 35 U.S.C. § 112(a) rejection set forth below) in response to Applicant’s amendments as claim 9 recites “training, via the processing circuitry using deep learning techniques, a foundational transformer model to determine steps of a data extraction map with data relevant to the determined enterprise function data domain token to determine steps of a data extraction map, wherein training includes applying deep learning techniques to and learn learning based on relevant domain-specific enterprise data from a knowledge base associated with the foundational transformer model, and storing data resulting from the training in an electronic storage device; determining, via the processing circuitry using the trained foundational transformer model, steps of the data extraction map based on the determined data domain token and relevant domain-specific enterprise data from the knowledge base; and updating, via the processing circuitry, the knowledge base with the cryptographically obfuscated data nulled via the data extraction map, and automatically training the foundational transformer model based on the updated knowledge base, which improve the functionality of the foundational transformer model each time when executed by the processing circuitry.
The 35 U.S.C. § 103 rejection as set forth in the previous Office Action is withdrawn (conditional based on the 35 U.S.C. § 112(a) rejection set forth below) in response to Application’s amendments. The closest prior art of Charisius et al., (US 2002/0078432), and in view of Cella et al., (WO 2024155584), and further in view of Martin (WO 2025/0174383), whether considered individually or in combination fails to teach or suggest “training, via the processing circuitry using deep learning techniques, a foundational transformer model to determine steps of a data extraction map with data relevant to the determined enterprise function data domain token to determine steps of a data extraction map, wherein training includes applying deep learning techniques to and learn learning based on relevant domain-specific enterprise data from a knowledge base associated with the foundational transformer model, determining, via the processing circuitry using the trained foundational transformer model, steps of the data extraction map based on the determined data domain token and relevant domain-specific enterprise data from the knowledge base; generating a localized runtime software container incorporating rules derived from the data extraction map, and cryptographically obfuscating sensitive identification fields within data pulled via the data extraction map prior to executing an outbound transfer string from the localized runtime software container to an external processor resource.” as recited in the amended claim 9.
Claim Rejections – 35 USC § 112
The following is a quotation of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), first paragraph:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 9-12 and 29-34 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for pre-AIA the inventor(s), at the time the application was filed, had possession of the claimed invention. The added subject matter which is not in the original specification is as follows:
Claims 9-12 and 29-34 recite one or more of “text payload”, “initializing an environment isolation container”, “metadata token”, “a data extraction map”, “data domain token”, “a localized runtime software container”, “cryptographically obfuscating”, “persona metadata enter field”, “sensitive identification fields within data pulled via the data extraction map prior to executing an outbound transfer string from the localized runtime software container to an external processor resource”, and “persona metadata token is uniquely mapped to a user role definition containing parameters”, appear to constitute new matter. Examiner could neither able to find any support for these limitations from the table at the end of the Remarks nor from the specification as originally filed. Applicant is required to cancel the new matter throughout the application in the reply to this Office Action.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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 extension fee 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 date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PAN CHOY whose telephone number is (571)270-7038. The examiner can normally be reached 5/4/9 compressed work schedule.
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, Jerry O'Connor can be reached on 571-272-6787. 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.
/PAN G CHOY/Primary Examiner, Art Unit 3624