Autonomous Loop Device Pool Management for Service Continuity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing pool management mechanism in communication networks fails to ensure continuity of services when a node device fails, leading to loss of service contexts and reduced network reliability due to the lack of peer interfaces between members.

Innovation Solution

A method and system for device pool management that establishes backup relations between node devices in an autonomous loop, allowing for data backup and load state information sharing, enabling seamless service takeover by other nodes in case of failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a pool management mechanism is introduced to implement load sharing and disaster recovery, then service interruption is reduced and network reliability is improved, but service contexts are lost when a node fails due to lack of peer interfaces between members

Engineering Contradiction:
Improvenetwork reliabilityVSAvoidservice context loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies preliminary action by establishing backup relationships between pool members in advance. Each member pre-configures peer interfaces and sets up data synchronization mechanisms with other members before failures occur. When a node fails, the backup relationships enable immediate service context recovery without information loss, resolving the contradiction between reliability improvement and information loss prevention.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple core network nodes run concurrently in a pool area, then service continuity is improved through load sharing, but service contexts are lost when a node fails due to no backup mechanism

Engineering Contradiction:
Improveservice continuityVSAvoidservice context loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent applies copying by creating backup copies of service contexts across multiple pool members. Each member maintains copies of service context data through peer interfaces and synchronization mechanisms. When a node fails, the copied service contexts on other members enable immediate takeover, ensuring service continuity while preventing information loss.

Inventive Principle:
Principle #26Copying

3Device complexity

If peer interfaces are not established between pool members, then device complexity is reduced, but synchronization, backup, and handover operations become impracticable

Engineering Contradiction:
Improvepool configuration complexityVSAvoidsynchronization and backup operation
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent applies segmentation by dividing the pool management functionality into independent peer interface modules. Each pool member is equipped with standardized peer interfaces that can be configured independently through management systems. This segmentation allows synchronization and backup operations to be performed through simple interface interactions without increasing overall system complexity, resolving the contradiction between device complexity and operational ease.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8780724B2Method, node device, and communication system for device pool management
Publication Date: 2014.07.15 HUAWEI TECH CO LTD
  • US8780724B2 patent drawing
  • US8780724B2 patent drawing
  • US8780724B2 patent drawing

AI summary

A method, a node device, and a communication system for device pool management are disclosed. The method includes: obtaining autonomous loop configuration data which describes relations between a node device and its ancestor node device and between the node device and its descendant node device in an autonomous loop by using identifiers of node devices in the autonomous loop; and setting up a backup relation between a node device and an ancestor node device as well as a backup relation between the node device and a descendant node device according to the autonomous loop configuration data, receiving and storing backup data sent by the ancestor node device, and sending data of the node device to be backed up to the descendant node device. Therefore, the service continuity is ensured when some of the node devices disengage from the autonomous loop.