PROTEÇÃO DE MÚLTIPLOS ENLACES COM CONTROLE DE NAV

The method of sending CTS frames on multiple links and managing NAVs through CF-end frames addresses inefficiencies in multi-link wireless networks, ensuring efficient low-latency traffic transmission.

BR112025024279A2Pending Publication Date: 2026-11-10KONINKLIJKE PHILIPS NV
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
BR112025024279
Authority / Receiving Office
BR · BR
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-10
Filing Date
2024-05-06
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In multi-link wireless networks, devices may unnecessarily refrain from transmitting due to misinterpretation of authorization responses, leading to inefficiencies in low-latency traffic transmission.

Method used

Implementing a method where a wireless device sends clear-to-send (CTS) frames on multiple links and transmits a contention-free-end (CF) frame if data is not received within a specified time, using multi-user request-to-send (MU-RTS) frames to manage network allocation vectors (NAV) and reset them based on reception of a CF-end frame.

Benefits of technology

Enhances network efficiency by preventing unnecessary transmission delays and ensuring seamless data exchange across multiple links, particularly in IEEE 802.11 networks.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

In order to achieve flexible NAV setting of multi-link devices, there is provided methods, devices, a system and a computer-program product. A method, comprises receiving, by a first wireless device from a second wireless device, via a first link, a first request to send (RTS) frame requesting transmission of data, via the first link, to the first wireless device and, via a second link, a second RTS frame requesting transmission of the data, via the second link, to the first wireless device. The method comprises transmitting, by the first wireless device to the second wireless device, via the first link, a first clear to send (CTS) frame in response to the first RTS frame and, via the second link, a second CTS frame in response to the second RTS frame, and based on the first wireless device not receiving the data via the first link within a time period from transmission of the first CTS frame, transmitting, by the first wireless device, a contention free-end (CF-end) frame on the first link.
Need to check novelty before this filing date? Find Prior Art

Description

1 / 70 “PROTECTION OF MULTIPLE LINKS WITH NAV CONTROL” FIELD

[001] The present invention relates to wireless networks, particularly, but not limited to, local area networks, such as those using IEEE 802.11 technology. BACKGROUND

[002] Modern wireless networks are often densely deployed, and devices need to be able to adapt to changing situations. In other words, achieving flexibility is desirable, even with complex devices. Furthermore, the requirements for low-latency traffic can result in additional constraints. SUMMARY

[003] The inventors realized that when multi-link devices are used and there is a requirement for low-latency traffic transmission, a situation may arise where two devices are using multi-link connections and a third device hears the authorization response to send from one device, but not the end-of-transmission announcement from the other device. The consequence of this is that the third device may unnecessarily refrain from transmitting.

[004] Consequently, aspects and embodiments of the invention are defined in the appended claims.

[005] In particular, in one aspect, a method is provided comprising receiving, by a first wireless device from a second wireless device, via a first link, a first request to send (RTS) frame requesting data transmission, via the first link, to the first wireless device; and via a second link, a second RTS frame requesting data transmission, via the second link, to the first wireless device; transmitting, by the first wireless device to the second wireless device, via a first link, a first clear to send (CTS) frame in response to the first RTS frame; Petition 870250101983, dated 07 / 11 / 2025, pp. 173 / 288 2 / 70 and through the second link, a second CTS frame in response to the second RTS frame, and based on the first wireless device not receiving the data through the first link within a period of time from the transmission of the first CTS frame, transmit, by the first wireless device, a contention-free-end (CF) frame on the first link.

[006] According to one modality, there is reception, by the first wireless device from the second wireless device, of the data through the second link in response to the second CTS frame.

[007] According to one embodiment, there is transmission, from the first wireless device to the second wireless device, of an acknowledgment frame (ACK acknowledgment) through the second link.

[008] According to one modality, the time period is longer than a short interframe space (SIFS).

[009] According to one modality, the second RTS frame overlaps the first RTS frame.

[010] According to one embodiment, the first and second RTS frames comprise multi-user request-to-send (MURTS) trigger frames.

[011] According to one embodiment, the first MU-RTS trigger frame or the second MU-RTS trigger frame comprises an indication of data transmission through a single link between the first link and the second link.

[012] According to one embodiment, the first wireless device does not receive data through the first link within the time period from the transmission of the first CTS frame, and the method further comprises transmitting, by the first wireless device, a contention-free end frame (CF end) through the first link. Petition 870250101983, dated 07 / 11 / 2025, pp. 174 / 288 3 / 70

[013] In one aspect, a method is provided comprising receiving, by a first wireless device from a second wireless device, via a first link, a first request-to-send (RTS) frame requesting data transmission, via the first link, to the first wireless device; and, via a second link, a second RTS frame requesting data transmission, via the second link, to the first wireless device; transmitting, by the first wireless device to the second wireless device via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame;Based on the first wireless device receiving a frame from the second wireless device indicating the transmission of data through the second link to the first wireless device, the first wireless device then transmits a contention-free end (CF) frame through the first link.

[014] In one aspect, a method is provided, comprising transmitting, by a first wireless device to a second wireless device via a first link, a first request-to-send (RTS) frame requesting data transmission, via the first link, to the second wireless device and via a second link, a second RTS frame requesting data transmission, via the second link, to the second wireless device, receiving, by the first wireless device from the second wireless device, via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame;and through the second link, a second CTS frame in response to the second RTS frame and based on the first wireless device transmitting the data to the second wireless device through the second link, transmit, by the first wireless device to the second wireless device, a frame indicating the transmission of data through the second link to the second wireless device. Petition 870250101983, dated 07 / 11 / 2025, pages 175 / 288 4 / 70

[015] According to one modality, the frame comprises a trigger frame.

[016] According to one embodiment, the trigger frame is transmitted through the first link.

[017] According to one embodiment, the frame comprises an indication for the second wireless device to transmit a contention-free end-frame (CF end) through the first link.

[018] According to one embodiment, the indication to transmit the CF endpoint frame through the first link is provided in a user information field or a common information field of the trigger frame.

[019] According to one modality, the frame comprises a data frame that comprises the data.

[020] According to one modality, there is transmission of the data frame through the second link.

[021] According to one modality, the table includes an indication of the first link.

[022] According to one embodiment, the indication of the first link indicates that data is not transmitted through the first link to the second wireless device.

[023] According to one embodiment, the indication of the first link is given in a Universal Signal (U-SIG) field of a physical layer (PHY) header of the frame.

[024] According to one embodiment, the U-SIG field additionally comprises a link identifier for the first link.

[025] According to one embodiment, the indication of the first link is provided in an aggregate control field (control A) of the frame.

[026] According to one embodiment, control field A is provided in a high-throughput (HT) control field of the frame. Petition 870250101983, dated 07 / 11 / 2025, pp. 176 / 288 5 / 70

[027] According to one modality, the frame indicates that data was not transmitted through the first link.

[028] In one aspect, a method is provided comprising receiving, by a first wireless device from a second wireless device via a first link, a first authorization-to-forward (CTS) frame and via a second link, a second CTS frame, setting a first network allocation vector (NAV) for the first link based on the first CTS frame and a second NAV for the second link based on the second CTS frame and resetting the first NAV for the first link based on receiving, from the second wireless device, a contention-free end.

[029] In one aspect, a method is provided, comprising receiving, by a first wireless device from a second wireless device, a first request-to-send (RTS) frame requesting data transmission to the first wireless device, transmitting, by the first wireless device to the second wireless device, a first authorization-to-send (CTS) frame in response to the first RTS frame and, based on the first wireless device not receiving the data within a period of time from the transmission of the first CTS frame, transmitting, by the first wireless device, a contention-free end-frame (CF-end).

[030] In one aspect, a device is provided that it is arranged to receive, from a second wireless device, via a first link, a first Request to Send (RTS) frame requesting data transmission, via the first link, and via a second link, a second RTS frame requesting data transmission, via the second link, to transmit, to the second wireless device via the first link, a first Authorization to Send (CTS) frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame, and on the basis that the first wireless device does not receive the data via the first link within Petition 870250101983, dated 07 / 11 / 2025, pp. 177 / 288 6 / 70 of a time period from the transmission of the first CTS frame, transmit, by the first wireless device, a contention-free end frame (CF end) on the first link.

[031] In one aspect, a device is provided that it is arranged to receive, from a second wireless device, via a first link, a first request-to-send (RTS) frame requesting data transmission, via the first link, to the first wireless device and via a second link, a second RTS frame requesting data transmission, via the second link, to the first wireless device, to transmit, to the second wireless device via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame and via the second link, a second CTS frame in response to the second RTS frame and based on the device receiving from the second wireless device a frame indicating data transmission via the second link to the first wireless device, to transmit a contention-free end frame (CF end) via the first link.

[032] In one aspect, a device is provided that is arranged to receive, from a first wireless device, a first request-to-send (RTS) frame requesting data transmission to the first wireless device, to transmit, to the first STA, a first authorization-to-send (CTS) frame in response to the first RTS frame and based on not receiving the data within a period of time from the transmission of the first CTS frame, to transmit, by the first wireless device, a contention-free end frame (CF end).

[033] In one aspect, a device is provided that is arranged to transmit, to a first wireless device, via a first link, a first request-to-send (RTS) frame requesting data transmission, via the first link, to the first wireless device and via a second link, a second RTS frame requesting data transmission, via the second Petition 870250101983, dated 07 / 11 / 2025, pages 178 / 288 7 / 70 link, for the first wireless device, receive, from the first wireless device via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame; and, via the second link, a second CTS frame in response to the second RTS frame and, based on transmitting the data to the first wireless device via the second link, transmit, to the first wireless device, a frame indicating the transmission of the data via the second link to the first wireless device.

[034] In one aspect, a device is provided that is arranged to receive, from a first wireless device, via a first link, a first authorization-to-forward (CTS) frame and, via a second link, a second CTS frame; to define a first network allocation vector (NAV) for the first link based on the first CTS frame and a second NAV for the second link based on the second CTS frame; and to reset the first NAV for the first link based on the receipt, from the second wireless device, of a contention-free end (CF end) frame via the first link.

[035] According to one embodiment, the first and second wireless devices are STAs according to the IEEE 802.11 standard.

[036] In one aspect, a wireless communication system is provided comprising a plurality of devices as described herein.

[037] In one aspect, a computer program product is provided characterized by being storable on a computer-readable medium and disposed, when executed on a processor, to execute the methods as described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[038] Examples of several of the various forms of the present disclosure are described here with reference to the drawings: Figure 1 illustrates an example wireless communication network in which the embodiments of the present disclosure can be implemented; Petition 870250101983, dated 07 / 11 / 2025, pp. 179 / 288 8 / 70 Figure 2 is a block diagram illustrating examples of implementations of a station (STA) and an access point (AP); Figure 3 illustrates an example of a medium access control (MAC) frame format; Figure 4 illustrates an example of a null quality of service (QoS) frame indicating buffer status information; Figure 5 illustrates an example format of a physical layer (PHY) protocol data unit (PPDU); Figure 6 illustrates an example that includes buffer status reports by STAs, scheduling by an AP of multi-user uplink (MU) transmissions, and transmission of scheduled uplink transmissions by STAs; Figure 7 illustrates an example reference model for a multi-link device (MLD); Figure 8 illustrates an example of an AP MLD and an associated non-AP MLD; Figure 9 illustrates an example of a multi-link configuration between an AP MLD and a non-AP MLD; Figure 10 illustrates an example of a traffic identifier (TID) to link mapping in a multi-link communication environment; Figure 11 illustrates an example Request to Send (RTS) / Authorization to Send (CTS) procedure; Figure 12 illustrates an example of an existing procedure that can be used to transmit low-latency data protected by an RTS / CTS exchange in a multi-link environment; Figure 13 illustrates an example of a procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality; Petition 870250101983, dated 07 / 11 / 2025, pp. 180 / 288 9 / 70 Figure 14 illustrates another example of a procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality; Figure 15 illustrates an example of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality; Figure 16 illustrates an example of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality; Figure 17 illustrates an example of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality; Figure 18 illustrates an example of a common information field of a basic multi-link element according to a modality; Figure 19 illustrates an example trigger frame that can be used in the modalities; Figure 20 illustrates an example universal signal field (U-SIG) that can be used in the modalities; Figure 21 illustrates an example process according to a modality; Figure 22 illustrates another example process according to a modality; Figure 23 illustrates another example process according to a modality; Figure 24 illustrates another example process according to a modality; Figure 25 illustrates another example process according to a modality. DETAILED DESCRIPTION Petition 870250101983, dated 07 / 11 / 2025, pages 181 / 288 10 / 70

[039] In the present disclosure, several embodiments are presented as examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be evident to those skilled in the relevant art that various changes in form and details can be made without departing from the scope. After reading the description, it will be evident to one skilled in the relevant art how to implement alternative embodiments. The present embodiments may not be limited by any of the exemplary embodiments described. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements of the revealed example embodiments may be combined to create additional embodiments within the scope of the disclosure. Any figures highlighting functionality and advantages are presented for illustrative purposes only.The revealed architecture is flexible and configurable enough that it can be used in ways other than those shown. For example, the actions listed in any flowchart can be reordered or optionally used in some modes.

[040] The modes can be configured to operate as needed. The disclosed mechanism can be executed when certain criteria are met, for example, at a station, an access point, a radio environment, a network, a combination of the above, and / or similar criteria. Example criteria may be based, at least in part, on, for example, wireless device or network node configurations, traffic load, initial system configuration, packet sizes, traffic characteristics, a combination of the above, and / or similar criteria. When one or more criteria are met, several example modalities can be applied. Therefore, it may be possible to implement example modalities that selectively implement disclosed protocols.

