Coordinated scheduling and signaling of limited target wake time (R-TWT) service periods

Abstract

The present disclosure provides methods, devices, and systems for protecting latency-sensitive communications during a restricted target wake time (r-TWT) service period (SP). Some implementations relate more specifically to coordinated scheduling of r-TWT SPs between BSSs. In some aspects, a first AP may coordinate with a second AP in scheduling r-TWT SPs such that latency-sensitive traffic in the first BSS does not interfere or collide with latency-sensitive traffic in a second BSS that overlaps with the first BSS. In some implementations, the first and second APs may schedule their respective r-TWT SPs to be orthogonal in time. In some other implementations, the first and second APs may schedule their r-TWT SPs to overlap in time when allocating coordinated resources to simultaneous or overlapping latency-sensitive traffic in the first and second BSSs (e.g., according to one or more multi-AP cooperation techniques).

Description

Technical Field

[0001] Cross-reference

[0001] This patent application claims the benefit of U.S. Patent Application No. 17 / 516,375, filed Nov. 1, 2021, by AJAMI et al., titled "COORDINATED SCHEDULING AND SIGNALING OF RESTRICTED TARGET WAKE TIME (R-TWT) SERVICE PERIODS", which has been assigned to the assignee of this application and is hereby incorporated by reference in its entirety.

[0002]

[0002] This disclosure generally relates to wireless communications, and more specifically, to coordinated scheduling and signaling of restricted Target Wake Time (r-TWT) service periods.

[0003] Description of Related Art

[0003] A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by several client devices, also called stations (STAs). The basic building block of a WLAN compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STA within the wireless range of the AP to establish or maintain a communication link with the WLAN.

[0004]

[0004] Some wireless communication devices may be associated with low-latency applications that have strict end-to-end latency, throughput, and timing requirements for data traffic. Exemplary low-latency applications include, but are not limited to, real-time gaming applications, video communications, and augmented reality (AR) and virtual reality (VR) applications (collectively referred to as extended reality (XR) applications). Such low-latency applications may specify a variety of latency, throughput, and timing requirements for the wireless communication system providing connectivity to these applications. Therefore, it is desirable to ensure that the WLAN can meet the various latency, throughput, and timing requirements of such low-latency applications. [Overview of the project]

[0005]

[0005] The systems, methods, and devices of this disclosure each have several innovative aspects, and no single aspect of them alone constitutes the desirable characteristics disclosed herein.

[0006]

[0006] One innovative aspect of the subject matter described herein can be realized as a method of wireless communication. The method may be performed by a wireless communication device and includes receiving coordinated limited target wake time (r-TWT) signaling information associated with a first r-TWT service period (SP) associated with an overlapping basic service set (OBSS); transmitting r-TWT schedule information indicating a second r-TWT SP associated with a basic service set (BSS) associated with the wireless communication device based on the coordinated r-TWT signaling information; and communicating with one or more first wireless stations (STAs) during the second r-TWT SP based on the respective latency requirements of one or more first STAs.

[0007]

[0007] In some embodiments, the first r-TWT SP may be temporally orthogonal to the second r-TWT SP. In some other embodiments, the first r-TWT may temporally overlap with the second r-TWT SP. In some implementations, communicating with one or more first STAs may include sending multi-user request-to-send (MU-RTS) frames to one or more first STAs. In some other implementations, the coordinated r-TWT signaling information may include shared SP information indicating multiple access point (multi-AP) coordination opportunities associated with the first r-TWT SP. In such implementations, communicating with one or more first STAs may include coordinating with access points (APs) associated with the OBSS based on the shared SP information so that communication with one or more first STAs occurs simultaneously with communication in the OBSS.

[0008]

[0008] In some implementations, coordinating with the AP may include exchanging with the AP transmit power information indicating at least one of the transmit power associated with communication with one or more first STAs, or the transmit power associated with communication in the OBSS. In some other implementations, coordinating with the AP may include exchanging with the AP frequency resource information indicating at least one of the allocation of frequency resources for communication with one or more first STAs, or the allocation of frequency resources for communication in the OBSS.

[0009]

[0009] In some embodiments, the coordinated r-TWT signaling information may indicate the allocation of resources for a second r-TWT SP. In some other embodiments, the coordinated r-TWT signaling information may indicate the allocation of resources for a first r-TWT SP. In some implementations, the method may further include negotiating the allocation of resources for a second r-TWT SP with the AP associated with the OBSS based on the coordinated r-TWT signaling information. In some implementations, the coordinated r-TWT signaling information may be carried in one or more packets transmitted by the AP associated with the OBSS to a wireless communication device. In some other implementations, the coordinated r-TWT signaling information may be carried in one or more management frames transmitted by the AP associated with the OBSS to one or more STAs associated with the OBSS. In some implementations, the coordinated r-TWT signaling information may be received by an STA associated with a BSS that intercepts one or more management frames transmitted by the AP associated with the OBSS.

[0010]

[0010] In some embodiments, the method may further include transmitting r-TWT coordination information indicating a first r-TWT SP associated with the OBSS. In some implementations, the r-TWT scheduling information and the r-TWT coordination information may be carried in a broadcast target wake time (TWT) information element (IE) contained in one or more packets transmitted by the wireless communication device. In some other implementations, the r-TWT scheduling information and the r-TWT coordination information may be carried in a broadcast TWT IE and a coordinating r-TWT IE, respectively, contained in one or more packets transmitted by the wireless communication device, the coordinating r-TWT IE being different from the broadcast TWT IE.

[0011]

[0011] Another innovative aspect of the subject matter described herein may be implemented in a wireless communication device. In some implementations, the wireless communication device may include at least one processor and at least one memory communicably coupled to the at least one processor and storing processor-readable code. In some implementations, the execution of processor-readable code by the at least one processor causes the wireless communication device to perform operations including receiving coordinated r-TWT signaling information associated with a first r-TWT SP associated with an OBSS, transmitting r-TWT scheduling information indicating a second r-TWT SP associated with a BSS associated with the wireless communication device based on the coordinated r-TWT signaling information, and communicating with one or more STAs in the second r-TWT SP based on the respective latency requirements of each of the one or more STAs.

[0012]

[0012] Another innovative aspect of the subject matter described herein may be realized as a method of wireless communication. The method may be performed by a wireless communication device and may include transmitting first coordinated r-TWT signaling information indicating a first r-TWT SP associated with a first BSS, and transmitting second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP. In some aspects, the first r-TWT SP may be temporally orthogonal to the second r-TWT SP.

[0013]

[0013] In some other embodiments, the first r-TWT SP may temporally overlap with the second r-TWT SP. In some implementations, the first coordinated r-TWT signaling information may indicate the transmit power associated with communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information may indicate the transmit power associated with communication in the second BSS in the second r-TWT SP. In some other implementations, the first coordinated r-TWT signaling information may indicate the allocation of a first frequency resource for communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information may indicate the allocation of a second frequency resource for communication in the second BSS in the second r-TWT SP. In such implementations, the first frequency resource may be orthogonal to the second frequency resource.

[0014]

[0014] In some implementations, the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information may be carried in a broadcast TWT IE contained in one or more packets transmitted by the wireless communication device. In some other implementations, the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information may be carried in the first and second coordinated r-TWT IEs contained in one or more packets transmitted by the wireless communication device, respectively.

[0015]

[0015] In some embodiments, the method may further include transmitting r-TWT scheduling information indicating a third r-TWT SP associated with a third BSS associated with a wireless communication device, based on a first r-TWT SP and a second r-TWT SP, and communicating with one or more STAs during the third r-TWT SP, based on the respective latency requirements of one or more STAs.

[0016]

[0016] Another innovative aspect of the subject matter described herein may be implemented in a wireless communication device. In some implementations, the wireless communication device may include at least one processor and at least one memory communicably coupled to the at least one processor and storing processor-readable code. In some implementations, the execution of processor-readable code by the at least one processor causes the wireless communication device to perform an operation that includes transmitting first cooperative r-TWT signaling information indicating a first r-TWT SP associated with a first BSS, and transmitting second cooperative r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP. [Brief explanation of the drawing]

[0017]

[0017] Details of one or more implementations of the subject matter described herein are described in the accompanying drawings and the following description. Other features, embodiments, and advantages will become apparent from the description, drawings, and claims. Note that the relative dimensions in the following figures may not be drawn to scale.

[0018] [Figure 1]

[0018] An illustrative diagram of a wireless communication network is shown. [Figure 2A]

[0019] An exemplary protocol data unit (PDU) that can be used for communication between an access point (AP) and one or more wireless stations (STAs) is shown. [Figure 2B]

[0020] Exemplary fields within the PDU of FIG. 2A are shown. [Figure 3]

[0021] An exemplary physical layer convergence protocol (PLCP) protocol data unit (PPDU) that can be used for communication between an AP and one or more STAs is shown. [Figure 4]

[0022] A block diagram of an exemplary wireless communication device is shown. [Figure 5A]

[0023] A block diagram of an exemplary AP is shown. [Figure 5B]

[0024] A block diagram of an exemplary STA is shown. [Figure 6]

[0025] A timing diagram illustrating exemplary wireless communication associated with a basic service set (BSS) that supports restricted target wake time (r-TWT) operation is shown. [Figure 7]

[0026] An exemplary communication environment having overlapping basic service sets (OBSS) according to some implementations is shown. [Figure 8]

[0027] A timing diagram illustrating exemplary wireless communication associated with an OBSS that supports r-TWT operation according to some implementations is shown. [Figure 9]

[0028] A timing diagram illustrating exemplary wireless communication associated with an OBSS that supports r-TWT operation according to some implementations is shown. [Figure 10A]

[0029] This sequence diagram illustrates exemplary message exchanges between OBSS systems that support the cooperative scheduling of r-TWT service periods (SPs) across several implementations. [Figure 10B]

[0030] The following sequence diagram illustrates exemplary message exchanges between OBSSs supporting r-TWT SP cooperative scheduling in several implementation forms. [Figure 11A]

[0031] The following sequence diagram illustrates exemplary message exchanges between OBSSs supporting r-TWT SP cooperative scheduling in several implementation forms. [Figure 11B]

[0032] The following sequence diagram illustrates exemplary message exchanges between OBSSs supporting r-TWT SP cooperative scheduling in several implementation forms. [Figure 12]

[0033] This shows exemplary packets that can be used for coordinated r-TWT signaling between one or more APs and one or more STAs, depending on several implementations. [Figure 13]

[0034] This shows another exemplary packet that can be used for coordinated r-TWT signaling between one or more APs and one or more STAs, depending on several implementations. [Figure 14]

[0035] A flowchart illustrating an exemplary process for wireless communication supporting r-TWT SP collaborative scheduling and signaling is shown. [Figure 15A]

[0036] A flowchart illustrating an exemplary process for wireless communication supporting r-TWT SP collaborative scheduling and signaling is shown. [Figure 15B]

[0037] A flowchart illustrating an exemplary process for wireless communication supporting r-TWT SP collaborative scheduling and signaling is shown. [Figure 16]

[0038] The following are block diagrams illustrating exemplary wireless communication devices in several implementation configurations. [Figure 17]

[0039] The following are block diagrams illustrating exemplary wireless communication devices in several implementation configurations.

[0019]

[0040] Similar reference numbers and names in various drawings refer to the same elements. [Modes for carrying out the invention]

[0020]

[0041] The following description covers several implementations for the purpose of illustrating innovative aspects of the present disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in numerous different ways. The implementations described may be realized in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with, among other things, one or more of the following standards: the IEEE 802.11 standard, the IEEE 802.15 standard, the Bluetooth® Special Interest Group (SIG) standard, or the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio, NR) standard published by the 3rd Generation Partnership Project (3GPP). The implementations described may be realized in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO), and multi-user (MU) MIMO.The implementations described may also be realized using other wireless communication protocols or RF signals suitable for use in one or more of the following: wireless personal area networks (WPAN), wireless local area networks (WLAN), wireless wide area networks (WWAN), or Internet of Things (IoT) networks.

[0021]

[0042] The revised IEEE 802.11be standard describes limited target wake time (r-TWT) service periods (SPs) that can be allocated to latency-sensitive traffic. As used herein, the term “non-legacy STA” refers to any wireless station (STA) that supports the revised IEEE 802.11be or any future generation of the IEEE 802.11 standard, while the term “low-latency STA” refers to any non-legacy STA that transmits or receives latency-sensitive traffic. In contrast, the term “legacy STA” may refer to any STA that supports only IEEE 802.11ax or any earlier generation of the IEEE 802.11 standard. Non-legacy STAs that support r-TWT operations and acquire transmit opportunities (TXOPs) outside of an r-TWT SP must terminate their respective TXOPs before the initiation of an r-TWT SP to which they are not members. Furthermore, the AP can suppress all traffic from legacy STAs during r-TWT SP by scheduling quiet intervals to overlap with r-TWT SP. Thus, r-TWT SP can provide latency-sensitive traffic with greater reliability, more predictable latency, reduced worst-case latency, or reduced jitter.

[0022]

[0043] Aspects of this disclosure recognize that overlapping basic service sets (OBSSs) exist in many wireless communication environments, particularly in dense or congested environments. An OBSS is any basic service set (BSS) that has an overlapping coverage area and operates on the same wireless channel as another BSS. Therefore, wireless communication on a given BSS may interfere with or collide with wireless communication on an OBSS, resulting in increased latency for communication on the BSS, OBSS, or both. Wireless communication devices (including access points (APs) and STAs) operating according to existing versions of the IEEE 802.11 standard (including the initial release (R1) of the revised IEEE 802.11be) may not recognize latency-sensitive traffic on an OBSS. Accordingly, new communication protocols and signaling are required to prevent latency-sensitive traffic on a given BSS from interfering with or colliding with latency-sensitive traffic on an OBSS.

[0023]

[0044] Various embodiments generally relate to protecting latency-sensitive communications during r-TWT SP, and more specifically, to the coordinated scheduling of r-TWT SP between OBSSs. In some embodiments, a first AP may coordinate with a second AP in scheduling r-TWT SP so that latency-sensitive traffic in the first BSS does not interfere with or collide with latency-sensitive traffic in the second BSS that overlaps with the first BSS. In some implementations, the first and second APs may schedule their respective r-TWT SPs to be temporally orthogonal. In some other implementations, the first and second APs may schedule their r-TWT SPs to overlap in time when allocating coordinated resources to simultaneous or overlapping latency-sensitive traffic in the first and second BSSs (according to one or more multi-AP coordination techniques, etc.). In some embodiments, coordinated r-TWT SPs may be scheduled by a central coordinator (such as an AP or network controller). For example, a central coordinator may communicate a coordinated r-TWT SP schedule to each of the first and second APs. In some other embodiments, the coordinated r-TWT SP may be scheduled in a distributed manner. For example, the first AP may communicate its r-TWT SP schedule to the second AP, and the second AP may schedule its r-TWT SP based on the first AP's r-TWT SP schedule.

