CN116600400A - Triggered multilink access coordination - Google Patents

Abstract

Embodiments for triggered Multilink (ML) access coordination are disclosed. A Station (STA) ML device (MLD) may establish a Preferred Trigger Link (PTL) with an Access Point (AP) MLD, where the PTL is a preferred link for receiving trigger frames. The STA MLD may transmit an Uplink (UL) frame via the PTL in response to the trigger frame. The STA MLD may then determine that the PTL is busy and transmit an Enhanced Distributed Channel Access (EDCA) UL frame on a non-PTL link. In the power save mode, the STA MLD may exchange UL and Downlink (DL) frames using the PTL. Multiple PTLs supporting simultaneous trigger frames may be established and a different Traffic ID (TID) range may be used for each of the PTLs. The STA MLD may utilize the AP MLD link pair information to receive DL retransmissions corresponding to one TID via both links of the AP MLD link pair.

Description

Triggered multilink access coordination

Cross Reference to Related Applications

The present application claims the benefit of U.S. provisional patent application No. 63/309,421, filed on 11, 2, 2022, which is incorporated herein by reference in its entirety.

Background

Technical Field

Embodiments relate generally to wireless devices that coordinate triggered multilink access in a wireless communication system.

RELATED ART

Wireless Local Area Network (WLAN) communications are described in IEEE p802.11revme_d0.0, draft Standard for Information technology-Telecommunications and information exchange between systems Local and metropolitan area networks-Specific requirements, part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications "IEEE p802.11revme".

Disclosure of Invention

Some embodiments include apparatus, methods, and computer program products for triggered Multilink (ML) access coordination. In some examples, a Station (STA) multi-link device (MLD) may inform an Access Point (AP) MLD of a Preferred Trigger Link (PTL) of a plurality of links of the station MLD, on which the STA MLD preferably receives a trigger frame. For example, the STA MLD may transmit an indication of the PTL corresponding to a first transceiver of the two or more transceivers of the station MLD. The STA MLD may receive the first trigger frame via the PTL, and transmit, via the PTL, first Uplink (UL) data stored in a buffer corresponding to the PTL in response to the first trigger frame. The transmission of the indication of the PTL may be made via the A control field or via a management frame. The PTL may correspond to a link having less co-existence usage than the remaining links associated with respective ones of the two or more transceivers.

In some embodiments, the STA MLD may determine that the PTL is busy (e.g., being used by another device), and the STA MLD may transmit the second UL data via a second link of a second transceiver of the two or more transceivers. When the STA MLD is in a power save mode (e.g., all STAs of the STA MLD are in the power save mode), the STA MLD may receive a Downlink (DL) frame via the PTL.

In some embodiments, the STA MLD may receive a second trigger frame on the second link, wherein the second trigger frame corresponds to the long resource duration. In response to the second trigger frame, the STA MLD may move the second UL data, which has been stored in the buffer corresponding to the PTL, to the second link and transmit the second UL data via the second link. In some examples, the STA MLD may transmit first UL data via the PTL using a first Traffic ID (TID) and transmit second UL data via a second link using a second TID. In some examples, the PTL corresponds to a first TID range, and the STA MLD may receive a second trigger frame via a second PTL corresponding to a second transceiver of the two or more transceivers concurrently with the first trigger frame. The second PTL may correspond to a second TID range, and the STA MLD may transmit second UL data via the second PTL using TIDs in the second TID range.

In some embodiments, the STA MLD may receive a communication signal including an AP MLD link pair corresponding to the PTL and another link of the two or more transceivers. The STA MLD may receive DL retransmissions corresponding to one TID via both links of the AP MLD link pair.

In some embodiments, the STA MLD may receive the second trigger frame via the PTL while transmitting the second UL data on another link via a second transceiver of the two or more transceivers. The STA MLD may transmit an error message in response to the second trigger frame and transmit third UL data via the PTL for a remaining transmission time of a reserved Resource Unit (RU) corresponding to the second trigger frame. In some examples, the STA MLD may receive the second trigger frame via the PTL while transmitting second UL data on another link via a second transceiver of the two or more transceivers, and transmit a Buffer Status Report (BSR) and quality of service (QoS) null frame for a duration of the reserved RU corresponding to the second trigger frame. In some examples, the STA MLD may receive the second trigger frame via the PTL while transmitting the second UL data on another link via a second transceiver of the two or more transceivers, calculate a statistic including link-specific and trigger frame-specific statistics, and transmit the statistic.

In some embodiments, the AP MLD may receive an indication of the PTL corresponding to a first transceiver of the two or more transceivers from the STA MLD. The AP MLD may prepare the buffered DL frames for transmission via the PTL. The AP MLD may transmit a first trigger frame via the PTL and receive first UL data via the PTL in response to the first trigger frame. In some examples, where the PTL corresponds to the first TID range, the AP MLD may transmit a second trigger frame via a second PTL corresponding to a second transceiver of the two or more transceivers concurrently with the first trigger frame. In some examples, the second PTL corresponds to a second TID range, and the AP MLD may receive second UL data via the second PTL using TID in the second TID range.

In some embodiments, the AP MLD may transmit a communication signal comprising an AP MLD link pair corresponding to the PTL and another link associated with a respective transceiver of the two or more transceivers, wherein a transceiver (e.g., an AP) corresponding to the AP MLD link pair resides on a common chip. The AP MLD may transmit DL retransmissions corresponding to one TID via both links of the AP MLD link pair.

In some embodiments, the AP MLD may transmit a second trigger frame via the PTL, receive an error message in response to the second trigger frame, and receive third UL data via the PTL for a remaining transmission time of the reserved RU corresponding to the second trigger frame. In some examples, the AP MLD may transmit the second trigger frame via the PTL while receiving UL data via another link of the AP MLD. In some embodiments, the AP MLD may transmit a second trigger frame via the PTL and receive a Buffer Status Report (BSR) and quality of service (QoS) null frame for a duration of a reserved RU corresponding to the second trigger frame and/or receive link-specific and trigger frame-specific statistics.

Further embodiments, features, and advantages of the present disclosure, as well as the structure and operation of the various embodiments of the present disclosure, are described in detail below with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the pertinent art to make and use the disclosure.

Fig. 1 illustrates an exemplary system for triggered Multilink (ML) access coordination according to some embodiments of the present disclosure.

Fig. 2 illustrates a block diagram of an exemplary wireless system supporting triggered ML access coordination in accordance with some embodiments of the present disclosure.

Fig. 3 illustrates a Preferred Trigger Link (PTL) example for triggered ML access coordination according to some embodiments of the present disclosure.

Fig. 4A illustrates an example of ML access coordination using PTL for triggering in accordance with some embodiments of the present disclosure.

Fig. 4B illustrates an example of PTL usage in a power saving mode according to some embodiments of the present disclosure.

Fig. 4C illustrates an example of a Traffic ID (TID) -specific PTL configuration according to some embodiments of the present disclosure.

Fig. 5A illustrates an example of signaling for establishing a PTL according to some embodiments of the present disclosure.

Fig. 5B illustrates exemplary fields for establishing a PTL according to some embodiments of the present disclosure.

Fig. 6A illustrates a first example of ML triggering capability according to some embodiments of the present disclosure.

