KR20240043146A - Non-simultaneous transmit-receive (NSTR) Soft access point (AP) Multi-link device (MLD) - Google Patents

Abstract

A radio station (STA) operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multiple link device (MLD) associated with the primary link and the non-primary link determines that the non-primary link is unusable, -Transmit only on the primary link a frame that returns an indication of the unavailability of the primary link. The NSTR softAP MLD can set the Do Not Transmit (DNT) bit to a value of 1 and operate as a single link device on the primary link based on the unavailability of the non-primary link. In some cases, the NSTR softAP MLD, while operating as a single link device on the primary link, determines that a non-primary link is available, resets the DNT bit based on the availability of the non-primary link, and resets the DNT bit in another frame. DNT is transmitted only on the basic link.

Description

Non-simultaneous transmit-receive (NSTR) Soft access point (AP) Multi-link device (MLD)

Cross-reference to related applications

This patent application is U.S. Patent Application No. 17/409,370, titled “NON-SIMULTANEOUS TRANSMIT-RECEIVE (NSTR) SOFT ACCESS POINT (AP) MULTI-LINK DEVICE (MLD),” filed on August 23, 2021. and claims priority to U.S. Patent Application No. 17/409,349, filed August 23, 2021, entitled “NON-SIMULTANEOUS TRANSMIT-RECEIVE (NSTR) SOFT ACCESS POINT (AP) MULTI-LINK DEVICE (MLD).” and these two applications were assigned to the assignee of the present application. The disclosures of all earlier applications are considered a part of this patent application and are incorporated by reference into this patent application.

Technology field

This disclosure relates generally to wireless communications, and more specifically to wireless communications associated with multi-link devices (MLDs).

A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by multiple client devices, also referred to as stations (STAs). The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is the Basic Service Set (BSS) managed by the AP. Each BSS is identified by a basic service set identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames, allowing any STAs within the wireless range of the AP to establish or maintain a communication link with the WLAN.

An AP multi-link device (MLD) may include multiple APs that can operate independently on multiple communication links. Each AP may establish a BSS on its respective communication link, and a wireless communication device associated with the AP MLD may transmit data to or receive data from the AP MLD on one or more communication links associated with the AP MLD. Each communication link can have varying bandwidths by combining multiple 20 MHz wide channels to form a 40 MHz wide channel, an 80 MHz wide channel, a 160 MHz wide channel, or a 320 MHz wide channel. It may be desirable for the STA to operate as a softAP MLD, although the STA may have limited filtering capabilities that may allow data reception on one link to interfere with data transmission on another link.

Each of the systems, methods, and devices of this disclosure have several innovative aspects, no single aspect of which is solely responsible for the desirable properties disclosed herein.

One innovative aspect of the subject matter described in this disclosure may be implemented in a method of wireless communication by a wireless station (STA). In some implementations, the method includes a non-simultaneous transmit-receive (NSTR) software comprising a first AP associated with a primary link and a second AP associated with a non-primary link. and operating as an access point (AP) multiple link device (MLD). The method includes determining that a non-default link is not available. The method includes transmitting a frame with an indication of unavailability of the non-primary link only on the primary link. The frame may be one of a beacon frame, probe response frame, association response frame, re-association response frame, or action frame. In some cases, the frame includes a Reduced Neighbor Report (RNR) element or a Per-STA profile sub-element that includes a Do Not Transmit (DNT) bit set to a value of 1. where the DNT bit set to a value of 1 indicates the unavailability of the non-primary link. In some examples, the frame includes a Capability Information field with a Critical Update Flag (CUF), where the CUF is set to a value of 1 based on the unavailability of the non-primary link.

In some implementations, the method may also include deactivating the non-primary link or placing the non-primary link in a power saving state based on the unavailability of the non-primary link. In some cases, deactivating the non-default link includes removing the non-default link from the multiple link context associated with the NSTR softAP MLD. Additionally, the method also includes determining that a non-primary link is available after removing the non-primary link from the multi-link context, and adding the non-primary link to the multi-link context based on the availability of the non-primary link. It may include steps. In some other cases, deactivating a non-default link includes remapping traffic identifiers (TIDs) from the non-default link to the default link. The method also includes determining that the non-primary link is available after deactivating the non-primary link, and remapping the TID from the primary link to the non-primary link based on the availability of the non-primary link. can do.

In some implementations, the method also includes operating as a single link device on the primary link based on unavailability of the non-primary link. In some cases, the method may also include determining whether a non-primary link is available while operating as a single link device on a primary link, resetting the DNT bit to a value of 0 based on the availability of the non-primary link. , and transmitting the reset DNT bit in another frame only on the primary link, wherein the other frame includes an STA-specific profile sub-element, or a reduced neighbor reporting (RNR) element with the reset DNT bit having a value of 0. Includes. In some other implementations, the method also includes determining that a non-primary link is available after sending the indication, transmitting an indication of the availability of the non-primary link only on the primary link, and and operating as a multi-link device on primary links and non-primary links based on availability.

In some implementations, the method also includes receiving a ready-to-send (RTS) frame from the STA MLD on the primary link, and transmitting a ready-to-send (RTS) frame on the primary link and the non-primary link based on receiving the RTS frame. It may include transmitting a CTS frame to the STA MLD, and receiving one or more UL PPDUs from the STA MLD on a primary link and a non-basic link. In some other implementations, the method may also include switching a primary link from a first channel to a second channel simultaneously with switching a non-primary link from a second channel to a first channel. In some cases, the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.

Other innovative aspects of the subject matter described in this disclosure can be implemented in a wireless communication device. In some implementations, a wireless communication device includes at least one modem, at least one processor communicatively coupled with the at least one modem, and storage communicatively coupled with the at least one processor and processor-readable code. May contain at least one memory. In some implementations, execution of processor readable code by at least one processor in conjunction with at least one modem causes the wireless communication device to include a first AP associated with a primary link and a second AP associated with a non-primary link. NSTR softAP can be configured to operate as an MLD. Execution of the processor-readable code may be configured to determine that the non-primary link is unavailable. Execution of the processor-readable code may be configured to transmit frames only on the primary link with an indication of unavailability of the non-primary link. The frame may be one of a beacon frame, probe response frame, association response frame, reassociation response frame, or action frame. In some cases, the frame includes a Reduced Neighbor Report (RNR) element or a Per-STA profile sub-element that includes a Do Not Transmit (DNT) bit set to a value of 1. where the DNT bit set to a value of 1 indicates the unavailability of the non-primary link. In some examples, the frame includes a Capability Information field with a Critical Update Flag (CUF), where the CUF is set to a value of 1 based on the unavailability of the non-primary link.

In some implementations, execution of the processor-readable code may be configured to disable the non-primary link or place the primary link in a sleep state based on the unavailability of the non-primary link. In some cases, deactivating the non-default link includes removing the non-default link from the multiple link context associated with the NSTR softAP MLD. Execution of the processor-readable code may also determine that a non-primary link is available after removing a non-primary link from a multi-link context, and to link a non-primary link to a multi-link context based on the availability of the non-primary link. A further step of adding may be included. In some other cases, deactivating a non-default link includes remapping traffic identifiers (TIDs) from the non-default link to the default link. The method may also include determining that the non-primary link is available after deactivating the non-primary link, and remapping the TID from the primary link to the non-primary link based on the availability of the non-primary link. You can.

In some implementations, execution of the processor readable code can also be configured to operate the wireless communication device as a single link device on the primary link based on the unavailability of the non-primary link. In some cases, execution of the processor readable code may also determine that a non-primary link is available while operating as a single link device on the primary link and set the DNT bit to a value of 0 based on the availability of the non-primary link. and is configured to transmit the reset DNT bit in other frames only on the primary link, and the other frames have a per-STA profile sub-element, or a reduced neighbor reporting (RNR) element with the reset DNT bit having a value of 0. Includes. In some other implementations, the execution of the processor-readable code may also determine that a non-primary link is available after sending the indication, transmit an availability indication of the non-primary link only on the primary link, and It can be configured to operate as a multi-link device on primary and non-primary links based on the availability of.

In some implementations, execution of the processor readable code further includes: receiving an RTS frame from the STA MLD on a primary link, transmitting a CTS frame to the STA MLD on the primary link and non-primary link based on receiving the RTS frame; It may be configured to receive one or more UL PPDUs from the STA MLD on the primary link and non-basic link. In some other implementations, execution of the processor readable code may also be configured to switch a basic link from a first channel to a second channel simultaneously with switching a non-primary link from a second channel to a first channel. . In some cases, the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.

The details of one or more implementations of the subject matter described in this disclosure are set forth in the detailed description below and the accompanying drawings. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative dimensions of the following drawings may not be drawn to scale.
1 shows a pictorial diagram of an example wireless communications network.
FIG. 2A illustrates an example protocol data unit (PDU) usable in communication between an access point (AP) and one or more wireless stations (STAs).
FIG. 2B shows example fields within the PDU of FIG. 2A.
3A shows another example PDU that can be used for communication between an AP and one or more STAs.
3B shows another example PDU that can be used for communication between an AP and one or more STAs.
FIG. 4 illustrates an example physical layer convergence protocol (PLCP) protocol data unit (PPDU) usable for communication between an AP and multiple STAs.
Figure 5 shows a block diagram of an example wireless communication device.
Figure 6A shows a block diagram of an access point (AP).
Figure 6B shows a block diagram of an example station (STA).
FIG. 7A shows a sequence diagram depicting an example wireless communication supporting a non-simultaneous transmit-receive (NSTR) soft access point (AP) multiple link device (MLD), according to some implementations.
FIG. 7B shows a sequence diagram depicting another example wireless communication supporting NSTR softAP MLD, according to some implementations.
Figure 8A shows a sequence diagram depicting an example wireless communication supporting NSTR softAP MLD, according to some other implementations.
FIG. 8B shows a sequence diagram depicting another example wireless communication supporting NSTR softAP MLD, according to some other implementations.
FIG. 9A shows a timing diagram depicting example wireless communication supporting NSTR softAP MLD, according to some implementations.
FIG. 9B shows a timing diagram depicting another example wireless communication supporting NSTR softAP MLD, according to some implementations.
10A shows an example management frame usable for multi-link communication, according to some implementations.
10B illustrates another example management frame that can be used for multi-link communications, according to some implementations.
FIG. 11A illustrates an example reduced neighbor reporting (RNR) that can be used for multi-link communications, according to some implementations.
FIG. 11B shows an example TBTT information header of the RNR element of FIG. 11A, according to some implementations.
FIG. 11C shows an example TBTT information field of the RNR element of FIG. 11A, according to some implementations.
12A illustrates an example multi-link (ML) element that can be used for multi-link communication, according to some implementations.
FIG. 12B illustrates an example multi-link control field of the ML element of FIG. 12A, according to some implementations.
FIG. 12C shows an example common information field of the ML element of FIG. 12A, according to some implementations.
FIG. 12D illustrates an example per-STA profile sub-element of the ML element of FIG. 12A, according to some implementations.
FIG. 12E illustrates an example STA control field of the per-STA profile sub-element of FIG. 12D, according to some implementations.
FIG. 12F illustrates an example STA information field of the per-STA profile sub-element of FIG. 12D, according to some implementations.
13-36 show flow diagrams illustrating an example wireless communication process supporting NSTR softAP MLD, according to some implementations.
Figure 37 shows a block diagram of an example wireless communication device in accordance with some implementations.
Figure 38 shows a block diagram of another example wireless communication device in accordance with some implementations.
Like reference numerals and designations in the various drawings indicate like elements.

The following description is directed to specific implementations to illustrate innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a number of different ways. The described implementations include, among other things, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, the Bluetooth® standard as defined by the Bluetooth Special Interest Group (SIG), or the Third Generation Partnership Project (3GPP). Any device, system, or device capable of transmitting and receiving radio frequency (RF) signals in accordance with one or more of the Long Term Evolution (LTE), 3G, 4G, or New Radio (NR) (5G) standards promulgated by It can be implemented in a network. The described implementations include the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC- to be implemented in any device, system or network that may transmit and receive RF signals according to one or more of FDMA), single-user (SU) multiple-input multiple-output (MIMO), and multi-user (MU) MIMO. You can. The described implementations may also include other wireless communication protocols suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an Internet of Things (IOT) network. Alternatively, it can be implemented using RF signals.

Various implementations generally relate to communication between multiple link devices (MLDs), such as AP MLD and STA MLD. Some implementations more specifically relate to a wireless station (STA) operating as a mobile hotspot over multiple communications links. An AP MLD includes a plurality of APs configured to communicate on a plurality of different communication links. The STA MLD may communicate with the AP MLD using one or more of different communication links simultaneously. The AP MLD may provide a multi-link context that contains or represents the entire profiles of the various communication links associated with the AP MLD. The full profile of each link may include each link's capabilities, operating parameters, and discovery information. An AP MLD can advertise a multi-link context on one of its communication links, such that a nearby wireless communication device (e.g., a STA MLD) operating on that communication link receives the multi-link context and You can obtain full profiles for them. In this way, a wireless communication device operating on one communication link can discover and associate the AP MLD with the AP MLD on one or more other communication links without scanning or probing the other communication links. The communication link where the AP MLD advertises a multi-link context may be referred to as the primary link, and other communication links may be referred to as non-primary links.

The multi-link context also allows the AP MLD and one or more associated devices to establish a common block acknowledgment (BA) policy or session for multiple communication links in the AP MLD. Enables the use of a single authentication mechanism. Associated devices can dynamically switch communications between the various communication links of the AP MLD using the multi-link context without having to disassociate or re-associate with the AP MLD. AP MLD can use multiple link contexts to dynamically change or remap the traffic identifier (TID) values and relationships between each of the various communication links.

Wireless STAs have limited filtering capabilities compared to APs, which may cause transmission to an STA on one link to interfere with data transmission from the STA on another link. For example, if a STA transmits downlink (DL) communications on one link and simultaneously receives uplink (UL) communications on another link, the relatively small spacing between the STA's antenna resources along with the STA's limited filtering capabilities causes DL data transmission on one link to interfere with or prevent simultaneous reception of UL data on another link. This cross-link interference can prevent or prevent STAs operating as mobile hotspots on multiple communication links from simultaneously transmitting and receiving data on different communication links. Because of this, these STAs may be referred to as non-simultaneous transmit-receive (NSTR) softAP MLD.

Aspects of the present disclosure recognize the importance of reducing or eliminating cross-link interference associated with NSTR softAP MLD. In some implementations, the NSTR softAP MLD associated with the default link and the non-default link may advertise the entire profile of the default link and the non-default link only on the default link. Additionally, the NSTR softAP MLD can advertise updates to one or more BSS parameters of primary and non-default links only on primary links. Advertising the full profile of both links in the NSTR softAP MLD on the primary link allows some wireless communication devices operating on the primary link to use NSTR on either or both the primary and non-primary links without having to scan or probe the non-primary link. Allows softAP MLDs to be retrieved and associated with them. In some implementations, a non-legacy device operating on a basic link may decode or parse the full profile of both the basic link and the non-default link, while a legacy device operating on a basic link may only decode the full profile of the basic link. Or you can parse it. As a result, legacy devices operating on the primary link may not be able to discover or associate with the NSTR softAP MLD on the non-primary link. Additionally, by not advertising the full profile of both links on the non-primary link, legacy devices operating on the non-primary link may not be able to discover or associate the NSTR softAP MLD on the non-primary link. In this manner, various aspects of the subject matter disclosed herein may limit communication between the NSTR softAP MLD and the legacy device to the primary link. As used herein, the term “legacy device” may refer to a wireless communications device configured to operate in accordance with a previous revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and the term “non-legacy device” may refer to may refer to a wireless communications device configured to operate in accordance with IEEE 802.11be or a later revision to the 802.11 family of wireless communications standards.

Various aspects of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. By limiting communication between NSTR softAP MLDs and legacy devices to the primary link (and thus preventing legacy devices from communicating with NSTR softAP MLDs on non-primary links), NSTR softAP MLDs can connect to one or more associated devices on primary links. It is possible to prevent legacy devices from transmitting UL data on non-default links while transmitting DL data. In this manner, implementations of the subject matter disclosed herein can reduce the likelihood that cross-link interference resulting from UL transmissions on non-primary links will degrade or otherwise disrupt DL transmissions from the NSTR softAP MLD on the primary link. there is.

1 shows a block diagram of an example wireless communications network 100. According to some aspects, wireless communications network 100 may be an example of a wireless local area network (WLAN), such as a Wi-Fi network (and will hereinafter be referred to as WLAN 100). For example, WLAN 100 may support the IEEE 802.11 family of standards (e.g., 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be), including but not limited to the IEEE 802.11-2016 standard or amendments thereto. It may be a network that implements at least one of the defined: WLAN 100 may include many wireless communication devices, such as an access point (AP) 102 and multiple stations (STAs) 104. Although only one AP 102 is shown, WLAN network 100 may also include multiple APs 102.

Each of the STAs 104 may also be a mobile station (MS), mobile device, mobile handset, wireless handset, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber, among other possibilities. It may be referred to as a unit. STAs 104 may be used in mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, laptop computers, tablet computers, laptops, display devices (e.g., TVs, among other possibilities), among other possibilities. computer monitors, navigation systems, etc.), music or other audio or stereo devices, remote control devices (“remote devices”), printers, kitchen or other appliances (e.g., manual keyless entry and start (PKES) systems). (for) may represent various devices such as a key fob.

A single AP 102 and an associated set of STAs 104 may be referred to as a basic service set (BSS) managed by an individual AP 102. 1 illustrates an example coverage area 106 of AP 102, which may additionally represent the basic service area (BSA) of WLAN 100. A BSS may be identified to users by a service set identifier (SSID), as well as to other users by a basic service set identifier (BSSID), which may be the medium access control (MAC) address of the AP 102. Devices can also be identified. The AP 102 allows any STAs 104 within wireless range of the AP 102 to “associate” or re-associate with the AP 102 to establish a respective communication link 108 (hereinafter also referred to as a “Wi-Fi link”). periodically broadcasts beacon frames (“beacons”) containing the BSSID to establish a communication link 108 with the AP 102 or maintain a communication link 108 with the AP 102. For example, the beacon may include identification of the primary channel used by each AP 102 as well as a timing synchronization function to establish or maintain timing synchronization with the AP 102. AP 102 may provide access to the external network to various STAs 104 in the WLAN via respective communication links 108.

To establish a communication link 108 with the AP 102, each of the STAs 104 communicates on a frequency channel in one or more frequency bands (e.g., 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). configured to perform passive or active scanning operations (“scanning”). To perform passive scanning, STA 104 uses periodic time, referred to as Target Beacon Transmission Time (TBTT) (measured in units of time (TU), where one TU may be equal to 1024 microseconds (μs)). It listens to beacons transmitted by individual APs 102 at intervals. To perform active scanning, the STA 104 generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs 102. Each STA 104 identifies or selects an AP 102 to associate with based on scanning information obtained through passive or active scanning, and authenticates and associates to establish a communication link 108 with the selected AP 102. May be configured to perform operations. The AP 102 assigns an association identifier (AID) to the STA 104 upon completion of association operations that the AP 102 uses to track the STA 104 .

As a result of the increasing ubiquity of wireless networks, the STA 104 can select one of many BSSs within the STA's range or connect to multiple APs (APs) that together form an extended service set (ESS) that includes multiple connected BSSs. 102) You can have the opportunity to choose between. An extended network station associated with WLAN 100 may be connected to a wired or wireless distribution system that may allow multiple APs 102 to be connected in this ESS. As such, a 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 association with an AP 102, the STA 104 may also be configured to periodically scan its surroundings to find a more suitable AP 102 to associate with. For example, a STA 104 that is moving relative to its associated AP 102 may find another AP 102 with more desirable network characteristics, such as greater received signal strength indicator (RSSI) or reduced traffic load. You can also perform a "roaming" scan to find it.

In some cases, STAs 104 may form networks without APs 102 or other equipment other than the STAs 104 themselves. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some cases, ad hoc networks may be implemented within a larger wireless network, such as WLAN 100. In such implementations, STAs 104 may be capable of communicating with each other via AP 102 using communication links 108 , but STAs 104 may also communicate via direct wireless communication links 110 They can communicate directly with each other. Additionally, two STAs 104 may communicate over a direct communication link 110 regardless of whether both STAs 104 are associated with and served by the same AP 102 . In this ad hoc system, one or more of the STAs 104 may assume the role fulfilled by the AP 102 in the BSS. Such STA 104 may be referred to as a group owner (GO), and may coordinate transmissions within the ad hoc network. Examples of direct wireless links 110 include Wi-Fi Direct connections, connections established using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

