Prosecution Insights
Last updated: October 27, 2026
Application No. 19/096,729

SYSTEMS AND METHODS FOR PERFORMING DIGITAL AUTHENTICATION

Non-Final OA §102
Filed
Apr 01, 2025
Priority
Apr 30, 2024 — provisional 63/640,840 +1 more
Examiner
DADA, BEEMNET W
Art Unit
Tech Center
Assignee
The Pnc Financial Services Group Inc.
OA Round
1 (Non-Final)
85%
Grant Probability
Favorable
1-2
OA Rounds
1y 5m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 85% — above average
85%
Career Allowance Rate
795 granted / 940 resolved
+24.6% vs TC avg
Strong +18% interview lift
Without
With
+18.4%
Interview Lift
resolved cases with interview
Typical timeline
2y 12m
Avg Prosecution
14 currently pending
Career history
961
Total Applications
across all art units

Statute-Specific Performance

§101
15.6%
-24.4% vs TC avg
§103
30.0%
-10.0% vs TC avg
§102
32.0%
-8.0% vs TC avg
§112
5.2%
-34.8% vs TC avg
Black line = Tech Center average estimate • Based on career data from 940 resolved cases

Office Action

§102
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 . Information Disclosure Statement The information disclosure statement (IDS) submitted on 07/17/2026 and 09/14/2026 have been considered. The submission is in compliance with the provisions of 37 CFR 1.97. Form PTO-1449 is signed and attached hereto. Drawings The drawings filed on April 01, 2025 are accepted. Specification The specification filed April 01, 2025 is accepted. Claim Rejections - 35 USC § 102 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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention. Claims 88-93, 95-104 and 106-110 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Zhu et al. US 2025/0265324 A1 [hereinafter Zhu]. As per claims 88 and 99, Zhu teaches a method for performing digital authentication, the method comprising: receiving a user input for logging into a cloud service from a user device through a login access point on a web-based user interface configured for display on the user device [paragraphs 0146-0156]; sending a request to update the web-based user interface from the login access point to an authentication access point [paragraphs 0034 and 0086]; initiating an authentication integration framework to transmit an authentication request to an authentication server for authenticating the user device [paragraphs 0146-0156 and 0168-0189]; receiving, through the authentication integration framework, a token associated with the cloud service from the authentication server [paragraphs 0146-0156 and 0168-0189]; storing the token as associated with a session of a browser engine through the web-based user interface [paragraphs 0146-0156 and 0168-0189]; redirecting the user device from the authentication access point to a landing interface for the cloud service [paragraphs 0146-0156 and 0168-0189]; and transmitting for display on the user device the landing interface for the cloud service [paragraphs 0146-0156 and 0168-0189]. As per claims 89 and 100, Zhu further teaches the method wherein the web-based user interface is generated according to one of a plurality of web frameworks [paragraphs 0146-0156 and 0168-0189]. As per claims 90 and 101, Zhu further teaches the method wherein the one of the plurality of web frameworks includes a component-based modular framework, a front-end framework, or a JavaScript-based framework [paragraphs 0146-0156 and 0168-0189]. As per claims 91 and 102, Zhu further teaches the method wherein the authentication request includes an authentication option [paragraphs 0146-0156 and 0168-0189]. As per claims 92 and 103, Zhu further teaches the method wherein the authentication option includes at least one of a single-factor authentication, a two-factor authentication, a multi-factor authentication, a fast-factor authentication, a fast identity online authentication, or a one-time password authentication [paragraphs 0146-0156 and 0168-0189]. As per claims 93 and 104, Zhu further teaches the method wherein initiating the authentication integration framework further includes: configuring the authentication integration framework with a plurality of parameters for connecting to the authentication server [paragraphs 0146-0156 and 0168-0189]. As per claims 95 and 106, Zhu further teaches the method further comprising: receiving a logout request through the landing interface for the cloud service, after display of the landing interface for the cloud service; and transmitting for display on the user device the login access point through the web-based user interface [paragraphs 0146-0156 and 0168-0189]. As per claims 96 and 107, Zhu further teaches the method wherein the user input is a first user input; and the method further comprises: receiving a second user input for the cloud service through the session of the browser engine [paragraphs 0146-0156 and 0168-0189]; skipping authenticating the user device according to the token stored in the session of the browser engine [paragraphs 0146-0156 and 0168-0189]; and transmitting for display on the user device the landing interface associated with the cloud service through the web-based user interface [paragraphs 0146-0156 and 0168-0189]. As per claims 97 and 108, Zhu further teaches the method further comprising: clearing the token when the session or the browser engine is closed [paragraphs 0146-0156 and 0168-0189]. As per claims 98 and 109, Zhu further teaches the method wherein the landing interface is generated according to a component-based modular framework, a front-end framework, or a JavaScript-based framework [paragraphs 0146-0156 and 0168-0189]. As per claim 110, Zhu further teaches the system wherein the token associated with the cloud service is generated by the authentication server in response to a determination that the user device is authenticated [paragraphs 0146-0156 and 0168-0189]. Allowable Subject Matter Claims 94 and 105 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to BEEMNET W DADA whose telephone number is (571)272-3847. The examiner can normally be reached Monday-Friday, 9am-5pm. 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, Amir Mehrmanesh can be reached at 571-270-3351. 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. BEEMNET W. DADA Primary Examiner Art Unit 2435 /BEEMNET W DADA/Primary Examiner, Art Unit 2435
Read full office action

Prosecution Timeline

Apr 01, 2025
Application Filed
Aug 01, 2025
Response after Non-Final Action
May 24, 2026
Response after Non-Final Action
Oct 05, 2026
Non-Final Rejection mailed — §102 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12739103
CRYPTOGRAPHIC AGILITY
2y 5m to grant Granted Sep 15, 2026
Patent 12719853
SYSTEMS AND METHODS FOR INDEPENDENTLY SOURCED AUTHENTICATION DURING REMOTE NETWORK SESSIONS
2y 6m to grant Granted Aug 25, 2026
Patent 12705358
TIME-WINDOW BASED MULTI-STAGE SAMPLING
2y 4m to grant Granted Aug 11, 2026
Patent 12699775
ACHIEVING MINIMUM TRUSTWORTHINESS IN DISTRIBUTED WORKLOADS
2y 4m to grant Granted Aug 04, 2026
Patent 12701137
USING IMAGES GENERATED FROM NETWORK PACKETS TO IDENTIFY APPLICATIONS
1y 11m to grant Granted Aug 04, 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
85%
Grant Probability
99%
With Interview (+18.4%)
2y 12m (~1y 5m remaining)
Median Time to Grant
Low
PTA Risk
Based on 940 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