Method and process for NSTR start time synchronization

By detecting and synchronizing the PPDU start time of the STA in the NSTR link pair, using backoff hold time and slotted computer system, the problem of channel conflict in the NSTR link pair is solved, and the device performance and channel efficiency are improved.

CN118975341APending Publication Date: 2024-11-15SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031134.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-06-21
Filing Date
2023-06-28
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In multi-link operation mode, the STA of the non-simultaneous transmit/receive (NSTR) link pair may experience channel conflicts at the synchronization start time, resulting in degradation of device performance, and it is difficult for the prior art to effectively avoid signal leakage and interference.

Method used

By detecting the start time of the synchronous physical layer protocol data unit (PPDU) between STAs of the NSTR link pair, using the back-up hold time and the slotted back-up hold time computer system, ensuring that the STA keeps the counter to zero during the back-up hold time, Start time with synchronous sending and postpone sending after energy detection is completed to avoid conflicts.

Benefits of technology

Effectively prevent wireless channel conflicts, improve the performance and throughput of NSTR-constrained devices, and ensure efficient link use and channel reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975341A_ABST
    Figure CN118975341A_ABST
Patent Text Reader

Abstract

Methods and apparatus for non-simultaneous transmit / receive (NSTR) start time synchronization are disclosed. A method for wireless communication performed by a non-access point (AP) multilink device (MLD) including a station (STA), the method comprising: forming a link with a corresponding AP of the AP MLD; detecting a non-simultaneous transmit and receive (NSTR) link pair; detecting an attempt to synchronize a start time of a physical layer protocol data unit (PPDU) by a first STA of the NSTR link pair with a second STA of the NSTR link pair, where the first STA is configured to maintain a backoff counter at a value of zero during a backoff hold time duration; determining a backoff hold time duration; and determining a number of time intervals that can be accommodated in the backoff hold time duration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to transmission efficiency in a wireless communication system including a multi-link device. Embodiments of the present disclosure relate to a method and apparatus for non-simultaneous transmit / receive (NSTR) start time synchronization. Background Art

[0002] Wireless Local Area Network (WLAN) technology allows devices to access the Internet in the 2.4GHz, 5GHz, 6GHz, or 60GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 family of standards is designed to increase speed and reliability and extend the operating range of wireless networks.

[0003] Multi-link operation (MLO) is a feature currently being developed by standards organizations in IEEE 802.11be for the next generation of extremely high throughput (EHT) Wi-Fi systems. Wi-Fi devices that support MLO are called multi-link devices (MLDs). Using MLO, non-access point (AP) multi-link devices (MLDs) can discover, authenticate, associate, and establish multiple links with AP MLDs. Channel access and frame exchange are possible on each link between AP MLDs and non-AP MLDs. Summary of the invention

[0004] Solution to the problem

[0005] Embodiments of the present disclosure provide a method and apparatus for NSTR start time synchronization.

[0006] In one embodiment, a non-access point (AP) multi-link device (MLD) is provided, comprising: a station (STA), each STA comprising a transceiver configured to form a link with a corresponding AP of the AP MLD. The non-AP MLD also comprises a processor operably coupled to the STA, the processor being configured to: detect a non-simultaneous transmit and receive (NSTR) link pair; detect an attempt by a first STA of the NSTR link pair to synchronize a start time of a physical (PHY) layer protocol data unit (PPDU) with a second STA of the NSTR link pair, wherein the first STA is configured to maintain a backoff counter at a value of zero during a backoff hold time duration; determine a backoff hold time duration; and determine the number of time intervals that can be accommodated in the backoff hold time duration.

[0007] In another embodiment, a method for wireless communication performed by a non-access point (AP) multi-link device (MLD) including a station (STA), the method comprising: forming a link with a corresponding AP of the AP MLD; detecting a non-simultaneous transmit and receive (NSTR) link pair; detecting an attempt by a first STA of the NSTR link pair to synchronize a start time of a physical layer protocol data unit (PPDU) with a second STA of the NSTR link pair, wherein the first STA is configured to maintain a backoff counter at a value of zero during a backoff hold time duration; determining the backoff hold time duration; and determining the number of time intervals that can be accommodated in the backoff hold time duration.

[0008] Other technical features may be clear to those skilled in the art from the following drawings, descriptions and claims.

[0009] Before carrying out the following specific embodiments, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include both direct and indirect communication. The terms "include" and "comprise" and their derivatives refer to including but not limited to this. The term "or" is inclusive, referring to and / or. The phrase "associated with..." and its derivatives refer to including, being included in, interconnected with, being included in, being connected to or connected with, being coupled to or coupled with, being communicable with, collaborating with, interweaving, juxtaposing, being close to, being bound to or bound with, having, having the nature of, having a relationship with, etc. The term "controller" refers to any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of..." means that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. As used herein, terms such as "first" and "second" can be used to simply distinguish a corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It should be understood that if an element (e.g., a first element) is referred to as "coupled to another element (e.g., a second element)", "coupled to another element (e.g., a second element)", "connected to another element (e.g., a second element)" or "connected to another element (e.g., a second element)" with or without the term "operably" or "communicatively", it means that the element can be coupled to another element directly (e.g., wired), wirelessly, or via a third element.

[0010] As used herein, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "component," or "circuit"). A module may be a single integrated component or its smallest unit or portion suitable for performing one or more functions. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0011] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard disk drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and overwrite data later, such as rewritable optical disks or erasable memory devices.

[0012] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

[0014] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0015] Figure 2A An example AP according to an embodiment of the present disclosure is shown;

[0016] Figure 2B An example station (STA) according to an embodiment of the present disclosure is shown;

[0017] Figure 3 shows an example of NSTR mobile AP MLD operation according to various embodiments of the present disclosure;

[0018] Figure 4 An example of NSTR operation with a start time synchronization PPDU access procedure according to various embodiments of the present disclosure is shown;

[0019] Figure 5 An example of reception occurring during a backoff hold time according to various embodiments of the present disclosure is shown;

