Multi-AP coordinated termination in wireless networks

Abstract

A first access point (AP) device in a wireless network is provided. The first AP includes a memory and a processor coupled to the memory. The first AP establishes a multi-AP coordination with the second AP, the multi-AP coordination comprising a set of protocols established between the first AP and the second AP. The first AP sends a first frame requesting termination of one or more protocols established between the first AP and the second AP.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to target wake-up time (TWT) operations in wireless communication systems, for example, but not limited to. Background Technology

[0002] Since the late 1990s, Wireless Local Area Network (WLAN) technology has evolved towards higher data rates and has seen continuous growth in various markets such as homes, businesses, and hotspots. WLAN allows devices to access the Internet in the 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz frequency bands. WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 standard family aims to improve speed and reliability and extend the operational range of wireless networks.

[0003] WLAN devices increasingly need to support a variety of latency-sensitive or real-time applications, such as augmented reality (AR), robotics, artificial intelligence (AI), cloud computing, and autonomous vehicles. To achieve the extremely low latency and extremely high throughput required for these applications, multi-link operation (MLO) has been proposed for WLANs. A WLAN is formed by WLAN devices within a limited area such as a home, school, apartment, or office. Each WLAN device can have one or more stations (STAs), such as access point (AP) STAs and non-access point (non-AP) STAs.

[0004] MLO enables non-AP multi-link devices (MLDs) to establish multiple links with AP MLDs. Each of these links can independently enable channel access and frame switching between the non-AP MLD and the AP MLD, which can reduce latency and increase throughput.

[0005] The descriptions set forth in the Background section should not be construed as prior art simply because they are set forth in the Background section. The Background section may describe aspects or embodiments of this disclosure. Summary of the Invention

[0006] Solution to the problem

[0007] One aspect of the present invention provides a first access point (AP) in a wireless network. The first AP includes a memory and a processor coupled to the memory. The processor is configured to establish multi-AP coordination with a second AP. The multi-AP coordination includes a set of protocols established between the first AP and the second AP. The processor is configured to send a first frame to the second AP, the first frame requesting termination of one or more protocols established between the first AP and the second AP.

[0008] In some embodiments, the processor is further configured to receive from the second AP a second frame indicating a response to the first frame, the second frame including a field indicating an acceptance, rejection, or alternative proposal for terminating at least one protocol between the first AP and the second AP.

[0009] In some embodiments, the first or second frame includes a field indicating whether the request is for a set of partially terminated protocols or a set of completely terminated protocols.

[0010] In some embodiments, the first or second frame includes a field indicating the type of multi-AP coordination.

[0011] In some embodiments, the first or second frame includes a field indicating an identifier of the protocol to be terminated.

[0012] In some embodiments, multi-AP coordination is multi-AP coordination based on target wake-up time (TWT).

[0013] In some embodiments, when a field indicates that a portion of the request is terminated, a subset of the protocol requested by the first or second frame is terminated.

[0014] One aspect of the present invention provides a first access point (AP) in a wireless network. The first AP includes a memory and a processor coupled to the memory. The processor is configured to establish multi-AP coordination with a second AP. The multi-AP coordination includes a set of protocols established between the first AP and the second AP. The processor is configured to receive a first frame from the second AP requesting termination of one or more protocols established between the first AP and the second AP.

[0015] In some embodiments, the processor is further configured to send a second frame to the second AP, the second frame indicating a response to the first frame, the second frame including a field indicating an acceptance, rejection, or alternative proposal for terminating at least one protocol between the first AP and the second AP.

[0016] In some embodiments, the first or second frame includes a field indicating whether the request is for a set of partially terminated protocols or a set of completely terminated protocols.

[0017] In some embodiments, the first or second frame includes a field indicating the type of multi-AP coordination.

[0018] In some embodiments, the first or second frame includes a field indicating an identifier of the protocol to be terminated.

[0019] In some embodiments, multi-AP coordination is multi-AP coordination based on target wake-up time (TWT).

[0020] In some embodiments, when a field indicates that a portion of the request is terminated, a subset of the protocol requested in the first or second frame is terminated.

[0021] One aspect of the present invention provides a method performed by a first access point (AP) device in a wireless network. The method includes establishing multi-AP coordination with a second AP. Multi-AP coordination includes a set of protocols established between the first AP and the second AP. The method includes sending a first frame to the second AP requesting termination of one or more protocols established between the first AP and the second AP.

[0022] In some embodiments, the method further includes receiving a second frame from the second AP indicating a response to the first frame, the second frame including a field indicating an acceptance, rejection, or alternative proposal for terminating at least one protocol between the first AP and the second AP.

[0023] In some embodiments, the first or second frame includes a field indicating whether the request is for a set of partially terminated protocols or a set of completely terminated protocols.

[0024] In some embodiments, the first or second frame includes a field indicating the type of multi-AP coordination.

[0025] In some embodiments, the first or second frame includes a field indicating an identifier of the protocol to be terminated.

[0026] In some embodiments, when a field indicates that a portion of the request is terminated, a subset of the protocol requested by the first or second frame is terminated. Attached Figure Description

[0027] Figure 1 An example of a wireless network according to an embodiment is shown.

[0028] Figure 2a An example of an AP according to an embodiment is shown.

[0029] Figure 2b An example of a STA according to an embodiment is shown.

[0030] Figure 3 An example of multi-link communication operation according to an embodiment is shown.

[0031] Figure 4 An example of a separate TWT operation according to an embodiment is shown.

[0032] Figure 5 An example of broadcast TWT operation according to an embodiment is shown.

[0033] Figure 6 An example of a typical AP development scenario based on TWT-based multi-AP coordination is shown according to an embodiment.

[0034] Figure 7 An example of C-TWT parameter update negotiation according to an embodiment is shown.

[0035] Figure 8 An example of full MAP termination according to an embodiment is shown.

[0036] Figure 9 An example of partial MAP termination according to an embodiment is shown.

[0037] Figure 10 An example procedure for terminating the MAP protocol in a TWT-based MAP coordination according to an embodiment is shown.

[0038] Figure 11 Another example procedure for MAP protocol termination in TWT-based MAP coordination according to an embodiment is shown.

[0039] Figure 12 Another example procedure for MAP protocol termination in TWT-based MAP coordination according to an embodiment is shown.

[0040] Figure 13 Example procedures for MAP protocol termination in various types of MAP coordination according to embodiments are shown.

[0041] Figure 14 An example format of a TWT element according to an embodiment is shown.

[0042] In one or more implementations, not all components depicted in each figure may be required, and one or more implementations may include additional components not shown in the figures. The arrangement and type of components may vary without departing from the scope of this subject matter disclosure. Within the scope of this subject matter disclosure, additional components, different components, or fewer components may be used. Detailed Implementation

