Apparatus, system, and method of multi-link wireless communication

Abstract

The present disclosure relates to apparatuses, systems, and methods of multi-link wireless communication. For example, a non-AP MLD may determine whether an EMLSR enable criterion is satisfied. For example, the EMLSR enable criteria may be based on one or more predefined enable criteria corresponding to one or more enable criteria parameters. For example, the non-AP MLD may activate operation of the non-AP MLD in an EMLSR mode of operation of the MLO on multiple links with the AP MLD based on a determination that the EMLSR enable criteria are satisfied. For example, a non-AP MLD may determine whether an EMLSR deactivation criterion is satisfied during an EMLSR mode of operation. For example, the EMLSR deactivation criteria may be based on one or more predefined deactivation criteria corresponding to one or more deactivation criteria parameters. The non-AP MLD may switch the non-AP MLD from the EMLSR operating mode to a non-EMLSR MLO mode based on a determination that the EMLSR deactivation criterion is satisfied.

Description

Technical Field

[0001] This disclosure generally relates to the field of communications, and more specifically to apparatus, systems, and methods for multi-link wireless communications. Background Technology

[0002] Devices in a wireless communication system can be configured to communicate on one or more communication links. Summary of the Invention

[0003] One aspect of this disclosure provides a method performed at a non-access point (AP) multi-link device (MLD), the method comprising: determining whether an Enhanced Multi-Link Single Radio (EMLSR) enable criterion is met, wherein the EMLSR enable criterion is based on one or more predefined enable criterions corresponding to one or more enable criterion parameters; based on determining that the EMLSR enable criterion is met, activating operation of the non-AP MLD in an EMLSR operation mode of multi-link operation (MLO) on multiple links with the AP MLD; determining whether an EMLSR deactivation criterion is met during the EMLSR operation mode, wherein the EMLSR deactivation criterion is based on one or more predefined deactivation criteria corresponding to one or more deactivation criterion parameters; and based on determining that the EMLSR deactivation criterion is met, switching the non-AP MLD from the EMLSR operation mode to a non-EMLSR MLO mode.

[0004] One aspect of this disclosure provides an apparatus including a controller configured to cause a non-access point (AP) multi-link device (MLD) to perform the above-described method.

[0005] One aspect of this disclosure provides a product comprising one or more tangible computer-readable nontransitory storage media, the one or more tangible computer-readable nontransitory storage media including instructions operable to, when executed by at least one processor, enable the at least one processor to enable a non-access point (AP) multi-link device (MLD) to perform the methods described above.

[0006] One aspect of this disclosure provides an apparatus including components for causing a non-access point (AP) multilink device (MLD) to perform the above-described method. Attached Figure Description

[0007] For the sake of clarity, the elements shown in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to others for clarity. Furthermore, reference numerals may be repeated in the figures to indicate corresponding or similar elements. The figures are listed below.

[0008] Figure 1It is a schematic block diagram of a system based on some illustrative aspects.

[0009] Figure 2 It is a schematic diagram of a multi-link communication scheme that can be implemented based on some illustrative aspects.

[0010] Figure 3 It is a schematic diagram of a multi-link communication scheme that can be implemented based on some illustrative aspects.

[0011] Figure 4 It is a schematic diagram of one or more operations based on the Enhanced Multi-Link Single Radio (EMLSR) operating mode, illustrating the technical aspects that can be addressed based on some illustrative aspects.

[0012] Figure 5 It is a schematic diagram of the state diagram for enabling / disabling EMLSR operating modes based on some illustrative aspects.

[0013] Figure 6 It is a schematic flowchart based on some illustrative aspects of multi-link wireless communication methods.

[0014] Figure 7 It is a schematic diagram of a product based on some illustrative aspects. Detailed Implementation

[0015] In the detailed description below, numerous specific details are set forth to provide a thorough understanding of certain aspects. However, those skilled in the art will understand that some aspects can be practiced without these specific details. In other instances, well-known methods, procedures, components, units, and / or circuits are not described in detail to avoid obscuring the discussion.

[0016] The terms used in this discussion, such as “processing,” “computing,” “operation,” “determining,” “establishing,” “analyzing,” “checking,” etc., may refer to one or more operations and / or processes of a computer, computing platform, computing system, or other electronic computing device that can manipulate and / or convert data represented as physical (e.g., electronic) quantities in the computer’s registers and / or memory into other data represented as physical quantities in the computer’s registers and / or memory or other information storage media that may store instructions for performing the operations and / or processes.

[0017] The terms “multiple” and “many” as used in this document include, for example, “multiple” or “two or more”. For example, “multiple items” includes two or more items.

[0018] The use of terms such as “one aspect,” “one aspect,” “illustrative aspect,” and “various aspects” indicates that the described aspect(s) may include specific features, structures, or characteristics, but not every aspect must include specific features, structures, or characteristics. Furthermore, the repeated phrase “in one aspect” does not necessarily refer to the same aspect, although it can.

[0019] As used herein, unless otherwise stated, the use of ordinal adjectives such as “first,” “second,” “third,” etc., to describe a common object only indicates that the objects referred to are different instances of similar objects and does not mean that the objects described must be arranged in a given order in time, space, ranking, or any other way.

[0020] Some aspects can be used in conjunction with a wide variety of devices and systems, such as user equipment (UE), mobile devices (MD), radio stations (STA), personal computers (PC), desktop computers, mobile computers, laptop computers, notebook computers, tablet computers, server computers, handheld computers, handheld devices, wearable devices, sensor devices, Internet of Things (IoT) devices, personal digital assistant (PDA) devices, handheld PDA devices, in-vehicle devices, non-in-vehicle devices, hybrid devices, vehicle devices, non-vehicle devices, mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (APs), wired or wireless routers, wired or wireless modems, video devices, audio devices, audio-video (A / V) devices, wired or wired networks, wireless local area networks (WLANs), wireless video local area networks (WVANs), local area networks (LANs), wireless LANs (WLANs), personal area networks (PANs), wireless PANs (WPANs), etc.

[0021] Some aspects can be used in conjunction with devices and / or networks operating according to the following standards: existing IEEE 802.11 standards (including IEEE 802.11-2020, IEEE Information Technology Standards – Telecommunications and Information Exchange between System LANs and Metropolitan Area Networks – Specific Requirements; Part 11: Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specifications, December 2020); and / or IEEE 802.11be (IEEE P802.11be / D5.0 Information Technology Standards Draft – Telecommunications and Information Exchange between System LANs and Metropolitan Area Networks – Specific Requirements; Part 11: Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specifications; Amendment 8: Enhancements for Extremely High Throughput (EHT), November 2023) and / or future versions and / or derivatives thereof; can be used in conjunction with devices and / or networks operating according to existing cellular specifications and / or protocols and / or future versions and / or derivatives thereof; can be used in conjunction with units and / or devices that are part of the aforementioned networks, etc.

[0022] Some aspects can be used in conjunction with the following devices or systems: one-way and / or two-way radio communication systems, cellular radio telephone communication systems, mobile phones, cellular phones, wireless phones, personal communication system (PCS) devices, PDA devices containing wireless communication devices, mobile or portable global positioning system (GPS) devices, devices containing GPS receivers or transceivers or chips, devices containing RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (e.g., smartphones), Wireless Application Protocol (WAP) devices, etc.

