# US 2020/0403874 A1 · Server and methods for synchronizing networking information with client devices

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

- Number: US 2020/0403874 A1
- Document ID: US20200403874A1
- Status: Published application
- Kind: A1
- Application number: 16/446,789
- Filed: 2019-06-20
- Published: 2020-12-24
- Earliest claimed: 2019-06-20
- Assignees: Kaloom Inc.
- Applicants: Kaloom Inc.
- Inventors: Geoffrey LEFEBVRE; Daniel RICHER; Harsimrandeep Singh PABLA
- Web page: https://patentgrep.com/patent/US20200403874A1

## CPC

- G06F 16/178: Techniques for file synchronisation in file systems
- H04L 41/045: comprising client-server management architectures
- H04L 41/0859: by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L 41/12: Discovery or management of network topologies
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 2101/622: Layer-2 addresses, e.g. medium access control [MAC] addresses
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Server and methods for performing synchronization and resynchronization of networking information with client devices. During standard operations, client networking data discovered by a given client device are received by the server from the given client device, stored by the server, and forwarded by the server to other client devices. Client networking data from the other client devices received and stored by the server are forwarded to the given client device. Upon occurrence of a pre-defined event at the given client device preventing exchange of information between the given client device and the server, a resynchronization of the client networking data is performed between the given client device and the server. The synchronization and resynchronization mechanisms are based on unique version numbers respectively generated by the server and the given client device.

## Claims

### Claim 1

A server comprising:
memory storing;
a global topology table comprising a plurality of entries, each entry comprising client networking data, a unique client identifier of one among a plurality of clients, and a unique server version number, the server version numbers increasing from a first value corresponding to a first entry in the global topology table to a last value S1 corresponding to a last entry in the global topology table; and
a client version table comprising one entry for each one among the plurality of clients, each entry comprising the unique client identifier of one among the plurality of clients and a corresponding client version number;
a communication interface; and
a processing unit for:
receiving from a given client among the plurality of clients via the communication interface a client synchronization message, the client synchronization message comprising the client identifier of the given client, new client networking data, and a new client version number;
updating the global topology table by adding one or more new entry to the global topology table, the one or more new entry comprising the new client networking data, the client identifier of the given client, and respective increasing server version numbers greater than S1;
updating the entry of the client version table corresponding to the client identifier of the given client with the new client version number; and
sending to the given client via the communication interface a server synchronization message, the server synchronization message comprising client networking data stored in the global topology table and having a client identifier different from the client identifier of the given client, the server synchronization message further comprising a current server version number.

### Claim 2 (depends on 1)

The server of claim 1, wherein the current server version number corresponds to the last entry in the global topology table currently stored in the memory.

### Claim 3 (depends on 1)

The server of claim 1, wherein the processing unit receives client synchronization messages from several among the plurality of clients and respectively updates the global topology table and the client version table based on the received client synchronization messages.

### Claim 4 (depends on 1)

The server of claim 1, wherein the processing unit sends server synchronization messages to several among the plurality of clients.

### Claim 5 (depends on 1)

The server of claim 1, wherein the client networking data comprise information related to a remote node and an identifier of an intermediate node.

### Claim 6 (depends on 5)

The server of claim 5, wherein the information related to the remote node comprises a Media Access Control (MAC) address of the remote node, an Internet Protocol (IP) address of the remote node, a MAC address and an IP address of the remote node, and a tuple identifying a network connection of the remote node.

### Claim 7 (depends on 5)

The server of claim 5, wherein the identifier of the intermediate node consists of an IP address or a MAC address of the intermediate node.

### Claim 8 (depends on 1)

The server of claim 1, wherein the unique client identifier of a client consists of a MAC address of the client, an IP address of the client or a unique identifier generated by the client.

### Claim 9

A method implemented by a server for performing synchronization of networking information with a client, the method comprising:
storing in a memory of the server a global topology table comprising a plurality of entries, each entry comprising client networking data, a unique client identifier of one among a plurality of clients, and a unique server version number, the server version numbers increasing from a first value corresponding to a first entry in the global topology table to a last value S1 corresponding to a last entry in the global topology table;
storing in the memory a client version table comprising one entry for each one among the plurality of clients, each entry comprising the unique client identifier of one among the plurality of clients and a corresponding client version number;
receiving by a processing unit of the server from a given client among the plurality of clients via a communication interface of the server a client synchronization message, the client synchronization message comprising the client identifier of the given client, new client networking data, and a new client version number;
updating by the processing unit the global topology table by adding one or more new entry to the global topology table, the one or more new entry comprising the new client networking data, the client identifier of the given client, and respective increasing server version numbers greater than S1;
updating by the processing unit the entry of the client version table corresponding to the client identifier of the given client with the new client version number; and
sending by the processing unit to the given client via the communication interface a server synchronization message, the server synchronization message comprising client networking data stored in the global topology table and having a client identifier different from the client identifier of the given client, the server synchronization message further comprising a current server version number.

