DETAILED ACTION
Notice of Pre-AIA or AIA Status
1. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Double Patenting
2. 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 either is anticipated by, or would have been obvious over, the reference claim. 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 §§ 706.02(l) (1) - 706.02(l) (3) 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 USPTO Internet website contains terminal disclaimer forms, which may be used. Please visit www.uspto.gov/patent/patents-forms. The 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/process/file/efs/guidance/eTD-info-I.jsp.
3. Claim(s) 1-20 is/are rejected on the ground of nonstatutory double patenting as being unpatentable over claim(s) 1 of U.S. Patent No. 12,153,806 B2. Although the claims at issue are not identical, they are not patentably distinct from each other because Claim(s) 1-2, 6-7, 9, 13-14, 16 & 20 of the current application matches directly to every element of Claim 1-2, 6-8, 13-15 & 20 of U.S. Patent No. 12,153,806 B2.
4. In addition, specifically Independent Claims 1, 7 & 14 is/are rejected on the ground of nonstatutory double patenting as being rejected over claim(s) 1, 7 & 14 of U.S. Patent No. 11,500,994 B2 (Khatri et al.) and in view of U.S. Patent No. 10,698,696 B2 (Raghuram et al.)
The claims are not patentable distinct from each other because it would have been obvious to one having ordinary skill in the art at the time the invention was made to take the teachings of Khatri-Raghuram and apply them on the teachings of Application No. 18/921,247 to a secure one-time programming undo systems that includes a component and a component configuration system.
5. The table below shows only a sample of how each of these claims is anticipated by claims such as Claim 1 of U.S. Patent No. 12,153,806 B2.
Instant Application 18/921,247
US Patent No. 12,153,806 B2
1. A secure one-time programming undo component, comprising:
1. A secure one-time programming undo system, comprising:
a component including a component chassis;
a first component; and
a component configuration system that includes:
a one-time programming subsystem that is configured to:
a secure memory subsystem housed in the component chassis; and
a component engine that is housed in the component chassis, that is coupled to the secure memory subsystem, and that is configured to:
receive, from a component configuration system, first personality configuration information;
provide the first personality configuration information in the secure memory subsystem to configure the component engine to perform first component operations;
provide the first component with first personality configuration information that configures the first component to perform first component operations; and
receive, from the component configuration system, a first one-time programming instruction and first one-time programming undo information;
configure, in response to receiving the first one-time programming instruction, the secure memory subsystem to prevent modification to the first personality configuration information;
perform a one-time programming operation that configures a first component engine in the first component to deny modification requests to modify the first personality configuration information; and
store the first one-time programming undo information in the secure memory subsystem;
a one-time programming undo subsystem that is configured to:
receive, from the component configuration system subsequent to configuring the secure memory subsystem to prevent modification to the first personality configuration information, a one-time programming undo instruction;
perform a one-time programming undo authentication operation; and
authenticate, based on the first one-time programming undo information stored in the secure memory subsystem, the one-time programing undo instruction; and
configure, in response to authenticating the first one-time programming instruction, the secure memory subsystem to allow modification to the first personality configuration information.
transmit a one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the first component,
wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the first component such that the first component executes the one-time programming undo instruction that reconfigures the first component engine in the first component to allow modification requests to modify the first personality configuration information.
2. The system of claim 1, wherein the component engine is configured to: receive, from the component configuration system subsequent to configuring the secure memory subsystem to allow modification to the first personality configuration information, second personality configuration information; provide the second personality configuration information in the secure memory subsystem in place of the first personality configuration information to configure the component engine to perform second component operations that are different than the first component operations; receive, from the component configuration system, a second one-time programming instruction and second one-time programming undo information; configure, in response to receiving the second one-time programming instruction, the secure memory subsystem to prevent modification to the second personality configuration information; and store the second one-time programming undo information in the secure memory subsystem.
2. The system of claim 1, further comprising: a second component that is the same type of component as the first component, wherein the one-time programming subsystem is configured to: provide the second component with second personality configuration information that is different than the first personality configuration information and that configures the second component to perform second component operations that are different than the first component operations; and perform the one-time programming operation that configures a second component engine in the second component to deny modification requests to modify the second personality configuration information, and wherein the one-time programming undo subsystem is configured to: perform the one-time programming undo authentication operation; and transmit the one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the second component, wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the second component such that the second component executes the one-time programming undo instruction that reconfigures the second component engine in the second component to allow modification requests to modify the second personality configuration information.
3. The system of claim 2, wherein the first component operations include encryption operations that prevent the reading and writing of data without authentication credentials, and wherein the second component operations allow the reading and writing of data without authentication credentials.
4. The system of claim 1, wherein the first one-time programming undo information is a first code that is stored in the secure memory subsystem, the one-time programming undo instruction includes a second code, and the one-time programing undo instruction is authenticated based on the second code matching the first code.
5. The system of claim 1, wherein the first one-time programming undo information is configured for use in enabling an authenticated communication session, and the one-time programing undo instruction is at least partially authenticated in response to being received via the authenticated communication session enabled using the first one-time programming undo information.
6. The system of claim 1, wherein the component is a storage device.
6. The system of claim 1, wherein the first component is a storage device, and wherein the first personality configuration information either configures the first component to enable the first component to perform security locking operations, or configures the first component to prevent the first component from performing security locking operations.
7. An Information Handling System (IHS), comprising: a processing system; and a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a component engine that is configured to: receive, from a component configuration system that is coupled to the processing system, first personality configuration information; provide the first personality configuration information in a secure memory subsystem that is coupled to the processing system to configure the component engine to perform first component operations; receive, from the component configuration system, a first one-time programming instruction and first one-time programming undo information; configure, in response to receiving the first one-time programming instruction, the secure memory subsystem to prevent modification to the first personality configuration information; store the first one-time programming undo information in the secure memory subsystem; receive, from the component configuration system subsequent to configuring the secure memory subsystem to prevent modification to the first personality configuration information, a one-time programming undo instruction; authenticate, based on the first one-time programming undo information stored in the secure memory subsystem, the one-time programing undo instruction; and configure, in response to authenticating the first one-time programming instruction, the secure memory subsystem to allow modification to the first personality configuration information.
7. An Information Handling System (IHS), comprising: a processing system; and a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a one-time programming subsystem that is configured to: provide a first component with first personality configuration information that configures the first component to perform first component operations; and perform a one-time programming operation that configures a first component engine in the first component to deny modification requests to modify the first personality configuration information, and wherein the memory system includes instructions that, when executed by the processing system, cause the processing system to provide a one-time programming undo subsystem that is configured to: perform a one-time programming undo authentication operation; and transmit a one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the first component, wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the first component such that the first component executes the one-time programming undo instruction that reconfigures the first component engine in the first component to allow modification requests to modify the first personality configuration information.
8. The IHS of claim 7, wherein the first component operations include encryption operations that prevent the reading and writing of data without authentication credentials.
9. The IHS of claim 7, wherein the component engine is configured to: receive, from the component configuration system subsequent to configuring the secure memory subsystem to allow modification to the first personality configuration information, second personality configuration information; provide the second personality configuration information in the secure memory subsystem in place of the first personality configuration information to configure the component engine to perform second component operations that are different than the first component operations; receive, from the component configuration system, a second one-time programming instruction and second one-time programming undo information; configure, in response to receiving the second one-time programming instruction, the secure memory subsystem to prevent modification to the second personality configuration information; and store the second one-time programming undo information in the secure memory subsystem.
8. The IHS of claim 7, wherein the one-time programming subsystem is configured to: provide a second component with second personality configuration information that is different than the first personality configuration information and that configures the second component to perform second component operations that are different than the first component operations; and perform the one-time programming operation that configures a second component engine in the second component to deny modification requests to modify the second personality configuration information, and wherein the one-time programming undo subsystem is configured to: perform the one-time programming undo authentication operation; and transmit the one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the second component, wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the second component such that the second component executes the one-time programming undo instruction that reconfigures the second component engine in the second component to allow modification requests to modify the second personality configuration information.
10. The IHS of claim 9, wherein the second component operations allow the reading and writing of data without authentication credentials.
11. The IHS of claim 7, wherein the first one-time programming undo information is a first code that is stored in the secure memory subsystem, the one-time programming undo instruction includes a second code, and the one-time programing undo instruction is authenticated based on the second code matching the first code.
12. The IHS of claim 7, wherein the first one-time programming undo information is configured for use in enabling an authenticated communication session, and the one-time programing undo instruction is at least partially authenticated in response to being received via the authenticated communication session enabled using the first one-time programming undo information.
13. The IHS of claim 7, wherein the IHS is a storage device.
13. The IHS of claim 7, wherein the first component is a storage device, and wherein the first personality configuration information configures the first component to prevent the first component from performing security locking operations.
14. A method for securely undoing one-time programming of a component, comprising: receiving, by a component from a component configuration system, first personality configuration information; providing, by the component, the first personality configuration information in a secure memory subsystem to configure the component to perform first component operations; receiving, by the component from the component configuration system, a first one-time programming instruction and first one-time programming undo information; configuring, by the component in response to receiving the first one-time programming instruction, the secure memory subsystem to prevent modification to the first personality configuration information; storing, by the component, the first one-time programming undo information in the secure memory subsystem; receiving, by the component from the component configuration system subsequent to configuring the secure memory subsystem to prevent modification to the first personality configuration information, a one-time programming undo instruction; authenticating, by the component based on the first one-time programming undo information stored in the secure memory subsystem, the one-time programing undo instruction; and configuring, by the component in response to authenticating the first one-time programming instruction, the secure memory subsystem to allow modification to the first personality configuration information.
14. A method for securely undoing one-time programming, comprising: providing, by a one-time programming subsystem, a first component with first personality configuration information that configures the first component to perform first component operations; performing, by the one-time programming subsystem, a one-time programming operation that configures a first component engine in the first component to deny modification requests to modify the first personality configuration information; performing, by a one-time programming undo subsystem, a one-time programming undo authentication operation; and transmitting, by the one-time programming undo subsystem, a one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the first component, wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the first component such that the first component executes the one-time programming undo instruction that reconfigures the first component engine in the first component to allow modification requests to modify the first personality configuration information.
15. The method of claim 14, wherein the first component operations include encryption operations that prevent the reading and writing of data without authentication credentials.
16. The method of claim 14, further comprising: receiving, by the component from the component configuration system subsequent to configuring the secure memory subsystem to allow modification to the first personality configuration information, second personality configuration information; providing, by the component, the second personality configuration information in the secure memory subsystem in place of the first personality configuration information to configure the component to perform second component operations that are different than the first component operations; receiving, by the component from the component configuration system, a second one-time programming instruction and second one-time programming undo information; configuring, by the component in response to receiving the second one-time programming instruction, the secure memory subsystem to prevent modification to the second personality configuration information; and storing, by the component, the second one-time programming undo information in the secure memory subsystem.
15. The method of claim 14, further comprising: providing, by the one-time programming subsystem, a second component with second personality configuration information that is different than the first personality configuration information and that configures the second component to perform second component operations that are different than the first component operations; performing, by the one-time programming subsystem, the one-time programming operation that configures a second component engine in the second component to deny modification requests to modify the second personality configuration information performing, by the one-time programming undo subsystem, the one-time programming undo authentication operation; and transmitting, by the one-time programming undo subsystem, the one-time programming undo instruction that is associated with the one-time programming undo authentication operation to the second component, wherein the one-time programming undo authentication operation is configured to authenticate the one-time programming undo instruction to the second component such that the second component executes the one-time programming undo instruction that reconfigures the second component engine in the second component to allow modification requests to modify the second personality configuration information.
17. The method of claim 16, wherein the second component operations allow the reading and writing of data without authentication credentials.
18. The method of claim 14, wherein the first one-time programming undo information is a first code that is stored in the secure memory subsystem, the one-time programming undo instruction includes a second code, and the one-time programing undo instruction is authenticated based on the second code matching the first code.
19. The method of claim 14, wherein the first one-time programming undo information is configured for use in enabling an authenticated communication session, and the one-time programing undo instruction is at least partially authenticated in response to being received via the authenticated communication session enabled using the first one-time programming undo information.
20. The method of claim 14, wherein the component is a storage device.
20. The method of claim 14, further comprising: wherein the first component is a storage device, and wherein the first personality configuration information configures the first component to prevent the first component from performing security locking operations.
Conclusion
6. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Khatri et al. (US 11,500,994 B2)
Raghuram et al. (US 10,698,696 B2
BeSerra et al. (US 9,984,021 B1)
Kumar et al. (US 11,582,033 B2)
7. Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHRISTOPHER B ROBINSON whose telephone number is (571)270-0702. The examiner can normally be reached M-F 7:00-3:00 EST.
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, Nicholas R Taylor can be reached at 571-272-3889. 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.
/CHRISTOPHER B ROBINSON/Primary Examiner, Art Unit 2443