Prosecution Insights
Last updated: August 17, 2026
Application No. 18/794,701

SYSTEMS AND METHODS FOR CONFIGURING DATA USING ADVANCED COMPUTATIONAL MODELS FOR DATA ANALYSIS AND AUTOMATED PROCESSING

Final Rejection §103
Filed
Aug 05, 2024
Examiner
SHIBEROU, MAHELET
Art Unit
2171
Tech Center
2100 — Computer Architecture & Software
Assignee
Bank of America Corporation
OA Round
2 (Final)
73%
Grant Probability
Favorable
3-4
OA Rounds
8m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 73% — above average
73%
Career Allowance Rate
424 granted / 578 resolved
+18.4% vs TC avg
Strong +27% interview lift
Without
With
+26.7%
Interview Lift
resolved cases with interview
Typical timeline
2y 9m
Avg Prosecution
31 currently pending
Career history
602
Total Applications
across all art units

Statute-Specific Performance

§101
11.7%
-28.3% vs TC avg
§103
66.5%
+26.5% vs TC avg
§102
7.7%
-32.3% vs TC avg
§112
7.6%
-32.4% vs TC avg
Black line = Tech Center average estimate • Based on career data from 578 resolved cases

Office Action

§103
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 . This Action is responsive to the Amendment filed on 5/12/2026. Claims 1-20 are pending in the case. Claim Rejections - 35 USC § 103 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claims 1-3, 7, 9-11, and 15, 17-19 are rejected under 35 U.S.C. 103 as being unpatentable over Opedal (US 20250291929 A1) in view of Dasari et al. (US 20260017137, hereinafter Dasari) and Stockert et al. (US 20250217695 A1, hereinafter Stockert). As to independent claim 1, Opedal teaches a system for configuring data using advanced computational models for data analysis and automated processing (computing system 400), the system comprising: a processing device (Fig. 4, processor 402, paragraph 0035); a non-transitory storage device containing instructions when executed by the processing device (a storage medium 426, paragraph 0035), causes the processing device to perform the steps of: train a large language model (LLM), wherein training the LLM comprises using system-specific data (“One or more of the LLMs described herein can be trained or fine-tuned using training data that includes logfiles as input and a desired output, such as instances of vulnerability identified in the logfiles.” Paragraph 0019, last sentence) comprising feed data, process run logs, historical events, code base, existing permissions, and data classification rules (“Examples of the obfuscated log files include, but are not limited to, logs generated based on interactions between a user device and the application, server logs saved in the log storage of the communications network, codebase of the application, or source files of the application.” Paragraph 0028); determine prone data, wherein the prone data comprises a log file comprising sensitive information, and wherein the prone data is determined via a prone module (“In some implementations, the vulnerability detection and mitigation system 105 prompts the LLM to determine contents stored in the first set of obfuscated log files or identify a security issue or a vulnerability in the first set of obfuscated log files… Examples of security and/or vulnerability issues include, but are not limited to, login information, identification information associated with users accessing one or more applications when the logfiles were generated, unique customer numbers, social security numbers, or other personal identifiable information that are identified in the first set of obfuscated log files.” Paragraph 0030); Opedal does not appear to expressly teach the system comprising: receive additional prone data at least substantially similar to the prone data such that the additional prone data causes an error requiring additional processing, wherein the additional prone data comprises a log file comprising additional sensitive information; configure the prone data and the additional prone data using a generative artificial intelligence (GenAI) module, wherein the GenAI module configures the prone data and additional prone data by masking the sensitive information and the additional sensitive information using a masking procedure; and determine the masking procedure via a decentralized autonomous organization (DAO). Dasari teaches receive additional prone data at least substantially similar to the prone data such that the additional prone data causes an error requiring additional processing, wherein the additional prone data comprises a log file comprising additional sensitive information (“During operation 204 of method 200, the error resolution module 102 extracts error related information from the logs 306. If the logs are maintained as secure logs with restricted access, then the error resolution module 102 may identify and mask sensitive data within the secure log” paragraph 0052, Fig. 1-2); configure the prone data using a generative artificial intelligence (GenAI) module (“Various embodiments of the present technology relate to artificial intelligence (AI) based application error detection and resolution.” Paragraph 0016, Fig. 1), wherein the GenAI module configures the prone data by masking the sensitive information using a masking procedure (“During operation 204 of method 200, the error resolution module 102 extracts error related information from the logs 306. If the logs are maintained as secure logs with restricted access, then the error resolution module 102 may identify and mask sensitive data within the secure logs (e.g., remove or redact social security information, dates of birth, social security numbers, etc.).” Paragraph 0052). Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise receive additional prone data at least substantially similar to the prone data such that the additional prone data causes an error requiring additional processing, wherein the additional prone data comprises a log file comprising additional sensitive information; configure the prone data and the additional prone data using a generative artificial intelligence (GenAI) module, wherein the GenAI module configures the prone data and additional prone data by masking the sensitive information and the additional sensitive information using a masking procedure. One would have been motivated to make such a combination to analyze logs in a secure manner -Dasari [0049]. Stockert teaches determine the Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise determine the masking procedure via a decentralized autonomous organization (DAO). One would have been motivated to make such a combination for allowing the DAO community to verify, process on procedures without exposing the underlying confidential information to the public. As to dependent claim 2, Opedal teaches the system of claim 1, Opedal further teaches wherein the GenAI module configures the prone data by: ingesting the system-specific data; understanding, via the prone module, the sensitive data within the prone data via a natural language processing module; and configuring the prone data, the log file, and the sensitive information using masking procedure (“The security and/or vulnerability issues can include, but are not limited to, login information, identification information associated with users accessing one or more applications when the logfiles were generated, and sensitive personal identifiable information such as unique customer numbers and social security numbers. One or more of the LLMs described herein can be trained or fine-tuned using training data that includes logfiles as input and a desired output, such as instances of vulnerability identified in the logfiles.” Paragraph 0019,0026). As to dependent claim 3, Opedal teaches the system of claim 1, Opedal further teaches wherein the masking procedure comprises creating a generalized message, wherein the generalized message configures the prone data by replacing the sensitive information with the generalized message (“After determining that the security and/or vulnerability issues identified in the logfile 225A exists in the logfile 225B, the vulnerability detection and mitigation system 105 can be configured to notify a network node or an administrator within the communications network responsible for storing the logfile 225B or handling the application that generated the logfile 225B.” paragraph 0026). As to dependent claim 7, Opedal teaches the system of claim 1, Opedal does not appear to expressly teach wherein the DAO comprises: executing a smart contract, wherein the smart contract transmits the masking procedure to one or more stakeholders; receiving an approval from the one or more stakeholders, wherein the approval approves the masking procedure; and implementing the masking procedure into a production-level GenAI module. Stockert teaches executing a smart contract, wherein the smart contract transmits the negotiation or execution of a contract. Thus, a smart contract comprises an automated mechanism involving two or more parties, where the parties' agreements are directly written into code and stored and replicated on a quantum temporal blockchain.” Paragraph 0055); receiving an approval from the one or more stakeholders, wherein the approval approves the implementing the Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise wherein the DAO comprises: executing a smart contract, wherein the smart contract transmits the masking procedure to one or more stakeholders; receiving an approval from the one or more stakeholders, wherein the approval approves the masking procedure; and implementing the masking procedure into a production-level GenAI module. One would have been motivated to make such a combination to provide for improving efficiency and minimizing the potential for errors. Claims 9-11, 15, and 17-19 are substantially the same as claims 1-3 and 7 and are therefore rejected under similar rationale as above. Claims 8 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Opedal in view of Dasari et al., Stockert et al. and Goel et al. (US 20260017462 A1, hereinafter Goel). As to dependent claim 8, Opedal teaches the system of claim 1, Opedal does not appear to expressly teach wherein the DAO comprises: executing a smart contract, wherein the smart contract transmits the masking procedure to one or more stakeholders; receiving a rejection from the one or more stakeholders, wherein the rejection rejects the masking procedure; generating one or more reports detailing the rejection of the masking procedure; refining the masking procedure via the LLM to create an updated masking procedure; and configuring, via the GenAI module, the prone data by masking the sensitive data using the updated masking procedure. Stockert teaches executing a smart contract, wherein the smart contract transmits the receiving a rejection from the one or more stakeholders, wherein the rejection rejects the among disparate, anonymous parties, which allows the parties to work together without needing to expose their real-world identities.” Paragraph 0070, this implies that the parties may reject or approve the procedure); generating one or more reports detailing the rejection of the Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise executing a smart contract, wherein the smart contract transmits the masking procedure to one or more stakeholders; receiving a rejection from the one or more stakeholders, wherein the rejection rejects the masking procedure; generating one or more reports detailing the rejection of the masking procedure. One would have been motivated to make such a combination to provide for improving efficiency and minimizing the potential for errors. Goel teaches refining the sanitizing procedure via the LLM to create an updated sanitizing procedure; and configuring, via the GenAI module, the prone data by masking the sensitive data using the updated sanitizing procedure (“When the sanitization system provides the modified prompt to the GAI system, to the extent that the GAI system might store the prompt in a database or use the prompt in a retraining process, the removal or replacement of the sensitive data from the prompt can reduce a likelihood of misuse of sensitive data,” Paragraph 0035). Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise refining the masking procedure via the LLM to create an updated masking procedure; and configuring, via the GenAI module, the prone data by masking the sensitive data using the updated masking procedure. One would have been motivated to make such a combination to reduce wasted resources. Claim 16 is substantially the same as claim 8 and is therefore rejected under similar rationale as above. Claims 4, 6, 12, 14, and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Opedal in view of Dasari et al., Stockert et al. and Nadav (US 20250036809 A1). As to dependent claim 4, Opedal teaches the system of claim 1, Opedal does not appear to expressly teach wherein the masking procedure comprises concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols. Nadav teaches wherein the masking procedure comprises concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols (“The terms mask or masked, as used herein, refers to text (such as a word or a number) that is concealed in some way. In the case of a word that is sensitive information, the word is masked such that the sensitive aspect of the word is eliminated. For example, to mask a word from a string of text, the word can be simply deleted from the string. For instance, the string of text “the cat belongs to John Smith of the United Kingdom” is replaced with “the cat belongs to of the United Kingdom”. In another example of masking, a masked word such as “John” or “Smith” is replaced with one or more characters that hide what the word was, such as “XXXX”.” paragraph 0023). Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise wherein the masking procedure comprises concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols. One would have been motivated to make such a combination for enhancing data security system and preventing data leakage. As to dependent claim 6, Opedal teaches the system of claim 1, Opedal further teaches wherein the masking procedure comprises: analyzing the prone data to determine the sensitive information (“In some implementations, the vulnerability detection and mitigation system 105 prompts the LLM to determine contents stored in the first set of obfuscated log files or identify a security issue or a vulnerability in the first set of obfuscated log files… Examples of security and/or vulnerability issues include, but are not limited to, login information, identification information associated with users accessing one or more applications when the logfiles were generated, unique customer numbers, social security numbers, or other personal identifiable information that are identified in the first set of obfuscated log files.” Paragraph 0030); structuring the prone data (“Examples of security and/or vulnerability issues include, but are not limited to, login information, identification information associated with users accessing one or more applications when the logfiles were generated, unique customer numbers, social security numbers, or other personal identifiable information that are identified in the first set of obfuscated log files.” Paragraph 0030). Opedal does not appear to expressly teach concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols. Nadav teaches concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols (“For example, to mask a word from a string of text, the word can be simply deleted from the string. For instance, the string of text “the cat belongs to John Smith of the United Kingdom” is replaced with “the cat belongs to of the United Kingdom”. In another example of masking, a masked word such as “John” or “Smith” is replaced with one or more characters that hide what the word was, such as “XXXX”.” paragraph 0023). Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise concealing the sensitive information of the prone data by replacing the sensitive information with one or more symbols. One would have been motivated to make such a combination for enhancing data security system and preventing data leakage. Claims 12, 14, and 20 are substantially the same as claims 4 and 6 and are therefore rejected under similar rationale as above. Claims 5 and 13 are rejected under 35 U.S.C. 103 as being unpatentable over Opedal in view of Dasari et al., Stockert et al. and Nainar et al (US 2024/0346180 A1, hereinafter Nainar). As to dependent claim 5, Opedal teaches the system of claim 1, Opedal does not appear to expressly teach wherein the masking procedure comprises transferring the prone data to a secured location, wherein the secured location comprises permission-based access restrictions. Nainar teaches wherein the masking procedure comprises transferring the prone data to a secured location, wherein the secured location comprises permission-based access restrictions (“the service provider computing device 108 is configured to detect sensitive data included within an email communication, store any detected sensitive data in a remote (and secure) memory location at a data store 114 of a data host provider 116, and replace the sensitive data with a reference to the memory location.” Paragraph 0023). Accordingly, it would have been obvious to a person of ordinary skill in the art before the effective filing date of the claimed invention to modify the system of Opedal to comprise wherein the masking procedure comprises transferring the prone data to a secured location, wherein the secured location comprises permission-based access restrictions. One would have been motivated to make such a combination One would have been motivated to make such a combination for enhancing data security system and preventing data leakage. Claim 13 is substantially the same as claim 5 and is therefore rejected under similar rationale as above. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Kissos et al. US 12495057 B1 Contextual anomaly detection in activity logs. 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 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 MAHELET SHIBEROU whose telephone number is (571)270-7493. The examiner can normally be reached Monday-Friday 9:00 AM-5:00 PM Eastern Time. 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, Kieu Vu can be reached at 571-272-4057. 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. /MAHELET SHIBEROU/Primary Examiner, Art Unit 2171
Read full office action

Prosecution Timeline

Aug 05, 2024
Application Filed
Feb 13, 2026
Non-Final Rejection mailed — §103
May 12, 2026
Response Filed
Jun 29, 2026
Final Rejection mailed — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12705077
GENERATION OF VIRTUALIZED SHARED TAB FOR SCREEN SHARING
3y 11m to grant Granted Aug 11, 2026
Patent 12688221
CREATING EXPLAINABLE SUMMARIES OF TEXT DOCUMENTS WITH CONTROLLABLE LEVELS OF DETAIL
2y 10m to grant Granted Jul 21, 2026
Patent 12684040
System and Method for Rich Content Browsing Multitasking on Device Operating Systems with Multitasking Limitations
3y 7m to grant Granted Jul 14, 2026
Patent 12681624
APPLICATION EXTENSIBILITY FOR SMART DEVICE CONTROL
2y 5m to grant Granted Jul 14, 2026
Patent 12681739
FRAMEWORK AGNOSTIC UI TOOLKIT
2y 9m to grant Granted Jul 14, 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
73%
Grant Probability
99%
With Interview (+26.7%)
2y 9m (~8m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 578 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