Methods and apparatuses for enhanced multi-link single radio (EMLSR) operation

Abstract

The present disclosure provides for an enhanced multi-link single radio ( EMLSR ) Methods and apparatuses for operating. The method can involve a first non-AP MLD and a second non-AP MLD exchanging capability information in a handshake procedure over one of a plurality of links. The method can also involve the first non-AP MLD and the second non-AP MLD establishing EMLSR operation over one or more of the plurality of links. Each of the first non-AP MLD and the second non-AP MLD can listen on at least one of the plurality of links.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more particularly, to pervasive enhanced multi-link single radio (EMLSR) operation in wireless communications. BACKGROUND

[0002] The methods described in this section are not prior art to the listing claims and are not admitted to be prior art by inclusion in this section.

[0003] In wireless communications according to Institute of Electrical and Electronics Engineers (IEEE) standards, such as Wi-Fi 7, EMLSR is expected to be a key operation mode for a given non-AP multi-link device (MLD). It is desirable to improve latency and throughput for peer-to-peer (P2P) and tunneled direct link setup (TDLS) related applications. However, how to enhance the performance of non-AP MLDs in a P2P / TDLS-EMLSR environment remains to be specified. Therefore, there is a need for solutions for pervasive EMLSR operation in wireless communications to enable performance enhancement between non-AP MLDs through EMLSR. SUMMARY

[0004] The following summary is illustrative only and is not intended to be in any way limiting. I.e., the following summary is provided to introduce the novel and non-obvious concepts, highlights, benefits, and advantages of the subject technology described herein. Selected implementations are further described in the DETAILED DESCRIPTION section. Thus, the following summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in determining the scope of the claimed subject matter.

[0005] It is an object of the present disclosure to provide solutions, concepts, designs, techniques, methods, and apparatuses related to performance enhancement between non-AP MLDs through EMLSR in wireless communications. Under various solutions proposed according to the present disclosure, an access point (AP) can avoid unnecessary reattempts on an unexpected link, as such reattempts end up causing unexpected packet loss and also reduce AP contention opportunities. Under various solutions proposed according to the present disclosure, performance can be enhanced through EMLSR between non-AP MLDs. Thus, various solutions proposed according to the present disclosure can solve or otherwise alleviate the problems described herein.

[0006] In one aspect, a method can involve a first non-AP MLD exchanging capability information with a second non-AP MLD in a handshake procedure over one of a plurality of links. The method can further involve the first non-AP MLD establishing an EMLSR operation with the second non-AP MLD over one or more of the plurality of links. Each of the first non-AP MLD and the second non-AP MLD can listen on at least one of the plurality of links.

[0007] In another aspect, an apparatus, which can be implemented in a first non-AP MLD, can include a transceiver configured for wireless communication and a processor coupled to the transceiver. The processor can exchange, via the transceiver, capability information with a second non-AP MLD in a handshake procedure over one of a plurality of links. The processor can further establish, via the transceiver, an EMLSR operation with the second non-AP MLD over one or more of the plurality of links. Each of the first non-AP MLD and the second non-AP MLD can listen on at least one of the plurality of links.

[0008] Notably, although the description provided herein can be in the context of certain radio access technologies, networks, and network topologies (e.g., Wi-Fi), the proposed concepts, solutions, and any variants / derivatives thereof can be implemented in, for, and by other types of radio access technologies, networks, and network topologies, such as, without limitation, Long-Term Evolution (LTE), LTE-A, LTE-A Pro, 5G, New Radio (NR), Internet-of-Things (IoT), Narrow Band Internet of Things (NB-IoT), and Industrial Internet of Things (IIoT). Thus, the scope of the present application is not limited to the examples described herein. BRIEF DESCRIPTION OF DRAWINGS

[0009] The accompanying drawings are included to provide a further understanding of the present application, and are incorporated in and constitute a part of the present application. The drawings illustrate embodiments of the present application and, together with the description, serve to explain the principles of the present application. It is understood that the drawings are not necessarily to scale, as some components can be shown exaggerated in scale or with exaggerated proportions in order to illustrate concepts more clearly.

[0010] Figure 1 An example network environment in which various solutions and solutions according to the present application can be implemented is illustrated.

[0011] Figure 2Example scenarios under the proposed scheme for non-AP EMLSR MLD operation such as P2P / TDLS are illustrated.

[0012] Figure 3 Example scenarios under the proposed scheme are illustrated.

[0013] Figure 4 Example scenarios under the proposed scheme for capability handshake are illustrated.

[0014] Figure 5 Example scenarios under the proposed scheme for EMLSR MAC protocol between non-AP MLDs are illustrated.

[0015] Figure 6 Example scenarios under the proposed scheme for EMLSR hitchhiking transmission-on-reception (Tx-on-Rx) are illustrated.

[0016] Figure 7 Example scenarios under the proposed scheme for detecting peer STA's EMLSR operation are illustrated.

[0017] Figure 8 Example scenarios under the proposed scheme for AP MLD's transparency are illustrated.

[0018] Figure 9 is a block diagram of an example communication system in accordance with an embodiment of the present application.

[0019] Figure 10 is a flow diagram of an example process in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0020] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. It is understood, however, that the detailed embodiments and implementations disclosed are merely examples of the claimed subject matter and can be embodied in various forms. The application is not to be limited to the example embodiments and implementations disclosed but is to cover all consistent modifications not inconsistent with the principles and spirit of the claimed subject matter. Such modifications can be understood by one of ordinary skill in the art having the benefit of the present disclosure. The present application is to be limited only by the claims sufficiently detailed below.

