TW202322657A - Method and apparatus for an enhanced multi-link single radio (emlsr) operation - Google Patents

Abstract

Techniques pertaining to performance enhancement between non-access point (non-AP) multi-link devices (MLDs) by enhanced multi-link single radio (EMLSR) in wireless communications are described. A first non-AP MLD exchanges EMLSR capability information with a second non-AP MLD in a handshake procedure on one of a plurality of links. The first non-AP MLD then establishes an EMLSR operation with the second non-AP MLD on one or more links of the plurality of links. Each of the first non-AP MLD and the second non-AP MLD listens on at least one of the plurality of links.

Description

Method and apparatus for enhanced multi-link single radio operation

The present invention relates to wireless communications, and more particularly to pervasive enhanced multi-link single radio (EMLSR) operation in wireless communications.

Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims claimed and are not admitted to be prior art by inclusion in this section.

In wireless communications based on Institute of Electrical and Electronics Engineers (IEEE) standards, such as Wi-Fi 7, EMLSR is expected to be a multi-link device for a given non-AP (non-AP) device, MLD) key operating modes. 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 MLD in the P2P/TDLS-EMLSR environment remains to be specified. Therefore, a solution to the EMLSR operation that is ubiquitous in wireless communication is needed to achieve performance enhancement between non-AP MLDs through the EMLSR.

The following summary is exemplary only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, highlights, benefits and advantages of the novel and non-obvious technologies described herein. Selected implementations are further described in the detailed description below. Accordingly, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

An object of the present invention is to provide schemes, concepts, designs, techniques, methods and devices related to performance enhancement between non-AP MLDs through EMLSR in wireless communication. Under the various schemes proposed according to the present invention, an access point (AP) can avoid unnecessary retries on unexpected links, because such retries end up causing unexpected data packet loss and also reduce AP contention opportunities. Under various schemes proposed according to the present invention, performance can be enhanced through EMLSR between non-AP MLDs. Accordingly, various solutions proposed by the present invention may solve or otherwise alleviate the problems described herein.

In one aspect, a method may involve a first non-AP MLD and a second non-AP MLD exchanging capability information during a handshake over one of a plurality of links. The method may also involve the first non-APMLD establishing EMLSR operation with the second non-APMLD on one or more of the plurality of links. Each of the first non-AP MLD and the second non-AP MLD may listen on at least one of the plurality of links.

In another aspect, an apparatus implementable in a first non-AP MLD can include a transceiver configured to communicate wirelessly and a processor coupled to the transceiver. The processor may exchange capability information during a handshake with the second non-AP MLD via the transceiver on one of the links. The processor may also establish EMLSR operation with the second non-AP MLD on one or more of the plurality of links via the transceiver. Each of the first non-AP MLD and the second non-AP MLD may listen on at least one of the plurality of links.

It is worth noting that while the description provided here can be in the context of certain radio access technologies, networks and network topologies (e.g. Wi-Fi), the concepts, schemes and any variants/derivatives thereof can be Enabled in, for and via other types of radio access technologies, networks and network topologies such as but not limited to Long-Term Evolution (LTE), LTE-A, LTE-A Pro, 5G, New Radio (New Radio, NR), Internet-of-Things (IoT), Narrow Band Internet of Things (NB-IoT) and Industrial Internet of Things (IIoT). Accordingly, the scope of the present invention is not limited to the examples described herein.

Detailed embodiments and implementations of the claimed subject matter are disclosed herein. It should be understood, however, that the detailed embodiments and implementations disclosed are merely illustrative of the various forms in which the claimed subject matter can be embodied. This invention may, however, be embodied in many different forms and should not be construed as limited to only the illustrated embodiments and implementations. These example embodiments and implementations are provided so that this description will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the following description, details of known features and techniques are omitted to avoid unnecessarily obscuring the embodiments and implementations of the invention.

overview

Embodiments according to the present invention relate to various technologies, methods, schemes and/or solutions related to performance enhancement between non-AP MLDs through EMLSR in wireless communication. According to the invention, various possible solutions can be implemented individually or in combination. That is, while these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one combination or another.

FIG. 1 illustrates an example network environment 100 in which various solutions and schemes according to the present invention may be implemented. 2 to 10 illustrate implementation examples of various proposals in the network environment 100 according to the present invention. The following description of various proposed solutions is provided with reference to Figures 1-10.

As shown in FIG. 1 , the network environment 100 may involve at least a first communicating entity or STA 110 in wireless communication with a second communicating entity or STA 120 . Each of STA 110 and STA 120 may be an access point (AP) STA or a non-access point (non-AP, non-AP) STA, respectively. Each of STA 110 and STA 120 may belong to a respective MLD capable of operating with EMLSR enabled. For example, STA 110 may be affiliated with a first non-AP MLD (MLD1), while STA 120 may be affiliated with a second non-AP MLD (MLD2). In some cases, STA 110 and STA 120 may be associated with a basic service set (BSS) according to one or more IEEE 802.11 standards such as Wi-Fi 7 (eg, IEEE 802.11be and future developed standards) couplet. STA 110 and STA 120 may be configured to communicate with each other by utilizing various proposed schemes described herein related to performance enhancement between non-AP MLDs through EMLSR in wireless communication. It should be noted that although various proposed solutions may be described individually or independently below, in actual implementation, each proposed solution may be used individually or independently, or some or all of the proposed solutions may be used in combination.

