Enhanced inter-link and same-link initial control frame collision avoidance and handling within multi-link single radio device

Abstract

The present disclosure relates to a method for handling and avoiding inter-link and same-link initial control frame collisions within an enhanced multi-link single radio in a wireless local area network. Technologies for handling cross-link conflicts may include determining when an enhanced multi-link single radio cross-link conflict occurs in a wireless device, and selecting a contention window for the wireless device based on the cross-link conflict. Technologies for avoiding same link collisions may include adjusting a backoff counter operation on one enhanced multi-link single radio link of a wireless device based on a transmit opportunity occurring on another enhanced multi-link single radio link.

Description

Technical Field

[0001] This application relates to wireless communications, including techniques and devices for enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling in wireless local area network architectures.

[0002] Related technical descriptions

[0003] Wireless communication systems are ubiquitous. Furthermore, wireless communication technology has evolved from solely voice communication to also include the transmission of data such as the internet and multimedia content.

[0004] Mobile electronic devices or stations (STAs) or user equipment (UEs) may take the form of smartphones or tablets typically carried by users. One aspect of wireless communication that can typically be performed by mobile devices may include, for example, wireless networking via a wireless local area network (WLAN), which may include devices operating according to one or more communication standards in the IEEE 802.11 family of standards.

[0005] Some wireless devices are capable of performing limited operations across multiple links, such as enhanced multi-link single radio devices in Wi-Fi systems. In some cases, such operations can potentially provide extended capabilities to wireless devices at a lower implementation cost compared to providing simultaneous transmit and receive capabilities, but may also introduce the additional possibility of initial control frame collisions. Therefore, improvements in this area are expected. Summary of the Invention

[0006] This article presents, in particular, implementation schemes for systems, apparatuses, and methods for enabling devices to process and, as far as possible, avoid initial control frame conflicts between links and within the same link in enhanced multi-link single radio architectures in wireless local area networks.

[0007] A wireless device may include: one or more antennas; one or more radio components operatively coupled to the one or more antennas; and a processor operatively coupled to the one or more radio components. The wireless device may be configured to establish a connection with an access point via a wireless local area network (WLAN) on one or more wireless links, or may be an access point configured to establish a connection with one or more other wireless devices via a WLAN on one or more wireless links. In some embodiments, the wireless device may operate in each of the plurality of wireless links using a corresponding radio component from the one or more radio components.

[0008] According to the techniques described herein, a wireless device can, for example, determine, based on the timing of transmissions on another enhanced multilink single radio device link, when the initial control frame is transmitted on an enhanced multilink single radio link, when the initial control frame is transmitted on an enhanced multilink single radio device link, that the initial control frame failure on one link is caused by an enhanced multilink single radio interlink collision with the wireless device addressed by the initial control frame. The wireless device can also determine whether to modify the contention window for the wireless device addressed by the initial control frame based on whether the initial control frame failure is caused by an enhanced multilink single radio interlink collision. In at least some cases, this can potentially help improve the effectiveness of contention window size adjustments for the wireless device.

[0009] This document also describes techniques for wireless devices to prevent simultaneous link collisions in at least some Enhanced Multi-Link Single Radio (EMS) links. These techniques may include: determining when a transmission opportunity is occurring on one EMS link, and adjusting or modifying backoff counter operation on another EMS link based on that transmission opportunity. For example, the backoff counter operation modification may include: suspending the backoff counter while the transmission opportunity is occurring to help reduce the likelihood that the backoff counters of multiple devices will reach zero during the transmission opportunity and that the multiple devices will transmit simultaneously once the transmission opportunity ends. As another example, the backoff counter operation modification may include: discarding a backoff counter that has reached zero on another EMS link while a transmission opportunity is occurring on one EMS link, and starting a new backoff counter (e.g., using the same contention window) once the transmission opportunity ends, which may similarly have the effect of reducing the likelihood that multiple devices will transmit simultaneously once the transmission opportunity ends.

[0010] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to cellular phones, tablet computers, accessory and / or wearable computing devices, portable media players, base stations, access points and other network infrastructure equipment, servers, unmanned aerial vehicles, unmanned aerial controllers, automobiles and / or motor vehicles, and any computing device in various other computing devices.

[0011] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0012] A better understanding of the subject matter can be obtained by considering the following specific description of the implementation scheme in conjunction with the accompanying drawings.

[0013] Figure 1 Example wireless communication systems including wireless devices are illustrated according to some implementation schemes;

[0014] Figure 2 This is a block diagram illustrating an example wireless device according to some implementation schemes;

[0015] Figure 3 This is a block diagram illustrating example network elements or access points according to some implementation schemes;

[0016] Figure 4 This is a block diagram illustrating an example modem or baseband processor according to some implementation schemes;

[0017] Figures 5 to 6 This is a flowchart illustrating an example method for avoiding and handling cross-link and same-link initial control frame collisions in Enhanced Multi-Link Single Radio (EMLSR) in wireless local area networks, according to some implementation schemes;

[0018] Figures 7 to 10 Examples of possible cross-link and proximity collision scenarios that may occur for a given EMLSR device architecture, based on some implementation schemes;

[0019] Figures 11 to 14 Examples of possible cross-link and proximity collision scenarios that may occur for another possible EMLSR device architecture, based on some implementation schemes;

[0020] Figures 15 to 16 Examples of possible cross-link collision handling techniques according to some implementation schemes are illustrated;

[0021] Figures 17 to 18 Examples of possible uplink and downlink EMLSR same-link collision scenarios are illustrated according to some implementation schemes; and

[0022] Figures 19 to 22 Examples of possible approaches to avoid uplink and downlink EMLSR conflicts on the same link, according to some implementation schemes, are illustrated.

[0023] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0024] the term

[0025] The following are definitions of the terms used in this disclosure:

[0026] Memory media—any device of any type of nontransitory memory device or storage device. The term "memory media" is intended to include any computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory; magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. The term "memory media" may include two or more memory media that may reside in different locations (e.g., different computer systems connected via a network). Memory media may store program instructions (e.g., embodied in a computer program) that can be executed by one or more processors.

[0027] Carrier medium—such as memory media as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media that convey signals (such as electrical signals, electromagnetic signals or digital signals).

[0028] Computer system—any of all types of computing or processing systems, including personal computer systems (PCs), server-based computer systems, wearable computers, networked appliances, internet-connected appliances, smartphones, television systems, grid computing systems, or other devices or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0029] User equipment (UE) (or “UE device”) — any of various types of mobile or portable computer systems or devices that perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone-based). TM Android TM This includes mobile phones, tablet computers, portable gaming devices, laptops, wearable devices (e.g., smartwatches, smart glasses, smart goggles, head-mounted displays, etc.), portable internet devices, music players, data storage devices or other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or a combination of these devices) that is easily transportable by the user and capable of wireless communication.

[0030] A wireless device or station (STA) is any of various types of computer systems or devices that perform wireless communication. A wireless device can be portable (or mobile), or it can be stationary or fixed in a location. The terms "station" and "STA" are used similarly. A UE is an example of a wireless device.

[0031] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0032] Base station or access point (AP) — The term “base station” has the full breadth of its common meaning and includes at least a wireless communication station installed in a fixed location for communication as part of a wireless communication system. The term “access point” (or “AP”) is often associated with and used similarly to Wi-Fi-based communication.