[0024]

[0045] Certain implementations of the subject matter described herein can be realized to achieve one or more of the following potential benefits: By coordinating the scheduling of r-TWT SPs among multiple APs belonging to an OBSS, an aspect of the disclosure can significantly improve the latency gain achievable by latency-sensitive traffic through the application of r-TWT SPs. As described above, simultaneous data transmissions in an OBSS can interfere with or collide with each other, thereby increasing the latency of communications in such an OBSS. By scheduling temporally orthogonal r-TWT SPs, an aspect of the disclosure can ensure that latency-sensitive data transmissions in a given BSS occur at different times than latency-sensitive data transmissions in an OBSS, thereby avoiding interference or collisions between OBSSs. By allocating cooperative resources to latency-sensitive traffic in different OBSSs, an aspect of the disclosure can enable simultaneous transmission of latency-sensitive traffic within the same or shared r-TWT SP (e.g., at relatively low power, or on orthogonal time or frequency resources). Therefore, as a result of cooperative scheduling, r-TWT SP can provide latency-sensitive traffic in OBSS with greater reliability, more predictable latency, reduced worst-case latency, or reduced jitter.

[0025]

[0046] Figure 1 shows a block diagram of an exemplary wireless communication network 100. In some embodiments, the wireless communication network 100 may be an example of a wireless local area network (WLAN), such as a Wi-Fi network (and will be referred to hereafter as WLAN 100). For example, WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of wireless communication protocol standards (such as those specified in the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). WLAN 100 may include a number of wireless communication devices, such as access points (APs) 102 and multiple stations (STAs) 104. Although only one AP 102 is shown, the WLAN network 100 may include multiple APs 102.

[0026]

[0047] Each of the STA104 may also be called, among other possible examples, a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), user equipment (UE), a subscriber station (SS), or a subscriber unit. Among other possible examples, the STA104 may represent a variety of devices such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., in particular TVs, computer monitors, navigation systems), music or other audio or stereo devices, remote control devices ("remote"), printers, kitchen appliances or other household appliances, and key fobs (e.g., for passive keyless entry and start (PKES) systems).

[0027]

[0048] A single AP102 and an associated set of STA104 may be referred to as a basic service set (BSS) managed by each AP102. Figure 1 shows an exemplary coverage area 108 of AP102, which may additionally represent the basic service area (BSA) of WLAN100. The BSS may be identified to users by a service set identifier (SSID) and to other devices by a basic service set identifier (BSSID), which may be the medium access control (MAC) address of AP102. AP102 periodically broadcasts beacon frames ("beacons") containing the BSSID so that any STA104 within AP102's wireless range can "associate" with AP102 or reassociate with AP102 in order to establish or maintain their respective communication links 106 (hereinafter also referred to as "Wi-Fi links") with AP102. For example, a beacon may include identification information for the primary channel used by each AP102, as well as a timing synchronization function to establish or maintain timing synchronization with the AP102. The AP102 may provide access to the external network to various STA104 in the WLAN via their respective communication links 106.

[0028]

[0049] To establish a communication link 106 with AP102, each STA104 is configured to perform a passive scan operation or an active scan operation ("scan") on a frequency channel within one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands). To perform a passive scan, the STA104 listens for beacons transmitted by each AP102 at regular time intervals called the target beacon transmission time (TBTT) (measured in time units (TUs), where 1 TU may be equal to 1024 microseconds (μs)). To perform an active scan, the STA104 generates probe requests and transmits them sequentially on each channel to be scanned and listens for probe responses from AP102. Each STA104 may be configured to perform authentication and association operations to identify or select an AP102 to associate with based on scan information obtained through passive or active scanning, and to establish a communication link 106 with the selected AP102. Upon completion of the association operation, the AP102 assigns an association identifier (AID) to the STA104, which the AP102 uses to track the STA104.

[0029]

[0050] As a result of the increased ubiquity of wireless networks, STA104 may have the opportunity to select one of many BSSs within the STA's range, or to select from multiple AP102s that together form an extended service set (ESS) containing multiple connected BSSs. The extended network station associated with WLAN100 may be connected to a wired or wireless distribution system that can enable multiple AP102s to be connected within such an ESS. Thus, STA104 can be covered by two or more AP102s and can be associated with different AP102s at different times for different transmissions. In addition, after association with an AP102, STA104 may also be configured to periodically scan its vicinity to find a more suitable AP102 to associate with. For example, STA104 working with its associated AP102 may perform a “roaming” scan to find another AP102 with more desirable network characteristics, such as a higher received signal strength indicator (RSSI) or reduced traffic load.

[0030]

[0051] In some cases, STA104 may form a network without AP102 or any other equipment other than the STA104 itself. An example of such a network is an ad-hoc network (or wireless ad-hoc network). Ad-hoc networks are sometimes referred to as mesh networks or peer-to-peer (P2P) networks. In some cases, an ad-hoc network may be implemented within a larger wireless network such as WLAN100. In such an implementation, STA104 may communicate with each other via AP102 using communication link 106, but STA104 may also communicate with each other directly via direct wireless link 110. In addition, two STA104 may communicate via direct communication link 110, regardless of whether both STA104 are associated with and serviced by the same AP102. In such an ad-hoc system, one or more of the STA104 may take on roles that are fulfilled by AP102 in the BSS. Such an STA104 may be called a group owner (GO) and can coordinate transmissions within an ad-hoc network. Examples of direct wireless links 110 include Wi-Fi Direct connections, connections established using Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other P2P group connections.

[0031]

[0052] AP102 and STA104 can function and communicate (via their respective communication links 106) in accordance with the IEEE 802.11 family of wireless communication protocol standards (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, as defined in the IEEE 802.11-2016 specification or its revisions). These standards define WLAN radio and baseband protocols for the PHY layer and the media access control (MAC) layer. AP102 and STA104 transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") between themselves in the form of Physical Layer Convergence Protocol (PLCP) protocol data units (PPDUs). AP102 and STA104 in WLAN100 may transmit PPDUs over unlicensed spectrum, which may be a portion of the spectrum including frequency bands conventionally used by Wi-Fi technology, such as the 2.4GHz band, 5GHz band, 60GHz band, 3.6GHz band, and 700MHz band. Some implementations of AP102 and STA104 described herein may also communicate over other frequency bands, such as the 6GHz band, which may support both licensed and unlicensed communications. AP102 and STA104 may be configured to communicate over other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in the same or overlapping frequency bands.

[0032]

[0053] Each frequency band may contain multiple subbands or frequency channels. For example, PPDUs compliant with the IEEE 802.11n, 802.11ac, 802.11ax, and revised 802.11be standards may be transmitted over the 2.4GHz, 5GHz, or 6GHz band, each divided into multiple 20MHz channels. Thus, these PPDUs are transmitted over physical channels with a minimum bandwidth of 20MHz, but larger channels can be formed through channel bonding. For example, a PPDU may be transmitted over physical channels with bandwidths of 40MHz, 80MHz, 160MHz, or 320MHz by bonding multiple 20MHz channels together.

[0033]

[0054] Each PPDU is a composite structure containing a PHY preamble and payload in the form of a PHY service data unit (PSDU). Information provided within the preamble may be used by the receiving device to decode subsequent data within the PSDU. In examples where PPDUs are transmitted over bonded channels, the preamble fields may be duplicated and transmitted on each of the multiple component channels. A PHY preamble may contain both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble may be used, among other applications, for packet detection, automatic gain control, and channel estimation. The legacy preamble may also generally be used to maintain compatibility with legacy devices. The format, coding, and information provided within the non-legacy portion of the preamble are based on the specific IEEE 802.11 protocol that will be used to transmit the payload.

[0034]

[0055] Figure 2A shows an exemplary protocol data unit (PDU) 200 that can be used for wireless communication between AP102 and one or more STA104s. For example, PDU 200 may be configured as a PPDU. As shown, PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, preamble 202 may include a legacy portion which itself includes a legacy short training field (L-STF) 206 which may consist of two BPSK symbols, a legacy long training field (L-LTF) 208 which may consist of two BPSK symbols, and a legacy signal field (L-SIG) 210 which may consist of two BPSK symbols. The legacy portion of preamble 202 may be configured according to the IEEE 802.11a wireless communication protocol standard. The preamble 202 may also include a non-legacy portion containing one or more non-legacy fields 212 that conform to an IEEE wireless communication protocol, such as IEEE 802.11ac, 802.11ax, 802.11be, or later wireless communication protocol standards.

[0035]

[0056] The L-STF206 generally allows the receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. The L-LTF208 generally allows the receiving device to perform fine timing and frequency estimation and also allows for initial estimation of the wireless channel. The L-SIG210 generally allows the receiving device to determine the duration of a PDU to avoid transmitting over the PDU and to use the determined duration. For example, the L-STF206, L-LTF208, and L-SIG210 can be modulated according to binary phase shift keying (BPSK) modulation scheme. The payload 204 may be modulated according to BPSK modulation scheme, quadrature BPSK (Q-BPSK) modulation scheme, quadrature amplitude modulation (QAM) modulation scheme, or another suitable modulation scheme. The payload 204 may include a PSDU containing a data field (DATA) 214, which may carry upper-layer data in the form of, for example, a Media Access Control (MAC) protocol data unit (MPDU) or an aggregated MPDU (A-MPDU).

[0036]

[0057] Figure 2B shows an exemplary L-SIG210 within the PDU200 in Figure 2A. The L-SIG210 includes a data rate field 222, reserved bits 224, a length field 226, parity bits 228, and a tail field 230. The data rate field 222 indicates the data rate (note that the data rate indicated in the data rate field 212 may not be the actual data rate of the data carried in the payload 204). The length field 226 indicates the length of the packet, for example, in units of symbols or bytes. The parity bits 228 may be used to detect bit errors. The tail field 230 includes tail bits that may be used by the receiving device to terminate the operation of the decoder (e.g., a Viterbi decoder). The receiving device may utilize the data rate and length indicated in the data rate field 222 and length field 226 to determine the duration of the packet, for example, in units of microseconds (μs) or other units of time.

[0037]

[0058] Figure 3 shows an exemplary PPDU 300 that can be used for communication between AP 102 and one or more STA 104s. As described above, each PPDU 300 includes a PHY preamble 302 and a PSDU 304. Each PSDU 304 may represent (or "carry") one or more MAC protocol data units (MPDUs) 316. For example, each PSDU 304 may carry an aggregate MPDU (A-MPDU) 306 that includes an aggregation of multiple A-MPDU subframes 308. Each A-MPDU subframe 306 may include an MPDU frame 310 that includes a MAC delimiter 312 and a MAC header 314 before an accompanying MPDU 316 which contains the data portion ("payload" or "frame body") of the MPDU frame 310. Each MPDU frame 310 may include a frame check sequence (FCS) field 318 for error detection (for example, the FCS field may include a cyclic redundancy check (CRC)) and padding bits 320. An MPDU 316 can carry one or more MAC service data units (MSDUs) 326. For example, an MPDU 316 may carry an aggregate MSDU (A-MSDU) 322 containing multiple A-MSDU subframes 324. Each A-MSDU subframe 324 includes a corresponding MSDU 330, preceded by a subframe header 328 and optionally followed by padding bits 332.

[0038]

[0059] Referring again to the MPDU frame 310, the MAC delimiter 312 acts as a marker for the start of the associated MPDU 316 and may indicate the length of the associated MPDU 316. The MAC header 314 may include several fields containing information that defines or indicates the characteristics or attributes of the data encapsulated within the frame body 316. The MAC header 314 may include a duration field indicating the duration that continues from the end of the PPDU until the end of the PPDU acknowledgment (ACK) or block ACK (BA) that will be transmitted by the receiving wireless communication device. The use of the duration field helps reserve the wireless medium for the indicated duration, allowing the receiving device to establish its network allocation vector (NAV). The MAC header 314 also includes one or more fields indicating the addresses of the data encapsulated within the frame body 316. For example, the MAC header 314 may include a source address, transmitter address, receiver address, or a combination of destination addresses. The MAC header 314 may further include a frame control field containing control information. The frame control field can specify the frame type, such as a data frame, control frame, or management frame.

[0039]

[0060] Figure 4 shows a block diagram of an exemplary wireless communication device 400. In some implementations, the wireless communication device 400 may be an example of a device used in an STA, such as one of the STA104 described with reference to Figure 1. In some implementations, the wireless communication device 400 may be an example of a device used in an AP, such as an AP102 described with reference to Figure 1. The wireless communication device 400 is capable of transmitting (or outputting for transmission) and receiving wireless communications (for example, in the form of wireless packets). For example, a wireless communication device may be configured to transmit and receive packets in the form of Physical Layer Convergence Protocol (PLCP) protocol data units (PPDUs) and Medium Access Control (MAC) protocol data units (MPDUs) that comply with IEEE 802.11 wireless communication protocol standards such as those specified in the IEEE 802.11-2016 specification or its revisions, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be.

[0040]

[0061] The wireless communication device 400 may be a chip, system on a chip (SoC), chipset, package, or device, or may include one or more modems 402, such as Wi-Fi (IEEE 802.11 compliant) modems. In some implementations, one or more modems 402 (collectively, "modem 402") may additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compliant modem). In some implementations, the wireless communication device 400 may also include one or more radios 404 (collectively, "radio 404"). In some implementations, the wireless communication device 406 may further include one or more processors, processing blocks or processing elements 406 (collectively, "processor 406"), and one or more memory blocks or elements 408 (collectively, "memory 408").

[0041]