[0043] The specific embodiments given below, in conjunction with the accompanying drawings, are intended to describe various implementations and not to represent the only implementations in which the subject matter can be practiced. Rather, the specific embodiments include detailed descriptions to provide a thorough understanding of the subject matter of the invention. As those skilled in the art will recognize, the described implementations can be modified in various ways without departing from the scope of this disclosure. Therefore, the drawings and descriptions are to be considered illustrative in nature and not restrictive. Similar reference numerals denote similar elements.

[0044] For the purpose of describing the innovative aspects of this disclosure, the following description is directed to certain implementations. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The examples in this disclosure are based on WLAN communication in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, including the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. However, the described embodiments can be implemented in any device, system, or network (such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof) capable of transmitting and receiving radio frequency (RF) signals according to the IEEE 802.11 standard, Bluetooth standard, Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunking Radio (TETRA), Wideband CDMA (W-CDMA), Evolved Data Optimized (EV-DO), 1xEV-DO, EV-DO Version A, EV-DO Version B, High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolved High-Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), 5G NR (New Radio), AMPS, or other known signals for communication within wireless, cellular, or Internet of Things (IoT) networks.

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

[0046] Multilink Operation (MLO) is a key feature currently being developed by the standards organization IEEE 802.11be for next-generation Ultra High Throughput (EHT) Wi-Fi systems. Wi-Fi devices that support MLO are called Multilink Devices (MLDs). Using MLO, a non-AP MLD can discover, authenticate, associate, and establish multiple links with an AP MLD. Channel access and frame switching are possible on each link between the AP MLD and non-AP MLDs.

[0047] Figure 1 An example of a wireless network 100 according to an embodiment is shown. Figure 1 The illustrated embodiment of the wireless network 100 is for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0048] like Figure 1 As shown, wireless network 100 may include multiple wireless communication devices. Each wireless communication device may include one or more stations (STAs). An STA may be a logical entity, which is a separately addressable instance of the Media Access Control (MAC) layer and Physical (PHY) layer interface to the wireless media. STAs may be classified as Access Point (AP) STAs and Non-Access Point (Non-AP) STAs. An AP STA may be an entity that provides access to distributed system services to associated STAs via the wireless media. A Non-AP STA may be a STA that is not included in an AP-STA. For simplicity, an AP STA may be referred to as an AP, and a non-AP STA may be referred to as a STA. Figure 1 In the example, APs 101 and 103 are wireless communication devices, and each wireless communication device may include one or more AP STAs. In such an embodiment, APs 101 and 103 may be AP multilink devices (MLDs). Similarly, STAs 111-114 are wireless communication devices, and each wireless communication device may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

[0049] APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network. AP 101 provides wireless access to network 130 to multiple stations (STAs) 111-114 in the coverage area 120 of AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

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

[0051] exist Figure 1 In the diagram, the dashed lines show the approximate extent of the coverage areas 120 and 125 of APs 101 and 103, which are shown as approximately circular for illustrative and explanatory purposes. It should be clearly understood that, depending on the configuration of the APs, the coverage areas associated with the APs (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0052] As described in more detail below, one or more of the APs may include circuitry and / or programs for managing MU-MIMO and OFDMA channel probing in the WLAN. Although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1 Various modifications can be made. For example, wireless network 100 can include any number of APs and any number of STAs in any suitable arrangement. Furthermore, AP 101 can communicate directly with any number of STAs and provide them with wireless broadband access to network 130. Similarly, each AP 101 and 103 can communicate directly with network 130 and provide STAs with direct wireless broadband access to network 130. Additionally, AP 101 and / or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0053] Figure 2a An example of AP 101 according to an embodiment is shown. Figure 2a The embodiment of AP 101 shown is for illustrative purposes, and Figure 1 AP 103 can have the same or similar configuration. However, APs have a wide variety of configurations, and Figure 2a This disclosure is not intended to limit the scope to any particular implementation of AP.

[0054] like Figure 2a As shown, AP 101 may include multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. AP 101 may also include a controller / processor 224, a memory 229, and a backhaul or network interface 234. RF transceivers 209a-209n receive incoming RF signals from antennas 204a-204n, such as signals transmitted by STAs in network 100. RF transceivers 209a-209n down-convert the incoming RF signals to generate intermediate frequency (IF) or baseband signals. The IF or baseband signals are sent to RX processing circuitry 219, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 219 sends the processed baseband signals to controller / processor 224 for further processing.

[0055] TX processing circuit 214 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 224. TX processing circuit 214 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 209a-209n receive the processed baseband or IF signal from TX processing circuit 214 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 204a-204n.

[0056] The controller / processor 224 may include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller / processor 224 may control the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 to receive uplink signals and transmit downlink signals, based on known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 224 may support beamforming or directional routing operations, where outgoing signals from multiple antennas 204a-204n are weighted differently to effectively direct the outgoing signals in a desired direction. The controller / processor 224 may also support OFDMA operations, where outgoing signals are assigned to different subsets of subcarriers from different receivers (e.g., different STAs 111-114). In the AP 101, the controller / processor 224 may support any of a variety of other functions, including a combination of DLMU-MIMO and OFDMA in the same transmission opportunity. In some embodiments, the controller / processor 224 may include at least one microprocessor or microcontroller. The controller / processor 224 is also capable of executing programs and other processes, such as an operating system, residing in the memory 229. The controller / processor 224 may move data into or out of the memory 229 as needed for the execution process.

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

[0058] As described in more detail below, AP 101 may include circuitry and / or programming for managing the channel detection process in a WLAN. Although Figure 2a An example of AP 101 is shown, but it is possible to compare it with other versions. Figure 2a Various changes can be made. For example, AP101 can include any number of... Figure 2aEach component is shown. As a specific example, the AP may include multiple interfaces 234, and the controller / processor 224 may support routing functionality to route data between different network addresses. As another example, although shown as a single instance including TX processing circuitry 214 and a single instance including RX processing circuitry 219, AP 101 may include multiple instances of each component (such as one instance per RF transceiver). Alternatively, as in a conventional AP, it may include only one antenna and one RF transceiver path. Furthermore, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0059] like Figure 2a As shown, in some embodiments, AP 101 may be an AP MLD comprising multiple APs 202a-202n. Each AP 202a-202n is attached to AP MLD 101 and includes multiple antennas 204a-204n, multiple radio frequency (RF) transceivers 209a-209n, transmit (TX) processing circuitry 214, and receive (RX) processing circuitry 219. Each AP 202a-202n may communicate independently with the controller / processor 224 and other components of AP MLD 101. Figure 2a The diagram shows that each AP 202a-202n has multiple antennas individually, but each AP 202a-202n can share multiple antennas 204a-204n without requiring separate multiple antennas. Each AP 202a-202n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0060] Figure 2b An example of STA 111 according to an embodiment is shown. Figure 2b The embodiment of STA 111 shown is for illustrative purposes, and Figure 1 STAs 111-114 can have the same or similar configurations. However, STAs have a wide variety of configurations, and Figure 2b This disclosure is not intended to limit the scope to any particular implementation of STA.