[0020] Figure 6 shows an example timeline showing various detections occurring after a reception start time in accordance with various embodiments of the present disclosure;

[0021] Figure 7 A flowchart of a method for medium synchronization recovery based on timing constraint information performed by an AP according to an embodiment of the present disclosure is shown;

[0022] Figure 8 shows a modified structure of an AP Assisted Medium Synchronization Recovery (AAR) Control subfield according to an embodiment of the present disclosure;

[0023] Fig. 9 A timing diagram illustrating a modified structure using an AAR control subfield according to an embodiment of the present disclosure;

[0024] Fig.10 A flowchart of a method for NSTR start time synchronization according to an embodiment of the present disclosure is shown;

[0025] Fig.11 A flow chart of a method for slotted backoff hold time calculation according to an embodiment of the present disclosure is shown;

[0026] Fig.12 An example frame format of a request frame for collecting backoff holding time slot durations by an AP MLD from a non-AP MLD according to an embodiment of the present disclosure is shown;

[0027] Fig.13 An example link ID element of a request frame format according to an embodiment of the present disclosure is shown;

[0028] Fig.14 shows an example frame format of a response frame sent by a non-AP MLD to an AP MLD according to an embodiment of the present disclosure;

[0029] Fig.15 An example backoff holding time slot duration element frame format according to an embodiment of the present disclosure is shown;

[0030] Fig.16 An example of a slotted backoff hold time process according to an embodiment of the present disclosure is shown; and

[0031] Fig.17 A flowchart of a method for wireless communication performed by a non-AP device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0032] Discussed below Figures 1 to 17The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0033] The following documents and standard descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: IEEE P802.11be / D3.0, 2023 (referred to herein as REF [1]).

[0034] Embodiments of the present disclosure provide a mechanism for traffic urgency indication.

[0035] Figure 1 An example wireless network 100 is shown in accordance with various embodiments of the present disclosure. Figure 1 The embodiment of the wireless network 100 shown is for illustration purposes. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0036] The wireless network 100 includes APs 101 and 103. The APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. The AP 101 provides wireless access to the network 130 for a plurality of STAs 111-114 within a coverage area 120 of the AP 101. The APs 101 and 103 may communicate with each other and with the STAs 111-114 using Wi-Fi or other WLAN communication technologies.

[0037] Depending on the network type, other well-known terms may be used instead of "access point" or "AP", such as "router" or "gateway". For convenience, the term "AP" is used in the present disclosure to refer to a network infrastructure component that provides wireless access to a remote terminal. In a WLAN, assuming that the AP also competes for a wireless channel, the AP may also be referred to as a STA (e.g., APSTA). In addition, depending on the network type, other well-known terms may be used instead of "station" or "STA", such as "mobile station", "subscriber station", "remote terminal", "user device", "wireless terminal" or "user device". For convenience, the terms "station" and "STA" are used in the present disclosure to refer to a remote wireless device that wirelessly accesses an AP or competes for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile phone or smart phone) or is generally considered to be a fixed device (such as a desktop computer, AP, media player, fixed sensor, TV, etc.). This type of STA may also be referred to as a non-AP STA.

[0038] In various embodiments of the present disclosure, each of the APs 101 and 103 and each of the STAs 111-114 may be an MLD. In such an embodiment, the APs 101 and 103 may be AP MLDs, and the STAs 111-114 may be non-AP MLDs. Each MLD is attached to more than one STA. For ease of explanation, an AP MLD is described herein as being attached to more than one AP (e.g., more than one AP STA), and a non-AP MLD is described herein as being attached to more than one STA (e.g., more than one non-AP STA).

[0039] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with APs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the APs and variations in the radio environment associated with natural and man-made obstacles.

[0040] As described in more detail below, one or more of the APs may include circuitry and / or programming for traffic urgency indication. Figure 1 One example of a wireless network 100 is shown, but may be Figure 1 Various changes may be made. For example, the wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. In addition, the AP 101 may communicate directly with any number of STAs and provide these STAs with wireless broadband access to the network 130. Similarly, each AP 101-103 may communicate directly with the network 130 and provide the STAs with direct wireless broadband access to the network 130. In addition, the APs 101 and / or 103 may provide access to other or additional external networks (such as an external telephone network or other types of data networks).

[0041] Figure 2A An example AP 101 is shown in accordance with various embodiments of the present disclosure. Figure 2A The embodiment of AP 101 shown in FIG. 1 is for illustration purposes only, and Figure 1 The APs 103 of FIG. 104 may have the same or similar configurations. In the embodiments discussed below, the AP 101 is an AP MLD. However, the APs have a variety of configurations, and Figure 2A The scope of the present disclosure is not limited to any particular implementation of an AP.

[0042] The AP MLD 101 is attached to a plurality of APs 202a-202n (which may be referred to as, for example, AP1-APn). Each of the attached APs 202a-202n includes a plurality of antennas 204a-204n, a plurality of radio frequency (RF) transceivers 209a-209n, a transmit (TX) processing circuit 214, and a receive (RX) processing circuit 219. The AP MLD 101 also includes a controller / processor 224, a memory 229, and a backhaul or network interface 234.

[0043] The illustrated components of each attached AP 202a-202n may represent the physical (PHY) layer and the lower media access control (lower MAC, LMAC) layer in the open system interconnection (OSI) networking model. In such an embodiment, the illustrated components of the AP MLD 101 represent a single upper MAC (UMAC) layer and other higher layers in the OSI model, which are shared by all attached APs 202a-202n.

[0044] For each attached AP 202a-202n, an RF transceiver 209a-209n receives incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in the network 100. In some embodiments, each attached AP 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), and thus the incoming RF signals received by each attached AP may be at a different RF frequency. The RF transceiver 209a-209n down-converts the incoming RF signals to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuit 219, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 219 sends the processed baseband signal to the controller / processor 224 for further processing.

