# US 10,313,198 B2 · Crash recovery for smart objects

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

- Number: US 10,313,198 B2
- Document ID: US10313198B2
- Status: Granted
- Kind: B2
- Application number: 15/113,315
- Filed: 2015-01-22
- Published: 2017-01-05
- Granted: 2019-06-04
- Earliest claimed: 2014-01-23
- Assignees: Koninklijke KPN N.V.; Imec Vzw; Universiteit Gent
- Applicants: Koninklijke Kpn N.V.; Imec Vzw; Universiteit Gent
- Inventors: Floris Van Den Abeele; Jeroen Hoebeke
- Web page: https://patentgrep.com/patent/US10313198B2

## CPC

- 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 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/085: Retrieval of network configuration; Tracking network configuration history
- H04L 67/00: Network arrangements or protocols for supporting network services or applications (user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for enabling restoration of an operational state on a server node is disclosed. The method includes intercepting, by a state directory, traffic between the server node and a client communicably connected to the server node over a network to derive the operational state. At least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node. The method further includes storing the operational state in the state directory, detecting, by the state directory, that the server node has lost the operational state, and providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state.

## Claims

### Claim 1

A method for enabling restoration of an operational state on a server node, the method comprising:
intercepting, by a state directory, traffic between a client communicably connected to the server node over a network and the server node to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
storing the operational state in the state directory;
detecting, by the state directory, that the server node has lost the operational state;
providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state;
intercepting, by the state directory, further traffic between the server node and the client to determine that the operational state is to be removed from the state directory; and
removing the operational state from the state directory after said determination.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the state directory is located in a cloud, in a gateway between the server node and the client, or in a local network comprising the server node.

### Claim 3

A method for enabling restoration of an operational state on a server node, the method comprising:
intercepting, by a state directory, traffic between a client communicably connected to the server node over a network and the server node to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
storing the operational state in the state directory;
detecting, by the state directory, that the server node has lost the operational state;
providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state;
determining, by the state directory, that the operational state is to be removed from the state directory as a result of the lack of further traffic between the server node and the client; and
removing the operational state from the state directory after said determination.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the state directory is located in a cloud, in a gateway between the server node and the client, or in a local network comprising the server node.

### Claim 5

A method for enabling restoration of an operational state on a server node, the method comprising:
intercepting, by a state directory, traffic between a client communicably connected to the server node over a network and the server node to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
storing the operational state in the state directory;
detecting, by the state directory, that the server node has lost the operational state;
providing, by the state directory, the operational state to the server node after detecting that the server node has lost the operational state;
wherein the state directory comprises an intermediate node in the network located as to be able to monitor bootstrapping traffic from the server node and wherein the state directory detects that the server node has lost the operational state as a result of receiving, from the server node, a request for bootstrapping.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the state directory provides the operational state to the server node by replaying at least a portion of the part of the traffic between the server node and the client that led to the establishment of the operational state on the server node.

### Claim 7 (depends on 5)

The method according to claim 5, wherein the state directory is located in a cloud, in a gateway between the server node and the client, or in a local network comprising the server node.

### Claim 8

A state directory for enabling restoration of an operational state on a server node, the state directory comprising:
an interception unit for intercepting traffic between the server node and a client communicably connected to the server node over a network to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
a memory for storing the operational state;
a processor for detecting that the server node has lost the operational state; and a transmitter for providing the operational state to the server node after detecting that the server node has lost the operational state;
the interception unit further configured for intercepting further traffic between the server node and the client to determine that the operational state is to be removed from the state directory; and
the processor further configured to remove the operational state from the state directory after said determination.

### Claim 9 (depends on 1)

A computer-readable non-transitory storage medium having computer program code stored thereon configured for, when run on a computer, executing the method steps according to claim 1.

### Claim 10

A state directory for enabling restoration of an operational state on a server node, the state directory comprising:
an interception unit for intercepting traffic between the server node and a client communicably connected to the server node over a network to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
a memory for storing the operational state;
a processor for detecting that the server node has lost the operational state; and a transmitter for providing the operational state to the server node after detecting that the server node has lost the operational state;
the processor further configured to determine that the operational state is to be removed from the state directory as a result of the lack of further traffic between the server node and the client and to remove the operational state from the state directory after said determination.

### Claim 11

A state directory for enabling restoration of an operational state on a server node, the state directory comprising:
an interception unit for intercepting traffic between the server node and a client communicably connected to the server node over a network to derive the operational state, where at least a part of the traffic between the server node and the client leads to establishment of the operational state on the server node;
a memory for storing the operational state;
a processor for detecting that the server node has lost the operational state; and a transmitter for providing the operational state to the server node after detecting that the server node has lost the operational state;
wherein the state directory comprises an intermediate node in the network located as to be able to monitor bootstrapping traffic from the server node and wherein the state directory detects that the server node has lost the operational state as a result of receiving, from the server node, a request for bootstrapping.

### Claim 12 (depends on 11)

The state directory according to claim 11, wherein the state directory provides the operational state to the server node by replaying at least a portion of the part of the traffic between the server node and the client that led to the establishment of the operational state on the server node.

### Claim 13 (depends on 3)

A computer-readable non-transitory storage medium having computer program code stored thereon configured for, when run on a computer, executing the method steps according to claim 3.

### Claim 14 (depends on 5)

A computer-readable non-transitory storage medium having computer program code stored thereon configured for, when run on a computer, executing the method steps according to claim 5.