[0061] like Figure 2b As shown, STA 111 may include an antenna 205, an RF transceiver 210, a TX processing circuit 215, a microphone 220, and an RX processing circuit 225. STA 111 may also include a speaker 230, a controller / processor 240, an input / output (I / O) interface (IF) 245, a touchscreen 250, a display 255, and a memory 260. The memory 260 may include an operating system (OS) 261 and one or more applications 262.

[0062] RF transceiver 210 receives incoming RF signals transmitted by the AP of network 100 from antenna 205. RF transceiver 210 down-converts the incoming RF signals to generate an IF or baseband signal. The IF or baseband signal is sent to RX processing circuitry 225, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 225 sends the processed baseband signal to speaker 230 (e.g., for voice data) or controller / processor 240 for further processing (e.g., for web browsing data).

[0063] TX processing circuit 215 receives analog or digital voice data from microphone 220 or other outgoing baseband data (such as web data, email, or interactive video game data) from controller / processor 240. TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the processed baseband or IF signal from TX processing circuit 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0064] The controller / processor 240 may include one or more processors and executes a basic OS program 261 stored in memory 260 to control the overall operation of STA 111. In one such operation, the controller / processor 240 controls the RF transceiver 210, RX processing circuitry 225, and TX processing circuitry 215 to receive downlink signals and transmit uplink signals according to known principles. The controller / processor 240 may also include processing circuitry configured to provide management of channel detection processes in a WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0065] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sensing processes in the WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution of the process. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for channel sensing, which include feedback calculations based on received null data packet announcements (NDPA) and null data packets (NDP), and sending beamforming feedback reports in response to trigger frames (TF). The controller / processor 240 can operate the multiple applications 262 based on the OS program 261 or in response to signals received from the AP. The controller / processor 240 is also coupled to an I / O interface 245, which provides the STA 111 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0066] The controller / processor 240 is also connected to input 250 (such as a touchscreen) and display 255. The operator of STA 111 can use input 250 to input data into STA 111. Display 255 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text (such as from a website) and / or at least limited graphics. Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), while another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0067] although Figure 2b An example of STA 111 is shown, but it is possible to compare it with other models. Figure 2b Make various changes. For example, Figure 2b The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. In a specific example, STA 111 may include any number of antennas 205 for MIMO communication with AP 101. In another example, STA 111 may not include voice communication, or the controller / processor 240 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although Figure 2b The STA 111 is shown configured as a mobile phone or smartphone, but the STA can be configured to operate as other types of mobile or fixed devices.

[0068] like Figure 2bAs shown, in some embodiments, STA 111 may be a non-AP MLD comprising multiple STAs 203a-203n. Each STA 203a-203n is attached to the non-AP MLD 111 and includes an antenna 205, an RF transceiver 210, TX processing circuitry 215, and RX processing circuitry 225. Each STA 203a-203n may independently communicate with the controller / processor 240 and other components of the non-AP MLD 111. Figure 2b It is shown that each STA 203a-203n has a separate antenna, but each STA 203a-203n can share antenna 205 without requiring a separate antenna. Each STA 203a-203n can represent the physical (PHY) layer and the lower media access control (MAC) layer.

[0069] Figure 3 An example of multi-link communication operation according to an embodiment is shown. Multi-link communication operation can be used in the IEEE 802.11be standard and any future revisions to the IEEE 802.11 standard. Figure 3 In the middle, AP MLD 310 can be Figure 1 Wireless communication devices 101 and 103, rather than AP MLD 220, can be Figure 1 One of the wireless communication devices 111-114 in the series.

[0070] like Figure 3 As shown, AP MLD 310 may include multiple auxiliary APs, such as AP 1, AP 2, and AP 3. Each auxiliary AP may include a PHY interface (Link 1, Link 2, or Link 3) to the wireless media. AP MLD 310 may include a single MAC Service Access Point (SAP) 318, through which the auxiliary APs of AP MLD 310 communicate with higher layers (Layer 3 or network layer). Each auxiliary AP of AP MLD 310 may have a MAC address (lower MAC address) different from any other auxiliary AP of AP MLD 310. AP MLD 310 may have an MLD MAC address (upper MAC address), and the auxiliary APs share the single MAC SAP 318 to Layer 3. Therefore, the auxiliary APs share a single IP address, and Layer 3 identifies AP MLD 310 by assigning a single IP address.

[0071] A non-AP MLD 320 may include multiple affiliated STAs, such as STA 1, STA 2, and STA 3. Each affiliated STA may include a PHY interface (Link 1, Link 2, or Link 3) to the wireless media. The non-AP MLD 320 may include a single MAC SAP 328, through which the affiliated STAs communicate with higher layers (Layer 3 or the network layer). Each affiliated STA of the non-AP MLD 320 may have a MAC address (lower-layer MAC address) different from any other affiliated STA of the non-AP MLD 320. The non-AP MLD 320 may have an MLD MAC address (upper-layer MAC address), and the affiliated STAs share the single MAC SAP 328 to Layer 3. Therefore, the affiliated STAs share a single IP address, and Layer 3 identifies the non-AP MLD 320 by assigning this single IP address.

[0072] Multiple links can be established between AP MLD 310 and non-AP MLD 320 devices and their associated APs and STAs. In this example, AP 1 and STA 1 can establish Link 1, operating in the 2.4 GHz band. Similarly, AP 2 and STA 2 can establish Link 2, operating in the 5 GHz band, and AP 3 and STA 3 can establish Link 3, operating in the 6 GHz band. Each link can independently enable channel access and frame switching between AP MLD 310 and non-AP MLD 320 devices, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (established links), each non-AP device is assigned a unique Association Identifier (AID).

[0073] The following documents are incorporated herein by reference in their entirety, as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications”, ii) IEEE 802.11ax-2021, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications”, and ii) IEEE P802.11be / D3.1, “Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications”.

[0074] Target Wake-Up Time (TWT) operation is a feature of power management in WLAN networks. TWT was introduced in the IEEE 802.11ah standard and later revised in the IEEE 802.11ax standard. TWT allows APs to manage activity within a Basic Service Set (BSS) to minimize contention between STAs and reduce wake-up time required by STAs during TWT operations. This is achieved by allocating STAs to operate on non-overlapping times or frequencies and performing frame exchange sequences within pre-scheduled service periods. During TWT operations, STAs can wake up at a pre-scheduled time negotiated with an AP in the BSS or another STA. STAs do not need to know the TWT parameter values ​​of other STAs within the BSS or STAs in other BSSs. STAs do not need to know the TWT service period (SP) used to exchange frames with other STAs. Frames transmitted during a TWT SP can use any PPDU (Physical Layer Protocol Data Unit) format supported by STAs with established TWT protocols, including but not limited to HEMU (High-Efficiency Multi-User) PPDU and HE TB (High-Efficiency Trigger-Based) PPDU.

