TWT operation in wireless network

Abstract

An AP attached to a non-simultaneous transmit and receive (NSTR) mobile access point (AP) multilink device (MLD) and operating on a primary link may advertise a broadcast wake time (TWT) schedule for another AP attached to the same NSTR mobile AP MLD and operating on a non-primary link by including a target TWT element in an STA profile field per STA profile sub-element of a basic multilink element, the TWT element includes a corresponding broadcast TWT parameter set field, and the basic multi-link element corresponds to an AP operating on the main link and is carried in a beacon frame and / or a probe response frame that it transmits on the main link.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication systems, and more specifically, to target wake time (TWT) operation in wireless communication systems, for example, but not limited to. BACKGROUND

[0002] Wireless local area network (WLAN) technology has evolved toward increased data rates and has continued to grow in various markets such as home, enterprise, and hot spot since the late 1990s. A WLAN allows devices to access the Internet in 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands. A WLAN is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. The IEEE 802.11 family of standards aims to improve speed and reliability and extend the operating range of wireless networks.

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

[0004] MLO can enable a non-AP multi-link device (MLD) to establish multiple links with an AP MLD. Each of the multiple links can independently implement channel access and frame exchange between the non-AP MLD and the AP MLD, which can reduce latency and increase throughput.

[0005] The description set forth in the Background section is not an admission that any of the SUMMARY

[0006] One aspect of the disclosure provides an access point (AP) multi-link device (MLD) associated with a non-AP MLD in a wireless network. The AP MLD comprises at least two APs, each AP affiliated with the AP MLD; and a processor coupled to the at least two APs. The processor is configured to announce, by a first AP affiliated with the AP MLD and operating on a primary link established between the first AP and a first STA affiliated with the non-AP MLD, a broadcast target wake-up time (TWT) schedule for a second AP affiliated with the AP MLD and operating on a secondary link established between the second AP and the first STA, by including a TWT element in a broadcast frame via the primary link, the TWT element including a broadcast TWT parameter set field corresponding to the second AP operating on the secondary link.

[0007] In some embodiments, the broadcast TWT parameter set field is included in a station (STA) profile field of a per-STA profile sub-element of a basic multi-link element.

[0008] In some embodiments, the broadcast frame is a beacon frame or a probe response frame.

[0009] In some embodiments, a value in a broadcast TWT persistence subfield corresponding to the broadcast target wake-up time (TWT) schedule is with respect to a most recent target beacon transmission time (TBTT) and a beacon interval indicated by the first AP operating on the primary link.

[0010] In some embodiments, the AP MLD is a non-simultaneous transmit and receive (NSTR) mobile AP MLD.

[0011] In some embodiments, the processor is further configured to receive, by the second AP from the second STA, a TWT request to join the broadcast TWT schedule.

[0012] In some embodiments, the first AP is not in a multiple basic service set identifier (BSSID) set, or the first AP corresponds to a transmitted BSSID in the multiple BSSID set.

[0013] In some embodiments, the primary link and the secondary link are a non-simultaneous transmit and receive (NSTR) link pair.

[0014] One aspect of the disclosure provides an access point (AP) multi-link device (MLD) associated with a non-AP MLD in a wireless network. The AP MLD includes at least two APs each associated with the AP MLD, and a processor coupled to the at least two APs. The processor is configured to: include, by a first AP affiliated with the AP MLD, a basic multi-link element for the AP MLD in a broadcast frame, where the basic multi-link element does not include a link information field unless the AP MLD is a non-simultaneous transmit and receive (NSTR) mobile AP MLD and the first AP operates on a primary link established between the first AP and a first STA affiliated with the non-AP MLD; and advertise a broadcast target wake time (TWT) schedule for a second AP affiliated with the AP MLD and operating on a non-primary link. The processor is configured to transmit, by the first AP affiliated with the AP MLD, the broadcast frame.

[0015] In some embodiments, the first AP is not in a multiple basic service set identifier (BSSID) set, or the first AP corresponds to a transmitted BSSID in the multiple BSSID set.

[0016] In some embodiments, the broadcast frame is a beacon frame or a probe response frame.

[0017] In some embodiments, the probe response frame is not in a multi-link probe response transmitted by the first AP.

[0018] In some embodiments, when the first AP is affiliated with the NSTR mobile AP MLD and operates on the primary link and the first AP advertises the broadcast TWT schedule for the second AP, a station (STA) profile in a link formation field of the basic multi-link element includes only a broadcast TWT element for the second AP operating on the non-primary link.

[0019] One aspect of this disclosure provides a non-AP MLD associated with an Access Point (AP) Multilink Device (MLD) in a wireless network. The non-AP MLD includes at least two STAs, each attached to the non-AP MLD; and a processor coupled to the at least two STAs. The processor is configured to receive a broadcast frame via the main link from the first STA, which is attached to the non-AP MLD and operates on a main link established between a first STA and a first AP attached to the AP MLD. The broadcast frame announces a broadcast TWT schedule for a second AP, which is attached to the AP MLD and operates on a non-main link established between a second STA and a second AP attached to the AP MLD, by including a Target Wake-Up Time (TWT) element. The TWT element includes a broadcast TWT parameter set field corresponding to the second AP operating on the non-main link. The processor is configured to send a TWT request from the second STA, which is attached to the non-AP MLD and operates on the non-main link, to join the broadcast TWT schedule.

