DETAILED ACTION
Acknowledgements
The amendment filed on 05/22/2026 is acknowledged.
Claims 1-6, 8-17 and 19-22 are pending.
Claims 1-6, 8-17 and 19-22 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 1-4, 8-9, 12-16 and 19-20 are amended.
Regarding applicant’s arguments on Claim Rejections - 35 U.S.C. §101, the arguments have been fully considered. The amendment integrates the judicial exception into a practical application because the claims apply or use the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole are more than a drafting effort designed to monopolize the exception. Accordingly, the amendment overcomes the 101 rejection and the rejection has been withdrawn.
Regarding applicant’s arguments on Claim Rejections - 35 U.S.C. §103, the arguments have been fully considered. The amendment overcomes the 103 rejection and the rejection has been withdrawn.
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.
Claims1-6, 8-17 and 19-22 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.
Regarding the amended claims 1 and 12, following limitations are not supported by the Specification.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:....generating, by a processor of the processing server within the network system, a cryptographic token for the user device based on at least the one or more verified user identity attributes and including at least one uniform resource locator (URL) configured to initiate a request for identity verification information for a user of the user device;” Specification Fig. 3A step 308 illustrates the processing server generating a token and alias. Additionally, Specification PGPub ¶0066 discloses “In step 308, the generation module 218 of the processing server 102 can generate a permission token and alias for the participant. The permission token can include a plurality of data fields for identity attributes used in regulation compliance where the data values for the data fields are based on the verified user identity attributes received in the onboarding request.” However, the specification is silent on generating, by a processor of the processing server within the network system, a cryptographic token for the user device based on at least the one or more verified user identity attributes and including at least one uniform resource locator (URL) configured to initiate a request for identity verification information for a user of the user device.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:....transferring, by transmitting, by a transmitter of the processing server within the network system, the generated cryptographic token to the blockchain wallet of the user device on a blockchain associated with a blockchain network using the blockchain address included in the received request;” Specification Fig. 3A step 310 illustrates the processing server transmit alias to the first computing device. Furthermore, Specification PGPub ¶0066 discloses “In step 310, the transmitting device 222 of the processing server 102 can electronically transmit the alias to the first service provider 110a in response to the onboarding request.”. However, the Specification is silent on transferring, by transmitting, by a transmitter of the processing server within the network system, the generated cryptographic token to the blockchain wallet of the user device on a blockchain associated with a blockchain network using the blockchain address included in the received request.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:....receiving by a second computing system, a service request for services from the user device, the request for services including at least information identifying the blockchain wallet of the user device;” Specification PGPub ¶0067 discloses “In step 316, the second service provider 110b can receive the transaction requested.”. However, The specification is silent on the request for services including at least information identifying the blockchain wallet of the user device.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:.... identifying, by the second computing system, (i) the cryptographic token in the blockchain wallet of the user device and (ii) a URL of the at least one URL included in the cryptographic token associated with user identity attributes required by the second computing system;” Specification Fig. 3B step 322 illustrates identify permission token, and ¶0068 discloses “In step 322, the querying module 216 of the processing server 102 can identify the permission token for the first participant in an account profile 208 associated therewith identified via the received alias.” However, the specification is silent on identifying, by the second computing system, (i) the cryptographic token in the blockchain wallet of the user device and (ii) a URL of the at least one URL included in the cryptographic token associated with user identity attributes required by the second computing system.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:.... receiving, by the receiver of the processing server, a request for identity verification information from the second computing system, the request initiated by the second computing system navigating to the URL identified from the cryptographic token;” Specification Fig. 3B step 320 illustrates the processing server received a token request from the second computing system. PGPub ¶0068 further discloses “In step 320, the receiving device 202 of the processing server 102 can receive the permission token request.” However, the specification is silent on a request for identity verification information from the second computing system, the request initiated by the second computing system navigating to the URL identified from the cryptographic token.
Claim 1 recites “A method for facilitating permission-based cryptographic transactions..., the method comprising:.... in response to the received request for identity verification information, transmitting, by the transmitter of the processing server, the one or more verified user identity attributes or a verification level to the second computing system without exposing any personally identifiable information of the user; and” Specification PGPub ¶0068 discloses “In step 324, the transmitting device 222 of the processing server 102 can electronically transmit the identified permission token for the first participant to the second service provider 110b in response to the permission token request.” However, the specification is silent on the received request for identity verification information, transmitting, by the transmitter of the processing server, the one or more verified user identity attributes or a verification level to the second computing system without exposing any personally identifiable information of the user.
Claim 12 is a system claim that recites similar languages as claim 1 which is not supported by the specification.
Dependent claims 2-6, 8-11 and 13-17, 19-22 are also rejected as each depends from claims 1 and 12 respectively.
For the purpose of examination, these limitations are being interpreted as follow:
generating, by a processor of the processing server within the network system, (1) a permission token based on at least the permission data and (2) an alias, wherein the permission token includes one or more verified identity data points;
transmitting, by a transmitter of the processing server within the network system, the generated alias to the first computing system in response to the received request;
receiving by a second computing system, a service request for services from the user device;
identifying, by the second computing system, alias;
receiving, by the receiver of the processing server, a token request from a second computing system, wherein the token request includes the alias; and
transmitting, by the transmitter of the processing server, at least the generated permission token and the identification value to the second computing system in response to the received token request.
Allowable Subject Matter
Claims 1-6, 8-17 and 19-22 would be allowable if rewritten or amended to overcome the rejection(s) under 35 U.S.C. 101 and 112(a) set forth in this Office action. The closest prior art of record is US20030028481A1 (“Flitcroft et al.”). Flitcroft et al. discloses receiving, by a receiver of a processing server within a network system, the request from the first computing system; (¶¶0231–232, ¶0238 and ¶0240) generating, by a processor of the processing server within the network system, a cryptographic token for the user device based on at least the one or more verified user identity attributes and including at least one uniform resource locator (URL) configured to initiate a request for identity verification information for a user of the user device; (¶¶0232–233) transferring, by transmitting, by a transmitter of the processing server within the network system, the generated cryptographic token to the blockchain wallet of the user device on a blockchain associated with a blockchain network using the blockchain address included in the received request; (¶¶0231-232) receiving, by the receiver of the processing server, a request for identity verification information from the second computing system, the request initiated by the second computing system navigating to the URL identified from the cryptographic token; (¶0240) in response to the received request for identity verification information, transmitting, by the transmitter of the processing server, the one or more verified user identity attributes or a verification level to the second computing system without exposing any personally identifiable information of the user; and (¶0240). However, the prior art does not teach, verifying, by a first computing system within the network system, one or more user identity attributes of a user associated with a user device; transmitting, by the first computing system, a request to a processing server within the network system, the request including the one or more verified user identity attributes and an identification value associated with a blockchain address for a blockchain wallet of the user device; receiving by a second computing system, a service request for services from the user device, the request for services including at least information identifying the blockchain wallet of the user device; identifying, by the second computing system, (i) the cryptographic token in the blockchain wallet of the user device and (ii) a URL of the at least one URL included in the cryptographic token associated with user identity attributes required by the second computing system; verifying, by the second computing system, compliance of the user device with one or more applicable regulations based on the transmitted one or more verified user identity attributes or the verification level prior to executing a cryptographic transaction on the blockchain.
Conclusion
The following prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US20190222422A1 (“Purves”) discloses A blockchain based alias directory may be utilized. Encrypted lists of aliases may be stored on the blockchain and may be accessible to network computers and secure gateways. Embodiments are directed to secure gateways and user devices for accessing the alias directory stored in the blockchain during a financial transaction. The user device may be provided with a list of aliases from which a user may select a payment account. Upon selection the user may be redirected to an identity verification system of the associated payment network.
US20230033361A1(“Mitra et al.”) discloses a method for facilitating benefit disbursements through the use of tokens and blockchain includes: receiving beneficiary information from a first computing system, the beneficiary information including a beneficiary identifier; storing a blockchain data entry, the blockchain data entry including a disbursement token associated with the beneficiary information and a recipient value generated using a public key of a cryptographic key pair; receiving a redemption message from a second computing system, the redemption message including the disbursement token, a digital signature generated using a private key of the cryptographic key pair, transaction account data, and a redemption amount; validating the digital signature using the public key of the cryptographic key pair; and transmitting a transfer message to the first computing system, the transfer message including the transaction account data and the redemption amount.
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
Prosecution Insights