Device management method and electronic device

Abstract

The application discloses a device management method and an electronic device. The device management method is applied to the electronic device and comprises the following steps: in response to the start of a basic input / output system, monitoring whether a target hot key is triggered; in the case that the target hot key is triggered, calling a target program; wherein the target program is stored in a local storage medium; sending a data request to the cloud through the target program; receiving a management data packet returned by the cloud in response to the data request; and managing the electronic device based on the management data packet.

Description

Technical Field

[0001] This application relates to the field of equipment management technology, and in particular to an equipment management method and electronic device. Background Technology

[0002] Currently, the software storage methods for various management functions of electronic devices, such as backup and recovery functions and security vulnerability patches, include: 1. Stored on the hard drive where the local operating system is located or on a separate hard drive. However, with this storage method, the management function of the electronic device will immediately fail if the hard drive fails or the hard drive partition is damaged. 2. Stored in the hard drive's secure zone. Although the secure zone provides a storage space on the hard drive that can be prevented from being deleted or formatted, it requires customization of the SSD hard drive controller, resulting in higher development and usage costs. Summary of the Invention

[0003] The purpose of this application is to provide a device management method and an electronic device.

[0004] In a first aspect, embodiments of this application provide a device management method applied to electronic devices, the device management method comprising: In response to the startup of the basic input / output system, monitor whether the target hotkey has been triggered; When the target hotkey is triggered, the target program is invoked; wherein the target program is stored in a local storage medium. The target program sends a data request to the cloud. Receive the management data packet returned by the cloud in response to the data request; Electronic devices are managed based on the aforementioned management data packets.

[0005] In one possible implementation, the device management method further includes: If the target hotkey is triggered, the startup process of the operating system is interrupted.

[0006] In one possible implementation, invoking the target program includes: The verification information of the target program is read from the local storage medium; wherein the verification information includes at least one of the following: the signature and version information of the target program; If the verification information passes verification, the target program is invoked.

[0007] In one possible implementation, sending a data request to the cloud via the target program includes: The target program acquires network information of an electronic device; wherein the network information includes at least one of the following: network card information, Internet Protocol address, and domain name; Construct a network environment based on the aforementioned network information; Based on the network environment, a data request is sent to the cloud.

[0008] In one possible implementation, sending a data request to the cloud based on the network environment includes: Obtain the attribute information of the electronic device; wherein the attribute information includes at least the device serial number, device model, motherboard identifier, permission identifier, current startup status, and hardware parameters; A data request is generated based on the attribute information.

[0009] In one possible implementation, the electronic device based on the management data packet includes: The management data packet is verified using a preset verification method; wherein the preset verification method includes at least signature verification and digest verification. If the management data packet passes verification, the management data packet is loaded into the memory space of the electronic device; If the management data packet includes a kernel data packet, the operating system of the electronic device is started based on the kernel data packet; When the management data package includes a kernel data package and various application data packages running on it, the operating system of the electronic device is started based on the kernel data package, and the electronic device is controlled to perform corresponding functions based on the various application data packages.

[0010] In one possible implementation, The management data packet is generated by the cloud after verifying the data request. The management data packet corresponds to the attribute information of the electronic device and can complete the startup of the operating system of the electronic device.

[0011] In one possible implementation, the device management method further includes: If the management data packet fails verification, determine whether the electronic device's local storage space contains cached data packets; If so, the electronic device is managed based on the cached data packets; If not, then activate the rescue mode of the electronic device.

[0012] In one possible implementation, the device management method further includes: In the event that the management electronic device fails to start, a startup failure log is generated; Extract the failure factors from the startup failure log; Report the startup failure log and / or the failure factors.

[0013] Secondly, embodiments of this application also provide an electronic device, including: The basic input / output system monitors whether a target hotkey is triggered upon power-on; if the target hotkey is triggered, the target program is invoked; wherein the target program is stored in local storage medium. The target program sends a data request to the cloud; receives a management data packet returned by the cloud in response to the data request; and manages electronic devices based on the management data packet. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 A flowchart of a device management method provided in this application is shown; Figure 2 This application provides a flowchart of a method for sending a data request to the cloud via a target program. Figure 3 A schematic diagram of the structure of an electronic device provided in this application is shown. Detailed Implementation