[041] In this revelation, one and an and similar phrases are to be interpreted as at least one and one or more. Similarly, any term ending with the suffix (s) is to be interpreted as at least one and one or more. In this Petition 870250101983, dated 07 / 11 / 2025, pages 182 / 28811 / 70 revelation, the term "may" should be interpreted as "may," for example. In other words, the term "may" indicates that the phrase following the term "may" is an example of one among a multitude of suitable possibilities that may or may not be employed by one or more of the various modalities. The terms "comprises" and "consists of," as used here, enumerate one or more components of the element being described. The term "comprises" is interchangeable with "includes" and does not exclude unenumerated components from being included in the element being described. In contrast, "consists of" provides a complete enumeration of one or more components of the element being described. The term "based on," as used here, can be interpreted as "based, at least in part, on" rather than, for example, "based only on." The term "and / or," as used here, represents any possible combination of enumerated elements.For example, A, B, and / or C could represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[042] If A and B are sets and each element of A is an element of B, A is called a subset of B. In this descriptive report, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1, STA2} are: {STA1}, {STA2} and {STA1, STA2}. The phrase based on (or equally based on at least on) indicates that the phrase following the term based on is an example of one among an infinite number of suitable possibilities that may or may not be employed in one or more of the various modalities. The phrase in response to (or equally in response to at least) indicates that the phrase following the phrase in response to is an example of one among an infinite number of suitable possibilities that may or may not be employed in one or more of the various modalities.The phrase "depending on" (or equally "depending at least on") indicates that the phrase following "depending on" is an example of one among a multitude of suitable possibilities that may or may not be employed in one or more of the various modalities. The phrase "employing / using" (or equally "employing / using at least") indicates that the phrase following "employing / using" is an example of one among a multitude of possibilities. Petition 870250101983, dated 07 / 11 / 2025, pages 183 / 288 12 / 70 suitable possibilities that may or may not be employed for one or more of the various modalities.

[043] The term configured can refer to the capability of a device, whether the device is in an operational or non-operational state. Configured can refer to specific settings on a device that affect the device's operational characteristics, whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, and / or the like can be configured within a device, whether the device is in an operational or non-operational state, to provide the device with specific characteristics. Terms such as a control message to trigger on a device can mean that a control message has parameters that can be used to configure specific characteristics or can be used to implement certain actions on the device, whether the device is in an operational or non-operational state.

[044] In this disclosure, parameters (or equally called fields or information elements: IEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M and parameter (IE) M comprises parameter (IE) K and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K and N comprises J. In an example embodiment, when one or more messages / frames comprise a plurality of parameters, this implies that a parameter in the plurality of parameters is in at least one of the one or more messages / frames, but need not be in each of the one or more messages / frames.

[045] Many of the features presented are described as optional through the use of may or parentheses. For the sake of brevity and readability, this disclosure does not explicitly mention each and every permutation that may be obtained by choosing from the set of features. Petition 870250101983, dated 07 / 11 / 2025, pages 184 / 288 13 / 70 optional. The present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven ways, namely, with only one of the three possible features, with any two of the three possible features, or with three of the three possible features.

[046] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware, in software in combination with hardware, firmware, wetware (e.g., hardware with a biological element), or a combination thereof, which may be behaviorally equivalent. For example, modules can be implemented as a software routine written in a computer language configured to run on a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, or similar) or a modeling / simulation program such as Simuenclace, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware.Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly language, C, C++, or similar languages. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs), such as VHDL (VHSIC hardware description language) or Verilog, which configure connections between internal hardware modules with lower functionality in a device. Petition 870250101983, dated 07 / 11 / 2025, pages 185 / 288 14 / 70 programmable. The technologies mentioned are often used in combination to achieve the result of a functional module.

[047] Figure 1 illustrates an example wireless communication network in which the embodiments of the present disclosure can be implemented.

[048] As shown in Figure 1, example wireless communication networks may include an Institute of Electrical and Electronics Engineers (IEEE) 802.11 infrastructure network (WLAN). The WLAN infrastructure network may include one or more basic service sets (BSSs) and a distribution system.

[049] BSSs 110-1 and 110-2 each include a set of one access point (AP or AP STA) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes an AP 104-1 and an STA 106-1, and BSS 110-2 includes an AP 104-2 and STAs 106-2 and 106-3. The AP and at least one STA in a BSS execute an association procedure to communicate with each other.

[050] The DS 130 can be configured to connect the BSS 110-1 and the BSS 110- 2. In this way, DS 130 can enable an extended service set (ESS) 150. Within ESS 150, APs 104-1 and 104-2 are connected through DS 130 and can have the same service set identification (SSID).

[051] The WLAN 102 infrastructure network can be coupled to one or more external networks. For example, as shown in Figure 1, the WLAN 102 infrastructure network can be connected to another 108 network (e.g., 802.X) via a 140 portal. The 140 portal can act as a bridge connecting the DS 130 of the WLAN 102 infrastructure network to the other 108 network.

[052] The example wireless communication networks illustrated in Figure 1 may additionally include one or more ad-hoc networks or independent BSSs (IBSSs independent BSSs). An ad-hoc network or IBSS is a network that includes a plurality of STAs that are within communication range of each other. The plurality of Petition 870250101983, dated 07 / 11 / 2025, pages 186 / 288 15 / 70 STAs are configured so that they can communicate with each other using direct point-to-point communication (i.e., not through an AP).

[053] For example, in Figure 1, STAs 106-4, 106-5, and 106-6 can be configured to form a first IBSS 112-1. Similarly, STAs 106-7 and 106-8 can be configured to form a second IBSS 112-2. Since an IBSS does not include an AP, it does not include a centralized management entity. Instead, the STAs within an IBSS are managed in a distributed manner. The STAs that form an IBSS can be fixed or mobile.

[054] A STA as a predetermined functional medium may include a medium access control (MAC) layer that conforms to an IEEE 802.11 standard. A physical layer interface for a radio medium may be used between APs and non-AP stations (STAs). The STA may also be referred to using various other terms, including mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term user may be used to denote an STA that participates in multi-user multiple input, multiple output (MU MIMO) and / or orthogonal frequency division multiple access (OFDMA) uplink transmission.

[055] A physical layer (PHY) protocol data unit (PPDU) can be a composite structure that includes a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). For example, the PSDU may include a PHY (PLCP) convergence protocol preamble and header and / or one or more MAC protocol data units (MPDUs). The information provided in the PHY preamble can be used by a receiving device to decode subsequent data in the PSDU. In cases where PPDUs are transmitted over a bonded channel (a channel formed through channel bonding), the preamble fields Petition 870250101983, dated 07 / 11 / 2025, pp. 187 / 288 16 / 70 can be duplicated and transmitted on each of the multiple component channels. The PHY preamble can include both a legacy portion (or legacy preamble) and a non-legacy portion (or non-legacy preamble). The legacy preamble can be used for packet detection, automatic gain control, and channel estimation, among other uses. The legacy preamble can also generally be used to maintain compatibility with legacy devices. The format, encoding, and information provided in the non-legacy portion of the preamble are based on the specific IEEE 802.11 protocol to be used to transmit the payload.

[056] A frequency band may include one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax and / or 802.11be standard amendments may be transmitted across the 2.4 GHz, 5 GHz and / or 6 GHz bands, each of which may be divided into multiple 20 MHz channels. PPDUs may be transmitted over a physical channel with a minimum bandwidth of 20 MHz. Larger channels may be formed by channel linking. For example, PPDUs may be transmitted over physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz or 520 MHz by linking multiple 20 MHz channels.

[057] Figure 2 is a block diagram illustrating sample implementations of a STA 210 and an AP 260. As shown in Figure 2, the STA 210 can include at least one processor 220, one memory 230, and at least one transceiver 240. The AP 260 can include at least one processor 270, one memory 280, and at least one transceiver 290. The 220 / 270 can be operatively connected to the memory 230 / 280 and / or the transceiver 240 / 290.

[058] The 220 / 270 processor can implement functions of the PHY layer, the MAC layer, and / or the logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). The 220 / 270 processor can include one or more processors and / or one or more controllers. The one or more processors and / or one or more controllers can comprise, for example, Petition 870250101983, dated 07 / 11 / 2025, pp. 188 / 288 17 / 70 for example, a general-purpose processor, a digital signal processor (PSD), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a logic circuit, or a chipset, for example.

[059] The 230 / 280 memory may include read-only memory (ROM), random access memory (RAM), flash memory, a memory card, storage media, and / or other storage unit. The 230 / 280 memory may comprise one or more non-transient computer-readable media. The 230 / 280 memory may store instructions or computer program code that can be executed by the 220 / 270 processor to perform one or more of the operations / modes discussed in this application. The 230 / 280 memory may be implemented (or located) within the 220 / 270 processor or external to the 220 / 270 processor. The 230 / 280 memory may be operationally connected to the 220 / 270 processor through various means known in the art.

[060] The 240 / 290 transceiver can be configured to transmit / receive radio signals. In one embodiment, the 240 / 290 transceiver can implement a corresponding device PHY layer (STA 210 or AP 260). In one embodiment, STA 210 and / or AP 260 can be a multi-link device (MLD), which is a device capable of operating across multiple links as defined by the IEEE 802.11 standard. Thus, STA 210 and / or AP 260 can each implement multiple PHY layers. The multiple PHY layers can be implemented using one or more of the 240 / 290 transceivers.

[061] Figure 3 illustrates an example MAC frame format. In operation, an STA can construct a subset of MAC frames for transmission and can decode a subset of received MAC frames upon validation. The specific subsets of frames that an STA can construct and / or decode can be determined by the functions supported by the STA. An STA can validate a received MAC frame using the sequence of Petition 870250101983, dated 07 / 11 / 2025, pp. 189 / 288 18 / 70 frame check sequence (FCS) is contained within the frame and can interpret certain fields from the MAC headers of all frames.

[062] As shown in Figure 3, a MAC frame includes a MAC header, a variable-length frame body, and a frame check sequence (FCS).

[063] The MAC header includes a frame control field, an optional duration / ID field, address fields, an optional sequence control field, an optional QoS control field, and an optional HT control field.

[064] The frame control field includes the following subfields: protocol version, type, subtype, To DS, From DS, more fragments, retry, power management, more data, protected frame and +HTC.

[065] The protocol version subfield is invariant in size and position across all revisions of the IEEE 802.11 standard. The value of the protocol version subfield is 0 for MAC frames.

[066] The type and subtype subfields together identify the function of the frame. MAC. There are three types of frames: control, data, and management. Each of the frame types has several defined subtypes. The bits within the subtype subfield are used to indicate a specific modification of the basic data frame (subtype 0). For example, in data frames, the most significant bit (MSB) of the subtype subfield, bit 7 (B7) of the frame control field, is defined as the QoS subfield. When the QoS subfield is set to 1, it indicates a QoS data frame, which is a data frame that contains a QoS control field in its MAC header. The second MSB of the subtype field, bit 6 (B6) of the frame control field, when set to 1 in data subtypes, indicates a data frame that does not contain a frame body field. Petition 870250101983, dated 07 / 11 / 2025, pages 190 / 288 19 / 70

[067] The To DS subfield indicates whether a data frame is destined for the distribution system (DS). The From DS subfield indicates whether a data frame originates from the DS.

[068] The more fragments subfield is set to 1 in all data or management frames that have another fragment to follow from the MAC service data unit (MSDU) or MAC management protocol data unit (MMPDU) carried by the MAC frame. The more fragments subfield is set to 0 in all other frames in which the more fragments subfield is present.

[069] The retry subfield is set to 1 in any data or management frame that is a retransmission of a previous frame. It is set to 0 in all other frames in which the retry subfield is present. A receiving STA uses this indication to assist it in the process of eliminating duplicate frames. These rules do not apply to frames sent by an STA under a block contract.

[070] The power management subfield is used to indicate the power management mode of an STA.

[071] The more data subfield indicates for a STA in power save (PS) mode that bufferable units (BUs) are buffered for that STA on the AP. The more data subfield is valid for individually addressed management data or frames transmitted by an AP to a STA in PS mode. The more data subfield is set to 1 to indicate that at least one additional buffered BU is present for the STA.

[072] The protected frame subfield is set to 1 if the frame body field contains information that has been processed by a cryptographic encapsulation algorithm.

[073] The +HTC subfield indicates that the MAC frame contains an HT control field. Petition 870250101983, dated 07 / 11 / 2025, pages 191 / 288 20 / 70

[074] The duration / ID field in the MAC header indicates various contents, depending on the frame type and subtype and the QoS capabilities of the sending STA. For example, in power save poll (PS-Poll) control frames, the duration / ID field carries an association identifier (AID) of the STA that transmitted the frame in the least significant 14 bits (LSB), with the most significant 2 bits (MSB) set to 1. In other frames sent by STAs, the duration / ID field contains a duration value (in microseconds) that is used by a receiver to update a network allocation vector (NAV). The NAV is a counter that indicates to an STA an amount of time during which the STA needs to delay access to the shared medium.

[075] Up to four address fields may be present in the MAC frame format. The address fields are used to indicate the basic service set identifier (BSSID), source address (SA), destination address (DA), transmitting address (TA), and receiving address (RA). Certain frames may not contain some of the address fields. Certain use of the address field may be specified by the relative position of the address field (1 to 4) within the MAC header, regardless of the type of address present in that field. Specifically, address field 1 always identifies the intended receiver(s) of the frame, and address field 2, when present, always identifies the transmitter of the frame.

[076] The sequence control field includes two subfields, a sequence number subfield and a fragment number subfield. The sequence number subfield in data frames indicates the sequence number of the MSDU (if not in an aggregated MSDU (A-MSDU)) or A-MSDU. The sequence number subfield in management frames indicates the sequence number of the frame. The fragment number subfield indicates the number of each fragment of an MSDU or an MMPDU. The fragment number is defined Petition 870250101983, dated 07 / 11 / 2025, pp. 192 / 288 21 / 70 is set to 0 in the first or only fragment of an MSDU or MMPDU and is incremented by one for each successive fragment of that MSDU or MMPDU. The fragment number is set to 0 in a MAC Protocol Data Unit (MPDU) containing an A-MSDU or in an MPDU containing an MSDU or MMPDU that is not fragmented. The fragment number remains constant across all fragment retransmissions.

[077] The QoS control field identifies the traffic category (TC) or traffic stream (TS) to which the MAC frame belongs. The QoS control field may also indicate various other QoS-related, A-MSDU-related, and mesh-related information about the frame. This information may vary depending on the frame type, frame subtype, and transmission STA type. The QoS control field is present in all data frames where the QoS subfield of the subtype subfield is equal to 1.

[078] The HT control field is present in QoS, QoS null, and management data frames, as determined by the +HTC subfield of the frame control field.

[079] The frame body field is a variable-length field that contains information specific to individual frame types and subtypes. The frame body can include one or more MSDUs or MMPDUs. The minimum length of the frame body is 0 octets.

[080] The FCS field contains a 32-bit Cyclic Redundancy Check (CRC) code. The FCS field value is calculated from all fields in the MAC header and frame body field.

[081] Figure 4 illustrates an example of a QoS null frame indicating buffer status information. A QoS null frame refers to a QoS data frame with an empty frame body. The QoS null frame includes a QoS control field and an optional HT control field that may contain a buffer status report (BSR) control subfield. A Petition 870250101983, dated 07 / 11 / 2025, pp. 193 / 288 A 22 / 70 QoS null frame indicating buffer status information can be transmitted by a STA to an AP.

