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 .
Status of Claims
Claims 1-20 are pending.
Priority
This application 18/787,544, filed 07/29/2024 claims priority to:
CON of 18/236,742, filed 08/22/2023, which claims priority to:
CON of 17/886,387, filed 08/11/2022 (effective filing date)
Applicant’s claim for the benefit of a prior-filed application under 35 U.S.C. 119(e) or under 35 U.S.C. 120, 121, 365(c), or 386(c) is acknowledged.
Information Disclosure Statement
The information disclosure statement(s) (IDS) submitted on 07/29/2024 is/are in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement(s) has/have been considered by the examiner.
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-3, 6-10, 13-17 and 19-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 5-8, and 12-14 of U.S. Patent No. 12,051,048 and claims 1, 5-8, and 12-14 of U.S. Patent No. 11,880,810. Although the claims at issue are not identical, they are not patentably distinct from each other because all the claims at issue are recited in claims 1, 5-8, and 12-14 of U.S. Patent No. 12,051,048 and claims 1, 5-8, and 12-14 of U.S. Patent No. 11,880,810. The claims are mapped as follows:
Instant Application 18/787,544
US Patent 12,051,048
US Patent 11,880,810
1. A method for conducting a cryptocurrency transaction, the method comprising:
establishing, by a first processor, a secure network session with a second processor;
receiving, by the first processor from the second processor using the secure network session, an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypting, by the first processor, the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmitting, by the first processor using a public network session, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receiving, by the first processor through the secure network session, an encrypted second payload including an indication that the cryptocurrency account has received the second transaction amount and a monetary amount of the second transaction amount;
decrypting, by the first processor, the encrypted second payload to access the second payload;
in response to accessing the second payload, validating, by the first processor, the monetary amount of the second transaction amount as the transmitted second transaction amount;
generating and encrypting, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmitting, by the first processor over the secure network session, the encrypted validation notification to the second processor; and
generating and transmitting, by the first processor to the second processor via the public network session, a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount.
8. A method comprising:
establishing a secure network banking session (SNBS) between a first processor of a first computing device and a second processor of a second computing device, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
generating, by the second processor, a first payload comprising the monetary amount of cryptocurrency, a wallet address of a cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypting, by the second processor, the first payload to generate an encrypted first payload;
transmitting, by the second processor via the SNBS to the first processor, the encrypted first payload;
decrypting, by the first processor, the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmitting, by the first processor via a public blockchain network (PBN) to the cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
receiving, by the second processor via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generating, by the second processor, a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypting, by the second processor, the second payload to generate an encrypted second payload;
transmitting, by the second processor via the SNBS to the first processor, the encrypted second payload;
decrypting, by the first processor, the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validating, by the first processor, the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypting, by the first processor, the first validation result to generate an encrypted first validation result;
transmitting, by the first processor via the SNBS to the second processor, the encrypted first validation result;
transmitting, by the first processor via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
receiving, by the second processor via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
8. A method comprising:
establishing a secure network banking session (SNBS) between a first processor of a first computing device and a second processor of a second computing device, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
generating, by the first processor, a request for a wallet address of a cryptocurrency account associated with the second processor for the cryptocurrency transaction;
encrypting, by the first processor, the request to generate an encrypted request;
transmitting, by the first processor via the SNBS to the second processor, the encrypted request;
decrypting, by the second processor, the encrypted request to access the request;
in response to decrypting the encrypted request, generating, by the second processor, a first payload comprising the monetary amount of cryptocurrency, the wallet address of the cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypting, by the second processor, the first payload to generate an encrypted first payload;
transmitting, by the second processor via the SNBS to the first processor, the encrypted first payload;
decrypting, by the first processor, the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmitting, by the first processor via a public blockchain network (PBN) to the cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
receiving, by the second processor via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generating, by the second processor, a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypting, by the second processor, the second payload to generate an encrypted second payload;
transmitting, by the second processor via the SNBS to the first processor, the encrypted second payload;
decrypting, by the first processor, the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validating, by the first processor, the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypting, by the first processor, the first validation result to generate an encrypted first validation result;
transmitting, by the first processor via the SNBS to the second processor, the encrypted first validation result;
transmitting, by the first processor via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
receiving, by the second processor via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
2. The method of claim 1,
wherein at least one of the first payload or the second payload is encrypted.
8. A method comprising:
…
encrypting, by the second processor, the first payload to generate an encrypted first payload;
…
encrypting, by the second processor, the second payload to generate an encrypted second payload;
…
8. A method comprising:
…
encrypting, by the second processor, the first payload to generate an encrypted first payload;
…
encrypting, by the second processor, the second payload to generate an encrypted second payload;
…
3. The method of claim 1,
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
12. The method of claim 8,
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
12. The method of claim 8,
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
4. The method of claim 1, further comprising:
establishing, by the first processor, an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
No double patenting rejection
No double patenting rejection
5. The method of claim 1, further comprising:
transmitting, by the first processor to the second processor via the secure network session, a third payload comprising a fourth transaction amount corresponding to a second transaction identifier.
No double patenting rejection
No double patenting rejection
6. The method of claim 1,
wherein the first transaction identifier is unique to the second processor.
13. The method of claim 8,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
13. The method of claim 8,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
7. The method of claim 1,
wherein the first transaction identifier is unique to the transaction request.
14. The method of claim 8,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the cryptocurrency transaction.
14. The method of claim 8,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the transaction.
8. A computer system comprising:
a server comprising at least one processor and a non-transitory computer-readable medium containing instructions that when executed by the at least one processor causes the at least one processor to:
establish a secure network session with a second processor;
receive by the secure network session an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmit, using a public network session, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receive by the secure network session an encrypted second payload including an indication that the cryptocurrency account has received the first transaction amount and a monetary amount of the second transaction amount;
decrypt the encrypted second payload to access the second payload;
in response to accessing the second payload, validate the monetary amount of the second transaction amount as the transmitted second transaction amount;
generate and encrypt, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmit, over the secure network session, the encrypted validation notification to the second processor; and
generate and transmit, to the second processor via the public network session, a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount.
1. A system comprising:
a first computing device comprising a first processor; and
a second computing device comprising a second processor,
wherein the first processor is configured to:
establish a secure network banking session (SNBS) with the second processor, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
decrypt an encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmit, via a public blockchain network (PBN) to a cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
decrypt the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validate the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypt the first validation result to generate an encrypted first validation result;
transmit, via the SNBS to the second processor, the encrypted first validation result; and
transmit, via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
wherein the second processor is configured to:
establish the SNBS with the first processor;
generate a first payload comprising the monetary amount of cryptocurrency, a wallet address of the cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypt the first payload to generate an encrypted first payload;
transmit, via the SNBS to the first processor, the encrypted first payload;
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generate a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypt the second payload to generate an encrypted second payload;
transmit, via the SNBS to the first processor, the encrypted second payload; and
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
1. A system comprising:
a first computing device comprising a first processor; and
a second computing device comprising a second processor,
wherein the first processor is configured to:
establish a secure network banking session (SNBS) with the second processor, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
generate a request for a wallet address of a cryptocurrency account associated with the second processor for the cryptocurrency transaction;
encrypt the request to generate an encrypted request;
transmit via the SNBS to the second processor, the encrypted request;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmit, via a public blockchain network (PBN) to the cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
decrypt the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validate the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypt the first validation result to generate an encrypted first validation result;
transmit, via the SNBS to the second processor, the encrypted first validation result; and
transmit, via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
wherein the second processor is configured to:
establish the SNBS with the first processor;
decrypt the encrypted request to access the request;
in response to decrypting the encrypted request, generate a first payload comprising the monetary amount of cryptocurrency, the wallet address of the cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypt the first payload to generate an encrypted first payload;
transmit, via the SNBS to the first processor, the encrypted first payload;
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generate a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypt the second payload to generate an encrypted second payload;
transmit, via the SNBS to the first processor, the encrypted second payload; and
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
9. The computer system of claim 8,
wherein at least one of the first payload or the second payload is encrypted.
1. A system comprising:
…
wherein the second processor is configured to:
…
encrypt the first payload to generate an encrypted first payload;
…
encrypt the second payload to generate an encrypted second payload;
…
1. A system comprising:
…
wherein the second processor is configured to:
…
encrypt the first payload to generate an encrypted first payload;
…
encrypt the second payload to generate an encrypted second payload;
…
10. The computer system of claim 8,
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
5. The system of claim 1,
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
5. The system of claim 1,
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
11. The computer system of claim 8,
wherein the instructions further cause the processor to establish an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
No double patenting rejection
No double patenting rejection
12. The computer system of claim 8,
wherein the instructions further cause the processor to transmit, to the second processor via the secure network session, a third payload comprising a fourth transaction amount corresponding to a second transaction identifier.
No double patenting rejection
No double patenting rejection
13. The computer system of claim 8,
wherein the first transaction identifier is unique to the second processor.
6. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
6. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
14. The computer system of claim 8,
wherein the first transaction identifier is unique to the transaction request.
7. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the cryptocurrency transaction.
7. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the transaction.
15. A computer system comprising:
a first processor configured to access a public network and a private network, the first processor configured to:
establish a secure network session with a second processor via the private network;
receive by the secure network session an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmit, using a public network session established on the public network, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receive by the secure network session an encrypted second payload including an indication that the cryptocurrency account has received the first transaction amount and a monetary amount of the second transaction amount;
decrypt the encrypted second payload to access the second payload;
in response to accessing the second payload, validate the monetary amount of the second transaction amount as the transmitted second transaction amount;
generate and encrypt, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmit, over the secure network session, the encrypted validation notification to the second processor; and
generate and transmit, to the second processor via the public network session a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount; and
the second processor accessing the public network and the private network, wherein the second processor is configured to:
transmit the first payload to the first processor through the secure network session; and
transmit, to the first processor, the indication that the cryptocurrency account has received the first transaction amount.
1. A system comprising:
a first computing device comprising a first processor; and
a second computing device comprising a second processor,
wherein the first processor is configured to:
establish a secure network banking session (SNBS) with the second processor, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
decrypt an encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmit, via a public blockchain network (PBN) to a cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
decrypt the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validate the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypt the first validation result to generate an encrypted first validation result;
transmit, via the SNBS to the second processor, the encrypted first validation result; and
transmit, via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
wherein the second processor is configured to:
establish the SNBS with the first processor;
generate a first payload comprising the monetary amount of cryptocurrency, a wallet address of the cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypt the first payload to generate an encrypted first payload;
transmit, via the SNBS to the first processor, the encrypted first payload;
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generate a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypt the second payload to generate an encrypted second payload;
transmit, via the SNBS to the first processor, the encrypted second payload; and
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
1. A system comprising:
a first computing device comprising a first processor; and
a second computing device comprising a second processor,
wherein the first processor is configured to:
establish a secure network banking session (SNBS) with the second processor, wherein the SNBS is active for an amount of time for a cryptocurrency transaction of a monetary amount of cryptocurrency;
generate a request for a wallet address of a cryptocurrency account associated with the second processor for the cryptocurrency transaction;
encrypt the request to generate an encrypted request;
transmit via the SNBS to the second processor, the encrypted request;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload, transmit, via a public blockchain network (PBN) to the cryptocurrency account associated with the second processor, a first amount of cryptocurrency, wherein the first amount of cryptocurrency is less than the monetary amount of cryptocurrency;
decrypt the encrypted second payload to access the second payload;
in response to decrypting the encrypted second payload,
validate the first amount of cryptocurrency within the second payload to generate a first validation result;
encrypt the first validation result to generate an encrypted first validation result;
transmit, via the SNBS to the second processor, the encrypted first validation result; and
transmit, via the PBN to the cryptocurrency account, a second amount of cryptocurrency, wherein the second amount of cryptocurrency represents a remainder of the monetary amount of cryptocurrency; and
wherein the second processor is configured to:
establish the SNBS with the first processor;
decrypt the encrypted request to access the request;
in response to decrypting the encrypted request, generate a first payload comprising the monetary amount of cryptocurrency, the wallet address of the cryptocurrency account associated with the second processor, and a first transaction identifier corresponding to the cryptocurrency transaction;
encrypt the first payload to generate an encrypted first payload;
transmit, via the SNBS to the first processor, the encrypted first payload;
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a first indication that the cryptocurrency account associated with the second processor has received the first amount of cryptocurrency;
in response to receiving the first indication, generate a second payload comprising the first amount of cryptocurrency, and a second transaction identifier associated with the first amount of cryptocurrency;
encrypt the second payload to generate an encrypted second payload;
transmit, via the SNBS to the first processor, the encrypted second payload; and
receive, via the PBN from at least one blockchain node associated with the cryptocurrency account, a second indication that the cryptocurrency account associated with the second processor has received the second amount of cryptocurrency.
16. The computer system of claim 15,
wherein at least one of the first payload or the second payload is encrypted.
1. A system comprising:
…
wherein the second processor is configured to:
…
encrypt the first payload to generate an encrypted first payload;
…
encrypt the second payload to generate an encrypted second payload;
…
1. A system comprising:
…
wherein the second processor is configured to:
…
encrypt the first payload to generate an encrypted first payload;
…
encrypt the second payload to generate an encrypted second payload;
…
17. The computer system of claim 15,
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
5. The system of claim 1,
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
5. The system of claim 1,
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
18. The computer system of claim 15,
wherein the first processor is configured to establish an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
No double patenting rejection
No double patenting rejection
19. The computer system of claim 15,
wherein the first transaction identifier is unique to the second processor.
6. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
6. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the second processor.
20. The computer system of claim 15,
wherein the first transaction identifier is unique to the transaction request.
7. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the cryptocurrency transaction.
7. The system of claim 1,
wherein at least one of the first transaction identifier or the second transaction identifier is unique to the transaction.
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 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Step 1
Step 1 of the eligibility analysis asks is the claim to a process, machine, manufacture or composition of matter (See MPEP § 2106.03, subsections I and II). Claims 1-7 are directed to a computer-implemented method (i.e., process). Claims 8-14 are directed to a computer-implemented system (i.e., machine, and manufacture). Claims 15-20 are directed to a non-transitory computer-readable storage medium (i.e., manufacture). Therefore, these claims fall within the four statutory categories of invention.
Step 2A, Prong One
Prong One asks does the claim recite an abstract idea, law of nature, or natural phenomenon (MPEP § 2106.04(II)(A)(1)). Claims 1, 8 and 15 under a broadest reasonable interpretation recite an abstract idea because the claims describe partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption. The abstract idea “partial payment and validation for a currency transaction request to a wallet address” is grouped within the “certain methods of organizing human activity” grouping of abstract ideas (MPEP § 2106.04(a)(2), subsection II). The claim limitations reciting the abstract idea are grouped within the “certain methods of organizing human activity” grouping of abstract ideas because the limitations describe fundamental economic principles or practices, including mitigating risk, and describe commercial or legal interactions, including advertising, marketing or sales activities or behaviors. The abstract idea “message encryption and decryption” is grouped within the “mathematical concepts” grouping of abstract ideas (See MPEP § 2106.04(a)(2), subsection I). The claim limitations reciting the abstract idea are grouped within the “mathematical concepts” grouping of abstract ideas because the limitations describe mathematical calculations, as they describe a mathematical operation or an act of calculating using mathematical methods. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
Claim 1:
A method for conducting a cryptocurrency transaction, the method comprising:
establishing, by a first processor, a secure network session with a second processor;
receiving, by the first processor from the second processor using the secure network session, an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypting, by the first processor, the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmitting, by the first processor using a public network session, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receiving, by the first processor through the secure network session, an encrypted second payload including an indication that the cryptocurrency account has received the second transaction amount and a monetary amount of the second transaction amount;
decrypting, by the first processor, the encrypted second payload to access the second payload;
in response to accessing the second payload, validating, by the first processor, the monetary amount of the second transaction amount as the transmitted second transaction amount;
generating and encrypting, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmitting, by the first processor over the secure network session, the encrypted validation notification to the second processor; and
generating and transmitting, by the first processor to the second processor via the public network session, a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount.
Claim 8:
A computer system comprising:
a server comprising at least one processor and a non-transitory computer-readable medium containing instructions that when executed by the at least one processor causes the at least one processor to:
establish a secure network session with a second processor;
receive by the secure network session an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmit, using a public network session, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receive by the secure network session an encrypted second payload including an indication that the cryptocurrency account has received the first transaction amount and a monetary amount of the second transaction amount;
decrypt the encrypted second payload to access the second payload;
in response to accessing the second payload, validate the monetary amount of the second transaction amount as the transmitted second transaction amount;
generate and encrypt, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmit, over the secure network session, the encrypted validation notification to the second processor; and
generate and transmit, to the second processor via the public network session, a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount.
Claim 15:
A computer system comprising:
a first processor configured to access a public network and a private network, the first processor configured to:
establish a secure network session with a second processor via the private network;
receive by the secure network session an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor;
decrypt the encrypted first payload to access the first payload;
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmit, using a public network session established on the public network, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
receive by the secure network session an encrypted second payload including an indication that the cryptocurrency account has received the first transaction amount and a monetary amount of the second transaction amount;
decrypt the encrypted second payload to access the second payload;
in response to accessing the second payload, validate the monetary amount of the second transaction amount as the transmitted second transaction amount;
generate and encrypt, by the first processor, a validation notification of the monetary amount of the second transaction amount;
transmit, over the secure network session, the encrypted validation notification to the second processor; and
generate and transmit, to the second processor via the public network session a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount; and
the second processor accessing the public network and the private network, wherein the second processor is configured to:
transmit the first payload to the first processor through the secure network session; and
transmit, to the first processor, the indication that the cryptocurrency account has received the first transaction amount.
Step 2A, Prong Two
Prong Two asks does the claim recite additional elements that integrate the judicial exception into a practical application (MPEP § 2106.04(II)(A)(2)). Here, the additional elements individually and in combination, are recited at a high level of generality as generic and conventional elements merely serving as a tool to perform the abstract idea (MPEP § 2106.05(f)) and generally linking the use of the abstract idea to a particular technological environment (MPEP § 2106.05(h)). The description of the additional elements evidences that they are generic and conventional elements used as tools to perform the abstract idea (See Pre-Grant Publication 0019, 0021, 0025, 0029-0036, 0076, 0082-0085). These additional elements do not improve the functioning of computers, another technology, or a technical field (MPEP §§ 2106.04(d)(1) and 2106.05(a)). They do not apply the abstract idea to effect a particular treatment or prophylaxis for a disease or medical condition (MPEP § 2106.04(d)(2)). They do not implement the abstract idea with a particular machine or manufacture that is integral to the claim (MPEP § 2106.05(b)). They do not transform or reduce a particular article to a different state or thing (MPEP § 2106.05(c)). Nor do they apply the abstract idea in a meaningful way or impose a meaningful limit on it beyond linking its use to a particular technological environment (MPEP § 2106.05(e)). Such a generic computer implementation does not make the abstract idea patent eligible because a wholly generic computer implementation is not generally the sort of additional feature that provides any practical assurance that the process is more than a drafting effort designed to monopolize the abstract idea itself. The Specification and the claim language provide evidence that the focus of the claim is not on a specific improvement in technology but rather on a scheme, for which generic and conventional elements are invoked merely as a tool to implement the abstract idea and link it to a particular field of use. Even if the Specification describes technical improvements, they are not claimed. Thus, the additional elements do not integrate the abstract idea into a practical application. Accordingly, the claims are directed to the abstract idea identified above.
Step 2B
Step 2B determines whether the claim as a whole amount to significantly more than the abstract idea itself (MPEP § 2106.05). Evaluating additional elements to determine whether they amount to an inventive concept requires considering them both individually and in combination to ensure that they amount to significantly more than the abstract idea itself. Individually, the additional elements do not amount to significantly more than the abstract idea. As discussed previously, the description of the additional elements evidences that they are generic and conventional elements used as tools to perform the abstract idea (See Pre-Grant Publication 0019, 0021, 0025, 0029-0036, 0076, 0082-0085). There is nothing in the Specification to indicate that the operations recited in the claims require any specialized hardware or inventive computer components or that the claimed invention is implemented using other than generic computer components to perform generic computer functions. As such, the additional elements merely serve as a tool to perform the abstract idea and generally link the use of the abstract idea to a particular technological environment. The ordered combination recites no more than the individual elements do. Thus, the additional elements are not significantly more than the abstract idea. Accordingly, the claims are directed to the abstract idea identified above without significantly more. The claims are not eligible, warranting a rejection for lack of subject matter eligibility and concluding the eligibility analysis.
Dependent Claims
Claim 2 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein at least one of the first payload or the second payload is encrypted.
Claim 3 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
Claim 4 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
establishing, by the first processor, an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
Claim 5 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
transmitting, by the first processor to the second processor via the secure network session, a third payload comprising a fourth transaction amount corresponding to a second transaction identifier.
Claim 6 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the second processor.
Claim 7 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the transaction request.
Claim 9 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein at least one of the first payload or the second payload is encrypted.
Claim 10 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
whereby the second processor verifies an integrity of the first payload or the second payload using metadata associated with each respective payload.
Claim 11 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the instructions further cause the processor to establish an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
Claim 12 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the instructions further cause the processor to transmit, to the second processor via the secure network session, a third payload comprising a fourth transaction amount corresponding to a second transaction identifier.
Claim 13 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the second processor.
Claim 14 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the transaction request.
Claim 16 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein at least one of the first payload or the second payload is encrypted.
Claim 17 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
whereby the second processor is configured to verify an integrity of the first payload or the second payload using metadata associated with each respective payload.
Claim 18 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first processor is configured to establish an authenticated session with the second processor when at least one of an integrity of the first payload or the second payload has been verified.
Claim 19 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the second processor.
Claim 20 recites an abstract idea because the claim describes partial payment and validation for a currency transaction request to a wallet address, and message encryption and decryption, grouped within the “certain methods of organizing human activity” and “mathematical concepts” grouping of abstract ideas. The additional elements do not integrate the abstract idea into a practical application because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. The additional elements are not significantly more than the abstract idea because individually and in combination, the additional elements are recited at a high level of generality as generic and conventional computers and components merely serving as a tool to perform the abstract idea and generally linking the use of the abstract idea to a particular technological environment. Therefore, the claim is not eligible. The following underlined claim limitations recite the abstract idea. The non-underlined claim limitations recite additional elements.
wherein the first transaction identifier is unique to the transaction request.
Claim Rejections - 35 USC § 112
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 8-14 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.
Lack of Antecedent Basis
Claim 8 recites "generate and encrypt, by the first processor, a validation notification …" without proper antecedent basis. The claim recites “… comprising: a server comprising at least one processor …”, but it is unclear whether “the first processor” constitutes the “at least one processor” or not. Appropriate correction is needed.
Claims 11-12 recite "wherein the instructions further cause the processor to …" without proper antecedent basis. Claim 8, which claims 11-12 depend on, recite “… comprising: a server comprising at least one processor …”, “a second processor”, and “the first processor”, thus it is unclear which of these, if any, the recitation of “the processor” refers to. Appropriate correction is needed.
Therefore, these claims are indefinite and are rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
Claims 9-14 are also rejected per dependency upon a rejected claim.
The following is a quotation of 35 U.S.C. 112(d):
(d) REFERENCE IN DEPENDENT FORMS.—Subject to subsection (e), a claim in dependent form shall contain a reference to a claim previously set forth and then specify a further limitation of the subject matter claimed. A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.
The following is a quotation of pre-AIA 35 U.S.C. 112, fourth paragraph:
Subject to the following paragraph [i.e., the fifth paragraph of pre-AIA 35 U.S.C. 112], a claim in dependent form shall contain a reference to a claim previously set forth and then specify a further limitation of the subject matter claimed. A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.
Claims 2, 9 and 16 are rejected under 35 U.S.C. 112(d) as being of improper dependent form for failing to further limit the subject matter of the claim upon which it depends, or for failing to include all the limitations of the claim upon which it depends.
Claims 2, 9 and 16 recite “wherein at least one of the first payload or the second payload is encrypted.” The claims contain a reference to a previous claim in the same application, that being claims 1, 8 and 15, respectively, thus the claims are dependent claims. However, the claims fail to further limit the subject matter of the claim upon which each depends because the limitations “an encrypted first payload” and “an encrypted second payload” are already recited in the previous claims. Therefore, the claims are rejected under 35 U.S.C. 112(d).
Applicant may cancel the claim(s), amend the claim(s) to place the claim(s) in proper dependent form, rewrite the claim(s) in independent form, or present a sufficient showing that the dependent claim(s) complies with the statutory requirements. “When examining a dependent claim, the examiner should determine whether the claim complies with 35 U.S.C. 112(d), which requires that dependent claims contain a reference to a previous claim in the same application, specify a further limitation of the subject matter claimed, and include all the limitations of the previous claim.” See MPEP 608.01(n) III.
Claims Free of Art
Claims 1-20 are free of art. The closest prior art of record is US 2020/0151686 A1 by Komandur et al. (hereinafter “Komandur”). Komandur teaches:
establishing, by a first processor, a secure network session with a second processor; (0379, 0381, 0388)
receiving, by the first processor from the second processor using the secure network session, an encrypted first payload, the encrypted first payload including a transaction request to transmit a first transaction amount to the second processor, a first transaction identifier, and a wallet address of a cryptocurrency account associated with the second processor; (0380-0381)
decrypting, by the first processor, the encrypted first payload to access the first payload; (0423, 0425, 0426, 0433, 0435)
receiving, by the first processor through the secure network session, an encrypted second payload including an indication that the cryptocurrency account has received the second transaction amount and a monetary amount of the second transaction amount; (0387, 0391-0392)
decrypting, by the first processor, the encrypted second payload to access the second payload; (0423, 0425, 0426, 0433, 0435)
in response to accessing the second payload, validating, by the first processor, the monetary amount of the second transaction amount as the transmitted second transaction amount; (0389)
generating and encrypting, by the first processor, a validation notification of the monetary amount of the second transaction amount; (0387, 0391-0392)
transmitting, by the first processor over the secure network session, the encrypted validation notification to the second processor; and (0387, 0391-0392)
US 2015/0262173 A1 to Durbin et al. is also of interest (hereinafter “Durbin”). Durbin teaches:
generating and transmitting, by the first processor to the second processor via the public network session (0018-0019), a third transaction amount to the cryptocurrency account, the third transaction amount corresponding to a value that is less than the first transaction amount and more than the second transaction amount (0038, 0045, 0052)
Therefore, the prior art does not teach, neither singly nor in combination the following:
in response to decrypting the encrypted first payload from the secure network session to access the first payload, transmitting, by the first processor using a public network session, a second transaction amount that corresponds to a value that is less than the first transaction amount to the wallet address of the cryptocurrency account associated with the second processor;
Conclusion
The following prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 2018/0046992 A1 by Hanrahan et al. discloses: Systems and methods for account reconciliation using a distributed ledger are disclosed. In one embodiment, a method for account reconciliation using a distributed ledger may include: (1) a payment sending financial institution receiving a transaction involving an account maintained by the payment sending financial institution for a payment receiving financial institution; (2) the payment sending financial institution communicating the transaction to the payment receiving financial institution using a transaction network; (3) the payment sending financial institution writing the transaction as a first ledger entry to the payment sending financial institution's copy of a distributed transaction ledger; (4) the payment sending financial institution receiving a second ledger entry from the payment receiving financial institution; and (5) the payment sending financial institution reconciling the account using the first ledger entry and the second ledger entry.
US 2017/0243193 A1 by Manian et al. discloses: This disclosure describes a hybrid of blockchain with other information management systems to provide validation for documents, transaction state and performance against contracts. A blockchain document hybrid allows portions of versioned documents to be shared without revealing full document content. For transaction and contract state a confidential Shared Data Structure (SDS) is combined with a publicly viewable blockchain to record the terms of a trade transaction, starting from as early as a purchase order. Out of these building blocks we present designs for commerce systems that can automatically execute the flow of money based upon signals resulting from the flow of goods. Besides reducing processing costs through automation, these designs open up avenues for innovations such as a Data LC, Blockchain Based Obligation (BBO), Deep Tier Financing, and Cash Flow Scrips.
US 11,276,054 B1 by Tomkins et al. discloses: Techniques for integrating a payment processing platform (PPP) and a payment making platform (PMP) for differentiated payment allocations using cryptocurrency is described. In response to an indication to allocate a first portion of funds generated from payment received for transaction(s) processed by the PPP to a cryptocurrency wallet account for a user, the PMP can receive a request for first account information associated with the cryptocurrency wallet account. The PMP can send the first account information to the PPP, wherein the first account information is associated with second account information of a merchant account of the user. The PMP can receive, from the PPP, a request to deposit a first portion of the funds into the cryptocurrency wallet account, wherein a second portion of funds is retained by the PPP for deposit into the merchant account as fiat currency.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Ari Shahabi whose telephone number is (571)272-2565. The examiner can normally be reached M-F: 8:00-5:00.
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 at 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.
/ARI SHAHABI/Primary Examiner, Art Unit 3697