# US 11,307,887 B2 · Server deployment method and system in hypervisor architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,307,887 B2
- Document ID: US11307887B2
- Status: Granted
- Kind: B2
- Application number: 16/700,524
- Filed: 2019-12-02
- Published: 2021-06-03
- Granted: 2022-04-19
- Earliest claimed: 2019-12-02
- Assignees: American Megatrends International, LLC
- Applicants: American Megatrends International, LLC
- Inventors: Chih-Kai Hu
- Web page: https://patentgrep.com/patent/US11307887B2

## CPC

- G06F 9/4416: {Network booting; Remote initial program loading [RIPL]}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 8/60: Software deployment
- G06F 8/61: Installation
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- H04L 61/5014: using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F 2009/45591: {Monitoring or debugging support}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A server deployment method and system in a hypervisor architecture are disclosed. The server deployment method, applied between a deployment management platform and at least one deployed server, includes steps of: (a) the deployed server requesting an internet protocol (IP); (b) the deployment management platform distributing the IP; (c) the deployed server requesting an agent; (d) the deployment management platform delivering the agent; (e) the deployed server automatically joining the deployment management platform; (f) the deployment management platform mounting a hard disk shared by the deployed server; (g) the deployment management platform selecting the type of central processing unit (CPU) and installing an operating system to the hard disk shared by the deployed server; and (h) establishing a connection of a monitor screen between the deployment management platform and the deployed server.

## Claims

### Claim 1

A server deployment method in a hypervisor architecture, applied between a deployment management platform and at least one deployed server, comprising steps of:
(a) the deployed server requesting an internet protocol (IP);
(b) the deployment management platform distributing the IP;
(c) the deployed server requesting an agent comprising a hypervisor;
(d) the deployment management platform delivering the agent;
(e) the deployed server automatically joining the deployment management platform;
(f) the deployment management platform mounting a remote hard disk shared by the deployed server;
(g) the deployment management platform selecting a type of a central processing unit (CPU) according to hardware information provided by the hypervisor and performing local installation of an operating system on the remote hard disk shared by the deployed server through a simulation machine; and
(h) establishing a connection of a monitor screen between the deployment management platform and the deployed server.

### Claim 2 (depends on 1)

The server deployment method of claim 1, wherein in the step (a), the deployed server requests the IP through a pre-boot execution environment (PXE).

### Claim 3 (depends on 1)

The server deployment method of claim 1, wherein the step (b) further comprises:
the deployment management platform informing the IP to a trivial file transfer protocol (TFTP).

### Claim 4 (depends on 1)

The server deployment method of claim 1, wherein the agent further comprises an internet small computer system interface (iSCSI) target service system.

### Claim 5 (depends on 4)

The server deployment method of claim 4, wherein the deployed server provides its hardware information to the deployment management platform through the hypervisor and the deployed server shares the remote hard disk through the iSCSI target service system.

### Claim 6 (depends on 1)

The server deployment method of claim 1, wherein in the step (e), the deployment management platform automatically detects the deployed server and adds the deployed server to the deployment management platform.

### Claim 7 (depends on 1)

The server deployment method of claim 1, wherein in the step (g), the operating system installed to the remote hard disk shared by the deployed server is Linux operating system or Windows operating system.

### Claim 8 (depends on 1)

The server deployment method of claim 1, wherein the deployed server and the deployment management platform are located in the same local area network (LAN), and the LAN comprises a dynamic host configuration protocol (DHCP) server and a TFTP server IP is specified to the deployment management platform.

### Claim 9 (depends on 1)

The server deployment method of claim 1, wherein the deployed server is deployed at a remote end by an administrator through a web-based user interface (UI).

### Claim 10 (depends on 1)

The server deployment method of claim 1, wherein a device at a user end is connected to the deployment management platform to monitor the installation of the operating system to the remote hard disk shared by the deployed server.

### Claim 11

A server deployment system in a hypervisor architecture, comprising:
a deployment management platform; and
at least one deployed server;
wherein when the deployed server requests an internet protocol (IP), the deployment management platform distributes the IP; when the deployed server requests an agent comprising a hypervisor, the deployment management platform delivers the agent; the deployed server automatically joins the deployment management platform; the deployment management platform mounts a remote hard disk shared by the deployed server; the deployment management platform selects a type of a central processing unit (CPU) according to hardware information provided by the hypervisor and performs local installation of an operating system on the remote hard disk shared by the deployed server through a simulation machine; and a connection of a monitor screen is established between the deployment management platform and the deployed server.

### Claim 12 (depends on 11)

The server deployment system of claim 11, wherein the deployed server requests the IP through a pre-boot execution environment (PXE).

### Claim 13 (depends on 11)

The server deployment system of claim 11, wherein the deployment management platform further informs the IP to a trivial file transfer protocol (TFTP).

### Claim 14 (depends on 11)

The server deployment system of claim 11, wherein the agent further comprises an internet small computer system interface (iSCSI) target service system.

### Claim 15 (depends on 14)

The server deployment system of claim 14, wherein the deployed server provides its hardware information to the deployment management platform through the hypervisor and the deployed server shares the remote hard disk through the iSCSI target service system.

### Claim 16 (depends on 11)

The server deployment system of claim 11, wherein the deployment management platform automatically detects the deployed server and adds the deployed server to the deployment management platform.

### Claim 17 (depends on 11)

The server deployment system of claim 11, wherein the operating system installed to the remote hard disk shared by the deployed server is Linux operating system or Windows operating system.

### Claim 18 (depends on 11)

The server deployment system of claim 11, wherein the deployed server and the deployment management platform are located in the same local area network (LAN), and the LAN comprises a dynamic host configuration protocol (DHCP) server and a TFTP server IP is specified to the deployment management platform.

### Claim 19 (depends on 11)

The server deployment system of claim 11, wherein the deployed server is deployed at a remote end by an administrator through a web-based user interface (UI).

### Claim 20 (depends on 11)

The server deployment system of claim 11, wherein a device at a user end is connected to the deployment management platform to monitor the installation of the operating system to the remote hard disk shared by the deployed server.
