Computing environment connectivity system
US-2017034036-A1 · Feb 2, 2017 · US
US10496300B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10496300-B2 |
| Application number | US-201615267460-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 16, 2016 |
| Priority date | Sep 16, 2015 |
| Publication date | Dec 3, 2019 |
| Grant date | Dec 3, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments of the present disclosure disclose a server management method and a management device. The method comprises determining whether a USB device is connected to the server, the USB device including a permission of a respective user to the server. The method further comprises: in response to determining that the USB device is connected to the server, transmitting the permission to the server to enable the server to be operated based on the permission.
Opening claim text (preview).
What is claimed is: 1. A method of managing a server using a Universal Serial Bus (USB) device, comprising: by the USB device, determining whether the USB device is connected to the server, the USB device including a permission of a respective user to the server; by the USB device in response to determining that the USB device is connected to the server, transmitting the permission to the server to enable the server to be operated based on the permission; providing, via the server, a level of operation of the server based on the permission; and by the USB device, monitoring conditions of the server while connected to the server, wherein the permission is a permission of a user of the server to use hardware of the server, and the permission specifies a performance level of the server as one or more hardware parameters including (1) a maximum number of central processing units (CPUs) and a maximum number of CPU cores of the server that can be used by the user, (2) a maximum operating frequency of a CPU of the server that can be used by the user, and (3) a size of available memory of the server that can be used by the user. 2. The method of claim 1 , wherein the permission is stored in a read-only memory within the USB device. 3. The method of claim 2 , further comprising, by the USB device: in response to a decryption operation on the USB device, performing at least one of the following: entering a safe mode; stopping working; or erasing the read-only memory. 4. The method of claim 2 , wherein the USB device comprises a battery configured to supply power to the USB device; and further comprising, by the USB device in response to a voltage of the battery being below a threshold, erasing the read-only memory. 5. The method of claim 1 , further comprising, by the USB device: obtaining status information of the server via a USB interface between the USB device and the server. 6. The method of claim 5 , wherein the USB device comprises a Radio Frequency Identification (RFID) interface; and further comprising, by the USB device: transmitting the status information of the server to an external device via the RFID interface. 7. The method of claim 1 , wherein, if the server fails to receive the permission from the USB device within a predetermined time, the server either shuts down or operates on a default permission. 8. The method of claim 7 , wherein the default permission is one of a minimum-level permission, a permission currently in use, or a permission at another level customized based on the service provided to a user. 9. A Universal Serial Bus (USB) device for managing a server, comprising: a processor configured to: determine whether the USB device is connected to the server, the USB device including a permission of a respective user to the server; in response to determining that the USB device is connected to the server, transmit the permission to the server to enable the server to be operated based on the permission, the permission specifying a level of operation of the server based on the permission; and monitor conditions of the server while the USB device is connected to the server, wherein the permission is a permission of a user of the server to use hardware of the server, and the permission specifies a performance level of the server as one or more hardware parameters including (1) a maximum number of central processing units (CPUs) and a maximum number of CPU cores of the server that can be used by the user, (2) a maximum operating frequency of a CPU of the server that can be used by the user, and (3) a size of available memory of the server that can be used by the user. 10. The USB device of claim 9 , wherein the permission is stored in a read-only memory within the USB device. 11. The USB device of claim 10 , wherein in response to a decryption operation on the USB device, the processor is configured to cause the USB device to perform at least one of the following operations: entering a safe mode; stopping working; or erasing the read-only memory. 12. The USB device of claim 10 , wherein the USB device further comprises a battery configured to supply power to the USB device, and the processor is further configured to: in response to a voltage of the battery being below a threshold, erase the read-only memory. 13. The USB device of claim 9 , wherein the USB device is configured to obtain status information of the server via a USB interface between the USB device and the server. 14. The USB device of claim 13 , wherein the USB device further comprises a Radio Frequency Identification (RFID) interface and is further configured to transmit the status information of the server to an external device via the RFID interface.
where the program performs an interfacing function, e.g. device driver (G06F13/105 takes precedence; contention policies within device drivers G06F9/4881; scheduling within device drivers G06F9/52) · CPC title
on a serial bus, e.g. I2C bus, SPI bus (on daisy chain buses G06F13/4247) · CPC title
Providing cryptographic facilities or services · CPC title
Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title
Universal serial bus [USB] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.