Integrated millimeter wave (IMMW) beam training for multi-link operation (MLO)

Abstract

The present disclosure provides methods, components, devices, and systems for integrated millimeter wave (IMMW) beam training for multi-link operations. Some aspects more specifically relate to beam sweeping and reporting for cooperating 60-gigahertz (GHz) and sub-7 GHz links. In some implementations, an access point (AP) multi-link device (MLD) can communicate with a non-AP MLD via a first omni-directional link, such as a sub-7 link, and a second directional link, such as a 60 GHz link. The AP MLD can use the omni-directional link to configure one or more parameters and report feedback for the directional link. For example, the AP MLD can send, to the non-AP MLD via the first link, an indication of a timing synchronization function (TSF) value associated with the second link of the AP MLD. The AP MLD and the non-AP MLD can use the TSF value to support beam training operations for the second link.

Description

Priority information

[0001] This patent application claims priority to U.S. Patent Application No. 19 / 075,531, filed March 10, 2025, entitled “INTEGRATEDMILLIMETER WAVE (IMMW) BEAM TRAINING FOR MULTI-LINK OPERATION (MLO),” which claims the benefit of U.S. Provisional Patent Application No. 63 / 563,795, filed March 11, 2024, entitled “INTEGRATEDMILLIMETER WAVE (IMMW) BEAM TRAINING FOR MULTI-LINK OPERATION (MLO),” each of which is assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates in general to wireless communications, and more specifically to integrated millimeter-wave (IMMW) beam training for multi-link operation (MLO). Background Technology

[0003] Wireless communication networks are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. Some wireless communication networks can support communication with multiple users by sharing available system resources, such as time, frequency, or power. Furthermore, wireless communication networks can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). Wireless communication devices can communicate using any one or more of these wireless communication technologies and may include radio stations (STAs), radio access points (APs), user equipment (UEs), network entities, or other wireless nodes. Summary of the Invention

[0004] The systems, methods, and apparatus disclosed herein each have some innovative aspects, but no single aspect is solely responsible for the desired properties disclosed herein.

[0005] One innovative aspect of the subject matter described in this disclosure can be implemented in a non-access point (AP) multilink device (MLD). The non-AP MLD may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the non-AP MLD to: communicate with an AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and obtain, via the first link, an indication of a first timing synchronization function (TSF) value associated with a second link between the AP MLD and the non-AP MLD. The processing system may also be configured to cause the non-AP MLD to: communicate with the AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0006] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at a non-AP MLD. The method may include: communicating with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and receiving, via the first link, an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD. The method may further include: communicating with the AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicating with the AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0007] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-AP MLD. The non-AP MLD may include: components for communicating with an AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and components for receiving, via the first link, an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD. The non-AP MLD may also include: components for communicating with the AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and components for communicating with the AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: communicate with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and receive, via the first link, an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD. The code may also include instructions executable by the one or more processors to: communicate with the AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0009] Some specific implementations of the non-AP MLD, methods, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting or otherwise outputting the one or more scan packets, wherein the one or more scan packets comprise a set of multiple scan packets associated with a set of multiple corresponding transmit beams for the beam scanning process, and wherein scan packets for the set of multiple scan packets transmit a corresponding TSF value from a set of multiple TSF values, and the report can be obtained based on the beam scanning process.

[0010] Some specific implementations of the non-AP MLD, method, and non-transitory computer-readable medium described herein may also include operations, features, components, or instructions for selecting a transmit beam for the second link corresponding to the scan packet in the one or more scan packets, based on a report indicating a second TSF value associated with the reception of the scan packet.

[0011] Some specific implementations of the non-AP MLD, methods, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving or otherwise acquiring the one or more scan packets for the beam scanning process, wherein the one or more scan packets are associated with one or more corresponding TSF values, and the report is output based on the acquisition of the one or more scan packets and the scan packets satisfying a signal strength threshold.

[0012] Some specific implementations of the non-AP MLD, methods, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for operating in a non-standalone (NSA) mode, wherein the first link includes a partner link for the second link in the NSA mode.

[0013] Some specific implementations of the non-AP MLD, method, and non-transitory computer-readable medium described herein may also include operations, features, components, or instructions for triggering the beam scanning process based on the establishment associated with the AP MLD, an inactive timer for the non-AP MLD, a reference signal indicating beam misalignment for the second frequency band, or any combination thereof.

[0014] Another innovative aspect of the subject matter described in this disclosure can be implemented in an AP MLD. The AP MLD may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the AP MLD to: communicate with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and output an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD via the first link. The processing system may also be configured to cause the AP MLD to: communicate with the non-AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0015] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication at an AP MLD. The method may include: communicating with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and transmitting via the first link an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD. The method may further include: communicating with the non-AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicating with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0016] Another innovative aspect of the subject matter described in this disclosure can be implemented in an AP MLD. The AP MLD may include: components for communicating with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and components for transmitting an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD via the first link. The AP MLD may also include: components for communicating with the non-AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and components for communicating with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication based on the beam scanning process and the first TSF value associated with the second link.

[0017] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: communicate with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; and transmit via the first link an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD. The code may also include instructions executable by the one or more processors to: communicate with the non-AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

[0018] Some specific implementations of the AP MLD, methods, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting or otherwise outputting the one or more scan packets, wherein the one or more scan packets comprise a set of multiple scan packets associated with a set of multiple corresponding transmit beams for the beam scanning process, and wherein scan packets for the set of multiple scan packets transmit a corresponding TSF value from a set of multiple TSF values, and the report is obtained based on the beam scanning process.

[0019] Some specific implementations of the AP MLD, method, and nontransitory computer-readable medium described herein may also include operations, features, components, or instructions for selecting a transmit beam for the second link corresponding to the scan packet in the one or more scan packets, based on a report indicating a second TSF value associated with the reception of the scan packet.

[0020] Some specific implementations of the AP MLD, methods, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving or otherwise acquiring the one or more scan packets for the beam scanning process, wherein the one or more scan packets are associated with one or more corresponding TSF values, and the report is output based on the acquisition of the one or more scan packets and the scan packets satisfying a signal strength threshold.

[0021] Details of one or more specific embodiments of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0022] Figure 1 A schematic diagram of an example wireless communication network is shown.

[0023] Figure 2 An example Protocol Data Unit (PDU) is shown that can be used for wireless communication between a wireless access point (AP) and one or more wireless stations (STA).

[0024] Figure 3 An example physical layer (PHY) protocol data unit (PPDU) capable of being used for wireless communication between a wireless AP and one or more wireless STAs is shown.

[0025] Figure 4 An example of a signaling diagram is shown that supports integrated millimeter-wave (IMMW) beam training for multi-link operation (MLO).

[0026] Figure 5 An example of a signaling timeline supporting IMW beam training for MLO is shown.

[0027] Figure 6 An example of a report format supporting IMW beam training for MLO is shown.

[0028] Figure 7 An example of a preemption process supporting IMW beam training for MLO is shown.

[0029] Figure 8 and Figure 9 A block diagram of an example wireless communication device supporting IMMW beam training for MLO is shown.

[0030] Figure 10A flowchart illustrating an example process that can be executed by a non-AP multi-link device (MLD) that supports IMW beam training for MLO, or that can be executed at such a non-AP MLD, is shown.

[0031] Figure 11 A flowchart illustrating an example process that can be executed by an AP MLD that supports IMMW beam training for MLO, or that can be executed at that AP MLD, is shown.

[0032] Similar reference numerals and names in the various figures indicate similar elements. Detailed Implementation

[0033] The following description refers to certain specific examples in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some or all of the examples described can be applied in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or Bluetooth as defined by the Bluetooth Special Interest Group (SIG). ® This can be implemented in any device, system, or network that transmits and receives radio frequency (RF) signals according to one or more of the standards or those published by the 3rd Generation Partnership Project (3GPP), such as Long Term Evolution (LTE), 3G, 4G, 5G (New Radio (NR)), or 6G. The described examples can be implemented in any suitable device, component, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiplexing (OFDM), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Space Division Multiple Access (SDMA), Rate Split Multiple Access (RSMA), Multi-User Shared Access (MUSA), Single-User (SU) Multiple-Input Multiple-Output (MIMO), and Multi-User (MU)-MIMO (MU-MIMO). The described examples can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of the following: Wireless Personal Area Network (WPAN), Wireless Local Area Network (WLAN), Wireless Wide Area Network (WWAN), Wireless Metropolitan Area Network (WMAN), Non-Terrestrial Network (NTN), or Internet of Things (IoT) networks.

[0034] In some WLANs, wireless communication devices can operate via the 60 GHz band. For example, a wireless communication device can transmit radio signals between 30 GHz and 300 GHz, with wavelengths between 1 mm and 10 mm, such as via the 60 GHz band. This type of communication with wavelengths between 1 mm and 10 mm can be referred to as millimeter-wave (mmW) communication. WLANs supporting this type of mmW communication can use integrated mmW (IMMW) technology to support operation via the 60 GHz band. Wireless communication devices can use directional communication to manage the relatively high attenuation loss associated with the 60 GHz band. To support directional communication, wireless communication devices can perform beam scanning operations (such as beam training) to select the directional beam to be used for communication. However, such beam scanning operations can involve significant processing and signaling overhead.

[0035] The various aspects collectively relate to IMW beam training for multi-link operation (MLO). Some aspects more specifically involve beam scanning and reporting processes using cooperative links, such as 60 GHz and sub-7 GHz links. A sub-7 link can be an example of a wireless communication link that supports communication via an operating channel with an operating frequency below 7 GHz (such as the 2.4 GHz band, 5 GHz band, or 6 GHz band). In some specific implementations, an Access Point (AP) Multilink Device (MLD) can communicate with a non-AP MLD via a first link and a second link. The first link (such as a sub-7 link or another link) can support omnidirectional communication, while the second link (such as a 60 GHz link or another link) can support directional beam-based communication. The AP MLD can use the omnidirectional link to configure one or more parameters for the directional link. For example, the AP MLD can send an indication to the non-AP MLD via the first link of a Timing Synchronization Function (TSF) value associated with the second link of the AP MLD. TSF can be an example of a mechanism for synchronizing timing between wireless communication devices in some wireless communication systems, such as Wi-Fi systems. The TSF value can be an indication (e.g., a value in microseconds) of a timestamp of a timer (such as a TSF timer) at the wireless communication device. In some implementations, the TSF value can be an example of a TSF offset value between a first link and a second link (e.g., the difference in microseconds between a TSF timer that tracks timing synchronization of the first link and a TSF timer that tracks timing synchronization of the second link). AP MLDs and non-AP MLDs can use the TSF value to support beam training operations for the second link. In some implementations, AP MLDs can use a sub7 link to configure the timing for transmitting scan packets for a beam scanning process via the 60 GHz band. The indicated TSF value ensures coordination between the scan packet transmission timing and scan packet reception timing of AP MLDs and non-AP MLDs. In some implementations, AP MLDs, non-AP MLDs, or both can use short scan packets that can be identified based on the scan packet reception timing rather than information included within the scan packet. Additionally or alternatively, the MLD may use a sub7 link to provide feedback for beam scanning procedures performed via the 60 GHz band. In some implementations, the AP MLD may perform transmit beam scanning procedures for multiple non-AP MLDs during a transmit period that is common to multiple non-AP MLDs. Non-AP MLDs may monitor the 60 GHz band during the common transmit period and may aggregate the corresponding beam training feedback for reporting via the sub7 link. Additionally or alternatively, the AP MLD may periodically send updated TSF information to non-AP MLDs via the sub7 link or the 60 GHz link.

[0036] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some specific implementations, by indicating the TSF value via a sub7 link, the AP MLD can improve timing coordination between the AP MLD and non-AP MLDs for the 60 GHz beam training process. Such timing coordination can support scan packets that can be identified based on the reception timing rather than information included in the scan packet. Therefore, the described techniques can support reducing the size of the scan packets used for transmit beam scanning by removing training sequences, sector identifier information, or both from the scan packets. Reducing the scan packet size can reduce latency and improve the signaling overhead associated with beam scanning processes for the 60 GHz band. Additionally or alternatively, by performing transmit beam scanning via the 60 GHz band during common transmit periods, the AP MLD can improve the processing and signaling overhead associated with beam training processes for multiple non-AP MLDs. In some implementations, the AP MLD, non-AP MLD, or both can facilitate the timely delivery of beam training feedback via sub7 link aggregation feedback reports, thereby improving latency associated with the beam training process for the 60 GHz link. Additionally or alternatively, by sending updated TSF information, the AP MLD can prevent clock drift, thereby improving timing coordination between the AP MLD and non-AP MLD.

[0037] Figure 1A schematic diagram of an example wireless communication network 100 is shown. Depending on some aspects, the wireless communication network 100 may be an example of a WLAN (such as a Wi-Fi network). For example, the wireless communication network 100 may be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as those defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bc, 802.11bd, 802.11be, 802.11bf, 802.11bn, and the upcoming 802.11bq standard). In some other specific implementations, the wireless communication network 100 may be an example of a cellular radio access network (RAN), such as a 5G or 6G RAN implementing one or more cellular protocols (such as those specified in one or more 3GPP standards). In some other embodiments, the wireless communication network 100 may include a WLAN that operates interoperably or convergently with one or more cellular RANs to provide greater or enhanced network coverage to wireless communication devices within the wireless communication network 100, or to enable such devices to connect to the core of the cellular network, such as to access network management capabilities and functionality provided by the cellular network core. In some other embodiments, the wireless communication network 100 may include a WLAN that operates interoperably or convergently with one or more personal area networks (such as networks implementing Bluetooth or other wireless technologies) to provide greater or enhanced network coverage or to provide or implement other capabilities, functionalities, applications, or services.

[0038] Wireless communication network 100 may include numerous wireless communication devices, including at least one access point (AP) 102 and any number of radio stations (STAs) 104. Although Figure 1 Only one AP 102 is shown, but the wireless communication network 100 may include multiple APs 102. AP 102 can be or represent various different types of network entities, including but not limited to home networking APs, enterprise-grade APs, single-band APs, dual-band synchronous (DBS) APs, tri-band synchronous (TBS) APs, standalone APs, non-standalone APs, software-enabled APs (software APs), and multi-link APs (also known as AP MLDs), as well as cellular (such as 3GPP, 4G LTE, 5G, or 6G) base stations or other cellular network nodes (such as Node Bs, evolved Node Bs (eNBs), gNBs, Transmitter Receiver Points (TRPs)) or another type of equipment or apparatus included in the RAN, including open RAN (O-RAN) network entities such as central units (CUs), distributed units (DUs), or radio units (RUs). AP 102 may be referred to as an AP STA or AP MLD, etc.

[0039] Each STA in STA 104 can also be referred to as a mobile station (MS), mobile device, mobile phone, wireless phone, access terminal (AT), user equipment (UE), subscriber station (SS), subscriber unit, non-AP STA, or non-AP MLD, etc. STA 104 can represent a variety of devices such as mobile phones, other handheld or wearable communication devices, netbooks, laptops, tablets, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR), or extended reality (XR) wireless headsets or other peripherals, wireless earbuds, other wearable devices, display devices (e.g., televisions, computer monitors, or video game consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators) or other home appliances, remote keys (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, vehicles, etc.

[0040] A single AP 102 and its associated set of STA 104s may be referred to as a Basic Service Set (BSS), which is managed by the respective AP 102. Figure 1 Additionally, an example coverage area 108 of AP 102 is shown, which may represent the Basic Service Area (BSA) of wireless communication network 100. The BSA can be identified by STA 104 and other devices via a Service Set Identifier (SSID) and a Basic Service Set Identifier (BSSID), which may be the Media Access Control (MAC) address of AP 102. AP 102 may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STA 104 within the wireless range of AP 102 to “associate” or reassociate with AP 102 to establish or maintain a corresponding communication link 106 with AP 102 (also referred to hereinafter as a “Wi-Fi link”). For example, the beacon may include an identifier or indication of the primary channel used by the corresponding AP 102, and a Timing Synchronization Function (TSF) or TSF value for establishing or maintaining timing synchronization with AP 102. AP 102 can provide access to external networks to each STA 104 in the wireless communication network 100 via the corresponding communication link 106.

[0041] To establish a communication link 106 with AP 102, each STA 104 is configured to perform passive or active scanning operations (“scanning”) on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform a passive scan, STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (referred to as the Target Beacon Transmission Time (TBTT)). To perform an active scan, STA 104 generates probe requests and transmits these requests sequentially via each channel to be scanned, and listens for probe responses from AP 102. Each STA 104 can identify, determine, determine, or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and can perform authentication and association operations to establish a communication link 106 with the selected AP 102. The selected AP102 assigns an association identifier (AID) to STA 104 at the end of the association operation, and AP 102 uses the association identifier (AID) to track STA 104.

[0042] As wireless networks become increasingly prevalent, STA 104 may have the opportunity to choose from one of many BSSs within its range or from multiple APs 102 that together form an Extended Service Set (ESS) (comprising multiple connected BSSs). For example, wireless communication network 100 may be connected to a wired or wireless distribution system capable of connecting multiple APs 102 in such an ESS. Therefore, STA 104 may be covered by more than one AP 102 and may be associated with different APs 102 at different times for different transmissions. Additionally, after associating with an AP 102, STA 104 may periodically scan its surroundings to find a more suitable AP 102 to associate with. For example, STA 104 moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 with more desirable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0043] In some implementations, STA 104 may form a network without AP 102 or other equipment besides STA 104 itself. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may also be referred to as mesh networks or peer-to-peer (P2P) networks. In some implementations, ad hoc networks may be implemented within a larger network, such as wireless communication network 100. In some such implementations, while STA 104 may be able to communicate with each other via communication link 106 through AP 102, STA 104 may also communicate directly with each other via direct wireless communication link 110. Additionally, two STA 104 may communicate via direct wireless communication link 110, regardless of whether the two STA 104 are associated with and served by the same AP 102. In such ad hoc systems, one or more STAs among STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi direct connections, connections established by using Wi-Fi Tunneling Direct Link Establishment (TDLS) links, and other P2P group connections.

[0044] In some networks, AP 102 or STA 104, or both, can support applications associated with high throughput or low latency requirements, or provide lossless audio to one or more other devices. For example, AP 102 or STA 104 can support applications and use cases associated with ultra-low latency (ULL), such as ULL gaming, or streaming lossless audio and video to one or more personal audio devices (such as peripherals) or AR / VR / MR / XR headsets. In scenarios where a user uses two or more peripherals, AP 102 or STA 104 can support extended personal audio networks that enable communication with these two or more peripherals. Additionally, AP 102 and STA 104 can support additional ULL applications with ULL and high throughput requirements, such as cloud-based applications (such as VR cloud gaming).

[0045] As indicated above, in some implementations, AP 102 and STA 104 may operate and communicate according to one or more of the IEEE 802.11 wireless communication protocol standard family (via the corresponding communication link 106). These standards define WLAN radio and baseband protocols for the physical (PHY) layer and MAC layer. AP 102 and STA 104 transmit and receive wireless communications to and from each other in the form of PHY Protocol Data Units (PPDUs) (also referred to below as "Wi-Fi communication" or "wireless packets").

[0046] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In instances where the PPDU is transmitted via a bonded channel or a wideband channel, the preamble field can be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble can be used for packet detection, automatic gain control (AGC), and channel estimation, among other purposes. The legacy preamble is also typically used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-legacy portion of the preamble are associated with the specific IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0047] AP 102 and STA 104 in wireless communication network 100 can transmit PPDUs on unlicensed spectrum, which may be a portion of the spectrum including frequency bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands. Some examples of AP 102 and STA 104 described herein can also communicate in other frequency bands that can support both licensed and unlicensed communication. For example, AP 102 or STA 104, or both, may also be able to communicate on licensed operating frequency bands, where multiple operators may have corresponding licenses to operate in the same or overlapping frequency ranges. Such licensed operating frequency bands may be specified or associated with frequency ranges mapped to or associated with FR1 (410MHz to 7.125GHz), FR2 (24.25GHz to 52.6GHz), FR3 (7.125GHz to 24.25GHz), FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz), and FR5 (114.25GHz to 300GHz).