[0033] A processing element (or processor) is a component or combination of components capable of performing functions in a device (e.g., a communication device or a network infrastructure device). A processor may include, for example: a processor and associated memory, circuitry such as an ASIC (Application-Specific Integrated Circuit), portions or circuitry of individual processor cores, an entire processor core, a processor array, programmable hardware devices such as field-programmable gate arrays (FPGAs), and / or a large portion of a system comprising multiple processors, as well as any combination of the above components.

[0034] IEEE 802.11 refers to technology based on the IEEE 802.11 wireless standard (such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11-2012, 802.11ac, 802.11ad, 802.11ax, 802.11ay, 802.11be, and / or other IEEE 802.11 standards). IEEE 802.11 technology can also be referred to as "Wi-Fi" or "Wireless Local Area Network (WLAN)" technology.

[0035] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In this context, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently switched on. Generally, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0036] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0037] Figures 1 to 2 – Wireless communication system

[0038] Figure 1 An example of a wireless communication system is shown. Note that... Figure 1 This represents one of many possibilities, and the features of this disclosure can be implemented as needed through any of various systems. For example, the situation described herein can be implemented in any type of wireless device. The wireless communication system described below is an example.

[0039] As shown in the figure, an exemplary wireless communication system includes an access point (AP) 102 that communicates with one or more wireless devices 106A, 106B, etc., via a transmission medium. Wireless devices 106A and 106B can be user equipment, such as a station (STA), a non-AP STA, a UE, or other WLAN devices.

[0040] STA 106 may be a device with wireless network connectivity, such as a mobile phone, handheld device, wearable device (e.g., such as a smartwatch, smart glasses, and / or head-mounted display), computer or tablet, unmanned aerial vehicle (UAV), unmanned aerial controller (UAC), automobile, or virtually any other type of wireless device. STA 106 may include a processor (processing element) configured to execute program instructions stored in memory. STA 106 may perform any of the methods described herein by executing one or more of such stored instructions. Alternatively or in addition, STA 106 may include programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), integrated circuits (e.g., ASICs), programmable logic devices (PLDs), and / or any of a variety of other possible hardware components configured to perform (e.g., individually or in combination) any of the methods described herein or any portion thereof.

[0041] AP 102 can be a standalone AP or an enterprise AP, a transceiver base station (BTS) or a cell site, and may include hardware enabling wireless communication with STA devices 106A and 106B. AP 102 may also be equipped to communicate with network 100 (e.g., the core network of a service provider (e.g., a cellular service provider, internet service provider, and / or operator), a WLAN, an enterprise network, and / or another communication network connected to the internet, and various other possibilities). Therefore, AP 102 facilitates communication between STA devices 106 and / or communication between STA devices 106 and network 100. AP 102 can be configured to provide communication via one or more wireless technologies, such as any, any combination of, and / or all of the following: 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ad, 802.11ax, 802.11ay, 802.11be, and / or other 802.11 versions, and / or cellular protocols such as 6G, 5G, or LTE, including in unlicensed frequency bands.

[0042] The communication area (or coverage area) of AP 102 may be referred to as the Basic Service Area (BSA) or cell. AP 102 and STA 106 can be configured to communicate via a transmission medium using any of a variety of radio access technologies (RAT) or wireless communication technologies such as Wi-Fi, LTE, Advanced LTE (LTE-A), 5G NR, 6G, Ultra Wideband (UWB), etc.

[0043] Therefore, AP 102 and other similar access points (not shown) operating according to one or more wireless communication technologies can be configured as a network that can, for example, provide continuous or nearly continuous overlapping services to STA devices 106A to 106B and similar devices within a geographical area via one or more communication technologies. STAs can roam directly from one AP to another, or can switch between APs and / or network cells (e.g., cellular network cells).

[0044] It should be noted that, at least in some cases, the STA device 106 can communicate using any of a variety of wireless communication technologies. For example, the STA device 106 can be configured to communicate using Wi-Fi, LTE, LTE-A, 5G NR, 6G, Bluetooth, UWB, one or more satellite systems, etc. Other combinations of wireless communication technologies (including more than two wireless communication technologies) are also possible. Similarly, in some cases, the STA device 106 can be configured to communicate using only a single wireless communication technology.

[0045] As shown in the figure, the exemplary wireless communication system may also include an access point (AP) 104 that communicates with the wireless device 106B via a transmission medium. AP 104 also provides a communication connection to network 100. Therefore, a wireless device can connect to either or both of AP 102 (or another cellular base station) and access point 104 (or another access point) to access network 100. For example, a STA may roam from AP 102 to AP 104 based on one or more factors such as mobility, coverage, interference, and / or capability. It should be noted that AP 104 may also allow access to networks different from those allowed by AP 102 (e.g., enterprise Wi-Fi networks, home Wi-Fi networks, etc.).

[0046] STA 106A and STA 106B may include handheld devices (such as smartphones or tablets), wearable devices (such as smartwatches, smart glasses, head-mounted displays), and / or may include any device of various types with wireless communication capabilities. For example, one or more of STA 106A and / or STA 106B may be wireless devices designed for fixed or nomadic deployments, such as home appliances, measuring devices / sensors, control devices, etc.

[0047] STA 106B can also be configured to communicate with STA 106A. For example, STA 106A and STA 106B may be able to perform direct device-to-device (D2D) communication. It should be noted that such direct communication between STAs may also be referred to as, or alternatively as, peer-to-peer (P2P) communication. Direct communication may be supported by AP 102 (e.g., AP 102 may facilitate discovery, and various possible forms of assistance), or may be performed in a manner not supported by AP 102. According to various examples, such P2P communication may be performed using any of the following direct communication technologies: 3GPP-based D2D communication technology, Wi-Fi-based P2P communication technology, UWB, BT, and / or various other direct communication technologies.

[0048] STA 106 may include one or more devices or integrated circuits for facilitating wireless communication, potentially including Wi-Fi modems, cellular modems, and / or one or more other wireless modems. The wireless modem may include one or more processors (processor elements) and various hardware components as described herein. STA 106 may perform any of the methods described herein (or any part thereof) by executing instructions on one or more programmable processors. For example, STA 106 may be configured to perform techniques such as enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling in wireless communication systems, according to the various methods described herein. Alternatively or otherwise, the one or more processors may be one or more programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays), application-specific integrated circuits (ASICs), or other circuitry configured to perform any of the methods described herein or any part thereof. The wireless modem described herein may be used in STA devices as defined herein, wireless devices as defined herein, or communication devices as defined herein. The wireless modem described herein may also be used in APs, base stations, picocells, femtocells, and / or other similar network-side devices.

[0049] STA 106 may include one or more antennas for communicating using two or more wireless communication protocols or radio access technologies (RATs). In some cases, STA device 106 may be configured to communicate using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Alternatively, STA device 106 may include two or more radio components, each of which may be configured to communicate via a corresponding wireless link. Other configurations are also possible.

[0050] Figure 2 –Example block diagram of STA device

[0051] Figure 2 An example block diagram of an STA device (such as STA 106) is illustrated. In some cases, STA 106 may additionally or alternatively be referred to as UE 106. STA 106 may also be referred to as a non-AP STA 106. As shown, STA 106 may include a System-on-Chip (SOC) 200, which may include one or more parts configured for various purposes. Some or all of the various illustrated components (and / or other device components not illustrated, e.g., in variant and alternative arrangements) may be “communically coupled” or “operationally coupled”, terms used herein to refer to components that can communicate directly or indirectly when the device is in operation.