[082] The QoS control field may include a traffic identifier (TID) subfield, an acknowledgment policy indicator subfield, and a queue size subfield (or a requested transmission opportunity duration (TXOP) subfield).

[083] The TID subfield identifies the traffic TC or TS for which a TXOP is being requested, through the configuration of the requested TXOP duration subfield or queue size. The encoding of the TID subfield depends on the access policy (e.g., allowed value of 0 to 7 for the enhanced distributed channel access (EDCA) access policy to identify the user priority for TC or TS).

[084] The acknowledgment policy indicator subfield, along with other information, identifies the acknowledgment policy followed by the delivery of the MPDU (e.g., normal acknowledgment, implicit block acknowledgment request, no acknowledgment, block acknowledgment, etc.)

[085] The queue size subfield is an 8-bit field that indicates the amount of traffic buffered for a given TC or TS in the STA for transmission to the AP identified by the receiver address of the frame containing the subfield. The queue size subfield is present in null QoS frames sent by an STA when bit 4 of the QoS control field is set to 1. The AP can use information contained in the queue size subfield to determine the TXOP duration assigned to the STA or to determine the uplink (UL) resources assigned to the STA.

[086] In a frame sent by or to a non-high-efficiency STA (without HE) For non-high efficiency queues, the following rules can be applied to the queue size value:

[087] The queue size value is the approximate total size, rounded to the nearest multiple of 256 octets and expressed in units of 256 octets, of Petition 870250101983, dated 07 / 11 / 2025, pp. 194 / 288 23 / 70 all MSDUs and A-MSDUs buffered in the STA (excluding the MSDU or A-MSDU contained in this QoS data frame) in the delivery queue used for MSDUs and A-MSDUs with TID values ​​equal to the value indicated in the TID subfield of the QoS control field.

[088] A queue size value of 0 is used only to indicate the absence of any buffered traffic in the queue used for the specified TID.

[089] A queue size value of 254 is used for all sizes greater than 64768 octets.

[090] A queue size value of 255 is used to indicate an unspecified or unknown size.

[091] In a frame sent by a HE STA to a HE AP, the following rules may apply to the queue size value.

[092] The queue size value, QS, is the approximate total size in octets of all MSDUs and A-MSDUs buffered in the STA (including MSDUs or A-MSDUs contained in the same PSDU as the frame containing the queue size subfield) in the delivery queue used for MSDUs and A-MSDUs with TID values ​​equal to the value indicated in the TID subfield of the QoS control field.

[093] The queue size subfield includes a scaling factor subfield in bits B14-B15 of the QoS control field and an unscaled value, UV, in bits B8-B13 of the QoS control field. The scaling factor subfield provides the scaling factor, SF.

[094] A STA obtains the queue size, QS, from a received QoS control field, which contains a scaling factor, SF, and an unscaled value, UV, as follows: QS = x UV, if SF is equal to 0; 1024 + 256 x UV, if SF is equal to 1; 17408 + 2048 x UV, if SF is equal to 2; Petition 870250101983, dated 07 / 11 / 2025, pp. 195 / 288 24 / 70 148480 + 32768 χ UV, if SF equals 3 and UV is less than 62; 2147328, if SF equals 3 and UV equals 62; Not specified or Unknown, if SF equals 3 and UV equals 63.

[095] The requested TXOP duration subfield, which may be included instead of the queue size subfield, indicates the duration, in 32 microsecond (µs) units, that the sending STA determines it needs for its next TXOP for the specified TID. The requested TXOP duration subfield is set to 0 to indicate that no TXOP is requested for the specified TID in the current service period (SP). The requested TXOP duration subfield is set to a non-zero value to indicate a requested TXOP duration in the range of 32 µs to 8160 µs in 32 µs increments.

[096] The HT control field may include a BSR control subfield, which may contain buffer status information used for UL MU operation. The BSR control subfield may be formed from an access category index (ACI) bitmap subfield, a delta TID subfield, an elevated ACI subfield, a scale change factor subfield, an elevated queue size subfield, and a total queue size subfield of the HT control field.

[097] The ACI bitmap subfield indicates the access categories (ACs - access categories) for which the buffer status is reported (e.g., B0: best effort (AC_BE), B1: background (AC_BK), B2: video (AC_VI), B3: voice (AC_VO), etc.). Each bit of the ACI bitmap subfield is set to 1 to indicate that the buffer status of the corresponding AC is included in the total queue size subfield and set to 0 otherwise, except that if the ACI bitmap subfield is 0 and the delta TID subfield is 3, then the buffer status of all 8 TIDs is included.

[098] The delta TID subfield, together with the ACI bitmap subfield values, indicate the number of TIDs to which the STA is reporting buffer status. Petition 870250101983, dated 07 / 11 / 2025, pp. 196 / 288 25 / 70

[099] The high ACI subfield indicates the ACI of the CA for which the BSR is indicated in the high queue size subfield. The ACI to AC mapping is defined as mapping ACI value 0 to AC_BE, mapping ACI value 1 to AC_BK, mapping ACI value 2 to AC_VI, and mapping ACI value 3 to AC_VO.

[0100] The scale change factor subfield indicates the unit SF, in octets, of the high queue size and total queue size subfields.

[0101] The high queue size subfield indicates the amount of buffered traffic, in SF unit octets, for the AC identified by the high ACI subfield, which is destined for the STA identified by the receiver address of the frame containing the BSR control subfield.

[0102] The total queue size subfield indicates the amount of buffered traffic, in SF unit octets, for all ACs identified by the ACI bitmap subfield, destined for the STA identified by the receiver address of the frame containing the BSR control subfield.

[0103] The queue size values ​​in the high queue size and total queue size subfields are the total sizes, rounded to the nearest multiple of SF octets, of all MSDUs and A-MSDUs buffered in the STA (including MSDUs or A-MSDUs contained in the same PSDU as the frame containing the BSR control subfield) in delivery queues used for MSDUs and A-MSDUs associated with the AC(s) that is / are specified in the high ACI and ACI bitmap subfields, respectively.

[0104] A queue size value of 254 in the high queue size and total queue size subfields indicates that the amount of buffered traffic is greater than 254 χ² SF octets. A queue size value of 255 in the high queue size and total queue size subfields indicates that the amount of buffered traffic is an unspecified or unknown size. The queue size value for QoS data frames containing fragments may remain constant. Petition 870250101983, dated 07 / 11 / 2025, pages 197 / 288 26 / 70 even though the amount of queued traffic changes as successive fragments are transmitted.

[0105] The MAC service provides peer entities with the ability to exchange MSDUs. To support this service, a local MAC uses the underlying PHY-level service to transport MSDUs to a peer MAC entity. This asynchronous MSDU transport is performed on a connectionless basis.

[0106] Figure 5 illustrates an example PPDU format. As shown, the PPDU can include a PHY preamble, a PHY header, a PSDU, and tail and padding bits.

[0107] A PSDU can include one or more MPDUs, such as a QoS data frame, an MMPDU, a MAC control frame, or a QoS null frame. In the case of an MPDU carrying a QoS data frame, the MPDU frame body can include an MSDU or an A-MSDU.

[0108] By default, MSDU transport is performed on a best-effort basis. That is, there is no guarantee that a transmitted MSDU will be successfully delivered. However, the QoS setup uses a traffic identifier (TID) to specify differentiated services based on MSDUs.

[0109] A STA can differentiate MSDU delivery according to the designated traffic category (TC) or traffic flow (TS) of individual MSDUs. MAC sublayer entities determine a user priority (UP) for an MSDU based on a TID value provided with the MSDU. The QoS installation supports eight UP values. UP values ​​range from 0 to 7 and form an ordered sequence of priorities, with 1 being the lowest value, 7 the highest value, and 0 between 2 and 3.

[0110] An MSDU with a specific UP is said to belong to a traffic category with that UP. The UP can be assigned to each MSDU at the Medium Access Control Service (MAC SAP) access point directly in a UP parameter. An A-MPDU can include MPDUs with different TID values. Petition 870250101983, dated 07 / 11 / 2025, pages 198 / 288 27 / 70

[0111] A STA can deliver buffer status reports (BSRs) to assist an AP in allocating UL MU resources. The STA can implicitly deliver BSRs in the QoS control field or BSR control subfield of any frame transmitted to the AP (unsolicited BSR) or explicitly deliver BSRs in a frame sent to the AP in response to a BSRP trigger frame (solicited BSR).

[0112] The buffer status reported in the QoS control field includes a queue size value for a given TID. The buffer status reported in the BSR control field includes an ACI bitmap, a delta TID, a high-priority AC, and two queue sizes.

[0113] A STA can report the buffer status to the AP, in the QoS control field, of QoS null frames and transmitted QoS data frames and, in the BSR control subfield (if present), of QoS null frames, QoS data frames and transmitted management frames, as defined below.

[0114] The STA can report the queue size for a given TID in the queue size subfield of the QoS control field of transmitted QoS data frames or QoS null frames; the STA can set the queue size subfield to 255 to indicate an unknown / unspecified queue size for that TID. The STA can aggregate multiple QoS data frames or QoS null frames into an A-MPDU to report the queue size for different TIDs.

[0115] The STA can report the buffer status in the BSR control subfield of transmitted frames if the AP has indicated its support for receiving the BSR control subfield.

[0116] A high-efficiency (HE) STA can report the queue size for a preferred AC, indicated by the elevated ACI subfield, in the elevated queue size subfield of the BSR control subfield. The STA can set the elevated queue size subfield to 255 to indicate an unknown / unspecified queue size for that AC. Petition 870250101983, dated 07 / 11 / 2025, pp. 199 / 288 28 / 70

[0117] A HE STA can report the queue size for ACs indicated by the ACI bitmap subfield in the total queue size subfield of the BSR control subfield. The STA can set the total queue size subfield to 255 to indicate unknown / unspecified BSRs for those ACs.

[0118] Figure 6 illustrates an example that includes buffer status reports by STAs, scheduling by an AP of multi-user uplink (MU) transmissions, and transmission of scheduled uplink transmissions by STAs.

[0119] As shown, the AP can request buffer status from one or more associated STAs (STA 1 and STA 2) by sending a buffer status report polling trigger frame (BSRP). Upon receiving the BSRP trigger frame, STA 1 and / or STA 2 can each generate a trigger-based PPDU (TB) if the BSRP trigger frame contains, in a user information field, the 12 LSBs of the STA AID.

[0120] STA 1 and / or STA 2 may each include, in the PPDU TB, one or more QoS null frames. The one or more QoS null frames may contain one or more QoS control fields or one or more BSR control subfields.

[0121] As described earlier, a QoS control field can include a queue size subfield for a TID for which the STA has a queue size to report to the AP. For example, as shown in Figure 6, STA 1 can respond to the AP's BSRP trigger frame by transmitting an A-MPDU including multiple QoS null frames. The QoS null frames each indicate, in their respective QoS control field, a queue size for a respective TID, for example, TID 0 and TID 2. Similarly, STA 2 can respond to the BSRP trigger frame by transmitting an MPDU including a QoS null frame, which indicates a queue size for TID 2 in its QoS control field.

[0122] A BSR control subfield can include a queue size from all subfields indicating the queue size for the ACs, indicated by the ACI bitmap subfield, for which the STA has a queue size to report to the AP if the AP Petition 870250101983, dated 07 / 11 / 2025, pp. 200 / 288 29 / 70 has indicated its support to receive the BSR control subfield. ASTA defines a TID delta, a scaling factor, a high ACI, and the high queue size subfields of the BSR control subfield.

[0123] Upon receiving BSRs from STA 1 and STA 2, the AP can transmit a basic trigger frame to allocate UL MU resources to STA 1 and STA 2. In response, STA 1 can transmit a PPDU TB containing QoS data frames with TID 0 and TID 2, and STA 2 can transmit a PPDU TB containing one or more QoS data frames with TID 0. The AP can acknowledge PPDUs TB transmitted from STA 1 and STA 2 by sending a multi-STA block acknowledgment frame.

[0124] Figure 7 illustrates an example reference model for a multi-link device (MLD).

[0125] An MLD is an entity capable of managing communication across multiple links. The MLD can be a logical entity and can have more than one affiliated station (STA). An MLD can be an access point MLD (AP MLD) where an STA affiliated to the MLD is an AP STA (or an AP). An MLD can be a non-access point MLD (non-AP MLD) where an STA affiliated to the MLD is a non-AP STA (or an STA).

[0126] Communication through different frequency bands / channels may occur simultaneously, or not, depending on the communication capabilities of both the AP MLD and the non-AP MLD.

[0127] As shown in Figure 7, an MLD can have a single MAC service access point (MAC SAP) for the LLC layer, which includes a MAC data service. The MLD can support multiple MAC sublayers coordinated by a sublayer management entity (SME). Each AP STA (or non-AP STA) affiliated with an AP MLD (or non-AP MLD) has a different MAC address within the MLD.

[0128] The SME is responsible for coordinating the MAC sublayer management entities (MLMEs) of the MLD's affiliated STAs to maintain a single key management entity. Petition 870250101983, dated 07 / 11 / 2025, pages 201 / 288 30 / 70 robust security network association (RSNA), as well as a single IEEE 802.1X authenticator or supplicant for multi-link operation (MLO).

[0129] Multi-link operation (MLO) procedures allow a pair of MLDs to discover, synchronize, (de)authenticate, (re)associate, disassociate, and manage resources with each other on any common bands or channels supported by both MLDs. The authenticator and MAC address of an AP MLD can be identified by the same MAC address of the AP MLD. The supplicant and MAC address of a non-AP MLD can be identified by the same MAC address of the non-AP MLD.

[0130] Figure 8 illustrates an example of an AP MLD and an associated non-AP MLD.

[0131] As shown, the AP MLD has two affiliated APs (AP1 and AP2), and the non-AP MLD has two affiliated STAs (STA1 and STA2). The AP MLD and the non-AP MLD can be communicatively coupled by two links (link 1 and link 2). Link 1 is established between AP1 and STA1, and link 2 is established between AP2 and STA2.

[0132] In general, the MAC addresses of an MLD and its affiliated STAs are different from each other. For example, as shown in Figure 8, the AP MLD may have a MAC address M, AP 1 may have a MAC address w, and AP2 may have a MAC address x. Similarly, the non-AP MLD may have MAC address P, STA 1 may have MAC address y, and STA2 may have MAC address z.

[0133] As shown in Figure 8, with each MLD, the MAC sublayer can be further divided into an upper MLD MAC sublayer and a lower MLD MAC sublayer. The upper MLD MAC sublayer (MLD) performs functionalities that are common to all links. The lower MLD MAC sublayer performs functionalities that are local to each link. Some of the functionalities require the joint processing of both the upper and lower MLD MAC sublayers. Petition 870250101983, dated 07 / 11 / 2025, pp. 202 / 288 31 / 70