[0048] Each of these frequency bands may include multiple sub-bands and frequency channels (also referred to as sub-channels). The terms "channel" and "sub-channel" are used interchangeably herein, as each can refer to a portion of the spectrum within the frequency band (e.g., a 20MHz, 40MHz, 80MHz, or 160MHz portion of the spectrum) through which communication between two or more wireless communication devices can occur. For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn standards can be transmitted on one or more of the 2.4GHz, 5GHz, or 6GHz frequency bands, each of which is divided into multiple 20MHz channels. Thus, these PPDUs are transmitted via physical channels with a minimum bandwidth of 20MHz, but larger channels can be formed through channel bonding. For example, a PPDU can be transmitted on a physical channel with bandwidths of 40MHz, 80MHz, 160MHz, 240MHz, 320MHz, 480MHz, or 640MHz by bundling multiple 20MHz channels together.

[0049] AP 102 can determine or select the operating bandwidth for STA 104 in its BSS, and select a range of channels within that bandwidth to provide the operating bandwidth. For example, AP 102 can select sixteen 20MHz channels that collectively span a 320MHz operating bandwidth. Within the operating bandwidth, AP 102 typically selects a single primary 20MHz channel on which AP 102 and STA 104 in its BSS monitor contention-based access schemes. In some specific implementations, AP 102 or STA 104 may be able to monitor only a single primary 20MHz channel for packet detection (e.g., for detecting preambles of PPDUs). Under normal circumstances, any transmission by AP 102 or STA 104 within the BSS must involve transmission on the primary 20MHz channel. Therefore, in a conventional system, the transmitting device must compete for and win a Transmit Opportunity (TXOP) on the primary channel to make any transmission. However, some AP 102 and STA104 devices supporting Ultra-High Reliability (UHR) communication or communication revised according to the IEEE 802.11bn standard can be configured to operate, monitor, compete for, and communicate using multiple primary 20MHz channels. This monitoring of multiple primary 20MHz channels can be sequential, such that in response to determining, identifying, or detecting that a first primary 20MHz channel is unavailable, the wireless communication device can switch to monitoring and competing using a second primary 20MHz channel. Additionally or alternatively, the wireless communication device can be configured to monitor multiple primary 20MHz channels in parallel. In some implementations, the first primary 20MHz channel may be referred to as the main primary (M-primary) channel, and one or more additional secondary primary channels may each be referred to as opportunistic primary (O-primary) channels. For example, if the wireless communication device measures, identifies, identifies, detects, or otherwise determines that the M-primary channel is busy or occupied (e.g., due to overlapping BSS (OBSS) transmissions), the wireless communication device can switch to monitoring and competing on the O-primary channel. In some implementations, the M primary channel can be used for beacon transmission and servicing legacy client equipment, while the O primary channel can be dedicated by non-legacy (e.g., UHR or IEEE 802.11bn compatible) equipment to opportunistically access spectrum that may otherwise be underutilized.

[0050] Figure 2 An example protocol data unit (PDU) 200 capable of wireless communication between a wireless access point (AP) and one or more wireless STAs is shown. For example, the AP and STA can be reference... Figure 1Examples of AP 102 and STA 104 are described. PDU 200 can be configured as a PPDU. As shown, PDU 200 includes a PHY preamble (such as preamble 202) and a PHY payload (such as payload 204). For example, preamble 202 may include a legacy portion, which itself includes a legacy short training field (L-STF) 206 consisting of two symbols, a legacy long training field (L-LTF) 208 consisting of two symbols, and a legacy signal field (L-SIG) 210 consisting of two symbols. The legacy portion of preamble 202 may be configured according to the IEEE 802.11a wireless communication protocol standard. Preamble 202 may also include a non-legacy portion, which includes one or more non-legacy fields 212, for example, conforming to one or more of the IEEE 802.11 series of wireless communication protocol standards.

[0051] L-STF 206 generally enables receiving devices (such as AP 102 or STA 104) to perform coarse timing and frequency tracking, as well as AGC. L-LTF 208 generally enables receiving devices to perform fine timing and frequency tracking, and also to perform initial estimation of the radio channel. L-SIG 210 generally enables receiving devices to determine (e.g., acquire, select, identify, detect, determine, calculate, or compute) the duration of the PDU and use the determined duration to avoid transmission over the PDU. The legacy portion of the preamble can be modulated according to a binary phase shift keying (BPSK) modulation scheme, including L-STF 206, L-LTF 208, and L-SIG 210. The payload 204 can be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another suitable modulation scheme. Payload 204 may include a PSDU containing a data field (DATA) 214, which in turn may carry higher-level data in the form of, for example, MAC Protocol Data Unit (MPDU) or Aggregated MPDU (A-MPDU).

[0052] Figure 3 An example PPDU350 is shown, capable of wireless communication between a wireless AP and one or more wireless STAs. For example, the AP and STA can be references. Figure 1Examples of AP 102 and STA 104 are described below. As shown, PPDU 350 includes a PHY preamble (which includes a legacy portion 352 and a non-legacy portion 354) and a payload 356 (which includes a data field 374). The legacy portion 352 of the preamble includes L-STF 358, L-LTF 360, and L-SIG 362. The non-legacy portion 354 of the preamble includes a repetition of L-SIG (RL-SIG) 364 and multiple wireless communication protocol version-related signal fields following RL-SIG 364. For example, the non-legacy portion 354 may include a general signal field (referred to herein as "U-SIG 366") and an EHT signal field (referred to herein as "EHT-SIG 368"). The presence of RL-SIG 364 and U-SIG 366 indicates to STA 104, which is EHT compliant or later, that PPDU 350 is an EHT PPDU or any later (post-EHT) version of a PPDU conforming to a new wireless communication protocol (conforming to the future IEEE 802.11 wireless communication protocol standard). One or both of U-SIG 366 and EHT-SIG 368 can be constructed as other wireless communication protocol versions associated with revisions to the IEEE series of standards above EHT and carry version-related information for those protocol versions. For example, U-SIG 366 can be used by receiving devices (such as AP102 and STA 104) to interpret bits in one or more of EHT-SIG 368 or data field 374. Similar to L-STF358, L-LTF 360, and L-SIG 362, in instances involving the use of bonded channels, the information in U-SIG 366 and EHT-SIG368 can be repeated and transmitted via each of the component 20MHz channels in the component 20MHz channel.

[0053] The non-legacy portion 354 also includes additional short training fields (referred to herein as "EHT-STF 370," but which can be constructed for other wireless communication protocol versions above EHT and carry version-specific information for those versions) and one or more additional long training fields (referred to herein as "EHT-LTF 372," but which can be constructed for other wireless communication protocol versions above EHT and carry version-specific information for those versions). EHT-STF 370 can be used for timing and frequency tracking as well as AGC, and EHT-LTF 372 can be used for more refined channel estimation.

[0054] EHT-SIG 368 can be used by AP 102 to identify one or more STAs 104 and to notify those STAs that AP 102 has scheduled uplink or downlink resources for them. EHT-SIG 368 can be decoded by each compatible STA 104 served by AP 102. EHT-SIG 368 can generally be used by the receiving device to interpret the bits in data field 374. For example, EHT-SIG 368 may include resource element (RU) allocation information, spatial flow configuration information, and per-user (e.g., STA-specific) signaling information. Each EHT-SIG 368 may include a common field and at least one user-specific field. In the context of OFDMA, the common field may indicate the RU distribution across multiple STAs 104, indicate RU assignment in the frequency domain, indicate which RUs are allocated for MU-MIMO transmission and which RUs correspond to OFDMA transmission, as well as the number of users in the allocation, and other examples. User-specific fields are assigned to specific STA 104 and carry STA-specific scheduling information, such as user-specific modulation and decoding scheme (MCS) values ​​and user-specific RU allocation information. This information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 374.

[0055] Access to a shared wireless medium is typically managed by a Distributed Coordination Function (DCF). With DCF, there is generally no centralized master device allocating time and frequency resources for the shared wireless medium. Instead, a wireless communication device (such as an AP102 or STA 104) can wait for a specific time and compete for access to the wireless medium before being permitted to transmit data. DCF is implemented using time intervals, such as time slot times (or “time slot intervals”) and inter-frame gaps (IFS) . IFS provides priority access for control frames used for proper network operation. Transmission can begin at time slot boundaries. Different variations of IFS exist, including Short IFS (SIFS), Distributed IFS (DIFS), Extended IFS (EIFS), and Arbitrated IFS (AIFS). Values ​​for time slot times and IFS can be provided by appropriate standard specifications, such as one or more of the IEEE 802.11 series of wireless communication protocol standards.

[0056] In some specific implementations, wireless communication devices (such as AP 102 or STA 104) can achieve DCF using Carrier-Sensed Multiple Access (CSMA) with Collision Avoidance (CA) (CSMA / CA) technology. According to such technology, before transmitting data, the wireless communication device can perform an idle channel assessment (CCA) and determine (e.g., identify, detect, ascertain, calculate, or compute) whether the relevant wireless channel is idle. CCA includes both physical (PHY-level) carrier sensing and virtual (MAC-level) carrier sensing. Physical carrier sensing is accomplished by measuring the received signal strength of valid frames and comparing it to a threshold to determine (e.g., identify, detect, ascertain, calculate, or compute) whether the channel is busy. For example, if the received signal strength of the detected preamble is higher than a threshold, the medium is considered busy. Physical carrier sensing also includes energy detection. Energy detection involves measuring the total energy received by the wireless communication device, regardless of whether the received signal represents a valid frame. If the detected total energy is higher than a threshold, the medium is considered busy.

[0057] Virtual carrier sensing is implemented using a Network Allocation Vector (NAV), which effectively serves as the elapsed time duration before a wireless communication device can compete for access, even in the absence of detected symbols or even when the detected energy is below a relevant threshold. The NAV is reset each time a valid frame not addressed to the wireless communication device is received. When the NAV reaches 0, the wireless communication device performs physical carrier sensing. If the channel remains idle for the appropriate Inception Frequency (IFS), the wireless communication device initiates a backoff timer, which represents the elapsed time duration during which the device senses the medium is idle before being allowed to transmit. If the channel remains idle until the backoff timer expires, the wireless communication device becomes the holder (or "owner") of the TXOP and can begin transmitting. The TXOP is the elapsed time duration during which the wireless communication device can transmit frames via the channel after it has "won" contention for the wireless medium. The TXOP duration can be indicated in the U-SIG field of the PPDU. Conversely, if one or more carrier sensing mechanisms in the carrier sensing mechanism indicate that the channel is busy, the MAC controller within the wireless communication device will not allow transmission.

[0058] Some APs and STAs (e.g., reference) Figure 1The described AP 102 and STA 104 implement techniques for spatial reuse involving coordinated communication schemes. According to such techniques, AP 102 can compete for access to a wireless medium to gain control of that medium for use in the TXOP. The AP that wins the competition (also referred to hereinafter as the "sharing AP") can select one or more other APs (also referred to hereinafter as the "shared AP") to share the TXOP resources. The sharing AP and the shared APs can be located close to each other such that at least some of their wireless coverage areas at least partially overlap. Some examples may specifically involve coordinated AP TDMA or OFDMA techniques for sharing time or frequency resources of the TXOP. To share the time or frequency resources of the TXOP, the sharing AP can divide the TXOP into multiple time segments or frequency segments, each time segment or frequency segment including a corresponding time or frequency resource representing a portion of the TXOP. The sharing AP can allocate the time or frequency segment to itself or to one or more of the shared APs. For example, each shared AP can use a portion of the TXOPs assigned by the shared AP to perform uplink or downlink communication with its associated STA.

[0059] In some specific implementations of this type of TDMA technology, each of the multiple parts of the TXOP includes a set of time resources that do not overlap with any other time resources in the set of multiple parts of the TXOP. In such implementations, scheduling information may include indications of the time resources associated with each part of the TXOP among the multiple time resources. For example, scheduling information may include indications of time segments of the TXOP (such as indications of one or more time slots or sets of symbol periods associated with each part of the TXOP), such as for use in multi-user TDMA.

[0060] In some implementations, the shared AP may perform polling of a set of unmanaged or non-co-managed APs that support coordinated reuse to identify candidates for future space reuse opportunities. For example, the shared AP may send one or more space reuse polling frames to determine one or more space reuse criteria and select one or more other APs as part of the shared APs. Based on the polling, the shared AP may receive responses from one or more of the polled APs. In some specific examples, the shared AP may send a Coordinating AP TXOP Indication (CTI) frame to other APs, indicating the time and frequency of resources for a shared TXOP. The shared AP may select one or more candidate APs upon receiving a Coordinating AP TXOP Request (CTR) frame from the corresponding candidate AP, indicating that the corresponding AP expects to participate in the TXOP. The polling response or CTR frame may include power indications, such as received (RX) power or RSSI measured by the corresponding AP. In some other implementations, the shared AP may directly measure potential interference with services (such as uplink transmissions) supported at one or more APs and select the shared APs based on the measured potential interference. Shared APs typically select an AP to participate in coordinated space reuse, allowing it to still protect its own outgoing traffic and transmissions from STAs in its BSS (these transmissions may be referred to as primary transmissions). As described above, resources can be allocated to the selected AP during TXOP.

[0061] APs and STAs including multiple antennas (e.g., reference) Figure 1 The described AP 102 and STA 104 can support various diversity schemes. For example, spatial diversity can be used by one or both of the transmitting devices (such as AP 102 or STA 104) or receiving devices (such as AP 102 or STA 104) to improve transmission robustness. For example, to implement a transmit diversity scheme, the transmitting devices can redundantly transmit the same data on two or more antennas.

[0062] The AP 102 and STA 104, which include multiple antennas, also support Space-Time Block Decoding (STBC). Using STBC, the transmitting device also transmits multiple copies of the data stream across multiple antennas to increase the likelihood of correctly decoding the data by utilizing various received versions of the data. More specifically, the data stream to be transmitted is encoded in blocks, which are distributed across spaced antennas and over time. Generally, when the number of transmitting antennas... Exceeding the number of spatial flows STBC can be used at this time. A spatial flow can be mapped to a specific number of ( ) spacetime streams, which are then mapped to One sending chain.

[0063] The AP 102 and STA 104, which include multiple antennas, also support spatial multiplexing, which can be used to improve the spectral efficiency of transmission and the resulting throughput. To achieve spatial multiplexing, the transmitting device divides the data stream into numerous... These are separate, independent spatial streams. These spatial streams are then encoded individually and transmitted via multiple... The transmitting antennas transmit in parallel.

[0064] The AP 102 and STA 104, which include multiple antennas, also support beamforming. Beamforming generally refers to directing transmitted energy in the direction of the target receiver. Beamforming can be used in single-user (SU) environments (e.g., to improve the signal-to-noise ratio (SNR)) or multi-user (MU) environments (e.g., to enable MU-MIMO transmission (also known as spatial division multiple access (SDMA))). In the MU-MIMO context, beamforming may additionally or alternatively involve canceling energy in the direction of other receiving devices. To perform SU beamforming or MU-MIMO, the transmitting device (called a beamformer) transmits a signal from each of the multiple antennas. The beamformer configures the amplitude and phase shift between the signals transmitted from the different antennas such that these signals are constructively added along a specific direction toward the intended receiver (called a beamformer receiver), or destructively added in other directions toward other devices, to mitigate interference in the MU-MIMO context. The way beamformers configure amplitude and phase shift depends on the channel state information (CSI) associated with the wireless channel on which the beamformer is designed to communicate with the beamforming receiver.

[0065] To obtain CSI for beamforming, the beamformer can perform a channel sounding process with the beamforming receiver. For example, the beamformer can send one or more sounding signals (e.g., in the form of empty data packets (NDPs)) to the beamforming receiver. An NDP is a PPDU without any data field. The beamforming receiver can then target the corresponding transmit and receive antenna pairs associated with the sounding signals. x Measurements are performed on each of the sub-channels. The beamforming receiver generates a feedback matrix associated with the channel measurements and typically compresses this feedback matrix before sending the feedback to the beamformer. The beamformer can generate a pre-decoding (or “guide”) matrix for the beamforming receiver associated with this feedback and uses this guide matrix to pre-decode the data stream to configure amplitude and phase shift for subsequent transmissions to that beamforming receiver. The beamformer can use the guide matrix to determine (e.g., identify, detect, determine, calculate, or compute) how to transmit signals using each antenna in the beamformer's antenna array to perform beamforming. For example, the guide matrix can indicate the phase shift or power level at which each antenna in the antenna array used to transmit a corresponding signal using the beamformer.

[0066] In some implementations, multiple APs 102 can concurrently transmit signaling or communication to a single STA 104 using a distributed MU-MIMO scheme. Examples of such distributed MU-MIMO transmissions include coordinated beamforming (CBF) and joint transmission (JT). With CBF, a signal (such as a data stream) for a given STA 104 can be transmitted by only a single AP 102. However, the coverage areas of adjacent APs may overlap, and a signal transmitted by a given AP 102 may arrive as an OBSS signal at a STA in an OBSS associated with an adjacent AP. CBF allows multiple adjacent APs to transmit concurrently while minimizing or avoiding interference, potentially creating more opportunities for spatial reuse. More specifically, using CBF, AP 102 can beamform a signal to STA 104 within the BSS while simultaneously creating nulls in the direction of the STA in the OBSS, ensuring that any signal received at the OBSS STA has sufficiently low power to limit interference at the STA. To achieve this, an inter-BSS coordination set can be defined between adjacent APs, which contains the identifiers of all APs and STAs participating in CBF transmission.

[0067] Using JT, a signal for a given STA 104 can be transmitted by multiple coordinated APs 102. To enable multiple APs 102 to transmit data concurrently to STA 104, all APs 102 may use a copy of the data to be transmitted to STA 104. Therefore, APs 102 can exchange data with each other to transmit to STA 104. Using JT, the combination of antennas of multiple APs 102 transmitting to one or more STAs 104 can be considered as a large antenna array (which can be represented as a virtual antenna array) for beamforming and signal transmission. Combined with MU-MIMO technology, the multiple antennas of multiple APs 102 can be able to transmit data via multiple spatial streams. Therefore, each STA 104 can receive data via one or more of the multiple spatial streams.

[0068] In some wireless communication systems, AP 102 can allocate or assign multiple RUs to a single STA 104 in OFDMA transmissions (hereinafter also referred to as "multi-RU aggregation"). Multi-RU aggregation, which facilitates puncturing and scheduling flexibility, can ultimately reduce latency. With emerging standards such as the IEEE 802.11be revision supporting 320MHz and the IEEE 802.11bn revision supporting 480MHz and 640MHz, various combinations of multiple RUs (multi-RUs) may exist. Values ​​indicating various multi-RU combinations can be provided by appropriate standard specifications, such as one or more of the IEEE 802.11 family of wireless communication protocol standards, including the 802.11be and 802.11bn revisions.

[0069] Since Wi-Fi is not the only technology operating in the 6 GHz band, combining channel puncturing with multiple RUs enables the use of large bandwidths, making high throughput possible, while avoiding transmissions on locally unlicensed frequencies due to existing operations. Punching can also be combined with multi-RU transmissions to enable the establishment of wide channels using discontinuous spectrum blocks. In such examples, a portion of the bandwidth between two RUs allocated to a specific STA 104 can be punctured. Accordingly, spectral efficiency and flexibility are improved.

