Browse Prior Art Database

Antidote broadcast priority Disclosure Number: IPCOM000030921D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Sep-01
Document File: 1 page(s) / 6K

Publishing Venue



There are many methods of allowing clients to download fixes (operating system, application, etc.) form a fix server. One of the most common is for the fix server to broadcast out to all clients that a fix is necessary. The clients upon receipt of this broadcast will attach to the fix server and apply the fix, then go back to normal operation. The problem that this disclosure fixes is what happens when all clients try to download the fix from the fix server at the same time. This will be a significant performance problem. It would be preferable if their was a prioritization scheme where more important clients (mission critical, etc.) would have a higher priority then other clients.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 65% of the total text.

Page 1 of 1

Antidote broadcast priority

Each client has an agent that controls the fix downloading action. At client deployment the client agent is set to a certain priority level. It can be any number of levels depending on IT policy. It is also possible to change the priority level remotely as client value can change over time.

The fix server sends a packet including a fix is required. The client agent queries software and memory in the client computer to see if the client computer has already installed the sent anti-virus fix.. The client agent now signals the fix server it is ready to start downloading the fix from the fix server and applying the patch to the client . As part of this request the client sends it's priority level.

The fix server captures and stores all of the client request. It sets up multiple queues (one for each priority). Queue entry is first in, first out. This is not very time consuming or network bandwidth consuming as the actual push of the fix is the biggest network bandwidth item.

Depending on policy we define a the following process to decide which clients get the fix in what order.

1) The fix server always starts with the highest priority queue. First in first out. Once all are done, move to next priority. We also add a process where policy driven, an IT administrator can ensure lower priority clients get the fix. We can do this in three ways:

Number driven. Policy set can be defined to go to lower queue after N higher

queue clients are service...