Prosecution Insights
Last updated: November 12, 2026
Application No. 19/098,166

SYSTEMS AND METHODS FOR DETERRING BOT ACCESS OF COMPUTER RESOURCE

Non-Final OA §101§103§112
Filed
Apr 02, 2025
Priority
Feb 14, 2023 — provisional 63/484,932 +1 more
Examiner
ZHOU, YINGYING
Art Unit
3697
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Axs Group LLC
OA Round
3 (Non-Final)
48%
Grant Probability
Moderate
3-4
OA Rounds
94%
With Interview

Examiner Intelligence

Grants 48% of resolved cases
48%
Career Allowance Rate
94 granted / 195 resolved
-3.8% vs TC avg
Strong +46% interview lift
Without
With
+45.8%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
19 currently pending
Career history
220
Total Applications
across all art units

Office Action

§101 §103 §112
DETAILED ACTION Acknowledgements The amendment filed on 05/27/2026 is acknowledged. Claims 11-30 are pending. Claims 11-30 have been examined. 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 . Response to Amendment/Arguments Claims 11-12, 14 and 17-19 are amended. Claims 20-30 are newly added. Regarding applicant’s remark on Claim Objections, the amendment overcomes the objection. Accordingly, the objection has been withdrawn. Regarding applicant’s arguments on Claim Rejections - 35 U.S.C. §101, the arguments have been fully considered but they are not persuasive. It is the applicant’s position that “claim 11 is not directed merely to ticketing service access control as a commercial interaction...claim 11 recites a specific computer-implemented token-processing method...” and claim 11 recites “a concrete technical method and a specific technical consequence, not a generalized business practice of selling or allocating tickets.” The Examiner respectfully disagrees. The claim(s) recite(s) ticketing service access control. Specifically, the claims recite “receiving, at a [ticketing computer system] over a [network] via a [network interface], a request from a [first device] of a user for access to a [ticket acquisition user interface] hosted by the [ticketing computer system]; transmitting via the [network interface], by the[ ticketing computer system] to a [device] associated with the user, a request for a time-limited, one-use [cryptographically verifiable token] associated with the request for access; determining, using the [ticketing computer system], whether the [first device] is associated with a human or an automated program by at least: determining whether a public key was received via the [network interface] in association with a time-limited, one-use [cryptographically verifiable token] associated with the user and configured to be only usable with the [ticketing computer system] via the [network interface], the [cryptographically verifiable token] comprising a [JSON Web token], a timestamp, a verifiable credential comprising a [pairwise-pseudonymous decentralized identifier] comprising a namespace component that identifies a decentralized identifier method, a signature, and a uniform resource identifier that associates the user with a decentralized identifier document; enabling the [first device] to utilize the [ticket acquisition user interface]; parsing, using the [ticketing computer system], the [JSON Web token] to obtain the verifiable credential, the decentralized identifier, and the uniform resource identifier; using, by the [ticketing computer system], at least one of the decentralized identifier or the uniform resource identifier to access a [remote system] and obtain a public key associated with the decentralized identifier; confirming, using the [ticketing computer system], a validity of the verifiable credential utilizing the public key associated with the decentralized identifier; at least partly in response to determining that the time-limited, one-use [cryptographically verifiable token] was received but that the [JSON Web token] did not successfully parse, or that a validity of the verifiable credential was not confirmed utilizing the public key associated with the decentralized identifier, adversely affecting a position of the request from the [first device] in a ticket request queue; at least partly in response to the user acquiring a first event ticket via the [ticket acquisition user interface], associating the first event ticket with the user in a first record; and at least partly in response to reading, by an [access control device], an authentication code from a [device] associated with the user, authenticating the user to access a venue.”, which is “commercial or legal interactions” within the “certain methods of organizing human activity” grouping of abstract ideas in prong one of step 2A of the Alice/Mayo test (See MPEP 2106) because the claims involve a series of steps for ticketing service access control. Accordingly, the claims recite an abstract idea. It is also the applicant’s position that “claim 11 recites a judicial exception at some level of abstraction, the claim integrates any such exception into a practical application.” because “it recites how the ticketing computer system uses specific information contained in the token in a particular manner:” and “claim 11 is directed to a particular implementation for handling invalid or unverified token scenarios in a networked ticketing environment, rather than merely invoking generic computers as tools to carry out an abstract idea.” The examiner respectfully disagrees. This judicial exception is not integrated into a practical application because, when analyzed under prong two of step 2A of the Alice/Mayo test (See MPEP 2106), the additional element(s) of the claim(s) such as the use of ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier, and remote system using the merely use(s) a computer as a tool to perform an abstract idea. The processors and memories are recited at a high-level of generality (i.e., as a generic processor performing a generic computer function of ticketing service access control) such that it amounts no more than mere instructions to apply the exception using a generic computer components. Accordingly, the additional elements do not impose any meaningful limits on practicing the abstract idea, and the claims are directed to an abstract idea. One of skill in the art would understand that when using authorization token for access control, there at least three basic scenarios that the system must be able to handle, such as no token, invalid token or valid token. Additionally, the applicant argues that “the ordered combination of limitations in claim 11 amounts to significantly more than any alleged abstract idea.” The examiner respectfully disagrees. The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of using ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier and remote system to perform ticketing service access control steps amounts to no more than mere instructions to apply the exception using a generic computer components. Mere instructions to apply an exception using a generic computer components cannot provide an inventive concept. The claim is not patent eligible. With respect to the applicant’s argument of “the mathematical concepts are not recited in the claims.”, the argument is moot as mathematical concepts was not used as the abstract idea group by the examiner. Regarding applicant’s arguments on Claim Rejections - 35 U.S.C. §103, the arguments are moot in light of the amendment overcomes the rejection. Accordingly, the rejection has been withdrawn. 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 11-30 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. Analysis In the instant case, claims 11-30 are directed to a method. Therefore, these claims fall within the four statutory categories of invention. The claim(s) recite(s) ticketing service access control. Specifically, the claims recite “receiving, at a [ticketing computer system] over a [network] via a [network interface], a request from a [first device] of a user for access to a [ticket acquisition user interface] hosted by the [ticketing computer system]; transmitting via the [network interface], by the[ ticketing computer system] to a [device] associated with the user, a request for a time-limited, one-use [cryptographically verifiable token] associated with the request for access; determining, using the [ticketing computer system], whether the [first device] is associated with a human or an automated program by at least: determining whether a public key was received via the [network interface] in association with a time-limited, one-use [cryptographically verifiable token] associated with the user and configured to be only usable with the [ticketing computer system] via the [network interface], the [cryptographically verifiable token] comprising a [JSON Web token], a timestamp, a verifiable credential comprising a [pairwise-pseudonymous decentralized identifier] comprising a namespace component that identifies a decentralized identifier method, a signature, and a uniform resource identifier that associates the user with a decentralized identifier document; enabling the [first device] to utilize the [ticket acquisition user interface]; parsing, using the [ticketing computer system], the [JSON Web token] to obtain the verifiable credential, the decentralized identifier, and the uniform resource identifier; using, by the [ticketing computer system], at least one of the decentralized identifier or the uniform resource identifier to access a [remote system] and obtain a public key associated with the decentralized identifier; confirming, using the [ticketing computer system], a validity of the verifiable credential utilizing the public key associated with the decentralized identifier; at least partly in response to determining that the time-limited, one-use [cryptographically verifiable token] was received but that the [JSON Web token] did not successfully parse, or that a validity of the verifiable credential was not confirmed utilizing the public key associated with the decentralized identifier, adversely affecting a position of the request from the [first device] in a ticket request queue; at least partly in response to the user acquiring a first event ticket via the [ticket acquisition user interface], associating the first event ticket with the user in a first record; and at least partly in response to reading, by an [access control device], an authentication code from a [device] associated with the user, authenticating the user to access a venue.”, which is “commercial or legal interactions” within the “certain methods of organizing human activity” grouping of abstract ideas in prong one of step 2A of the Alice/Mayo test (See MPEP 2106) because the claims involve a series of steps for ticketing service access control. Accordingly, the claims recite an abstract idea. This judicial exception is not integrated into a practical application because, when analyzed under prong two of step 2A of the Alice/Mayo test (See MPEP 2106), the additional element(s) of the claim(s) such as the use of ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier, and remote system using the merely use(s) a computer as a tool to perform an abstract idea. The processors and memories are recited at a high-level of generality (i.e., as a generic processor performing a generic computer function of ticketing service access control) such that it amounts no more than mere instructions to apply the exception using a generic computer components. Accordingly, the additional elements do not impose any meaningful limits on practicing the abstract idea, and the claims are directed to an abstract idea. The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of using ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier and remote system to perform ticketing service access control steps amounts to no more than mere instructions to apply the exception using a generic computer components. Mere instructions to apply an exception using a generic computer components cannot provide an inventive concept. The claim is not patent eligible. Dependent claims 12, 14 and 17-19 describe handling the second request. Dependent claim 13 describes requesting token from the user. Dependent claims 15-16 describe authentication code. Dependent claim 20 describes handling a request from a second device. Dependent claim 21 describes decentralized identifier document. Dependent claim 22 describes parsing the JSON Web token. Dependent claim 23 describes cryptographically verifiable token. Dependent claims 24-25 describe verifiable credential. Dependent claims 26 and 30 describe authentication code. Dependent claim 27 describes handling the second cryptographically verifiable token. Dependent claim 28 describes the request from the first device. Dependent claim 29 describes the ticketing compute system handling verifiable credential. These claims further recite the abstract idea of the certain methods of organizing human activity. This judicial exception is not integrated into a practical application because the additional element(s) of the claim(s) such as the use of ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier and remote system merely use(s) a computer as a tool to perform an abstract idea. The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. The claims are not patent eligible. Viewed as a whole, the combination of elements recited in the claims simply recite the concept of ticketing service access control. The claims do not, for example, purport to improve the functioning of the computer itself. Nor do they effect an improvement in any other technology or technical field. The use of a ticketing computer system, network, network interface, first device, device, ticket acquisition user interface, cryptographically verifiable token, JSON Web token, pairwise-pseudonymous decentralized identifier and remote system as tools to implement the abstract idea does not render the claim patent eligible because it does not provide meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment and requires no more than a computer performing functions that correspond to acts required to carry out the abstract idea. Claim Rejections - 35 USC § 112 The following is a quotation of the first paragraph of 35 U.S.C. 112(a): (a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention. The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112: The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention. Claims 11-30 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for pre-AIA the inventor(s), at the time the application was filed, had possession of the claimed invention. New Matter Regarding the amended claim 11, following limitations are new matter as they are not supported by the Specification. “parsing, using the ticketing computer system, the JSON Web token to obtain the verifiable credential, the decentralized identifier, and the uniform resource identifier;”. However, the specification is silent on parsing, using the ticketing computer system, the JSON Web token to obtain the verifiable credential, the decentralized identifier, and the uniform resource identifier. “using, by the ticketing computer system, at least one of the decentralized identifier or the uniform resource identifier to access a remote system and obtain a public key associated with the decentralized identifier;“ However, the specification is silent on using, by the ticketing computer system, at least one of the decentralized identifier or the uniform resource identifier to access a remote system and obtain a public key associated with the decentralized identifier. “at least partly in response to determining that the time-limited, one-use cryptographically verifiable token was received but that the JSON Web token did not successfully parse, or that a validity of the verifiable credential was not confirmed utilizing the public key associated with the decentralized identifier, adversely affecting a position of the request from the first device in a ticket request queue;” Specification Fig. 2 steps 206 and 208 illustrates adverse queue position when token is not received. Furthermore, Specification PGPub ¶0069 discloses “If, at block 206, a determination is made that the token was not received, the user may receive adverse treatment. For example, the user may be required to successfully complete a CAPTCHA and may receive a more negative position in a ticket queue, if one exists. Thus, other users (that did provide their respective tokens and were successfully determined to be human) that requested access after a first user that did not provide the token, may nonetheless be placed ahead of the first user.” However, the specification is silent on “at least partly in response to determining that the time-limited, one-use cryptographically verifiable token was received but that the JSON Web token did not successfully parse, or that a validity of the verifiable credential was not confirmed utilizing the public key associated with the decentralized identifier”. For the purposes of examination, these limitations are being interpreted as follows: at least partly in response to determining that the cryptographically verifiable token was not received via the network interface: adversely affecting a position of the request from the first device in a ticket request queue; Claims 12-30 are also rejected as each depends from claim 11. The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 1-30 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor, or for pre-AIA the applicant regards as the invention. Unclear Claim 11 recites “receiving, at a ticketing computer system over a network via a network interface, a request from a first device of a user...; transmitting via the network interface, by the ticketing computer system to a device associated with the user, a request...; ... at least partly in response to reading, by an access control device, an authentication code from a device associated with the user, ...” This renders the claim indefinite because it is unclear to one of ordinary skill in the art that a first device and a device are the same user device. Claims 12 and 14 recite “receiving, at the ticketing computer system over the network via the network interface, a request from a second device of a second user...; ...at least partly in response to reading, by an access control device, an authentication code from a device associated with the user, ...”. This renders the claim indefinite because it is unclear to one of ordinary skill in the art that a second device and a device are the same user device. Claim 11 recites “determining whether a public key was received...;...using, by the ticketing computer system,...obtain a public key associated with the decentralized identifier;”. This renders the claim indefinite because it is unclear to one of ordinary skill in the art that these public keys are the same. Dependent claims 12-30 are also rejected as each depend from claim 11. Allowable Subject Matter Claims 11-30 would be allowable if rewritten or amended to overcome the rejection(s) under 35 U.S.C. 101, 112(a) and 112(b) set forth in this Office action. The closest prior art of record is US20220321354A1 (“Ladd et al.”) teaches receiving, at a computer system over a network via a network interface, a request from a first device of a user for access to a service hosted by the computer system; (Fig. 3A step 302; ¶0053) transmitting via the network interface, by the computer system to a device associated with the user, a request (Fig. 3A step 310; ¶0055)for an access token; determining, using the ticketing computer system, whether the first device is associated with a human or an automated program by at least: (3A step 304; ¶0054) determining whether a public key was received in association with a cryptographically verifiable token associated with the user and configured to be only usable with the ticketing system via the network interface, (Fig. 3A step 314; ¶0057); enabling the first device to utilize the service; (Fig. 3A step 306; ¶0054). US20250148466A1 (“Kokaji et al.”) teaches wherein a computer system is a ticketing computer system, (Fig. 7 item 10) wherein the service is a ticket acquisition user interface; (Figs. 8-10 and 14-15) at least partly in response to the user acquiring a first event ticket via the ticket acquisition user interface, associating the first event ticket with the user in a first record; and (¶0087) at least partly in response to reading, by an access control device, an authentication code from a device associated with the user, authenticating the user to access a venue. (Fig. 12; ¶¶0076-79). US20160078370A1 (“McEwen et al.”) teaches at least partly in response to determining that the cryptographically verifiable token was not received via the network interface: adversely affecting a position of the request from the first device in a ticket request queue; (¶0055, claim 1 “a queue engine that,…” and claim 6). US20200313897A1 (“Health et al.”) teaches the cryptographically verifiable token comprising a JSON Web token, a timestamp, a verifiable credential comprising a pairwise-pseudonymous decentralized identifier comprising a namespace component that identifies a decentralized identifier method, a signature, and a uniform resource identifier that associates the user with a decentralized identifier document; (¶0044). However, the prior art does not teach, neither singly nor in combination the following: wherein the access token is a time-limited, one-use cryptographically verifiable token associated with the request for access, parsing, using the ticketing computer system, the JSON Web token to obtain the verifiable credential, the decentralized identifier, and the uniform resource identifier; using, by the ticketing computer system, at least one of the decentralized identifier or the uniform resource identifier to access a remote system and obtain a public key associated with the decentralized identifier; confirming, using the ticketing computer system, a validity of the verifiable credential utilizing the public key associated with the decentralized identifier. Conclusion The following prior art made of record and not relied upon is considered pertinent to applicant's disclosure. US20200211099A1 (“Smith et al.”) discloses systems and methods for decentralized distribution of verifiable information, such as financial information, without requiring resort to centralized information system at the time of a query or other request for information. A decentralized method includes the steps of creating a digital wallet, issuing/receiving an issued verifiable digital credential signed by a credential issuer acting as a trust anchor for a claim contained in the verifiable digital credential, storing the verifiable digital credential within the digital wallet, receiving a request for verified information, and providing the verifiable digital credential, including the claim, from the digital wallet. The verification of information may occur as a zero-knowledge proof such that a required standard is verified as satisfied without disclosing more information about a consumer or other user than is absolutely necessary. US20200014538A1 (“Liu”) discloses a method of facilitating authentication of a user. The method may include performing at least one of generating and receiving, using a processor, a primary cryptographic identifier consisted of a primary public key and a primary private key. Further, the method may include generating, using the processor, a global static user identifier corresponding to the user based on the primary public key. Further, the method may include generating, using the processor, a digital signature corresponding to a service based on a unique identifier associated with the service and the primary cryptographic identifier. Further, the method may include generating, using the processor, a key generation seed based on the digital signature and the global static user identifier. Further, the method may include generating, using the processor, a secondary cryptographic identifier including a secondary public key based on the key generation seed. THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any extension fee pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to YINGYING ZHOU whose telephone number is (571)272-5308. The examiner can normally be reached Mon - Fri 9:00am - 5:00pm ET. 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, John W Hayes can be reached on 571-272-6708. 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. /YINGYING ZHOU/Primary Examiner, Art Unit 3697
Read full office action

Prosecution Timeline

Show 1 earlier event
Mar 16, 2026
Non-Final Rejection mailed — §101, §103, §112
May 21, 2026
Applicant Interview (Telephonic)
May 21, 2026
Examiner Interview Summary
May 27, 2026
Response Filed
Aug 06, 2026
Final Rejection mailed — §101, §103, §112
Sep 04, 2026
Request for Continued Examination
Sep 10, 2026
Response after Non-Final Action
Nov 04, 2026
Non-Final Rejection mailed — §101, §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12784057
System and Methods of Verifiable Smart Contract as a Service
2y 8m to grant Granted Nov 03, 2026
Patent 12775920
Collateral Management With Blockchain and Smart Contracts Apparatuses, Methods and Systems
8y 1m to grant Granted Oct 27, 2026
Patent 12775940
PAYMENT PROCESSOR SUPPORTED WEB 3.0 WALLETS
3y 2m to grant Granted Oct 27, 2026
Patent 12762559
PAYMENTS FEDERATED DIRECTORY
2y 10m to grant Granted Oct 13, 2026
Patent 12749060
NFT Enforcement Control System
3y 3m to grant Granted Sep 29, 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
48%
Grant Probability
94%
With Interview (+45.8%)
High
PTA Risk
Based on 195 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