[0070] As previously described, STA-specific RU allocation information can be included in the signaling fields of the PPDU preamble (such as the EHT-SIG field for EHT PPDUs). Preamble puncturing enables wider bandwidth transmission in the presence of interference from existing technologies and other wireless communication devices, thereby improving throughput and spectral efficiency. Because RUs can be allocated individually in MU PPDUs, the use of the MU PPDU format can indicate preamble puncturing for SU transmissions. While puncturing in the IEEE 802.11ax standard revision is limited to OFDMA transmissions, the IEEE 802.11be standard revision extends puncturing to SU transmissions. In some implementations, RU allocation information in the common fields of EHT-SIG can be used to allocate RUs individually to a single user, thereby avoiding punctured channels. In some other implementations, U-SIG can be used to indicate SU preamble puncturing. For example, SU preamble puncturing can be indicated by the value of the EHT-SIG compression field in U-SIG.

[0071] Some APs and STAs (such as references) Figure 1The described AP 102 and STA 104 are capable of MLO (Multi-Level Logging). For example, AP 102 and STA 104 may support MLO as defined in one or both of the IEEE 802.11be and 802.11bn standard revisions. Devices with MLO capability may be referred to as MLDs. In some specific implementations, MLO supports the establishment of multiple different communication links between MLDs (such as a first link on the 2.4 GHz band, a second link on the 5 GHz band, and a third link on the 6 GHz band). Each communication link may support one or more sets of channels or logical entities. For example, the AP MLD may set a corresponding operating bandwidth, one or more corresponding primary channels, and various BSS configuration parameters for each communication link. The MLD may include a single upper MAC entity and may include, for example, three independent lower MAC entities and three associated independent PHY entities for the corresponding links in the 2.4 GHz, 5 GHz, and 6 GHz bands. This architecture allows for a single association process and security context. AP MLD may include multiple APs 102, each of which is configured to communicate with one or more corresponding STAs 104 (also referred to as "STA MLD") via a corresponding communication link.

[0072] To support MLO technology, the AP MLD and STA MLD can exchange MLO capability information (such as supported aggregation types or supported frequency bands). In some implementations, information exchange can occur via beacon frames, probe request frames, probe response frames, association request frames, association response frames, another management frame, dedicated action frames, or Operation Mode Indicators (OMIs), etc. In some implementations, the AP MLD can designate a specific channel of a link within a frequency band as an anchor channel, through which the AP MLD periodically transmits beacons and other control or management frames. In such implementations, the AP MLD can also transmit shorter beacons (such as beacons that may contain less information) on other links for discovery purposes or other purposes.

[0073] MLDs can dynamically and, in some cases concurrently, exchange packets via one or more communication links. MLDs can also independently compete for access on each communication link, which reduces latency by allowing the MLD to transmit its packets via the first communication link that becomes available. For example, "alternating multilink" can refer to MLO mode, in which the MLD can concurrently listen on two or more different high-performance links and associated channels. In alternating multilink operation mode, the MLD can alternate between using two links to transmit portions of its traffic. Specifically, an MLD with buffered traffic can use the first link, on which the MLD wins contention and obtains a TXOP to transmit traffic. Although in some specific implementations, such an MLD can only transmit or receive on one communication link at any given time, having access opportunities via two different links allows the MLD to avoid congestion, reduce latency, and maintain throughput.

[0074] Multi-link aggregation (MLA) (also known as carrier aggregation (CA)) is another MLO mode in which an MLD can send or receive traffic to another MLD in parallel and concurrently via multiple communication links, thereby increasing the utilization of available resources to achieve higher throughput. That is, for at least some time duration, transmission or portions of transmission can occur simultaneously and concurrently via two or more communication links. In some implementations, parallel communication links can support synchronous transmission. In some other implementations, or during some other time durations, transmissions via communication links can be parallel, but not synchronous or concurrent. Additionally, in some implementations or time durations, two or more communication links can be used for communication between MLDs in the same direction (such as all uplinks or all downlinks), while in some other implementations or time durations, two or more communication links can be used for communication in different directions (e.g., one or more communication links can support uplink communication, and one or more communication links can support downlink communication). In such a specific implementation, at least one of the MLDs can operate in full-duplex mode.

[0075] MLA can be packet-based or stream-based. For packet-based aggregation, frames of a single service stream (such as all services associated with a given service identifier (TID)) can be transmitted concurrently across multiple communication links. For stream-based aggregation, a single corresponding communication link among multiple communication links can be used to transmit each service stream (such as all services associated with a given TID). As an example, a single STA MLD can access a web browser while streaming video in parallel. Following the example above, services associated with web browser access can be delivered via a first communication link, while services associated with the video stream can be delivered in parallel via a second communication link (so that at least some of the data can be transmitted concurrently via the first channel with data transmitted via the second channel). In some other implementations, MLA can be implemented using a hybrid of stream-based and packet-based aggregation. For example, MLA can employ stream-based aggregation when multiple service streams are created, and packet-based aggregation in other cases. Switching between MLA techniques or modes can be additionally or alternatively correlated with other metrics, such as time of day, network traffic load, or battery level of wireless communication devices, and other factors or considerations.

[0076] Other MLO techniques can be associated with traffic bootstrapping and Quality of Service (QoS) characterization, which can achieve latency reduction and other QoS enhancements by mapping traffic flows with different latency or other requirements to different links. For example, traffic with relatively low latency requirements can be mapped to a communication link operating in the 6 GHz band, and more latency-tolerant traffic can be mapped to a communication link operating in the 2.4 GHz or 5 GHz band. Such operations (referred to as TID-to-Link Mapping (TTLM)) allow two MLDs to negotiate the mapping of certain traffic flows in the downlink direction, uplink direction, or both directions to one or more communication links set up between them. In some implementations, the AP MLD can advertise a global TTLM applied to all associated non-AP MLDs. A communication link to which no TID is mapped in either direction is called a disabled link. An enabled link has at least one TID mapped to it in at least one direction.

[0077] In some implementations, an MLD may include multiple radio components, and each communication link associated with the MLD may be associated with a corresponding radio component of the MLD. Each radio component may include one or more of its own transmit / receive (Tx / Rx) chains, including its own physical antenna or one or more physical antennas or shared antennas or coupled thereto, and includes signal processing components and other components. An MLD with multiple radio components that can be used concurrently for MLO may be referred to as a multi-link multi-radio (MLMR) MLD. Some MLMR MLDs may also be able to operate in an enhanced MLMR (eMLMR) mode, in which the MLD may be able to dynamically switch radio resources (such as antennas or RF front-ends) between multiple communication links (e.g., from using radio resources for one communication link to using radio resources for another communication link) to achieve higher transmit and receive speeds using higher capacity via a given communication link. In this eMLMR operating mode, the MLD may be able to move Tx / Rx radio resources from one communication link to another, thereby increasing the spatial streaming capability of other communication links. For example, if a non-AP MLD includes four or more STAs, the STAs associated with the eMLMR link can "pool" their antennas so that each of these STAs can utilize the antennas of other STAs when transmitting or receiving via one of the eMLMR links.

[0078] Other MLDs may have more limited capabilities and may not include multiple radio components. An MLD with only a single radio component shared across multiple communication links can be called a Multi-Link Single Radio Component (MLSR) MLD. In an example where at least one MLD operates as an MLSR MLD, control frames can be exchanged between MLDs before initiating data frame or management frame exchanges between them. Because an MLD operating in MLSR mode is limited to a single radio component, it cannot use multiple communication links concurrently, but can only listen (e.g., monitor), transmit, or receive via a single communication link at any given time. An MLSR MLD can alternatively switch between different frequency bands using Time Division Multiplexing (TDM). In contrast, some MLSR MLDs may also be able to operate in an Enhanced MLSR (eMLSR) mode, in which the MLD can concurrently listen for specific types of packets, such as Buffer Status Report Polling (BSRP) frames or Multi-User (MU) Request Transmit (RTS) (MU-RTS) frames, on multiple links. Although an MLD operating in eMLSR mode can still only transmit or receive via one link at any given time, it can dynamically switch between frequency bands, resulting in improvements in both latency and throughput. For example, when a STA of a non-AP MLD can detect a BSRP frame via its corresponding communication link, the non-AP MLD can tune all its antennas to the communication link through which it detected the BSRP frame. In contrast, a non-AP MLD operating in MLSR mode can only listen to one communication link at any given time and can only transmit or receive via that one communication link.

[0079] MLDs capable of concurrent transmission and reception via multiple communication links are referred to as Simultaneous Transmit and Receive (STR) devices. In an STR-capable MLD, the radio component associated with a communication link can independently transmit or receive frames via that link without interfering with, or being interfered with by, the operation of another radio component associated with a different communication link of the MLD. For example, an MLD with suitable filters can simultaneously transmit via the 2.4 GHz band and receive via the 5 GHz band, or vice versa, or simultaneously transmit via the 5 GHz band and receive via the 6 GHz band, or vice versa, and is therefore considered an STR device for the corresponding paired communication links. Such STR-capable MLDs are typically AP MLDs or higher-end STA MLDs with more high-performance filters. MLDs that cannot simultaneously transmit and receive via multiple communication links are referred to as non-STR (NSTR) devices. The radio component associated with a given communication link in an NSTR device may experience interference when transmitting via another communication link of the NSTR device. For example, an MLD with a standard filter may not be able to transmit via the 5GHz band and receive via the 6GHz band simultaneously, or vice versa, and therefore can be considered an NSTR device for both communication links.

[0080] In some wireless communication systems, an MLD may include multiple non-co-located entities. For example, an AP MLD may include non-co-located AP devices, and a STA MLD may include non-co-located STA devices. If an AP MLD includes multiple non-co-located AP devices, a single Mobility Domain (SMD) entity may refer to the logical entity that controls the associated non-co-located APs. Non-AP STAs (such as non-MLD non-APSTAs or non-AP MLDs including one or more associated non-AP STAs) may be associated with an SMD entity via one of their constituent APs and may roam seamlessly between APs associated with the SMD entity (e.g., without performing reassociation). The SMD entity may also maintain other contexts (such as security and block acknowledgment (BA)) for the non-AP STAs associated with it.

[0081] The aforementioned and related MLO techniques can provide several benefits to the wireless communication network 100. For example, MLO can improve user-aware throughput (UPT) (e.g., by rapidly refreshing the per-user transmit queue). Similarly, MLO can improve throughput by improving the utilization of available channels and can increase spectrum utilization (e.g., by increasing the bandwidth-time product). Furthermore, MLO can enable smooth transitions between multi-band radio components (e.g., where each radio component can be associated with a given RF band) or implement a framework for separating control and data channels. Other benefits of MLO include reducing the modem's "on" time, which can benefit wireless communication devices in terms of power consumption. Another benefit of MLO is increased multiplexing opportunities for a single BSS. For example, MLA can increase the number of users transmitted per multiplexed segment served by a multi-link AP MLD.

[0082] Figure 4 An example signaling diagram supporting IMW beam training for MLO is shown. This signaling diagram may include a wireless communication system 400, which includes AP 102-a and STA 104-a, which may be respectively as referenced... Figure 1 Examples of AP 102 and STA 104 described. AP 102-a can be an example or component of an AP MLD, and STA 104-a can be an example or component of a non-AP MLD (such as a STA MLD). The wireless communication system 400 can support operation via the 60 GHz band. AP 102-a and STA 104-a can use multi-link operation to manage beam training for the 60 GHz band.

[0083] The 60 GHz band offers a relatively wide spectrum for communication. Therefore, the 60 GHz band can support a relatively large number of wireless communication devices and transmissions via this band. However, signal propagation in the 60 GHz band may suffer relatively high attenuation losses. To mitigate these attenuation losses, wireless communication devices can use beamforming for transmission and reception to perform directional communication. Wireless communication devices can perform beam training to align the communication beam for reliable communication. Beam training can involve the wireless communication device performing a beam scanning process to select a beam directed towards other wireless communication devices. For example, AP 102-a can perform a beam scanning process to select transmit and receive beams for directional communication with STA 104-a, and STA 104-a can perform a beam scanning process to select transmit and receive beams for directional communication with AP 102-a.

[0084] In some other systems, beam training for the 60 GHz band can involve relatively high overhead (such as processing overhead, signaling overhead, and beam training latency). For example, a beam training process may involve four beam scans: a transmit sector scan at the initiating device, a transmit sector scan at the responding device, a receive sector scan at the initiating device, and a receive sector scan at the responding device. Devices may perform transmit sector scans in turn, followed by receive sector scans. The number of scans and the size of the scan packets can lead to significant overhead and latency associated with these beam training processes.