Fig. 6B illustrates a second example of ML triggering capability according to some embodiments of the present disclosure.

Fig. 7 illustrates an example of Access Point (AP) ML device (MLD) link pair capability supporting triggered ML access coordination according to some embodiments of the present disclosure.

Fig. 8A illustrates an example of an error during a triggering operation according to some embodiments of the present disclosure.

Fig. 8B illustrates an example of transmitting an error message during a triggering operation according to some embodiments of the present disclosure.

Fig. 8C illustrates an example of transmitting a Buffer Status Report (BSR) during a trigger operation according to some embodiments of the present disclosure.

Fig. 8D illustrates an example of multiple trigger frames that are unresponsive in a transmission opportunity (TXOP) in accordance with some embodiments of the present disclosure.

Fig. 8E illustrates an example of transmitting a statistical report corresponding to a trigger operation according to some embodiments of the present disclosure.

Fig. 9A illustrates an example of an Enhanced Distributed Channel Access (EDCA) Uplink (UL) transmission, in accordance with some embodiments of the disclosure.

Fig. 9B illustrates an example of triggered ML UL transmissions according to some embodiments of the present disclosure.

Fig. 10 illustrates an exemplary method for supporting triggered ML access coordination Site (STA) MLD according to some embodiments of the present disclosure.

Fig. 11 illustrates an exemplary method for supporting triggered ML access coordination AP MLD according to some embodiments of the present disclosure.

FIG. 12 is an exemplary computer system for implementing some embodiments or portions thereof.

The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numbers indicate identical or functionally similar elements. Further, generally, the leftmost digit(s) of a reference number identifies the figure in which the reference number first appears.

Detailed Description

Some embodiments include apparatus, methods, and computer program products for triggered Multilink (ML) access coordination. A station (e.g., a User Equipment (UE)) may contend for access to a wireless network and use Enhanced Distributed Channel Access (EDCA) for Uplink (UL) transmission. A Station (STA) ML device (MLD) including a plurality of stations and corresponding links may support multi-user (MU) EDCA. However, STA MLD may have difficulty responding simultaneously to trigger frames with the same Traffic ID (TID) on different links. In other words, STA MLD may not support simultaneous transmission of data with the same TID (e.g., the same quality of service (QoS) class) on two or more links. Simultaneous transmissions in two or more links would require separation of data sets within the same data buffer. However, it may not be possible to share a data set to more than one link at a time.

Some embodiments enable STA MLD to manage and coordinate triggered ML access. For example, the STA MLD may determine a link preferred for receiving the trigger frame, define a number of links in which the Access Point (AP) MLD may trigger the STA MLD at the same time, and/or provide a signal to the AP MLD when a response to the trigger frame results in an error and/or a response is not transmitted.

Fig. 1 illustrates an exemplary system 100 for triggered ML access coordination according to some embodiments of the present disclosure. The system 100 includes an AP MLD 110 that provides access to a network 150 to STA MLD120 and STA 140. The AP MLD 110 may include a plurality of APs, where each AP corresponds to a particular different link. For example, AP 112 may communicate with STA 122 via 2.4GHz identified by link 161; AP 114 may communicate with STA 124 via 5GHz identified by link 165; and AP 116 may communicate with STA 126 via 6GHz identified by link 167. AP 112, AP 114, and AP 116 may each have a radio transceiver that operates independently of the other radio transceivers. For example, the AP MLD 110 may communicate with the STA MLD120 over multiple links (e.g., over one or more frequency bands) using one or more radios (e.g., 3 transceivers). For example, AP MLD 110 may utilize transceivers of AP 112, AP 114, and/or AP 116 to communicate with STA MLD120 via link 161, link 165, and/or link 167.

STA MLD 120 and STA140, which are adjacent to AP MLD110, may be associated with AP MLD110. For example, STA MLD 120 may scan across all three links and identify AP MLD110. After association with the AP MLD110, the STA MLD 120 may communicate via any of these links (link 161, link 165, and/or link 167) that are available in, for example, three different frequency bands (e.g., 2.4GHz, 5GHz, and 6 GHz). If one link is busy, the STA MLD 120 or the AP MLD110 selects the other link that is available first.

STA140 may be a non-MLD STA (e.g., a STA with a single transceiver). STA140 may communicate with AP MLD110 via one of AP 112, AP 114, or AP 116. STA MLD 120 and/or STA140 may be electronic devices that may include, but are not limited to, cellular telephones, smart phones, tablet computers, personal Digital Assistants (PDAs), or laptop computers. Network 150 may include, but is not limited to, any one of a Local Area Network (LAN), metropolitan Area Network (MAN), wireless Local Area Network (WLAN), and/or the internet, or any combination thereof. In some embodiments, the AP 110 may not be an MLD, where the AP 110 may include a single transceiver.

Fig. 2 illustrates a block diagram of an exemplary wireless system 200 supporting triggered ML access coordination in accordance with some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 2 may be described with reference to elements of FIG. 1. For example, system 200 may be any of the following electronic devices of system 100: AP MLD110, AP 112, AP 114, AP 116, STA MLD 120, STA 122, STA 124, STA 126, or STA 140. System 200 includes one or more processors 265, a transceiver 270, a communication interface 275, a communication infrastructure 280, a memory 285, and an antenna 290. Memory 285 may include Random Access Memory (RAM) and/or cache, and may include control logic (e.g., computer instructions) and/or data. The one or more processors 265 may execute instructions stored in the memory 285 to perform operations that enable the wireless system 200 to transmit and receive wireless communications, including the functions for triggered ML access coordination described herein. In some embodiments, one or more processors 265 may be "hard-coded" to perform these functions herein. According to some embodiments, transceiver 270 transmits and receives wireless communication signals including wireless communication supporting triggered ML access coordination and may be coupled to one or more antennas 290 (e.g., 290a, 290 b). In some embodiments, a transceiver 270a (not shown) may be coupled to the antenna 290a, and a different transceiver 270b (not shown) may be coupled to the antenna 290b. Communication interface 275 allows system 200 to communicate with other devices, which may be wired and/or wireless. Communication infrastructure 280 may be a bus. Antenna 290 may include one or more antennas, which may be of the same or different types.

Fig. 9A illustrates an example 900 of EDCA Uplink (UL) transmission in accordance with some embodiments of the disclosure. For purposes of illustration and not limitation, the example 900 may be described with reference to elements of other figures in the disclosure. For example, AP 912 and STA 922 may correspond to AP112 and STA 122 of fig. 1. STA 922 may transmit UL data using a Traffic ID (TID) 1 via EDCA transmission opportunity (TXOP) 930. STA 922 controls aspects of EDCA TXOP 930 including, but not limited to, modulation Coding Scheme (MCS), number of Special Streams (NSS), transmission (TX) power, bandwidth, and TID value. The AP 912 receives the EDCA TXOP 930 and, in response, transmits a Block Acknowledgement (BA) 932. Duration 940 shows a flexible TXOP start time and a duration including BA 932. Briefly, a transmitter STA 922 controls aspects of UL EDCA transmission in an ML environment. This is in contrast to the triggered ML UL transmission discussed in fig. 9B, where the AP transmitting the ML trigger frame controls aspects of the triggered UL response (e.g., characteristic 985).