APs 102 and STAs 104 support the IEEE 802.11 family of standards (e.g., IEEE 802.11-, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). and capable of functioning and communicating (via individual communication links 108) in accordance with the 2016 standard or any amendments thereto. These standards define WLAN radio and baseband protocols for PHY and medium access control (MAC) layers. The APs 102 and STAs 104 transmit and receive wireless communication (hereinafter also referred to as Wi-Fi communication) with each other in the form of a Physical Layer Conversion Protocol (PLCP) Protocol Data Unit (PPDU). APs 102 and STAs 104 of WLAN 100 may transmit PPDUs over unlicensed spectrum, which includes the 2.4 GHz band, 5.0 GHz band, 60 GHz band, 3.6 GHz band, and 900 MHz band. It may be part of a spectrum that includes frequency bands commonly used by Wi-Fi technology, such as a band. Some implementations of APs 102 and STAs 104 described herein may also communicate in other frequency bands, such as the 6.0 GHz band, which may support both licensed and unlicensed communications. APs 102 and STAs 104 also communicate over other frequency bands, such as shared licensed frequency bands where multiple operators may have a license to operate in the same or overlapping frequency band or bands. It can be configured to do so.

Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs that comply with the IEEE 802.11n, 802.11ac, and 802.11ax standard revisions may be transmitted over the 2.4 and 5.0 GHz bands, each of which is divided into multiple 20 MHz channels. Thereby, these PPDUs are transmitted over a physical channel with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel combining. For example, PPDUs can be transmitted over physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz or 320 MHz by combining multiple 20 MHz channels together.

Each PPDU is a complex structure that includes a payload in the form of a PSDU (PLCP service data unit) and a PHY preamble. The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In cases where PPDUs are transmitted through a combined channel, preamble fields may be duplicated and transmitted in each of 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 may be used for packet detection, automatic gain control, and channel estimation, among other purposes. A legacy preamble may also be used generally to maintain compatibility with legacy devices. The format, coding and information provided in the non-legacy portion of the preamble are based on the specific IEEE 802.11 protocol that will be used to transmit the payload.

FIG. 2A shows an example protocol data unit (PDU) 200 usable for communication between an AP and multiple STAs. For example, PDU 200 may be configured as a PPDU. As shown, PDU 200 includes PHY preamble 202 and PHY payload 204. For example, the PHY preamble 202 itself includes a legacy short training field (L-STF) 206, a legacy long training field (L-LTF) 208, and a legacy signaling field (L-SIG) 210. It may include legacy parts that do. PHY preamble 202 may also include non-legacy portions (not shown). The L-STF 206 generally allows the receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. L-LTF 208 generally allows a receiving device to perform precise timing and frequency estimation and also estimate the wireless channel. L-SIG 210 generally allows the receiving device to determine the duration of a PDU and prevent transmission of other than the PDU using the determined duration. For example, the L-STF 206, L-LTF 208, and L-SIG 210 may be modulated according to a binary phase shift keying (BPSK) modulation scheme. Payload 204 may 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 generally carry upper layer data in the form of, for example, a medium access control (MAC) protocol data unit (MPDU) or an aggregated MPDU (A-MPDU).

FIG. 2B shows an example L-SIG field 220 of the PDU of FIG. 2A. L-SIG 220 includes a data rate field 222, reservation bits 224, length field 226, parity bit 228, and tail field 220. Data rate field 222 indicates the data rate (note that the data rate indicated in data rate field 222 may not be the actual data rate of the data carried in payload 204). The length field 226 indicates the length of the packet, for example, in bytes. Parity bit 228 is used to detect bit errors. Tail field 220 includes tail bits used by the receiving device to terminate operation of a decoder (e.g., a Viterbi decoder). The receiving device utilizes the data rate and length indicated in the data rate field 222 and length field 226 to determine the duration of the packet, for example in microseconds (μs).

FIG. 3A shows another example PDU 300 usable for wireless communication between an AP and one or more STAs. PDU 300 can be used for SU, OFDMA or MU-MIMO transmissions. PDU 300 may be formatted as a High Efficiency (HE) WLAN PPDU according to the IEEE 802.11ax revision to the IEEE 802.11 wireless communication protocol standard. PPDU 300 includes a PHY preamble that includes a legacy portion 302 and a non-legacy portion 304. The PDU 300 may further include a PHY payload 306 after a preamble, for example, in the form of a PSDU including a data field 324.

The legacy portion of the preamble 302 includes L-STF 308, L-LTF 310, and L-SIG 312. The non-legacy portion 304 includes a repetition of L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, and a HE short training field (HE-STF) 320. , and one or more HE long training fields (or symbols) (HE-LTF) 322. For OFDMA or MU-MIMO communications, the second portion 304 further includes a second HE signal field (HE-SIG-B) 318 encoded separately from HE-SIG-A 316. Like L-STF 308, L-LTF 310, and L-SIG 312, information from RL-SIG 314 and HE-SIG-A 316 involves the use of combined channels. In some cases, the component may be replicated and transmitted on each of the 20 MHz channels. In contrast, the content of HE-SIG-B 318 may be unique to each 20 MHz channel and target specific STAs 104.

RL-SIG 314 may indicate to HE-compatible STAs 104 that PDU 300 is a HE PPDU. The AP 102 uses HE-SIG-A to identify multiple STAs 104 and inform the STAs 104 that the AP has scheduled UL or DL resources for those STAs 104. (316) can be used. For example, HE-SIG-A 316 may include a resource allocation subfield indicating resource allocation for the identified STAs 104. HE-SIG-A 316 may be decoded by each HE-compatible STA 104 served by AP 102. For MU transmissions, HE-SIG-A 316 further contains information that can be used by each identified STA 104 to decode the associated HE-SIG-B 318. For example, HE-SIG-A 316 includes the positions and lengths of HE-SIG-Bs 318, available channel bandwidths, and modulation and coding schemes (MCS), among other examples. Frame format can be displayed. HE-SIG-A 316 may also include HE WLAN signaling information usable by STAs 104 other than the identified STAs 104.

HE-SIG-B 318 may carry STA-specific scheduling information, such as, for example, STA-specific (or “user-specific”) MCS values and STA-specific RU assignment information. In the context of DL MU-OFDMA, this information allows individual STAs 104 to identify and decode corresponding resource units (RUs) in the associated data field 324. Each HE-SIG-B 318 includes common fields and at least one STA-specific field. The common field indicates, among other examples, RU assignments for multiple STAs 104 including RU assignments in the frequency domain, which RUs are assigned for MU-MIMO transmissions and which RUs are MU -Indicates whether it corresponds to OFDMA transmissions, and may indicate the number of users in the assignments. The common field may be encoded with common bits, CRC bits, and tail bits. User-specific fields are assigned to specific STAs 104 and may be used to schedule specific RUs and indicate scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields containing information about the two individual STAs in order to decode their respective RU payloads in the data field 324.

FIG. 3B shows another example PPDU 350 usable for wireless communication between an AP and one or more STAs. PDU 350 may be used for SU, OFDMA, or MU-MIMO transmission. PDU 350 may be formatted as an Extreme High Throughput (EHT) WLAN PPDU in accordance with the IEEE 802.11be amendment to the IEEE 802.11 wireless communications protocol standard, or as a WLAN PPDU compliant with a future IEEE 802.11 wireless communications protocol standard or other wireless communications standard. It may be formatted as a PPDU conforming to any later (post-EHT) version of the new wireless communication protocol. PPDU 350 includes a PHY preamble that includes a legacy portion 352 and a non-legacy portion 354. The PDU 350 may further include a PHY payload 356 after the preamble, for example in the form of a PSDU including a data field 376.

The legacy portion 352 of the preamble includes L-STF 358, L-LTF 360, and L-SIG 362. The non-legacy portion of the preamble 354 includes RL-SIG 364 and a number of wireless communication protocol version-dependent signal fields following RL-SIG 364. For example, non-legacy portion 354 may include universal signal field 366 (herein referred to as “U-SIG 366”) and EHT signal field 368 (herein referred to as “EHT-SIG 368”). (referred to as "). One or both of U-SIG 366 and EHT-SIG 368 may be configured for, and carry version-dependent information about, other wireless communication protocol versions beyond EHT. The non-legacy portion 354 includes an additional short training field 372 (referred to herein as “EHT-STF 372”), which is structured as and carries version-dependent information about other wireless communication protocol versions beyond EHT. and one or more additional long training fields 374 (referred to herein as “EHT-LTFs 374”), which are structured as and carry version-dependent information about other wireless communication protocol versions beyond EHT. may be included). Like L-STF 358, L-LTF 360, and L-SIG 362, information from U-SIG 366 and HE-SIG 368 is useful in cases involving the use of combined channels. It can be replicated and transmitted on each of the component 20 MHz channels. In some implementations, EHT-SIG 368 may additionally or alternatively carry information on one or more non-primary 20 MHz channels that are different from the information carried on the primary 20 MHz channel.

EHT-SIG 368 may include one or more co-encoded symbols, and may be encoded in a different block than the block in which U-SIG 366 is encoded. The EHT-SIG 368 is used by the AP to identify multiple STAs 104 and inform the STAs 104 that the AP has scheduled UL or DL resources for those STAs 104. can be used EHT-SIG 368 may be decoded by each compatible STA 104 served by AP 102. EHT-SIG 368 may be used by a receiving device to generally interpret the bits of data field 376. For example, EHT-SIG 368 may include user-specific signaling information such as RU assignment information, spatial stream configuration information, and MCSs, among other examples. The EHT-SIG 368 may further include a cyclic redundancy check (CRC) (e.g., 4 bits) and a tail (e.g., 6 bits) that may be used for a binary convolutional code (BCC). In some implementations, EHT-SIG 368 may include one or more code blocks, each including a CRC and a tail. In some aspects, each of the code blocks may be encoded individually.

HE-SIG 368 may carry STA-specific scheduling information, such as user-specific MCS values and user-specific RU assignment information. EHT-SIG 368 may be used by a receiving device to generally interpret the bits of data field 376. In the context of DL MU-OFDMA, this information allows individual STAs 104 to identify and decode corresponding RUs in the associated data field 376. Each EHT-SIG 368 may include common fields and at least one user-specific field. The common field indicates, among other examples, RU distributions for multiple STAs 104, indicates RU allocations in the frequency domain, which RUs are assigned for MU-MIMO transmissions, and which RUs are assigned to MU-MIMO transmissions. It may indicate whether it corresponds to OFDMA transmissions, and may indicate the number of users in the assignments. The common field may be encoded with common bits, CRC bits, and tail bits. User-specific fields are assigned to specific STAs 104 and may be used to schedule specific RUs and indicate scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields containing information about two individual STAs, e.g., to decode their respective RU payloads.

The presence of RL-SIG 364 and U-SIG 366 ensures that the PPDU 350 complies with any later (post-EHT) version of the new wireless communication protocol that complies with the future IEEE 802.11 wireless communication protocol standard. EHT PPDU or PPDU may be indicated to EHT- or later-compliant STAs 104. For example, U-SIG 366 may be used by a receiving device to interpret one or more bits of EHT-SIG 368 or data field 376.

FIG. 4 shows an example PPDU 400 usable for communications between an AP 102 and multiple STAs 104 . As described above, each PPDU 400 includes a PHY preamble 402 and a PSDU 404. Each PSDU 404 may carry one or more MAC protocol data units (MPDUs), for example, an aggregated MPDU (A-MPDU) 406 containing multiple MPDU subframes 408. It may be possible. Each MPDU subframe 408 may include a MAC delimiter 412 and a MAC header 414 preceding the accompanying frame body 416, which contains the data portion or “payload” of the MPDU subframe 408. You can. Frame body 416 may carry one or more MAC service data units (MSDUs), for example, an aggregated MSDU (A-MSDU) 422 comprising multiple MSDU subframes 424. It may be possible. Each MSDU subframe 424 includes a subframe header 428, a frame body 430, and a corresponding MSDU 426 that includes one or more padding bits 432.

Referring back to the A-MPDU subframe 406, the MAC header 414 may include a number of fields containing information defining or indicating characteristics or attributes of the data encapsulated within the frame body 416. . MAC header 414 also includes a number of fields indicating addresses for data encapsulated within frame body 416. For example, MAC header 412 may include a combination of source address, transmitter address, receiver address, or destination address. MAC header 414 may include a frame control field containing control information. The frame control field specifies the frame type, such as a data frame, control frame, or management frame. MAC header 414 indicates a duration extending from the end of a PPDU to the end of the acknowledgment (ACK) of the last PPDU to be transmitted by the wireless communication device (e.g., a block ACK (BA) in the case of an A-MPDU). Additional duration fields may be included. Use of the duration field serves to reserve the wireless medium for the indicated duration, thereby setting the NAV. Each A-MPDU subframe 408 may also include a frame check sequence (FCS) field 418 for error detection. For example, the FCS field 418 may include a cyclic redundancy check (CRC), followed by one or more padding bits 420.

As described above, APs 102 and STAs 104 may support multi-user (MU) communications. That is, simultaneous transmissions from one device to each of multiple devices (e.g., multiple simultaneous downlink (DL) communications from AP 102 to corresponding STAs 104), or multiple devices Simultaneous transmissions are made from multiple devices to a single device (e.g., multiple simultaneous uplink (UL) transmissions from corresponding STAs 104 to AP 102). To support MU transmissions, APs 102 and STAs 104 use multi-user multiple-input, multiple-output (MU-MIMO) and multi-user orthogonal frequency division multiple access (MU-OFDMA) technologies. You can utilize it.

In MU-OFDMA schemes, the available frequency spectrum of a wireless channel may be divided into a number of resource units (RUs), each containing a number of different frequency subcarriers (“tones”). Different RUs may be assigned or allocated by the AP 102 to different STAs 104 at specific times. The sizes and distributions of RUs may be referred to as RU allocation. In some implementations, RUs may be spaced 2 MHz apart, such that the smallest RU may contain 26 tones consisting of 24 data tones and 2 pilot tones. As a result, in a 20 MHz channel, a maximum of 9 RUs (eg, 2 MHz, 26 RUs) can be assigned (since some tones are reserved for other purposes). Similarly, in a 160 MHz channel, a maximum of 74 RUs can be assigned. Larger 52 tonne, 106 tonne, 242 tonne, 484 tonne and 996 tonne RUs can also be assigned. Adjacent RUs may be separated by a null subcarrier (e.g., a DC subcarrier), e.g., to reduce interference between adjacent RUs, reduce receiver DC offset, and avoid transmission center frequency leakage.

For UL MU transmissions, AP 102 may send a trigger frame to initiate and synchronize UL MU-OFDMA or UL MU-MIMO transmission from multiple STAs 104 to AP 102. Accordingly, these trigger frames can enable multiple STAs 104 to transmit UL traffic to the AP 102 at the same time in time. A trigger frame may address one or more STAs 104 via individual association identifiers (AIDs), and may identify one or more RUs that may be used to transmit UL traffic to the AP 102 for each AID (and thus Accordingly, it can be allocated to each STA (104). The AP may also designate one or more random access (RA) RUs with which unscheduled STAs 104 may compete.

FIG. 5 shows a block diagram of an example wireless communication device 500. In some implementations, wireless communication device 500 may be an example of a device for use in an STA, such as one of the STAs 104 described above with reference to FIG. 1 . In some implementations, wireless communication device 500 may be an example of a device for use in an AP, such as AP 102 described above with reference to FIG. 1 . Wireless communication device 500 may transmit (or output for transmission) and receive wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device 500 may be configured according to the IEEE 802.11-2016 standard or amendments thereto, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. It may be configured to transmit and receive packets in the form of a Physical Layer Conversion Protocol (PLCP) Protocol Data Unit (PPDU) and a Medium Access Control (MAC) Protocol Data Unit (MPDU) conforming to the IEEE 802.11 standard as defined.

Wireless communication device 500 may be or may include a chip, system on chip (SoC), chipset, package, or device that includes one or more modems 502, such as a Wi-Fi (IEEE 802.11 compliant) modem. You can. In some implementations, one or more modems 502 (collectively, “modem 502”) additionally includes a WWAN modem (e.g., a 3GPP 4G LTE or 5G compliant modem). In some implementations, wireless communication device 500 also includes one or more radios 504 (collectively, “radios 504”). In some implementations, wireless communication device 500 includes one or more processors, processing blocks or processing elements 506 (collectively, “processor 506”) and one or more memory blocks or elements 508. ) (collectively, “memory 508”).

Modem 502 may include an intelligent hardware block or device, such as, for example, an application specific integrated circuit (ASIC), among other possibilities. Modem 502 is generally configured to implement a PHY layer. For example, modem 502 is configured to modulate packets and output the modulated packets to radio 504 for transmission over a wireless medium. Modem 502 is similarly configured to obtain modulated packets received by radio 504 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, modem 502 may further include digital signal processing (DSP) circuitry, automatic gain control (AGC), coder, decoder, multiplexer, and demultiplexer. For example, while in transfer mode, data obtained from processor 506 is provided to a coder, and the coder encodes the data and provides encoded bits. The encoded bits are then mapped to points in the modulation constellation (using the selected MCS) to provide the modulated symbols. The modulated symbols may then be mapped to a number of spatial streams N _SS or a number of space-time streams N _STS . The modulated symbols of the individual spatial or spatiotemporal streams can then be multiplexed, transformed through an inverse fast Fourier transform (IFFT) block, and subsequently provided to DSP circuitry for Tx windowing and filtering. The digital signals can then be provided to a digital-to-analog converter (DAC). The resulting analog signals can then be provided to a frequency upconverter, and ultimately to radio 504. In implementations involving beamforming, the modulated symbols of the individual spatial streams are pre-coded through a steering matrix before being provided to the IFFT block.

While in the receive mode, digital signals received from radio 504 are provided to DSP circuitry, which is configured to acquire the received signal, such as by detecting the presence of the signal and estimating initial timing and frequency offsets. The DSP circuitry is further adapted to digitally condition digital signals using, for example, channel (narrowband) filtering, analog disturbance conditioning (e.g., I/Q imbalance correction), and application of digital gain to ultimately obtain a narrowband signal. It is composed. The output of the DSP circuit may then be provided to an AGC, configured to determine an appropriate gain using, for example, information extracted from the digital signals of one or more received training fields. The output of the DSP circuit also includes a demodulator configured to extract modulated symbols from the signal and calculate, for example, a log likelihood ratio (LLR) for each bit position of each subcarrier in each spatial stream. are coupled. A demodulator may be coupled to a decoder, and the decoder may be configured to process the LLRs and provide decoded bits. The decoded bits from all spatial streams are then provided to the demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 506) for processing, evaluation, or interpretation.

Radio 504 generally includes at least one radio frequency (RF) transmitter (or “transmitter chain”) and at least one RF receiver (or “receiver chain”), which may be coupled to one or more transceivers. For example, RF transmitters and receivers may each include various DSP circuits including at least one power amplifier (PA) and at least one low-noise amplifier (LNA). RF transmitters and receivers may in turn be coupled to one or more antennas. For example, in some implementations, wireless communication device 500 includes or includes multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). It can be coupled with . Symbols output from modem 502 are provided to radio 504, which then transmits the symbols via coupled antennas. Similarly, symbols received via antennas are acquired by radio 504, which then provides the symbols to modem 502.

Processor 506 may include, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc. It may include an intelligent hardware block or device such as a programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processor 506 processes information received via radio 504 and modem 502 and processes information to be output via modem 502 and radio 504 for transmission over wireless media. For example, processor 506 may implement a control plane and MAC layer configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform or facilitate coding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, among other operations or techniques. In some implementations, processor 506 may control modem 502 generally to cause modem 502 to perform various operations described above.

Memory 508 may include a type of storage medium, such as random access memory (RAM) or read only memory (ROM), or a combination thereof. Memory 508 also, when executed by processor 506, allows the processor to perform various functions described herein for wireless communications, including generating, transmitting, receiving, and interpreting MPDUs, frames, or packets. Non-transitory processor or computer-executable software (SW) code containing instructions to perform operations may be stored. For example, various functions of the components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein, may be implemented as one or more modules of one or more computer programs.

Figure 6A shows a block diagram of an example AP 602. For example, AP 602 may be an example implementation of AP 102 described with reference to FIG. 1 . The AP 602 includes a wireless communication device (WCD) 610. For example, wireless communication device 610 may be an example implementation of wireless communication device 500 described with reference to FIG. 5 . AP 602 also includes multiple antennas 620 coupled with a wireless communication device 610 to transmit and receive wireless communications. In some implementations, AP 602 additionally includes an applications processor 630 coupled with a wireless communication device 610 and a memory 640 coupled with the applications processor 630. AP 602 further includes at least one external network interface 650 that allows AP 602 to communicate with a core network or backhaul network to gain access to external networks, including the Internet. For example, external network interface 650 may include one or both a wired (eg, Ethernet) network interface and a wireless network interface (eg, WWAN interface). Components of the aforementioned components may communicate with other components of the components directly or indirectly over at least one bus. AP 602 further includes a wireless communication device 610, an applications processor 630, memory 640, and a housing including at least some of antennas 620 and an external network interface 650.

Figure 6B shows a block diagram of an example STA 604. For example, AP 604 may be an example implementation of AP 104 described with reference to FIG. 1 . STA 604 includes a wireless communication device 615. For example, wireless communication device 615 may be an example implementation of wireless communication device 500 described with reference to FIG. 5 . STA 604 also includes one or more antennas 625 coupled with a wireless communication device 615 to transmit and receive wireless communications. STA 604 additionally includes an applications processor 635 coupled with a wireless communication device 615 and a memory 645 coupled with the applications processor 635 . In some implementations, the STA 604 further includes a display 665 and a user interface (UI) 655 (e.g., a touchscreen or keypad) that can be integrated with the UI 655 to form a touchscreen display. Includes. In some implementations, STA 604 may further include one or more sensors 675, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Components of the aforementioned components may communicate with other components of the components directly or indirectly over at least one bus. STA 604 further includes a housing including a wireless communication device 615, an application processor 635, memory 645, and at least some of antennas 625, UI 655, and display 665. do.