In P2P/TDLS EMLSR regarding listening, detection and transmission, both the first non-AP MLD and the second non-AP MLD may be in P2P communication and operate in EMLSR mode. Two EMLSR non-AP MLDs can listen to two or more links and can switch to the same link when EMLSR communication between two non-AP MLDs starts. This may also apply to other MLDs, such as mixed-mode non-AP MLDs and/or non-simultaneous-transmission-and-reception (NSTR) non-AP MLDs. Compared with the single-link P2P scenario, in the scenario of high network load, the delay and throughput can be significantly improved.

In various proposals according to the invention, in an EMLSR operation between two EMLSR non-AP MLDs (referred to herein as "MLD1" and "MLD2"), initially, the first non-AP MLD (MLD1) and the second A non-AP MLD (MLD2) may listen to multiple EMLSR-enabled links, such as a first link (referred to herein as "Link 1") and a second link (referred to herein as "Link 2"). MLD1 can then trigger its peer EMLSR non-AP MLD (or MLD2) for EMLSR communication. MLD1 can send request to send (request-to-send, RTS), multi-user request to send (multi-user request-to-send, MU-RTS), buffer status report polling (buffer status report poll) on link 1 , BSRP) and/or power-saving poll (PS-Poll) as an initial physical-layer protocol data unit (physical-layer protocol data unit, PPDU) to trigger MLD2 to perform EMLSR operation on link 1. When detecting RTS/MU-RTS/BSRP/PS-Poll on link 1, MLD2 can send (clear-to-send, CTS), buffer status report (buffer status report, BSR) and/or acknowledgment (ACK) in response. Therefore, both MLD1 and MLD2 may switch to a link (eg, link 1 ) for EMLSR communication, which may include data exchange and block acknowledgment (BA). That is to say, when MLD1 sends RTS/MU-RTS/BSRP/PS-Poll, MLD1 can switch to link 1 (so that MLD1 cannot receive data on link 2) for EMLSR communication, when MLD2 sends CTS/BSR /ACK, MLD2 can switch to link 1 (so that MLD2 cannot receive data on link 2) for EMLSR operation. Therefore, during the EMLSR communication phase, MLD1 and MLD2 cannot receive data on other EMLSR links (such as link 2).

Fig. 2 illustrates an example scenario 200 under the proposed scheme for non-AP EMLSR MLD operation, such as P2P/TDLS, according to the present invention. In Figure 2, there are 4 devices, namely EMLSR non-AP MLD1 (with link 1 and link 2), EMLSR non-AP MLD2 (with link 1 and link 2), AP (with link 1) , Non-AP. Among them, in Figure 2, "EMLSR" on the main link indicates communication between AP and non-AP MLD, "P2P EMLSR" indicates point-to-point communication between non-AP MLD, and "other communication" indicates communication between AP and non-AP Communications (such as "other communications" in gray background in Figure 2). Under the proposed scheme, the same links that can be enabled between EMLSR non-AP MLDs and APs. 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 when the primary link (e.g., link 1) is busy (e.g., unavailable ), communicate on the secondary link (or auxiliary link) (eg, link 2). Even if no primary link is defined among the multiple links, the EMLSR non-AP MLD can detect that other of the multiple links are busy and the peer MLD is not included in the link. Under the proposed scheme, regarding capability handshakes, P2P/TDLS STAs can negotiate EMLSR capabilities and EMLSR link sets for EMLSR operation between STAs. In addition, regarding the medium access control (medium access control, MAC) protocol, when the primary link is busy and the AP is transparent to the EMLSR operation on the secondary When the EMLSR operation between STAs), the non-AP STA can perform the EMLSR operation on the secondary (or secondary) link. Additionally, non-APMLDs can also perform EMLSR operations on the primary link with the knowledge of the AP.

Fig. 3 illustrates an example scenario 300 under the proposed scheme according to the present invention. Compared with Fig. 2, under the proposed scheme shown in Fig. 3, the AP affiliated to the MLD can support the detection of P2P/TDLS EMLSR operation between EMLSR MLDs, and the AP MLD can simultaneously send and receive (simultaneous -transmission-and-reception, MLD of STR). Furthermore, the AP can know that a non-AP belonging to another MLD is communicating (with another non-AP). As shown in Figure 3, when P2P (or TDLS) EMLSR communication between two non-AP MLDs occurs on the secondary (or secondary) link, and one or more other operations occur between the AP and the two non-AP MLDs When one or two of the main links (such as "other communication" without gray background in Figure 3), the AP can know the P2P (or TDLS) EMLSR communication on the auxiliary (or auxiliary) link. Therefore, Avoid triggering any communication with two non-AP MLDs on other links with EMLSR enabled to reduce or minimize the initial trigger cost.