Fig. 9B illustrates an example 950 of triggered ML UL transmissions according to some embodiments of the disclosure. For purposes of illustration and not limitation, the example 950 may be described with reference to elements of other figures in this disclosure. For example, AP 912, STA 922, and STA 924 may correspond to AP112, STA 122, and STA 124 of fig. 1. Example 950 illustrates a trigger frame 960 transmitted from an AP 912. In response, STAs 922 and 924 are triggered to transmit corresponding UL data 965 and 975, UL data 965 and 975 being limited to a duration 980 having a precise Resource Unit (RU) duration. In addition, AP 912 (and/or a corresponding AP MLD (e.g., AP MLD 110), a portion of which is AP 912) sets RU, MCS, NSS and TX power characteristics 985. The corresponding STA MLD (e.g., STA MLD 120) may have limited ML UL data transmission capability and may not be able to respond within a relatively short time after receiving the trigger frame 960. AP 912 transmits BA 967 in response to received UL data 965 and 975. In addition, the STA MLD 120 may not be able to transmit UL data 965 and UL data 975 simultaneously using the same TID. Embodiments herein enable coordinated responses to trigger frames in an ML environment.

Fig. 3 illustrates a Preferred Trigger Link (PTL) example 300 for triggered ML access coordination according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 3 may be described with reference to the elements of fig. 1 and 2. For example, AP MLD 310, AP 312, AP 314, AP 316, STA MLD 320, STA 322, STA 324, and STA 326 of fig. 3 may correspond to AP MLD 110, AP 112, AP 114, AP 116, STA MLD 120, STA 122, STA124, and STA 126 of fig. 1, and/or system 200 of fig. 2. In example 300, AP 312, AP 314, and AP 316 may signal EDCA parameters and MU-EDCA parameters to corresponding STA 322, STA 324, and STA 326.

In some embodiments, the STA MLD 320 informs the AP MLD 310 of the PTL on which the STA MLD 320 preferably receives the trigger frame. The PTL may be selected as a link corresponding to a buffer in which UL data resides and/or the PTL may be selected as a link with less or minimal coexistence activity (e.g., peer-to-peer communication). For example, if STA MLD 320 often utilizes link 361 at 2.4GHz and/or link 365 at 5GHz for peer-to-peer communication, STA MLD 320 may select a different link (such as link 367 at 6 GHz) as the PTL.

In example 300, assume that STA MLD 320 has UL data buffered at STA 322 for transmission on link 361, so STA MLD 320 selects link 361 as the PTL. The STA MLD 320 may transmit a PTL request to the AP MLD 310, and the AP MLD 310 acknowledges the PTL request. Subsequently, the STA MLD 320 expects to receive a trigger frame via the PTL (i.e., link 361). Upon receiving trigger frame 332 via link 361, STA 322 immediately transmits a response 334 that includes UL trigger-based (TB) data and TID.

Fig. 4A illustrates an example 400 of ML access coordination using PTL for triggering in accordance with some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 4A may be described with reference to elements of other figures. For example, STA 422, STA 424, AP 412, AP 414, link 461, and link 465 may correspond to STA 322, STA 324, AP 312, AP 314, link 361, and link 365 of fig. 3.

Example 400 shows AP 412 transmitting trigger frame 405 on PTL link 461.

STA 422 receives trigger frame 405 and, in response, transmits UL data 410.

The AP 412 receives UL data 410 and transmits a Block Acknowledgement (BA) 415 according to the received UL data 410.

Setting up a PTL (e.g., link 461) does not prevent the AP MLD from transmitting trigger frames to the STA MLD on a different link.

The AP MLD may transmit the trigger frame on another link than the PTL even if the other link is not ideal for the STA MLD. In some embodiments, the STA MLD does not respond to trigger frames received outside of the PTL.

With continued reference to example 400, ap 414 may transmit trigger frame 420 to STA 424 via link 465 other than the PTL.

STA MLD (e.g., STA MLD 320) first moves any UL data from a buffer corresponding to PTL (link 661) during delay time 425 and then transmits the moved UL data in UL data 430 for the remaining time of RU corresponding to trigger frame 420.

AP 414 receives UL data 430 and, in response, transmits BA 435.

A trigger frame (e.g., trigger frame 420) should be allocated a sufficiently long Resource Unit (RU) (e.g., a long resource duration) to move UL data from PTL (e.g., link 461) to link 465 during delay time 425. Note that receiving the trigger frame via the PTL saves delay time 425 during which the allocated transmission RU is not used, and also saves resources (e.g., power) that must be spent moving UL data from the buffer corresponding to the PTL to link 465.

Returning to example 300, ap MLD 310 may announce MU EDCA parameters via the PTL. When STA322 responds to trigger frame 332 in the PTL with UL TB data 334 on access category 1 (AC 1) (which may include traffic from TIDs 0 and 3, for example), then the STA should use MU EDCA parameters (e.g., AIFS, CWmin, and CWmax) to obtain EDCA TXOPs for AC1 (e.g., TIDs 0 and 3) in the PTL. The use of MU EDCA parameters may result in poor EDCA performance on the PTL. As shown in example 300, STA EDCA parameter STA322 utilizes MU EDCA and STAs 324 and 326 use EDCA.

In some embodiments, the STA MLD320 may determine whether the PTL is busy when the PTL is busy (e.g., has an ongoing transmission) and/or when the AP MLD 310 transmits a trigger frame and MU EDCA parameters on the PTL. When the PTL is busy, the STA MLD320 may transmit UL data with EDCA on another link other than the PTL.

In example 300, when STA 322 detects that some other device (e.g., STA140 of fig. 1, not shown in fig. 3) is transmitting in PTL link 361, STA MLD320 determines that PTL link 361 is busy, and STA MLD320 may transmit UL data 340 via link 365 of STA 324.

Fig. 4B illustrates an example 440 of PTL usage in a power saving mode according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 4B may be described with reference to elements of other figures, such as AP MLD110 and STA MLD 120 of fig. 1. In some embodiments, when the STA MLD 120 enters a power save mode (e.g., all STAs affiliated to the STA MLD enter a power save mode), the STA MLD 120 may exchange UL and Downlink (DL) data by default using the PTL. In example 440, PTL 471 has been established between AP 114 and STA 124. AP MLD110 may prepare the buffered DL frames for delivery via PTL 471. When STA MLD 120 is in a power save mode and obtains a UL frame for transmission, STA 124 may wake up to transmit the UL frame via PTL 471. The UL frame may include signaling, e.g., the power management bit in the MAC header of the transmitted frame is set to 1, and this signaling indicates to the AP MLD110 that the AP MLD110 may send buffered frames to the STA. Subsequently, STA 124 may obtain DL frames buffered by AP MLD110 at AP 114. This buffered DL frame on the PTL may reduce the duration of the STA 124 operating in the awake state.

In some embodiments, when the PTL is not configured, the AP MLD 110 may include a link recommendation in the beacon frame, wherein the link recommendation indicates a link, and the STA MLD 120 retrieves the buffered DL frame from the indicated link. The STA MLD 120 may receive little or only Delivery Traffic Indication Message (DTIM) beacons. Thus, waiting for the next beacon may increase UL transmission delay. The same link may also be used for transmitting trigger frames.

