# US 12,007,841 B2 · Disaster recover preparedness with trusted firmware boot method over a smart phone > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,007,841 B2 - Document ID: US12007841B2 - Status: Granted - Kind: B2 - Application number: 17/722,762 - Filed: 2022-04-18 - Published: 2023-10-19 - Granted: 2024-06-11 - Earliest claimed: 2022-04-18 - Assignees: Dell Products L.P. - Applicants: Dell Products L.P. - Inventors: Shekar Babu Suryanarayana; Ibrahim Sayyed - Web page: https://patentgrep.com/patent/US12007841B2 ## CPC - G06F 11/1417: {Boot up procedures} - G06F 9/4408: {Boot device selection} - G06F 11/1448: {Management of the data involved in backup or backup restore} - G06F 11/1469: {Backup restoration techniques} - G06F 21/575: {Secure boot} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Methods and systems for managing the operation of data processing systems are disclosed. A data processing system may include a computing device that may enter various operating states by performing various types of startups. Performance the startups may require access to various portions of data which may become unavailable and thereby prevent startup completion. The data processing systems may host a management controller that may facilitating performing a specialized startup process through which unavailable data may be retrieved from other devices via intermediary devices, and may reduce risk in connecting to other devices through verification, validation, and/or other processes. ## Claims ### Claim 1 A computer-implemented method for managing operation of a data processing system, the method comprising: detecting a boot failure of the data processing system; in response to the boot failure and as part of a startup of the data processing system: activating a recovery for the data processing system using a device connectable via a local wireless network, the device being operably connected to an authorization system; connecting to the device via the local wireless network for the recovery; making a first determination that the device is verified; based on the first determination: establishing a connection to the authorization system via the device; obtaining a signed file from the authorization system; making a second determination that a signature of the signed file is verified; and updating the startup of the data processing system using the file based on the second determination. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the connection to the authorization system is secured using a pre-shared key. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, wherein the first determination is made by providing an authorization pattern to the device, the authorization pattern being known to a management controller of the data processing system and the authorization system but not the device. ### Claim 4 (depends on 3) The computer-implemented method of claim 3, wherein the first determination is further made by receiving a one-time password from the device, the one-time password being generated by the authorization system and verifiable by the management controller using a public key for the authorization system. ### Claim 5 (depends on 4) The computer-implemented method of claim 4, further comprising: registering, with the authorization system, the device, the device registration associating the authorization pattern with contact information for the device, the contact information indicating a different communication path for communicating with the device than a communication path through which the authorization pattern is provided to the authorization system. ### Claim 6 (depends on 5) The computer-implemented method of claim 5, wherein the first determination is further made by receiving a signed blob, the signed blob being signed by the authorization system and comprising an identifier for the device, an identifier for the data processing system, and an identifier of a startup management entity hosted by the data processing system. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, wherein the first determination is further made by verifying the signed blob against data stored in the management controller and known to the authorization system. ### Claim 8 A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause a data processing system to perform operations, the operations comprising: detecting a boot failure of the data processing system; in response to the boot failure and as part of a startup of the data processing system: activating a recovery for the data processing system using a device connectable via a local wireless network, the device being operably connected to an authorization system; connecting to the device via the local wireless network for the recovery; making a first determination that the device is verified; based on the first determination: establishing a connection to the authorization system via the device; obtaining a signed file from the authorization system; making a second determination that a signature of the signed file is verified; and updating the startup of the data processing system using the file based on the second determination. ### Claim 9 (depends on 8) The non-transitory machine-readable medium of claim 8, wherein the connection to the authorization system is secured using a pre-shared key. ### Claim 10 (depends on 9) The non-transitory machine-readable medium of claim 9, wherein the first determination is made by providing an authorization pattern to the device, the authorization pattern being known to a management controller of the data processing system and the authorization system but not the device. ### Claim 11 (depends on 10) The non-transitory machine-readable medium of claim 10, wherein the first determination is further made by receiving a one-time password from the device, the one-time password being generated by the authorization system and verifiable by the management controller using a public key for the authorization system. ### Claim 12 (depends on 11) The non-transitory machine-readable medium of claim 11, wherein the operation further comprise: registering, with the authorization system, the device, the device registration associating the authorization pattern with contact information for the device, the contact information indicating a different communication path for communicating with the device than a communication path through which the authorization pattern is provided to the authorization system. ### Claim 13 (depends on 12) The non-transitory machine-readable medium of claim 12, wherein the first determination is further made by receiving a signed blob, the signed blob being signed by the authorization system and comprising an identifier for the device, an identifier for the data processing system, and an identifier of a startup management entity hosted by the data processing system. ### Claim 14 (depends on 13) The non-transitory machine-readable medium of claim 13, wherein the first determination is further made by verifying the signed blob against data stored in the management controller and known to the authorization system. ### Claim 15 A data processing system, comprising: a hardware processor adapted to execute a startup management entity configured to perform a boot of the data processing system; and a management controller configured to: detect a boot failure of the data processing system; in response to the boot failure and as part of a startup of the data processing system: activate a recovery for the data processing system using a device via a local wireless network, the device being operably connected to an authorization system; connect to the device via the local wireless network for the recovery; make a first determination that the device is verified; based on the first determination: establish a connection to the authorization system via the device; obtain a signed file from the authorization system; make a second determination that a signature of the signed file is verified; and update the startup management entity of the data processing system using the file based on the second determination. ### Claim 16 (depends on 15) The data processing system of claim 15, wherein the connection to the authorization system is secured using a pre-shared key. ### Claim 17 (depends on 16) The data processing system of claim 16, wherein the first determination is made by providing an authorization pattern to the device, the authorization pattern being known to a management controller of the data processing system and the authorization system but not the device. ### Claim 18 (depends on 17) The data processing system of claim 17, wherein the first determination is further made by receiving a one-time password from the device, the one-time password being generated by the authorization system and verifiable by the management controller using a public key for the authorization system. ### Claim 19 (depends on 18) The data processing system of claim 18, wherein the management controller is further configured to: register, with the authorization system, the device, the device registration associating the authorization pattern with contact information for the device, the contact information indicating a different communication path for communicating with the device than a communication path through which the authorization pattern is provided to the authorization system. ### Claim 20 (depends on 19) The data processing system of claim 19, wherein the first determination is further made by receiving a signed blob, the signed blob being signed by the authorization system and comprising an identifier for the device, an identifier for the data processing system, and an identifier of a startup management entity hosted by the data processing system.