### Claim 10

A server comprising:
memory storing;
a global topology table comprising a plurality of entries, each entry comprising client networking data, a unique client identifier of one among a plurality of clients, and a unique server version number, the server version numbers increasing from a first value corresponding to a first entry in the global topology table to a last value corresponding to a last entry in the global topology table; and
a client version table comprising one entry for each one among the plurality of clients, each entry comprising the unique client identifier of one among the plurality of clients and a corresponding client version number;
a communication interface; and
a processing unit for:
receiving from a given client via the communication interface a join message, the join message comprising the client identifier of the given client and an estimated server version number S4;
determining that the global topology table comprises at least one entry having a client identifier different from the client identifier of the given client and a server version number greater than the estimated server version number S4; and
sending to the given client via the communication interface a server synchronization message, the server synchronization message comprising client networking data corresponding to the at least one entry of the global topology table having a client identifier different from the client identifier of the given client and a server version number greater than the estimated server version number S4, a current server version number, and the client version of the given client currently stored in the client version table.

### Claim 11 (depends on 10)

The server of claim 10, wherein the current server version number corresponds to the last entry in the global topology table currently stored in the memory.

### Claim 12 (depends on 10)

The server of claim 10, wherein the processing unit further:
receives from the given client via the communication interface a client synchronization message, the client synchronization message comprising the client identifier of the given client, new client networking data, and a new client version number;
updating the global topology table by adding one or more new entry to the global topology table, the one or more new entry comprising the new client networking data, the client identifier of the given client, and respective increasing server version numbers; and
updating the entry of the client version table corresponding to the client identifier of the given client with the new client version number.

### Claim 13 (depends on 10)

The server of claim 10, wherein the client networking data comprise information related to a remote node and an identifier of an intermediate node.

### Claim 14 (depends on 13)

The server of claim 13, wherein the information related to the remote node comprises a Media Access Control (MAC) address of the remote node, an Internet Protocol (IP) address of the remote node, a MAC address and an IP address of the remote node, and a tuple identifying a network connection of the remote node.

### Claim 15 (depends on 13)

The server of claim 13, wherein the identifier of the intermediate node consists of an IP address or a MAC address of the intermediate node.

### Claim 16 (depends on 10)

The server of claim 10, wherein the unique client identifier of a client consists of a MAC address of the client, an IP address of the client or a unique identifier generated by the client.

### Claim 17

A method implemented by a server for performing resynchronization of networking information with a client, the method comprising:
storing in a memory of the server a global topology table comprising a plurality of entries, each entry comprising client networking data, a unique client identifier of one among a plurality of clients, and a unique server version number, the server version numbers increasing from a first value corresponding to a first entry in the global topology table to a last value corresponding to a last entry in the global topology table;
storing in the memory a client version table comprising one entry for each one among the plurality of clients, each entry comprising the unique client identifier of one among the plurality of clients and a corresponding client version number;
receiving by a processing unit of the server from a given client via the communication interface of the server a join message, the join message comprising the client identifier of the given client and an estimated server version number S4;
determining by the processing unit that the global topology table comprises at least one entry having a client identifier different from the client identifier of the given client and a server version number greater than the estimated server version number S4; and
sending by the processing unit to the given client via the communication interface a server synchronization message, the server synchronization message comprising client networking data corresponding to the at least one entry of the global topology table having a client identifier different from the client identifier of the given client and a server version number greater than the estimated server version number S4, a current server version number, and the client version of the given client currently stored in the client version table.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
receiving by the processing unit from the given client via the communication interface a client synchronization message, the client synchronization message comprising the client identifier of the given client, new client networking data, and a new client version number;
updating by the processing unit the global topology table by adding one or more new entry to the global topology table, the one or more new entry comprising the new client networking data, the client identifier of the given client, and respective increasing server version numbers; and
updating by the processing unit the entry of the client version table corresponding to the client identifier of the given client with the new client version number.