[0021] SUMMARY

[0022] Embodiments according to the present application relate to various techniques, methods, schemes and / or solutions related to performance enhancements between non-AP MLDS in wireless communications through EMLSR. According to the present application, a variety of possible solutions can be implemented individually or jointly. That is, while the following can describe these possible solutions separately, two or more of these possible solutions can be implemented in one combination or another.

[0023] Figure 1 An example network environment 100 in which various solutions and schemes according to the present application can be implemented is illustrated. Figures 2-10 Embodiments of various proposed schemes in the network environment 100 according to the present application are illustrated. Reference is made to Figures 1-10 The following description of various proposed schemes is provided.

[0024] As Figure 1 illustrated, the network environment 100 can involve at least a first communication entity or STA 110 wirelessly communicating with a second communication entity or STA 120. Each of the STA 110 and the STA 120 can be an access point (AP) STA or a non-access point (non-AP) STA, respectively. Each of the STA 110 and the STA 120 can belong to a respective MLD capable of operating with EMLSR enabled. For example, the STA 110 can belong to a first non-AP MLD (MLD1), while the STA 120 can belong to a second non-AP MLD (MLD2). In some cases, the STA 110 and the STA 120 can be associated with a basic service set (BSS) according to one or more IEEE 802.11 standards (e.g., IEEE 802.11be and future developed standards) such as Wi-Fi 7. The STA 110 and the STA 120 can be configured to communicate with each other by utilizing various proposed schemes described herein, which are related to performance enhancements between non-AP MLDS in wireless communications through EMLSR. Notably, while the following can describe various proposed schemes separately or independently, in actual implementation, each proposed scheme can be used individually or independently, or some or all proposed schemes can be used jointly.

[0025] In P2P / TDLS EMLSR for listening, detection, and transmission, both the first non-AP MLD and the second non-AP MLD can be in P2P communication and operate in EMLSR mode. The two EMLSR non-AP MLDs can listen to two or more links and can switch to the same link when EMLSR communication between the two non-AP MLDs starts. This can also apply to other MLDs, such as hybrid mode non-AP MLDs and / or non-simultaneous-transmission-and-reception (NSTR) non-AP MLDs. Compared to single-link P2P scenarios, latency and throughput can be significantly improved in high network load scenarios.

[0026] In various proposed solutions according to the present application, in EMLSR operation between two EMLSR non-AP MLDs (referred to herein as “MLD1” and “MLD2”), initially, a first non-AP MLD (MLD1) and a second non-AP MLD (MLD2) can listen to multiple EMLSR-enabled links, e.g., a first link (referred to herein as “link 1”) and a second link (referred to herein as “link 2”). Then, MLD1 can trigger its peer EMLSR non-AP MLD (or MLD2) for EMLSR communication. MLD1 can send a request-to-send (RTS), multi-user request-to-send (MU-RTS), buffer status report poll (BSRP), and / or power-saving poll (PS-Poll) on link 1 as an initial physical-layer protocol data unit (PPDU) to trigger MLD2 for EMLSR operation on link 1. Upon detecting the RTS / MU-RTS / BSRP / PS-Poll on link 1, MLD2 can respond with a clear-to-send (CTS), buffer status report (BSR), and / or acknowledgement (ACK) on link 1. Thus, both MLD1 and MLD2 can switch to the link (e.g., link 1) for EMLSR communication, which can include data exchange and block acknowledgement (BA). That is, when MLD1 sends the RTS / MU-RTS / BSRP / PS-Poll, MLD1 can switch to link 1 (thus causing MLD1 to be unable to receive data on link 2) for EMLSR communication, and when MLD2 sends the CTS / BSR / ACK, MLD2 can switch to link 1 (thus causing MLD2 to be unable to receive data on link 2) for EMLSR operation. Thus, during the EMLSR communication phase, MLD1 and MLD2 are unable to receive data on the other EMLSR link (e.g., link 2).

[0027] Figure 2 An example scenario 200 is illustrated under the proposed solution according to the present application with respect to non-AP EMLSR MLD operation such as P2P / TDLS. In Figure 2 there are 4 devices, EMLSR non-AP MLD1 (with link 1 and link 2), EMLSR non-AP MLD2 (with link 1 and link 2), an AP (with link 1), and a non-AP. Among them, inFigure 2 In the main link, "EMLSR" indicates communication between the AP and a non-AP MLD, "P2P EMLSR" indicates point-to-point communication between non-AP MLDs, and "Other Communication" indicates communication between the AP and a non-AP (such as...). Figure 2 (Other communications are highlighted in gray). Under the proposed scheme, EMLSR non-AP MLDs can enable the same links with the AP. For example, each EMLSR non-AP MLD can listen, detect (e.g., determine if a peer STA is communicating with other STAs on the primary link), and communicate on a secondary link (or auxiliary link) (e.g., link 2) when the primary link (e.g., link 1) is busy (e.g., unavailable). Even if no primary link is defined among multiple links, the EMLSR non-AP MLD can detect that other links among multiple links are busy and that the link does not include a peer MLD. Under the proposed scheme, regarding capability handshakes, P2P / TDLS STAs can negotiate the EMLSR capabilities and EMLSR link sets used for EMLSR operations between STAs. Furthermore, regarding the medium access control (MAC) protocol, when the primary link is busy and the AP is transparent to EMLSR operations on the secondary link (meaning the AP is unaware of EMLSR operations between non-AP MLDs performed on the secondary link), non-APSTAs can perform EMLSR operations on the secondary (or auxiliary) link. Additionally, non-AP MLDs can also perform EMLSR operations on the primary link with the AP's knowledge.

