SCALABLE DISTRIBUTED MULTICLUSTER DEVICE MANAGEMENT SERVER ARCHITECTURE AND METHOD OF OPERATION THEREOF

1 . A server architecture for managing devices, comprising:

a plurality of manager clusters; and

a dispatcher cluster coupled to said plurality of manager clusters and configured to:

receive an initial contact from a device,

assign said device to one manager cluster of said plurality of manager clusters, said one manager cluster becoming a home cluster for said device,

cause data regarding said device to be transferred to said home cluster, and

cause said device thereafter to communicate directly with, and be managed by, said home cluster.

2 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to cause said device to communicate directly with, and be managed by, a manager cluster backup instead of said home cluster if said home cluster is affected by a disaster.

3 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to cause said device to communicate directly with, and be managed by, a secondary manager cluster instead of said home cluster if said home cluster temporarily experiences an excessive load.

4 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to register said device.

5 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to activate said device.

6 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to assign said device based on a type of said device.

7 . The server architecture as recited in claim 1 wherein said dispatcher cluster is further configured to assign said device based on a geographical location of said device.

8 . A method of managing devices, comprising:

receiving an initial contact from a device into a dispatcher cluster;

employing said dispatcher cluster to assign said device to one manager cluster of a plurality of manager clusters, said one manager cluster becoming a home cluster for said device;

causing data regarding said device to be transferred to said home cluster; and

causing said device thereafter to communicate directly with, and be managed by, said home cluster.

9 . The method as recited in claim 8 further comprising causing said device to communicate directly with, and be managed by, a manager cluster backup instead of said home cluster if said home cluster is affected by a disaster.

10 . The method as recited in claim 8 further comprising causing said device to communicate directly with, and be managed by, a secondary manager cluster instead of said home cluster if said home cluster temporarily experiences an excessive load.

11 . The method as recited in claim 8 further comprising employing said dispatcher cluster to register said device.

12 . The method as recited in claim 8 further comprising employing said dispatcher cluster to activate said device.

13 . The method as recited in claim 8 wherein said employing said dispatcher cluster to assign said device comprises employing said dispatcher cluster to assign said device based on a type of said device.

14 . The method as recited in claim 8 wherein said employing said dispatcher cluster to assign said device comprises employing said dispatcher cluster to assign said device based on a geographical location of said device.

15 . A server architecture for managing devices, comprising:

a plurality of manager clusters; and

a dispatcher cluster coupled to said plurality of manager clusters and configured to:

receive an initial contact from a device,

register said device,

configure at least some service parameters on said device,

assign said device to one manager cluster of said plurality of manager clusters, said one manager cluster becoming a home cluster for said device,

cause data regarding said device to be transferred to said home cluster, and

cause said device thereafter to communicate directly with, and be managed by, said home cluster.

16 . The server architecture as recited in claim 15 wherein said dispatcher cluster is further configured to cause said device to communicate directly with, and be managed by, a manager cluster backup instead of said home cluster if said home cluster is affected by a disaster.

17 . The server architecture as recited in claim 15 wherein said dispatcher cluster is further configured to cause said device to communicate directly with, and be managed by, a secondary manager cluster instead of said home cluster if said home cluster temporarily experiences an excessive load.

18 . The server architecture as recited in claim 15 wherein said dispatcher cluster is further configured to assign said device based on a type of said device.

19 . The server architecture as recited in claim 15 wherein said dispatcher cluster is further configured to assign said device based on a geographical location of said device.

20 . A server architecture for managing devices, comprising:

a plurality of manager clusters configured to serve as home cluster for ones of said devices; and

a dispatcher cluster coupled to said plurality of manager clusters and configured to assign said device to one manager cluster of said plurality of manager clusters and cause data regarding said device to be transferred to said home cluster, said one manager cluster becoming a home cluster for said device, said server architecture capable scaling by both increasing a number of servers in said plurality of manager clusters and said dispatcher cluster and increasing a number of said plurality of manager clusters.