[0075] The IEEE 802.11 standard describes two types of TWT operations: standalone TWT operations and broadcast TWT operations. In standalone TWT operations, a separate TWT protocol can be established between two STAs or between a STA and an AP. Negotiation for a standalone TWT operation can be conducted separately between two STAs or between a STA and an AP. An AP may have TWT protocols with multiple STAs. Any change to the TWT protocol between an AP and a STA will not affect the TWT protocols between that AP and other STAs.

[0076] Figure 4 An example of a separate TWT operation according to an embodiment is shown. Figure 4 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any specific implementation.

[0077] exist Figure 4 In this context, STA 1 and STA 2 are TWT request STAs, and AP is a TWT response STA. Figure 4In the example, STA 1 sends a TWT request 401 to the AP to establish a trigger-enabled TWT protocol. The AP accepts STA 1's TWT request 401 and confirms the acceptance in a TWT response 403 sent to STA 1. Subsequently, the AP sends an unsolicited TWT response 405 to STA 2 to establish a trigger-enabled TWT protocol with STA 2. Both TWT protocols are configured as announcement-type TWTs. During the trigger-enabled TWT SP, the AP sends a basic trigger frame 407 to the TWT requesting STAs (STA 1 and STA 2), which can indicate that they are awake during the TWT SP. In response to the basic trigger frame 407, STA 1 indicates that it is awake by sending a PS (power save) polling frame 409, and STA 2 indicates that it is awake by sending a QoS (quality of service) empty frame 411. Subsequently, the AP sends a multi-STA block acknowledgment (BlockAck) frame 413 and a DL MU (Downlink Multi-User) PPDU 415 to both STA 1 and STA 2. After that, STA 1 and STA 2 send block acknowledgment frames 417 and 419 to the AP respectively, and then enter a sleep state.

[0078] On the other hand, broadcast TWTs operate on a membership basis. In broadcast TWT operations, an AP can establish a shared TWT session for a group of STAs. The AP is typically the controller for broadcast TWT scheduling. Non-AP STAs in the BSS can request membership in a broadcast TWT schedule, or the AP can send an unsolicited response to an STA to make the STA a member of a broadcast TWT schedule maintained by the AP in the BSS. An AP can advertise and maintain multiple broadcast TWT schedules in the BSS. When any broadcast TWT schedule in the BSS is changed, it may affect all or some of the STAs that are members of the corresponding broadcast TWT schedule.

[0079] Figure 5 An example of broadcast TWT operation according to one embodiment is shown. Figure 5 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0080] exist Figure 5 In this context, STA 1 and STA 2 are TWT-scheduled STAs, and AP is a TWT-scheduling AP. Figure 5In the example, STA 1 and AP can optionally negotiate TBTT (Target Beacon Transmission Time) by exchanging TWT request frames 501 and TWT response frames 503. After the first TBTT, the AP sends a beacon frame 505 that includes a broadcast TWT element indicating a broadcast TWTSP. During the TWTSP, the AP can send a trigger frame or downlink bufferable unit (BU) to the TWT-scheduled STAs (STA 1 and STA 2). STA 1 and STA 2 wake up to receive beacon frame 505 to determine the broadcast TWT. During a trigger-enabled TWTSP, the AP sends a basic trigger frame 507 to STA 1 and STA 2, indicating that they are awake during the TWTSP. In response to the basic trigger frame 507, STA 1 indicates that it is awake by sending a PS-Poll frame 509, while STA 2 indicates that it is awake by sending a QoS empty frame 511. STA 1 and STA 2 receive their DL BUs in subsequent frame exchanges with the AP (e.g., multi-STA BlockAck 513, DL MU PPDU 515, and BlockAck 517 and 519) and enter a sleep state outside of the TWT SP. After the TWT SP, the AP periodically sends beacon frames 521 and 523 to STA 1 and STA 2. As shown, the AP can advertise / announce and maintain multiple broadcast TWT schedules in the BSS. When any broadcast TWT schedule is changed, it may affect all STAs that are members of a specific TWT schedule.

[0081] Recently, the IEEE 802.11be standard introduced TWT enhancements for MLDs. For a separate TWT protocol between two MLDs, the STA belonging to the MLD and acting as the TWT requesting STA can indicate the link requested to establish the TWT protocol in the Link ID bitmap subfield of the TWT element in the TWT request (if present). If only one link is indicated in the Link ID bitmap subfield of the TWT element, a single TWT protocol is requested for the corresponding STA belonging to the same MLD that is operating on the indicated link. The Target Wake-up Time field of the TWT element should reference the Time Synchronization Function (TSF) time of the link indicated by the TWT element. The TWT response STA belonging to the peer MLD that received the TWT request containing the Link ID bitmap subfield in the TWT element responds with a TWT response indicating the link in the Link ID bitmap field of the TWT element. The link in the TWT element carried in the TWT response (if present) can be the same as the link indicated in the TWT element of a soliciting TWT request.

[0082] Restricted Time-to-Wave (R-TWT) operation is another important feature of next-generation WLANs. R-TWT operation provides better support for latency-sensitive applications. For example, traffic in real-time applications has strict requirements regarding latency and jitter, and certain reliability constraints. In this disclosure, such traffic may be referred to as latency-sensitive traffic. R-TWT operation can provide protected service periods (SPs) for R-TWT member STAs by sending quiet elements to non-member STAs in the BSS of the R-TWT schedule. In some implementations, the quiet interval of the quiet element overlaps with the initial portion of the R-TWT SP. Therefore, it can provide R-TWT member STAs with more channel access opportunities than non-member STAs, thereby improving the flow of latency-sensitive traffic.

[0083] Interference from a single BSS typically causes performance issues for STAs and APs in adjacent BSSs. This interference can lead to a decrease in overall network throughput. Overlapping BSS (OBSS) interference can also increase overall latency because more time is required to access the channel due to interference occupancy. If STAs in a BSS have latency-sensitive traffic, this delay in channel access can significantly impair the performance of latency-sensitive applications on those STAs. To address these issues, TWT-based multi-AP (MAP) coordination is being considered for next-generation WLAN systems.

[0084] Figure 6 An example of a typical AP development scenario based on TWT-based multi-AP coordination is shown according to an embodiment.

[0085] exist Figure 6 In this diagram, AP 1, AP 2, AP 3, and AP 4 form BSS 1, BSS 2, BSS 3, and BSS 4, respectively. In some embodiments, AP 1, AP 2, AP 3, and AP 4 may be members of a TWT-coordinated AP set and are participating in TWT-based multi-AP (MAP) coordination. As shown in the figure, BSS 1 overlaps with BSS 2, BSS 3, and BSS 4.

[0086] refer to Figure 6 These APs can be used as TWT scheduling APs in their respective BSS systems. APs participating in TWT-based MAP coordination can negotiate the coordination by directly exchanging frames between APs.

