DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 01/27/2025 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Acknowledgement
The preliminary amendment filed 12/31/2024 is acknowledged.
Status of Claims
Claims 1-18 and 36-37 are pending
Claims 19-35 are cancelled.
Claim Objections
Claims 36 and 37 are objected to because of the following informalities:
The claim status of each says (Original). The claim status for the amended claims should be (Currently Amended) as per MPEP 714.
Appropriate correction is required.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claim(s) 1-18 and 36-37 is/are rejected under 35 U.S.C. 103 as being unpatentable over (US 2020134586) hereinafter ‘586.
‘586 discloses (see description, paragraphs 0003-0007, 0022-0083, figures 1-12): one or more methods, systems, apparatuses, and computer readable mediums storing processor- executable process steps, as described in claims 1, system claim 36 and computer program claim 37, to increase anonymity and traceability of a digital property management system that manage digital property transactions based on cryptographic technology in a distributed transaction consensus network.
It is known within the art that alternative cryptographic algorithms known to people with ordinary skill in the art can be used.
Thus, since a distributed ledger is used to record digital property transactions, it is known that a complete copy of the distributed ledger is maintained at a large number of nodes in the distributed transaction consensus network. It is also known that when a subscriber opens a virtual wallet with a digital property manager, the subscriber’s personal information is created and maintained within the virtual wallet, including the physical identification which can be used to identify an individual or entity in the real world (such as name, social security number, and telephone number) and as well as virtual identification are often used to identify his/her virtual wallet (e.g., virtual wallet ID and virtual wallet address), by its digital property management module.
Thus, sender's digital property management module ("sender's module) has both the sender's physical identification and virtual identification; conversely, the recipient's digital property management module ("recipient's module") maintains both recipient's physical identification and virtual identification.
Each transaction node 120, 150 in the ledger corresponds to a digital property management module ("module") which comprises both hardware and software to construct, sign, and send transactions to the transaction node. A digital property management module includes a wallet server, a signing server, a middleware (also known as transaction processing engine), token mapping database, message public key of transaction node look up API, etc. to implement these functions.
Subscribers of digital property managers can request, via a network device, a transaction to be processed and recorded by the TBCA Network 100. A transaction is regularly prepared by a digital property management module which then submits the transaction to its transaction node.
In step 830 of FIG. 8, the sender's wallet server 802 receives a remittance request from the sender, e.g. William, for transferring an amount, e.g. 60 digital US Dollars, to the recipient, e.g. Steve. The remittance request includes at least (1) sender's physical identification, such as William's mobile phone number, (2) recipient's physical identification, such as Steve's mobile phone number, and the amount of digital property and its type for remittance. Sender's wallet server 802 may receive sender's virtual identification, William's virtual wallet ID, directly from the sender, or retrieve it from a data storage of sender's digital property management module. In step 832, sender's wallet server 802 sends a token request to wallet servers of all other digital property management modules. After receiving the token request, recipient's module verifies the message is authentic and then confirms that the recipient is a subscriber by checking his/her physical identification, such as Steve's mobile phone number. Then, recipient's module generates a token and creates a token mapping that relates the token to recipient's virtual identification, such as Steve's virtual wallet ID. In one embodiment, a token can be a string randomly generated. When a token is generated, a copy of the token is also placed in a valid token pool. After the delivery transaction which the token is used to construct is committed to a distributed ledger, it is removed from the valid token pool to prevent it from being used again. In step 834, recipient's wallet server 812 sends a token response directly back to sender's wallet server 802. In step 836, after collecting all necessary information, sender's wallet server 802 provides the information to sender's middleware 804 to construct the remittance transaction for distributed transaction consensus network. Sender's middleware 804 tried to construct sending transaction, inter-manager transaction, and delivery transaction.
Recipient’s digital property management module verifies the inter-manager transactions to confirm that the virtual wallet of recipient’s digital property manager will receive a fund transfer fund transfer from the virtual wallet of sender’s digital property manager. Then, recipient’s module converts the temporary delivery trans action t nor more using the token and the token mapping database.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to DANIEL S FELTEN whose telephone number is (571)272-6742. The examiner can normally be reached Flex.
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, Ryan D Donlon can be reached at 5712703602. 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.
DANIEL S. FELTEN
Examiner
Art Unit 3692
/DANIEL S FELTEN/Primary Examiner, Art Unit 3692
Prosecution Insights