[0016] Various embodiments and features of this application are described herein with reference to the accompanying drawings.

[0017] It should be understood that various modifications can be made to the embodiments described herein. Therefore, the above description should not be considered as limiting, but merely as an example of embodiments. Other modifications within the scope and spirit of this application will be apparent to those skilled in the art.

[0018] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present application and, together with the general description of the present application given above and the detailed description of the embodiments given below, serve to explain the principles of the present application.

[0019] These and other features of this application will become apparent from the following description of preferred forms of embodiments given as non-limiting examples, with reference to the accompanying drawings.

[0020] It should also be understood that although this application has been described with reference to some specific examples, those skilled in the art can certainly implement many other equivalent forms of this application, which have the features described in the claims and are therefore all within the scope of protection defined herein.

[0021] The above and other aspects, features and advantages of this application will become more apparent when taken in conjunction with the accompanying drawings and in view of the following detailed description.

[0022] Specific embodiments of this application are described thereafter with reference to the accompanying drawings; however, it should be understood that the claimed embodiments are merely examples of this application, which can be implemented in various ways. Well-known and / or repeated functions and structures are not described in detail to avoid unnecessary or redundant details that could obscure the application. Therefore, the specific structural and functional details claimed herein are not intended to be limiting, but merely serve as the basis and representative basis for the claims to teach those skilled in the art to use this application in a variety of substantially any suitable detailed structures.

[0023] This specification may use the phrases “in one embodiment,” “in another embodiment,” “in yet another embodiment,” or “in other embodiments,” all of which may refer to one or more of the same or different embodiments according to this application.

[0024] To facilitate understanding of this application, a detailed description of the equipment management method provided herein will follow. As an example, Figure 1 A flowchart of a device management method provided in an embodiment of this application is shown, wherein the steps specifically include S101-S105.

[0025] S101 responds to the startup of the basic input / output system by monitoring whether the target hotkey has been triggered.

[0026] For example, after a user presses the power button on an electronic device, the basic input / output system powers on and starts up, performing tasks such as power-on self-test, initializing the basic environment, initializing DDR memory (RAM), basic bus (PCIe / SPI), and initializing peripherals (such as graphics cards, network cards, NVMe / SATA hard drives, USB, etc.) to prepare for the subsequent startup of the operating system.

[0027] Simultaneously, in response to the startup of the basic input / output system, it monitors whether the target hotkey has been triggered. The target hotkey is pre-defined, such as F2, F3, or other keys.

[0028] It should be noted that the basic input / output system in this application embodiment can be a BIOS stored on a local disk or a Unified Extensible Firmware Interface (UEFI) stored on the motherboard. The basic input / output system will be different under different systems, and this application embodiment does not limit it.

[0029] S102, when the target hotkey is triggered, the target program is invoked; wherein, the target program is stored in the local storage medium.

[0030] When a user presses a target hotkey, the Basic Input / Output System (BIOS) detects that the hotkey has been triggered. In response, the target program is invoked, and the operating system's boot process is interrupted. Conversely, if no target hotkey is detected, the normal operating system boot process is executed. Pre-setting target hotkeys simplifies user operation.

[0031] The target program is stored on a local storage medium, which can be an independent flash memory card used to store and run the target program. Because the data is not lost after power failure, the target program is effectively guaranteed not to be erased due to device failure.

[0032] For example, to prevent the target program from being maliciously tampered with and causing security risks (such as virus implantation or data leakage) when the electronic device calls the tampered target program, the basic input / output system first reads the verification information of the target program from the local storage medium to verify the verification information of the target program, and calls the target program only if the verification information passes the verification.

[0033] If the verification information passes, it indicates that the target program has not been maliciously tampered with. Conversely, if the verification information fails, it indicates that the target program may have been maliciously tampered with, posing a certain security risk. In this case, the target program will not be invoked. This, to a certain extent, ensures the security of electronic devices.