[0085] Wireless communication system 400 can utilize multi-link operation to mitigate the overhead associated with beam training processes for the 60 GHz band. For example, AP 102-a can use another frequency band (such as the sub7 band or another frequency band) to communicate timing information related to the beam training process for the 60 GHz band to STA 104-a. AP 102-a can send a TSF value associated with AP 102-a (such as associated with AP 102-a's 60 GHz link) to STA 104-a via sub7 link 408 (or another similarly active or otherwise established link between AP 102-a and STA 104-a). In some implementations, this TSF value can be an example of a current TSF value announced by AP 102-a (such as via the 60 GHz link or sub7 link 408), a TSF value indicating the time when a sector scan will occur via the 60 GHz link, or both (such as multiple TSF values ​​indicating both the current time and the sector scan timing). TSF values ​​can be examples of complete TSF values ​​(such as octet values ​​indicating TSF values) or partial TSF values ​​(such as (lower) two-octet values ​​indicating TSF values). For example, a TSF value can include any number of bits or octets indicating a timestamp, where relatively fewer bits can reduce the packet size used to send the TSF value indication. AP 102-a can indicate the TSF value associated with the 60GHz link directly or relative to the timing of sub7 link 408. Alternatively, AP 102-a and STA 104-a can use timing indicators different from TSF values, such as any timestamp, time offset value, or any other timing information that supports timing synchronization. For example, as used herein, "TSF value" can refer to any value indicating a specific time or time offset.

[0086] STA 104-a and AP 102-a can use TSF values ​​to coordinate the beam training process. For example, STA 104-a and AP 102-a can use TSF values ​​to coordinate the timing of scan packet transmission. AP 102-a can transmit scan packets 402 of the beam scanning process with a specific TSF value via a 60 GHz band or link. In some implementations, AP 102-a can be configured with a specific TSF value such that STA 104-a can determine (e.g., calculate, identify, detect, select, or otherwise ascertain) the specific TSF value and can monitor the 60 GHz band at a specific time to find scan packet 402. In some other implementations, AP 102-a can independently of or otherwise transparently select (e.g., determine, identify, or otherwise ascertain) the specific TSF value for scan packet 402 (so that STA 104-a is unaware of the specific TSF value corresponding to scan packet 402). AP 102-a can transmit a first scan packet 402-a corresponding to the first sector 404-a with a first TSF value, and correspondingly transmit a first transmit beam for directional communication. AP 102-a can transmit a second scan packet 402-b corresponding to the second sector 404-b with a second TSF value, a third scan packet 402-c corresponding to the third sector 404-c with a third TSF value, and a fourth scan packet 402-d corresponding to the fourth sector 404-d with a fourth TSF value. STA 104-a can monitor the 60 GHz band (e.g., during a time window including TSF values) and can select the scan packets 402 to be received (e.g., scan packets 402 with the strongest received power, highest received quality, or both). The beam scanning process may involve STA 104-a performing received signal strength measurements relative to one or more beam directions for directional communication. For example, STA 104-a can receive the third scan packet 402-c with a third TSF value (or at the reception time corresponding to a transmission with the third TSF value). STA 104-a can, for example, send a report 406 to AP 102-a indicating the third TSF value of the scan packet 402-c for reception based on received signal strength measurements. In some implementations, STA 104-a can determine (e.g., by calculation, selection, identification, detection, or other means) the third TSF value based on a fixed reference time, such as the TSF value announced by AP 102-a. STA 104-a can send the report 406 to AP 102-a via sub7 link 408. AP 102-a can receive the report 406 and, based on the third indicated TSF value, select a third transmit beam corresponding to the third sector 404-c for communication with STA 104-a via the 60 GHz band.

[0087] Using the techniques described herein, AP 102-a (such as AP MLD) and STA 104-a (such as non-AP MLD) can support scan packet overhead reduction, sub7 link-based feedback, AP transmit sector scan aggregation for multiple STA 104s, sub7 feedback aggregation or piggybacking, timely delivery of training feedback, or any combination thereof, for 60 GHz beam training operations.

[0088] Figure 5 An example of a signaling timeline 500 supporting IMW beam training for MLO is shown. Signaling timeline 500 may involve an AP MLD 502, a first non-AP MLD 504-a (such as a first STA MLD), and a second non-AP MLD 504-b (such as a second STA MLD). AP MLD 502 may support a first link via a first frequency band 506-a and a second link via a second frequency band 506-b. For example, the first AP link may be an example of a sub7 GHz link, and the second AP link may be an example of a 60 GHz link. Similarly, the first non-AP MLD 504-a may support a first link via a first frequency band 506-a and a second link via a second frequency band 506-b, and the second non-AP MLD 504-b may support a first link via a first frequency band 506-a and a second link via a second frequency band 506-b. MLD can leverage multi-link operation to improve the overhead and latency associated with beam scanning processes used in the second band 506-b, such as the 60 GHz band supporting directional communications.

[0089] In some implementations, the MLD can support reduced scan packet overhead using short scan signals. The MLD can operate in non-standalone (NSA) mode, allowing it to pair 60 GHz links with partner links via sub7 band 506-a. Using a multi-link operation framework, the MLD can perform management-level signaling for the 60 GHz link via one or more sub7 links. For example, the MLD can perform discovery, multi-link setup, other protocols (such as BA and timing coordination protocols), or any combination thereof via sub7 links. A non-AP MLD can use communication via sub7 links to determine (such as receive, select, or otherwise ascertain) information related to the 60 GHz link, including the 60 GHz link as part of a multi-link set, setting the service period of the 60 GHz link, or any combination thereof, for example, without exchanging frames via the 60 GHz link. Therefore, the MLD can use omnidirectional or quasi-omnidirectional (such as non-directional) communication via sub7 links to support beamforming operations for cooperative 60 GHz links. Although this article describes the sub7 link and the 60GHz link with reference, the techniques described herein can be applied to other types of links associated with other frequency bands.

[0090] A multi-link operation framework may involve AP MLD 502 maintaining a constant TSF offset for each link (such as each affiliated AP) associated with AP MLD 502. In some implementations, AP MLD 502 may advertise one or more TSF offsets, where the TSF offset is relative to a first AP link and another affiliated AP link. For example, AP MLD 502 may send an advertisement packet or another packet including a TSF value indication 522 associated with a link of AP MLD 502 (such as a second link associated with 60 GHz band 506-b). In some implementations, this packet may include a TSF offset field or subfield indicating the offset between the TSF timer of the first AP and the TSF timer of the second AP of AP MLD 502, where the offset may be an example of TSF value indication 522. AP MLD 502 may use omnidirectional or quasi-omnidirectional transmission to send TSF value indication 522 via the first link. One or more non-AP MLDs (such as non-AP MLD 504-a) can receive packets and can determine (such as by receiving, decoding, processing, or otherwise identifying) the TSF for at least one link of AP MLD 502. Using constant TSF offset information, non-AP MLD 504-a can use the TSF value received for any link of AP MLD 502 to determine (such as by calculating, selecting, or otherwise identifying) the TSF for any other link of AP MLD 502 based on the TSF offset.

[0091] AP MLD 502 can negotiate or instruct timing information with non-AP MLD 504-a via a sub7 link to support beam training procedures for the 60 GHz link. For example, AP MLD 502 can instruct non-AP MLD 504-a of the exact time for beam training, such as the exact TSF value. This time can be common to more than one non-AP MLD or can be reserved for a specific non-AP MLD. For example, a common start time for beam training performed by multiple non-AP MLDs could be the start time of an AP sector reference transmission period (ATP). During the ATP, AP MLD 502 can perform a common beam scan for multiple non-AP MLDs. AP MLD 502 can use TSF information to configure the start time of the beam scan procedure via the 60 GHz band, a dedicated time period for beam training, or both. For example, AP MLD 502 and non-AP MLD 504-a can establish a dedicated service period for performing beam scans. In some systems, dedicated time slots can be configured to repeat relatively frequently (up to a relatively long time period), allowing these slots to be used for exchanging data frames between AP MLD 502 and non-AP MLD 504-a after the beam training process has begun (and the directional beam between AP MLD 502 and non-AP MLD 504-a has been established). The relatively high directional nature of the 60 GHz band allows MLDs to gain access to the 60 GHz medium during dedicated service slots to perform directional scan packet transmission 514.

[0092] Because both MLDs are configured using specific timing information for the beam training process, the MLDs can avoid using training sequences, sector identification information, or both to support scan packet identification in the scan packets. Avoiding the use of training sequences, sector identification information, or both reduces the overhead associated with scan packet transmission 514, thereby improving latency and overhead during beam scanning. Such scan packets can be referred to as “short” scan packets. Short scan packets can span one or two microseconds, with the physical design including an LTF that can span approximately one microsecond, or an LTF and SIG that can span approximately two microseconds. Short scan packets can include a fixed bit or tone pattern that the receiving MLD can use to distinguish the short scan packets from ambient or surrounding noise. In some implementations, the AP MLD 502 can be configured with a fixed pattern for scan packets during the association process (such as via a sub7 link). The fixed pattern can be unique to the AP MLD 502. In some other implementations, the non-AP MLD 504-a can be configured using a fixed pattern for short scan packets. For example, a fixed pattern can be defined in wireless standards such as one or more IEEE 802.11 standards. In some specific implementations, short scan packets may include sector identification information (such as sector identifiers), device identifiers (such as an AP identifier or non-AP STA identifier indicating the device sending the short scan packet, or a BSS color indicating the AP sending the short scan packet), fixed bit or tone patterns, or any combination of these elements. Such elements can support the identification of short scan packets.

[0093] The MLD receiving scan packet transmission 514 can identify the scan packet using the time it was received (e.g., corresponding to a TSF value), instead of using training sequence or sector identification information to identify which scan packet transmission 514 was received. Based on TSF coordination between links, the MLD receiving one or more scan packets can select and report TSF values ​​for scan packets that meet thresholds. For example, the MLD can select and report TSF values ​​for scan packets corresponding to the strongest received signal power, meeting a quality threshold, or some combination thereof. The MLD transmitting scan packets can receive the transmission report 520 and can correlate the indicated TSF value with the corresponding sector information to support transmit beam selection.

[0094] For example, AP MLD 502 can send a TSF value indication 522 associated with a second link of AP MLD 502 to non-AP MLD 504-a via a first link. AP MLD 502 can be additionally configured to perform a transmission beam scan for a period of time based on the indicated TSF value. AP MLD 502 can transmit a set of scan packet transmissions 514 via the second link during the configured time period, and non-AP MLD 504-a can perform omnidirectional or quasi-omnidirectional monitoring 512 during the configured time period. For example, non-AP MLD 504-a can monitor a second frequency band 506-b for scan packet transmissions 514 during the configured time period based on the indicated TSF value and a fixed pattern for the scan packets. Non-AP MLD 504-a can detect or otherwise receive one or more scan packet transmissions 514 based on scan packet monitoring 516. If the non-AP MLD 504-a receives a scan packet transmission 514, the non-AP MLD 504-a can determine (e.g., receive, decode, process, or otherwise ascertain) the TSF value for scan packet reception 518. If the non-AP MLD 504-a receives more than one scan packet transmission 514, the non-AP MLD 504-a can determine (e.g., calculate, select, or otherwise ascertain) the TSF value for scan packet reception 518 that meets a threshold (e.g., signal strength or signal quality threshold). The non-AP MLD 504-a can transmit a report 520-a via the first link indicating the determined TSF value or another value corresponding to the determined TSF value (e.g., a packet identifier or beam identifier). The non-AP MLD 504-a can receive the report 520-a and can select the transmission beam to be used for the second link corresponding to the reported value (e.g., the reported TSF value). Additionally or alternatively, the non-AP MLD 504-a can perform similar beam training to select the transmit beam to be used for the second link.

[0095] In some implementations, the non-AP MLD 504-a can trigger beamtraining for the 60 GHz link based on one or more factors. If the non-AP MLD 504-a is recently associated with AP MLD 502 for the 60 GHz link, the non-AP MLD 504-a can perform beamtraining for the 60 GHz band with the affiliated AP before initiating frame switching via the 60 GHz link. The non-AP MLD 504-a can perform discovery, multi-link setup, or both using the multi-link operation framework via the sub7 band. Additionally or alternatively, if the non-AP MLD 504-a is inactive via the 60 GHz link for at least a threshold amount of time, the non-AP MLD 504-a can perform beamtraining for the 60 GHz band with the affiliated AP to update beam selection if the orientation of the non-AP MLD 504-a relative to AP MLD 502 has changed during the inactivity period. Additionally or alternatively, if a non-AP MLD 504-a active via the 60 GHz link detects a beam misalignment with AP MLD 502, the non-AP MLD 504-a can trigger beam training. In some implementations, an affiliated AP in the 60 GHz band can transmit a reference signal or another packet via the 60 GHz link, indicating to the non-AP MLD 504-a whether any beam misalignment has occurred. In some other implementations, AP MLD 502 can determine (e.g., identify, calculate, or otherwise detect) a beam misalignment with non-AP MLD 504-a and can send an instruction to non-AP MLD 504-a to trigger beam training. If a beam misalignment is detected, the non-AP MLD 504-a can perform beam training or refinement.

[0096] In some implementations, AP MLD 502 can perform beam scanning for the 60 GHz band during one or more common periods. For example, an affiliated AP for the 60 GHz band can perform transmit beam scanning during one or more common periods. AP MLD 502 can advertise information about one or more common periods via a sub7 link. One or more non-AP MLDs can monitor the 60 GHz band during common periods to derive relevant beam training information. For example, during the same common period, an active non-AP MLD 504-a can determine (such as identifying or selecting) to retrain or refine the beam alignment, while a newly associated or newly active non-AP MLD 504-b can perform beam training using the same scan packet transmission 514, thereby effectively aggregating the transmit scans of the AP MLD for multiple non-AP MLDs. Therefore, any number of non-AP MLDs can monitor a second band 506-b during common periods and can receive the same or different scan packet transmissions 514 based on the monitoring. In some implementations, common periods can be referred to as transmit periods, ATP, or any similar term. The duration of ATP 508 can be relatively short (e.g., one microsecond per AP sector). For example, both the first non-AP MLD 504-a and the second non-AP MLD 504-b can perform omnidirectional or quasi-omnidirectional monitoring 512 during ATP 508, and can receive different scan packet transmissions 514 during ATP 508 depending on the different orientations between the AP MLD 502 and the different non-AP MLDs. In some specific implementations, the scan packet transmission 514 during ATP 508 can be an example of AP sector reference (ASR) frame transmission. An ASR frame can be an example of a relatively short beacon or beacon frame or similar to a relatively short beacon or beacon frame. Compared to a beacon frame, an ASR frame can include a subset of information, such as partial TSF information, sector identifiers, short identifiers of transmitting devices (e.g., transmitting APs), or any combination thereof. The first non-AP MLD 504-a can send a first report 520-a indicating a first TSF value for scan packet reception 518 at the first non-AP MLD 504-a, and the second non-AP MLD 504-b can send a second report 520-b indicating a second TSF value for scan packet reception 518 at the second non-AP MLD 504-b.

[0097] In some implementations, the AP MLD 502 can split its transmit beam scan across multiple ATP 508s. For example, the AP MLD 502 can perform partial beam scans during ATP 508. In some implementations, the AP MLD 502 can transmit scan packets associated with a corresponding transmit beam corresponding to a first subset of sectors of the AP MLD 502 during ATP 508, and the AP MLD 502 can transmit scan packets associated with a corresponding transmit beam corresponding to a second subset of sectors of the AP MLD 502, different from the first subset of sectors, during subsequent ATP 508 periods. If a beam scan during ATP 508 does not cover a sector corresponding to a non-AP MLD, the non-AP MLD may fail to detect scan packet transmissions 514 from the AP MLD 502 during ATP 508. If the non-AP MLD fails to detect scan packets while monitoring during ATP 508, the non-AP MLD may avoid reporting TSF values. For example, if a non-AP MLD supports trigger-based (TB) reporting, the non-AP MLD can respond to a trigger frame (TF) with a null value or other null (such as a 0 value) report.

[0098] In some implementations, the AP MLD 502 can be configured with a dedicated or special time period for non-AP MLDs to perform transmit beam scanning. For example, the AP MLD 502 can establish a first dedicated time period for a first non-AP MLD 504-a to perform transmit beam scanning via the 60 GHz band, and a second dedicated time period for a second non-AP MLD 504-b to perform transmit beam scanning via the 60 GHz band. The dedicated or special time period can be referred to as a Dedicated Scan Period (D-SP) or other similar terms. The D-SP duration can span several milliseconds. In some implementations, the AP MLD 502 can set the D-SP for non-AP MLD 504-a via sub7 signaling (e.g., using an AP coordination interval framework such as a Target Wake-up Time (TWT) framework). For example, the AP MLD 502 can be configured via one or more sub7 links to use a first D-SP 510-a for a non-AP MLD 504-b and a second D-SP 510-b for a non-AP MLD 504-a. In some implementations, the non-AP MLD can use the configured D-SP to exchange data via the 60GHz band after completing the beam training process for the 60GHz band.

[0099] During the first D-SP 510-a, the non-AP MLD 504-b can perform sectorized scan packet transmission 514 via the 60 GHz band, and the AP MLD 502 can monitor the 60 GHz band in response to the scan packet transmission 514. The AP MLD 502 can use omnidirectional or quasi-omnidirectional monitoring, or it can monitor according to the direction selected for the transmission beam according to the transmission beam scan of the AP MLD. If the AP MLD 502 detects or otherwise receives one or more scan packet transmissions 514 from the non-AP MLD 504-b, the AP MLD 502 can send a report 520-c indicating the TSF value corresponding to the scan packet reception 518. The AP MLD 502 can send the report 520-c to the non-AP MLD 504-b via the sub7 link.

[0100] Additionally or alternatively, during the second D-SP 510-b, the non-AP MLD 504-a may perform sectorized scan packet transmission 514 via the 60 GHz band, and the AP MLD 502 may monitor the 60 GHz band in response to the scan packet transmission 514. If the AP MLD 502 detects or otherwise receives one or more scan packet transmissions 514 from the non-AP MLD 504-a, the AP MLD 502 may send a report 520-d indicating a TSF value corresponding to the scan packet reception 518. The AP MLD 502 may send the report 520-d to the non-AP MLD 504-a via a sub7 link.

[0101] In some implementations, the AP MLD 502 may repeatedly announce timing information to support drift correction. For example, the AP MLD 502 may provide local time information in periodic (or semi-periodic or otherwise scheduled) intervals. The AP MLD 502 may send frames that include timing information, such as updated TSF values ​​for one or more APs for the AP MLD 502. In some implementations, the AP MLD 502 may send frames based on frequency or periodicity, such as every 20 milliseconds. This frame may be an example of a Fast Initial Link Setup (FILS) Discovery (FD) frame, a Broadcast Probe Response frame, or some other broadcast or individual addressing frame. The timing information may have relatively high granularity (such as a few nanoseconds). For example, the granularity of the timing information may specify the periodicity (or frequency) at which the information is announced or otherwise indicated. In some implementations, fields in frames that include timing information may include the full TSF value or a partial TSF value, such as one or more least significant bits (LSBs) of the TSF value. In some systems, fields carrying timing information can be protected by integrity (such as by generating message integrity checks (MIC)) or by encryption.

[0102] In some systems, the AP MLD 502 can indicate the start of a training period (ATP or dedicated) with relatively low granularity (such as using units of 1 microsecond). For example, the granularity of the start time could indicate the periodicity (or frequency) of the start time. Therefore, in some implementations, the start of a training period may appear offset by at most 1 microsecond for AP or non-AP. In some such implementations, the device may begin its transmit scan slightly later (such as at most 1 microsecond later) to account for this difference in the interpretation of the start time of the beam training period.

[0103] Figure 6 An example of a report format 600 supporting IMMW beam training for MLO is shown. AP MLD 602 ​​(which can be as referenced herein) Figure 1 , Figure 4 and Figure 5 The described AP MLD 502 or AP 102 (examples) can trigger the reporting of beam training feedback from one or more non-AP MLDs. For example, a first non-AP MLD 604-a and a second non-AP MLD 604-b (which may be referred to as STA MLDs) can perform beam training and report beam training feedback to the AP MLD 602. Non-AP MLDs can be as referenced herein. Figure 1 , Figure 4 and Figure 5 The described example is a non-AP MLD or STA 104. The AP MLD602 can aggregate report feedback from non-AP MLDs to avoid report conflicts.

[0104] The AP MLD 602 ​​can perform transmit beam scanning via the 60 GHz band during public hours. Multiple non-AP MLDs can monitor the 60 GHz band during public hours to perform beam training with the AP MLD 602 ​​and can report feedback via the sub-7 band, such as indicating the TSF value of scan packets received during beam scanning. To avoid conflicts between feedback from multiple non-AP MLDs, the AP MLD 602 ​​can trigger one or more non-AP MLDs to provide aggregated feedback. For example, the AP MLD 602 ​​can identify (such as by detection, identification, selection, or other means) a non-AP MLD that recently performed a multi-link setup including a 60 GHz link, a non-AP MLD that recently transitioned to an activity mode involving a 60 GHz link, or both.

[0105] The AP MLD 602 ​​can send a TF 610 instructing one or more RUs (Recruits) for a non-AP MLD to provide beam training feedback. In some implementations, the TF 610 can instruct a directional RU for a specific non-AP MLD to report beam training feedback. Additionally or alternatively, the TF 610 can instruct a random access (RA) RU for a non-AP MLD to report beam training feedback. Any non-AP STA (such as a non-AP STA that has not received a directional RU) can use an RA-RU to provide feedback. In some implementations, the TF 610 may include a special AID for the RA-RU to avoid receiving responses from other non-IMMW or non-training STAs.

[0106] TF 610 can trigger TB PPDU 612, which can include feedback from multiple non-AP MLDs. For example, TB PPDU 612 can include one or more directional RUs for a specific non-AP MLD, one or more RA-RUs for any non-AP MLD, or a combination thereof. In some specific implementations, AP MLD 602 ​​can determine (e.g., identify or otherwise detect) that a first non-AP MLD 604-a is in training mode, but may not determine (e.g., fail to identify or otherwise detect) that a second non-AP MLD 604-b is in training mode. AP MLD 602 ​​can assign a directional RU (such as first RU 614-a) to the first non-AP MLD 604-a via TF 610, and may not assign a directional RU to the second non-AP MLD 604-b. Instead, the second non-AP MLD 604-b can use an RA-RU (such as second RU 614-b) indicated by TF 610 as an RA-RU for beam training feedback. The first non-AP MLD 604-a can report the first TSF value via the first RU 614-a, and the second non-AP MLD 604-b can report the second TSF value via the second RU 614-b of the TB PPDU 612. For example, the first non-AP MLD 604-a can report the first TSF value via the first RU 614-a in a frame such as an extension of a multi-STA BA frame, a QoS null frame, a QoS data frame, an action frame (such as a new action frame), an extension of a management frame, or any combination of these or other frames.

[0107] In some implementations, the AP MLD 602 ​​may transmit a first frame 608 before the TF 610 (such as the basic TF) to determine (e.g., identify, detect, or otherwise ascertain) which non-AP MLDs are in training mode for beam training via the 60 GHz band. For example, the first frame 608 may be an example of a short feedback report polling for beam training feedback, a variant of the NDP feedback report polling (NFRP), a variant of the BSRP, or some combination thereof. In some implementations, the short feedback report polling may request a response from a non-AP MLD performing beam training during a common period for the AP to transmit beam scans. A non-AP MLD may respond to the first frame 608 if it is in training mode, monitoring the 60 GHz band during the AP's beam scan process, or receiving scan packets. The AP MLD 602 ​​may assign a directed RU to a non-AP MLD responding to the first frame 608 via the TF 610 to reduce the likelihood of RA-RU conflicts between different non-AP MLDs. Non-AP MLDs can report beam training feedback, such as TSF values, via the directional RU of TB PPDU 612. In some implementations, AP MLD 602 ​​can send acknowledgment reports of received multi-STA BA 616 via sub7 band to non-AP MLDs reporting TSF values ​​via TB PPDU 612.

[0108] Non-AP MLDs can report beam training feedback in a relatively timely manner, such as within a threshold time. However, transmissions via the sub7 band can be contention-based, leading to variations in the actual transmission time of the reports. In some implementations, AP MLD 602 ​​can be configured with protected periods for receiving reports via the sub7 band. For example, to ensure timely delivery of beam training feedback, AP MLD 602 ​​can announce one or more special channel access periods 606 to protect the feedback duration from other transmissions, such as in-BSS transmissions. Other MLDs can avoid contention for the sub7 band (or a portion of the sub7 band) during the special channel access period 606. In some implementations, neighboring APs can coordinate the special channel access period 606 to protect the timely delivery of beam training feedback. In some implementations, AP MLD 602 ​​may use inter-AP coordination intervals or epochs, inter-AP service intervals or epochs, AP coordination intervals or epochs, or any other technology used to configure service periods, such as (coordinated) restricted TWT ((c)rTWT), to support special channel access period 606. For example, AP MLD 602 ​​may announce or negotiate special channel access period 606. In some implementations, crTWT may involve supporting rTWT and coordinating OBSS APs to avoid contention within the BSS via the sub7 band based on the start time of special channel access period 606. AP MLD 602 ​​may have prioritized channel access for the sub7 band.

[0109] In some specific implementations, the start of the sub7 special channel access period 606 can be aligned with or close to the end of the 60GHz ATP, as referenced in this document. Figure 5 As described. For example, AP MLD 602 ​​can be configured to handle the reception of the last scan signal via the 60 GHz band using ATP and special channel access period 606, while providing sufficient time to transmit the first frame (such as frame 608 or TF 610 requesting feedback) within special channel access period 606.

[0110] In some implementations, the AP MLD 602 ​​can employ one or more mechanisms to provide additional protection and relatively faster feedback via the sub7 band. For example, the AP MLD 602 ​​can use MU Enhanced Distributed Channel Access (EDCA) with an Arbitration Inter-Frame Spacing Number (AIFSN) set to zero, Clear Transmission (CTS) enabled, relatively short TXOPs, or any combination thereof for one or more sub7 links.

[0111] Additionally or alternatively, the AP MLD 602 ​​can aggregate or piggyback beamtrain feedback reports to one or more non-AP MLDs to similarly support the timely delivery of beamtrain feedback for transmit beam scans of non-AP MLDs. For example, the AP MLD 602 ​​can transmit beamtrain feedback (such as TSF values ​​for scan packets used for reception) to non-AP MLDs (such as non-AP MLD 604-a) via the sub7 band. The AP MLD 602 ​​can aggregate or piggyback beamtrain feedback along with other downlink data from the AP MLD 602 ​​to non-AP MLD 604-a (or a different non-AP MLD 604-b). For example, if the AP MLD 602 ​​has pending frames for non-AP MLD 604-a, the AP MLD 602 ​​can aggregate the feedback in the A-MPDU. Additionally or alternatively, the AP MLD 602 ​​may transmit downlink MU-PPDUs including beam training feedback for non-AP MLD 604-a, while serving one or more other non-AP MLDs via the sub7 band.

[0112] In some implementations, to prevent any clock drift, the AP MLD 602 ​​may send an indication of local time, such as the TSF value of the AP used by the AP MLD 602, to one or more non-AP MLDs. For example, the AP MLD 602 ​​may send the indication of local time before polling the non-AP MLDs. The AP MLD 602 ​​may send an explicit frame including time information (which may or may not be aggregated with short feedback report polling, if present), or the time information may be included with the TF 610 requesting beam training feedback. For example, the TF 610 may include a special user information field containing the TSF value. The non-AP MLD receiving the timing information (such as non-AP MLD 604-a) may apply any correction to the TSF value used for reporting, such as to correct for any clock drift, before sending the report. Additionally or alternatively, the AP MLD 602 ​​may embed local time information (such as the TSF value), where its reporting of the TSF corresponds to scan packets received from the non-AP MLDs. Non-AP MLDs can apply any correction to the indicated TSF value to resolve reports from AP MLD 602.

[0113] In some implementations, the AP MLD 602 ​​can use individually addressed TSF polling to receive beam training feedback from non-AP MLDs. For example, instead of polling non-AP MLDs by broadcasting a TF 610 requesting feedback via the sub7 band after ATP, the AP MLD 602 ​​can send individually addressed TSF polling frames, similar to NFRP type frames, to one or more non-AP MLDs to receive feedback. For example, the TSF polling frame can be a variant of the NFRP frame or a new short feedback report polling frame (which can be defined by a standard such as IEEE 802.11), where each response tone is mapped to a beam TSF value. The non-AP MLD 604-a receiving the TSF polling addressed to it can set the tone of the response corresponding to the TSF value of the scan packet used for reception. In some implementations, the TSF polling frame may additionally include a field providing a timing reference (such as the TSF value) to account for clock drift. This feedback process can relax the timing of the AP MLD 602 ​​polling non-AP MLDs for the TSF value corresponding to the transmitted beam. The AP MLD 602 ​​can send such TSF polling frames to non-AP MLDs, which the non-AP MLD 602 ​​identifies as having recently performed multilink setup, recently transitioned to the 60 GHz band, or possibly having monitored the AP MLD's 60 GHz band ATP, or any combination thereof. Additionally or alternatively, the AP MLD 602 ​​can send TSF polling frames (such as NFRP or short feedback report polling variants) via the 60 GHz band after ATP to identify which non-AP MLDs are in the beam training phase (such as monitoring the 60 GHz band during ATP), and can poll each of these non-AP MLDs individually.

[0114] Additionally or alternatively, the AP MLD 602 ​​may transmit multiple NFRP or short feedback report polls via the sub7 band after ATP, each poll corresponding to a TSF value or a set of TSF values. Such polls may include a field indicating the corresponding TSF value, and each tone may be mapped to the AID of the non-AP MLD being polled. If a responding non-AP MLD selects a TSF value corresponding to a particular poll for reporting, that non-AP MLD may set the tone matching its AID to that specific value. In some implementations, the poll may additionally include a field providing a timing reference (such as a TSF value) to account for clock drift. In some implementations, the AP MLD 602 ​​may protect such polling and polling response exchanges via crTWT or other coordination techniques.

[0115] In some implementations, non-AP MLDs (such as non-AP MLD 604-a) can send TSF reports for beam training via multi-STA BA frames. The multi-STA BA frame format can be extensible, allowing standards (such as the IEEE 802.11 standard) to define mechanisms for multi-STA BA frames to include beam training information, including TSF values. In some implementations, AP MLD 602 ​​can send a special form of Multi-User BA Request (MU-BAR) frame to request reports from multiple STAs 104 (such as non-AP MLDs), and the multiple STAs 104 can respond with a multi-STA BA frame with a modified format to provide corresponding TSF reports (such as beam training feedback) for those multiple STAs 104. In some other implementations, multi-STA BA can be unsolicited, where STAs 104 can send their own multi-STA BA including beam training feedback information. Additionally or alternatively, the AP MLD 602 ​​can use multiple STA BA frames to provide beam training feedback to multiple STA 104s (such as multiple non-AP MLDs).

[0116] In some implementations, the AP MLD 602 ​​can select which feedback scheme to use based on the number of sectors of the AP MLD 602, the number of non-AP MLDs performing beam training with the AP MLD 602, or some combination thereof. For example, if the AP MLD 602 ​​has a relatively large number of sectors (such as 32 or 64) with a relatively small number of non-AP MLDs operating in beam training mode (such as one to twenty non-AP MLDs), the AP MLD 602 ​​can choose a feedback scheme that polls individual short feedback reports involving the non-AP MLDs.

[0117] Figure 7 An example of a preemption procedure supporting IMW beam training for MLO is shown. The preemption procedure may include example downlink preemption procedure 700-a and example uplink preemption procedure 700-b. In some specific implementations, AP MLD (such as those referenced herein) Figure 1 and Figures 4 to 6 The described AP MLD can support preemption techniques to facilitate timely delivery of training feedback via the sub7 link.

[0118] For example, an AP MLD can preempt an ongoing PPDU via the sub7 channel to poll or provide feedback for a transmit beam scan performed via the 60 GHz band. In some implementations, if a preemption scheme is used, the AP MLD can avoid setting a dedicated time interval (such as TWT or rTWT) for feedback polling. After the AP MLD performs a transmit beam scan, for example, during ATP via the 60 GHz band, the AP MLD can compete for the TXOP via the sub7 band. If the AP MLD wins the TXOP contention, it can transmit a frame via the sub7 band to request feedback. However, if a non-AP MLD (such as STA 104 within the AP MLD's BSS) wins the TXOP contention, the AP MLD can send a preemption request to STA 104 to gain access to the sub7 medium for polling. In some implementations, the AP MLD can, for example, use configuration or management signaling to notify STA 104 when preemption is permitted. In some aspects, preemption can be associated with polling priority. In some specific implementations, the IMMW STA 104 can detect ATP via the 60 GHz band and can preempt during sub7TXOP according to ATP permission.

[0119] After a non-AP MLD performs a transmit beam scan via the 60GHz band, the AP MLD can provide feedback via the sub7 link. In some implementations, the AP MLD can perform preemption-based feedback, where the AP MLD can preempt transmissions from STAs within the BSS. In other implementations, the AP MLD can aggregate or piggyback feedback with downlink transmissions from APs (same AP 102 or different AP 102). IMMW APs can be configured with such preemption schemes, allowing IMMW sub7 AP 102 to preempt transmissions from other sub7 AP 102s to support feedback polling via the sub7 band.

[0120] In some specific implementations, the AP MLD can support shared TXOP feedback using coordinated TDMA (c-TDMA) between APs 102. For example, the AP MLD can negotiate c-TDMA such that if at least a portion of the TXOP is approximately aligned with the end time of the AP MLD's ATP via the 60 GHz band, a neighboring AP having a sub7 TXOP can share that portion of the TXOP with the AP MLD.

[0121] AP MLD can support downlink preemption procedure 700-a, uplink preemption procedure 700-b, or both for the sub7 band. For example, sub7 AP 102 can preempt its transmissions to sub7 STA 104 and allow transmissions to or from different STA 104. For downlink preemption procedure 700-a, sub7 AP 102-b can preempt its own downlink transmissions to STA 104-b, instead performing relatively higher priority or time-sensitive downlink transmissions to different STA 104. For example, AP 102-b can gain access to the sub7 channel for TXOP 702-a and can break long PPDUs into multiple relatively shorter PPDUs. AP 102-b can send the first downlink PPDU 704-a to STA 104-b and can receive acknowledgment (ACK) messages in response, such as ACK 706-a. However, AP 102-b can preempt subsequent downlink PPDUs, for example, to support beam training feedback processes for the 60GHz link. AP 102-b can send the preempted downlink PPDU 708 to a different STA 104-b and can receive the preempted ACK 710 from a different STA 104-b. In some specific implementations, AP 102-b can continue to send a second downlink PPDU 704-b to STA 104-b and can receive an ACK 706-b as a response during TXOP 702-a.

[0122] For uplink preemption procedure 700-b, sub7 AP 102-c can preempt its own downlink transmission to STA 104-c, instead allowing STA 104-c to send relatively higher priority or time-sensitive uplink transmissions to AP 102-c. For example, AP 102-c can gain access to the sub7 channel used for TXOP 702-b and can break long PPDUs into multiple relatively short PPDUs. AP 102-c can send a first downlink PPDU with polling 712 (such as including NFRP or BSRP) to STA 104-c and can receive ACK 706-c and a response 714 to that polling, such as an NDP Feedback Report (NFR) or a Buffer Status Report (BSR). This polling can support uplink preemption for a portion of TXOP 702-b. AP 102-c can send TF 716 to trigger uplink preemption, and STA 104-c can send one or more uplink PPDUs to AP 102-c. For example, STA 104-c can send a first uplink TB-PPDU 718-a, a second uplink TB-PPDU 718-b, a third uplink TB-PPDU 718-c, or any combination thereof (such as in response to TF 716) in the preempted resource. In some implementations, multiple STAs 104 can send uplink TB-PPDUs in the preempted resource. AP 102-c can send a second downlink PPDU with ACK 720 for the uplink TB-PPDU, and STA 104-c can respond with ACK 706-d. In some implementations, AP 102-c can support utility-oriented resource allocation (UORA) preemption for uplink preemption.

[0123] For both uplink and downlink preemption, the sub7 AP can provide signaling to support preemption via a preamble to the initial downlink PPDU or embedded in the frame of the downlink MPDU. This signaling can allow the associated STA 104 to prepare to send or receive the preempted frame. For example, for uplink preemption, AP 102-b can indicate that it is allowing STA 104 (such as STA 104 with beam training TSF values ​​to report) to preempt the AP's downlink resources to transmit time-sensitive uplink traffic (such as reporting). In some implementations, STA 104 may have an uplink TXOP for sending to AP 102-c. AP 102-c can acknowledge the STA's uplink transmission and can add a per-AID TID information field that includes beam training information feedback. For downlink preemption, this signaling can allow AP 102-c to prepare STA 104 (such as STA 104 participating in beam training via the 60 GHz band) to receive AP TSF reports via the sub-7 band. Alternatively, preparing for downlink preemption may involve STA 104 avoiding setting the NAV within the BSS and entering a "dormant" state. Alternatively, AP 102 may set the downlink NAV (e.g., in the initial downlink PPDU) to a short NAV, causing the corresponding STA 104 to wake up and monitor any transmissions from AP 102.

[0124] Figure 8 A block diagram of an example wireless communication device 800 supporting IMW beam training for MLO is shown. In some specific implementations, the wireless communication device 800 is configured to perform reference... Figure 10 The process described is 1000. Wireless communication device 800 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, components, or devices that individually or collectively constitute or include a processing system. The processing system may interface with other components of wireless communication device 800 and typically processes information (such as inputs or signals) received from and outputs information (such as outputs or signals) to such other components. In some embodiments, an example chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, enabling wireless communication device 800 to transmit information output from the chip. The second interface may refer to an interface between the chip's processing system and a receiving component, enabling wireless communication device 800 to receive information, which is then passed to the processing system. In some embodiments, the first interface may also, for example, acquire information from the transmitting component, and the second interface may also, for example, output information to the receiving component.

[0125] The processing system of the wireless communication device 800 includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as a central processing unit (CPU), graphics processing unit (GPU), neural processing unit (NPU) (also referred to as a neural network processor or deep learning processor (DLP)) or digital signal processor (DSP)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuitry, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories may be coupled to one or more processors and may store processor-executable code, individually or collectively, which, when executed by one or more processors, configures one or more processors to perform the various functions or operations described herein. Additionally or alternatively, in some embodiments, one or more processors may be pre-configured to perform the various functions or operations described herein without software configuration. The processing system may also include or be coupled to one or more modems (such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem). In some embodiments, one or more processors of the processing system may include or implement one or more modems. The processing system may also include or be coupled to multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. In some embodiments, the processing system may include multiple independent or interconnected processing systems.

[0126] In some specific implementations, the wireless communication device 800 may be configured for or be configured to be used in STAs (e.g., non-AP STAs or non-AP MLDs) such as references Figure 1 The STA 104 described herein is used. In some other embodiments, the wireless communication device 800 may be a STA (e.g., a non-AP STA or a non-AP MLD) that includes such a processing system as well as other components including multiple antennas. The wireless communication device 800 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 800 may be configured or configured to transmit and receive packets in the form of PPDUs and MPDUs conforming to one or more of the IEEE 802.11 wireless communication protocol family of standards. In some other embodiments, the wireless communication device 800 may be configured or configured to transmit and receive signals and communications conforming to one or more 3GPP specifications, including those for 5G NR or 6G. In some embodiments, the wireless communication device 800 also includes one or more application processors or may be coupled to such application processors, which may also be coupled to one or more other memories. In some embodiments, the wireless communication device 800 also includes a user interface (UI) (such as a touchscreen or keypad) and a display that may be integrated with the UI to form a touchscreen display coupled to the processing system. In some implementations, the wireless communication device 800 may also include one or more sensors, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors coupled to the processing system.

[0127] Wireless communication device 800 includes a first link component 825, a TSF component 830, a second link component 835, a beam scanning component 840, a reporting component 845, and an NSA mode component 850. A portion of one or more of the first link component 825, TSF component 830, second link component 835, beam scanning component 840, reporting component 845, and NSA mode component 850 can be implemented at least partially in hardware or firmware. For example, one or more of the first link component 825, TSF component 830, second link component 835, beam scanning component 840, reporting component 845, and NSA mode component 850 can be implemented at least partially by a processor or modem. In some embodiments, portions of one or more of the first link component 825, TSF component 830, second link component 835, beam scanning component 840, reporting component 845, and NSA mode component 850 can be implemented at least partially by a processor and software in the form of processor-executable code stored in memory.

[0128] Wireless communication device 800 may support wireless communication according to examples disclosed herein. First link component 825 may be configured or configured to communicate with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication. Wireless communication devices, processing systems, or both may convey information by transmitting (or otherwise outputting) information, receiving (or otherwise acquiring) information, or a combination thereof. That is, “communication” may involve transmitting, outputting, receiving, acquiring, or any other form of communication. TSF component 830 may be configured or configured to receive, via the first link, an indication of a first TSF value associated with a second link between the AP MLD and non-AP MLDs (such as wireless communication device 800). Reporting component 845 may be configured or configured to communicate with the AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets used in a beam scanning process. In some implementations, the report may indicate a second TSF value associated with a scan packet received at the AP MLD for a beam scanning procedure performed at a non-AP MLD (such as wireless communication device 800), wherein the reporting component 845 may be configured or configured to receive or otherwise obtain the report from the AP MLD. In some other implementations, the report may indicate a second TSF value associated with a scan packet received at a non-AP MLD (such as wireless communication device 800) for a beam scanning procedure performed at the AP MLD, wherein the reporting component 845 may be configured or configured to send or otherwise output the report to the AP MLD. The second link component 835 may be configured or configured to communicate with the AP MLD via a second link corresponding to a second frequency band associated with directional communication, based on the beam scanning procedure (such as a second TSF value indicated for the beam scanning procedure) and a first TSF value associated with the second link. For example, the second link component 835 may be configured or configured to communicate with the AP MLD based on the first TSF value, the second TSF value, or both. The first TSF value can support timing synchronization between the first link and the second link, and the second TSF value can indicate the beam (such as the transmit beam) used for communication via the second link.

[0129] In some implementations, the beam scanning component 840 can be configured to or be configured to transmit one or more scan packets, wherein the one or more scan packets include a set of multiple scan packets associated with a set of multiple respective transmit beams for the beam scanning process, and wherein the scan packets for the set of multiple scan packets transmit a corresponding TSF value from a set of multiple TSF values.

[0130] In some implementations, the reporting component 845 can be configured or configured to receive a report indicating a second TSF value from a set of multiple TSF values. In some implementations, the beam scanning component 840 can be configured or configured to select a transmission beam for the second link corresponding to a scan packet associated with the second TSF value from a set of multiple scan packets.

[0131] In some implementations, the second TSF value is associated with the first link and is based on the first TSF value associated with the second link. In some other implementations, the second TSF value is associated with the second link.

[0132] In some implementations, the report is received via a first link, a second link, or both. In some implementations, the report is received via a multi-STA BA frame. In other implementations, the report is aggregated with downlink data used for non-AP MLD.

[0133] In some implementations, the report also indicates updated TSF values ​​for the first link or the second link of the AP MLD. In some implementations, selecting the transmit beam involves correcting a second TSF value based on the updated TSF value.

[0134] In some implementations, the beam scanning component 840 can be configured or be configured to receive, via a first link, an indication of a time period (such as a dedicated time period) for the beam scanning process, wherein a set of multiple TSF values ​​are within that time period.

[0135] In some implementations, the scan packets in the set of multiple scan packets include LTF, SIG, or both. In some implementations, each scan packet in the set of multiple scan packets includes the same pattern, such as the same bit pattern or the same waveform. In some implementations, the beam scanning component 840 can be configured or is configured to receive, via a first link, an indication of the same bit pattern or the same waveform for the set of multiple scan packets.

[0136] In some embodiments, the beam scanning component 840 can be configured or configured to receive one or more scan packets associated with one or more corresponding TSF values ​​used in the beam scanning process. In some embodiments, the reporting component 845 can be configured or configured to send a report indicating a second TSF value associated with a scan packet received from one or more scan packets that meets a signal strength threshold.

[0137] In some implementations, the second TSF value is associated with the first link and is based on the first TSF value associated with the second link. In some other implementations, the second TSF value is associated with the second link.

[0138] In some implementations, the report is transmitted via a first link, a second link, or both. In some implementations, the report is transmitted via a multi-STA BA frame.

[0139] In some implementations, the beam scanning component 840 can be configured or configured to monitor transmission periods for one or more scan packets via a second link, wherein the transmission periods may be common to a set of multiple non-AP MLDs. In some implementations, the reporting component 845 can be configured or configured to receive a TF associated with a transmission period via a first link, including a reported TB-PPDU transmitted via the first link based on that TF. In some implementations, the TF includes at least one of MU-BAR, a basic TF, BSRP, and short feedback polling variants such as Beamforming Reporting Polling (BFRP), Bandwidth Query Reporting Polling (BQRP), NFRP, BSRP, or a relatively short variant of any such polling signal. In some implementations, the TF indicates a dedicated RU for reporting transmission, an RA-RU for reporting transmission, or both. In some implementations, the report is transmitted via the RA-RU based on an AID value (such as a special AID value) dedicated to beamforming feedback reception for the second link.

[0140] In some implementations, the beam scanning component 840 can be configured or configured to receive, via a first link, a Short Feedback Report Poll, a BSRP, or both associated with beam training feedback. In some implementations, the beam scanning component 840 can be configured or configured to transmit, via the first link, a response frame indicating a training mode for a non-AP MLD based on the Short Feedback Report Poll, BSRP, or both, wherein the TF indicates a dedicated RU for the non-AP MLD based on the training mode indicated by the response frame in association with the beam training process.

[0141] In some implementations, the reporting component 845 can be configured or be configured to receive, via a first link, an indication of a channel access period (such as a special channel access period) associated with feedback for the beam scanning process, wherein the report is sent based on the channel access period.

[0142] In some implementations, the TSF component 830 can be configured or configured to receive an indication of an updated TSF value for a first link or a second link of the AP MLD, wherein the TSF value associated with the reception of scan packets is corrected based on the updated TSF value.

[0143] In some implementations, the reporting component 845 can be configured or configured to receive a TSF polling frame indicating a non-AP MLD via a first link, wherein the report is sent based on the TSF polling frame and via a frequency tone mapped to a TSF value associated with the reception of a scan packet. In some implementations, the reporting component 845 can be configured or configured to receive one or more polling messages (such as short feedback report polling) corresponding to one or more scan packets, wherein the report is sent based on a polling message (such as short feedback report polling) corresponding to a TSF value associated with the reception of a scan packet.

[0144] In some specific implementations, the NSA mode component 850 can be configured to or be configured to operate in NSA mode, wherein the first link includes a partner link for the second link in NSA mode.

[0145] In some implementations, the beam scanning component 840 can be configured or be configured to trigger the beam scanning process based on an establishment associated with the AP MLD, an inactive timer for a non-AP MLD, a reference signal indicating beam misalignment for a second band, or any combination thereof.

[0146] In some implementations, the TSF component 830 can be configured or configured to receive periodic updates to a first TSF value for a first link used for the AP MLD, a second TSF value for a second link used for the AP MLD, or both, wherein the periodic updates include partial or complete TSF values. In some implementations, the periodic updates include at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames. In some implementations, the field including partial or complete TSF values ​​is protected by integrity, encryption, or both. In some implementations, the TSF value includes a zero or non-zero value indicating the TSF offset between the first and second links.

[0147] In some implementations, the beam scanning component 840 can be configured to receive an indication of the start time of the beam scanning process and delay the start time of the beam scanning process according to the periodicity of the indicated start time.

[0148] Figure 9 A block diagram of an example wireless communication device 900 supporting IMW beam training for MLO is shown. In some specific implementations, the wireless communication device 900 is configured to perform reference... Figure 11The process described is 1100. Wireless communication device 900 may include one or more chips, SoCs, chipsets, packages, components, or devices that individually or collectively constitute or include a processing system. The processing system may interface with other components of wireless communication device 900 and typically processes information (such as inputs or signals) received from and outputs information (such as outputs or signals) to such other components. In some embodiments, an example chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, enabling wireless communication device 900 to transmit information output from the chip. The second interface may refer to an interface between the chip's processing system and a receiving component, enabling wireless communication device 900 to receive information, which is then passed to the processing system. In some embodiments, the first interface may also, for example, acquire information from a transmitting component, and the second interface may also, for example, output information to a receiving component.

[0149] The processing system of the wireless communication device 900 includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as CPUs, GPUs, NPUs (also known as neural network processors or DLPs), or DSPs), processing blocks, ASICs, PLDs (such as FPGAs), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuitry, each of which may include tangible storage media such as RAM or ROM or combinations thereof (all of which are generally referred to herein individually as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories may be coupled to one or more processors and may individually or collectively store processor-executable code that, when executed by one or more processors, configures one or more processors to perform the various functions or operations described herein. Additionally or alternatively, in some embodiments, one or more processors in the processing system may be pre-configured to perform the various functions or operations described herein without requiring software configuration. The processing system may also include or be coupled to one or more modems (such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem). In some embodiments, one or more processors in the processing system include or implement one or more modems in the modems. The processing system may also include or be coupled to multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas in a plurality of antennas. In some embodiments, one or more processors in the processing system include or implement one or more of the radio components, RF chains, or transceivers.

[0150] In some specific implementations, the wireless communication device 900 may be configured to be used for or configured to be used in an AP (e.g., AP STA or AP MLD) such as a reference. Figure 1The described AP 102 is used. In some other embodiments, the wireless communication device 900 may be an AP (e.g., AP STA or APMLD) that includes such a processing system and other components including multiple antennas. The wireless communication device 900 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 900 may be configured or configured to transmit and receive packets in the form of PPDUs and MPDUs conforming to one or more of the IEEE 802.11 wireless communication protocol family of standards. In some other embodiments, the wireless communication device 900 may be configured or configured to transmit and receive signals and communications conforming to one or more 3GPP specifications, including those for 5G NR or 6G. In some embodiments, the wireless communication device 900 also includes one or more application processors or may be coupled to such application processors, which may also be coupled to one or more other memories. In some embodiments, the wireless communication device 900 also includes at least one external network interface coupled to the processing system, which enables communication with the core network or backhaul network implementing the wireless communication device 900 to obtain access to external networks, including the Internet.

[0151] Wireless communication device 900 includes a first link component 925, a TSF component 930, a second link component 935, a beam scanning component 940, a reporting component 945, a preemption component 950, and a feedback scheme component 955. One or more of the first link component 925, TSF component 930, second link component 935, beam scanning component 940, reporting component 945, preemption component 950, and feedback scheme component 955 can be implemented at least partially in hardware or firmware. For example, one or more of the first link component 925, TSF component 930, second link component 935, beam scanning component 940, reporting component 945, preemption component 950, and feedback scheme component 955 can be implemented at least partially by a processor or a modem. In some specific implementations, portions of one or more of the first link component 925, TSF component 930, second link component 935, beam scanning component 940, reporting component 945, preemption component 950, and feedback scheme component 955 may be implemented, at least in part, by a processor and software in the form of processor-executable code stored in memory.

[0152] Wireless communication device 900 may support wireless communication according to examples disclosed herein. First link component 925 may be configured or configured to communicate with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication. TSF component 930 may be configured or configured to transmit via the first link an indication of a first TSF value associated with a second link between the AP MLD (such as wireless communication device 900) and the non-AP MLD. Reporting component 945 may be configured or configured to communicate with the non-AP MLD a report indicating a second TSF value associated with the reception of a scan packet in one or more scan packets for a beam scanning procedure. In some embodiments, the report may indicate a second TSF value associated with a scan packet received at the AP MLD (such as wireless communication device 900) for a beam scanning procedure performed at the non-AP MLD, wherein reporting component 945 may be configured or configured to transmit or otherwise output the report to the non-AP MLD. In some other implementations, the report may indicate a second TSF value associated with a scan packet received at a non-AP MLD for a beam scanning procedure performed at an APMLD (such as wireless communication device 900), wherein the reporting component 945 may be configured or configured to receive or otherwise obtain the report from the non-AP MLD. The second link component 935 may be configured or configured to communicate with the non-AP MLD via a second link corresponding to a second frequency band associated with directional communication, based on the beam scanning procedure (such as the second TSF value indicated for the beam scanning procedure) and a first TSF value associated with the second link. For example, the second link component 935 may be configured or configured to communicate with the non-AP MLD based on the first TSF value, the second TSF value, or both. The first TSF value may support timing synchronization between the first and second links, and the second TSF value may indicate the beam (such as a transmit beam) used for communication via the second link.

[0153] In some specific implementations, the beam scanning component 940 can be configured or configured to transmit one or more scan packets, wherein the one or more scan packets include a set of multiple scan packets associated with a set of multiple respective transmit beams for the beam scanning process, and wherein the scan packets for the set of multiple scan packets transmit a corresponding TSF value from a set of multiple TSF values.

[0154] In some implementations, the reporting component 945 can be configured or configured to receive a report associated with a non-AP MLD indicating a second TSF value from a set of multiple TSF values. In some implementations, the beam scanning component 940 can be configured or configured to select a transmission beam for the second link corresponding to a scan packet associated with the second TSF value from a set of multiple scan packets.

[0155] In some implementations, the second TSF value is associated with the first link and is based on the first TSF value associated with the second link. In some other implementations, the second TSF value is associated with the second link.

[0156] In some implementations, the report is received via a first link, a second link, or both. In some implementations, the report is received via a multi-STA BA frame.

[0157] In some implementations, the reporting component 945 can be configured or be configured to transmit via a first link an indication of a channel access period (such as a special channel access period) associated with feedback for the beam scanning process, wherein the report is received based on the channel access period.

[0158] In some implementations, the TSF component 930 can be configured or is configured to send an indication of an updated TSF value for a first link or a second link of the AP MLD, wherein the second TSF value is based on the updated TSF value.

[0159] In some implementations, the reporting component 945 can be configured to, or be configured to, transmit a TSF polling frame indicating a non-AP MLD via a first link, wherein the report is received based on the TSF polling frame and is received via a frequency tone mapped to the indicated TSF.

[0160] In some implementations, the reporting component 945 can be configured to send a set of multiple polling messages (such as short feedback report polling) corresponding to a set of multiple scan groups, wherein a report is received based on a polling message corresponding to a second TSF value from the set of multiple polling messages.

[0161] In some implementations, the scan packets in the set of multiple scan packets include LTF, SIG, or both. In some implementations, each scan packet in the set of multiple scan packets includes the same pattern, such as the same bit pattern or the same waveform. In some implementations, the beam scanning component 940 can be configured or is configured to transmit an indication of the same pattern (such as the same bit pattern or the same waveform) for the set of multiple scan packets via a first link.

[0162] In some implementations, the set of multiple TSF values ​​is transmitted within a transmission period for a set of multiple scan packets via a second link, wherein the transmission period may be common to the set of multiple non-AP MLDs. In some implementations, the reporting component 945 can be configured or is configured to receive a set of multiple reports associated with the set of multiple non-AP MLDs according to the transmission period, the set of multiple reports indicating the corresponding TSF values ​​in the set of multiple TSF values. In some implementations, the set of multiple reports is received via a multi-STA BA frame.

[0163] In some implementations, the reporting component 945 can be configured to, or be configured to, transmit a TF associated with a transmission period via a first link, wherein a TB-PPDU of a set of multiple reports is received according to the TF. In some implementations, the TF includes at least one of MU-BAR, basic TF, BSRP, and short feedback polling variants. In some implementations, the TF indicates one or more dedicated RUs, one or more RA-RUs, or combinations thereof for the set of multiple reports.

[0164] In some specific implementations, in order to support the reception of a set of multiple reports, the reporting component 945 can be configured or be configured to receive reports associated with non-AP MLDs via one or more RA-RUs based on AID values ​​(such as special AID values) dedicated to beamforming feedback reception for the second link.

[0165] In some implementations, the reporting component 945 can be configured or configured to transmit a short feedback report poll, BSRP, or both associated with beam training feedback via a first link. In some implementations, the reporting component 945 can be configured or configured to receive a response frame indicating a training mode for non-AP MLD via the first link based on the short feedback report poll, BSRP, or both, wherein the TF indicates a dedicated RU for non-AP MLD based on the training mode indicated by the response frame in association with the beam training process.

[0166] In some implementations, a set of multiple corresponding transmit beams is associated with a first sector subset for the AP MLD, and the beam scanning component 940 can be configured or configured to transmit a set of a second plurality of scan packets associated with a second plurality of corresponding transmit beams during a second transmission period, wherein the second plurality of corresponding transmit beams is associated with a second sector subset for the AP MLD, which is different from the first sector subset.

[0167] In some embodiments, the beam scanning component 940 can be configured or configured to receive one or more scan packets associated with one or more corresponding TSF values ​​used in the beam scanning process. In some embodiments, the reporting component 945 can be configured or configured to send a report indicating a TSF value associated with one or more scan packets received, which scan packets meet a signal strength threshold.

[0168] In some implementations, the second TSF value is associated with the first link and is based on the first TSF value associated with the second link. In some other implementations, the second TSF value is associated with the second link.

[0169] In some implementations, the report is transmitted via a first link, a second link, or both. In some implementations, to support report transmission, the reporting component 945 can be configured or is configured to aggregate the report with downlink data used for non-APMLD. In some implementations, the report also indicates updated TSF values ​​for the first link used for AP MLD or the second link used for APMLD.

[0170] In some implementations, the beam scanning component 940 can be configured or configured to transmit an indication of a time period (such as a dedicated time period) for the beam scanning process via a first link. In some implementations, the beam scanning component 940 can be configured or configured to monitor a time period for one or more scan packets via a second link, wherein one or more corresponding TSF values ​​are within that time period.

[0171] In some implementations, the TSF component 930 can be configured or configured to send periodic updates to a first TSF value associated with a second link of the AP MLD, wherein the periodic updates to the first TSF value include a partial TSF value or a complete TSF value. In some implementations, the periodic updates include at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames. In some implementations, the field including a partial TSF value or a complete TSF value is protected by integrity, encryption, or both.

[0172] In some implementations, the preemption component 950 can be configured or configured to send a preemption request to the additional non-AP MLD associated with preempting the additional non-AP MLD via the TXOP of the first frequency band. In some implementations, the reporting component 945 can be configured or configured to transmit, via the first link, a report associated with a beam scanning process for the non-AP MLD via the preempted TXOP.

[0173] In some implementations, the reporting component 945 can be configured or is configured to transmit reports associated with beam scanning procedures for non-AP MLDs via a first link, through the resources of one or more TDMs of the TXOP associated with the additional AP MLD via a first frequency band.

[0174] In some implementations, the feedback scheme component 955 can be configured or be configured to select a feedback scheme based on the number of first sectors associated with the beam scanning process, the number of second non-AP MLDs associated with the beam scanning process, or a combination thereof. In some implementations, the feedback scheme may include a preemption-based feedback scheme, a TXOP-based feedback scheme, a first TSF polling feedback scheme associated with one or more STAs, a second TSF polling feedback scheme associated with one or more beams, or any combination thereof.

[0175] In some specific implementations, the first TSF value includes a zero or non-zero value indicating the TSF offset between the first link and the second link.

[0176] In some implementations, the beam scanning component 940 can be configured to, or be configured to, send an indication of the start time of the beam scanning process, and delay the start time of the beam scanning process according to the periodicity of the indicated start time.

[0177] Figure 10 A flowchart illustrating an example process 1000 that can be executed by or at a non-AP MLD supporting IMW beam training for MLO is shown. Operation of process 1000 can be implemented by a non-AP MLD or its components as described herein. For example, process 1000 can be executed by a wireless communication device (such as a reference STA) operating as a wireless STA or within a wireless STA. Figure 8 The described wireless communication device 800) performs the process. In some specific implementations, process 1000 may be performed by a wireless STA (such as reference STA). Figure 1 The described STA 104 is executed.

[0178] In some specific implementations, in 1005, the non-AP MLD can communicate with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication. The operation of 1005 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1005 can be derived from references... Figure 8 The first link component 825 described herein shall be used to perform this action.

[0179] In some specific implementations, in 1010, a non-AP MLD can receive an indication of a first TSF value associated with a second link of the AP MLD via a first link. The operation of 1010 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1010 can be derived from references... Figure 8 The TSF component 830 described is used for execution.

[0180] In some specific implementations, in 1015, the non-AP MLD can convey a report indicating a second TSF value associated with the reception of one or more scan packets in the beam scanning process. Operation of 1015 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1015 can be provided by reference to... Figure 8 The report component 845 described is used to perform this.

[0181] In some specific implementations, in 1020, a non-AP MLD can communicate with the AP MLD via a second link corresponding to a second frequency band associated with directional communication, based on a beam scanning procedure and a first TSF value associated with the second link. Operation of 1020 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1020 can be described by reference to... Figure 8 The second link component 835 described is used to perform this.

[0182] Figure 11 A flowchart illustrating an example process 1100 that can be executed by an AP MLD supporting IMW beam training for MLO, or at such an AP MLD, is shown. The operation of process 1100 can be implemented by an AP MLD or its components as described herein. For example, process 1100 can be implemented by a wireless communication device operating as a wireless AP or within a wireless STA (such as reference 2010). Figure 9 The described wireless communication device 900) performs the process. In some specific implementations, process 1100 may be performed by a wireless AP (such as reference 900). Figure 1 The described AP 102 is executed.

