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 .
Claim Objections
Claims 2, 3, 5, 6, 15 and 16 are objected to because of the following informalities:
Claim 2 recites “each of the plurality authorization nodes is selected.” It should be “each of the plurality of authorization nodes is selected.”
Claim 3 recites “a data dissemination proximity associated with each of the plurality of nodes.” It should be “a data dissemination proximity associated with each of the plurality of authorization nodes is selected.”
Claims 5, 6, 15 and 16 recite “the predetermined condition.” It should be “the predefined condition.”
Appropriate correction is required.
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 1-20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as failing to set forth the subject matter which the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the applicant regards as the invention.
Claim 1 recites the limitation "the task." There is insufficient antecedent basis for this limitation in the claim because claims 1 defines “tasks performed by users” and “a particular task.”
Claim 5 recites the limitation " one or more of the cryptographic blocks.". There is insufficient antecedent basis for this limitation in the claim because claim 1 defines “a cryptographic block of a blockchain published by the localized blockchain authorization network” and “one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.”
Claim 7 recites the limitation "the data related to the transaction on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 8 recites the limitation "the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 9 recites the limitation " the data related to the transaction on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 10 recites the limitation "the task.". There is insufficient antecedent basis for this limitation in the claim because claims 1 defines “tasks performed by users” and “a particular task.”
Claim 11 recites the limitation "the task." There is insufficient antecedent basis for this limitation in the claim because claims 1 defines “tasks performed by users” and “a particular task.”
Claim 15 recites the limitation " one or more of the cryptographic blocks.". There is insufficient antecedent basis for this limitation in the claim because claim 11 defines “a cryptographic block of a blockchain published by the blockchain-based authorization network” and “one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.”
Claim 17 recites the limitation "the data related to the transaction on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 18 recites the limitation "the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 19 recites the limitation " the data related to the transaction on a second localized channel." There is insufficient antecedent basis for this limitation in the claim.
Claim 20 recites the limitation "the task.". There is insufficient antecedent basis for this limitation in the claim because claims 11 defines “tasks performed by users” and “a particular task.”
The respective dependent claims inherit the deficiencies of the independent claims upon which they are based and thus rejected as well.
Double Patenting
A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957).
A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101.
Claims 1-20 are rejected under 35 U.S.C. 101 as claiming the same invention as that of claims 1-10 and 16-25 of prior U.S. Patent No. US 12244744 B2. This is a statutory double patenting rejection (See the table provided below).
The instant application
Patent No. US 12244744 B2
1. A method, performed by a distributed ledger-based system for managing tasks performed by users of the system, comprising:
providing, by a initiator node, an authorization record proposal to a blockchain authorization network for validation, the authorization record proposal comprising a task identifier that identifies a particular task, a smart contract for validating the authorization record proposal and a localization profile, the localization profile comprising a listing of a plurality of authorization nodes that each meet one or more criteria, forming a localized blockchain authorization network for executing the smart contract;
validating, by the localized blockchain authorization network, the authorization record proposal to produce a validated authorization record in a cryptographic block of a blockchain published by the localized blockchain authorization network; and
processing, by a blockchain transaction network, transaction proposals related to the task and submitted by one or more transaction nodes, wherein processing comprises validating the transaction proposals against the validated authorization record and producing one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.
2. The method of claim 1, wherein each of the plurality authorization nodes is selected based on data sharing characteristics of a plurality of authorization nodes in the system, respectively.
3. The method of claim 2, wherein the data sharing characteristics comprise one or more of a data syntactical proximity, a data semantic proximity and/or a data dissemination proximity associated with each of the plurality of nodes.
4. The method of claim 1, wherein the particular task comprises an ephemeral task, and the localization profile further comprises a predefined condition when the localized channel should be deleted.
5. The method of 4, wherein the predetermined condition comprises validation, by a second smart contract executed by the blockchain transaction network, of one or more indications that one or more of the cryptographic blocks should be deleted.
6. The method of 4, wherein the predetermined condition comprises receipt of one or more indications that a mission associated with the particular task has been completed.
7. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for sharing the data related to the transaction on a second localized channel.
8. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for publishing two cryptographic blocks relating to the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel.
9. The method of claim 1, further comprising:
after validation of the authorization record proposal, providing, by the initiator node, a data sharing authorization record proposal to the localized blockchain authorization network for validation, the data sharing authorization record proposal for supplementing the validated authorization record, comprising sharing information for sharing the data related to the transaction on a second localized channel.
10. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising an identification of one or more nodes for receiving the data associated with the task, a public/private key pair, and a particular cryptographic nonce for each of the one or more nodes identified in the sharing information, respectively, each particular cryptographic nonce required for each of the one or more nodes to obtain the private key in order to decrypt the data;
wherein the public/private key pair and the cryptographic nonces provide an audit trail for tracking the data.
11. A distributed ledger-based system for managing tasks performed by users of the system, comprising:
an issuer node for providing an authorization record proposal to a blockchain authorization network for validation, the authorization record proposal comprising a task identifier that identifies a particular task, a smart contract that processes transactions related to the task and a localization profile, the localization profile comprising a listing of a plurality of nodes that each meet one or more criteria, for forming a localized blockchain authorization network for executing the smart contract;
the blockchain authorization network, for validating the authorization record proposal to produce a validated authorization record in a cryptographic block of a blockchain published by the blockchain-based authorization network; and
a blockchain transaction network, for processing transaction proposals related to the task and submitted by one or more transaction nodes, wherein processing comprises validating the transaction proposals against the validated authorization record and producing one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.
12. The system of claim 11, wherein each of the plurality of nodes is selected based on data sharing characteristics of each node, respectively.
13. The system of claim 12, wherein the data sharing characteristics comprise one or more of a data syntactical proximity, a data semantic proximity and/or a data dissemination proximity associated with each of the plurality of nodes.
14. The system of claim 11, wherein the particular task comprises an ephemeral task, and the localization profile further comprises a predefined condition when the localized channel should be deleted.
15. The system of claim 11, wherein the predetermined condition comprises validation, by a second smart contract executed by the blockchain transaction network, of one or more indications that one or more of the cryptographic blocks should be deleted.
16. The system of 15, wherein the predetermined condition comprises receipt of one or more indications that a mission associated with the particular task has been completed.
17. The system of claim 15, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for sharing the data related to the transaction on a second localized channel.
18. The system of claim 11, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for publishing two cryptographic blocks relating to the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel.
19. The system of claim 11, further comprising:
after validation of the authorization record proposal, providing, by the initiator node, a data sharing authorization record proposal to the localized blockchain authorization network for validation, the data sharing authorization record proposal for supplementing the validated authorization record, comprising sharing information for sharing the data related to the transaction on a second localized channel.
20. The system of claim 11, wherein the localization profile further comprises sharing information, the sharing information comprising an identification of one or more nodes for receiving the data associated with the task, a public/private key pair, and a particular cryptographic nonce for each of the one or more nodes identified in the sharing information, respectively, each particular cryptographic nonce required for each of the one or more nodes to obtain the private key in order to decrypt the data;
wherein the public/private key pair and the cryptographic nonces provide an audit trail for tracking the data.
1. A method, performed by a distributed ledger-based system for managing tasks performed by users of the system, comprising:
providing, by a initiator node, an authorization record proposal to a blockchain authorization network for validation, the authorization record proposal comprising a task identifier that identifies a particular task, a smart contract for validating the authorization record proposal and a localization profile, the localization profile comprising a listing of a plurality of authorization nodes that each meet one or more criteria, forming a localized blockchain authorization network for executing the smart contract;
validating, by the localized blockchain authorization network, the authorization record proposal to produce a validated authorization record in a cryptographic block of a blockchain published by the localized blockchain authorization network; and
processing, by a blockchain transaction network, transaction proposals related to the task and submitted by one or more transaction nodes, wherein processing comprises validating the transaction proposals against the validated authorization record and producing one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.
2. The method of claim 1, wherein each of the plurality authorization nodes is selected based on data sharing characteristics of a plurality of authorization nodes in the system, respectively.
3. The method of claim 2, wherein the data sharing characteristics comprise one or more of a data syntactical proximity, a data semantic proximity and/or a data dissemination proximity associated with each of the plurality of nodes.
4. The method of claim 1, wherein the particular task comprises an ephemeral task, and the localization profile further comprises a predefined condition when the localized channel should be deleted.
5. The method of 4, wherein the predetermined condition comprises validation, by a second smart contract executed by the blockchain transaction network, of one or more indications that one or more of the cryptographic blocks should be deleted.
6. The method of 4, wherein the predetermined condition comprises receipt of one or more indications that a mission associated with the particular task has been completed.
7. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for sharing the data related to the transaction on a second localized channel.
8. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for publishing two cryptographic blocks relating to the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel.
9. The method of claim 1, further comprising:
after validation of the authorization record proposal, providing, by the initiator node, a data sharing authorization record proposal to the localized blockchain authorization network for validation, the data sharing authorization record proposal for supplementing the validated authorization record, comprising sharing information for sharing the data related to the transaction on a second localized channel.
10. The method of claim 1, wherein the localization profile further comprises sharing information, the sharing information comprising an identification of one or more nodes for receiving the data associated with the task, a public/private key pair, and a particular cryptographic nonce for each of the one or more nodes identified in the sharing information, respectively, each particular cryptographic nonce required for each of the one or more nodes to obtain the private key in order to decrypt the data;
wherein the public/private key pair and the cryptographic nonces provide an audit trail for tracking the data.
16. A distributed ledger-based system for managing tasks performed by users of the system, comprising:
an issuer node for providing an authorization record proposal to a blockchain authorization network for validation, the authorization record proposal comprising a task identifier that identifies a particular task, a smart contract that processes transactions related to the task and a localization profile, the localization profile comprising a listing of a plurality of nodes that each meet one or more criteria, for forming a localized blockchain authorization network for executing the smart contract;
the blockchain authorization network, for validating the authorization record proposal to produce a validated authorization record in a cryptographic block of a blockchain published by the blockchain-based authorization network; and
a blockchain transaction network, for processing transaction proposals related to the task and submitted by one or more transaction nodes, wherein processing comprises validating the transaction proposals against the validated authorization record and producing one or more cryptographic blocks comprising data related to the task on a localized channel after the task has been completed.
17. The system of claim 16, wherein each of the plurality of nodes is selected based on data sharing characteristics of each node, respectively.
18. The system of claim 17, wherein the data sharing characteristics comprise one or more of a data syntactical proximity, a data semantic proximity and/or a data dissemination proximity associated with each of the plurality of nodes.
19. The system of claim 16, wherein the particular task comprises an ephemeral task, and the localization profile further comprises a predefined condition when the localized channel should be deleted.
20. The system of claim 16, wherein the predetermined condition comprises validation, by a second smart contract executed by the blockchain transaction network, of one or more indications that one or more of the cryptographic blocks should be deleted.
21. The system of 20, wherein the predetermined condition comprises receipt of one or more indications that a mission associated with the particular task has been completed.
22. The system of claim 20, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for sharing the data related to the transaction on a second localized channel.
23. The system of claim 16, wherein the localization profile further comprises sharing information, the sharing information comprising instructions for publishing two cryptographic blocks relating to the validated transaction record, a first cryptographic block comprising a first portion of the data associated with the completed task for publication on a first localized channel, and a second portion of the data associated with the completed task for publication on a second localized channel.
24. The system of claim 16, further comprising:
after validation of the authorization record proposal, providing, by the initiator node, a data sharing authorization record proposal to the localized blockchain authorization network for validation, the data sharing authorization record proposal for supplementing the validated authorization record, comprising sharing information for sharing the data related to the transaction on a second localized channel.
25. The system of claim 16, wherein the localization profile further comprises sharing information, the sharing information comprising an identification of one or more nodes for receiving the data associated with the task, a public/private key pair, and a particular cryptographic nonce for each of the one or more nodes identified in the sharing information, respectively, each particular cryptographic nonce required for each of the one or more nodes to obtain the private key in order to decrypt the data;
wherein the public/private key pair and the cryptographic nonces provide an audit trail for tracking the data.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Hennebert et al. (US 20250317276 A1): [0046] Using a blockchain smart contract to transmit the hash of the encrypted message makes it possible to trigger the transmission of the hash by publishing the transaction in the registry. The receiving peer will not need to retrieve the hash from the registry to verify the authenticity of the message. [0090] The peer device of index i has been previously configured to include an index j of another peer device, a master public key Kmaster and an IBE decryption key aDKey[Idi, Kmaster] in its electronic memory. The peer device of index i deterministically determines 106 the identifier Idj of the peer device of index j from the index j and the master public key Kmaster. Then the peer device of index i calculates 107 an IBE encryption key aCKey[Idj, Kmaster] according to an identity-based cryptography scheme using the identifier Idj and the master public key Kmaster. The peer device of index i encrypts 108 a first message 60, intended for the peer device of index j, using the IBE encryption key aCKey[Idj, Kmaster] then sends 109 the first encrypted message 61 to the peer device of index j. The peer device of index i may also receive a second encrypted message from the peer of the peer device of index j and decipher 110 this second encrypted message 64 using the IBE decryption key aDKey[Idi, Kmaster].
Smith et al. (US 11108627 B2): The object may last as long as a single device, such as a refrigerator, or only until a current function is completed. For example, a refrigerator may be regarded as a composite object 502 consisting of multiple other objects, such as a light, a compressor, a temperature sensor, a thermostat, a water dispenser, an ice maker, and the like. The other objects may each be atomic objects 504, 506, and 508, or may themselves be composite objects 502. The ice maker may be composite object 502 formed from atomic objects 504, 506, and 508, such as a temperature sensor, a thermostat, a solenoid-operated water valve, a timer, an ice tray, and the like. An example of a virtual composite object 502 made up of a number of physical devices is the intersection and the emergency cluster, described with respect to FIG. 4.
Bequet et al. (US 20220253335 A1):[0580] In some embodiments, to enable such aspects of the storage of an object to be taken into account, indications of such aspects may be included in its associated object location identifier 2222, 2332, 2442, 2722 or 2772 for use in a subsequent retrieval of the object. Therefore, and referring back to FIGS. 17C-D as an example, the conversion of the flow input data set 2330 into its distributable form 2330 d and the subsequent storage of the distributable form 2330 d as the multiple data object blocks 2336 d, as depicted in FIG. 17C, may be followed by the storage, within one of the data object location identifiers 2332 depicted in FIG. 17D, of indications of the flow input data set 2330 having been stored in a distributed manner as the multiple data object blocks 2336 d across multiple devices 2500 a-x or 2600 a-x, along with indications of which ones of the multiple devices 2500 a-x or 2600 a-x the multiple data object blocks 2336 d are stored within.
Manamohan et al. (US 20200311583 A1):The authorization information and expected credentials may be encoded within the smart contracts or other stored information available to nodes on the blockchain network. The valid state information may prohibit nodes exhibiting certain restricted semantic states from participating in an iteration. The restricted semantic states may include, for example, having uninitialized parameter values, being a new node requesting enrollment in an iteration after the iteration has started (with other participant nodes in the blockchain network), a stale node or restarting node, and/or other states that would taint or otherwise disrupt an iteration of model building. Stale or restarting nodes may be placed on hold for an iteration so that they can synchronize their local parameters to the latest values, such as after the iteration has completed.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANDREW SUH whose telephone number is (571)270-5524. The examiner can normally be reached 9:00 AM- 5:00 PM.
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, Carl Colin can be reached at (571) 272-3862. 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.
/ANDREW SUH/Primary Examiner, Art Unit 2493
Prosecution Insights