[0034] The verification information includes at least one of the following: the signature of the target program and its version information. Optionally, one or more of the target program's identification information, its storage address on the local storage medium, and its version information can be encrypted in advance to obtain the signature of the target program. The encryption calculation can be performed using any encryption algorithm among hash digest algorithms, symmetric encryption algorithms, and asymmetric encryption algorithms.

[0035] For example, when verifying the verification information of the target program, one or more of the target program's identification information, storage address in the local storage medium, and version information can be obtained again for encryption calculation. Of course, the encryption algorithm is pre-specified. After the signature is calculated, it is compared with the signature stored in the local storage medium. If they match, the verification information passes the verification.

[0036] As another example, when verifying the version of a target program, it is also possible to check whether the version is a compliant version (released or certified by the licensor) or a specified version (such as user-specified or the latest version). If the version of the target program is a compliant version and a specified version, the verification information passes the verification.

[0037] S103 sends a data request to the cloud through the target program.

[0038] Optionally, the target program in this application embodiment can establish a communication connection between the terminal (the electronic device to which the target program belongs) and the cloud. After the target program is called, that is, after the target program is run, a communication connection between the electronic device and the cloud is established through the target program, and a data request is sent to the cloud.

[0039] The data request is used to request the cloud to return a data packet for the electronic device to start running.

[0040] S104 receives the management data packet returned by the cloud response data request.

[0041] Optionally, after receiving a data request from the target program of the electronic device, the cloud responds to the data request and generates a corresponding management data packet to return to the electronic device.

[0042] The management data packet is generated by the cloud after verifying the data request. Optionally, when the cloud verifies the data request, it may determine, for example, whether the current startup status included in the requested data indicates that the electronic device is in management mode; if not, it will directly determine that the verification has failed; it may also determine whether the device identity information included in the requested data has the necessary permissions; if not, it will directly determine that the verification has failed.

[0043] Once the cloud verifies that the data request has been verified, the cloud selects one or more of the corresponding data, such as Linux kernel, initrd, driver package, functional module, policy configuration, and permission scope, based on the device identity information and motherboard identity information included in the data request, to generate a management data package and return it to the electronic device.

[0044] In other words, the management data packets correspond to the attribute information of the electronic devices. For example, different drivers are returned for different device models; different management capabilities are issued for different permission levels; and different management modes are switched for different startup states, such as normal management mode, recovery mode, deployment mode, and diagnostic mode. Optionally, an AI orchestration engine can also be introduced into the cloud, for example, to comprehensively analyze the device's historical operation logs, fault records, hardware compatibility matrices, and policy templates to more intelligently select appropriate data, thereby improving the first-time startup success rate and management accuracy; and the cloud returns appropriate management data packets based on the differentiated attribute information of the electronic devices, effectively improving the flexibility and accuracy of adaptation.

[0045] S105, an electronic device managed based on management data packets.

[0046] The management data packet is responsible for booting the operating system of the electronic device. Based on this, after receiving the management data packet returned from the cloud, the electronic device is managed accordingly. Managing the electronic device includes not only booting the management system, but also scheduling hardware, providing low-level disk / network / hardware read capabilities, performing device management, image restoration, remote diagnostics, hardware detection, asset management, and policy updates.

[0047] Considering the possibility of tampering or packet loss during the process of returning management data packets from the cloud to electronic devices, a preset verification method is used to verify the management data packets before managing the electronic devices. This preset verification method includes at least signature verification and digest verification. For example, when the preset verification method is signature verification, the target program uses the public key stored in the electronic device to decrypt the signature generated by the cloud's private key and compares it with the original digest. If the decryption is successful and the digests match, it is determined that the management data packet was issued by the authorized party, meaning the management data packet has passed verification. When the preset verification method is digest verification, the target program performs encrypted calculations on the kernel included in the received management data packet, such as calculating the MD5 / SHA256 value, and then compares it with the standard digest returned from the remote end. If they match, it is determined that the management data packet is complete and has not been modified or is missing, meaning the management data packet has passed verification.