As discussed, a wireless STA may have limited filtering capabilities compared to an AP, which may cause reception of UL data on one communication link to interfere with transmission of DL data on another communication link. As a result, an STA operating as an NSTR softAP MLD associated with the primary link and the non-primary link may not be able to simultaneously receive UL data on the non-primary link and transmit DL data on the primary link. Likewise, an STA operating as an NSTR softAP MLD may not be able to transmit DL data on a non-primary link while receiving UL data on the primary link.

Aspects of the present disclosure recognize the importance of reducing or eliminating cross-link interference associated with NSTR softAP MLD. In some implementations, the NSTR softAP MLD associated with the default link and the non-default link may advertise the entire profile of the default link and the non-default link only on the default link. Additionally, the NSTR softAP MLD can advertise updates to one or more BSS parameters of primary and non-default links only on primary links. Advertising the full profile of both links in the NSTR softAP MLD on the primary link allows some wireless communication devices operating on the primary link to use NSTR on either or both the primary and non-primary links without having to scan or probe the non-primary link. Allows softAP MLDs to be retrieved and associated with them. In some implementations, a non-legacy device operating on a basic link may decode or parse the full profile of both the basic link and the non-default link, while a legacy device operating on a basic link may only decode the full profile of the basic link. Or you can parse it. As a result, legacy devices operating on the primary link may not be able to discover or associate with the NSTR softAP MLD on the non-primary link. Additionally, by not advertising the full profile of both links on the non-primary link, legacy devices operating on the non-primary link may not be able to discover or associate the NSTR softAP MLD on the non-primary link. In this manner, various aspects of the subject matter disclosed herein may limit communication between the NSTR softAP MLD and the legacy device to the primary link.

Various aspects of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. By limiting communication between NSTR softAP MLDs and legacy devices to the primary link (and thus preventing legacy devices from communicating with NSTR softAP MLDs on non-primary links), NSTR softAP MLDs can connect to one or more associated devices on primary links. It is possible to prevent legacy devices from transmitting UL data on non-default links while transmitting DL data. In this manner, implementations of the subject matter disclosed herein can reduce the likelihood that cross-link interference resulting from UL transmissions on non-primary links will degrade or otherwise disrupt DL transmissions from the NSTR softAP MLD on the primary link. there is.

FIG. 7A shows a sequence diagram depicting an example multi-link (ML) communication 700 in accordance with some implementations. In the example of Figure 7A, multi-link communication 700 may be performed between an STA operating as an NSTR softAP MLD and one or more associated STAs (only one associated STA is shown for simplicity). The STA may be any suitable wireless communication device, including, for example, STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. In some implementations, the NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD.

NSTR softAP MLD can be configured to broadcast the entire profile of both primary and non-primary links in one or more frames transmitted only on the primary link. Accordingly, some wireless communication devices within NSTR softAP MLD range can obtain full profiles of both primary and non-primary links while operating on the primary link. Specifically, in some cases, a non-legacy device that obtains a full profile of the primary and non-primary links may be associated with an NSTR softAP MLD on either or both the primary and non-primary links, while the primary link Legacy devices that receive the full profile broadcast from can only associate with the NSTR softAP MLD on the primary link. In this way, communication between a legacy device and NSTR softAP MLD can be restricted to the primary link, which ultimately reduces cross-link interference on the primary link caused by transmissions from the legacy device on non-primary links. You can.

In the example of Figure 7A, the NSTR softAP MLD transmits the first frame only on the primary link, which includes the entire profile of the primary link and represents the entire profile of the non-primary link. In some implementations, the overall profile of each link includes at least beacon interval, capability information, service set identifier (SSID), supported speed, timing synchronization function (TSF) value, and one or more additional fields associated with the discovery of each link. Or it may contain elements. In some other implementations, the overall profile of each link is defined to include all of the capabilities, operating parameters, and discovery information that may be included in a beacon frame or probe response broadcast by the AP operating the BSS on each link. It can be.

In some implementations, the primary link may be configured as a full BSS, and the non-primary link may be configured as a pseudo-BSS that shares one or more capabilities and operating parameters with the primary link. For example, in some aspects, a non-default link may have the same SSID, TSF value, and beacon interval as the default link, and thus inherit these values from the default link. Because of this, the SSID, TSF value, and beacon interval of the non-primary link may not be included in the first frame. In this way, the size of the first frame can be reduced or minimized. Other capabilities and operational parameters of a non-default link may be different from those of the default link and therefore may not be inherited from the default link. Examples of such capabilities and operational parameters include (but are not limited to) EDCA parameters, bandwidth, number of spatial streams (NSS), puncturing pattern, BSSID, and MLD capabilities.

The first frame may be any suitable frame capable of carrying or displaying a full profile of both basic and non-basic links. In some implementations, the first frame may be a beacon frame, probe response frame, association response frame, or reassociation response frame. In some cases, the NSTR softAP MLD may also transmit action frames, such as fast initial link setup (FILS) discovery frames, traffic indication map (TIM) frames, and notification frames, only on the primary link. NSTR softAP MLD can also transmit group addressing frames (e.g. multicast frames) only on the primary link. In this way, NSTR softAP MLD can limit communication with legacy devices to the primary link.

In some implementations, the first frame includes a frame body that includes a plurality of fields and elements followed by a multiple link (ML) element. Multiple fields and elements may convey the entire profile of the underlying link. The ML element may include STA-specific profile sub-elements representing the overall profile of the non-default link. The ML element may also include a common information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) field that indicates updates to one or more BSS parameters associated with the underlying link. In some cases, one or more bits of the multi-link control field or common information field carried in the ML element may indicate whether the first frame is transmitted from the first AP in the NSTR softAP MLD. For example, one or more bits of the multi-link control field or the common information field may be set to a first value indicating that the first frame is transmitted from the first AP in the NSTR softAP MLD, or the AP MLD (or other simultaneous transmission - It may be set to a second value indicating that the first frame is transmitted from the AP associated with the receiving (STR) device).

The body of the first frame may also include a reduced neighbor reporting (RNR) element carrying a neighbor AP information field associated with the non-primary link. The Neighbor AP Information field may carry a Target Beacon Transmission Time (TBTT) information field consisting of a Basic Service Set Identification (BSSID) and one or more MLD parameters of the non-primary link. As discussed, a non-primary link can be configured as a pseudo-BSS that inherits some capabilities and operating parameters from the primary link, and thus the TBTT information fields associated with the non-primary link include the TBTT Offset subfield, short-SSID subfield, and It may not contain one or more subfields, such as (but not limited to) field, BSS parameters subfield, and PSD subfield. If these subfields are omitted, the size or length of the TBTT information field in the adjacent AP information field associated with the non-primary link may be reduced compared to the TBTT information field in the adjacent AP information field associated with other communication links. Because of this, the size or length of the TBTT information field in the neighbor AP information field associated with the non-default link can be used by the receiving STA to determine whether the first frame is transmitted from the first AP in the NSTR softAP MLD. In some aspects, the TBTT information field associated with a non-basic link consists of a 6 octet BSSID field and a 3 octet MLD parameter field and has a length of 9 octets.

In some implementations, the Neighbor AP Information field may include a TBTT Information field type set to a value indicating that the Neighbor AP Information field carries only information associated with a non-primary link. In some cases, the neighbor AP information field may be of a new or undefined type, and the TBTT information field type may be set to 1 or a reserved value indicating the new or undefined type of the TBTT information field. In this way, the receiving STA can determine that the first frame was transmitted from the first AP in the NSTR softAP MLD by parsing the TBTT information field type in the neighboring AP information field associated with the non-primary link. In some examples, non-legacy devices can recognize the new type of TBTT information field disclosed herein and thus obtain full profiles of both primary and non-basic links from the first frame. Conversely, legacy devices may not understand the new type of TBTT information field disclosed herein and may therefore ignore the TBTT information field in the adjacent AP information field associated with a non-primary link. In this manner, aspects of the subject matter disclosed herein may preclude at least some legacy devices from discovering non-primary links based on information received on the primary link.

In some cases, the MLD parameter field of the TBTT information field may include a Basic Service Set (BSS) Parameter Change Count (BPCC) field that carries a value indicating an update to one or more BSS parameters associated with the non-default link. . In some other cases, a value indicating an update to one or more BSS parameters associated with the non-basic link may be carried in another suitable field, element, or header of the first frame.

The STA may receive the first frame transmitted by the NSTR softAP MLD on the primary link and parse the first frame to obtain the full profile of the primary and non-basic links. The STA may use the entire profile of the primary link to discover or associate with the NSTR softAP MLD on the primary link, and may use the entire profile of the non-primary link to discover or associate with the NSTR softAP MLD on the non-primary link. there is. In some cases, the STA may transmit a response frame on the primary link containing capability information, operating parameters, and other information that can be used in the association and authentication process with the NSTR softAP MLD. After the STA associates with the NSTR softAP MLD on the basic link, the STA and NSTR softAP MLD can exchange data, control signals, and other information with each other on the basic link. For implementations where the STA is a multiple wireless device with STR capability, the STA may associate with an NSTR softAP MLD on a non-primary link and exchange data, control signals, and other information with the NSTR softAP MLD on the non-primary link. .

In some cases, one or more of the BSS parameters associated with the underlying link may be changed or updated. Likewise, one or more of the BSS parameters associated with a non-primary link may be changed or updated. In some implementations, the BSS parameters of each communication link include a Channel Switch Announcement (CSA) element, an Extended Channel Switch Announcement (eCSA) element, an Enhanced Distributed Channel Access (EDCA) parameter, and a Quiet Period. ) element, Direct Sequence Spread Spectrum (DSSS) parameter set, high-throughput (HT) operating element, very high-throughput (VHT) operating element, high-efficiency (HE) operating element, extremely high-throughput (EHT) operating element. , a wideband channel switching element, an operating mode notification element, a broadcast Target Wait Time (TWT) element, a BSS color change notification element, a multi-user (MU) EDCA parameter set, a spatial reuse parameter set, or an uplink (UL) orthogonal frequency. It may include one or more of the Division Multiple Access (OFDMA) Random Access (UORA) parameter sets.

In some implementations, the NSTR softAP MLD may generate and transmit a second frame only on the primary link, indicating an update to one or more BSS parameters of the primary link and an update to one or more BSS parameters of the non-primary link. Specifically, when the NSTR softAP MLD receives or determines an update to one or more BSS parameters of the underlying link, the NSTR softAP MLD increments the BPCC value associated with the underlying link and replaces the incremented BPCC value with the It can be inserted into the BPCC subfield within the common information field of the ML element. When the NSTR softAP MLD receives or determines an update to one or more BSS parameters of a non-primary link, the NSTR softAP MLD increments the BPCC value associated with the non-primary link and carries the incremented BPCC value in a second frame. It can be inserted into the BPCC subfield of the MLD parameter field in the adjacent AP information field of the RNR element. In some cases, the NSTR softAP MLD may also set a critical update flag (CUF) carried in the capability information field of the second frame based on the BPCC value associated with the non-primary link being incremented.

The STA may receive the second frame and parse the second frame to obtain BSS parameter updates for the primary link and non-primary link. In some implementations, the second frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some cases, the second frame may include updated BSS parameters of one or both the primary link and the non-primary link. In other implementations, the second frame may be an action frame, such as a notification frame. In some aspects, one or more updated BSS parameters of each communication link may be part of a partial profile of each communication link. For example, in some aspects, the NSTR softAP MLD may transmit a spontaneous broadcast probe response frame on the primary link carrying a partial profile of each communication link with one or more updated BSS parameters. Thereafter, the STA may transmit UL data to the NSTR softAP MLD at least on the primary link, and the NSTR softAP MLD may transmit DL data to the STA at least on the primary link.

FIG. 7B shows a sequence diagram depicting another example multi-link communication 710 according to some implementations. In the example of Figure 7B, multi-link communication 710 may be performed between the NSTR softAP MLD and one or more associated STAs described with reference to Figure 7A (only one associated STA is shown for simplicity). The NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD.

As discussed with reference to Figure 7A, NSTR softAP MLD can broadcast the entire profile of primary and non-primary links only on the primary link. Broadcasting the full profile of both links only on the primary link may cause non-legacy devices to discover and associate NSTR softAP MLDs on either or both the primary and non-primary links, and allow legacy devices to You can discover the NSTR softAP MLD in the link and prevent it from being associated with it.

In some cases, the NSTR softAP MLD may determine that a non-default link is unavailable. For various reasons, non-default links may not be available for multi-link communication between the NSTR softAP MLD and its associated STA. For example, if a non-basic link is used for a cellular link in a long term evolution (LTE) radio access network (RAN) or fifth generation (5G) new radio (NR), the non-basic link may be unavailable. As another example, if the non-primary link is in a power saving mode (including sleep mode or doze mode) to reduce power consumption or extend the battery life of the STA operating as an NSTR softAP MLD, the non-primary link may be utilized It may be impossible. As another example, if the non-primary link is used for peer-to-peer (P2P) or infrastructure-STA communication, the non-primary link may be unavailable.

Aspects of the present disclosure recognize that a primary link may be more suitable for informing STAs associated with an NSTR softAP MLD of the unavailability of a non-primary link. In some implementations, the NSTR softAP MLD may generate a first frame that includes a critical update flag (CUF) set to 1 and a do not transmit (DNT) bit set to 1 based on the unavailability of the non-primary link. . In some cases, the CUF may be carried in the capability information field of the first frame, and the DNT bit may be carried in the STA-specific profile sub-element or RNR element of the first frame.

NSTR softAP MLD can transmit the first frame to the STA (and other related devices operating on the basic link) only on the basic link. In some implementations, the NSTR softAP MLD may operate as a single link device on the primary link based on the non-primary link being unavailable. For example, in some cases, the NSTR softAP MLD allows a softAP (or other transmit chain, receive chain, signaling circuit, etc.) associated with a non-primary link to be placed in sleep, dose, or sleep states while remaining fully operational on the primary link. Or you can leave it in the power off state. In this single link state, NSTR softAP MLD allows the BSS to operate as a single link BSS on the primary link while reducing (or almost eliminating) the power consumption associated with operation on the non-primary link.

The STA may receive the first frame and parse the first frame to obtain an indication that the non-primary link is not available. In some cases, the first frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In other cases, the first frame may be an action frame, such as a notification frame. While the NSTR softAP MLD operates as a single link device on the primary link, the NSTR softAP MLD and its associated STA can exchange frames with each other only on the primary link.

Non-primary links may become available while the NSTR softAP MLD operates as a single link device on the primary link. The NSTR softAP MLD may determine that a non-default link is available and send an indication that the non-default link is available. In some cases, the NSTR softAP MLD may reset the DNT bit associated with the non-primary link and transmit a second frame carrying at least the reset DNT bit only on the primary link. In some implementations, the NSTR softAP MLD can operate as a multi-link device on the primary link and the non-primary link based on determining that the non-primary link is available. For example, NSTR softAP MLD can return a softAP (or other transmit chain, receive chain, signaling circuitry, etc.) associated with a non-primary link to full operation. In this multi-link state, NSTR softAP MLD can operate BSS on both primary and non-primary links.

The STA may receive the second frame and parse the second frame to obtain an indication that the non-default link is available. In some cases, the second frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In other cases, the second frame may be an action frame, such as a notification frame. Thereafter, the NSTR softAP MLD and its associated STA may exchange frames with each other on either or both the primary and non-primary links.

In some implementations, determining the unavailability of a non-primary link may include or be associated with placing the non-primary link in a power saving state (including a sleep state or a doze state), which reduces power consumption and The battery life of NSTR softAP MLD can be extended. In some other implementations, determining the unavailability of a non-primary link may include or be associated with deactivating the non-primary link. In some cases, the NSTR softAP MLD may deactivate a non-primary link by removing the non-primary link from the multiple link context associated with the primary and non-primary links, thereby preventing its associated STA from using the non-primary link. is prevented. When a non-primary link becomes available, the NSTR softAP MLD can return the non-primary link to or add it to the multi-link context, thereby allowing its associated STA to use the non-primary link (in addition to the primary link). becomes available. In some aspects, the NSTR softAP MLD may send a first notification frame on the primary link to indicate that the non-primary link is no longer included in the multi-link context and that the non-primary link has been added to the multi-link context. A second notification frame may be transmitted on the primary link to indicate this. In some other cases, NSTR softAP MLD can deactivate a non-default link by remapping the traffic identifier (TID) of the non-default link from the non-default link to the default link. When a non-default link becomes available, the NSTR softAP MLD can remap the TID from the default link to the non-default link. In some aspects, the NSTR softAP MLD may send a first notification frame on the primary link to indicate that TIDs associated with the non-default link have been remapped to the primary link, and some TIDs associated with the primary link have been remapped to the non-primary link. A second notification frame may be sent on the primary link to indicate that it has been remapped.

FIG. 8A shows a sequence diagram depicting an example multi-link (ML) communication 800 in accordance with some implementations. In the example of Figure 8A, multi-link communication 800 may be performed between the NSTR softAP MLD and one or more associated STAs described with reference to Figures 7A and 7B (only one associated STA is shown for simplicity). . The NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD.

As discussed, NSTR softAP MLD can advertise the full profile of both primary and non-primary links in one or more frames transmitted only on the primary link. Because of this, a non-legacy device may discover a non-default link while operating on a default link, and a legacy device operating on a default link or a non-default link will not discover a non-default link associated with an NSTR softAP MLD. It may not be possible. In this way, communication between the NSTR softAP MLD and the legacy device can be limited to the primary link, which in turn allows the NSTR softAP MLD to transmit UL on the non-primary link while transmitting DL data on the primary link to one or more associated devices. You can reduce the possibility of doing so. This in turn can prevent or reduce cross-link interference to DL transmissions on the primary link caused by simultaneous UL transmissions on the non-primary link.

As discussed, the NSTR softAP MLD can only transmit management frames on primary links that contain the full profile of the primary link and represent the full profile of the non-primary link. The STA may receive the management frame to associate with and authenticate the NSTR softAP MLD on the primary link using the primary link's full profile. In some cases, a STA can associate with and authenticate an NSTR softAP MLD on a non-primary link using the full profile of the non-primary link.

In some implementations, the NSTR softAP MLD may instruct the STA to exchange a ready-to-send (RTS) frame and a clear-to-send (CTS) frame with the NSTR softAP MLD before transmitting UL data to the NSTR softAP MLD. You can. In some cases, the NSTR softAP MLD may transmit a frame on the primary link containing an instruction to perform an RTS/CTS frame exchange before UL data is transmitted to the NSTR softAP MLD. In some other cases, the NSTR softAP MLD may instruct the STA to perform an RTS/CTS frame exchange before transmitting UL data to the NSTR softAP MLD while associated with the NSTR softAP MLD.

STA receives instructions. At a later time, such as when the STA has queued UL data to transmit, the STA may transmit an RTS frame to the NSTR softAP MLD on the primary link. The NSTR softAP MLD receives the RTS frame, determines that a non-primary link is available, and transmits a CTS frame to the STA on both the primary and non-primary links. The STA receives CTS frames on both the primary and non-primary links and determines that the non-primary link is available based on receiving CTS frames on both the primary and non-primary links. The STA transmits one or more UL PPDUs to the NSTR softAP MLD on one or both of the primary and non-primary links. In some cases, sending a CTS frame to the STA on both the primary and non-basic links allows the STA to link the non-basic and primary links together.

The NSTR softAP MLD may later determine that the non-primary link is not available. In some implementations, the NSTR softAP MLD may set the CUF to 1 and the DNT bit to 1 based on a determination that the non-primary link is not available. In some cases, the NSTR softAP MLD may indicate unavailability of a non-primary link by transmitting a CTS frame only on the primary link based on receiving an RTS frame from the STA. For example, if the STA queues UL data, the STA transmits another RTS frame to the NSTR softAP MLD on the primary link. NSTR softAP MLD receives the RTS frame and transmits the CTS frame to the STA only on the primary link based on the unavailability of the non-primary link. The STA receives the CTS frame and determines that the non-primary link is unavailable based on receiving the CTS frame only on the primary link. The STA transmits one or more UL PPDUs to the NSTR softAP MLD only on the basic link.

In some other implementations, the NSTR softAP MLD may perform a channel switching operation based on a determination that a non-primary link is not available. For example, in some cases, the NSTR softAP MLD may transition the primary link from the first wireless channel to the second wireless channel while simultaneously transitioning the non-primary link from the second wireless channel to the first wireless channel. In some aspects, the first wireless channel may be located in the 6 GHz frequency band and the second wireless channel may be located in the 5 GHz frequency band. In other aspects, the first wireless channel may be located in the 5 GHz frequency band and the second wireless channel may be located in the 6 GHz frequency band. In some other aspects, the first wireless channel may be located in one of the 2.4 GHz frequency band, the 5 GHz frequency band, or the 6 GHz frequency band, and the second wireless channel may be located in the 2.4 GHz frequency band, the 5 GHz frequency band, or It may be located in another one of the 6 GHz frequency bands.