[0134] The higher MAC sublayer functions of MLD may include: authentication, association and reassociation (between an AP MLD and a non-AP MLD); Security association (e.g., pairwise master key security association (PMKSA), pairwise transient key security association (PTKSA)) and group temporal key (GTK) / integrity CTK (IGTK) / beacon IGTK (BIGTK) distribution; Assignment of sequence number (SN) / packet number (PN) to frames to be encrypted by pairwise transient key (PTK) for single-cast frames; Encryption / decryption using PTK for single-cast frames; Selection of the lower MAC sublayer of MLD for transmission (TID to link mapping); Reordering of packets to ensure delivery in order for each block recognition session; Block recognition scoreboarding for individually addressed frames (in collaboration with the lower MAC sublayer of MLD); optionally, the upper MAC sublayer of MLD delivers the block recognition record on one link to the lower MAC sublayer of MLD from other links; and exchange / indication of MLD-level management information via the lower MAC sublayer of MLD.

[0135] Lower MAC sublayer functions (MLD) may include: GTK / IGTK / BIGTK maintenance specific to the link (between an AP affiliated with the AP MLD and a STA affiliated with the non-AP MLD); Petition 870250101983, dated 07 / 11 / 2025, pages 203 / 288 32 / 70 encryption / decryption / link-specific integrity protection and PN assignment using GTK / IGTK / BIGTK (between an AP affiliated with the AP MLD and a non-AP MLD affiliated STA); Exchange / indication of link-specific management information (e.g., radio beacon); Exchange / indication of link-specific control information (e.g., RTS / CTS, acknowledgments, etc.); energy saving state and mode; MAC address filtering for frame reception; and block-aware scoreboarding for individually addressed frames (in collaboration with the MLD upper MAC sublayer); optionally, the MLD lower MAC sublayer receives the block-aware record on the other links from the MLD upper MAC sublayer.

[0136] Multi-link (re)configuration between a non-AP MLD and an AP MLD may include a (re)association request / response frame exchange. A (re)association request / response frame exchange for a multi-link configuration may include both frames carrying a basic multi-link element.

[0137] In the (re)association request form, the non-AP MLD indicates the links that are requested for (re)configuration and the capabilities and operational parameters of the requested links. The non-AP MLD can request the (re)configuration of links with a subset of APs affiliated with the AP MLD. The links that are requested for (re)configuration and the capabilities and operational parameters of the requested links are independent of the existing configuration links with an associated AP MLD and the capabilities and operational parameters of the configuration links.

[0138] In the (re)association response frame, the AP MLD can indicate the requested links that are accepted and the requested links that are rejected for (re)configuration, and the capabilities and operational parameters of the links. Petition 870250101983, dated 07 / 11 / 2025, pages 204 / 288 33 / 70 requested. The AP MLD can accept a subset of the links that are requested for (re)configuration. The (re)association response frame is sent to the non-AP STA, affiliated with the non-AP MLD, that sent the (re)association request frame.

[0139] An MLD that requests or accepts the (re)configuration of multiple links for any two links ensures that each link is located on a different non-overlapping channel. After successful (re)configuration of multiple links between a non-AP MLD and an AP MLD, the non-AP MLD and the AP MLD configure links for multi-link operation, and the non-AP MLD is (re)associated with the AP MLD. For each link configuration, the corresponding non-AP STA affiliated with the non-AP MLD is in the same associated state as the non-AP MLD and is associated with a corresponding AP affiliated with the AP MLD. For each link configuration, the functionalities between a non-AP STA and its associated AP are activated, unless the functionalities have been extended to the MLD level or specified otherwise.

[0140] Figure 9 illustrates an example of a multi-link configuration between an AP MLD and a non-AP MLD. As shown, the AP MLD has three affiliated APs: AP 1 operating in the 2.4 GHz band, AP 2 operating in the 5 GHz band, and AP 3 operating in the 6 GHz band. The non-AP MLD has three affiliated STAs: non-AP STA 1 operating in the 2.4 GHz band, non-AP STA 2 operating in the 5 GHz band, and non-AP STA 3 operating in the 6 GHz band.

[0141] The non-AP MLD can initiate multi-link configuration via non-AP STA 1 by sending an association request frame to AP 1 affiliated with the AP MLD. In the association request frame, the transmitter address (TA) field is set to the MAC address of non-AP STA 1 and the receiver address (RA) field is set to the MAC address of AP 1. The association request frame includes a basic multi-link element indicating the MAC address of the non-AP MLD and the complete information of non-AP STA 1, non-AP STA 2, and non-AP STA 3. The association request frame can Petition 870250101983, dated 07 / 11 / 2025, pages 205 / 288 34 / 70 request the configuration of three links between the non-AP MLD and the AP MLD (one link between AP 1 and non-AP STA 1, one link between AP 2 and non-AP STA 2, and one link between AP 3 and non-AP STA 3).

[0142] The AP MLD can respond to the multi-link configuration request from the AP by sending an association response frame to the non-AP STA 1 affiliated with the non-AP MLD. In the association response frame, the TA field is set to the MAC address of AP 1 and the RA field is set to the MAC address of the non-AP STA 1. The association response frame includes a basic multi-link element indicating the MAC address of the AP MLD and the complete information of AP 1, AP 2, and AP 3. The association response frame signals the successful multi-link configuration by configuring three links between the non-AP MLD and the AP MLD (link 1 between AP 1 and non-AP STA 1, link 2 between AP 2 and non-AP STA 2, and link 3 between AP 3 and non-AP STA 3).

[0143] By default, all TIDs on the non-AP MLD are mapped to all configuration links for both uplink and downlink. The TID-to-link mapping mechanism allows an AP MLD and a non-AP MLD that has performed or is performing multi-link configuration to specify how UL and DL QoS traffic corresponding to different TIDs (e.g., between 0 and 7) can be assigned to configuration links. In a negotiated TID-to-link mapping, a TID can be mapped to a set of links, which is a subset of configuration links, in the range from a single configuration link to all configuration links.

[0144] A configuration link is set to enabled for a non-AP MLD if at least one TID is mapped to that link in DL or UL, and is set to disabled if no TID is mapped to that link in DL and UL. At any given time, a TID is always mapped to at least one configuration link in DL and UL, meaning that a mapping change of Petition 870250101983, dated 07 / 11 / 2025, pp. 206 / 288 35 / 70 A TID for a link can only be valid and appropriate if it does not result in a TID with a set of mapped links made up of zero configuration links.

[0145] By default, all configuration links are enabled. If a link is enabled for a non-AP MLD, it can be used for the exchange of individually addressed frames, subject to the power state of the non-AP STA operating on that link. Only MSDUs or A-MSDUs with TIDs mapped to a link can be transmitted on that link in the direction (DL / UL) corresponding to the TID-to-link mapping. Individually addressed control frames and management frames can be sent on any enabled link between an affiliated STA of the non-AP MLD and a corresponding AP of the AP MLD, in both DL and UL.

[0146] If a link is disabled for a non-AP MLD, the link may not be used for the exchange of individually addressed frames between an affiliated STA of the non-AP MLD and a corresponding AP of the AP MLD.

[0147] If a TID is mapped in UL to a set of links enabled for a non-AP MLD, the non-AP MLD can use any link within that set of links enabled to transmit individually addressed MSDUs or A-MSDUs corresponding to that TID.

[0148] If a TID is mapped in DL to a set of links enabled for a non-AP MLD, the non-AP MLD can retrieve individually addressed BUs buffered in the AP MLD that are MSDUs or A-MSDUs corresponding to the TID, on any link in the set of enabled links. Conversely, the AP MLD can use any link within the set of enabled links to transmit individually addressed MSDUs or A-MSDUs corresponding to the TID, subject to the power state of the non-AP STA on each of the links used.

[0149] If the default mode is used, the non-AP MLD can retrieve buffered BUs from the AP MLD on any configuration link, although the AP MLD can recommend a link. Petition 870250101983, dated 07 / 11 / 2025, pages 207 / 288 36 / 70

[0150] A non-AP MLD can retrieve buffered BUs that are buffered MMPDUs in the AP MLD on any enabled link. An AP MLD can use any enabled link to transmit individually addressed buffered management frames that are not metering MMPDUs, subject to the power state of the non-AP STA on the link used.

[0151] If an STA affiliated with a non-AP MLD is in active mode on a link with a set of TIDs mapped for DL ​​transmission, its associated AP affiliated with the AP MLD can transmit to the STA: MSDUs / A-MSDUs for the set of TIDs mapped to the non-AP MLD; and MMPDUs that are not metering MMPDUs for the non-AP MLD or its affiliated STAs, unless the frames are transmitted to another STA affiliated with the same non-AP MLD and in active mode.

[0152] As mentioned above, in standard mapping mode, all TIDs are mapped to all configuration links for DL ​​and UL, and all configuration links are enabled. A non-AP MLD and an AP MLD that perform multi-link configuration must operate under this mode if a TID-to-link mapping negotiation for a different mapping has not occurred, has not been adequate, or has been disassembled.

[0153] In a multi-link (re)configuration procedure, a non-AP MLD can initiate a TID-to-link mapping negotiation by including a TID-to-link mapping element in a (re)association request frame if an AP MLD has indicated support for TID-to-link mapping negotiation.

[0154] After receiving the (re)association request frame containing the TID-to-link mapping element, the AP MLD can respond to the (re)association request frame according to the following rules. The AP MLD can accept the requested TID-to-link mapping indicated in the TID-to-link mapping element in the received (re)association request frame only if it accepts the (re)configuration of multiple links for all links where at least one TID is requested to be mapped. In this case, the Petition 870250101983, dated 07 / 11 / 2025, pages 208 / 288 37 / 70 MLD without AP includes in the (re)association response frame a TID-to-link mapping element. Otherwise, MLD without AP indicates the rejection of the proposed TID-to-link mapping by including in the (re)association response frame a TID-to-link mapping element that suggests a preferred TID-to-link mapping.

[0155] After a proper (re)configuration of multiple links, to negotiate a new TID-to-link mapping, an initiating MLD can send an individually addressed TID-to-link mapping request frame to a responding MLD that has indicated TID-to-link mapping negotiation support.

[0156] Upon receiving the individually addressed TID-to-link mapping request frame, the responding MLD sends an individually addressed TID-to-link mapping response frame to the initiating MLD according to the following rules. The responding MLD may accept the requested TID-to-link mapping indicated in the TID-to-link mapping element in the received TID-to-link mapping request frame by transmitting a TID-to-link mapping response frame. Otherwise, the responding MLD may indicate the rejection of the proposed TID-to-link mapping in the TID-to-link mapping response frame. The responding MLD may suggest a preferred TID-to-link mapping in the TID-to-link mapping response frame by including the TID-to-link mapping element in the TID-to-link mapping response frame.

[0157] An MLD can suggest a preferred TID-to-link mapping to a peer MLD by sending an unsolicited TID-to-link mapping response frame that includes a TID-to-link mapping element.

[0158] When a peer MLD indicates a preferred TID-to-link mapping, an MLD may take into account the preferred TID-to-link mapping when it initiates a new TID-to-link mapping. Furthermore, Petition 870250101983, dated 07 / 11 / 2025, pages 209 / 288 38 / 70 an AP MLD can take into account the traffic flow(s) affiliated with the non-AP MLD and the capabilities and restrictions (if any) of the non-AP MLD.

[0159] When two MLDs have negotiated a TID-to-link mapping, either MLD can dismantle the negotiated TID-to-link mapping by sending an individually addressed TID-to-link mapping dismantle frame. After dismantling, the MLDs operate in standard mapping mode.

[0160] When an MLD successfully negotiates a TID-to-link mapping with a peer MLD, both the MLD and the peer MLD update uplink and / or downlink TID-to-link mapping information according to the negotiated TID-to-link mapping.

[0161] When an MLD has correctly negotiated with a peer MLD a TID-to-link mapping of an uplink and / or downlink in which the bit position i of a link mapping field n in the TID-to-link mapping element is set to 0, a TID n should not be mapped to the link associated with link ID i in an uplink and / or downlink. When an MLD has correctly negotiated with a peer MLD a TID-to-link mapping of an uplink and / or downlink in which the bit position i of a link mapping field n in the TID-to-link mapping element is set to 1, the TID n is mapped to the link associated with link ID i in an uplink and / or downlink.

[0162] Figure 10 illustrates an example of a TID-to-link mapping in a multi-link communication environment. As shown, the multi-link communication environment includes an AP MLD with three affiliated APs and a non-AP MLD with three affiliated STAs.

[0163] During or after the configuration of multiple links, the non-AP MLD and the AP MLD can negotiate a TID-to-link mapping. The TID-to-link mapping maps TIDs on the non-AP MLD to UL and DL to configure links between the AP MLD and the non-AP MLD. For example, as shown in Figure 10, Petition 870250101983, dated 07 / 11 / 2025, pages 210 / 288 39 / 70 TID-to-link mapping can map TIDs 0 to 6 in both UL and DL to link 1, and TID 7 in both UL and DL to link 2. This enables links 1 and 2, and disables link 3. TID-to-link mapping negotiation can be performed by exchanging an association request / response frame or a TID-to-link mapping request / response frame between the non-AP MLD and the AP MLD.

[0164] Figure 11 illustrates an example Request to Send (RTS) / Authorization to Send (CTS) 1100 procedure. The example RTS / CTS 1100 procedure may be an example according to the RTS / CTS procedure as defined in section 10.3.2.9 of the IEEE 802.11 standard draft IEEE P802.11REVme™ / D2.1, January 2023. As shown in Figure 11, the example RTS / CTS 1100 procedure may include STAs 1102 and 1104. Other STAs of the same BSS may also be within the communication range of STAs 1102 and 1104.

[0165] In one example, STA 1102 may transmit an RTS 1106 frame to STA 1104. STA 1102 may transmit the RTS 1106 frame to protect against STA(s) obscuring the transmission of a data frame 1110 that STA 1102 intends to transmit. The RTS 1106 frame may include a duration / ID field. The duration / ID field may be set to the time, in microseconds, required to transmit the data frame 1110, plus a CTS frame, plus an ACK frame (if required), plus three SIFS (short frame spacing) periods.

