Client server method for loading a client with a specific image or utility based on the client's state

• US 6,601,096 B1
• Filed: 01/04/2000
• Issued: 07/29/2003
• Est. Priority Date: 01/04/2000
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Lassiter, Linwood Ottis Jr.
• Primary Examiner(s): Lim, Krisna
• Assistant Examiner(s): Barqadle, Yasin M
• Application Number:
  US09/477,743
• Time in Patent Office: 1,302 Days
• Field of Search: 709/227, 709/217, 709/219, 709/223, 713/2, 713/200
• US Class Current: 709/222
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/50 Address allocation
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

PXE Frame extension tags are used for remote boot loading client machines to afford servers deterministic ability for what image or utility the client requires based on its boot state. The invention takes advantage of the PXE frame by using the DHCP/PXE Vendor Tags for providing information to the PXE Server as to what image or boot process is required from the server by the client. This solution is targeted primarily, but not limited to, “media less” or “thin clients”. The invention provides the client an ability to give a DHCP/PXE server more deterministic information about itself. The server can use this information (i.e. information contained within the Extension tags) to determine more precisely the client machine'"'"'s boot state DHCP/PXE server code parseses the DHCP/PXE extension tags (contained within the DHCP/PXE data frame) and uses the POST error information and/or the Vital Product Data (VPD) to provide the client with a tailored boot image.

Claims

1. A method for loading a client with an image from a server, including the steps of:

(a) at the client;

generating a DHCP/PXE frame;

inserting vital product data relating to the client in data fields of the vendor extension Tag 128 of the DHCP/PXE frame;

transmitting the DHCP/PXE frame with said vendor extension Tag 128 to the server;

(b) at the server;

parsing the vital product data transmitted in the vendor extension Tag 128;

transmitting an image to the client based on the vital product data transmitted in the vendor extension Tag 128.

2. A method for loading a client with an image from a server, including the steps of:

(a) at the client;

generating a DHCP/PXE frame;

inserting vital product data relating to the client in data fields of the vendor extension Tag 128 of the DHCP/PXE frame;

inserting POST error log information in data fields of the vendor extension Tag 129 of the DHCP/PXE frame;

transmitting the DHCP/PXE frame with said vendor extension Tags 128 and 129 to the server;

(b) at the server;

parsing the vital product data transmitted in the vendor extension Tag 128;

parsing the POST error log information transmitted in vendor extension Tag 129;

transmitting an image to the client based on the vital product data transmitted in the vendor extension Tags 128 and 129.

3. A method for loading a client with an image from a server, including the steps of:

(a) at the client;

generating a DHCP/PXE frame;

inserting POST error log information in data fields of the vendor extension Tag 129 of the DHCP/PXE frame;

transmitting the DHCP/PXE frame with said vendor extension Tag 129 to the server;

(b) at the server;

parsing the POST error log information transmitted in vendor extension Tag 129;

transmitting an image to the client based on the post error log information transmitted in the vendor extension Tag 129.

4. A method for loading a client with an image from a server, including the steps of:

(a) at the client;

generating a boot frame;

inserting vital product data relating to the client in data fields of a vendor extension tag of the boot frame;

transmitting the boot frame with said vendor extension tag to the server;

(b) at the server;

parsing the vital product data transmitted in the vendor extension tag;

transmitting an image to the client based on the vital product data transmitted in the vendor extension tag.

5. A method for loading a client with an image from a server, including the steps of:

(a) at the client;

generating a boot frame;

inserting POST error log information in data fields of a vendor extension tag of the boot frame;

transmitting the boot frame with said vendor extension tag to the server;

(b) at the server;

parsing the POST error log information transmitted in vendor extension tag;

transmitting an image to the client based on the post error log information transmitted in the vendor extension tag.