Border Node IP Address Management for MPLS-TP Interworking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Interworking between MPLS-TP and IP/MPLS network domains introduces complexity and increased costs due to the need for a third architecture or layer, which complicates resiliency and OAM, leading to higher capital and operating expenses.
Innovation Solution
Implementing a primary and standby border node for efficient IP address management across the network domain boundary, where the primary border node assigns and advertises IP prefixes to minimize IP address usage, allowing for seamless routing of network data traffic without requiring non-MPLS handoffs between domains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a third architecture or layer (such as VLAN) is implemented at the boundary between access network and core network to facilitate inter-domain communications, then interworking between MPLS-TP and IP/MPLS domains is enabled, but device complexity and operational complexity increase significantly
Solution Approach 1:
The patent extracts the interworking functionality from a separate third layer architecture and integrates it directly into the border nodes themselves. The border nodes perform protocol conversion and address mapping functions natively, eliminating the need for an intermediate VLAN layer or separate interworking infrastructure, thereby reducing architectural complexity while maintaining interdomain communication capability
Solution Approach 2:
The border nodes are designed to perform multiple functions: they serve as routing nodes within the core network, as access points for the access network, and as protocol translation points between MPLS-TP and IP/MPLS domains. This multi-functionality eliminates the need for dedicated interworking layers, reducing overall system complexity
2Adaptability or versatility
If a third architecture or layer is implemented for interworking, then protocol compatibility between domains is achieved, but capital expenditure and operating expenses increase significantly
Solution Approach 1:
The patent merges the interworking functions with the existing border node infrastructure. Instead of deploying separate VLAN layers or dedicated interworking devices, the border nodes are enhanced to perform protocol conversion and address mapping, consolidating multiple functions into existing hardware and reducing both capital and operational expenditures
Solution Approach 2:
The border nodes autonomously perform protocol translation and address mapping operations without requiring external interworking infrastructure. The nodes self-manage the complexity of interdomain communications, eliminating the need for additional specialized equipment and reducing deployment costs
3Ease of operation
If traditional IP address assignment is used in interworking scenarios, then each border node requires multiple IP addresses for different functions, but IP address consumption increases
Solution Approach 1:
The patent implements a unified IP address assignment scheme where a single IP address at each border node serves multiple functions: routing to the core network, routing to the access network, and participation in routing protocols. This eliminates the need for separate IP addresses for different interfaces and functions, significantly reducing IP address consumption
Solution Approach 2:
Multiple IP addressing functions are merged into a single IP address per border node. The same IP address is used for core network routing, access network routing, and routing protocol participation, consolidating what would traditionally require multiple addresses into one universal address
4Ease of operation
If multiple IP addresses are assigned to border nodes for different functions, then routing capability is enhanced, but the number of routes in the core network increases
Solution Approach 1:
By assigning a single universal IP address to each border node that handles all routing functions, the patent reduces the number of routes that need to be advertised and maintained in the core network. This single address represents the entire border node for routing purposes, simplifying routing tables and reducing computational overhead
Data Source
AI summary
IP addresses are efficiently assigned and advertised across the boundary of two network domains. The two network domains include an access network that implements MPLS-TP and a core network that implements IP, MPLS, or a combination of both. A primary BN at the domain boundary receives an assignment of an IP prefix for a VPN that connects a set of CEs to one or more SNs. The IP prefix represents a pool of IP addresses. The primary BN assigns only one IP address to both itself and a standby BN for the VPN to minimize the use of assigned IP addresses. The primary BN assigns the other IP addresses to the CEs in the VPN. The primary BN then advertises the IP prefix into the core network to enable routing of network data traffic across the network domain boundary.