[0166] In one example, STA 1104 can respond to RTS frame 1106 by transmitting a CTS frame 1108 to STA 1102. The CTS frame 1108 can be transmitted for one SIFS period after the RTS frame 1106. STA 1104 can respond to RTS frame 1106 when the RTS frame 1106 is addressed to STA 1104 and after considering the NAV, unless the NAV was set by a frame originating from STA 1102. STA 1104 can respond to RTS frame 1106 when the RTS frame 1106 is addressed to STA 1104 and if the NAV Petition 870250101983, dated 07 / 11 / 2025, pp. 211 / 288 40 / 70 indicate idle. For a non-S1G STA, the NAV indicates idle when the NAV count is 0 or when the NAV count is non-zero, but a non-bandwidth signaling TA obtained from a TA field of the RTS 1106 frame matches a saved TXOP holder address. For an S1G STA, the NAV indicates idle when the NAV and RID (Response Indication Delay) counters are 0 or when the NAV or RID counter is non-zero, but the TA field of the RTS 1106 frame matches the saved TXOP holder address.

[0167] STA 1104 can set an RA field of the CTS 1108 frame to a non-bandwidth signaling TA obtained from the TA field of the RTS 1106 frame.STA 1104 can define a CTS 1108 frame duration field based on the RTS 1106 frame duration / ID field, i.e., equal to the value of the RTS 1106 frame duration / ID field, adjusted by subtracting the time required to transmit the CTS 1108 frame and a SIFS period.

[0168] Upon receiving CTS frame 1108, STA 1102 may wait for a SIFS period before transmitting data frame 1110. STA 1104 may transmit an ACK frame 1112 in response to data frame 1110. STA 1104 may transmit a SIFS to ACK frame 1112 after receiving data frame 1110.

[0169] As shown in the RTS / CTS 1100 procedure, other STAs within the communication range of STAs 1102 and 1104, and belonging to the same BSS, can set their NAVs according to the RTS 1106 frame and / or the CTS 1108 frame. For example, an STA that receives an RTS 1106 frame can set its NAV based on the duration / frame ID field of RTS 1106. Another STA that receives a CTS 1008 frame can set its NAV based on the frame duration field of CTS 1108. In this way, the other STAs cannot access the channel using EDCA until the end of the transmission of ACK frame 1112. Similarly, STAs belonging to an overlapping BSS (OBSS) can set their NAVs according to RTS or CTS frames, if they are within the STA transmission communication band. Petition 870250101983, dated 07 / 11 / 2025, pages 212 / 288 41 / 70

[0170] Future IEEE 802.11 standards are expected to provide several mechanisms to support the quality of service (QoS) requirements of low-latency (LL) (or latency-sensitive) traffic. This traffic may originate from various real-time applications that have stringent latency requirements (e.g., very low average latency, a worst-case latency on the order of a few to tens of milliseconds, and / or a small jitter). In operation, LL traffic may be associated with one or more traffic identifiers (TIDs) associated with one or more predetermined ACs or traffic flows (hereinafter, TIDs associated with LL traffic are referred to as LL TIDs). The one or more predetermined ACs may comprise access categories for video (AC_VI) and voice (AC_VO), for example.

[0171] In addition to supporting the QoS requirements of low-latency traffic, future IEEE 802.11 radios (e.g., ultra-high reliability (UHR) 802.11 radios) are also expected to support reliable low-latency traffic communication. Reliability can be achieved by using the RTS / CTS procedure before transmitting low-latency data to protect the low-latency data transmission from interference. When STAs perform RTS / CTS exchange, other STAs within their communication range can listen to the RTS frame and / or the CTS frame and can set their NAVs based on the duration field of that frame. In a scenario where multiple links are available, a multi-link RTS / CTS exchange can be used.A STA within the communication range of the transmitting and / or receiving STA (e.g., the OBSS STA or another STA in the same BSS as the transmitting and receiving STAs) can define its NAV for all links through which the STA listens to RTS frames from the transmitting STA and CTS frames from the receiving STA. However, since the STA transmits the data frame through only one link, the STA may unnecessarily refrain from communicating through the other unused links. Figure 12 described below is a 1200 example illustrating an existing procedure that can be used to transmit low-latency data protected by an RTS / CTS exchange in a multi-link environment. Petition 870250101983, dated 07 / 11 / 2025, pp. 213 / 288 42 / 70

[0172] As shown in Figure 12, example 1200 includes STAs 1210, 1211, and 1212. STAs 1210, 1211, and 1212 may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links, for example, a first link and a second link. In one example, the first link may comprise one of the 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a future band to be defined. Similarly, the second link may comprise one of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or a future band to be defined, with the second link being different from the first link. For example, STA 1212 may be within the communication ranges of STA 1210 and STA 1211.

[0173] In example 1200, STA 1210 may have a low-latency data frame 1224 to transmit to STA 1211 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with LL TIDs. In one implementation, STA 1210 may associate a counter with the transmission completion time. The transmission completion time counter may start with the arrival at STA 1210 of the low-latency data being transmitted in low-latency data frame 1224. In another implementation, the transmission completion time counter may start with the start of an RTS / CTS procedure by STA 1210. In yet another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1224 by STA 1210.In one implementation, the successful transmission of a low-latency data frame may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may differ for different low-latency data frames. Petition 870250101983, dated 07 / 11 / 2025, pages 214 / 288 43 / 70

[0174] According to the existing procedure, to transmit the low-latency data frame 1224, STA 1210 can transmit an RTS frame 1220 to STA 1211 through a second link (e.g., link-2) and an RTS frame 1221 to STA 1211 through a first link (e.g., link-1). STA 1210 can initiate the transmissions of the RTS frames 1220 and 1221 simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS frames 1220 and 1221 may or may not be time-aligned. In one example, STA 1210 can start the transmission completion timer associated with the low-latency data frame 1224 upon transmission of the RTS frame 1220.Upon hearing the RTS 1220 frame via the second link and the RTS 1221 frame via the first link, STA 1212 can set its NAV for the first link and the second link based on the RTS 1221 and 1220 frames, respectively (based on the duration / ID fields of the RTS 1221 and 1220 frames).

[0175] In one example, STA 1211 can transmit a CTS 1222 frame to STA 1210 in response to the RTS 1220 frame via the second link, if its NAV indicates idle. STA 1211 can also respond to the RTS 1221 frame by transmitting a CTS 1223 frame to STA 1210 via the first link, if its NAV indicates idle. Upon hearing the CTS 1222 frame via the second link and the CTS 1223 frame via the first link, STA 1212 can update its NAV for the first link and the second link based on the CTS 1223 and 1222 frames, respectively (based on the duration fields of the CTS 1223 and 1222 frames). Normally, the duration / ID field of an RTS frame and the duration field of a responsive CTS frame are set to the same values; therefore, a STA that listens to a responsive CTS frame after listening to an RTS frame does not change the value of its NAV set when listening to the RTS frame.

[0176] After receiving the CTS 1222 frame via the second link (for example, STA 1210 receives the CTS 1222 frame via the second link before the CTS 1223 frame via the first link), STA 1210 can transmit the Petition 870250101983, dated 07 / 11 / 2025, pp. 215 / 288 44 / 70 low-latency data frame 1224 is sent to STA 1211 via the second link. STA 1211 can transmit an ACK frame 1225 to STA 1210 via the second link after receiving the low-latency data frame 1224. After transmitting the CTS frame 1223 via the first link, and based on not receiving data via the first link from STA 1210 within a certain time period following the transmission of the CTS frame 1223, STA 1211 may not take any action. Note that STA 1211 does not set its NAV based on the RTS frame 1221, given that the RTS frame 1221 is addressed to STA 1211.

[0177] STA 1212 may not communicate over the first or second link while data exchange between STA 1210 and STA 1211 is occurring. Specifically, although the first link is not used for any frame transmission, STA 1212 cannot reset its NAV to the first link and therefore cannot communicate over the first link. Thus, although the existing procedure may allow low-latency data to be delivered before the transmission completion time, many STAs may become unavailable on the first link, even though the first link is not being used.

[0178] The embodiments of the present disclosure, as further described below, address the problems described above of the existing procedure. In one aspect, the embodiments enable a transmit / receive STA (AP STA or non-AP STA) of a multi-link RTS / CTS exchange to inform neighboring STAs of a link through which the transmit / receive STA does not transmit / receive data after the multi-link RTS / CTS exchange. In one embodiment, the transmit / receive STA can transmit a CF endframe through the link through which the transmit / receive STA does not transmit / receive data after the multi-link RTS / CTS exchange. The CF endframe enables neighboring STAs to reset their NAVs for the link, freeing them to communicate through the link, while the transmit / receive STA transmits / receives data through another link. Petition 870250101983, dated 07 / 11 / 2025, pp. 216 / 288 45 / 70

[0179] Figure 13 is an example 1300 that illustrates a procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality. As shown in Figure 13, example 1300 also includes STAs 1210, 1211, and 1212 described above in Figure 12.

[0180] In example 1300, STA 1210 may have a low-latency data frame 1324 to transmit to STA 1211 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with LL TIDs. In one implementation, STA 1210 may associate a counter with the transmission completion time. The transmission completion time counter may start with the arrival at STA 1210 of the low-latency data being transmitted in low-latency data frame 1324. In another implementation, the transmission completion time counter may start with the start of an RTS / CTS procedure by STA 1210. In yet another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1324 by STA 1210.In one implementation, the successful transmission of a low-latency data frame may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may differ for different low-latency data frames.

[0181] In one embodiment, to transmit the low-latency data frame 1324, STA 1210 can transmit an RTS 1320 frame to STA 1211 through the second link and an RTS 1321 frame to STA 1211 through the first link. STA 1210 can initiate transmissions of the RTS 1320 and 1321 frames simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS 1320 and 1321 frames may or may not occur. Petition 870250101983, dated 07 / 11 / 2025, pp. 217 / 288 46 / 70 must be time-aligned. In one example, STA 1210 can start the transmission completion time counter associated with the low-latency data frame 1324 upon transmission of the RTS frame 1320. By listening to the RTS frame 1320 through the second link and the RTS frame 1321 through the first link, STA 1212 can set its NAV for the first link and the second link based on the RTS frames 1321 and 1320, respectively (based on the duration / ID fields of the RTS frames 1321 and 1320).

[0182] In one example, STA 1211 can transmit a CTS 1322 frame to STA 1210 in response to the RTS 1320 frame via the second link, if its NAV indicates idle. STA 1211 can also respond to the RTS 1321 frame by transmitting a CTS 1323 frame to STA 1210 via the first link, if its NAV indicates idle. Upon hearing the CTS 1322 frame via the second link and the CTS 1323 frame via the first link, STA 1212 can update its NAV for the first link and the second link based on the CTS 1323 and 1322 frames, respectively (based on the duration fields of the CTS 1323 and 1322 frames). Normally, the duration / ID field of an RTS frame and the duration field of a responsive CTS frame are set to the same values; therefore, a STA that listens to a responsive CTS frame after listening to an RTS frame does not change the value of its NAV set when listening to the RTS frame.

[0183] After receiving the CTS 1322 frame via the second link (for example, STA 1210 receives the CTS 1322 frame via the second link before the CTS 1323 frame via the first link), STA 1210 can transmit the low-latency data frame 1324 to STA 1211 via the second link. STA 1211 can transmit an ACK frame 1326 to STA 1210 via the second link after receiving the data frame 1324.

[0184] In addition to transmitting data frame 1324 over the second link, STA 1210 can transmit a contention-free end frame (CF end) 1325 over the first link. STA 1210 can transmit the CF end frame 1325 before, simultaneously with, or after the transmission of the Petition 870250101983, dated 07 / 11 / 2025, pp. 218 / 288 47 / 70 data frame 1324. STA 1210 may be allowed to transmit the CF endpoint frame 1325 as the TXOP initiator through the first link. The CF endpoint frame 1325 enables an STA within the communication range of STA 1210 to reset its NAV to the first link. The STA can therefore become available for communication through the first link. For example, in the listening CF endpoint frame 1325 through the first link, STA 1212 can reset its NAV to the first link (which was set based on the RTS frame 1321 and updated based on the CTS frame 1323) and can become available for communication through the first link.Thus, the procedure in Figure 13 allows low-latency data to be delivered before the transmission completion time and, additionally, it can enable the STA within the communication range of STA 1210 to communicate through the first link while the data exchange between STA 1210 and 1211 occurs through the second link. However, as described further below in relation to Figure 14, the STA outside the communication range of STA 1210, but within the communication range of STA 1211, may still be prevented from communicating through the first link.

[0185] Figure 14 is another 1400 example that illustrates the procedure in Figure 13. As shown in Figure 14, the 1400 example includes STAs 1210 and 1211 described above and a STA 1412. STA 1412 may belong to a different BSS than STAs 1210 and 1211. STA 1412 may comprise an AP MLD or a non-AP MLD capable of communicating through multiple links, for example, a first link and a second link. In one example, the first link may comprise a 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a future band to be defined. Similarly, the second link may comprise one of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or a future band to be defined, with the second link being different from the first link. In example 1400, STA 1412 may be within the communication range of STA 1211, but outside the communication range of STA 1210. Petition 870250101983, dated 07 / 11 / 2025, pages 219 / 288 48 / 70

[0186] In example 1400, STA 1210 may have a low-latency data frame 1424 to transmit to STA 1211 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with LL TIDs. In one implementation, STA 1210 may associate a counter with the transmission completion time. The transmission completion time counter may start with the arrival at STA 1210 of the low-latency data being transmitted in low-latency data frame 1424. In another implementation, the transmission completion time counter may start with the start of an RTS / CTS procedure by STA 1210. In yet another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1424 by STA 1210.In one implementation, the successful transmission of a low-latency data frame may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may differ for different low-latency data frames.

[0187] In one embodiment, to transmit the low-latency data frame 1424, STA 1210 can transmit an RTS 1420 frame to STA 1211 through the second link and an RTS 1421 frame to STA 1211 through the first link. STA 1210 can initiate transmissions of the RTS 1420 and 1421 frames simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS 1420 and 1421 frames may or may not be time-aligned. In one example, STA 1210 might start the transmission completion time counter associated with low-latency data frame 1424 upon transmission of RTS frame 1420. Because it is outside the communication range of STA 1210, STA 1412 might not hear RTS frame 1420 through it. Petition 870250101983, dated 07 / 11 / 2025, pp. 220 / 288 49 / 70 from the second link and the RTS 1421 frame through the first link, and therefore may not set its NAV for the first link and the second link.

[0188] In one example, STA 1211 can transmit a CTS 1422 frame to STA 1210 in response to the RTS 1420 frame via the second link, if its NAV indicates idle. STA 1211 can also respond to the RTS 1421 frame by transmitting a CTS 1423 frame to STA 1210 via the first link, if its NAV indicates idle. Upon hearing the CTS 1422 frame via the second link and the CTS 1423 frame via the first link, STA 1412 can set its NAV to the first link and the second link based on the CTS 1423 and 1422 frames, respectively (based on the duration fields of the CTS 1423 and 1422 frames).