[0028] Figure 3 An example scenario 300 according to the proposed solution of the present invention is illustrated. Figure 2 In comparison, Figure 3 In the proposed scheme, the AP belonging to the MLD can support detecting P2P / TDLS EMLSR operations between EMLSR MLDs, and the AP MLD can be a simultaneous-transmission-and-reception (STR) MLD. Furthermore, the AP can be aware that a non-AP belonging to another MLD is communicating (with another non-AP). Figure 3 As shown, when P2P (or TDLS) EMLSR communication between two non-AP MLDs occurs on a secondary (or auxiliary) link, while one or more other operations occur on the primary link between the AP and one or both of the two non-AP MLDs (e.g., ... Figure 3When the AP is aware of P2P (or TDLS) EMLSR communication on the secondary (or secondary) link (e.g., when the AP receives a "Other Communication" with no gray background color), the AP can be aware of P2P (or TDLS) EMLSR communication on the secondary (or secondary) link, and thus avoid triggering any communication with the two non-AP MLDs on the other link with EMLSR enabled to reduce or minimize the initial triggering cost.

[0029] Figure 4 An example scenario 400 under the proposed solution according to the present application regarding capability handshake is illustrated. Under the proposed solution, a handshake protocol can be used for TDLS and / or P2P EMLSR operation. For example, an EMLSR capability field can be added in the handshake flow (e.g., in a multi-link element, such as a TDLS multi-link element, or in a Peer-to-Peer Link Event Request sub-element). Alternatively or additionally, EMLSR operation information (e.g., channel number) can be added to the handshake flow (e.g., in a TDLS multi-link element). The EMLSR TDLS link can not be restricted by the link associated with the AP. Thus, it can be expected that at least one of the multiple links can be associated with the AP for a STA enabling EMLSR TDLS.

[0030] Reference Figure 4 In part (A) of FIG. 1, the AP can be associated with each of a first non-AP MLD 1 (non-AP1) and a second non-AP MLD 2 (non-AP2) on a first link (link 1) of multiple links including the first link (link 1) and a second link (link 2). After the first non-AP MLD 1 and the second non-AP MLD 2 handshake, the two non-AP MLDs can perform EMLSR operation on link 1 and link 2. In part (B) of FIG. 1, the AP can be aware of P2P (or TDLS) EMLSR communication on the secondary (or secondary) link (e.g., when the AP receives a "Other Communication" with no gray background color), and thus avoid triggering any communication with the two non-AP MLDs on the other link with EMLSR enabled to reduce or minimize the initial triggering cost. Figure 4The AP can be associated with each of a first non-AP MLD1 of a first enhanced multi-link multiple radios (EMLMR) MLD (EMLMR MLD1) and a second non-AP MLD2 of a second EMLMR MLD (EMLMR MLD2) on a first link of a plurality of links including the first link (link 1), a second link (link 2), and a third link (link 3) for the (B) part. For the EMLMR MLD1, link 1 (Non-AP1-STA1) and link 2 (Non-AP1-STA2) can be STR links, link 1 and link 3 (Non-AP1-STA3) can be STR links, and link 2 and link 3 can be EMLSR links. For the EMLSR MLD2, link 1 (Non-AP2-STA1) and link 2 (Non-AP2-STA2) can be STR links, link 1 and link 3 (Non-AP2-STA3) can be STR links, and link 2 and link 3 can be EMLSR links. After the first non-AP MLD and the second non-AP MLD handshake, the two STAs can perform EMLSR operation on link 2 and link 3.

[0031] Figure 5 An example scenario 500 under the proposed scheme for EMLSR MAC protocol between non-AP MLDS according to the present application is illustrated. Referring to Figure 5 , a first EMLSR non-AP MLD (MLD1) can trigger a peer EMLSR non-AP MLD (MLD2) for EMLSR communication. MLD1 and MLD2 can switch to the link carrying the initial PPDU (the initial PPDU of this transmission is used for EMLSR communication). During the EMLSR communication phase, MLD1 and MLD2 cannot receive data on other EMLSR links. MLD1 can use MU-RTS / BSRP / RTS / PS-Poll as the initial PPDU to trigger MLD2 for EMLSR operation. It is worth noting that this can not be applicable for EMLSR between one AP MLD and another AP MLD.

[0032] Figure 6 An example scenario 600 under the proposed scheme for EMLSR hitchhiking transmission-on-reception (Tx-on-Rx) according to the present application is illustrated. EMLSR hitchhiking can be, for example Figure 6In the upper part, TLDS / P2P EMLSR communication is conducted on one link (e.g., a secondary link) during other communication on another link (e.g., a primary link). Under the proposed scheme, the EMLSR MLD can detect that one or more links are busy and determine or otherwise obtain certain information. According to the proposed scheme, the EMLSR MLD can determine that transmissions on the one or more busy links are not to or from the EMLSR MLD (not2me), not to or from a peer EMLSR MLD (not2peer), and / or not from a peer EMLSR MLD (notfrompeer). For example, such determination of not2me / not2peer / notfrompeer can be based on a preamble (e.g., HE-SIG-B field or EHT-SIG field) or MAC header (e.g., address 1 or address 2) in a PPDU. Further, under the proposed scheme, the EMLSR MLD can obtain a duration of a PPDU and / or transmission opportunity (TXOP) of the busy link. For example, the TXOP / PPDU duration can be estimated based on the preamble in the PPDU. Further, under the proposed scheme, the EMLSR MLD can have access to an idle link with a duration limit. For example, the EMLSR MLD can conduct TLDS / P2P EMLSR communication on a non-busy (idle) link during the duration of a PPDU and / or transmission opportunity (TXOP) of a busy link, thus requiring the duration of the PPDU and / or TXOP of the busy link to be obtained. Further, under the proposed scheme, the above limit can apply to certain links (e.g., a primary link) of the EMLSR MLD to achieve transparency to the AP MLD (e.g., provide transparency to the AP MLD regarding EMLSR operation so that the AP MLD is aware of it). For example, the primary or secondary link can be defined by the EMLSR MLD itself.

[0033] Figure 7An example scenario 700 under the proposed scheme for detection of EMLSR operation of a peer STA according to the present application is illustrated. The detection of EMLSR operation of a peer STA can be achieved by one or more of several ways described below. Under the proposed scheme, if an EMLSR MLD receives an RTS, MU-RTS, BSRP, PS-Poll, or clear-to-send-to-self (CTS2self) with transmitter address (TA) of a peer EMLSR MLD, the EMLSR MLD can not trigger the peer MLD on another EMLSR link. Under the proposed scheme, upon receiving a clear-to-send (CTS) or ACK with receiver address (RA) of a hidden node, the EMLSR MLD needs to know the address of the peer’s peer. For example, the link address of the peer’s peer can be specified using an EMLSR element. It is worth noting that if the peer’s peer is an AP, this can be a false alarm. According to the proposed scheme, upon receiving a trigger frame with association identifier (AID) of the peer’s AID, the EMLSR MLD can need other information, such as BSS ID, to identify the STA of the target trigger. For example, a protocol can be used to negotiate the AID and TA information. Under the proposed scheme, when a peer STA is detected to be negotiating with its peer other MAC addresses for EMLSR operation (e.g., in P2P mode), then the EMLSR operation of the peer STA can be detected. For example, a protocol can be used to negotiate the peer and peer’s macAddress-set and / or AID on the EMLSR link. Figure 7 Part (A) of FIG. 1 relates to detection of communication on one of the peer’s EMLSR links (e.g., link 1) and not triggering EMLSR operation on other EMLSR links under the proposed scheme (e.g., non-AP MLD2 detects communication on link 1 of its peer non-AP MLD3, then non-AP MLD2 does not trigger EMLSR operation of non-AP MLD3 on other EMLSR links). Figure 7 Part (B) of FIG. 1 relates to detection of TXOP end of a peer STA under the proposed scheme. Referring to Figure 7When the EMLSR MLD detects the communication of the peer, in the case that the Point Coordination Function (PCF) inter-frame space (PIFS) idle is triggered, the EMLSR MLD can determine that the blocking EMLSR operation of the peer on the other link ends.

[0034] Figure 8 An example scenario 800 under the proposed scheme of the transparency of the AP MLD according to the present application is exemplified. According to the proposed scheme, the AP MLD can be provided with transparency when the AP MLD is a STR MLD and the non-AP MLD1 and the non-AP MLD2 are EMLSR MLDs associated with the AP MLD. Under the proposed scheme, when the non-AP MLD1 and the non-AP MLD2 intend to communicate through TDLS or P2P, the non-AP MLD1 and the non-AP MLD2 can inform each other and can set the power saving mode for the AP MLD on the link 1 and the link 2 at the same time. In addition, the non-AP MLD1 and the non-AP MLD2 can perform the hitchhiking Tx-on-Rx as described above on the power-save link with each other. In addition, the non-AP MLD1 and the non-AP MLD2 can perform TDLS-EMLSR or P2P on the power-save link through the negotiation frame.

[0035] Exemplary Implementations

[0036] Figure 9 An example system 900 having at least an example apparatus 910 and an example apparatus 920 is shown in accordance with an embodiment of the present application. Each of the apparatus 910 and the apparatus 920 can perform various functions to implement the schemes, techniques, processes, and methods described herein related to performance enhancements between non-AP MLDs through EMLSR in wireless communications, including the various designs, concepts, schemes, systems, and methods proposed above and the processes described below. For example, the apparatus 910 can be implemented in a STA 110 (or an MLD1 operating as a STA 110) and the apparatus 920 can be implemented in a STA 120 (or an MLD2 operating as a STA 120), or vice versa.

[0037] Each of devices 910 and 920 can be part of an electronic device, which can be a non-APSTA or AP STA, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in an STA, each of devices 910 and 920 can be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. Each of devices 910 and 920 can also be part of a machine-type device, which can be an IoT device, home device, wired communication device, or computing device, such as a non-movable or fixed device. For example, each of devices 910 and 920 can be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented in or as a network device, devices 910 and / or 920 can be implemented in a network node (e.g., an AP in a WLAN).

[0038] In some embodiments, each of devices 910 and 920 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. In all the above embodiments, each of devices 910 and 920 may be implemented in or as an STA or AP. Each of devices 910 and 920 may include Figure 9 At least some of the components shown. For example, Figure 9 The processors in the devices are, respectively, processor 912 and processor 922. Each of devices 910 and 920 may further include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of the present invention, and therefore, for simplicity and brevity, these components of devices 910 and 920 are not listed in the table. Figure 9 As shown in the image.

[0039] In an aspect, each of processor 912 and processor 922 can be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even though a singular term “processor” is used herein to refer to processor 912 and processor 922, according to the present application, each of processor 912 and processor 922 can include multiple processors and can include a single processor in some implementations and in other implementations, respectively. In another aspect, each of processor 912 and processor 922 can be implemented in the form of hardware (and, optionally, firmware) having electronic components including, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors configured and arranged to achieve a particular purpose, and / or one or more varactor diodes, for example. In other words, in at least some implementations, each of processor 912 and processor 922 can be an application-specific device that is specifically designed, arranged, and configured to perform a particular task, including tasks related to performance enhancements between non-AP MLDs over EMLSR in wireless communications.

[0040] In some implementations, apparatus 910 can also include a transceiver 916 coupled to processor 912. Transceiver 916 can include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. In some implementations, apparatus 920 can also include a transceiver 926 coupled to processor 922. Transceiver 926 can include a transmitter capable of wirelessly transmitting data and a receiver capable of wirelessly receiving data. Notably, while transceiver 916 and transceiver 926 are shown as being external to and separate from processor 912 and processor 922, respectively, in some implementations, transceiver 916 can be an integral part of processor 912 and / or transceiver 926 can be an integral part of processor 922 as a system on a chip (SoC).

[0041] In some implementations, the apparatus 910 can further include a memory 914 coupled to the processor 912 and accessible to the processor 912 for storing data. In some implementations, the apparatus 920 can also include a memory 924 coupled to the processor 922 and accessible to the processor 922 for storing data. Each of the memory 914 and the memory 924 can include a random-access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero capacitor RAM (Z-RAM). Alternatively or additionally, each of the memory 914 and the memory 924 can include a read-only memory (ROM), such as a mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of the memory 914 and the memory 924 can include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase change memory.

[0042] Each of the apparatus 910 and the apparatus 920 can be a communication entity capable of communicating with each other using various aspects presented in accordance with the present disclosure. For illustrative purposes and without limitation, a description of the capabilities of the apparatus 910 as a STA 110 and the apparatus 920 as a STA 120 is provided below. Notably, while a detailed description of the capabilities, functionalities, and / or technical features of the apparatus 920 is provided below, the same can apply to the apparatus 910, and a detailed description thereof is not provided for brevity. It is also noted that while example implementations described below are provided in the context of a WLAN, the same can be implemented in other types of networks as well.

[0043] Under various proposed schemes for performance enhancement between non-AP MLIDs through EMLSR in wireless communications according to the present disclosure, in a network environment 100 according to one or more of the IEEE 802.11 standards, the apparatus 910 is implemented in or as a first non-AP MLD (e.g., MLD1), and the apparatus 920 is implemented in or as a second non-AP MLD (e.g., MLD2). The processor 912 of the apparatus 910 can exchange capability information with the apparatus 920 in a handshake procedure over one of the multiple links via the transceiver 916. Further, the processor 912 can establish an EMLSR operation with the apparatus 920 over one or more of the multiple links via the transceiver 916. Each of the apparatus 910 (as the first non-AP MLD) and the apparatus 920 (as the second non-AP MLD) can listen on at least one of the multiple links.

[0044] In some embodiments, the EMLSR operation can be a P2P EMLSR operation or a TDLS EMLSR operation between the first non-AP MLD and the second non-AP MLD.

[0045] In some embodiments, in exchanging the EMLSR capability information, the processor 912 can exchange EMLSR operation information or an EMLSR capability field or both in a handshake flow. Further, the EMLSR operation information can include a channel number. In some embodiments, the EMLSR capability field can be in a TDLS multi-link element or a P2P Link Event Request sub-element.

[0046] In some embodiments, the processor 912 can perform certain operations when establishing the EMLSR operation. For example, the processor 912 can trigger the second non-AP MLD to perform EMLSR communication on one or more of the plurality of links. In addition, the processor 912 can switch to an available link of the plurality of links. In this case, after the first non-AP MLD and the second non-AP MLD establish the EMLSR operation on each other over the available link, the first non-AP MLD and the second non-AP MLD can be unaware of activities on other links of the plurality of links. In some embodiments, the processor 912 can perform certain operations in the triggering. For example, the processor 912 can send an RTS, a MU-RTS, a BSRP, or a PS-Poll to the second non-AP MLD over the available link. In addition, the processor 912 can receive a requested frame, such as a CTS, a BSR, or an ACK, from the second non-AP MLD over the available link in response.

[0047] In some embodiments, the processor 912 can detect availability of each of one or more of the plurality of links to select the one of the plurality of links available for the EMLSR operation when establishing the EMLSR operation. In some embodiments, the processor 912 can detect a preamble or a MAC header of a PPDU transmitted over one of the plurality of links when detecting the availability, because the link is unavailable if the PPDU transmitted over the link is from or to a peer device. Alternatively or additionally, the processor 912 can estimate a duration of a PPDU or a TXOP transmitted over an unavailable link based on information in the PPDU when detecting the link availability. In some embodiments, the processor 912 can establish the EMLSR operation over the available link of the plurality of links based on the estimation, taking the duration of the PPDU as a constraint when establishing the EMLSR operation. Alternatively or additionally, the processor 912 can apply the duration constraint obtained from the above estimation to at least one link of the plurality of links to which the first non-AP MLD and / or the second non-AP MLD is associated with an AP MLD when establishing the EMLSR operation.

[0048] In some embodiments, the processor 912 can perform one or more of the following when establishing the EMLSR operation: (a) notify an AP MLD of a power save mode over at least one link of the plurality of links to which the first non-AP MLD is associated with the AP MLD; (b) detect whether each of one or more of the plurality of links is unavailable; (c) perform a P2P EMLSR operation or a TDLS EMLSR operation over the at least one link on which the power save mode is set for the AP MLD.

[0049] In some embodiments, the processor 912 can perform additional operations. For example, the processor 912 can detect another EMLSR operation of the second non-AP MLD on an available link of the plurality of links. Further, the processor 912 can refrain from triggering an EMLSR operation of the second non-AP MLD on one or more other links of the plurality of links. In some implementations, in the detecting, the processor 912 can receive an RTS, an MU-RTS, a BSRP, a CTS2Self, and / or a PS-Poll whose TA or RA is the second non-AP MLD. Alternatively or additionally, in the detecting, the processor 912 can receive a CTS or an ACK whose RA is the second non-AP MLD or a peer STA of the second non-AP MLD. Alternatively or additionally, in the detecting, the processor 912 can receive a trigger frame whose AID is an AID of the second non-AP MLD. Alternatively or additionally, in the detecting, the processor 912 can detect a negotiation of another MAC address or AID by the second non-AP MLD for another EMLSR operation. Further, in the case that PIFS idle is triggered, the processor 912 can determine an end of the blocked EMLSR operation for the second non-AP MLD on the other link of the plurality of links.

[0050] In some embodiments, in establishing the EMLSR operation, the processor 912 can perform one or more of the following: (a) inform the AP MLD of a power save mode on at least one link of the plurality of links on which the first non-AP MLD is associated with the AP MLD; (b) detect whether each of one or more links of the plurality of links is unavailable; (c) perform a P2P EMLSR operation or a TDLS EMLSR operation on at least one link on which the power save mode is set for the AP MLD.

[0051] Exemplary procedures

[0052] Figure 10 An example procedure 1000 according to embodiments of the application is illustrated. The procedure 1000 can represent one aspect of implementing the various designs, concepts, schemes, systems, and methods presented above. More specifically, the procedure 1000 can represent one aspect of the presented concepts and schemes related to performance enhancements between non-AP MLDS in wireless communications by EMLSR according to the present application. The procedure 1000 can include one or more operations, actions, or functions as shown in one or more of steps 1010 and 1020. Although illustrated as discrete steps, various steps of the procedure 1000 can be divided into additional steps, combined into fewer steps, or eliminated, depending on the desired implementation. Further, the steps / sub-steps of the procedure 1000 can be performed in any order, in any combination, or in parallel, depending on the desired implementation. Figure 10The order in which the steps are shown or performed can be changed. Also, one or more steps / sub-steps of the process 1000 can be performed repeatedly or iteratively. The process 1000 can be implemented by or in the apparatus 910 and the apparatus 920, and any variants thereof. For illustrative purposes only and without limitation of scope, the process 1000 is described below in the context of the apparatus 910 implemented in or as a first non-AP MLD (e.g., MLD1) and the apparatus 920 implemented in or as a second non-AP MLD (e.g., MLD2) in a network environment 100 in accordance with one or more of the IEEE 802.11 standards. The process 1000 can begin at step 1010.

[0053] At step 1010, the process 1000 can involve the processor 912 exchanging EMLSR capability information with the apparatus 920 in a handshake procedure via the transceiver 916 over one of the plurality of links. The process 1000 can proceed from step 1010 to step 1020.

[0054] At step 1020, the process 1000 can involve the processor 912 establishing EMLSR operation with the apparatus 920 via the transceiver 916 over one or more of the plurality of links. Each of the apparatus 910 (first non-AP MLD) and the apparatus 920 (second non-AP MLD) can listen on at least one of the plurality of links.

[0055] In some embodiments, the EMLSR operation can be a P2P EMLSR operation or a TDLS EMLSR operation between the first non-AP MLD and the second non-AP MLD.

[0056] In some embodiments, in exchanging the EMLSR capability information, the process 1000 can involve the processor 912 exchanging EMLSR operation information or an EMLSR capability field, or both, in a handshake stream. Further, the EMLSR operation information can include a channel number. In some embodiments, the EMLSR capability field can be in a TDLS multi-link element or a P2P link event request sub-element.

[0057] In some embodiments, in establishing the EMLSR operation, the process 1000 can involve the processor 912 performing certain operations. For example, the process 1000 can involve the processor 912 triggering the second non-AP MLD to perform EMLSR communication on one or more of the plurality of links. In addition, the process 1000 can involve the processor 912 switching to an available (or not busy) link of the plurality of links. In such a case, after the first non-AP MLD and the second non-AP MLD establish the EMLSR operation with each other on the available link, neither the first non-AP MLD nor the second non-AP MLD is aware of the activities on other links of the plurality of links. In some embodiments, in the triggering, the process 1000 can involve the processor 912 performing certain operations. For example, the process 1000 can involve the processor 912 sending an initial frame such as an RTS, an MU-RTS, a BSRP, or a PS-Poll to the second non-AP MLD on the available link. In addition, the process 1000 can involve the processor 912 receiving a solicited frame such as a CTS, a BSR, or an ACK from the second non-AP MLD on the available link in response.

[0058] In some embodiments, in establishing the EMLSR operation, the process 1000 can involve the processor 912 detecting link availability of each of one or more of the plurality of links to select the link of the plurality of links that is available for the EMLSR operation. In some embodiments, in detecting the link availability, the process 1000 can involve the processor 912 detecting a preamble or a MAC header of a PPDU transmitted on one of the plurality of links as the link is unavailable when the PPDU transmitted on the link is from or to a peer device. Alternatively or additionally, in detecting the link availability, the process 1000 can involve the processor 912 estimating a duration of a PPDU or a TXOP transmitted on the unavailable link based on information in the PPDU. In some embodiments, in establishing the EMLSR operation, the process 1000 can involve the processor 912 performing the EMLSR operation on the available link of the plurality of links with the duration of the PPDU being considered as a constraint. Alternatively or additionally, in establishing the EMLSR operation, the process 1000 can involve the processor 912 applying the duration constraint obtained from the above estimation to at least one link of the plurality of links that the first non-AP MLD and / or the second non-AP MLD is associated with an AP MLD.

[0059] In some embodiments, in establishing the EMLSR operation, the process 1000 can involve the processor 912 performing one or more of: (a) informing the AP MLD of the power save mode on at least one link of the plurality of links on which the first non-AP MLD is associated with the AP MLD; (b) detecting whether each of one or more links of the plurality of links is unavailable; (c) performing a P2P EMLSR operation or a TDLS EMLSR operation on the at least one link on which the power save mode is set for the AP MLD.

[0060] In some embodiments, the process 1000 can involve the processor 912 performing additional operations. For example, the process 1000 can involve the processor 912 detecting another EMLSR operation of the second non-AP MLD on a first link of the plurality of links. Further, the process 1000 can involve the processor 912 refraining from triggering the EMLSR operation of the second non-AP MLD on one or more other links of the plurality of links. In some embodiments, in the detecting, the process 1000 can involve the processor 912 receiving an RTS, an MU-RTS, a BSRP, a CTS2Self, and / or a PS-Poll, where its TA or RA is the second non-AP MLD. Alternatively or additionally, in the detecting, the process 1000 can involve the processor 912 receiving a CTS or an ACK, where the RA is the second non-AP MLD or a peer STA of the second non-AP MLD. Alternatively or additionally, in the detecting, the process 1000 can involve the processor 912 receiving a trigger frame, where the AID is an AID of the second non-AP MLD. Alternatively or additionally, in the detecting, the process 1000 can involve the processor 912 detecting a negotiation of the second non-AP MLD for another MAC address or AID for another EMLSR operation. Further, the process 1000 can involve the processor 912 determining an end of the blocked EMLSR operation of the second non-AP MLD on the other links of the plurality of links in case of PIFS idle being triggered.

[0061] In some embodiments, in establishing the EMLSR operation, the process 1000 can involve the processor 912 performing one or more of: (a) informing the AP MLD of the power save mode on at least one link of the plurality of links on which the first non-AP MLD is associated with the AP MLD; (b) detecting whether each of one or more links of the plurality of links is unavailable; (c) performing a P2P EMLSR operation or a TDLS EMLSR operation on the at least one link on which the power save mode is set for the AP MLD.

[0062] Supplemental Explanation

[0063] The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being "operably couplable", to each other to achieve the desired functionality. Suitable "associations" in this context can include connections, interchanges, links, communications, interworking, interoperability, etc., between various software and / or hardware components, and / or any group thereof. The term "associated with" as used herein can include connected with, contained within, interchanged, linked to, in communication with, etc., one or more other parts.

[0064] Also, to the extent that any numeral and / or singular term herein implies more than one application, the singular and / or plural sense of such can be changed as appropriate to fit the context of this disclosure. Various single / plural interchanges can be explicitly set forth herein for illustrative purposes.

[0065] In addition, those skilled in the art will appreciate that, in general, the terms used herein, and especially in the appended claims (e.g., in the body of the appended claims), are generally intended as "open" terms (e.g., the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "including" should be interpreted as "including but not limited to," etc.). Those skilled in the art will further understand that, unless otherwise indicated herein, the singular forms of terms used herein are intended to include the plural forms of those terms. Those skilled in the art will appreciate that, when certain claims are introduced that recite a specific number of an introduced claim recitation, that such an intent is expressly recited in the claim and that no such intent exists when such a recitation is not present. For example, as an aid in understanding, the appended claims can contain the use of the introductory phrases "at least one" and "one or more" of an introduced claim recitation. However, the use of such phrases should not be interpreted as implying that any specific claim limitation that follows the introductory phrase is limited to only one such claim limitation of the introduced claim recitation, even when the same claim includes the introductory phrase "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a and / or an" should be interpreted to mean "at least one" or "one or more"), the same applies to the use of the definite article to introduce a claim recitation. In addition, even when a specific number of an introduced claim recitation is expressly recited, those skilled in the art will recognize that such a recitation is to be interpreted to mean at least the recited number (e.g., an unqualified recitation of "two of the introduced claim recitations" means at least two of the introduced claim recitations or two or more of the introduced claim recitations) absent further modification. Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general, such a construction is intended to be interpreted in the same manner as "at least one of A, B, and C" even when the conjunctive phrase does not expressly appear. By way of example, the phrase "at least one of A, B, or C" should be construed to mean at least one of A, at least one of B, at least one of C, at least one of A and B, at least one of A and C, at least one of B and C, and at least one of A, B, and C. An exception to this is the use of two "at a time" or "two at a time" in the claims to indicate that an element must be present in at least one but only one of the claim limitations. In those instances, the phrase "two at a time" or "two at a time" is to be interpreted to mean that the element is to be present in at least one, but only one, of the claim limitations; e.g., the phrase "two at a time" preceding the introductory clause of a claim limitation is to be interpreted to mean that the element is to be present in at least one, but only one, of the claim limitations. Those skilled in the art will further understand that any disjunctive word or phrase, such as "among