Fig. 4 illustrates an example scenario 400 under the proposed scheme regarding capability handshaking according to the present invention. Under the proposed scheme, the handshake protocol can be used for TDLS and/or P2P EMLSR operation. For example, an EMLSR capability field can be added in a handshake flow (e.g., in a multilink element, such as a TDLS multilink element, or in a Peer-to-Link Event Request (Peer-to -Peer Link Event Request) child element). Alternatively or additionally, EMLSR operational information (eg, channel number) may be added to the handshake flow (eg, in a TDLS multilink element). EMLSR TDLS links can be independent of links associated with APs. Therefore, it is contemplated that at least one of the multiple links may be associated with an AP for an EMLSR TDLS enabled STA.

Referring to part (A) of Figure 4, the AP can communicate with the first non-AP MLD on the first link of multiple links including the first link (Link 1) and the second link (Link 2). 1 (non-AP1) and each of the second non-AP MLD 2 (non-AP2). After the handshake between the first non-AP MLD1 and the second non-AP MLD2, the two non-AP MLDs can perform EMLSR operations on link 1 and link 2. Referring to part (B) of Figure 4, the AP can be on multiple links including the first link (link 1), the second link (link 2) and the third link (link 3) On the first link, the first non-AP MLD 1 of the first enhanced multi-link multiple radios (EMLMR) MLD (EMLMR MLD1) and the second non-AP MLD of the second EMLMR MLD (EMLMR MLD2) Each of AP MLD2 is associated. For 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 , link 2 and link 3 can be EMLSR links. For 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 , link 2 and link 3 can be EMLSR links. After the handshake between the first non-AP MLD and the second non-AP MLD, the two STAs can perform EMLSR operations on link 2 and link 3 .

Fig. 5 illustrates an example scenario 500 under the proposed scheme for EMLSR MAC protocol between non-AP MLDs according to the present invention. Referring to Figure 5, the first EMLSR non-AP MLD (MLD1) can trigger the peer EMLSR non-AP MLD (MLD2) for EMLSR communication. MLD1 and MLD2 may switch to the link carrying the initial PPDU (the initial PPDU for this transmission is 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 initial PPDU to trigger MLD2 to perform EMLSR operation. It is worth noting that this may not apply to EMLSR between one AP MLD and another AP MLD.

Fig. 6 illustrates an example scenario 600 under the proposed scheme regarding EMLSR hitchhiking (transmission-on-reception, Tx-on-Rx) according to the present invention. EMLSR hitchhiking can be, for example, TLDS/P2P EMLSR communication on a link (e.g. secondary link) during other communications on a link (e.g. primary link) in the upper part of Figure 6 . Under the proposed scheme, the EMLSR MLD can detect that one or more links are busy and determine or otherwise obtain certain information. Depending on the proposed scheme, an EMLSR MLD may determine that a transmission on one or more busy links is not addressed to or destined for the EMLSR MLD (not2me), is not addressed to or destined for a peer EMLSR MLD (not2peer), and/or is not from Peer-to-peer EMLSR MLD (notfrompeer). For example, such determination of not2me/not2peer/notfrompeer can be based on preamble (eg HE-SIG-B field or EHT-SIG field) or MAC header (eg address 1 or address 2) in the PPDU. Furthermore, under the proposed scheme, EMLSR MLD can obtain the duration of PPDUs and/or transmission opportunities (TXOPs) of busy links. For example, the TXOP/PPDU duration can be estimated based on the preamble in the PPDU. Furthermore, under the proposed scheme, EMLSR MLD can access idle links with a duration limit. For example, an EMLSR MLD may conduct TLDS/P2P EMLSR communication on a non-busy (idle) link during the duration of a busy link's PPDU and/or a Transmission Opportunity (TXOP), thus requiring a busy link's PPDU and/or The duration of the TXOP. Furthermore, under the proposed scheme, the above restrictions can be applied to certain links of EMLSR MLD (e.g., the main link) to achieve AP MLD transparency (e.g., to provide AP MLD with transparency about EMLSR operations so that AP MLD know this). For example, primary or secondary links may be defined by the EMLSR MLD itself.

FIG. 7 illustrates an example scenario 700 under the proposed scheme for detecting EMLSR operation of peer STAs according to the present invention. The detection of the EMLSR operation of the peer STA can be implemented in one or more of the following ways. Under the proposed scheme, if EMLSR MLD receives RTS, MU-RTS, BSRP, PS-Poll or clear-to-send-to-self (CTS2self) whose transmitter address (transmitter address, TA) is the peer EMLSR MLD, Then the EMLSR MLD may not trigger the peer MLD on another EMLSR link. Under the proposed scheme, after receiving a clear-to-send (CTS) or ACK (whose receiver address (RA) is a hidden node), the EMLSR MLD needs to know that its peer The address of the peer's peer. For example, an EMLSR element may be used to specify a peer's peer's link address. It's worth noting that this could be a false alarm if the peer's peer is the AP. According to the proposed scheme, after receiving a triggered frame with the association identifier (AID) being the peer's AID, the EMLSR MLD may require additional information, such as the BSS ID, to identify the STA triggered by the target. For example, a protocol can be used to negotiate AID and TA information. Under the proposed scheme, the EMLSR operation of a peer STA can be detected when it is detected that the peer STA is negotiating with its peer an additional MAC address for EMLSR operation (e.g., in P2P mode). For example, a protocol can be used to negotiate the macAddress-set and/or AID of peers and peers on an EMLSR link. Part (A) of Figure 7 involves detecting communication on one of the peer's EMLSR links (e.g., link 1) under the proposed scheme, and not triggering EMLSR actions on other EMLSR links (e.g., non-AP MLD2 detects communication on link 1 of its peer non-AP MLD3, then non-AP MLD2 does not trigger non-AP MLD3's EMLSR operation on other EMLSR links). Part (B) of Fig. 7 involves detecting the end of TXOP of a peer STA under the proposed scheme. Referring to part (B) of Figure 7, when peer-to-peer communication is detected, in the case where the Point Coordination Function (PCF) inter-frame space (PIFS) idle is triggered, The EMLSR MLD can determine the end of a peer's blocking EMLSR operation (blocking EMLSR operation) on other links.