[0023] Some aspects can be used in conjunction with one or more types of wireless communication signals and / or systems, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), orthogonal frequency division multiple access (OFDMA), time division multiplexing (TDM) with FDM, time division multiple access (TDMA), multi-user MIMO (MU-MIMO), space division multiple access (SDMA), extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, ultra-wideband (UWB), 4G, fifth-generation (5G) or sixth-generation (6G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, enhanced data rate GSM evolution (EDGE), etc. Other aspects can be used in a variety of other devices, systems, and / or networks.

[0024] As used herein, the term "wireless device" includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, etc. In some illustrative aspects, a wireless device may be or may include a peripheral device that can be integrated with a computer, or a peripheral device that can be attached to a computer. In some illustrative aspects, the term "wireless device" may optionally include wireless services.

[0025] The term "communicate" as used in this document regarding communication signals includes both sending and / or receiving communication signals. For example, a communication unit capable of transmitting communication signals may include a transmitter for sending communication signals to at least one other communication unit and / or a receiver for receiving communication signals from at least one other communication unit. The verb "transmit" can be used to refer to either the act of sending or the act of receiving. In one example, the phrase "transmit signal" may refer to the act of a first device sending a signal and does not necessarily include the act of a second device receiving a signal. In another example, the phrase "transmit signal" may refer to the act of a first device receiving a signal and does not necessarily include the act of a second device sending a signal. Communication signals may be transmitted and / or received, for example, in the form of radio frequency (RF) communication signals and / or any other type of signal.

[0026] As used herein, the term "circuit" may refer to, be part of, or include: an application-specific integrated circuit (ASIC), an integrated circuit, an electronic circuit, a processor (shared, dedicated, or grouped) and / or memory (shared, proprietary, or grouped), combinational logic circuitry, and / or other suitable hardware components that provide the described functionality, executing one or more software or firmware programs. In some aspects, some functions associated with a circuit may be implemented by one or more software or firmware modules. In some aspects, a circuit may include logic that is at least partially operable in hardware.

[0027] For example, the term "logic" can refer to computational logic embedded in the circuitry of a computing device and / or computational logic stored in the memory of the computing device. For example, logic can be accessed by a processor of the computing device to execute computational logic to perform computational functions and / or operations. In one example, logic can be embedded in various types of memory and / or firmware, such as silicon blocks of various chips and / or processors. Logic can include in and / or be implemented as part of various circuits, such as radio circuits, receiver circuits, control circuits, transmitter circuits, transceiver circuits, processor circuits, etc. In one example, logic can be embedded in volatile and / or non-volatile memory, including random access memory, read-only memory, programmable memory, magnetic memory, flash memory, persistent memory, etc. Logic can be executed by one or more processors using memory such as registers, buffers, etc., which are coupled to one or more processors, for example, as needed to execute the logic.

[0028] Some illustrative aspects can be used in conjunction with WLAN (e.g., Wi-Fi networks). Other aspects can be used in conjunction with any other suitable wireless communication network (e.g., wireless LAN, "piconet", WPAN, WVAN, etc.).

[0029] Some illustrative aspects can be used in conjunction with wireless communication networks that communicate in frequency bands below 10 GHz (e.g., the 2.4 GHz band, the 5 GHz band, the 6 GHz band, and / or any other frequency band below 10 GHz).

[0030] Some illustrative aspects can be used in conjunction with wireless communication networks that communicate in the extremely high frequency (EHF) band (also known as the “millimeter wave (mmWave)” band), such as bands between 20 GHz and 300 GHz, such as bands above 45 GHz (e.g., the 60 GHz band), and / or any other mmWave band.

[0031] Some illustrative aspects can be used in conjunction with wireless communication networks that communicate in the sub-10 GHz band and / or mmWave band, for example, as described below. However, other aspects can be implemented using any other suitable wireless communication band, such as the 5G band, the sub-20 GHz band, the sub-1 GHz (S1G) band, the WLAN band, the WPAN band, etc.

[0032] Some illustrative aspects can be implemented by an mmWave STA (mSTA), for example, it can include an STA with a radio transmitter capable of operating on a channel within the mmWave band. In one example, mmWave communication can involve one or more directional links communicating at multiple gigabits per second, for example, at least 1 gigabits per second, for example, at least 7 gigabits per second, at least 30 gigabits per second, or any other rate.

[0033] In some illustrative aspects, an mmWave STA may include a directional multi-gigabit (DMG) STA, which can be configured to communicate over a DMG band. For example, a DMG band may include a band with a channel start frequency higher than 45 GHz.

[0034] In some illustrative aspects, an mmWave STA may include an Enhanced DMG (EDMG) STA, which can be configured to implement one or more mechanisms that can be configured to enable single-user (SU) and / or multi-user (MU) communication of downlink (DL) and / or uplink (UL) frames using MIMO schemes. For example, an EDMG STA may be configured to implement one or more channel bonding mechanisms, such as those supporting communication over a channel bandwidth (BW) (also known as a “wide channel,” “EDMG channel,” or “bonded channel”) comprising two or more channels, such as two or more 2.16 GHz channels. For example, a channel bonding mechanism may include, for instance, a mechanism and / or operation by which two or more channels, such as 2.16 GHz channels, can be combined, for example, for higher bandwidth packet transmission, enabling higher data rates compared to transmission on a single channel. This document describes some illustrative aspects of communication over a channel bandwidth (BW) comprising two or more 2.16 GHz channels. However, other aspects can also be implemented for communication over channel bandwidths, such as "wide" channels, which include or are formed by any other number of channels among two or more channels, for example, aggregated channels comprising more than two channels. For example, the EDMG STA can be configured to implement one or more channel bonding mechanisms that can, for example, support increased channel bandwidths, such as a 4.32 GHz channel bandwidth, a 6.48 GHz channel BW, an 8.64 GHz channel BW, and / or any other additional or alternative channel BWs. The EDMG STA can perform other additional or alternative functions.

[0035] In other respects, mmWave STAs may include any other type of STA and / or may perform other additional or alternative functions. These other aspects may be achieved through any other device, equipment, and / or station.

[0036] As used herein, the term "antenna" can include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. In some aspects, an antenna may use separate transmitting and receiving antenna elements to achieve transmitting and receiving functions. In other aspects, an antenna may use shared and / or integrated transmitting / receiving elements to achieve transmitting and receiving functions. Antennas may include, for example, phased array antennas, unit antennas, a set of switched-beam antennas, etc.

[0037] refer to Figure 1 The system 100 is illustrated schematically according to some illustrative aspects.

[0038] like Figure 1As illustrated, in some illustrative aspects, system 100 may include one or more wireless communication devices. For example, system 100 may include wireless communication device 102, wireless communication device 140, and / or one or more other devices.

[0039] In some illustrative aspects, devices 102 and / or 140 may include mobile or non-mobile devices, such as static devices.

[0040] For example, devices 102 and / or 140 may include, for example, UE, MD, STA, AP, PC, desktop computer, mobile computer, laptop computer, Ultrabook™ computer, notebook computer, tablet computer, server computer, handheld computer, Internet of Things (IoT) device, sensor device, handheld device, wearable device, PDA device, handheld PDA device, in-vehicle device, non-in-vehicle device, hybrid device (e.g., combining cellular phone functionality with PDA device functionality), consumer device, vehicle device, non-vehicle device, mobile or portable device, non-mobile or non-portable device, mobile phone, cellular phone, PCS device, PDA device containing wireless communication equipment, mobile or portable GPS device, DVB device, relatively small computing device, non-desktop computer, "Lightweight, Enjoy Life" (CSLL) device, ultra-mobile device (UMD). Ultra-mobile PCs (UMPCs), mobile internet devices (MIDs), origami devices or computing devices, devices supporting Dynamically Composable Computation (DCC), context-aware devices, video devices, audio devices, A / V devices, set-top boxes (STBs), Blu-ray disc (BD) players, BD burners, digital video disc (DVD) players, high-definition (HD) DVD players, DVD burners, HD DVD burners, personal video recorders (PVRs), broadcast HD receivers, video sources, audio sources, video receivers, audio receivers, stereo tuners, broadcast radio receivers, flat panel displays, personal media players (PMPs), digital video cameras (DVCs), digital audio players, speakers, audio receivers, audio amplifiers, gaming devices, data sources, data receivers, digital cameras (DSCs), media players, smartphones, televisions, music players, etc.

[0041] In some illustrative aspects, device 102 may include, for example, one or more of processor 191, input unit 192, output unit 193, memory unit 194, and / or storage unit 195; and / or device 140 may include, for example, one or more of processor 181, input unit 182, output unit 183, memory unit 184, and / or storage unit 185. Devices 102 and / or 140 may optionally include other suitable hardware and / or software components. In some illustrative aspects, some or all components of one or more of devices 102 and / or 140 may be enclosed in a common housing or package and may be interconnected or operatively associated using one or more wired or wireless links. In other aspects, components of one or more of devices 102 and / or 140 may be distributed across multiple or separate devices.

[0042] In some illustrative aspects, processor 191 and / or processor 181 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multi-core processor, a microprocessor, a host processor, a controller, multiple processors or controllers, a chip, a microchip, one or more circuits, a circuit system, a logic unit, an integrated circuit (IC), an application-specific integrated circuit (ASIC), or any other suitable multipurpose or dedicated processor or controller. Processor 191 may execute instructions for, for example, the operating system (OS) of device 102 and / or one or more suitable application programs. Processor 181 may execute instructions for, for example, the operating system (OS) of device 140 and / or one or more suitable application programs.

[0043] In some illustrative aspects, input unit 192 and / or input unit 182 may include, for example, a keyboard, keypad, mouse, touchscreen, touchpad, trackball, stylus, microphone, or other suitable pointing or input device. Output unit 193 and / or output unit 183 may include, for example, a monitor, screen, touchscreen, flat panel display, light-emitting diode (LED) display unit, liquid crystal display (LCD) display unit, plasma display unit, one or more audio speakers or headphones, or other suitable output device.

[0044] In some illustrative aspects, memory cell 194 and / or memory cell 184 include, for example, random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous DRAM (SD-RAM), flash memory, volatile memory, non-volatile memory, cache memory, buffer, short-term memory cell, long-term memory cell, or other suitable memory cell. Memory cell 195 and / or memory cell 185 may include, for example, hard disk drive, disk drive, solid-state drive (SSD), and / or other suitable removable or non-removable memory cell. For example, memory cell 194 and / or memory cell 195 may store data processed by device 102. For example, memory cell 184 and / or memory cell 185 may store data processed by device 140.

[0045] In some illustrative aspects, wireless communication devices 102 and / or 140 are capable of transmitting content, data, information, and / or signals via wireless medium (WM) 103. In some illustrative aspects, wireless medium 103 may include, for example, a radio channel, RF channel, Wi-Fi channel, cellular channel, 5G channel, IR channel, Bluetooth (BT) channel, Global Navigation Satellite System (GNSS) channel, etc.

[0046] In some illustrative aspects, WM 103 may include one or more wireless communication bands and / or channels. For example, WM 103 may include one or more channels in a wireless communication band below 10 GHz (e.g., a 2.4 GHz wireless communication band), one or more channels in a 5 GHz wireless communication band, and / or one or more channels in a 6 GHz wireless communication band. In another example, WM 103 may additionally or alternatively include one or more channels in an mmWave wireless communication band.

[0047] In other respects, WM 103 can include any other type of channel on any other frequency band.

[0048] In some illustrative aspects, device 102 and / or device 140 may include one or more radio devices, including circuitry and / or logic for performing wireless communication between devices 102, 140, and / or one or more other wireless communication devices. For example, device 102 may include one or more radio devices 114, and / or device 140 may include one or more radio devices 144.

[0049] In some illustrative aspects, radio device 114 and / or radio device 144 may include one or more wireless receivers (Rx) including circuitry and / or logic for receiving wireless communication signals, RF signals, frames, blocks, transport streams, packets, messages, data items, and / or data. For example, radio device 114 may include at least one receiver 116, and / or radio device 144 may include at least one receiver 146.

[0050] In some illustrative aspects, radio devices 114 and / or 144 may include one or more wireless transmitters (Tx) including circuitry and / or logic for transmitting wireless communication signals, RF signals, frames, blocks, transport streams, packets, messages, data items, and / or data. For example, radio device 114 may include at least one transmitter 118, and / or radio device 144 may include at least one transmitter 148.

[0051] In some illustrative aspects, radio devices 114 and / or 144, transmitters 118 and / or 148, and / or receivers 116 and / or 146 may include circuitry; logic; radio frequency (RF) components, circuitry, and / or logic; baseband components, circuitry, and / or logic; modulation components, circuitry, and / or logic; demodulation components, circuitry, and / or logic; amplifiers; analog-to-digital and / or digital-to-analog converters; filters, etc. For example, radio devices 114 and / or 144 may include or be implemented as part of a wireless network interface card (NIC), etc.

[0052] In some illustrative aspects, radio devices 114 and / or 144 may be configured to communicate on the 2.4 GHz band, 5 GHz band, 6 GHz band, and / or any other band, such as directional bands, such as millimeter wave bands, 5G bands, S1G bands, and / or any other bands.

[0053] In some illustrative aspects, radio devices 114 and / or 144 may include one or more antennas, or may be associated with one or more antennas.

[0054] In some illustrative aspects, device 102 may include one or more antennas 107, and / or device 140 may include one or more antennas 147.

[0055] Antennas 107 and / or 147 may include any type of antenna suitable for transmitting and / or receiving wireless communication signals, blocks, frames, transport streams, packets, messages, and / or data. For example, antennas 107 and / or 147 may include any suitable configuration, structure, and / or arrangement of one or more antenna elements, components, units, assemblies, and / or arrays. In some aspects, antennas 107 and / or 147 may implement transmission and reception functions using separate transmitting and receiving antenna elements. In some aspects, antennas 107 and / or 147 may implement transmission and reception functions using shared and / or integrated transmitting / receiving elements.

[0056] In some illustrative aspects, device 102 may include controller 124, and / or device 140 may include controller 154. Controller 124 may be configured to perform and / or trigger, prompt, instruct, and / or control device 102 to perform one or more communications to generate and / or transmit one or more messages and / or transmissions, and / or perform one or more functions, operations, and / or processes between devices 102, 140, and / or one or more other devices; and / or controller 154 may be configured to perform and / or trigger, prompt, instruct, and / or control device 140 to perform one or more communications to generate and / or transmit one or more messages and / or transmissions, and / or perform one or more functions, operations, and / or processes between devices 102, 140, and / or one or more other devices, for example, as described below.

[0057] In some illustrative aspects, controllers 124 and / or 154 may include, or may be implemented in part or entirely by, circuitry and / or logic, such as one or more processors, memory circuitry and / or logic, media access control (MAC) circuitry and / or logic, physical layer (PHY) circuitry and / or logic, baseband (BB) circuitry and / or logic, BB processor, BB memory, application processor (AP) circuitry and / or logic, AP processor, AP memory, and / or any other circuitry and / or logic configured to perform the functions of controllers 124 and / or 154, respectively. Alternatively or additionally, one or more functions of controllers 124 and / or 154 may be implemented by logic that may be executed by a machine and / or one or more processors, for example, as described below.

[0058] In one example, controller 124 may include circuitry and / or logic, such as one or more processors including circuitry and / or logic, to cause, trigger, and / or control a wireless device (e.g., device 102) and / or a wireless station (e.g., a wireless STA implemented by device 102) to perform one or more operations, communications, and / or functions, such as those described herein. In one example, controller 124 may include at least one memory, such as one or more processors coupled to it, which may be configured to, for example, store (e.g., at least temporarily store) at least some of the information processed by the one or more processors and / or circuitry, and / or may be configured to store logic used by the processors and / or circuitry.

[0059] In one example, controller 154 may include circuitry and / or logic, such as one or more processors including circuitry and / or logic, to cause, trigger, and / or control a wireless device (e.g., device 140) and / or a wireless station (e.g., a wireless STA implemented by device 140) to perform one or more operations, communications, and / or functions, such as those described herein. In one example, controller 154 may include at least one memory, such as one or more processors coupled to it, which may be configured to, for example, store (e.g., at least temporarily store) at least some of the information processed by one or more processors and / or circuitry, and / or may be configured to store logic to be used by the processors and / or circuitry.

[0060] In some illustrative aspects, at least a portion of the functionality of controller 124 may be implemented as part of one or more elements of radio device 114, and / or at least a portion of the functionality of controller 154 may be implemented as part of one or more elements of radio device 144.

[0061] In other respects, the functionality of controller 124 may be implemented as part of any other element of device 102, and / or the functionality of controller 154 may be implemented as part of any other element of device 140.

[0062] In some illustrative aspects, device 102 may include message processor 128 configured to generate, process, and / or access one or more messages transmitted by device 102.

[0063] In one example, message processor 128 may be configured to generate one or more messages to be sent by device 102, and / or message processor 128 may be configured to access and / or process one or more messages received by device 102, for example, as described below.

[0064] In one example, message processor 128 may include: at least one first component configured to generate a message, for example, in the form of frames, fields, information elements, and / or protocol data units, such as MAC Protocol Data Units (MPDUs); at least one second component configured to convert the message into a PHY Protocol Data Unit (PPDU), for example, by processing the message generated by the at least one first component (e.g., by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message); and / or at least one third component configured to facilitate the transmission of the message via a wireless communication medium (e.g., via a wireless communication channel in a wireless communication band), for example, by applying one or more transmission waveforms to one or more fields of the PPDU. In other aspects, message processor 128 may be configured to perform any other additional or alternative functions and / or may include any other additional or alternative components to generate and / or process the message to be transmitted.

[0065] In some illustrative aspects, device 140 may include message processor 158, which is configured to generate, process, and / or access one or more messages transmitted by device 140.

[0066] In one example, message processor 158 may be configured to generate one or more messages to be sent by device 140, and / or message processor 158 may be configured to access and / or process one or more messages received by device 140, for example, as described below.

[0067] In one example, message processor 158 may include: at least one first component configured to generate a message, for example, in the form of frames, fields, information elements, and / or protocol data units, such as MPDUs; at least one second component configured to convert the message into a PPDU, for example, by processing the message generated by the at least one first component (e.g., by encoding the message, modulating the message, and / or performing any other additional or alternative processing on the message); and / or at least one third component configured to facilitate the transmission of the message via a wireless communication medium (e.g., via a wireless communication channel in a wireless communication band), for example, by applying one or more transmission waveforms to one or more fields of the PPDU. In other aspects, message processor 158 may be configured to perform any other additional or alternative functions and / or may include any other additional or alternative components to generate and / or process messages to be transmitted.

[0068] In some illustrative aspects, message processors 128 and / or 158 may include, or may be implemented in part or in whole by, circuitry and / or logic, such as one or more processors, memory circuitry and / or logic, MAC circuitry and / or logic, PHY circuitry and / or logic, BB circuitry and / or logic, BB processor, BB memory, AP circuitry and / or logic, AP processor, AP memory, and / or any other circuitry and / or logic configured to perform the functions of message processors 128 and / or 158, respectively. Alternatively or additionally, one or more functions of message processors 128 and / or 158 may be implemented by logic that may be executed by a machine and / or one or more processors, for example, as described below.

[0069] In some illustrative aspects, at least a portion of the functionality of message processor 128 may be implemented as part of radio device 114, and / or at least a portion of the functionality of message processor 158 may be implemented as part of radio device 144.

[0070] In some illustrative aspects, at least a portion of the functionality of message processor 128 may be implemented as part of controller 124, and / or at least a portion of the functionality of message processor 158 may be implemented as part of controller 154.

[0071] In other respects, the functionality of message processor 128 may be implemented as part of any other element of device 102, and / or the functionality of message processor 158 may be implemented as part of any other element of device 140.

[0072] In some illustrative aspects, at least a portion of the functionality of controller 124 and / or message processor 128 may be implemented by an integrated circuit, such as a chip, such as a system-on-a-chip (SoC). In one example, the chip or SoC may be configured to perform one or more functions of one or more radio devices 114. For example, the chip or SoC may include one or more elements of controller 124, one or more elements of message processor 128, and / or one or more elements of one or more radio devices 114. In one example, controller 124, message processor 128, and one or more radio devices 114 may be implemented as part of a chip or SoC.

[0073] In other respects, the controller 124, the message processor 128, and / or one or more radio devices 114 may be implemented by one or more additional or alternative elements of the device 102.

[0074] In some illustrative aspects, at least a portion of the functionality of controller 154 and / or message processor 158 may be implemented by an integrated circuit, such as a chip, like a SoC. In one example, the chip or SoC may be configured to perform one or more functions of one or more radio devices 144. For example, the chip or SoC may include one or more elements of controller 154, one or more elements of message processor 158, and / or one or more elements of one or more radio devices 144. In one example, controller 154, message processor 158, and one or more radio devices 144 may be implemented as part of a chip or SoC.

[0075] In other respects, the controller 154, the message processor 158, and / or one or more radio devices 144 may be implemented by one or more additional or alternative elements of the device 140.

[0076] In some illustrative aspects, device 102 and / or device 140 may include one or more STAs, operate thereon, perform their roles, and / or perform one or more of their functions. For example, device 102 may include at least one STA and / or device 140 may include at least one STA.

[0077] In some illustrative aspects, device 102 and / or device 140 may include one or more Extremely High Throughput (EHT) STAs, operate thereas, perform their roles, and / or perform one or more of their functions. For example, device 102 may include one or more EHT STAs, operate thereas, perform their roles, and / or perform one or more of their functions, and / or device 140 may include one or more EHT STAs, operate thereas, perform their roles, and / or perform one or more of their functions.

[0078] In some illustrative aspects, for example, device 102 and / or device 140 may be configured to perform one or more operations and / or functions of Wi-Fi 8STA.

[0079] In other respects, for example, devices 102 and / or 140 may be configured to perform one or more operations and / or functions of Ultra-High Reliability (UHR) STA.

[0080] In other respects, for example, devices 102 and / or 140 may be configured to perform one or more operations and / or functions of any other additional or alternative types of STA.

[0081] In other respects, device 102 and / or device 140 may include any other wireless device and / or station (e.g., WLAN STA, Wi-Fi STA, etc.), as its operation, to perform its role, and / or to perform one or more of its functions.

[0082] In some illustrative aspects, device 102 and / or device 140 may be configured to operate as an access point (AP) (e.g., an EHT AP STA and / or a UHR AP STA), perform its role, and / or perform one or more of its functions.

[0083] In some illustrative aspects, device 102 and / or device 140 may be configured to operate as a non-AP STA (e.g., an EHT non-AP STA and / or a UHR non-AP STA), perform their roles, and / or perform one or more of their functions.

[0084] In other respects, device 102 and / or device 140 may operate as any other additional or alternative device and / or station, perform their roles, and / or perform one or more of their functions.

[0085] In one example, a station (STA) may include a logical entity that is a separate addressable instance of the Media Access Control (MAC) and Physical Layer (PHY) interfaces to the wireless medium (WM). The STA may perform any other additional or alternative functions.

[0086] In one example, an AP may include an entity that contains a Station (STA) and provides the associated STA with access to distribution services via wireless media (WM). The AP may include STA and Distribution System Access Function (DSAF). The AP may perform any other additional or alternative functions.

[0087] In some illustrative aspects, devices 102 and / or 140 can be configured to communicate in an EHT network, a UHR network, and / or any other network.

[0088] In some illustrative aspects, devices 102 and / or 140 may be configured to operate according to one or more specifications, such as including one or more IEEE 802.11 specifications, such as the IEEE 802.11-2020 specification, the IEEE 802.11be specification, and / or any other specifications and / or protocols.

[0089] In some illustrative aspects, device 102 and / or device 140 may include one or more multilink logical entities, as they operate, perform their roles, and / or perform their functions, for example, as described below.

[0090] On the other hand, device 102 and / or device 140 may include any other entity, such as an entity that is not a multi-link logical entity, operating as any other entity, performing the role of any other entity, and / or performing the function of any other entity.

[0091] For example, a multilink logical entity may include a logical entity containing one or more STAs. The logical entity may have a MAC data service interface and a primitive to a logical link control (LLC), as well as a single address associated with that interface, which can be used for communication over a distribution system medium (DSM). For example, the DSM may include a medium or set of media used by the distribution system (DS) for communication between APs, mesh gates, and extended service set (ESS) portals. For example, the DS may include a system for interconnecting a set of basic service sets (BSS) and integrated local area networks (LANs) to create an extended service set (ESS). In one example, a multilink logical entity may allow STAs within the multilink logical entity to have the same MAC address. Multilink entities may perform any other additional or alternative functions.

[0092] In some illustrative aspects, device 102 and / or device 140 may include a multi-link device (MLD), operate therein, perform its role, and / or perform its function. For example, device 102 may include at least one MLD, operate therein, perform its role, and / or perform its function, and / or device 140 may include at least one MLD, operate therein, perform its role, and / or perform its function, for example, as described below.

[0093] For example, an MLD may include a device that is a logical entity capable of supporting more than one associated station (STA) and operating using one or more associated STAs. For instance, an MLD may present a Media Access Control (MAC) data service and a single MAC Service Access Point (SAP) to the Logical Link Control (LLC) sublayer. An MLD may perform any other additional or alternative functions.

[0094] In some illustrative aspects, for example, an infrastructure framework may include (e.g., on one side) multi-link AP logical entities (including APs) and (e.g., on the other side) multi-link non-AP logical entities (including non-APs).

[0095] In some illustrative respects, device 102 and / or device 140 may be configured to operate as an AP MLD, perform its role, and / or perform one or more of its functions.

[0096] In some illustrative respects, device 102 and / or device 140 may be configured to operate as a non-AP MLD, perform its role, and / or perform one or more of its functions.

[0097] In other respects, device 102 and / or device 140 may operate as any other additional or alternative device and / or station, perform their roles, and / or perform one or more of their functions.

[0098] For example, an AP MLD may include an MLD, where each STA associated with the MLD is an AP. In one example, an APMLD may include a multi-link logical entity, where each STA within that multi-link logical entity is an EHT AP. The AP MLD may perform any other additional or alternative functions.

[0099] For example, a non-AP MLD may include an MLD, where each STA associated with the MLD is a non-AP STA. In one example, a non-AP MLD may include a multi-link logical entity, where each STA within that multi-link logical entity is a non-AP STA. A non-AP MLD may perform any other additional or alternative functions.

[0100] In one example, a multi-link infrastructure framework can be configured as an extension of a link operation between two STAs (e.g., an AP and a non-AP STA).

[0101] In some illustrative aspects, controller 124 may be configured to cause, trigger, indicate, and / or control device 102 to operate as AP MLD 131, perform its role, and / or perform one or more of its operations and / or functions, AP MLD 131 including a plurality of AP STAs 133, such as AP STA 135, AP STA 137, and / or AP STA 139. In some aspects, such as Figure 1 As shown, AP MLD 131 may include three AP STAs. In other respects, AP MLD 131 may include any other number of AP STAs.

[0102] In one example, AP STA 135, AP STA 137, and / or AP STA 139 may act as EHT AP STAs, perform their roles, and / or perform one or more of their operations and / or functions. In other respects, AP STA 135, AP STA 137, and / or AP STA 139 may perform any other additional or alternative functions.

[0103] In some illustrative aspects, for example, one or more radio devices 114 may include, for example, radio devices for AP STA 135 to communicate on a first wireless communication frequency channel and / or frequency band (e.g., 2.4 GHz band), as described below.

[0104] In some illustrative aspects, for example, one or more radio devices 114 may include, for example, radio devices for AP STA 137 to communicate on a second wireless communication frequency channel and / or band (e.g., 5 GHz band), as described below.

[0105] In some illustrative aspects, for example, one or more radio devices 114 may include, for example, radio devices for AP STA 139 to communicate on a third wireless communication frequency channel and / or band (e.g., 6 GHz band), as described below.

[0106] In some illustrative aspects, the radio device 114 used by AP 133 can be implemented as a separate radio device. In other aspects, the radio device 114 used by AP 133 can be implemented by one or more shared and / or common radio devices and / or radio components.

[0107] In other respects, controller 124 may be configured to cause, trigger, indicate, and / or control device 102 to operate, perform its role, and / or perform one or more of its operations and / or functions as any other additional or alternative entity and / or STA (e.g., a single STA, multiple STAs, and / or non-MLD entity).

[0108] In some illustrative aspects, controller 154 may be configured to cause, trigger, indicate, and / or control device 140 to operate as MLD 151, perform its role, and / or perform one or more of its operations and / or functions, MLD 151 including a plurality of STAs 153, such as STA 155, STA 157, and / or STA 159. In some aspects, such as Figure 1 As shown, MLD 151 may include three STAs. In other respects, MLD 151 may include any other number of STAs.

[0109] In one example, STA 155, STA 157, and / or STA 159 can act as EHT STAs, perform their roles, and / or perform one or more of their operations and / or functions. In other respects, STA 155, STA 157, and / or STA 159 can perform any other additional or alternative functions.

[0110] In some illustrative aspects, for example, one or more radio devices 144 may include, for example, radio devices for STA 155 to communicate on a first wireless communication frequency channel and / or frequency band (e.g., 2.4 GHz band), as described below.

[0111] In some illustrative aspects, for example, one or more radio devices 144 may include, for example, radio devices for STA 157 to communicate on a second wireless communication frequency channel and / or band (e.g., 5 GHz band), as described below.

[0112] In some illustrative aspects, for example, one or more radio devices 144 may include, for example, radio devices for STA159 to communicate on a third wireless communication frequency channel and / or band (e.g., 6 GHz band), as described below.

[0113] In some illustrative aspects, the radio device 144 used by STA 153 can be implemented as a standalone radio device. In other aspects, the radio device 144 used by STA 153 can be implemented by one or more shared and / or common radio devices and / or radio components.

[0114] In some illustrative aspects, controller 154 may be configured to cause, trigger, indicate, and / or control MLD 151 to operate as a non-AP MLD, perform its role, and / or perform one or more of its operations and / or functions. For example, STA 155, STA 157, and / or STA 159 may operate as a non-AP EHT STA, perform its role, and / or perform one or more of its operations and / or functions.

[0115] In some illustrative aspects, controller 154 may be configured to cause, trigger, indicate, and / or control MLD 151 to operate as an AP MLD, perform its role, and / or perform one or more of its operations and / or functions. For example, STA 155, STA 157, and / or STA 159 may operate as an AP EHT STA, perform its role, and / or perform one or more of its operations and / or functions.

[0116] In other respects, controller 154 may be configured to cause, trigger, indicate, and / or control device 140 to operate, perform its role, and / or perform one or more of its operations and / or functions as any other additional or alternative entity and / or STA (e.g., a single STA, multiple STAs, and / or non-MLD entity).

[0117] refer to Figure 2 It schematically illustrates a multi-link communication scheme 200 that can be implemented according to some illustrative aspects.

[0118] like Figure 2 As shown, the first multi-link logical entity 202 (“Multi-link Logical Entity 1”), such as the first MLD, may include multiple STAs, such as STA 212, STA 214, and STA 216. In one example, AP MLD 131 ( Figure 1 It can perform one or more operations, one or more functions, roles, and / or features of the multi-link logical entity 202.

[0119] like Figure 2As shown, the second multi-link logical entity 240 (“Multi-link Logical Entity 2”), such as the second MLD, may include multiple STAs, such as STA 252, STA 254, and STA 256. In one example, MLD 151 ( Figure 1 It can perform one or more operations, one or more functions, roles, and / or features of the multi-link logical entity 240.

[0120] like Figure 2 As shown, multi-link logical entity 202 and multi-link logical entity 240 can be configured to form and / or set up multiple links and / or communicate on multiple links, such as link 272 between STA 212 and STA 252, link 274 between STA 214 and STA 254, and / or link 276 between STA 216 and STA 256.

[0121] refer to Figure 3 It schematically illustrates a multi-link communication scheme 300 that can be implemented according to some illustrative aspects.

[0122] like Figure 3 As shown, a multi-link AP logical entity 302, such as AP MLD, can include multiple AP STAs, such as AP STA 312, AP STA 314, and AP STA 316. In one example, AP MLD 131 ( Figure 1 It can perform one or more operations, one or more functions, roles, and / or features of the multi-link AP logical entity 302.

[0123] like Figure 3 As shown, a multi-link non-AP logical entity 340, such as a non-AP MLD, can include multiple non-AP STAs, such as non-AP STA 352, non-AP STA 354, and non-AP STA 356. In one example, MLD 151 ( Figure 1 It can perform one or more operations, one or more functions, roles, and / or features of the multi-link non-AP logical entity 340.

[0124] like Figure 3 As shown, the multi-link AP logical entity 302 and the multi-link non-AP logical entity 340 can be configured to form and / or set up multiple links and / or communicate on multiple links, such as, for example, link 372 between AP STA 312 and non-AP STA 352, link 374 between AP STA 314 and non-AP STA 354, and / or link 376 between AP STA 316 and non-AP STA 356.

[0125] For example, such as Figure 3 As shown, the multi-link AP logical entity 302 may include a multi-band AP MLD, which can be configured to communicate on multiple wireless communication frequency bands. For example, as Figure 3 As shown, AP STA 312 can be configured to communicate in the 2.4 GHz band, AP STA 314 can be configured to communicate in the 5 GHz band, and / or AP STA 316 can be configured to communicate in the 6 GHz band. In other respects, AP STA 312, AP STA 314, and / or AP STA 316 can be configured to communicate in any other additional or alternative wireless communication bands.

[0126] Return to reference Figure 1 In some illustrative aspects, device 102 and / or device 140 may be configured to communicate according to a multi-link communication mechanism, for example, as described below.

[0127] In some illustrative aspects, device 102 and / or device 140 may be configured to communicate according to a multilink communication mechanism that can implement one or more operations and / or functions for communication in Enhanced Multilink Single Radio (EMLSR) operating mode, for example, according to the IEEE 802.11 specification and / or the Wi-Fi 7 specification, as described below.

[0128] In some illustrative aspects, for example, according to the IEEE 802.11be specification, the EMLSR operating mode can be defined as including an operating mode that allows a non-AP MLD with multiple receive chains (e.g., when the corresponding STA associated with the non-AP MLD is awake) to listen for initial control frames sent by the AP associated with the AP MLD on a set of enabled links. For example, the initial control frame can be sent by the AP in a non-high-throughput (non-HT) (repeated) PPDU, for example, using a spatial stream. For example, one or more frame exchanges can occur on the link receiving the initial control frame. In other aspects, the EMLSR operating mode can be defined to include any other suitable additional or alternative functionality.

[0129] This document describes some illustrative aspects for wireless communication devices (e.g., wireless communication device 102) operating according to EMLSR operating mode. Other aspects may be implemented for wireless communication devices (e.g., wireless communication device 102) operating according to any other additional or alternative multilink operating mode.

[0130] In some illustrative aspects, device 102 and / or device 140 may be configured to communicate according to an EMLSR operating mode, which may be defined such that when a non-AP MLD (e.g., a non-AP MLD implemented by device 140) enters EMLSR mode, the non-AP MLD may have at least two active links.

[0131] For example, a non-AP MLD operating in EMLSR mode can be allowed to transmit on only one link at a time.

[0132] In some illustrative aspects, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) may have a first active link and a second active link, for example, when operating in EMLSR mode and / or in any other multi-link operation mode, the second active link may be configured differently from the first active link.

[0133] In some illustrative aspects, the first active link and the second active link may have different PHY configurations that can support different PHY rates, for example, as described below.

[0134] In some illustrative aspects, a first active link may be configured according to a first PHY configuration, which includes a first bandwidth, a first nominal modulation and coding scheme (MCS), a first transmit (Tx) power limit setting, and / or one or more first additional or alternative PHY settings.

[0135] For example, the first PHY configuration may support a first PHY rate for data communication in uplink (UL) transmissions, such as to an AP (e.g., an AP implemented by device 102). For example, the first PHY rate may support a first throughput of UL transmissions.

[0136] In some illustrative aspects, a second active link can be configured based on a second PHY configuration, which includes a second bandwidth, a second nominal MCS, a second Tx power limiting setting, and / or one or more second additional or alternative PHY settings.

[0137] For example, the second PHY configuration may support a second PHY rate (e.g., different from the first PHY rate) for data communication in UL transmissions, such as to an AP (e.g., an AP implemented by device 102). For example, the second PHY rate may support a second throughput of the UL transmission, such as a second throughput different from the first throughput.

[0138] In some illustrative aspects, device 140 may be configured to implement one or more operations and / or functions of a multilink communication mechanism, which may be configured to address one or more technical problems of communication on multiple links, for example, during EMLSR operation mode and / or during any other multilink operation mode, for example, as described below.

[0139] For example, an EMLSR operating mode can be implemented to provide a "cost-effective" solution that enables dynamic switching between different links on the same or different frequency bands.

[0140] For example, the EMLSR operating mode can allow a single radio device with multiple receive chains to listen on a set of enabled links, for example, using at least one spatial stream. For instance, an AP can send an initial control frame to a single radio device on a specific link among the enabled links, utilizing a spatial stream. According to this example, the single radio device can detect the initial control frame on the specific link and can, for example, switch to that specific link carrying all its spatial streams, to receive data from the AP using all streams.

[0141] For example, an AP can perform multi-link, multi-radio device functionality, which allows the AP to receive any transmission from any link. According to this example, the AP can receive data transmissions sent by a single radio device, for example, on any enabled link.

[0142] In some illustrative aspects, for example, under certain conditions, use cases, and / or scenarios, the EMLSR operating mode can be utilized to improve Wi-Fi system performance and / or latency.

[0143] For example, the EMLSR operating mode can be used to improve overall throughput time (TpT) and / or latency, for example, by intelligently utilizing one or more multi-links. For instance, when a non-AP STA is in EMLSR operating mode and one link is busy, sending data on a second link of the non-AP STA may (e.g., will) increase TpT ​​and / or reduce latency, for example, compared to a multi-link (ML) single-user (SU) STA that may not be allowed to use another link.

[0144] In some illustrative aspects, for example, in some use cases and / or scenarios, continuous operation of STA in EMLSR operating mode may be disadvantageous, for example, as described below.

[0145] For example (e.g., in the case of continuous use of EMLSR operating mode under all conditions) EMLSR operating mode may have one or more constraints that may affect the TpT, delay, power, and / or any other additional or alternative system performance criteria for the entire system.

[0146] For example, (for example, when continuously using EMLSR operating mode) there may be one or more conditions and / or constraints that may result in the Wi-Fi system performance not being improved.

[0147] For example, (for example, when continuously using EMLSR operating mode) there may be one or more conditions and / or constraints that may cause Wi-Fi system performance to degrade, such as a decrease in average throughput.

[0148] refer to Figure 4 It schematically illustrates operation 400 according to the EMLSR operating mode to illustrate one or more technical aspects that can be addressed according to some illustrative aspects.

[0149] For example, the EMLSR operating mode may have one or more constraints, which may lead to performance degradation, for example, as described below.

[0150] For example, continuous operation in EMLSR operating mode may lead to increased EMLSR signaling overhead and / or increased air fill duration, for example, as described below.

[0151] For example, continuous operation in MLSR mode may lead to frequent EMLSR conversion delays, as described below.

[0152] For example, such as Figure 4 As shown, the STA 440 can operate in EMLSR mode.

[0153] For example, STA 440 can be in a listening state, which can be characterized by an active link (1x1), such as on link 403.

[0154] For example, such as Figure 4 As shown, AP 402 can send trigger frames to STA 440, such as Multi-User (MU) Request Transmission (RTS) (MU-RTS) 420.

[0155] For example, STA 440 can be in a listening state, for instance, before receiving MU-RTS 420 from AP 402.

[0156] For example, the STA 440 can move from a listening state to an active state, which can be characterized by at least two active links (2x2).

[0157] For example, as shown by arrow 410, STA 440 can move from the listening state to the active state for data frame exchange 424.

[0158] For example, such as Figure 4As shown, the STA 440 can have an EMLSR transition delay for the transition from a listening state to an active state. For example, as Figure 4 As shown, AP 402 may need to add padding 422, for example, to account for the transition latency of STA 440 from listening state to active state. This padding 422 may increase EMLSR overhead.

[0159] For example, as shown by arrow 412, STA 440 can switch back to listening mode, for example, after transmitting data frame exchange 424. For example, as Figure 4 As shown, after frame exchange 424, STA 440 may also have a transition delay 426 when moving back to listening state.

[0160] For example, continuous operation in EMLSR mode may cause one or more potential beacon frame reception problems.

[0161] For example, such as Figure 4 As shown, for example, when beacon 428 on link 405 overlaps with data frame exchange 424 on link 403, STA 440 may miss beacon 428 in link 405.

[0162] For example, continuous operation in EMLSR operating mode may cause EMLSR "deafness".

[0163] For example, continuous operation in EMLSR operating mode can result in relatively high power consumption. For example, multiple receive chains can be operated when using EMLSR operating mode. For example, operating multiple receive chains can lead to increased power consumption compared to non-EMLSR multi-link operation (MLO) mode.

[0164] Return to reference Figure 1 In some illustrative aspects, device 102 and / or device 140 may be configured to implement one or more operations and / or functions of a selective EMLSR enable / disable mechanism, which may be configured to selectively enable and / or selectively disable an EMLSR operating mode, for example, as described below.

[0165] In some illustrative aspects, the selective EMLSR enable / disable mechanism can be configured to, for example, selectively enable and / or selectively disable the EMLSR operating mode based on one or more EMLSR enable / disable criteria (also known as "entry / exit EMLSR transformation criteria"), as described below.

[0166] In some illustrative aspects, a selective EMLSR enable / disable mechanism may include, for example, activating the operation of a non-AP MLD in the EMLSR operation mode of an MLO on multiple links with an AP MLD, based on determining that the EMLSR enable criteria are met, as described below.

[0167] In some illustrative aspects, a selective EMLSR enable / disable mechanism may include, for example, switching a non-AP MLD from EMLSR operating mode to a non-EMLSR MLO mode based on determining that EMLSR disabling criteria are met, as described below.

[0168] In some illustrative aspects, the EMLSR enable / disable criteria can be specific to one or more use cases, for example, as described below.

[0169] In some illustrative aspects, the EMLSR enable / disable criterion can be configured, for example, to allow non-AP MLDs to optionally enable the EMLSR operating mode (e.g., in use cases where the EMLSR operating mode can be utilized) to improve overall system TpT, latency, power consumption, and / or any other additional or alternative performance parameters, for example, as described below.

[0170] In some illustrative aspects, device 102 and / or device 140 may be configured to implement one or more operations and / or functions of a selective EMLSR enable / disable mechanism, which may be configured as a technical solution to support improved (e.g., optimized) system performance, for example, as described below.

[0171] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to determine whether the EMLSR enable criteria are met, for example, as described below.

[0172] In some illustrative aspects, EMLSR enable criteria can be based on one or more predefined enable criteria corresponding to one or more enable criterion parameters, for example, as described below.

[0173] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to activate the operation of the non-AP MLD in the EMLSR operation mode of the MLO on multiple links with the AP MLD, for example, based on determining that the EMLSR enable criteria are met, as described below.

[0174] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to determine, for example, whether EMLSR deactivation criteria are met during EMLSR operation mode, as described below.

[0175] In some illustrative aspects, EMLSR deactivation criteria can be based on one or more predefined deactivation criteria corresponding to one or more deactivation criterion parameters, for example, as described below.

[0176] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to switch the non-AP MLD from EMLSR operating mode to non-EMLSR MLO mode based on determining that EMLSR deactivation criteria are met, for example, as described below.

[0177] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct a non-AP MLD implemented by device 140, for example, to send an EMLSR enable instruction to the AP MLD based on determining that the EMLSR enable criteria are met, as described below.

[0178] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140, for example, to send an EMLSR deactivation instruction to the AP MLD based on determining that the EMLSR deactivation criteria are met, for example, as described below.

[0179] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine that EMLSR enable criteria are met based on determining that multiple predefined enable criteria corresponding to multiple predefined enable criterion parameters are met, for example, as described below.

[0180] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether EMLSR enable criteria are met based solely on determining that all of a plurality of predefined enable criteria are met, as described below.

[0181] In some illustrative aspects, one or more predefined enable criteria may include other device channel-load-by-others enable criteria, for example, as described below.

[0182] In some illustrative aspects, the other device channel load enable criterion can be based on the other device channel load parameter, which represents the channel load caused by other devices transmitting traffic on channels not used by AP STAs to communicate with AP MLDs, for example, as described below.

[0183] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine that other device channel load enable criteria are met based on the determination that the value of other device channel load parameter is greater than other device channel load threshold, for example, as described below.

[0184] In some illustrative aspects, one or more predefined enabling criteria may include receive performance enabling criteria, which may be based on, for example, receive performance parameters, as described below.

[0185] In some illustrative aspects, the receive performance parameters can be configured to represent the performance level of receiving communication from an AP MLD at a non-AP MLD, for example, as described below.

[0186] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine that a reception performance enable criterion is met based on the determination that the value of a reception performance parameter is greater than a reception performance threshold, for example, as described below.

[0187] In some illustrative aspects, one or more predefined enable criteria may include power-based enable criteria, which may be based on, for example, power-based parameters, as described below.

[0188] In some illustrative aspects, power-based parameters can be configured to represent the relationship between a first power consumption level and a second power consumption level, for example, as described below.

[0189] In some illustrative aspects, the first power consumption level may include the power consumption of a non-AP MLD transmitting a specific traffic with an APMLD in EMLSR operating mode, for example, as described below.

[0190] In some illustrative aspects, the second power consumption level may include the power consumption of a non-AP MLD transmitting specific traffic with an APMLD in a non-EMLSR MLO mode, for example, as described below.

[0191] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether a power-based enable criterion is met, for example, as described below, based on determining that a first power consumption level is less than a second power consumption level by determining the value of a power-based parameter.

[0192] In some illustrative aspects, one or more predefined enable criteria may include delay-based enable criteria, which may be based on, for example, delay-based parameters, as described below.

[0193] In some illustrative aspects, the delay-based parameters can be configured to represent the relationship between the first delay and the second delay, for example, as described below.

[0194] In some illustrative aspects, the first delay may include the delay in transmitting specific traffic with the AP MLD in EMLSR operating mode, for example, as described below.

[0195] In some illustrative aspects, the second delay may include the delay in transmitting specific traffic with the AP MLD in non-EMLSR MLO mode, for example, as described below.

[0196] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether a delay-based enabling criterion is met, for example, as described below, based on determining the value of a delay-based parameter indicating that a first delay is less than a second delay.

[0197] In some illustrative aspects, one or more predefined enable criteria may include self-interference enable criteria, which may be based on, for example, self-interference parameters, as described below.

[0198] In some illustrative aspects, the self-interference parameter can indicate whether self-interference from at least one co-located component of a non-AP MLD exists on at least one of a plurality of links, for example, as described below.

[0199] In some illustrative aspects, at least one co-located component may include a co-located wireless communication interface, for example, as described below.

[0200] In some illustrative aspects, at least one co-located component may include a co-located electric circuit clock, for example, as described below.

[0201] In other respects, at least one co-located component may include any other additional or alternative components.

[0202] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine that self-interference enable criteria are met based on determining that self-interference parameters indicate that there is no self-interference on any of the multiple links, for example, as described below.

[0203] In some illustrative aspects, one or more predefined enable criteria may include operating mode enable criteria, which may be based on, for example, operating mode parameters, as described below.

[0204] In some illustrative aspects, the operating mode parameters can be configured to indicate whether wireless communication with other devices should be performed on at least one of a plurality of links, for example, as described below.

[0205] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine whether wireless communication with other devices will be performed on any of the multiple links based on determined operating mode parameters, and to determine whether operating mode enable criteria are met, for example, as described below.

[0206] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine that EMLSR deactivation criteria are met based on determining that at least one of a plurality of predefined deactivation criteria is met, for example, as described below.

[0207] In some illustrative aspects, one or more predefined deactivation criteria may include other device channel load deactivation criteria, which may be based on, for example, other device channel load parameters, as described below.

[0208] In some illustrative aspects, other device channel load parameters can be configured to represent the channel load caused by other devices transmitting traffic on channels not used by AP STAs for communication with AP MLD, for example, as described below.

[0209] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine that other device channel load deactivation criteria are met based on the determination that the value of other channel load parameters is lower than other device channel load thresholds, for example, as described below.

[0210] In some illustrative aspects, one or more predefined deactivation criteria may include reception performance deactivation criteria, which may be based on, for example, reception performance parameters, as described below.

[0211] In some illustrative aspects, the receive performance parameters can be configured to represent the performance level of receiving communication from an AP MLD at a non-AP MLD, for example, as described below.

[0212] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine that a reception performance deactivation criterion is met based on the determination that the value of a reception performance parameter is below a reception performance threshold, for example, as described below.

[0213] In some illustrative aspects, one or more predefined deactivation criteria may include power-based deactivation criteria, which may be based on, for example, power-based parameters, as described below.

[0214] In some illustrative aspects, power-based parameters can be configured to represent the relationship between a first power consumption level and a second power consumption level, for example, as described below.

[0215] In some illustrative aspects, the first power consumption level may include the power consumption of a non-AP MLD transmitting a specific traffic with an APMLD in EMLSR operating mode, for example, as described below.

[0216] In some illustrative aspects, the second power consumption level may include the power consumption of a non-AP MLD transmitting specific traffic with an APMLD in a non-EMLSR MLO mode, for example, as described below.

[0217] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether a power-based deactivation criterion is met, for example, as described below, based on determining that a second power consumption level is less than a first power consumption level by determining the value of a power-based parameter.

[0218] In some illustrative aspects, one or more predefined deactivation criteria may include a time-based deactivation criterion, which may be based on, for example, a time-based parameter, as described below.

[0219] In some illustrative aspects, the delay-based parameters can be configured to represent the relationship between the first delay and the second delay, for example, as described below.

[0220] In some illustrative aspects, the first delay may include the delay in transmitting specific traffic with the AP MLD in EMLSR operating mode, for example, as described below.

[0221] In some illustrative aspects, the second delay may include the delay in transmitting specific traffic with the AP MLD in non-EMLSR MLO mode, for example, as described below.

[0222] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether a delay-based deactivation criterion is met, such as, based on determining the value of a delay-based parameter indicating that a second delay is less than a first delay.

[0223] In some illustrative aspects, one or more predefined deactivation criteria may include self-interference deactivation criteria, which may be based on, for example, self-interference parameters, as described below.

[0224] In some illustrative aspects, the self-interference parameter can be configured to indicate the presence of self-interference from at least one co-located component of a non-AP MLD on at least one of the multiple links, for example, as described below.

[0225] In some illustrative aspects, at least one co-located component may include a co-located wireless communication interface, for example, as described below.

[0226] In some illustrative aspects, at least one co-located component may include a co-located circuit clock, for example, as described below.

[0227] In other respects, at least one co-located component may include any other component.

[0228] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine that self-interference is present on at least one of a plurality of links based on a determined self-interference parameter indicating that self-interference exists, to determine that self-interference deactivation criteria are met, for example, as described below.

[0229] In some illustrative aspects, one or more predefined deactivation criteria may include operating mode deactivation criteria, which may be based on, for example, operating mode parameters, as described below.

[0230] In some illustrative aspects, the operating mode parameter can be configured to indicate whether wireless communication with other devices should be performed on at least one of a plurality of links, for example, as described below.

[0231] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLD implemented by device 140, for example, to determine whether wireless communication with other devices will be performed on at least one of a plurality of links based on determined operating mode parameters, and to determine whether operating mode deactivation criteria are met, for example, as described below.

[0232] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to monitor (e.g., monitor in real time) one or more deactivation criterion parameters, such as those described below, for example, during operation of the non-AP MLD in EMLSR operating mode.

[0233] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct the non-AP MLD implemented by device 140 to monitor (e.g., monitor in real time) one or more enabling standard parameters, such as those described below, during operation of the non-AP MLD in a non-EMLSR MLO mode.

[0234] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine whether EMLSR enable criteria are met based solely on determining that all of a plurality of predefined enable criteria are met, as described below.

[0235] In some illustrative aspects, controller 154 may be configured to control, trigger, prompt, and / or instruct non-AP MLDs implemented by device 140, for example, to determine that EMLSR deactivation criteria are met based on determining that at least one of a plurality of predefined deactivation criteria is met, for example, as described below.

[0236] In some illustrative aspects, device 102 and / or device 140 may be configured to implement one or more operations and / or functions of a selective EMLSR enable / disable mechanism, which may be configured to dynamically enable / disable EMLSR operating modes, for example, based on one or more EMLSR enable / disable criteria, as described below.

[0237] In some illustrative aspects, device 102 and / or device 140 may be configured to implement one or more operations and / or functions of a selective EMLSR enable / disable mechanism, which may be configured to dynamically enable an EMLSR operating mode, for example, based on determining that an EMLSR enable criterion is met, as described below.

[0238] In some illustrative aspects, device 102 and / or device 140 may be configured to implement one or more operations and / or functions of a selective EMLSR enable / disable mechanism, which may be configured to, for example, dynamically disable an EMLSR operating mode based on determining that an EMLSR disabling criterion is met, as described below.

[0239] In some illustrative aspects, a selective EMLSR enable / disable mechanism can be configured to, for example, enable EMLSR operating mode when one or more (e.g., some or all) EMLSR initiation criteria (also known as "entry conversion criteria") are met, as described below.

[0240] In some illustrative aspects, the selective EMLSR enable / disable mechanism can be configured, for example, to enable the EMLSR operating mode only when all entry conversion criteria are met, as described below.

[0241] In some illustrative aspects, the selective EMLSR enable / disable mechanism can be configured to, for example, disable the EMLSR operating mode when at least one EMLSR disabling criterion (also known as the "exit conversion criterion") is met, as described below.

[0242] In some illustrative aspects, the selective EMLSR enable / disable mechanism can be configured to: exit EMLSR operating mode, for example, when EMLSR operating mode is active; or, for example, when EMLSR operating mode is inactive, such as when at least one exit conversion criterion is met, choose not to enter EMLSR operating mode, for example, as described below.

[0243] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism may include, for example, other device channel load enable / disable criteria, which may be based on, for example, other device channel load parameters (“other device channel load (occupancy)”), which may represent the channel load caused by other devices transmitting traffic on channels not used by AP MLD for communication with AP MLD.

[0244] In one example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can measure Wi-Fi components that can be used to determine the "other device channel load (occupancy)" parameter on the link, which can be used in non-EMLSR MLO mode (e.g., in ML SU mode), such as when a non-AP ML is operating in non-EMLSD MLO mode.

[0245] In another example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can determine the "Other Device Channel Load (Occupancy)" parameter, for example, based on received AP channel load measurements that can be advertised in beacons sent by the AP. For example, the channel load from the AP can be based on or may take into account traffic from the non-AP MLD. For example, the non-AP MLD can be configured to determine the "Other Device Channel Load" parameter, for example, by subtracting the traffic from the non-AP MLD from the AP channel load measurements.

[0246] For example, compared to non-EMLSR MLO mode, such as during EMLSR operation mode, EMLSR TpT overhead and / or EMLSR deafness may lead to a decrease in EMLSR TpT. Based on this example, when there is some channel load on the first link, EMLSR operation mode can obtain more TpT ​​from the second link.

[0247] In some illustrative aspects, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) may determine whether other device channel load criteria are met, for example, based on a comparison between the values ​​of other device channel load parameters and other device channel load thresholds, as described below.

[0248] For example, if a non-AP MLD is operating on a link in non-EMLSR MLO mode and "Other device channel load" = X, the maximum TpT of the non-AP MLD on that link is expected to decrease.

[0249] In one example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can be defined to operate outside of EMLSR operating mode (not enter EMLSR operating mode), for example, when the value of the other device channel load parameter is equal to or lower than the other device channel load threshold (MIN EMLSR CHANNEL LOAD threshold), such as when the “other device channel load” parameter is <= MIN EMLSR CHANNEL LOAD threshold.

[0250] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can choose not to operate in EMLSR operating mode (not to enter EMLSR operating mode), for example, to remain in non-EMLSR MLO mode if it is already in non-EMLSR MLO mode, or to exit EMLSR mode if it is already in EMLSR operating mode.

[0251] For example, the MIN EMLSR CHANNEL LOAD threshold can be configured to represent the minimum channel load that is not expected to improve TpT ​​if the system is moved to EMLSR operating mode, for example due to reduced EMLSR standard overhead, media synchronization, failure to switch to another link, and / or any other technical effects.

[0252] In one example, it can be defined that, for instance, when the value of the other device channel load parameter is greater than the other device channel load threshold (MIN EMLSR CHANNEL LOAD threshold) (e.g., when "other device channel load" > MIN EMLSR CHANNEL LOAD threshold), a non-AP MLD (e.g., a non-AP MLD implemented by device 140) is allowed to operate in EMLSR operating mode. For example, non-AP MLDs can be allowed to operate in EMLSR operating mode, for instance, assuming that better results can be obtained using EMLSR operating mode with two links.

[0253] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can be configured to collect channel load results over time and make decisions at each time period (denoted as T).

[0254] For example, channel load results can be filtered, such as an average filter and / or filters like those provided with more gain for the latest results compared to older results. Based on this example, the filtered results can be compared to the MINEMLSR CHANNEL LOAD threshold.

[0255] For example, a non-AP MLD (such as a non-AP MLD implemented by device 140) supports selectively enabling / disabling EMLSR operating mode based on other channel load parameters. This non-AP MLD can, for example, choose not to enter EMLSR operating mode in the following situations:

[0256] • Relatively favorable conditions, such as Received Signal Strength Indicator (RSSI) > -60 dBm, with medium to high traffic on links in frequency bands not supported by the AP MLD (e.g., 5G Wi-Fi bands and / or 6G Wi-Fi bands, and / or other bands); and

[0257] • The detected channel load of other devices is approximately 0, which could indicate that there is traffic only between non-AP MLDs and APs, for example, there is no interference.

[0258] For example, a non-AP MLD (such as a non-AP MLD implemented by device 140) supports selectively enabling / disabling EMLSR operating mode based on other device channel load parameters. This non-AP MLD can, for example, choose to enter EMLSR operating mode in the following situations:

[0259] • Increased channel load on other devices (e.g., other STAs) transmitting or receiving on the same link.

[0260] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism may include, for example, a receive performance enable / disable criterion (good or bad receive criterion), which may be based on, for example, a receive performance parameter that represents the performance level of receiving communication from an AP MLD at a non-AP MLD.

[0261] In some illustrative aspects, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) may determine that the reception performance enable criterion is met, for example, based on the determination that the value of the reception performance parameter is greater than the reception performance threshold.

[0262] For example, when the value of the receive performance parameter is greater than the receive performance threshold, a non-AP MLD can enter EMLSR operation mode.

[0263] For example, the receive performance threshold can be set to indicate a relatively high performance level for receiving communication from an AP MLD at a non-AP MLD.

[0264] In some illustrative aspects, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can, for example, determine that the reception performance deactivation criteria are met based on the fact that the value of the reception performance parameter is below the reception performance threshold.

[0265] For example, when the value of the receive performance parameter is below the receive performance threshold (which may indicate that the performance level of receiving communication from the AP MLD at a non-AP MLD is relatively low), the non-AP MLD can switch from EMLSR operating mode to non-EMLSRMLO mode (e.g., ML SU operating mode) or can choose to remain in non-EMLSR MLO mode.

[0266] For example, the receive performance enable criterion (good reception) can be identified based on one or more of the following parameters:

[0267] • The RSSI level may be higher than the predefined RSSI threshold (good RSSI threshold);

[0268] • There are probably virtually no beacons missing;

[0269] • The data rate may be higher than the data rate threshold (good data rate threshold), and the packet error rate (PER) may be lower than the PER threshold (good PER threshold). For example, the data rate can be measured as a function of MCS, number of spatial streams (NSS), guard interval (GI), BW, and / or any other additional or alternative parameters.

[0270] For example, the reception performance decommissioning criteria (poor reception) can be identified based on one or more of the following parameters:

[0271] • The RSSI level may be below the predefined RSSI threshold (bad RSSI threshold);

[0272] • A lost beacon may be detected on one or both of the EMLSR links;

[0273] • The data rate may be below the data rate threshold (poor data rate threshold), and the PER may be below the PER threshold (low PER threshold). For example, the data rate can be measured as a function of MCS, NSS, GI, BW, and / or any other additional or alternative parameters. For example, in this case, switching to two spatial streams (e.g., through two antennas) may (e.g., will) improve communication reception at the non-AP MLD.

[0274] For example, in the event of a beacon loss during EMLSR operation, it can be identified whether the beacon was not received due to poor reception conditions or due to EMLSR beacon reception constraints.

[0275] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) can be configured to collect reception performance results over time and make decisions at each time period (e.g., time period T).

[0276] For example, reception performance results can be filtered using one or more filters, such as an average filter and / or filters that provide more gain for the latest results compared to older results. Following this example, the results of the filters can be compared to “good reception” and / or “poor reception” thresholds, for example, to identify whether reception performance enable / disable criteria are met. For instance, reception performance enable / disable criteria could be based on whether the performance level of receiving communication from an AP MLD at a non-AP MLD is identified as “good reception” or “poor reception.”

[0277] For example, non-AP MLD (e.g., non-AP MLD implemented by device 140) supports selectively enabling / disabling the EMLSR operation mode based on other device channel load parameters. For example, in the case of adding attenuation on the link and / or when the non-AP MLD moves away from the AP MLD (e.g., before the RSSI on the link becomes low), the non-AP MLD can choose to exit the EMLSR operation mode.

[0278] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism can include, for example, a per-link traffic criterion that can be used in the EMLSR operation mode, such as an exit transition criterion.

[0279] For example, the per-link traffic criterion can be based on a per-link traffic parameter that can verify whether the traffic between the AP MLD and the non-AP MLD is distributed across both links of the non-AP MLD or mainly or entirely on one of the links.

[0280] For example, the traffic on the link can be measured in various ways. For example, the traffic can be measured, for example, by counting the Tx and / or Rx bytes per link, counting the PPDU transmissions and / or receptions per link, counting the frames per link, and / or based on any other additional or alternative parameters.

[0281] For example, the traffic can be affected by the data rate (e.g., directly affected), such as the data rate measured by, for example, MCS, NSS, GI, and / or BW. According to this example, a link with a higher data rate may be able to transmit more data.

[0282] For example, when the value of the per-link traffic percentage parameter is less than the per-link traffic percentage threshold (MINTRAFFIC PERCENTAGE ON ONE LINK THR) (e.g., the traffic percentage on the link < MIN TRAFFIC PERCENTAGE ON ONE LINK THR, or the traffic percentage on the link > (100 - MIN TRAFFIC PERCENTAGE ON ONE LINK THR)), it can be determined that one of the links of the non-AP MLD is hardly used, while the other link of the non-AP MLD is used most of the time.

[0283] For example, a non-AP MLD can be configured to, for example, opt out of the EMLSR operating mode based on determining the traffic percentage on a link <MIN TRAFFICPERCENTAGE ON ONE LINK THR, or the traffic percentage on a link>(100 - MIN TRAFFIC PERCENTAGE ONONE LINK THR).

[0284] For example, the per-link traffic percentage threshold can be defined as a function of traffic. In one example, a first threshold can be defined for latency traffic while a second threshold can be defined for TpT traffic.

[0285] For example, a non-AP MLD (e.g., the non-AP MLD implemented by device 140) can be configured to collect measured traffic results over time and make a decision at each time period (e.g., time period T).

[0286] For example, the measured traffic results can be filtered by filters such as an average filter and / or filters that provide more gain for the latest results compared to the old results. According to this example, the results of the filters can be compared with the MIN TRAFFIC PERCENTAGE ON ONE LINK threshold and / or the results of (100 - MIN TRAFFIC PERCENTAGE ON ONELINK THR), for example, to identify whether the non-AP MLD is required to opt out of the EMLSR operating mode.

[0287] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism can include, for example, a power-based enable criterion that can be based on a power-based parameter representing the relationship between the power consumption of a non-AP MLD (e.g., the non-AP MLD implemented by device 140) for transmitting a specific traffic with an AP MLD in the EMLSR operating mode and the non-EMLSR MLO mode.

[0288] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism can include, for example, a latency-based enable / disable criterion that is based on a latency-based parameter representing the relationship between the latency of transmitting a specific traffic with an AP MLD in the EMLSR operating mode and the non-EMLSR MLO mode.

[0289] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism can include, for example, power / delay-based enable / disable criteria, e.g., power vs. TpT criteria, as described below, for example.

[0290] For example, in certain states, a non-AP MLD may prefer to save power and thus may prefer to operate in a non-EMLSR mode.

[0291] For example, a non-AP MLD can include multiple receive chains, e.g., these receive chains can be kept open to receive an initial control frame during an EMLSR operation mode. According to this example, the non-AP MLD may prefer to move to a low power state (e.g., similar to a traditional SU mode) to reduce its power consumption level, for example.

[0292] For example, the non-AP MLD can remain in the EMLSR operation mode and turn off one of its links and its corresponding receive chain, e.g., by moving the link to a sleep state, e.g., by sending a power save (PS) indication (PS = 1) to the AP. However, this state may not be advantageous because the non-AP MLD may still be operating in the EMLSR operation mode without the benefits of the EMLSR operation mode.

[0293] For example, e.g., when there is traffic that requires delay and / or when operating high TpT traffic on a link with channel load, the non-AP MLD may prefer to operate in the EMLSR operation mode.

[0294] For example, it can be determined that the traffic TpT is less than a predefined low traffic threshold (LOW TRAFFIC threshold), e.g., traffic TpT < LOW TRAFFIC threshold. According to this example, being in the EMLSR operation mode may be disadvantageous because using more links may consume more power.

[0295] For example, e.g., when the traffic TpT < LOW TRAFFIC threshold, the non-AP MLD can determine to operate in a non-EMLSR MLO mode, e.g., in an ML SU mode, to reduce power consumption, for example.

[0296] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) supports selectively enabling / disabling EMLSR operation mode based on other device channel load parameters. The non-AP MLD can operate in EMLSR operation mode and can, for example, choose to exit EMLSR operation mode or remain in EMLSR operation mode based on one or more different TpT scenarios (e.g., no TpT, low TpT, high TpT, voice call, video call, video and voice (collaboration) scenario and / or any other additional or alternative scenario).