NSTR softAP MLD can simultaneously switch channels on primary and non-primary links using any suitable rules or mechanisms. In some implementations, the NSTR softAP MLD determines the channel carried in the body of a management frame (e.g., a beacon frame, probe response frame, association response frame, or reassociation response frame) transmitted on the primary link when performing a channel switching operation. You can use a transition notification (CSA) element or an extended channel transition notification (eCSA) element.

FIG. 8B shows a sequence diagram depicting another example multi-link communication 810 according to some implementations. In the example of Figure 8B, multi-link communication 810 may be performed between the NSTR softAP MLD and one or more associated STAs described with reference to Figures 7A and 7B (only one associated STA is shown for simplicity). . The NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD. As discussed, NSTR softAP MLD can advertise profiles of both primary and non-default links only on primary links.

In some implementations, the NSTR softAP MLD transmits a first frame only on the primary link, including the full profile of the primary link and MLD information common to the primary and non-primary links. In some cases, the first frame may include a frame body containing a plurality of fields and elements followed by an ML element. Multiple fields and elements may convey the entire profile of the underlying link. ML elements may consist of MLD common information. That is, the ML element carried in the first frame may not include link information related to the non-default link. In some cases, the MLD common information may include an MLD medium access control (MAC) address field, a link ID information field, a BPCC field, a synchronization delay field, an enhanced multi-link (EML) capability field, and an MLD capability field ( but is not limited to this). The MLD MAC address field may include the MAC address of the NSTR softAP MLD. The BPCC field may indicate updates to one or more BSS parameters associated with the basic link.

The STA may receive the first frame transmitted on the basic link, parse the first frame, and obtain the entire profile and MLD common information of the basic link. The STA may use the full profile of the primary link to discover or associate with the NSTR softAP MLD on the primary link, and may use the MLD common information to determine whether to request the full profile of the non-primary link from the AP MLD. .

The STA transmits a second frame on the primary link containing a request for the full profile of the non-primary link. In some cases, the request frame may be a broadcast probe request frame. In other cases, the second frame may be an association request frame. In some other cases, the second frame may be a reassociation request frame.

The NSTR softAP MLD receives the second frame and parses the request for the full profile of the non-default link. In response to the request, the NSTR softAP MLD transmits a third frame representing the entire profile of the non-default link only on the default link. In some implementations, the body of the third frame may include an ML element and an RNR element. The ML element may carry an STA-specific profile sub-element representing the overall profile of the non-default link. The RNR element may include a neighbor AP information field associated with the non-primary link consisting of the BSSID and one or more MLD parameters of the non-primary link. In some cases, the MLD parameter field of the TBTT information field carried in the neighbor AP information field may include a PBCC field that carries a value indicating whether any of the BSS parameters of the non-primary link have been updated. In some other cases, a value indicating whether any of the non-basic link's BSS parameters have been updated may be carried in another suitable field, element, or header of the third frame.

As discussed with reference to Figure 7A, the primary link may be configured as a full BSS, and the non-primary link may be configured as a pseudo-BSS that shares at least some capabilities and operating parameters with the primary link. In some cases, a non-default link may have the same SSID, TSF value, and beacon interval as the default link, and may inherit these values from the default link. A non-default link may also inherit the default link's TBTT offset, short-SSID, BSS parameters, and PSD limits. Because of this, the TBTT information field carried in the adjacent AP information field associated with a non-primary link may lack the TBTT offset, short-SSID, BSS parameters, and PSD subfields, thereby reducing the length or size of the corresponding RNR element. You can.

In various implementations, the first frame may be a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. The second frame may be a probe request frame, an association request frame, or a reassociation request frame. The third frame may be a probe response frame, an association response frame, or a reassociation response frame.

FIG. 9A shows a timing diagram depicting example multi-link communication 900 in accordance with some implementations. In the example of Figure 9A, multi-link communication 900 may be performed between the NSTR softAP MLD described with reference to Figures 7A, 7B, 8A, or 8B and two associated wireless stations STA1 and STA2. The STA may be any suitable wireless communication device, including, for example, STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. The NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD. In some implementations, STA1 is a legacy device configured to operate in accordance with a previous revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and STA2 is configured to operate in accordance with a later revision to the IEEE 802.11be or 802.11 family of wireless communications standards. It is a non-legacy device configured to:

Before time t ₀ , the NSTR softAP MLD competes for channel access to the primary link using an appropriate channel access mechanism (e.g., EDCA mechanism) to obtain a transmission opportunity (TXOP) on the primary link. After obtaining TXOP on the primary link, NSTR softAP MLD can also acquire channel access to the non-primary link. In some cases, obtaining channel access to a non-primary link may be based on obtaining channel access or TXOP on the primary link. In some implementations, NSTR softAP MLD may limit transmission on non-primary links to individually addressed frames.

At time t ₀ , the NSTR softAP MLD transmits the first beacon frame 901, which includes the entire profile of the default link and represents the entire profile of the non-default link, only on the default link. A basic link may consist of a full BSS, and a non-basic link may consist of a pseudo-BSS that inherits one or more capabilities and operating parameters from the basic link. For example, in some aspects, a non-primary link may inherit the SSID, TSF value, and beacon interval from the primary link.

Beacon frame 901 includes a frame body containing a plurality of fields and elements followed by an ML element. Multiple fields and elements may convey the entire profile of the underlying link. The ML element may carry an STA-specific profile sub-element representing the overall profile of the non-default link. The ML element may include a common information field carrying a BPCC field indicating updates to one or more BSS parameters associated with the underlying link. In some cases, one or more bits of the multi-link control field or common information field carried in the ML element may indicate whether the first beacon frame 901 is transmitted from the first AP of the NSTR softAP MLD. For example, one or more bits of the multi-link control field or the common information field may be set to a first value indicating that the first beacon frame 901 is transmitted from the first AP of the NSTR softAP MLD, or simultaneous transmission - It may be set to a second value indicating that the first beacon frame 901 is transmitted from the AP associated with the receiving (STR) device (eg, AP MLD).

The first beacon frame 901 may also include an RNR element carrying a neighbor AP information field associated with the non-primary link. The Neighbor AP Information field may carry a TBTT Information field consisting of the BSSID and one or more MLD parameters of the non-primary link. In some cases, the MLD parameter field of the TBTT information field may include a BPCC field carrying a value indicating an update to one or more BSS parameters associated with the non-primary link. In some other cases, one or more values indicating an update to one or more BSS parameters associated with the non-basic link may be carried in another suitable field, element, or header of the first beacon frame 901.

STA1 and STA2 may receive the first beacon frame 901 on the basic link and parse the first beacon frame 901 to obtain the entire profile of the basic link and the non-basic link. In some implementations, STA1 and STA2 may each parse or decode the entire profile of the underlying link carried in fields and elements included in the body of the first beacon frame 901. STA2, as a non-legacy device, can also parse or decode the full profile of the non-default link indicated in the ML element of the first beacon frame 901. STA1 as a legacy device may not be able to parse or decode one or more portions of the ML elements carried in the first beacon frame 901, and thus the capabilities, operating parameters, and Other discovery information may not be obtained. STA1 may also be unable to parse or decode one or more portions of the RNR element carried in the first beacon frame 901. Accordingly, STA2 can discover and associate with the NSTR softAP MLD on both primary and non-primary links using the information obtained in the first beacon frame 901, while STA1 can use the information obtained in the first beacon frame 901 Using the obtained information, NSTR softAP MLD can be discovered and associated with only the basic link. In this way, communication between the NSTR softAP MLD and STA1 (and other legacy devices associated with the NSTR softAP MLD) can be limited to the primary link.

At time t ₁ , the NSTR softAP MLD simultaneously transmits the first DL PPDU 911 to STA1 on the basic link and the second DL PPDU 912 to STA2 on the non-basic link. In some cases, the NSTR softAP MLD may use the first antenna resource group to transmit the DL PPDU 911 to the first STA group (e.g., STA1) on the primary link and DL PPDU 912 on the non-primary link. ) can be used to transmit the second antenna resource group to the second STA group (eg, STA2).

Between time t ₁ and time t ₂ , STA1 receives the first DL PPDU 911 on the primary link, and STA2 receives the second DL PPDU 912 on the non-primary link. Simultaneous transmission of DL PPDUs 911 and 912 on the primary link and non-primary link allows wireless communication devices (e.g., STA1 and STA2) associated with the NSTR softAP MLD to transmit the primary link and the non-primary link between time t ₁ and time t ₂ . It is possible to prevent UL data from being transmitted to NSTR softAP MLD on the basic link.

In some cases, the NSTR softAP MLD uses an appropriate channel access mechanism to compete for channel access to the primary link between time t ₂ and time t ₃ to obtain another TXOP on the primary link. NSTR softAP MLD can obtain TXOP on the non-default link by obtaining TXOP on the primary link and then obtaining channel access to the non-primary link. In some other cases, the NSTR softAP MLD may maintain the TXOP obtained on the primary link and the non-primary link between time t ₀ and t ₁ , and may compete for channel access between time t ₂ and t _3. You may not need it.

At time t ₃ , the NSTR softAP MLD transmits the second beacon frame 902 only on the primary link. In some implementations, the second beacon frame 902 can be similar to the first beacon frame 901, for example, by carrying the entire profile of the primary link and displaying the entire profile of the non-primary link. there is. In some other implementations, the second beacon frame 902 may include less information than the first beacon frame 901. For example, in some cases, the second beacon frame 902 may carry or indicate a partial profile of one or both the primary link and the non-primary link. In some other cases, the second beacon frame 902 may carry a full or partial profile of the primary link and may not include capabilities or operating parameters of the non-primary link. In some implementations, the second beacon frame 902 may be similar to the first frame described with reference to FIG. 8B, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link. .

At time t ₄ , NSTR softAP MLD transmits DL PPDU (921) to STA1 on the basic link. STA1 can receive the DL PPDU (921) on the basic link from time t ₄ to time t ₅ . Aspects of the present disclosure recognize that cross-link interference resulting from transmission of the DL PPDU 921 on the primary link may cause a period of “deafness” on the non-primary link, during which NSTR softAP MLD cannot receive or properly decode UL transmissions on non-primary links. In some implementations, the NSTR softAP MLD may cause the non-primary link to enter the deaf state 914 while transmitting the DL PPDU 921 on the primary link. A non-primary link may not be available for communication between the NSTR softAP MLD and its associated STA when in a hearing loss state 914. Specifically, in some aspects, STA2 (and other wireless communication devices associated with the NSTR softAP MLD) may not be allowed to transmit UL data over the non-default link during the hearing loss condition 914. In this way, UL transmissions that the NSTR softAP MLD may not receive or decode properly due to cross-link interference caused by the transmission of the DL PPDU 921 on the primary link are prevented or delayed until after the DL transmission has ended. It can be.

Hearing loss condition 914 may be of any suitable duration. In some cases, the duration of the hearing loss condition 914 may be temporally aligned with the transmission duration of the DL PPDU 921 on the primary link. In some other cases, the duration of the hearing loss condition 914 may include a guard time followed by the transmission duration of the DL PPDU 921 followed by another guard time. Other durations may be suitable for hearing loss conditions 914. In some implementations, the guard time may be selected to prevent (or to some extent reduce) the effects of cross-link interference on DL communications transmitted on the non-primary link. For example, in some cases, the duration of the guard time may be configured such that the first and last symbols of the DL PPDU 921 do not interfere with UL transmission on the non-primary link.

After transmission of the DL PPDU (921) ends, the NSTR softAP MLD recovers the non-primary link from the hearing loss condition (914). The NSTR softAP MLD may recover a non-primary link from a hearing loss condition 914 using any suitable loss recovery rules or mechanisms. In some implementations, the NSTR softAP MLD may send an indication of the availability of a non-primary link on the primary link based on recovery of the non-primary link. In implementations where the NSTR softAP MLD removes a non-primary link in a multi-link context when the non-primary link is placed in a deaf state 914 (and thus becomes unavailable), the non-primary link is placed in a deaf state 914. Recovering at 914 may include adding the non-default link to the multi-link context. In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that a non-primary link has been added to the multi-link context. In implementations where the NSTR softAP MLD remaps the TID from the non-default link to the default link when the non-default link is placed in an inactive state 914 (and thus becomes unavailable), the non-default link Recovering from the hearing loss condition 914 may include remapping the TID from a primary link to a non-primary link. In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that some TIDs associated with the primary link have been remapped to a non-primary link.

At time t ₆ , STA1 transmits the UL PPDU (922) to the NSTR softAP MLD on the primary link, and STA2 transmits the UL PPDU (923) to the NSTR softAP MLD on the non-primary link. NSTR softAP MLD receives UL PPDUs (922, 923) between time t ₆ and time t ₇ . Simultaneous transmission of UL PPDUs (922 and 923) on the primary link and non-primary link can prevent the NSTR softAP MLD from transmitting DL data on the primary link and non-primary link between time t ₆ and time t ₇ . , which may eliminate the need to leave the non-primary link in a deaf state between time t ₆ and time t ₇ .

In some cases, the NSTR softAP MLD uses an appropriate channel access mechanism to compete for channel access to the primary link between time t ₇ and time t ₈ to obtain another TXOP on the primary link. NSTR softAP MLD can obtain TXOP on the non-default link by obtaining TXOP on the primary link and then obtaining channel access to the non-primary link.

At time t ₈ , NSTR softAP MLD transmits the third beacon frame 903 only on the basic link. In some implementations, the third beacon frame 903 can be similar to the first beacon frame 901, for example, by carrying the entire profile of the primary link and displaying the entire profile of the non-primary link. there is. In some other implementations, third beacon frame 903 may be similar to second beacon frame 902, for example, by carrying less information than first beacon frame 901.

At t ₉ , STA1 transmits the UL PPDU (931) to the NSTR softAP MLD on the basic link. Between t ₉ and t ₁₀ , the NSTR softAP MLD receives the UL PPDU (931) on the primary link. Aspects of the present disclosure recognize that cross-link interference resulting from transmission of the UL PPDU 931 on the primary link may interfere with DL transmission on the non-primary link. In some implementations, the NSTR softAP MLD places the non-primary link in a deaf state (932) while transmitting the UL PPDU (931) on the primary link. A non-primary link may not be available for communication between the NSTR softAP MLD and its associated STA when in a hearing loss state 931. In some implementations, the NSTR softAP MLD may not transmit DL data on the non-primary link during the hearing loss condition 932. In this way, DL transmissions on non-primary links that are vulnerable to cross-link interference resulting from transmission of the UL PPDU 931 on the primary link can be prevented or delayed until after the hearing loss condition 932 expires. In some cases, STA2 (and other wireless communication devices associated with the NSTR softAP MLD) may not be permitted to transmit UL data on the non-primary link during the hearing loss condition 932.

Hearing loss condition 932 may be of any suitable duration. In some cases, the duration of the hearing loss condition 932 may be temporally aligned with the transmission duration of the UL PPDU 931 on the primary link. In some other cases, the duration of the hearing loss condition 932 may include a guard time followed by the transmission duration of the UL PPDU 931 followed by another guard time. Other durations may be suitable for the hearing loss condition 932. In some implementations, the guard time may be selected to prevent (or to some extent reduce) the effects of cross-link interference on DL communications transmitted on the non-primary link. For example, in some cases, the duration of the guard time may be configured such that DL transmission on a non-primary link does not interfere with the first or last symbol of the UL PPDU 931. After the UL PPDU 931 transmission ends or the hearing loss condition 932 expires, the NSTR softAP MLD recovers the non-primary link from the hearing loss condition 932.

FIG. 9B shows a sequence diagram depicting an example multi-link (ML) communication 940 in accordance with some implementations. In some implementations, multi-link communication 940 may be performed between the NSTR softAP MLD and radio stations STA1 and STA2 described with reference to FIG. 9A. In some other implementations, multi-link communication 940 may be performed between the NSTR softAP MLD described with reference to FIGS. 7A, 7B, 8A, or 8B and associated wireless stations STA1 and STA2. The STA may be any suitable wireless communication device, including, for example, STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. The NSTR softAP MLD may include a first AP associated with a primary link and a second AP associated with a non-primary link. In some cases, the first and second AP may be a softAP implemented by the STA operating as an NSTR softAP MLD. As discussed, STA1 is a legacy device configured to operate in accordance with a previous revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and STA2 is configured to operate in accordance with a later revision to the IEEE 802.11be or 802.11 family of wireless communications standards. It is a configured non-legacy device.

Before time t ₀ , the NSTR softAP MLD competes for channel access to the primary link using an appropriate channel access mechanism (e.g., EDCA mechanism) to obtain a TXOP on the primary link. After obtaining TXOP on the primary link, NSTR softAP MLD can also acquire channel access to the non-primary link. In some cases, obtaining channel access to a non-primary link may be based on obtaining channel access or TXOP on the primary link. In some implementations, NSTR softAP MLD may limit transmission on non-primary links to individually addressed frames.

At time t ₀ , the NSTR softAP MLD transmits the first beacon frame 941 only on the basic link. The first beacon frame 941 may include the entire profile of the basic link and may represent the entire profile of the non-default link. As discussed, a basic link can consist of a full BSS, and a non-basic link can consist of a pseudo-BSS that inherits one or more capabilities and operating parameters from the basic link. For example, in some aspects, a non-default link may have the same SSID, TSF value, and beacon interval as the default link, and may inherit the SSID, TSF value, and beacon interval from the default link.

In some implementations, first beacon frame 941 may be similar to first beacon frame 901 of FIG. 9A. That is, the first beacon frame 941 may include a frame body including a plurality of fields and elements followed by an ML element. Multiple fields and elements may convey the entire profile of the underlying link. The ML element may carry an STA-specific profile sub-element representing the overall profile of the non-default link. The ML element contains a common information field carrying a BPCC field indicating updates to one or more BSS parameters of the underlying link. One or more bits of the multi-link control field or common information field carried in the ML element may indicate whether the first beacon frame 941 is transmitted from the first AP of the NSTR softAP MLD. The first beacon frame 941 may also include an RNR element carrying a neighbor AP information field associated with the non-primary link. The Neighbor AP Information field may carry a TBTT Information field consisting of the BSSID and one or more MLD parameters of the non-primary link. In some cases, the MLD parameter field of the TBTT information field carried in the neighbor AP information field associated with the non-primary link may include a BPCC field carrying a value indicating an update to one or more BSS parameters of the non-primary link. there is. In some other cases, a value indicating an update to one or more BSS parameters associated with the non-basic link may be carried in another suitable field, element, or header of the first beacon frame 941.

STA1 and STA2 may receive the first beacon frame 941 on the primary link and parse the beacon frame 941 to obtain the full profile of the primary link and non-basic link. In some implementations, STA1 and STA2 may each parse or decode the entire profile of the basic link carried in fields and elements included in the body of the first beacon frame 941. STA2, as a non-legacy device, can also parse or decode the entire profile of the non-default link indicated in the ML element of the first beacon frame 941. STA1 as a legacy device may not be able to parse or decode one or more portions of the ML elements carried in the first beacon frame 941 and therefore may be unable to determine the capabilities, operating parameters, and other information of the non-basic link from the first beacon frame 941. Discovery information may not be obtained. STA1 may also be unable to parse or decode one or more portions of the RNR element carried in the first beacon frame 941. Accordingly, STA2 can discover and associate with the NSTR softAP MLD on both primary and non-primary links using the information obtained in the first beacon frame 941, while STA1 can use the information obtained in the first beacon frame 941 Using the obtained information, NSTR softAP MLD can be discovered and associated with only the basic link. In this way, communication between NSTR softAP MLD and STA1 (and other legacy devices) can be limited to the primary link.

At time t ₁ , the NSTR softAP MLD transmits the first trigger frame 951 on the basic link while simultaneously transmitting the second trigger frame 952 on the non-basic link. The first trigger frame 951 may request UL transmission from a first STA group (including STA1) on the primary link, and the second trigger frame 952 may request UL transmission from a second STA group (including STA2) on the non-primary link. UL transmission can be requested.

Between time t ₂ and time t ₃ , STA1 transmits a trigger-based (TB) PPDU 961 to the NSTR softAP MLD on the primary link based on receiving the first trigger frame 951, and STA2 transmits the second trigger Based on receiving the frame 952, TB PPDU 962 is transmitted to the NSTR softAP MLD on the non-primary link. Simultaneous transmission of TB PPDUs (961 and 962) from STA1 and STA2, respectively, on the primary and non-primary links allows the NSTR softAP MLD to transmit DL data on the primary and non-primary links between time t ₂ and time t ₃ . transmission can be prevented, which can eliminate the need to leave the non-primary link in a deaf state between times t ₂ and times t ₃ .