[0062] The modem 402 may include intelligent hardware blocks or devices, such as application-specific integrated circuits (ASICs), among other possible examples. The modem 402 is generally configured to implement the PHY layer. For example, the modem 402 is configured to modulate packets and output the modulated packets to the radio 404 for transmission over the wireless medium. The modem 402 is also configured to acquire the modulated packets received by the radio 404 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 402 may further include digital signal processing (DSP) circuits, automatic gain control (AGC), a coder, a decoder, a multiplexer, and a demultiplexer. For example, while in transmit mode, data acquired from the processor 406 is provided to the coder, which encodes the data to provide encoded bits. The encoded bits are then mapped to points in a modulation constellation (using a selected MCS) to provide modulated symbols. Next, the modulated symbol is N SS A spatial stream of a number of elements or N STSIt can be mapped to a number of spatiotemporal streams. Then, each spatial stream or modulated symbol within a spatiotemporal stream can be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and subsequently provided to a DSP circuit for TX windowing and filtering. The digital signal can then be provided to a digital-to-analog converter (DAC). The resulting analog signal can then be provided to a frequency upconverter and finally to the radio 404. In implementations with beamforming, the modulated symbols within each spatial stream are precoded via a steering matrix before being provided to the IFFT block.

[0042]

[0063] While in receive mode, the digital signal received from the radio 404 is supplied to a DSP circuit, which is configured to collect the received signal, for example, by detecting the presence of the signal and estimating the initial timing and frequency offset. The DSP circuit is further configured to digitally adjust the digital signal, for example, by using channel (narrowband) filtering, analog fault correction (such as correcting I / Q imbalance), and by applying digital gain to finally obtain a narrowband signal. The output of the DSP circuit may then be supplied to an AGC, which is configured to use information extracted from the digital signal in one or more received training fields to determine, for example, an appropriate gain. The output of the DSP circuit is also coupled to a demodulator, which is configured to extract modulated symbols from the signal and calculate, for example, logarithm likelihood ratios (LLRs) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which may be configured to process the LLRs to provide the decoded bits. Next, the decoded bits from all of the spatial stream are fed to a demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 406) for processing, evaluation, or interpretation.

[0043]

[0064] The radio 404 generally includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which may be combined into one or more transceivers. For example, the RF transmitter and RF receiver may each include various DSP circuits, each including at least one power amplifier (PA) and at least one low-noise amplifier (LNA). The RF transmitter and RF receiver may then be coupled to one or more antennas. For example, in some implementations, the wireless communication device 400 may include, or be coupled with, multiple transmitting antennas (each with a corresponding transmitting chain) and multiple receiving antennas (each with a corresponding receiving chain). Symbols output from the modem 402 are provided to the radio 404, which then transmits the symbols via the coupled antennas. Similarly, symbols received via the antennas are acquired by the radio 404, which then provides the symbols to the modem 402.

[0044]

[0065] The processor 406 may include intelligent hardware blocks or devices, such as processing cores, processing blocks, central processing units (CPUs), microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs) such as field programmable gate arrays (FPGAs), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The processor 406 processes information received via the radio 404 and modem 402 and processes the information to be output via the modem 402 and radio 404 for transmission over a wireless medium. For example, the processor 406 may implement a control plane and MAC layer configured to perform various operations relating to the generation and transmission of MPDUs, frames, or packets. Among the operations or techniques, the MAC layer may perform or be configured to facilitate frame coding and decoding, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation. In some implementations, the processor 406 can generally control the modem 402 to cause the modem to perform the various operations described above.

[0045]

[0066] Memory 408 may include tangible storage media such as random-access memory (RAM), read-only memory (ROM), or a combination thereof. Memory 408 may also store non-temporary processor or computer-executable software (SW) code, which, when executed by processor 406, causes the processor to perform various operations for wireless communication described herein, including generating, transmitting, receiving, and interpreting MPDUs, frames, or packets. For example, various functions of the components disclosed herein, or various blocks or steps of the methods, operations, processes, or algorithms disclosed herein, may be executed as one or more modules of one or more computer programs.

[0046]

[0067] Figure 5A shows a block diagram of an exemplary AP502. For example, AP502 may be an exemplary implementation of AP102 described with reference to Figure 1. AP502 includes a wireless communication device (WCD) 510 (although AP502 itself may be commonly referred to as the wireless communication device used herein). For example, wireless communication device 510 may be an exemplary implementation of wireless communication device 400 described with reference to Figure 4. AP502 also includes a number of antennas 520 coupled with the wireless communication device 510 for transmitting and receiving wireless communications. In some implementations, AP502 also includes an application processor 530 coupled with the wireless communication device 510 and memory 540 coupled with the application processor 530. AP502 further includes at least one external network interface 550 that enables AP502 to communicate with a core network or backhaul network in order to access an external network, including the Internet. For example, the external network interface 550 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Some of the components described above can communicate directly or indirectly with some of the other components via at least one bus. The AP 502 further includes a housing that encompasses at least a portion of the wireless communication device 510, application processor 530, memory 540, and antenna 520, and the external network interface 550.

[0047]

[0068] Figure 5B shows a block diagram of an exemplary STA504. For example, STA504 may be an exemplary implementation of STA104 described with reference to Figure 1. STA504 includes a wireless communication device 515 (although STA504 itself may be more commonly referred to as the wireless communication device used herein). For example, the wireless communication device 515 may be an exemplary implementation of the wireless communication device 400 described with reference to Figure 4. STA504 also includes one or more antennas 525 coupled with the wireless communication device 515 for transmitting and receiving wireless communications. In addition, STA504 includes an application processor 535 coupled with the wireless communication device 515 and a memory 545 coupled with the application processor 535. In some implementations, STA504 further includes a user interface (UI) 555 (such as a touchscreen or keypad) and a display 565, the display 565 of which may be integrated with the UI 555 to form a touchscreen display. In some implementations, the STA504 may further include one or more sensors 575, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Some of the above-mentioned components can communicate directly or indirectly with some of the other components via at least one bus. The STA504 further includes a housing that includes a wireless communication device 515, an application processor 535, memory 545, and at least a portion of an antenna 525, a UI 555, and a display 565.

[0048]

[0069] The revised IEEE 802.11be standard describes limited target wake time (r-TWT) service periods (SPs) that may be allocated for latency-sensitive traffic. As used herein, the term “non-legacy STA” refers to any STA that supports the revised IEEE 802.11be or any future generation of the IEEE 802.11 standard, while the term “low-latency STA” refers to any non-legacy STA that transmits or receives latency-sensitive traffic. In contrast, the term “legacy STA” may refer to any STA that supports only IEEE 802.11ax or any earlier generation of the IEEE 802.11 standard. Non-legacy STAs that support r-TWT operations and acquire TXOPs outside of an r-TWT SP must terminate their respective TXOPs before the initiation of an r-TWT SP to which they are not members. Furthermore, the AP can suppress all traffic from legacy STAs during r-TWT SP by scheduling a silence interval that overlaps with r-TWT SP. Thus, r-TWT SP can provide latency-sensitive traffic with greater reliability, more predictable latency, reduced worst-case latency, or reduced jitter.

[0049]

[0070] Figure 6 shows a timing diagram 600 illustrating exemplary wireless communication associated with a BSS supporting r-TWT operation. In the example in Figure 6, the BSS may include multiple non-legacy STAs 602 and 604 that support r-TWT operation. More specifically, STA 602 may be a low-latency STA that is a member of an r-TWT SP over a duration from time t3 to t8, while STA 604 may be a non-member STA. In some implementations, each of STA 602 and 604 may be an example of either STA 104 or 504 in Figures 1 and 5B, respectively. Although two non-legacy STAs 602 and 604 are shown in the example in Figure 6 in actual implementations, the BSS may include any number of legacy or non-legacy STAs.

[0050]

[0071] The non-member STA604 attempts to access the shared wireless channel before initiating the r-TWT SP. More specifically, based on channel detection behavior (such as clear channel assessment, CCA), the non-member STA604 detects that the channel is idle for a threshold duration from time t0 to t1, and further counts down a random backoff (RBO) duration from time t1 to t2 before attempting to acquire a TXOP. For example, the threshold duration (from time t0 to t1) could be the arbitration interframe spacing (AIFS) duration associated with a particular access category (AC) of data traffic. Accordingly, the RBO duration (from time t1 to t2) could be randomly selected from a range of RBOs across the competition window associated with the AC. At time t2, the non-member STA604 detects that the wireless channel is still idle and proceeds to acquire a TXOP, for example, by initiating transmission over the shared channel. In the example in Figure 6, the desired TXOP may be longer than the remaining duration before the start of the r-TWT SP at time t3. However, since existing rules regarding r-TWT operations require non-member STAs to terminate their TXOPs at the start of the r-TWT SP, non-member STA604 must shorten its TXOP between times t2 and t3.

[0051]

[0072] The low-latency STA602 attempts to access the shared wireless channel at the start of the r-TWT SP. In the example in Figure 6, the low-latency STA602 detects that the channel is idle during the AIFS duration from time t3 to t4, and further counts down the TXOP duration from time t4 to t6 before attempting to acquire a TXOP. As shown in Figure 6, the non-member STA604 also attempts to access the shared wireless channel at the start of the r-TWT SP. For example, the non-member STA604 detects that the channel is idle during the AIFS duration from time t3 to t5, and further counts down the RBO duration starting at time t5. In some implementations, data traffic associated with the low-latency STA602 may be assigned to ACs with higher priority than data traffic associated with the non-member STA604. Thus, the AIFS or RBO duration associated with the low-latency STA602 may be shorter than the AIFS or RBO duration associated with the non-member STA604, respectively. As a result, the low-latency STA602 gains access to the wireless channel and obtains TXOP at time t6, for example, by initiating transmission over the shared channel.

[0052]

[0073] Non-member STA604 detects at time t6 that the wireless medium is busy and refrains from accessing the shared channel for the duration of the TXOP (from t6 to t7). After the TXOP ends, at time t7, non-member STA604 may attempt to access the wireless channel again. In this way, r-TWT operations can prioritize latency-sensitive traffic in the BSS, for example, by requiring other non-member STAs to terminate their TXOPs at the start of r-TWT SPs to which they do not belong as members. Furthermore, an AP (not shown for simplicity) can suppress all traffic from legacy STAs associated with the BSS by scheduling a quiet interval to overlap with at least a portion of the r-TWT SP (such as one or more time units (TUs) following time t3). For example, the duration of the quiet interval may be indicated by one or more quiet elements contained within management frames (such as beacon frames and probe response frames) sent by the AP before the start of the r-TWT SP.

[0053]

[0074] As explained above, OBSSs exist in many wireless communication environments, especially in dense or congested environments. An OBSS is any BSS that has overlapping coverage areas and operates on the same wireless channel as another BSS. Therefore, wireless communication on a given BSS may interfere with or collide with wireless communication on an OBSS, resulting in increased latency for communication on the BSS, OBSS, or both. Wireless communication devices (including APs and STAs) operating according to existing versions of the IEEE 802.11 standard (including the initial release (R1) of the revised IEEE 802.11be) may not be aware of latency-sensitive traffic on the OBSS. Accordingly, new communication protocols and signaling are needed to prevent latency-sensitive traffic on a given BSS from interfering with or colliding with latency-sensitive traffic on the OBSS.

[0054]

[0075] Various embodiments generally relate to latency-sensitive communications, and more specifically, to coordinating latency-sensitive communications between OBSSs. In some embodiments, a first AP may coordinate with a second AP in scheduling r-TWT SPs so that latency-sensitive traffic in the first BSS does not interfere with or collide with latency-sensitive traffic in the second BSS that overlaps with the first BSS. In some implementations, the first and second APs may schedule their respective r-TWT SPs to be temporally orthogonal. In some other implementations, the first and second APs may schedule their r-TWT SPs to overlap in time when allocating coordinating resources to simultaneous or overlapping latency-sensitive traffic in the first and second BSSs (according to one or more multi-AP coordination techniques, etc.). In some embodiments, the coordinated r-TWT SPs may be scheduled by a central coordinator (such as an AP or network controller). For example, a central coordinator may communicate a coordinated r-TWT SP schedule to each of the first and second APs. In some other embodiments, the coordinated r-TWT SP may be scheduled in a distributed manner. For example, the first AP may communicate its r-TWT SP schedule to the second AP, and the second AP may schedule its r-TWT SP based on the first AP's r-TWT SP schedule.

[0055]

[0076] Certain implementations of the subject matter described herein can be realized to achieve one or more of the following potential benefits: By coordinating r-TWT SPs among multiple APs belonging to an OBSS, an aspect of the disclosure can significantly improve the latency gain achievable by latency-sensitive traffic through the application of r-TWT SPs. As described above, simultaneous data transmissions in an OBSS can interfere with or collide with each other, thereby increasing the latency of communications in such an OBSS. By scheduling temporally orthogonal r-TWT SPs, an aspect of the disclosure can ensure that latency-sensitive data transmissions in a given BSS occur at different times than latency-sensitive data transmissions in an OBSS, thereby avoiding interference or collisions between OBSSs. By allocating cooperative resources to latency-sensitive traffic in different OBSSs, an aspect of the disclosure can enable simultaneous transmission of latency-sensitive traffic within the same or shared r-TWT SP (e.g., at relatively low power, or on orthogonal time or frequency resources). As a result of collaborative scheduling, r-TWT SP can provide latency-sensitive traffic within OBSS with greater reliability, more predictable latency, reduced worst-case latency, or reduced jitter.

[0056]

[0077] Figure 7 shows an exemplary communication environment 700 having OBSS in several implementation forms. More specifically, the exemplary communication environment 700 includes several STA701-706 and several AP711-713. In some implementation forms, each of STA701-706 may be an example of either STA104 or 504 in Figures 1 and 5B. In some implementation forms, each of AP711-713 may be an example of either AP102 or 502 in Figures 1 and 5A. AP711-713 may each represent a BSS (BSS1-BSS3) having coverage areas 711-713.

[0057]

[0078] As shown in Figure 7, STA701 and 702 are associated with AP711 (or BSS1) and located within coverage area 721, STA703-705 are associated with AP712 (or BSS2) and located within coverage area 722, and STA706 is associated with AP713 (or BSS3) and located within coverage area 723. In the example in Figure 7, each of AP711-713 may be configured to operate on the same wireless channel. Furthermore, AP711 and 712 have overlapping coverage areas 721 and 722, respectively. Therefore, AP711 and 712 represent OBSS. Similarly, AP712 and 713 have overlapping coverage areas 722 and 723, respectively. Therefore, AP712 and 713 represent OBSS.

[0058]

