Multi-Link B-ACK Localization for Seamless MLD Roaming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-link device (MLD) architectures face challenges in seamless roaming due to the inability to perform per-Traffic Identifier (TID) frame aggregation and Block Acknowledgment (B-ACK) functions efficiently across non-collocated Access Points (APs, leading to delayed acknowledgments and potential service disruptions.
Innovation Solution
A multi-AP MLD entity architecture is introduced, where an Upper Service Access Point (U-SAP) establishes a TID-to-link map, and Lower Service Access Points (L-SAPs) perform localized per-TID frame aggregation and B-ACK functions, eliminating transport hops and ensuring timely acknowledgments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If per-TID frame aggregation and B-ACK functions are performed across non-collocated APs in existing MLD architectures, then multi-link capacity is increased, but acknowledgment delay occurs and service disruption happens
Solution Approach 1:
The patent segments the MLD entity into collocated APs that share common hardware resources (transport, processor, memory). This segmentation allows B-ACK functions to be performed locally at the collocated AP level rather than across distributed non-collocated APs, eliminating transport hops and reducing acknowledgment delay while maintaining multi-link capacity through the coordinated operation of multiple collocated APs.
Solution Approach 2:
The patent introduces collocated APs as intermediaries that provide shared hardware resources (transport interface, processor, memory) between multiple RF links. These intermediaries enable efficient local processing of frame aggregation and B-ACK functions, acting as a mediator that resolves the conflict between multi-link capacity requirements and low-latency acknowledgment needs.
2Adaptability or versatility
If B-ACK functions are performed across non-collocated APs, then multi-link operation is enabled, but transport hops increase causing delayed acknowledgments
Solution Approach 1:
The patent segments the network architecture into collocated AP groups where each group shares common hardware resources. This segmentation enables multi-link operation within each collocated group without requiring transport hops between APs, thereby reducing system complexity while maintaining adaptability through the ability to coordinate multiple collocated APs.
Solution Approach 2:
The patent merges the transport, processor, and memory resources of collocated APs into shared hardware resources. This merging eliminates the need for inter-AP transport hops for B-ACK functions, reducing device complexity while preserving multi-link operation capabilities through the coordinated use of multiple collocated APs with shared resources.
3Ease of operation
If frame aggregation and B-ACK are performed centrally, then coordination is simplified, but acknowledgment time exceeds required period
Solution Approach 1:
The patent segments B-ACK functionality into collocated AP-level operations rather than centralized control. Each collocated AP independently performs frame aggregation and B-ACK for its associated links using shared local resources, eliminating coordination complexity while achieving low-latency acknowledgments through local processing without centralized intervention.
Solution Approach 2:
The patent enables collocated APs to self-service by locally performing frame aggregation and B-ACK functions using shared hardware resources. This self-service approach eliminates the need for centralized coordination, simplifying operation while reducing acknowledgment time through immediate local processing without waiting for centralized control decisions.
Data Source
AI summary
Seamless client roaming for Multi-Link Device (MLD) clients may be provided. First, a Traffic Identifier (TID)-to-link map may be established by an Upper Service Access Point (U-SAP) of a multi-AP MLD entity that assigns subsets of TIDs to at least two links of the entity. For example, a client device logically associates with the U-SAP, while the client device physically connects to a first and second AP of the entity on a respective first and second link, where the first and second AP include first and second Lower Service Access Points (L-SAPs) and are non-collocated. Next, using the map, data received at the U-SAP is directed over one of the two links for transmission to the client device. Further, frame aggregation and block acknowledgment functions may be performed by one of the first or second L-SAP based on whether data transmission is over the first or second link.