[0297] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) supports selectively enabling / disabling EMLSR operation mode based on channel load parameters of other devices. This non-AP MLD, for example, can choose whether to enter EMLSR operation mode after being associated with an AP MLD. For example, the non-AP MLD can choose whether to enter or remain in EMLSR operation mode based on data TpT, for example, under good link conditions, such as with or without channel load.

[0298] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism may include, for example, a self-interference enable criterion, which may be based on a self-interference parameter. For example, the self-interference parameter may indicate whether self-interference (also referred to as “internal channel interference”) from at least one co-located component is present on at least one of a plurality of links between a non-AP MLD (e.g., a non-AP MLD implemented by device 140) and an AP.

[0299] In one example, a non-AP MLD may be subject to interference, which could be caused by another non-Wi-Fi technology, such as a co-located wireless communication interface and / or interference from any other additional or alternative co-located components.

[0300] In another example, the non-AP MLD may be subject to interference, which could be caused by the activation of specific components, such as the co-located circuit clock and / or any other additional or alternative co-located components.

[0301] For example, the occurrence of self-interference can be predetermined. According to this example, a non-AP MLD can be configured to operate in a non-EMLSR mode, for example, once channel interference is activated and begins to interfere with one of the EMLSR links. For example, the non-AP MLD can choose to exit from EMLSR operation mode to a non-EMLSR MLO mode, such as exiting to ML SU mode, to communicate on a non-EMLSR MLO channel unaffected by interference.