[0183] In some implementations, in 1105, the AP MLD can communicate with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication. Operation of 1105 can be performed according to the examples disclosed herein. In some implementations, aspects of the operation of 1105 can be derived from references... Figure 9 The first link component 925 described is used to perform this.

[0184] In some specific implementations, in 1110, the AP MLD can send an indication of a first TSF value associated with a second link of the AP MLD via a first link. The operation of 1110 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1110 can be derived from references... Figure 9 The TSF component 930 described is used for execution.

[0185] In some implementations, in 1115, the AP MLD can convey a report indicating a second TSF value associated with the reception of one or more scan packets in the beam scanning process. The operation of 1115 can be performed according to the examples disclosed herein. In some implementations, aspects of the operation of 1115 can be provided by reference to... Figure 9 The report component 945 described is used to perform this.

[0186] In some specific implementations, in 1120, the AP MLD can communicate with a non-AP MLD via a second link corresponding to a second frequency band associated with directional communication, based on a beam scanning process and a first TSF value associated with the second link. Operation of 1120 can be performed according to the examples disclosed herein. In some specific implementations, aspects of the operation of 1120 can be derived from references... Figure 9 The second link component 935 described is used to perform this.

[0187] Specific implementation examples are described in the following numbered clauses:

[0188] Aspect 1: A non-AP MLD comprising: a processing system including processor circuitry and memory circuitry storing code, the processing system being configured to cause the non-AP MLD to: communicate with an AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; obtain, via the first link, an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD; communicate with the AP MLD a report indicating a second TSF value associated with reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the AP MLD via the second link corresponding to a second frequency band associated with directional communication based on the beam scanning process and the first TSF value associated with the second link.

