Prosecution Insights
Last updated: November 21, 2026
Application No. 19/340,091

Intelligent Generation Of Visualizations Of Data Metrics

Non-Final OA §102§DOUBLEPATENT
Filed
Sep 25, 2025
Priority
Nov 09, 2023 — continuation of 12/450,303
Examiner
ROBINSON, GRETA LEE
Art Unit
2163
Tech Center
2100 — Computer Architecture & Software
Assignee
ORACLE INTERNATIONAL Corporation
OA Round
1 (Non-Final)
80%
Grant Probability
Favorable
1-2
OA Rounds
1y 10m
Est. Remaining
98%
With Interview

Examiner Intelligence

Grants 80% — above average
80%
Career Allowance Rate
803 granted / 997 resolved
+25.5% vs TC avg
Strong +17% interview lift
Without
With
+17.1%
Interview Lift
resolved cases with interview
Typical timeline
3y 0m
Avg Prosecution
15 currently pending
Career history
1024
Total Applications
across all art units

Statute-Specific Performance

§101
6.6%
-33.4% vs TC avg
§103
39.0%
-1.0% vs TC avg
§102
12.5%
-27.5% vs TC avg
§112
32.3%
-7.7% vs TC avg
Black line = Tech Center average estimate • Based on career data from 997 resolved cases

Office Action