[0302] In some illustrative aspects, one or more EMLSR enable / disable criteria that can be implemented by a selective EMLSR enable / disable mechanism may include, for example, an operation mode enable criterion, which may be based on operation mode parameters. For example, operation mode parameters may indicate whether wireless communication with other devices should be performed on at least one of a plurality of links in an EMLSR operation mode.

[0303] In some illustrative aspects, a non-AP MLD (such as a non-AP MLD implemented by device 140) can determine whether it meets the operation mode enable criteria based on the determination of operation mode parameters indicating that it will not wirelessly communicate with other devices on any of the multiple links in the EMLSR operation mode.

[0304] For example, when a non-AP MLD needs to operate on different links for extended periods for one or more other Wi-Fi networks, the non-AP MLD may not be able to operate in EMLSR mode to listen on two links. For instance, a non-AP MLD might be required to operate as a multi-MAC STA, a peer-to-peer (P2P) STA, a software-enabled access point (SoftAP), and / or any other type of STA that can be enabled to operate on different links for extended periods.

[0305] For example, a non-AP MLD can perform one or more other Wi-Fi operations using one or more (e.g., all) receive and transmit chains. According to this example, during this time, the non-AP MLD may be unable to operate in EMLSR operating mode to listen on two links, for example, even if the links are the same. Therefore, in this case, the non-AP MLD can (e.g., will) exit EMLSR operating mode, or can utilize the EMLSR availability period, for example, by using a Target Wake Time (TWT) mechanism, a Power Saving (PS) mechanism, and / or any other additional or alternative mechanism.