[0189] Aspect 2: The non-AP MLD according to Aspect 1, wherein the processing system is further configured to cause the non-AP MLD to: output the one or more scan packets, wherein the one or more scan packets comprise a set of multiple scan packets associated with a set of multiple corresponding transmit beams for the beam scanning process, and wherein the report is obtained according to the beam scanning process.

[0190] Aspect 3: The non-AP MLD according to aspect 2, wherein the processing system is further configured to cause the non-AP MLD to: select a transmit beam for the second link corresponding to the scan packet in the one or more scan packets, based on the report indicating the second TSF value associated with the reception of the scan packet.

[0191] Aspect 4: The non-AP MLD according to aspect 3, wherein the report further indicates an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, and wherein selecting the transmit beam includes: correcting the second TSF value associated with the reception of the scan packet based on the updated TSF value.

[0192] Aspect 5: Non-AP MLD according to any one of Aspects 2 to 4, wherein the report is obtained via the first link, via the second link, or both.

[0193] Aspect 6: The non-AP MLD according to any one of Aspects 2 to 5, wherein the report is aggregated with downlink data for the non-AP MLD.

[0194] Aspect 7: Non-AP MLD according to any one of Aspects 2 to 5, wherein the report is obtained via multiple STA BA frames.

[0195] Aspect 8: A non-AP MLD according to any one of Aspects 2 to 7, wherein the processing system is further configured to cause the non-AP MLD to: obtain an indication of a time period for the beam scanning process via the first link, wherein the set of the plurality of TSF values ​​is within the time period.

[0196] Aspect 9: The non-AP MLD according to any one of Aspects 2 to 8, wherein each scan group in the set of the plurality of scan groups includes LTF, SIG, or both.

[0197] Aspect 10: The non-AP MLD according to any one of Aspects 2 to 9, wherein each scan group in the set of the plurality of scan groups includes the same bit pattern.

[0198] Aspect 11: The non-AP MLD according to aspect 10, wherein the processing system is further configured to cause the non-AP MLD to: obtain an indication of the same bit pattern for the set of the plurality of scan packets via the first link.

[0199] Aspect 12: The non-AP MLD according to any one of Aspects 2 to 11, wherein the scan packets for the set of the plurality of scan packets transmit corresponding TSF values ​​from the set of the plurality of TSF values.

[0200] Aspect 13: A non-AP MLD according to any one of Aspects 1 to 12, wherein the processing system is further configured to cause the non-AP MLD to: obtain the one or more scan groups for the beam scanning process, wherein the one or more scan groups are associated with one or more corresponding TSF values, and the report is output based on obtaining the one or more scan groups and the scan groups satisfying a signal strength threshold.

[0201] Aspect 14: The non-AP MLD according to aspect 13, wherein the report is output via the first link, via the second link, or both.