[0048] Once the management data package passes verification, it is loaded into the electronic device's memory space, such as RAM, to manage the device. The management data package can include a kernel data package, and may also include the kernel data package and various application data packages running on it. The kernel data package can include the Linux kernel, initrd, and driver packages. Considering the limited storage space of local storage media, the kernel data package preferably includes a trimmed-down version of the Linux kernel; that is, as long as the kernel data package can provide a basic operating system runtime environment, it is sufficient. Various application data packages can include parameter configuration modules, policy customization modules, data backup modules, and other application modules. These application data packages enable various functions, enriching the capabilities of the electronic device and ensuring its software and hardware security.

[0049] After the management data package is loaded into the memory space of the electronic device, if the management data package includes a kernel data package, the operating system of the electronic device is started based on the kernel data package. For example, the Linux kernel included in the kernel data package is run, such as decompressed and initialized, and the initrd in memory is mounted as the root directory. At this time, the system execution control of the electronic device is transferred from the BIOS or UEFI firmware to the Linux kernel, and the electronic device enters the Linux kernel type management system.

[0050] Furthermore, after the operating system boots up and runs, it can obtain information about various components of the electronic device, such as motherboard model, CPU model, memory size, network card information, graphics card information, sound card information, hard drive serial number, chassis information, information about each interface / serial port, PCI / PCIe devices, and local storage media information. Based on its own needs and the information obtained about each component, the operating system can send requests for various application data packages to the cloud. Of course, the cloud also needs to verify the request. After verification, it returns the corresponding application data package. The operating system verifies the received application data, and after verification, installs and runs each application data package. Here, the cloud's verification of the request and the operating system's verification of the application data can be referred to the above description, and will not be elaborated further.

[0051] It should be noted that some application data packages can be transmitted directly to electronic devices from the cloud or the publishing end, meaning they cannot be requested through the operating system. Examples include system upgrade data packages and vulnerability patches. Of course, application data packages transmitted directly from the cloud or the publishing end also need to be verified to ensure the security of the electronic device.

[0052] Of course, when managing data packets, including kernel data packets and various application data packets running on them, one can directly start the operating system of the electronic device based on the kernel data packet and control the electronic device to achieve the corresponding functions based on various application data packets.

[0053] For example, the Linux kernel type management system controls the electronic devices to perform corresponding functions, including at least system data backup, image recovery, batch deployment, remote diagnostics, hardware detection, asset management, policy updates, and log transmission. Device management includes software and hardware layer coordination and scheduling, and space configuration; image recovery includes accessing disk partitions, backing up the entire system, and one-click system image recovery from faulty devices; batch deployment includes automatic partitioning, automatic system installation, and simultaneous batch installation on multiple terminals; remote diagnostics includes remotely connecting to devices, remotely reading processes, disk logs, and network status, executing hardware troubleshooting commands, and locating blue screens, crashes, and startup anomalies. Hardware detection includes reading hardware information such as CPU, memory, disk, network card, motherboard serial number, temperature sensor, and SMBIOS; detecting bad sectors on the disk, hardware failures, and component compatibility; and outputting a hardware health report. Asset management includes collecting information such as motherboard serial number, device serial number, device model, hardware model, memory size, and disk capacity; compiling a hardware asset ledger and uploading it to the cloud to achieve unified inventory of terminal hardware across the company. Policy updates include remotely distributing configurations, security policies, firewall rules, etc., and batch modifying the configuration parameters of electronic devices. Log feedback includes collecting kernel logs and application logs, uploading local logs to a remote server for storage, and centralized fault viewing.

[0054] This application embodiment triggers cloud management via a pre-set target hotkey. Specifically, it calls a target program stored on a local storage medium, which is an independent flash memory card. The target program stored on this card is unaffected by hard drive formatting or system reinstallation. Furthermore, the target program is only used to establish a communication connection between the electronic device and the cloud, occupying minimal storage space and therefore not limited by the space constraints of the local storage medium. Moreover, local storage media are widely available, thus reducing hardware costs and ensuring compatibility with various types of electronic devices, such as desktops, laptops, and wired IoT devices.

[0055] This application embodiment also includes using a basic input / output system to verify the target program, using the cloud to verify data requests, and using the target program to verify management data packets, in order to form a complete chain of trust, ensuring the validity, integrity, and security of the data, thereby enabling the management of electronic devices such as startup, backup, and asset configuration.

