Using multicasting to concurrently image multiple client devices

• US 9,936,055 B2
• Filed: 01/27/2016
• Issued: 04/03/2018
• Est. Priority Date: 01/27/2016
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Hebbar, Chaithra
• Primary Examiner(s): Bui, Jonathan A
• Application Number:
  US15/007,472
• Publication Number:
  US 20170214727A1
• Time in Patent Office: 797 Days
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• 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/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

An update can be multicast to a number of client devices. By multicasting an update, the update can be concurrently distributed to a large number of client devices using a single network transmission. This greatly reduces the amount of time required to update the client devices as well as the amount of bandwidth that is required to transfer the update over the network. As part of this multicasting process, the client device, which may have missed a segment of the multicast, can request the missed segment. The missed segment can then also be multicast to eliminate or minimize the redundant transmission of the missed segment.

Claims

1. A method, performed by a multicast server, for multicasting an update to a number of client devices, the method comprising:

multicasting control information which defines a total size of an update and a segment size;

multicasting, to the client devices, a number of segments of the update, each segment comprising application layer data that is provided to a transport layer API for transmission via the multicast;

receiving, from a first client device, a communication that identifies one or more segments of the update that the first client device did not receive; and

in response, multicasting, to the client devices, the one or more segments of the update identified in the communication thereby enabling any other client devices to also receive the one or more segments.

2. The method of claim 1, wherein the client devices are thin clients.

3. The method of claim 2, wherein the multicast server is a thin client.

4. The method of claim 1, wherein the update comprises an image of the multicast server.

5. The method of claim 1, further comprising:

receiving, from a device management tool, a schedule identifying when to initiate the multicast.

6. The method of claim 1, wherein the size of each segment is selected by the multicast server based on one or more network conditions.

7. The method of claim 6, wherein the update is an image and the segment size corresponds with a size of two blocks of the image.

8. The method of claim 1, wherein multicasting comprises IP multicasting.

9. The method of claim 1, wherein the total size is defined as one of:

a total number of bytes in the update;

or

a total number of segments in the update.

10. The method of claim 1, wherein the control information further defines a transmission rate of the segments.

11. The method of claim 1, wherein the control information is multicast one or both of prior to multicasting the segments or while multicasting the segments.

12. One or more computer storage media storing computer executable instructions which when executed by a multicast server implement a method for multicasting an update to a number of client devices, the method comprising:

multicasting, to the client devices, control information which defines a total size of an update to be multicast and a segment size for segments of the update, each segment comprising application layer data that is provided to a transport layer API for transmission via the multicast;

multicasting, to the client devices, the segments of the update;

receiving, from a first client device, a communication that identifies one or more segments of the update that the first client device did not receive; and

in response, multicasting, to the client devices, the one or more segments of the update identified in the communication thereby enabling any other client devices to also receive the one or more segments.

13. The computer storage media of claim 12, wherein the segment size corresponds to a size of a number of blocks of the update.

14. The computer storage media of claim 12, wherein each of the segments includes a sequential identifier that identifies a relative position of the segment within the update.

15. The computer storage media of claim 12, further comprising:

receiving, from a second client device, a communication that identifies one or more segments of the update that the second client device did not receive; and

in response, multicasting, to the client devices, the one or more segments of the update that the second client device did not receive.

16. The computer storage media of claim 15, wherein the one or more segments that the second client device did not receive are different than the one or more segments that the first client device did not receive.

17. The computer storage media of claim 15, wherein the multicast server and the client devices are thin clients.

18. A method for updating thin clients comprising:

selecting one thin client from among the thin clients to function as a multicast server;

transmitting a schedule to the thin clients, the schedule defining a time when an update will be multicast to the thin clients;

multicasting control information that identifies a total size and a segment size for the update;

at the scheduled time, multicasting, by the multicast server, the update to the thin clients;

receiving, by the multicast server and from a first thin client, a communication that identifies one or more segments of the update that the first thin client did not receive during the multicast; and

in response, re-multicasting the one or more segments.

19. The method of claim 18, wherein a device management tool selects the thin client to function as the multicast server.

20. The method of claim 18, wherein the total size is defined as one of:

a total number of bytes in the update;

or

a total number of segments in the update.