[0020] In some embodiments, the broadcast TWT parameter set field is included in the STA profile field of the per STA profile sub-element of the basic multilink element.

[0021] In some embodiments, the broadcast frame is a beacon frame or a probe response frame.

[0022] In some embodiments, the value in the broadcast TWT persistence subfield corresponding to the broadcast TWT scheduling is about the nearest target beacon transmission time (TBTT) and beacon interval indicated by the first AP operating on the main link.

[0023] In some embodiments, the AP MLD is a Non-Simultaneous Transmit and Receive (NSTR) Mobile AP MLD.

[0024] In some embodiments, the first AP is not in the multiple basic service set identifier (BSSID) set, or the first AP corresponds to a transmitted BSSID in the multiple BSSID set.

[0025] In some embodiments, the primary link and the secondary link are non-simultaneous transmit and receive (NSTR) link pairs. Attached Figure Description

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

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

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

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

[0030] Figure 4 An example NSTR operation according to an embodiment is shown.

[0031] Figure 5 An example procedure for broadcasting TWT scheduling for announcing NSTR mobile AP MLDs is shown according to an embodiment.

[0032] Figure 6 An example procedure for broadcasting TWT scheduling for announcing NSTR mobile AP MLDs is shown according to an embodiment.

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

[0034] Figure 8 An example format of a multi-link element according to an embodiment is shown.

[0035] Figure 9 An example procedure for announcing broadcast TWT scheduling for NSTR mobile AP MLD using aligned scheduling, according to an embodiment, is shown.

[0036] Figure 10 An example process for announcing broadcast TWT scheduling is shown according to an embodiment.

[0037] Figure 11 An example of aligned scheduling according to an embodiment is shown.

[0038] Figure 12 An example of establishing a broadcast TWT according to an embodiment is shown.

[0039] Figure 13 An example process for announcing broadcast TWT scheduling is shown according to an embodiment.

[0040] In one or more embodiments, not all components depicted in each figure are necessary, and one or more embodiments may include additional components not shown in the figures. Variations in the arrangement and type of components may be made without departing from the scope of this subject matter disclosure. Additional components, different components, or fewer components may be utilized within the scope of this subject matter disclosure. Detailed Implementation

[0041] The detailed description set forth below in conjunction with the accompanying drawings is intended to describe various embodiments and not to represent only possible embodiments in which the subject matter can be practiced. Rather, the detailed description includes specific details for the purpose of providing 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 description are to be considered illustrative rather than restrictive in nature. The same reference numerals denote the same elements.

[0042] For the purpose of describing the innovative aspects of the invention, the following description is directed to certain embodiments. 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 according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (including the IEEE 802.11 be standard and any future revisions to the IEEE 802.11 standard). However, the described embodiments can be implemented in any device, system, or network 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 Rev A, EV-DO Rev 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 used for communication within wireless, cellular, or Internet of Things (IoT) networks, such as systems utilizing 3G, 4G, 5G, 6G, or further implementations thereof.

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

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

[0045] 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.

[0046] 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 that serves as a separately addressable instance of an interface to the Media Access Control (MAC) layer and Physical (PHY) layer of the wireless medium. 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 a distribution system service to an associated STA via the wireless medium. A Non-AP STA may be a STA that is not included within 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 1In the example, APs 101 and 103 are wireless communication devices, each of which 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, each of which may include one or more non-AP STAs. In such an embodiment, STAs 111-114 may be non-AP MLDs.

[0047] 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 111-114 in a coverage area 120 with AP 101. APs 101 and 103 can communicate with each other and with STAs using Wi-Fi or other WLAN communication technologies.

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

[0049] exist Figure 1 In the diagram, the dashed lines indicate 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 the coverage areas associated with APs (such as coverage areas 120 and 125) can have other shapes, including irregular shapes, depending on the configuration of the APs.

[0050] As described in more detail below, one or more of the APs may include circuitry and / or programming for managing MU-MIMO and OFDMA channel detection in a WLAN. Although Figure 1 An example of a wireless network 100 is shown, but more details can be found on other wireless networks. Figure 1Various 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 those STAs 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.

[0051] 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 configurations. However, APs have a wide range of configurations, and Figure 2a This disclosure is not intended to limit the scope of any particular implementation of AP.

[0052] 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 (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.

[0053] 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 processed baseband or IF signals. RF transceivers 209a-209n receive the outgoing processed baseband or IF signals from TX processing circuit 214 and up-convert the baseband or IF signals into RF signals transmitted via antennas 204a-204n.

[0054] 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 reception of uplink signals and the transmission of downlink signals by the RF transceivers 209a-209n, the RX processing circuitry 219, and the TX processing circuitry 214 according to known principles. The controller / processor 224 may also support additional functions, such as more advanced wireless communication functions. 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 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 for different receivers (e.g., different STAs 111-114). The controller / processor 224 may support any of a wide variety of other functions in the AP 101, including combinations of DL MU-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.

[0055] 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 with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. 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, and another portion of memory 229 can include flash memory or other ROM.

[0056] 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 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 (such as one instance per RF transceiver). Alternatively, only one antenna and RF transceiver path may be included, as in a conventional AP. Furthermore, Figure 2a The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0057] 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.

[0058] 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 of any particular implementation of STA.

[0059] 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.

[0060] 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 IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 225 sends the processed baseband signals to speaker 230 (e.g., for voice data) or to controller / processor 240 for further processing (e.g., for web browsing data).

