Multi-Link Convergence via Binding Identity for Bandwidth Aggregation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for network access convergence, such as link backup mode, fail to achieve real bandwidth convergence across multiple networks, limiting seamless handover and quadruple-play service operations.
Innovation Solution
A multi-link convergence method where a server and client establish multiple links, perform authentication, and use a shared Binding Identity (BID) to jointly use these links for data transmission, increasing available bandwidth by converging multiple links.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If link backup mode is used for network access convergence, then service continuity is improved, but real bandwidth convergence is not achieved
Solution Approach 1:
The patent merges multiple network links into a single logical binding identified by a BID (Binding ID). Multiple physical links are combined at the data link layer through PPPoE binding, allowing simultaneous use of multiple links for data transmission while presenting a unified interface to the network layer, thereby achieving real bandwidth convergence.
Solution Approach 2:
The binding mechanism created by the patent serves multiple functions: it provides service continuity through redundancy, achieves bandwidth convergence by aggregating multiple links, enables seamless handover between access networks, and maintains compatibility with existing IP network infrastructure. This multi-functional binding layer resolves the contradiction between reliability and productivity.
2Productivity
If multiple links are established for bandwidth convergence, then available bandwidth is increased, but system complexity increases
Solution Approach 1:
The patent introduces a binding layer as an intermediary between the physical link layer and the network layer. This binding layer, identified by BID, acts as a mediator that manages multiple physical links transparently. The binding mechanism simplifies the system by providing a unified interface while handling the complexity of multiple link management, authentication, and data packet routing internally.
Solution Approach 2:
The patent creates a virtual copy of the network interface at the binding layer. Instead of managing multiple physical interfaces directly, the system creates a single logical interface (the binding) that replicates the functionality of individual links while aggregating their bandwidth. This virtual interface simplifies configuration and management while achieving bandwidth convergence.
3Adaptability or versatility
If link backup mode is used, then service handover is enabled, but seamless handover between access networks is not achieved
Solution Approach 1:
The patent implements dynamic link management where the binding can adaptively use multiple physical links based on their availability and status. The system dynamically routes data packets across different physical links while maintaining the same BID, enabling seamless handover between access networks without requiring service interruption or complex reconfiguration.
Solution Approach 2:
The binding mechanism ensures continuous data transmission by maintaining the same BID across multiple physical links. When handover between access networks is needed, the binding layer continues to operate without interruption, seamlessly transitioning data flow from one physical link to another while preserving the end-to-end connection and avoiding service disruption.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A multi-link convergence method, a server, a client, and a system are disclosed. A multi-link convergence method may include: receiving, by a server, a first binding request sent by a client by using a first link; sending, by the server, a first LSID to the client by using the first link; receiving, by the server, a first authentication request sent by the client by using the first link; performing, by the server, authentication on the first link according to the first authentication request; if the first link is authenticated successfully, sending, by the server, a BID to the client by using the first link; receiving, by the server, a second binding request sent by the client by using a second link, where the second binding request carries the BID; sending, by the server, a second LSID to the client by using the second link; receiving, by the server, a second authentication request sent by the client by using the second link; performing, by the server, authentication on the second link according to the second authentication request; and if the second link is authenticated successfully, sending, by the server, a binding acknowledgement message to the client by using the second link.