Fig. 8 illustrates an example scenario 800 under the proposed scheme regarding the transparency of AP MLD according to the present invention. According to the proposed scheme, transparency can be provided for the AP MLD when the AP MLD is a STR MLD and the non-AP MLD1 and non-AP MLD2 are EMLSR MLDs associated with the AP MLD. Under the proposed scheme, when non-AP MLD1 and non-AP MLD2 intend to communicate via TDLS or P2P, non-AP MLD1 and non-AP MLD2 can notify each other, and can set a province for AP MLD on both link 1 and link 2. electric mode. In addition, non-AP MLD1 and non-AP MLD2 may perform hitchhiking Tx-on-Rx (hitchhiking Tx-on-Rx) with each other on a power-save link as described above. In addition, non-AP MLD1 and non-AP MLD2 can implement TDLS-EMLSR or P2P on the power-saving link through a negotiation frame.

Exemplary Implementation

Figure 9 shows an example system 900 having at least an example device 910 and an example device 920 in accordance with an embodiment of the invention. Each of the device 910 and the device 920 can perform various functions to implement the solutions, techniques, procedures and methods described herein related to performance enhancement between non-AP MLDs through EMLSR in wireless communication, including various designs proposed above, Concepts, schemes, systems and methods and processes described below. For example, means 910 may be implemented in STA 110 (or MLD1 operating as STA 110 ), and means 920 may be implemented in STA 120 (or MLD2 operating as STA 120 ), or vice versa.

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

In some embodiments, each of apparatus 910 and apparatus 920 may be implemented in the form of one or more integrated circuit (IC) dies, such as, but not limited to, one or more single-core processors, one or more Multiple multicore processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. In the foregoing various solutions, each of the apparatus 910 and the apparatus 920 may be implemented in or as an STA or an AP. Each of apparatus 910 and apparatus 920 may include at least some of those elements shown in FIG. 9 . For example, processors in FIG. 9 such as processor 912 and processor 922, respectively. Each of the device 910 and the device 920 may further include one or more other elements not related to the proposed solution of the present invention (for example, an internal power supply, a display device, and/or a user interface device), and thus, for the sake of simplicity And for brevity, neither of these elements of device 910 and device 920 are shown in FIG. 9 .

In one 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. The form is realized. That is, even though the singular term "processor" is used herein to refer to processor 912 and processor 922, according to the present invention, each of processor 912 and processor 922 may include multiple processor and may include a single processor in other embodiments. In another aspect, each of processor 912 and processor 922 may be implemented in the form of hardware (and optionally firmware) having electronic components including, for example but not limited to, one or more electronic crystal, 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 specific purpose, and and/or one or more varactor diodes. In other words, in at least some embodiments, each of the processor 912 and the processor 922 may be a dedicated device, which is specially designed, arranged and configured to perform specific tasks, including communicating with the Tasks related to performance enhancement between AP MLDs.

In some implementations, the apparatus 910 may also include a transceiver 916 coupled to the processor 912 . Transceiver 916 may include a transmitter capable of wirelessly transmitting material and a receiver capable of wirelessly receiving material. In some implementations, the apparatus 920 can also include a transceiver 926 coupled to the processor 922 . Transceiver 926 may include a transmitter capable of wirelessly transmitting material and a receiver capable of wirelessly receiving material. 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 may be implemented as a system-on-chip (SoC ) of the processor 912 and/or the transceiver 926 may be an integral part of the processor 922 as an SoC.