[0189] After receiving the CTS frame 1422 through the second link (for example, STA 1210 receives the CTS frame 1422 through the second link before the CTS frame 1423 through the first link), STA 1210 can transmit data frame 1424 to STA 1211 through the second link. STA 1211 can transmit an ACK frame 1426 to STA 1210 through the second link after receiving data frame 1424.

[0190] In addition to transmitting data frame 1424 over the second link, STA 1210 may transmit an endframe CF 1425 over the first link. STA 1210 may transmit the endframe CF 1425 before, simultaneously with, or after the transmission of data frame 1424. STA 1210 may be permitted to transmit the endframe CF 1425 as the TXOP initiator over the first link. The endframe CF 1425 enables an STA within the communication range of STA 1210 to reset its NAV to the first link. However, in example 1400, being outside the communication range of STA 1210, STA 1412 may not hear the end frame CF 1425 through the first link and may thus maintain its NAV for the first link (defined based on the CTS 1423 frame). Therefore, although the first link is not used for any data frame transmission between STA 1210 and STA 1412, Petition 870250101983, dated 07 / 11 / 2025, pp. 221 / 288 50 / 70 1211, STA 1412 may not be allowed to use the first link for communication while data exchange between STA 1210 and STA 1211 occurs via the second link.

[0191] Figure 15 illustrates an example 1500 of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality. As shown in Figure 15, example 1500 includes STAs 1510, 1511, and 1512. STA 1512 may belong to a different BSS than STAs 1510 and 1511. STAs 1510, 1511, and 1512 may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links, for example, a first link and a second link. In one example, the first link may comprise a 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a future band to be defined. Similarly, the second link may comprise one of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or a future band to be defined, with the second link being different from the first link.In example 1500, STA 1512 may be within the communication range of STA 1511, but outside the communication range of STA 1510.

[0192] In example 1500, STA 1510 may have a low-latency data frame 1524 to transmit to STA 1511 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with LL TIDs. In one implementation, STA 1510 may associate a counter with the transmission completion time. The transmission completion time counter may start with the arrival at STA 1510 of the low-latency data being transmitted in low-latency data frame 1524. In another implementation, the transmission completion time counter may start with the start of an RTS / CTS procedure by STA 1510. In yet another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1524 by STA 1510. In one implementation, the successful transmission of a Petition 870250101983, dated 07 / 11 / 2025, pages 222 / 288 51 / 70 low-latency data frames may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may differ for different low-latency data frames.

[0193] In one embodiment, to transmit the low-latency data frame 1524, STA 1510 can transmit an RTS 1520 frame to STA 1511 through the second link and an RTS 1521 frame to STA 1511 through the first link. STA 1510 can initiate transmissions of the RTS 1520 and 1521 frames simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS 1520 and 1521 frames may or may not be time-aligned. In one instance, the RTS 1521 frame may overlap the RTS 1520 frame. In another instance, STA 1510 can initiate the transmission completion time counter associated with the low-latency data frame 1524 during the transmission of the RTS 1520 frame.Because it is outside the communication range of STA 1510, STA 1512 may not hear the RTS 1520 frame through the second link and the RTS 1521 frame through the first link, and therefore may not set its NAV to the first and second links. In one embodiment, the RTS 1520 and 1521 frames may comprise multi-user request-to-send (MU-RTS) trigger frames. In one example, the first MU-RTS trigger frame or the second MU-RTS trigger frame may comprise an indication to transmit the data through a single link between the first and second links.

[0194] In one example, STA 1511 can transmit a CTS 1522 frame to STA 1510 in response to the RTS 1520 frame via the second link, if its NAV indicates idle. STA 1511 can also respond to the RTS 1521 frame by transmitting a CTS 1523 frame to STA 1510 via the first link, if its NAV indicates idle. When listening to the CTS 1522 frame via the second link Petition 870250101983, dated 07 / 11 / 2025, pp. 223 / 288 52 / 70 and the CTS 1523 frame through the first link, STA 1512 can set its NAV for the first link and the second link based on the CTS 1523 and 1522 frames, respectively (based on the duration fields of the CTS 1523 and 1522 frames).

[0195] After receiving the CTS 1522 frame via the second link (for example, STA 1510 receives the CTS 1522 frame via the second link before the CTS 1523 frame via the first link), STA 1510 can transmit data frame 1524 to STA 1511 via the second link. STA 1511 can transmit an ACK frame 1526 to STA 1510 via the second link after receiving data frame 1524 on the second link.

[0196] In one embodiment, based on STA 1511 not receiving data through the first link within a time period from the transmission of CTS frame 1523, STA 1511 may transmit an end frame CF 1525 on the first link. STA 1512 being within the communication range of STA 1511 may reset its NAV to the first link (and become available for communication through the first link) upon hearing the end frame CF 1525. In one embodiment, the time period may be longer than a SIFS. In one mode, STA 1512 can transmit a frame via the first link to another STA (not shown in Figure 15) within a duration indicated in CTS frame 1523. In another mode, STA 1512 can receive a frame from another STA (not shown in Figure 15) via the first link within the duration indicated in CTS frame 1523.

[0197] Thus, using the procedure in Figure 15, STAs that are within the communication range of the receiving STA, but outside the communication range of the transmitting STA, can be released to communicate through the link that is not used for data exchange after the exchange of RTS / CTS from multiple links. Note that STAs that are within the communication range of the transmitting STA, but outside the communication range of the receiving STA, can also be authorized to communicate through the unused link. Such Petition 870250101983, dated 07 / 11 / 2025, pages 224 / 288 53 / 70 STAs redefine their NAVs for the unused link (defined based on receiving an RTS frame through the unused link) when they do not hear a corresponding CTS frame through the unused link. An advantage of the procedure illustrated in Figure 15 is the low overhead of the overall procedure, where the receiving STA (TXOP responder) can decide to transmit a CF end structure without receiving a trigger structure or a transmit flag (TX flag) from a transmitting STA (TXOP support).

[0198] Figure 16 illustrates a 1600 example of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality. As shown in Figure 16, the 1600 example includes STAs 1610, 1611, and 1612. STA 1612 may belong to a different BSS than STAs 1610 and 1611. STAs 1610, 1611, and 1612 may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links, for example, a first link and a second link. In one example, the first link may comprise a 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a future band to be defined. Similarly, the second link may comprise one of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or a future band to be defined, with the second link being different from the first link.In example 1600, STA 1612 may be within the communication range of STA 1611, but outside the communication range of STA 1610.

[0199] In example 1600, STA 1610 may have a low-latency data frame 1624 to transmit to STA 1611 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with TIDs LL. In one implementation, STA 1610 may associate a counter with the transmission completion time. The transmission completion time counter may start upon the arrival at STA 1610 of the low-latency data being transmitted in the data frame of Petition 870250101983, dated 07 / 11 / 2025, pp. 225 / 288 54 / 70 low latency 1624. In another implementation, the transmission completion time counter may start with the beginning of an RTS / CTS procedure by STA 1610. In another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1624 by STA 1610. In one implementation, the successful transmission of a low-latency data frame may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may be different for different low-latency data frames.

[0200] In one embodiment, to transmit the low-latency data frame 1624, STA 1610 can transmit an RTS 1620 frame to STA 1611 through the second link and an RTS 1621 frame to STA 1611 through the first link. STA 1610 can initiate transmissions of the RTS 1620 and 1621 frames simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS 1620 and 1621 frames may or may not be time-aligned. In one instance, the RTS 1621 frame may overlap the RTS 1620 frame. In another instance, STA 1610 can initiate the transmission completion time counter associated with the low-latency data frame 1624 during the transmission of the RTS 1620 frame.Because it is outside the communication range of STA 1610, STA 1612 may not hear the RTS 1620 frame through the second link and the RTS 1621 frame through the first link, and therefore may not set its NAV to the first and second links.

[0201] In one example, STA 1611 can transmit a CTS 1622 frame to STA 1610 in response to the RTS 1620 frame via the second link, if its NAV indicates idle. STA 1611 can also respond to the RTS 1621 frame by transmitting a CTS 1623 frame to STA 1610 via the first link, if its NAV indicates idle. When listening to the CTS 1622 frame via the second link Petition 870250101983, dated 07 / 11 / 2025, pp. 226 / 288 55 / 70 and the CTS 1623 frame through the first link, another STA 1612 can set its NAV to the first link and the second link based on the CTS 1623 and 1622 frames, respectively (based on the duration fields of the CTS 1623 and 1622 frames).

[0202] After receiving the CTS 1622 frame via the second link (for example, STA 1610 receives the CTS 1622 frame via the second link before the CTS 1623 frame via the first link), STA 1610 can transmit data frame 1624 to STA 1611 via the second link. STA 1611 can transmit an ACK frame 1627 to STA 1610 via the second link after receiving data frame 1624 on the second link.

[0203] In one embodiment, based on STA 1610 transmitting data frame 1624 to STA 1611 via the second link, STA 1610 may transmit to STA 1611 a frame 1625 via the first link indicating the transmission of data via the second link to STA 1611. In one embodiment, the first frame 1625 may be a first trigger frame. In one embodiment, the trigger frame may indicate to STA 1611 not to transmit data via the first link. In one embodiment, the trigger frame may comprise an indication for STA 1611 to transmit an end-frame CF via the first link. In one embodiment, the indication to transmit the end-frame CF via the first link may be provided in a user information field or a common information field of the trigger frame.

[0204] Based on STA 1611 receiving frame 1610 from STA 1625 indicating the transmission of data through the second link to STA 1611, STA 1611 can transmit an end frame CF 1626 through the first link. STA 1612, being within the communication range of STA 1611, can reset its NAV to the first link (and can thus become available for communication) upon hearing the end frame CF 1626. In one mode, STA 1612 can transmit through the first link a frame to another STA (not shown in Figure 16) within a duration indicated in frame CTS 1623. In another Petition 870250101983, dated 07 / 11 / 2025, pp. 227 / 288 In mode 56 / 70, STA 1612 can receive a frame from another STA (not shown in Figure 16) via the first link within the duration indicated in CTS frame 1623.

[0205] Thus, using the procedure in Figure 16, STAs that are within the communication range of the receiving STA, but outside the communication range of the transmitting STA, can be allowed to communicate via the link that is not used for data exchange after the exchange of RTS / CTS from multiple links. Note that STAs that are within the communication range of the transmitting STA, but outside the communication range of the receiving STA, can also be allowed to communicate via the unused link. Such STAs reset their NAVs to the unused link (defined based on receiving an RTS frame via the unused link) when they do not hear a corresponding CTS frame via the unused link.When compared to Figure 15, an advantage of the procedure illustrated in Figure 16 is that the receiving STA (TXOP responder) transmits a CF end structure only if triggered by the transmitting STA (TXOP support). Thus, reliability can be increased as the transmitting STA informs the receiving STA of the unused link.

[0206] Figure 17 illustrates an example 1700 of another procedure that can be used to transmit low-latency data protected by a multi-link RTS / CTS exchange according to a modality. As shown in Figure 17, example 1700 includes STAs 1710, 1711, and 1712. STA 1712 may belong to a different BSS than STAs 1710 and 1711. STAs 1710, 1711, and 1712 may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links, for example, a first link and a second link. In one example, the first link may comprise a 2.4 GHz band, a 5 GHz band, a 6 GHz band, or a future band to be defined. Similarly, the second link may comprise one of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or a future band to be defined, with the second link being different from the first link. In example 1700, STA 1712 may be Petition 870250101983, dated 07 / 11 / 2025, pages 228 / 288 57 / 70 within the communication range of STA 1711, but outside the communication range of STA 1710.

[0207] In example 1700, STA 1710 may have a low-latency data frame 1724 to transmit to STA 1711 within a transmission completion time. A low-latency data frame may be a data frame comprising one or more MPDUs with LL TIDs. In one implementation, STA 1710 may associate a counter with the transmission completion time. The transmission completion time counter may start with the arrival at STA 1710 of the low-latency data being transmitted in low-latency data frame 1724. In another implementation, the transmission completion time counter may start with the start of an RTS / CTS procedure by STA 1710. In yet another implementation, the transmission completion time counter may start with the transmission of low-latency data frame 1724 by STA 1710.In one implementation, the successful transmission of a low-latency data frame may require acknowledgment of the low-latency data frame by the destination STA before the transmission completion time counter expires. In one implementation, transmission completion time may refer to the amount of time required for the low-latency data frame to be delivered to the destination STA. The transmission completion time may differ for different low-latency data frames.

[0208] In one embodiment, to transmit the low-latency data frame 1724, STA 1710 can transmit an RTS 1720 frame to STA 1711 through the second link and an RTS 1721 frame to STA 1711 through the first link. STA 1710 can initiate transmissions of the RTS 1720 and 1721 frames simultaneously. Due to random withdrawals through the first and second links, the transmissions of the RTS 1720 and 1721 frames may or may not be time-aligned. In one instance, the RTS 1721 frame may overlap the RTS 1720 frame. In another instance, STA 1710 can initiate the transmission completion time counter associated with the low-latency data frame. Petition 870250101983, dated 07 / 11 / 2025, pp. 229 / 288 58 / 70 1724 in the transmission of the RTS 1720 frame. Due to being outside the communication range of STA 1710, STA 1712 may not hear the RTS 1720 frame through the second link and the RTS 1721 frame through the first link, and therefore may not set its NAV to the first and second links.

[0209] In one example, STA 1711 can transmit a CTS 1722 frame to STA 1710 in response to the RTS 1720 frame via the second link, if its NAV indicates idle. STA 1711 can also respond to the RTS 1721 frame by transmitting a CTS 1723 frame to STA 1710 via the first link, if its NAV indicates idle. Upon hearing the CTS 1722 frame via the second link and the CTS 1723 frame via the first link, another STA 1712 can set its NAV to the first link and the second link based on the CTS 1723 and 1722 frames, respectively (based on the duration fields of the CTS 1723 and 1722 frames).

[0210] After receiving the CTS 1722 frame via the second link (for example, STA 1710 receives the CTS 1722 frame via the second link before the CTS 1723 frame via the first link), STA 1710 can transmit data frame 1724 to STA 1711 via the second link. STA 1711 can transmit an ACK frame 1726 to STA 1710 via the second link after receiving data frame 1724 on the second link.