[0061] TX processing circuitry 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 circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 210 receives the outgoing processed baseband or IF signal from TX processing circuitry 215 and up-converts the baseband or IF signal into an RF signal transmitted via antenna 205.

[0062] 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 manage the channel detection process in a WLAN. In some embodiments, the controller / processor 240 may include at least one microprocessor or microcontroller.

[0063] The controller / processor 240 is also capable of executing other processes and programs residing in the memory 260, such as operations for managing channel sounding processes in a WLAN. The controller / processor 240 can move data into or out of the memory 260 as needed for the execution of processes. In some embodiments, the controller / processor 240 is configured to execute multiple applications 262, such as applications for channel sounding, including 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 STA111 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 245 is the communication path between these accessories and the main controller / processor 240.

[0064] The controller / processor 240 is also coupled to input 250 (e.g., a touchscreen) and display 255. An 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 and / or at least limited graphics from a website. Memory 260 is coupled to the controller / processor 240. A portion of memory 260 may include random access memory (RAM), and another portion of memory 260 may include flash memory or other read-only memory (ROM).

[0065] 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, you can combine, further subdivide, or omit. Figure 2b The STA 111 can include various components and additional components can be added as needed. In a specific example, the STA 111 may include any number of antennas 205 for MIMO communication with the AP 101. In another example, the 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.

[0066] 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.

[0067] 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.11 be standard and any future revisions of the IEEE 802.11 standard. Figure 3 In the middle, AP MLD 310 can be Figure 1 Wireless communication devices 101 and 103 are included, and the non-AP MLD 220 can be... Figure 1 One of the wireless communication devices 111-114 in the series.

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

[0069] 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 to the wireless medium (Link 1, Link 2, or Link 3). A non-AP MLD 320 may include a single MAC SAP 328, through which affiliated STAs communicate with higher layers (Layer 3 or network layer). Each affiliated STA of a non-AP MLD 320 may have a different MAC address (lower MAC address) than any other affiliated STA of the non-AP MLD 320. A 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.

[0070] AP MLD 310 and non-AP MLD 320 can establish multiple links between 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, which can increase data throughput and reduce latency. When associated with an AP MLD on a set of links (setup links), each non-AP device is assigned a unique Association Identifier (AID).

[0071] The following documents are incorporated herein by reference in their entirety, as if fully set forth herein: i) IEEE 802.11-2020, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification” and ii) IEEE P 802.11be / D3.0, “Wireless LAN Media Access Control (MAC) and Physical Layer (PHY) Specification”.

[0072] Target Wake-Up Time (TWT) operation is a feature of power management in WLAN networks. TWT operation was introduced in the IEEE 802.11ah standard and later modified in the IEEE 802.11ax standard. TWT operation enables the AP to manage activity within a Basic Service Set (BSS) to minimize contention between STAs and reduce the wake-up time required by STAs during TWT operations. This is achieved by allocating STAs to operate at non-overlapping times or frequencies and executing frame exchange sequences within pre-scheduled service periods. During TWT operation, a STA can wake up at a pre-scheduled time negotiated with another STA in the AP or BSS. 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 that the TWT service period (SP) is 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 that have established a corresponding TWT agreement or TWT scheduling, including but not limited to HE MU (High Efficiency Multi-User) PPDU and HE TB (High Efficiency Triggered) PPDU.

[0073] The IEEE 802.11 standard describes two types of TWT operations: standalone TWT operations and broadcast TWT operations. In a standalone TWT operation, a separate TWT agreement can be established between two STAs or between a STA and an AP. Negotiation for a standalone TWT operation can occur on a separate basis between two STAs or between a STA and an AP. An AP can have TWT agreements with multiple STAs. Any change to the TWT agreement between an AP and one STA does not affect the TWT agreements between the AP and other STAs.

[0074] On the other hand, broadcast TWTs operate on a membership-based 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 the broadcast TWT schedule, or the AP can send an unsolicited response to an STA to make the STA a member of the 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.

[0075] AP MLDs are typically capable of transmitting and receiving frames simultaneously on all their links. However, the current version of the IEEE 802.11 be standard defines a special type of AP MLD called a "Non-Simultaneous Transmit and Receive (NSTR) Mobile AP MLD," which is a mobile AP MLD with NSTR link pairs. In this disclosure, a mobile AP refers to an AP that is able to maintain the operational availability of its Basic Service Set (BSS) when its location changes. Two types of links are defined for an NSSTR mobile AP MLD: the primary link and the non-primary link. Beacon frames or probe response frames can only be transmitted via the primary link and not via the non-primary link. Furthermore, when transmitting PPDUs via the non-primary link, an AP attached to an NSTR mobile AP MLD operating on the non-primary link, or a non-AP STA attached to a non-AP MLD associated with an NSTR mobile AP MLD and operating on the non-primary link, needs to align the PPDU with the PPDU transmitted via the primary link.

[0076] Figure 4 An example NSTR 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 particular implementation.

[0077] exist Figure 4 In this model, AP MLD 410 includes auxiliary AP 1 and AP 2, and non-AP MLD 420 includes auxiliary STA 1 and STA 2. Figure 4 In this example, AP MLD 410 is an NSTR mobile AP MLD. An NSTR link pair is established between AP MLD 410 and non-AP MLD 420. Specifically, a primary link is established between AP 1 and STA 1, while a non-primary link is established between AP 2 and STA 2. AP MLD 410 and non-AP MLD 420 exchange PPDUs on both the primary and non-primary links. However, PPDUs sent from AP 2 and STA 2 on the non-primary link are aligned with those sent on the primary link.