[0306] For example, a non-AP MLD (e.g., a non-AP MLD implemented by device 140) supports selectively enabling / disabling the EMLSR operating mode based on other device channel load parameters. The non-AP MLD can operate in EMLSR operating mode and can optionally exit EMLSR operating mode, for example, once the P2P function or soft AP function is activated, it can optionally exit EMLSR operating mode.

[0307] refer to Figure 5 It schematically illustrates the state diagram 500 for enabling / disabling EMLSR operating modes based on some illustrative aspects.

[0308] For example, non-AP MLD (e.g., by device 140) Figure 1The non-AP MLD implemented can perform one or more operations of state diagram 500.

[0309] For example, such as Figure 5 As shown, a non-AP MLD may be in ML mode, such as multi-link (ML) single-user (SU) mode.

[0310] For example, a non-AP MLD can enter EMLSR operating mode, for example, based on determining that one or more (e.g., all) of a plurality of predefined EMLSR enable criteria (“entry conversion criteria”) are met.

[0311] For example, as shown by arrow 503, a non-AP MLD can switch to EMLSR operation mode when the EMLSR enable criteria are met (good EMLSR conditions).

[0312] For example, a non-APMLD can exit EMLS operation mode when at least one of a plurality of EMLS deactivation criteria (“exit conversion criteria”) is met.