Fig. 4C illustrates an example 480 of a TID-specific PTL configuration according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 4C may be described with reference to elements of other figures, such as AP MLD 110 and STA MLD 120 of fig. 1. In some embodiments, the STA MLD 120 may configure a TID-specific PTL. For example, PTL 481 may be configured to utilize TID 0-3 (e.g., for background and best effort traffic), and PTL 487 is configured to use TID 4-7 (e.g., for low latency traffic). Thus, TID-specific PTL 487 is used to transmit only high TID traffic. In some embodiments, STA MLD 120 may have up to 15 simultaneous links to respond to trigger frames. In some embodiments, if the STA MLD 120 can transmit a multi-TID transmission, in a long RU, the STA MLD 120 may first transmit TIDs configured for PTL and continue data transmission on other TIDs. Depending on STA MLD transmission decisions, qoS requirements for available UL traffic, and frames appropriate for the allocated RU, the transmitted TID may be on a configured TID or other TID.

Fig. 5A illustrates an example 500 of signaling for establishing a PTL according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 5A may be described with reference to elements of other figures. For example, STA 522 and AP 512 may correspond to STA MLD 120 and AP MLD 110 of fig. 1. STA 522 may select the PTL based on the link with UL data ready for immediate transmission and/or the link with fewer or minimal coexistence issues. STA 522 may transmit PTL notification message 545 to AP 512. AP 512 may receive PTL notification message 545 and, in response, transmit Acknowledgement (ACK) message 555.

Table 1 shows signaling alternatives for setting up PTLs. The PTL notification 545 may be transmitted via an A control field or management frame signal signaling the MAC header of the PTL. In some embodiments, the link from which the last EDCA UL frame was transmitted becomes the PTL.

Table 1: preferred Trigger Link (PTL) signaling alternatives

Fig. 5B illustrates an exemplary field 560 for establishing a PTL according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 5A may be described with reference to elements of other figures (such as FIG. 5B). STA 522 may signal the PTL using an AP Assisted Recovery (AAR) a control field. The AAR a control field may include a supplemental AP link ID bitmap 565, where a value of "1" in supplemental AP link ID bitmap 565 indicates that STA 522 prefers the triggered link (e.g., PTL). In some embodiments, at least one bit may be set to "1". In some embodiments, the TID or reserved field 570 may correspond to the TID value (0-15) of the corresponding PTL of the bitmap. Thus, the STA MLD 320 may configure different PTLs for the corresponding TIDs. In some examples, TID value 14 may signal that the PTL corresponding to the bitmap is the default PTL for all TIDs. In some examples, TID or reserved field 570 includes a reserved value.

The STA MLD 320 may change the configured PTL by transmitting a second management frame or aara control field to the AP. If TID-specific PTL configurations are used, each TID may be changed with separate new signaling, or the signaling may change all TID configurations. The STA MLD 320 may stop using the PTL by transmitting an AAR a control field or a second management frame signaling no PTL to the AP MLD 310.

Fig. 6A illustrates an example 600 of ML triggering capability according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 6A may be described with reference to elements of other figures in the disclosure. For example, STA 622, STA 624, AP 612, AP 614, link 661, and link 665 may correspond to STA 322, STA 324, AP 312, AP 314, link 361, and link 365 corresponding to STA MLD 320 and AP MLD 310 of fig. 3. In some embodiments, the STA MLD (e.g., STA MLD 320) may signal to the AP MLD (e.g., AP MLD 310) the capability to respond to simultaneous trigger frames in different links. The signalling may be transmitted in a (re) association request frame. In some examples, the STA MLD 320 may signal that the STA MLD 320 cannot respond to the trigger frame in all of the multiple links simultaneously. In some examples, STA MLD 320 cannot transmit UL data with the same TID in multiple links simultaneously.

In some embodiments, STA MLD320 may signal ML Simultaneous Transmission and Reception (STR) data triggering capability via ML triggering data triggering capability field values as shown in table 2 below. The value field indicates the number of APs of the AP MLD 310 from which the STA MLD320 may receive the basic trigger frame.

Table 2: ML STA MLD level data triggering capability field value

In example 600, the corresponding STA MLD (not shown) has signaled the ML data trigger capability field value=1 to the AP MLD (not shown), and the STA MLD includes only buffered UL data with one TID: tid=0 corresponding to link 661.

AP 612 transmits trigger frame 605 over link 661.

STA 622 receives the trigger frame 605 and, in response, transmits UL trigger-based (TB) data 610, such as a physical layer protocol data unit (PPDU) with a data payload from tid=0.

AP 614 simultaneously transmits trigger frame 620 on link 665 when STA 622 is transmitting UL TB data 610.

Since STA 624 of link 665 does not have any UL data to transmit, STA 624 does not respond to trigger frame 620.

AP 612 receives UL TB data 610 and transmits BA 615 accordingly.

Fig. 6B illustrates an example 650 of ML triggering capability according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 6B may be described with reference to elements of other figures in the disclosure (such as fig. 6A). In example 650, the corresponding STA MLD (e.g., STA MLD 320) has signaled the ML STA MLD data trigger capability field value = 1 to the AP MLD (e.g., AP MLD 310), and the STA MLD320 includes buffered UL data with two TIDs: tid=0 for link 661 and tid=3 for link 665.

AP 612 transmits trigger frame 655 over link 661.

STA 622 receives trigger frame 655 and, in response, transmits UL trigger-based (TB) data 660, such as PPDU with tid=0.

AP 614 simultaneously transmits trigger frame 670 on link 665 when STA 622 is transmitting UL TB data 660.

Since STA 624 of link 665 has UL data to transmit, STA 624 responds to trigger frame 670 by transmitting UL TB data 675 (such as PPDU with tid=3).

AP 612 receives UL TB data 660 and transmits BA 665 accordingly.

AP 614 receives UL TB data 675 and transmits BA 680 accordingly.

In some embodiments, an AP MLD (e.g., AP MLD 310) may signal the ML triggering capability of AP MLD 310. The signaled capability may assist the STA MLD (e.g., STA MLD 320) in selecting the corresponding AP MLD 310 and selecting the corresponding mode of operation for the AP MLD 310. For example, the STA MLD320 may select a PTL or a number of PTLs based on the AP MLD 310 capabilities. The STA MLD320 may choose to activate only a single link to the AP MLD 310 because the AP MLD 310 does not support triggers in other links. The STA MLD320 may select a link in which the STA MLD320 is available for triggering, and may select a link in which the STA MLD320 is used only for EDCA transmission. The STA MLD320 may choose to transmit data with certain TIDs only on the selected link.

AP MLD 310 capabilities may be transmitted in beacons, probe responses, multi-link probe responses, and/or (re) association response messages. This capability may be at the MLD level or the AP MLD link pair level (as discussed below). For example, the MLD level capabilities of the AP MLD 310 are similar to those of the STA MLD 320. For example, the STA MLD 320 receives a single response of the AP applied to the AP MLD 310. In other words, AP 312, AP 314, and AP 316 share the same capability value. In addition, the STA MLD 320 will be informed whether the AP MLD 310 supports the simultaneous trigger frame. Table 3 below shows exemplary values of the ML AP MLD level data triggering capability field.