[0087] In this disclosure, a TWT-sharing AP can refer to an AP that has or intends to have TWT scheduling or a TWT protocol in its BSS and initiates a TWT coordination procedure with the AP in the OBSS to better protect the TWT SP, for example, by increasing channel access opportunities or reducing OBSS interference. Additionally, a TWT-shared AP can refer to an AP that receives a TWT coordination request from the TWT-sharing AP. In one embodiment, the TWT-sharing AP can share or suggest TWT information to the STA with the TWT-shared AP; this can be referred to as "coordinated TWT (C-TWT)". Such coordination can help mitigate OBSS interference or enhance signal power during the TWT SP.

[0088] In current TWT operations, there are no rules for terminating TWT-based MAP coordination. Therefore, this disclosure provides various concepts, conditions, and procedures for TWT-based MAP coordination.

[0089] In some embodiments, when a TWT-sharing AP intends to update the parameters of a C-TWT, these updates need to be communicated to the TWT-shared AP and subsequently to the BSS of the TWT-shared AP.

[0090] In one embodiment, the TWT-shared AP monitors the beacon frames of the TWT-sharing AP, which announces any changes or upcoming updates to the TWT parameters based on TWT-based MAP coordination or C-TWT scheduling. Whenever the TWT-sharing AP announces an update to the TWT parameters based on TWT-based MAP coordination or C-TWT scheduling, the TWT-shared AP accepts these updates and subsequently notifies its respective BSS. When an update to the TWT parameters is ineffective for the TWT-shared AP, or when the TWT-shared AP may not be able to accept the update, the TWT-shared AP may terminate the TWT-based MAP coordination and notify the TWT-sharing AP of the termination. This could be an example of implicit notification.

[0091] In an embodiment, the TWT-sharing AP can explicitly notify each TWT-shared AP of impending changes to the TWT parameters of TWT-based MAP coordination or C-TWT scheduling. The TWT-shared APs may respond by accepting, rejecting, or suggesting an alternative. When a TWT-shared AP accepts an update to its TWT parameters, it can subsequently notify its respective BSS of the update. When a TWT-shared AP rejects the update, TWT-based MAP coordination can be terminated for the TWT-shared AP, and the TWT-shared AP can notify its BSS of the termination.

[0092] In this embodiment, a TWT-shared AP or a TWT-shared AP can terminate TWT-based MAP coordination at any time, but they need to notify the other party of the termination.

[0093] A TWT-sharing AP or a TWT-shared AP can send a separate addressing frame, broadcast frame, or multicast frame to indicate that it does not intend to participate in TWT-based MAP coordination, and then it can terminate the TWT-based MAP coordination.

[0094] Termination procedures or conditions may apply to other types of multi-AP coordination, including but not limited to joint transmission and coordinated beamforming.

[0095] Figure 7 An example of C-TWT parameter update negotiation according to an embodiment is shown. Figure 7 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0096] exist Figure 7 In this diagram, AP 1 is a TWT-sharing AP used for TWT-based MAP coordination, while AP 2, AP 3, and AP 4 are TWT-shared APs used for TWT-based MAP coordination. AP 1 sends a C-TWT parameter update notification to AP 2, AP 3, and AP 4, indicating its intention to change or update the C-TWT parameters. The TWT parameter update notification can be sent via a separately addressed frame, a broadcast frame, or a multicast frame. In response, AP 2 refuses to comply with the updated C-TWT parameters by sending a C-TWT parameter update response to AP 1. Therefore, the TWT-based MAP coordination between AP 1 and AP 2 is terminated. On the other hand, AP 3 and AP 4 propose updated replacement TWT parameter sets by sending C-TWT parameter update responses, respectively. Subsequently, AP 1 notifies AP 3 and AP 4 of the new update or change by sending a second C-TWT parameter update notification. AP 3 and AP 4 accept the update by sending C-TWT parameter update responses, respectively.

[0097] In some embodiments, different MAP coordination termination modes may exist. For example, full MAP termination and partial MAP termination. For simplicity, MAP coordination termination may be referred to as "MAP termination" in this disclosure. In a full MAP termination embodiment, when a termination frame is transmitted to terminate a particular type of MAP coordination, all existing protocols of the MAP coordination may be terminated. In a partial MAP termination embodiment, when a termination frame is transmitted to terminate a particular type of MAP coordination, only a subset of the existing protocols of the MAP coordination are terminated, without terminating and maintaining the remaining parts of the MAP coordination protocols.

[0098] Figure 8An example of full MAP termination according to an embodiment is shown. Figure 8 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0099] Figure 8 The top line in the diagram illustrates the C-TWT SPs between a TWT-sharing AP and one or more TWT-shared APs in a TWT-based MAP coordination. As shown, three C-TWT SPs (C-TWT SP A, C-TWT SP B, and C-TWT SP C) have been protocol-used for TWT-based MAP coordination. C-TWT SP A corresponds to C-TWT schedule 1, while C-TWT SP B and C-TWT SP C correspond to C-TWT schedule 2 and C-TWT schedule 3, respectively.

[0100] Figure 8 The bottom line in the figure shows the situation after the termination of TWT-based MAP coordination. As shown, all C-TWT SPs corresponding to C-TWT schedules 1 to 3 are terminated.

[0101] Figure 9 An example of partial MAP termination according to an embodiment is shown. Figure 9 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0102] Figure 9 The top line in the diagram illustrates the C-TWT SPs between a TWT-sharing AP and one or more TWT-shared APs in a TWT-based MAP coordination. As shown, three C-TWT SPs (C-TWT SP A, C-TWT SP B, and C-TWT SP C) have been used in the protocol for TWT-based MAP coordination. C-TWT SP A corresponds to C-TWT schedule 1, while C-TWT SP B and C-TWT SP C correspond to C-TWT schedule 2 and C-TWT schedule 3, respectively.

[0103] Figure 9 The bottom line in the figure illustrates the situation after partial termination of TWT-based MAP coordination. As shown, C-TWT SP B, corresponding to C-TWT schedule 2, is terminated, while C-TWT SP A and C-TWT SP C are not terminated and are maintained.

[0104] In some embodiments, the first AP has agreed to coordinate TWT-based MAP coordination with the second AP and has established a MAP coordination protocol. The first AP may send a MAP termination frame to the second AP, indicating that the first AP intends to terminate one or more MAP protocols between the first AP and the second AP. When the first AP sends the MAP termination frame, the intended MAP protocol is terminated.

[0105] Figure 10 An example procedure 1000 for MAP protocol termination in TWT-based MAP coordination according to an embodiment is shown. Figure 10 The scenes and operations depicted are for illustrative purposes only and do not limit the scope of this disclosure to any particular implementation.

[0106] refer to Figure 10 Process 1000 can begin with operation 1010. In operation 1010, TWT-sharing AP 1001 and TWT-shared AP 1002 establish one or more C-TWT schedules for TWT-based MAP coordination.