In some implementations, the device 910 may further include a memory 914 coupled to the processor 912 and capable of being accessed by the processor 912 . In some implementations, the device 920 may further include a memory 924 coupled to the processor 922 and capable of being accessed by the processor 922 . Each of memory 914 and memory 924 may include random-access memory (random-access memory, RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and/or Zero-capacitance RAM (Z-RAM). Alternatively or additionally, each of memory 914 and memory 924 may include read-only memory (read-only memory, ROM), such as mask ROM, programmable ROM (PROM), erasable Programmable ROM (EPROM) and/or Electrically Erasable Programmable ROM (EEPROM). Alternatively or additionally, each of memory 914 and memory 924 may include non-volatile random-access memory (non-volatile random-access memory, NVRAM), such as flash memory, solid-state memory , ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and/or phase change memory.

Each of the device 910 and the device 920 may be a communication entity capable of communicating with each other using various proposed schemes according to the present invention. For illustrative purposes and not limitation, a description of the capabilities of device 910 as STA 110 and device 920 as STA 120 is provided below. It is worth noting that although a detailed description of the capabilities, functions and/or technical features of the device 920 is provided below, the same applies to the device 910, and a detailed description thereof is not provided for brevity only. It is also worth noting that while the example implementations described below are provided in the context of a WLAN, they can be implemented in other types of networks as well.

According to various proposals for performance enhancement between non-AP MLDs through EMLSR in wireless communication according to the present invention, in the network environment 100 according to one or more standards in the IEEE 802.11 standard, the device 910 is in the first non-AP The AP MLD (eg, MLD1 ) is implemented in or as a first non-AP MLD, and the apparatus 920 is implemented in a second non-AP MLD (eg, MLD2 ) or as a second non-AP MLD. The processor 912 of the device 910 may exchange capability information with the device 920 through the transceiver 916 during a handshake process on one of the links. Additionally, processor 912 may establish EMLSR operation with device 920 via transceiver 916 over one or more of the plurality of links. Each of apparatus 910 (as the first non-AP MLD) and apparatus 920 (as the second non-AP MLD) may listen on at least one of the plurality of links.

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

In some implementations, when exchanging EMLSR capability information, processor 912 may exchange EMLSR operational information or EMLSR capability fields or both in a handshake flow. In addition, the EMLSR operation information may include a channel number. In some implementations, the EMLSR capability field may be in the TDLS multi-link element or in the P2P Link Event Request (P2P Link Event Request) sub-element.

In some implementations, processor 912 may perform certain operations when establishing EMLSR operation. For example, processor 912 may trigger the second non-AP MLD to perform EMLSR communication on one or more of the plurality of links. In addition, the processor 912 may switch to an available link (available link) among the plurality of links. In this case, after the first non-AP MLD and the second non-AP MLD have established EMLSR operation between each other on available links, the first non-AP MLD and the second non-AP MLD may not be aware of other activity on the link. In some implementations, upon triggering, processor 912 may perform certain operations. For example, processor 912 may send RTS, MU-RTS, BSRP, or PS-Poll to the second non-AP MLD on an available link. Additionally, processor 912 may receive a requested frame, such as a CTS, BSR or ACK, from the second non-AP MLD on an available link in response.

In some implementations, when establishing an EMLSR operation, the processor 912 may detect the availability (availability) of each link in one or more links among the plurality of links, so as to select the availability among the plurality of links The link that EMLSR operates on. In some implementations, when detecting availability, the processor 912 may detect the preamble or MAC header of the PPDU transmitted on one of the links, because if the PPDU transmitted on the link is from the peer device or to a peer device, the link is unavailable. Alternatively or additionally, upon detecting link availability, processor 912 may estimate the duration of the PPDU or TXOP transmitted on the unavailable link based on information in the PPDU. In some implementations, when establishing EMLSR operation, processor 912 may establish EMLSR operation on an available link among the plurality of links based on the estimation, considering the duration of the PPDU as a constraint. Alternatively or additionally, when establishing EMLSR operation, the processor 912 may apply the duration constraints obtained from the above estimation to multiple links in which the first non-AP MLD and/or the second non-AP MLD are related to the AP MLD connected to at least one link.

In some implementations, when establishing EMLSR operation, the processor 912 may perform one or more of the following: (a) send a message to the AP on at least one link in which the first non-AP MLD is associated with the AP MLD in the plurality of links MLD notifies power saving mode; (b) detects whether each link in one or more links of multiple links is unavailable; (c) on at least one link for which power saving mode for AP MLD is set Execute P2P EMLSR operation or TDLS EMLSR operation.

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

In some implementations, when establishing EMLSR operation, the processor 912 may perform one or more of the following: (a) send a message to the AP on at least one link in which the first non-AP MLD is associated with the AP MLD in the plurality of links MLD notifies power saving mode; (b) detects whether each of one or more of the multiple links is unavailable; (c) executes on at least one link for which AP MLD has set power saving mode P2P EMLSR operation or TDLS EMLSR operation.

Exemplary process

Figure 10 illustrates an example process 1000 in accordance with an embodiment of the invention. Process 1000 may represent one aspect of implementing the various designs, concepts, solutions, systems and methods presented above. More specifically, process 1000 may represent an aspect of the proposed concepts and schemes related to performance enhancement between non-AP MLDs through EMLSR in wireless communications according to the present invention. Process 1000 may include one or more operations, actions or functions as indicated by one or more of steps 1010 and 1020 . Although shown as discrete steps, various steps of process 1000 may be divided into additional steps, combined into fewer steps, or eliminated, depending on the desired implementation. Additionally, the steps/sub-steps of process 1000 may be performed in the order shown in FIG. 10 or in a different order. Additionally, one or more steps/sub-steps of process 1000 may be performed repeatedly or iteratively. Process 1000 may be implemented by or within apparatus 910 and apparatus 920 and any variations thereof. For illustrative purposes only and not limiting in scope, process 1000 is hereinafter described in the context of apparatus 910 and apparatus 920 in networked environment 100 according to one or more of the IEEE 802.11 standards. The apparatus 920 is implemented in or as the first non-AP MLD (eg, MLD1 ), and the apparatus 920 is implemented in or as the second non-AP MLD (eg, MLD2 ). Process 1000 may begin at step 1010 .

At step 1010, process 1000 may involve processor 912 exchanging EMLSR capability information with device 920 via transceiver 916 in a handshake process over one of a plurality of links. Process 1000 may proceed from step 1010 to step 1020 .

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

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

In some implementations, when exchanging EMLSR capability information, process 1000 may involve processor 912 exchanging EMLSR operational information or EMLSR capability fields, or both, in a handshake flow. Additionally, the EMLSR operation information may include channel numbers. In some implementations, the EMLSR Capability field may be in the TDLS Multilink element or in the P2P Link Event Request sub-element.

In some implementations, process 1000 may involve processor 912 performing certain operations in establishing EMLSR operation. For example, process 1000 may involve processor 912 triggering a second non-AP MLD to perform EMLSR communications on one or more of a plurality of links. Additionally, process 1000 may involve 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 EMLSR operation on each other's available links, neither the first non-AP MLD nor the second non-AP MLD is aware of other links on multiple links. Activities on the road. In some implementations, in a trigger, process 1000 may involve processor 912 performing certain operations. For example, process 1000 may involve processor 912 sending an initial frame, such as an RTS, MU-RTS, BSRP, or PS-Poll, to a second non-AP MLD over an available link. Additionally, process 1000 may involve processor 912 receiving a solicited frame, such as a CTS, BSR, or ACK, from the second non-AP MLD on an available link in response.

In some implementations, when establishing EMLSR operation, process 1000 may involve processor 912 detecting the link availability (link availability) of each of one or more of the plurality of links to select multiple Links that can be used for EMLSR operation among the links. In some implementations, when detecting link availability, process 1000 may involve processor 912 detecting the preamble or MAC header of a PPDU transmitted on one of the links because when the PPDU transmitted on that link The link is unavailable when sending from or to a peer. Alternatively or additionally, upon detecting link availability, process 1000 may involve processor 912 estimating the duration of a PPDU or TXOP transmitted on the unavailable link based on information in the PPDU. In some implementations, in establishing the EMLSR operation, the process 1000 may involve the processor 912 performing the EMLSR operation on available links among the plurality of links considering the duration of the PPDU as a constraint. Alternatively or additionally, in establishing EMLSR operation, process 1000 may involve processor 912 applying the duration constraints obtained from the above estimation to the first non-AP MLD and/or the second non-AP MLD and At least one link associated with the AP MLD.

In some implementations, in establishing EMLSR operation, process 1000 may involve processor 912 performing one or more of the following: (a) at least one link associated with the first non-AP MLD in the plurality of links and the AP MLD Notify the power saving mode to the AP MLD on the road; (b) detect whether each link in one or more links in the plurality of links is unavailable; (c) set the power saving mode for the AP MLD at least one Perform P2P EMLSR operation or TDLS EMLSR operation on the link.

In some implementations, process 1000 may involve processor 912 performing additional operations. For example, process 1000 may involve processor 912 detecting another EMLSR operation by a second non-AP MLD on a first link of the plurality of links. Additionally, process 1000 may involve processor 912 refraining from triggering EMLSR operations by a second non-AP MLD on one or more other links of the plurality of links. In some implementations, in detection, process 1000 may involve processor 912 receiving an RTS, MU-RTS, BSRP, CTS2Self, and/or PS-Poll whose TA or RA is the second non-AP MLD. Alternatively or additionally, in detecting, process 1000 may involve processor 912 receiving a CTS or ACK, where the RA is the second non-AP MLD or a peer STA of the second non-AP MLD. Alternatively or additionally, in detecting, process 1000 may involve processor 912 receiving a trigger frame whose AID is the AID of the second non-AP MLD. Alternatively or additionally, in detecting, process 1000 may involve processor 912 detecting a negotiation by a second non-AP MLD for another MAC address or AID for another EMLSR operation. Additionally, process 1000 may involve processor 912 determining an end of blocking EMLSR operation of the second non-AP MLD on other links of the plurality of links if PIFS idle is triggered.

In some implementations, in establishing EMLSR operation, process 1000 may involve processor 912 performing one or more of the following: (a) at least one of the multiple links associated with the first non-AP MLD and the AP MLD Informing the AP MLD of the power saving mode on a link; (b) detecting whether each link of one or more links in a plurality of links is unavailable; (c) setting the power saving mode for the AP MLD at least Execute P2P EMLSR operation or TDLS EMLSR operation on a link.

Supplementary Note

The herein described subject matter sometimes illustrates different components contained within, or connected with, various other components. It is to be understood that these depicted architectures are examples only, 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, independent of architectures or intermediary 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 coupled" to each other. "Operationally coupleable" to achieve the desired functionality. Specific examples of operatively coupleable components include, but are not limited to, physically matable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactive components.

Furthermore, with regard to the substantial use of any plural and/or singular terms herein, one of ordinary skill in the art may convert from plural to singular and/or from singular to plural as appropriate to the context and/or application. For the sake of clarity, various singular/plural reciprocities may be explicitly set forth herein.

Additionally, those skilled in the art will understand that terms used herein, and especially in the appended claims (eg, the subject of the appended claims), generally mean "open" terms For example, the term "comprising" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", and so on. It will also be understood by those skilled in the art that if a specific number of an incorporated claim recitation is intended, such intent will be explicitly recited in the claim, and that no such intent is present in the absence of such recitation. For example, as an aid to understanding, the appended claims may contain usage of the introductory phrases "at least one" and "one or more" to introduce the claims' recitations. However, use of such phrases should not be construed to imply that the introduction of a claim list by the indefinite article "a" or "an" limits any particular claim containing such an introduced claim list to only includes one such enumerated implementation 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 a" shall be construed to mean "at least one" or "one or more"), the same applies to the use of the definite article used to introduce a claim enumeration. In addition, even if a specific number of an incorporated claim recitation is expressly recited, those skilled in the art will recognize that such recitation should be construed to mean at least that recited number (eg, in the absence of other modifiers In the case of , an unambiguous listing of "two listings" means at least two listings or two or more listings). Furthermore, where a convention similar to "at least one of A, B, and C, etc." is used, such an interpretation is generally intended in the sense that one skilled in the art would understand this convention (e.g., "has A , B, and C" would include, but not limited to, A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C, etc. system). In those cases where a convention similar to "at least one of A, B, or C, etc." is used, such an interpretation is generally intended in the sense that those skilled in the art will understand the convention (e.g., "has A, B, etc. or C" will include, but not limited to, A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A together, systems of B and C, etc.). Those skilled in the art will also understand that any transitional word and/or phrase that actually presents two or more alternative items, whether in the specification, claims, or drawings, should be understood to contemplate including those items. one, either, or both of these items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