§102 §DOUBLEPATENT
DETAILED ACTION Claims 1-20 are pending in the present application. 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 . 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 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No.19/340076 (reference application). Although the claims at issue are not identical, they are not patentably distinct from each other because it is well settled that omission of elements and their functioning is an obvious expedient if the remaining elements perform the same function as before. See In re Karlson, 136 USPQ 184 (CCPA 1963). This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented. 19/340,076 1. One or more non-transitory computer-readable media comprising instructions that, when executed by one or more hardware processors, cause performance of operations comprising: obtaining one or more attributes of a data metric that is to be visualized in a user dashboard; based, at least in part, on the one or more attributes of the data metric, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard. 2. The one or more non-transitory computer-readable media of claim 1, wherein determining the target visualization type for the data metric comprises: based, at least in part, on the one or more attributes of the data metric, determining one or more candidate visualization types for the data metric; presenting the one or more candidate visualization types for the data metric as a set of recommended visualization types for the data metric, the set of recommended visualization types comprising the target visualization type; and receiving user input selecting the target visualization type from the set of recommended visualization types. 3. The one or more non-transitory computer-readable media of claim 1: wherein the data metric is a particular type of data metric; and wherein determining the target visualization type for the data metric is based, at least in part, on a frequency that the particular type of data metric is visualized in accordance with the target visualization type. 4. The one or more non-transitory computer-readable media of claim 1: wherein the data metric is a particular type of data metric; and wherein determining the target visualization type for the data metric is based, at least in part, on how recently the particular type of data metric has been visualized in accordance with the target visualization type. 5. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: obtaining one or more user characteristics of a user of the user dashboard, wherein determining the target visualization type for the data metric is further based on the one or more user characteristics of the user. 6. The one or more non-transitory computer-readable media of claim 1, wherein determining the target visualization type for the data metric is based, at least in part, on a size of the values associated with the data metric. 7. The one or more non-transitory computer-readable media of claim 1, wherein determining the target visualization type for the data metric comprises: obtaining sets of training data, wherein a first set of training data of the sets of training data comprises: a set of one or more attributes of a particular data metric; and a set of one or more visualization types that are relevant to the particular data metric; training a machine learning model based on the sets of training data; and applying the machine learning model to the one or more attributes of the data metric to determine the target visualization type for the data metric. 8. The one or more non-transitory computer-readable media of claim 7, wherein the operations further comprise: receiving feedback regarding the visualization of the data metric; and updating the machine learning model based on the feedback. 9. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: obtaining one or more user characteristics of a user of the user dashboard; and based, at least in part, on the one or more user characteristics of the user, determining that the data metric is to be visualized in the user dashboard. 10. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: prior to generating the visualization of the data metric: generating a multi-dimensional representation of a data set comprising the values associated with the data metric; based, at least in part, on the multi-dimensional representation of the data set, generating a query for the values associated with the data metric; and subsequent to generating the query, receiving the values associated with the data metric. 11. A method comprising: obtaining one or more attributes of a data metric that is to be visualized in a user dashboard; based, at least in part, on the one or more attributes of the data metric, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard, wherein the method is performed by at least one device including a hardware processor. 12. The method of claim 11, wherein determining the target visualization type for the data metric comprises: based, at least in part, on the one or more attributes of the data metric, determining one or more candidate visualization types for the data metric; presenting the one or more candidate visualization types for the data metric as a set of recommended visualization types for the data metric, the set of recommended visualization types comprising the target visualization type; and receiving user input selecting the target visualization type from the set of recommended visualization types. 13. The method of claim 11: wherein the data metric is a particular type of data metric; and wherein determining the target visualization type for the data metric is based, at least in part, on a frequency that the particular type of data metric is visualized in accordance with the target visualization type. 14. The method of claim 11: wherein the data metric is a particular type of data metric; and wherein determining the target visualization type for the data metric is based, at least in part, on how recently the particular type of data metric has been visualized in accordance with the target visualization type. 15. The method of claim 11, further comprising: obtaining one or more user characteristics of a user of the user dashboard, wherein determining the target visualization type for the data metric is further based on the one or more user characteristics of the user. 16. The method of claim 11, wherein determining the target visualization type for the data metric is based, at least in part, on a size of the values associated with the data metric. 17. The method of claim 11, wherein determining the target visualization type for the data metric comprises: obtaining sets of training data, wherein a first set of training data of the sets of training data comprises: a set of one or more attributes of a particular data metric; and a set of one or more visualization types that are relevant to the particular data metric; training a machine learning model based on the sets of training data; and applying the machine learning model to the one or more attributes of the data metric to determine the target visualization type for the data metric. 18. The method of claim 11, further comprising: obtaining one or more user characteristics of a user of the user dashboard; and based, at least in part, on the one or more user characteristics of the user, determining that the data metric is to be visualized in the user dashboard. 19. The method of claim 11, further comprising: prior to generating the visualization of the data metric: generating a multi-dimensional representation of a data set comprising the values associated with the data metric; based, at least in part, on the multi-dimensional representation of the data set, generating a query for the values associated with the data metric; and subsequent to generating the query, receiving the values associated with the data metric. 20. A system comprising: one or more hardware processors; one or more non-transitory computer-readable media; and program instructions stored on the one or more non-transitory computer-readable media which, when executed by the one or more hardware processors, cause the system to: obtain one or more attributes of a data metric that is to be visualized in a user dashboard; based, at least in part, on the one or more attributes of the data metric, determine a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generate a visualization of the data metric in accordance with the target visualization type for the data metric; and present the visualization of the data metric in the user dashboard. 19/340,091 1. One or more non-transitory computer-readable media comprising instructions that, when executed by one or more hardware processors, cause performance of operations comprising: identifying a data metric that is to be visualized in a user dashboard of a user; obtaining one or more user characteristics of the user; based, at least in part, on the one or more user characteristics of the user, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard. 2. The one or more non-transitory computer-readable media of claim 1, wherein determining the target visualization type for the data metric comprises: based, at least in part, on the one or more user characteristics of the user, determining one or more candidate visualization types for the data metric; presenting the one or more candidate visualization types for the data metric as a set of recommended visualization types for the data metric, the set of recommended visualization types comprising the target visualization type; and receiving user input selecting the target visualization type from the set of recommended visualization types. 3. The one or more non-transitory computer-readable media of claim 1: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how frequently the target visualization type has been used to visualize data metrics in user dashboards of users corresponding to the particular user type. 4. The one or more non-transitory computer-readable media of claim 1: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how recently the target visualization type has been used to visualize one or more data metrics in one or more user dashboards of one or more users corresponding to the particular user type. 5. The one or more non-transitory computer-readable media of claim 1: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how frequently users of the particular user type interact with visualizations of data metrics that are visualized in accordance with the target visualization type. 6. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: prior to determining the target visualization type for the data metric: obtaining one or more attributes of the data metric that is to be visualized in the user dashboard of the user, wherein determining the target visualization type for the data metric is further based on the one or more attributes of the data metric. 7. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: obtaining sets of training data, wherein a first set of training data of the sets of training data comprises: a set of one or more user characteristics of a particular user; and a set of one or more data metrics that are relevant to the particular user; training a machine learning model based on the sets of training data; and applying the machine learning model to the one or more user characteristics of the user to determine the target visualization type for the data metric. 8. The one or more non-transitory computer-readable media of claim 7, wherein the operations further comprise: receiving feedback regarding the visualization of the data metric; and updating the machine learning model based on the feedback. 9. The one or more non-transitory computer-readable media of claim 1, wherein identifying the data metric that is to be visualized in the user dashboard of the user comprises: determining that the data metric is to be visualized in the user dashboard based, at least in part, on the one or more user characteristics of the user. 10. The one or more non-transitory computer-readable media of claim 1, wherein the operations further comprise: prior to generating the visualization of the data metric: generating a multi-dimensional representation of a data set comprising the values associated with the data metric; based, at least in part, on the multi-dimensional representation of the data set, generating a query for the values associated with the data metric; and subsequent to generating the query, receiving the values associated with the data metric. 11. A method comprising: identifying a data metric that is to be visualized in a user dashboard of a user; obtaining one or more user characteristics of the user; based, at least in part, on the one or more user characteristics of the user, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard, wherein the method is performed by at least one device including a hardware processor. 12. The method of claim 11, wherein determining the target visualization type for the data metric comprises: based, at least in part, on the one or more user characteristics of the user, determining one or more candidate visualization types for the data metric; presenting the one or more candidate visualization types for the data metric as a set of recommended visualization types for the data metric, the set of recommended visualization types comprising the target visualization type; and receiving user input selecting the target visualization type from the set of recommended visualization types. 13. The method of claim 11: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how frequently the target visualization type has been used to visualize data metrics in user dashboards of users corresponding to the particular user type. 14. The method of claim 11: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how recently the target visualization type has been used to visualize one or more data metrics in one or more user dashboards of one or more users corresponding to the particular user type. 15. The method of claim 11: wherein the one or more user characteristics of the user comprises a particular user type of the user; and wherein determining the target visualization type for the data metric is based, at least in part, on how frequently users of the particular user type interact with visualizations of data metrics that are visualized in accordance with the target visualization type. 16. The method of claim 11, further comprising: prior to determining the target visualization type for the data metric: obtaining one or more attributes of the data metric that is to be visualized in the user dashboard of the user, wherein determining the target visualization type for the data metric is further based on the one or more attributes of the data metric. 17. The method of claim 11, wherein determining the target visualization type for the data metric comprises: obtaining sets of training data, wherein a first set of training data of the sets of training data comprises: a set of one or more user characteristics of a particular user; and a set of one or more data metrics that are relevant to the particular user; training a machine learning model based on the sets of training data; and applying the machine learning model to the one or more user characteristics of the user to determine the target visualization type for the data metric. 18. The method of claim 11, wherein identifying the data metric that is to be visualized in the user dashboard of the user comprises: determining that the data metric is to be visualized in the user dashboard based, at least in part, on the one or more user characteristics of the user. 19. The method of claim 11, further comprising: prior to generating the visualization of the data metric: generating a multi-dimensional representation of a data set comprising the values associated with the data metric; based, at least in part, on the multi-dimensional representation of the data set, generating a query for the values associated with the data metric; and subsequent to generating the query, receiving the values associated with the data metric. 20. A system comprising: one or more hardware processors; one or more non-transitory computer-readable media; and program instructions stored on the one or more non-transitory computer-readable media which, when executed by the one or more hardware processors, cause the system to: identify a data metric that is to be visualized in a user dashboard of a user; obtain one or more user characteristics of the user; based, at least in part, on the one or more user characteristics of the user, determine a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generate a visualization of the data metric in accordance with the target visualization type for the data metric; and present the visualization of the data metric in the user dashboard. 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 1 and 11 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1 and 11 of U.S. Patent No. 12,450,303 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because it is well settled that omission of elements is an obvious expedient if the remaining elements perform the same function as before. See In re Karlson, 136 USPQ 184 (CCPA 1963). 19/340,091 1. One or more non-transitory computer-readable media comprising instructions that, when executed by one or more hardware processors, cause performance of operations comprising: identifying a data metric that is to be visualized in a user dashboard of a user; obtaining one or more user characteristics of the user; based, at least in part, on the one or more user characteristics of the user, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard. 11. A method comprising: identifying a data metric that is to be visualized in a user dashboard of a user; obtaining one or more user characteristics of the user; based, at least in part, on the one or more user characteristics of the user, determining a target visualization type for the data metric; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric; and presenting the visualization of the data metric in the user dashboard, wherein the method is performed by at least one device including a hardware processor. US Patent 12,450,303 B2 1. One or more non-transitory computer-readable media comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising: obtaining a set of characteristics of a target user, the set of characteristics comprising one or more characteristics of the target user; determining a set of candidate data metrics that are relevant to the target user based on the set of characteristics of the target user, the set of candidate data metrics comprising one or more data metrics; presenting the set of candidate data metrics as a set of recommended data metrics for generating a visualization in a user dashboard; receiving user input selecting a particular data metric of the set of recommended data metrics; generating the visualization based on a set of values associated with the particular data metric; and presenting the visualization in the user dashboard. 11. A method comprising: obtaining a set of characteristics of a target user, the set of characteristics comprising one or more characteristics of the target user; determining a set of candidate data metrics that are relevant to the target user based on the set of characteristics of the target user, the set of candidate data metrics comprising one or more data metrics; presenting the set of candidate data metrics as a set of recommended data metrics for generating a visualization in a user dashboard; receiving user input selecting a particular data metric of the set of recommended data metrics; generating the visualization based on a set of values associated with the particular data metric; and presenting the visualization in the user dashboard wherein the method is performed by at least one device including a hardware processor. 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. Claim(s) 1, 11, and 20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Beers US Patent Application Publication No. 2022/0035831 A1. Regarding claim 1, Beers teaches the following: One or more non-transitory computer-readable media comprising instructions that, when executed by one or more hardware processors, [note: figure 4 (418) Dashboards; paragraph 0081, “non-transitory processor-readable removable storage device 236”; paragraphs 0082-0083; paragraph 0086, embodiments may include one or more hardware processors ] cause performance of operations comprising: identifying a data metric that is to be visualized in a user dashboard of a user [note: paragraph 0027 in some cases, the type of metrics that are available may depend on the visualization being analyzed; paragraph 0053, the web-enabled client computer is configured to send and receive responses over the web; paragraph 0107, data models may include fields or attributes in data sources;]; obtaining one or more characteristics of a user [note: paragraph 0027 in some cases, the type of metrics that are available may depend on the visualization being analyzed; paragraph 0053, the web-enabled client computer is configured to send and receive responses over the web; paragraph 0107, data models may include fields or attributes in data sources; paragraph 0108-0113, visualization engine 404 may be employed to transform and may data sources into data models, determine the layout, styling, interactivity that may be displayed, metric values populate visualizations , the system may implement rules that support different types of visualizations ]; based, at least in part, on the one or more user characteristics of the user, determining a target visualization type for the data metric [note: paragraphs 0107-0113]; based, at least in part, on values associated with the data metric, generating a visualization of the data metric in accordance with the target visualization type for the data metric [note: paragraph 0124, user interface 500 may be considered a dashboard ]; and presenting the visualization of the data metric in the user dashboard [note: paragraph 0124, dashboard; figure 8 (802) dashboard; also figure 4 (418) Dashboard ]. The limitations of claims 11 and 20 parallel the limitations of claim 1; therefore, they are rejected under the same rationale. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Note attached form PTO-892. Any inquiry concerning this communication or earlier communications from the examiner should be directed to GRETA ROBINSON whose telephone number is (571)272-4118. The examiner can normally be reached Mon.-Fri. 9:30AM-6:00PM. 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, Hassan Mahmoudi can be reached at 571-272-4078. 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. /GRETA L ROBINSON/Primary Examiner, Art Unit 2163
Read full office action