[0107] In operation 1012, TWT-sharing AP 1001 intends to terminate all C-TWT scheduling established with TWT-shared AP 1002. TWT-sharing AP 1001 sends a C-TWT termination frame to TWT-shared AP 1002. The C-TWT termination frame indicates complete MAP termination.

[0108] In operation 1014, when a C-TWT termination frame is received from the TWT sharing AP 1001, the TWT is processed by the sharing AP 1002 to form the C-TWT termination frame.

[0109] In Operation 1016, all existing C-TWT scheduling between TWT-sharing AP 1001 and TWT-shared AP 1002 is terminated.

[0110] Figure 11 Another example process 1100 for MAP protocol termination in TWT-based MAP coordination according to an embodiment is shown. Figure 11 The scenes and operations depicted are for illustrative purposes only and do not limit the scope of this disclosure to any particular implementation.

[0111] refer to Figure 11 Process 1100 can begin with operation 1110. In operation 1110, TWT-sharing AP 1101 and TWT-shared AP 1102 establish one or more C-TWT schedules for TWT-based MAP coordination.

[0112] In operation 1112, the TWT-sharing AP 1101 intends to terminate only a subset of all C-TWT schedules established with the TWT-shared AP 1102. The TWT-sharing AP 1101 sends a C-TWT termination frame to the TWT-shared AP 1102. The C-TWT termination frame indicates partial MAP termination. In an embodiment, the C-TWT termination frame indicates that the C-TWT schedule with [C-TWT ID = X] will be terminated.

[0113] In operation 1114, when a C-TWT termination frame is received from the TWT sharing AP 1101, the TWT is processed by the sharing AP 1102 to form the C-TWT termination frame.

[0114] In operation 1116, only the C-TWT schedule corresponding to [C-TWT ID=X] is terminated, while all other existing C-TWT schedules are maintained.

[0115] In some embodiments, upon receiving a C-TWT termination frame from TWT-sharing AP 1101, TWT-sharing AP 1102 may send an acknowledgment frame to TWT-sharing AP 1101 in response. Sending the acknowledgment frame to TWT-sharing AP 1101 may terminate the intended C-TWT scheduling.

[0116] Figure 12 Another example process 1200 for MAP protocol termination in TWT-based MAP coordination according to an embodiment is shown. Figure 12 The scenes and operations depicted are for illustrative purposes only and do not limit the scope of this disclosure to any particular implementation.

[0117] refer to Figure 12 Process 1200 can begin with operation 1210. In operation 1210, the TWT-sharing AP 1201 and the TWT-shared AP 1202 establish one or more C-TWT schedules for TWT-based MAP coordination.

[0118] In operation 1212, TWT-sharing AP 1201 intends to terminate all existing C-TWT scheduling established with TWT-shared AP 1202. TWT-sharing AP 1201 sends a C-TWT termination frame to TWT-shared AP 1202. The C-TWT termination frame indicates complete MAP termination.

[0119] In operation 1214, after receiving the C-TWT termination frame from the TWT sharing AP 1201, the TWT is processed by the sharing AP 1202 to form the C-TWT termination frame.

[0120] In operation 1216, the TWT-shared AP 1202 sends a C-TWT termination response frame to the TWT-shared AP 1201. The C-TWT termination response frame can be an acknowledgment frame.

[0121] In operation 1218, all existing C-TWT scheduling between TWT-sharing AP 1201 and TWT-shared AP 1202 is terminated.

[0122] In some embodiments, the first AP and the second AP establish one or more types of MAP coordination protocols, such as, but not limited to, coordinated TWT (C-TWT), coordinated spatial multiplexing (C-SR), coordinated time division multiple access (C-TDMA), coordinated beamforming (C-BF), or coordinated joint transmission (C-JT). The first AP may send a MAP termination frame to the second AP to terminate the existing MAP protocol. In the MAP termination frame, the first AP may indicate which type of MAP coordination protocol to terminate. Furthermore, the first AP may also identify a subset of MAP coordination protocols of the indicated type that the first AP intends to terminate by including an indication of the protocol to be terminated (e.g., but not limited to, a C-TDMA ID corresponding to a specific type of C-TDMA protocol) in the MAP termination frame.

[0123] Figure 13 Example process 1300 for MAP protocol termination in various types of MAP coordination according to embodiments is shown. Figure 13 The scenes and operations depicted are for illustrative purposes only and do not limit the scope of this disclosure to any particular implementation.

[0124] refer to Figure 13 Process 1300 can begin with operation 1310. In operation 1310, MAP coordinating AP 1 and MAP coordinating AP 2 establish a set of MAP coordination protocols.

[0125] In operation 1312, MAP Coordinating AP 1 intends to terminate only a subset of all existing MAP coordination protocols. MAP Coordinating AP 1 sends a MAP termination frame to MAP Coordinating AP 2. The C-TWT termination frame indicates the type of MAP coordination and the identifier of the protocol to be terminated. In an embodiment, the C-TWT termination frame indicates that the C-TDMA protocol with [C-TDMA ID = Y] will be terminated.

[0126] In operation 1314, when a MAP termination frame is received from MAP Coordination AP 1, MAP Coordination AP 2 processes the C-TWT termination frame.

[0127] In operation 1316, the C-TDMA protocol with [C-TDMA ID = Y] is terminated.

[0128] Example formats for MAP termination frames are shown in Table 1 below. In some embodiments, the same format can be used for MAP termination request frames when request / response-based termination is required. A MAP termination frame may include a category field, an unprotected S1G action field, a session token field, a MAP termination mode field, a MAP protocol type field, and a MAP protocol ID field. The category field indicates the category of the MAP termination frame. The unprotected S1G action field may include field values ​​associated with the MAP termination frame to distinguish the unprotected S1G action frame format. The session token field may include a value identifying the MAP termination transaction. The MAP termination mode field indicates whether a partial or full MAP termination is requested. In an embodiment, when the MAP termination mode field is set to 1, it indicates a request for full MAP termination. Conversely, when the MAP termination mode field is set to 0, it indicates a request for partial MAP termination. The MAP protocol type field indicates the type of MAP protocol to be terminated. In an embodiment, when this field is set to 0, it indicates the termination of C-TWT. When this field is set to 1, it indicates the termination of C-TDMA, and when this field is set to 2, it indicates the termination of C-SR. The MAP Protocol ID field indicates the identifier of the MAP protocol to be terminated. The type of MAP protocol is indicated in the MAP Protocol Type field.

[0129] Table 1

[0130]

