# US 2016/0261480 A1 · Client-side fault tolerance in a publish-subscribe system

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

- Number: US 2016/0261480 A1
- Document ID: US20160261480A1
- Status: Published application
- Kind: A1
- Application number: 14/639,351
- Filed: 2015-03-05
- Published: 2016-09-08
- Earliest claimed: 2015-03-05
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Kanak B. Agarwal; Patrick J. Bohrer; Ahmed Gheith; Michael D. Kistler; Ramakrishnan Rajamony
- Web page: https://patentgrep.com/patent/US20160261480A1

## CPC

- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 67/145: avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
- H04L 67/55: Push-based network services
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

To provide client-side fault-tolerance in a publish-subscribe system, a message is received on a channel from a server. At a function executing using a processor and a memory, a determination is made whether the message contains a heartbeat data. When the message contains the heartbeat data, a determination is made whether a content signature contained in the message matches a last known content signature saved from a previous message. When the content signature contained in the message does not match the last known content signature saved from a previous message, a refresh message is sent to the channel.

## Claims

### Claim 1

A method for client-side fault-tolerance in a publish-subscribe system, the method comprising:
receiving, on a channel, a message from a server;
determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data;
determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message;
sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving an other message after the message;
determining that the other message carries content and a corresponding content signature; and
saving the content signature of the other message as the last known content signature.

### Claim 3 (depends on 1)

The method of claim 1, wherein the content signature contained in the message comprises a content signature used by the server in a last message that carried content, wherein the content is responsive to a request, and wherein the heartbeat data is not responsive to the request.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
activating a timeout timer upon receiving the previous message;
determining that the message has been received on the channel prior to the timeout timer expiring; and
resetting and reactivating the timeout timer upon receiving the message.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
activating a timeout timer upon receiving an other message; and
re-subscribing to the channel, responsive to the timeout timer expiring prior to receiving a next message subsequent to the other message.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
clearing, responsive to sending the refresh message, the last known content signature from the previous message;
receiving, responsive to the refresh message, a response message;
setting the last known content signature with a content signature contained in the response message;
activating a timeout timer upon receiving the response message;
receiving, prior to the timeout timer expiring, a next message subsequent to the response message;
determining that the next message carries a second heartbeat data;
determining that a second content signature contained in the next message matches the last known content signature saved from the response message;
resetting and reactivating the timeout timer upon receiving the next message; and
monitoring the channel for a content update from the server.

### Claim 7

A computer usable program product comprising a computer readable storage device including computer usable code for client-side fault-tolerance in a publish-subscribe system, the computer usable code comprising:
computer usable code for receiving, on a channel, a message from a server;
computer usable code for determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data;
computer usable code for determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message;
computer usable code for sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message.

### Claim 8 (depends on 7)

The computer usable program product of claim 7, further comprising:
computer usable code for receiving an other message after the message;
computer usable code for determining that the other message carries content and a corresponding content signature; and
computer usable code for saving the content signature of the other message as the last known content signature.

### Claim 9 (depends on 7)

The computer usable program product of claim 7, wherein the content signature contained in the message comprises a content signature used by the server in a last message that carried content, wherein the content is responsive to a request, and wherein the heartbeat data is not responsive to the request.

### Claim 10 (depends on 7)

The computer usable program product of claim 7, further comprising:
computer usable code for activating a timeout timer upon receiving the previous message;
computer usable code for determining that the message has been received on the channel prior to the timeout timer expiring; and
computer usable code for resetting and reactivating the timeout timer upon receiving the message.

### Claim 11 (depends on 7)

The computer usable program product of claim 7, further comprising:
computer usable code for activating a timeout timer upon receiving an other message; and
computer usable code for re-subscribing to the channel, responsive to the timeout timer expiring prior to receiving a next message subsequent to the other message.

### Claim 12 (depends on 7)

The computer usable program product of claim 7, further comprising:
computer usable code for clearing, responsive to sending the refresh message, the last known content signature from the previous message;
computer usable code for receiving, responsive to the refresh message, a response message;
computer usable code for setting the last known content signature with a content signature contained in the response message;
computer usable code for activating a timeout timer upon receiving the response message;
computer usable code for receiving, prior to the timeout timer expiring, a next message subsequent to the response message;
computer usable code for determining that the next message carries a second heartbeat data;
determining that a second content signature contained in the next message matches the last known content signature saved from the response message;
computer usable code for resetting and reactivating the timeout timer upon receiving the next message; and
computer usable code for monitoring the channel for a content update from the server.

### Claim 13 (depends on 7)

The computer usable program product of claim 7, wherein the computer usable code is stored in a computer readable storage device in a data processing system, and wherein the computer usable code is transferred over a network from a remote data processing system.

### Claim 14 (depends on 7)

The computer usable program product of claim 7, wherein the computer usable code is stored in a computer readable storage device in a server data processing system, and wherein the computer usable code is downloaded over a network to a remote data processing system for use in a computer readable storage device associated with the remote data processing system.

### Claim 15

A data processing system for client-side fault-tolerance in a publish-subscribe system, the data processing system comprising:
a storage device, wherein the storage device stores computer usable program code; and
a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises:
computer usable code for receiving, on a channel, a message from a server;
computer usable code for determining, at a function executing using a processor and a memory, whether the message contains a heartbeat data;
computer usable code for determining, responsive to the message containing the heartbeat data, whether a content signature contained in the message matches a last known content signature saved from a previous message;
computer usable code for sending a refresh message to the channel, responsive to the content signature contained in the message not matching the last known content signature saved from a previous message.

### Claim 16 (depends on 15)

The data processing system of claim 15, further comprising:
computer usable code for receiving an other message after the message;
computer usable code for determining that the other message carries content and a corresponding content signature; and
computer usable code for saving the content signature of the other message as the last known content signature.

### Claim 17 (depends on 15)

The data processing system of claim 15, wherein the content signature contained in the message comprises a content signature used by the server in a last message that carried content, wherein the content is responsive to a request, and wherein the heartbeat data is not responsive to the request.

### Claim 18 (depends on 15)

The data processing system of claim 15, further comprising:
computer usable code for activating a timeout timer upon receiving the previous message;
computer usable code for determining that the message has been received on the channel prior to the timeout timer expiring; and
computer usable code for resetting and reactivating the timeout timer upon receiving the message.

### Claim 19 (depends on 15)

The data processing system of claim 15, further comprising:
computer usable code for activating a timeout timer upon receiving an other message; and
computer usable code for re-subscribing to the channel, responsive to the timeout timer expiring prior to receiving a next message subsequent to the other message.

### Claim 20 (depends on 15)

The data processing system of claim 15, further comprising:
computer usable code for clearing, responsive to sending the refresh message, the last known content signature from the previous message;
computer usable code for receiving, responsive to the refresh message, a response message;
computer usable code for setting the last known content signature with a content signature contained in the response message;
computer usable code for activating a timeout timer upon receiving the response message;
computer usable code for receiving, prior to the timeout timer expiring, a next message subsequent to the response message;
computer usable code for determining that the next message carries a second heartbeat data;
determining that a second content signature contained in the next message matches the last known content signature saved from the response message;
computer usable code for resetting and reactivating the timeout timer upon receiving the next message; and
computer usable code for monitoring the channel for a content update from the server.