[0052] In some cases, the STA 106 can be configured as a multi-link device (MLD). In such cases, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform concurrent data transmission and reception across a single frequency band and / or multiple frequency bands (e.g., such as the 2.4 GHz band, the 5 GHz band, and / or the 6 GHz band) on multiple channels. Therefore, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform multi-link operation (MLO). For example, the STA 106 (e.g., one or more radio components of the STA 106) can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured such that a single radio component can simultaneously listen to two or more links).

[0053] As shown, the SOC 200 may include: a processor 202 that executes program instructions for the STA 106; and a display circuit 204 that performs graphics processing and provides display signals to the display 260. The SOC 200 may also include motion sensing circuitry 270, which may use, for example, any motion sensing component such as a gyroscope, accelerometer, and / or various other motion sensing components to detect motion of the STA 106 in one or more dimensions. The processor 202 may also be coupled to a memory management unit (MMU) 240, which may be configured to receive addresses from the processor 202 and translate these addresses into locations in memory (e.g., memory 206, read-only memory (ROM) 250, flash memory 210). The MMU 240 may be configured to perform memory protection and page table translation or setup. In some cases, the MMU 240 may be included as part of the processor 202.

[0054] As shown in the figure, SOC 200 can be coupled to various other circuits of STA 106. For example, STA 106 may include various types of memory (e.g., including NAND flash memory 210), connector interface 220 (e.g., for coupling to computer systems, docking stations, charging stations, etc.), display 260, and wireless communication circuitry 230 (e.g., for LTE, LTE-A, 5G NR, 6G, Bluetooth, Wi-Fi, NFC, GPS, UWB, peer-to-peer (P2P), device-to-device (D2D), etc.).

[0055] STA 106 may include at least one antenna, and in some cases may include multiple antennas, such as 235A and 235B, for performing wireless communication with access points, base stations, wireless stations, and / or other devices. For example, STA 106 may use antennas 235A and 235B to perform wireless communication. As noted above, STA 106 may be configured in some examples to perform wireless communication using multiple wireless communication standards or radio access technologies (RATs).

[0056] The wireless communication circuitry 230 may include a Wi-Fi modem 232, a cellular modem 234, and a Bluetooth modem 236. It should be noted that one or more of the Wi-Fi modem 232, cellular modem 234, and / or Bluetooth modem 236 may be configured for MLO, for example, as described above. The Wi-Fi modem 232 enables STA 106 to perform Wi-Fi or other WLAN communications, for example, on an 802.11 network. The Bluetooth modem 236 enables STA 106 to perform Bluetooth communications. The cellular modem 234 may be able to perform cellular communications according to one or more cellular communication technologies, for example, according to one or more 3GPP specifications.

[0057] As described herein, STA 106 may include hardware and software components for implementing aspects of this disclosure. For example, one or more components of the wireless communication circuitry 230 of STA 106 (e.g., Wi-Fi modem 232, cellular modem 234, BT modem 236) may be configured, for example, to implement part or all of the methods described herein for enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling by means of a processor executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), a processor configured as an FPGA (Field Programmable Gate Array), and / or using dedicated hardware components that may include ASICs (Application-Specific Integrated Circuits).

[0058] Figure 3 – Block diagram of the access point

[0059] Figure 3 An example block diagram of Access Point (AP) 104 is shown. In some cases (e.g., in an 802.11 communication context), AP 104 may also be referred to as a Station (STA), and may be more specifically referred to as an AP STA. Note that... Figure 3 The AP is merely one example of a possible access point. As shown, AP 104 may include a processor 304 capable of executing program instructions for AP 104. Processor 304 may also be coupled to a memory management unit (MMU) 340, which may be configured to receive addresses from processor 304 and translate these addresses into locations in memory (e.g., memory 360 and read-only memory (ROM) 350), or into other circuitry or devices.

[0060] In some cases, AP 104 can be configured as a multi-link device (MLD). In such cases, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform concurrent data transmission and reception across a single frequency band and / or multiple frequency bands (e.g., such as the 2.4 GHz band, 5 GHz band, and / or 6 GHz band) on multiple channels. Therefore, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform multi-link operation (MLO). For example, AP 104 (e.g., one or more radio components of AP 104) can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured such that a single radio component can simultaneously listen to two or more links).

[0061] AP 104 may include at least one network port 370. Network port 370 may be configured to be coupled to a network and provide network access to multiple devices such as STA device 106, as described above in this document. Figure 1 As described in the text.

[0062] Network port 370 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider (e.g., an operator and / or cellular carrier). The core network may provide mobility-related services and / or other services to multiple devices (such as STA device 106). In some cases, network port 370 may be coupled to a telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other STA devices served by a cellular service provider).

[0063] AP 104 may include one or more radio components 330A-330N and at least one antenna 334 (and may include multiple antennas), the radio components being coupled to one or more corresponding communication links. Antenna 334 may be configured to operate as a wireless transceiver in conjunction with one or more other components, and may also be configured to communicate with STA device 106 via radio components 330A-330N. Note that one or more of the radio components 330A-330N may be configured for MLO, for example, as described above. Antennas 334A to 334N communicate with one or more corresponding radio components 330A to 330N via communication links 332A to 332N. Communication link 332 may be a receive link, a transmit link, or both. Radio components 330A to 330N may be configured to communicate according to various wireless communication standards, including but not limited to LTE, LTE-A, 5G NR, 6G, UWB, Wi-Fi, BT, etc. AP 104 can be configured to operate on multiple wireless links using one or more radio components 330A to 330N. In some specific implementations, each radio component can be used to operate on a corresponding wireless link.

[0064] AP 104 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, AP 104 may include multiple radio components that enable network entities to communicate according to various wireless communication technologies. For example, as one possibility, AP 104 may include 4G or 5G radio components for performing communication according to 3GPP wireless communication technologies, and Wi-Fi radio components for performing communication according to one or more Wi-Fi specifications. In this case, AP 104 may be able to operate as both a cellular base station and a Wi-Fi access point. As another possibility, AP 104 may include multimode radio components capable of performing communication according to any of the various wireless communication technologies (e.g., 5G NR and Wi-Fi, 5G NR and LTE, etc.). As yet another possibility, AP 104 may be configured to function exclusively as a Wi-Fi access point, for example, in the absence of cellular communication capabilities.

[0065] As further described herein, AP 104 may include hardware and software components for implementing or supporting the features described herein, such as enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling, as well as various other possible features. The processor 304 of AP 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) to operate multiple radio links using multiple corresponding radio components. Alternatively, processor 304 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or otherwise), the processor 304 of AP 104, in conjunction with one or more of other components 330, 332, 334, 340, 350, 360, 370, may be configured to implement or support some or all of the features described herein.

[0066] Figure 4 – Block diagram of a modem or baseband processor