[0079] In some embodiments, each of STA701-706 and each of AP711-713 may support r-TWT operation. More specifically, AP711 may schedule one or more r-TWT SPs that can be used by its associated STA701 and 702 to communicate latency-sensitive traffic; AP712 may schedule one or more r-TWT SPs that can be used by its associated STA703-705 to communicate latency-sensitive traffic; and AP713 may schedule one or more r-TWT SPs that can be used by its associated STA706 to communicate latency-sensitive traffic. Since BSS2 overlaps with BSS1 and BSS3, wireless communications in BSS2 may interfere with or collide with wireless communications in either BSS1 or BSS3. Similarly, wireless communications in either BSS1 or BSS3 may interfere with or collide with wireless communications in BSS2.

[0059]

[0080] In some embodiments, AP711 and 712 may coordinate the scheduling of their respective r-TWT SPs to avoid interference or collisions between latency-sensitive data traffic in BSS1 and latency-sensitive data traffic in BSS2. Thus, AP711 and 712 may be referred to herein as “r-TWT coordinated APs”. In some implementations, AP711 and 712 may schedule their respective r-TWT SPs to be temporally orthogonal. For example, AP711 may schedule one or more r-TWT SPs to occur during time periods that do not overlap with any r-TWT SPs scheduled by AP712. Similarly, AP712 may schedule one or more r-TWT SPs to occur during time periods that do not overlap with any r-TWT SPs scheduled by AP711. In some other implementations, AP711 and 712 may schedule their r-TWT SPs to overlap in time when allocating cooperative resources to simultaneous or overlapping latency-sensitive traffic in BSS1 and BSS2 (for example, by using one or more multi-AP coordination techniques). For example, within the same or overlapping r-TWT SP, latency-sensitive traffic may be transmitted at relatively low power or over different time or frequency resources across BSS1 and BSS2.

[0060]

[0081] In some embodiments, coordinated r-TWT SPs can be scheduled by a central coordinator. For example, the central coordinator may schedule r-TWT SPs for each of AP711 and 712 and communicate the r-TWT SP schedule to AP711 and 712 via coordinated r-TWT signaling. In some implementations, the central coordinator may be an AP, such as one of AP711 or 712. In some other implementations, the central coordinator may be a network controller that communicates with AP711 and 712 via (wired or wireless) backhaul. In some other embodiments, coordinated r-TWT SPs can be scheduled in a distributed manner. For example, AP711 may communicate its r-TWT SP schedule to AP712, and AP712 may schedule its r-TWT SPs based on AP711's r-TWT SP schedule. In some implementations, AP711 may "explicitly" signal its r-TWT SP schedule to AP712 via wired backhaul or in one or more packets sent to (or intended to be received by AP712). In some other implementations, AP711 may "implicitly" signal its r-TWT SP schedule to AP712. In such implementations, AP712 may obtain AP711's r-TWT SP schedule by intercepting one or more packets sent by AP711 to its associated STA (such as STA701 or 702).

[0061]

[0082] In some implementations, each of the r-TWT coordinating APs 711 and 712 may transmit or broadcast coordinating r-TWT signaling information to other nearby APs or STAs. For example, AP 711 may broadcast its r-TWT SP schedule and AP 712's r-TWT SP schedule to its associated STAs 701 and 702, as well as to any other APs within wireless communication range. Accordingly, STAs 701 and 702 (with other APs) may schedule their latency-sensitive communications to occur simultaneously with AP 712's r-TWT SP while avoiding AP 711's r-TWT SP. Similarly, AP 712 may broadcast its r-TWT SP schedule and AP 711's r-TWT SP schedule to its associated STAs 703-705 and any other APs within wireless communication range. Accordingly, STA703~705 can schedule their latency-sensitive communications to occur simultaneously with AP711's r-TWT SP, while avoiding AP712's r-TWT SP.

[0062]

[0083] In some embodiments, AP713 may not coordinate its r-TWT SP scheduling with AP712 (or may not support coordinated r-TWT scheduling). Therefore, AP713 may be referred to herein as a “non-coordinated r-TWT AP”. In some implementations, AP712 may obtain AP713’s r-TWT SP schedule by intercepting beacon frames, management frames, or other packets transmitted by AP713 to its associated STA (e.g., STA706). Accordingly, AP712 may schedule its own r-TWT SP based on AP713’s r-TWT SP schedule. In some implementations, AP712 may schedule its r-TWT SP so as to be temporally orthogonal to (or avoiding) the r-TWT SP scheduled by AP713. In some other implementations, AP712 may utilize other information associated with AP713 in addition to AP713’s r-TWT SP schedule when scheduling its own r-TWT SP. For example, AP712 can evaluate the level of interference from AP713 based on the received signal strength indication (RSSI) of the wireless signal received from AP713, and adjust the transmission power or timing of latency-sensitive traffic in BSS2 to avoid interference or collision with latency-sensitive traffic in BSS3.

[0063]

[0084] In some other embodiments, AP713 may be hidden from (or undetectable from) AP712. In some implementations, AP712 may obtain AP713's r-TWT SP schedule from one or more associated STAs (such as STA705) located within AP713's coverage area 723. For example, STA705 may intercept one or more beacon frames, management frames, or other packets transmitted by AP713 to its associated STA (such as STA706). STA705 may analyze the intercepted packets for r-TWT schedule information indicating AP713's r-TWT SP schedule and relay the r-TWT SP schedule to AP712. Accordingly, AP712 may schedule its r-TWT SPs based on AP713's r-TWT SP schedule. In some implementations, AP712 may schedule its r-TWT SP to be temporally orthogonal to (or avoiding) the r-TWT SP scheduled by AP713. In some other implementations, AP712 may, in scheduling its own r-TWT SP, utilize other information associated with AP713 (such as the RSSI of the wireless signal received from AP713) in addition to AP713's r-TWT SP schedule. For example, AP712 may adjust the transmit power or timing of latency-sensitive traffic in BSS2 to avoid interference or collision with latency-sensitive traffic in BSS3.

[0064]

[0085] Figure 8 shows a timing diagram illustrating exemplary wireless communication associated with OBSSs (BSS1-BSS3) that support r-TWT operation in several implementation forms. In the example in Figure 8, BSS1, BSS2, and BSS3 are represented by access points AP1, AP2, and AP3, respectively. In some implementation forms, access points AP1, AP2, and AP3 may be examples of AP711, 712, and 713 in Figure 7, respectively. As shown in Figure 8, access points AP1 and AP2 belong to a cooperative r-TWT scheduling group. Therefore, access points AP1 and AP2 can coordinately schedule their r-TWT SPs so that latency-sensitive data traffic in BSS1 does not interfere with or collide with latency-sensitive data traffic in BSS2. In contrast, access point AP3 does not belong to a cooperative r-TWT scheduling group. Therefore, access point AP3 does not coordinately schedule its r-TWT SPs with either access point AP1 or AP2.

[0065]

[0086] In some implementations, access points AP1 and AP2 can schedule their r-TWT SPs to be temporally orthogonal while avoiding the r-TWT SP scheduled by access point AP3. As shown in Figure 8, access point AP3 schedules an r-TWT SP (r-TWT SP3) to occur between time t3 and t4. Accordingly, access points AP1 and AP2 can avoid scheduling either of their r-TWT SPs to occur between t3 and t4. In the example in Figure 8, access point AP1 schedules an r-TWT SP (r-TWT SP1) to occur between time t1 and t2, and access point AP2 schedules an r-TWT SP (r-TWT SP2) to occur between t2 and t3. In some implementations, each of the service periods r-TWT SP1, r-TWT SP2, and r-TWT SP3 may be an example of an r-TWT SP shown in Figure 6 (from time t3 to t8). Accordingly, the first access point AP1 may communicate latency-sensitive data with one or more low-latency STAs in BSS1 during r-TWT SP1, the second access point AP2 may communicate latency-sensitive data with one or more low-latency STAs in BSS2 during r-TWT SP2, and the third access point AP3 may communicate latency-sensitive data with one or more low-latency STAs in BSS3 during r-TWT SP3.

[0066]

[0087] Aspects of this disclosure recognize that STAs located at the edge of an AP's coverage area (such as STA702, 703, and 705 in Figure 7) are more susceptible to interference from OBSS than STAs located closer to the AP. Therefore, assigning such STAs to temporally orthogonal r-TWT SPs can significantly improve the quality of their latency-sensitive data communications compared to other means of coordinated r-TWT scheduling. In some embodiments, each of access points AP1, AP2, and AP3 may assign or allocate low-latency STAs to service-period r-TWT SP1, r-TWT SP2, and r-TWT SP3, respectively, based on r-TWT scheduling information carried in beacons or other management frames transmitted before (or during) one or more r-TWT SPs. In some implementations, r-TWT scheduling information associated with a particular r-TWT SP may assign one or more STAs to that r-TWT SP. In some other implementations, the STA may request to join a particular r-TWT SP in response to receiving r-TWT scheduling information associated with that SP.

[0067]

[0088] As shown in Figure 8, at time t0, access point AP1 transmits a beacon frame 801 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP1. For example, referring to Figure 7, beacon frame 801 may be transmitted by AP711 and may assign or allocate STA702 to r-TWT SP1. At time t0, access point AP2 transmits a beacon frame 802 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP2. For example, referring to Figure 7, beacon frame 802 may be transmitted by AP712 and may assign or allocate one or more of STA703 or 705 to r-TWT SP2. At time t0, access point AP3 transmits a beacon frame 803 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP3. For example, referring to Figure 7, beacon frame 803 may assign or allocate STA706 to r-TWT SP3. Figure 8 shows beacon frames 801-803 transmitted at the same time (t0), but in some other implementations, one or more of the beacon frames 801-803 may be transmitted at different times.

[0068]

[0089] In some implementations, beacon frames 801 and 802 broadcast by coordinating access points AP1 and AP2, respectively, may further carry coordinating r-TWT signaling information. As described above, the coordinating r-TWT signaling information may indicate r-TWT SP schedules associated with one or more OBSSs. For example, beacon frame 801 may carry coordinating r-TWT signaling information indicating a schedule for one or more of the service periods r-TWT SP2 or r-TWT SP3, and beacon frame 802 may carry coordinating r-TWT signaling information indicating a schedule for one or more of the service periods r-TWT SP1 or r-TWT SP3. As used herein, the term “schedule” may include timing information, resource allocation information, or various other communication parameters associated with the r-TWT SP. For example, a schedule for r-TWT SP1 may indicate that r-TWT SP1 occurs between time t1 and t2; a schedule for r-TWT SP2 may indicate that r-TWT SP2 occurs between time t2 and t3; and a schedule for r-TWT SP3 may indicate that r-TWT SP3 occurs between time t3 and t4.

[0069]

[0090] Figure 9 shows a timing diagram illustrating exemplary wireless communication associated with OBSSs (BSS1-BSS3) supporting r-TWT operation in several implementation forms. In the example in Figure 9, BSS1, BSS2, and BSS3 are represented by access points AP1, AP2, and AP3, respectively. In some implementation forms, access points AP1, AP2, and AP3 may be examples of AP711, 712, and 713 in Figure 7, respectively. As shown in Figure 9, access points AP1 and AP2 belong to a cooperative r-TWT scheduling group. Therefore, access points AP1 and AP2 can coordinately schedule their r-TWT SPs so that latency-sensitive data traffic in BSS1 does not interfere with or collide with latency-sensitive data traffic in BSS2. In contrast, access point AP3 does not belong to a cooperative r-TWT scheduling group. Therefore, access point AP3 does not coordinately schedule its r-TWT SPs with either access point AP1 or AP2.

[0070]

[0091] In some implementations, access points AP1 and AP2 may schedule their r-TWT SPs to overlap in time while avoiding the r-TWT SP scheduled by access point AP3. As shown in Figure 9, access point AP3 schedules an r-TWT SP (r-TWT SP3) to occur between time t2 and t3. Accordingly, access points AP1 and AP2 may avoid scheduling either of their r-TWT SPs to occur between t2 and t3. In the example in Figure 9, access points AP1 and AP2 schedule their respective r-TWT SPs (r-TWT SP1 and r-TWT SP2) to occur between time t1 and t2. In some implementations, each of the service periods r-TWT SP1, r-TWT SP2, and r-TWT SP3 may be an example of an r-TWT SP shown in Figure 6 (from time t3 to t8). Accordingly, the first access point AP1 may communicate latency-sensitive data with one or more low-latency STAs in BSS1 during r-TWT SP1, the second access point AP2 may communicate latency-sensitive data with one or more low-latency STAs in BSS2 during r-TWT SP2, and the third access point AP3 may communicate latency-sensitive data with one or more low-latency STAs in BSS3 during r-TWT SP3.

[0071]

[0092] In some embodiments, access points AP1 and AP2 may coordinate their resource allocation for wireless communications during overlapping service periods r-TWT SP1 and r-TWT SP2 to prevent latency-sensitive traffic in BSS1 from interfering with or colliding with latency-sensitive traffic in BSS2. Suitable resources to illustrate include, among other examples, transmit power, timing, or frequency allocation for latency-sensitive traffic. In some implementations, access points AP1 and AP2 may coordinate the transmit times of wireless communications in BSS1 and BSS2 during r-TWT SP1 and r-TWT SP2. In such implementations, the timing of latency-sensitive traffic in BSS1 may be orthogonal to the timing of latency-sensitive traffic in BSS2. For example, access points AP1 and AP2 may initiate a TXOP during r-TWT SP1 and r-TWT SP2 by sending a multi-user (MU) request-to-send (RTS) frame requesting simultaneous clear-to-send (CTS) frames from multiple STAs, thereby protecting the TXOP from interference by STAs in the OBSS.

[0072]

[0093] In some other implementations, access points AP1 and AP2 may coordinate the frequency resources (such as RUs) allocated to wireless communications in BSS1 and BSS2 during r-TWT SP1 and r-TWT SP2. In such implementations, the frequency resources allocated to latency-sensitive traffic in BSS1 may be orthogonal to the frequency resources allocated to latency-sensitive traffic in BSS2. For example, before (or during) r-TWT SP1 and r-TWT SP2, access points AP1 and AP2 may exchange coordination information indicating the allocation of frequency resources for wireless communications in at least one of BSS1 or BSS2 (such as in coordinated OFDMA (C-OFDMA) operation). Access points AP1 and AP2 may use the exchange of coordination information to propose, accept, or negotiate orthogonal frequency resources to be allocated to wireless communications in BSS1 and BSS2 during overlapping service periods r-TWT SP1 and r-TWT SP2.

[0073]

