Multi-Domain Network Protection via Segmented Switching Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multi-domain network protection mechanisms require a large number of service access nodes to be reconstructed and upgraded, leading to complex device implementation and high costs due to their inability to support multiple source and sink nodes effectively.
Innovation Solution
A protection method and system that allows a second node to disconnect a first protection path and connect a sub-path within its domain when a link fails, using the second node as an endpoint, and sends failure monitoring messages to maintain service continuity across domains, optimizing protection path reconstruction without needing extensive upgrades on non-intersecting nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple protection paths are configured on protection switching nodes to support multi-source and multi-sink protection, then protection reliability is improved, but device complexity and implementation costs increase due to the need to upgrade a large number of service access nodes
Solution Approach 1:
The patent segments the protection domain into multiple protection domains, each with its own protection switching node. Service access nodes are divided into those that require full multi-source/multi-sink support and those that can use simpler single-source/single-sink mechanisms. This segmentation allows complex protection functionality to be concentrated at boundary nodes while keeping access nodes simple.
Solution Approach 2:
The patent introduces protection switching nodes as intermediary elements between service access nodes and the core network. These intermediary nodes handle the complex multi-source/multi-sink protection switching functionality, allowing service access nodes to use simpler mechanisms while still benefiting from robust end-to-end protection.
2Adaptability or versatility
If service access nodes are upgraded to support multiple source and sink nodes, then protection capability is improved, but implementation costs increase
Solution Approach 1:
The patent segments the network into protection domains where only boundary nodes (protection switching nodes) require advanced multi-source/multi-sink capabilities. The majority of service access nodes can remain simple single-source/single-sink devices, significantly reducing upgrade costs while maintaining overall system protection capability.
Solution Approach 2:
The patent applies different protection mechanisms to different parts of the network based on their functional requirements. Protection switching nodes at domain boundaries implement complex multi-source/multi-sink protection, while service access nodes use simpler mechanisms. This local differentiation optimizes both capability and cost.
3Device complexity
If traditional linear protection mechanism is used with single source and sink, then device implementation is simplified, but protection effectiveness decreases when multiple domains are involved
Solution Approach 1:
The patent divides the multi-domain network into multiple protection domains, each managed by a protection switching node. Within each domain, simple linear protection can be used, but across domain boundaries, the segmented structure enables effective end-to-end protection through coordinated switching at boundary nodes.
Solution Approach 2:
Protection switching nodes act as intermediaries that coordinate between simple linear protection segments. They implement the complex multi-source/multi-sink switching logic needed for cross-domain protection while allowing constituent segments to use simpler mechanisms.
Data Source
Figure 1~2
Figure 3~4
Figure 5~6a
AI summary
The present invention relates to the field of network communications, and specifically discloses a protection method for a multi-domain network, including: after a second node detects that a first link fails, disconnecting a first protection path on the node, connecting a first sub-path and a path that is within a second domain, uses the second node as an endpoint, and is used to bear a service; sending, on the first sub-path, a first failure monitoring message that carries first maintenance information to a third node, where the first maintenance information is the same as second maintenance information carried in a second failure monitoring message; the second failure monitoring message is a message that is sent on the first protection path by a first node to the third node and is used to monitor a failure of the first protection path; the first link is a link between the first node and the second node; the first protection path is formed by splicing the first sub-path and a second sub-path and is a protection path of a first working path; and the first working path is a working path of the service between the first node and the third node within a first domain.