[0211] In one embodiment, based on STA 1710 transmitting data frame 1724 to STA 1711 via the second link, STA 1710 may transmit to STA 1711 a frame indicating the transmission of data via the second link to STA 1711. In another embodiment, the frame may indicate the non-transmission of data via the first link. In one embodiment, the frame may comprise a data frame containing the data. For example, as shown in Figure 17, the frame may be data frame 1724. In another embodiment, the frame may be separate from data frame 1724. In one embodiment, the frame may comprise an indication of the first link, wherein the indication of the first link may indicate the non-transmission of data. Petition 870250101983, dated 07 / 11 / 2025, pp. 230 / 288 59 / 70 via the first link to STA 1711. In one embodiment, the indication may be a transmit flag. In another embodiment, the first link indication may be provided in a universal signal field (U-SIG) of a frame PHY header, wherein the U-SIG field additionally comprises a link identifier of the first link. In another embodiment, the first link indication may be provided in an aggregate control field (control A) of the frame, wherein the control A field is provided in a high-throughput (HT) control field of the frame.

[0212] Based on STA 1711 receiving frame 1710 from STA 1724 indicating the transmission of data through the second link to STA 1711, STA 1711 can transmit an end frame CF 1725 through the first link. STA 1712, being within the communication range of STA 1711, can reset its NAV to the first link (and become available for further communication) upon hearing end frame CF 1725. In one mode, STA 1712 can transmit through the first link a frame to another STA (not shown in Figure 17) within a duration indicated in CTS frame 1723. In another mode, STA 1712 can receive through the first link a frame from another STA (not shown in Figure 17) within the duration indicated in CTS frame 1723.

[0213] Thus, using the procedure in Figure 17, STAs that are within the communication range of the receiving STA, but outside the communication range of the transmitting STA, can be allowed to communicate through the link that is not used for data exchange after the exchange of RTS / CTS frames from multiple links. Note that STAs that are within the communication range of the transmitting STA, but outside the communication range of the receiving STA, can also be authorized to communicate through the unused link. Such STAs reset their NAVs to the unused link (defined based on receiving an RTS frame through the unused link) when they do not hear a corresponding CTS frame through the unused link. Another advantage of the procedure illustrated in Figure 17 is that it does not require signaling through a Petition 870250101983, dated 07 / 11 / 2025, pp. 231 / 288 A separate 60 / 70 structure is used to trigger the receiving STA to transmit a CF end structure. Instead, the signaling is combined with the data frame, resulting in reduced signaling overhead.

[0214] Figure 18 illustrates an example 1800 common information field of a basic multi-link element according to a modality. The basic multi-link element can be transmitted by one STA to another STA to inform the other STA of its capabilities. As shown in Figure 18, the 1800 common information field can include a common information length subfield, an MLD MAC address subfield, a link ID information subfield, a BSS parameter change count subfield, a synchronization average delay information subfield, an EML capabilities subfield, an MLD capabilities and operations subfield, an MLD AP ID subfield, and an extended MLD capabilities and operations subfield.

[0215] In one embodiment, a reserved bit of the MLD capabilities and operations subfield can be used to signal an operating mode for data transmission comprising low-latency traffic protected by a multi-link RTS / CTS exchange and through a single link (see Figures 15 to 17). In one embodiment, by setting the reserved bit to one, an STA can inform another STA of its ability to transmit data comprising low-latency traffic using a multi-link RTS / CTS exchange followed by transmission of the data through a single link. Conversely, by setting the reserved bit to one, the STA can inform the other STA of its ability to receive data comprising low-latency traffic through a single link, preceded by a multi-link RTS / CTS exchange, and transmit an end-frame CF through the unused link as described in the embodiments of Figures 15, 16, and 17 above.

[0216] Figure 19 illustrates an example 1900 trigger frame that can be used in the modalities. As shown in Figure 19, the trigger frame of Petition 870250101983, dated 07 / 11 / 2025, pages 232 / 288 Example 61 / 70 1900 may include a frame control subfield, a duration subfield, a receiver address (RA) subfield, a transmitter address (TA) subfield, a common information subfield, a user information list subfield, a completion subfield, and an FCS subfield.

[0217] In one example, a trigger type field subfield of the common information subfield may indicate that trigger frame 1900 is a variant of MU-RTS trigger frame. In one embodiment, as a variant of MU-RTS trigger frame, trigger frame 1900 may be an embodiment of frames 1520 and / or 1521 described above when frames 1520 and / or 1521 are MU-RTS frames. In one embodiment, trigger frame 1900 may comprise an indication of data transmission over a single link between a first link and a second link. In one example, the indication of data transmission over a single link can be transmitted in one or more of the reserved bits of the common information subfield of the 1900 trigger frame. In another example, the indication of data transmission over a single link can be transmitted in one or more of the reserved bits of the user information subfield of the 1900 trigger frame.In one embodiment, when a transmitting STA sets the bit carrying the data transmission indication over a single link to one, the receiving STA can expect to receive low-latency data over a single link, despite an RTS / CTS exchange over multiple links. In another embodiment, based on the indication being set to one, the receiving STA can transmit an end-CF frame over the link where the receiving STA does not receive data after a period of time from the transmission of a CTS frame on that link (see Figure 15).

[0218] In another example, the 1900 trigger frame may be an embodiment of the 1625 trigger frame described above. In one embodiment, the 1900 trigger frame may comprise an indication for a receiving STA to transmit a CF end frame over a first link (CF end indication). In one embodiment, setting the CF end indication bit to one, Petition 870250101983, dated 07 / 11 / 2025, pp. 233 / 288 62 / 70 The transmitting STA indicates to the receiving STA that the receiving STA should transmit a CF end frame over the link on which the receiving STA receives the 1900 trigger frame from the transmitting STA (see Figure 16). Otherwise, by setting the CF end indication bit to zero, the transmitting STA can indicate to the receiving STA that the receiving STA should use legacy behavior. In one embodiment, the CF end indication can be provided in a user information field or a common information field of the trigger frame. In another embodiment, the CF end indication can be transmitted in one of the reserved bits (i.e., bits 20 to 38) of the user information field. In another embodiment, the CF end indication can be transmitted in one of the reserved bits (i.e., bits 22, 26, 53, or 63) of the common information field.In another embodiment, the subfield of the user information list may indicate the link through which the CF endpoint frame should be transmitted.

[0219] Figure 20 illustrates an example universal signal field (U-SIG) 2000 that can be used in the modes. As shown in Figure 20, the U-SIG 2000 field contains version-independent and version-dependent subfields. The version-independent subfields are located from bit B0 to B19, while the version-dependent subfields are located from bits B20 to B51.

[0220] Version-independent subfields are subfields that are consistent in location and interpretation across multiple IEEE 802.11 PHY layers. The purpose of version-independent subfields is to achieve better coexistence between IEEE 802.11 PHYs defined for the 2.4, 5, and 6 GHz spectrums from the extremely high throughout (EHT) PHY specification. The value of this subfield is used to identify the exact PHY version of the EHT PPDU. Other version-independent subfields include a bandwidth (BW) subfield, which indicates the PPDU bandwidth, and an uplink / downlink (UL / DL) subfield, which indicates whether the PPDU is an uplink or downlink PPDU. Petition 870250101983, dated 07 / 11 / 2025, pp. 234 / 288 63 / 70 is a BSS color subfield, which indicates the BSS color of the PPDU, and a TXOP subfield, which indicates the duration of a TXOP during which the PPDU is transmitted.

[0221] In one embodiment, a U-SIG field, such as the U-SIG 2000 field, may be provided in the PHY header of a frame to provide an indication of a link that is not used for data transmission. For example, as described earlier in relation to Figure 17, in one embodiment, frame 1724 may comprise an indication of the first link, wherein the indication of the first link may indicate to STA 1711 that data is not being transmitted through the first link to STA 1711. In one embodiment, the indication of the first link may comprise a transmit flag. In one embodiment, frame 1724 may include a U-SIG field, such as the U-SIG 2000 field, in its PHY header. In one embodiment, the indication of the first link may be provided in any of the version-dependent subfields of the U-SIG 2000 field.In one embodiment, the U-SIG 2000 field may additionally comprise a link identifier from the first link in version-dependent subfields.

[0222] In another embodiment, the indication of the first link may be provided in an aggregate control field (control A) of the frame, wherein the control field A is provided in a high-throughput (HT) control field of the frame, as illustrated previously in Figure 4. In one embodiment, the control field A may additionally comprise a link identifier of the first link.

[0223] Figure 21 illustrates an example 2100 process according to one embodiment. The example 2100 process is provided for illustrative purposes only and is not limiting. The example 2100 process can be executed by a first STA, such as STA 1511, for example. The first STA may have multi-link capability (e.g., comprising a multi-link device (MLD)). The first STA may be an AP STA or a non-AP STA. The first STA may be a receiving STA that receives a data transmission from a second STA. The second STA may also comprise an MLD. Petition 870250101983, dated 07 / 11 / 2025, pp. 235 / 288 64 / 70 The first STA and the second STA can communicate through at least one first link and one second link.

[0224] As shown in Figure 21, process 2100 may include, in step 2110, receiving by the first STA from the second STA via a first link, a first RTS frame requesting data transmission, via the first link, to the first STA; and via a second link, a second RTS frame requesting data transmission, via the second link, to the first STA. In one embodiment, the first STA and the second STA may each comprise an AP MLD or a non-AP MLD capable of communicating across multiple links. In one embodiment, the data may comprise low-latency traffic. In one embodiment, the second RTS frame may overlap the first RTS frame.In another embodiment, the first and second RTS frames may comprise MU-RTS trigger frames, wherein the first MU-RTS trigger frame or the second MU-RTS trigger frame may comprise an indication to transmit the data over a single link between the first link and the second link.

[0225] In step 2120, process 2100 may include transmitting, by the first STA to the second STA via the first link, a first CTS frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame.

[0226] In step 2130, process 2100 may include transmitting, by the first STA, a CF end frame on the first link based on the first STA not receiving the data through the first link within a time period from the transmission of the first CTS frame. In one embodiment, the time period may be longer than a SIFS.

[0227] In one embodiment, process 2100 may additionally comprise receiving, by the first STA from the second STA, the data through the second link in response to the second CTS frame. In response, process 2100 may Petition 870250101983, dated 07 / 11 / 2025, pp. 236 / 288 65 / 70 additionally involves transmitting, from the first STA to the second STA, an acknowledgment frame (ACK) through the second link.

[0228] In one embodiment, process 2100 may additionally comprise, when the first STA does not receive the data through the first link within the time period from the transmission of the first CTS frame, transmitting, by the first STA, an end CF frame through the first link.

[0229] Figure 22 illustrates another example 2200 process according to an embodiment. The example 2200 process is provided for illustrative purposes only and is not exhaustive. The example 2200 process can be executed by a first STA, such as STA 1511, for example. The first STA may have multi-link capability (i.e., comprising a multi-link device (MLD)). The first STA may be an AP STA or a non-AP STA. The first STA may be a receiving STA that receives a data transmission from a second STA. The second STA may also comprise an MLD. The first STA and the second STA may communicate through at least one first link and one second link.

[0230] As shown in Figure 22, process 2200 may include, in step 2210, receiving by the first STA from the second STA via a first link, a first RTS frame requesting data transmission, via the first link, to the first STA; and via a second link, a second RTS frame requesting data transmission, via the second link, to the first STA. In one embodiment, the first STA and the second STA may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links. In one embodiment, the data may comprise low-latency traffic. In one embodiment, the second RTS frame may overlap the first RTS frame.

[0231] In step 2220, process 2200 may include transmitting, by the first STA to the second STA via the first link, a first CTS frame in Petition 870250101983, dated 07 / 11 / 2025, pages 237 / 288 66 / 70 response to the first RTS frame; and through the second link, a second CTS frame in response to the second RTS frame.

[0232] In step 2230, process 2200 may include the transmission by the first STA of an end-frame CF through the first link based on the first STA receiving from the second STA a frame indicating the transmission of data through the second link to the first STA. In another embodiment, the frame may indicate the non-transmission of data through the first link.

[0233] In one embodiment, the frame may comprise a trigger frame. In one embodiment, process 2200 may further comprise receiving the trigger frame through the first link. In one embodiment, the frame may comprise an indication to transmit the CF endpoint frame through the first link, wherein the indication to transmit the CF endpoint frame through the first link may be provided in a user information field or a common information field of the trigger frame.

[0234] In another embodiment, the frame may comprise a data frame comprising the data. In one embodiment, process 2200 may additionally comprise receiving the data frame through the second link. In one embodiment, the frame may comprise an indication of the first link, wherein the indication of the first link may indicate the non-transmission of data through the first link to the first STA. In one example, the indication of the first link may be provided in a U-SIG field of a frame PHY header, wherein the U-SIG field may further comprise a link identifier of the first link. In another example, the indication of the first link may be provided in a frame A control field, wherein the A control field may be provided in a frame HT control field.

[0235] Figure 23 illustrates another example process 2300 according to an embodiment. The example process 2300 is provided for illustrative purposes only and is not limiting. The example process 2300 can be executed by a first STA, such as STA 1510, for example. The first STA can have a Petition 870250101983, dated 07 / 11 / 2025, pp. 238 / 288 67 / 70 multi-link capability (i.e., comprising a multi-link device (MLD)). The first STA can be an AP STA or a non-AP STA. The first STA can be a transmit STA that has data to transmit to a second STA. The second STA can also comprise an MLD. The first STA and the second STA can communicate through at least one first link and one second link.

[0236] As shown in Figure 23, process 2300 may include, in step 2310, transmitting from the first STA to the second STA via a first link, a first RTS frame requesting data transmission, via the first link, to the second STA; and via a second link, a second RTS frame requesting data transmission, via the second link, to the second STA. In one embodiment, the first STA and the second STA may each comprise an AP MLD or a non-AP MLD capable of communicating over multiple links. In one embodiment, the data may comprise low-latency traffic. In one embodiment, the second RTS frame may overlap the first RTS frame.

[0237] In step 2320, process 2300 may include receiving, by the first STA from the second STA via the first link, a first CTS frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame.

[0238] In step 2330, process 2300 may include transmitting, by the first STA to the second STA, a frame indicating the transmission of data through the second link to the second STA based on the first STA transmitting the data to the second STA through the second link. In one embodiment, the frame may indicate the non-transmission of data through the first link.

[0239] In one embodiment, the frame may comprise a trigger frame. In one embodiment, process 2300 may additionally comprise transmitting the trigger frame through the first link. In one embodiment, the frame may comprise an indication to transmit the CF endpoint frame through the Petition 870250101983, dated 07 / 11 / 2025, pp. 239 / 288 68 / 70 first link, where the indication to transmit the CF endpoint frame through the first link can be provided in a user information field or a common information field of the trigger frame.

