Moveable IP Address Failover for Cloud Network Resilience

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Telecommunications networks face frequent outages due to various factors, leading to downtime, productivity loss, and security risks, necessitating a robust and resilient network solution.

Innovation Solution

A method and network node for IP address management that reallocates IP addresses from failing nodes to functional nodes, enabling seamless data routing through a moveable IP address mechanism, particularly in cloud environments lacking Layer 2 connectivity and ECMP routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network devices are updated frequently to improve functionality and security, then the network becomes more susceptible to bugs, exploits and cyberattacks, but network resilience and availability deteriorate

Engineering Contradiction:
Improvenetwork functionalityVSAvoidnetwork availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs liveness detection and health checks on network nodes before failures occur. By monitoring node status proactively and detecting issues early, the system can initiate failover procedures in advance, preventing complete network outages and maintaining availability during updates and potential attacks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements IP address allocation to standby nodes (third network nodes) as a preventive measure. When a node fails, the pre-configured IP address allocation mechanism allows immediate failover without service interruption. This cushioning approach ensures network resilience against bugs, exploits, and cyberattacks by having ready-replacement nodes.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

2Loss of time

If network outages are resolved quickly to minimize downtime costs, then productivity loss is reduced, but the complexity of detecting and measuring network node failures increases

Engineering Contradiction:
Improvenetwork downtimeVSAvoidnode failure detection
Core Design Contradiction:
Loss of timeVSDifficulty of detecting and measuring

Solution Approach 1:

The system implements continuous liveness detection that provides real-time feedback on network node status. This feedback mechanism monitors node health and triggers automatic IP address reallocation when failures are detected, enabling rapid response to outages and minimizing downtime while maintaining straightforward detection through standardized health check protocols.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The network system performs self-diagnosis through automated liveness detection and self-healing through automatic IP address reallocation from failed nodes to standby nodes. This self-service approach reduces the complexity of manual failure detection and enables rapid automated response to outages, minimizing productivity loss without requiring complex intervention procedures.

Inventive Principle:
Principle #25Self-service

3Reliability

If IP address reallocation is performed manually to ensure network resilience, then data security is maintained, but the speed of failover and network recovery decreases

Engineering Contradiction:
Improvedata securityVSAvoidfailover speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The system implements automated IP address reallocation that performs failover without manual intervention. The automated mechanism detects node failures through liveness detection and automatically reallocates IP addresses from failed nodes to standby nodes, maintaining data security through controlled automated processes while achieving rapid failover speeds that manual procedures cannot match.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The automated failover system uses real-time feedback from liveness detection to trigger IP address reallocation. This feedback-driven automated process maintains security by following predefined allocation protocols while achieving rapid failover, eliminating the speed limitation of manual procedures while preserving security through controlled automated decision-making.

Inventive Principle:
Principle #23Feedback

4Reliability

If network nodes are monitored continuously to detect failures early, then network availability is improved, but the use of energy and computational resources increases

Engineering Contradiction:
Improvenetwork availabilityVSAvoidmonitoring energy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements selective liveness detection that monitors only critical network nodes and essential failure modes rather than continuous comprehensive monitoring of all nodes. This partial monitoring approach maintains network availability by detecting failures in key nodes while reducing energy and computational resource consumption compared to exhaustive monitoring of the entire network.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12634225B2Moveable IP based network resilience
Publication Date: 2026.05.19 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US12634225B2 patent drawing
  • US12634225B2 patent drawing
  • US12634225B2 patent drawing

AI summary

A network node and a method for moveable IP based network resilience. A method at a first network node for IP address management in a network that is not capable to perform load balance with L3 or below information only comprises: determining whether a second network node, to which a first IP address is allocated, fails to function or not; and in response to determining that the second network node fails to function, de-allocating the first IP address from the second network node; and allocating the first IP address to a third network node, such that a fourth network node is enabled to route data, which is intended to be routed to the first IP address, to the third network node rather than the second network node.