Table 3: ML AP MLD level data triggering capability field value

Fig. 7 illustrates an example 700 of AP MLD link pair capability supporting triggered ML access coordination in accordance with some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 7 may be described with reference to elements of other figures in the disclosure. For example, AP MLD 710, AP 712, AP 714, and AP716 may correspond to AP MLD 310, AP 312, AP 314, and AP 316 of fig. 3. In example 700, AP 712 may be implemented on chip 730, while both AP 714 and AP716 may be implemented on a single chip (chip 740). The AP MLD link pair (e.g., AP 714 and AP 716) may have better capabilities than the other APs (e.g., AP 712) because the other APs communicate across links as shown in table 4 below.

For example, capability sets 1 and 2 may be similar in that cross-link communication is between two chips (e.g., chip 730 and chip 740). However, capability set 3 may have excellent capabilities because information is shared within a single chip (e.g., chip 740), which may reduce communication latency.

Table 4: AP MLD link pair and capabilities

Link pair	Examples of signaled capabilities
		AP 712-AP 714	Capability set 1
AP 712-AP 716	Capability set 2
		AP 714-AP 716	Capability set 3

In some embodiments, the AP MLD link pair communication from the AP MLD 710 to the corresponding STA MLD (not shown) indicates whether the paired APs (e.g., AP 714 and AP 716) are capable of sharing information and cross-link information sharing capability. The AP MLD link pair communication may inform the STA MLD of the extent of AP 714 and AP 716 information exchange (e.g., exemplary real-time information exchange). The associated station may benefit from the AP MLD link pair information by selecting a link corresponding to the AP MLD link pair for operation and expecting a better trigger (e.g., coordination between AP 714 and AP 716) for fast communication. An example of the scheduling parameters for the AP MLD link is shown in table 5 below.

Table 5: AP MLD link pair specific scheduling parameters

Fig. 8A illustrates an example 800 of an error during a triggering operation according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 8A may be described with reference to elements of other figures in the disclosure. For example, AP 814, STA 824, and link 865 may correspond to AP314, STA 324, and link 365 of fig. 3. In some examples, the STA MLD may receive the trigger frame, but may not be able to respond to the trigger frame. For example, AP 814 may transmit trigger frame 805 with tid=0 and not receive response 810 from STA 824. AP 814 and the corresponding AP MLD (e.g., AP MLD 310) may not understand why STA 824 and the corresponding STA MLD (e.g., STA MLD 320) did not respond, and thus AP MLD 310 does not have information for determining whether to make any changes/adjustments. In some embodiments, STA 824 may provide various responses as described further below.

Fig. 8B illustrates an example 830 of transmitting an error message during a triggering operation according to some embodiments of the disclosure. For purposes of illustration and not limitation, FIG. 8B may be described with reference to elements of other figures in the disclosure. For example, AP 812, AP 814, STA 822, STA 824, link 861, and link 865 may correspond to AP 312, AP 314, STA 322, STA 324, link 361, and link 365 of fig. 3. In some embodiments, if a STA MLD (e.g., STA MLD 320) is transmitting data on another link and receives a trigger frame, the STA MLD 320 may respond to the trigger frame with an error message during a transmission time of a reserved RU corresponding to the trigger frame. Thus, no additional overhead is incurred. Further, if the STA MLD 320 is capable, the STA MLD 320 may transmit the UL frame corresponding to the trigger frame for the remaining transmission time of the reserved RU corresponding to the trigger frame.

In example 830, link 865 is a PTL and STA MLD 320 includes buffered UL data with tid=0.

STA 822 may transmit EDCA TXOP 835 with UL data and tid=0 on link 861.

Meanwhile, on link 865, AP 814 may transmit trigger frame 840 with tid=0.

STA 824 may transmit error message 842 during the reserved RU corresponding to trigger frame 840, where the error message may indicate that no TID is available. After EDCA TXOP 835 is completed and the time remains for the reserved RU, sta 824 may transmit UL data 844 with tid=0 in response to trigger frame 840.

AP 812 may receive EDCA TXOP 835 and transmit BA 838 accordingly.

AP 814 may receive UL data 844 and transmit BA 846 accordingly.

Based on error message 842, ap 814 does not reduce the transmission rate because the error message indicates that the problem is due to an unavailable TID. The AP MLD 310 may schedule subsequent trigger frames at the correct time for the available data.

The contents of error message 842 may include, but are not limited to, the following:

another type of transmission (e.g., peer-to-peer (P2P) or infrastructure TX (such as EDCA TXOP 835));

another transmitted link (e.g., link 861);

time during which triggered UL data transmission is possible again;

the amount of buffered traffic and the corresponding TID;

the delay bound time remaining for transmitting buffered traffic; and/or

New PTL for the next transmission.

Fig. 8C illustrates an example 850 of transmitting a Buffer Status Report (BSR) during a triggering operation according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 8C may be described with reference to elements of other figures in the disclosure (such as fig. 8B). In some embodiments, if the STA MLD320 is transmitting data on another link and cannot respond to the trigger frame, the STA MLD320 may respond with a Buffer Status Report (BSR) and signal the STA MLD320 that there is data available. Responding with a BSR may be simpler than attempting to transmit data (e.g., instead of UL data 844 of example 830) from STA MLD320 to AP MLD 310. When the AP MLD 310 receives the BSR, the AP MLD 310 knows at least the following: the trigger frame is received, the allocated RU is idle, the STA MLD320 cannot transmit data due to some other error, and/or the STA MLD320 still has UL data (e.g., buffered UL data) available and expects to receive the trigger frame from the AP MLD 310. Accordingly, the AP MLD 310 may use the BSR information to determine to transmit a new trigger frame to the STA MLD 320.

In example 850, link 865 is a PTL and STA MLD 320 includes buffered UL data with tid=0.

STA 822 may transmit EDCA TXOP 852 with UL data and tid=0 on link 861.

Meanwhile, on link 865, AP 814 may transmit trigger frame 860 with tid=0.

STA 824 may transmit quality of service (QoS) null and BSR 862 for the duration of the allocated RU corresponding to trigger frame 860 (e.g., during reserved RU).

AP 812 may receive EDCA TXOP 852 and transmit BA 854 accordingly.

The AP 814 may receive the QoS null and BSR 862 and transmit the BA 864 accordingly.

Based on the QoS null and BSR 862, the ap MLD 310 may schedule a new trigger frame.

Fig. 8D illustrates an example 870 of multiple trigger frames without a response in a TXOP in accordance with some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 8D may be described with reference to elements of other figures in the disclosure (such as fig. 8A). In some examples, the AP MLD 310 may transmit multiple trigger frames in the TXOP. If the first response to the first trigger is received correctly but the second response to the second trigger is not received, the AP MLD 310 may determine that the lack of the second response may be due to an error of the STA MLD 320. The first trigger and first response have set a Network Allocation Vector (NAV) around the AP MLD 310 and the responding STA MLD 320, so that Wireless Local Area Network (WLAN) interference is unlikely to be the cause of the error (e.g., resulting in a lack of the second response). Accordingly, the AP MLD 310 may ignore the failure of the second response and determine to retransmit the trigger frame.