In some implementations, NSTR softAP MLD can establish coordinated TWT sessions on primary and non-primary links. Although not shown in FIG. 9B for simplicity, a TWT session on the primary link includes one or more service periods (SPs) in which the NSTR softAP MLD can schedule transmissions to and from STA1 or the first STA group on the primary link. may include, and the NSTR softAP MLD may include one or more SPs that can reserve transmission to and from STA2 or a second STA group on a non-primary link. In some cases, the NSTR softAP MLD may synchronize the TWT SPs of each TWT session established on the primary link and the non-primary link with each other. For example, when individual TWT sessions or TWT SPs are coordinated with each other on the basic link and the non-basic link, the NSTR softAP MLD transmits the TB PPDU 962 from STA2 on the non-basic link and simultaneously transmits the TB PPDU (962) on the basic link. It is possible to schedule UL transmission of the TB PPDU (961) from STA1. In this way, the TB PPDU 961 transmission from STA1 on the primary link can be temporally aligned with the TB PPDU 962 transmission from STA2 on the non-primary link.

In some cases, the NSTR softAP MLD competes for channel access to the primary link between time t ₃ and time t ₄ using an appropriate channel access mechanism (e.g., EDCA mechanism) to obtain a TXOP on the primary link. NSTR softAP MLD can obtain TXOP on the non-default link by obtaining TXOP on the primary link and then obtaining channel access to the non-primary link. In some other cases, the NSTR softAP MLD may maintain the TXOP obtained on the primary link and the non-primary link between time t ₀ and t ₁ , and may compete for channel access between time t ₃ and t _4. You may not need it.

At time t ₄ , the NSTR softAP MLD transmits the second beacon frame 942 only on the basic link. In some implementations, the second beacon frame 942 can be similar to the first beacon frame 941, for example, by carrying the entire profile of the primary link and displaying the entire profile of the non-primary link. there is. In some other implementations, the second beacon frame 942 may include less information than the first beacon frame 941. For example, in some cases, the second beacon frame 942 may carry or indicate a partial profile of one or both the primary link and the non-primary link. In some other cases, the second beacon frame 942 may carry a full or partial profile of the primary link and may not include capabilities or operating parameters of the non-primary link. In some implementations, the second beacon frame 942 may be similar to the first frame described with reference to FIG. 8B, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link. .

At time t ₅ , the NSTR softAP MLD transmits the third trigger frame 953 on the non-primary link. The third trigger frame 953 requests UL transmission from STA2 (or a second STA group) on a non-basic link. Between time t ₆ and time t ₇ , STA2 transmits the TB PPDU 963 to the NSTR softAP MLD on the non-primary link based on receiving the third trigger frame 953. In the example of FIG. 9B, STA1 transmits the unsolicited UL PPDU 971 to the NSTR softAP MLD on the primary link between time t ₆ and time t ₇ . Transmission of UL PPDU (971) and TB PPDU (963) from STA1 and STA2 on the primary link and non-primary link, respectively, is performed by NSTR softAP MLD on the primary link and non-primary link between time t ₆ and time t ₇ . Transmitting DL data can be avoided, which can eliminate the need to leave the non-primary link in a deaf state between time t ₆ and time t ₇ .

In some implementations, the NSTR softAP MLD may establish a TWT session independent of the non-primary link to schedule the transmission of the TB PPDU 963 to the NSTR softAP MLD. Although not shown in Figure 9B for simplicity, an independent TWT session on a non-primary link allows the NSTR softAP MLD to schedule UL transmissions from STA2 or DL transmissions to STA2 (and other related devices) on the non-primary link. It may contain one or more SPs.

At time t ₈ , the NSTR softAP MLD simultaneously transmits the first DL PPDU (981) to STA1 on the basic link and the second DL PPDU (982) to STA2 on the non-basic link. Between time t ₈ and time t ₉ , STA1 receives the first DL PPDU 981 on the primary link, and STA2 receives the second DL PPDU 982 on the non-primary link. Since the NSTR softAP MLD does not receive any UL communication between time t ₈ and time t ₉ , the simultaneous transmission of DL PPDU 981 and DL PPDU 982 on the primary and non-primary links, respectively, occurs between time t ₈ and time t 9. Cross-link interference caused by UL transmission between time points _t9 may not be visible.

In some implementations, the NSTR softAP MLD is coordinated on the primary and non-primary links to schedule transmission of DL PPDU 981 and DL PPDU 982 to STA1 and STA2, respectively, on the primary and non-primary links. You can set TWT SP. In this way, NSTR softAP MLD can ensure that STA1 and STA2 are awake to receive DL PPDU (981 and 982) transmission, respectively. In some cases, the TWT SP for the non-primary link is synchronized with the TWT SP for the primary link so that DL transmissions on the primary link and the non-primary link can be aligned with each other in time. In some cases, the NSTR softAP MLD may use the first antenna resource group to transmit DL PPDU 981 to the first STA group (including STA1) on the primary link and DL PPDU 982 on the non-primary link. The second antenna resource group can be used to transmit to the second STA group (including STA2).

At time t ₁₀ , NSTR softAP MLD transmits the third beacon frame 943 only on the basic link. In some implementations, the third beacon frame 943 can be similar to the first beacon frame 941, for example, by carrying the entire profile of the primary link and indicating the entire profile of the non-primary link. there is. In some other implementations, third beacon frame 943 may be similar to second beacon frame 942, for example, by carrying less information than first beacon frame 941.

At t ₁₁ , STA1 transmits UL PPDU (991) to NSTR softAP MLD on the basic link. NSTR softAP MLD can receive UL PPDU (991) on the basic link between time t ₁₁ and time t ₁₂ . Aspects of the present disclosure recognize that cross-link interference resulting from transmission of the UL PPDU 991 on the primary link may cause periods of hearing loss on the non-primary link. In some implementations, the NSTR softAP MLD may place the non-primary link in a deaf state 992 while transmitting the UL PPDU 991 on the primary link. A non-primary link may not be available for communication between the NSTR softAP MLD and its associated STA when in a hearing loss state 992. In some implementations, the NSTR softAP MLD may not transmit DL data on the non-primary link during the hearing loss condition 992. In this way, DL transmissions on non-primary links that are vulnerable to cross-link interference resulting from transmission of UL PPDU 991 on the primary link can be prevented or delayed until after the hearing loss condition 992 expires. In some cases, STA2 (and other wireless communication devices associated with the NSTR softAP MLD) may not be permitted to transmit UL data on the non-primary link during the hearing loss condition 992.

Hearing loss condition 992 may be of any suitable duration. In some cases, the duration of the hearing loss condition 992 may be temporally aligned with the transmission duration of the UL PPDU 991 on the primary link. In some other cases, the duration of the hearing loss condition 992 may include a guard time followed by the transmission duration of the UL PPDU 991 followed by another guard time. Other durations may be appropriate for the hearing loss condition 992. In some implementations, the guard time may be selected to prevent (or to some extent reduce) the effects of cross-link interference on DL communications transmitted on the non-primary link. For example, in some cases, the duration of the guard time may be configured such that DL transmission on the non-primary link does not interfere with the first or last symbol of the UL PPDU 991. After the UL PPDU 991 transmission ends or after the hearing loss condition 992 expires, the NSTR softAP MLD recovers the non-primary link from the hearing loss condition 992.

FIG. 10A illustrates an example management frame 1000A usable for wireless communications supporting NSTR softAP MLD, according to some implementations. Management frame 1000A may be a beacon frame, probe response frame, association response frame, reassociation response frame, or some other suitable management frame. In some aspects, management frame 1000A is the first or second frame of FIG. 7A, the first or second frame of FIG. 7B, the frame of FIG. 8A, the third frame of FIG. 8B, the beacon frame of FIG. 9A, or This may be an example implementation of the beacon frame of FIG. 9B. For ease of description, some information elements of frame 1000A may be considered interchangeably terms "field", "subfield", "element", or "sub-element" for purposes of discussion herein. It may also be referred to as .

Frame 1000A is shown to include a plurality of elements and fields 1010, reduced neighbor reporting (RNR) element 1020, capabilities and operating parameters 1030, and base multi-link (ML) element 1040. It is done. Elements and fields 1010 may carry the entire profile of the underlying link. RNR element 1020 may include one or more AP entries 1022. Each of the AP entries 1022 may be associated with a respective AP in the AP MLD and may carry or indicate one or more parameters of each AP. In some implementations, the one or more parameters may include the BSSID and MLD parameters of each AP. In some cases, each AP entry 1022 may not include one or more of the TBTT offset, short-SSID, BSS parameter, or PSD limit of the corresponding non-primary link. Capabilities and operating parameters 1030 may include any number of capabilities and operating parameters associated with the underlying link. The ML element 1040 may include common information 1042 and a number of STA-specific profile sub-elements 1044(1) to 1044(n). Common information 1042 may include MLD parameters and other information that are common to the primary link and one or more non-primary links. Each of the STA-specific profile sub-elements 1044(1) to 1044(n) may be associated with a corresponding non-default link of the AP MLD, and may carry or display the entire profile of the corresponding non-default link. .

FIG. 10B illustrates another example management frame that can be used for multi-link communication with an NSTR softAP MLD, according to some implementations. Management frame 1000B may be a beacon frame, probe response frame, association response frame, reassociation response frame, or some other suitable management frame. In some aspects, management frame 1000B may be an example implementation of the first frame of FIG. 8B. For ease of description, some information elements of frame 1000A may be considered interchangeably terms "field", "subfield", "element", or "sub-element" for purposes of discussion herein. It may also be referred to as .

Frame 1000B is shown as including a plurality of elements and fields 1010, an RNR element 1020, capabilities and operating parameters 1030, and a basic ML element 1050. Elements and fields 1010 may carry the entire profile of the underlying link. RNR element 1020 may include one or more AP entries 1022. Each of the AP entries 1022 may be associated with a respective AP in the AP MLD and may carry or indicate one or more parameters of each AP. In some implementations, the one or more parameters may include the BSSID and MLD parameters of each AP. In some cases, each AP entry 1022 may not include one or more of the TBTT offset, short-SSID, BSS parameter, or PSD limit of the corresponding non-primary link. Capabilities and operating parameters 1030 may include any number of capabilities and operating parameters associated with the underlying link. ML element 1050 may include common information 1042. Common information 1042 may include MLD parameters and other information common to one or more non-primary links and primary links associated with the AP MLD.

FIG. 11A shows an example RNR element 1100 usable for multi-link communications, according to some implementations. In some implementations, RNR element 1100 may be an example implementation of RNR element 1020 of example management frames 1000A and 1000B described with reference to FIGS. 10A and 10B, respectively. In some cases, the RNR element 1100 may be included in a frame such as, but not limited to, a beacon frame, probe response frame, association response frame, or reassociation response frame transmitted from the AP MLD. For ease of description, some information elements of MLE 1100 may be considered interchangeable terms "field", "subfield", "element", or "sub-element" for purposes of discussion herein. It may also be referred to as .

The RNR element 1100 may be used to indicate channel information, parameters, and other information related to one or more APs involved in the AP MLD. As shown, RNR element 1100 includes an element ID field 1102, a length field 1104, and one or more neighbor AP information fields 1106. Element ID field 1102 carries a value that identifies the RNR element 1100. The length field 1104 carries a value indicating the length of the RNR element 1100. Each neighboring AP information field 1106 carries information indicating the timing reference, operating class, channel number, and other parameters of the corresponding AP in the AP MLD.

As shown, the neighbor AP information field 1106 includes a TBTT information header 1111, an operating class field 1112, a channel number field 1113, and a TBTT information set field 1114. The TBTT information header 1111 carries general information about the corresponding AP. The operating class field 1112 indicates a channel start frequency indicating the basic channel of the BSS of the AP associated with the adjacent AP information field along with the channel number field. The channel number field 1113 indicates the last known basic channel of the AP associated with the neighboring AP information field. The TBTT information set field 1114 includes one or more TBTT information fields carrying TBTT information, operating parameters, and MLD parameters for the AP associated with the Neighbor AP Information field.

In some implementations, the RNR element 1100 stores one or more unique link IDs that can be used to map entries within the neighbor AP information fields 1106 with information stored in the link-specific profile sub-element of the ML element. It can be extended to include an ID field. In some other implementations, RNR element 1100 may be extended to include a Do Not Transmit (DNT) field that may carry a DNT indication for the corresponding communication link. Additionally or alternatively, one or more elements or fields of RNR element 1100 may be combined, added, removed, or modified.

FIG. 11B shows an example TBTT information header 1120 according to some implementations. In some cases, TBTT information header 1120 may be an example implementation of TBTT information header 1111 of FIG. 11A. As shown, the TBTT information header 1120 includes a TBTT information field type subfield 1121, a filtered neighbor AP subfield 1122, a reserved subfield 1123, a TBTT information count subfield 1124, and Contains a TBTT information length subfield (1125). The TBTT information field type subfield 1121 returns a value indicating the type or format of the TBTT information field. In some implementations, the value of the TBTT Information Field Type subfield 1121 can be set to 1 or a reserved value indicating that the TBTT Information Field is a new type or format associated with an NSTR device. In this way, a wireless communication device that has received an RNR element with the TBTT Information Field Type subfield set to 1 or a reserved value can determine that the frame carrying that RNR element was transmitted by an NSTR device.

The Filtered Neighbor AP subfield 1122 is reserved except when a reduced Neighbor Report element is returned in a probe response frame transmitted by a TVHT AP. Reserved subfield 1123 contains one or more reserved or unused bits. The TBTT information number subfield 1124 represents the number of TBTT information fields included in the TBTT information set field of the adjacent AP information field minus 1. The TBTT information length subfield 1125 indicates the length of each TBTT information field included in the TBTT information set field of the adjacent AP information field.

Figure 11C shows an example TBTT information field 1130 according to some implementations. In some cases, TBTT information field 1130 may be an implementation of the TBTT information field(s) carried in TBTT information set field 1114 of FIG. 11A. As shown, the TBTT information field 1130 includes a neighboring AP TBTT offset subfield 1131, an optional BSSID subfield 1132, an optional Short-SSID subfield 1133, a BSS parameters subfield 1134, and a 20 MHz field. Includes a PSD subfield 1135, and an MLD parameters subfield 1136. The adjacent AP TBTT offset subfield 1131 indicates the offset (in TU units) of the next TBTT of the reported AP from the immediately previous TBTT of the reporting AP. The optional BSSID subfield 1132 returns the BSSID of the reported AP. The optional Short-SSID subfield 1133 returns the shortened SSID of the reported AP. BSS Parameters subfield 1134 includes (such as) OCT Recommended subfield, Same SSID subfield, Multiple BSSID subfield, Transmitted BSSID subfield, ESS Membership subfield, Spontaneous Probe Response Active subfield, and Co-located AP subfield. (but not limited to this) indicates one or more BSS parameters of the reported AP. The 20 MHz PSD subfield 1135 indicates the maximum transmit power for the corresponding AP in the basic 20 MHz channel. In some cases, the Neighbor AP TBTT Offset subfield 1131, Short-SSID subfield 1133, BSS Parameters subfield 1134, and 20 MHz PSD subfield 1135 are omitted from the TBTT Information field 1130. It can be.

The MLD parameters subfield 1136 includes an MLD ID subfield, a link ID subfield, a BSS parameter change count (BPCC) subfield, and a reserved subfield. The MLD ID subfield represents the identifier of the AP MLD and can be used to identify the reported AP list associated with the AP MLD. The Link ID subfield indicates the link identifier of the corresponding AP and is unique to the corresponding AP. The BSS Parameter Change Count subfield is an unsigned integer that is initialized to 0 and incremented when a significant update to the reported AP's beacon frame occurs. A reserved subfield contains one or more reserved or unused bits.

FIG. 12A illustrates an example multi-link (ML) element 1200 that can be used for multi-link communications, according to some implementations. In some implementations, ML element 1200 may be an example implementation of basic ML element 1040 described with reference to FIG. 10A. In some cases, ML element 1200 may be included in a frame such as, but not limited to, a beacon frame, probe response frame, association response frame, or reassociation response frame transmitted from the NSTR softAP MLD. For ease of description, some information elements of ML 1200 are referred to as “fields,” “subfields,” “elements,” or “sub-elements,” which may be considered interchangeable terms for purposes of discussion herein. It may also be referred to as .

The ML element 1200 includes an element ID field 1201, a length field 1202, an element ID extension field 1203, a multi-link control field 1204, a common information field 1205, and a link information field 1206. Includes. The element ID field 1201 and the element ID extension field 1203 indicate that the element 1200 is an ML element and return a value indicating the type of the ML element. The length field 1202 carries a value indicating the length of the ML element 1200. The multi-link control field 1204 carries information indicating the presence of various fields and subfields of the common information field 1205. Common information field 1205 carries information that is common to one or more non-primary links associated with the AP MLD. Link information field 1206 carries information specific to each non-primary link associated with the AP MLD. In some cases, link information field 1206 includes one or more STA-specific profile sub-elements that may convey or indicate the overall profile of one or more corresponding non-default links of an AP MLD, such as an NSTR softAP MLD.

FIG. 12B shows an example multiple link control field 1210 according to some implementations. In some cases, multi-link control field 1210 may be an implementation of multi-link control field 1204 of ML element 1200 of FIG. 12A. As shown, the multi-link control field 1210 includes a type field 1211, a reserved field 1212, and a presence bitmap field 1213. The type field 1211 is used to distinguish between variations of the ML element 1200 (e.g., basic ML element and probe request ML element). Reserved field 1212 includes one or more reserved or unused bits. The presence bitmap field 1213 is used to indicate the presence of various subfields within the common information field 1205 of the ML element 1200. For example, the presence bitmap field 1213 may include the MLD MAC address field, the link ID information field, the BSS parameter change count (BPCC) field 1223, and the intermediate synchronization delay within the common information field 1205 of the ML element 1200. It may indicate the presence of an information field, an enhanced multi-link (EML) capability field, and an MLD capability field.

Figure 12C shows an example common information field 1220 according to some implementations. In some cases, common information field 1220 may be an implementation of common information field 1205 of ML element 1200 of FIG. 12A. As shown, common information fields 1220 include MLD MAC address field 1221, link ID information field 1222, BPCC field 1223, intermediate synchronization delay information field 1224, and enhanced multi-link (EML) capability. field 1225, and MLD capability field 1226. The MLD MAC address field 1221 returns the MAC address of the MLD (eg, NSTR softAP MLD). Link ID information field 1222 carries the link identifier of the AP transmitting ML element 1200. The BSS Parameter Change Count (BPCC) field 1223 carries an unsigned integer initialized to 0, which is incremented when a significant update occurs to the operating parameters for the AP transmitting the base variant ML element.

The Medium Sync Delay information field 1224 returns a value indicating the duration of the MediumSyncDelay timer. EML capability field 1225 includes a number of subfields used to advertise capabilities for EML single radio (SR) operation and EML multi-radio (MR) operation. The MLD capability field 1226 represents various capabilities of the MLD. In some cases, the MLD capability field 1226 may specify the maximum number of links that support simultaneous transmission or reception of frames, whether the MLD supports reception of frames carrying the SRS control subfield, and whether the MLD performs TID-to-link mapping negotiation. It can indicate whether to support, and the minimum frequency spacing between any two links recommended by non-AP MLD for STR operation.

FIG. 12D illustrates an example per-STA profile sub-element 1230 according to some implementations. In some cases, the per-STA profile sub-element 1230 may be an implementation of the per-STA profile sub-element carried in the link information field 1206 of the ML element 1200 in FIG. 12A. As shown, the STA-specific profile sub-element 1230 includes a sub-element ID field 1231, a length field 1232, an STA control field 1233, an STA information field 1234, and an STA profile field 1235. It can be included. The sub-element ID field 1231 returns a value indicating the type of the profile sub-element 1230 for each STA. The length field 1232 returns a value indicating the length of the profile sub-element 1230 for each STA. The STA control field 1233 carries information indicating the presence (or absence) of various fields and subfields within the STA profile field 1235. The STA information field 1234 carries information related to the AP corresponding to the STA-specific profile sub-element 1230. The STA profile field 1235 carries information indicating the entire profile of the AP corresponding to the STA-specific profile sub-element 1230.

Figure 12E shows an example STA control field 1240 according to some implementations. In some cases, the STA control field 1240 may be an implementation of the STA control field 1233 of the per-STA profile sub-element 1230 of FIG. 12D. As shown, the STA control field 1240 includes a link ID field 1241, a full profile field 1242, a MAC address presence field 1243, a beacon interval presence field 1244, a DTIM information presence field 1245, Includes an NSTR Link Pair Presence field (1246), an NSTR Bitmap Size field (1247), and a Reserved field (1248). The link ID field 1241 carries a value that uniquely identifies the communication link associated with the AP corresponding to the STA-specific profile sub-element 1230. The full profile field 1242 carries a value indicating whether the STA-specific profile sub-element 1230 carries the full profile of the corresponding AP. The MAC address presence field 1243 returns a value indicating whether the STA-specific profile sub-element 1230 returns the MAC address of the corresponding AP. The beacon interval presence field 1244 carries a value indicating whether the STA information field 1234 of the STA-specific profile sub-element 1230 carries the beacon interval of the corresponding AP. The DTIM information presence field 1245 carries a value indicating whether the STA information field 1234 of the STA-specific profile sub-element 1230 carries the DTIM information of the corresponding AP. The NSTR link pair presence field 1246 carries a value indicating whether the STA-specific profile sub-element 1230 carries information regarding the communication link pair (e.g., primary link and non-default link) associated with the NSTR softAP MLD. . The NSTR bitmap size field 1247 carries a value indicating the size of the NSTR indication bitmap field included in the STA-specific profile sub-element 1230.