[0202] Aspect 15: Non-AP MLD according to any one of Aspects 13 or 14, wherein the report is output via multiple STABA frames.

[0203] Aspect 16: A non-AP MLD according to any one of Aspects 13 to 15, wherein the processing system is further configured to cause the non-AP MLD to: monitor the transmission period for the one or more scan packets via the second link, wherein the transmission period is common to the set of multiple non-AP MLDs.

[0204] Aspect 17: The non-AP MLD according to aspect 16, wherein the processing system is further configured to cause the non-AP MLD to: obtain a trigger indication associated with the transmission period via the first link, wherein the report is output via the first link according to the trigger indication.

[0205] Aspect 18: The non-AP MLD according to aspect 16, wherein the processing system is further configured to enable the non-AP MLD to: obtain the TF associated with the transmission period via the first link.

[0206] Aspect 19: The non-AP MLD according to aspect 18, wherein: the TF includes at least one of MU-BAR, basic TF, BSRP and short feedback polling variants; the TF indicates a dedicated RU for sending the report, an RA-RU for sending the report, or both; or any combination thereof.

[0207] Aspect 20: The non-AP MLD according to aspect 19, wherein the report is output via the RA-RU based on the AID value received via beamforming feedback dedicated to the second link.

[0208] Aspect 21: A non-AP MLD according to any one of Aspects 18 to 20, wherein the processing system is further configured to cause the non-AP MLD to: obtain a short feedback report poll, BSRP, or both associated with beam training feedback via the first link; and output a response frame indicating a training mode for the non-AP MLD via the first link according to the short feedback report poll, the BSRP, or both, wherein the TF indicates a dedicated RU for the non-AP MLD according to the response frame indicating that the training mode is associated with the beam training process.

[0209] Aspect 22: The non-AP MLD according to any one of Aspects 18 to 21, including the reported TB-PPDU being output via the first link according to the TF.

[0210] Aspect 23: A non-AP MLD according to any one of Aspects 13 to 22, wherein the processing system is further configured to cause the non-AP MLD to: obtain via the first link an indication of a channel access period associated with feedback for the beam scanning process, wherein the report is output based on the channel access period.

[0211] Aspect 24: A non-AP MLD according to any one of Aspects 13 to 23, wherein the processing system is further configured to cause the non-AP MLD to: obtain an indication of an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein the second TSF value associated with the reception of the scan packet is corrected based on the updated TSF value.

[0212] Aspect 25: A non-AP MLD according to any one of Aspects 13 to 24, wherein the processing system is further configured to cause the non-AP MLD to: obtain a TSF polling frame indicating the non-AP MLD via the first link, wherein the report is output based on the TSF polling frame and is output via a frequency tone mapped to the second TSF value associated with the reception of the scan packet.

[0213] Aspect 26: A non-AP MLD according to any one of Aspects 13 to 25, wherein the processing system is further configured to cause the non-AP MLD to: obtain one or more polling messages corresponding to the one or more scan packets, wherein the report is output based on a polling message in the one or more polling messages corresponding to the second TSF value associated with the reception of the scan packet.

[0214] Aspect 27: The non-AP MLD according to any one of Aspects 1 to 26, wherein: the second TSF value associated with the reception of the scan packet is also associated with the first link and the first TSF value is associated with the second link; or the second TSF value associated with the reception of the scan packet is also associated with the second link.

[0215] Aspect 28: A non-AP MLD according to any one of Aspects 1 to 27, wherein the processing system is further configured to cause the non-AP MLD to operate in NSA mode, wherein the first link includes a partner link for the second link in the NSA mode.

[0216] Aspect 29: A non-AP MLD according to any one of Aspects 1 to 28, wherein the processing system is further configured to cause the non-AP MLD to trigger the beam scanning process based on the establishment of an association with the AP MLD, an inactive timer for the non-AP MLD, a reference signal indicating beam misalignment for the second frequency band, or any combination thereof.

[0217] Aspect 30: A non-AP MLD according to any one of Aspects 1 to 29, wherein the processing system is further configured to cause the non-AP MLD to: obtain periodic updates to a third TSF value for the first link of the AP MLD, a fourth TSF value for the second link of the AP MLD, or both, wherein the periodic updates include partial TSF values ​​or complete TSF values.

[0218] Aspect 31: The non-AP MLD according to aspect 30, wherein: the periodic update includes at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames; the field including the partial TSF value or the full TSF value is protected by integrity, encryption, or both; or any combination thereof.

[0219] Aspect 32: The non-AP MLD according to any one of Aspects 1 to 31, wherein the first TSF value associated with the second link includes a zero or non-zero value indicating the TSF offset between the first link and the second link.

[0220] Aspect 33: A non-AP MLD according to any one of Aspects 1 to 32, wherein the processing system is further configured to cause the non-AP MLD to: obtain an indication of the start time of the beam scanning process; and delay the start time of the beam scanning process according to the periodicity of the indication of the start time.

[0221] Aspect 34: An AP MLD comprising: a processing system including processor circuitry and memory circuitry storing code, the processing system being configured to cause the AP MLD to: communicate with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; output an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD via the first link; communicate with the non-AP MLD a report indicating a second TSF value associated with reception of a scan packet in one or more scan packets for a beam scanning process; and communicate with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication based on the beam scanning process and the first TSF value associated with the second link.

[0222] Aspect 35: According to the AP MLD of aspect 34, wherein the processing system is further configured to cause the AP MLD to: output the one or more scan packets, wherein the one or more scan packets include a set of multiple scan packets associated with a set of multiple corresponding transmit beams for the beam scanning process, and wherein the report is obtained according to the beam scanning process.

[0223] Aspect 36: According to the AP MLD of aspect 35, wherein the processing system is further configured to cause the AP MLD to: select a transmission beam for the second link corresponding to the scan packet in the one or more scan packets, based on the report indicating a second TSF value associated with the reception of the scan packet.

[0224] Aspect 37: AP MLD according to any one of Aspects 35 or 36, wherein the report is obtained via the first link, via the second link, or both.

[0225] Aspect 38: AP MLD according to any one of Aspects 35 to 37, wherein the report is obtained via multiple STA BA frames.

[0226] Aspect 39: The AP MLD according to any one of Aspects 35 to 38, wherein the processing system is further configured to cause the AP MLD to output an indication of a channel access period associated with feedback for the beam scanning process via the first link, wherein the report is obtained based on the channel access period.

[0227] Aspect 40: The AP MLD according to any one of Aspects 35 to 39, wherein the processing system is further configured to cause the AP MLD to: output an indication of an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein the second TSF value is corrected based on the updated TSF value.

[0228] Aspect 41: According to any one of Aspects 35 to 40, the AP MLD, wherein the processing system is further configured to cause the AP MLD to: output a TSF polling frame of the non-AP MLD via the first link, wherein the report is obtained based on the TSF polling frame and is obtained via a frequency tone mapped to the second TSF value associated with the reception of the scan packet.

[0229] Aspect 42: The AP MLD according to any one of Aspects 35 to 41, wherein the processing system is further configured to cause the AP MLD to output a set of multiple polling messages corresponding to the set of the plurality of scan packets, wherein the report is obtained based on a polling message in the set of the plurality of polling messages corresponding to the second TSF value associated with the reception of the scan packet.

[0230] Aspect 43: AP MLD according to any one of Aspects 35 to 42, wherein each scan group in the set of the plurality of scan groups includes LTF, SIG or both.

[0231] Aspect 44: According to any one of Aspects 35 to 43, each scan group in the set of the plurality of scan groups includes the same bit pattern.

[0232] Aspect 45: According to aspect 44, the AP MLD is further configured to cause the AP MLD to output an indication of the same bit pattern for the set of the plurality of scan packets via the first link.

[0233] Aspect 46: According to any one of Aspects 35 to 45, the set of said plurality of TSF values ​​is within a transmission period for the set of said plurality of scan packets, and said transmission period is common to the set of said plurality of non-AP MLDs.

[0234] Aspect 47: According to the AP MLD of aspect 46, wherein the processing system is further configured to cause the AP MLD to: obtain a set of multiple reports associated with the set of the plurality of non-AP MLDs according to the transmission period, the set of multiple reports indicating a corresponding TSF value in the set of the plurality of TSF values.

[0235] Aspect 48: According to the AP MLD of aspect 47, the set of the plurality of reports is obtained via multiple STA BA frames.

[0236] Aspect 49: The AP MLD according to any one of Aspects 47 or 48, wherein the processing system is further configured to cause the AP MLD to output a trigger indication associated with the transmission period via the first link, wherein the set of the plurality of reports is obtained according to the trigger indication.

[0237] Aspect 50: AP MLD according to any one of Aspects 47 or 48, wherein the processing system is further configured to cause the AP MLD to output a TF associated with the transmission period via the first link.

[0238] Aspect 51: AP MLD according to aspect 50, wherein: the TF includes at least one of MU-BAR, basic TF, BSRP and short feedback polling variants; the TF indicates one or more dedicated RUs, one or more RA-RUs or combinations thereof for the set of the plurality of reports; or any combination thereof.

[0239] Aspect 52: According to the AP MLD of aspect 51, wherein in order to obtain the set of the plurality of reports, the processing system is configured to cause the AP MLD to obtain reports associated with the non-AP MLD via one or more RA-RUs based on AID values ​​dedicated to beamforming feedback reception for the second link.

[0240] Aspect 53: According to any one of Aspects 50 to 52, the AP MLD, wherein the processing system is further configured to cause the AP MLD to: output a short feedback report poll, BSRP, or both associated with beam training feedback via the first link; and obtain a response frame indicating a training mode for the non-AP MLD via the first link based on the short feedback report poll, the BSRP, or both, wherein the TF indicates a dedicated RU for the non-AP MLD based on the response frame indicating that the training mode is associated with the beam training process.

[0241] Aspect 54: AP MLD according to any one of Aspects 50 to 53, wherein the TB-PPDU comprises a collection of the plurality of reports according to the TF.

[0242] Aspect 55: An AP MLD according to any one of Aspects 46 to 54, wherein the set of the plurality of corresponding transmit beams is associated with a first sector subset for the AP MLD, and the processing system is further configured to cause the AP MLD to: output a set of a second plurality of scan packets associated with a second plurality of corresponding transmit beams during a second transmit period, wherein the second plurality of corresponding transmit beams is associated with a second sector subset for the AP MLD, the second sector subset being different from the first sector subset.

[0243] Aspect 56: AP MLD according to any one of Aspects 35 to 55, wherein scan packets for the set of the plurality of scan packets are transmitted corresponding TSF values ​​in the set of the plurality of TSF values.

[0244] Aspect 57: According to any one of Aspects 34 to 56, the AP MLD, wherein the processing system is further configured to cause the AP MLD to: obtain the one or more scan groups for the beam scanning process, wherein the one or more scan groups are associated with one or more corresponding TSF values, and the report is output based on obtaining the one or more scan groups and the scan groups satisfying a signal strength threshold.

[0245] Aspect 58: The AP MLD according to aspect 57, wherein the report is output via the first link, via the second link, or both.

[0246] Aspect 59: According to any one of Aspects 57 or 58, the AP MLD, wherein in order to convey the report, the processing system is further configured to cause the AP MLD to: aggregate the report with downlink data for the non-AP MLD.

[0247] Aspect 60: AP MLD according to any one of Aspects 57 to 59, wherein the report further indicates an updated TSF value for the first link or the second link of the AP MLD.

[0248] Aspect 61: According to any one of Aspects 57 to 60, the AP MLD, wherein the processing system is further configured to cause the AP MLD to: output an indication of a time period for the beam scanning process via the first link; and monitor the time period for the one or more scan groups via the second link, wherein the one or more corresponding TSF values ​​are within the time period.

[0249] Aspect 62: According to any one of Aspects 34 to 61, the AP MLD is further configured to cause the AP MLD to: output a periodic update of the first TSF value associated with the second link of the AP MLD, wherein the periodic update of the first TSF value includes a partial TSF value or a complete TSF value.

[0250] Aspect 63: The AP MLD according to aspect 62, wherein: the periodic update includes at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames; the field including the partial TSF value or the complete TSF value is protected by integrity, encryption, or both; or any combination thereof.

[0251] Aspect 64: AP MLD according to any one of Aspects 34 to 63, wherein: the second TSF value associated with the reception of the scan packet is also associated with the first link and the first TSF value is associated with the second link; or the second TSF value associated with the reception of the scan packet is also associated with the second link.

[0252] Aspect 65: An AP MLD according to any one of Aspects 34 to 64, wherein the processing system is further configured to cause the AP MLD to: output a preemption request associated with a TXOP preempting the additional non-AP MLD via the first frequency band to an additional non-AP MLD, wherein the report is communicated via the preempted TXOP.

[0253] Aspect 66: AP MLD according to any one of Aspects 34 to 65, wherein the report is transmitted via the first frequency band through the resources of one or more TDMs of the TXOP associated with the additional AP MLD.

[0254] Aspect 67: According to any one of Aspects 34 to 66, the AP MLD is further configured to cause the AP MLD to select a feedback scheme based on the number of first sectors associated with the beam scanning process, the number of second non-AP MLDs associated with the beam scanning process, or a combination thereof.

[0255] Aspect 68: According to the AP MLD of aspect 67, the feedback scheme includes a preemption-based feedback scheme, a TXOP-based feedback scheme, a first TSF polling feedback scheme associated with one or more STAs, a second TSF polling feedback scheme associated with one or more beams, or any combination thereof.

[0256] Aspect 69: AP MLD according to any one of Aspects 34 to 68, wherein the first TSF value includes a zero or non-zero value indicating the TSF offset between the first link and the second link.

[0257] Aspect 70: According to any one of Aspects 34 to 69, the AP MLD, wherein the processing system is further configured to cause the AP MLD to: output an indication of the start time of the beam scanning process; and delay the start time of the beam scanning process according to the periodicity of the indication of the start time.

[0258] Aspect 71: A method for wireless communication at a non-AP MLD, the method comprising: communicating with an AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; receiving via the first link an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD; communicating with the AP MLD a report indicating a second TSF value associated with reception of a scan packet in one or more scan packets for a beam scanning process; and communicating with the AP MLD via the second link corresponding to a second frequency band associated with directional communication based on the beam scanning process and the first TSF value associated with the second link.

[0259] Aspect 72: The method according to aspect 71, the method further comprising: transmitting the one or more scan packets, wherein the one or more scan packets comprise a set of multiple scan packets associated with a set of multiple corresponding transmitted beams for the beam scanning process, and wherein the report is received according to the beam scanning process.

[0260] Aspect 73: The method according to aspect 72, the method further comprising: selecting a transmit beam for the second link corresponding to one or more scan packets based on the report indicating a second TSF value associated with the reception of the scan packet.

[0261] Aspect 74: The method according to aspect 73, wherein the report further indicates an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein selecting the transmit beam includes: correcting the second TSF value associated with the reception of the scan packet based on the updated TSF value.

[0262] Aspect 75: The method according to any one of aspects 72 to 74, wherein the report is received via the first link, via the second link, or both.

[0263] Aspect 76: The method according to any one of Aspects 72 to 75, wherein the report is aggregated with downlink data for the non-APMLD.

[0264] Aspect 77: The method according to any one of aspects 72 to 75, wherein the report is received via multiple STA BA frames.

[0265] Aspect 78: The method according to any one of aspects 72 to 77, the method further comprising: receiving via the first link an indication of a time period for the beam scanning process, wherein the set of the plurality of TSF values ​​is within the time period.

[0266] Aspect 79: The method according to any one of aspects 72 to 78, wherein each scan group in the set of the plurality of scan groups includes a long training field, a signal field, or both.

[0267] Aspect 80: The method according to any one of aspects 72 to 79, wherein each scan group in the set of the plurality of scan groups comprises the same bit pattern.

[0268] Aspect 81: The method according to aspect 80, the method further comprising: receiving, via the first link, an indication of the same bit pattern for a set of the plurality of scan groups.

[0269] Aspect 82: The method according to any one of aspects 72 to 81, wherein a corresponding TSF value from a set of multiple TSF values ​​is transmitted for a set of scan packets.

[0270] Aspect 83: The method according to any one of aspects 71 to 82, the method further comprising: receiving the one or more scan packets for the beam scanning process, wherein the one or more scan packets are associated with one or more corresponding TSF values, and the report is sent based on receiving the one or more scan packets and the scan packets satisfying a signal strength threshold.

[0271] Aspect 84: The method according to aspect 83, wherein the report is sent via the first link, via the second link, or both.

[0272] Aspect 85: The method according to any one of aspects 83 or 84, wherein the report is transmitted via multiple STA BA frames.

[0273] Aspect 86: The method according to any one of aspects 83 to 85, the method further comprising: monitoring the transmission period for the one or more scan packets via the second link, wherein the transmission period is common to a set of multiple non-AP MLDs.

[0274] Aspect 87: The method according to aspect 86, the method further comprising: receiving a trigger indication associated with the transmission period via the first link, wherein the report is transmitted via the first link according to the trigger indication.

[0275] Aspect 88: According to the method of aspect 86, the method further includes: receiving a TF associated with the transmission period via the first link.

[0276] Aspect 89: The method according to aspect 88, wherein: the TF includes at least one of MU-BAR, basic TF, BSRP and short feedback polling variants; the TF indicates a dedicated RU for sending the report, an RA-RU for sending the report, or both; or any combination thereof.

[0277] Aspect 90: The method according to aspect 89, wherein the report is transmitted via the RA-RU based on an AID value received specifically for beamforming feedback for the second link.

[0278] Aspect 91: The method according to any one of Aspects 88 to 90, the method further comprising: receiving via the first link a short feedback report poll, BSRP, or both associated with beam training feedback; and transmitting via the first link a response frame indicating a training mode for the non-AP MLD based on the short feedback report poll, the BSRP, or both, wherein the TF indicates a dedicated RU for the non-AP MLD based on the response frame indicating that the training mode is associated with the beam training process.

[0279] Aspect 92: The method according to any one of aspects 88 to 91, wherein the reported TB-PPDU is transmitted via the first link according to the TF.

[0280] Aspect 93: The method according to any one of aspects 83 to 92, the method further comprising: receiving via the first link an indication of a channel access period associated with feedback for the beam scanning process, wherein the report is sent according to the channel access period.

[0281] Aspect 94: The method according to any one of aspects 83 to 93, the method further comprising: receiving an indication of an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein the second TSF value associated with the reception of the scan packet is corrected based on the updated TSF value.

[0282] Aspect 95: The method according to any one of Aspects 83 to 94, the method further comprising: receiving a TSF polling frame indicating the non-AP MLD via the first link, wherein the report is sent according to the TSF polling frame and is sent via a frequency tone mapped to a second TSF value associated with the reception of the scan packet.

[0283] Aspect 96: The method according to any one of aspects 83 to 95, the method further comprising: receiving one or more polling messages corresponding to the one or more scan groups, wherein the report is sent based on a polling message in the one or more polling messages corresponding to the second TSF value associated with the reception of the scan group.

[0284] Aspect 97: The method according to any one of Aspects 71 to 96, wherein: the second TSF value associated with the reception of the scan packet is also associated with the first link and the first TSF value is associated with the second link; or the second TSF value associated with the reception of the scan packet is also associated with the second link.

[0285] Aspect 98: The method according to any one of aspects 71 to 97, the method further comprising: operating in NSA mode, wherein the first link includes a partner link for the second link in the NSA mode.

[0286] Aspect 99: The method according to any one of Aspects 71 to 98, the method further comprising: triggering the beam scanning process based on the establishment of an association with the APMLD, an inactive timer for the non-AP MLD, a reference signal indicating beam misalignment for the second frequency band, or any combination thereof.