In example 870, link 865 is a PTL.

AP 814 may transmit a Buffer Status Report Poll (BSRP) trigger 872.

STA 824 may receive BSRP trigger 872 and, in response, transmit BSR 874.

AP 814 may transmit a basic trigger frame 876 after receiving BSR 874.

As shown by no response 878, AP 814 does not receive a response to basic trigger frame 876.

Subsequently, the AP MLD 310 may ignore the failure of the second response (e.g., no response 878) and determine to retransmit the basic trigger frame.

Fig. 8E illustrates an example 880 of transmitting a statistical report corresponding to a trigger operation according to some embodiments of the present disclosure. For purposes of illustration and not limitation, fig. 8E may be described with reference to elements of other figures in the disclosure (such as fig. 8B). In some examples, the STA MLD 310 may not be able to transmit a response to the trigger frame. In some cases, the STA MLD 310 may not have any reporting time to explain the reason for the failure of the response to the trigger frame. Therefore, the AP MLD 310 does not know whether the STA MLD 320 missed the trigger frame or whether there is another reason why the STA MLD 320 does not respond to the trigger frame. In some embodiments, the STA MLD 320 calculates the statistics and transmits the statistics to the AP MLD 310. In some examples, the STA MLD 320 transmits the statistics to the AP MLD 310 as a response to a BSRP trigger frame, or as a response to a new trigger frame. In some examples, if the STA MLD 320 detects an error in the trigger frame response and wants to notify the AP MLD 310, the STA MLD 320 may transmit an unsolicited statistics frame. In some examples, the statistics may be listed in an a control field in a MAC header transmitted to the AP MLD 310.

In example 880, link 865 is a PTL.

STA 822 may transmit EDCA TXOP 882 with UL data and tid=0 on link 861.

Meanwhile, on link 865, AP 814 may transmit trigger frame 890 with tid=0.

STA 824 may not respond to trigger frame 890 as indicated by no response 892.

AP 812 may receive EDCA TXOP 882 and transmit BA 884 accordingly.

The STA MLD 320 may then calculate link-specific and/or trigger frame-specific statistics and transmit the statistics: i) As a response to a BSRP trigger frame or as a response to a new trigger frame; ii) in an unsolicited statistics frame; and/or iii) listing the statistics in an a control field in the MAC header. In some embodiments, STA MLD 320 calculates the individual statistics based on the type of trigger frame (e.g., basic, multi-user (MU) Ready To Send (RTS), BSRP, and MU Block Acknowledgement Request (BAR)). The trigger response statistics may be 2 octets in size. Some examples of trigger response statistics include, but are not limited to, the following:

assigning to the STA the number of received trigger frames of RU

Number of trigger frames of response

Number of unresponsiveness due to lack of data

Number of unresponsiveness due to another transmission in progress in another link

Number of unresponsiveness due to ongoing P2P transmissions

Number of unresponsiveness due to allocated RUs being busy (e.g., clear Channel Assessment (CCA) busy)

Fig. 10 illustrates an exemplary method 1000 for supporting triggered ML access coordination STA MLD according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 10 may be described with reference to elements of other figures in the disclosure. For example, the method 1000 may be performed by the STA MLD 320 of fig. 3 including STA 322, STA 324, and STA 326, and/or the system 200 of fig. 2. The STA MLD 320 may communicate with the AP MLD 310 including the AP 312, the AP 314, and the AP 316 via the corresponding links of fig. 3.

At 1010, the STA MLD 320 may establish a PTL with the AP MLD 310 to mitigate Simultaneous Transmission and Reception (STR) responses to the ML trigger frame. For example, STA MLD 320 may transmit an indication of a PTL (link 361) corresponding to STA 322 and receive a first trigger frame (e.g., trigger frame 322) via the PTL (link 361). In response to the first trigger frame, the STA 320 may transmit first UL data (e.g., UL TB data 334) that has been stored in a buffer corresponding to the PTL via the PTL (link 361). In some embodiments, the transmission of the indication of the PTL may be made via an a control field or via a management frame. In some embodiments, the PTL corresponds to a link (e.g., a respective transceiver associated with a link) having fewer or minimal coexistence usage than the remaining links of the respective transceivers associated with the STA MLD 320.

At 1020, the STA MLD320 may implement EDCA UL transmission on the non-PTL link of the STA MLD 320. For example, STA MLD320 determines that the PTL is busy (e.g., AP MLD 110 may be using the PTL to communicate with a STA not shown in fig. 3) and transmits second UL data (e.g., UL EDCA data 340) via a second link (e.g., link 365) corresponding to the second transceiver (STA 324).

At 1030, STA MLD320 may transmit and receive frames via a PTL (e.g., PTL 471 of fig. 4B) while in a power save mode (e.g., long term power save mode). For example, STA MLD320 operates a power save mode over multiple links. Only PTL is activated to retrieve DL data and transmit UL data.

At 1040, the STA MLD320 may receive the trigger on another link (e.g., non-PTL) and move the UL frame from the buffer of the PTL to the other link. For example, STA MLD320 may receive a trigger frame (e.g., trigger frame 420 of fig. 4A) on a second link (e.g., link 465 of fig. 4A), where the trigger frame corresponds to a long resource duration. In response to the trigger frame, the STA MLD320 may move the second UL data, which has been stored in the buffer corresponding to the PTL (e.g., link 461), to the second buffer corresponding to the second link, and transmit the second UL data from the second buffer via the second link. In some examples, STA MLD320 may be configured to transmit first UL data via a PTL (e.g., PTL 481 of fig. 4C) using a first TID and transmit second UL data via a second link (e.g., PTL 487 of fig. 4C) using a second TID.

At 1050, the STA MLD 320 may enable reception of simultaneous trigger frames from the AP MLD via multiple links of the station MLD. For example, the STA MLD 320 may allocate a TID range to a PTL (e.g., PTL 481 of fig. 4C) and another range to another link of the STA MLD 320 (e.g., link PTL 487 of fig. 4C). The STA MLD 320 may receive a second trigger frame (e.g., trigger frame 670 of link 665) via a second PTL corresponding to a second transceiver (e.g., STA 624) concurrently with the first trigger frame, and wherein the second PTL corresponds to a second TID range. The STA MLD 320 may transmit the second UL data via the second PTL using TIDs in the second TID range.

At 1060, the STA MLD 320 may utilize the AP MLD link pair communication signals. The STA MLD 320 may receive a communication signal including an AP MLD link pair (e.g., AP MLD 710 with link pair AP 714 and AP 716) corresponding to the PTL and another link of the two or more transceivers. In some embodiments, the STA MLD 320 may receive DL retransmissions corresponding to one TID via both links of the AP MLD link pair.

At 1070, the STA MLD 320 may communicate to the AP MLD the reason for the STA MLD not responding to the trigger frame. In some examples, the STA MLD 320 may receive the second trigger frame via the PTL while transmitting the second UL data on the other link via a second transceiver of the two or more transceivers, and transmit an error message in response to the second trigger frame. The STA MLD 320 may transmit the third UL data via the PTL for the remaining transmission time of the reserved RU corresponding to the second trigger frame.