[0056] For example, Figure 2A flowchart of a method for sending a data request to the cloud through a target program is shown, wherein the steps specifically include S201-S203.

[0057] S201, Obtain network information of electronic device through target program; wherein, network information includes at least one of the following: network card information, Internet Protocol address and domain name.

[0058] S202, Constructing a network environment based on network information.

[0059] S203 sends data requests to the cloud based on the network environment.

[0060] For example, after the target program runs, it can obtain the network information of the electronic device. This network information includes at least one of the following: network interface card (NIC) information, Internet Protocol (IP) address, and domain name. Optionally, the NIC information indicates whether the NIC is available and may also include the MAC address of an available NIC; the IP address can be a dynamic IP address (e.g., assigned in real-time based on Dynamic Host Configuration Protocol) or a fixed IP address (e.g., manually set by the user); the domain name corresponds to one or more IP addresses and needs to be resolved through the Domain Name System (DNS) to be converted into a real IP address. Of course, the network information of the electronic device may also include subnet, gateway, and cloud server addresses, etc.

[0061] After obtaining network information from electronic devices, a network environment is constructed based on this information, and data requests are sent to the cloud based on this network environment.

[0062] When constructing the network environment, the target program can also synchronously obtain the attribute information of electronic devices. Based on this, when sending a data request to the cloud based on the network environment, it obtains the attribute information of the electronic devices and generates a data request based on the attribute information.

[0063] In this embodiment, the attribute information of the electronic device includes at least the device serial number, device model, motherboard identifier, permission identifier, current startup status, and hardware parameters. The device serial number, device model, motherboard identifier, and permission identifier represent the identity information of the device or motherboard. Hardware parameters include attribute information of the hard drive and memory, such as serial number and size. The device serial number, device model, motherboard identifier, permission identifier, and hardware parameters are identified when the Basic Input / Output System (BIOS) starts, and the target program can directly query and obtain them based on the BIOS. The current startup status is determined in real time, indicating whether the electronic device is currently in management mode, operating system running mode, or other state. Of course, the attribute information of the electronic device may also include extended fields such as CPU type, network card type, disk mode, and organizational tenant identifier.

[0064] In another example, there are situations such as the target program failing verification, the target program failing to build the network environment, the data request failing to be sent, or the management data packet failing verification (such as failure to receive, modification, or corruption). Based on this, this application further sets up a setting to determine whether there is a cached data packet stored in the local storage space of the electronic device when any of the above situations occur. The cached data packet can be the image data cached to the local storage space when the electronic device was last started, or it can be the image data manually configured by the user in advance.

[0065] If cached data packets are stored in the local storage space, electronic devices are managed based on these cached data packets, including startup, backup, and asset configuration. If no cached data packets are stored in the local storage space or the cached data packets are corrupted, the electronic device's rescue mode is activated to ensure that the terminal has a minimum level of management and recovery capabilities.

[0066] In the rescue mode, electronic devices retain only basic functions such as basic hardware detection, network diagnostics, log export, and manual recovery access, and operate on Double Data Rate Random Access Memory (DRAM). Random Access Memory (DDR) does not rely on a local solid-state drive.

[0067] This application embodiment sets up a system that manages electronic devices based on cached data packets stored in local storage when any of the following situations occur: target program fails verification, target program fails to build network environment, data request fails to send, or management data packet fails verification. Furthermore, when no cached data packets are stored in local storage or the cached data packets are corrupted, a rescue mode for the electronic device is activated. Through this layered caching and disaster recovery path design, the minimum availability of the electronic device can be ensured to a certain extent.

[0068] Furthermore, if the rescue mode of the electronic device cannot be started, a message will be displayed indicating that the user's electronic device has failed to start.

[0069] In the event of a failed startup of an electronic device, a startup failure log is generated and analyzed to extract the failure factors, such as DNS resolution failure, timeout of the management data packet returned by the cloud, signature mismatch, digest error, driver incompatibility, and cache corruption.

[0070] The startup failure logs and / or failure factors will be reported for analysis and optimization by the operations and maintenance platform. Of course, if the current electronic device can communicate with the cloud, the startup failure logs and / or failure factors will be reported directly to the cloud; if the current electronic device cannot communicate with the cloud, the startup failure logs and / or failure factors will be reported to the cloud after the network is restored.

