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 .
This action is responding to the application papers filed on 7/8/2024.
Claims 1-20 are pending in the application.
Information disclosure statement filed on 7/16/2024 is considered.
Claim Interpretation
The following is a quotation of 35 U.S.C. 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
The following is a quotation of pre-AIA 35 U.S.C. 112, sixth paragraph:
An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, because the claim limitation(s) uses a generic placeholder that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier. Such claim limitation(s) is/are: “processing systems each configured to operate” and “a test management processor configured to generate baseline results, generate additional results, and validate in claim 1.
Because this/these claim limitation(s) is/are being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, it/they is/are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
If applicant does not intend to have this/these limitation(s) interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph, applicant may: (1) amend the claim limitation(s) to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitation(s) recite(s) sufficient structure to perform the claimed function so as to avoid it/them being interpreted under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-7 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention. The corresponding structure for the processing systems and test management processor are not described in the disclosure.
Per claim 1, for the limitation, “one or more transactions are performed by or on a first DIDO,” the specification does not describe the transactions are performed by a DIDO.
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-7 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 applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Per claim 1, it is not clear whether the test platform with processing systems and test management processor is associated with corresponding structure for performing the claimed respective functions. Furthermore, it is unclear how the test and virtual nodes on line 10-13 are related to the transactions. “one or more transactions are performed by or on a first DIDO” is interpreted as: executing the test includes performing one or more tractions by each virtual node on a first DIDO.
Per claims 2-7, these claims are rejected because they depend on claim 1.
Claim limitation “processing systems” and “a test management processor” invokes 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph. However, the written description fails to disclose the corresponding structure, material, or acts for performing the entire claimed function and to clearly link the structure, material, or acts to the function. In the specification, the test platform appears to be a software platform with virtual processing systems and virtual network. The test management processor is not described as a hardware processor, rather, it is described as a virtual processor for the emulation. Therefore, the claim is indefinite and is rejected under 35 U.S.C. 112(b) or pre-AIA 35 U.S.C. 112, second paragraph.
Applicant may:
(a) Amend the claim so that the claim limitation will no longer be interpreted as a limitation under 35 U.S.C. 112(f) or pre-AIA 35 U.S.C. 112, sixth paragraph;
(b) Amend the written description of the specification such that it expressly recites what structure, material, or acts perform the entire claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(c) Amend the written description of the specification such that it clearly links the structure, material, or acts disclosed therein to the function recited in the claim, without introducing any new matter (35 U.S.C. 132(a)).
If applicant is of the opinion that the written description of the specification already implicitly or inherently discloses the corresponding structure, material, or acts and clearly links them to the function so that one of ordinary skill in the art would recognize what structure, material, or acts perform the claimed function, applicant should clarify the record by either:
(a) Amending the written description of the specification such that it expressly recites the corresponding structure, material, or acts for performing the claimed function and clearly links or associates the structure, material, or acts to the claimed function, without introducing any new matter (35 U.S.C. 132(a)); or
(b) Stating on the record what the corresponding structure, material, or acts, which are implicitly or inherently set forth in the written description of the specification, perform the claimed function. For more information, see 37 CFR 1.75(d) and MPEP §§ 608.01(o) and 2181.
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-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-15 of U.S. Patent No. 12086057. Although the claims at issue are not identical, they are not patentably distinct from each other because they are directed to substantially the same invention and recites only obvious differences such as implementing a test platform version, simply omitting/adding steps or elements along with their functions which would have been obvious for one having ordinary skill in the art before the effective filing date of the claimed invention to expedite the method version.
1. A test platform for a distributed system comprising: a plurality of processing systems each configured to operate at least one virtual node in a plurality of virtual nodes; a network coupled to the plurality of processing systems and configured to communicatively couple the plurality of virtual nodes with a test environment, the plurality of virtual nodes being configured to emulate a distributed system that is used to process and manage distributed immutable data objects (DIDOs); and a test management processor provided by the test environment and configured to: generate baseline results by executing a test when each virtual node in the emulated distributed system comprises a validated node, wherein one or more transactions are performed by or on a first DIDO to obtain a modified first DIDO; generate additional results by executing the test after at least one additional virtual node is added to the emulated distributed system, or after one or more virtual nodes in the emulated distributed system have been modified; and validate the at least one additional virtual node or the one or more virtual nodes in the emulated distributed system that have been modified when the baseline results match the additional results (patent 1. A method for testing nodes in a distributed system comprising: configuring a plurality of virtual nodes to emulate a distributed system that is used to process and manage distributed immutable data objects (DIDOs) in the distributed system; initiating, by a test environment, a test of the emulated distributed system, the test including performing one or more transactions on a first DIDO to obtain a modified first DIDO in the emulated distributed system; verifying, by the test environment, the emulated distributed system by comparing the modified first DIDO with a second DIDO that has been generated from the first DIDO by a validated system; generating, by the test environment, baseline results for the test by executing the test when each virtual node in the emulated distributed system comprises a validated node; comparing, by the test environment, the baseline results with additional results obtained by executing the test after adding or modifying at least one virtual node in the emulated distributed system; and validating, by the test environment, the added or modified at least one virtual node or the emulated distributed system when the baseline results match the additional results.)
2. The test platform of claim 1, wherein the test management processor is further configured to: verify the emulated distributed system by comparing the modified first DIDO with a second DIDO that has been generated from the first DIDO by a validated system in which each node has been validated (1. A method for testing nodes in a distributed system comprising: configuring a plurality of virtual nodes to emulate a distributed system that is used to process and manage distributed immutable data objects (DIDOs) in the distributed system; initiating, by a test environment, a test of the emulated distributed system, the test including performing one or more transactions on a first DIDO to obtain a modified first DIDO in the emulated distributed system; verifying, by the test environment, the emulated distributed system by comparing the modified first DIDO with a second DIDO that has been generated from the first DIDO by a validated system; generating, by the test environment, baseline results for the test by executing the test when each virtual node in the emulated distributed system comprises a validated node; comparing, by the test environment, the baseline results with additional results obtained by executing the test after adding or modifying at least one virtual node in the emulated distributed system; and validating, by the test environment, the added or modified at least one virtual node or the emulated distributed system when the baseline results match the additional results).
3. The test platform of claim 2, wherein at least one of the one or more transactions is executed by a virtual node under test in the emulated distributed system, and wherein the test management processor is further configured to: validate the virtual node under test when content of the modified first DIDO corresponds to content of the second DIDO. (3. The method of claim 2, further comprising: validating the node under test when content of the modified first DIDO corresponds to content of the second DIDO).
4. The test platform of claim 2, wherein the first DIDO is a copy of a reference DIDO, wherein the second DIDO is obtained by causing the validated system to perform the one or more transactions on an identical copy of the first DIDO, wherein the validated system is a real-world system, and wherein the reference DIDO, the second DIDO and the one or more transactions are copied from the real-world system at corresponding recorded points-in-time (4. The method of claim 1, wherein the first DIDO is a copy of a reference DIDO and wherein the second DIDO is obtained by causing the validated system to perform the one or more transactions on an identical copy of the first DIDO; 7. The method of claim 4, wherein the validated system is a real-world system, and wherein the reference DIDO, the second DIDO and the one or more transactions are copied from the real-world system at corresponding recorded points-in-time).
5. The test platform of claim 4, wherein the validated system is a real-world system, and wherein the reference DIDO, the second DIDO and the one or more transactions are copied from the real-world system at corresponding recorded points-in-time (7. The method of claim 4, wherein the validated system is a real-world system, and wherein the reference DIDO, the second DIDO and the one or more transactions are copied from the real-world system at corresponding recorded points-in-time).
6. The test platform of claim 1, wherein the test management processor is further configured to: include a twin node in the emulated distributed system, wherein the twin node is addressed using an identifier shared by one or more other twin nodes in the emulated distributed system; compare the baseline results with additional results obtained by executing the test after adding or modifying the twin node; and validate at least one added or modified twin node or the emulated distributed system when the baseline results match the additional results (14. The method of claim 1, further comprising: including a virtual twin node in the emulated distributed system, wherein the virtual twin node is addressed using an identifier shared by one or more other twin nodes in the emulated distributed system; comparing the baseline results with the additional results obtained by executing the test after adding or modifying the virtual twin node; and validating the added or modified virtual twin node or the emulated distributed system when the baseline results match the additional results obtained by executing the test after adding or modifying the virtual twin node; 15. The method claim 1, further comprising: including a physical twin node in the emulated distributed system, wherein the physical twin node is addressed using an identifier shared by one or more other twin nodes in the emulated distributed system; comparing the baseline results with the additional results obtained by executing the test after adding or modifying the physical twin node; and validating the added or modified physical twin node or the emulated distributed system when the baseline results match the additional results obtained by executing the test after adding or modifying the physical twin node).
7. The test platform of claim 6, wherein the twin node comprises a virtual twin node (14. The method of claim 1, further comprising: including a virtual twin node in the emulated distributed system, wherein the virtual twin node is addressed using an identifier shared by one or more other twin nodes in the emulated distributed system; comparing the baseline results with the additional results obtained by executing the test after adding or modifying the virtual twin node; and validating the added or modified virtual twin node or the emulated distributed system when the baseline results match the additional results obtained by executing the test after adding or modifying the virtual twin node).
Per claims 8-20, patent 1-15 corresponds to the instant claims 8-20.
Reasons for Allowance
The following is an examiner’s statement of reasons for allowance:
While the closest art, Choi (cited) teaches emulating a distributed system in a decentralized digital ledger test network for analyzing an execution log to determine test data, compares it with a simulation result to test a smart contract including comparing an output value of a design model with a variable value of data after a transaction, Jin (US 20190251018, cited) discloses a real world validated system and a consensus protocol for appending test blocks to a test blockchain, maintain a copy of the test blockchain, Stow (cited) teaches decrypting information in a distributed ledger, and Lu teaches a blockchain network real-time modes, the prior arts of record, taken alone or in combination do not teach the specific method of testing including: generate baseline results by executing a test when each virtual node in the emulated distributed system comprises a validated node, wherein one or more transactions are performed by or on a first DIDO to obtain a modified first DIDO; generate additional results by executing the test after at least one additional virtual node is added to the emulated distributed system, or after one or more virtual nodes in the emulated distributed system have been modified; and validate the at least one additional virtual node or the one or more virtual nodes in the emulated distributed system that have been modified when the baseline results match the additional results.
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US20210256113 is related to validation of software by blockchains;
CN 111949531 is related to automatic test of block chain network.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to INSUN KANG whose telephone number is (571)272-3724. The examiner can normally be reached M-TR 9am-5pm.
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, Chat Do can be reached on 571-272-3721. 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.
/INSUN KANG/Primary Examiner, Art Unit 2193