From the foregoing it will be appreciated that various implementations of the invention have been described herein for purposes of illustration and that various modifications may be made without departing from the scope and spirit of the invention. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the appended claims. The above descriptions are only preferred embodiments of the present invention, and all equivalent changes and modifications made according to the scope of the patent application of the present invention shall fall within the scope of the present invention.

100: Network environment 110, 120:STA 200, 300, 400, 500, 600, 700, 800: scenes 900: system 910, 920: device 912, 922: Processor 916, 926: Transceiver 914, 924: memory 1000: process 1010, 1020: steps

The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this invention. The drawings illustrate implementations of the invention and together with the description serve to explain the principles of the invention. It is to be understood that the drawings are not necessarily to scale since some elements may be shown out of scale to the size of an actual implementation in order to clearly illustrate the inventive concept. Figure 1 illustrates an example network environment in which various solutions and solutions according to the present invention may be implemented. Figure 2 illustrates an example scenario under the proposed scheme for non-AP EMLSR MLD operation such as P2P/TDLS according to the present invention. Fig. 3 illustrates an example scenario under the proposed scheme according to the present invention. Fig. 4 illustrates an example scenario under the proposed scheme for capability handshaking according to the present invention. Fig. 5 illustrates an example scenario under the proposed scheme of the EMLSR MAC protocol between non-AP MLDs according to the present invention. Fig. 6 illustrates an example scenario under the proposed scheme of EMLSR hitchhiking (transmission-on-reception, Tx-on-Rx) according to the present invention. Fig. 7 illustrates an example scenario under the proposed scheme for detecting EMLSR operation of a peer STA according to the present invention. Fig. 8 illustrates an example scenario under the proposed scheme regarding the transparency of AP MLD according to the present invention. Figure 9 is a block diagram of an example communication system in accordance with an embodiment of the present invention. Figure 10 is a flowchart of an example process according to an embodiment of the invention.