[0045] For each attached AP 202a-202n, the TX processing circuit 214 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 224. The TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 209a-209n receives the outgoing processed baseband or IF signal from the TX processing circuit 214 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 204a-204n. In embodiments where each attached AP 202a-202n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signals transmitted by each attached AP may be at a different RF frequency.

[0046] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP MLD 101. For example, the controller / processor 224 may control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceivers 209a-209n, the RX processing circuit 219, and the TX processing circuit 214 according to well-known principles. The controller / processor 224 may support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 224 may support beamforming or directional routing operations, in which outgoing signals from multiple antennas 204a-204n are weighted differently to effectively guide the outgoing signals to the desired direction. The controller / processor 224 may also support orthogonal frequency division multiple access (OFDMA) operations, in which outgoing signals are allocated to different subcarrier subsets for different recipients (e.g., different STAs 111-114). The controller / processor 224 may support any of a variety of other functions in the AP MLD 101, including traffic urgency indication. In some embodiments, the controller / processor 224 includes at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an operating system (OS), residing in the memory 229. The controller / processor 224 can move data into or out of the memory 229 as required by the executing process.

[0047] The controller / processor 224 is also coupled to a backhaul or network interface 234. The backhaul or network interface 234 allows the AP MLD 101 to communicate with other devices or systems over a backhaul connection or over a network. The interface 234 can support communication over any suitable wired or wireless connection. For example, the interface 234 can allow the AP MLD 101 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 234 includes any suitable structure that supports communication over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory 229 is coupled to the controller / processor 224. A portion of the memory 229 may include RAM, and another portion of the memory 229 may include flash memory or other ROM.

[0048] As described in more detail below, AP MLD 101 may include circuitry and / or programming for traffic urgency indication. Figure 2A An example of AP MLD 101 is shown, but the same may be applied to Figure 2A For example, AP MLD 101 may include any number of Figure 2A. As a specific example, the AP MLD 101 may include multiple interfaces 234, and the controller / processor 224 may support routing functions to route data between different network addresses. As another specific example, although each attached AP 202a-202n is shown as including a single instance of the TX processing circuit 214 and a single instance of the RX processing circuit 219, the AP MLD 101 may include multiple instances of each of one or more of the attached APs 202a-202n (such as one for each RF transceiver). Alternatively, in one or more of the attached APs 202a-202n, such as in a traditional AP, only one antenna and RF transceiver path may be included. In addition, Figure 2A The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0049] Figure 2B An example STA 111 is shown according to various embodiments of the present disclosure. Figure 2B The embodiment of STA 111 shown in FIG. is for illustration, and Figure 1 STAs 111-114 may have the same or similar configurations. In the embodiments discussed below, STA 111 is a non-AP MLD. However, STAs may have a variety of configurations, and Figure 2B The scope of this disclosure is not limited to any particular implementation of a STA.

[0050] The non-AP MLD 111 is attached with a plurality of STAs 203a-203n (which may be referred to as, for example, STA1-STAn). Each of the attached STAs 203a-203n includes an antenna 205, an RF transceiver 210, a TX processing circuit 215, and an RX processing circuit 225. The non-AP MLD 111 also includes a microphone 220, a speaker 230, a controller / processor 240, an input / output interface (I / O IF) 245, a touch screen 250, a display 255, and a memory 260. The memory 260 includes an OS 261 and one or more applications 262.

[0051] The illustrated components of each attached STA 203a-203n may represent the PHY layer and LMAC layer in the OSI networking model. In such an embodiment, the illustrated components of the non-AP MLD 111 represent a single UMAC layer and other higher layers in the OSI model, which are shared by all attached STAs 203a-203n.

[0052] For each attached STA 203a-203n, the RF transceiver 210 receives an incoming RF signal sent by the AP of the network 100 from the antenna 205. In some embodiments, each attached STA 203a-203n operates at a different bandwidth (e.g., 2.4GHz, 5GHz, or 6GHz), and thus the incoming RF signal received by each attached STA may be at a different RF frequency. The RF transceiver 210 down-converts the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is sent to the RX processing circuit 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuit 225 sends the processed baseband signal to the speaker 230 (such as for voice data) or to the controller / processor 240 for further processing (such as for web browsing data).

[0053] For each attached STA 203a-203n, the TX processing circuit 215 receives analog or digital voice data from the microphone 220, or receives other outgoing baseband data (such as network data, email, or interactive video game data) from the controller / processor 240. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 210 receives the outgoing processed baseband or IF signal from the TX processing circuit 215 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 205. In embodiments where each attached STA 203a-203n operates at a different bandwidth (e.g., 2.4 GHz, 5 GHz, or 6 GHz), the outgoing RF signal transmitted by each attached STA may be at a different RF frequency.

[0054] The controller / processor 240 may include one or more processors and execute a basic OS program 261 stored in the memory 260 to control the overall operation of the non-AP MLD 111. In one such operation, the main controller / processor 240 controls the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 210, the RX processing circuit 225, and the TX processing circuit 215 according to well-known principles. The main controller / processor 240 may also include processing circuits configured to support traffic urgency indication. In some embodiments, the controller / processor 240 includes at least one microprocessor or microcontroller.

[0055] The controller / processor 240 is also capable of executing other processes and programs resident in the memory 260, such as operations for supporting traffic urgency indications. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for supporting traffic urgency indications. The controller / processor 240 can operate multiple applications 262 based on the OS program 261 or in response to a signal received from the AP. The main controller / processor 240 is also coupled to an I / O interface 245, which provides the non-AP MLD 111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller 240.

[0056] The controller / processor 240 is also coupled to a touch screen 250 and a display 255. An operator of the non-AP MLD 111 can use the touch screen 250 to input data into the non-AP MLD 111. The display 255 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website. A memory 260 is coupled to the controller / processor 240. A portion of the memory 260 can include RAM, and another portion of the memory 260 can include flash memory or other ROM.