[0078] In current WLAN systems, broadcast TWT scheduling can be announced by the TWT scheduling AP by including the corresponding TWT element in the beacon frame or probe response frame sent by the TWT scheduling AP. However, APs attached to the NSTR mobile AP MLD and operating on non-primary links do not send beacon frames or probe response frames. Therefore, in current WLAN systems, there is no mechanism for announcing broadcast TWT scheduling for non-primary links used by the NSTR mobile AP MLD.

[0079] This disclosure provides various example procedures for broadcast TWT operations with NSTR mobile AP MLD.

[0080] In some embodiments, an AP attached to an NSTR mobile AP MLD and operating on a non-primary link can announce broadcast TWT scheduling for the non-primary link by carrying TWT elements (including the corresponding broadcast TWT scheduling) in beacon frames and / or probe response frames sent on the primary link. This is because there are no beacons on the non-primary link of the NSTR mobile AP MLD. Therefore, broadcast TWT scheduling for the non-primary link can be announced by an AP operating on the primary link at the NSTR mobile AP MLD.

[0081] Figure 5 An example procedure for broadcast TWT scheduling to notify NSTR mobile AP MLDs according to an embodiment is shown. For purposes of explanation and illustration, example procedure 500 may be provided by Figure 4 AP 1 and AP 2 are depicted in the diagram. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods.