[0067] Figure 4 An example block diagram of a modem 400 is illustrated, which may also be referred to as a baseband processor 400. Modem 400 can provide signal processing functionality for one or more wireless communication technologies such as Wi-Fi, Bluetooth, and / or cellular (e.g., 3GPP) communication technologies. Therefore, as an option, modem 400 may represent a Wi-Fi modem; for example, Figure 4 The illustrated modem 400 can represent Figure 2 One possible example of the illustrated Wi-Fi modem 232. Alternatively, modem 400 could represent a cellular modem or a cellular baseband processor; for example... Figure 4 The illustrated modem 400 can represent Figure 2 One possible example of the illustrated cellular modem 234. As a further possibility, modem 400 could represent a Bluetooth modem; for example, Figure 4 The illustrated modem 400 can represent Figure 2 This is one possible example of the illustrated Wi-Fi modem 236. In some cases, modem 400 may implement functionality to support communication according to various wireless communication technologies. In at least some cases, modem 400 may run a real-time operating system, for example, to facilitate the performance of time-dependent wireless communication functionality.

[0068] In some cases, modem 400 can be configured to perform concurrent data transmission and reception across multiple channels in a single and / or multiple frequency bands (e.g., such as the 2.4 GHz band, 5 GHz band, and / or 6 GHz band). Therefore, modem 400 can be configured to perform multi-link operation (MLO). For example, modem 400 can be configured to perform simultaneous transmit and receive (STR) operation (e.g., configured for simultaneous uplink and downlink traffic on a pair of links) and / or enhanced multi-link single radio (EMLSR) operation (e.g., configured to allow a single radio component to simultaneously listen to two or more links).

[0069] Modem 400 may include processing circuitry 402, which may include one or more processor cores, ASICs, programmable hardware elements, digital signal processors, and / or other processing elements. The processing circuitry may be able to prepare baseband signals for up-conversion and transmission by the radio circuitry of a wireless device, and / or process baseband signals for reception and down-conversion by the radio circuitry of the wireless device. Such processing may include signal modulation, encoding, decoding, etc., among various possible functions. The processing circuitry may also be able to, or alternatively, perform functionality of one or more baseband and / or other layers / sublayers of a protocol stack for one or more wireless communication technologies implemented by modem 400, such as physical layer (PHY) functionality, media access control (MAC) functionality, logical link control (LLC) functionality, radio resource control (RRC) functionality, radio link control (RLC) functionality, etc. In some cases, modem 400 itself may include at least some radio circuitry (e.g., for performing input baseband signal to radio frequency signal conversion and / or input radio frequency signal to baseband signal conversion). Alternatively or additionally, some or all of these functions may be performed by separate radio / transceiver components of the wireless device.

[0070] The modem 400 may also include a memory 404, which may include a non-transitory computer-readable storage medium. The memory 404 may include program instructions for performing signal processing and / or any of the various possible general-purpose processing functions. The processing circuitry 402 may be able to execute the program instructions stored in the memory 404. The memory 404 may also store data generated and / or used during processing performed by the processing circuitry 402.

[0071] As shown in the figure, the modem 400 may also include, for example, for communication with wireless devices (such as...) Figures 1 to 3Interface circuitry that communicates with other components of the illustrated STA 106 or AP 104 (such as the application processor, radio / transceiver circuitry, and / or any of the various other components). Such an interface can be implemented in any of a variety of ways; for example, as one possibility, the modem 400 may have a direct interface to the transceiver circuitry of the wireless device and may have additional indirect interfaces via the system bus to the application processor and / or other components of the wireless device. Other configurations are also possible.

[0072] In at least some cases, the hardware and software components of modem 400 may be configured to implement or support the features described herein (such as enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling) and various other possible features. For example, the processing circuitry 402 of modem 400 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on memory (e.g., a non-transitory computer-readable storage medium) 404 and / or using dedicated hardware components.

[0073] Figures 5 to 6 – Enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling flow chart

[0074] Figures 5 to 6 This is a flowchart illustrating methods for supporting enhanced multi-link single-radio cross-link and same-link initial control frame collision avoidance and handling in WLANs, according to some implementation schemes. In various implementation schemes, some elements of the illustrated methods may be performed simultaneously, in a different order than shown, replaced by one or more other method elements, or omitted. Additional method elements may also be performed as needed.

[0075] Figures 5 to 6 Various aspects of the method can be derived from wireless devices (such as in...) Figures 1 to 4 This can be implemented as illustrated and relative to the AP 104 or STA 106 described in these figures, or more generally, it can be implemented as needed in conjunction with any of the computer circuits, systems, devices, elements, or components shown in the figures. For example, the processor of such a device (such as in...) Figure 4 The baseband processor 400 illustrated and described relative to the figure and / or other hardware may be configured to cause the device to perform any combination of the method elements shown and / or other method elements.

[0076] It should be noted that, although described in a manner relating to the use of communication technologies and / or features associated with the IEEE 802.11 specification document... Figures 5 to 6 The method incorporates at least some elements, but this description is not intended to limit the scope of this disclosure. Figures 5 to 6Various aspects of this method can be used in any suitable wireless communication system as needed. As shown in the figure, the method can be operated as follows.

[0077] Access point (AP) wireless devices can provide one or more basic service sets (BSS). In some implementations, an AP wireless device can be an AP multilink device (MLD) capable of providing a BSS on each of multiple links, such as 2.4 GHz, 5 GHz, and / or 6 GHz. An AP wireless device can operate independently or may be attached to one or more other devices (e.g., as part of a larger network). For example, in some implementations, an AP wireless device can be a member of a multi-access point (MAP) system that may include multiple AP wireless devices.

[0078] An access point (AP) wireless device can establish a wireless association with one or more non-AP (or "STA") wireless devices. Depending on the implementation, such wireless associations can be established using Wi-Fi, at least partially Wi-Fi-based wireless communication technologies, and / or any of a variety of other wireless communication technologies. For example, as a possibility, the access point (AP) wireless device may provide (e.g., broadcast) a beacon transmission including information for association with the AP wireless device, and one or more other wireless devices (e.g., non-AP wireless devices) may use the information provided in the beacon transmission to request association with the AP wireless device. In some cases, it is also possible to use (e.g., unicast) probe requests and probe responses for non-AP wireless devices to obtain AP parameters and / or other system information about the AP wireless device. Variations and / or other technologies for establishing associations are also possible.

[0079] According to at least some implementations, the AP wireless device can provide wireless LAN functionality to associated wireless devices. As part of the wireless LAN functionality, depending on the general specifications of the wireless communication technology used by the wireless LAN (e.g., as a possibility, Wi-Fi) and / or the network-specific parameters configured by the AP wireless device, the wireless devices may compete for medium access and may perform wireless transmissions on one or more wireless communication channels (each of which may include multiple sub-channels).

[0080] For example, according to at least some implementations, performing downlink data transmission from an AP wireless device to a non-AP wireless device in such a wireless LAN may include contention for medium access (e.g., to avoid collisions and potential interference), and once medium access is obtained, a Physical Layer (PHY) Protocol Data Unit (PPDU) (which may also be referred to as a downlink frame) is sent to the destination wireless device. The downlink frame may include physical layer signaling (e.g., including preambles for frame detection, time and frequency synchronization, channel estimation, etc., and header information indicating packet configuration, format, data rate, channel occupancy time, and / or other control information) and data (which may in turn include one or more higher-layer packets, such as Medium Access Control (MAC) Protocol Data Units (MPDUs)). It should be noted that other types of transmissions (e.g., including triggered uplink frames, Enhanced Distributed Channel Access (EDCA) uplink frames, Transmission Opportunity (TXOP) sharing for peer-to-peer (P2P) communication, etc.) are also possible in such wireless LANs. In some implementations, Initial Control Frame (ICF) / Initial Control Response (ICR) signaling exchanges (such as Request to Transport (RTS) or Multi-User RTS (MU-RTS) and Clear Transport (CTS) exchanges (e.g., for downlink or EDCA uplink operations) or Buffer Status Report Polling (BSRP) and Buffer Status Report (BSR) exchanges (e.g., for triggered uplink operations)) and various other possible methods may be used to obtain media access for a period of time (e.g., a transmission opportunity or "TXOP").