[0240] In another embodiment, the frame may comprise a data frame comprising the data. In one embodiment, process 2300 may additionally comprise transmitting the data frame through the second link. In one embodiment, the frame may comprise an indication of the first link, wherein the indication of the first link may indicate the non-transmission of data through the first link to the first STA. In one example, the indication of the first link may be provided in a U-SIG field of a frame PHY header, wherein the U-SIG field may further comprise a link identifier of the first link. In another example, the indication of the first link may be provided in a frame A control field, wherein the A control field may be provided in a frame HT control field.

[0241] Figure 24 illustrates another example 2400 process according to one embodiment. The example 2400 process is provided for illustrative purposes only and is not exhaustive. The example 2400 process can be executed by a first STA, such as STA 1512, for example. The first STA can have multi-link capability (i.e., comprising a multi-link device (MLD)). The first STA can be an AP STA or a non-AP STA. The first STA can be a receiving STA that receives a data transmission from a second STA. The second STA can also comprise an MLD. The first STA and the second STA can communicate through at least one first link and one second link. Furthermore, the first STA can be a transmitting STA that has data to transmit to a third STA, or it can be a receiving STA that receives a data transmission from the third STA. The third STA can also comprise an MLD.The first STA and the third STA can communicate through at least one first link and one second link. Petition 870250101983, dated 07 / 11 / 2025, pp. 240 / 288 69 / 70

[0242] As shown in Figure 24, process 2400 may include, in step 2410, receiving by the first STA from the second STA via a first link, a first CTS frame; and via a second link, a second CTS frame. In one embodiment, the first STA and the second STA may each comprise an AP MLD or a non-AP MLD capable of communicating across multiple links. In one embodiment, the second CTS frame may overlap the first CTS frame.

[0243] In step 2420, process 2400 may include setting up a first NAV for the first link based on the first CTS frame and a second NAV for the second link based on the second CTS frame. In step 2430, process 2400 may include resetting the first NAV for the first link based on receiving, from the second STA, a CF end frame through the first link.

[0244] In one embodiment, process 2400 may additionally comprise transmitting, via the first STA to the third STA and through the first link, a frame for a duration specified in the first CTS frame. In another embodiment, process 2400 may additionally comprise receiving, via the first STA from the third STA and through the first link, a frame for a duration specified in the first CTS frame.

[0245] Although example modalities are described above in relation to operation in a multi-link environment, the modalities can be readily extended to a single-link structure, as would be understood by a person skilled in the art based on the teachings provided here, as in Figure 25 below.

[0246] Figure 25 illustrates another example process 2500 according to an embodiment. The example process 2500 is provided for illustrative purposes only and is not limiting. The process 2500 can be executed by a first STA. The first STA can be an AP STA or a non-AP STA. The first STA can be a receiving STA that can receive a data transmission from Petition 870250101983, dated 07 / 11 / 2025, pages 241 / 288 70 / 70 a second STA. The first STA and the second STA can communicate through a single link.

[0247] As shown in Figure 25, process 2500 may include, in step 2510, receiving by the first STA from the second STA, a first RTS frame requesting data transmission to the first STA. In one embodiment, the data may comprise low-latency traffic. In one embodiment, the first RTS frame may comprise an MU-RTS trigger frame.

[0248] In step 2520, process 2500 may include the first STA transmitting a first CTS frame to the second STA in response to the first RTS frame.

[0249] In step 2530, process 2500 may include transmitting, by the first STA, a CF end frame based on the first STA not receiving the data within a time period from the transmission of the first CTS frame. In one embodiment, the time period may be longer than a SIFS.

[0250] In one embodiment, process 2500 may additionally, when the first STA does not receive the data within the time period from the transmission of the first CTS frame, comprise transmitting, by the first STA, an end-frame CF. Petition 870250101983, dated 07 / 11 / 2025, pp. 242 / 288

Claims

1 / 10 CLAIMS 1. A method characterized by comprising: receiving, by a first wireless device from a second wireless device: via a first link, a first Request to Send (RTS) frame requesting data transmission, via the first link, to the first wireless device; and via a second link, a second RTS frame requesting data transmission, via the second link, to the first wireless device; transmitting, by the first wireless device to the second wireless device: via the first link, a first Authorization to Send (CTS) frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame;And based on the first wireless device not receiving data through the first link within a certain time period from the transmission of the first CTS frame, transmit, by the first wireless device, a contention-free end-frame (CF end) on the first link.

2. Method, according to claim 1, characterized by further comprising receiving, by the first wireless device from the second wireless device, the data through the second link in response to the second CTS frame.

3. Method according to claim 2, characterized by further comprising transmitting, from the first wireless device to the second wireless device, an acknowledgment frame (ACK) through the second link. Petition 870250101983, dated 07 / 11 / 2025, pp. 279 / 288 2 / 10 4. A method, according to any one of claims 1 to 3, characterized in that the time period is greater than a short space between frames (SIFS).

5. A method, according to any one of claims 1 to 4, characterized in that the second RTS frame overlaps the first RTS frame.

6. A method, according to any one of claims 1 to 5, characterized in that the first and second RTS frames comprise multi-user request trigger frames (MU-RTS).

7. Method, according to claim 6, characterized in that the first MU-RTS trigger frame or the second MU-RTS trigger frame comprises an indication of data transmission through a single link between the first link and the second link.

8. A method according to claim 7, characterized in that the first wireless device does not receive data through the first link within the time period from the transmission of the first CTS frame, wherein the method further comprises transmitting, by the first wireless device, a contention-free end frame (CF end) through the first link.

9. Method characterized by comprising: receiving, by a first wireless device from a second wireless device: through a first link, a first Request to Send (RTS) frame requesting data transmission, through the first link, to the first wireless device; and through a second link, a second RTS frame requesting data transmission, through the second link, to the first wireless device; transmitting, by the first wireless device to the second wireless device: Petition 870250101983, dated 07 / 11 / 2025, p.280 / 288 3 / 10 through the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame; and through the second link, a second CTS frame in response to the second RTS frame; and based on the first wireless device receiving from the second wireless device a frame indicating the transmission of data through the second link to the first wireless device, transmit, by the first wireless device, a contention-free end frame (CF end) through the first link.

10. Method according to claim 9, characterized in that the frame comprises a trigger frame.

11. Method, according to claim 10, characterized by further comprising receiving the trigger frame through the first link.

12. Method, according to any one of claims 10 to 11, characterized in that the frame comprises an indication for transmitting the CF end frame through the first link.

13. Method, according to claim 12, characterized in that the indication to transmit the CF endpoint frame through the first link is provided in a user information field or a common information field of the trigger frame.

14. Method according to claim 9, characterized in that the framework comprises a data frame comprising the data.

15. Method according to claim 14, characterized by additionally comprising receiving the data frame through the second link.

16. Method, according to any one of claims 14 to 15, characterized in that the frame comprises an indication of the first link.

17. Method, according to claim 16, characterized in that the indication of the first link indicates that data is not transmitted through the first link to the first wireless device. Petition 870250101983, dated 07 / 11 / 2025, pp. 281 / 288 4 / 10 18. A method, according to any one of claims 16 to 17, characterized in that the indication of the first link is provided in a Universal Signal (U-SIG) field of a physical layer (PHY) header of the frame.

19. Method according to claim 18, characterized in that the U-SIG field additionally comprises a link identifier of the first link.

20. Method, according to any one of claims 16 to 17, characterized in that the indication of the first link is provided in an aggregate control field (control A) of the frame.

21. Method according to claim 20, characterized in that the control field A is provided in a high-processing capacity (HT) control field of the frame.

22. A method, according to any one of claims 10 to 21, characterized in that the frame indicates that data is not transmitted through the first link.

23. A method characterized by comprising: transmitting, by a first wireless device to a second wireless device: through a first link, a first Request to Send (RTS) frame requesting data transmission, through the first link, to the second wireless device; and through a second link, a second RTS frame requesting data transmission, through the second link, to the second wireless device; receiving, by the first wireless device from the second wireless device: through the first link, a first Authorization to Send (CTS) frame in response to the first RTS frame; and through the second link, a second CTS frame in response to the second RTS frame; and Petition 870250101983, dated 07 / 11 / 2025, p.282 / 288 5 / 10 based on the first wireless device transmitting data to the second wireless device through the second link, transmit, from the first wireless device to the second wireless device, a frame indicating the transmission of data through the second link to the second wireless device.

24. Method according to claim 23, characterized in that the frame comprises a trigger frame.

25. Method according to claim 24, characterized by further comprising transmitting the trigger frame through the first link.

26. A method according to any one of claims 24 to 25, characterized in that the frame comprises an indication for the second wireless device to transmit a contention-free end frame (CF end) through the first link.

27. Method according to claim 26, characterized in that the indication to transmit the CF endpoint frame through the first link is provided in a user information field or a common information field of the trigger frame.

28. Method according to claim 23, characterized in that the framework comprises a data frame comprising the data.

29. Method, according to claim 28, characterized by additionally transmitting and receiving the data frame through the second link.

30. Method, according to any one of claims 28 to 29, characterized in that the first frame comprises an indication of the first link.

31. Method, according to claim 30, characterized in that the indication of the first link indicates that data is not transmitted through the first link to the second wireless device.

32. A method, according to any one of claims 30 to 31, characterized in that the indication of the first link is provided in a Universal Signal (U-SIG) field of a physical layer (PHY) header of the frame. Petition 870250101983, dated 11 / 07 / 2025, pp. 283 / 288 6 / 10 33. Method according to claim 11, characterized in that the U-SIG field additionally comprises a link identifier of the first link.

34. Method, according to any one of claims 30 to 31, characterized in that the indication of the first link is provided in an aggregate control field (control A) of the frame.

35. Method according to claim 34, characterized in that the control field A is provided in a high-processing capacity (HT) control field of the frame.

36. A method, according to any one of claims 27 to 35, characterized in that the frame indicates that data is not transmitted through the first link.

37. A method characterized by comprising: receiving, by a first wireless device from a second wireless device: through a first link, a first authorization-to-send (CTS) frame; and through a second link, a second CTS frame; defining a first network allocation vector (NAV) for the first link based on the first CTS frame and a second NAV for the second link based on the second CTS frame; and resetting the first NAV for the first link based on the receipt, from the second wireless device, of a contention-free end frame (CF end) through the first link.

38. Method, according to claim 37, characterized by further comprising transmitting, by the first wireless device to a third STA and through the first link, a frame for a duration specified in the first CTS frame.

39. Method, according to claim 37, characterized by further comprising receiving, by the first wireless device from a third STA and through the first link, a frame for a duration indicated in the first CTS frame.

40. Method, according to any one of claims 37 to 39, characterized in that the second CTS frame overlaps the first CTS frame.

41. A method characterized by comprising: receiving, by a first wireless device from a second wireless device, a first request-to-send (RTS) frame requesting data transmission to the first wireless device; transmitting, by the first wireless device to the second wireless device, a first authorization-to-send (CTS) frame in response to the first RTS frame; and based on the first wireless device not receiving the data within a period of time from the transmission of the first CTS frame, transmitting, by the first wireless device, a contention-free end frame (CF end).

42. Method according to claim 41, characterized in that the time period is longer than a short space between frames (SIFS).

43. A method, according to any one of claims 41 to 42, characterized in that the first RTS frame comprises a multi-user request-to-send (MU-RTS) trigger frame.

44. A method, according to any one of claims 41 to 43, characterized in that the first wireless device does not receive the data within the time period from the transmission of the first CTS frame, wherein the method further comprises transmitting, by the first wireless device, a contention-free end frame (CF end).

45. A device characterized by being arranged to receive, from a second wireless device via a first link, a first request-to-send (RTS) frame requesting data transmission via the first link, and Petition 870250101983, dated 07 / 11 / 2025, pp. 285 / 288 8 / 10 via a second link, a second RTS frame requesting data transmission via the second link; transmitting, to the second wireless device via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame; and based on the device not receiving the data via the first link within a period of time from the transmission of the first CT frame, transmitting a contention-free end frame (CF end) on the first link.

46. ​​A device characterized by being arranged to receive, from a second wireless device via a first link, a first request-to-send (RTS) frame requesting data transmission, via the first link, to the first wireless device; and via a second link, a second RTS frame requesting data transmission, via the second link, to the first wireless device; transmit, to the second wireless device: via the first link, a first authorization-to-send (CTS) frame in response to the first RTS frame; and via the second link, a second CTS frame in response to the second RTS frame; and based on the device receiving from the second wireless device a frame indicating data transmission via the second link to the first wireless device, transmit a contention-free end frame (CF end) via the first link.Petition 870250101983, dated 07 / 11 / 2025, pp. 286 / 288 9 / 10.

47. A method, as defined in any of the preceding claims, characterized in that the first and second wireless devices are STAs according to the IEEE 802.11 standard.

48. A device characterized by being arranged to receive, from a first wireless device, a first request-to-send (RTS) frame requesting data transmission to the first wireless device; transmit, to the first STA, a first authorization-to-send (CTS) frame in response to the first RTS frame; and, based on not receiving the data within a period of time from the transmission of the first CTS frame, transmit, by the first wireless device, a contention-free end frame (CF end).

49. A device characterized by being arranged to transmit, to a first wireless device: through a first link, a first Request to Send (RTS) frame requesting data transmission, through the first link, to the first wireless device; and through a second link, a second RTS frame requesting data transmission, through the second link, to the first wireless device; to receive, from the first wireless device: through the first link, a first Authorization to Send (CTS) frame in response to the first RTS frame; and through the second link, a second CTS frame in response to the second RTS frame; and based on transmitting data to the first wireless device through the second link, to transmit, to the first wireless device, a frame indicating the transmission of data through the second link to the first wireless device. Petition 870250101983, dated 07 / 11 / 2025, p.287 / 288 10 / 10.

50. A device characterized by being arranged to receive, from a first wireless device: through a first link, a first authorization-to-send (CTS) frame; and through a second link, a second CTS frame; defining a first network allocation vector (NAV) for the first link based on the first CTS frame and a second NAV for the second link based on the second CTS frame; and resetting the first NAV for the first link based on the receipt, from the second wireless device, of a contention-free end frame (CF end) through the first link.

51. Wireless communication system, characterized by comprising a plurality of devices as defined in any one of claims 48 to 50.

52. Computer program product characterized by being storable on a computer-readable medium and disposed, when executed on a processor, to execute the methods as defined in any of claims 1 to 47. Petition 870250101983, dated 07 / 11 / 2025, pp. 288 / 288