[0131] An example format for a MAP termination response frame is shown in Table 2 below. A MAP termination response frame may include a category field, an unprotected S1G action field, a session token field, a status code field, a MAP termination mode field, a MAP protocol type field, and a MAP protocol ID field. The category field indicates the category of the MAP termination response frame. The unprotected S1G action field may include field values ​​associated with the MAP termination response frame to distinguish the unprotected S1G action frame format. The session token field may include a value identifying the MAP termination transaction. The status code field indicates whether the requested operation succeeded or failed. In an embodiment, when the code field is set to 0, it may indicate rejection of the MAP termination request. When the code field is set to 1, it may indicate acceptance of the MAP termination request, and when the code field is set to 2, it may indicate an alternative suggestion for the MAP termination request. Alternative suggestions may be indicated in the MAP termination mode field, the MAP protocol type field, and the MAP protocol ID field. The MAP termination mode field may indicate partial or complete MAP termination. In an embodiment, when the MAP termination mode field is set to 1, it may indicate complete MAP termination. Conversely, when the MAP Termination Mode field is set to 0, it can indicate partial MAP termination. The MAP Protocol Type field indicates the type of MAP protocol to be terminated. In an embodiment, when this field is set to 0, it can indicate the termination of C-TWT. When this field is set to 1, it can indicate the termination of C-TDMA, and when this field is set to 2, it can indicate the termination of C-SR. The MAP Protocol ID field indicates the identifier of the MAP protocol to be terminated. The type of MAP protocol is indicated in the MAP Protocol Type field.

[0132] Table 2

[0133]

[0134] Figure 14 An example format of a TWT element according to an embodiment is shown.

[0135] exist Figure 14 In the TWT element 1400, an element ID field, a length field, a control field, and one or more TWT parameter information fields may be included. The element ID field may include information identifying the TWT element 1400. The length field may indicate the length of the TWT element 1400.

[0136] The control fields may include the NDP Paging Indicator subfield, the Responder Power Management (PM) Mode subfield, the Negotiation Type subfield, the TWT Message Frame Disable subfield, the Wake-up Duration Unit subfield, the Link ID Bitmap Presence subfield, and the OBSS R-TWT subfield. The NDP Paging Indicator subfield indicates whether an NDP paging field exists in a separate TWT parameter set field. The Responder PM Mode subfield indicates the power management mode, such as active mode and power saving (PS) mode. The Negotiation Type subfield indicates whether the information included in the TWT element is used for negotiating parameters for broadcast or individual TWTs or Wake-up TBTT (Target Beacon Transmission Time) intervals. The MSB (Most Significant Bit) of the Negotiation Type subfield is the broadcast field, indicating whether one or more broadcast TWT parameter sets are included in the TWT element. The TWT Message Frame Disable subfield indicates whether the STA has disabled the reception of TWT message frames. The Wake-up Duration Unit subfield indicates the unit of the nominal minimum TWT wake-up duration subfield in the broadcast TWT parameter set field. The Link ID Bitmap Existence subfield indicates the presence of the Link ID Bitmap field within a separate TWT Parameter Set field. The OBSS R-TWT subfield indicates whether the R-TWT scheduler in the TWT element corresponding to the Broadcast TWT Parameter Set field is an R-TWT scheduler for an adjacent BSS. When the OBSS R-TWT subfield is set to '1', it indicates that the R-TWT scheduler in the TWT element is an R-TWT scheduler for an adjacent BSS. Otherwise, it indicates that there is no R-TWT scheduler for an adjacent BSS in the TWT element.

[0137] The TWT parameter information field includes a single TWT parameter set field or one or more broadcast TWT parameter set fields. For ease of description, Figure 14 The broadcast TWT parameter set field is shown. The broadcast TWT parameter set field 1410 may include a request type field, a target wake-up time field, a nominal minimum TWT wake-up duration field, a TWT wake-up interval tail number field, a broadcast TWT information field, and an optional restricted TWT traffic information field.

[0138] The request type field in broadcast TWT parameter set field 1410 can be used to indicate the presence of an aligned TWT schedule. (See reference...) Figure 14 The request type field includes the TWT request subfield, TWT creation command subfield, trigger subfield, last broadcast parameter set subfield, stream type subfield, broadcast TWT recommendation subfield, TWT wake-up interval index subfield, and alignment subfield. The request type field can be used for broadcast TWT operations.

[0139] The TWT Request subfield indicates whether the sending STA is a TWT scheduling AP (or STA) or a TWT-scheduled STA (or AP). The TWT Establish Command subfield indicates the type of TWT command, such as request TWT, suggest TWT, demand TWT, TWT packet, accept TWT, replace TWT, indicate TWT, and reject TWT. The Trigger subfield indicates whether the TWT SP indicated by the TWT element includes a trigger frame. The Last Broadcast Parameter Set subfield indicates whether there is another broadcast TWT parameter set field following this broadcast TWT parameter set field. The Flow Type subfield indicates the type of interaction between the TWT-scheduled STA and the TWT scheduling AP, such as an announcement TWT or a non-announcement TWT. The Broadcast TWT Recommendation subfield indicates a recommendation regarding the type of frames sent by the TWT-scheduled STA and the TWT scheduling AP during the broadcast TWT SP. For example, the frame type could be a PS-Poll and QoS empty frame, a management frame, a control response frame, or a frame without constraints. The TWT Wake-up Interval Exponent subfield indicates the exponential value of the TWT wake-up interval. The alignment subfield can indicate whether one or more other links of the AP MLD have broadcast a TWT schedule aligned with the corresponding schedule. More specifically, if the subfield is set to 1, it can indicate that there are one or more schedules on other links aligned with the TWT schedule identified by the Broadcast TWT Parameter Set field. Otherwise, there is no such schedule on other links.

[0140] The Target Wake-up Time field may include an unsigned integer corresponding to the TSF (Time Synchronization Function) time at which the TWT-scheduled STA wakes up. The Target Wake-up Time field may indicate the start time of the TWT Service Period (SP) on the corresponding link. The Nominal Minimum TWT Wake-up Duration field may indicate the minimum amount of time the TWT-scheduled STA is expected to wake up in order to complete frame exchange within the TWT wake-up interval. The TWT wake-up interval is the average time expected to elapse between consecutive TWT SPs by the TWT-scheduled STA. The TWT Wake-up Interval Tail field may indicate the value of the tail of the TWT wake-up interval value. The Broadcast TWT Information field may include information related to the broadcast TWT, such as the Limited TWT Traffic Information Presence field, the Limited TWT Scheduling Information field, the Broadcast TWT ID field, and the Broadcast TWT Duration field. The Limited TWT Traffic Information Presence field indicates whether the Limited TWT Traffic Information field exists. The Limited TWT Scheduling Information field indicates whether active R-TWT scheduling is active. The Broadcast TWT ID field indicates the specific broadcast TWT for which the sending STA is providing TWT parameters. The Broadcast TWT Duration field indicates the number of TBTTs existing for a broadcast TWT SP corresponding to this set of broadcast TWT parameters.