[0081] Non-AP STAs in such systems may be able to operate on multiple radio links using Enhanced Multi-Link Single Radio (EMLSR) technology. For example, an EMLSR-capable STA may be able to simultaneously monitor multiple links (e.g., for idle channel assessment and / or to receive certain signaling information) using a primary radio component and auxiliary radio components, or using reconfigurable radio components or another EMLSR architecture. It is also possible that an EMLSR cannot simultaneously transmit or receive data frames on multiple links; for example, the radio architecture of an EMLSR device may consist of only a single radio component with bandwidth, modulation and decoding scheme (MCS), and other capabilities sufficient to support data frame communication. In some cases, a device capable of simultaneously transmitting or receiving data frames on multiple links may be referred to as a device with simultaneous transmit and receive (STR) capability. In some implementations, the AP wireless device may be a device with STR capability.

[0082] (STR)AP wireless devices and (EMLSR) non-AP STAs can establish multiple wireless links. For example, 5GHz and 6GHz links may be available in a Wi-Fi-based communication system. APs and non-AP STAs can attempt to communicate on those links in a manner that results in cross-link collisions. For example, an AP can generate an ICF configured to be sent to a non-AP STA and can contend for medium access and send the ICF to the non-AP STA on a first link. A non-AP STA can contend for medium access to send an ICF or other uplink frame to the AP on a second link, where timing prevents the non-AP STA from receiving the entire ICF from the AP and therefore does not respond to the ICF from the AP, resulting in ICF failure. For example, an AP may determine that an MU-RTS failure has occurred after a CTS timeout period has elapsed without a CTS being received, or an AP may determine that a BSRP failure has occurred if a BSR is not received within a short inter-frame interval (SIFS) after the BSRP transmission ends. Therefore, it is possible for an AP to determine that an ICF failure has occurred based on an ICR timeout period or other configured time period elapsed without an ICR being received.

[0083] The AP can determine whether such ICF failures are caused by cross-link collisions (502). For example, because the AP may have STR capabilities, it may be able to receive ICFs or other uplink frames from non-AP STAs on a second link and determine, at least in part, based on the timing of the ICF or other uplink frames, that the ICF failure on the first link is caused by a cross-link EMLSR operation by a non-AP STA. Alternatively, if no ICF or other uplink frames are received on the second link from a non-AP STA (or from any other non-AP STA on any other link established between the AP MLD and the non-AP MLD), and the timing should correspond to the cross-link EMLSR operation that caused the ICF failure on the first link, it is possible that the AP can determine that the ICF failure on the first link is not caused by a cross-link EMLSR operation by any STA of the non-AP MLD.

[0084] The AP can determine the contention window (504) for a non-AP STA based at least in part on whether the ICF failure was caused by a cross-link collision. In some implementations, this may include: determining to use the last valid contention window (e.g., keeping the contention window unchanged for non-AP STAs) if the multi-link radio device has already initiated a TXOP on the second link and the timing indicates a cross-link collision; and determining to modify the contention window for a non-AP STA (e.g., doubling the last valid contention window as a possibility) if the multi-link radio device has not yet initiated a TXOP on the second link and the timing indicates a cross-link collision. The AP may choose to back off from the (possibly modified) determined contention window to compete for medium access in order to make its next transmission to the non-AP STA in the non-AP MLD.

[0085] This approach may be useful because, although increasing the contention window may be beneficial in at least some other cases (e.g., as a possibility, in cases where ICF failure is caused by a collision due to media congestion), increasing the contention window may not remedy ICF failure instances caused by EMLSR cross-link collisions, and therefore may only be used to reduce media usage efficiency, at least according to some implementations.

[0086] In some implementations, the AP may additionally or alternatively determine, at least in part, not to respond to uplink transmissions from a non-AP STA on other links (e.g., including a second link) based on generating an ICF and sending an ICF to a non-AP STA on a first link (e.g., for a configured period of time). This prevents a non-AP STA from using uplink transmissions to occupy a second link when the AP has downlink transmissions for a non-AP STA (e.g., because a non-AP STA can abandon a TXOP on the second link if no ICR is received within the configured ICR timeout period), allowing the AP to attempt to perform another downlink transmission more quickly after such EMLSR cross-link conflicts. However, this may also involve more wasted media usage, at least in some implementations, especially if the non-AP STA initiates a TXOP on the second link by directly sending uplink data frames instead of sending an ICF.

[0087] The AP and / or non-AP STA may also, or alternatively, implement one or more techniques for avoiding collisions on the same EMLSR link. Such techniques may, for example, utilize knowledge of TXOPs occurring on one EMLSR link to adjust or modify backoff counter operation on another EMLSR link between the AP and a non-AP STA.

[0088] For example, a device (e.g., an AP MLD or a non-AP MLD) may determine that a TXOP (602) is occurring on a (“first”) EMLSR link and that contention for a TXOP on another (“second”) EMLSR link is being initiated. The device may then adjust its backoff counter operation for the second EMLSR link (604) at least in part based on the TXOP on the first EMLSR link, for example, if the TXOP on the second EMLSR link and the TXOP on the first EMLSR link belong to the same MLD's STA.

[0089] Such adjustments / modifications may be designed to reduce the likelihood that the backoff counters of multiple devices (e.g., both AP and non-AP STAs in various cases, or multiple non-AP STAs in the case of multi-user operation) will simultaneously reach zero (0) on the second EMLSR link, which could cause those transmissions attempted by these multiple devices on the second EMLSR link to collide.

[0090] As one possibility, adjusting the backoff counter operation for the second EMLSR link may include: pausing the backoff counter for the second EMLSR link during a TXOP on the first EMLSR link (or delaying its initiation), and if the TXOP is for another non-AP STA on the same non-AP MLD, resuming the backoff counter for the second EMLSR link (or allowing its initiation) after returning to the listening operation following the end of the TXOP on the first EMLSR link. According to various embodiments, the pause / delay may be triggered by the end of the ICF or ICR used when initiating the TXOP, or by any of a variety of other possible timing rules. According to various embodiments, resuming backoff / allowing backoff initiation may be triggered after a configuration transition delay following the end of the TXOP on the first EMLSR link, or by any of a variety of other possible timing rules.

[0091] As an alternative possibility, the backoff counter for the second EMLSR link may continue to operate during the TXOP on the first EMLSR link. However, the device may initiate a TXOP on the second EMLSR link without basing it on the backoff counter for the second EMLSR link reaching 0 during the TXOP on the first EMLSR link. In this case, if the TXOP is for another non-AP STA within the same non-AP MLD, a new backoff counter may be started after the TXOP on the first EMLSR link is completed. For example, adjusting the backoff counter operation for the second EMLSR link may include: determining that the backoff counter for the second EMLSR link has reached 0 during the TXOP on the first EMLSR link, and if the TXOP is for another non-AP STA within the same non-AP MLD, starting a new backoff counter for the second EMLSR link after returning to the listening operation following the TXOP on the first EMLSR link, based at least in part on the backoff counter for the second EMLSR link reaching 0 during the TXOP on the first EMLSR link. The new backoff counter may be selected from the current contention window.