[0057] although Figure 2B An example of a non-AP MLD 111 is shown, but the Figure 2B Make various changes. For example, Figure 2B The various components in may be combined, further subdivided, or omitted, and additional components may be added as required. In a specific example, one or more of the attached STAs 203a-203n may include any number of antennas 205 for multiple-input multiple-output (MIMO) communications with the AP 101. In another example, the non-AP MLD 111 may not include voice communications, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, although Figure 2B The non-AP MLD 111 is shown configured as a mobile phone or smart phone, but the non-AP MLD may also be configured to operate as other types of mobile or fixed devices.

[0058] Various embodiments of the present disclosure recognize that multi-link operation has two key variants. The first variant is simultaneous transmit / receive (STR), in which STAs attached to MLDs can transmit and receive independently of each other. The second variant is non-simultaneous transmit / receive (NSTR). If a pair of links constitutes an NSTR pair, transmission on one link may cause signal leakage that interferes with the reception of the other link. Due to this interference, the device cannot transmit on one link while receiving on another link. The NSTR capability of the device may vary over time depending on multiple factors such as frequency separation between links, antenna separation, internal design of the chip, etc. Therefore, non-AP STAs are more likely to be subject to NSTR constraints. Therefore, in a scenario including a STR AP attached to an AP MLD connected to an NSTR non-AP STA attached to a non-AP MLD, the actual performance upper limit of multi-link operation in 802.11be will be achieved. In order to avoid interference caused by signal leakage under NSTR constraints, the standard requires alignment of start and end times on the links that constitute the NSTR link pair. With this alignment, the two links constituting the NSTR link pair are either both in transmit mode or both in receive mode. Therefore, there is no effect of signal leakage from one link to the other, and both links can be used simultaneously to achieve the higher throughput values ​​envisioned by 802.11be.

[0059] Various embodiments of the present disclosure recognize that in the NSTR mode of operation, when one of the STAs constituting the NSTR link pair transmits a frame and another STA attached to the same MLD cannot start transmitting, the other STA faces a blindness due to which the STA may not be able to sense the preamble of other transmissions on its channel and may need to start a medium synchronization loss recovery process. One of the processes described in REF [1] utilizes AP-assisted medium synchronization recovery to help a non-AP STA attached to a non-AP MLD that has lost synchronization to transmit a frame without causing a conflict with an existing transmission on its own channel.

[0060] Figure 3 An example of NSTR mobile AP MLD operations 300 is shown in accordance with various embodiments of the present disclosure. Figure 3 The illustrated embodiment of the example NSTR mobile AP MLD operation 300 is for illustration. Other embodiments of the example NSTR mobile AP MLD operation 300 may be used without departing from the scope of the present disclosure.

[0061] like Figure 3As shown, two APs (i.e., AP1 and AP2) are attached to the NSTR mobile AP MLD. In addition, STA1 and STA2 are two non-AP STAs attached to the non-AP MLD. STA1 and STA2 are associated with AP1 and AP2, respectively, thereby generating two links. The link between AP1 and STA1 is designated as the primary link, and the link between AP2 and STA2 is designated as the non-primary link.

[0062] Figure 4 An example of NSTR operation with a start time synchronization PPDU access procedure 400 is shown in accordance with various embodiments of the present disclosure. Figure 4 The illustrated embodiment of the example NSTR operation with start time synchronization PPDU access procedure 400 is for illustration. Other embodiments of the example NSTR operation with start time synchronization PPDU access procedure 400 may be used without departing from the scope of the present disclosure.

[0063] According to the 802.11 random backoff process for channel access, a STA with data to send generates a random backoff count. The backoff count is a pseudo-random integer extracted from a uniform distribution on the range [0, CW], where aCWmin≤CW≤aCWmax. CW starts with an initial value of aCWmin, and its value increases exponentially with each failed transmission attempt until it reaches aCWmax. When the backoff count is selected, the STA counts the number of those multiple backoff slots. Each backoff slot has a fixed duration determined by the specification (e.g., 9 microseconds in 802.11ac and higher standards). After the number of remaining slots becomes zero, the device can initiate transmission.

[0064] In order to synchronize the start time of transmission, IEEE 802.11be provides a start time synchronization PPDU access procedure. As part of this procedure, when the backoff counter of the STA of the MLD that is part of the NSTR link pair reaches zero, the STA may choose not to transmit and keep its backoff counter at zero to synchronize the start time with the other link that constitutes the NSTR link pair.

[0065] Examples include Figure 4As shown in the figure, the non-AP MLD forms two links—Link 1 and Link 2—after associating with the AP MLD. The AP MLD has two APs attached to it—AP 1 and AP 2. The non-AP MLD has two non-AP STAs attached to it—STA1 and STA2. The STAs of the non-AP MLD have data packets to send to the AP MLD. Each STA starts the backoff process as shown in the figure. When the STA1 attached to the non-AP MLD has a count of zero, it may want to keep the counter at zero for a period of time (referred to as the backoff hold time) to keep in contact with STA2 attached to the same non-AP MLD (an example of which is shown in FIG. 1 ). Figure 4 ) synchronization. After the backoff hold time, STA1 and STA2 can start their transmissions with their PPDU start times synchronized with each other. In order to allow some tolerance in the alignment of the start times, IEEE 802.11be allows the start times to be misaligned by up to 4 microseconds when the STAs attempt to synchronize the start times.

[0066] Various embodiments of the present disclosure recognize that when one STA affiliated with an MLD attempts to synchronize the start time with another STA of the same MLD, problems as described below may occur.

[0067] For example, when a STA requests AP assistance in medium synchronization, the AP does not know within what time limit the STA needs to be served. In such a case, the AP may end up serving a STA that no longer needs AP assistance (e.g., the STA has discarded the packet it intended to send and no longer needs help from the AP). In this case, the AP needs to know this situation in advance so that it can act accordingly.

[0068] As another example, a device attempting to synchronize the start time maintains its backoff counter at zero during the backoff hold time. During this interval, a STA attempting to maintain its backoff counter at zero may receive a PPDU. Figure 5 An example is shown in , which shows an example in which reception occurs during the backoff holding time 500 according to various embodiments of the present disclosure. Figure 5 The embodiment of the example in which reception occurs during the backoff hold time 500 shown in FIG. 5 is for illustration. Other embodiments of the example in which reception occurs during the backoff hold time 500 may be used without departing from the scope of the present disclosure.

