Device-Level Network Switching with Heartbeat Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network switching technologies fail to ensure reliable and continuous connectivity for telehealth devices, particularly in environments with unstable network connections, leading to potential disruptions in critical communication scenarios.

Innovation Solution

Implementing a device-level network switching mechanism that utilizes multiple network interfaces, prioritizes connectivity based on a predetermined order, and switches to a secondary interface upon failure, ensuring continuous access to services by associating timestamps with interface failures and selecting the next available interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single network interface is used for connectivity, then device complexity is reduced, but network reliability deteriorates due to potential failures in unstable network environments

Engineering Contradiction:
Improvenetwork connectivity reliabilityVSAvoidnetwork interface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network interface functionality is segmented into multiple independent network interfaces (first network interface and second network interface), each capable of operating independently. This segmentation allows the system to divide the connectivity function across multiple interfaces, improving reliability by ensuring that failure of one interface does not compromise overall connectivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes the operational state of network interfaces based on detected failure conditions. When a failure is detected on the first network interface, the system transitions from using only the first interface to utilizing the second interface, thereby adapting the connectivity parameters to maintain reliable operation despite changing network conditions.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If network switching is implemented upon failure, then connectivity reliability is improved, but response time deteriorates due to the need for detection and switching operations

Engineering Contradiction:
Improvenetwork connectivity reliabilityVSAvoidconnectivity restoration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary configuration of multiple network interfaces and establishes a predetermined switching mechanism before failures occur. The heartbeat monitoring mechanism is pre-configured to continuously check interface status, and the switching logic is prepared in advance, enabling rapid response when failures are detected without requiring complex real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism through heartbeat monitoring, where the continuous detection of interface status provides real-time information about connectivity health. This feedback loop enables the system to detect failures promptly and trigger the switching mechanism, minimizing the time loss associated with connectivity restoration.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250310408A1Device-Level Network Switching
Publication Date: 2025.10.02 VITALCHAT INC
  • US20250310408A1 patent drawing
  • US20250310408A1 patent drawing
  • US20250310408A1 patent drawing

AI summary

A device includes a plurality of network interfaces that include a first network interface and secondary network interfaces, and a processor. The processor is configured to execute instructions stored in a memory to: configure the device to use the first network interface to connect to a service over a network; send a heartbeat request from the device to a heartbeat responder via the first network interface; and in response to a failure to receive a response to the heartbeat request: associate, with the first network interface, a timestamp indicating a time of failure, select a second network interface from the plurality of network interfaces based on a predetermined priority order and excluding interfaces associated with a timestamp indicating failure within a threshold amount of time; and configure the device to use the selected second network interface to connect to the service.