Figure 12F shows an example STA information field 1250 according to some implementations. In some cases, the STA information field 1250 may be an implementation of the STA information field 1234 of the per-STA profile sub-element 1230 of FIG. 12D. As shown, the STA information field 1250 includes a MAC address field 1251, a beacon interval field 1252, a DTIM field 1253, an NSTR link pair field 1254, and an NSTR bitmap field 1255. do. The MAC address field 1251 returns the MAC address of the AP corresponding to the STA-specific profile sub-element 1230. The beacon interval profile field 1252 carries information indicating the beacon interval of the AP corresponding to the profile sub-element 1230 for each STA. The DTIM field 1253 carries information indicating the number of DTIMs and DTIM period of the AP corresponding to the STA-specific profile sub-element 1230. The NSTR link pair field 1254 carries information identifying the communication link pair associated with the AP corresponding to the per-STA profile sub-element 1230. The NSTR bitmap field 1255 carries the NSTR bitmap of the AP corresponding to the STA-specific profile sub-element 1230.

FIG. 13 shows a flow diagram illustrating an example process 1300 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1300 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 1300 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1300 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7A.

In some implementations, process 1300 begins at block 1302 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link. At block 1304, process 1300 continues transmitting a frame only on the primary link, where the frame includes the entire profile of the primary link and represents the entire profile of the non-primary link, respectively, of the primary link and the non-primary link. The overall profile of includes at least beacon interval, capability information, service set identifier (SSID), supported rate, timing synchronization function (TSF) value, and one or more additional fields or elements associated with discovery of each link, respectively. The frame is transmitted only through the basic link and can be one of a beacon frame, probe response frame, association response frame, and re-association response frame. In some cases, the beacon interval, SSID, and TSF values of the non-primary link's global profile are inherited from the primary link's global profile. Because of this, the frame may be missing the beacon interval, SSID, and TSF values of the non-primary link.

In some implementations, the frame includes a multiple link (ML) element that includes a plurality of fields and elements carrying the overall profile of the primary link and carries STA-specific profile sub-elements representing the overall profile of the non-primary link. Includes a frame body that The ML element contains a common information field carrying a BPCC field indicating updates to one or more BSS parameters associated with the underlying link. One or more bits of the multi-link control field or common information field of the ML element may indicate whether a frame is transmitted from the first AP of the NSTR softAP MLD.

The frame body may also include an RNR element carrying a neighbor AP information field associated with the non-primary link. The Neighbor AP Information field may carry a TBTT Information field consisting of the BSSID and one or more MLD parameters of the non-primary link. In some cases, the non-basic link's TBTT offset, short-SSID, BSS parameters, and PSD parameters may be inherited from the primary link. Accordingly, the TBTT offset subfield, short-SSID subfield, BSS parameters subfield, and PSD subfield can be omitted from the TBTT information field in the adjacent AP information field associated with the non-primary link, thereby reducing the size of the RNR element and Overhead is reduced. In some aspects, this reduced size TBTT information field may be a new type of TBTT information field not defined in any of the existing revisions to the 802.11 family of wireless communications standards. To this end, the Neighbor AP Information field may include a TBTT Information field type set to a value indicating that the Neighbor AP Information field carries information related only to non-primary links. In some cases, the TBTT information field type may be set to 1 or a reserved value indicating a new or undefined type of TBTT information field. Setting the TBTT Information Field Type to 1 or a reserved value may also indicate that the associated Neighbor AP Information field, and thus the frame carrying the corresponding RNR element, is transmitted from the AP associated with the NSTR softAP MLD.

In some implementations, the length of the TBTT information field indicates whether the frame is transmitted from the first AP in the NSTR softAP MLD. In some cases, the length of the TBTT information field is 9 octets. One or more MLD parameters of the TBTT information field may include a BPCC field indicating an update to one or more BSS parameters associated with the non-default link.

FIG. 14 shows a flow diagram illustrating an example process 1400 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1400 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 1400 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1400 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7A.

In some implementations, process 1400 may be performed after transmitting the frame at block 1304 of FIG. 13. For example, at block 1402, process 1400 begins with receiving an update to at least one of the BSS parameters associated with the non-primary link. At block 1404, process 1400 continues to increment the value of the BPCC field of the TBTT information field included in the RNR element of another frame based on the received update. At block 1406, process 1400 continues setting a critical update flag (CUF) in the capability information field of another frame based on incrementing the value carried in the BPCC field. At block 1408, process 1400 continues transmitting another frame only on the primary link, where the other frame represents an update to at least one BSS parameter associated with the non-primary link. In some cases, the other frame may be an action frame, such as a beacon frame, probe response frame, association response frame, reassociation response frame, or notification frame.

In some implementations, the BSS parameters include a Channel Switch Announcement (CSA) element, an Extended Channel Switch Announcement (eCSA) element, an Enhanced Distributed Channel Access (EDCA) parameter, a Quiet Period element, and a DSSS ( Direct Sequence Spread Spectrum (Direct Sequence Spread Spectrum) parameter set, high-throughput (HT) operating element, very high-throughput (VHT) operating element, high-efficiency (HE) operating element,

extremely high-throughput (EHT) operating element, wide bandwidth channel switching element, operating mode notification element, broadcast Target Wait Time (TWT) element, BSS color change notification element, multi-user (MU) EDCA parameter set, space reuse parameter set , or an uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter set.

FIG. 15 shows a flow diagram illustrating an example process 1500 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1500 may be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG. 5 . In some implementations, process 1500 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1500 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7A.

In various implementations, process 1500 may be performed after transmitting the frame at block 1304 of FIG. 13. For example, at block 1502, process 1500 begins by receiving updates to one or more BSS parameters associated with a non-primary link. At block 1504, process 1500 continues sending one or more updated BSS parameters associated with the non-primary link only on the primary link. In some implementations, one or more updated BSS parameters may be carried in a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other implementations, one or more updated BSS parameters may be part of a partial profile of a non-primary link. In some cases, the NSTR softAP MLD may transmit a spontaneous broadcast probe response frame on the primary link that carries a partial profile of the non-primary link (and thus indicates one or more updated BSS parameters of the non-primary link).

FIG. 16 shows a flow diagram illustrating an example process 1600 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1600 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5. In some implementations, process 1600 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1600 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 1600 begins at block 1602 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link. At block 1604, process 1600 continues determining that the non-primary link is not available. At block 1606, process 1600 continues transmitting a frame only on the primary link carrying an indication of the unavailability of the non-primary link. In some cases, the frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other cases, the frame may be an action frame, such as a notification frame.

Non-default links may not be available for a variety of reasons. For example, if a non-primary link is used for a cellular link in a Long Term Evolution (LTE) Radio Access Network (RAN) or a 5th Generation (5G) New Radio (NR) access network, the non-primary link is associated with the NSTR softAP MLD. May not be available for multi-link communication. Another example is when the non-primary link is in a power saving mode (including sleep mode or doze mode) to reduce power consumption or extend the battery life of the NSTR softAP MLD. , non-primary links may not be available for multi-link communication associated with the NSTR softAP MLD. As another example, if the non-primary link is used for peer-to-peer (P2P) or infrastructure STA communications, the non-primary link may not be available for multi-link communications associated with the NSTR softAP MLD.

FIG. 17 shows a flow diagram illustrating an example process 1700 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1700 may be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG. 5 . In some implementations, process 1700 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1700 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 1700 may be performed in conjunction with sending an indication at block 1606 of FIG. 16 . For example, at block 1702, process 1700 begins by setting the do not transmit (DNT) bit to a value of 1 based on the unavailability of the non-primary link. In some cases, the DNT bit may be carried in the STA-specific profile sub-element or RNR element of a frame transmitted on the primary link. In some other implementations, the NSTR softAP MLD may set the Critical Update Flag (CUF) carried in the frame to a value of 1 based on the unavailability of the non-primary link. In some cases, the frame includes a capability information field carrying a CUF set to a value of 1.

FIG. 18 shows a flow diagram illustrating an example process 1800 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1800 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5. In some implementations, process 1800 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1800 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 1800 may be performed after transmitting the frame carrying the indication at block 1606 of FIG. 16. For example, at block 1802, process 1800 begins with operating as a single link device on the primary link based on the unavailability of the non-primary link. In some aspects, when a non-primary link is not available, the NSTR softAP MLD keeps the softAP (or other transmit chain, receive chain, signaling circuitry, etc.) associated with the non-primary link fully operational on the primary link. You can put it in sleep state, doze state, or power off state. In this single link state, NSTR softAP MLD allows the BSS to operate as a single link BSS on the primary link while also reducing the power consumption associated with operation on the non-primary link.

FIG. 19 shows a flow diagram illustrating an example process 1900 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 1900 may be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG. 5 . In some implementations, process 1900 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 1900 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 1900 may be performed at block 1802 of FIG. 18 while the NSTR softAP MLD is operating as a single link device. For example, at block 1902, process 1900 begins by determining that a non-primary link is available while operating as a single link device on the primary link. At block 1904, process 1900 continues to reset the do not transmit (DNT) bit to a value of 0 based on the availability of the non-primary link. At block 1906, process 1900 continues transmitting the reset DNT bit in other frames only on the primary link, and the other frames carry the reset DNT bit with a value of 0 in the STA-specific profile sub-element or reduced neighbor. Includes reporting (RNR) elements. In some cases, the other frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other cases, the other frame may be an action frame, such as a notification frame.

FIG. 20 shows a flow diagram illustrating an example process 2000 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2000 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2000 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2000 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2000 may be performed after process 1600 of FIG. 16. For example, at block 2002, process 2000 begins by determining that a non-primary link is available after transmitting an indication. At block 2004, process 2000 continues sending an indication of the availability of the non-primary link only on the primary link. At block 2006, process 2000 continues operating as a multi-link device on the primary link and the non-primary link based on the availability of the non-primary link. In some cases, the indication may be transmitted on the underlying link in an appropriate management frame, such as, but not limited to, a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other cases, an indication may be sent on the underlying link in an appropriate action frame, such as a notification frame. In some aspects, the NSTR softAP MLD may power on the softAP associated with the non-primary link when the non-primary link becomes available (or within a configured time). In this multi-link state, NSTR softAP MLD can operate BSS on both primary and non-primary links.

FIG. 21 shows a flow diagram illustrating an example process 2100 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2100 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2100 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2100 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2100 may be performed after determining the unavailability of the non-primary link at block 1604 of FIG. 16. For example, at block 2102, process 2100 begins by disabling the non-primary link or placing the non-primary link in a sleep state based on the unavailability of the non-primary link. In some cases, the NSTR softAP MLD may also place a softAP (or other transmit chain, receive chain, signaling circuit, etc.) associated with a non-primary link into a sleep state, doze state, or power-on while remaining fully operational on the primary link. You can also leave it off. In this way, NSTR softAP MLD can reduce the power consumption associated with operation on non-primary links and also reduce cross-link interference caused by UL transmission on non-primary links.

FIG. 22 shows a flow diagram illustrating an example process 2200 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2200 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2200 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2200 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2200 may be one implementation of deactivating a non-default link at block 2102 of FIG. 21 . For example, at block 2202, process 2200 begins by removing a non-default link from the multiple link context associated with the NSTR softAP MLD. In some cases, when a non-primary link is removed from a multi-link context, a wireless communication device associated with an NSTR softAP MLD may not be able to access or utilize the non-primary link. In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that the non-primary link is no longer included in the multi-link context.

FIG. 23 shows a flow diagram illustrating an example process 2300 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2300 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2300 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2300 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2300 may be performed after removing the non-primary link from the multiple link context at block 2202 of FIG. 22. For example, at block 2302, process 2300 begins by removing the non-primary link from the multi-link context and then determining that the non-primary link is available. At block 2304, process 2300 continues adding the non-primary link to the multi-link context based on the availability of the non-primary link. In some cases, a wireless communication device associated with an NSTR softAP MLD may access and utilize the non-primary link without disassociating or re-associating with the NSTR softAP MLD once the non-primary link is added to the multi-link context. You can. In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that a non-primary link has been added to the multi-link context.

FIG. 24 shows a flow diagram illustrating an example process 2400 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2400 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2400 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2400 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2400 may be another implementation that deactivates the non-default link at block 2102 of FIG. 21 . For example, at block 2402, process 2400 begins by remapping a traffic identifier (TID) from a non-primary link to a primary link. For example, a primary link may be associated or associated with a first TID value initially representative of a first type or flow of traffic, and a non-primary link may be associated with a second TID value initially representative of a second type or flow of traffic. may be related to or related to. When the non-default link is unavailable, NSTR softAP MLD can remap the secondary TID value from the non-default link to the default link. In this way, the traffic type or flow indicated by the second TID value can be carried on the primary link (rather than the non-primary link). In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that the TID associated with the non-primary link has been remapped to the primary link.

FIG. 25 shows a flow diagram illustrating an example process 2500 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2500 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2500 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2500 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2500 may be performed after remapping the TID from the non-primary link to the primary link at block 2402 in FIG. 24. For example, at block 2502, process 2500 begins by determining that a non-primary link is available after deactivating the non-primary link. At block 2504, process 2500 continues remapping TIDs from the primary link to the non-primary link based on the availability of the non-primary link. Continuing the example described with reference to FIG. 24, when a non-default link becomes available, the NSTR softAP MLD may remap the second TID value from the default link to the non-default link. In this way, communication of the traffic type or flow indicated by the second TID value may be returned to the non-primary link. In some aspects, the NSTR softAP MLD may send a notification frame on the primary link to indicate that some TIDs associated with the primary link have been remapped to a non-primary link.

FIG. 26 shows a flow diagram illustrating an example process 2600 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2600 may be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG. 5 . In some implementations, process 2600 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2600 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7B.

In some implementations, process 2600 may be performed after transmitting the frame at block 1606 of FIG. 16. For example, at block 2602, process 2600 begins by switching a primary link from a first channel to a second channel while simultaneously switching a non-primary link from a second channel to a first channel. In some cases, the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.

FIG. 27 shows a flow diagram illustrating an example process 2700 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2700 may be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG. 5 . In some implementations, process 2700 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2700 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 8A.

In some implementations, process 2700 begins at block 2702 with receiving a ready to send (RTS) frame from the STA MLD on the primary link. At block 2704, process 2700 continues transmitting a transportable (CTS) frame to the STA MLD on the primary and non-primary links based on receiving the RTS frame. At block 2706, process 2700 continues receiving one or more uplink (UL) physical layer protocol data units (PPDUs) from the STA MLD on the primary and non-primary links. In some cases, the NSTR softAP MLD can indicate the availability of a non-primary link by sending a CTS frame on both the primary and non-primary links. If the STA MLD receives a CTS frame on both the default link and the non-default link, the STA MLD can transmit UL data on both the default link and the non-default link. Conversely, if the STA MLD receives a CTS frame only on the basic link, the STA MLD can transmit UL data to the NSTR softAP MLD only on the basic link.

FIG. 28 shows a flow diagram illustrating an example process 2800 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2800 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2800 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2800 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 8B.

In some implementations, the process 2800 begins at block 2802 with receiving a first frame only on the primary link from the NSTR softAP MLD associated with the primary link and the non-primary link. The first frame may include the entire profile of the basic link and MLD information common to the basic link and non-basic link. The full profile may include at least beacon interval, capability information, SSID, supported speed, TSF value, and one or more additional fields or elements associated with discovery of the primary link. At block 2804, process 2800 continues sending a second frame to the NSTR softAP MLD on the primary link only, the second frame requesting the full profile of the non-primary link. At block 2806, process 2800 continues receiving a third frame from the NSTR softAP MLD on the primary link only, where the third frame represents the full profile of the non-primary link. In some cases, the first frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. The second frame may be one of a probe request frame, an association request frame, or a reassociation request frame. The third frame may be one of a probe response frame, an association response frame, or a reassociation response frame.

In some implementations, the first frame includes a frame body that includes a ML element comprised of MLD common information and includes a plurality of fields and elements carrying the entire profile of the underlying link. The third frame may include a frame body including an ML element carrying STA-specific profile sub-elements indicating the entire profile of the non-basic link. The body of the third frame may also include an RNR element carrying a neighbor AP information field associated with the non-primary link. The Neighbor AP Information field may carry a TBTT Information field consisting of the BSSID and one or more MLD parameters of the non-primary link. In some cases, the non-basic link's TBTT offset, short-SSID, BSS parameters, and PSD parameters may be inherited from the primary link. Accordingly, the TBTT offset subfield, short-SSID subfield, BSS parameters subfield, and PSD subfield can be omitted from the TBTT information field in the adjacent AP information field associated with the non-primary link, thereby reducing the size of the RNR element and Overhead is reduced. In some aspects, the length of the TBTT information field is 9 octets.

FIG. 29 shows a flow diagram illustrating an example process 2900 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 2900 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 2900 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 2900 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 7A.

In some implementations, process 2900 begins at block 2902 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link. At block 2904, process 2900 continues transmitting only the primary link a frame that includes one or more timing parameters associated with the primary link, wherein the timing parameters of the non-primary link are based on the one or more timing parameters associated with the primary link. It is done. In some aspects, the timing parameters of a non-basic link are inherited from the primary link. The frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In some cases, the primary link is associated with a target beacon transmission time (TBTT), and the non-primary link may be a pseudo-BSS aligned with the primary link's TBTT. The one or more timing parameters may include at least one of a channel change notification, a dead period, or a beacon interval.

FIG. 30 shows a flow diagram illustrating an example process 3000 for wireless communication with an NSTR softAP MLD, according to some implementations. Process 3000 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3000 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3000 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9A.

In some implementations, process 3000 begins at block 3002 operating as an NSTR softAP MLD associated with a primary link and a non-primary link. At block 3004, process 3000 continues to obtain channel access on the primary link. At block 3006, process 3000 continues transmitting the first frame on the primary link to the first associated STA. At block 3008, process 3000 continues putting the non-primary link into a deaf state for the duration of transmitting frames on the primary link. At block 3010, process 3000 continues restoring the non-primary link from the hearing loss condition after frame transmission on the primary link has ended. In some implementations, the frame can be any suitable frame, including but not limited to a management frame, control frame, or data frame.

FIG. 31 shows a flow diagram illustrating an example process 3100 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 3100 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3100 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3100 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9A.

In some implementations, process 3100 may be performed after repairing the non-primary link at block 3010 of FIG. 30. For example, at block 3102, process 3100 begins with obtaining channel access on a non-primary link based on channel access on the primary link. At block 3104, process 3100 continues transmitting the second frame on the non-primary link to the second associated STA while simultaneously transmitting the third frame on the primary link to the first associated STA. In some implementations, the NSTR softAP MLD can synchronize transmission of the second frame on the non-primary link with transmission of the third frame on the primary link. In some cases, the first associated STA is a legacy device configured to operate in accordance with an earlier revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and the second associated STA is a legacy device configured to operate in accordance with the IEEE 802.11be or later revision to the 802.11 family of wireless communications standards. It is a non-legacy device configured to operate according to a revision of .

FIG. 32 shows a flow diagram illustrating an example process 3200 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 3200 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3200 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3200 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9A.

In some implementations, process 3200 may be performed after restoring the non-primary link at block 3010 of FIG. 30. For example, at block 3202, process 3200 begins with obtaining channel access on a non-primary link while at least a portion of the channel access is obtained on the primary link. At block 3204, process 3200 continues transmitting the second frame to the one or more second associated STAs on the non-primary link while transmitting the first frame on the primary link.

Figure 33 shows a flow diagram illustrating an example process 3300 for wireless communication with an NSTR softAP MLD, according to some implementations. Process 3300 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3300 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3300 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9B.

In some implementations, process 3300 begins at block 3302 with operating as an NSTR softAP MLD associated with a primary link and a non-primary link. At block 3304, process 3300 continues to obtain channel access to the primary link and the non-primary link. At block 3306, process 3300 continues establishing adjusted target latency (TWT) sessions on the primary and non-primary links. At block 3308, process 3300 continues with transmitting a first trigger frame on the primary link, where the first trigger frame requests uplink (UL) transmission from a first STA group on the primary link. At block 3310, process 3300 simultaneously transmits the first trigger frame on the primary link and sends a second trigger frame requesting uplink (UL) transmission from the second STA group on the non-primary link. Proceed with transmission. In some cases, the coordinated TWT session is one or more respective service periods (SPs) in which the corresponding STA or corresponding STA group can be scheduled or triggered for UL transmission on the respective primary and non-primary links. It can be included.

Figure 34 shows a flow diagram illustrating an example process 3400 for wireless communication with an NSTR softAP MLD, according to some implementations. Process 3400 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3400 may be performed by a wireless communication device operating as or within an STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3400 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9B.

In some implementations, process 3400 may be performed after transmitting the frame at blocks 3308 and 3310 of FIG. 33 . For example, the process 3400 may begin with receiving one or more first UL PPDUs on the primary link from a first STA group based on a first trigger frame at block 3402. At block 3404, process 3400 continues to receive one or more second UL PPDUs on the non-primary link from the second STA group based on the second trigger frame. In some cases, transmission of the first and second UL PPDUs from each first and second STA group may be synchronized with each other.

Figure 35 shows a flow diagram illustrating an example process 3500 for wireless communication with an NSTR softAP MLD, according to some implementations. Process 3500 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3500 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3500 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9B.

In some implementations, process 3500 may be performed after process 3300 of FIG. 33. For example, process 3500 may begin at block 3502 by synchronizing one or more TWT service periods on a non-primary link with one or more respective TWT service periods on a primary link. In this way, the transmission of one or more first UL PPDUs by a first STA group on the primary link may be temporally aligned with the transmission of one or more second UL PPDUs by a second STA group on the non-primary link. .

Figure 36 shows a flow diagram illustrating an example process 3600 for wireless communication supporting multi-link communication with an NSTR softAP MLD, according to some implementations. Process 3600 may be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG. 5 . In some implementations, process 3600 may be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIGS. 1 and 6B, respectively. there is. In some cases, process 3600 may be performed by an AP MLD, such as the NSTR softAP MLD described with reference to FIG. 9B.

In some implementations, process 3600 may be performed after receiving one or more first and second UL PPDUs at blocks 3402 and 3404 of FIG. 34 . For example, process 3600 may begin at block 3602 by transmitting one or more first downlink (DL) PPDUs on the primary link to the first STA group. At block 3604, process 3600 continues transmitting one or more first DL PPDUs to the first STA group on the primary link while concurrently transmitting one or more second DL PPDUs to the second STA group on the non-primary link. .

Figure 37 shows a block diagram of an example wireless communication device 3700 in accordance with some implementations. In some implementations, wireless communication device 3700 is configured to perform communication 700 in FIG. 7A, communication 710 in FIG. 7B, or communication 810 in FIG. 8A. Wireless communication device 3700 may be an example implementation of wireless communication device 500 described above with reference to FIG. 5 . For example, wireless communication device 3700 may be a chip, SoC, chipset, package, or device that includes at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem). You can. In some implementations, wireless communication device 3700 may be a device for use in a STA, such as one of STAs 104 and 604 described with reference to FIGS. 1 and 6B. In some other implementations, wireless communication device 3700 may be an STA that includes such a chip, SoC, chipset, package or device as well as at least one antenna (e.g., antenna 625 in FIG. 6B). In various implementations, wireless communication device 3700 may be an example of one or more of the NSTR SoftAP MLDs described herein.