[0092] Therefore, according to Figures 5 to 6 According to at least some implementation methods, it may be possible to handle cross-link EMLSR conflicts and avoid at least some same-link EMLSR conflicts, such as to provide more efficient wireless device and network operation.

[0093] Figures 7 to 22 and additional information

[0094] Figures 7 to 22 Examples of possible combinations are given. Figures 5 to 6 The method used is another aspect. However, it should be noted that in Figures 7 to 22 The exemplary details illustrated and described with respect to these figures are not intended to limit this disclosure as a whole: many variations and alternatives to the details provided below are possible and should be considered within the scope of this disclosure.

[0095] Enhanced Multi-Link Single Radio (EMLSR) is a feature introduced in IEEE 802.11be and is widely adopted in wireless devices with Wi-Fi 7 capability. Devices supporting EMLSR can potentially operate simultaneously on multiple links using a single, fully-capable radio component (e.g., under certain limitations). Numerous possible wireless device design and architecture options exist to support such EMLSR operation, including designs with one fully-capable radio component and one or more limited-capability radio components (e.g., “scanning” or “auxiliary” radio components), and / or designs with reconfigurable antenna architectures, among various other possibilities.

[0096] With the deployment of new-generation equipment (e.g., including Wi-Fi 8STA), the number of EMLSR links supported by wireless devices can potentially increase further. In the case of EMLSR operation, there may also be EMLSR cross-link collisions and EMLSR intra-link collisions, which can be exacerbated by increasing the number of EMLSR links. An excessive number of such collisions can potentially lead to network inefficiency and worse latency and throughput performance.

[0097] In a multi-link operation (MLO) scenario, a cross-link collision of the same device's EMLSR may occur when one STA (“STA1”) in a STA MLD initiates an uplink transmission opportunity (TXOP) with one AP (“AP1”) in an AP MLD on a first link (“L1”) and another AP (“AP2”) in the AP MLD initiates a downlink TXOP with another STA (“STA2”) in the STA MLD on a different link (“L2”). Since STA2 lacks any radio components to receive the MU-RTS for the DL TXOP on L2 due to operation on L1, a MU-RTS / CTS failure may occur. The probability of such cross-link collisions of EMLSRs may increase with the number of EMLSR links; with more EMLSR links present, when a STA is already in a UL TXOP, an AP in the AP MLD may attempt to initiate a DL TXOP with a STA outside the AP MLD on different EMLSR links, thus the impact of cross-link collisions may be exacerbated by the increase in the number of EMLSR links outside the AP MLD.

[0098] When there is an uplink or downlink TXOP between an AP and a STA on the first link, and one or more other APs and STAs of the same AP MLD and the same non-AP MLD access the channel on the second link to initiate a TXOP at the end of the TXOP on the first link, the same device EMLSR on the same link may conflict in the MLO scenario, which may lead to an Initial Control Frame (ICF) conflict.

[0099] Figures 7 to 10 Examples of possible cross-link and proximity collision scenarios that may occur for a given EMLSR device architecture, based on some implementation schemes, are illustrated. Figures 7 to 10In the EMLSR architecture of the scenario, the non-AP MLD has a primary radio component (e.g., with sufficient bandwidth, modulation and decoding schemes and / or other capabilities for Wi-Fi data communication) and one or more auxiliary radio components (e.g., with limited bandwidth, modulation and decoding schemes and / or other capabilities sufficient to perform idle channel assessment and / or receive initial control frames (e.g., MU-RTS and BSRP), as well as various possible operations).

[0100] exist Figure 7 In this scenario, before the non-AP MLD begins switching its main radio components to L2 to initiate a TXOP, AP1 of the AP MLD initiates a TXOP on L1. In this case, STA1 receives the MU-RTS up to the user information field and is able to determine that operation for the TXOP continues on L1, preventing STA2 from initiating a TXOP on L2 and thus preventing cross-link collisions.

[0101] exist Figure 8 In this scenario, AP1 initiates a TXOP on L1, but STA1 cannot receive the user information field. In this situation, the primary radio unit begins switching to L2 before STA1 determines whether AP1 intends to initiate its TXOP, and STA2 initiates the TXOP on L2. Therefore, due to cross-link activity from non-AP MLDs, a MU-RTS collision and CTS timeout occur on L1. It should be noted that, at least according to some implementations, AP2 can still respond with CTS on L2, allowing the TXOP on L2 to continue in this scenario.

[0102] exist Figure 9 In this scenario, a non-AP MLD performs a radio component handover between L1 and L2 to initiate a TXOP on L2, where timing ensures that the auxiliary radio component does not receive the MU-RTS transmitted by AP1 on L1 (e.g., due to local sensitivity degradation caused by transmissions on L2 and / or timing of the radio component handover). Similar to... Figure 8 In this scenario, due to cross-link activities not originating from APMLD, MU-RTS conflicts and CTS timeouts will occur on L1. It should be noted that, also in this scenario, at least according to some implementation schemes, AP2 can respond with CTS on L2, allowing TXOP on L2 to continue in this scenario.

[0103] exist Figure 10In this scenario, the non-AP MLD initiates a handover of the primary radio component to L2, and starts the TXOP before AP1 initiates it on L1. AP2 receives the RTS on L2, but there is a "cross-link processing delay" time when delivering the information to AP1, so AP1's TXOP initiation on L1 continues and causes a cross-link collision. It should be noted that the "cross-link processing delay" can vary depending on the specific device implementation and other possible factors. As shown in the figure, at least in some implementations, the total duration of the cross-link collision in this scenario may include: the duration of the padded MU-RTS + the RTS + the cross-link processing time at the AP MLD.

[0104] Figures 11 to 14 Examples of possible cross-link and proximity collision scenarios that may occur with another possible EMLSR device architecture, based on some implementation schemes, are illustrated. Figures 11 to 14 In the EMLSR architecture of the scenario, the non-AP MLD has a reconfigurable antenna array that can be reconfigured for 1x1 operation on multiple links (e.g., with limited bandwidth, modulation and decoding schemes and / or other capabilities sufficient to perform idle channel assessment and / or at least receive initial control frames (e.g., MU-RTS and BSRP), and various possible operations) or can be reconfigured for 2x2 operation on one link (e.g., with sufficient bandwidth, modulation and decoding schemes and / or other capabilities for Wi-Fi data communication).

[0105] exist Figure 11 In scenarios similar to Figure 7 In the scenario where AP1 of the AP MLD initiates a TXOP on L1 before the non-AP MLD begins reconfiguring its radio components to 2x2 on L2 to initiate a TXOP, STA1 receives the MU-RTS up to the user information field and is able to determine that it should instead reconfigure its radio components to L1 for the TXOP initiated by AP1, thus preventing STA2 from initiating a TXOP on L2 and avoiding cross-link collisions.