[0066] In light of the above, it will be appreciated that the various implementations described herein have been described for the purpose of illustration only and that various modifications are possible without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, the true scope and spirit being indicated by the following claims.

Claims

1. A method of enhanced multi-link single radio, EMLSR, operation, comprising: exchanging, by a first non-access point, non-AP, multi-link device, MLD, with a second non-AP MLD, EMLSR capability information in a handshake procedure over one of a plurality of links; and establishing, by the first non-AP MLD, EMLSR operation with the second non-AP MLD over one or more of the plurality of links, wherein each of the first non-AP MLD and the second non-AP MLD listens on at least one of the plurality of links; wherein establishing the EMLSR operation comprises: triggering the second non-AP MLD to perform EMLSR communication over the one or more of the plurality of links; and switching to an available link of the plurality of links, wherein the first non-AP MLD and the second non-AP MLD are unaware of activities on other links of the plurality of links after the first non-AP MLD and the second non-AP MLD establish the EMLSR operation with each other over the available link.

2. The method of claim 1, wherein the EMLSR operation is a point-to-point, P2P, EMLSR operation or a tunneled direct link setup, TDLS, EMLSR operation between the first non-AP MLD and the second non-AP MLD.

3. The method of claim 1, wherein, the exchange of the EMLSR capability information comprises exchanging an EMLSR operation information or an EMLSR capability field or both in a handshake flow.

