Prosecution Insights
Last updated: November 08, 2026
Application No. 18/435,875

DISCOVERING VALUES FOR METRICS OF ENTITIES FROM NON-STANDARDIZED DATASETS

Non-Final OA §101§102§103
Filed
Feb 07, 2024
Priority
Feb 07, 2023 — provisional 63/483,586
Examiner
KANG, IRENE S
Art Unit
3696
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Forge Global Inc.
OA Round
1 (Non-Final)
16%
Grant Probability
At Risk
1-2
OA Rounds
2y 1m
Est. Remaining
43%
With Interview

Examiner Intelligence

Grants only 16% of cases
16%
Career Allowance Rate
37 granted / 225 resolved
-35.6% vs TC avg
Strong +26% interview lift
Without
With
+26.2%
Interview Lift
resolved cases with interview
Typical timeline
4y 11m
Avg Prosecution
11 currently pending
Career history
245
Total Applications
across all art units

Statute-Specific Performance

§101
36.7%
-3.3% vs TC avg
§103
34.7%
-5.3% vs TC avg
§102
16.2%
-23.8% vs TC avg
§112
9.2%
-30.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 225 resolved cases

Office Action

§101 §102 §103
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 . DETAILED ACTION The following is a Non-Final Office Action in response to communications received June 18, 2026. Applicant’s election without traverse of Claims 5-24 in the reply filed on June 18, 2026 is acknowledged. Claims 1-4 have been withdrawn. Claims 5-24 remain pending and examined. Drawings The drawings are objected to because Figures 1-6 contain grayscale features. Corrected drawing sheets in compliance with 37 CFR 1.121(d) are required in reply to the Office action to avoid abandonment of the application. Any amended replacement drawing sheet should include all of the figures appearing on the immediate prior version of the sheet, even if only one figure is being amended. The figure or figure number of an amended drawing should not be labeled as “amended.” If a drawing figure is to be canceled, the appropriate figure must be removed from the replacement sheet, and where necessary, the remaining figures must be renumbered and appropriate changes made to the brief description of the several views of the drawings for consistency. Additional replacement sheets may be necessary to show the renumbering of the remaining figures. Each drawing sheet submitted after the filing date of an application must be labeled in the top margin as either “Replacement Sheet” or “New Sheet” pursuant to 37 CFR 1.121(d). If the changes are not accepted by the examiner, the applicant will be notified and informed of any required corrective action in the next Office action. The objection to the drawings will not be held in abeyance. 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 5-24 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. (Step 1) The claims recite a method and product. For the purposes of this analysis, representative claim 5 is addressed. (Step 2A, prong 1) Abstract ideas are in bold below, and represents certain methods of organizing human activity, as a method of predicting an equity metric of a target entity. Predicting an equity metric of a target entity is akin to certain methods of organizing human activity. A method for predicting an equity metric of a target entity, the method comprising: configuring a list to include a particular key for a fund portfolio issued by a particular management service of equity metrics for two types of entities, wherein the two types of entities include a public entity and a non-public entity; selecting the particular key for the particular fund portfolio to include in a query, wherein the query is configured for input to a repository to search for reports matching the particular key; monitoring the repository based on the query for a particular report generated by the particular management service having a key matching the particular key, wherein the repository is configured to store multiple and distinct reports that were communicated over one or more computer networks from servers of the multiple management services, wherein each report includes distinct value per quantity metrics for respective public entities, and wherein each report includes equity metrics data for non-public entities but precludes a public value per quantity metrics for non-public entities; retrieving a particular report for the particular fund portfolio having a timestamp subsequent to other reports stored at the repository for the fund portfolio; populating a data table with equity metrics data of the non-public entities extracted from the particular report, wherein the data table includes additional data for the non-public entities aggregated from additional reports for the particular fund portfolio and additional fund portfolios; discovering target data of a target non-public entity in the data table based on fuzzy logic that matches similar but not identical entries indicative of the target non-public entity; clearing security features from the target data of the target non-public entity in the data table; predicting a value per quantity metric for the target non-public entity based on the target data of the target non-public entity having the security features cleared; and causing an electronic device to present an actionable control element in association with the predicted value per quantity metric for the target non-public entity, wherein execution of the actionable control element causes communication of a message configured to initiate a transaction for one or more equity units of the target non- public entity at the predicted value per quantity metric. (Step 2A prong 2) The additional elements are considered as follows: “repository is configured to store multiple and distinct reports” This is merely “apply it” this sever is claimed at a high level of generality, it receives the information, performs the abstract idea, and outputs the results. “reports that were communicated over one or more computer networks from servers of the multiple management services”. This is merely “apply it” these computer networks and servers are claimed at a high level of generality, it receives the information, performs the abstract idea, and outputs the results. “data table”. This is an extra solution activity, akin to data gathering and storing. “electronic device to present an actionable control element” This is merely “apply it” this electronic device is claimed at a high level of generality, it receives the information, performs the abstract idea, and outputs the results. “actionable control element causes communication of a message configured to initiate a transaction” This is an extra solution activity, akin to data gathering and data transmitting. (Step 2B) The claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration into a practical application, the additional elements amount to no more than mere instructions to apply the abstract idea of using generic computer components. The claim elements when considered separately and in an ordered combination, do not add significantly more than predicting an equity metric of a target entity, over a generic computer network with generic computing elements, and generic hardware. The additional elements do not include an improvement to another technology or technical field, an improvement to the functioning of the computer itself, or meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment. Analysis of dependent claims 6-20, 22, and 23 recited additional details which only further narrow the abstract idea and do not add any additional features, alone or in combination, that would provide a practical application or provide significantly more. Claim Rejections - 35 USC § 102 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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claims 5-24 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by the patent by Lipke et al. (Patent No.: US 11,410,242 B1). As to Claim 5, Lipke teaches a method for predicting an equity metric of a target entity (see Col. 11, lines 49-50), the method comprising: configuring a list to include a particular key for a fund portfolio issued by a particular management service of equity metrics for two types of entities, wherein the two types of entities include a public entity and a non-public entity (see Col. 11, lines 58-60 – “ In some configurations, the analytics server may not display the proprietary fund portfolio information inputted by the administrator (step 210). As a result, when users who do not have permission to view such proprietary information log in the web-based application, they may only see an overall valuation of the fund without being able to view any information associated with the underlying private entities.”; and Col. 12, lines 43-45 – “the analytics server may provide a valuation for all private entities (within the list of ten private entities) that fall within “technology” or “manufacturing” categories. By unmasking the valuation of different categories of various private entities, the analytics server may provide better insights to users without necessarily displaying individual valuation of the private entities.”); selecting the particular key for the particular fund portfolio to include in a query, wherein the query is configured for input to a repository to search for reports matching the particular key (see Col. 17, lines 27-30 – “The dataset may include two separate sets of data comprising different data points. The first set of data points may represent an independent attribute/variable and the second set of data points may represent another attribute that is dependent upon the independent attribute. The analytics server may use this dataset to generate and/or train an AI model.”); monitoring the repository based on the query for a particular report generated by the particular management service having a key matching the particular key, wherein the repository is configured to store multiple and distinct reports that were communicated over one or more computer networks from servers of the multiple management services, wherein each report includes distinct value per quantity metrics for respective public entities, and wherein each report includes equity metrics data for non-public entities but precludes a public value per quantity metrics for non-public entities (see Col. 7, lines 12-17 – “The transaction data may generally refer to information regarding the fund' portfolio and may include data associated with one or more private entities within the fund's portfolio, such as a proportion of the fund associated with each private entity, number of shares purchased from each private entity, price per share for each private entity, a value of each private entity estimated by an administrator of the fund.”; Col. 8, lines 32-35 – “The analytics server may generate a dataset comprising various data records where each data record corresponds to an attribute (inputted by the administrator or calculated by the analytics server) of the fund.” & lines 45-49 – “the analytics server may generate a dataset corresponding to the attributes illustrated in table 1. The analytics server may also store the dataset in an internal (e.g., local) or external electronic data repository.”; and Col. 11, lines 7-10 – “In some other embodiments, the analytics server may monitor the identified comparable public entities and adjust the value of the private entity accordingly.”); retrieving a particular report for the particular fund portfolio having a timestamp subsequent to other reports stored at the repository for the fund portfolio (see Col. 8, lines 37-39 – “The analytics server may also store the dataset in an internal (e.g., local) or external electronic data repository.”; and Col. 10, lines 20-29 – “the analytics server may continuously retrieve financial transaction data of the identified comparable public entities in real time. The analytics server may retrieve the dataset including the list of all identified comparable public entities associated with the fund. Subsequently, the analytics server may retrieve financial transaction data associated with the identified comparable public entities from various data sources. For instance, the analytics server may continuously scan one or more electronic data repositories to retrieve a real time stock price of each comparable public entity.”); populating a data table with equity metrics data of the non-public entities extracted from the particular report, wherein the data table includes additional data for the non-public entities aggregated from additional reports for the particular fund portfolio and additional fund portfolios (see Col. 8, lines 32-37 – “The analytics server may generate a dataset comprising various data records where each data record corresponds to an attribute (inputted by the administrator or calculated by the analytics server) of the fund. For instance, the analytics server may generate a dataset corresponding to the attributes illustrated in table 1. “; and Col. 12, lines 7-9 – “the analytics server may aggregate the valuations for multiple private entities within a closed end fund.”); discovering target data of a target non-public entity in the data table based on fuzzy logic that matches similar but not identical entries indicative of the target non-public entity (see Col. 8, lines 35-37 – “the analytics server may generate a dataset corresponding to the attributes illustrated in table 1. “; and Col. 10, lines 59-62 – “In some embodiments, the analytics server may consider data retrieved in step 230 (e.g., values of each identified comparable public entity) to determine a value for each private entity within the fund.”); clearing security features from the target data of the target non-public entity in the data table (see Col. 5, lines 40-44 – “an administrator may input various public or nonpublic data into a graphical user interface displayed on the computing device 140a where the analytics server 110a may use the inputted data to valuate a portfolio. In some embodiments, the analytics server 110a may utilize the application programming interface (API) 140d to monitor market data within the electronic data sources 140.”); predicting a value per quantity metric for the target non-public entity based on the target data of the target non-public entity having the security features cleared (see Col. 11, lines 49-50 – “the analytics server may calculate a new value for the funds based on the new predicted valuations of the private entities within the funds.”); and causing an electronic device to present an actionable control element in association with the predicted value per quantity metric for the target non-public entity, wherein execution of the actionable control element causes communication of a message configured to initiate a transaction for one or more equity units of the target non- public entity at the predicted value per quantity metric (see Col. 8, lines 40-49 – “the analytics server may execute a set of artificial intelligence models to identify a plurality of comparable public entities to each private entity within the fund. The analytics server may execute the set of AI models to identify one or more comparable public entities. As discussed below, the analytics server may use publicly available data (e.g., financial data associated with publicly traded companies, trading data) to identify the comparable public entities and to predict a value for each private entity within the fund.”; and Col. 11, lines 46-51 – “the analytics server may display the value of the fund based on the valuation of each private entity where the identity of the private entities are anonymized. As described above, the analytics server may calculate a new value for the funds based on the new predicted valuations of the private entities within the funds.”). As to Claim 6, Lipke teaches the method of claim 5, wherein configuring the list to include the particular key comprises: selecting the particular key for the target non-public entity of interest (see Col. 11, lines 7-10); collecting keys for one or more fund portfolios including equity data for the target non-public entity of interest, wherein a script is executed to navigate between websites of management services that host the one or more fund portfolios (see Col. 5, lines1-2, 54-57, and 64-65; and Col. 9, lines 3-5); comparing the collected keys with keys stored in a current list configured to monitor fund portfolios (see Col. 5, lines 64-65); and adding the collected keys to the list of keys to monitor for reports for funds of interest (see Col. 11, lines 58-60; and Col. 12, lines 43-45). As to Claim 7, Lipke teaches the method of claim 5 further comprising: recursively selecting a next key on the list of keys to monitor a next report for a next fund portfolio (see Col. 10, lines 14-15; and Col. 11, lines 7-10). As to Claim 8, Lipke teaches the method of claim 5: wherein the equity metrics relate to equity shares of a public company or a non-public company, wherein the equity metrics for any public company are public, and wherein the equity metrics for any non-public company are private (see Col. 6, lines 46-55; Col. 8, lines 40-44; and Col. 23, lines 60-61). As to Claim 9, Lipke teaches the method of claim 5: wherein the equity metrics relate to equity shares of a public entity or a non-public entity (see Col 23, lines 60-61). As to Claim 10, Lipke teaches the method of claim 5, wherein selecting the particular key to monitor the repository comprises: configuring a query to include one or more keys to search the repository for one or more reports generated by one or more management services (see Col. 5, lines 54-57; Col. 9, lines 3-5; Col. 11, lines 58-60; and Col. 12, lines 43-45). As to Claim 11, Lipke teaches the method of claim 5: wherein reports are communicated over the one or more computer networks from the multiple management services to the repository on a periodic basis, and wherein only some of the reports communicated over the one or more computer networks are released publicly (see Col. 8, lines 32-39; and Col. 10, lines 20-29). As to Claim 12, Lipke teaches the method of claim 5, wherein multiple reports each include total equity values for the target non-public entity held by management services, and wherein predicting the value per quantity metric for the target non-public entity (see Col. 8, lines 32-37; and Col. 11, lines 49-50) comprises: processing the equity metrics data of the target non-public entity with a machine-learned engine that is generated and trained based on reports including data of non-public entities (see Col. 9, lines 17-19); and outputting the predicted value per quantity metric of the target non-public entity as an output of the machine-learned engine (see Col. 11, lines 49-53)). As to Claim 13, Lipke teaches the method of claim 5, wherein predicting the value per quantity metric for the target non-public entity comprises: determining a total value held in a fund portfolio for the target non-public entity; and predicting a total unit value for the target non-public entity held in the fund portfolio, wherein the predicted value per quantity metric is estimated by dividing the total value by the total unit value (see Col. Lines 36-45). As to Claim 14, Lipke teaches the method of claim 5, wherein retrieving the particular report comprises: comparing timestamps of multiple reports for the particular fund portfolio relative to a current time; and identifying, based on the comparison, a most recent report as the particular report for the particular fund portfolio (see Col. 6, lines 5-10; and Col. 10, lines 27-29). As to Claim 16, Lipke teaches the method of claim 5, wherein the data table includes data for the public entities aggregated from reports in addition to the data from the non-public entities (see Col. 7, lines 12-17). As to Claim 17, Lipke teaches the method of claim 5, wherein discovering the target data of the target non-public entity based on fuzzy logic comprises: matching text in the data table based on the particular key, wherein the particular key is for the particular non-public entity (see Col. 8, lines 35-37; Col. 10, lines 58-62; and Col. 14, lines 35-37). As to Claim 18, Lipke teaches the method of claim 5, wherein clearing the security features comprises: performing text and pattern recognition to determine a security type and remove unnecessary information from the target data of the target non-public entity (see Col. 5, lines 54-57 & 62-64; and Col. 9, lines 3-13). As to Claim 19, Lipke teaches the method of claim 5 further comprises: derive additional analytics that provide insights of the target non-public entity (see Col. 9, lines 20-22). As to Claim 20, Lipke teaches the method of claim 5, wherein discovering the target data of the target non-public entity in the data table based on fuzzy logic comprises: comparing a key for the target non-public entity to keys in the data table (see Col. 8, lines 35-37; Col. 9, lines 16-19; and Col. 10, lines 50-62). Claim 21 is the non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor of a system, cause the system to perform the method of Claim 5 and is rejected under the same reasoning as Claim 5. Claim 22 is the non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor of a system, cause the system to perform the method of Claims 6 & 7 and is rejected under the same reasoning as Claims 6 & 7. Claim 23 is the non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor of a system, cause the system to perform the method of Claim 5 and is rejected under the same reasoning as Claim 5. Claim 24 is the server system comprising: at least one hardware processor; and at least one non-transitory memory storing instructions, which, when executed by the at least one hardware processor, cause the system to perform the method of Claim 5 and is rejected under the same reasoning as Claim 5. 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. Claim 15 is/are rejected under 35 U.S.C. 103 as being unpatentable over the patent by Samer M. Lipke (Patent No.: US 11,410,242 B1) in view of the publication by Hertz et al. (Publication No.: US 2019/0354544 A1). As to Claim 15, although Lipke substantially teaches the method of claim 15, it does not explicitly teach wherein populating the data table with data of the non-public entities extracted from the particular report comprises: generating an xml file; and populating the xml file with entries for the data of the non-public entities. Hertz does teach wherein populating the data table with data of the non-public entities extracted from the particular report comprises: generating an xml file; and populating the xml file with entries for the data of the non-public entities (see ¶[0078]). It would have been obvious to one of ordinary skill in the art at the time of filing to modify the invention of Lipke to include wherein populating the data table with data of the non-public entities extracted from the particular report comprises: generating an xml file; and populating the xml file with entries for the data of the non-public entities as taught by Hertz in order to provide and generate a contingency table to record and determine associations. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to IRENE S KANG whose telephone number is (571)270-3611. The examiner can normally be reached on Monday through Friday between M-F 10am-2pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Matt Gart may be reached at (571)-273-3955. 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. /IRENE KANG/ Examiner, Art Unit 3695 9/29/2026 /MATTHEW S GART/Supervisory Patent Examiner, Art Unit 3696
Read full office action

Prosecution Timeline

Feb 07, 2024
Application Filed
Oct 01, 2026
Non-Final Rejection mailed — §101, §102, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12586131
METHOD AND SYSTEM FOR COVARIANCE MATRIX ESTIMATION
4y 5m to grant Granted Mar 24, 2026
Patent 12555162
EVENT TRIGGERED TRADING
2y 4m to grant Granted Feb 17, 2026
Patent 12469018
SPLIT ATM BOOTH AND METHOD OF PERFORMING BANKING TRANSACTIONS THEREIN
11y 9m to grant Granted Nov 11, 2025
Patent 12423701
TRANSACTION PROCESSING SYSTEM AND TRANSACTION PROCESSING METHOD
2y 2m to grant Granted Sep 23, 2025
Patent 12288203
Systems and Methods for an Electronic Wallet Payment Tool
9y 0m to grant Granted Apr 29, 2025
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

1-2
Expected OA Rounds
16%
Grant Probability
43%
With Interview (+26.2%)
4y 11m (~2y 1m remaining)
Median Time to Grant
Low
PTA Risk
Based on 225 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