IP Library Granted Patent US 12,737,350
Granted Patent B2
US 12,737,350 · App. 18/927,695 · Granted Sep 15, 2026

Metrics and events infrastructure

Inventors: Gregory Fast (Cambridge, MA); Greg Schrock (Billerica, MA); Dillon Buchanan (Waltham, MA)
Assignee: Hewlett Packard Enterprise Development LP
G06F16/2379G06F16/2474H04L41/069H04L45/44H04L67/1095H04L45/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,737,350
App. No.
18/927,695
Granted
Sep 15, 2026
Kind
B2
Abstract

Illustrative embodiments provide an efficient, resilient high-availability (“HA”) router architecture. In illustrative embodiments, metric and event data is made resilient to node failover by replication. The same data is stored on the database of each router. Instead of pushing metrics directly from all of each node's software to each node's database, replication is instead handled by the database loader application subscribing to queues on both nodes. In some embodiments, records are written in the queues to topics that have a certain time to live (TTL), so the loader on one node has the duration of the TTL to read from the other node's queue in order to achieve replication.

Claims (35)

1 . A system comprising:

a shared network interface; and

processing circuitry in communication with storage media, the processing circuitry configured to execute a second router node of a routing system;

wherein, prior to a failure of a first router node of the routing system, and based on a configuration of the first router node to receive network traffic and send the network traffic to a device with the shared network interface, and the second router node is configured to receive the network traffic with the shared network interface without sending the network traffic,

wherein the second router node is further configured to receive, from the first router node, first analytics data related to a first routing operation of the first router node while the first router node is configured to receive the network traffic and send the network traffic to the device,

wherein the second router node is further configured to build an analytics image based at least in part on the first analytics data and second analytics data related to a second routing operation of the second router node, and

wherein, based at least in part on a failure of the first router node, the second router node is further configured to send, based on the analytics image, the network traffic to the device with the shared network interface to provide high availability for the routing system.

2 . The system of claim 1 ,

wherein the analytics image comprises a second analytics image, and

wherein the second analytics image is the same as a first analytics image built by the first router node from the first analytics data and the second analytics data.

3 . The system of claim 1 , wherein the second router node is configured to send the second analytics data to the first router node via a cross-coupling connection of the routing system.

4 . The system of claim 1 , wherein the second router node is configured to receive the first analytics data from the first router node via a cross-coupling connection of the routing system.

5 . The system of claim 1 , wherein each item of the first analytics data comprises a first source tag specifying a first router application of a plurality of first router applications executed by the first router node that generated the item.

6 . The system of claim 1 , wherein the first analytics data comprises first analytics data queues corresponding to a plurality of first router applications executed by the first router node, each of the first analytics data queues storing metric data or event data for a corresponding first router application of the plurality of first router applications.

7 . The system of claim 1 ,

wherein the processing circuitry is further configured to execute the first router node of the routing system, and

wherein the system further comprises a housing configured to house the shared network interface, the processing circuitry, the first router node, and the second router node.

8 . A method comprising:

prior to a failure of a first router node of a routing system and based on the first router node receiving network traffic and sending the network traffic to a device with a shared network interface, receiving, by a second router node of the routing system, the network traffic with the shared network interface without sending the network traffic, wherein the first router node and the second router node are executed by processing circuitry;

receiving, by the second router node and from the first router node, first analytics data related to a first routing operation of the first router node while the first router node is receiving the network traffic and sending the network traffic to the device;

building, by the second router node, an analytics image based at least in part on the first analytics data and second analytics data related to a second routing operation of the second router node; and

based at least in part on a failure of the first router node, sending, by the second router node and based on the analytics image, the network traffic to the device with the shared network interface to provide high availability for the routing system.

9 . The method of claim 8 ,

wherein the analytics image comprises a second analytics image, and

wherein the second analytics image is the same as a first analytics image built by the first router node from the first analytics data and the second analytics data.

10 . The method of claim 8 , further comprising sending, by the second router node, the second analytics data to the first router node via a cross-coupling connection of the routing system.

11 . The method of claim 8 , further comprising receiving, by the second router node, the first analytics data from the first router node via a cross-coupling connection of the routing system.

12 . The method of claim 8 , wherein each item of the first analytics data comprises a first source tag specifying a first router application of a plurality of first router applications executed by the first router node that generated the item.

13 . The method of claim 8 , wherein the first analytics data comprises first analytics data queues corresponding to a plurality of first router applications executed by the first router node, each of the first analytics data queues storing metric data or event data for a corresponding first router application of the plurality of first router applications.

14 . Non-transitory, computer-readable media comprising instructions that, when executed, are configured to cause processing circuitry to:

execute a second router node of a routing system,

wherein, prior to a failure of a first router node of the routing system and based on a configuration of the first router node to receive network traffic and send the network traffic to a device with the shared network interface, the second router node is configured to receive the network traffic with the shared network interface without sending the network traffic,

wherein the second router node is further configured to receive, from the first router node, first analytics data related to a first routing operation of the first router node while the first router node is configured to receive the network traffic and send the network traffic to the device,

