IP Library Patent Application 15287899
Patent Application
App. No. 15/287,899

METHOD AND SYSTEM FOR EFFICIENT TASK MANAGEMENT

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
15/287,899
Abstract

A computer implemented method and apparatus for efficient task management. The method comprises receiving a task request on a first server of a plurality of server, wherein a task associated with the task request is to be performed on a first device of a plurality of devices; determining an identification of a second server of the plurality of servers that has an affinity for the requested task, wherein the second server is different from the first server; and transferring the task request to the second server.

Claims (52)

1 . A computer implemented method for efficient task management comprising:

receiving a task request on a first server of a plurality of server, wherein a task associated with the task request is to be performed on a first device of a plurality of devices;

determining an identification of a second server of the plurality of servers that has an affinity for the requested task, wherein the second server is different from the first server; and

transferring the task request to the second server.

2 . The method of claim 1 , further comprising:

receiving the task request on the second server, wherein a task associated with the task request is to be performed on the first device;

determining the second server no longer has an affinity for the requested task;

determining an identification of a third server of the plurality of servers that has an affinity for the requested task, wherein the third server is different from the second server; and

transferring the task request to the third server.

3 . The method of claim 1 , wherein transferring the task request comprises sending the task request to a named queue for the second server.

4 . The method of claim 1 , wherein determining the identification of a second server of the plurality of servers that has an affinity for the requested task comprises:

transmitting a request to a shared memory; and

receiving in response to the request an indication of which server of the plurality of servers has an affinity for the task associated with the task request.

5 . The method of claim 1 , wherein the second server has an affinity for the requested task when it is determined the second server is the server in the plurality of servers where a communication channel to the first device was last opened.

6 . The method of claim 1 , wherein the second server has an affinity for the requested task when the second server is predefined to execute a specific type of task associated with the task request.

7 . The method of claim 1 , further comprising, upon determining that the server with an affinity for the requested task is a current server where the task request was received, performing the steps of:

generating a task based on the task request; and

providing the generated task to a device driver for the first device, wherein providing the generated task causes the device driver to transmit the generated task to the first device for execution.

8 . The method of claim 7 , further comprising storing in a shared memory an indication of which server of the plurality of servers generated the task and provided the generated task to the device driver for the first device.

9 . The method of claim 1 , wherein the first server and the second server are virtual machines on a same server.

10 . A system for efficient task management for a plurality of task management servers, comprising:

a) at least one processor;

b) at least one input device; and

c) at least one storage device storing processor-executable instructions which, when executed by the at least one processor, perform a method including:

receiving a task request on a first server of a plurality of server, wherein a task associated with the task request is to be performed on a first device of a plurality of devices;

determining an identification of a second server of the plurality of servers that has an affinity for the requested task, wherein the second server is different from the first server; and

transferring the task request to the second server.

11 . The system of claim 10 , further comprising:

receiving the task request on the second server, wherein a task associated with the task request is to be performed on the first device;

determining the second server no longer has an affinity for the requested task;

determining an identification of a third server of the plurality of servers that has an affinity for the requested task, wherein the third server is different from the second server; and

transferring the task request to the third server.

12 . The system of claim 10 , wherein transferring the task request comprises sending the task request to a named queue for the second server.

13 . The system of claim 10 , wherein determining the identification of a second server of the plurality of servers that has an affinity for the requested task comprises:

transmitting a request to a shared memory; and

receiving in response to the request an indication of which server of the plurality of servers has an affinity for the task associated with the task request.

14 . The system of claim 10 , wherein the second server has an affinity for the requested task when it is determined the second server is the server in the plurality of servers where a communication channel to the first device was last opened.

15 . The system of claim 10 , wherein the second server has an affinity for the requested task when the second server is predefined to execute a specific type of task associated with the task request.

16 . The system of claim 10 , further comprising, upon determining that the server with an affinity for the requested task is a current server where the task request was received, performing the steps of:

generating a task based on the task request; and

providing the generated task to a device driver for the first device, wherein providing the generated task causes the device driver to transmit the generated task to the first device for execution.

17 . The system of claim 16 , further comprising storing in a shared memory an indication of which server of the plurality of servers generated the task and provided the generated task to the device driver for the first device.

18 . The system of claim 10 , wherein the first server and the second server are virtual machines on a same server.

19 . A non-transitory computer readable medium for storing computer instructions that, when executed by at least one processor causes the at least one processor to perform a method for efficient task management, comprising:

receiving a task request on a first server of a plurality of server, wherein a task associated with the task request is to be performed on a first device of a plurality of devices;

determining an identification of a second server of the plurality of servers that has an affinity for the requested task, wherein the second server is different from the first server; and

transferring the task request to the second server.

20 . The non-transitory computer readable medium of claim 19 , further comprising:

receiving the task request on the second server, wherein a task associated with the task request is to be performed on the first device;

determining the second server no longer has an affinity for the requested task;

determining an identification of a third server of the plurality of servers that has an affinity for the requested task, wherein the third server is different from the second server; and

transferring the task request to the third server.

Assignments (2)
SECURITY INTEREST Recorded Nov 12, 2019
From: TRILLIANT NETWORKS, INC.; TRILLIANT HOLDINGS, INC.; TRILLIANT NETWORKS (CANADA) INC.
To: THIRD EYE CAPITAL CORPORATION
Reel/Frame 050989/0361 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 11, 2016
From: BRIDGER, PHILIP
To: TRILLIANT NETWORKS INC.
Reel/Frame 039988/0045 →