In some embodiments, the STA MLD 320 may receive the second trigger frame via the PTL while transmitting the second UL data on the other link via a second transceiver of the two or more transceivers, and transmit the BSR and the QoS null frame for a duration of the reserved RU corresponding to the second trigger frame. In some embodiments, the STA MLD 320 may receive the second trigger frame via the PTL while transmitting the second UL data on another link via a second transceiver of the two or more transceivers, calculate statistics including link-specific and trigger frame-specific, and transmit the statistics to the AP MLD 320.

Fig. 11 illustrates an exemplary method 1100 for supporting triggered ML access coordination AP MLD according to some embodiments of the present disclosure. For purposes of illustration and not limitation, FIG. 11 may be described with reference to elements of other figures in the disclosure. For example, the method 1100 may be performed by the AP MLD 310 of fig. 3 including the AP 312, the AP 314, and the AP 316, and/or the system 200 of fig. 2. The AP MLD 310 may communicate with the STA MLD 320 of fig. 3 including STA 322, STA 324, and STA 326 via the corresponding links of fig. 3.

At 1110, the AP MLD 310 may accommodate a request for PTL from the STA MLD 320 indicating a preference for receiving a trigger frame to mitigate a trigger response to the ML trigger frame. For example, the AP MLD 310 may receive an indication of a PTL corresponding to a first transceiver of the two or more transceivers from the STA MLD 320 and prepare the buffered DL frames for transmission via the PTL. The AP MLD 310 may transmit a first trigger frame via the PTL and receive first UL data via the PTL in response to the first trigger frame.

At 1120, the AP MLD 310 may communicate via the PTL (e.g., with devices other than the STA MLD 320) and concurrently receive EDCA UL transmissions on the non-PTL links of the STA MLD 320.

At 1130, when the STA MLD 320 is in a power save mode (e.g., a long-term power save mode), the AP MLD 310 may transmit and receive frames via the PTL.

At 1140, AP MLD 310 may transmit the trigger on another link (e.g., non-PTL) and receive the UL frame via the other link than PTL.

At 1150, the AP MLD 310 may transmit simultaneous trigger frames via multiple links of the STA MLD 320 according to signals received from the STA MLD 320. For example, when the PTL corresponds to a first TID range, the AP MLD 310 may transmit a second trigger frame via a second PTL corresponding to a second transceiver of the two or more transceivers simultaneously with the first trigger frame, wherein the second PTL corresponds to a second TID range, and receive second UL data via the second PTL using the TID in the second TID range.

At 1160, the AP MLD 310 may communicate using an AP MLD link pair between APs sharing a single chip. For example, the AP MLD 310 may transmit a communication signal including an AP MLD link pair corresponding to the PTL and another link associated with a respective transceiver of the two or more transceivers, wherein the transceivers corresponding to the AP MLD link pair reside on a common chip. The AP MLD 31 may transmit DL retransmissions corresponding to one TID via both links of the AP MLD link pair.

At 1170, the AP MLD 310 may receive a communication indicating one or more reasons for the STA MLD 320 not to respond to the trigger frame. For example, the AP MLD 310 may transmit a second trigger frame via the PTL, receive an error message in response to the second trigger frame, and receive third UL data via the PTL for the remaining transmission time of the reserved RU corresponding to the second trigger frame. In some embodiments, the AP MLD 310 may transmit the second trigger frame via the PTL and receive the BSR and QoS null frames for the duration of the reserved RU corresponding to the second trigger frame, or receive link-specific and trigger frame-specific statistics.

Various embodiments may be implemented, for example, using one or more well-known computer systems, such as computer system 1200 shown in fig. 12. Computer system 1200 may be any well known computer capable of performing the functions described herein. For example, and without limitation, STA MLD 120 and/or AP MLD 110 of fig. 1, system 200 of fig. 2, method 1000 of fig. 10, method 1100 of fig. 11 (and/or other devices and/or components shown in the figures) may be implemented using computer system 1200 or portions thereof.

Computer system 1200 includes one or more processors (also referred to as central processing units or CPUs), such as processor 1204. The processor 1204 is connected to a communication infrastructure 1206, which may be a bus. The one or more processors 1204 may each be a Graphics Processing Unit (GPU). In an embodiment, the GPU is a processor designed to handle dedicated electronic circuits for mathematically intensive applications. GPUs may have efficient parallel structures for parallel processing of large data blocks, such as computer graphics applications, graphics, video, and so forth, general-purpose, mathematically intensive data.

Computer system 1200 also includes a user input/output device 1203, such as a monitor, keyboard, pointing device, etc., that communicates with the communication infrastructure 1206 via user input/output interface 1202. Computer system 1200 also includes a main memory or main memory 1208, such as Random Access Memory (RAM). Main memory 1208 may include one or more levels of cache. Main memory 1208 has stored therein control logic components (e.g., computer software) and/or data.

Computer system 1200 may also include one or more secondary storage devices or memories 1210. Secondary memory 1210 may include, for example, a hard disk drive 1212 and/or a removable storage device or drive 1214. Removable storage drive 1214 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and/or any other storage device/drive.

The removable storage drive 1214 may interact with a removable storage unit 1218. Removable storage unit 1218 includes a computer usable or readable storage device having computer software (control logic) and/or data stored thereon. Removable storage unit 1218 may be a floppy disk, magnetic tape, an optical disk, a DVD, an optical storage disk, and/or any other computer data storage device. The removable storage drive 1214 reads from and/or writes to a removable storage unit 1218 in a well known manner.