[0069] like Figure 5 As shown, STA1 attached to the non-AP MLD keeps its backoff counter at zero to try to synchronize with the start time of STA2. During this time, STA1 can receive PPDU on link 1.

[0070] Figure 6An example timeline 600 showing various detections occurring after a receive start time is shown in accordance with various embodiments of the present disclosure. Figure 6 The embodiment of the example timeline 600 showing various detections occurring after a receive start time shown in FIG is for illustration. Other embodiments of the example timeline 600 showing various detections occurring after a receive start time may be used without departing from the scope of the present disclosure.

[0071] like Figure 6 As shown, after packet reception begins, there is a finite period of time after which energy detection is able to detect reception. Typically, energy detection occurs before the point at which preamble reception is complete and PPDU timing information becomes available.

[0072] If the start of reception occurs during the backoff hold time, the backoff hold time may reach zero before the energy detection detects an over-the-air packet. This may cause STA1 on link 1 to fail to accurately detect its own MAC state and initiate a transmission when it has actually started receiving a PPDU. This may cause channel conflicts to occur, which may affect the performance of devices subject to NSTR constraints.

[0073] To elaborate, consider Figure 6 In the example in which the STA on link 1 has a packet to send and is performing a channel contention process in order to send the packet. After its backoff count is 0, the STA can keep the backoff counter at 0 to align the start time of its transmission with the STA on link 2 (e.g. Figure 4 However, while the STA keeps its backoff counter at 0, some other device may capture the channel and packet reception may begin. After packet reception begins, it may take a finite period of time for the STA to detect that packet reception has begun (e.g. Figure 6 ). This period of time mainly includes the time to completely receive the initial preamble part, perform energy detection to detect packets on the channel, etc. However, if the backoff hold time can be completed after the reception starts but before the energy detection is completed, the STA on link 1 can receive the frame (but not be detected by the STA because the energy detection is not completed), and can also start sending. This may cause a conflict on the channel because two STAs (STA1 that starts sending and another STA that has been sending on the channel and whose packet is being received by STA1) perform transmission at the same time. This may reduce device throughput and performance.

[0074] Therefore, various embodiments of the present disclosure provide a mechanism and framework for enabling an AP to have timing constraint information that indicates to the AP the time limit within which the STA needs to be served. In addition, various embodiments of the present disclosure provide a mechanism that a STA can use to accurately detect its own MAC state and initiate transmission when it has actually started receiving a PPDU.

[0075] The above-described mechanisms and frameworks may help prevent an increase in collisions on wireless channels, which may degrade the performance of NSTR-constrained devices.

[0076] Figure 7 A flowchart of an example method 700 performed by an AP for medium synchronization recovery based on timing constraint information according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of the method 700 for medium synchronization recovery based on timing constraint information performed by an AP shown in FIG is for illustration. Other embodiments of the example method 700 for medium synchronization recovery based on timing constraint information performed by an AP may be used without departing from the scope of the present disclosure.

[0077] According to one embodiment, a STA that requires AP assistance may provide timing constraint information. In one embodiment, timing constraint information may be provided in the AAR control subfield. The timing constraint may indicate the time until which the STA will require AP assistance to send the corresponding packet. If the AP cannot provide assistance to the STA within the duration, the AP may consider that the STA no longer requires its assistance. The AP may consider multiple factors (e.g., the average channel access time on the link for which it requests assistance, and whether it can provide assistance considering the timing constraints of the STA) when determining whether it can provide assistance to the STA.

[0078] like Figure 7 As shown, method 700 begins at step 702, where it is determined whether the AP has received timing constraint information from the STA / MLD. If not, then at step 704, no action is required. If yes, then at step 706, it is determined whether the AP has received a request for medium synchronization recovery from the STA / MLD. If no, then at step 708, no action is required. If yes, then at step 710, the AP uses the timing constraint information from the STA / MLD in assisting medium synchronization recovery.

[0079] Figure 8 A modified structure of the AAR control subfield 800 is shown according to an embodiment of the present disclosure. Figure 8 The embodiment of the modified structure of the AAR Control subfield 800 shown in FIG. 8 is for illustration. Other embodiments of the modified structure of the AAR Control subfield 800 may be used without departing from the scope of the present disclosure.

[0080] like Figure 8 As shown, the frame structure uses reserved bits (B15-B19) to indicate timing constraint information. The timing constraint information can be an indicator of the remaining time until which the STA will need AP assistance. For example, the remaining packet delay timer value, the expiration time of the packet, etc.

[0081] Fig. 9 A timing diagram 900 using a modified structure of the AAR control subfield is shown according to an embodiment of the present disclosure. Fig. 9 The embodiment of the timing diagram 900 using the modified structure of the AAR control subfield shown in is for illustration. Other embodiments of the timing diagram 900 using the modified structure of the AAR control subfield may be used without departing from the scope of the present disclosure.

[0082] In another embodiment, for each request made by the STA for AP assistance, the STA may provide a duration for which its request will be considered valid. This may be accomplished by providing a validity period in the AAR Control subfield sent by the STA. Upon expiration of this period, the STA may make another request if necessary, and the AP may consider the previous request invalid. This duration may be provided relative to the time the STA sends the request.

[0083] Timing diagram Fig. 9 As shown. In this example, the AP MLD has two APs attached to it—AP1 and AP2. The non-AP MLD has two non-AP STAs attached to it—STA1 and STA2. The non-AP MLD is associated with the AP MLD and has formed two links—Link 1 and Link 2—that constitute the NSTR link pair. As shown in the figure, AP2 is requested to assist STA2, which has lost medium synchronization, to send a frame. In this example, STA1 sends a data frame to AP1, and the modified AAR control subfield may be present in the data frame. The AAR control subfield requests AP2 to assist STA2 in medium synchronization recovery. The bit corresponding to Link 2 may be set to 1 in the link ID bitmap to indicate the link for which assistance is being requested. Timing constraint information may be indicated in the modified AAR control subfield. Based on this information, AP2 knows the time when its front STA2 must be assisted. Then, after the data frame reception at AP1 is completed, AP2 may send a trigger frame to STA2 to request uplink frame transmission. Upon receiving the trigger frame, STA2 may consider its medium synchronization recovery to be complete and send an uplink frame.

[0084] In another embodiment, the STA may send a frame to provide measurement related information to the AP. The measurement related information may provide the AP with an understanding of the delay constraints for the frames that the STA intends to send to the AP. The AP may consider the delay constraints when assisting the STA in medium synchronization recovery.

[0085] In one embodiment, a STA (affiliated to the same MLD) that forms an NSTR link pair and wants to synchronize the start time with another STA affiliated to the same MLD and as part of the NSTR link pair may perform the division of the backoff hold time into time slots while counting down.

[0086] Fig.10 A flowchart of a method 1000 for NSTR start time synchronization performed by a STA according to an embodiment of the present disclosure is shown. Fig.10 The embodiment of the flowchart 1000 for NSTR start time synchronization shown in FIG. 1 is for illustration. Other embodiments of the flowchart 1000 for NSTR start time synchronization may be used without departing from the scope of the present disclosure.

[0087] like Fig.10 As shown, method 1000 begins at step 1002, where it is determined whether the device is subject to NSTR constraints. If not, then at step 1004, no action is required. If yes, then at step 1006, it is determined whether another link is also competing for channel access. If no, no action is required (step 1004). If yes, then at step 1008, a backoff hold time is calculated. At step 1010, the backoff hold time is divided into time slots or time intervals. At step 1012, the time slots are counted down. At step 1014, it is determined whether reception is detected. If not, then at step 1016, it is determined whether the time slot count is equal to zero. If the time slot count is not equal to zero, the method returns to step 1012. If the time slot count is equal to zero, then at step 1018, if the NSTR rules permit, transmission is started. If reception is detected at step 1014, then at step 1020, the method waits for preamble detection to set the NAV timer. At step 1022, it is determined whether a preamble is detected. If no, the method returns to step 1020. If yes, then at step 1024, transmission is postponed to avoid collisions.

[0088] like Fig.10 As shown, when forming an NSTR link pair and wanting to synchronize the start time of PPDU transmission with another STA that is part of the link pair, the STA that wants to synchronize the start time of PPDU transmission can first calculate the backoff hold time. As an example, if the STA on link 1 wants to wait until the backoff on link 2 is completed, the backoff hold time can be calculated as follows:

[0089] Backoff hold time = T0 L2 -T0 L1

[0090] Where T0 L1 is the time when the backoff counter of the STA on link 1 reaches zero, and T0 L2 It is the time when the backoff counter of the STA on link 2 reaches zero.

[0091] Therefore, after calculating the backoff hold time, if Fig.10 As shown, the backoff hold time can be divided into time slots. Here, the time slot durations can be set to values ​​that are greater than the time for energy detection to complete (e.g., 9 microseconds). The importance of dividing the backoff hold time into time slots whose values ​​are higher than the energy detection time is to prevent the device from switching states in the middle of the time slot. According to one embodiment, in order to divide the backoff into time slots, the number of time slots that can be accommodated in the backoff hold time can be calculated as follows.

[0092]

[0093] Furthermore, according to this embodiment, the backoff holding time can be adjusted as follows.

[0094] Backoff hold time = backoff hold time slot duration * backoff hold time slot count

[0095] This ensures that there is a sufficient period of time to complete energy detection and detect the receive state, which will trigger a state change to receive, thereby preventing the STA from starting transmissions that may cause collisions.

[0096] Fig.11 A flowchart of a method 1100 for slotted backoff holding time calculation according to an embodiment of the present disclosure is shown. Fig.11 The illustrated embodiment of the method 1100 for slotted backoff hold time calculation is for illustration. Other embodiments of the method 1100 for slotted backoff hold time calculation may be used without departing from the scope of the present disclosure.

[0097] like Fig.11 As shown, method 1100 begins at step 1102, where it is determined whether the backoff hold time has been calculated. If not, then at step 1104, no action is required. If yes, then at step 1106, the number of time slots that can be accommodated in the backoff hold time is calculated. At step 1108, the new backoff hold time is equal to the number of time slots*time slot duration.

[0098] Once the number of backoff hold time slots is calculated, such as Fig.10As shown, the device can start counting down the time slots. In the middle of any time slot, if the energy detection detects reception, the STA can delay transmission and add additional waiting time until the preamble is detected. In such a scenario, the STA on the other link that constitutes an NSTR link pair and the STA on the first link attempts to synchronize its PPDU start time with it by keeping its backoff counter at zero can enter an NSTR-based postponement state, in which it can postpone its transmission to avoid any NSTR interference with the reception of the first STA. However, if no reception is detected and the backoff hold time slot count reaches zero, the STA can initiate data transmission if the NSTR transmission rules in the standard allow.

[0099] IEEE 802.11be allows a 4 microsecond mismatch in the PPDU Transmit Start Times of the two STAs that make up the NSTR link pair. This 4 microsecond value is derived from the aRxTxTurnaroundTime value, which is also equal to 4 microseconds. When the Backoff Hold Time is adjusted, this further increases the mismatch between the PPDU Start Times of the two links. According to one embodiment, the allowed mismatch in the PPDU Transmit Start Times can be increased to 4 + the Backoff Hold Time slot duration to account for the additional mismatch that may result from the Backoff Hold Time slot division.

[0100] In one embodiment, the backoff holding time slot duration may be a fixed value, such as a value mandated by a standard. In another embodiment, the backoff holding time slot duration may be determined by an individual device based on its own hardware capabilities and taking into account the amount of time it takes to perform energy detection.

[0101] In another embodiment, the backoff slot time may be a value that the AP may determine. This may be useful to maintain fairness in channel contention between non-AP MLDs that have NSTR link pairs and will use the backoff hold time slot procedure to align PPDU start times. Otherwise, if some STAs of the non-AP MLD have a smaller backoff hold time slot duration, they may gain an unfair advantage because two STAs on the same link and attached to different MLDs may count down to zero faster if their backoff hold times are the same.

[0102] According to this embodiment, the AP may send a frame to each STA to check the value of the backoff holding time slot duration that the STA intends to use on a given link. Example values ​​of the information in the frame and the size required to carry the information may be as shown in Table 1.

[0103] Table 1 below shows an example of information requested by the AP to determine the common backoff holding time slot duration of all STAs constituting an NSTR link pair.

[0104] [Table 1]

[0105]

[0106] Fig.12 An example frame format 1200 of a request frame for collecting backoff keeping time slot durations from non-AP MLDs by an AP MLD according to an embodiment of the present disclosure is shown. Fig.12 The embodiment of the example frame format 1200 shown in FIG. 1 is for illustration. Other embodiments of the example frame format 1200 may be used without departing from the scope of the present disclosure.

[0107] like Fig.12 As shown, the request frame includes a link ID element. The link ID element includes a link ID corresponding to each link for which the AP requests a backoff holding time slot duration.

[0108] Fig.13 An example link ID element 1300 of a request frame format is shown according to an embodiment of the present disclosure. Fig.13 The illustrated embodiment of the example link ID element 1300 of the request frame format is for illustration. Other embodiments of the example link ID element 1300 of the request frame format may be used without departing from the scope of the present disclosure.

[0109] like Fig.13 As shown, if the number of link IDs is an odd number, the remaining 4 bits can be reserved.

[0110] Upon receiving the request frame, the non-AP MLD may send the request information in a response frame including the information shown in Table 2.

[0111] Table 2 below shows an example of information sent by a non-AP MLD in response to an AP's request frame.

[0112] [Table 2]

[0113]

[0114] Fig.14 An example frame format 1400 of a response frame sent by a non-AP MLD to an AP MLD according to an embodiment of the present disclosure is shown. Fig.14The illustrated embodiment of the example frame format 1400 of a response frame sent by a non-AP MLD to an AP MLD is for illustration. Other embodiments of the example frame format 1400 of a response frame sent by a non-AP MLD to an AP MLD may be used without departing from the scope of the present disclosure.

[0115] like Fig.14 As shown, similar to the request frame, the response frame may also include a link ID element, which indicates the link ID for which the non-AP MLD indicates information. In addition, the response frame may also include a backoff holding time slot duration element, which includes the backoff holding time slot duration value for the link ID indicated in the link ID element. The order of the backoff holding time slot duration values ​​is the same as the order of indicating the link ID.

[0116] Fig.15 An example backoff holding time slot duration element frame format 1500 is shown according to an embodiment of the present disclosure. Fig.15 The embodiment of the example backoff holding time slot duration element frame format 1500 shown in is for illustration. Other embodiments of the example backoff holding time slot duration element frame format 1500 may be used without departing from the scope of the present disclosure.

[0117] like Fig.15 As shown, the backoff holding time slot duration element frame format may include the backoff holding time slot duration of the first link ID and the backoff holding time slot duration of the second link ID. Upon receiving the backoff holding time slot duration value from all STAs, the AP may determine an appropriate value and send the value to all STAs in a separate frame. The frame may have the same Fig.14 The format of the response frame is the same as that shown in FIG. 14. Thus, for each link ID indicated in the link ID element, the AP can provide a backoff holding time slot duration that the STAs on that particular link can use.

[0118] Fig.16 An example of a slotted backoff hold time process 1600 is shown in accordance with an embodiment of the present disclosure. Fig.15 The embodiment of the example slotted backoff keeping time process 1600 shown in FIG. 1 is for illustration. Other embodiments of the example slotted backoff keeping time process 1600 may be used without departing from the scope of the present disclosure.

[0119] like Fig.16As shown, after applying the hold time process, the behavior of the STA on link 1 can make it possible to avoid the problem of increased conflicts. As shown in the example, the STA on link 1 performs a slotted backoff hold time process. At the end of each time slot, the STA on link 1 checks the result of the energy detection. In this example, the backoff hold time duration and the time slot duration result in two time slots being calculated. At the end of each time slot, the result of the energy detection is checked to determine the next steps to be taken. At the end of time slot 1, as shown in the example, the energy detection is not completed. Therefore, the device continues to count down the time slots. At the end of time slot 2, the energy detection is completed, and the device detects that the channel is busy and postpones communication, thereby avoiding conflicts.

[0120] Fig.17 A flowchart of a method 1700 for wireless communication performed by a non-AP device according to an embodiment of the present disclosure is shown. Fig.17 The embodiment of the method 1700 for wireless communication performed by a non-AP device shown in FIG. 1 is for illustration. Other embodiments of the method 1700 for wireless communication performed by a non-AP device may be used without departing from the scope of the present disclosure.

[0121] like Fig.17 As shown, method 1700 begins at step 1702, where the non-AP MLD forms a link with the corresponding AP of the AP MLD. At step 1704, the non-AP MLD detects an NSTR link pair. At step 1706, the non-AP MLD detects an attempt by a first STA of the NSTR link pair to synchronize a start time of a PPDU with a second STA of the NSTR link pair, wherein the first STA is configured to maintain a backoff counter at a value of zero during a backoff hold time duration. At step 1708, the non-AP MLD determines a backoff hold time duration. At step 1710, the non-AP MLD determines the number of time intervals that can be accommodated in the backoff hold time duration.

[0122] In one embodiment, a non-AP MLD detects initiation of a medium synchronization loss recovery process; sends timing-associated information to an AP, the timing-associated information being configured to assist the AP in making scheduling decisions; and receives data associated with the timing-associated information from the AP.

[0123] In one embodiment, the non-AP MLD sends information associated with timing in the AAR control subfield.

[0124] In one embodiment, the information associated with timing includes measurement information associated with a delay constraint for a frame that the first STA intends to send to the AP.

[0125] In one embodiment, the non-AP MLD determines a backoff holding time duration T0L2-T0L1, where T0L1 is a duration when the backoff counter of the first STA reaches zero, T0L2 is a duration when the backoff counter of the second STA reaches zero, and T0L2>T0L1.

[0126] In one embodiment, the duration of each of the time intervals is greater than the duration of energy detection completion, and the number of time intervals that can be accommodated in the backoff hold time duration = ceil (backoff hold time duration / duration of each of the time intervals), where ceil is a round-up function.

[0127] In one embodiment, the non-AP MLD counts down by a number of time intervals; detects that an energy detect indicates an idle channel; and continues to the next time interval.

[0128] In one embodiment, the non-AP MLD adjusts the backoff holding time duration, wherein the adjusted backoff holding time duration=the duration of each of the time intervals*the number of time intervals that can be accommodated in the backoff holding time duration.

[0129] In one embodiment, the duration of each of the time intervals is a fixed value.

[0130] In one embodiment, non-AP MLD 2 determines a duration of time for each of the time intervals; and sends the duration of time for each of the time intervals.

[0131] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods or processes shown in the flow charts. For example, although shown as a series of steps, the various steps can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0132] Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A non-access point (AP) multi-link device (MLD), include: stations (STAs), each STA including a transceiver configured to form a link with a corresponding AP of the AP MLD; as well as A processor operatively coupled to the STA, the processor being configured to: Detection of non-simultaneous transmit and receive (NSTR) link pairs; detecting an attempt by a first STA of the NSTR link pair to synchronize a start time of a physical layer protocol data unit (PPDU) with a second STA of the NSTR link pair; Determine the backoff hold time duration; as well as determining a number of time intervals that can be accommodated in the backoff hold time duration, Wherein, the first STA is configured to maintain a backoff counter at a value of zero during the backoff hold time duration.