1010, 1020: steps

1000: process

Claims (20)

A method of enhanced multilink single radio (EMLSR) operation, comprising: exchanging EMLSR capability information by a first non-access point (non-AP, non-AP) multilink device (MLD) and a second non-AP MLD during a handshake on one of the links; and establishing, by the first non-AP MLD, EMLSR operation with the second non-AP MLD on 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. The method of enhanced EMLSR operation as claimed in claim 1, wherein the EMLSR operation is a point-to-point (P2P) EMLSR operation or tunnel direct link establishment between the first non-AP MLD and the second non-AP MLD ( TDLS) EMLSR operation. The enhanced EMLSR operation method according to claim 1, wherein the exchange of EMLSR capability information includes exchanging EMLSR operation information or EMLSR capability fields or both in a handshake flow. The method for operating an enhanced EMLSR according to claim 3, wherein the EMLSR capability field is in a TDLS multi-link element or a P2P link event request sub-element. The enhanced EMLSR operation method of claim 1, wherein establishing the EMLSR operation includes: triggering the second non-AP MLD to perform EMLSR communication on the one or more of the plurality of links; and switching to an available link of the plurality of links, Wherein, after the first non-AP MLD and the second non-AP MLD establish the EMLSR operation between each other on the available link, the first non-AP MLD and the second non-AP MLD do not know activity on other links of the plurality of links. The method of enhanced EMLSR operation as claimed in item 5, wherein the trigger includes: sending an initial frame to the second non-AP MLD on 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 Power Saving Polling (PS-Poll); and In response, receiving a request frame from the second non-AP MLD on the available link, the request frame being a clear to send (CTS), buffer status report (BSR), or acknowledgment (ACK) . The method of enhanced EMLSR operation as claimed in claim 1, wherein establishing the EMLSR operation includes: detecting the link availability of each link in the one or more links in the plurality of links to select An available link of the plurality of links is used for the EMLSR operation. The method of enhanced EMLSR operation of claim 7, wherein said detecting link availability comprises detecting a preamble or media of a physical layer protocol data unit (PPDU) transmitted on one of said plurality of links An Access Control (MAC) header, where the link carrying the PPDU is unavailable if the PPDU transmitted is from or to a peer device. The method of enhanced EMLSR operation of claim 7, wherein said detecting link availability comprises estimating a duration of said PPDU or transmission opportunity (TXOP) transmitted on an unavailable link based on information in said PPDU. The method of enhanced EMLSR operation of claim 9, wherein establishing said EMLSR operation comprises establishing said EMLSR on an available link of said plurality of links considering the duration of said PPDU as a constraint operate. The method of enhanced EMLSR operation of claim 9, wherein establishing said EMLSR operation comprises applying a duration constraint obtained from said estimation to said first non-AP MLD and/or all The second non-AP MLD is on at least one link associated with the AP MLD. As the method for the enhanced EMLSR operation of claim item 1, it also includes: 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 Avoid triggering EMLSR operation of the second non-AP MLD on one or more other links of the plurality of links. The method of enhanced EMLSR operation as claimed in claim 12, wherein said detecting comprises receiving RTS, MU-RTS, BSRP, CTS2Self or PS-Poll, wherein a transmitter address (TA) or a receiver address (RA) is said first Two non-AP MLD. The method of enhanced EMLSR operation of claim 12, wherein said detecting comprises receiving a CTS or ACK, wherein a receiver address (RA) is said second non-AP MLD or a peer STA of said second non-AP MLD . The method of enhanced EMLSR operation of claim 12, wherein said detecting comprises receiving a trigger frame whose association identifier (AID) is the association identifier of said second non-AP MLD. The method of enhanced EMLSR operation of claim 12, wherein said detecting comprises detecting negotiation of another medium access control (MAC) address or AID operated by said second non-AP MLD for said another EMLSR. As the method for the enhanced EMLSR operation of claim item 12, it also includes: determining, by the first non-AP MLD, blocking EMLSRs of the second non-AP MLD on other links of the plurality of links in the event that point coordination function inter-frame space (PIFS) idling is triggered The end of the operation. The enhanced EMLSR operation method of claim 1, wherein establishing the EMLSR operation includes performing one or more of the following: notifying the AP MLD of a power saving mode on at least one of the plurality of links with 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 for which the power saving mode is set for the AP MLD. The method of enhanced EMLSR operation as claimed in claim 11, wherein establishing the EMLSR operation includes performing one or more of the following: notifying the AP MLD of a power saving mode on at least one of the plurality of links with 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 for which the power saving mode is set for the AP MLD. An apparatus implementable in a first non-AP MLD comprising: a transceiver configured to communicate wirelessly; and a processor coupled to the transceiver and configured to perform operations including: exchanging EMLSR capability information during a handshake with a second non-AP MLD via the transceiver on one of the links; and establishing EMLSR operation with the second non-AP MLD via the transceiver on 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.

Images