# US 2017/0286490 A1 · Implicit subscriptions in the connection protocol of a network switch

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

- Number: US 2017/0286490 A1
- Document ID: US20170286490A1
- Status: Published application
- Kind: A1
- Application number: 15/273,977
- Filed: 2016-09-23
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: Arista Networks, Inc.
- Applicants: Arista Networks, Inc.
- Inventors: Michael Greenwald; Stephen Schleimer
- Web page: https://patentgrep.com/patent/US20170286490A1

## CPC

- G06F 16/2455: Query execution
- G06F 16/211: {Schema design and management}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- 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

A network device includes a connection manager and a state machine. The connection manager is programmed to establish a connection with a client; send, using the connection, a database planner to the client; obtain, using the connection, a subscription request from the client; and modify the database planner based on the subscription request. The state machine is programmed to process the database planner.

## Claims

### Claim 1

A network device, comprising:
a connection manager programmed to:
establish a connection with a client;
send, using the connection, a database planner to the client;
obtain, using the connection, a subscription request from the client;
modify the database planner based on the subscription request; and
a state machine programmed to process the database planner.

### Claim 2 (depends on 1)

The network device of claim 1, wherein the database planner specifies each location of each entry of a database.

### Claim 3 (depends on 1)

The network device of claim 1, wherein the subscription request specifies a table of a database.

### Claim 4 (depends on 3)

The network device of claim 3, wherein the subscription request specifies write access.

### Claim 5 (depends on 4)

The network device of claim 4, wherein processing the database planner comprises:
writing data received by the connection to the table of the database.

### Claim 6 (depends on 3)

The network device of claim 3, wherein the subscription request specifies read access.

### Claim 7 (depends on 6)

The network device of claim 6, wherein processing the database planner comprises:
sending an entry of the table by the connection to the client.

### Claim 8 (depends on 1)

The network device of claim 1, wherein the subscription request specifies a query that produces an output based on a table of a database.

### Claim 9 (depends on 8)

The network device of claim 8, wherein processing the database planner comprises:
sending the output generated by the query to the client by the connection.

### Claim 10 (depends on 1)

The network device of claim 1, wherein the subscription request specifies an observer that monitors an entry of a table of a database.

### Claim 11 (depends on 10)

The network device of claim 10, wherein processing the database planner comprises:
sending the entry of the table of the database to the client by the connection in response to a change in a value of the entry of the table of the database.

### Claim 12 (depends on 1)

The network device of claim 1, wherein the subscription request specifies a modifier that stores an output of a query to an entry of a table of a database.

### Claim 13 (depends on 12)

The network device of claim 12, wherein processing the database planner comprises:
sending the output of the query to the client by the connection in response to the modifier storing the output.

### Claim 14 (depends on 1)

The network device of claim 1, wherein the network device is one network device selected from the group of network devices consisting of a switch, a router, and a multilevel switch.

### Claim 15 (depends on 1)

The network device of claim 1, wherein the client is a second network device.

### Claim 16 (depends on 1)

The network device of claim 1, wherein the client is a program executing on the network device.

### Claim 17 (depends on 1)

The network device of claim 1, wherein the connection is a socket connection.

### Claim 18

A method of operating a network device, comprising:
establishing, by a connection manager of the network device, a connection with a client;
sending, by the connection manager, a database planner to the client by the connection;
obtaining, by the connection manager, a subscription request specifying a table of the database planner; and
modifying, by the connection manager, the database planner based on the subscription request.

### Claim 19 (depends on 18)

The method of claim 18, wherein modifying the database planner comprises:
adding, by the connection manager, a row to the table of the database planner.

### Claim 20 (depends on 19)

The method of claim 19, wherein the row specifies an entity of the database.