# US 2013/0097322 A1 · Scalable distributed multicluster device management server architecture and method of operation thereof

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0097322 A1
- Document ID: US20130097322A1
- Status: Published application
- Kind: A1
- Application number: 13/274,955
- Filed: 2011-10-17
- Published: 2013-04-18
- Earliest claimed: 2011-10-17
- Assignees: Alcatel-Lucent USA Inc.
- Inventors: Jigang Yang; Arabinda Bose; Vinod T. Nair; Eivind Skildheim
- Web page: https://patentgrep.com/patent/US20130097322A1

## CPC

- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 41/0695: the faulty arrangement being the maintenance, administration or management system
- H04L 67/1006: with static server selection, e.g. the same server being selected for a specific client
- H04L 41/042: comprising distributed management centres cooperatively managing the network
- H04L 67/101: based on network conditions
- H04L 67/1021: based on client or server locations
- H04L 67/1034: Reaction to server failures by a load balancer
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A server architecture for, and method of, managing devices. In one embodiment, the server architecture includes: (1) a plurality of manager clusters and (2) a dispatcher cluster coupled to the plurality of manager clusters and configured to: (2a) receive an initial contact from a device, (2b) assign the device to one manager cluster of the plurality of manager clusters, the one manager cluster becoming a home cluster for the device, (2c) cause data regarding the device to be transferred to the home cluster and (2d) cause the device thereafter to communicate directly with, and be managed by, the home cluster.

## Claims

### Claim 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.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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.

### Claim 4 (depends on 1)

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

### Claim 5 (depends on 1)

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

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

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.

### Claim 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.

### Claim 9 (depends on 8)

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.

### Claim 10 (depends on 8)

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.

### Claim 11 (depends on 8)

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

### Claim 12 (depends on 8)

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

### Claim 13 (depends on 8)

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.

### Claim 14 (depends on 8)

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.

### Claim 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.

### Claim 16 (depends on 15)

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.

### Claim 17 (depends on 15)

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.

### Claim 18 (depends on 15)

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.

### Claim 19 (depends on 15)

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.

### Claim 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.