[0094] Furthermore, in some implementations, access points AP1 and AP2 can coordinate the transmit power for wireless communication in BSS1 and BSS2 within r-TWT SP1 and r-TWT SP2. In such implementations, the transmit power for latency-sensitive traffic in BSS1 can be appropriately low so as not to interfere with latency-sensitive traffic in BSS2, and the transmit power for latency-sensitive traffic in BSS2 can be appropriately low so as not to interfere with latency-sensitive traffic in BSS1. For example, before (or during) r-TWT SP1 and r-TWT SP2, access points AP1 and AP2 can exchange coordinated information indicating the transmit power to be used for wireless communication in at least one of BSS1 or BSS2 (according to coordinated spatial reuse (C-SR) operation, etc.). Access points AP1 and AP2 may utilize coordinated information exchange to propose, accept, or negotiate the transmit power to be used for wireless communication in BSS1 and BSS2 during overlapping service periods r-TWT SP1 and r-TWT SP2.

[0074]

[0095] Aspects of this disclosure recognize that STAs located closer to the AP (such as STA701 and 704 in Figure 7) are more susceptible to interference from OBSS than STAs located further away from the AP. Therefore, reducing the transmit power of wireless communications associated with such STAs can effectively suppress interference between OBSS in overlapping r-TWT SPs. In some embodiments, each of access points AP1, AP2, and AP3 may assign or allocate low-latency STAs to service periods r-TWT SP1, r-TWT SP2, and r-TWT SP3, respectively, based on r-TWT scheduling information carried in beacons or other management frames transmitted before (or during) one or more r-TWT SPs. In some implementations, r-TWT scheduling information associated with a particular r-TWT SP may assign one or more STAs to that r-TWT SP. In some other implementations, an STA may request to join a particular r-TWT SP in response to receiving r-TWT scheduling information associated with that r-TWT SP.

[0075]

[0096] As shown in Figure 9, at time t0, access point AP1 transmits a beacon frame 901 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP1. For example, referring to Figure 7, beacon frame 901 may be transmitted by AP711 and may assign or allocate STA701 to r-TWT SP1. At time t0, access point AP2 transmits a beacon frame 902 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP2. For example, referring to Figure 7, beacon frame 902 may be transmitted by AP712 and may assign or allocate STA704 to r-TWT SP2. At time t0, access point AP3 transmits a beacon frame 903 carrying r-TWT schedule information indicating the schedule associated with r-TWT SP3. For example, referring to Figure 7, beacon frame 903 may assign or allocate STA706 to r-TWT SP3. Figure 9 shows beacon frames 901-903 transmitted at the same time (t0), but in some other implementations, one or more of the beacon frames 901-903 may be transmitted at different times.

[0076]

[0097] In some implementations, beacon frames 901 and 902 broadcast by cooperative access points AP1 and AP2, respectively, may further carry cooperative r-TWT signaling information. As described above, the cooperative r-TWT signaling information may indicate r-TWT SP schedules associated with one or more OBSSs. For example, beacon frame 901 may carry cooperative r-TWT signaling information indicating a schedule for one or more of the service periods r-TWT SP2 or r-TWT SP3, and beacon frame 902 may carry cooperative r-TWT signaling information indicating a schedule for one or more of the service periods r-TWT SP1 or r-TWT SP3. More specifically, a schedule for r-TWT SP1 may indicate that r-TWT SP1 occurs from time t1 to t2, a schedule for r-TWT SP2 may indicate that r-TWT SP2 also occurs from time t1 to t2, and a schedule for r-TWT SP3 may indicate that r-TWT SP3 occurs from time t2 to t3.

[0077]

[0098] Figure 10A shows sequence diagram 1000 illustrating exemplary message exchange between OBSSs (BSS1 and BSS2) supporting r-TWT SP cooperative scheduling in several implementations. As shown in Figure 10A, BSS1 includes AP1001 and STA1003, and BSS2 includes AP1002 and STA1004. In some implementations, AP1001 and 1002 may each be examples of AP711 and 712 in Figure 7, STA1003 may be an example of either STA701 or 702, and STA1004 may be an example of any of STA703 to 705.

[0078]

[0099] In some embodiments, the network controller 1005 may coordinate the scheduling of r-TWT SPs for BSS1 and BSS2 so that latency-sensitive communications in BSS1 do not interfere with or conflict with latency-sensitive communications in BSS2. For example, the network controller 1005 may be coupled to or communicate with APs 1001 and 1002 via (wired or wireless) backhaul. In the example in Figure 10A, the network controller 1005 may schedule a first r-TWT SP for BSS1 (r-TWT SP1) and a second r-TWT SP for BSS2 (r-TWT SP2). In some implementations, r-TWT SP1 and r-TWT SP2 may be temporally orthogonal (as described with reference to Figure 8). In some other implementations, r-TWT SP1 and r-TWT SP2 may overlap in time (as described with reference to Figure 9). In this implementation configuration, the network controller 1005 can coordinate the allocation of resources (such as transmission power, timing, or frequency allocation) for wireless communication during overlapping service periods r-TWT SP1 and r-TWT SP2.

[0079]

[0100] The network controller 1005 communicates coordinated r-TWT signaling information to AP1001 and AP1002, respectively. More specifically, the coordinated r-TWT signaling information provided to AP1001 may include a schedule for r-TWT SP1, and the coordinated r-TWT signaling information provided to AP1002 may include a schedule for r-TWT SP2. In some implementations, the coordinated r-TWT signaling information provided to AP1001 may also include a schedule for r-TWT SP2, and the coordinated r-TWT signaling information provided to AP1002 may also include a schedule for r-TWT SP1.

[0080]

[0101] AP1001 schedules r-TWT SP1 based on the received cooperative r-TWT signaling information and transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP1. For example, r-TWT schedule information may be carried in a broadcast r-TWT information element (IE) included in a beacon frame or other management frame transmitted by AP1001 to STA1003 (according to existing versions of the IEEE 802.11 standard, for example). In response to receiving r-TWT schedule information from AP1001, STA1003 joins r-TWT SP1 (as a member). In some implementations, r-TWT schedule information may assign STA1003 to r-TWT SP1. In some other implementations, STA1003 may request to join r-TWT SP1 based on the received r-TWT schedule information. Subsequently, AP1001 and STA1003 can exchange latency-sensitive traffic during r-TWT SP1.

[0081]

[0102] In some embodiments, AP1001 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP2. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1001 to STA1003. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1001 to STA1003. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1003 may schedule its communications (during r-TWT SP2) to avoid interference with latency-sensitive traffic in BSS2 based on the coordinated r-TWT signaling information.

[0082]

[0103] AP1002 schedules r-TWT SP2 based on the received coordinated r-TWT signaling information and transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP2. For example, r-TWT schedule information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame sent by AP1002 to STA1004 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving r-TWT schedule information from AP1002, STA1004 joins r-TWT SP2 (as a member). In some implementations, r-TWT schedule information may assign STA1004 to r-TWT SP2. In some other implementations, STA1004 may request to join r-TWT SP2 based on the received r-TWT schedule information. AP1002 and STA1004 can then exchange latency-sensitive traffic during r-TWT SP2.

[0083]

[0104] In some embodiments, AP1002 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP1. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1002 to STA1004. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1002 to STA1004. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1004 may schedule its communications (during r-TWT SP1) to avoid interference with latency-sensitive traffic in BSS1 based on the coordinated r-TWT signaling information.

[0084]

[0105] Figure 10B shows a sequence diagram 1010 illustrating exemplary message exchange between OBSSs (BSS1 and BSS2) supporting the cooperative scheduling of r-TWT SPs in several implementation configurations. As shown in Figure 10B, BSS1 includes AP1011 and STA1013, and BSS2 includes AP1012 and STA1014. In some implementation configurations, AP1011 and 1012 may each be examples of AP711 and 712 in Figure 7, STA1013 may be an example of either STA701 or 702, and STA1014 may be an example of any of STA703 to 705.

[0085]

[0106] In some embodiments, AP1011 can coordinate the scheduling of r-TWT SPs for BSS1 and BSS2 so that latency-sensitive communications in BSS1 do not interfere with or collide with latency-sensitive communications in BSS2. In the example in Figure 10B, AP1011 can schedule a first r-TWT SP (r-TWT SP1) for BSS1 and a second r-TWT SP (r-TWT SP2) for BSS2. In some implementations, r-TWT SP1 and r-TWT SP2 may be temporally orthogonal (as described with reference to Figure 8). In some other implementations, r-TWT SP1 and r-TWT SP2 may overlap in time (as described with reference to Figure 9). In such implementations, AP1011 can coordinate the allocation of resources (such as transmit power, timing, or frequency allocation) for wireless communications during the overlapping service periods of r-TWT SP1 and r-TWT SP2.

[0086]

[0107] AP1011 communicates coordinated r-TWT signaling information to AP1012. In some implementations, AP1011 may communicate coordinated r-TWT signaling information to AP1012 via (wired or wireless) backhaul. In some other implementations, AP1011 may send coordinated r-TWT signaling information to AP1012 via one or more wireless communication packets or frames (such as a new action frame or an enhanced broadcast services (EBCS) frame). More specifically, the coordinated r-TWT signaling information may include a schedule for r-TWT SP2. In some implementations, the coordinated r-TWT signaling information may also include a schedule for r-TWT SP1.

[0087]

[0108] AP1011 further transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP1. For example, r-TWT schedule information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1011 to STA1013 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving the r-TWT schedule information from AP1011, STA1013 joins r-TWT SP1 (as a member). In some implementations, the r-TWT schedule information may assign STA1013 to r-TWT SP1. In some other implementations, STA1013 may request to join r-TWT SP1 based on the received r-TWT schedule information. AP1011 and STA1013 can then exchange latency-sensitive traffic in r-TWT SP1.

[0088]

[0109] In some embodiments, AP1011 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP2. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1011 to STA1013. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1011 to STA1013. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1013 may schedule its communications (during r-TWT SP2) to avoid interference with latency-sensitive traffic in BSS2 based on the coordinated r-TWT signaling information.

[0089]

[0110] AP1012 schedules the r-TWT SP2 based on the received coordinated r-TWT signaling information and transmits or broadcasts r-TWT scheduling information indicating the schedule for the r-TWT SP2. For example, the r-TWT scheduling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1012 to STA1014 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving the r-TWT scheduling information from AP1012, STA1014 joins the r-TWT SP2 (as a member). In some implementations, the r-TWT scheduling information may assign STA1014 to the r-TWT SP2. In some other implementations, STA1014 may request to join the r-TWT SP2 based on the received r-TWT scheduling information. AP1012 and STA1014 can then exchange latency-sensitive traffic during the r-TWT SP2.

[0090]

[0111] In some embodiments, AP1012 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP1. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1012 to STA1014. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1012 to STA1014. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1014 may schedule its communications (during r-TWT SP1) to avoid interference with latency-sensitive traffic in BSS1 based on the coordinated r-TWT signaling information.

[0091]

[0112] Figure 11A shows sequence diagram 1100 illustrating exemplary message exchange between OBSSs (BSS1 and BSS2) supporting r-TWT SP cooperative scheduling in several implementations. As shown in Figure 11A, BSS1 includes AP1101 and STA1103, and BSS2 includes AP1102 and STA1104. In some implementations, AP1101 and 1102 may each be examples of AP711 and 712 in Figure 7, STA1103 may be an example of either STA701 or 702, and STA1104 may be an example of any of STA703 to 705.

[0092]

[0113] In some embodiments, AP1101 and 1102 may coordinate the scheduling of r-TWT SPs in BSS1 and BSS2 in a distributed manner so that latency-sensitive communications in BSS1 do not interfere with or collide with latency-sensitive communications in BSS2. In the example in Figure 11A, AP1101 schedules a first r-TWT SP (r-TWT SP1) for BSS1 and communicates coordinated r-TWT signaling information indicating the schedule for r-TWT SP1 to AP1102. In some implementations, AP1101 may communicate coordinated r-TWT signaling information to AP1102 via (wired or wireless) backhaul. In some other implementations, AP1101 may transmit coordinated r-TWT signaling information to AP1102 via one or more wireless communication packets or frames (such as a new action frame or an enhanced broadcast service (EBCS) frame).

[0093]

[0114] AP1102 schedules a second r-TWT SP (r-TWT SP2) for BSS2 based on the received coordinated r-TWT signaling information. More specifically, AP1102 may coordinate its schedule for r-TWT SP2 based on its schedule for r-TWT SP1. In some implementations, AP1102 may schedule r-TWT SP2 to be temporally orthogonal to r-TWT SP1 (as described with reference to Figure 8). In some other implementations, AP1102 may schedule r-TWT SP2 to overlap in time with r-TWT SP1 (as described with reference to Figure 9). In such implementations, access points AP1101 and 1102 may further coordinate the allocation of resources (such as transmit power, timing, or frequency allocation) for wireless communication during the overlapping service periods of r-TWT SP1 and r-TWT SP2.

[0094]

[0115] In some implementations, AP1102 may negotiate with AP1101 to schedule r-TWT SP2 based on coordinated r-TWT signaling information received from AP1101. For example, AP1102 may determine that the intended schedule for r-TWT SP1 does not allow for an appropriate schedule to be allocated to r-TWT SP2. Therefore, AP1102 may reject one or more aspects of the intended schedule for r-TWT SP1 (such as the intended allocation of transmit power or resources). Similarly, AP1101 may negotiate with AP1102 to schedule r-TWT SP1. As a result of the negotiation process, AP1101 and AP1102 may coordinate their schedules for r-TWT SP1 and r-TWT SP2, respectively, in a manner suitable for latency-sensitive traffic in BSS1 and BSS2.

[0095]

[0116] AP1101 further transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP1. For example, r-TWT schedule information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1101 to STA1103 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving r-TWT schedule information from AP1101, STA1103 joins r-TWT SP1 (as a member). In some implementations, r-TWT schedule information may assign STA1103 to r-TWT SP1. In some other implementations, STA1103 may request to join r-TWT SP1 based on the received r-TWT schedule information. AP1101 and STA1103 can then exchange latency-sensitive traffic in r-TWT SP1.

[0096]

[0117] In some embodiments, AP1101 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP2. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1101 to STA1103. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1101 to STA1103. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1103 may schedule its communications (during r-TWT SP2) to avoid interference with latency-sensitive traffic in BSS2 based on the coordinated r-TWT signaling information.

[0097]

