Partitioned Subnet Routing With Dynamic Host Liveness Monitoring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for routing in partitioned subnets, such as using bridge networks and L2 switches, are costly, non-scalable, and complex, and fail to detect silent hosts effectively.

Innovation Solution

A method and system that utilize performance measurement (PM) based liveness monitoring, combined with border gateway protocol (BGP) and address resolution protocol (ARP/Neighbor Discovery), to dynamically manage host routes and detect host liveness, enabling scalable and cost-effective routing in partitioned subnets without the need for additional hardware or complex signaling protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If bridge network and L2 switch are used to handle partitioned subnets, then routing functionality is achieved, but hardware cost increases and device complexity increases

Engineering Contradiction:
Improverouting functionalityVSAvoidhardware complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the bridge network hardware component and replaces it with a software-based routing solution using BGP protocols. The L2 switch hardware is also removed, with functionality implemented through software routing tables and performance measurement probes, thereby reducing hardware complexity while maintaining routing functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces the mechanical/hardware bridge network and L2 switch system with a software-based routing mechanism using BGP protocols and performance measurement probes. This substitution eliminates the need for expensive hardware while achieving the same routing functionality through software processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If bridge network and L2 switch are used to handle partitioned subnets, then routing functionality is achieved, but hardware cost increases

Engineering Contradiction:
Improverouting functionalityVSAvoidhardware cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent removes the expensive bridge network and L2 switch hardware components, replacing them with software-based routing solutions that can be implemented on standard network devices, thereby significantly reducing hardware costs while maintaining routing functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent substitutes the expensive hardware bridge network and L2 switches with a software-based routing mechanism using BGP protocols, eliminating the need for specialized hardware and reducing overall system cost while achieving the same routing objectives.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If bridge network is used to handle partitioned subnets, then routing functionality is achieved, but scalability is limited

Engineering Contradiction:
Improverouting functionalityVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic routing using BGP protocols that automatically adapt to network changes, host movements, and topology modifications. The performance measurement probes dynamically monitor host liveness and trigger route updates, enabling the system to scale dynamically as network conditions change without requiring manual reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates performance measurement probes that continuously monitor host liveness and provide feedback to the routing system. When hosts move or become unavailable, the probes detect these changes and trigger automatic route updates, enabling scalable and adaptive routing that responds to real-time network conditions.

Inventive Principle:
Principle #23Feedback

4Reliability

If bridge network solution is used, then partitioned subnet routing is achieved, but operational complexity increases

Engineering Contradiction:
Improverouting functionalityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service routing where the system automatically manages its own routing tables and liveness monitoring without requiring manual intervention. Performance measurement probes automatically detect host availability, and BGP protocols automatically propagate routing changes, eliminating complex operational procedures while maintaining reliable routing functionality.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent uses performance measurement probes to continuously monitor host liveness and provide automatic feedback to the routing system. This automated feedback mechanism eliminates the need for manual operational interventions, reducing operational complexity while ensuring reliable routing through continuous automated monitoring and adaptation.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250323868A1Solution for routing in a partitioned subnet based on dynamic liveness monitoring
Publication Date: 2025.10.16 CISCO TECHNOLOGY INC
  • US20250323868A1 patent drawing
  • US20250323868A1 patent drawing
  • US20250323868A1 patent drawing

AI summary

Routing of packets in a partitioned subnet is realized in a data center (DC) by using a first type of address prefix (e.g., /24 prefixes) to advertise respective hosts to its peers (i.e., external traffic). For routing traffic within the DC (i.e., internal traffic), a second type of address prefix (e.g., /32 prefixes) that is longer than the first type. Switches/routers within the DC perform liveness probes detecting which hosts are connected thereto and updating a table (e.g., an ARP/ND table) to include the connected hosts (e.g., removing hosts that fail to respond). For changes to the table, a gate protocol (e.g., BGP or IGP) is triggered such that the switch/router advertises within the DC fabric the second type of address prefix for the host routes of the connected host. The switch/router also configures Liveness sessions for the connected hosts.