[0313] For example, as shown by arrow 505, the STA can switch to non-EMLSR MLO mode when at least one EMLSR deactivation criterion is met (poor EMLSR condition).

[0314] For example, a non-AP MLD can determine not to enter EMLSR operating mode if at least one of the EMLSR deactivation criteria is met.

[0315] For example, a non-AP MLD can use entry transition criteria, such as to enter or exit EMLSR operating mode, and / or use exit transition criteria, such as to exit EMLSR operating mode, for example, to operate under conditions that can optimize overall system performance, such as by obtaining TpT and / or latency.

[0316] For example, a non-AP MLD can use one or more of the following criteria as entry and / or exit criteria to convert between non-EMLSR mode and EMLS operating mode:

[0317] • Good or poor reception. For example, a non-AP MLD can enter EMLSR operating mode under good reception conditions, as described above. For example, a non-AP MLD can exit or not enter EMLSR operating mode under poor reception conditions, as described above.

[0318] • "Other device channel load (occupancy)". For example, when there is channel load exceeding a predetermined threshold (e.g., excluding load generated by non-AP MLDs), a non-AP MLD can enter EMLSR operation mode, as described above.

[0319] • Traffic per link. For example, if the data traffic of the AP MLD is not split across the two links, the non-AP MLD can exit EMLSR operation mode, for example, as described above.