[0118] AP1102 further transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP2. For example, r-TWT schedule information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1102 to STA1104 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving the r-TWT schedule information from AP1102, STA1104 joins r-TWT SP2 (as a member). In some implementations, the r-TWT schedule information may assign STA1104 to r-TWT SP2. In some other implementations, STA1104 may request to join r-TWT SP2 based on the received r-TWT schedule information. AP1102 and STA1104 can then exchange latency-sensitive traffic within r-TWT SP2.

[0098]

[0119] In some embodiments, AP1102 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP1. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1102 to STA1104. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1102 to STA1104. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1104 may schedule its communications (during r-TWT SP1) to avoid interference with latency-sensitive traffic in BSS1 based on the coordinated r-TWT signaling information.

[0099]

[0120] Figure 11B shows sequence diagram 1110 illustrating exemplary message exchange between OBSSs (BSS1 and BSS2) supporting r-TWT SP cooperative scheduling in several implementations. As shown in Figure 11B, BSS1 includes AP1111 and STA1113, and BSS2 includes AP1112 and STA1114. In some implementations, AP1111 and 1112 may each be examples of AP711 and 712 in Figure 7, STA1113 may be an example of either STA701 or 702, and STA1114 may be an example of any of STA703 to 705.

[0100]

[0121] In some embodiments, AP1111 and 1112 may coordinate the scheduling of r-TWT SPs for BSS1 and BSS2 in a distributed manner so that latency-sensitive communications in BSS1 do not interfere with or collide with latency-sensitive communications in BSS2. In the example in Figure 11B, AP1111 schedules a first r-TWT SP (r-TWT SP1) for BSS1 and transmits or broadcasts r-TWT scheduling information indicating the schedule for r-TWT SP1. For example, the r-TWT scheduling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1111 to STA1113 (according to an existing version of the IEEE 802.11 standard, for example). In response to receiving the r-TWT scheduling information from AP1111, STA1113 joins r-TWT SP1 (as a member). In some implementations, r-TWT schedule information may assign STA1113 to r-TWT SP1. In some other implementations, STA1113 may request to join r-TWT SP1 based on the received r-TWT schedule information. AP1111 and STA1113 can then exchange latency-sensitive traffic within r-TWT SP1.

[0101]

[0122] AP1112 obtains r-TWT schedule information from AP1111 and schedules a second r-TWT SP (r-TWT SP2) for BSS2 based on the obtained r-TWT schedule information. For example, AP1112 may obtain r-TWT schedule information by intercepting one or more frames transmitted by AP1111 to STA1113 (or other STAs in BSS1). As a result, AP1112 may coordinate its schedule for r-TWT SP2 based on its schedule for r-TWT SP1. In some implementations, AP1112 may schedule r-TWT SP2 to be temporally orthogonal to r-TWT SP1 (as described with reference to Figure 8). In some other implementations, AP1112 may schedule r-TWT SP2 to be temporally overlapping with r-TWT SP1 (as described with reference to Figure 9). In this implementation configuration, access points AP1111 and 1112 can further coordinate the allocation of resources (such as transmit power, timing, or frequency allocation) for wireless communication during overlapping service periods r-TWT SP1 and r-TWT SP2.

[0102]

[0123] AP1112 further transmits or broadcasts r-TWT schedule information indicating the schedule for r-TWT SP2. For example, r-TWT schedule information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1112 to STA1114 (according to existing versions of the IEEE 802.11 standard, etc.). In response to receiving the r-TWT schedule information from AP1112, STA1114 joins r-TWT SP2 (as a member). In some implementations, the r-TWT schedule information may assign STA1114 to r-TWT SP2. In some other implementations, STA1114 may request to join r-TWT SP2 based on the received r-TWT schedule information. AP1112 and STA1114 can then exchange latency-sensitive traffic within r-TWT SP2.

[0103]

[0124] In some embodiments, AP1112 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP1. In some implementations, the coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE included in a beacon frame or other management frame transmitted by AP1112 to STA1114. In some other implementations, the coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE in a beacon frame or other management frame transmitted by AP1112 to STA1114. Furthermore, in some implementations, the coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1114 may schedule its communications (during r-TWT SP1) to avoid interference with latency-sensitive traffic in BSS1 based on the coordinated r-TWT signaling information.

[0104]

[0125] In some embodiments, AP1111 may also transmit coordinated r-TWT signaling information indicating a schedule for r-TWT SP2. For example, AP1111 may obtain a schedule for r-TWT SP2 by intercepting one or more frames transmitted by AP1112 to STA1114 (or other STAs in BSS2). In some implementations, coordinated r-TWT signaling information may be carried in a broadcast r-TWT IE contained within a beacon frame or other management frame transmitted by AP1111 to STA1113. In some other implementations, coordinated r-TWT signaling information may be carried in a new coordinated r-TWT IE within a beacon frame or other management frame transmitted by AP1111 to STA1113. Furthermore, in some implementations, coordinated r-TWT signaling information may be carried in a new frame or packet (such as an MPDU or PPDU) designed for coordinated r-TWT signaling. As a result, STA1113 can schedule its communications based on coordinated r-TWT signaling information to avoid interfering with latency-sensitive traffic in BSS2 (during r-TWT SP2).

[0105]

[0126] Figure 12 shows an exemplary packet 1200 that can be used for coordinated r-TWT signaling between one or more APs and one or more STAs in several implementations. In the example in Figure 12, packet 1200 is illustrated as an MPDU frame. Referring to Figure 3, for example, packet 1200 could be an example of an MPDU frame 310. In some implementations, packet 1200 may be a management frame type (such as a beacon or probe response frame) as defined in existing versions of the IEEE 802.11 standard. In some other implementations, packet 1200 may be a new type of frame (such as an action frame or EBCS frame) designed for coordinated r-TWT signaling.

[0106]

[0127] In some embodiments, packet 1200 may be sent by the AP to one or more STAs associated with its BSS. In some implementations, packet 1200 may be used to assign STAs associated with one or more r-TWT SPs to be allocated to latency-sensitive communications in the current BSS. In some other implementations, packet 1200 may be used to prevent the associated STAs from interfering with latency-sensitive communications in one or more OBSSs. In some other embodiments, packet 1200 may be sent by the AP to other APs associated with one or more OBSSs. In some implementations, packet 1200 may be used to coordinate r-TWT SP scheduling with other APs. In some other implementations, packet 1200 may be used to prevent other APs from interfering with latency-sensitive communications in the current BSS.

[0107]

[0128] Packet 1200 includes a MAC header 1210, followed by a frame body 1220 and an FCS 1230. Although not shown for simplicity, the MAC header 1210 may include a frame control field, a duration field, a receiver address (RA) field, and a transmitter address (TA) field. The frame body 1220 includes one or more IEs that carry information about the r-TWT operation. In some implementations, the frame body 1220 may include a broadcast TWT element 1221 and a quiet element 1222. The broadcast TWT element 1221 includes several (N) restricted TWT parameter sets 1231(1) to 1231(N), each carrying information associated with its respective r-TWT SP. In some implementations, at least one of the restricted TWT parameter sets 1231(1) to 1231(N) is used to carry r-TWT schedule information 1224, and at least one of the restricted TWT parameter sets 1231(1) to 1231(N) is used to carry cooperative r-TWT signaling information 1225.

[0108]

[0129] In some implementations, r-TWT schedule information 1224 may be an example of any of the r-TWT schedule information described with reference to Figures 7 to 11B. More specifically, r-TWT schedule information 1224 may indicate the r-TWT SP schedule for the current BSS. In some implementations, cooperative r-TWT signaling information 1225 may be an example of any of the cooperative r-TWT signaling information described with reference to Figures 7 to 11B. More specifically, cooperative r-TWT signaling information 1225 may indicate the r-TWT SP schedule for the OBSS. The quiet element 1222 may carry information indicating one or more quiet durations (as specified in existing versions of the IEEE 802.11 standard). In some implementations, one or more quiet durations may span the durations of one or more r-TWT SPs allocated to the current BSS. In some other implementations, one or more quiet durations can span the durations of one or more r-TWT SPs allocated to the OBSS.

[0109]

[0130] In some implementations, the broadcast TWT element 1221 may conform to an existing broadcast TWT element format, such as that specified in the revised IEEE 802.11be standard. In such implementations, the cooperative r-TWT signaling information 1225 may be implemented using only minor modifications to the IEEE 802.11 standard. However, aspects of this disclosure recognize that each restricted TWT parameter set may contain information that is irrelevant to or unnecessary for cooperative r-TWT signaling (such as information used to set up or establish an r-TWT SP with one or more low-latency STAs). Therefore, in some implementations, the cooperative r-TWT signaling information 1225 may represent only a subset of the information carried in the restricted TWT parameter set.

[0110]

[0131] Figure 13 shows another exemplary packet 1300 that can be used for coordinated r-TWT signaling between one or more APs and one or more STAs in several implementations. In the example in Figure 13, packet 1300 is illustrated as an MPDU frame. Referring to Figure 3, for example, packet 1300 could be an example of an MPDU frame 310. In some implementations, packet 1300 may be a management frame type (such as a beacon or probe response frame) as defined in existing versions of the IEEE 802.11 standard. In some other implementations, packet 1300 may be a new type of frame (such as an action frame or EBCS frame) designed for coordinated r-TWT signaling.

[0111]

[0132] In some embodiments, packet 1300 may be sent by the AP to one or more STAs associated with its BSS. In some implementations, packet 1300 may be used to assign STAs associated with one or more r-TWT SPs to be allocated to latency-sensitive communications in the current BSS. In some other implementations, packet 1300 may be used to prevent the associated STAs from interfering with latency-sensitive communications in one or more OBSSs. In some other embodiments, packet 1300 may be sent by the AP to other APs associated with one or more OBSSs. In some implementations, packet 1300 may be used to coordinate r-TWT SP scheduling with other APs. In some other implementations, packet 1300 may be used to prevent other APs from interfering with latency-sensitive communications in the current BSS.

[0112]

[0133] Packet 1300 includes a MAC header 1310, followed by a frame body 1320 and an FCS 1330. Although not shown for simplicity, the MAC header 1310 may include a frame control field, a duration field, an RA field, and a TA field. The frame body 1320 includes one or more IEs that carry information about r-TWT operations. In some implementations, the frame body 1320 may include a broadcast TWT element 1321, a quiet element 1322, and a cooperative r-TWT element 1323. In the example in Figure 13, the broadcast TWT element 1321 carries r-TWT scheduling information 1324, and the cooperative r-TWT element 1323 carries cooperative r-TWT signaling information 1325.

[0113]

[0134] In some implementations, the r-TWT schedule information 1324 may be an example of any of the r-TWT schedule information described with reference to Figures 7 to 11B. More specifically, the r-TWT schedule information 1324 may indicate the r-TWT SP schedule for the current BSS. In some implementations, the cooperative r-TWT signaling information 1325 may be an example of any of the cooperative r-TWT signaling information described with reference to Figures 7 to 11B. More specifically, the cooperative r-TWT signaling information 1325 may indicate the r-TWT SP schedule for the OBSS. The quiet element 1322 may carry information indicating one or more quiet durations (as specified in existing versions of the IEEE 802.11 standard). In some implementations, one or more quiet durations may span the durations of one or more r-TWT SPs allocated to the current BSS. In some other implementations, one or more quiet durations can span the durations of one or more r-TWT SPs allocated to the OBSS.

[0114]

[0135] For simplicity, only one cooperative r-TWT element 1323 is shown in Figure 13, but in some other implementations, each packet 1300 may contain any number (N) cooperative r-TWT elements to carry cooperative r-TWT signaling information for N OBSSs. In some implementations, the cooperative r-TWT signaling information 1325 may contain only the set of parameters required for cooperative r-TWT signaling (or scheduling). For example, referring to Figure 12, the cooperative r-TWT signaling information 1325 may contain only a subset of the information carried in the restricted TWT parameter set 1223 (N). In some implementations, the cooperative r-TWT signaling information 1325 may contain one or more additional parameters not included in the restricted TWT parameter set 1223 (N). For example, the additional parameters may represent information specific to cooperative r-TWT signaling.

[0115]

[0136] As shown in Figure 13, the coordinated r-TWT signaling information 1325 may include TWT information indicating the time (relative to TBTT) for which the low-latency STA associated with the r-TWT SP must be awake, i.e., the nominal minimum TWT wake duration indicating the duration of the r-TWT SP (in wake duration units), the TWT wake interval indicating the average time between r-TWT SPs (which can be calculated using the TWT wake interval mantissa and TWT wake interval exponent), the wake duration units (μs or TU), the broadcast TWT ID used to identify the r-TWT SP, and broadcast TWT persistence information indicating the duration (in TBTT) for which the coordinated r-TWT signaling information 1325 is valid.

[0116]

[0137] In some implementations, the cooperative r-TWT signaling information 1325 includes trigger information indicating whether latency-sensitive communication in the r-TWT SP is trigger-based, non-trigger-based, or a hybrid thereof; a TID bitmap indicating one or more traffic identifiers (TIDs) supported by the r-TWT SP; a link ID bitmap indicating one or more communication links that may be used to communicate latency-sensitive data traffic in the r-TWT SP; an indication of the number of member STAs assigned to (or joined by) the r-TWT SP; a shared bit indicating whether the r-TWT SP may be shared by duplicate r-TWT SPs (e.g., multi-AP cooperation opportunities); an indication of whether the r-TWT SP is assigned to peer-to-peer (P2P) communication, infrastructure BSS (infrastructure) communication, or a hybrid thereof; SP type information indicating whether the cooperative r-TWT signaling information 1325 is related to the current BSS or OBSS; and r-TWT The r-TWT SP may further include SP status information indicating whether membership in the SP is full, TBTT information which may be used to coordinate TBTT timing or frequency between multiple APs, maximum TXOP duration information indicating the maximum duration which can be allocated to a TXOP during the r-TWT SP, and indications of one or more EDCA parameters supported by the r-TWT SP.

[0117]

[0138] In some embodiments, the parameters associated with the coordinated r-TWT signaling information 1325 may vary depending on whether the intended recipient of packet 1300 is an STA (associated with the current BSS) or an AP (associated with an OBSS). For example, one or more parameters (such as shared bits or TBTT information) may be omitted from the coordinated r-TWT signaling information 1325 provided to the STA in the current BSS in order to reduce the signaling overhead of packet 1300. Similarly, one or more parameters (such as a TID bitmap or SP status information) may be omitted from the coordinated r-TWT signaling information 1325 provided to APs in one or more OBSSs.

