DETAILED ACTION
Status of Claims
This Office Action is in response to claims filed on 02/11/2026.
Claims 1-18 are pending and examined hereon.
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 .
Allowable Subject Matter
The present invention is directed to transferring tagged funds between accounts on tagged blockchain accounts of users. If the rejection rendered hereon are properly overcome, the claims may become patentable as the prior art made of record alone or in combination do not disclose: wherein said account request message (i) requests creation of a first/second tagged blockchain accounts configured to store at least a first/second amount of tagged funds; creating, by the processing server, the first/second tagged blockchain accounts; a disbursement request that identifies (i) an account identifier associated with the first tagged blockchain account, (ii) an account identifier associated with the second tagged blockchain account, and (iii) a second amount of tagged funds; and concurrent with the transferring of the second amount of tagged funds, creating, by the processing server, a genesis block on the blockchain.
Yet even if the missing claimed elements were found in a reasonable number of references, a person of ordinary skill in the art at the time the invention was made would not have been motivated to combine the above missing elements.
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-18 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Analysis
In the instant case, claims 1-9 are directed to a “Method” (Process). Claims 10-18 are directed to “A network system for creating traceability comprising: a processing server; a first computing system; a second computing system…” (Machine). Therefore, these claims fall within the four statutory categories of invention.
The claims recite an abstract idea of processing fund transfers, which is an abstract idea. Specifically, but for the additional elements, the claim under its broadest reasonable interpretation recites limitations grouped within the “Certain Methods of Organizing Human Activity,” grouping of abstract ideas in prong one of step 2A of the Alice/Mayo test since the steps include commercial interactions, and managing relationships (See MPEP 2106.04 & 2106.04(a)). The use of a physical aid to help perform Organized Human Activity and Mathematical Concept steps does not negate the Organized Human Activity nature of the limitations, but simply accounts for variations in memory capacity from one person to another. Further, claims can recite a Methods of Organized Human Activity even if they are claimed as being performed on a computer. See MPEP § 2106.04(a)(2), subsection III. The claim limitations reciting the abstract idea are grouped within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas as they involve transferring funds between accounts and creating a record of transfer with the transferring associated data after crating of accounts based on receiving request to create accounts for transferring of funds which is a commercial interaction between fund transferor (payer), fund transferee (payee) and fund transferring service provider based on managed relationships of accounts data associated with the transferring parties. More specifically, the following non-underlined claim elements recite the abstract idea while the underlined, bolded claim elements recite additional elements according to MPEP 2106.04(a).
Claims 1, as similar as 10,
A network system for creating traceability comprising: a processing server; a first computing system; a second computing system; and a blockchain network, wherein the processing server includes a processor and a memory storing instructions thereon that when executed by the processor cause the processor to
receive a first account request message, from the first computing system, wherein said account request message
(i) requests creation of a first blockchain account configured to store at least a first amount of tagged funds and
(ii) includes an identifier associated with the first computing system and the first amount of tagged funds;
create the first tagged blockchain account on a blockchain running in parallel with a payment gateway service maintained by the processing server;
receive a second account request message, from the second computing system, wherein said second account request message
(i) requests creation of a second tagged blockchain account configured to receive tagged funds and
(ii) includes an identifier associated with the second computing system;
create the second tagged blockchain account on the blockchain;
receive, once the first and second tagged blockchain accounts are created, a disbursement request from the first computing system, wherein the disbursement request identifies
(i) a second amount of tagged funds,
(ii) an account identifier associated with the first tagged blockchain account, and
(iii) an account identifier associated with the second tagged blockchain account;
transfer the second amount of tagged funds from the first amount of tagged funds in the first tagged blockchain account to the second tagged blockchain account; and
create, concurrent with the transferring of currency, a genesis block on the blockchain that includes
(i) a unique identifier tag assigned to the disbursement request and
(ii) disbursement details associated with the disbursement of the second amount of tagged funds.
This judicial exception is not integrated into a practical application because, when analyzed under prong two of step 2A of the Alice/Mayo test (See MPEP 2106.04(d)), the additional elements are merely used as circuitry and tools to perform an abstract idea and generally link the use of a judicial exception to a particular technological environment. Specifically, these additional elements perform the steps or functions of the abstract idea. Viewed as a whole, the use of the additional elements as a tools to implement the abstract idea and generally linking the use of the abstract idea to a particular technological environment does not integrate the abstract idea into a practical application because it requires no more than a computer performing functions that correspond to acts required to carry out the abstract idea. The additional elements do not involve improvements to the functioning of a computer, or to any other technology or technical field (MPEP 2106.05(a)), and the claims do not apply or use the abstract idea in some other meaningful way beyond generally linking the use of the abstract idea to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception (MPEP 2106.05(e) and Vanda Memo). Therefore, the claims do not, for example, purport to improve the functioning of a computer. Nor do they effect an improvement in any other technology or technical field. Accordingly, the additional elements do not impose any meaningful limits on practicing the abstract idea, and the claims are directed to an abstract idea.
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception because, when analyzed under step 2B of the Alice/Mayo test (See MPEP 2106.05), using the additional elements to perform the steps amounts to no more than using a computer or processor to automate and implement the abstract idea. As discussed above, taking the claim elements separately, these additional elements perform the steps or functions of the abstract idea. These functions correspond to the actions required to perform the abstract idea. Viewed as a whole, the combination of elements recited in the claims merely recite the concept of processing fund transfers. Therefore, the use of these additional elements does no more than employ the computer as a tool to automate and implement the abstract idea. The use of a computer or processor to merely automate and implement the abstract idea cannot provide significantly more than the abstract idea itself (MPEP 2106.05 (f) & (h)). Therefore, the claim is not patent eligible.
Dependent claims 2-9 and 11-18 further describe the abstract idea of processing fund transfers. That is, although claims 2-9 and 11-18 recite further functional steps using the additional elements of a processing server, a first computing system, a third computing system, a second computing system and a blockchain network, the additional element are merely used as circuitry and tools to perform an abstract idea and generally link the use of a judicial exception to a particular technological environment. The dependent claims do not include additional elements that integrate the abstract idea into a practical application or that provide significantly more than the abstract idea. Therefore, the dependent claims are also not patent eligible.
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 10-18 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.
Claim 10 recites “the transferring of currency.” There is insufficient antecedent basis for this limitation in the claim. Therefore, the scope of the claim is unclear. (See In re Zletz, 893 F.2d 319, 13 USPQ2d 1320 (Fed. Cir. 1989)).
Claims 11-18 are also rejected as each depend on claim 10.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
PGPub Kuang, Li-zhong (CN 112446787 A) discloses: A method and A network system for creating traceability comprising: a processing server; (“blockchain system 302”) a first computing system (“first resource management server”); a second computing system (“second resource management server”); and a blockchain network, wherein the processing server includes a processor and a memory storing instructions thereon that when executed by the processor cause the processor to (Figs. 1, 3, 7; “a blockchain system 100 refers to a system for performing data sharing between nodes, a plurality of nodes 101 may be included in the blockchain system 100, and the plurality of nodes 101 may refer to respective clients in the blockchain system 100.”)
receive a first account request message, from the first computing system, wherein said account request message (i) requests of a first blockchain account configured to store at least a first amount of funds and (ii) includes an identifier associated with the first computing system (“account address of the first blockchain account”) and the first amount of funds (“balance”); (Page 6, Lines 1-2; Page 13, Lines 6-8 “the registration module 601 is configured to: receive a blockchain account registration request, where the blockchain account registration request carries a first resource account identifier; generate a first blockchain account, where the account data of the first blockchain account includes the account address and balance; store the first resource account identifier corresponding to the account address of the first blockchain account.”)
create the first blockchain account on a blockchain running in parallel with a payment gateway (“The target resource management server 3011 may be a resource management server of a token issuer.”) service maintained by the processing server; (Page 6, Lines 1-2; Page 13, Lines 6-8 “generate a first blockchain account, where the account data of the first blockchain account includes the account address and balance; store the first resource account identifier corresponding to the account address of the first blockchain account.”)
receive a second account request message, from the second computing system, wherein said second account request message (i) requests of a second blockchain account configured to receive funds and (ii) includes an identifier associated with the second computing system (“second resource account identifier”); (Page 6, Lines 34-35 “Step 403: and the second resource management server sends a block chain account registration request to the block chain system, wherein the block chain account registration request carries a second resource account identifier.” Page 7, Lines 14-20)
create the second tagged blockchain account on the blockchain; (Page 7, Lines 15-20 “the blockchain system may generate a second blockchain account, where account data of the second blockchain account includes an account address and a balance; and correspondingly storing the second resource account identifier carried by the block chain account registration request and the account address of the second block chain account.”)
receive, once the first and second tagged blockchain accounts are created, a disbursement request (“a resource transfer request”) from the first computing system, wherein the disbursement request identifies (i) a second amount of funds (“a first resource amount”), (ii) an account identifier associated with the first blockchain account (“resource account identifier of the payer (i.e., the first resource account identifier)”), and (iii) an account identifier associated with the second tagged blockchain account (“the resource account identifier (i.e., the second resource account identifier) of the recipient”); (Page 8, Lines 47-51 “Step 408: the first resource management server sends a resource transfer request to the blockchain system. The resource transfer request is used to request a resource transfer. The resource transfer request carries a first resource amount that the first resource account needs to transfer to the second resource account. Specifically, the resource transfer request may carry a resource account identifier of the payer (i.e., a first resource account identifier), a resource account identifier of the payee (i.e., a second resource account identifier), and a quantity of the first resource to be transferred.”)
transfer the second amount of funds from the first amount of funds in the first blockchain account to the second blockchain account; (Page 9, Lines 18-34 “Step 409: after receiving a resource transfer request sent by a first resource management server, the block chain system determines the number of first coins corresponding to the first resource number, and transfers the tokens of the first coin number in the balance of the first block chain account to the balance of a second block chain account.”)
PGPub Wilkins et al. (US 2020/0322167 A1) discloses:
create the first blockchain account on a blockchain running in parallel with a payment gateway service maintained by the processing server; (Fig. 1; Par. [0059] “Creating operation 602 creates a first addressed account (e.g., customer portfolio wallet)… ”)
([0070] “the customer portfolio wallet data and the customer committed wallet data are recorded with distributed crypto ledgers as opposed to a database owned by an exchange in typical trading systems today (e.g., New York Stock Exchange owns its trading data) (918). Therefore, to provide the wallet data to the broker-dealers, the Crypto Adapter gathers the wallet data from crypto ledgers.”)
create the second tagged blockchain account on the blockchain; (Par. [0059] “Creating operation 602 creates… a second addressed account (e.g., customer committed wallet) for a customer.”)
receive, once the first and second tagged blockchain accounts are created, a disbursement request, wherein the disbursement request identifies (i) a second amount of funds (“a specified amount (e.g., an amount corresponding to a value of the digital transactional items)”), (ii) an account identifier associated with the first blockchain account (“addressed accounts: a first customer portfolio wallet”), and (iii) an account identifier associated with the second blockchain account (“addressed accounts:… a first customer committed wallet”); (Pars. [0062] “Receiving operation 702 receives a request to match a buy transaction with a sell transaction. The buy transaction can include a buy order to purchase digital transactional items for a specified amount (e.g., an amount corresponding to a value of the digital transactional items) and the sell transaction can include a sell order to sell the digital transactional items for an amount. The customer purchasing the digital transactional items can have two addressed accounts: a first customer portfolio wallet and a first customer committed wallet.”)
transfer the second amount of tagged funds from the first amount of tagged funds in the first tagged blockchain account to the second tagged blockchain account; (Fig. 6; Pars. [0047], [0074] “The Crypto Adapter determines whether the balance for the order is available (1024). If the balance is available, the Crypto Adapter creates and signs a crypto commitment transaction with the customer's private key for the customer portfolio wallet to transfer the USD token in the customer committed wallet (1026).” [0080]) and
create, concurrent with the transferring of currency, on the blockchain that includes (i) a unique identifier tag (“transaction identifier or hash/order identifier”) assigned to the disbursement request and (ii) disbursement details associated with the disbursement of the second amount of funds (“The FIX order transaction can include a message type (e.g., buy, sell), order identifier, funding transaction hash, return account, and a public key.”). (Fig. 10; Pars. [0038], [0048] “In addition to creating a crypto committed transaction, Crypto Adapter 215 creates a FIX order transaction. To create the FIX order transaction, Crypto Adapter 215 takes a non-crypto FIX order, maps the customer to a set of wallets and keys using the customer identifier, and creates and signs the FIX transaction with the customer portfolio wallet private key. The FIX transaction may be enriched with the output of the crypto order transaction, specifically a transaction identifier or hash of the crypto transaction order. The FIX order transaction can include a message type (e.g., buy, sell), order identifier, funding transaction hash, return account, and a public key.” [0074]).
PGPub Park Jong Eun (KR 20220064570 A) discloses create, concurrent with the transferring of currency, on the blockchain that includes (i) a unique identifier tag assigned to the disbursement request and (ii) disbursement details associated with the disbursement of the second amount of funds. (“the step of storing the first transaction ID and the transfer execution result in the block chain network may include storing the first transaction ID and the transfer execution result in the block chain network when the transfer execution result is a successful transfer.”)
PGPub Mullins et al. (US 2023/0075202 A1) discloses transfer the second amount of tagged funds from the first amount of tagged funds in the first tagged blockchain account to the second tagged blockchain account; (Fig. 2; Pars. [0047] “Specifically, transaction 210 includes a payor user account identifier (Account D) and a payee user account identifier (Account A), as well as a value specifying an amount of an asset (in this case a CBDC asset) that is to be transferred.”)
PGPub Zhang, Yang (CN 112767169 A) discloses
create the first blockchain account on a blockchain running in parallel with a payment gateway service maintained by the processing server; (“Referring to fig. 1 and 2, a first account is created on the blockchain network 105.”)
create the second blockchain account on the blockchain; (“Referring to fig. 1 and 6, a second account is created on the blockchain network 105.”)
Any inquiry concerning this communication or earlier communications from the examiner should be directed to WODAJO GETACHEW whose telephone number is (469)295-9069. The examiner can normally be reached M-F 8:00-6:00 CST.
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.
/WODAJO GETACHEW/Examiner, Art Unit 3697