Wireless communication device 3700 includes a receiving component 3710, a communication manager 3720, and a transmitting component 3730. Communications manager 3720 includes a channel access component 3721, a frame creation component 3722, a link profile component 3723, a link availability component 3724, a parameter update component 3725, and a timing and synchronization component 3726. Includes more. Portions of one or more of the components may be implemented, at least in part, in hardware or firmware. In some implementations, at least some of the components 3721, 3722, 3723, 3724, 3725, 3726 are implemented, at least in part, in software stored in memory (e.g., memory 508 in FIG. 5). For example, a portion of one or more of the components 3721, 3722, 3723, 3724, 3725, and 3726 may be connected to a processor (e.g., processor 506 in FIG. 5) to perform the function or operation of each component. It can be implemented as non-transitory instructions (or “code”) executable by

Receive component 3710 is configured to receive RX signals from other wireless communication devices over one or more wireless channels or links. Communication manager 3720 is configured to control or manage communication with the other wireless communication devices. In some implementations, channel access component 3721 competes for and obtains channel access on a primary and/or non-primary link associated with wireless communication device 3700. Frame generation component 3722 is configured to transmit discovery information, profile information, operating parameters, updates to operating parameters, link availability, link timing criteria, and other appropriate information related to MLD operating on primary and non-primary links. Create a frame. Link profile component 3723 creates a full profile or a partial profile for one or more of the basic links and non-basic links. Link availability component 3724 indicates whether the primary link and/or non-primary link is available. Parameter update component 3725 determines changes to one or more parameters of primary and non-basic links and transmits an indication of the parameter update. Timing and synchronization component 3726 generates timing references for non-primary links relative to the primary link.

Transmission component 3730 is configured to transmit the TX signal to one or more other wireless communication devices over a wireless channel. In some implementations, transmit component 3730 is capable of transmitting discovery information, profile information, operating parameters, updates to operating parameters, link availability, link timing criteria, and primary and non-primary links associated with wireless communication device 3700. Frames may be transmitted containing or displaying other appropriate information related to the.

FIG. 38 shows a block diagram of another example wireless communication device 3800 in accordance with some implementations. In some implementations, wireless communication device 3800 is configured to perform communication 810 of FIG. 8B. Wireless communication device 3800 may be an example implementation of wireless communication device 500 described above with reference to FIG. 5 . For example, wireless communication device 3800 may be a chip, SoC, chipset, package, or device that includes at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem). You can. In some implementations, wireless communication device 3800 may be a device for use in a STA, such as one of STAs 104 and 604 described with reference to FIGS. 1 and 6B. In some other implementations, wireless communication device 3800 may be an STA that includes such a chip, SoC, chipset, package or device as well as at least one antenna (e.g., antenna 625 in FIG. 6B). In various implementations, wireless communication device 3800 may be an example of one or more of the NSTR SoftAP MLDs described herein.

Wireless communication device 3800 includes a receiving component 3810, a communication manager 3820, and a transmitting component 3830. Communication manager 3820 further includes a channel access component 3821, a frame creation component 3822, and a profile request component 3823. Portions of one or more of the components may be implemented, at least in part, in hardware or firmware. In some implementations, at least some of components 3821, 3822, 3823 are implemented, at least in part, in software stored in memory (e.g., memory 508). For example, portions of one or more of components 3821, 3822, or 3823 may include non-transitory instructions (or can be implemented as "code").

Receive component 3810 is configured to receive RX signals from other wireless communication devices over one or more wireless channels or links. Communication manager 3820 is configured to control or manage communication with the other wireless communication devices. In some implementations, channel access component 3821 acquires channel access by competing for channel access on a primary link and/or non-primary link associated with an AP MLD, such as an NSTR softAP MLD. Frame generation component 3822 generates frames to convey performance and operating parameters of wireless communication device 3800. Profile request component 3823 creates a request to the AP MLD to provide a full profile or a partial profile of one or more of basic links and non-default links.

Transmit component 3830 is configured to transmit the TX signal to one or more other wireless communication devices over a wireless channel. In some implementations, transmit component 3830 may transmit a frame that includes or indicates capabilities, operating parameters, profile request, and other appropriate information related to primary and non-primary links associated with the AP MLD.

Implementations are described in the numbered sections below.

One. A wireless communication method using a wireless station (STA),

Operating as a non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) comprising a first access point (AP) associated with a primary link and a second AP associated with a non-primary link; and

transmitting a frame only on a primary link, wherein the frame includes a full profile of the primary link and represents a full profile of the non-primary link, wherein each full profile of the primary link and the non-primary link includes at least beacon interval, capability information, transmitting the frame, each comprising a service set identifier (SSID), a supported rate, a timing synchronization function (TSF) value, and one or more additional fields or elements associated with discovery of the respective link. Wireless communication method.

2. The method of item 1, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

3. The method of any one or more of items 1 to 2, wherein the beacon interval, SSID, and TSF values of the non-basic link are inherited from the primary link.

4. The method of any one or more of items 1 to 3, wherein the frame comprises a frame body, and the frame body comprises:

A plurality of fields and elements that return the entire profile of the primary link; and

A method of wireless communication by a wireless station, comprising a Multiple Link (ML) element carrying STA-specific profile sub-elements representing the overall profile of the non-basic link.

5. The wireless communication by a wireless station of item 4, wherein the ML element further comprises a common information field carrying a basic service set (BSS) parameter change count (BPCC) value indicating an update to one or more BSS parameters associated with the underlying link. method.

6. The wireless communication by a wireless station according to any one or more of items 4 to 5, wherein one or more bits of the multi-link control field or common information field of the ML element indicate whether the frame is transmitted from the first AP of the NSTR softAP MLD. method.

7. The method of any one or more of items 4 through 6, wherein the frame body further comprises a reduced neighbor reporting (RNR) element comprising a neighbor AP information field associated with a non-default link, wherein the neighbor AP information field is a basic service set A method of wireless communication by a wireless station, comprising a Target Beacon Transmission Time (TBTT) information field consisting of an identification (BSSID) and one or more MLD parameters of a non-primary link.

8. The method of item 7, wherein the TBTT offset subfield, short-SSID subfield, BSS parameters subfield, and Power Spectral Density (PSD) subfield are not present in the TBTT information field corresponding to the non-basic link. Method of communication.

9. The wireless communication by a wireless station of any one or more of items 7 through 8, wherein the neighbor AP information field includes a TBTT information field type set to a value indicating that the neighbor AP information field carries information related only to a non-primary link. method.

10. The method of item 9, wherein the TBTT information field type is set to 1 or a reserved value.

11. The method of any one or more of items 7 to 10, wherein the length of the TBTT information field indicates whether a frame is transmitted from the first AP of the NSTR softAP MLD.

12. The method of any one or more of items 7 to 11, wherein the length of the TBTT information field is 9 octets.

13. The method of any one or more of items 7 through 12, wherein the one or more MLD parameters carried in the TBTT information field are a basic service set (BSS) parameter change count (BPCC) indicating an update to one or more BSS parameters associated with the non-primary link. A method of wireless communication by a wireless station, including a value.

14. In item 13,

Receiving an update to at least one of the BSS parameters associated with the non-primary link;

Incrementing the value of the Basic Service Set (BSS) Parameter Change Count (BPCC) field of the Target Beacon Transmission Time (TBTT) information field included in the Reduced Neighbor Reporting (RNR) element of another frame based on the received update;

setting a critical update flag (CUF) in the capability information field of another frame based on incrementing the value of the BPCC field; and

Transmitting another frame only on a primary link, wherein the other frame represents an update to at least one BSS parameter associated with a non-primary link.

15. In Item 13, the BSS parameters include Channel Switch Alert (CSA) elements, Extended Channel Switch Alert (eCSA) elements, Enhanced Distributed Channel Access (EDCA) parameters, Quiet Period elements, and Direct Sequence Spread Spectrum (DSSS). Parameter set, high-throughput (HT) operating element, very high-throughput (VHT) operating element, high-efficiency (HE) operating element, extremely high-throughput (EHT) operating element, wide bandwidth channel switching element, operating mode notification element, broadcast target wait time (TWT) element, BSS color change notification element, multi-user (MU) EDCA parameter set, spatial reuse parameter set, or uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) element. ) A wireless communication method by a wireless station, comprising at least one of the parameter sets.

16. In any one or more of items 1 to 15,

Receiving updates to one or more basic service set (BSS) parameters associated with a non-primary link; and

A method of wireless communication by a wireless station, further comprising transmitting one or more updated BSS parameters associated with a non-primary link only on the primary link.

17. The method of item 16, wherein the one or more updated BSS parameters are part of a partial profile of a non-basic link.

18. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code;

The processor-readable code, when executed by at least one processor in conjunction with at least one modem,

Operates as a non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) including a first access point (AP) associated with a primary link and a second AP associated with a non-primary link; and

configured to transmit a frame only on a primary link, wherein the frame includes a full profile of the primary link and represents a full profile of a non-primary link, and each full profile of the primary link and the non-primary link includes at least beacon interval, capability information, A wireless communication device, each comprising a service set identifier (SSID), a supported rate, a timing synchronization function (TSF) value, and one or more additional fields or elements associated with discovery of the respective link.

19. The wireless communications device of item 18, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

20. The wireless communication device of any one or more of items 18-19, wherein the beacon interval, SSID, and TSF values of the non-primary link are inherited from the primary link.

21. The method of any one or more of items 18 to 20, wherein the frame comprises a frame body, the frame body comprising:

A plurality of fields and elements that return the entire profile of the primary link; and

A wireless communication device comprising a Multiple Link (ML) element carrying STA-specific profile sub-elements representing an overall profile of a non-primary link.

22. The wireless communication device of item 21, wherein the ML element further comprises a common information field carrying a basic service set (BSS) parameter change count (BPCC) value indicating an update to one or more BSS parameters associated with the underlying link.

23. The wireless communication device of any one or more of items 21-22, wherein one or more bits of the multi-link control field or common information field of the ML element indicate whether the frame is transmitted from the first AP of the NSTR softAP MLD.

24. The method of any one or more of items 21 to 23, wherein the frame body further comprises a reduced neighbor reporting (RNR) element comprising a neighbor AP information field associated with a non-default link, wherein the neighbor AP information field is: A wireless communication device comprising a Target Beacon Transmission Time (TBTT) information field consisting of an identification (BSSID) and one or more MLD parameters of a non-primary link.

25. The wireless communication device of item 24, wherein the TBTT information field corresponding to the non-basic link does not include a TBTT offset subfield, a short-SSID subfield, a BSS parameters subfield, and a power spectral density (PSD) subfield.

26. The wireless communication device of any one or more of items 24-25, wherein the neighbor AP information field includes a TBTT information field type set to a reserved value indicating that the neighbor AP information field carries information related only to a non-primary link. .

27. The wireless communication device of any one or more of items 24-26, wherein the length of the TBTT information field indicates whether the frame is transmitted from the first AP in the NSTR softAP MLD.

28. The method of item 24, wherein the one or more MLD parameters carried in the TBTT information field include a basic service set (BSS) parameter change count (BPCC) value indicating an update to one or more BSS parameters associated with the non-default link. device.

29. The method of item 28, wherein execution of the processor-readable code comprises:

receive updates to at least one of the BSS parameters associated with the non-primary link;

Increment the value of the Basic Service Set (BSS) Parameter Change Count (BPCC) field of the Target Beacon Transmission Time (TBTT) information field included in the Reduced Neighbor Reporting (RNR) element of another frame based on the received update;

Set a critical update flag (CUF) in the capability information field of another frame based on incrementing the value of the BPCC field; and

The wireless communication device further configured to transmit another frame only on a primary link, wherein the other frame represents an update to at least one BSS parameter associated with the non-primary link.

30. The method of any one or more of items 18-29, wherein executing the processor-readable code comprises:

receive updates to one or more basic service set (BSS) parameters associated with the non-primary link; and

The wireless communication device further configured to transmit one or more updated BSS parameters associated with a non-primary link only on a primary link.

31. A wireless communication method using a wireless station (STA),

Operating as a non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) comprising a first access point (AP) associated with a primary link and a second AP associated with a non-primary link;

determining that the non-default link is not available; and

A method of wireless communication by a wireless station, comprising transmitting a frame only on a primary link carrying an indication of unavailability of the non-primary link.

32. The method of item 31, wherein the frame includes one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame.

33. The method of any one or more of items 31 to 32, wherein the frame includes a per-STA profile sub-element or reduced neighbor reporting (RNR) element carrying a do not transmit (DNT) bit set to a value of 1, and A method of wireless communication by a wireless station wherein a set DNT bit indicates unavailability of a non-primary link.

34. The radio station of any one of items 31 to 33, wherein the frame includes a capability information field carrying a critical update flag (CUF), wherein the CUF is set to a value of 1 based on unavailability of the non-primary link. Wireless communication method by.

35. In any one or more of items 31 to 34,

A method of wireless communication by a wireless station, further comprising operating as a single link device on a primary link based on unavailability of the non-primary link.

36. In item 35,

determining that a non-primary link is available while operating as a single link device on the primary link;

resetting the do not transmit (DNT) bit to a value of 0 based on the availability of the non-primary link; and

Further comprising transmitting the reset DNT bit in another frame only on the primary link, wherein the other frame includes a per-STA profile sub-element or reduced neighbor reporting (RNR) element carrying the reset DNT bit with a value of 0. A wireless communication method using a wireless station.

37. In any one or more of items 31 to 36,

determining that a non-default link is available after sending the indication;

transmitting an indication of availability of a non-primary link only on the primary link; and

A method of wireless communication by a wireless station, further comprising operating as a multi-link device on primary and non-primary links based on availability of the non-primary link.

38. The method of any one or more of items 31 to 36, further comprising deactivating the non-primary link or placing the non-primary link in a power saving state based on unavailability of the non-primary link. .

39. The method of item 38, wherein deactivating the non-primary link includes removing the non-primary link from a multiple link context associated with the NSTR softAP MLD.

40. In item 39,

determining that the non-primary link is available after removing the non-primary link from the multi-link context; and

A method of wireless communication by a wireless station, further comprising adding a non-primary link to the multi-link context based on availability of the non-primary link.

41. The method of item 38, wherein deactivating the non-primary link includes remapping a traffic identifier (TID) from the non-primary link to the primary link.

42. In item 41,

determining that the non-default link is available after deactivating the non-default link; and

A method of wireless communication by a wireless station, further comprising remapping a TID from a primary link to a non-primary link based on availability of the non-primary link.

43. In any one or more of items 31 to 42,

Receiving a ready to send (RTS) frame from the STA MLD on the primary link;

transmitting a transmittable (CTS) frame to the STA MLD on the primary link and the non-basic link based on receiving the RTS frame; and

A method of wireless communication by a wireless station, further comprising receiving one or more uplink (UL) physical layer protocol data units (PPDUs) from the STA MLD on a primary link and a non-basic link.

44. In any one or more of items 31 to 42,

A method of wireless communication by a wireless station, further comprising switching a basic link from a first channel to a second channel simultaneously with switching a non-basic link from a second channel to a first channel.

45. The method of item 44, wherein the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.

46. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code;

The processor-readable code, when executed by at least one processor in conjunction with at least one modem,

Operates as a non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) including a first access point (AP) associated with a primary link and a second AP associated with a non-primary link;

determine that the non-default link is not available; and

A wireless communication device configured to transmit only on a primary link a frame carrying an indication of unavailability of the non-primary link.

47. The wireless communication device of item 46, wherein the frame includes one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame.

48. The method of any one or more of items 46 to 47, wherein the frame includes a per-STA profile sub-element or reduced neighbor reporting (RNR) element carrying a do not transmit (DNT) bit set to a value of 1, and A wireless communications device wherein a set DNT bit indicates unavailability of a non-primary link.

49. The wireless device of any one or more of items 46-47, wherein the frame includes a capability information field carrying a critical update flag (CUF), wherein the CUF is set to a value of 1 based on unavailability of the non-primary link. Communication device.

50. The method of any one or more of items 46 through 49, wherein executing the processor readable code comprises:

A wireless communication device further configured to operate as a single link device on a primary link based on unavailability of the non-primary link.

51. The method of item 50, wherein execution of the processor-readable code comprises:

determine that a non-primary link is available while operating as a single link device on the primary link;

reset the do not transmit (DNT) bit to a value of 0 based on the availability of the non-primary link; and

further configured to transmit reset DNT bits in other frames only on the primary link, wherein the other frames include a per-STA profile sub-element or reduced neighbor reporting (RNR) element carrying reset DNT bits with a value of 0, Wireless communication device.

52. The method of any one or more of items 46-51, wherein executing the processor-readable code comprises:

After sending the indication, determine that a non-primary link is available;

send an indication of the availability of the non-primary link only on the primary link; and

The wireless communication device further configured to operate as a multi-link device on primary and non-primary links based on availability of non-primary links.

53. The wireless device of any one or more of items 46-52, wherein execution of the processor readable code is further configured to disable the non-primary link or place the non-primary link in a sleep state based on unavailability of the non-primary link. Communication device.

54. The wireless communication device of item 53, wherein deactivating the non-primary link includes removing the non-primary link from a multiple link context associated with the NSTR softAP MLD.

55. The method of item 54, wherein execution of the processor-readable code comprises:

determine that the non-primary link is available after removing the non-primary link in the multi-link context; and

The wireless communication device further configured to add a non-primary link to the multi-link context based on availability of the non-primary link.

56. The wireless communications device of item 53, wherein deactivating the non-primary link includes remapping a traffic identifier (TID) from the non-primary link to the primary link.

57. The method of item 56, wherein executing the processor-readable code comprises:

determine that the non-default link is available after disabling the non-default link; and

The wireless communication device further configured to remap the TID from the primary link to the non-primary link based on the availability of the non-primary link.

58. The method of any one or more of items 46-57, wherein executing the processor-readable code comprises:

Receive a Ready to Send (RTS) frame from the STA MLD on the primary link;

transmit a transmittable (CTS) frame to the STA MLD on the primary link and the non-primary link based on receiving the RTS frame; and

The wireless communication device further configured to receive one or more uplink (UL) physical layer protocol data units (PPDUs) from the STA MLD on a primary link and a non-basic link.

59. The method of any one or more of items 46 through 58, wherein executing the processor readable code comprises:

A wireless communication device further configured to switch a primary link from a first channel to a second channel while simultaneously switching a non-primary link from a second channel to a first channel.

60. The wireless communications device of item 59, wherein the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band.

61. A wireless communication method using a wireless station (STA),

Receiving a first frame only on the primary link from a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with the primary link and the non-primary link, wherein the first frame is on the primary link. Containing a full profile and MLD information common to primary and non-primary links, the full profile includes at least beacon interval, capability information, service set identifier (SSID), supported speed, timing synchronization function (TSF) value, and primary link receiving the first frame only on a primary link, the first frame comprising one or more additional fields or elements associated with the discovery of;

transmitting a second frame requesting the full profile of the non-primary link to the NSTR softAP MLD only on the primary link; and