wherein the second router node is further configured to build an analytics image based at least in part on the first analytics data and second analytics data related to a second routing operation of the second router node, and

wherein, based at least in part on a failure of the first router node, the second router node is further configured to send, based on the analytics image, the network traffic to the device with the shared network interface to provide high availability for the routing system.

Assignments (1)
NUNC PRO TUNC ASSIGNMENT Recorded May 6, 2026
From: 128 TECHNOLOGY, INC.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 075513/0087 →
Continuity (4)
Continuation 18473772 · Sep 25, 2023
Continuation 17104672 · Nov 25, 2020
Provisional Application 62941162 · Nov 27, 2019
Related Publication 20250117377A1 · Apr 10, 2025
References Cited (47)
US 9311479B1 · Manni et al. · 2016 [cited by applicant]
US 10002141B2 · Jalan · 2018 [cited by examiner]
US 10038601B1 · Becker · 2018 [cited by examiner]
US 10050933B2 · Froelich · 2018 [cited by applicant]
US 10123063B1 · Brown · 2018 [cited by applicant]
US 10275412B2 · Ramamurthi · 2019 [cited by applicant]
US 10411985B1 · Miller et al. · 2019 [cited by applicant]
US 10509396B2 · Sandler · 2019 [cited by examiner]
US 10635986B2 · Miyakoshi et al. · 2020 [cited by applicant]
US 10989430B2 · Kim · 2021 [cited by applicant]
US 11816095B2 · Fast et al. · 2023 [cited by applicant]
US 12164509B2 · Fast et al. · 2024 [cited by applicant]
US 20050135276A1 · Bouchat · 2005 [cited by examiner]
US 20060002394A1 · Kuranari · 2006 [cited by examiner]
US 20080209413A1 · Kakumani et al. · 2008 [cited by applicant]
US 20090245099A1 · Tsuchiya · 2009 [cited by examiner]
US 20140226566A1 · Soneda et al. · 2014 [cited by applicant]
US 20140229504A1 · Kim et al. · 2014 [cited by applicant]
US 20150341135A1 · Xia · 2015 [cited by examiner]
US 20160042014A1 · Jalan et al. · 2016 [cited by applicant]
US 20160315871A1 · Kwak · 2016 [cited by examiner]
US 20170102933A1 · Vora et al. · 2017 [cited by applicant]
US 20170195169A1 · Mills et al. · 2017 [cited by applicant]
US 20170357250A1 · Sandler et al. · 2017 [cited by applicant]
US 20180006943A1 · Dubey · 2018 [cited by examiner]
US 20180234348A1 · Goloubew · 2018 [cited by examiner]
US 20180276266A1 · Diwakar · 2018 [cited by applicant]
US 20180288146A1 · Wang et al. · 2018 [cited by applicant]
US 20190014055A1 · Gupta et al. · 2019 [cited by applicant]
US 20190138559A1 · Wang et al. · 2019 [cited by applicant]
US 20190146884A1 · Gangadharappa et al. · 2019 [cited by applicant]
US 20190363865A1 · Dong et al. · 2019 [cited by applicant]
US 20200134217A1 · Vishnyakov et al. · 2020 [cited by applicant]
US 20210067429A1 · Krochmal · 2021 [cited by applicant]
US 20210157796A1 · Fast et al. · 2021 [cited by applicant]
CN 103984694A · 2014 [cited by applicant]
CN 105683929A · 2016 [cited by applicant]
Banks, “Packet Walking Through A 128 Technology Network,” 128 Technology, Retrieved Feb. 15, 2021 from: https://www.128technology.com/resources/resources-sd-wan/128-technology-raises-30-million-series-d-financing-2/, Se… [cited by applicant]
Extended Search Report from counterpart European Application No. 20893977.7 dated Feb. 1, 2023, 8 pp. [cited by applicant]
First Office Action and Search Report, and translation thereof, from counterpart Chinese Application No. 202080094685.4 dated Jul. 19, 2023, 12 pp. [cited by applicant]
International Preliminary Report on Patentability from International Application No. PCT/US2020/062144, dated Jun. 9, 2022, 7 pp. [cited by applicant]
Notice of Intent to Grant, and translation thereof, from counterpart Chinese Application No. 202080094685.4 dated Feb. 1, 2024, 4 pp. [cited by applicant]
Pignolet et al., “Load-optimal local fast rerouting for resilient networks”, IEEE/IFIP International Conference on Dependable Systems and Networks, IEEE, Nov. 22, 2017, 12 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 17/104,672, dated May 10, 2022 through Aug. 28, 2023, 89 pp. [cited by applicant]
Prosecution History from U.S. Appl. No. 18/473,772, dated Oct. 18, 2023 through Nov. 1, 2024, 33 pp. [cited by applicant]
Notice of Intent to Grant and Text Intended to Grant from counterpart European Application No. 20893977.7 dated Dec. 22, 2025, 57 pp. [cited by applicant]
Extended European Search Report and Search Opinion received for European Application No. 20893977.7, mailed on Jan. 2, 2023, 8 pages. [cited by applicant]