2. The non-AP MLD according to claim 1, in: The processor is further configured to detect initiation of a medium synchronization loss recovery procedure, and The transceiver is further configured to: sending information associated with timing to the AP, wherein the information associated with timing is configured to assist the AP in making a scheduling decision, Data associated with the timing-associated information is received from the AP.

3. The non-AP MLD according to claim 2, in, The transceiver is configured to transmit the timing-associated information in an AP-assisted medium synchronization recovery (AAR) control subfield.

4. The non-AP MLD according to claim 2, in, The information associated with timing includes measurement information associated with a delay constraint for a frame that the first STA intends to send to the AP.

5. The non-AP MLD according to claim 1, in, To determine the backoff hold time duration, the processor is configured to determine T0 L1 and T0 L2 ,in: T0 L1 is the duration when the backoff counter of the first STA reaches zero, T0 L2 is the duration when the backoff counter of the second STA reaches zero, T0 L2 >T0 L1 ,and The backoff holding time = T0 L2 -T0 L1 .

6. The non-AP MLD according to claim 1, in: The duration of each of the time intervals is greater than the duration of energy detection completion, The number of time intervals that can be accommodated in the backoff holding time duration=ceil(the backoff holding time duration / the duration of each time interval in the time intervals), where ceil is a ceiling function, and The duration of each of the time intervals is a fixed value.