[0071] On the other hand, this application also provides an electronic device. Since the principle of solving the problem by the electronic device in this application is similar to the device management method described above, the implementation of the electronic device can refer to the implementation of the device management method described above, and the repeated parts will not be described again.

[0072] For example, Figure 3 A schematic diagram of the electronic device is shown, for reference. Figure 3 The electronic device includes: The basic input / output system monitors whether a target hotkey is triggered upon power-on; if the target hotkey is triggered, the target program is invoked; wherein the target program is stored in local storage medium. The target program sends a data request to the cloud; receives a management data packet returned by the cloud in response to the data request; and manages electronic devices based on the management data packet.

[0073] As another example, the basic input / output system interrupts the operating system's startup process when the target hotkey is triggered.

[0074] As another example, when a basic input / output system calls a target program, it includes: The verification information of the target program is read from the local storage medium; wherein the verification information includes at least one of the following: the signature and version information of the target program; If the verification information passes verification, the target program is invoked.

[0075] As another example, when the target program sends a data request to the cloud, it includes: The target program acquires network information of an electronic device; wherein the network information includes at least one of the following: network card information, Internet Protocol address, and domain name; Construct a network environment based on the aforementioned network information; Based on the network environment, a data request is sent to the cloud.

[0076] As another example, when the target program sends a data request to the cloud based on the network environment, it includes: Obtain the attribute information of the electronic device; wherein the attribute information includes at least the device serial number, device model, motherboard identifier, permission identifier, current startup status, and hardware parameters; A data request is generated based on the attribute information.

[0077] As another example, when the target program manages an electronic device based on the management data packet, it includes: The management data packet is verified using a preset verification method; wherein the preset verification method includes at least signature verification and digest verification. If the management data packet passes verification, the management data packet is loaded into the memory space of the electronic device; If the management data packet includes a kernel data packet, the operating system of the electronic device is started based on the kernel data packet; When the management data package includes a kernel data package and various application data packages running on it, the operating system of the electronic device is started based on the kernel data package, and the electronic device is controlled to perform corresponding functions based on the various application data packages.

[0078] Another example is the target program: If the management data packet fails verification, determine whether the electronic device's local storage space contains cached data packets; If so, the electronic device is managed based on the cached data packets; If not, then activate the rescue mode of the electronic device.

[0079] Another example is the target program: In the event that the management electronic device fails to start, a startup failure log is generated; Extract the failure factors from the startup failure log; Report the startup failure log and / or the failure factors.

[0080] In another aspect, embodiments of this application also provide a computer program product, which is a computer-readable medium storing a computer program. When executed by a processor, the computer program implements the method provided in any embodiment of the present invention, including the following steps S11 to S15: S11, responds to the startup of the basic input / output system, and monitors whether the target hotkey is triggered; S12, when the target hotkey is triggered, the target program is invoked; wherein the target program is stored in the local storage medium; S13, Send a data request to the cloud through the target program; S14, Receive the management data packet returned by the cloud in response to the data request; S15, manage the electronic device based on the management data packet.

[0081] In another aspect, embodiments of this application also provide a storage medium carrying one or more computer programs, which, when executed by a processor, implement the method provided in any embodiment of the present invention, including the following steps S21 to S25: S21, responding to the startup of the basic input / output system, monitors whether the target hotkey has been triggered; S22, when the target hotkey is triggered, the target program is invoked; wherein the target program is stored in a local storage medium; S23, send a data request to the cloud through the target program; S24, Receive the management data packet returned by the cloud in response to the data request; S25, manage the electronic device based on the management data packet.

[0082] Optionally, in this embodiment, the aforementioned computer program product and storage medium may include, but are not limited to, various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk. Optionally, in this embodiment, the processor executes the method steps described in the above embodiments according to the program code stored in the computer program product. Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, which will not be repeated here. Obviously, those skilled in the art should understand that the various modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed on a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be executed in a different order than those described here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any specific hardware and software combination.

