# US 2020/0351366 A1 · Inter-process communication fault detection and recovery system

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

- Number: US 2020/0351366 A1
- Document ID: US20200351366A1
- Status: Published application
- Kind: A1
- Application number: 16/935,560
- Filed: 2020-07-22
- Published: 2020-11-05
- Earliest claimed: 2018-04-10
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Michael Emery Brown; Santosh Kumar Bidaralli
- Web page: https://patentgrep.com/patent/US20200351366A1

## CPC

- H04L 67/562: Brokering proxy services
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- G06F 11/0703: {Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0757: {by exceeding a time limit, i.e. time-out, e.g. watchdogs}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- H04L 41/0654: using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437)
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/0805: by checking availability
- H04L 43/0817: by checking functioning
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An inter-process communication (IPC) system, includes a first client engine, a first server engine, and a broker engine that is coupled to the first client engine. The broker engine initiates a first timer that is configured to reset when traffic is received from the first server engine while the first server engine is registered with the broker engine and coupled to the broker engine via a communication channel. The traffic that causes the first timer to reset includes at least one of: traffic generated by the first client engine to complete a request, and a first server-to-broker heartbeat message generated by the first server engine. The broker engine determines that the first timer has reached a predefined time amount, and in response, removes the registration of the first server engine and removes the communication channel between the broker engine and the first server engine.

## Claims

### Claim 1

A broker/server communication channel management system, comprising:
a server engine; and
a broker engine that is coupled to the server engine and that is configured to:
establish a communication channel with the server engine;
monitor for server traffic transmitted by the server engine via the communication channel;
maintain the communication channel with the server engine in response to receiving the server data traffic from the server engine within a first time period; and
remove the communication channel with the server engine in response to not receiving the server data traffic from the server engine within the first time period.

### Claim 2 (depends on 1)

The IPC system of claim 1, wherein the broker engine is configured to:
transmit broker data traffic to the server engine via the communication channel.

### Claim 3 (depends on 2)

The IPC system of claim 2, wherein the server engine is configured to:
monitor for the broker data traffic transmitted by the broker engine via the communication channel; and
transmit a communication channel re-establishment request to the broker engine in response to not receiving the broker data traffic from the broker engine within a second time period.

### Claim 4 (depends on 3)

The IPC system of claim 3, wherein the broker engine is configured to:
re-establish the communication channel with the server engine in response to receiving the communication channel re-establishment request.

### Claim 5 (depends on 1)

The IPC system of claim 1, wherein the server data traffic includes a server-to-broker heartbeat message.

### Claim 6 (depends on 5)

The IPC system of claim 5, wherein the server-to-broker heartbeat message includes a sequence number that is configured for use by the broker engine to determine whether the server engine has become unavailable.

### Claim 7 (depends on 1)

The IPC system of claim 1, further comprising:
a client engine, wherein the broker engine is configured to:
provide, in response to not receiving the server data traffic from the server engine within the first time period, a notification to the client engine that the server engine is unavailable.

### Claim 8

An information handling system (IHS), comprising:
a processing system; and
a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a broker engine that is configured to:
establish a communication channel with a server engine;
monitor for server traffic transmitted by the server engine via the communication channel;
maintain the communication channel with the server engine in response to receiving the server data traffic from the server engine within a first time period; and
remove the communication channel with the server engine in response to not receiving the server data traffic from the server engine within the first time period.

### Claim 9 (depends on 8)

The IHS of claim 8, wherein the broker engine is configured to:
transmit broker data traffic to the server engine via the communication channel.

### Claim 10 (depends on 9)

The IHS of claim 9, wherein the broker engine is configured to:
receive a communication channel re-establishment request that was transmitted by the server engine in response to not receiving the broker data traffic from the broker engine within a second time period; and
re-establish the communication channel with the server engine in response to receiving the communication channel re-establishment request.

### Claim 11 (depends on 8)

The IHS of claim 8, wherein the server data traffic includes a server-to-broker heartbeat message.

### Claim 12 (depends on 11)

The IHS of claim 11, wherein the server-to-broker heartbeat message includes a sequence number that is configured for use by the broker engine to determine whether the server engine has become unavailable.

### Claim 13 (depends on 8)

The IHS of claim 8, wherein the broker engine is configured to:
provide, in response to not receiving the server data traffic from the server engine within the first time period, a notification to a client engine that the server engine is unavailable.

### Claim 14

A method of managing a broker/server communication channel, comprising:
establishing, by a broker engine, a communication channel with the server engine;
monitoring, by the broker engine, for server traffic transmitted by the server engine via the communication channel;
maintaining, by the broker engine, the communication channel with the server engine in response to receiving the server data traffic from the server engine within a first time period; and
removing, by the broker engine, the communication channel with the server engine in response to not receiving the server data traffic from the server engine within the first time period.

### Claim 15 (depends on 14)

The method of claim 14, further comprising
transmitting, by the broker engine, broker data traffic to the server engine via the communication channel.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
monitoring, by the server engine, for the broker data traffic transmitted by the broker engine via the communication channel; and
transmitting, by the server engine, a communication channel re-establishment request to the broker engine in response to not receiving the broker data traffic from the broker engine within a second time period.

### Claim 17 (depends on 16)

The method of claim 16, further comprising:
re-establishing, by the broker engine, the communication channel with the server engine in response to receiving the communication channel re-establishment request.

### Claim 18 (depends on 14)

The method of claim 14, wherein the server data traffic includes a server-to-broker heartbeat message.

### Claim 19 (depends on 18)

The method of claim 18, wherein the server-to-broker heartbeat message includes a sequence number that is configured for use by the broker engine to determine whether the server engine has become unavailable.

### Claim 20 (depends on 14)

The method of claim 14, further comprising:
providing, by the broker engine in response to not receiving the server data traffic from the server engine within the first time period, a notification to a client engine that the server engine is unavailable.