7. The non-AP MLD according to claim 6, in, The processor is further configured to: Counting down the number of said time intervals by value one, detecting that the energy detection indicates an idle channel, Continue to the next time interval, and Adjust the duration of the backoff hold time, The adjusted backoff holding time duration=the duration of each time interval in the time intervals*the number of time intervals that can be accommodated in the backoff holding time duration.

8. The non-AP MLD according to claim 6, in: The processor is configured to determine a duration of time for each of the time intervals, and The transceiver is configured to transmit a duration of time of each of the time intervals.

9. A method for wireless communication performed by a non-access point (AP) multi-link device (MLD) including a station (STA), the method include: Establish a link with the AP corresponding to the AP MLD; Detection of non-simultaneous transmit and receive (NSTR) link pairs; detecting an attempt by a first STA of the NSTR link pair to synchronize a start time of a physical layer protocol data unit (PPDU) with a second STA of the NSTR link pair; Determine the backoff hold time duration; as well as determining a number of time intervals that can be accommodated in the backoff hold time duration, Wherein, the first STA is configured to maintain a backoff counter at a value of zero during the backoff hold time duration.

10. The method according to claim 9, further comprising: include: Detecting the initiation of a recovery process for a loss of medium synchronization; sending information associated with timing to the AP, wherein the information associated with timing is configured to assist the AP in making a scheduling decision; receiving data associated with the timing-associated information from the AP; as well as The timing-associated information is sent in an AP-Assisted Medium Synchronization Recovery (AAR) Control subfield.

11. The method according to claim 10, in, The information associated with timing includes measurement information associated with a delay constraint for a frame that the first STA intends to send to the AP.

12. The method according to claim 11, in: Determining the backoff hold time duration includes determining T0L1 and T0L2, T0L1 is the duration when the backoff counter of the first STA reaches zero, T0L2 is the duration when the backoff counter of the second STA reaches zero, T0L2>T0L1, and The backoff holding time duration=T0L2-T0L1.

13. The method according to claim 11, in: The duration of each of the time intervals is greater than the duration of energy detection completion, The number of time intervals that can be accommodated in the backoff holding time duration=ceil(the backoff holding time duration / the duration of each time interval in the time intervals), where ceil is a ceiling function, and The duration of each of the time intervals is a fixed value.

14. The method according to claim 13, further comprising: include: Counting down the number of said time intervals by value one; detecting that the energy detection indicates an idle channel; Continue to the next time interval; as well as Adjust the duration of the backoff hold time, The adjusted backoff holding time duration=the duration of each time interval in the time intervals*the number of time intervals that can be accommodated in the backoff holding time duration.

15. The method according to claim 13, further comprising: include: determining a duration of time for each of the time intervals; as well as The duration of time for each of the time intervals is sent.