Prosecution Timeline

Sep 25, 2025
Application Filed
Oct 24, 2025
Response after Non-Final Action
Nov 09, 2026
Non-Final Rejection mailed — §102, §DOUBLEPATENT (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12801952
AUTOMATED MACHINE LEARNING TO GENERATE RECOMMENDATIONS FOR WEBSITES OR APPLICATIONS
1y 4m to grant Granted Nov 17, 2026
Patent 12792612
SYSTEMS AND METHODS FOR ACTIVITY-RELATED QUERY-RESPONSE PROCESSING
2y 2m to grant Granted Nov 10, 2026
Patent 12783545
System For Live-Migration and Automated Recovery of Applications in a Distributed System
2y 8m to grant Granted Nov 03, 2026
Patent 12775720
AUTO GENERATING BUILD TIME POLICIES FROM RUN TIME POLICIES FOR SHIFT LEFT SECURITY
1y 8m to grant Granted Oct 27, 2026
Patent 12763176
VIEWING PROCEDURE MANAGEMENT SYSTEM AND VIEWING PROCEDURE MANAGEMENT METHOD
2y 6m to grant Granted Oct 13, 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

1-2
Expected OA Rounds
80%
Grant Probability
98%
With Interview (+17.1%)
3y 0m (~1y 10m remaining)
Median Time to Grant
Low
PTA Risk
Based on 997 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