[0106] exist Figure 12 In scenarios similar to Figure 8In this scenario, AP1 initiates a TXOP on L1, but STA1 cannot receive the user information field because the radio component switches to L2 before receiving the user information field. In this case, before STA1 determines whether AP1 wants to initiate a TXOP with it, the radio component is reconfigured to a 2x2 start on L2 (giving up reception on L1), and STA2 initiates a TXOP on L2. Therefore, due to cross-link activity from non-AP MLDs, a MU-RTS collision and CTS timeout occur on L1. It should be noted that, at least according to some implementations, AP2 can still respond with CTS on L2, allowing the TXOP on L2 to continue in this scenario.

[0107] exist Figure 13 In scenarios similar to Figure 9 In this scenario, the radio components are reconfigured to a 2x2 configuration on L2 by a non-AP MLD to initiate a TXOP on L2, causing STA1 to not receive MU-RTS transmitted by AP1 on L1 (e.g., due to radio component handover timing). Due to the cross-link activity of the non-AP MLD, MU-RTS collisions and CTS timeouts occur on L1. It should be noted that, also in this scenario, at least according to some implementations, AP2 can respond with a CTS on L2, allowing the TXOP on L2 to continue in this scenario.

[0108] exist Figure 14 In scenarios similar to Figure 10 In this scenario, a non-AP MLD initiates a reconfiguration of the radio components to a 2x2 configuration on L2, and begins a TXOP before AP1 initiates one on L1. AP2 receives the RTS on L2, but there is a "cross-link processing delay" when delivering the information to AP1, so AP1's TXOP initiation on L1 continues and causes a cross-link collision. Similarly... Figure 10 In this scenario, "cross-link processing latency" can vary depending on the specific device implementation and other possible factors. As shown in the figure, at least in some implementations, the total duration of cross-link conflicts in this scenario may include: the duration of the padded MU-RTS + RTS + cross-link processing time at the AP MLD.

[0109] In some implementation schemes, such as... Figures 8 to 10 and Figures 12 to 14The consequences of cross-link collisions in such scenarios may include: doubling of contention window parameters, reduced channel utilization, and / or rate adaptation effects. For example, this type of cross-link collision may lead to a rate reduction if the rate adaptation algorithm fails to account for ICF when updating the rate. However, since this type of ICF is not caused by poor RSSI or interference, there may be situations where reducing the rate is unnecessary or unhelpful in this scenario.

[0110] Therefore, at least in some implementations, improving the handling of such cross-link collision scenarios could potentially benefit wireless device operation and overall network efficiency. Figure 15 An example aspect of one possible cross-link collision handling technique according to some implementations is illustrated. As shown, it is possible that when an AP determines that a MU-RTS collision is caused by a cross-link collision, the AP will not double the contention window, but instead select a new backoff from the last valid contention window. To determine that the MU-RTS collision is caused by a cross-link collision, when an AP in the MLD sends a MU-RTS to a STA in a non-AP MLD but does not receive a CTS, the AP can check whether the corresponding STA in the same non-AP MLD on a different link has already initiated a TXOP with another AP in the same AP MLD on the uplink. If so, the AP can determine that it will not double the contention window due to the MU-RTS / CTS failure. In some implementations, rules can be potentially defined in 802.11 and / or other wireless communication specifications to specify that such cross-link collisions will not result in a doubling of the contention window.

[0111] Figure 16 Example aspects of another possible cross-link collision handling technique according to some implementations are illustrated. As shown, it is possible that when an AP initiates a TXOP with a STA that is not an AP MLD, the AP does not respond to any uplink transmissions from other STAs of the same non-AP MLD. This could potentially reduce the duration for which a collision prevents an AP from initiating a TXOP with a non-AP MLD on L1, for example, because STA2 does not continue with a TXOP initiated on L2 after AP2 does not respond to an RTS on L2. However, in some cases, this can also lead to additional media resource waste. Furthermore, if the uplink on L2 does not begin with an RTS / CTS exchange (e.g., UL TXOPs are not required to be initiated by an RTS / CTS), even greater media resource waste may exist, for example, for the transmission of the entire data PPDU by STA2.

[0112] Figures 17 to 18Example aspects of possible uplink and downlink EMLSR same-link collision scenarios according to some implementation schemes are illustrated. The illustrated scenarios are shown using a wireless device with an EMLSR architecture based on primary radio components / auxiliary radio components; however, it should be noted that similar scenarios may occur for other EMLSR architectures. In these example scenarios, for non-AP MLDs, when an EMLSR STA participates in a TXOP on one link, another EMLSR STA can resume its backoff on the other link. Therefore, in Figure 17 In the uplink example, STA2 and AP2 compete during an ongoing TXOP on L1 (e.g., between STA1 in the same non-AP MLD and AP1 in the same AP MLD). Given that TX on L1 degrades L2 sensitivity, STA2 may compete during BA reception on L1. The backoff counter remains at 0 when it reaches 0 (considering the medium remains idle). Considering that AP2 wants to initiate a TXOP with another STA in the same non-AP MLD, both AP2 and STA2 simultaneously transmit MU-RTS and RTS after the transition delay, which can lead to a collision. Figure 18 In the downlink example, STA2 and AP2 compete during an ongoing TXOP on L1 (e.g., between STA1 in the same non-AP MLD and AP1 in the same AP MLD). When the backoff counter reaches 0, it remains at 0 (considering the medium remains idle), and if AP2 initiates a TXOP with STA2 in a non-AP MLD, the RTS / MU-RTS will be transmitted simultaneously after the transition delay, leading to a collision. Additionally, in the multi-user downlink case where AP1 transmits to multiple STAs on L1, the likelihood of other STAs in a non-AP MLD transmitting RTS frames after the TXOP ends, and the corresponding collision probability, may further increase. It should also be noted that in both scenarios described above (i.e., Figures 17 to 18 In scenarios where a non-AP MLD STA initiates a UL TXOP using a Physical Layer Protocol Data Unit (PPDU) instead of an RTS, the airtime may be wasted for an even longer duration.

[0113] Figures 19 to 22 Examples of possible approaches to avoid uplink and downlink EMLSR conflicts on the same link, according to some implementation schemes, are illustrated. Figures 19 to 20Example aspects of how APs and STAs follow the behavior of all Access Classes (ACs) in Enhanced Distributed Channel Access (EDCA) are illustrated. For example, the following rule can be defined: if a STA participates in a TXOP (DL or UL) on an EMLSR link, that STA should not compete and should suspend its backoff on another EMLSR link. According to some implementations, the STA may be allowed to resume its backoff after returning to listening operation at the end of the TXOP. The following rule can also be defined: if an AP in an AP MLD participates in a TXOP on an EMLSR link with a STA in a non-AP MLD, then another AP in the same AP MLD should not compete to initiate a TXOP on another link with another STA in the same non-AP MLD until the TXOP on the first link ends. As a possibility, the triggering event for suspending backoff could be the end of the CTS, for example, because at that time, the continuation of the TXOP can be determined by both the AP and the STA. However, as a possibility, other triggering events (such as the end of RTS transmission) can also be used to suspend backoff.

[0114] Figures 21 to 22 Example aspects of another approach to the behavior of all ACs where APs and STAs follow EDCA are illustrated. In these examples, the following rule can be defined: When a downlink or uplink TXOP exists on an EMLSR link, if the AP's backoff counter reaches 0 during the transition delay of the TXOP or another EMLSR link, other APs in the same AP MLD should not initiate a TXOP with another STA in the same non-AP MLD after returning to listening operation, and should invoke a new backoff number from the current contention window. The following rule can also be defined: When a downlink or uplink TXOP exists on an EMLSR link, if the STA's backoff counter reaches 0 during the transition delay of the TXOP or another EMLSR link, other STAs in the same non-AP MLD should not initiate a TXOP with another AP in the same AP MLD after returning to listening operation, and should invoke a new backoff number from the current contention window.

[0115] It should be noted that while many of the examples provided herein involve TXOP initiation using MU-RTS as the initial control frame, similar cross-link and same-link collision scenarios, along with their handling and avoidance methods, can also be applied to TXOPs initiated using Buffer Status Report Polling (BSRP) frames and / or other initial control frames, depending on the implementation.

[0116] As previously discussed, there may be situations where performing rate adaptation based on RTS failures in cross-link collision scenarios is unhelpful. Therefore, at least in some implementations, it is possible that APs and STAs do not use RTS and ICF (MU-RTS / BSRP) failures as a basis for rate reduction, at least for the same link collision and cross-link collisions. For example, since the RTS and ICF rates are often already low (basic MCS rate), in many cases the cause of RTS and ICF failures (e.g., no response to RTS and ICF) may not be due to link quality, and therefore it can be determined that such failures should not be used for rate adaptation.

[0117] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0118] In addition to the exemplary embodiments described above, further embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0119] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein, if executed by a computer system, the program instructions cause the computer system to perform a method, such as any method embodiment of the method embodiments described herein, or any combination of method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