[0118]

[0139] Figure 14 shows a flowchart illustrating an exemplary process 1400 of wireless communication supporting r-TWT SP cooperative scheduling and signaling. In some implementations, process 1400 may be performed by an AP, such as one of AP102 or AP502 as described above with reference to Figures 1 and 5A, respectively, or by a wireless communication device operating within an AP.

[0119]

[0140] In some implementations, process 1400 begins in block 1402 by receiving coordinated r-TWT signaling information associated with a first r-TWT SP associated with the OBSS. In block 1404, process 1400 proceeds to transmit r-TWT scheduling information indicating a second r-TWT SP associated with a BSS associated with a wireless communication device, based on the coordinated r-TWT signaling information. In block 1406, process 1400 proceeds to communicate with one or more first STAs in the second r-TWT SP, based on the respective latency requirements of each of the one or more first STAs.

[0120]

[0141] In some embodiments, a first r-TWT SP may be temporally orthogonal to a second r-TWT SP. In some other embodiments, a first r-TWT may temporally overlap with a second r-TWT SP. In some implementations, a wireless communication device may communicate with one or more first STAs by transmitting MU-RTS frames to one or more first STAs. In some other implementations, the coordinating r-TWT signaling information may include shared SP information indicating multi-AP coordination opportunities associated with a first r-TWT SP. In such implementations, the wireless communication device may coordinate with APs associated with the OBSS based on the shared SP information so that communication with one or more first STAs occurs simultaneously with communication in the OBSS.

[0121]

[0142] In some implementations, a wireless communication device may coordinate with an AP by exchanging transmit power information indicating at least one of the transmit power associated with communication with one or more first STAs, or the transmit power associated with communication in the OBSS. In some other implementations, a wireless communication device may coordinate with an AP by exchanging frequency resource information indicating at least one of the frequency resource allocations for communication with one or more first STAs, or the frequency resource allocations for communication in the OBSS.

[0122]

[0143] In some embodiments, the coordinated r-TWT signaling information may indicate the allocation of resources for a second r-TWT SP. In some other embodiments, the coordinated r-TWT signaling information may indicate the allocation of resources for a first r-TWT SP. In some implementations, a wireless communication device may negotiate the allocation of resources for a second r-TWT SP with the AP associated with the OBSS based on the coordinated r-TWT signaling information. In some implementations, the coordinated r-TWT signaling information may be carried in one or more packets transmitted by the AP associated with the OBSS to the wireless communication device. In some other implementations, the coordinated r-TWT signaling information may be carried in one or more management frames transmitted by the AP associated with the OBSS to one or more STAs associated with the OBSS. In some implementations, the coordinated r-TWT signaling information may be received by an STA associated with a BSS that intercepts one or more management frames transmitted by the AP associated with the OBSS.

[0123]

[0144] In some embodiments, the wireless communication device may further transmit r-TWT coordination information indicating a first r-TWT SP associated with the OBSS. In some implementations, the r-TWT scheduling information and r-TWT coordination information may be carried in a broadcast TWT IE contained in one or more packets transmitted by the wireless communication device. In some other implementations, the r-TWT scheduling information and r-TWT coordination information may be carried in a broadcast TWT IE and a coordinating r-TWT IE, respectively, contained in one or more packets transmitted by the wireless communication device, the coordinating r-TWT IE being distinct from the broadcast TWT IE.

[0124]

[0145] Figure 15A shows a flowchart illustrating an exemplary process 1500 for wireless communication supporting r-TWT SP cooperative scheduling and signaling. In some implementations, process 1500 may be performed by an AP, such as one of AP102 or AP502 as described above with reference to Figures 1 and 5A, respectively, or by a wireless communication device operating within an AP.

[0125]

[0146] In some implementations, process 1500 begins in block 1502 by transmitting first coordinated r-TWT signaling information indicating a first r-TWT SP associated with a first BSS. In block 1504, process 1500 proceeds to transmit second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP. In some embodiments, the first r-TWT SP may be temporally orthogonal to the second r-TWT SP.

[0126]

[0147] In some other embodiments, the first r-TWT SP may temporally overlap with the second r-TWT SP. In some implementations, the first coordinated r-TWT signaling information may indicate the transmit power associated with communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information may indicate the transmit power associated with communication in the second BSS in the second r-TWT SP. In some other implementations, the first coordinated r-TWT signaling information may indicate the allocation of a first frequency resource for communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information may indicate the allocation of a second frequency resource for communication in the second BSS in the second r-TWT SP. In such implementations, the first frequency resource may be orthogonal to the second frequency resource.

[0127]

[0148] In some implementations, the first and second coordinated r-TWT signaling information may be carried in a broadcast TWT IE contained within one or more packets transmitted by the wireless communication device. In some other implementations, the first and second coordinated r-TWT signaling information may be carried in the first and second coordinated r-TWT IEs, respectively, contained within one or more packets transmitted by the wireless communication device.

[0128]

[0149] Figure 15B shows a flowchart illustrating an exemplary process 1510 for wireless communication supporting r-TWT SP cooperative scheduling and signaling. In some implementations, process 1510 may be performed by an AP, such as one of AP102 or AP502 as described above with reference to Figures 1 and 5A, respectively, or by a wireless communication device operating within an AP.

[0129]

[0150] For example, referring to Figure 15A, process 1510 may begin in block 1512 after the transmission of the first coordinated r-TWT signaling information in block 1502 and after the transmission of the second coordinated r-TWT signaling information in block 1504. In some implementations, process 1510 begins in block 1512 by transmitting r-TWT scheduling information indicating a third r-TWT SP associated with a third BSS associated with a wireless communication device, based on the first r-TWT SP and the second r-TWT SP. In block 1514, process 1510 proceeds to communicate with one or more STAs during the third r-TWT SP, based on the respective latency requirements of each of the one or more STAs.

[0130]

[0151] Figure 16 shows block diagrams of exemplary wireless communication device 1600 in several implementation forms. In some implementation forms, the wireless communication device 1600 is configured to perform process 1400 as described above with reference to Figure 14. The wireless communication device 1600 may be an exemplary implementation of the wireless communication device 400 as described above with reference to Figure 4. For example, the wireless communication device 1600 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem).

[0131]

[0152] The wireless communication device 1600 includes a receiving component 1610, a communication manager 1620, and a transmitting component 1630. The communication manager 1620 further includes an r-TWT coordinating component 1622, an r-TWT scheduling component 1624, and an r-TWT communication component 1626. One or more parts of components 1622, 1624, and 1626 may be implemented at least partially in hardware or firmware. In some implementations, at least some of components 1622, 1624, or 1626 are implemented at least partially as software stored in memory (such as memory 408). For example, one or more parts of components 1622, 1624, and 1626 may be implemented as non-transient instructions (or "code") that can be executed by a processor (such as processor 406) to perform the function or operation of each component.

[0132]

[0153] The receiving component 1610 is configured to receive RX signals from one or more other wireless communication devices via a wireless channel. The transmitting component 1630 is configured to transmit TX signals to one or more other wireless communication devices via a wireless channel. The communication manager 1620 is configured to control or manage communication with one or more other wireless communication devices. In some implementations, the r-TWT coordination component 1622 may receive coordinated r-TWT signaling information associated with a first r-TWT SP associated with an OBSS, the r-TWT scheduling component 1624 may transmit r-TWT scheduling information indicating a second r-TWT SP associated with a BSS associated with a wireless communication device based on the coordinated r-TWT signaling information, and the r-TWT communication component 1626 may communicate with one or more STAs during the second r-TWT SP based on the respective latency requirements of each of the one or more STAs.

[0133]

[0154] Figure 17 shows block diagrams of exemplary wireless communication device 1700 in several implementation configurations. In some implementation configurations, the wireless communication device 1700 is configured to perform process 1500 as described above with reference to Figure 15. The wireless communication device 1700 may be an exemplary implementation of the wireless communication device 400 as described above with reference to Figure 4. For example, the wireless communication device 1700 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem).

[0134]

[0155] The wireless communication device 1700 includes a receiving component 1710, a communication manager 1720, and a transmitting component 1730. The communication manager 1720 further includes a cooperative r-TWT scheduling component 1722. Parts of the cooperative r-TWT scheduling component 1722 can be implemented in hardware or firmware, at least in part. In some implementations, the cooperative r-TWT scheduling component 1722 is implemented, at least in part, as software stored in memory (such as memory 408). For example, parts of the cooperative r-TWT scheduling component 1722 can be implemented as non-transient instructions (or "code") that can be executed by a processor (such as processor 406) to perform the functions or operations of each component.

[0135]

[0156] The receiving component 1710 is configured to receive RX signals from one or more other wireless communication devices via a wireless channel. The transmitting component 1730 is configured to transmit TX signals to one or more other wireless communication devices via a wireless channel. The communication manager 1720 is configured to control or manage communication with one or more other wireless communication devices. In some implementations, the cooperative r-TWT scheduling component 1722 may transmit first cooperative r-TWT signaling information indicating a first r-TWT SP associated with a first BSS, and may further transmit second cooperative r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP.

[0136]

[0157] Implementation examples are described in the following numbered clauses.

[0137] Article 1 A method of wireless communication using a wireless communication device, Receiving Coordinated Limited Target Wake Time (r-TWT) signaling information associated with the first r-TWT service period (SP) associated with the overlapping basic service set (OBSS), Based on coordinated r-TWT signaling information, transmit r-TWT schedule information indicating a second r-TWT SP associated with the Basic Service Set (BSS) associated with the wireless communication device, A method comprising communicating with one or more first wireless stations (STAs) during a second r-TWT SP based on the respective latency requirements of one or more first STAs.

[0138] Clause 2 The method according to Clause 1, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP.

[0139] Clause 3 The method according to Clause 1, wherein the first r-TWT overlaps in time with the second r-TWT SP.

[0140] Clause 4 Communicating with one or more First STAs, The method described in either of Clauses 1 or 3, which includes sending a Multi-User Send Request (MU-RTS) frame to one or more first STAs.

[0141] Clause 5 The method described in either Clause 1 or 3, wherein the coordinated r-TWT signaling information includes shared SP information indicating a multiple access point (multi-AP) coordination opportunity associated with a first r-TWT SP.

[0142] Clause 6 Communicating with one or more First STAs, The method described in any one of Clauses 1, 3, or 5, which includes coordinating with an access point (AP) associated with the OBSS based on shared SP information, so that communication with one or more first STAs occurs simultaneously with communication in the OBSS.

[0143] To coordinate with Article 7 AP, The method of any one of Clauses 1, 3, 5, or 6, comprising exchanging with the AP transmit power information indicating at least one of the transmit powers associated with communication with one or more first STAs, or the transmit powers associated with communication in OBSS.

[0144] To cooperate with Article 8 AP, The method described in any one of Clauses 1, 3, 5, or 6, comprising exchanging frequency resource information with the AP indicating at least one of the following: an allocation of frequency resources for communication with one or more first STAs, or an allocation of frequency resources for communication in OBSS.

[0145] Clause 9 The method described in any one of Clauses 1 to 8, wherein the coordinated r-TWT signaling information indicates the allocation of resources for a second r-TWT SP.

[0146] Clause 10 The method described in any one of Clauses 1 to 8, wherein the coordinated r-TWT signaling information indicates the allocation of resources for the first r-TWT SP.

[0147] Clause 11 further includes negotiating resource allocation for a second r-TWT SP with the AP associated with OBSS based on coordinated r-TWT signaling information, The method described in any one of the clauses 1 to 8 or 10.

[0148] Clause 12 The method according to any one of Clauses 1 to 8 or 10, wherein coordinated r-TWT signaling information is carried in one or more packets transmitted to a wireless communication device by an AP associated with the OBSS.

[0149] The method described in any one of the clauses 1 to 8 or 10, wherein coordinated r-TWT signaling information is carried in one or more management frames transmitted by an AP associated with the OBSS to one or more STAs associated with the OBSS.

[0150] Clause 14 The method described in any one of Clauses 1 to 8 or 10, wherein coordinated r-TWT signaling information is received by an STA associated with a BSS that intercepts one or more management frames transmitted by an AP associated with an OBSS.

[0151] Clause 15 further includes transmitting r-TWT coordination information indicating the first r-TWT SP associated with OBSS, The method described in any one of the clauses 1 to 14.

[0152] The method according to any one of the clauses 1 to 15, wherein r-TWT scheduling information and r-TWT coordination information are carried in a broadcast target wake time (TWT) information element (IE) contained in one or more packets transmitted by a wireless communication device.

[0153] The method according to any one of the Clauses 1 to 15, wherein the r-TWT scheduling information and the r-TWT coordination information are carried in a broadcast TWT IE and a coordination r-TWT IE, respectively, which are contained in one or more packets transmitted by a wireless communication device, and the coordination r-TWT IE is different from the broadcast TWT IE.

[0154] Article 18 At least one processor, The present invention includes at least one memory communicatively coupled to at least one processor, which stores processor-readable code configured to perform, when executed by at least one processor, one or more of the methods described in any one of the clauses 1 to 17, Wireless communication device.

[0155] Article 19 A method of wireless communication performed by a wireless communication device, Transmitting first Cooperatively Limited Target Wake Time (r-TWT) signaling information indicating a first r-TWT service period (SP) associated with a first Basic Service Set (BSS), A method comprising transmitting a second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on a first r-TWT SP.

[0156] Clause 20 The method according to Clause 19, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP.

[0157] Clause 21 The method according to Clause 19, wherein the first r-TWT SP overlaps in time with the second r-TWT SP.

[0158] Clause 22 The method according to either one of Clauses 19 or 21, wherein the first coordinated r-TWT signaling information indicates the transmit power associated with the communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information indicates the transmit power associated with the communication in the second BSS in the second r-TWT SP.

[0159] The method according to any one of the provisions of Clause 23, the first coordinated r-TWT signaling information indicates the allocation of a first frequency resource for communication in a first BSS in a first r-TWT SP, and the second coordinated r-TWT signaling information indicates the allocation of a second frequency resource for communication in a second BSS in a second r-TWT SP.

[0160] Clause 24 The method described in any one of Clauses 19 or 21 to 23, wherein the first frequency resource is orthogonal to the second frequency resource.

[0161] The method according to any one of the Clauses 19 to 24, wherein the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information are carried in a broadcast target wake time (TWT) information element (IE) contained in one or more packets transmitted by a wireless communication device.