A method of wireless communication by a wireless station, comprising receiving a third frame representing the entire profile of the non-basic link from the NSTR softAP MLD on the primary link only.

62. The method of item 61, wherein the first frame is a beacon frame, the second frame is a probe request frame, and the third frame is a probe response frame.

63. The method of any one or more of items 61 to 62, wherein the first frame includes a frame body that carries a full profile of the underlying link and includes a multi-link (ML) element comprised of MLD common information. method.

64. In item 63, the MLD common information includes an MLD media access control (MAC) address field, a link ID information field, a basic service set (BSS) parameter change count (BPCC) field, a synchronization delay field, and an enhanced multi-link (EML) capability field. , and a MLD capability field.

65. The method of item 64, wherein the BPCC field indicates an update to one or more BSS parameters associated with the primary link.

66. The method of any one or more of items 64 to 65, wherein the ML element of the first frame does not have link information of a non-basic link.

67. The method of any one or more of items 61 to 66, wherein the third frame includes a frame body containing a multi-link (ML) element carrying STA-specific profile sub-elements representing an overall profile of the non-basic link. wireless communication method.

68. Item 67, wherein the frame body further includes a reduced neighbor reporting (RNR) element carrying a neighbor AP information field associated with the non-primary link, wherein the neighbor AP information field includes a basic service set identification (BSSID) and a non-default link. A method of wireless communication by a wireless station carrying a Target Beacon Transmission Time (TBTT) information field consisting of one or more MLD parameters of an underlying link.

69. The method of item 68, wherein the TBTT offset subfield, short-SSID subfield, BSS parameters subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-basic link. Method of communication.

70. The method of any one or more of items 61 to 69, wherein the beacon interval, SSID, and TSF values of the non-primary link are inherited from the primary link.

71. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code, wherein the processor-readable code, when executed by the at least one processor in conjunction with the at least one modem:

Receiving a first frame only on the primary link from a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with the primary link and the non-primary link, wherein the first frame is transmitted across the primary link. The profile includes MLD information common to the primary link and the non-primary link, and the full profile includes at least beacon intervals, capability information, service set identifier (SSID), supported speed, timing synchronization function (TSF) value, and receive the first frame only on a primary link, including one or more additional fields or elements associated with discovery;

send a second frame requesting the full profile of the non-primary link to the NSTR softAP MLD only on the primary link;

A wireless communication device configured to receive a third frame representing the entire profile of the non-primary link from the NSTR softAP MLD only on the primary link.

72. The wireless communication device of item 71, wherein the first frame is a beacon frame, the second frame is a probe request frame, and the third frame is a probe response frame.

73. The wireless communications device of any one or more of items 71-72, wherein the first frame includes a frame body that carries a full profile of the underlying link and includes a multiple link (ML) element comprised of MLD common information.

74. In item 73, the MLD common information includes an MLD media access control (MAC) address field, a link ID information field, a basic service set (BSS) parameter change count (BPCC) field, a synchronization delay field, and an enhanced multi-link (EML) capability field. , and a MLD capability field.

75. The wireless communication device of item 74, wherein the BPCC field indicates an update to one or more BSS parameters associated with the underlying link.

76. The wireless communication device of item 73, wherein link information of a non-basic link is not present in the ML element of the first frame.

77. The wireless communication of any one or more of items 71 to 76, wherein the third frame comprises a frame body including a multi-link (ML) element carrying STA-specific profile sub-elements representing an overall profile of the non-basic link. device.

78. Item 77, wherein the frame body further comprises a reduced neighbor reporting (RNR) element carrying a neighbor AP information field associated with the non-primary link, wherein the neighbor AP information field includes a basic service set identification (BSSID) and a non-default link. A wireless communication device carrying a Target Beacon Transmission Time (TBTT) information field consisting of one or more MLD parameters of an underlying link.

79. The wireless communication device of item 78, wherein the TBTT information field corresponding to the non-basic link does not include a TBTT offset subfield, a short-SSID subfield, a BSS parameters subfield, and a power spectral density (PSD) subfield.

80. The wireless communication device of any one or more of items 71-79, wherein the beacon interval, SSID, and TSF values of the non-primary link are inherited from the primary link.

81. A wireless communication method using a wireless station (STA),

Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links; and

A method of wireless communication by a wireless station, comprising transmitting only a primary link, a frame comprising one or more timing parameters associated with the primary link, wherein the non-primary link comprises one or more timing parameters inherited from the primary link.

82. The method of item 81, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

83. The method of any one or more of items 81-82, wherein the one or more timing parameters include at least one of a channel change notification, a dead period, or a beacon interval.

84. The wireless communication by a wireless station of any one or more of items 81 to 83, wherein the primary link is associated with a target beacon transmission time (TBTT), and the non-primary link comprises a pseudo-BSS aligned with the TBTT of the primary link. method.

85. The method of any one or more of items 81 to 84, wherein a target latency (TWT) session established on a non-primary link is synchronized with a TWT session established on a primary link.

86. In any one or more of items 81 to 85,

A method of wireless communication by a wireless station, further comprising aligning an uplink (UL) transmission to an NSTR softAP MLD on a non-primary link with a UL transmission to the NSTR softAP MLD on a primary link.

87. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code, wherein the processor-readable code, when executed by the at least one processor in conjunction with the at least one modem:

Operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links; and

A wireless communications device configured to transmit only a primary link, a frame comprising one or more timing parameters associated with the primary link, wherein the non-primary link includes one or more timing parameters inherited from the primary link.

88. The wireless communications device of item 87, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

89. The wireless communication device of any one or more of items 87-88, wherein the one or more timing parameters include at least one of a channel change notification, a dead period, or a beacon interval.

90. The wireless communications device of any one or more of items 87-89, wherein the primary link is associated with a target beacon transmission time (TBTT), and the non-primary link comprises a pseudo-BSS aligned with the TBTT of the primary link.

91. The wireless communication device of any one or more of items 87-90, wherein a target latency (TWT) session established on a non-primary link is synchronized with a TWT session established on a primary link.

92. The method of any one or more of items 87-91, wherein executing the processor-readable code comprises:

A wireless communications device further configured to align uplink (UL) transmissions to an NSTR softAP MLD on a non-primary link with UL transmissions to an NSTR softAP MLD on a primary link.

93. A wireless communication method using a wireless station (STA),

Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links;

Obtaining channel access on the primary link;

transmitting a first frame to a first associated STA on a primary link;

putting the non-primary link into a deaf state for the duration of transmitting frames on the primary link; and

A method of wireless communication by a wireless station, comprising recovering a non-primary link from a hearing loss condition after frame transmission on the primary link is terminated.

94. The method of item 93, wherein the first frame comprises a management frame, a control frame, or a data frame.

95. In any one or more of items 93 to 95,

obtaining channel access on a non-primary link based on channel access obtained on the primary link; and

A method of wireless communication by a wireless station, further comprising transmitting a second frame to a second associated STA on a non-basic link simultaneously with transmitting a third frame on a primary link to a first associated STA.

96. The method of item 95, wherein the first associated STA is a legacy device configured to operate in accordance with an earlier revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and the second associated STA is a legacy device configured to operate in accordance with an IEEE 802.11be or later revision to the 802.11 family of wireless communications standards. A method of wireless communication by a wireless station, a non-legacy device configured to operate in accordance with a revision of .

97. In item 95,

A method of wireless communication by a wireless station, further comprising synchronizing transmission of a second frame on a non-basic link with transmission of a third frame on a primary link.

98. In item 93,

Obtaining channel access on a non-primary link during at least a portion of the channel access obtained on the primary link; and

During transmission of the first frame on the primary link, transmitting a second frame on a non-primary link to one or more second associated STAs.

99. The method of item 98, wherein the first frame is a beacon frame and the second frame is an aggregated transmission to one or more second associated STAs.

100. The method of item 99, wherein the one or more second associated STAs are multiple wireless devices operating on primary links and non-primary links.

101. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code, wherein the processor-readable code, when executed by the at least one processor in conjunction with the at least one modem:

Operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links;

obtain channel access on the primary link;

transmit the first frame to the first associated STA on the primary link;

place the non-primary link in a deaf state for the duration of the frame transmission on the primary link; and

A wireless communications device configured to restore a non-primary link from a hearing loss state after frame transmission on the primary link is terminated.

102. The wireless communication device of item 101, wherein the first frame comprises a management frame, a control frame, or a data frame.

103. The method of any one or more of items 101-102, wherein executing the processor-readable code comprises:

obtain channel access on the non-primary link based on channel access obtained on the primary link; and

The wireless communication device further configured to transmit the second frame to the second associated STA on the non-primary link simultaneously with transmitting the third frame to the first associated STA on the primary link.

104. The method of item 103, wherein the first associated STA is a legacy device configured to operate in accordance with an earlier revision to the IEEE 802.11ax or 802.11 family of wireless communications standards, and the second associated STA is a legacy device configured to operate in accordance with the IEEE 802.11be or later revision to the 802.11 family of wireless communications standards. A wireless communication device, which is a non-legacy device configured to operate in accordance with a revision of .

105. The method of item 103, wherein execution of the processor-readable code comprises:

The wireless communication device further configured to synchronize transmission of the second frame on the non-basic link with transmission of the third frame on the primary link.

106. The method of item 101, wherein execution of the processor readable code comprises:

acquire channel access on a non-primary link during at least a portion of the channel access obtained on the primary link; and

The wireless communication device further configured to transmit, during transmission of the first frame on the primary link, a second frame on the non-primary link to the one or more second associated STAs.

107. The wireless communication device of item 106, wherein the first frame is a beacon frame and the second frame is an aggregated transmission to one or more second associated STAs.

108. The wireless communication device of item 107, wherein the one or more second associated STAs are multiple wireless devices operating on primary and non-primary links.

109. A wireless communication method using a wireless station (STA),

Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links;

Obtaining channel access to primary and non-primary links;

establishing adjusted target latency (TWT) sessions on primary and non-primary links;

Transmitting, on the basic link, a first trigger frame requesting uplink (UL) transmission from a first STA group on the basic link; and

Concurrently with transmitting the first trigger frame on the primary link, transmitting on the non-primary link a second trigger frame requesting uplink (UL) transmission from a second STA group on the non-primary link. Wireless communication method by.

110. In item 109,

Receiving one or more first UL physical layer protocol data units (PPDUs) from a first STA group on a basic link based on a first trigger frame; and

A method of wireless communication by a wireless station, further comprising receiving one or more second UL physical layer protocol data units (PPDUs) from a second STA group on a non-basic link based on a second trigger frame.

111. In item 110,

A method of wireless communication by a wireless station, further comprising synchronizing one or more respective TWT service periods on a non-primary link with one or more respective TWT service periods on a primary link.

112. The wireless station of item 110, wherein the transmission of the one or more second UL PPDUs by the second STA group on the primary link is temporally aligned with the transmission of the one or more first UL PPDUs by the first STA group on the primary link. wireless communication method.

113. In item 110,

Transmitting one or more first downlink (DL) PPDUs on a primary link to a first STA group; and

A method of wireless communication by a wireless station further comprising transmitting one or more first DL PPDUs to a first STA group on a primary link and simultaneously transmitting one or more second DL PPDUs to a second STA group on a non-primary link. .

114. As a wireless communication device,

At least one modem;

at least one processor communicatively coupled with at least one modem; and

at least one memory communicatively coupled to at least one processor and storing processor-readable code, wherein the processor-readable code, when executed by the at least one processor in conjunction with the at least one modem:

Operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) associated with primary and non-primary links;

Obtain channel access to primary and non-primary links;

Establish coordinated target latency (TWT) sessions on primary and non-primary links;

Transmit, on the basic link, a first trigger frame requesting uplink (UL) transmission from the first STA group on the basic link; and

The wireless communication further configured to transmit, simultaneously with transmission of the first trigger frame on the primary link, a second trigger frame requesting uplink (UL) transmission from a second STA group on the non-primary link. device.

115. The method of item 114, wherein execution of the processor readable code comprises:

Receive one or more first UL physical layer protocol data units (PPDUs) from a first STA group on a basic link based on a first trigger frame; and

The wireless communication device further configured to receive one or more second UL physical layer protocol data units (PPDUs) from a second STA group on a non-basic link based on the second trigger frame.

116. The method of item 115, wherein execution of the processor-readable code comprises:

The wireless communication device further configured to synchronize one or more TWT service periods on a non-primary link with one or more respective TWT service periods on a primary link.

117. The wireless communication of item 115, wherein transmission of the one or more second UL PPDUs by the second STA group on the primary link is temporally aligned with transmission of the one or more first UL PPDUs by the first STA group on the primary link. device.

118. The method of item 115, wherein execution of the processor-readable code comprises:

transmit one or more first downlink (DL) PPDUs on the primary link to the first STA group; and

The wireless communication device further configured to transmit one or more first DL PPDUs on a primary link to a first STA group while simultaneously transmitting one or more second DL PPDUs on a non-primary link to a second STA group.

As used herein, a phrase referring to “at least one of” or “one or more of” a list of items refers to any combination of those items, including single elements. For example, “at least one of a, b, or c” means a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of b and c. It is intended to encompass the possibilities of

The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithmic processes described in connection with the implementations disclosed herein include the structures disclosed herein and their structural equivalents, electronic It may be implemented in hardware, firmware, software, or a combination of hardware, firmware, or software. The interchangeability of hardware, firmware and software has been described generally in terms of functionality and is illustrated by the various example components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and design constraints imposed on the overall system.

Various modifications to the implementations described in this disclosure may be apparent to those skilled in the art, and the generic principles defined herein may be applied to other implementations without departing from the spirit or scope of the disclosure. Accordingly, the claims are not intended to be limited to the implementations described herein but are to be accorded the widest scope consistent with the disclosure, principles, and novel features disclosed herein.

Additionally, various features described herein in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. To this end, although features may be described above and even initially claimed as operating in certain combinations, one or more features from a claimed combination may in some cases be deleted from that combination, and the claimed combination may It may be about a sub-combination or a change in a sub-combination.

Similarly, although operations are shown in the drawings in a particular order, this is not to be understood as requiring that such operations be performed in the particular order or sequential order shown, or that all illustrated operations be performed, to achieve the desired results. should not be Additionally, the drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, concurrently with, or between any of the illustrated operations. Multitasking and parallel processing may be advantageous in some environments. Additionally, the separation of various system components in the implementations described above should not be construed as requiring such separation in all implementations, and that the described program components and systems are generally integrated together in a single software product or may be integrated into multiple It should be understood that it can be packaged into software products.

Claims (30)

A wireless communication method using a wireless station (STA),
A non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) comprising a first access point (AP) associated with a primary link and a second AP associated with a non-primary link. operating steps;
determining that the non-primary link is not available; and
A method of wireless communication by a wireless station, comprising transmitting a frame only on the primary link carrying an indication of the unavailability of the non-primary link. The method of claim 1, wherein the frame includes one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame. The method of claim 1, wherein the frame includes a profile sub-element for each STA or a reduced neighbor report (RNR) element carrying a Do Not Transmit (DNT) bit set to a value of 1, and 1 wherein the DNT bit set to a value indicates unavailability of the non-primary link. The method of claim 1, wherein the frame includes a capability information field carrying a Critical Update Flag (CUF), wherein the CUF is set to a value of 1 based on unavailability of the non-primary link. A wireless communication method using a radio station. According to paragraph 1,
A method of wireless communication by a wireless station, further comprising operating as a single link device on the primary link based on unavailability of the non-primary link. According to clause 5,
determining that the non-primary link is available while operating as the single link device on the primary link;
resetting a do not transmit (DNT) bit to a value of 0 based on availability of the non-primary link; and
Further comprising transmitting the reset DNT bit in another frame only on the basic link, wherein the other frame is a per-STA profile sub-element or reduced neighbor report (RNR) carrying the reset DNT bit with a value of 0. ) A method of wireless communication by a wireless station, comprising elements. According to paragraph 1,
determining that the non-default link is available after sending the indication;
transmitting an indication of availability of the non-primary link only on the primary link; and
A method of wireless communication by a wireless station, further comprising operating as a multi-link device on the primary link and the non-primary link based on availability of the non-primary link. 2. The wireless station of claim 1, further comprising disabling the non-primary link or placing the non-primary link in a power save state based on unavailability of the non-primary link. Wireless communication method by. 9. The method of claim 8, wherein deactivating the non-basic link includes removing the non-basic link from a multiple link context associated with the NSTR softAP MLD. According to clause 9,
determining that the non-primary link is available after removing the non-primary link from the multi-link context; and
A method of wireless communication by a wireless station further comprising adding the non-primary link to the multi-link context based on availability of the non-primary link. 9. The method of claim 8, wherein deactivating the non-basic link includes remapping a traffic identifier (TID) from the non-basic link to the primary link. According to clause 11,
determining that the non-primary link is available after deactivating the non-primary link; and
A method of wireless communication by a wireless station, further comprising remapping the TID from the primary link to the non-primary link based on availability of the non-primary link. According to paragraph 1,
Receiving a ready-to-send (RTS) frame from the STA MLD on the basic link;
Transmitting a clear-to-send (CTS) frame to the STA MLD in the basic link and the non-basic link based on receiving the RTS frame; and
Wireless communication by a radio station, further comprising receiving one or more uplink (UL) physical-layer protocol data units (PPDU) from the STA MLD on the primary link and the non-basic link. method. According to paragraph 1,
Switching the basic link from the first channel to the second channel simultaneously with switching the non-basic link from the second channel to the first channel. 15. The method of claim 14, wherein the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band. Wireless communication method. As a wireless communication device,
At least one modem;
at least one processor communicatively coupled to the at least one modem; and
at least one memory communicatively coupled to the at least one processor and storing processor-readable code, wherein the processor-readable code, when executed by the at least one processor in conjunction with the at least one modem, ,
Operates as a non-simultaneous transmit-receive (NSTR) soft AP multi-link device (MLD) including a first access point (AP) associated with a primary link and a second AP associated with a non-primary link;
determine that the non-default link is not available; and
A wireless communication device configured to transmit only on a primary link a frame carrying an indication of unavailability of the non-primary link. 17. The wireless communications device of claim 16, wherein the frame comprises one of a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or an action frame. The method of claim 16, wherein the frame includes an STA-specific profile sub-element or a reduced neighbor reporting (RNR) element carrying a transmission prohibition (DNT) bit set to a value of 1, and the DNT bit set to a value of 1. A wireless communication device indicating unavailability of the non-primary link. 17. The wireless communications device of claim 16, wherein the frame includes a capability information field carrying a critical update flag (CUF), wherein the CUF is set to a value of 1 based on unavailability of the non-primary link. 17. The method of claim 16, wherein executing the processor readable code comprises:
The wireless communication device further configured to operate as a single link device on the primary link based on unavailability of the non-primary link. 21. The method of claim 20, wherein executing the processor readable code comprises:
determine that the non-primary link is available while operating as the single link device on the primary link;
reset a do not transmit (DNT) bit to a value of 0 based on availability of the non-primary link; and
STA-specific profile sub-element or reduced neighbor reporting (RNR) element further configured to transmit the reset DNT bit in another frame only on the primary link, and the other frame carries the reset DNT bit with a value of 0. A wireless communication device including. 17. The method of claim 16, wherein executing the processor readable code comprises:
determine that the non-default link is available after sending the indication;
send an indication of availability of the non-primary link only on the primary link; and
The wireless communication device further configured to operate as a multi-link device on the primary link and the non-primary link based on availability of the non-primary link. 17. The wireless communications device of claim 16, wherein execution of processor readable code is further configured to deactivate the non-primary link or place the non-primary link in a power saving state based on unavailability of the non-primary link. 24. The wireless communications device of claim 23, wherein deactivating the non-primary link includes removing the non-primary link from a multi-link context associated with an NSTR softAP MLD. 25. The method of claim 24, wherein executing the processor readable code comprises:
determine that the non-primary link is available after removing the non-primary link from the multi-link context; and
The wireless communication device further configured to add the non-primary link to the multi-link context based on availability of the non-primary link. 24. The wireless communications device of claim 23, wherein deactivating the non-primary link includes remapping a traffic identifier (TID) from the non-primary link to the primary link. 27. The method of claim 26, wherein executing the processor readable code comprises:
determine that the non-default link is available after deactivating the non-default link; and
and remap the TID from the primary link to the non-primary link based on availability of the non-primary link. 17. The method of claim 16, wherein executing the processor readable code comprises:
Receive a ready to send (RTS) frame from the STA MLD on the primary link;
transmit a transmittable (CTS) frame to the STA MLD on the primary link and the non-primary link based on receiving the RTS frame; and
The wireless communication device further configured to receive one or more uplink (UL) physical layer protocol data units (PPDUs) from the STA MLD on the primary link and the non-basic link. 17. The method of claim 16, wherein executing the processor readable code comprises:
The wireless communication device further configured to switch the basic link from the first channel to the second channel simultaneously with switching the non-basic link from the second channel to the first channel. 30. The wireless communications device of claim 29, wherein the first channel is in one of the 5 GHz frequency band or the 6 GHz frequency band, and the second channel is in the other of the 5 GHz frequency band or the 6 GHz frequency band. .

Images