[0083] Furthermore, although exemplary embodiments have been described herein, their scope includes any and all embodiments based on this application that have equivalent elements, modifications, omissions, combinations (e.g., schemes involving intersections of various embodiments), adaptations, or alterations. Elements in the claims will be interpreted broadly based on the language used in the claims and are not limited to the examples described in this specification or during the implementation of this application, which will be interpreted as non-exclusive. Therefore, this specification and examples are intended to be considered illustrative only, and the true scope and spirit are indicated by the following claims and the full scope of their equivalents.

[0084] The above description is intended to be illustrative and not restrictive. For example, the above examples (or one or more of them) can be used in combination with each other. Other embodiments may be used by those skilled in the art upon reading the above description. Furthermore, in the above detailed description, various features may be grouped together to simplify the application. This should not be construed as an intention that a disclosed feature not claimed is necessary for any claim. Rather, the subject matter of this application may be less than all the features of a particular disclosed embodiment. Thus, the following claims are incorporated herein by reference as examples or embodiments, wherein each claim is an independent, separate embodiment, and these embodiments are contemplated as being possible in various combinations or arrangements. The scope of this application should be determined by reference to the appended claims and the full scope of their equivalents.

[0085] The foregoing has described in detail several embodiments of this application, but this application is not limited to these specific embodiments. Those skilled in the art can make various variations and modifications based on the concept of this application, and all such variations and modifications should fall within the scope of protection claimed in this application.

Claims

1. A device management method applied to electronic devices, the device management method comprising: In response to the startup of the basic input / output system, monitor whether the target hotkey has been triggered; When the target hotkey is triggered, the target program is invoked; wherein the target program is stored in a local storage medium. The target program sends a data request to the cloud. Receive the management data packet returned by the cloud in response to the data request; Electronic devices are managed based on the aforementioned management data packets.

2. The equipment management method according to claim 1 further includes: If the target hotkey is triggered, the operating system startup process is interrupted.

3. The device management method according to claim 1, invoking the target program, includes: The verification information of the target program is read from the local storage medium; wherein the verification information includes at least one of the following: the signature and version information of the target program; If the verification information passes verification, the target program is invoked.

4. The device management method according to claim 1, wherein sending a data request to the cloud through the target program includes: The target program acquires network information of an electronic device; wherein the network information includes at least one of the following: network card information, Internet Protocol address, and domain name; Construct a network environment based on the aforementioned network information; Based on the network environment, a data request is sent to the cloud.

5. The device management method according to claim 4, wherein sending a data request to the cloud based on the network environment includes: Obtain the attribute information of the electronic device; wherein the attribute information includes at least the device serial number, device model, motherboard identifier, permission identifier, current startup status, and hardware parameters; A data request is generated based on the attribute information.

6. The device management method according to claim 1, wherein managing the electronic device based on the management data packet comprises: The management data packet is verified using a preset verification method; wherein the preset verification method includes at least signature verification and digest verification. If the management data packet passes verification, the management data packet is loaded into the memory space of the electronic device; If the management data packet includes a kernel data packet, the operating system of the electronic device is started based on the kernel data packet; When the management data package includes a kernel data package and various application data packages running on it, the operating system of the electronic device is started based on the kernel data package, and the electronic device is controlled to perform corresponding functions based on the various application data packages.

7. The equipment management method according to any one of claims 1-6, The management data packet is generated by the cloud after verifying the data request. The management data packet corresponds to the attribute information of the electronic device and can complete the startup of the operating system of the electronic device.

8. The equipment management method according to claim 6 further includes: If the management data packet fails verification, determine whether the electronic device's local storage space contains a cached management data packet; If so, the electronic device is managed based on the cache management data packet; If not, then activate the rescue mode of the electronic device.

9. The equipment management method according to claim 1 further includes: In the event that the management electronic device fails to start, a startup failure log is generated; Extract the failure factors from the startup failure log; Report the startup failure log and / or the failure factors.

10. An electronic device, comprising: The basic input / output system monitors whether the target hotkey is triggered upon power-on startup. When the target hotkey is triggered, the target program is invoked; wherein the target program is stored in a local storage medium. The target program sends a data request to the cloud; and receives a management data packet returned by the cloud in response to the data request. Electronic devices are managed based on the aforementioned management data packets.

Images