Multiplexing Backbone and Non-Backbone Traffic on Common Ports
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing communication networks require separate links and ports for backbone and non-backbone traffic, leading to increased complexity and cost in infrastructure construction and technology migration, particularly in IEEE 802.1ah backbone network architectures.
Innovation Solution
A method and apparatus that multiplexes both backbone and non-backbone traffic over a common port using a Provider Network Port (PNP) and Customer Network Port (CNP), eliminating the need for distinct ports and reducing infrastructure complexity by distinguishing traffic based on VLAN identifiers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate links and ports are used for backbone and non-backbone traffic, then traffic can be clearly distinguished and managed, but infrastructure complexity and construction cost increase
Solution Approach 1:
The patent combines backbone traffic and non-backbone traffic into a single common port (PNP/CNP) by merging previously separate transmission paths. This reduces infrastructure complexity while maintaining traffic distinction through VLAN identifier-based differentiation, directly resolving the contradiction between clear traffic management and reduced infrastructure complexity.
Solution Approach 2:
The common port (PNP/CNP) is designed to handle multiple types of traffic (both backbone and non-backbone) simultaneously. This multi-functional port replaces the need for separate dedicated ports, reducing the number of infrastructure components while maintaining the ability to clearly distinguish and manage different traffic types through VLAN identifiers.
2Ease of operation
If separate ports are used for backbone and non-backbone traffic, then port functions are specialized and clear, but the number of ports and infrastructure components increases
Solution Approach 1:
The patent merges the functions of separate backbone ports and non-backbone ports into a single common port. This reduces the total number of ports required in the infrastructure while maintaining operational clarity through the use of VLAN identifiers that clearly distinguish between traffic types within the unified port.
Solution Approach 2:
The common port is designed with universal functionality to handle both backbone and non-backbone traffic. This multi-functional approach reduces the quantity of ports needed while maintaining clear port function through VLAN-based traffic differentiation and appropriate B-tagging operations.
3Ease of manufacture
If distinct ports are required for backbone and non-backbone traffic, then network architecture is simplified in design, but infrastructure construction cost and complexity increase
Solution Approach 1:
The patent merges infrastructure components by allowing a single common port to carry both backbone and non-backbone traffic. This reduces infrastructure construction complexity and cost by eliminating the need for separate physical ports and links, while maintaining design simplicity through VLAN identifier-based traffic management.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An apparatus including a first interface configured to transmit or receive backbone traffic, a second interface configured to transmit or receive non-backbone traffic, and a third interface in communication with the first interface and second interface, the third interface configured to multiplex or demultiplex the backbone traffic and the non-backbone traffic is disclosed. The backbone traffic is traffic that will be, is, or has been B-tagged. Also disclosed is a node including a processor configured to implement a method including receiving a first data stream including backbone traffic, receiving a second data stream comprising non-backbone traffic, and multiplexing the first data stream with the second data stream.