[0162] The method according to any one of the Clauses 19 to 24, wherein the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information are carried in the first and second coordinated r-TWT IEs, respectively, which are contained in one or more packets transmitted by a wireless communication device.

[0163] Article 27 Transmit r-TWT schedule information indicating a third r-TWT SP associated with a third BSS associated with a wireless communication device, based on a first r-TWT SP and a second r-TWT SP. This further includes communicating with one or more wireless stations (STAs) during a third r-TWT SP, based on the respective latency requirements of each of the STAs. The method described in any one of the clauses 19 to 26.

[0164] Article 28 At least one processor, The at least one memory, communicatively coupled to at least one processor, which stores processor-readable code configured, when executed by at least one processor, to perform one or more of the methods described in any one of the clauses 19 to 27, Wireless communication device.

[0165]

[0158] As used herein, any phrase referring to “at least one of” or “one or more of” the list of items means any combination of those items that contains a single element. For example, “at least one of a, b, or c” is intended to encompass the possibilities of a only, b only, c only, a and b, a and c, b and c, and a, b and c.

[0166]

[0159] The various exemplary components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described herein with respect to the implementation forms disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware, or software, including the structures and their structural equivalents disclosed herein. The compatibility of hardware, firmware, and software is described conceptually in terms of functionality and is shown above for the various exemplary components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0167]

[0160] Various modifications of the implementations described herein may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Accordingly, the claims should not be limited to the implementations shown herein, but should be given the broadest scope consistent with this disclosure, the principles disclosed herein, and novel features.

[0168]

[0161] In addition, the various features described herein in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, the various features described in the context of a single implementation may also be implemented separately in multiple implementations or in any preferred partial combination. Thus, features are described above as working in a particular combination and may even be initially claimed as such, but in some cases one or more features may be removed from the claimed combination, and the claimed combination may cover a partial combination or a variation of a partial combination.

[0169]

[0162] Similarly, while operations are illustrated in a specific order in the diagrams, this should not be understood as requiring that such operations be performed in a specific or sequential order shown, or that all shown operations be performed, in order to achieve the desired result. Furthermore, the diagrams may schematically illustrate another exemplary process in the form of a flowchart or flow diagram. However, other operations not illustrated may be incorporated into the schematically illustrated exemplary process. For example, one or more additional operations may be performed before, after, simultaneously with, or in between any of the operations shown. In some situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementation forms described above should not be understood as requiring such separation in all implementation forms, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged in multiple software products. The invention described in the original claims of this application is listed below. [C1] A method for wireless communication by a wireless communication device, Receiving coordinated r-TWT signaling information associated with the first limited target wake time (r-TWT) service period (SP) associated with the overlapping basic service set (OBSS), Based on the aforementioned coordinated r-TWT signaling information, transmit r-TWT schedule information indicating a second r-TWT SP associated with the basic service set (BSS) associated with the wireless communication device, A method comprising communicating with one or more first wireless stations (STAs) during the second r-TWT SP based on the respective latency requirements of each of the first STAs. [C2] The method according to C1, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP. [C3] The method according to C1, wherein the first r-TWT overlaps in time with the second r-TWT SP. [C4] Communicating with one or more of the first STAs, The method of C3, comprising transmitting a Multi-User Send Request (MU-RTS) frame to one or more first STAs. [C5] The method according to C3, wherein the cooperative r-TWT signaling information includes shared SP information indicating a multiple access point (multi-AP) cooperation opportunity associated with the first r-TWT SP. [C6] Communicating with one or more of the first STAs, The method of C5, comprising coordinating with an access point (AP) associated with the OBSS based on the shared SP information, such that the communication with the one or more first STAs takes place simultaneously with the communication in the OBSS. [C7] The AP and the cooperation described above The method of C6, comprising exchanging with the AP transmit power information indicating at least one of the transmit powers associated with the communication with the one or more first STAs, or the transmit powers associated with the communication in the OBSS. [C8] The AP and the cooperation described above The method of C6, comprising exchanging frequency resource information with the AP indicating at least one of the following: an allocation of frequency resources for the communication with one or more first STAs, or an allocation of frequency resources for the communication in the OBSS. [C9] The method according to C1, wherein the cooperative r-TWT signaling information indicates the allocation of resources for the second r-TWT SP. [C10] The method according to C1, wherein the cooperative r-TWT signaling information indicates the allocation of resources for the first r-TWT SP. [C11] Further comprising negotiating the allocation of resources for the second r-TWT SP with the AP associated with the OBSS based on the coordinated r-TWT signaling information, Methods described in C10. [C12] The method of C10, wherein the coordinated r-TWT signaling information is carried in one or more packets transmitted to the wireless communication device by the AP associated with the OBSS. [C13] The method of C10, wherein the coordinated r-TWT signaling information is carried in one or more management frames transmitted by the AP associated with the OBSS to one or more STAs associated with the OBSS. [C14] The method of C13, wherein the coordinated r-TWT signaling information is received from an STA associated with the BSS that intercepts the one or more management frames transmitted by the AP associated with the OBSS. [C15] Further comprising transmitting r-TWT coordination information indicating the first r-TWT SP associated with the OBSS, The method described in C14. [C16] The method of C15, wherein the r-TWT schedule information and the r-TWT coordination information are carried in a broadcast target wake time (TWT) information element (IE) included in one or more packets transmitted by the wireless communication device. [C17] The method according to C15, wherein the r-TWT schedule information and the r-TWT coordination information are carried in a broadcast TWT IE and a coordination r-TWT IE, respectively, which are contained in one or more packets transmitted by the wireless communication device, and the coordination r-TWT IE is different from the broadcast TWT IE. [C18] At least one processor, At least one memory that is communicatively coupled to the at least one processor, and which is executed by the at least one processor, The system receives Coordinated Limited Target Wake Time (r-TWT) signaling information associated with the first r-TWT service period (SP) associated with the overlapping basic service set (OBSS), Based on the aforementioned coordinated r-TWT signaling information, r-TWT schedule information indicating a second r-TWT SP associated with the basic service set (BSS) associated with the wireless communication device is transmitted. A memory that stores processor-readable code configured to communicate with the one or more first wireless stations (STAs) during the second r-TWT SP based on the respective latency requirements of each of the first STAs, Wireless communication device. [C19] The execution of the processor-readable code is A wireless communication device according to C18, further configured to transmit r-TWT coordination information indicating the first r-TWT SP associated with the OBSS. [C20] A method for wireless communication by a wireless communication device, Transmitting first Cooperatively Limited Target Wake Time (r-TWT) signaling information indicating a first r-TWT service period (SP) associated with a first Basic Service Set (BSS), A method comprising transmitting second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP. [C21] The method according to C20, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP. [C22] The method according to C20, wherein the first r-TWT SP overlaps in time with the second r-TWT SP. [C23] The method according to C22, wherein the first coordinated r-TWT signaling information indicates the transmit power associated with the communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information indicates the transmit power associated with the communication in the second BSS in the second r-TWT SP. [C24] The method according to C22, wherein the first coordinated r-TWT signaling information indicates the allocation of a first frequency resource for communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information indicates the allocation of a second frequency resource for communication in the second BSS in the second r-TWT SP. [C25] The method according to C24, wherein the first frequency resource is orthogonal to the second frequency resource. [C26] The method according to C20, wherein the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information are carried in a broadcast target wake time (TWT) information element (IE) contained in one or more packets transmitted by the wireless communication device. [C27] The method according to C20, wherein the first coordinated r-TWT signaling information and the second coordinated r-TWT signaling information are carried in first and second coordinated r-TWT IEs, each contained in one or more packets transmitted by the wireless communication device. [C28] Transmitting r-TWT schedule information indicating a third r-TWT SP associated with a third BSS associated with the wireless communication device, based on the first r-TWT SP and the second r-TWT SP, The third r-TWT SP further includes communicating with one or more wireless stations (STAs) during the third r-TWT SP based on the respective latency requirements of each of the STAs. Methods used in C20. [C29] At least one processor, At least one memory that is communicatively coupled to the at least one processor, and which is executed by the at least one processor, Transmit first Cooperatively Limited Target Wake Time (r-TWT) signaling information indicating a first r-TWT service period (SP) associated with a first basic service set (BSS), A wireless communication device comprising: a memory storing processor-readable code configured to transmit a second cooperative r-TWT signaling information indicating a second r-TWT SP associated with a second BSS based on the first r-TWT SP; [C30] The execution of the processor-readable code is Based on the first r-TWT SP and the second r-TWT SP, r-TWT schedule information indicating a third r-TWT SP associated with a third BSS associated with the wireless communication device is transmitted. A wireless communication device according to C29, configured to communicate with one or more wireless stations (STAs) during the third r-TWT SP based on the respective latency requirements of each of the STAs.

Claims

1. A method for wireless communication by a wireless communication device operating as an access point (AP) or operating within an AP, Receiving coordinated r-TWT signaling information associated with a first limited target wake time (r-TWT) service period (SP) associated with an overlapping basic service set (OBSS), Based on the aforementioned coordinated r-TWT signaling information, transmit r-TWT schedule information indicating a second r-TWT SP associated with the basic service set (BSS) associated with the wireless communication device, A method comprising communicating with one or more first wireless stations (STAs) during the second r-TWT SP based on the respective latency requirements of each of the first STAs.

2. The method according to claim 1, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP.

3. The first r-TWT overlaps in time with the second r-TWT SP, Communicating with the one or more first STAs is This includes transmitting a Multi-User Transmission Request (MU-RTS) frame to one or more of the first STAs, The cooperative r-TWT signaling information includes shared SP information indicating multiple access point (multi-AP) cooperation opportunities associated with the first r-TWT SP, Communicating with the one or more first STAs is The communication with one or more first STAs is performed simultaneously with the communication in the OBSS, including coordinating with an access point (AP) associated with the OBSS based on the shared SP information, The aforementioned AP and the aforementioned cooperation This includes exchanging with the AP transmission power information indicating at least one of the transmission powers associated with the communication with one or more first STAs, or the transmission powers associated with the communication in the OBSS, or The aforementioned AP and the aforementioned cooperation The method according to claim 1, comprising exchanging frequency resource information with the AP indicating at least one of the following: the allocation of frequency resources for communication with one or more first STAs, or the allocation of frequency resources for communication in the OBSS.

4. The method according to claim 1, wherein the coordinated r-TWT signaling information indicates the allocation of resources for the second r-TWT SP.

5. The method according to claim 1, wherein the coordinated r-TWT signaling information indicates the allocation of resources for the first r-TWT SP.

6. The further includes negotiating the allocation of resources for the second r-TWT SP with the AP associated with the OBSS, based on the aforementioned coordinated r-TWT signaling information. The method according to claim 5.

7. The method according to claim 5, wherein the coordinated r-TWT signaling information is carried in one or more packets transmitted to the wireless communication device by the AP associated with the OBSS.

8. The coordinated r-TWT signaling information is carried in one or more management frames transmitted by the AP associated with the OBSS to one or more STAs associated with the OBSS. The method according to claim 5, wherein the coordinated r-TWT signaling information is received from an STA associated with the BSS that intercepts the one or more management frames transmitted by the AP associated with the OBSS.

9. The further includes transmitting r-TWT coordination information indicating the first r-TWT SP associated with the OBSS, The r-TWT schedule information and the r-TWT coordination information are carried in a broadcast target wake time (TWT) information element (IE) included in one or more packets transmitted by the wireless communication device, or The r-TWT schedule information and the r-TWT coordination information are carried in a broadcast TWT IE and a coordinated r-TWT IE, respectively, which are included in one or more packets transmitted by the wireless communication device, and the coordinated r-TWT IE is different from the broadcast TWT IE. The method according to claim 1.

10. A wireless communication device that operates as an access point (AP) or within an AP, At least one processor, The system comprises at least one memory that is communicatively coupled to the at least one processor and stores processor-readable code, The processor-readable code, when executed by the at least one processor, The system receives coordinated limited target wake time (r-TWT) signaling information associated with the first r-TWT service period (SP) associated with the overlapping basic service set (OBSS), Based on the aforementioned coordinated r-TWT signaling information, r-TWT schedule information indicating a second r-TWT SP associated with the basic service set (BSS) associated with the wireless communication device is transmitted. A wireless communication device configured to communicate with one or more first wireless stations (STAs) during the second r-TWT SP, based on the respective latency requirements of each of the first STAs.

11. A method for wireless communication by a wireless communication device operating as an access point (AP) or operating within an AP, Transmitting first Coordinated Limited Target Wake Time (r-TWT) signaling information indicating a first r-TWT service period (SP) associated with a first Basic Service Set (BSS), A method comprising transmitting a second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS based on the first r-TWT SP.

12. The method according to claim 11, wherein the first r-TWT SP is temporally orthogonal to the second r-TWT SP.

13. The first r-TWT SP overlaps in time with the second r-TWT SP, The first coordinated r-TWT signaling information indicates the transmit power associated with the communication in the first BSS in the first r-TWT SP, and the second coordinated r-TWT signaling information indicates the transmit power associated with the communication in the second BSS in the second r-TWT SP, or The first coordinated r-TWT signaling information indicates the allocation of a first frequency resource for communication in the first BSS within the first r-TWT SP, and the second coordinated r-TWT signaling information indicates the allocation of a second frequency resource for communication in the second BSS within the second r-TWT SP. The method according to claim 11, wherein the first frequency resource is orthogonal to the second frequency resource.

14. A wireless communication device that operates as an access point (AP) or within an AP, At least one processor, The system comprises at least one memory that is communicatively coupled to the at least one processor and stores processor-readable code, The processor-readable code, when executed by the at least one processor, Transmit first Coordinated Limited Target Wake Time (r-TWT) signaling information indicating a first r-TWT service period (SP) associated with a first Basic Service Set (BSS), A wireless communication device configured to transmit a second coordinated r-TWT signaling information indicating a second r-TWT SP associated with a second BSS, based on the first r-TWT SP.

15. A computer program comprising instructions, When the instruction is executed by at least one processor of a wireless communication device operating as an access point (AP) as described in claim 10, or operating within an AP, the at least one processor is caused to perform the method according to any one of claims 1 to 9. A computer program which, when the instruction is executed by at least one processor of a wireless communication device operating as an access point (AP) as described in claim 14, or operating within an AP, causes the at least one processor to perform the method according to any one of claims 11 to 13.

Images