[0320] • Power and TpT / Delay. For example, a non-AP MLD can enter or exit EMLSR operating mode, for example, as a function of power, TpT, delay, and / or any other additional or alternative criteria, for example, as described above.

[0321] • Internal channel interference. For example, if there is high interference from at least one co-located component (on the same board or die) on one of the channels (links), a non-AP MLD can exit EMLSR operation mode, for example, as described above.

[0322] • Device operating mode. For example, when other Wi-Fi operations require one of the links for extended periods (e.g., multi-MAC, P2P, or soft AP), the non-AP MLD can exit EMLSR operating mode, or can choose not to enter EMLSR operating mode, as described above.

[0323] refer to Figure 6 This schematically illustrates a multi-link wireless communication method based on some illustrative aspects. For example, Figure 6 One or more operations of the method can be performed by the system (e.g., system 100). Figure 1 One or more components of a device may perform this action, for example, one or more wireless devices, such as device 102. Figure 1 ) and / or equipment 140 ( Figure 1 ), controller, such as controller 124 ( Figure 1 ) and / or controller 154 ( Figure 1 ), radio, such as radio device 114 ( Figure 1 ) and / or radio devices 144 Figure 1 ), and / or message processors, such as message processor 128 ( Figure 1 ) and / or message processor 158 ( Figure 1 ).