[0082] refer to Figure 4 and Figure 5 Process 500 can begin in operation 501. In operation 501, the NSTR moves the MLD (e.g., Figure 4 The AP MLD 410 in the document intends to announce the broadcast TWT scheduling for non-master links.

[0083] In Operation 503, an AP attached to an NSTR mobile AP MLD and operating on the main link (e.g., Figure 4 AP1 in the text represents an AP that is attached to the same NSTR mobile AM ​​MLD and operates on a non-master link (e.g., Figure 4 AP 2) announces the broadcast TWT schedule on the main link.

[0084] In some embodiments, broadcast TWT scheduling for non-primary links can be advertised by including a corresponding TWT element in the per-STA profile sub-element transmitted on the primary link. Specifically, an AP attached to an NSTR mobile AP MLD and operating on the primary link can advertise broadcast TWT scheduling for APs attached to the same NSTR mobile MLD and operating on non-primary links. This can be achieved by including a TWT element in the STA profile field of the per-STA profile sub-element of the basic multilink element, which includes a corresponding broadcast TWT parameter set field. The corresponding broadcast TWT parameter set field corresponds to the AP operating on the non-primary link and is carried in beacon frames and / or probe response frames transmitted on the primary link. The value in the broadcast TWT persistence sub-field corresponding to the broadcast TWT scheduling can be related to the nearest target beacon transmission time (TBTT) and beacon interval (BI) indicated by the AP operating on the primary link.

[0085] Figure 6 An example procedure for broadcast TWT scheduling to notify NSTR mobile AP MLDs according to an embodiment is shown. For purposes of explanation and illustration, example procedure 600 may be provided by Figure 4 AP 1 and AP 2 are depicted in the diagram. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 6 The process in the document illustrates an example of announcing a broadcast TWT schedule for a non-master link by including the corresponding TWT element in the sub-element of each STA profile sent on the master link.

[0086] refer to Figure 4 and Figure 6 Process 600 can begin in operation 601. In operation 601, the NSTR moves the MLD (e.g., Figure 4 The AP MLD 410 in the document intends to announce the broadcast TWT scheduling for non-master links.

[0087] In Operation 603, an AP attached to an NSTR mobile AP MLD and operating on the main link (e.g., Figure 4 AP1 in the network can advertise to APs attached to the same NSTR mobile MLD and operating on a non-primary link (e.g., Figure 4The broadcast TWT scheduling for AP 2) in the basic multilink element is achieved by including a TWT element in the STA profile field of each STA profile sub-element within the link info field of the basic multilink element. This TWT element includes the corresponding broadcast TWT parameter set field. The corresponding broadcast TWT parameter set 1 field corresponds to APs operating on non-primary links and is carried in beacon frames and / or probe response frames sent on the primary link.

[0088] In some embodiments, if an AP attached to an NSTR mobile AP MLD and operating on the primary link advertises broadcast TWT scheduling for an AP attached to the same NSTR mobile MLD and operating on a non-primary link, this can be achieved by including a TWT element in the per-STA profile field of the per-STA profile sub-element of the basic multilink element, the TWT element including a corresponding broadcast TWT parameter set field. The basic multilink element corresponds to the AP operating on the non-primary link and is carried in a beacon frame or probe response frame on the primary link. In this scenario, timing fields (such as a target wake-up time field) in the TWT element can be related to the TSF of the primary link. In one embodiment, timing fields in the TWT element can be related to the TSF of the non-primary link.

[0089] In some embodiments, an AP attached to an NSTR mobile AP MLD and operating on the primary link advertises a TWT schedule on the primary link, which is an aligned schedule. Since an NSTR mobile AP MLD can have up to two links (e.g., a primary link and a non-primary link), the advertisement of an aligned schedule on the primary link may mean that the TWT schedule is also available on the non-primary link.

[0090] In some embodiments, if an AP attached to an NSTR mobile AP MLD and operating on the primary link intends to advertise a broadcast TWT schedule to an AP attached to the same NSTR mobile AP MLD and operating on a non-primary link, then the AP operating on the primary link can advertise the broadcast TWT schedule on the primary link, and indicate that the broadcast TWT schedule is an aligned schedule, for example, by setting the alignment subfield of the request type field in the corresponding broadcast TWT parameter set field to 1. Since an NSTR mobile AP MLD can have up to two links (primary link and non-primary link), the non-AP MLD associated with the NSTR mobile AP MLD that receives the announcement of an aligned schedule via a beacon frame or probe response frame on the primary link can uniquely identify the existence of an aligned TWT schedule on the non-primary link.

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

[0092] exist Figure 4In the TWT element 700, an element identifier (ID) field, a length field, a control field, and a TWT parameter information field may be included. The element ID field may include information used to identify the TWT element 700. The length field indicates the length of the TWT element 700.

[0093] 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 the presence of an NDP paging field 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 separate TWT or Wake-up TBTT (Target Beacon Transmission Time) intervals. The MSB (Most Significant Bit) of the Negotiation Type subfield is a 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 disables 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 parameter set field. The OBSS R-TWT subfield indicates whether the R-TWT schedule corresponding to the broadcast TWT parameter set field in the TWT element is an R-TWT schedule for an adjacent BS. When the OBSS R-TWT subfield is set to '1', it indicates that the R-TWT schedule in the TWT element is an R-TWT schedule for an adjacent BS. Otherwise, it indicates that there is no R-TWT schedule for an adjacent BSS in the TWT element.

[0094] TWT parameter information fields include individual parameter set fields or one or more broadcast TWT parameter set fields. For ease of description, Figure 11 The broadcast TWT parameter set field is shown. The broadcast TWT parameter set field 710 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 service information field.

[0095] The request type field in broadcast TWT parameter set field 710 can be used to indicate the presence of an aligned TWT schedule. (See reference...) Figure 11The request type field includes the TWT request subfield, TWT setting 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.

[0096] 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 Set Command subfield indicates the type of TWT command, such as request TWT, suggest TWT, demand TWT, TWT grouping, accept TWT, replace TWT, dictate 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 another broadcast TWT parameter set field follows this broadcast TWT parameter set field. The Flow Type subfield indicates the type of interaction, such as whether it's an advertised or unadvertised TWT at the TWT between a TWT scheduling STA and a TWT scheduling AP. The Broadcast TWT Recommendation subfield indicates a recommendation regarding the type of frames sent by the TWT scheduling STA and the TWT scheduling AP during the broadcast TWT SP. For example, the frame type could be PS polling and QoS empty frames, management frames, control response frames, or no constraints on the frame. The TWT wake-up interval index subfield indicates the value of the index of the TWT wake-up interval value. The alignment subfield indicates whether one or more other links of the AP MLD have a broadcast TWT schedule aligned with the corresponding schedule. More specifically, if the subfield is set to 1, it indicates that one or more schedules aligned with the TWT schedule identified by the broadcast TWT parameter set field exist on other links. Otherwise, the schedule is not such a schedule on other links. As described above, in some embodiments, if an AP attached to an NSTR mobile AP MLD and operating on the primary link intends to advertise a broadcast TWT schedule for an AP attached to the same NSTR mobile AP MLD and operating on a non-primary link, then the AP operating on the primary link can advertise the broadcast TWT schedule on the primary link, and indicate that the broadcast TWT schedule is aligned, for example, by setting the alignment subfield of the request type field in the corresponding broadcast TWT parameter set field to 1.

[0097] The Target Wake-up Time field may include an unsigned integer corresponding to the TSF (Time Synchronization Function) time for STA wake-up used for TWT scheduling. The Target Wake-up Time field indicates the start time of the TWT Service Period (SP) on the corresponding link. The Nominal Minimum TWT Wake-up Duration field indicates the minimum amount of time expected for a TWT-scheduled STA 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 successive TWT SPs for a TWT-scheduled STA. The TWT Wake-up Interval Tail field indicates the tail value of the TWT Wake-up Interval. The Broadcast TWT Information field may include information related to the broadcast TWT, such as the Restricted TWT Service Information Presence field, the Restricted TWT Scheduling Information field, the Broadcast TWT ID field, and the Broadcast TWT Persistence field. The Restricted TWT Service Information Presence field indicates whether the Restricted TWT Service Information field exists. The Restricted 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 Persistence field indicates the number of Broadcast TWT SPs that exist during the TBTT period, corresponding to the Broadcast TWT parameter set.

[0098] Figure 11 An example format of a multi-link element according to an embodiment is shown.

[0099] exist Figure 4 In this implementation, the multilink element 800 includes an element identifier (ID) field, a length field, an element ID extension field, a multilink control field, a common information field, and a link information field. The element ID field and the element ID extension field may include information used to identify the multilink element 800. The length field indicates the length of the TWT element 800. The multilink control field may include a type field indicating the type of the multilink element 800. In some implementations, the value of the type field indicates that the multilink element 800 is a basic multilink element. The common information field may include information common to all links with some exceptions.

[0100] The link information field may include information specific to one or more links, and may optionally be present. The link information field may include one or more per-STA profile sub-elements. Figure 11An example per-STA profile sub-element is shown included in the link information field of a basic multilink element. The per-STA profile sub-element may include a sub-element ID field, a length field, an STA control field, an STA information field, and an STA profile field. The sub-element ID field may include information for identifying the per-STA profile sub-element. The length field may indicate the length of the per-STA profile sub-element. The STA control field may include control information for the basic multilink element. The STA profile field may include various information. In some embodiments, an AP attached to an NSTR mobile AP MLD and operating on the primary link may advertise a broadcast TWT schedule for an AP attached to the same NSTR mobile MLD and operating on a non-primary link. This can be achieved by including a TWT element in the STA profile field of the per-STA profile sub-element within the link information field of the basic multilink element, the TWT element including a corresponding broadcast TWT parameter set field. The broadcast TWT parameter set field corresponds to another AP operating on a non-primary link and is carried in beacon frames and / or probe response frames transmitted on the primary link.

[0101] Figure 10 An example procedure for announcing broadcast TWT scheduling for NSTR mobile AP MLD using aligned scheduling, according to an embodiment, is shown. For purposes of explanation and illustration, example procedure 900 can be provided by... Figure 12 AP 1 and AP 2 are depicted in the diagram. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods.

[0102] refer to Figure 12 and Figure 12 Process 900 can begin in operation 901. In operation 901, the NSTR moves the MLD (e.g., Figure 11 The AP MLD 410 in the document intends to announce the broadcast TWT scheduling for non-master links.

[0103] In Operation 903, APs attached to the NSTR Mobile AP MLD and operating on the main link (e.g., Figure 12 AP1 in the middle announces the broadcast TWT schedule on the main link and indicates that the broadcast TWT schedule is an aligned schedule.

[0104] In some embodiments, the STA is attached to a non-AP MLD associated with the NSTR Mobile MLD and operates on a non-primary link. When the STA sends a TWT request to an AP attached to the NSTR Mobile MLD and operating on a non-primary link, or when the STA requests membership for alignment scheduling on a non-primary link, the STA can use the same broadcast TWT ID used to identify alignment scheduling advertised on the primary link.

[0105] Figure 13 An example procedure for announcing broadcast TWT scheduling according to an embodiment is shown. For purposes of explanation and illustration, example procedure 1000 may be provided by... Figure 4 STA 1 and STA 2 are depicted in the diagram. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 13 The process in the document illustrates an example of using aligned scheduling to announce broadcast TWT scheduling for non-master links used by NSTR mobile AP MLDs.

[0106] refer to Figure 4 and Figure 13 Process 1000 can begin in operation 1001. In operation 1001, non-AP MLDs (e.g., Figure 4 The non-AP MLD 420 in the NSTR mobile AP MLD (e.g., Figure 4 This is associated with AP MLD 410. Non-APMLDs intend to establish broadcast TWT scheduling on non-master links.

[0107] In operation 1003, STAs attached to non-AP MLDs and operating on the main link (e.g., Figure 4 STA 1) receives a broadcast TWT schedule announcement via the main link. In some embodiments, the announcement may include an indication that the broadcast TWT schedule is an aligned schedule. For example, the broadcast TWT ID of an aligned schedule announced on the main link may be set to B1.

[0108] In operation 1005, STAs attached to non-AP MLDs and operating on non-master links (e.g., Figure 4 STA 2) in the NSTR moves to the MLD attached to the NSTR via a non-primary link and operates on the non-primary link (e.g., Figure 4 AP 2) sends a TWT request. The TWT request requests to become a member of the alignment schedule. The broadcast TWTID of the broadcast TWT schedule that sends the request can be the same as B1.

[0109] Figure 4 An example of aligned scheduling according to an embodiment is shown.Figure 11 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0110] refer to Figure 11 An NSTR link pair, including both primary and non-primary links, is established between AP MLD 410 and non-AP MLD 420. AP MLD 410 is an NSTR mobile AP MLD. Figure 11 The difference lies in the establishment of the non-primary link between AP 1 and STA 1, and the primary link between AP 2 and STA 2. As shown in the diagram, a broadcast TWT schedule A ("Schedule-A") is established on the non-primary link between AP 1 and STA 1, while a broadcast TWT schedule B ("Schedule-B") is established on the primary link between AP 2 and STA 1. Schedule-A and Schedule-B are aligned with each other. Figure 4 In this context, scheduler-A and scheduler-B can have the same TWT parameter, including the broadcast TWT ID, as shown in the reference. Figure 11 The explanation given.

[0111] In some embodiments, if the primary link has a second broadcast TWT schedule, the NSTR mobile AP MLD may announce or establish a first broadcast TWT schedule for the non-primary link via the primary link, such that the start and end times of the TWT SP corresponding to the first broadcast TWT schedule on the non-primary link overlap in time with the TWT SP corresponding to the second TWT schedule on the primary link.

[0112] Figure 10 An example of establishing a broadcast TWT according to an embodiment is shown. Figure 12 The operations described herein are for illustrative purposes and do not limit the scope of this disclosure to any particular implementation.

[0113] In addition to the TWT SP duration Figure 12 Examples are similar to Figure 12 Example. See reference. Figure 11 Schedule-A and Schedule-B are aligned in their TWT SP start times, but the TWT SP duration of Schedule-B is longer than that of Schedule-A. The start and end times of the TWT SP of Schedule-A overlap with those of Schedule-B. In this scenario, AP MLD 410 can advertise or establish Schedule-A for non-primary links via the primary link.

[0114] In some embodiments, an AP attached to an NSTR mobile AP MLD intends to announce broadcast TWT scheduling for a non-primary link by including a corresponding TWT element in a beacon frame or probe response frame transmitted on the primary link. This TWT element includes a corresponding broadcast TWT parameter set field. The AP may include a link information field in the basic multilink element for an AP attached to an NSTR mobile AP MLD and operating on a non-primary link.

[0115] In some embodiments, an AP attached to an NSTR mobile AP MLD and operating on the primary link can announce a broadcast TWT schedule for another AP attached to the same NSTR mobile AP MLD and operating on a non-primary link by including a TWT element in the STA profile field of each STA profile sub-element of the basic multilink element. This TWT element includes a corresponding broadcast TWT parameter set field, and the basic multilink element corresponds to the AP operating on the primary link, beacon frames, and probe response frames it transmits on the primary link. The value in the broadcast TWT persistence sub-field corresponding to the broadcast TWT schedule should be related to the most recent TBTT and beacon interval indicated by the AP operating on the primary link.

[0116] In some embodiments, if the AP attached to the AP MLD is not in a multi-BSSID set, or if the AP corresponds to a transmitted BSSID in a multi-BSSID set, the AP may selectively include or exclude the link information field for the basic multi-link elements of the AP MLD in the beacon frame and / or probe response frame (which is not a multi-link probe response it transmitted). In some implementations, the AP may exclude the link information field for the basic multi-link elements of the AP MLD unless the AP is attached to an NSTR mobile AP MLD and operates on the primary link, and advertises a broadcast TWT schedule for another AP attached to the same NSTR mobile AP MLD and operating on a non-primary link. In this case, the link information field only includes the broadcast TWT element for the AP operating on the non-primary channel. In some implementations, if the AP is attached to an NSTR mobile AP MLD and operates on the primary link, the AP may include the link information field for the basic multi-link elements of the AP MLD and advertise a broadcast TWT schedule for other APs attached to the same NSTR mobile AP MLD and operating on the primary link. In this case, the link information field only includes the broadcast TWT element for APs operating on non-primary links.

[0117] In some embodiments, broadcast TWT scheduling for an AP advertised to an NSTR mobile AP MLD and operating on a non-primary link is aligned with broadcast TWT scheduling for another AP advertised to an AP advertised to the same NSTR mobile AP MLD and operating on the primary link.

[0118] Figure 12 An example procedure for announcing broadcast TWT scheduling according to an embodiment is shown. For purposes of explanation and illustration, example procedure 1300 may be provided by... Figure 13 STA 1 and STA 2 are depicted in the diagram. Although one or more operations are described or shown in a specific order, in other embodiments, the operations may be rearranged in a different order, which may include performing multiple operations in at least partially overlapping time periods. Figure 4 The process in the diagram illustrates the general operation of establishing a broadcast TWT schedule for a non-AP MLD to a non-primary link of an NSTR mobile AP MLD.

[0119] refer to Figure 13 and Figure 4 Process 1300 can begin in operation 1301. In operation 1301, non-AP MLDs (e.g., Figure 13 The non-AP MLD 420 in the NSTR mobile AP MLD (e.g., Figure 4 This is associated with AP MLD 410. Non-APMLDs intend to establish broadcast TWT scheduling on non-master links.

[0120] In operation 1303, STAs attached to non-AP MLDs and operating on the main link (e.g., Figure 4 STA 1) receives a broadcast TWT scheduling announcement via the primary link. In some embodiments, the TWT element, including the corresponding broadcast TWT parameter set field, is included in the STA profile field of each STA profile sub-element within the link info field of the basic multilink element. The basic multilink element corresponds to an AP operating on a non-primary link and is carried in beacon frames and / or probe response frames transmitted on the primary link.

[0121] In operation 1305, STAs attached to non-AP MLDs and operating on non-master links (e.g., Figure 4 STA 2) in the NSTR moves to the MLD attached to the NSTR via a non-primary link and operates on the non-primary link (e.g., Figure 4 Figure 4 AP 2) Sends a TWT request. A TWT request can request to become a member of the broadcast TWT scheduler.

[0122] Unless otherwise stated, references to elements in the singular form are not intended to refer to one and only one, but rather to one or more. For example, a “one” module can refer to one or more modules. Without further constraints, elements beginning with “a,” “an,” “the,” or “the” do not exclude the existence of other identical elements.

[0123] Titles and subtitles (if any) are used for convenience only and do not limit the invention. The word "exemplary" is used to mean as an example or illustration. Within the scope of the use of the terms "comprising," "having," etc., such terms are intended to be inclusive in a manner similar to the term "comprising," as "comprising" is interpreted when used as a transitional word in the claims. Relational terms such as "first" and "second" may 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.

[0124] Phrases such as aspect, that aspect, on the other hand, some aspects, one or more aspects, implementation, that implementation, another implementation, some implementations, one or more implementations, implementation, that implementation, another implementation, some implementations, one or more implementations, configuration, that configuration, another configuration, some configurations, one or more configurations, subject matter, this disclosure, this disclosure, other variations thereof, etc., are for convenience and do not imply that the disclosure associated with such phrases is essential to the subject matter, or that such disclosure applies to all configurations of the subject matter. Disclosures associated with such phrases may apply to all configurations or one or more configurations. Disclosures associated with such phrases may provide one or more examples. Phrases such as aspect or some aspects may refer to one or more aspects, and this similarly applies to other foregoing phrases.

[0125] The phrase “at least one of…” preceding a list of items (where the terms “and” or “or” are used to separate any of the items) modifies the list as a whole, not each member of the list. The phrase “at least one of…” does not require selection of at least one item; rather, the phrase allows for the meaning of at least one of any of the items, and / or at least one of any combination of the items, and / or at least one of each of the 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 each of A, B, and C.

[0126] It should be understood that the specific order or hierarchy of the disclosed steps, operations, or processes is an illustration of exemplary methods. Unless otherwise expressly stated, 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 the elements of various steps, operations, or processes in a sample 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 different orders. 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.

[0127] This disclosure is provided to enable any person skilled in the art to practice the various aspects described herein. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring the concepts of the subject matter. 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 apparent to those skilled in the art, and the principles described herein can be applied to other aspects.

[0128] All structural and functional equivalents of elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, and such structural and functional equivalents are known to or will be known hereafter by one of ordinary skill in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims. No claim element should be construed under paragraph 6 of 35 U.S.SC §112, unless it is explicitly stated using a phrase or, in the case of a method claim, is stated using a phrase step.

[0129] The title, background art, description of the drawings, abstract, and figures are incorporated herein by reference and are provided as illustrative examples rather than 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 the description provides illustrative examples, and various features are grouped together in various embodiments for the purpose of simplifying the disclosure. The method of this disclosure should not be construed as reflecting an intention to require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in all features of fewer than those in a single disclosure configuration or operation. The appended claims are thus incorporated into the detailed description, wherein each claim is independently claimed as a separate subject matter.

[0130] 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 cover all legal equivalents. Nevertheless, the claims are not intended to include subject matter that does not meet the requirements of applicable patent law, nor should they be interpreted in this manner.

Claims

1. An AP MLD associated with a non-access point (AP) multi-link device (MLD) in a wireless network, the AP MLD comprising: At least two APs, each AP attached to AP MLD; and A processor, coupled to at least two APs, is configured as follows: A first AP, which is attached to an AP MLD and operates on a main link established between a first AP and a first STA, which is attached to a non-AP MLD, announces a broadcast TWT schedule for a second AP, which is attached to an AP MLD and operates on a non-AP MLD, by including a Target Wake-Up Time (TWT) element in a broadcast frame via the main link. The TWT element includes a broadcast TWT parameter set field corresponding to the second AP operating on the non-AP MLD.

2. The AP MLD according to claim 1, wherein, The broadcast TWT parameter set field is included in the STA profile field of the per-station STA profile sub-element of the basic multilink element.

3. The AP MLD according to claim 1 or claim 2, wherein, Broadcast frames are either beacon frames or probe response frames.

4. The AP MLD according to any one of the preceding claims, wherein, The value in the Broadcast TWT Persistence subfield corresponding to the Broadcast Target Wake-up Time (TWT) scheduling is about the nearest target beacon transmission time (TBTT) and beacon interval indicated by the first AP operating on the main link.

5. The AP MLD according to any one of the preceding claims, wherein, AP MLD is a non-simultaneous transmit and receive NSTR mobile AP MLD.

6. The AP MLD according to any one of the preceding claims, wherein, The processor is also configured to receive TWT requests from the second STA via the second AP to join the broadcast TWT schedule.

7. The AP MLD according to any one of the preceding claims, wherein, The first AP is not in the multi-basic service set identifier (BSSID) set, or the first AP corresponds to a transmitted BSSID in the multi-BSSID set.

8. The AP MLD according to any one of the preceding claims, wherein, The primary link and the secondary link are non-simultaneous transmission and reception NSTR link pairs.

9. A non-AP MLD associated with an access point (AP) multi-link device (MLD) in a wireless network, the non-AP MLD comprising: At least two STAs, each attached to a non-AP MLD; and The processor, coupled to at least two STAs, is configured as follows: A first STA, which is attached to a non-AP MLD and operates on a main link established between a first STA and a first AP attached to an AP MLD, receives a broadcast frame via the main link. The broadcast frame announces a broadcast TWT schedule for a second AP, which is attached to an AP MLD and operates on a non-main link established between a second STA and a second AP attached to an AP MLD, by including a Target Wake-Up Time (TWT) element. The TWT element includes a broadcast TWT parameter set field corresponding to the second AP operating on the non-main link. and A second STA, attached to a non-AP MLD and operating on a non-master link, sends a TWT request to join the broadcast TWT schedule.

10. The non-AP MLD according to claim 9, wherein, The broadcast TWT parameter set field is included in the STA profile field of each STA profile sub-element of the basic multilink element.

11. The non-AP MLD according to claim 9 or claim 10, wherein, Broadcast frames are either beacon frames or probe response frames.

12. The non-AP MLD according to any one of claims 9 to 11, wherein, The value in the Broadcast TWT Persistence subfield corresponding to the Broadcast TWT scheduling is about the nearest target beacon transmission time (TBTT) and beacon interval indicated by the first AP operating on the main link.

13. The non-AP MLD according to any one of claims 9 to 12, wherein, AP MLD is a non-simultaneous transmit and receive NSTR mobile AP MLD.

14. The non-AP MLD according to any one of claims 9 to 13, wherein, The first AP is not in the multi-basic service set identifier (BSSID) set, or the first AP corresponds to a transmitted BSSID in the multi-BSSID set.

15. The non-AP MLD according to any one of claims 9 to 14, wherein, The primary link and the secondary link are non-simultaneous transmission and reception NSTR link pairs.

Images