# US 2022/0022087 A1 · Method and apparatus for wireless communications

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

- Number: US 2022/0022087 A1
- Document ID: US20220022087A1
- Status: Published application
- Kind: A1
- Application number: 17/381,151
- Filed: 2021-07-20
- Published: 2022-01-20
- Earliest claimed: 2020-07-20
- Assignees: NXP USA, Inc.
- Applicants: NXP USA, Inc.
- Inventors: Liwen Chu; Young Hoon Kwon; Hongyuan Zhang
- Web page: https://patentgrep.com/patent/US20220022087A1

## CPC

- H04W 28/0263: {involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]}
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 52/0216: {using a pre-established activity schedule, e.g. traffic indication frame}
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Embodiments of a method and an apparatus for wireless communications are disclosed. In an embodiment, a method for wireless communications involves connecting, by a first multi-link device (MLD) to a second MLD via at least two links, mapping, by the first MLD, a Traffic Identifier (TID) to at least one of the two links associated with the first MLD and the second MLD, transmitting, by the first MLD to the second MLD, frames that correspond to the TID on at least one of the two links according to the mapping by the first MLD, and receiving, by the first MLD from the second MLD, subsequent frames on at least one of the two links according to the mapping by the first MLD.

## Claims

### Claim 1

A method for wireless communications, the method comprising:
connecting, by a first multi-link device (MLD) to a second MLD via at least two links;
mapping, by the first MLD, a Traffic Identifier (TID) to at least one of the two links associated with the first MLD and the second MLD;
transmitting, by the first MLD to the second MLD, frames that correspond to the TID on at least one of the two links according to the mapping by the first MLD; and
receiving, by the first MLD from the second MLD, subsequent frames on at least one of the two links according to the mapping by the first MLD.

### Claim 2 (depends on 1)

The method of claim 1, wherein mapping the TID to at least one of the two links includes:
negotiating, by the first MLD, TID-to-Link Mapping with the second MLD, wherein negotiating the TID-to-Link Mapping with the second MLD includes:
transmitting, by the first MLD to the second MLD, a TID-to-Link Mapping Request frame that includes a request Token and requested TID-to-Link Mapping information; and
receiving, by the first MLD from the second MLD, a TID-to-Link Mapping Response frame that includes a response Token and a negotiation result.

### Claim 3 (depends on 2)

The method of claim 2, wherein the method involves matching the request Token of the TID-to-Link Mapping Request frame to the TID-to-Link Mapping Response frame transmitted by the second MLD.

### Claim 4 (depends on 2)

The method of claim 2, wherein at least one of the TID-to-Link Mapping Request frame and the TID-to-Link Mapping Response frame includes a TID-to-Link Mapping element.

### Claim 5 (depends on 4)

The method of claim 4, wherein the TID-to-Link Mapping element includes a TID-to-Link Mapping Information field with an up-link (UL) Link Bitmap subfield, a down-link (DL) Link Bitmap subfield, and corresponding TID Bitmap subfields for the UL Link Bitmap subfield and the DL Link Bitmap subfield.

### Claim 6 (depends on 2)

The method of claim 2, wherein the negotiation result included in the TID-to-Link Mapping Response frame indicates that the TID-to-Link Mapping is accepted.

### Claim 7 (depends on 2)

The method of claim 2, wherein the negotiation result included in the TID-to-Link Mapping Response frame indicates that the TID-to-Link Mapping is rejected and includes a rejection reason.

### Claim 8 (depends on 7)

The method of claim 7, wherein the TID-to-Link Mapping Response frame that indicates that the TID-to-Link Mapping is rejected includes Suggested TID-to-Link Mapping information.

### Claim 9 (depends on 1)

The method of claim 1, wherein mapping the TID to at least one of the two links includes the first MLD using a TID-to-Link Mapping teardown to resume default TID-to-Link Mapping.

### Claim 10 (depends on 9)

The method of claim 9, wherein the default TID-to-Link Mapping is accepted when the first MLD uses the TID-to-Link Mapping teardown to resume the default TID-to-Link Mapping.

### Claim 11 (depends on 1)

The method of claim 1, wherein mapping the TID to at least one of the two links includes:
transmitting, by the first MLD to the second MLD, a TID-to-Link Mapping Request frame that requests default TID-to-Link Mapping; and
receiving, by the first MLD from the second MLD, a TID-to-Link Mapping Response frame that indicates that the default TID-to-Link Mapping is accepted.

### Claim 12 (depends on 1)

The method of claim 1, wherein mapping the TID to at least one of the two links includes:
announcing, by the first MLD, TID-to-Link Mapping with the second MLD, wherein announcing the TID-to-Link Mapping with the second MLD includes:
transmitting, by the first MLD to the second MLD, a TID-to-Link Mapping Announcement frame; and
receiving, by the first MLD from the second MLD, an indication of an announcement result.

### Claim 13 (depends on 12)

The method of claim 12, wherein the second MLD is a non-Access Point (non-AP) MLD that supports restricted Target Wake Time (TWT) and the indication of the announcement result accepts the TID-to-Link Mapping at non-AP stations (STAs) of the non-AP MLD that support the announced TID-to-Link Mapping.

### Claim 14 (depends on 12)

The method of claim 12, wherein the second MLD is a low latency non-AP MLD and the indication of the announcement result accepts the TID-to-Link Mapping where a first set of links is dedicated to a first set of traffic types.

### Claim 15 (depends on 1)

The method of claim 1, wherein mapping the TID to at least one of the two links includes:
announcing, by the first MLD, TID-to-Link Mapping with the second MLD via a TID-to-Link Mapping Announcement frame, wherein the second MLD does not indicate acceptance of the TID-to-Link Mapping from the first MLD;
negotiating, by the first MLD, the TID-to-Link Mapping with the second MLD that does not indicate acceptance of the TID-to-Link Mapping, wherein negotiating the TID-to-Link Mapping with the second MLD includes:
transmitting, by the first MLD to the second MLD, a TID-to-Link Mapping Request frame that includes a request Token and requested TID-to-Link Mapping information; and
receiving, by the first MLD from the second MLD, a TID-to-Link Mapping Response frame that includes a response Token and a negotiation result.

### Claim 16 (depends on 15)

The method of claim 15, wherein the TID-to-Link Mapping Announcement frame is a Beacon frame.

### Claim 17 (depends on 1)

The method of claim 1, wherein the method involves performing link disablement by mapping the TID to at least one of the two links associated with the first MLD and the second MLD.

### Claim 18 (depends on 16)

The method of claim 16, wherein link disablement via the TID-to-Link Mapping is performed by the first MLD by at least one of a TID-to-Link Mapping negotiation and a TID-to-Link Mapping announcement on links with at least one mapped TID, and wherein at least one of the TID-to-Link Mapping negotiation and the TID-to-Link Mapping announcement is accepted by the second MLD.

### Claim 19 (depends on 1)

The method of claim 1, wherein the second MLD is a STA MLD and after a DL TID is mapped to a new link where TIDs have not been mapped, a STA of the STA MLD in the new link is in power save mode and in doze state after at least one of a map negotiation and a map indication.

### Claim 20

A first multi-link device (MLD), the first MLD comprising:
a processor configured to:
connect to a second MLD via at least two links;
map a Traffic Identifier (TID) to at least one of the two links associated with the first MLD and the second MLD;
transmit, to the second MLD, frames that correspond to the TID on at least one of the two links according to the mapping by the first MLD; and
receive subsequent frames on at least one of the two links according to the mapping by the first MLD from the second MLD.