4. The method of claim 3, wherein, the EMLSR capability field is in a TDLS multi-link element or in a P2P link event request sub-element.

5. The method of claim 1, wherein, the triggering comprises: sending an initial frame to the second non-AP MLD over the available link, the initial frame being a request to send, RTS, a multi-user request to send, MU-RTS, a buffer status report poll, BSRP, or a power save poll, PS-Poll; and in response, receiving a requested frame from the second non-AP MLD over the available link, the requested frame being a clear to send, CTS, a buffer status report, BSR, or an acknowledgement, ACK.

6. The method of claim 1, wherein establishing the EMLSR operation comprises: detecting link availability of each of the one or more of the plurality of links to select an available link of the plurality of links for the EMLSR operation.

7. The method of claim 6, wherein, the detecting link availability comprises detecting a preamble or a media access control, MAC, header of a physical layer protocol data unit, PPDU, transmitted over one of the plurality of links, wherein a link carrying the PPDU is unavailable in case the transmitted PPDU is from or to a peer device.

8. The method of claim 7, wherein, the detecting link availability comprises estimating a duration of the PPDU or a transmission opportunity, TXOP, transmitted over an unavailable link based on information in the PPDU.

9. The method of claim 8, wherein, the establishing the EMLSR operation comprises establishing the EMLSR operation over the available link of the plurality of links with considering a duration of the PPDU as a constraint. the establishing the EMLSR operation comprises establishing the EMLSR operation over the available link of the plurality of links with considering a duration of the PPDU as a constraint.