[0324] As shown in box 602, the method may include: determining whether an EMLSR enabling criterion is met at a non-AP MLD. For example, the EMLSR enabling criterion may be based on one or more predefined enabling criteria corresponding to one or more enabling criterion parameters. For example, controller 154 ( Figure 1 ) can be configured to prompt, trigger, and / or control device 140 ( Figure 1 Determine whether the EMLSR enabling criteria are met, for example, as described above.

[0325] As shown in block 604, the method may include, for example, activating operation of a non-AP MLD in the EMLS operation mode of an MLO on multiple links with an AP MLD, based on determining that the EMLS enable criterion is met. For example, controller 154 ( Figure 1 ) can be configured to prompt, trigger, and / or control device 140 ( Figure 1 For example, based on determining that the EMLSR enable criteria are met, the operation of non-APMLD in EMLSR operation mode is activated, for example, as described above.

[0326] As shown in box 606, the method may include: determining whether EMLSR deactivation criteria are met during EMLSR operation mode. For example, EMLSR deactivation criteria may be based on one or more predefined deactivation criteria corresponding to one or more deactivation criterion parameters. For example, controller 154 ( Figure 1 ) can be configured to prompt, trigger, and / or control device 140 ( Figure 1 During EMLSR operation mode, it determines whether the EMLSR deactivation criteria are met, for example, as described above.

[0327] As shown in block 608, the method may include, for example, switching a non-AP MLD from EMLSR operating mode to a non-EMLSR MLO mode based on determining that EMLSR deactivation criteria are met. For example, controller 154 ( Figure 1 ) can be configured to prompt, trigger, and / or control device 140 ( Figure 1 For example, based on determining that the EMLSR deactivation criteria are met, the non-AP MLD can be switched from EMLSR operation mode to non-EMLSR MLO mode, for example, as described above.

[0328] refer to Figure 7 The illustration schematically shows an article 700 according to some illustrative aspects. The article 700 may include one or more tangible computer-readable (“machine-readable”) non-transitory storage media 702, which may include computer-executable instructions, implemented, for example, by logic 704, operable to, when executed by at least one computer processor, enable at least one computer processor to enable the device 102 ( Figure 1 ), equipment 140 ( Figure 1 ), controller 124 ( Figure 1 ), controller 154 ( Figure 1 ), Message Processor 128 ( Figure 1 ), Message Processor 158 ( Figure 1 ), Radio device 114 ( Figure 1 ), Radio device 144 ( Figure 1 ), transmitter 118 ( Figure 1 ), transmitter 148 ( Figure 1 ), receiver 116 ( Figure 1 ), and / or receiver 146 ( Figure 1 Operation at point 102; prompting equipment 102 ( Figure 1 ), equipment 140 ( Figure 1 ), controller 124 ( Figure 1 ), controller 154 ( Figure 1 ), Message Processor 128 Figure 1 ), Message Processor 158 ( Figure 1 ), Radio device 114 ( Figure 1 ), Radio device 144 ( Figure 1 ), transmitter 118 ( Figure 1 ), transmitter 148 ( Figure 1 ), receiver 116 ( Figure 1 ), and / or receiver 146 ( Figure 1 )Execute, trigger, and / or implement the references in this article Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 and / or Figure 6 The description includes one or more operations and / or functions; and / or execution, triggering, and / or implementation of the references in this document. Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 and / or Figure 6 Describes one or more operations and / or functions. The phrases “non-transitory machine-readable medium” and “computer-readable non-transitory storage medium” can include all machine and / or computer-readable media, with the sole exception of transient propagation signals.

[0329] In some illustrative aspects, product 700 and / or machine-readable storage medium 702 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. For example, machine-readable storage medium 702 may include RAM, DRAM, double data rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory (e.g., NOR or NAND flash), content-addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, disk, hard disk, etc. The computer-readable storage medium may include any suitable medium relating to downloading or transferring a computer program from a remote computer to a requesting computer via a communication link (e.g., modem, radio, or network connection), the computer program being carried by data signals contained in a carrier wave or other propagation medium.

[0330] In some illustrative aspects, logic 704 may include instructions, data, and / or code that, when executed by a machine, can cause the machine to perform the methods, processes, and / or operations described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware, software, firmware, etc.

[0331] In some illustrative aspects, logic 704 may include, or can be implemented as, software, software modules, applications, programs, subroutines, instructions, instruction sets, computation code, words, values, symbols, etc. Instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Instructions may be implemented according to predefined computer languages, methods, or syntaxes to instruct the processor to perform specific functions. Instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled, and / or interpreted programming languages, machine code, etc.

[0332] Example

[0333] The following examples involve other aspects.

[0334] Example 1 includes an apparatus comprising logic and circuitry configured to enable a non-access point (AP) multi-link device (MLD) to determine whether an Enhanced Multi-Link Single Radio (EMLSR) enable criterion is met, wherein the EMLSR enable criterion is based on one or more predefined enable criterions corresponding to one or more enable criterion parameters; based on the determination that the EMLSR enable criterion is met, to activate operation of the non-AP MLD in an EMLSR operation mode of multi-link operation (MLO) on multiple links with the AP MLD; during the EMLSR operation mode, to determine whether an EMLSR deactivation criterion is met, wherein the EMLSR deactivation criterion is based on one or more predefined deactivation criteria corresponding to one or more deactivation criterion parameters; and based on the determination that the EMLSR deactivation criterion is met, to switch the non-AP MLD from the EMLSR operation mode to a non-EMLSR MLO mode.

[0335] Example 2 includes the subject of Example 1, and optionally, one or more predefined enable criteria include an additional device channel load enable criterion based on an additional device channel load parameter, which represents the channel load caused by other devices transmitting traffic on channels that are not used by AP STAs to communicate with AP MLD.

[0336] Example 3 includes the subject of Example 2, and optionally, the device is configured to cause the non-AP MLD to determine that the other device channel load enable criterion is met based on the determination that the value of the other device channel load parameter is greater than the other device channel load threshold.

[0337] Example 4 includes the subject of any one of Examples 1 to 3, and optionally, one or more of the predefined enable criteria include a receive performance enable criterion based on a receive performance parameter that represents the performance level of receiving communication from an APMLD at a non-AP MLD.

[0338] Example 5 includes the subject of Example 4, and optionally, the device is configured to cause the non-AP MLD to determine that the reception performance enable criterion is met based on the determination that the value of the reception performance parameter is greater than the reception performance threshold.

[0339] Example 6 includes the subject of any one of Examples 1 to 5, and optionally, one or more of the predefined enable criteria include a power-based enable criterion based on a power-based parameter representing a relationship between a first power consumption level and a second power consumption level, the first power consumption level including the power consumption of a non-AP MLD transmitting specific traffic with an AP MLD in EMLSR operating mode, and the second power consumption level including the power consumption of a non-AP MLD transmitting specific traffic with an AP MLD in non-EMLSRMLO mode.

[0340] Example 7 includes the subject of Example 6, and optionally, the device is configured to cause the non-AP MLD to determine that a power-based enable criterion is met based on the value of a first power consumption level being less than a second power consumption level, determined by a power-based parameter.

[0341] Example 8 includes the subject of any one of Examples 1 to 7, and optionally, one or more of the predefined enable criteria include a latency-based enable criterion that is based on a latency-based parameter that represents a relationship between a first latency and a second latency, the first latency including latency for transmitting specific traffic with APMLD in EMLSR operating mode, and the second latency including latency for transmitting specific traffic with APMLD in non-EMLSR MLO mode.

[0342] Example 9 includes the subject of Example 8, and optionally, the device is configured to cause the non-AP MLD to determine, based on the value of a delay-based parameter, that a first delay is less than a second delay, and to determine that a delay-based enable criterion is met.

[0343] Example 10 includes the subject of any one of Examples 1 to 9, and optionally, one or more predefined enable criteria include a self-interference enable criterion based on a self-interference parameter indicating whether self-interference from at least one co-located component exists on at least one of a plurality of links, wherein the at least one co-located component includes at least one of a co-located wireless communication interface or a co-located circuit clock.

[0344] Example 11 includes the subject of Example 10, and optionally, the device is configured to cause a non-AP MLD to determine that a self-interference enable criterion is met based on a determination of self-interference parameters indicating that there is no self-interference on any of the multiple links.

[0345] Example 12 includes the subject of any one of Examples 1 to 11, and optionally, one or more predefined enable criteria include an operation mode enable criterion based on an operation mode parameter that indicates whether wireless communication with other devices is to be performed on at least one of a plurality of links.

[0346] Example 13 includes the subject of Example 12, and optionally, the device is configured to cause a non-AP MLD to determine that it does not wirelessly communicate with other devices on any of the multiple links based on determined operating mode parameters, thereby determining that the operating mode enable criterion is met.

[0347] Example 14 includes the subject of any one of Examples 1 to 13, and optionally, one or more of the predefined deactivation criteria include an other device channel load deactivation criterion based on other device channel load parameters, which represent the channel load caused by other devices transmitting traffic on channels that are not used by AP STAs to communicate with AP MLDs.

[0348] Example 15 includes the subject of Example 14, and optionally, the device is configured to cause the non-AP MLD to determine that the other device channel load deactivation criteria are met based on the determination that the value of the other device channel load parameter is lower than the other device channel load threshold.

[0349] Example 16 includes the subject of any one of Examples 1 to 15, and optionally, one or more of the predefined deactivation criteria include a receive performance deactivation criterion based on a receive performance parameter that represents the performance level of receiving communication from an APMLD at a non-AP MLD.

[0350] Example 17 includes the subject of Example 16, and optionally, the device is configured to cause the non-AP MLD to determine that the reception performance deactivation criterion is met based on the determination that the value of the reception performance parameter is below the reception performance threshold.

[0351] Example 18 includes the subject of any one of Examples 1 to 17, and optionally, one or more of the predefined deactivation criteria include a power-based deactivation criterion based on a power-based parameter representing a relationship between a first power consumption level and a second power consumption level, the first power consumption level including the power consumption of a non-AP MLD transmitting specific traffic with an AP MLD in EMLSR operating mode, and the second power consumption level including the power consumption of a non-AP MLD transmitting specific traffic with an AP MLD in non-EMLSRMLO mode.

[0352] Example 19 includes the subject of Example 18, and optionally, the device is configured to cause the non-AP MLD to determine that a power-based deactivation criterion is met based on the determination of the value of a power-based parameter indicating that the second power consumption level is less than the first power consumption level.

[0353] Example 20 includes the subject of any one of Examples 1 to 19, and optionally, one or more of the predefined deactivation criteria include a delay-based deactivation criterion based on a delay-based parameter representing a relationship between a first delay and a second delay, the first delay including a delay in transmitting specific traffic with AP MLD in EMLSR operating mode, and the second delay including a delay in transmitting specific traffic with AP MLD in non-EMLSR MLO mode.

[0354] Example 21 includes the subject of Example 20, and optionally, the device is configured to cause the non-AP MLD to determine, based on the value of a delay-based parameter, that a second delay is less than a first delay, and to determine that a delay-based deactivation criterion is met.

[0355] Example 22 includes the subject matter of any one of Examples 1 to 21, and optionally, one or more predefined deactivation criteria include a self-interference deactivation criterion based on a self-interference parameter indicating whether self-interference from at least one co-located component is present on at least one of a plurality of links, wherein the at least one co-located component includes at least one of a co-located wireless communication interface or a co-located circuit clock.

[0356] Example 23 includes the subject of Example 22, and optionally, the apparatus is configured to cause the non-AP MLD to determine that self-interference is present on at least one of a plurality of links based on a self-interference parameter determination.

[0357] Example 24 includes the subject of any one of Examples 1 to 23, and optionally, one or more predefined deactivation criteria include an operation mode deactivation criterion based on an operation mode parameter indicating whether wireless communication with other devices should be performed on at least one of a plurality of links.

[0358] Example 25 includes the subject of Example 24, and optionally, the device is configured to cause a non-AP MLD to determine, based on determined operating mode parameters, whether to perform wireless communication with other devices on at least one of a plurality of links, and to determine whether the operating mode deactivation criteria are met.

[0359] Example 26 includes the subject of any one of Examples 1 to 25, and optionally, the device is configured to cause a non-APMLD to send an EMLD enabling instruction to the AP MLD based on determining that the EMLD enabling criteria are met.

[0360] Example 27 includes the subject of any one of Examples 1 to 26, and optionally, the device is configured to cause a non-APMLD to send an EMLSR deactivation instruction to an AP MLD based on determining that the EMLSR deactivation criteria are met.

[0361] Example 28 includes the subject of any one of Examples 1 to 27, and optionally, the device is configured to enable real-time monitoring of one or more disabled standard parameters during non-AP MLD operation in EMLSR operation mode, and real-time monitoring of one or more enabled standard parameters during non-AP MLD operation in non-EMLSR MLO mode.

[0362] Example 29 includes the subject of any one of Examples 1 to 28, and optionally, the apparatus is configured to cause a non-APMLD to determine that it meets the EMLSR enable criteria based on determining that it meets a plurality of predefined enable criteria corresponding to a plurality of predefined enable criterion parameters.

[0363] Example 30 includes the subject of Example 29, and optionally, the device is configured to cause the non-AP MLD to determine that the EMLSR enable criteria are met only based on determining that all of the multiple predefined enable criteria are met.

[0364] Example 31 includes the subject of any one of Examples 1 to 30, and optionally, the apparatus is configured to cause a non-APMLD to determine that it meets the EMLSR deactivation criteria based on determining that at least one of a plurality of predefined deactivation criteria is met.

[0365] Example 32 includes the subject of any one of Examples 1 to 31, and optionally, the apparatus is configured to cause non-APMLD to determine that EMLSR enable criteria are met only based on determining that all of the multiple predefined enable criteria are met, and to determine that EMLSR deactivation criteria are met based on determining that at least one of the multiple predefined deactivation criteria is met.

[0366] Example 33 includes the subject of any one of Examples 1 to 32, and optionally includes a radio device for transmitting traffic with the AP MLD.

[0367] Example 34 includes the subject of Example 33 and optionally includes one or more antennas connected to the radio device, and a processor that executes instructions of an operating system that is not an AP MLD.

[0368] Example 35 includes a wireless communication device that includes the means of any one of Examples 1 to 34.

[0369] Example 36 includes a mobile device that includes the device of any one of Examples 1 to 34.

[0370] Example 37 includes an apparatus that includes means for performing the operations described in any one of Examples 1 to 34.

[0371] Example 38 includes a product comprising one or more tangible computer-readable nontransitory storage media, the storage media including instructions operable to, when executed by at least one processor, enable at least one processor to cause a wireless communication device to perform any of the operations described in any of Examples 1 to 34.

[0372] Example 39 includes an apparatus comprising: a memory interface; and processing circuitry configured to perform any of the operations described in any of Examples 1 to 34.

[0373] Example 40 includes a method comprising any of the operations described in any of Examples 1 to 34.

[0374] The functions, operations, components, and / or features described in this document with reference to one or more other aspects may be used in conjunction with one or more other functions, operations, and / or features described in this document with reference to one or more other aspects, and vice versa.

[0375] While certain features have been described and illustrated herein, many modifications, substitutions, alterations, and equivalents can be made by those skilled in the art. Therefore, it should be understood that the appended claims are intended to cover all modifications and alterations consistent with the true spirit of this disclosure.

Claims

1. A method performed at a non-access point (non-AP) multi-link device (MLD), the method comprising: determining whether enhanced multi-link single radio (EMLSR) enable criteria are satisfied, wherein the EMLSR enable criteria are based on one or more predefined enable criteria corresponding to one or more enable criteria parameters; based on a determination that the EMLSR enable criteria are satisfied, activating operation of the non-AP MLD in an EMLSR operating mode of multi-link operation (MLO) over multiple links with an AP MLD; determining whether EMLSR disable criteria are satisfied during the EMLSR operating mode, wherein the EMLSR disable criteria are based on one or more predefined disable criteria corresponding to one or more disable criteria parameters; and based on a determination that the EMLSR disable criteria are satisfied, switching the non-AP MLD from the EMLSR operating mode to a non-EMLSR MLO mode.

2. The method of claim 1, wherein, the one or more predefined enable criteria include an other-device channel load enable criterion based on an other-device channel load parameter that is representative of channel load due to other devices transmitting traffic on channels used by the non-AP MLD to communicate with the AP MLD.

3. The method of claim 2, comprising: based on a determination that a value of the other-device channel load parameter is greater than an other-device channel load threshold, determining that the other-device channel load enable criterion is satisfied.

4. The method of claim 1, wherein, the one or more predefined enable criteria include a reception performance enable criterion based on a reception performance parameter that is representative of a level of performance of receiving communications at the non-AP MLD from the AP MLD.

5. The method of claim 1, wherein, the one or more predefined enable criteria include a power-based enable criterion that is based on a power-based parameter that is representative of a relationship between a first power consumption level and a second power consumption level, the first power consumption level comprising power consumption of the non-AP MLD to transmit particular traffic with the AP MLD in the EMLSR operating mode, the second power consumption level comprising power consumption of the non-AP MLD to transmit the particular traffic with the AP MLD in the non-EMLSR MLO mode.

6. The method of claim 5, comprising: based on a determination that a value of the power-based parameter is representative of the first power consumption level being less than the second power consumption level, determining that the power-based enable criterion is satisfied.

7. The method of claim 1, wherein, the one or more predefined enable criteria include a latency-based enable criterion that is based on a latency-based parameter that is representative of a relationship between a first latency and a second latency, the first latency comprising latency to transmit particular traffic with the AP MLD in the EMLSR operating mode, the second latency comprising latency to transmit the particular traffic with the AP MLD in the non-EMLSR MLO mode.

8. The method of claim 7, comprising: based on a determination that a value of the latency-based parameter is representative of the first latency being less than the second latency, determining that the latency-based enable criterion is satisfied.

9. The method of claim 1, wherein, The one or more predefined enablement criteria include a self-interference enablement criterion based on a self-interference parameter that indicates whether self-interference from at least one co-located component is present on at least one of the plurality of links, where the at least one co-located component includes at least one of a co-located wireless communication interface or a co-located circuit clock.

10. The method of claim 1, wherein, The one or more predefined enablement criteria include an operating mode enablement criterion based on an operating mode parameter that indicates whether wireless communication with other devices is to be performed on at least one of the plurality of links.

11. The method of claim 1, wherein, The one or more predefined deactivation criteria include an other-device channel load deactivation criterion based on an other-device channel load parameter that represents a channel load due to other devices transmitting traffic on a channel used by the non-AP MLD to communicate with the AP MLD.

12. The method of claim 1, wherein, The one or more predefined deactivation criteria include a power-based deactivation criterion that is based on a power-based parameter that represents a relationship between a first power consumption level and a second power consumption level, the first power consumption level comprising a power consumption of the non-AP MLD to transmit particular traffic with the AP MLD in the EMLSR operating mode, the second power consumption level comprising a power consumption of the non-AP MLD to transmit the particular traffic with the AP MLD in the non-EMLSR MLO mode.

13. The method of claim 1, wherein, The one or more predefined deactivation criteria include a latency-based deactivation criterion that is based on a latency-based parameter that represents a relationship between a first latency and a second latency, the first latency comprising a latency to transmit particular traffic with the AP MLD in the EMLSR operating mode, the second latency comprising a latency to transmit the particular traffic with the AP MLD in the non-EMLSR MLO mode.

14. The method of claim 1, comprising: transmitting an EMLSR enablement indication to the AP MLD based on determining that the EMLSR enablement criteria are satisfied, and / or transmitting an EMLSR deactivation indication to the AP MLD based on determining that the EMLSR deactivation criteria are satisfied.

15. The method of claim 1, comprising: determining that the EMLSR enablement criteria are satisfied based only on determining that all of a plurality of predefined enablement criteria are satisfied, and determining that the EMLSR deactivation criteria are satisfied based on determining that at least one of a plurality of predefined deactivation criteria is satisfied.

16. The method of claim 1, comprising: monitoring the one or more deactivation criteria parameters in real-time during operation of the non-AP MLD in the EMLSR operating mode, and monitoring the one or more enablement criteria parameters in real-time during operation of the non-AP MLD in the non-EMLSR MLO mode.

17. The method of claim 1, comprising: determining that the EMLSR enablement criteria are satisfied based on determining that a plurality of predefined enablement criteria corresponding to a plurality of predefined enablement criteria parameters are satisfied, and determining that the EMLSR deactivation criteria are satisfied based on determining that at least one of a plurality of predefined deactivation criteria is satisfied.

18. An apparatus comprising a controller configured to cause a non-access point (non-AP) multi-link device (MLD) to perform the method of any one of claims 1 to 17.

19. The apparatus of claim 18, comprising a radio for communicating traffic with the AP MLD, one or more antennas connected to the radio, and a processor for executing instructions of an operating system of the non-AP MLD.

20. A product comprising one or more tangible computer-readable non-transitory storage media comprising instructions operable to, when executed by at least one processor, enable the at least one processor to cause a non-access point (non-AP) multi-link device (MLD) to perform the method of any one of claims 1 to 17.

21. An apparatus comprising means for causing a non-access point (non-AP) multi-link device (MLD) to perform the method of any one of claims 1 to 17.

Images