[0141] According to various embodiments, a mechanism is provided for negotiating and coordinating a portion of the TWT parameter set for TWT-based MAP coordination between the TWT-sharing AP and the TWT-shared AP. Therefore, the TWT-sharing AP can assume that the TWT coordination negotiation has been successful for a portion of the protocol. This will improve the channel access opportunities for STAs and APs participating in TWT-based MAP coordination.

[0142] Unless otherwise specified, an element mentioned in the singular does not mean one and only one, but one or more. For example, a “one” module can refer to one or more modules. Without further restriction, an element beginning with “a,” “an,” “the,” or “the” does not exclude the existence of other identical elements.

[0143] Titles and subtitles (if any) are for convenience only and do not limit the invention. The word “exemplary” is used to indicate that it is an example or illustration. With regard to the use of terms such as “comprising,” “having,” etc., such terms are intended to encompass in a manner similar to how the term “comprising” is interpreted when used as a transitional word in a claim. Relational terms such as “first” and “second” can be used to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between these entities or actions.

[0144] Phrases such as "one aspect," "this aspect," "on the other hand," "some aspects," "one or more aspects," "an implementation," "this implementation," "another implementation," "some implementations," "one or more implementations," "an embodiment," "this embodiment," "another embodiment," "some embodiments," "one or more embodiments," "a configuration," "this configuration," "another configuration," "some configurations," "one or more configurations," "the subject matter," "disclosure," "this disclosure," and other variations thereof are used for convenience and do not imply that the disclosures associated with these phrases are necessary to the subject matter, nor do they imply that these disclosures are applicable to all configurations of the subject matter. The disclosures associated with these phrases can be applied to all configurations, or one or more configurations. The disclosures associated with these phrases can provide one or more examples. Phrases such as "one aspect" or "some aspects" can refer to one or more aspects, and vice versa, and this also applies to other foregoing phrases.

[0145] The phrase “at least one of” following a series of items, along with the terms “and” or “or” separating any items, modifies the entire list, not each member of the list. The phrase “at least one of” does not require the selection of at least one item; rather, it allows for the inclusion of any one of at least one items, and / or any combination of at least one items, and / or the meaning of each of at least one items. For example, each of the phrases “at least one of A, B, and C” or “at least one of A, B, or C” refers to only A, only B, or only C; any combination of A, B, and C; and / or at least one of A, B, and C.

[0146] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration of exemplary methods. Unless explicitly stated otherwise, it should be understood that the specific order or hierarchy of steps, operations, or processes may be performed in a different order. Some steps, operations, or processes may be performed simultaneously or as part of one or more other steps, operations, or processes. The appended method claims (if any) present elements of various steps, operations, or processes in an exemplary order and are not intended to limit one to the specific order or hierarchy presented. These may be performed serially, linearly, in parallel, or in a different order. It should be understood that the described instructions, operations, and systems may generally be integrated together in a single software / hardware product or packaged into multiple software / hardware products.

[0147] This disclosure is intended to enable any person skilled in the art to practice the aspects described herein. In some instances, to avoid obscuring the concepts of the subject matter, well-known structures and components are shown in block diagram form. This disclosure provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0148] All structural and functional equivalents of the elements of the aspects described in this disclosure that are known or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. No element expressly recited in the claims is subject to the provisions of paragraph 6 of 35 USC §112 unless the element is expressly expressed as “means for…” (or a similar phrase), or, in the case of a method claim, as “steps for…” (or a similar phrase).

[0149] The title, background art, description of the drawings, abstract, and figures are incorporated herein by reference as illustrative examples, not as limiting descriptions. It should be understood at the time of filing that they are not intended to limit the scope or meaning of the claims. Furthermore, in the detailed description, it will be apparent that illustrative examples are provided, and various features are combined in various implementations to simplify the disclosure. This approach to disclosure should not be construed as reflecting an intention that the claimed subject matter requires more features than expressly stated in each claim. Rather, as reflected in the appended claims, the inventive subject matter lies in all features of fewer than those in a single disclosed configuration or operation. The appended claims are thus incorporated into the detailed description, each claim itself as a separately claimed subject matter.

[0150] The claims are not intended to be limited to the aspects described herein, but rather to conform to the full scope consistent with the language claims and to include all legal equivalents. Nevertheless, no claim is intended to include subject matter that fails to meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. A first access point (AP) in a wireless network, comprising: Memory; and A processor coupled to the memory, the processor being configured such that: Establish multi-AP coordination with the second AP, the multi-AP coordination including a set of protocols established between the first AP and the second AP; and Send the first frame to the second AP requesting termination of one or more protocols established between the first AP and the second AP.

2. The first AP according to claim 1, wherein, The processor is also configured such that: Receive a second frame from the second AP indicating a response to the first frame, the second frame including a field indicating acceptance, rejection, or alternative proposal for a requested termination of at least one protocol between the first AP and the second AP.

3. The first AP according to claim 2, wherein, The first frame or the second frame includes a field indicating whether the request is to partially terminate the set of protocols or to completely terminate the set of protocols.

4. The first AP according to claim 2, wherein, The first or second frame includes a field indicating the type of multi-AP coordination.

5. The first AP according to claim 2, wherein, The first frame or the second frame includes a field indicating an identifier of the protocol to be terminated.

6. The first AP according to claim 1, wherein, The multi-AP coordination is based on the target wake-up time (TWT).

7. The first AP according to claim 3, wherein, When the field indicates that the request is partially terminated, a subset of the protocol requested by the first frame or the second frame is terminated.

8. A first access point (AP) in a wireless network, comprising: Memory; and A processor coupled to the memory, the processor being configured such that: Establish multi-AP coordination with the second AP, the multi-AP coordination including a set of protocols established between the first AP and the second AP; and The second AP receives a first frame requesting the termination of one or more protocols established between the first AP and the second AP.

9. The first AP according to claim 8, wherein, The processor is also configured such that: Send a second frame to the second AP indicating a response to the first frame, the second frame including a field indicating an acceptance, rejection, or alternative proposal for terminating at least one protocol between the first AP and the second AP.

10. The first AP according to claim 9, wherein, The first frame or the second frame includes a field indicating whether the request is to partially terminate the set of protocols or to completely terminate the set of protocols.

11. The first AP according to claim 9, wherein, The first or second frame includes a field indicating the type of multi-AP coordination.

12. The first AP according to claim 9, wherein, The first frame or the second frame includes a field indicating an identifier of the protocol to be terminated.

13. The first AP according to claim 8, wherein, The multi-AP coordination is based on the target wake-up time (TWT).

14. The first AP according to claim 10, wherein, When the field indicates that the request is partially terminated, a subset of the protocol requested by the first frame or the second frame is terminated.

15. A method performed by a first access point (AP) device in a wireless network, comprising: Establish multi-AP coordination with the second AP, the multi-AP coordination including a set of protocols established between the first AP and the second AP; and Send the first frame to the second AP requesting termination of one or more protocols established between the first AP and the second AP.

Images