[0287] Aspect 100: The method according to any one of aspects 71 to 99, the method further comprising: receiving periodic updates to a third TSF value for the first link of the AP MLD, a fourth TSF value for the second link of the AP MLD, or both, wherein the periodic update includes a partial TSF value or a complete TSF value.

[0288] Aspect 101: The method according to aspect 100, wherein: the periodic update includes at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames; the field including the partial TSF value or the complete TSF value is protected by integrity, encryption, or both; or any combination thereof.

[0289] Aspect 102: The method according to any one of aspects 71 to 101, wherein the first TSF value associated with the second link includes a zero value or a non-zero value indicating the TSF offset between the first link and the second link.

[0290] Aspect 103: The method according to any one of aspects 71 to 102, the method further comprising: receiving an indication of a start time for the beam scanning process; and delaying the start time of the beam scanning process according to the periodicity of the indication of the start time.

[0291] Aspect 104: A method for wireless communication at an AP MLD, the method comprising: communicating with a non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; transmitting via the first link an indication of a first TSF value associated with a second link between the AP MLD and the non-AP MLD; communicating with the non-AP MLD a report indicating a second TSF value associated with reception of a scan packet in one or more scan packets for a beam scanning process; and communicating with the non-AP MLD via the second link corresponding to a second frequency band associated with directional communication based on the beam scanning process and the first TSF value associated with the second link.

[0292] Aspect 105: The method according to aspect 104, the method further comprising: transmitting the one or more scan packets, wherein the one or more scan packets comprise a set of multiple scan packets associated with a set of multiple corresponding transmitted beams for the beam scanning process, and wherein the report is received according to the beam scanning process.

[0293] Aspect 106: The method according to aspect 105, the method further comprising: selecting a transmit beam for the second link corresponding to one or more scan packets based on the report indicating a second TSF value associated with the reception of the scan packet.

[0294] Aspect 107: The method according to any one of aspects 105 or 106, wherein the report is received via the first link, via the second link, or both.

[0295] Aspect 108: The method according to any one of aspects 105 to 107, wherein the report is received via multiple STA BA frames.

[0296] Aspect 109: The method according to any one of aspects 105 to 108, the method further comprising: transmitting via the first link an indication of a channel access period associated with feedback for the beam scanning process, wherein the report is received based on the channel access period.

[0297] Aspect 110: The method according to any one of aspects 105 to 109, the method further comprising: sending an indication of an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein the second TSF value is corrected based on the updated TSF value.

[0298] Aspect 111: The method according to any one of aspects 105 to 110, the method further comprising: transmitting a TSF polling frame indicating the non-AP MLD via the first link, wherein the report is received according to the TSF polling frame and is received via a frequency tone mapped to a second TSF value associated with the reception of the scan packet.

[0299] Aspect 112: The method according to any one of aspects 105 to 111, the method further comprising: sending a set of a plurality of polling messages corresponding to a set of the plurality of scan groups, wherein the report is received based on a polling message in the set of the plurality of polling messages corresponding to a second TSF value associated with the reception of the scan group.

[0300] Aspect 113: The method according to any one of aspects 105 to 112, wherein each scan group in the set of the plurality of scan groups includes LTF, SIG or both.

[0301] Aspect 114: The method according to any one of aspects 105 to 113, wherein each scan group in the set of the plurality of scan groups includes the same bit pattern.

[0302] Aspect 115: The method according to aspect 114, the method further comprising: transmitting via the first link an indication of the same bit pattern for the set of the plurality of scan packets.

[0303] Aspect 116: The method according to any one of aspects 105 to 115, wherein the set of the plurality of TSF values ​​is within a transmission period for the set of the plurality of scan packets, and wherein the transmission period is common to the set of the plurality of non-AP MLDs.

[0304] Aspect 117: The method according to aspect 116, the method further comprising: receiving, according to the transmission period, a set of multiple reports associated with the set of the plurality of non-AP MLDs, the set of multiple reports indicating a corresponding TSF value in the set of the plurality of TSF values.

[0305] Aspect 118: According to the method of aspect 117, the set of said plurality of reports is received via multiple STA BA frames.

[0306] Aspect 119: The method according to any one of aspects 117 or 118, the method further comprising: transmitting a trigger indication associated with the transmission period via the first link, wherein the set of the plurality of reports is received according to the trigger indication.

[0307] Aspect 120: The method according to any one of aspects 117 or 118, the method further comprising: transmitting a TF associated with the transmission period via the first link.

[0308] Aspect 121: The method according to aspect 120, wherein: the TF includes at least one of MU-BAR, basic TF, BSRP and short feedback polling variants; the TF indicates one or more dedicated RUs, one or more RA-RUs or combinations thereof for the set of the plurality of reports; or any combination thereof.

[0309] Aspect 122: According to the method of aspect 121, receiving the set of the plurality of reports includes: receiving a report associated with the non-AP MLD via an RA-RU of the one or more RA-RUs based on an AID value received for beamforming feedback dedicated to the second link.

[0310] Aspect 123: The method according to any one of Aspects 120 to 122, the method further comprising: transmitting via the first link a short feedback report poll, BSRP, or both associated with beam training feedback; and receiving via the first link a response frame indicating a training mode for the non-AP MLD based on the short feedback report poll, the BSRP, or both, wherein the TF indicates a dedicated RU for the non-AP MLD based on the response frame indicating that the training mode is associated with the beam training process.

[0311] Aspect 124: The method according to any one of aspects 120 to 123, wherein the TB-PPDU comprises a collection of the plurality of reports according to the TF.

[0312] Aspect 125: The method according to any one of Aspects 116 to 124, wherein the set of the plurality of corresponding transmit beams is associated with a first sector subset for the AP MLD, the method further comprising: transmitting during a second transmit period a set of a second plurality of scan packets associated with a second set of the plurality of corresponding transmit beams, wherein the second set of the plurality of corresponding transmit beams is associated with a second sector subset for the AP MLD, the second sector subset being different from the first sector subset.

[0313] Aspect 126: The method according to any one of aspects 105 to 125, wherein a corresponding TSF value from a set of multiple TSF values ​​is transmitted for a set of scan packets.

[0314] Aspect 127: The method according to any one of aspects 104 to 126, the method further comprising: receiving the one or more scan packets for the beam scanning process, wherein the one or more scan packets are associated with one or more corresponding TSF values, and the report is sent based on receiving the one or more scan packets and the scan packets satisfying a signal strength threshold.

[0315] Aspect 128: The method according to aspect 127, wherein the report is sent via the first link, via the second link, or both.

[0316] Aspect 129: The method according to any one of Aspects 127 or 128, wherein communicating the report further includes: aggregating the report with downlink data for the non-AP MLD.

[0317] Aspect 130: The method according to any one of Aspects 127 to 129, wherein the report further indicates an updated TSF value for the first link of the AP MLD or the second link of the AP MLD.

[0318] Aspect 131: The method according to any one of aspects 127 to 130, the method further comprising: transmitting an indication of a time period for the beam scanning process via the first link; and monitoring the time period for the one or more scan groups via the second link, wherein the one or more corresponding TSF values ​​are within the time period.

[0319] Aspect 132: The method according to any one of aspects 104 to 131, the method further comprising: sending a periodic update to the first TSF value associated with the second link of the AP MLD, wherein the periodic update to the first TSF value includes a partial TSF value or a complete TSF value.

[0320] Aspect 133: The method according to aspect 132, wherein: the periodic update includes at least one of FD frames, broadcast probe response frames, and broadcast or individual addressing frames; the field including the partial TSF value or the complete TSF value is protected by integrity, encryption, or both; or any combination thereof.

[0321] Aspect 134: The method according to any one of aspects 104 to 133, wherein: the second TSF value associated with the reception of the scan packet is also associated with the first link and the first TSF value is associated with the second link; or the second TSF value associated with the reception of the scan packet is also associated with the second link.

[0322] Aspect 135: The method according to any one of aspects 104 to 134, the method further comprising: sending a preemption request to an additional non-AP MLD associated with a TXOP preempting the additional non-AP MLD via the first frequency band, wherein the report is communicated via the preempted TXOP.

[0323] Aspect 136: The method according to any one of Aspects 104 to 135, wherein the report is transmitted via the first frequency band via resources of one or more TDMs of the TXOP associated with the additional APMLD.

[0324] Aspect 137: The method according to any one of aspects 104 to 136, the method further comprising: selecting a feedback scheme based on a first sector number associated with the beam scanning process, a second non-AP MLD number associated with the beam scanning process, or a combination thereof.

[0325] Aspect 138: The method according to aspect 137, wherein the feedback scheme includes a preemption-based feedback scheme, a TXOP-based feedback scheme, a first TSF polling feedback scheme associated with one or more STAs, a second TSF polling feedback scheme associated with one or more beams, or any combination thereof.

[0326] Aspect 139: The method according to any one of aspects 104 to 138, wherein the first TSF value includes a zero value or a non-zero value indicating the TSF offset between the first link and the second link.

[0327] Aspect 140: The method according to any one of aspects 104 to 139, the method further comprising: sending an indication of a start time for the beam scanning process; and delaying the start time of the beam scanning process according to the periodicity of the indication of the start time.

[0328] As used herein, the term "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, estimation, investigation, searching (such as by searching in a table, database, or other data structure), reasoning, ascertaining, or measuring, as well as other possibilities. Additionally, "determine" can include receiving (such as receiving information) or accessing (such as accessing data stored in memory), and so on. Furthermore, "determine" can include parsing, selecting, obtaining, choosing, building, and other similar actions.

[0329] As used herein, the phrase “at least one of” or “one or more of” refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc. As used herein, “or” is intended to be interpreted in an inclusive sense unless otherwise explicitly indicated. For example, “a or b” may include only a, only b, or a combination of a and b. Furthermore, as used herein, the phrase referring to “one” element means one or more of such elements that act individually or collectively to perform the stated function. Additionally, “set” means one or more items, and “subset” means less than the entire set, but not empty.

[0330] As used herein, unless otherwise explicitly indicated, “based on” is intended to be interpreted in an inclusive sense. For example, unless otherwise explicitly indicated, “based on” may be used interchangeably with “at least partially based on,” “associated with,” “associated with,” or “according to.” Specifically, unless the phrase in the context means “based on only one” or an equivalent, whether it is “based on one” or “at least partially based on one,” it may be based solely on “one” or based on a combination of “one” and one or more other factors, conditions, or information.

[0331] The various exemplary components, logic units, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the examples disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of its functionality and exemplified in the various exemplary components, blocks, modules, circuits, and processes described above. Whether this functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0332] Various modifications to the examples described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the examples shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0333] Additionally, the various features described in this specification in the context of individual examples may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple examples. Thus, although features may be described above as functioning in a particular combination, and even initially claimed in this way, one or more features from the claimed combination may be removed from the combination in some embodiments, and the claimed combination may be for sub-combinations or variations thereof.

[0334] Similarly, although operations are depicted in a specific order in the diagrams, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the accompanying figures may schematically depict one or more example processes in the form of flowcharts or flow diagrams. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples described above should not be construed as requiring such separation in all examples, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. A non-access point (AP) multilink device (MLD), the non-access point (AP) multilink device (MLD) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the non-AP MLD to: Communicating with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; An indication of a first timing synchronization function (TSF) value associated with a second link between the AP MLD and the non-AP MLD is obtained via the first link; The AP MLD communicates a report indicating a second TSF value associated with the reception of one or more scan packets in the beam scanning process; as well as The AP MLD is communicated via the second link, which corresponds to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

2. The non-AP MLD of claim 1, wherein the processing system is further configured to cause the non-AP MLD to: The one or more scan packets are output, wherein the one or more scan packets include multiple scan packets associated with multiple corresponding transmit beams for the beam scanning process, and wherein the scan packets for the multiple scan packets transmit corresponding TSF values ​​among multiple TSF values, and the report is obtained according to the beam scanning process.

3. The non-AP MLD of claim 2, wherein the processing system is further configured to cause the non-AP MLD to: The transmit beam corresponding to the scan packet in the one or more scan packets is selected for the second link based on the report indicating the second TSF value associated with the reception of the scan packet.

4. The non-AP MLD according to claim 2, wherein: The report is obtained via the first link, via the second link, or both; The report is aggregated with downlink data used for the non-AP MLD; The report was obtained via a multi-station (STA) block acknowledgment (BA) frame; or Any combination of them.

5. The non-AP MLD of claim 2, wherein the processing system is further configured to cause the non-AP MLD to: An indication of a time period for the beam scanning process is obtained via the first link, wherein the plurality of TSF values ​​are within the time period.

6. The non-AP MLD of claim 1, wherein the processing system is further configured to cause the non-AP MLD to: The report is output based on the acquisition of the one or more scan groups for the beam scanning process, wherein the one or more scan groups are associated with one or more corresponding TSF values, and the report is output based on the acquisition of the one or more scan groups and the scan groups satisfying a signal strength threshold.

7. The non-AP MLD of claim 6, wherein the processing system is further configured to cause the non-AP MLD to: The second link monitors the transmission period for the one or more scan packets, wherein the transmission period is common to multiple non-AP MLDs.

8. The non-AP MLD of claim 7, wherein the processing system is further configured to cause the non-AP MLD to: A trigger frame (TF) associated with the transmission period is obtained via the first link, which includes the reported trigger-based physical layer convergence protocol (PLCP) protocol data unit (TB-PPDU) output via the first link based on the TF.

9. The non-AP MLD of claim 6, wherein the processing system is further configured to cause the non-AP MLD to: An indication of the channel access period associated with feedback for the beam scanning process is obtained via the first link, wherein the report is output based on the channel access period.

10. The non-AP MLD of claim 6, wherein the processing system is further configured to cause the non-AP MLD to: An indication is obtained of an updated TSF value for the first link or the second link of the AP MLD, wherein the second TSF value associated with the reception of the scan packet is corrected based on the updated TSF value.

11. The non-AP MLD of claim 6, wherein the processing system is further configured to cause the non-AP MLD to: A TSF polling frame indicating the non-AP MLD is obtained via the first link, wherein the report is output based on the TSF polling frame and is output via a frequency tone mapped to the second TSF value associated with the reception of the scan packet.

12. The non-AP MLD of claim 6, wherein the processing system is further configured to cause the non-AP MLD to: Obtain one or more polling messages corresponding to the one or more scan groups, wherein the report is output based on the polling message in the one or more polling messages corresponding to the second TSF value associated with the reception of the scan group.

13. The non-AP MLD of claim 1, wherein the processing system is further configured to cause the non-AP MLD to: The beam scanning process is triggered by the establishment of an association with the AP MLD, an inactive timer for the non-AP MLD, a reference signal indicating beam misalignment for the second frequency band, or any combination thereof.

14. An access point (AP) multilink device (MLD), the access point (AP) multilink device (MLD) comprising: A processing system, comprising processor circuitry and memory circuitry for storing code, is configured to cause the AP MLD to: Communicating with the non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; The first link outputs an indication of the first timing synchronization function (TSF) value associated with the second link between the AP MLD and the non-AP MLD; The non-AP MLD communicates a report of a second TSF value associated with the reception of one or more scan packets in the beam scanning process; as well as The non-AP MLD communicates via the second link, which corresponds to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

15. The AP MLD of claim 14, wherein the processing system is further configured to cause the AP MLD to: The one or more scan packets are output, wherein the one or more scan packets include multiple scan packets associated with multiple corresponding transmit beams for the beam scanning process, and wherein the scan packets for the multiple scan packets transmit corresponding TSF values ​​among multiple TSF values, and the report is obtained according to the beam scanning process.

16. The AP MLD of claim 15, wherein the processing system is further configured to cause the AP MLD to: The transmit beam corresponding to the scan packet in the one or more scan packets is selected for the second link based on the report indicating the second TSF value associated with the reception of the scan packet.

17. The AP MLD of claim 15, wherein the processing system is further configured to cause the AP MLD to: The first link output indicates the channel access period associated with the feedback for the beam scanning process, wherein the report is obtained based on the channel access period.

18. The AP MLD of claim 15, wherein the processing system is further configured to cause the AP MLD to: Output an indication of an updated TSF value for the first link of the AP MLD or the second link of the AP MLD, wherein the second TSF value is corrected based on the updated TSF value.

19. The AP MLD of claim 15, wherein the plurality of TSF values ​​are within a transmission period for the plurality of scan packets, and wherein the transmission period is common to the plurality of non-AP MLDs.

20. The AP MLD of claim 19, wherein the processing system is further configured to cause the AP MLD to: Multiple reports associated with the multiple non-AP MLDs are obtained based on the transmission period, and the multiple reports indicate the corresponding TSF value among the multiple TSF values.

21. The AP MLD of claim 14, wherein the processing system is further configured to cause the AP MLD to: The report is output based on the acquisition of the one or more scan groups for the beam scanning process, wherein the one or more scan groups are associated with one or more corresponding TSF values, and the report is output based on the acquisition of the one or more scan groups and the scan groups satisfying a signal strength threshold.

22. The AP MLD of claim 21, wherein the processing system is further configured to cause the AP MLD to: The first link outputs an indication of the time period used for the beam scanning process; and The time period for the one or more scan packets is monitored via the second link, wherein the one or more corresponding TSF values ​​are within the time period.

23. The AP MLD of claim 14, wherein the processing system is further configured to cause the AP MLD to: Output a preemption request to the additional non-AP MLD associated with preempting the transmission opportunity of the additional non-AP MLD via the first frequency band, wherein the report is communicated via the preempted transmission opportunity.

24. The AP MLD of claim 14, wherein the processing system is further configured to cause the AP MLD to: The feedback scheme is selected based on the number of first sectors associated with the beam scanning process, the number of second non-AP MLDs associated with the beam scanning process, or a combination thereof.

25. The AP MLD of claim 24, wherein the feedback scheme comprises a preemption-based feedback scheme, a transmission opportunity (TXOP) sharing-based feedback scheme, a first TSF polling feedback scheme associated with one or more radio stations (STAs), a second TSF polling feedback scheme associated with one or more beams, or any combination thereof.

26. A method for wireless communication at a non-access point (AP) multi-link device (MLD), the method comprising: Communicating with the AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; Receive an indication of a first timing synchronization function (TSF) value associated with a second link between the AP MLD and the non-AP MLD via the first link; The AP MLD communicates a report indicating a second TSF value associated with the reception of one or more scan packets in the beam scanning process; as well as The AP MLD is communicated via the second link, which corresponds to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

27. The method according to claim 26, further comprising: The one or more scan packets are transmitted, wherein the one or more scan packets include multiple scan packets associated with multiple corresponding transmit beams for the beam scanning process, and wherein the scan packets for the multiple scan packets transmit corresponding TSF values ​​among multiple TSF values, and the report is received according to the beam scanning process.

28. The method according to claim 26, further comprising: Receive one or more scan packets for the beam scanning process, wherein the one or more scan packets are associated with one or more corresponding TSF values, and the report is sent based on receiving the one or more scan packets and the scan packets meeting a signal strength threshold.

29. A method for wireless communication at an access point (AP) multilink device (MLD), the method comprising: Communicating with the non-AP MLD via a first link corresponding to a first frequency band associated with omnidirectional communication; Send an indication of a first timing synchronization function (TSF) value associated with a second link between the AP MLD and the non-AP MLD via the first link; The non-AP MLD communicates a report of a second TSF value associated with the reception of one or more scan packets in the beam scanning process; as well as The non-AP MLD communicates via the second link, which corresponds to a second frequency band associated with directional communication, based on the beam scanning process and the first TSF value associated with the second link.

30. The method according to claim 29, further comprising: The one or more scan packets are transmitted, wherein the one or more scan packets include multiple scan packets associated with multiple corresponding transmit beams for the beam scanning process, and wherein the scan packets for the multiple scan packets transmit corresponding TSF values ​​among multiple TSF values, and the report is received according to the beam scanning process.

Images