10. The method of claim 8, wherein, Establishing the EMLSR operation includes applying a duration constraint obtained from the estimation to at least one link of the plurality of links on which the first non-AP MLD and / or the second non-AP MLD is associated with the AP MLD.

11. The method of claim 1, further comprising: detecting, by the first non-AP MLD, another EMLSR operation of the second non-AP MLD on an available link of the plurality of links; and avoiding triggering the EMLSR operation of the second non-AP MLD on one or more other links of the plurality of links.

12. The method of claim 11, wherein the detecting comprises receiving an RTS, MU-RTS, BSRP, CTS2Self, or PS-Poll, wherein a transmitter address (TA) or a receiver address (RA) is the second non-AP MLD.

13. The method of claim 11, wherein, the detecting comprises receiving a CTS or an ACK, wherein a receiver address (RA) is the second non-AP MLD or a peer STA of the second non-AP MLD.

14. The method of claim 11, wherein, the detecting comprises receiving a trigger frame, an association identifier (AID) of which is an association identifier of the second non-AP MLD.

15. The method of claim 11, wherein the detecting comprises detecting a negotiation of another medium access control (MAC) address or AID by the second non-AP MLD for the another EMLSR operation.

16. The method of claim 11, further comprising: determining, by the first non-AP MLD, an end of a blocked EMLSR operation of the second non-AP MLD on another link of the plurality of links in case of a point coordination function interframe space (PIFS) idle being triggered.

17. The method of claim 1, wherein establishing the EMLSR operation includes performing one or more of: informing a power save mode to the AP MLD on at least one link of the plurality of links on which the first non-AP MLD is associated with the AP MLD; detecting whether each of the one or more links of the plurality of links is unavailable; and performing a P2P EMLSR operation or a TDLS EMLSR operation on the at least one link on which the power save mode is set for the AP MLD.

18. The method of claim 10, wherein establishing the EMLSR operation includes performing one or more of: informing a power save mode to the AP MLD on at least one link of the plurality of links on which the first non-AP MLD is associated with the AP MLD; detecting whether each of the one or more links of the plurality of links is unavailable; and performing a P2P EMLSR operation or a TDLS EMLSR operation on the at least one link on which the power save mode is set for the AP MLD.

19. An apparatus implementable in a first non-AP MLD, comprising: a transceiver configured to wirelessly communicate; and ​ a processor coupled to the transceiver and configured to perform the method of any one of claims 1 to 18.

Images