[0120] In some implementations, the device (e.g., AP 104 or STA 106) may be configured to include a processor (or a set of processors) and a memory medium storing program instructions, wherein the processor is configured to read from and execute these program instructions, wherein these program instructions are executable to implement any method implementation (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets) of the various method implementations described herein. The device may be implemented in any of a variety of forms.

[0121] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for operating in wireless communications, the method comprising: generating an initial control frame configured for transmission to a multi-link wireless device on a first link; determining that an initial control frame failure has occurred for the initial control frame; and determining a contention window for the multi-link wireless device based at least in part on whether the multi-link wireless device has initiated a transmit opportunity (TXOP) on a second link.

2. The method of claim 1, wherein determining the contention window comprises: determining to use a last effective contention window when the multi-link wireless device has initiated a TXOP on a second link; and determining to increase a duration of the last effective contention window when the multi-link wireless device has not initiated a TXOP on a second link.

3. The method of claim 1, wherein the method further comprises: selecting a backoff time associated with contending for medium access for transmission to the multi-link wireless device based at least on the determined contention window.

4. The method of claim 1, wherein the initial control frame comprises a multi-user request to send (MU-RTS) frame.

5. The method of claim 1, wherein the initial control frame comprises a buffer status report poll (BSRP) frame.

6. The method of claim 1, wherein determining that the initial control frame failure has occurred for the initial control frame comprises: determining that an initial control response (ICR) timeout period or other configured time period has elapsed without receiving an ICR.

7. The method of claim 1, wherein the method further comprises: determining not to respond to an uplink transmission from the multi-link wireless device on the second link based at least in part on generating the initial control frame configured for transmission to the multi-link wireless device on the first link.

8. A processor comprising a memory configured to cause the processor to perform operations comprising: determining that a transmit opportunity (TXOP) is occurring on a first enhanced multi-link single radio (EMLSR) link; and adjusting a backoff counter operation for a second EMLSR link based at least in part on the TXOP on the first EMLSR link.

9. The processor of claim 8, wherein the TXOP on the first EMLSR link is associated with a first station (STA) of a multi-link device (MLD), wherein a second TXOP to be initiated on the second EMLSR link is associated with a second STA of the MLD, and wherein the backoff counter operation for the second EMLSR link is adjusted further based at least in part on the TXOP on the first EMLSR link and the second TXOP to be initiated on the second EMLSR link being associated with respective STAs of one MLD.

10. The processor of claim 8, wherein adjusting the backoff counter operation for the second EMLSR link further comprises: suspending a backoff counter for the second EMLSR link during the TXOP on the first EMLSR link; and resuming the backoff counter for the second EMLSR link after resuming listen operations following the TXOP on the first EMLSR link.

11. The processor of claim 8, wherein suspending the backoff counter for the second EMLSR link is triggered by: an initial control response (ICR) initiating the TXOP on the first EMLSR link; or an initial control frame (ICF) initiating the TXOP on the first EMLSR link.

12. The processor of claim 8, wherein adjusting the backoff counter operation for the second EMLSR link further comprises: determining that a backoff counter for the second EMLSR link has been zeroed during the TXOP on the first EMLSR link; and starting a new backoff counter for the second EMLSR link after resuming listen operations following the TXOP on the first EMLSR link based at least in part on the backoff counter for the second EMLSR link having been zeroed during the TXOP on the first EMLSR link.

13. A wireless device, the wireless device comprising: one or more antennas; one or more radios operably coupled to the one or more antennas; and a processor operably coupled to the one or more radios; wherein the wireless device is configured to: determine that a transmit opportunity (TXOP) is occurring on a first enhanced multi-link single radio (EMLSR) link; and adjust a backoff counter operation for a second EMLSR link based at least in part on the TXOP on the first EMLSR link.

14. The wireless device of claim 13, wherein the TXOP on the first EMLSR link is associated with a first station (STA) of a multi-link device (MLD), wherein a second TXOP to be initiated on the second EMLSR link is associated with a second STA of the MLD, and wherein the backoff counter operation for the second EMLSR link is adjusted based at least in part on the TXOP on the first EMLSR link and the second TXOP to be initiated on the second EMLSR link being associated with respective STAs of one MLD.

15. The wireless device of claim 13, wherein to adjust the backoff counter operation for the second EMLSR link, the wireless device is further configured to: suspend a backoff counter for the second EMLSR link during the TXOP on the first EMLSR link; and resume the backoff counter for the second EMLSR link after resuming listen operations following the TXOP on the first EMLSR link. ​ 16. The wireless device of claim 15, wherein the back-off counter for the second EMLSR link is suspended after: an initial control response (ICR) initiating the TXOP on the first EMLSR link, or an initial control frame (ICF) initiating the TXOP on the first EMLSR link.

17. The wireless device of claim 13, wherein adjusting the back-off counter operation for the second EMLSR link further comprises: determining that a back-off counter for the second EMLSR link has reached zero during the TXOP on the first EMLSR link; and starting a new back-off counter for the second EMLSR link after resuming listen operations after the TXOP on the first EMLSR link based at least in part on the back-off counter for the second EMLSR link having reached zero during the TXOP on the first EMLSR link.

18. The wireless device of claim 17, wherein a duration of the new back-off counter is selected based at least in part on a current contention window.

19. The wireless device of claim 13, wherein the wireless device comprises an access point multi-link wireless device capable of simultaneous transmit and receive (STR) operations on the first EMLSR link and the second EMLSR link, and wherein the TXOP and the back-off counter operation are occurring on a non-AP multi-link wireless device capable of EMLSR operations on the first EMLSR link and the second EMLSR link.

20. The wireless device of claim 13, wherein the wireless device comprises a non-access point multi-link wireless device capable of EMLSR operations on the first EMLSR link and the second EMLSR link.

Images