Secondary memory 1210 may include other means, tools, or other methods for allowing computer programs and/or other instructions and/or data to be accessed by computer system 1200, according to some embodiments. Such means, tools, or other methods may include, for example, a removable storage unit 1222 and an interface 1220. Examples of removable storage units 1222 and interfaces 1220 can include a program cartridge and cartridge interface (such as those found in video game devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and/or any other removable storage unit and associated interface.

Computer system 1200 may also include a communication or network interface 1224. Communication interface 1224 enables computer system 1200 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (referenced individually and collectively by reference numeral 1228). For example, communication interface 1224 may allow computer system 1200 to communicate with remote device 1228 via a communication path 1226, which may be wired and/or wireless, and may include any combination of LANs, WANs, the internet, and the like. The control logic components and/or data can be transferred to and from computer system 1200 via communications path 1226.

The operations in the foregoing embodiments may be implemented in a wide variety of configurations and architectures. Thus, some or all of the operations in the foregoing embodiments may be performed in hardware, software, or in both hardware and software. In some embodiments, a tangible, non-transitory apparatus or article of manufacture comprises a tangible, non-transitory computer-usable or readable medium having stored thereon control logic means (software), also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 1200, main memory 1208, secondary memory 1210, and removable storage units 1218 and 1222, as well as tangible articles of manufacture embodying any combination of the foregoing. Such control logic, when executed by one or more data processing devices (such as computer system 1200), causes such data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparent to one of ordinary skill in the relevant art how to make and use embodiments of this disclosure using data processing devices, computer systems, and/or computer architectures other than those shown in FIG. 12. In particular, embodiments may operate with software, hardware, and/or operating system implementations other than those described herein.

It should be appreciated that the detailed description section, and not the summary and abstract sections, is intended to be used to interpret the claims. The summary and abstract sections may set forth one or more, but not all exemplary embodiments of the disclosure as contemplated by the inventors, and thus are not intended to limit the disclosure or the appended claims in any way.

Although the present disclosure has been described herein with reference to exemplary embodiments in the exemplary field and application, it should be understood that the present disclosure is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of the present disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and/or entities shown in the figures and/or described herein. Furthermore, embodiments (whether explicitly described herein or not) have significant utility for fields and applications beyond the examples described herein.

The implementations have been described herein with the aid of functional building blocks illustrating the implementation of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternate boundaries may be defined so long as the specified functions and relationships (or equivalents thereof) are appropriately performed. Furthermore, alternative embodiments may use orders that differ from those described herein for performing the functional blocks, steps, operations, methods, and the like.

References herein to "one embodiment," "an example embodiment," or similar phrases indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Also, such phraseology and terminology does not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the relevant art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described herein.

The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will adhere to established privacy policies and/or privacy practices. In particular, such entities should exercise and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be readily accessible to the user and should be updated as the collection and/or use of the data changes. Personal information from users should be collected for legal and reasonable use by entities and not shared or sold outside of these legal uses. Furthermore, such collection/sharing should only be after receiving user informed consent. Moreover, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that others having access to the personal information data adhere to their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to collect and/or access specific types of personal information data and to suit applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state law, such as the health insurance transfer and liability act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be processed accordingly. Thus, different privacy practices should be maintained for different personal data types in each country.

Claims (20)

1. A station (STA) multilink device (MLD), the STA MLD comprising: two or more transceivers; and a processor communicatively coupled to the two or more transceivers and configured to: transmitting an indication of a preferred trigger link (PTL) corresponding to a first transceiver of the two or more transceivers; receiving a first trigger frame via the PTL; and First uplink (UL) data stored in a buffer associated with the PTL is transmitted via the PTL in response to the first trigger frame. 2. The STA MLD of claim 1, wherein the processor is further configured to: determining that the PTL is busy; and Second UL data is transmitted via a second link corresponding to a second transceiver of the two or more transceivers. 3. The STA MLD of claim 1, wherein the indication of the PTL is transmitted via an A control field or via a management frame. 4. The STA MLD of claim 1, wherein the STAs of the STA MLD are in a power saving mode, and the processor is further configured to: wake up the transceiver corresponding to the PTL; and Downlink (DL) frames are received via the PTL. 5. The STA MLD of claim 1 , wherein the PTL corresponds to having fewer coexistence links than one or more remaining links associated with respective ones of the two or more transceivers link used. 6. The STA MLD of claim 1, wherein the processor is further configured to: receiving a second trigger frame on a second link, wherein the second trigger frame corresponds to a long resource duration; and Second UL data corresponding to the PTL is transmitted via the second link. 7. The STA MLD of claim 6, wherein the processor is further configured to transmit the first UL data via the PTL using a first traffic ID (TID), and to transmit the first UL data via the PTL using a second TID. The second link transmits the second UL data. 8. The STA MLD of claim 1 , wherein the PTL corresponds to a first Traffic ID (TID) range, and the processor is further configured to: receiving a second trigger frame simultaneously with the first trigger frame via a second PTL corresponding to a second transceiver of the two or more transceivers, wherein the second PTL corresponds to a second TID range ;as well as Second UL data is transmitted via the second PTL using TIDs in the second TID range. 9. The STA MLD of claim 1 , wherein the processor is further configured to receive a communication signal that includes an additional PTL corresponding to the PTL and corresponding to the two or more transceivers. Access Point (AP) MLD link-pair for a link. 10. The STA MLD of claim 9, wherein the processor is further configured to receive a downlink (DL) corresponding to a traffic ID (TID) via two links in the AP MLD link pair. )Retransmission. 11. The STA MLD of claim 1, wherein the processor is further configured to: receiving a second trigger frame via the PTL while transmitting second UL data on another link via a second transceiver of the two or more transceivers; transmitting an error message in response to the second trigger frame; and The third UL data is transmitted via the PTL within a remaining transmission time of reserved resource units (RUs) corresponding to the second trigger frame. 12. The STA MLD of claim 1, wherein the processor is further configured to: receiving a second trigger frame via the PTL while transmitting second UL data on another link via a second transceiver of the two or more transceivers; and Buffer Status Report (BSR) and Quality of Service (QoS) null frames are transmitted for a duration of reserved resource units (RUs) corresponding to the second trigger frame. 13. The STA MLD of claim 1, wherein the processor is further configured to: receiving a second trigger frame via the PTL while transmitting second UL data on another link via a second transceiver of the two or more transceivers; Compute link-specific and/or trigger frame-specific statistics; and Transfer calculated statistics. 14. An access point (AP) multilink device (MLD), comprising: two or more transceivers; and a processor communicatively coupled to the two or more transceivers and configured to: receiving an indication of a preferred trigger link (PTL) corresponding to a first transceiver of the two or more transceivers from the site MLD; transmitting a first trigger frame via the PTL; and First uplink (UL) data via the PTL is received via the PTL in response to the first trigger frame. 15. The AP MLD of claim 14, wherein the PTL corresponds to a first traffic ID (TID) range, and the processor is further configured to: transmitting a second trigger frame simultaneously with the first trigger frame via a second PTL, wherein the second PTL corresponds to a second transceiver of the two or more transceivers, and wherein the second the PTL corresponds to the second TID range; and Second UL data is received via the second PTL using TIDs in the second TID range. 16. The AP MLD of claim 14, wherein the processor is further configured to: transmitting a communication signal comprising an AP MLD link pair corresponding to the PTL and another link associated with a respective one of the two or more transceivers, wherein a link corresponding to the AP the transceivers of the MLD link pair reside on a common chip; and DL retransmissions corresponding to one traffic ID (TID) are transmitted via two links in the AP MLD link pair. 17. The AP MLD of claim 14, wherein the processor is further configured to: transmitting a second trigger frame via the PTL; receiving an error message in response to the second trigger frame; and Third UL data is received via the PTL within a remaining transmission time of a reserved resource unit (RU) corresponding to the second trigger frame. 18. The AP MLD of claim 14, wherein the processor is further configured to: transmitting a second trigger frame via the PTL; and receiving buffer status report (BSR) and quality of service (QoS) empty frames for the duration of reserved resource units (RU) corresponding to said second trigger frame, or receiving link-specific statistics and/or trigger frames specific statistics. 19. A method of operating a station (STA) multilink device (MLD), the method comprising: transmitting an indication of a preferred trigger link (PTL) corresponding to a first transceiver of the two or more transceivers of the STA MLD; receiving a first trigger frame via the PTL; and First uplink (UL) data stored in a buffer associated with the PTL is transmitted via the PTL in response to the first trigger frame. 20. The method of claim 19, further comprising: receiving Multi-User (MU) Enhanced Distributed Channel Access (EDCA) parameters via the PTL; determining that the PTL is busy; and Responsive to the determination, transmitting second UL data via a second link of the STA MLD.