# US 2025/0211368 A1 · Multi-link operation with localized performance of b-ack functions

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0211368 A1
- Document ID: US20250211368A1
- Status: Published application
- Kind: A1
- Application number: 19/076,115
- Filed: 2025-03-11
- Published: 2025-06-26
- Earliest claimed: 2021-01-08
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Malcolm Muir SMITH; Brian D. HART; Pooya MONAJEMI; Santosh Babaji KULKARNI; Vishal Satyendra DESAI
- Web page: https://patentgrep.com/patent/US20250211368A1

## CPC

- H04L 1/1621: {Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers}
- H04W 76/15: Setup of multiple wireless link connections
- H04L 1/1614: {using bitmaps}
- H04L 1/1635: {Cumulative acknowledgement, i.e. the acknowledgement message applying to all previous messages}
- H04L 1/1893: {Physical mapping arrangements (physical resource mapping in general H04L5/00)}
- H04W 8/12: between location registers or mobility servers
- H04W 36/22: for handling the traffic
- H04W 40/02: Communication route or path selection, e.g. power-based or shortest path routing
- H04W 76/11: Allocation or use of connection identifiers
- H04W 36/18: for allowing seamless reselection, e.g. soft reselection
- H04W 84/12: WLAN [Wireless Local Area Networks]
- H04W 88/10: adapted for operation in multiple networks, e.g. multi-mode access points
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

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.

## Claims

### Claim 1

An apparatus comprising:
an Upper Service Access Point (U-SAP) that a client device is logically associated with to connect to a network;
a first Access Point (AP) that the client device is physically connected to on a first link, the first AP including a first Lower Service Access Point (L-SAP); and
a second AP that the client device is physically connected to on a second link, the second AP including a second L-SAP;
wherein the U-SAP is operable to:
establish a Traffic Identifier (TID)-to-link map that assigns a first subset of a plurality of TIDs to the first link and a second subset of the plurality of TIDs to the second link; and
use the TID-to-link map to direct data received at the U-SAP over one of the first link and the second link for transmission to the client device; and
wherein, based on whether the data transmission is over the first link or the second link, the first L-SAP or the second L-SAP is respectively operable to locally perform Block Acknowledgment (B-ACK) functions.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein, based on whether the data transmission is over the first link or the second link, the first L-SAP or the second L-SAP is respectively operable to locally perform frame per-TID frame aggregation functions.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the B-ACK functions comprise computing and returning a B-ACK to the client device.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the B-ACK functions comprise receiving, from the client device, an acknowledgement of the data transmission.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the plurality of TIDs include a TID pair for one or more Access Categories (ACs) of the network, and to establish the TID-to-link map, the U-SAP is further operable to:
assign a first TID of a TID pair for an AC to the first link; and
assign a second TID of the TID pair for the AC to the second link.

### Claim 6

A method comprising:
establishing, by an Upper Service Access Point (U-SAP) of a multi-Access Point (AP) Multi-Link Device (MLD) entity, a traffic identifier (TID)-to-link map that assigns subsets of a plurality of TIDs to at least two links of the multi-AP MLD entity;
using the TID-to-link map to direct data received at the U-SAP over one of the at least two links for transmission to a client device; and
locally performing, by a respective Lower Service Access Point (L-SAP) of an AP of the AP MLD entity based on the one of the at least two links over which the data is transmitted, Block Acknowledgment (B-ACK) functions, wherein:
the client device logically associates with the U-SAP to connect to a network; and
the client device is physically connected to at least:
a first AP of the multi-AP MLD entity on a first link of the at least two links, the first AP comprising a first L-SAP; and
a second AP of the multi-AP MLD entity on a second link of the at least two links, the second AP comprising a second L-SAP.

### Claim 7 (depends on 6)

The method of claim 6, wherein, based on whether the data transmission is over the first link or the second link, the first L-SAP or the second L-SAP is respectively operable to locally perform frame per-TID frame aggregation functions.

### Claim 8 (depends on 6)

The method of claim 6, wherein the B-ACK functions comprise computing and returning a B-ACK to the client device.

### Claim 9 (depends on 6)

The method of claim 6, wherein the B-ACK functions comprise receiving, from the client device, an acknowledgement of the data transmission.

### Claim 10 (depends on 6)

The method of claim 6, wherein the plurality of TIDs include a TID pair for one or more Access Categories (ACs) of the network, and to establish the TID-to-link map, the method further comprising, by the U-SAP:
assigning a first TID of a TID pair for an AC to the first link; and
assigning a second TID of the TID pair for the AC to the second link.

### Claim 11 (depends on 6)

The method of claim 6, wherein the first AP and the second AP are non-collocated in the network.
