Non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD)

Abstract

A wireless station (STA) operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multi-link device (MLD) is associated with a primary link and a non-primary link. The NSTR soft AP MLD transmits, only on the primary link, a frame that includes a complete profile of the primary link and indicates a complete profile of the non-primary link. The respective complete profiles of the primary and non-primary links each include capabilities, operating parameters, and other discovery information. The frame can include fields and elements carrying the complete profile of the primary link and can include a multi-link (ML) element indicating the complete profile of the non-primary link. The NSTR soft AP MLD can receive or determine an update to an operating parameter of the non-primary link and can transmit, on the primary link, an indication of the update to the operating parameter of the non-primary link.

Description

[0001] Cross-reference to related applications

[0002] This patent application 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 U.S. Patent Application No. 17 / 409,370, filed August 23, 2021, entitled "NON-SIMULTANEOUS TRANSMIT-RECEIVE(NSTR) SOFT ACCESS POINT(AP) MULTI-LINK DEVICE(MLD)", which are assigned to the assignee of this application. All disclosures of the prior applications are considered part of this patent application and are incorporated herein by reference. Technical Field

[0003] This disclosure relates in general to wireless communications, and more specifically to wireless communications associated with multi-link devices (MLDs). Background Technology

[0004] A Wireless Local Area Network (WLAN) can be formed by one or more Access Points (APs) that provide a shared wireless communication medium for use by several client devices (also known as stations (STAs)). The basic building block of a WLAN conforming to the 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 to enable any STA within the AP's wireless range to establish or maintain a communication link with the WLAN.

[0005] An AP multilink device (MLD) can include multiple APs capable of operating independently on multiple corresponding communication links. Each AP can establish a BSS on its corresponding communication link, and wireless communication devices associated with the AP MLD can transmit data to or receive data from the AP MLD on one or more of the communication links associated with the AP MLD. Each of these communication links can have various bandwidths by bundling several 20MHz wide channels together to form 40MHz, 80MHz, 160MHz, or 320MHz wide channels. Although a STA may have limited filtering capabilities that allow data reception on one link to interfere with data transmission on another link, it may be desirable for the STA to operate as a soft AP MLD. Summary of the Invention

[0006] The systems, methods, and apparatuses disclosed herein are all innovative in some respects, but no single aspect is solely responsible for the desired properties disclosed herein.

[0007] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a radio station (STA). In some implementations, the method may include operating the STA as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD including a first AP associated with a primary link and a second AP associated with a non-primary link. The method also includes transmitting frames that include a complete profile of the primary link and indicate a complete profile of the non-primary link only on the primary link. In some instances, the respective complete profiles of the primary link and the non-primary link each include at least a beacon interval, capability information, a service set identifier (SSID), supported rates, a timing synchronization function (TSF) value, and one or more additional fields or elements associated with the discovery of the respective link. The frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some instances, the beacon interval, the SSID, and the TSF value of the non-primary link may be inherited from the primary link.

[0008] In some implementations, the frame includes a frame body comprising multiple fields and elements carrying a complete profile of the primary link, and a multi-link (ML) element carrying a per-STA profile sub-element indicating a complete profile of a non-primary link. The ML element also includes a common information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) field, which indicates an update to one or more BSS parameters associated with the primary link. In some instances, one or more bits of the ML element's multi-link control field or common information field indicate whether the frame was transmitted from the first AP of the NSTR soft APMLD.

[0009] In some implementations, the frame body also includes a Reduced Neighbor Report (RNR) element, which includes a neighbor AP information field associated with the non-primary link. This neighbor AP information field may contain a Target Beacon Transit Time (TBTT) information field, which includes the Basic Service Set Identifier (BSSID) and one or more MLD parameters for the non-primary link. In some instances, the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield may not be present in the TBTT information field corresponding to the non-primary link. The neighbor AP information field may also include a TBTT information field type set to indicate that the neighbor AP information field carries information relevant only to the non-primary link. In some instances, the TBTT information field type may be set to 1 or a reserved value to indicate that the TBTT information field has a new or undefined type. In some implementations, the length of the TBTT information field may indicate whether the frame was transmitted from the first AP of the NSTR soft AP MLD. In some aspects, the length of the TBTT information field is nine octets.

[0010] In some implementations, the one or more MLD parameters carried in the TBTT information field may include a PBCC value indicating an update to one or more BSS parameters associated with the non-primary link. In some instances, the method may further include: receiving an update to at least one of the BSS parameters associated with the non-primary link; incrementing the BPCC value carried in the TBTT information field of another frame based on the received update; setting a Key Update Flag (CUF) in the capability information field of the other frame based on the incremented BPCC value; and transmitting the other frame only on the primary link. In this way, the receiving device can obtain updates to the BSS parameters of the non-primary link while residing on the primary link. In various implementations, the BSS parameter may include at least one of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

[0011] The method may further include: receiving updates to one or more BSS parameters associated with the non-primary link; and transmitting the updated one or more BSS parameters associated with the non-primary link on the primary link. In some instances, the updated one or more BSS parameters may be part of a partial profile of the non-primary link. The updated one or more BSS parameters may be transmitted on the primary link in beacon frames, probe response frames, association response frames, reassociation response frames, or action frames (such as notification frames).

[0012] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. In some implementations, the wireless communication device may include 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. In some implementations, the execution of the processor-readable code by the at least one processor in conjunction with the at least one modem may be configured to operate the wireless communication device as an NSTR soft AP MLD, the NSTR soft AP MLD including a first AP associated with a primary link and a second AP associated with a non-primary link. The execution of the processor-readable code may also be configured to transmit frames that include a complete profile of the primary link and indicate a complete profile of the non-primary link only on the primary link. In some instances, the complete profiles of the primary link and the non-primary link each include at least a beacon interval, capability information, SSID, supported rate, TSF value, and one or more additional fields or elements associated with the discovery of the respective link. The frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some instances, the beacon interval, SSID, and TSF value of the non-primary link can be inherited from the primary link.

[0013] In some implementations, the frame includes a frame body comprising multiple fields and elements carrying the full profile of the primary link, and an ML element carrying per-STA profile sub-elements indicating the full profile of the non-primary link. The ML element also includes a common information field, which includes a BPCC field indicating an update to one or more BSS parameters associated with the primary link. In some instances, 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 soft AP MLD.

[0014] In some implementations, the frame body also includes an RNR element, which includes a neighbor AP information field associated with the non-primary link. This neighbor AP information field may include a TBTT information field, which includes the BSSID of the non-primary link and one or more MLD parameters. In some instances, the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and PSD subfield may not be present in the TBTT information field corresponding to the non-primary link. The neighbor AP information field may also include a TBTT information field type set to a value indicating that the neighbor AP information field carries information only relevant to the non-primary link. In some instances, the TBTT information field type may be set to 1 or a reserved value to indicate that the TBTT information field has a new or undefined type. In some implementations, the length of the TBTT information field may indicate whether the frame is transmitted from the first AP of the NSTR soft AP MLD. In some aspects, the length of the TBTT information field is nine octets.

[0015] In some implementations, the one or more MLD parameters carried in the TBTT information field may include a BPCC value indicating an update to one or more BSS parameters associated with the non-primary link. In some instances, the execution of the processor-readable code may also be configured to: receive an update to at least one of the BSS parameters associated with the non-primary link; increment the BPCC value carried in the TBTT information field of another frame based on the received update; set the CUF in the capability information field of the other frame based on the incremented BPCC value; and transmit the other frame only on the primary link. In this way, the receiving device can obtain updates to the BSS parameters of the non-primary link while residing on the primary link. In various implementations, the BSS parameter may include at least one of the following: CSA element, eCSA element, EDCA parameter, quiet period element, DSSS parameter set, HT operation element, VHT operation element, HE operation element, EHT operation element, wideband channel switching element, operation mode notification element, broadcast TWT element, BSS color change announcement element, MU EDCA parameter set, space reuse parameter set, or UORA parameter set.

[0016] The processor-readable code can also be configured to: receive updates to one or more BSS parameters associated with the non-primary link; and transmit the updated one or more BSS parameters associated with the non-primary link on the primary link. In some instances, the updated one or more BSS parameters may be part of a partial profile of the non-primary link. The updated one or more BSS parameters may be transmitted on the primary link in beacon frames, probe response frames, association response frames, reassociation response frames, or action frames (such as notification frames). Attached Figure Description

[0017] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Note that the relative dimensions in the drawings may not be depicted to scale.

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

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

[0020] Figure 2B It shows Figure 2A Example fields in the PDU.

[0021] Figure 3A Another example PDU that can be used for communication between an AP and one or more STAs is shown.

[0022] Figure 3B Another example PDU that can be used for communication between an AP and one or more STAs is shown.

[0023] Figure 4 An example Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) is shown that can be used for communication between an AP and several STAs.

[0024] Figure 5 A block diagram of an example wireless communication device is shown.

[0025] Figure 6A A block diagram of an example access point (AP) is shown.

[0026] Figure 6B A block diagram of an example station (STA) is shown.

[0027] Figure 7A Sequence diagrams depicting example wireless communications supporting non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink devices (MLDs) according to some implementations are shown.

[0028] Figure 7B A sequence diagram depicting another example of wireless communication supporting NSTR soft AP MLD according to some implementations is shown.

[0029] Figure 8A A sequence diagram depicting an example wireless communication supporting an NSTR soft AP MLD according to some other implementations is shown.

[0030] Figure 8B A sequence diagram depicting another example of wireless communication supporting NSTR soft AP MLD according to some other implementations is shown.

[0031] Figure 9A A timing diagram depicting example wireless communication supporting NSTR soft AP MLD according to some implementations is shown.

[0032] Figure 9B A timing diagram depicting another example of wireless communication supporting NSTR soft AP MLD according to some implementations is shown.

[0033] Figure 10A Example management frames that can be used for multi-link communication are shown according to some implementations.

[0034] Figure 10B Another example of a management frame that can be used for multi-link communication, based on some implementations, is shown.

[0035] Figure 11A An example of a reduced neighbor report (RNR) element, based on some implementations, is shown that can be used for multi-link communication.

[0036] Figure 11B It shows some implementations Figure 11A Example TBTT message header for RNR elements.

[0037] Figure 11C It shows some implementations Figure 11A Example TBTT information field of RNR element.

[0038] Figure 12A An example multilink (ML) element is shown, based on some implementations, that can be used for multilink communication.

[0039] Figure 12B It shows some implementations Figure 12A Example of a multi-link control field for ML elements.

[0040] Figure 12C It shows some implementations Figure 12A Examples of ML elements share information fields.

[0041] Figure 12D It shows some implementations Figure 12A Examples of ML elements per ST profile element.

[0042] Figure 12E It shows some implementations Figure 12D Example STA control fields for each STA profile element.

[0043] Figure 12F It shows some implementations Figure 12D Example STA information fields for each STA profile element.

[0044] Figures 13 to 36 A flowchart illustrating an example process for wireless communication supporting NSTR soft AP MLD according to some implementations is shown.

[0045] Figure 37 A block diagram of an example wireless communication device based on some implementations is shown.

[0046] Figure 38 A block diagram of another example wireless communication device based on some implementations is shown.

[0047] The same reference numerals and names in different figures denote the same elements.

[0048] Implementation

[0049] The following description is directed to certain implementations in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, and as defined by the Bluetooth Special Interest Group (SIG). The described implementation can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to one or more of the following standards, or those published by the 3rd Generation Partnership Project (3GPP): Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)). The described implementation can be implemented in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Single User (SU) Multiple Input Multiple Output (MIMO), and Multi User (MU) MIMO. The described implementation can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of Wireless Personal Area Networks (WPANs), Wireless Local Area Networks (WLANs), Wireless Wide Area Networks (WWANs), or Internet of Things (IoT) networks.

[0050] Various implementations generally involve communication between multilink devices (MLDs), such as AP MLDs and STA MLDs. Some implementations more specifically involve radio stations (STAs) operating as mobile hotspots on multiple communication links. An AP MLD includes multiple APs configured to communicate on multiple different communication links. A STA MLD can simultaneously use one or more of the different communication links to communicate with the AP MLD. The AP MLD can provide a multilink context, which includes or indicates complete profiles of the different communication links associated with the AP MLD. The complete profiles of the respective links may include the capabilities, operating parameters, and discovery information of the respective links. An AP MLD can advertise a multilink context on one of its communication links, allowing nearby wireless communication devices (such as STA MLDs) operating on that communication link to receive the multilink context and obtain complete profiles of the multiple communication links for the AP MLD. In this way, a wireless communication device operating on one communication link can discover and associate with one or more other AP MLDs on other communication links without scanning or probing other communication links. The communication link on which the AP MLD advertises the multilink context may be referred to as the primary link, and the other communication links may be referred to as non-primary links.

[0051] Multi-link context also allows the AP MLD and one or more associated devices to establish shared block acknowledgment (BA) policies or sessions on multiple communication links of the AP MLD, and to use a single authentication mechanism for multiple communication links of the AP MLD. Associated devices can use multi-link context to dynamically switch communication between different communication links of the AP MLD without unassociating or reassociating with the AP MLD. The AP MLD can use multi-link context to dynamically change or remap the traffic identifier (TID) value with the affiliation relationship between each communication link in different communication links.

[0052] Compared to access points (APs), wireless STAs have limited filtering capabilities that allow transmissions to the STA on one link to interfere with data transmissions from the STA on another link. For example, when a STA transmits downlink (DL) communication on one link while simultaneously receiving uplink (UL) communication on another, the relatively small spacing between the STA's antenna resources, along with its limited filtering capabilities, can allow DL data transmission on one link to interfere with or prevent concurrent UL data reception on another link. This cross-link interference can suppress or prevent STAs operating as mobile hotspots on multiple communication links from concurrently transmitting and receiving data on different communication links. Therefore, these STAs can be referred to as Non-Simultaneous Transmit-Receive (NSTR) soft APs (MLDs).

[0053] Various aspects of this disclosure recognize the importance of reducing or eliminating cross-link interference associated with NSTR soft AP MLDs. In some implementations, an NSTR soft AP MLD associated with a primary link and a secondary link can advertise complete profiles of both the primary and secondary links only on the primary link. The NSTR soft AP MLD can also advertise updates to one or more BSS parameters of the primary and secondary links only on the primary link. Advertising complete profiles of both links for the NSTR soft AP MLD on the primary link allows some wireless communication devices operating on the primary link to discover and associate with NSTR soft AP MLDs on one or both of the primary and secondary links without scanning or probing the secondary link. In some implementations, legacy devices operating on the primary link may be able to decode or parse the complete profiles of both the primary and secondary links, while legacy devices operating on the primary link may be able to decode or parse only the complete profile of the primary link. Therefore, legacy devices operating on the primary link may not be able to discover or associate with NSTR soft AP MLDs on the secondary link. Furthermore, by not advertising the complete profile of any link on non-main links, legacy devices operating on non-main links may not be able to discover or associate with the NSTR soft AP MLD on the non-main link. In this way, various aspects of the subject matter disclosed herein can restrict communication between the NSTR soft AP MLD and legacy devices to the main link. As used herein, the term "legacy device" may refer to a wireless communication device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and the term "non-legacy device" may refer to a wireless communication device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0054] Various aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. By restricting communication between the NSTR soft AP MLD and legacy devices to the main link (and thereby preventing legacy devices from communicating with the NSTR soft AP MLD on non-main links), the NSTR soft AP MLD can prevent legacy devices from transmitting UL data on non-main links, while the NSTR soft AP MLD transmits DL data to one or more associated devices on the main link. In this way, implementations of the subject matter disclosed herein can reduce the likelihood of cross-link interference caused by UL transmission on non-main links or otherwise interfere with DL transmission from the NSTR soft AP MLD on the main link.

[0055] Figure 1A block diagram of an example wireless communication network 100 is shown. Depending on some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) (such as a Wi-Fi network) (and will be referred to WLAN 100 below). For example, WLAN 100 may be a network implementing at least one of the IEEE 802.11 standard family (such as standards defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). WLAN 100 may include numerous wireless communication devices, such as access points (APs) 102 and multiple stations (STAs) 104. Although only one AP 102 is shown, WLAN network 100 may also include multiple APs 102.

[0056] Each STA 104 may also be referred to as a mobile station (MS), mobile device, mobile handheld device, wireless handheld device, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, etc. STA 104 can represent various devices such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, laptops, tablets, laptops, display devices (e.g., TVs, computer monitors, navigation systems, etc.), music or other audio or stereo devices, remote control devices ("remote controllers"), printers, kitchen or other household appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.

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

[0058] In order to establish a communication link 108 with AP 102, each STA 104 is configured to perform passive or active scanning operations (“scan”) on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). To perform a passive scan, STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (referred to as Target Beacon Transmission Time (TBTT) (measured in units of time (TU), where one TU can be equal to 1024 microseconds (μs)). To perform an active scan, STA 104 generates probe requests and transmits these probe requests sequentially on each channel to be scanned, and listens for probe responses from AP 102. Each STA 104 can be configured to identify or select an AP 102 to associate with based on scan information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 108 with the selected AP 102. At the end of the association operation, AP 102 assigns an Association Identifier (AID) to STA 104, which AP 102 uses to track STA 104.

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

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

[0061] AP 102 and STA 104 can operate and communicate (via the corresponding communication link 108) according to the IEEE 802.11 standard family (such as standards defined by the IEEE 802.11-2016 specification or its revisions, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). These standards define the WLAN radio and baseband protocols used for the PHY and Media Access Control (MAC) layers. AP 102 and STA 104 transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communication") to and from each other in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs). AP 102 and STA 104 in WLAN 100 can transmit PPDUs on unlicensed spectrum, which can be a portion of a spectrum that includes bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz band, 5.0 GHz band, 60 GHz band, 3.6 GHz band, and 900 MHz band. Some implementations of AP 102 and STA 104 described herein can also communicate in other bands, such as the 6.0 GHz band, that can support both licensed and unlicensed communication. AP 102 and STA 104 can also be configured to communicate on other bands, such as shared licensed bands, where multiple operators may have licenses to operate in one or more of the same or overlapping bands.

[0062] Each frequency band can include multiple sub-bands or frequency channels. For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, and 802.11ax standards can be transmitted in the 2.4 GHz and 5.0 GHz bands, where each band is divided into multiple 20 MHz channels. Thus, these PPDUs are transmitted on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs can be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.

[0063] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PLCP Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving equipment to decode subsequent data in the PSDU. In instances where the PPDU is transmitted over bonded channels, the preamble field may be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a traditional portion (or "traditional preamble") and a non-traditional portion (or "non-traditional preamble"). The traditional preamble can be used for packet detection, automatic gain control, and channel estimation, among other applications. The traditional preamble is also generally used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-traditional portion of the preamble are based on the specific IEEE 802.11 protocol to be used for transmitting the payload.

[0064] Figure 2A An example Protocol Data Unit (PDU) 200 is shown that can be used for communication between an AP and several STAs. For example, PDU 200 can be configured as a PPDU. As shown, PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, the PHY preamble 202 may include a conventional portion, which itself includes a conventional short training field (L-STF) 206, a conventional long training field (L-LTF) 208, and a conventional signaling field (L-SIG) 210. The PHY preamble 202 may also include a non-conventional portion (not shown). L-STF 206 generally enables the receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. L-LTF 208 generally enables the receiving device to perform fine timing and frequency estimation, and also to estimate the radio channel. L-SIG 210 generally enables the receiving device to determine the duration of the PDU and use the determined duration to avoid transmission over the PDU. For example, L-STF 206, L-LTF 208, and L-SIG 210 can be modulated according to a binary phase shift keying (BPSK) modulation scheme. Payload 204 can be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another appropriate modulation scheme. Payload 204 can generally carry higher-layer data (e.g., in the form of Media Access Control (MAC) Protocol Data Units (MPDUs) or Aggregated MPDUs (A-MPDUs).

[0065] Figure 2B It shows Figure 2AExample L-SIG field 220 in the PDU. L-SIG 220 includes a data rate field 222, reserved bits (R) 224, a length field 226, a parity bit (P) 228, and a tail field 220. The data rate field 222 indicates the data rate (note that the data rate indicated in the data rate field 222 may not be the actual data rate of the data carried in the payload 204). The length field 226 indicates the packet length, for example, in bytes. The parity bit 228 is used to detect bit errors. The tail field 220 includes a tail portion, which is used by the receiving device to terminate the operation of the decoder (e.g., the Viterbi decoder). The receiving device uses the data rate and length indicated in the data rate field 222 and the length field 226 to determine the packet duration, for example, in microseconds (μs).

[0066] Figure 3A Another example PDU 300 is shown that can be used 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 can be formatted as a High Efficiency (HE) WLAN PPDU according to the IEEE 802.11ax revision of the IEEE 802.11 wireless communication protocol standard. PDU 300 includes a PHY preamble comprising a traditional portion 302 and a non-traditional portion 304. PDU 300 may further include a PHY payload 306 (e.g., in the form of a PSDU including a data field 324) after the preamble.

[0067] The conventional portion 302 of the preamble includes L-STF 308, L-LTF 310, and L-SIG 312. The non-conventional portion 304 includes a repetition of L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, a short HE training field (HE-STF) 320, and one or more long HE training fields (or symbols) (HE-LTF) 322. For OFDMA or MU-MIMO communication, the second portion 304 further includes a second HE signal field (HE-SIG-B) 318 encoded separately from HE-SIG-A 316. Similar to L-STF 308, L-LTF 310, and L-SIG 312, in instances involving the use of bonded channels, the information in RL-SIG 314 and HE-SIG-A 316 can be copied and transmitted in each component 20MHz channel. In contrast, the contents of HE-SIG-B 318 can be unique for each 20MHz channel and target-specific STA 104.

[0068] RL-SIG 314 indicates to HE-compatible STA 104 that PDU 300 is an HE PPDU. AP 102 can use HE-SIG-A316 to identify multiple STAs 104 and notify them that the AP has scheduled UL or DL ​​resources for them. For example, HE-SIG-A 316 may include a resource allocation subfield indicating the resource allocation for the identified STA 104. HE-SIG-A 316 can be decoded by each HE-compatible STA 104 served by AP 102. For MU transmissions, HE-SIG-A 316 further includes information that can be used by each identified STA 104 to decode the associated HE-SIG-B 318. For example, HE-SIG-A 316 may indicate the frame format (including the location and length of HE-SIG-B 318), available channel bandwidth, modulation and decoding scheme (MCS), and other examples. HE-SIG-A 316 may also include HE WLAN signaling information that can be used by STA 104 other than the identified STA 104.

[0069] 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 allocation information. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding Resource Unit (RU) in the associated data field 324. Each HE-SIG-B 318 includes a common field and at least one STA-specific field. The common field may indicate RU allocations (including RU assignments in the frequency domain) for multiple STAs 104, indicating which RUs are allocated for MU-MIMO transmissions and which RUs correspond to MU-OFDMA transmissions, as well as the number of users in the allocation and other examples. The common field may be encoded with common bits, CRC bits, and a tail portion. The user-specific field is assigned to a specific STA 104 and may be used to schedule a specific RU and indicate that scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields, which contain information about the corresponding RU payload in the two corresponding STA decoding data fields 324.

[0070] Figure 3BAnother example PPDU 350 for wireless communication between an AP and one or more STAs is shown. The PDU 350 can be used for SU, OFDMA, or MU-MIMO transmissions. The PDU 350 can be formatted as an Extremely High Throughput (EHT) WLAN PPDU according to the IEEE 802.11be revision of the IEEE 802.11 wireless communication protocol standard, or it can be formatted as a PPDU of any future (post-EHT) version conforming to a new wireless communication protocol (conforming to future IEEE 802.11 wireless communication protocol standards or other wireless communication standards). The PDU 350 includes a PHY preamble comprising a traditional portion 352 and a non-traditional portion 354. The PDU 350 may also include a PHY payload 356 (e.g., in the form of a PSDU including a data field 376) after the preamble.

[0071] The conventional portion 352 of the preamble includes L-STF 358, L-LTF 360, and L-SIG 362. The non-conventional portion 354 of the preamble includes RL-SIG 364 and signal fields related to multiple wireless communication protocol versions following RL-SIG 364. For example, the non-conventional portion 354 may include a general signal field 366 (referred to herein as "U-SIG 366") and an EHT signal field 368 (referred to herein as "EHT-SIG 368"). One or both of U-SIG 366 and EHT-SIG 368 may be configured for other wireless communication protocol versions above EHT and carry information related to that version. The non-traditional portion 354 also includes an additional short training field 372 (referred to herein as "EHT-STF 372", but may also be constructed to carry version-related information for other wireless communication protocol versions besides EHT) and one or more additional long training fields 374 (referred to herein as "EHT-LTF 374", but may be constructed to carry version-related information for other wireless communication protocol versions besides EHT). Similar to L-STF 358, L-LTF 360, and L-SIG 362, in instances involving the use of bonded channels, the information in U-SIG 366 and EHT-SIG 368 may be copied and transmitted in each component 20MHz channel. In some implementations, EHT-SIG 368 may additionally or alternatively carry information different from that carried in the primary 20MHz channel in one or more non-primary 20MHz channels.

[0072] EHT-SIG 368 may include one or more jointly encoded symbols and may be encoded in a different block than the block in which U-SIG 366 is encoded. EHT-SIG 368 may be used by the AP to identify multiple STAs 104 and to notify those STAs that the AP has scheduled UL or DL ​​resources for them. EHT-SIG 368 may be decoded by each compatible STA 104 served by AP 102. EHT-SIG 368 may generally be used by the receiving device to interpret the bits in data field 376. For example, EHT-SIG 368 may include RU allocation information, spatial flow configuration information, and per-user signaling information (such as MCS) and other examples. 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 binary convolutional codes (BCC). In some implementations, EHT-SIG 368 may include one or more code blocks, each containing a CRC and a tail. In some aspects, each code block may be encoded individually.

[0073] EHT-SIG 368 can carry STA-specific scheduling information, such as, for example, user-specific MCS values ​​and user-specific RU allocation information. EHT-SIG 368 can generally be used by the receiving device to interpret the bits in data field 376. In the context of DL MU-OFDMA, this information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 376. Each EHT-SIG 368 may include a common field and at least one user-specific field. The common field may indicate the RU distribution across multiple STAs 104, indicate RU assignment in the frequency domain, indicate which RUs are allocated for MU-MIMO transmissions and which RUs correspond to MU-OFDMA transmissions, and the number of users in the allocation, among other examples. The common field may be encoded with common bits, CRC bits, and a tail portion. The user-specific field is assigned to a specific STA 104 and can be used to schedule specific RUs and indicate this scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include, for example, two user fields containing information for the two corresponding STAs to decode their respective RU payloads.

[0074] The presence of RL-SIG 364 and U-SIG 366 ensures compatibility with EHT or later versions. STA 104 indicates that PPDU 350 is an EHT PPDU or a PPDU of any later (post-EHT) version that conforms to a new wireless communication protocol (compliant with the future IEEE 802.11 wireless communication protocol standard). For example, U-SIG 366 can be used by the receiving device to interpret bits in one or more of EHT-SIG 368 or data field 376.

[0075] Figure 4 An example PPDU 400 is shown that can be used for communication between AP 102 and several 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), such as an aggregated MPDU (A-MPDU) 406 including multiple MPDU subframes 408. Each MPDU subframe 408 may include a MAC delimiter 412 and a MAC header 414 preceding the accompanying frame body 416, which includes the data portion or "payload" of the MPDU subframe 408. The frame body 416 may carry one or more MAC Service Data Units (MSDUs), such as an aggregated MSDU (A-MSDU) 422 including multiple MSDU subframes 424. Each MSDU subframe 424 contains a corresponding MSDU 426, which includes a subframe header 428, a frame body 430, and one or more padding bits 432.

[0076] Referring back to A-MPDU subframe 406, MAC header 414 may include several fields containing information defining or indicating the characteristics or attributes of the data encapsulated within frame body 416. MAC header 414 also includes several fields indicating the address of the data encapsulated within frame body 416. For example, MAC header 412 may include a combination of source address, sender address, receiver address, or destination address. MAC header 414 may include a frame control field containing control information. This frame control field specifies the frame type, such as a data frame, control frame, or management frame. MAC header 414 may also include a duration field indicating the duration from the end of the PPDU to the end of the acknowledgment (ACK) of the last PPDU to be transmitted by the wireless communication device (e.g., block ACK (BA) in the case of A-MPDU). The duration field is used to preserve the wireless medium until the indicated duration, thereby establishing NAV. Each A-MPDU subframe 408 may also include a Frame Check Sequence (FCS) field 418 for error detection. For example, FCS field 418 may include cyclic redundancy check (CRC), and may be followed by one or more padding bits 420.

[0077] As described above, AP 102 and STA 104 can support multi-user (MU) communication. That is, concurrent transmission from one device to each of multiple devices (e.g., multiple simultaneous downlink (DL) communications from AP 102 to the corresponding STA 104), or concurrent transmission from multiple devices to a single device (e.g., multiple simultaneous uplink (UL) transmissions from the corresponding STA 104 to AP 102). To support MU transmission, AP 102 and STA 104 can utilize multi-user multiple-input multiple-output (MU-MIMO) and multi-user orthogonal frequency division multiple access (MU-OFDMA) technologies.

[0078] In the MU-OFDMA scheme, the available spectrum of the radio channel can be divided into multiple Resource Elements (RUs), each comprising several different frequency subcarriers (“frequency modulo”). Different RUs can be allocated by AP 102 at specific times or assigned to different STAs 104. The size and distribution of RUs are referred to as RU allocation. In some implementations, RUs can be allocated in 2MHz intervals, and thus, the smallest RU can include 26 frequency moduloes, comprising 24 data frequency moduloes and 2 pilot frequency moduloes. Therefore, in a 20MHz channel, up to 9 RUs (such as 2MHz, 26-frequency modulo RUs) can be allocated (because some frequency moduloes are reserved for other purposes). Similarly, in a 160MHz channel, up to 74 RUs can be allocated. Larger RUs of 52, 106, 242, 484, and 996 frequency moduloes can also be allocated. Adjacent RUs can be separated by empty subcarriers (such as DC subcarriers) to reduce interference between adjacent RUs, reduce receiver DC offset, and avoid leakage of the transmit center frequency.

[0079] For UL MU transmissions, AP 102 can transmit trigger frames to initiate and synchronize ULMU-OFDMA or UL MU-MIMO transmissions from multiple STAs 104 to AP 102. Such trigger frames thus enable multiple STAs 104 to concurrently send UL traffic to AP 102 in time. The trigger frame can address one or more STAs 104 via a corresponding Association Identifier (AID), and can assign one or more RUs to each AID (and thus to each STA 104), which can be used to send UL traffic to AP 102. AP can also specify one or more Random Access (RA) RUs that are contentious for by unscheduled STAs 104.

[0080] Figure 5 A block diagram of an example wireless communication device 500 is shown. In some implementations, the wireless communication device 500 may be for STAs (such as those mentioned above). Figure 1Examples of devices in one of the described STA 104. In some implementations, the wireless communication device 500 may be for an AP (such as those described above). Figure 1 Example of a device in the described AP 102. Wireless communication device 500 is capable of transmitting (or outputting for transmission) and receiving wireless communications (e.g., in the form of wireless packets). For example, wireless communication device 500 can be configured to transmit and receive packets in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs) and Media Access Control (MAC) Protocol Data Units (MPDUs) conforming to IEEE 802.11 standards (such as those defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).

[0081] The wireless communication device 500 may be or may include a chip, system-on-a-chip (SoC), chipset, package, or device that includes one or more modems 502 (e.g., a Wi-Fi (compliant with IEEE 802.11) modem). In some implementations, the one or more modems 502 (collectively, "modem 502") additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compatible modem). In some implementations, the wireless communication device 500 also includes one or more radio components 504 (collectively, "radio components 504"). In some implementations, the wireless communication device 500 also 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").

[0082] Modem 502 may include intelligent hardware blocks or devices, such as, for example, application-specific integrated circuits (ASICs). Modem 502 is generally configured to implement a PHY layer. For example, modem 502 is configured to modulate packets and output modulated packets to radio component 504 for transmission over a wireless medium. Modem 502 is similarly configured to receive modulated packets received by radio component 504 and demodulate these packets to provide demodulated packets. In addition to modulators and demodulators, modem 502 may also include digital signal processing (DSP) circuitry, automatic gain control (AGC), encoders, decoders, multiplexers, and demultiplexers. For example, when in transmit mode, data obtained from processor 506 is provided to encoders, which encode the data to provide coded bits. These coded bits are then mapped to points in a modulation cluster (using a selected MCS) to provide modulated symbols. Subsequently, the modulated symbols can be mapped to a number N SS A spatial flow or a number N STS A space-time stream. Subsequently, the modulated symbols in the corresponding space stream or space-time stream can be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuitry for windowing and filtering on Tx. The digital signal can then be provided to a digital-to-analog converter (DAC). The resulting analog signal can then be provided to an up-converter and finally to the radio component 504. In the implementation involving beamforming, the modulated symbols in the corresponding space stream are pre-coded via a guiding matrix before being provided to the IFFT block.

[0083] When in receive mode, the digital signal received from radio component 504 is provided to a DSP circuitry system configured to capture the received signal, for example, by detecting the presence of the signal and estimating the initial timing and frequency offset. The DSP circuitry system is further configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correcting I / Q imbalance), and applying digital gain to ultimately obtain a narrowband signal. The output of the DSP circuitry system can then be fed to an AGC, configured to use information extracted from the digital signal (e.g., in one or more received training fields) to determine an appropriate gain. The output of the DSP circuitry system is also coupled to a demodulator configured to extract modulated symbols from the signal and, for example, calculate the log-likelihood ratio (LLR) at each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder configured to process the LLR to provide decoded bits. The decoded bits from all spatial streams are then fed to a demultiplexer for demultiplexing. The demultiplexed bits can then be descrambled and provided to the MAC layer (processor 506) for processing, evaluation, or interpretation.

[0084] Radio component 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 combined into one or more transceivers. For example, the RF transmitter and receiver may include various DSP circuitry systems, each including at least one power amplifier (PA) and at least one low-noise amplifier (LNA). The RF transmitter and receiver may further be coupled to one or more antennas. For example, in some implementations, wireless communication device 500 may include or be coupled to multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). Symbols output from modem 502 are provided to radio component 504, which then transmits these symbols via the coupled antennas. Similarly, symbols received via the antennas are acquired by radio component 504, which then provides these symbols to modem 502.

[0085] Processor 506 may include intelligent hardware blocks or devices designed to perform the functions described herein, such as, for example, processing cores, processing blocks, central processing units (CPUs), microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), discrete gate or transistor logic, discrete hardware components, or any combination thereof. Processor 506 processes information received via radio component 504 and modem 502, and processes information to be output via modem 502 and radio component 504 for transmission over a wireless medium. For example, processor 506 may implement a control plane and a 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 frame decoding and decoding, spatial multiplexing, space-time block decoding (STBC), beamforming, and OFDMA resource allocation, and other operations or techniques. In some implementations, processor 506 may generally control modem 502 to cause the modem to perform the various operations described above.

[0086] Memory 508 may include tangible storage media, such as random access memory (RAM) or read-only memory (ROM), or combinations thereof. Memory 508 may also store non-transitory processor or computer-executable software (SW) code containing instructions that, when executed by processor 506, cause the processor to perform various operations described herein for wireless communication, including MDPU, frame or packet generation, transmission, reception, and interpretation. For example, the various functions of the components disclosed herein, or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein, may be implemented as one or more modules of one or more computer programs.

[0087] Figure 6A A block diagram of example AP 602 is shown. For example, AP 602 could be a reference... Figure 1 The described example implementation of AP 102. AP 602 includes a wireless communication device (WCD) 610. For example, the wireless communication device 610 may be a reference... Figure 5 An example implementation of the described wireless communication device 500 is provided. AP 602 also includes a plurality of antennas 620 coupled to the wireless communication device 610 for transmitting and receiving wireless communications. In some implementations, AP 602 additionally includes an application processor 630 coupled to the wireless communication device 610, and a memory 640 coupled to the application processor 630. AP 602 further includes at least one external network interface 650 that enables AP 602 to communicate with a core network or backhaul network to obtain access to external networks, including the Internet. For example, external network interface 650 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Some of the components described above may communicate directly or indirectly with other components via at least one bus. AP 602 also includes a housing that encloses at least portions of the wireless communication device 610, application processor 630, memory 640, and antennas 620 and external network interface 650.

[0088] Figure 6B A block diagram of example STA 604 is shown. For example, STA 604 could be a reference... Figure 1 The described example implementation of STA 104. STA 604 includes a wireless communication device 615. For example, the wireless communication device 615 may be a reference... Figure 5An example implementation of the described wireless communication device 500. STA 604 also includes one or more antennas 625 coupled to the wireless communication device 615 for transmitting and receiving wireless communications. STA 604 additionally includes an application processor 635 coupled to the wireless communication device 615, and a memory 645 coupled to the application processor 635. In some implementations, STA 604 further includes a user interface (UI) 655 (such as a touchscreen or keyboard) and a display 665, which may be integrated with the UI 655 to form a touchscreen display. In some implementations, STA 604 may further include one or more sensors 675 (such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors). Some of the components described above may communicate directly or indirectly with other components via at least one bus. STA 604 also includes a housing that encloses at least portions of the wireless communication device 615, application processor 635, memory 645, and antennas 625, UI 655, and display 665.

[0089] As discussed, compared to an AP, a wireless STA can have limited filtering capabilities that allow the reception of UL data on one communication link to interfere with the transmission of DL data on another communication link. Therefore, a STA operating as an NSTR soft AP MLD associated with both the main and non-main links can not simultaneously receive UL data on the non-main link and transmit DL data on the main link. Similarly, a STA operating as an NSTR soft AP MLD can not simultaneously receive UL data on the main link and transmit DL data on the non-main link.

[0090] Various aspects of this disclosure recognize the importance of reducing or eliminating cross-link interference associated with NSTR soft AP MLDs. In some implementations, an NSTR soft AP MLD associated with a primary link and a secondary link can advertise the complete profiles of both the primary and secondary links only on the primary link. The NSTR soft AP MLD can also advertise updates to one or more BSS parameters of the primary and secondary links only on the primary link. Advertising the complete profiles of both links of the NSTR soft AP MLD on the primary link allows some wireless communication devices operating on the primary link to discover and associate with the NSTR soft AP MLD on one or both of the primary and secondary links without scanning or probing the secondary link. In some implementations, non-traditional devices operating on the primary link may be able to decode or parse the complete profiles of both the primary and secondary links, while traditional devices operating on the primary link may be able to decode or parse only the complete profile of the primary link. Therefore, traditional devices operating on the primary link may not be able to discover or associate with NSTR soft AP MLDs on the secondary link. Furthermore, by not advertising a complete profile of any link on non-primary links, legacy devices operating on non-primary links may not be able to discover or associate with the NSTR soft AP MLD on the non-primary link. In this way, various aspects of the subject matter disclosed herein can restrict communication between the NSTR soft AP MLD and legacy devices to the primary link.

[0091] Various aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. By restricting communication between the NSTR soft AP MLD and legacy devices to the main link (and thereby preventing legacy devices from communicating with the NSTR soft AP MLD on non-main links), the NSTR soft AP MLD can prevent legacy devices from transmitting UL data on non-main links, while the NSTR soft AP MLD transmits DL data to one or more associated devices on the main link. In this way, implementations of the subject matter disclosed herein can reduce the likelihood of cross-link interference caused by UL transmission on non-main links or otherwise interfere with DL transmission from the NSTR soft AP MLD on the main link.

[0092] Figure 7A A sequence diagram depicting an example multi-link communication 700 according to some implementations is shown. Figure 7A In the example, multi-link communication 700 can be performed between a STA operating as an NSTR soft AP MLD and one or more associated STAs (only one associated STA is shown for simplicity). The STA can be any suitable wireless communication device, including, for example, those described above respectively. Figure 1 and Figure 6BThe STAs 104 and 604 are described. In some implementations, the NSTR soft AP MLD may include a first AP associated with the primary link and may include a second AP associated with a non-primary link. In some instances, the first AP and the second AP may be soft APs implemented by STAs operating as NSTR soft AP MLDs.

[0093] The NSTR soft AP MLD can be configured to broadcast complete profiles of both the main link and the non-main link in one or more frames transmitted only on the main link. Therefore, some wireless communication devices within the range of the NSTR soft AP MLD can obtain complete profiles of both the main link and the non-main link when operating on the main link. Specifically, in some instances, non-traditional devices that obtain complete profiles of both the main link and the non-main link can be associated with the NSTR soft AP MLD on one or both of the main link and the non-main link, while traditional devices that receive complete profiles broadcast on the main link can be associated with the NSTR soft AP MLD only on the main link. In this way, communication between traditional devices and the NSTR soft AP MLD can be restricted to the main link, which in turn reduces cross-link interference on the main link caused by transmissions from traditional devices on the non-main link.

[0094] exist Figure 7A In the example, the NSTR soft AP MLD transmits only the first frame on the primary link, which includes the full profile of the primary link and indicates the full profile of the non-primary link. In some implementations, the full profile of the corresponding link may include at least the beacon interval, capability information, service set identifier (SSID), supported rates, timing synchronization function (TSF) value, and one or more additional fields or elements associated with the discovery of the corresponding link. In some other implementations, the full profile of the corresponding link may be defined as including all capabilities, operating parameters, and discovery information that will be included in the beacon frame or probe response broadcast by the AP operating the BSS on the corresponding link.

[0095] In some implementations, the primary link can be configured as a full BSS, and non-primary links can be configured as pseudo-BSSs sharing one or more capabilities and operational parameters with the primary link. For example, in some aspects, a non-primary link can have the same SSID, TSF value, and beacon interval as the primary link, and therefore inherit these values ​​from the primary link. Consequently, 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 the non-primary link may differ from those of the primary link, and therefore may not be inherited from the primary link. Examples of such capabilities and operational parameters include (but are not limited to) EDCA parameters, bandwidth, number of spatial streams (NSS), puncturing mode, BSSID, and MLD capabilities.

[0096] The first frame can be any suitable frame that carries or indicates a complete profile of both the primary and non-primary links. In some implementations, the first frame can be a beacon frame, probe response frame, association response frame, or reassociation response frame. In some instances, the NSTR soft AP MLD can also transmit only Fast Initial Link Establishment (FILS) discovery frames, Traffic Indication Mapping (TIM) frames, and action frames (such as notification frames) on the primary link. The NSTR soft AP MLD can also transmit only group-addressed frames (such as multicast frames) on the primary link. In this way, the NSTR soft AP MLD can restrict communication with legacy devices to the primary link.

[0097] In some implementations, the first frame contains a frame body comprising multiple fields and elements, followed by a multi-link (ML) element. These fields and elements may carry a complete profile of the primary link. The ML element may include per-STA profile sub-elements indicating a complete profile of a non-primary link. The ML element may also include a common information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) field, which indicates an update to one or more BSS parameters associated with the primary link. In some instances, 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 of the NSTR soft AP MLD. For example, one or more bits of the multi-link control field or common information field may be set to a first value to indicate that the first frame is transmitted from the first AP of the NSTR soft AP MLD, or to a second value to indicate that the first frame is transmitted from an AP associated with the AP MLD (or other simultaneous transmit-receive (STR) device).

[0098] The body of the first frame may also include a Reduced Neighbor Report (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, which includes the Basic Service Set Identifier (BSSID) of the non-primary link and one or more MLD parameters. As discussed, the non-primary link may be configured as a pseudo-BSS inheriting some capabilities and operational parameters from the primary link, and therefore the TBTT Information field associated with the non-primary link may not include one or more subfields, such as (but not limited to) a TBTT Offset subfield, a Short SSID subfield, a BSS Parameter subfield, and a PSD subfield. Omitting these subfields reduces the size or length of the TBTT Information field in the Neighbor AP Information field associated with the non-primary link compared to the TBTT Information field in the Neighbor AP Information field associated with other communication links. Thus, the size or length of the TBTT Information field in the Neighbor AP Information field associated with the non-primary link can be used by the receiving STA to determine whether to transmit the first frame from the first AP in the NSTR soft AP MLD. In some respects, the TBTT information fields associated with non-primary links include a 6-octet BSSID field and a 3-octet MLD parameter field, and are 9 octets in length.

[0099] In some implementations, the Neighbor AP Information Field may include a TBTT Information Field Type set to indicate that the Neighbor AP Information Field carries only information associated with the non-primary link. In some instances, the Neighbor AP Information Field may have a new or undefined type, and the TBTT Information Field Type may be set to 1 or a reserved value to indicate a new or undefined type of TBTT Information Field. In this way, the receiving STA can determine the first AP transmission from the NSTR soft AP MLD by parsing the TBTT Information Field Type in the Neighbor AP Information Field associated with the non-primary link. In some instances, non-traditional devices may be aware of the new types of TBTT Information Fields disclosed herein and can therefore obtain a complete profile of both the primary and non-primary links from the first frame. Conversely, traditional devices may not understand the new types of TBTT Information Fields disclosed herein and may therefore ignore the TBTT Information Fields in the Neighbor AP Information Fields associated with the non-primary link. In this way, aspects of the subject matter disclosed herein can prevent at least some traditional devices from discovering the non-primary link based on information received on the primary link.

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

[0101] The STA receives the first frame transmitted by the NSTR soft AP MLD on the main link and can parse the first frame to obtain complete profiles for both the main and non-main links. The STA can use the complete profile for the main link to discover or associate with the NSTR soft AP MLD on the main link, and can use the complete profile for the non-main link to discover or associate with the NSTR soft AP MLD on a non-main link. In some instances, the STA can transmit a response frame on the main link, which includes capability information, operating parameters, and other information that can be used for association and authentication processes with the NSTR soft AP MLD. After the STA associates with the NSTR soft AP MLD on the main link, the STA and the NSTR soft AP MLD can exchange data, control signals, and other information with each other on the main link. For STA implementations that are STR-capable multi-radio devices, the STA can also associate with NSTR soft AP MLDs on non-main links and exchange data, control signals, and other information with them on non-main links.

[0102] In some instances, one or more BSS parameters associated with the primary link can be changed or updated. Similarly, one or more BSS parameters associated with a non-primary link can be changed or updated. In some implementations, the BSS parameters for the corresponding communication link may include one or more of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

[0103] In some implementations, the NSTR soft AP MLD can generate and transmit a second frame only on the primary link. This second frame indicates updates to one or more BSS parameters on the primary link and updates to one or more BSS parameters on non-primary links. Specifically, when the NSTR soft AP MLD receives or determines an update to one or more BSS parameters on the primary link, it can increment the BPCC value associated with the primary link and insert the incremented BPCC value into the BPCC subfield of the common information field of the ML element carried in the second frame. When the NSTR soft AP MLD receives or determines an update to one or more BSS parameters on a non-primary link, it can increment the BPCC value associated with the non-primary link and insert the incremented BPCC value into the BPCC subfield of the MLD parameter field in the neighbor AP information field of the RNR element carried in the second frame. In some instances, the NSTR soft AP MLD can also set the Key Update Flag (CUF) carried in the capability information field of the second frame based on the incremented BPCC value associated with the non-primary link.

[0104] The STA receives the second frame and can parse it to obtain BSS parameter updates for both the primary and secondary links. In some implementations, the second frame can be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some instances, the second frame may include updated BSS parameters for one or both of the primary and secondary links. In other implementations, the second frame can be an action frame (such as a notification frame). In some aspects, the updated one or more BSS parameters for the corresponding communication link may be part of a partial profile of the corresponding communication link. For example, in some aspects, the NSTR soft APMLD can transmit an unsolicited broadcast probe response frame on the primary link, which carries a partial profile of each communication link with updated one or more BSS parameters. Thereafter, the STA can transmit UL data to the NSTR soft APMLD at least on the primary link, and the NSTR soft APMLD can transmit DL data to the STA at least on the primary link.

[0105] Figure 7B A sequence diagram depicting another example of multi-link communication 710 according to some implementations is shown. Figure 7B In the example, you can refer to Figure 7A The described NSTR soft AP MLD performs multi-link communication 710 with one or more associated STAs (only one associated STA is shown for simplicity). The NSTR soft AP MLD may include a first AP associated with a primary link and may include a second AP associated with a non-primary link. In some instances, the first AP and the second AP may be soft APs implemented by STAs operating as NSTR soft AP MLDs.

[0106] For reference Figure 7A The NSTR soft AP MLD discussed here can broadcast the complete profiles of both the primary and non-primary links only on the primary link. Broadcasting the complete profiles of both links only on the primary link allows non-traditional devices to discover and associate with the NSTR soft AP MLD on one or both of the primary and non-primary links, while preventing traditional devices from discovering and associating with the NSTR soft AP MLD on the non-primary link.

[0107] In some instances, the NSTR soft AP MLD can determine that non-primary links are unavailable. Non-primary links may be unavailable for multi-link communication between the NSTR soft AP MLD and its associated STA for various reasons. For example, a non-primary link may be unavailable when used as a cellular link in a Long Term Evolution (LTE) Radio Access Network (RAN) or a Fifth Generation (5G) New Radio Access Network (NR). As another example, a non-primary link may be unavailable when it is placed in a power-saving mode (including sleep or hibernation mode) to reduce power consumption or extend the battery life of the STA operating as the NSTR soft AP MLD. As yet another example, a non-primary link may be unavailable when used for peer-to-peer (P2P) or STA-to-STA communication.

[0108] All aspects of this disclosure recognize that the primary link may be better suited to notify STAs associated with the NSTR soft AP MLD of non-primary link unavailability. In some implementations, based on non-primary link unavailability, the NSTR soft AP MLD may generate a first frame including a Key Update Flag (CUF) set to 1 and a No Transmit (DNT) bit set to 1. In some instances, the CUF may be carried in the capability information field of the first frame, and the DNT bit may be carried in the per STA profile sub-element or RNR element of the first frame.

[0109] The NSTR soft AP MLD can transmit the first frame to the STA (and other associated devices operating on the main link) solely on the main link. In some implementations, the NSTR soft AP MLD can operate as a single-link device on the main link, even when a non-main link is unavailable. For example, in some instances, the NSTR soft AP MLD can put a soft AP (or other transmit link, receive link, signal processing circuitry, etc.) associated with a non-main link into sleep, hibernation, or power-off state while remaining fully operational on the main link. In this single-link state, the NSTR soft AP MLD can operate the BSS as a single-link BSS on the main link, while reducing (or virtually eliminating) the power consumption associated with operating on a non-main link.

[0110] The STA receives the first frame and can parse it to obtain an indication that the non-primary link is unavailable. In some instances, the first frame can be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In other instances, the first frame can be an action frame (such as a notification frame). When the NSTR soft AP MLD operates as a single-link device on the primary link, the NSTR soft AP MLD and its associated STAs can exchange frames with each other only on the primary link.

[0111] When an NSTR soft AP MLD operates as a single-link device on the primary link, a non-primary link may become available. The NSTR soft AP MLD can determine that the non-primary link is available and can transmit an indication of its availability. In some instances, the NSTR soft AP MLD can reset the DNT bit associated with the non-primary link and can transmit a second frame carrying at least the reset DNT bit only on the primary link. In some implementations, based on the determination that the non-primary link is available, the NSTR soft AP MLD can operate as a multi-link device on both the primary and non-primary links. For example, the NSTR soft AP MLD can return a soft AP (or other transmit link, receive link, signal processing circuitry, etc.) associated with a non-primary link to a fully operational state. In this multi-link state, the NSTR soft AP MLD can operate the BSS on both the primary and non-primary links.

[0112] The STA receives the second frame and can parse it to obtain an indication that the non-primary link is available. In some instances, the second frame can be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In other instances, the second frame can be an action frame (such as a notification frame). Afterward, the NSTR soft AP MLD and its associated STA can exchange frames with each other on one or both the primary and non-primary links.

[0113] In some implementations, determining the unavailability of a non-primary link may include, or may be associated with, placing the non-primary link into a power-saving state (including sleep or hibernation), which can reduce power consumption and extend the battery life of the NSTR soft AP MLD. In some other implementations, determining the unavailability of a non-primary link may include, or may be associated with disabling the non-primary link. In some instances, the NSTR soft AP MLD can disable a non-primary link by removing it from the multilink context associated with both the primary and non-primary links, thereby preventing its associated STAs from using the non-primary link. When the non-primary link becomes available, the NSTR soft AP MLD can return or add the non-primary link to the multilink context, thereby allowing its associated STAs to use the non-primary link (as a supplement to the primary link). In some aspects, the NSTR soft AP MLD can transmit a first notification frame on the primary link to indicate that the non-primary link is no longer included in the multilink context, and can transmit a second notification frame on the primary link to indicate that the non-primary link has been added to the multilink context. In some other instances, the NSTR soft AP MLD can disable a non-primary link by remapping the Traffic Identifier (TID) from the non-primary link to the primary link. When a non-primary link becomes available, the NSTR soft AP MLD can remap TIDs from the primary link to the non-primary link. In some aspects, the NSTR soft AP MLD can transmit a first notification frame on the primary link to indicate that TIDs attached to the non-primary link have been remapped to the primary link, and can transmit a second notification frame on the primary link to indicate that some TIDs attached to the primary link have been remapped to the non-primary link.

[0114] Figure 8A A sequence diagram depicting an example multi-link communication 800 according to some other implementations is shown. Figure 8A In the example, you can refer to Figure 7A and Figure 7B The described NSTR soft AP MLD performs multi-link communication 800 with one or more associated STAs (only one associated STA is shown for simplicity). The NSTR soft AP MLD may include a first AP associated with a primary link and may include a second AP associated with a non-primary link. In some instances, the first AP and the second AP may be soft APs implemented by STAs operating as NSTR soft AP MLDs.

[0115] As discussed, the NSTR soft AP MLD can advertise complete profiles of both the primary and non-primary links in one or more frames transmitted only on the primary link. Thus, non-traditional devices operating on the primary link can discover non-primary links, while traditional devices operating on either the primary or non-primary link may not be able to discover the non-primary links associated with the NSTR soft AP MLD. In this way, communication between the NSTR soft AP MLD and traditional devices can be restricted to the primary link, which in turn reduces the likelihood of UL transmissions on non-primary links when the NSTR soft AP MLD transmits DL data to one or more associated devices on the primary link. This, in turn, prevents or reduces cross-link interference on DL transmissions on the primary link caused by concurrent UL transmissions on non-primary links.

[0116] As discussed, an NSTR soft AP MLD can transmit management frames that include the complete profile of the primary link and indicate the complete profile of the non-primary link, all on the primary link only. The STA receives the management frames and can use the complete profile of the primary link to associate and authenticate with the NSTR soft AP MLD on the primary link. In some instances, the STA can use the complete profile of the non-primary link to associate and authenticate with the NSTR soft AP MLD on the non-primary link.

[0117] In some implementations, the NSTR soft AP MLD can instruct the STA to exchange Prepare to Transmit (RTS) and Clear to Transmit (CTS) frames with the NSTR soft AP MLD before transmitting UL data to the NSTR soft AP MLD. In some instances, the NSTR soft AP MLD can transmit a frame on the main link that includes instructions to perform RTS / CTS frame switching before transmitting UL data to the NSTR soft AP MLD. In some other instances, the NSTR soft AP MLD can instruct the STA to perform RTS / CTS frame switching during its association with the NSTR soft AP MLD before transmitting UL data to the NSTR soft AP MLD.

[0118] The STA receives the instruction. At a later time, such as when the STA has queued UL data to be transmitted, the STA can transmit an RTS frame to the NSTR soft AP MLD on the primary link. The NSTR soft AP MLD receives the RTS frame, determines that the non-primary link is available, and transmits a CTS frame to the STA on both the primary and non-primary links. The STA receives the CTS frame on both the primary and non-primary links and determines that the non-primary link is available based on the receipt of the CTS frame on both the primary and non-primary links. The STA transmits one or more UL PPDUs to the NSTR soft AP MLD on one or both of the primary and non-primary links. In some instances, transmitting a CTS frame to the STA on both the primary and non-primary links allows the STA to link the non-primary link and the primary link together.

[0119] The NSTR soft AP MLD can later determine that a non-primary link is unavailable. In some implementations, based on the determination that a non-primary link is unavailable, the NSTR soft AP MLD can set the CUF to 1 and the DNT bit to 1. In some instances, based on receiving an RTS frame from the STA, the NSTR soft AP MLD can indicate the unavailability of a non-primary link by transmitting a CTS frame only on the primary link. For example, when the STA already has queued UL data, the STA transmits another RTS frame to the NSTR soft AP MLD on the primary link. The NSTR soft AP MLD receives this RTS frame and, based on the unavailability of the non-primary link, transmits a CTS frame to the STA only on the primary link. The STA receives this CTS frame and, based on the fact that it only receives the CTS frame on the primary link, determines that the non-primary link is unavailable. The STA then transmits one or more UL PPDUs to the NSTR soft AP MLD only on the primary link.

[0120] In some other implementations, the NSTR soft AP MLD can perform channel handover operations based on determining that a non-primary link is unavailable. For example, in some instances, the NSTR soft AP MLD can concurrently switch the primary link from the first wireless channel to the second wireless channel with switching 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 band, and the second wireless channel may be located in the 5 GHz band. In other aspects, the first wireless channel may be located in the 5 GHz band, and the second wireless channel may be located in the 6 GHz band. In some other aspects, the first wireless channel may be located in one of the 2.4 GHz band, the 5 GHz band, or the 6 GHz band, and the second wireless channel may be located in the other of the 2.4 GHz band, the 5 GHz band, or the 6 GHz band.

[0121] The NSTR soft AP MLD can use any suitable rules or mechanism to concurrently switch channels on the primary and non-primary links. In some implementations, when performing a channel switching operation, the NSTR soft AP MLD can use a Channel Switching Announcement (CSA) element or an Extended Channel Switching Announcement (eCSA) element carried in the body of management frames (such as beacon frames, probe response frames, association response frames, or reassociation response frames) transmitted on the primary link.

[0122] Figure 8B A sequence diagram depicting another example of multi-link communication 810 according to some other implementations is shown. Figure 8B In the example, you can refer to Figure 7A and Figure 7B The described NSTR soft AP MLD performs multi-link communication 810 with one or more associated STAs (only one associated STA is shown for simplicity). The NSTR soft AP MLD may include a first AP associated with the primary link and may include a second AP associated with a non-primary link. In some instances, the first AP and the second AP may be soft APs implemented by STAs operating as NSTR soft AP MLDs. As discussed, the NSTR soft AP MLD may advertise profiles of both the primary link and the non-primary link only on the primary link.

[0123] In some implementations, the NSTR soft AP MLD transmits only the first frame on the primary link. This first frame includes a complete profile of the primary link and MLD information shared by the primary and non-primary links. In some instances, the first frame may include a frame body containing multiple fields and elements, followed by ML elements. These fields and elements may carry a complete profile of the primary link. ML elements may include shared MLD information. That is, the ML elements carried in the first frame may not include link information about non-primary links. In some instances, shared MLD information may include (but is not limited to) an MLD Media Access Control (MAC) address field, a link ID information field, a BPCC field, a synchronization delay field, an Enhanced Multilink (EML) capability field, and an MLD capability field. The MLD MAC address field may include the MAC address of the NSTR soft AP MLD. The BPCC field may indicate an update to one or more BSS parameters associated with the primary link.

[0124] The STA receives the first frame transmitted on the main link and can parse the first frame to obtain the complete profile of the main link and MLD shared information. The STA can use the complete profile of the main link to discover or associate with the NSTR soft AP MLD on the main link, and can use the MLD shared information to determine whether to request a complete profile of a non-main link from the AP MLD.

[0125] The STA transmits a second frame on the primary link, which includes a request for a complete profile of the non-primary link. In some instances, the second frame may be a probe request frame. In other instances, the second frame may be an association request frame. In still other instances, the second frame may be a reassociation request frame.

[0126] The NSTR soft AP MLD receives the second frame and parses a request for a complete profile of the non-primary link. In response to this request, the NSTR soft AP MLD transmits a third frame indicating the complete profile of the non-primary link only on the primary link. In some implementations, the body of the third frame may include ML elements and RNR elements. The ML element may carry a per-STA profile sub-element indicating the complete profile of the non-primary link. The RNR element may include a neighbor AP information field associated with the non-primary link, which includes the non-primary link's BSSID and one or more MLD parameters. In some instances, the MLD parameter field of the TBTT information field carried in the neighbor AP information field may include a PBCC field, which carries a value indicating whether any of the BSS parameters of the non-primary link has been updated. In some other instances, the value indicating whether any of the BSS parameters of the non-primary link has been updated may be carried in another suitable field, element, or header of the third frame.

[0127] For reference Figure 7A The primary link discussed can be configured as a full BSS, and non-primary links can be configured as pseudo-BSSs sharing at least some capabilities and operational parameters with the primary link. In some instances, non-primary links can have the same SSID, TSF value, and beacon interval as the primary link and can inherit these values ​​from the primary link. Non-primary links can also inherit the primary link's TBTT offset, short SSID, BSS parameters, and PSD limits. Therefore, the TBTT offset, short SSID, BSS parameters, and PSD subfields may not exist in the TBTT information field carried in the neighbor AP information field associated with the non-primary link, thereby reducing the length or size of the corresponding RNR element.

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

[0129] Figure 9A A timing diagram depicting an example multi-link communication 900 according to some implementations is shown. Figure 9A In the example, you can refer to Figure 7A , Figure 7B , Figure 8A or Figure 8BThe described NSTR soft APMLD performs multilink communication 900 between two associated wireless stations STA1 and STA2. STAs can be any suitable wireless communication device, including, for example, those described above respectively. Figure 1 and Figure 6B The STAs 104 and 604 are described. An NSTR soft AP MLD may include a first AP associated with a primary link and may include a second AP associated with a non-primary link. In some instances, the first and second APs may be soft APs implemented by STAs operating as NSTR soft AP MLDs. In some implementations, STA1 is a legacy device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and STA2 is a non-legacy device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0130] Before time t0, the NSTR soft AP MLD uses an appropriate channel access mechanism (such as EDCA) to contend for channel access to the primary link and obtains a transmission opportunity (TXOP) on the primary link. After obtaining a TXOP on the primary link, the NSTR soft AP MLD can also obtain channel access to non-primary links. In some instances, obtaining channel access to non-primary links can be based on obtaining channel access to the primary link or a TXOP. In some implementations, the NSTR soft AP MLD can restrict transmissions on non-primary links to individually addressed frames.

[0131] At time t0, the NSTR soft AP MLD transmits only the first beacon frame 901 on the primary link, which includes the complete profile of the primary link and indicates the complete profile of the non-primary link. The primary link can be configured as a full BSS, and the non-primary link can be configured as a pseudo BSS that inherits one or more capabilities and operating parameters from the primary link. For example, in some respects, the non-primary link can inherit the SSID, TSF value, and beacon interval from the primary link.

[0132] Beacon frame 901 includes a frame body comprising multiple fields and elements, followed by an ML element. These fields and elements may carry a complete profile of the primary link. The ML element may carry per-STA profile sub-elements indicating a complete profile of a non-primary link. The ML element may include a common information field carrying a BPCC field indicating an update to one or more BSS parameters associated with the primary link. In some instances, 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 soft AP MLD. For example, one or more bits of the multi-link control field or common information field may be set to a first value to indicate that the first beacon frame 901 is transmitted from the first AP of the NSTR soft AP MLD, or may be set to a second value to indicate that the first beacon frame 901 is transmitted from an AP associated with a simultaneous transmit-receive (STR) device (such as an AP MLD).

[0133] The first beacon frame 901 may also include an RNR element carrying a neighbor AP information field associated with a non-primary link. The neighbor AP information field may carry a TBTT information field including the BSSID of the non-primary link and one or more MLD parameters. In some instances, 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 instances, one or more values ​​indicating an update to one or more BSS parameters associated with the non-primary link may be carried in another suitable field, element, or header of the first beacon frame 901.

[0134] STA1 and STA2 receive the first beacon frame 901 on the primary link and can parse the first beacon frame 901 to obtain complete profiles of the primary and non-primary links. In some implementations, each of STA1 and STA2 can parse or decode the complete profile of the primary link carried in the fields and elements contained in the body of the first beacon frame 901. As a non-traditional device, STA2 may also be able to parse or decode the complete profile of the non-primary link indicated in the ML elements of the first beacon frame 901. As a traditional device, STA1 may not be able to parse or decode one or more portions of the ML elements carried in the first beacon frame 901, and therefore may not be able to obtain the capabilities, operating parameters, and other discovery information associated with the non-primary link from the first beacon frame 901. STA1 may also not be able to parse or decode one or more portions of the RNR elements carried in the first beacon frame 901. Therefore, while STA2 can use the information obtained from the first beacon frame 901 to discover and associate with the NSTR soft AP MLD on both the primary and non-primary links, STA1 can use the information obtained from the first beacon frame 901 to discover and associate with the NSTR soft AP MLD only on the primary link. In this way, communication between the NSTR soft AP MLD and STA1 (and other conventional devices associated with the NSTR soft AP MLD) can be restricted to the primary link.

[0135] At time t1, the NSTR soft AP MLD transmits the first DL PPDU 911 to STA1 on the primary link and concurrently transmits the second DL PPDU 912 to STA2 on a non-primary link. In some instances, the NSTR soft AP MLD may use a first set of antenna resources to transmit DL PPDU 911 to a first set of STAs (such as STA1) on the primary link and may use a second set of antenna resources to transmit DL PPDU 912 to a second set of STAs (such as STA2) on a non-primary link.

[0136] Between times t1 and t2, STA1 receives the first DL PPDU 911 on the main link, and STA2 receives the second DL PPDU 912 on the non-main link. The concurrent transmission of DL PPDUs 911 and 912 on the main and non-main links prevents wireless communication devices (such as STA1 and STA2) associated with the NSTR soft AP MLD from transmitting UL data to the NSTR soft AP MLD on both the main and non-main links between times t1 and t2.

[0137] In some instances, the NSTR soft AP MLD uses a suitable channel access mechanism to contend for channel access on the primary link between times t2 and t3 to obtain another TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR soft AP MLD can obtain channel access on a non-primary link and acquire the TXOP on the non-primary link. In other instances, the NSTR soft AP MLD can retain the TXOPs acquired on the primary and non-primary links between times t0 and t1, without having to contend for channel access between times t2 and t3.

[0138] At time t3, the NSTR soft AP MLD transmits the second beacon frame 902 only on the primary link. In some implementations, the second beacon frame 902 may be similar to the first beacon frame 901, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link. In some other implementations, the second beacon frame 902 may include less information than the first beacon frame 901. For example, in some instances, the second beacon frame 902 may carry or indicate a partial profile of one or both of the primary and non-primary links. In some other instances, the second beacon frame 902 may carry the complete or partial profile of the primary link and may not include the capabilities or operational parameters of the non-primary link. In some implementations, the second beacon frame 902 may be similar to the reference frame, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link. Figure 8B The first frame as described.

[0139] At time t4, the NSTR soft AP MLD transmits DL PPDU 921 to STA1 on the main link. STA1 can receive DL PPDU 921 on the main link between times t4 and t5. Various aspects of this disclosure recognize that cross-link interference caused by the transmission of DL PPDU 921 on the main link can lead to a "deafness" period on the non-main link, during which the NSTR soft AP MLD may be unable to receive or correctly decode UL transmissions on the non-main link. In some implementations, during the transmission of DL PPDU 921 on the main link, the NSTR soft AP MLD can put the non-main link into a deafness state 914. When in deafness state 914, the non-main link may be unavailable for communication between the NSTR soft AP MLD and its associated STA. Specifically, in some aspects, STA2 (and other wireless communication devices associated with the NSTR soft AP MLD) may not be allowed to transmit UL data on the non-main link during deafness state 914. In this way, UL transmissions that NSTR soft APMLD may fail to receive or correctly decode due to cross-link interference caused by the transmission of DLPPDU 921 on the main link can be prevented until the DL transmission ends.

[0140] The deaf state 914 can have any suitable duration. In some instances, the duration of the deaf state 914 can be time-aligned with the transmission duration of the DL PPDU 921 on the primary link. In other instances, the duration of the deaf state 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 the deaf state 914. In some implementations, the guard time can be selected to prevent cross-link interference from affecting (or reducing) DL communication transmitted on non-primary links. For example, in some instances, the duration of the guard time can be configured to ensure that the first and last symbols of the DL PPDU 921 do not interfere with UL transmissions on non-primary links.

[0141] After the transmission of DL PPDU 921 ends, the NSTR soft AP MLD restores the non-primary link from the deaf state 914. The NSTR soft AP MLD can use any suitable deaf recovery rule or mechanism to restore the non-primary link from the deaf state 914. In some implementations, the NSTR soft AP MLD may transmit an indication of the availability of the non-primary link on the primary link based on restoring the non-primary link. In implementations where the NSTR soft AP MLD removes the non-primary link from the multilink context when the non-primary link is placed in the deaf state 914 (and thus becomes unavailable), restoring the non-primary link from the deaf state 914 may include adding the non-primary link to the multilink context. In some aspects, the NSTR soft AP MLD may transmit a notification frame on the primary link to indicate that the non-primary link has been added to the multilink context. In the implementation of the NSTR soft AP MLD, remapping TIDs from the non-primary link to the primary link when a non-primary link is placed in a deaf state 914 (and thus becomes unavailable), restoring the non-primary link from the deaf state 914 may include remapping TIDs from the primary link to the non-primary link. In some aspects, the NSTR soft AP MLD may transmit notification frames on the primary link to indicate that some TIDs attached to the primary link have been remapped to the non-primary link.

[0142] At time t6, STA1 transmits UL PPDU 922 to the NSTR soft AP MLD on the primary link, and STA2 transmits UL PPDU 923 to the NSTR soft AP MLD on the non-primary link. The NSTR soft AP MLD receives UL PPDU 922 and 923 between times t6 and t7. The concurrent transmission of UL PPDU 922 and 923 on the primary and non-primary links prevents the NSTR soft AP MLD from transmitting DL data on both the primary and non-primary links between times t6 and t7, thus avoiding the need to disable the non-primary link between times t6 and t7.

[0143] In some instances, the NSTR soft AP MLD uses a suitable channel access mechanism to contend for channel access to the primary link between time t7 and t8 to obtain another TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR soft AP MLD can obtain channel access to a non-primary link and obtain the TXOP on the non-primary link.

[0144] At time t8, the NSTR soft AP MLD transmits only the third beacon frame 903 on the primary link. In some implementations, the third beacon frame 903 may be similar to the first beacon frame 901, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link. In some other implementations, the third beacon frame 903 may be similar to the second beacon frame 902, for example, by carrying less information than the first beacon frame 901.

[0145] At time t9, STA1 transmits the UL PPDU 931 to the NSTR soft AP MLD on the main link. At times t9 and t... 10 During this period, the NSTR soft AP MLD receives UL PPDU 931 on the main link. All aspects of this disclosure recognize that cross-link interference caused by the transmission of UL PPDU 931 on the main link can interfere with DL transmissions on non-main links. In some implementations, during the transmission of DL PPDU 931 on the main link, the NSTR soft AP MLD places the non-main link into a deaf state 932. While in deaf state 931, the non-main link may be unavailable for communication between the NSTR soft AP MLD and its associated STA. In some implementations, the NSTR soft AP MLD may not transmit DL data on the non-main link during deaf state 932. In this way, DL transmissions on non-main links sensitive to cross-link interference caused by the transmission of UL PPDU 931 on the main link can be prevented or delayed until the deaf state 932 expires. In some instances, STA2 (and other wireless communication devices associated with the NSTR soft AP MLD) may not be allowed to transmit UL data on the non-main link during deaf state 932.

[0146] The deaf state 932 can have any suitable duration. In some instances, the duration of the deaf state 932 can be time-aligned with the transmission duration of the UL PPDU 931 on the primary link. In some other instances, the duration of the deaf state 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 deaf state 932. In some implementations, the guard time can be selected to prevent cross-link interference from affecting (or reducing) DL communication transmitted on the non-primary link. For example, in some instances, the duration of the guard time can be configured to ensure that DL transmissions on the non-primary link do not interfere with the first or last symbol of the UL PPDU 931. After the transmission of the UL PPDU 931 ends, or after the deaf state 932 expires, the NSTR soft AP MLD restores the non-primary link from the deaf state 932.

[0147] Figure 9B A timing diagram depicting example multi-link communication 940 according to some other implementations is shown. In some implementations, it can be found in reference... Figure 9A The described NSTR soft AP MLD performs multi-link communication 940 between wireless stations STA1 and STA2. In some other implementations, see reference... Figure 7A , Figure 7B , Figure 8A or Figure 8B The described NSTR soft AP MLD performs multi-link communication 940 with associated wireless stations STA1 and STA2. STAs can be any suitable wireless communication device, including, for example, those described above respectively. Figure 1 and Figure 6B The STAs 104 and 604 are described. An NSTR soft AP MLD may include a first AP associated with a main link and may include a second AP associated with a non-main link. In some instances, the first and second APs may be soft APs implemented by STAs operating as NSTR soft AP MLDs. As discussed, STA1 is a legacy device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and STA2 is a non-legacy device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0148] Before time t0, the NSTR soft AP MLD contends for channel access to the primary link using an appropriate channel access mechanism (such as EDCA) and obtains the TXOP on the primary link. After obtaining the TXOP on the primary link, the NSTR soft AP MLD can also obtain channel access to non-primary links. In some instances, obtaining channel access to non-primary links can be based on obtaining channel access or the TXOP on the primary link. In some implementations, the NSTR soft AP MLD can restrict transmissions on non-primary links to individually addressed frames.

[0149] At time t0, the NSTR soft AP MLD transmits the first beacon frame 941 only on the primary link. The first beacon frame 941 may include the complete profile of the primary link and may also indicate the complete profile of the non-primary link. As discussed, the primary link may be configured as a full BSS, and the non-primary link may be configured as a pseudo BSS that inherits one or more capabilities and operating parameters from the primary link. For example, in some aspects, the non-primary link may have the same SSID, TSF value, and beacon interval as the primary link, and may inherit the SSID, TSF value, and beacon interval from the primary link.

[0150] In some implementations, the first beacon frame 941 can be similar to Figure 9A The first beacon frame 901, or 941, may include a frame body comprising multiple fields and elements, followed by an ML element. These fields and elements may carry a complete profile of the primary link. The ML element may carry per-STA profile sub-elements indicating a complete profile of a non-primary link. The ML element may include a common information field carrying a BPCC field indicating an update to one or more BSS parameters of the primary 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 soft AP 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 including the BSSID of the non-primary link and one or more MLD parameters. In some instances, 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. In some other instances, the value indicating an update to one or more BSS parameters on a non-primary link may be carried in another suitable field, element, or header of the first beacon frame 941.

[0151] STA1 and STA2 receive the first beacon frame 941 on the primary link and can parse beacon frame 941 to obtain complete profiles of the primary and non-primary links. In some implementations, each of STA1 and STA2 can parse or decode the complete profile of the primary link carried in the fields and elements contained in the body of the first beacon frame 941. As a non-traditional device, STA2 may also be able to parse or decode the complete profile of the non-primary link indicated in the ML element of the first beacon frame 941. As a traditional device, STA1 may not be able to parse or decode one or more portions of the ML element carried in the first beacon frame 941, and therefore may not be able to obtain non-primary link capabilities, operating parameters, and other discovery information from the first beacon frame 941. STA1 may also not be able to parse or decode one or more portions of the RNR element carried in the first beacon frame 941. Therefore, while STA2 can use the information obtained from the first beacon frame 941 to discover and associate with the NSTR soft AP MLD on both the primary and non-primary links, STA1 can use the information obtained from the first beacon frame 941 to discover and associate with the NSTR soft AP MLD only on the primary link. In this way, communication between the NSTR soft AP MLD and STA1 (and other conventional devices) can be restricted to the primary link.

[0152] At time t1, the NSTR soft AP MLD concurrently transmits the first trigger frame 951 on the main link with the transmission of the second trigger frame 952 on the non-main link. The first trigger frame 951 can solicit UL transmission from the first group of STAs (including STA1) on the main link, and the second trigger frame 952 can solicit UL transmission from the second group of STAs (including STA2) on the non-main link.

[0153] Between times t2 and t3, STA1 transmits a triggered (TB)PPDU 961 to the NSTR soft AP MLD on the primary link based on receiving the first trigger frame 951, and STA2 transmits TB PPDU 962 to the NSTR soft AP MLD on the non-primary link based on receiving the second trigger frame 952. The concurrent transmission of TB PPDU 961 and 962 from STA1 and STA2 on the primary and non-primary links respectively prevents the NSTR soft AP MLD from transmitting DL data on both the primary and non-primary links between times t2 and t3, thus avoiding the need to disable the non-primary link between times t2 and t3.

[0154] In some implementations, NSTR soft AP MLDs can establish coordinated TWT sessions on both the primary and non-primary links. (Although this is not explicitly stated in the original text...) Figure 9BAs shown, a TWT session on the primary link may include one or more service periods (SPs) during which the NSTR soft AP MLD can schedule transmissions to and from STA1 or the first group of STAs on the primary link. Similarly, a TWT session on a non-primary link may include one or more SPs during which the NSTR soft AP MLD can schedule transmissions to and from STA2 or the second group of STAs on the non-primary link. In some instances, the NSTR soft AP MLD can synchronize the TWT SPs of corresponding TWT sessions established on the primary and non-primary links. For example, coordinating corresponding TWT sessions or TWT SPs on the primary and non-primary links allows the NSTR soft AP MLD to concurrently schedule TB PPDU 961's UL transmission from STA1 on the primary link with TB PPDU 962's UL transmission from STA2 on the non-primary link. In this way, TB PPDU 961's transmission from STA1 on the primary link can be time-aligned with TB PPDU 962's transmission from STA2 on the non-primary link.

[0155] In some instances, the NSTR soft AP MLD uses a suitable channel access mechanism (such as EDCA) to contend for channel access to the primary link between times t3 and t4, and acquires the TXOP on the primary link. After acquiring the TXOP on the primary link, the NSTR soft AP MLD can acquire channel access to a non-primary link and acquire the TXOP on the non-primary link. In other instances, the NSTR soft AP MLD can retain the TXOP acquired on the primary and non-primary links between times t0 and t1, and can avoid contending for channel access between times t3 and t4.

[0156] At time t4, the NSTR soft AP MLD transmits the second beacon frame 942 only on the primary link. In some implementations, the second beacon frame 942 may be similar to the first beacon frame 941, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link. In some other implementations, the second beacon frame 942 may include less information than the first beacon frame 941. For example, in some instances, the second beacon frame 942 may carry or indicate a partial profile of one or both of the primary and non-primary links. In some other instances, the second beacon frame 942 may carry the complete or partial profile of the primary link and may not include capabilities or operational parameters associated with the non-primary link. In some implementations, the second beacon frame 942 may be similar to the reference frame, for example, by carrying or indicating only the BSSID and MLD common parameters of the non-primary link. Figure 8B The first frame as described.

[0157] At time t5, the NSTR soft AP MLD transmits the third trigger frame 953 on the non-primary link. The third trigger frame 953 solicits UL transmission from STA2 (or from the second group of STAs) on the non-primary link. Between times t6 and t7, STA2, based on receiving the third trigger frame 953, transmits TB PPDU 963 to the NSTR soft AP MLD on the non-primary link. Figure 9B In the example, STA1 transmits an unsolicited UL PPDU 971 to the NSTR soft AP MLD on the primary link between times t6 and t7. The transmissions of UL PPDU 971 and TBPPDU 963 from STA1 and STA2 on the primary and non-primary links respectively prevent the NSTR soft AP MLD from transmitting DL data on both the primary and non-primary links between times t6 and t7, thus avoiding the need to disable the non-primary link between times t6 and t7.

[0158] In some implementations, the NSTR soft AP MLD can establish independent TWT sessions on non-primary links to schedule TBPPDU 963 transmissions to the NSTR soft AP MLD. Although for simplicity... Figure 9B As shown, however, a standalone TWT session on a non-primary link may include one or more SPs, during which the NSTR soft AP MLD may schedule UL transmissions from STA2 or DL ​​transmissions to STA2 (and other associated devices) on a non-primary link.

[0159] At time t8, the NSTR soft AP MLD transmits the first DL PPDU 981 to STA1 on the primary link and concurrently transmits the second DL PPDU 982 to STA2 on the non-primary link. Between times t8 and t9, STA1 receives the first DL PPDU 981 on the primary link, and STA2 receives the second DL PPDU 982 on the non-primary link. The NSTR soft AP MLD does not receive any UL communication between times t8 and t9, and therefore the concurrent transmission of DL PPDUs 981 and 982 on the primary and non-primary links respectively may not result in any cross-link interference caused by the UL transmission between times t8 and t9.

[0160] In some implementations, the NSTR soft AP MLD can establish a coordinated TWT SP on the primary and secondary links to schedule the transmission of DL PPDU 981 and 982 to STA1 and STA2 on the primary and secondary links, respectively. In this way, the NSTR soft AP MLD can ensure that STA1 and STA2 are woken up to receive the transmissions of DL PPDU 981 and 982, respectively. In some instances, the TWT SP on the secondary link can be synchronized with the TWT SP on the primary link, ensuring that the DL transmissions on the primary and secondary links are time-aligned. In some instances, the NSTR soft AP MLD can use a first set of antenna resources to transmit DL PPDU 981 to the first group of STAs (including STA1) on the primary link, and can use a second set of antenna resources to transmit DL PPDU 982 to the second group of STAs (including STA2) on the secondary link.

[0161] At time t 10 The NSTR soft AP MLD transmits only the third beacon frame 943 on the primary link. In some implementations, the third beacon frame 943 may be similar to the first beacon frame 941, for example, by carrying the complete profile of the primary link and indicating the complete profile of the non-primary link. In some other implementations, the third beacon frame 943 may be similar to the second beacon frame 942, for example, by carrying less information than the first beacon frame 941.

[0162] At time t 11 STA1 transmits the UL PPDU 991 to the NSTR soft AP MLD on the main link. The NSTR soft AP MLD can transmit the UL PPDU 991 to the NSTR soft AP MLD at time t. 11 and t 12 The NSTR soft AP MLD receives UL PPDU 991 on the main link. Various aspects of this disclosure recognize that cross-link interference caused by the transmission of UL PPDU 991 on the main link can lead to periods of deafness on non-main links. In some implementations, during the transmission of UL PPDU 991 on the main link, the NSTR soft AP MLD can place the non-main link into a deaf state 992. When in deaf state 992, the non-main link may be unavailable for communication between the NSTR soft AP MLD and its associated STA. In some implementations, the NSTR soft AP MLD can prevent the transmission of DL data on the non-main link during deaf state 992. In this way, DL transmission on the non-main link, which is sensitive to cross-link interference caused by the transmission of UL PPDU 991 on the main link, can be prevented or delayed until the deaf state 992 expires. In some instances, STA2 (and other wireless communication devices associated with the NSTR soft AP MLD) may not be allowed to transmit UL data on the non-main link during deaf state 992.

[0163] The deaf state 992 can have any suitable duration. In some instances, the duration of the deaf state 992 can be time-aligned with the transmission duration of the UL PPDU 991 on the primary link. In some other instances, the duration of the deaf state 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 suitable for the deaf state 992. In some implementations, the guard time can be selected to prevent cross-link interference from affecting (or reducing) DL communication transmitted on the non-primary link. For example, in some instances, the duration of the guard time can be configured to ensure that DL transmissions on the non-primary link do not interfere with the first or last symbol of the UL PPDU 991. After the transmission of the UL PPDU 991 ends, or after the deaf state 992 expires, the NSTR soft AP MLD restores the non-primary link from the deaf state 992.

[0164] Figure 10A An example management frame 1000A, according to some implementation, can be used for wireless communication supporting NSTR soft AP MLD. Management frame 1000A can 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 can be... Figure 7A The first or second frame Figure 7B The first or second frame Figure 8A frames, Figure 8B The third frame Figure 9A beacon frames or Figure 9B An example implementation of a beacon frame. For ease of explanation, some information elements of frame 1000A may also be referred to as "field", "subfield", "element" or "subelement", which are considered interchangeable terms for the purposes of this discussion.

[0165] Frame 1000A is shown as including multiple elements and fields 1010, Reduced Neighbor Report (RNR) element 1020, Capability and Operational Parameters 1030, and Basic Multilink (ML) element 1040. Elements and fields 1010 may carry a complete profile of the primary link. RNR element 1020 may include one or more AP entries 1022. Each AP entry in AP entry 1022 may be associated with a corresponding AP in the AP MLD and may carry or indicate one or more parameters of the corresponding AP. In some implementations, one or more parameters may include the BSSID and MLD parameters of the corresponding AP. In some instances, the corresponding AP entry 1022 may not include one or more of the TBTT offset, short SSID, BSS parameters, or PSD limits of the corresponding non-primary link. Capability and Operational Parameters 1030 may include any number of capability and operation parameters associated with the primary link. ML element 1040 may include common information 1042 and several per-STA profile sub-elements 1044(1)-1044(n). Shared information 1042 may include MLD parameters and other information shared by the primary link and one or more non-primary links. Each of the sub-elements 1044(1)-1044(n) of each STA profile may be associated with the corresponding non-primary link of the AP MLD and may carry or indicate the complete profile of the corresponding non-primary link.

[0166] Figure 10B Another example management frame, based on some implementations, can be used for multi-link communication with an NSTR soft AP MLD. Management frame 1000B can 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 can be... Figure 8B Example implementation of the first frame. For ease of explanation, some information elements of frame 1000A may also be referred to as "field", "subfield", "element" or "subelement", which are considered interchangeable terms for the purposes of this discussion.

[0167] Frame 1000B is shown as including multiple elements and fields 1010, RNR element 1020, capability and operational parameters 1030, and basic ME element 1050. Elements and fields 1010 may carry a complete profile of the primary link. RNR element 1020 may include one or more AP entries 1022. Each AP entry in AP entry 1022 may be associated with a corresponding AP in the AP MLD and may carry or indicate one or more parameters of the corresponding AP. In some implementations, one or more parameters may include the BSSID and MLD parameters of the corresponding AP. In some instances, the corresponding AP entry 1022 may not include one or more of the TBTT offset, short SSID, BSS parameters, or PSD limits of the corresponding non-primary link. Capability and operational parameters 1030 may include any number of capabilities and operational parameters associated with the primary link. ML element 1050 may include shared information 1042. Shared information 1042 may include MLD parameters and other information shared by the primary link and one or more non-primary links associated with the AP MLD.

[0168] Figure 11A Example RNR element 1100 for use in multi-link communication is shown according to some implementations. In some implementations, RNR element 1100 may be respectively referenced... Figure 10A and Figure 10B The example implementation of RNR element 1020 for example management frames 1000A and 1000B is described. In some instances, RNR element 1100 may be included in frames such as (but not limited to) beacon frames, probe response frames, association response frames, or reassociation response frames transmitted from the AP MLD. For ease of interpretation, some informational elements of RNR element 1100 may be referred to as "field", "subfield", "element", or "subelement", and these terms are considered interchangeable for the purposes of this discussion.

[0169] RNR element 1100 can be used to indicate channel information, parameters, and other information related to one or more APs attached to the AP MLD. As shown in the figure, RNR element 1100 includes an element ID field 1102, a length field 1104, and one or more neighbor AP information fields 1106. The element ID field 1102 carries a value that identifies RNR element 1100. The length field 1104 carries a value indicating the length of RNR element 1100. Each neighbor AP information field 1106 carries information indicating the timing reference, operation category, channel number, and other parameters of the corresponding AP in the AP MLD.

[0170] As shown in the figure, the Neighbor AP Information field 1106 includes a TBTT information header 1111, an operation category 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 operation category field 1112 indicates the channel start frequency, which, together with the channel number field, indicates the primary channel of the BSS of the AP associated with the Neighbor AP Information field. The channel number field 1113 indicates the last known primary channel of the AP associated with the Neighbor AP Information field. The TBTT information set field 1114 contains one or more TBTT information fields carrying TBTT information, operation parameters, and MLD parameters for the AP associated with the Neighbor AP Information field.

[0171] In some implementations, RNR element 1100 may be extended to include a link ID field, which stores one or more unique link IDs that can be used to map entries in the neighbor AP information field 1106 to information stored in the per STA profile sub-element of the ML element. In some other implementations, RNR element 1100 may be extended to include a no-transmission (DNT) field, which may carry a DNT indication for the corresponding communication link. Furthermore, or in alternatives, one or more elements or fields of RNR element 1100 may be combined, added, removed, or modified.

[0172] Figure 11B An example TBTT message header 1120 based on some implementations is shown. In some instances, the TBTT message header 1120 can be... Figure 11A An example implementation of the TBTT information header 1111 is shown below. As illustrated, the TBTT information header 1120 includes a TBTT information field type subfield 1121, a filtered neighboring AP subfield 1122, a reserved subfield 1123, a TBTT information count subfield 1124, and a TBTT information length subfield 1125. The TBTT information field type subfield 1121 carries 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 to indicate that the TBTT information field has a new type or format associated with the NSTR device. In this way, a wireless communication device receiving an RNR element with a TBTT information field type subfield set to 1 or a reserved value can determine that the frame carrying the RNR element was transmitted by the NSTR device.

[0173] Except when the reduced neighbor report element is carried in the probe response frame transmitted by the TVHT AP, the filtered neighbor AP subfield 1122 is retained. The retained subfield 1123 includes one or more reserved bits or unused bits. The TBTT information count subfield 1124 indicates the number of TBTT information fields included in the TBTT information set field of the neighbor AP information field minus one. The TBTT information length subfield 1125 indicates the length of each TBTT information field included in the TBTT information set field of the neighbor AP information field.

[0174] Figure 11C Example TBTT information field 1130 is shown according to some implementations. In some instances, TBTT information field 1130 can be... Figure 11A This is an implementation of the TBTT information field carried in the TBTT information set field 1114. As shown in the figure, 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 parameter subfield 1134, a 20MHz PSD subfield 1135, and an MLD parameter subfield 1136. The neighboring AP TBTT offset subfield 1131 indicates the offset (in TU) between the next TBTT of the reported AP and the immediately preceding TBTT of the reporting AP. The optional BSSID subfield 1132 carries the BSSID of the reported AP. The optional short SSID subfield 1133 carries the shortened SSID of the reported AP. BSS Parameter subfield 1134 indicates one or more BSS parameters of the reported AP, such as (but not limited to) the OCT Recommendation subfield, the Same SSID subfield, multiple BSSID subfields, the Transmitted BSSID subfield, the ESS Membership subfield, the Unsolicited Probe Response Activity subfield, and the Co-located AP subfield. The 20MHz PSD subfield 1135 indicates the maximum transmission power of the corresponding AP on the primary 20MHz channel. In some instances, the Neighbor AP TBTT Offset subfield 1131, the Short SSID subfield 1133, the BSS Parameter subfield 1134, and the 20MHz PSD subfield 1135 can be omitted from the TBTT Information field 1130.

[0175] MLD parameter subfield 1136 includes the MLD ID subfield, Link ID subfield, BSS Parameter Change Count (BPCC) subfield, and Reserved subfield. The MLD ID subfield indicates the identifier of the AP MLD and can be used to identify a list of reported APs associated with the AP MLD. The Link ID subfield indicates the link identifier of the corresponding AP and is unique for that AP. The BSS Parameter Change Count subfield is an unsigned integer initialized to 0, which increments when a critical update occurs to the beacon frame of the reported AP. The Reserved subfield includes one or more reserved or unused bits.

[0176] Figure 12A An example multilink (ML) element 1200 for use in multilink communication is shown according to some implementations. In some implementations, ML element 1200 may be a reference... Figure 10A An example implementation of the basic ML element 1040 described herein. In some instances, the ML element 1200 may be included in frames such as (but not limited to) beacon frames, probe response frames, association response frames, or reassociation response frames transmitted from the NSTR soft AP MLD. For ease of interpretation, some information elements of the ML element 1200 may be referred to as "field", "subfield", "element", or "subelement", and these terms may be considered interchangeable for the purposes of this discussion.

[0177] 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. The element ID field 1201 and the element ID extension field 1203 carry values ​​indicating that element 1200 is an ML element and indicating the type of ML element. The length field 1202 carries values ​​indicating the length of ML element 1200. The multi-link control field 1204 carries information indicating the presence of various fields and subfields in the common information field 1205. The common information field 1205 carries information shared by one or more non-primary links associated with the AP MLD. The link information field 1206 carries information specific to each non-primary link associated with the AP MLD. In some instances, the link information field 1206 includes one or more per-STA profile sub-elements that can carry or indicate a complete profile of one or more corresponding non-primary links of the AP MLD (such as an NSTR soft AP MLD).

[0178] Figure 12B Example multilink control field 1210 is shown according to some implementations. In some instances, multilink control field 1210 can be... Figure 12AThis is an implementation of the multi-link control field 1204 of the ML element 1200. As shown, the multi-link control field 1210 includes a type field 1211, a reserved field 1212, and an existence bitmap field 1213. The type field 1211 is used to distinguish between various variants of the ML element 1200, such as the basic ML element and the probe request ML element. The reserved field 1212 includes one or more reserved bits or unused bits. The existence bitmap field 1213 is used to indicate the presence of various subfields in the common information field 1205 of the ML element 1200. For example, the existence bitmap field 1213 may indicate the presence of an MLD MAC address field, a link ID information field, a BSS parameter change count (BPCC) field 1223, a media synchronization delay information field, an enhanced multilink (EML) capability field, and an MLD capability field in the common information field 1205 of the ML element 1200.

[0179] Figure 12C The example shown is a shared information field 1220 based on some implementations. In some instances, the shared information field 1220 may be... Figure 12A This is an implementation of the common information field 1205 of the ML element 1200. As shown, the common information field 1220 includes an MLD MAC address field 1221, a link ID information field 1222, a BPCC field 1223, a media synchronization delay information field 1224, an enhanced multi-link (EML) capability field 1225, and an MLD capability field 1226. The MLD MAC address field 1221 carries the MAC address of the MLD (such as an NSTR soft AP MLD). The link ID information field 1222 carries the link identifier of the AP transmitting the ML element 1200. The BSS parameter change count (BPCC) field 1223 carries an unsigned integer initialized to 0, which increments when a critical update occurs to the operating parameters of the AP transmitting the basic variant ML element.

[0180] The Medium Synchronization Delay Information field 1224 carries a value indicating the duration of the Medium Synchronization Delay (MediumSyncDelay) timer. The EML Capability field 1225 contains several subfields for declaring the capabilities of EML Single Radio (SR) and EML Multiple Radio (MR) operations. The MLD Capability field 1226 indicates various capabilities of the MLD. In some instances, the MLD Capability field 1226 may indicate the maximum number of links supporting simultaneous transmission or reception of each frame, whether the MLD supports reception of frames carrying SRS control subfields, whether the MLD supports TID-to-link mapping negotiation, and the minimum frequency gap between any two links recommended by the non-AP MLD for STR operation.

[0181] Figure 12DExample per-STA profile element 1230 is shown according to some implementations. In some instances, per-STA profile element 1230 can be... Figure 12A This is an implementation of the per STA profile sub-element carried in the link information field 1206 of the ML element 1200. As shown, the per STA profile sub-element 1230 may include 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. The sub-element ID field 1231 carries a value indicating the type of the per STA profile sub-element 1230. The length field 1232 carries a value indicating the length of the per STA profile sub-element 1230. The STA control field 1233 carries information indicating the presence (or absence) of various fields and sub-fields in the STA profile field 1235. The STA information field 1234 carries information about the AP corresponding to the per STA profile sub-element 1230. The STA profile field 1235 carries information indicating the complete profile of the AP corresponding to the per STA profile sub-element 1230.

[0182] Figure 12E Example STA control field 1240 is shown according to some implementations. In some instances, STA control field 1240 can be... Figure 12DAn implementation of the STA control field 1233 of each STA profile sub-element 1230. As shown in the figure, the STA control field 1240 includes a link ID field 1241, a complete profile field 1242, a MAC address presence field 1243, a beacon interval presence field 1244, a DTIM information presence field 1245, 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 each STA profile sub-element 1230. The complete profile field 1242 carries a value indicating whether each STA profile sub-element 1230 carries the complete profile of the corresponding AP. The MAC address presence field 1243 carries a value indicating whether each STA profile sub-element 1230 carries the MAC address of the corresponding AP. The beacon interval presence field 1244 carries a value indicating whether the STA information field 1234 of each STA profile 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 each STA profile sub-element 1230 carries the corresponding AP's DTIM information. The NSTR link pair presence field 1246 carries a value indicating whether each STA profile element 1230 carries information about the communication link pair (such as the primary link and non-primary links) associated with the NSTR soft AP MLD. The NSTR bitmap size field 1247 carries a value indicating the size of the NSTR indicator bitmap field included in each STA profile element 1230.

[0183] Figure 12F Example STA information field 1250 is shown according to some implementations. In some instances, STA information field 1250 can be... Figure 12D An implementation of the STA information field 1234 of each STA profile sub-element 1230. 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. The MAC address field 1251 carries the MAC address of the AP corresponding to each STA profile sub-element 1230. The beacon interval field 1252 carries information indicating the beacon interval of the AP corresponding to each STA profile element 1230. The DTIM field 1253 carries information indicating the DTIM count and DTIM period of the AP corresponding to each STA profile element 1230. The NSTR link pair field 1254 carries information identifying the communication link pair associated with the AP corresponding to each STA profile element 1230. The NSTR bitmap field 1255 carries the NSTR bitmap of the AP corresponding to each STA profile element 1230.

[0184] Figure 13 A flowchart illustrating an example process 1300 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1300. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STAs 104 and 604) performs process 1300. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7A The described NSTR soft AP MLD execution process 1300.

[0185] In some implementations, in block 1302, process 1300 begins operating as an NSTR soft AP MLD associated with the primary and secondary links. In block 1304, process 1300 continues to transmit a frame only on the primary link, which includes a complete profile of the primary link and indicates a complete profile of the secondary link. The respective complete profiles for the primary and secondary links each include at least the 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 the discovery of the respective link. This frame is transmitted only on the primary link and can be a beacon frame, probe response frame, association response frame, or reassociation response frame. In some instances, the beacon interval, SSID, and TSF values ​​of the secondary link's complete profile are inherited from the primary link's complete profile. Thus, the beacon interval, SSID, and TSF values ​​of the secondary link may not be present in the frame.

[0186] In some implementations, the frame includes a frame body that comprises multiple fields and elements carrying a complete profile of the primary link, and a multi-link (ML) element carrying a per-STA profile sub-element indicating a complete profile of a non-primary link. The ML element includes a common information field carrying a BPCC field indicating an update to one or more BSS parameters associated with the primary link. One or more bits of the ML element's multi-link control field or common information field can indicate whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

[0187] The frame body may also include an RNR element carrying a neighbor AP information field associated with a non-primary link. The neighbor AP information field may carry a TBTT information field including the non-primary link's BSSID and one or more MLD parameters. In some instances, the non-primary link's TBTT offset, short SSID, BSS parameters, and PSD parameters may be inherited from the primary link. Therefore, the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and PSD subfield may be omitted from the TBTT information field in the neighbor AP information field associated with the non-primary link, thereby reducing the size and overhead of the RNR element. In some aspects, this reduced-size TBTT information field may be a new type of TBTT information field not defined by any of the existing revisions to the 802.11 wireless communication standard family. Thus, 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 only related to the non-primary link. In some instances, the TBTT information field type may be set to 1 or a reserved value to indicate this new or undefined type of TBTT information field. Setting the TBTT information field type to 1 or a reserved value can also indicate that the associated neighbor AP information field, and therefore the frame carrying the corresponding RNR element, is transmitted from the AP associated with the NSTR soft AP MLD.

[0188] In some implementations, the length of the TBTT information field indicates whether the frame was transmitted from the first AP of the NSTR soft AP MLD. In some instances, the TBTT information field is nine octets long. 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 a non-master link.

[0189] Figure 14 A flowchart illustrating an example process 1400 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1400. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 1400. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7A The described NSTR soft AP MLD execution process 1400.

[0190] In some implementations, it is possible Figure 13After the frame in box 1304 is transmitted, process 1400 is executed. For example, at box 1402, process 1400 begins by receiving an update for at least one BSS parameter among the BSS parameters associated with the non-primary link. At box 1404, process 1400 continues to increment the value of the BPCC field in the TBTT information field included in the RNR element of another frame based on the received update. At box 1406, process 1400 continues to set the Critical Update Flag (CUF) in the Capability Information field of the other frame based on the incremented value carried in the BPCC field. At box 1408, process 1400 continues to transmit the other frame only on the primary link, which indicates an update for at least one BSS parameter associated with the non-primary link. In some cases, this other frame may be a beacon frame, probe response frame, association response frame, reassociation response frame, or action frame (such as a notification frame).

[0191] In some implementations, BSS parameters may include at least one of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

[0192] Figure 15 A flowchart illustrating an example process 1500 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1500. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device operating within or on one of the described STAs 104 and 604 performs process 1500. In some instances, this can be performed by an AP MLD (such as referenced in the documentation). Figure 7A The described NSTR soft AP MLD execution process 1500.

[0193] In various implementations, it is possible Figure 13After the frame in block 1304 is transmitted, process 1500 is executed. For example, at block 1502, process 1500 begins by receiving updates to one or more BSS parameters associated with the non-primary link. At block 1504, process 1500 continues to transmit the updated one or more BSS parameters associated with the non-primary link only on the primary link. In some implementations, the updated one or more BSS parameters may be carried in a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other implementations, the updated one or more BSS parameters may be part of a partial profile of the non-primary link. In some instances, the NSTR soft AP MLD may transmit an unsolicited broadcast probe response frame on the primary link carrying a partial profile of the non-primary link (and thus indicating the updated one or more BSS parameters of the non-primary link).

[0194] Figure 16 A flowchart illustrating an example process 1600 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1600. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STAs 104 and 604) performs process 1600. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The described NSTR soft AP MLD execution process 1600.

[0195] In some implementations, in block 1602, process 1600 begins by operating as an NSTR soft AP MLD associated with the primary and non-primary links. In block 1604, process 1600 proceeds to determine that the non-primary link is unavailable. In block 1606, process 1600 continues to transmit a frame carrying an indication of the unavailability of the non-primary link only on the primary link. In some instances, this frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some other instances, this frame may be an action frame (such as a notification frame).

[0196] Non-primary links may be unavailable for various reasons. For example, when a non-primary link is used for a cellular link in a Long Term Evolution (LTE) Radio Access Network (RAN) or a Fifth Generation (5G) New Radio Access Network (NR), it may not be available for multi-link communication associated with the NSTR soft AP MLD. As another example, when a non-primary link is placed in a power-saving mode (including sleep or hibernation mode) for example to reduce power consumption or extend the battery life of the NSTR soft AP MLD, it may not be available for multi-link communication associated with the NSTR soft AP MLD. As yet another example, when a non-primary link is used for peer-to-peer (P2P) or STA-based communication, it may not be available for multi-link communication associated with the NSTR soft AP MLD.

[0197] Figure 17 A flowchart illustrating an example process 1700 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1700. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 1700. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The NSTR soft AP MLD execution process described is 1700.

[0198] In some implementations, it can be combined Figure 16 The transmission instructions in box 1606 are used to execute process 1700. For example, at box 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 instances, the DNT bit may be carried in each STA profile sub-element or RNR element in a frame transmitted on the primary link. In some other implementations, the NSTR soft AP MLD may also set the Key Update Flag (CUF) carried in the frame to a value of 1 based on the unavailability of the non-primary link. In some instances, the frame includes a capability information field carrying a CUF set to a value of 1.

[0199] Figure 18 The diagram illustrates an example process 1800 of wireless communication facilitating multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1800. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6BThe wireless communication device operating within or on one of the described STAs 104 and 604 performs process 1800. In some instances, this can be performed by the AP MLD (such as referenced in the image). Figure 7B The described NSTR soft AP MLD execution process 1800.

[0200] In some implementations, it is possible Figure 16 Process 1800 is executed after the transmission of the frame carrying the indication in block 1606. For example, at block 1802, process 1800 begins with operation as a single-link device on the main link based on the unavailability of the non-main link. In some aspects, when the non-main link is unavailable, the NSTR soft AP MLD can put the soft AP (or other transmission link, receive link, signal processing circuitry system, etc.) associated with the non-main link into a sleep, hibernation, or power-off state while remaining fully operable on the main link. In this single-link state, the NSTR soft AP MLD can operate the BSS as a single-link BSS on the main link while also reducing the power consumption associated with operation on the non-main link.

[0201] Figure 19 The diagram illustrates an example process 1900 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 1900. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device operating within or on one of the described STAs 104 and 604 performs process 1900. In some instances, this can be accomplished by the AP MLD (such as referenced in the original text). Figure 7B The NSTR soft AP MLD execution process described is 1900.

[0202] In some implementations, it is possible Figure 18When the NSTR soft AP MLD in box 1802 operates as a single-link device, process 1900 is executed. For example, at box 1902, process 1900 begins by determining that a non-primary link is available when operating as a single-link device on the primary link. At box 1904, process 1900 continues by resetting the Non-Transmit (DNT) bit to a value of 0 based on the availability of the non-primary link. At box 1906, process 1900 continues by transmitting the reset DNT bit in another frame only on the primary link, which includes a per-STA profile sub-element or a Reduced Neighbor Report (RNR) element carrying the reset DNT bit with a value of 0. In some instances, this other frame may be one of a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other instances, this other frame may be an action frame (such as a notification frame).

[0203] Figure 20 The diagram illustrates a flowchart of an example process 2000 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2000. In some implementations, this can be performed by a STA (such as those described above, each referred to separately). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2000. In some instances, this can be accomplished by the AP MLD (such as referenced in the documentation). Figure 7B The described NSTR soft AP MLD execution process 2000.

[0204] In some implementations, it is possible Figure 16 Process 1600 is followed by process 2000. For example, at block 2002, process 2000 begins by determining that a non-primary link is available after a transmission indication. At block 2004, process 2000 continues to transmit an indication of the availability of the non-primary link only on the primary link. At block 2006, process 2000 continues to operate as a multi-link device on both the primary and non-primary links based on the availability of the non-primary link. In some instances, this indication may be transmitted on the primary link in a suitable management frame such as (but not limited to) a beacon frame, probe response frame, association response frame, or reassociation response frame. In some other instances, this indication may be transmitted on the primary link in a suitable action frame such as a notification frame. In some aspects, when (or within a configured time) a non-primary link becomes available, the NSTR soft AP MLD may power on the soft AP associated with the non-primary link. In this multi-link state, the NSTR soft AP MLD may operate the BSS on both the primary and non-primary links.

[0205] Figure 21A flowchart illustrating an example process 2100 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2100. In some implementations, this can be performed by a STA (such as those described above, referred to separately). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2100. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The NSTR soft AP MLD execution process described is 2100.

[0206] In some implementations, it is possible Figure 16 After determining the unavailability of the non-primary link in block 1604, process 2100 is executed. For example, at block 2102, process 2100 begins by disabling the non-primary link or placing it into a power-saving state based on its unavailability. In some instances, the NSTR soft AP MLD can also place the soft AP (or other transmit link, receive link, signal processing circuitry, etc.) associated with the non-primary link into a sleep, hibernation, or power-off state while remaining fully operational on the primary link. In this way, the NSTR soft AP MLD can reduce the power consumption associated with operating on the non-primary link and can also reduce cross-link interference caused by UL transmissions on the non-primary link.

[0207] Figure 22 A flowchart illustrating an example process 2200 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2200. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2200. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The NSTR soft AP MLD execution process described is 2200.

[0208] In some implementations, procedure 2200 can be Figure 21One implementation of disabling a non-primary link is shown in box 2102. For example, at box 2202, process 2200 begins by removing a non-primary link from the multilink context associated with the NSTR soft AP MLD. In some instances, when a non-primary link is removed from the multilink context, the wireless communication device associated with the NSTR soft AP MLD may be unable to access or utilize the non-primary link. In some aspects, the NSTR soft AP MLD may transmit a notification frame on the primary link to indicate that the non-primary link is no longer included in the multilink context.

[0209] Figure 23 The diagram illustrates a flowchart of an example process 2300 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2300. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2300. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The NSTR soft AP MLD execution process described is 2300.

[0210] In some implementations, it is possible Figure 22 Procedure 2300 is executed after the removal of the non-primary link from the multilink context in box 2202. For example, at box 2302, procedure 2300 begins by determining that the non-primary link is available after its removal from the multilink context. At box 2304, procedure 2300 continues by adding the non-primary link to the multilink context based on its determined availability. In some instances, once the non-primary link is added to the multilink context, wireless communication devices associated with the NSTR soft AP MLD can access and utilize the non-primary link without deassociating or reassociating with the NSTR soft AP MLD. In some aspects, the NSTR soft AP MLD can transmit a notification frame on the primary link to indicate that the non-primary link has been added to the multilink context.

[0211] Figure 24 A flowchart illustrating an example process 2400 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2400. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6BThe wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2400. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The described NSTR soft AP MLD execution process 2400.

[0212] In some implementations, procedure 2400 can be Figure 21 Another implementation of disabling non-primary links is shown in box 2102. For example, at box 2402, process 2400 begins by remapping traffic identifiers (TIDs) from non-primary links to primary links. As an example, the primary link may initially be associated with or attached to a first TID value indicating a first traffic type or traffic flow, and the non-primary link may initially be associated with or attached to a second TID value indicating a second traffic type or traffic flow. When the non-primary link is unavailable, the NSTR soft AP MLD may remap the second TID value from the non-primary link to the primary link. In this way, the traffic type or traffic flow indicated by the second TID value can be transmitted on the primary link (rather than the non-primary link). In some aspects, the NSTR soft AP MLD may transmit a notification frame on the primary link to indicate that a TID attached to a non-primary link has been remapped to the primary link.

[0213] Figure 25 The diagram illustrates a flowchart of an example process 2500 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2500. In some implementations, this can be performed by a STA (such as those described above, referred to separately). Figure 1 and Figure 6B The wireless communication device that operates or operates within a STA (either of the described STA 104 and 604) performs process 2500. In some instances, this can be performed by an AP MLD (such as referenced in the documentation). Figure 7B The described NSTR soft AP MLD) execution process 2500.

[0214] In some implementations, it is possible Figure 24 After remapping the TID from the non-primary link to the primary link in box 2402, process 2500 is executed. For example, at box 2502, process 2500 begins by determining that the non-primary link is available after disabling it. At box 2504, process 2500 continues by remapping the TID from the primary link to the non-primary link based on the availability of the non-primary link. Continue to refer to Figure 24In the described example, when a non-primary link becomes available, the NSTR soft AP MLD can remap the second TID value from the primary link to the non-primary link. In this way, the transmission of traffic types or traffic flows indicated by the second TID value can return to the non-primary link. In some aspects, the NSTR soft AP MLD can transmit notification frames on the primary link to indicate that some TIDs attached to the primary link have been remapped to the non-primary link.

[0215] Figure 26 A flowchart illustrating an example process 2600 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2600. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2600. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7B The NSTR soft AP MLD execution process described is 2600.

[0216] In some implementations, it is possible Figure 16 After the frame is transmitted in block 1606, process 2600 is executed. For example, at block 2602, process 2600 begins by simultaneously switching the primary link from the first channel to the second channel with switching the non-primary link from the second channel to the first channel. In some instances, the first channel is in one of the 5 GHz band or the 6 GHz band, and the second channel is in the other of the 5 GHz band or the 6 GHz band.

[0217] Figure 27 A flowchart illustrating an example process 2700 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2700. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device operating within or on one of the described STAs 104 and 604 performs process 2700. In some instances, this can be accomplished by the AP MLD (such as referenced in the documentation). Figure 8A The NSTR soft AP MLD execution process described is 2700.

[0218] In some implementations, at block 2702, process 2700 begins by receiving a Ready to Transmit (RTS) frame from the STAMLD on the primary link. At block 2704, process 2700 continues to transmit a Clear Transmit (CTS) frame to the STA MLD on both the primary and non-primary links based on the received RTS frame. At block 2706, process 2700 continues to receive one or more uplink (UL) physical layer protocol data units (PPDUs) from the STA MLD on both the primary and non-primary links. In some instances, the NSTR soft AP MLD can indicate the availability of the non-primary link by transmitting a CTS frame on both the primary and non-primary links. When the STA MLD receives a CTS frame on both the primary and non-primary links, the STA MLD can transmit UL data on both the primary and non-primary links. Conversely, when the STA MLD receives a CTS frame only on the primary link, the STA MLD can transmit UL data to the NSTR soft AP MLD only on the primary link.

[0219] Figure 28 A flowchart illustrating an example process 2800 of wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2800. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2800. In some instances, this can be performed by the STA MLD (such as referenced in the original text). Figure 8B The described STAMLD execution process 2800.

[0220] In some implementations, in block 2802, process 2800 begins by receiving a first frame only on the primary link from the NSTR soft AP MLD associated with both the primary and non-primary links. This first frame may include a complete profile of the primary link and MLD information shared by both the primary and non-primary links. The complete profile may include at least beacon interval, capability information, SSID, supported rate, TSF value, and one or more additional fields or elements associated with the discovery of the primary link. In block 2804, process 2800 continues by transmitting a second frame only on the primary link to the NSTR soft AP MLD, which requests a complete profile for the non-primary link. In block 2806, process 2800 continues by receiving a third frame only on the primary link from the NSTR soft AP MLD, which indicates a complete profile for the non-primary link. In some instances, the first frame may be one of a beacon frame, a probe response frame, an association response frame, or a 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 can be one of a probe response frame, an association response frame, or a reassociation response frame.

[0221] In some implementations, the first frame contains a frame body that includes multiple fields and elements carrying a complete profile of the primary link, and includes ML elements containing shared MLD information. The third frame may contain a frame body that includes ML elements carrying per-STA profile sub-elements indicating a complete profile of a non-primary 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 including the non-primary link's BSSID and one or more MLD parameters. In some instances, the non-primary link's TBTT offset, short SSID, BSS parameters, and PSD parameters can be inherited from the primary link. Therefore, the TBTT offset sub-field, short SSID sub-field, BSS parameter sub-field, and PSD sub-field can be omitted from the TBTT information field in the neighbor AP information field associated with the non-primary link, thereby reducing the size and overhead of the RNR element. In some aspects, the TBTT information field is nine octets long.

[0222] Figure 29 The diagram illustrates a flowchart of an example process 2900 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 2900. In some implementations, this can be performed by a STA (such as those described above, each referred to separately). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 2900. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 7A The NSTR soft AP MLD execution process described is 2900.

[0223] In some implementations, in block 2902, process 2900 begins operating as an NSTR soft AP MLD associated with both the primary and secondary links. In block 2904, process 2900 continues to transmit frames only on the primary link, including one or more timing parameters associated with the primary link, where the timing parameters for the secondary links are based on one or more timing parameters associated with the primary link. In some aspects, the timing parameters for the secondary links are inherited from the primary link. The frame can be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some instances, the primary link is associated with the Target Beacon Transmission Time (TBTT), and the secondary link can be a pseudo-BSS aligned to the TBTT of the primary link. One or more timing parameters can include at least one of a channel handover announcement, a silence period, or a beacon interval.

[0224] Figure 30 The diagram illustrates a flowchart of an example process 3000 for wireless communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 3000. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within a STA (either of the described STA 104 and 604) performs process 3000. In some instances, this can be accomplished by an APMLD (such as referenced...). Figure 9A The described NSTR soft AP MLD) execution process 3000.

[0225] In some implementations, in block 3002, process 3000 begins operating as an NSTR soft AP MLD associated with the primary and secondary links. In block 3004, process 3000 continues to acquire channel access on the primary link. In block 3006, process 3000 continues to transmit the first frame to the first associated STA on the primary link. In block 3008, process 3000 continues to put the secondary link into a deactivated state during the duration of frame transmission on the primary link. In block 3010, process 3000 continues to restore the secondary link from the deactivated state after frame transmission on the primary link has ended. In some implementations, the frame can be any suitable frame, including (but not limited to) management frames, control frames, or data frames.

[0226] Figure 31A flowchart illustrating an example process 3100 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 3100. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STAs 104 and 604) performs process 3100. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 9A The NSTR soft AP MLD execution process described is 3100.

[0227] In some implementations, it is possible Figure 30 After the non-primary link is restored in block 3010, process 3100 is executed. For example, at block 3102, process 3100 begins by obtaining channel access on the non-primary link based on channel access to the primary link. At block 3104, process 3100 continues concurrently with the transmission of the third frame to the first associated STA on the primary link and the transmission of the second frame to the second associated STA on the non-primary link. In some implementations, the NSTR soft AP MLD can synchronize the transmission of the second frame on the non-primary link with the transmission of the third frame on the primary link. In some instances, the first associated STA is a legacy device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and the second associated STA is a non-legacy device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0228] Figure 32 A flowchart illustrating an example process 3200 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations, is shown. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5 The described wireless communication device 500) executes process 3200. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 3200. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 9A The NSTR soft AP MLD execution process described is 3200.

[0229] In some implementations, it is possible Figure 30The process 3200 is executed after the non-primary link is restored in block 3010. For example, at block 3202, process 3200 begins by obtaining channel access on the non-primary link during at least a portion of the channel access obtained on the primary link. At block 3204, process 3200 continues by transmitting a second frame on the non-primary link to one or more second associated STAs during the transmission of the first frame on the primary link.

[0230] Figure 33 A flowchart illustrating an example process 3300 for wireless communication with an NSTR soft AP MLD, based on some implementation, is shown. This can be achieved by a wireless communication device (such as the one described above). Figure 5 The described wireless communication device 500) executes process 3300. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within a STA (either of the described STAs 104 and 604) performs process 3300. In some instances, this can be accomplished by an APMLD (such as referenced...). Figure 9B The NSTR soft AP MLD execution process described is 3300.

[0231] In some implementations, in block 3302, process 3300 begins operating as an NSTR soft AP MLD associated with the primary and secondary links. In block 3304, process 3300 continues to acquire channel access to the primary and secondary links. In block 3306, process 3300 continues to establish a Coordinated Target Waiting Time (TWT) session on the primary and secondary links. In block 3308, process 3300 continues to transmit a first trigger frame on the primary link, which solicits uplink (UL) transmissions from a first group of STAs on the primary link. In block 3310, process 3300 continues to transmit a second trigger frame on the secondary link concurrently with the transmission of the first trigger frame on the primary link, which solicits UL transmissions from a second group of STAs on the secondary link. In some instances, the coordinated TWT session may include one or more corresponding service periods (SPs) during which a corresponding STA or corresponding group of STAs may be scheduled or triggered for UL transmissions on the corresponding primary and secondary links.

[0232] Figure 34 The diagram illustrates a flowchart of an example process 3400 for wireless communication with an NSTR soft AP MLD, based on some implementation. This can be achieved by a wireless communication device (such as the one described above). Figure 5 The described wireless communication device 500) executes process 3400. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6BThe wireless communication device that operates or operates within a STA (either of the described STA 104 and 604) performs process 3400. In some instances, this can be performed by an APMLD (such as referenced...). Figure 9B The NSTR soft AP MLD execution process described is 3400.

[0233] In some implementations, it is possible Figure 33 Process 3400 is executed after the transmission trigger frames in blocks 3308 and 3310. For example, in block 3402, process 3400 may begin by receiving one or more first UL PPDUs from a first group of STAs on the primary link based on a first trigger frame. In block 3404, process 3400 continues by receiving one or more second UL PPDUs from a second group of STAs on a non-primary link based on a second trigger frame. In some instances, the transmission of first UL PPDUs from the corresponding first group of STAs and the transmission of second UL PPDUs from the corresponding second group of STAs may be synchronized with each other.

[0234] Figure 35 The diagram illustrates a flowchart of an example process 3500 for wireless communication with an NSTR soft AP MLD, based on some implementation. This can be achieved by a wireless communication device (such as the one described above). Figure 5 The described wireless communication device 500) executes process 3500. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within a STA (either of the described STA 104 and 604) performs process 3500. In some instances, this can be accomplished by an APMLD (such as referenced...). Figure 9B The described NSTR soft AP MLD execution process 3500.

[0235] In some implementations, it can be combined Figure 33 Process 3300 executes process 3500. For example, in block 3502, process 3500 may begin by synchronizing one or more TWT service periods on the non-master link with one or more corresponding TWT service periods on the master link. In this way, transmissions of one or more first UL PPDUs performed by the first group of STAs on the master link can be time-aligned with transmissions of one or more second UL PPDUs performed by the second group of STAs on the non-master link.

[0236] Figure 36 The diagram illustrates a flowchart of an example process 3600 for wireless communication supporting multi-link communication with an NSTR soft AP MLD, based on some implementations. This can be achieved by wireless communication devices (such as those mentioned above). Figure 5The described wireless communication device 500) executes process 3600. In some implementations, this can be performed by a STA (such as those described above, see below for details). Figure 1 and Figure 6B The wireless communication device that operates or operates within the STA (either of the described STA 104 and 604) performs process 3600. In some instances, this can be performed by the AP MLD (such as referenced in the documentation). Figure 9B The NSTR soft AP MLD execution process described is 3600.

[0237] In some implementations, it is possible Figure 34 Process 3600 is performed after receiving one or more first UL PPDUs and second UL PPDUs in blocks 3402 and 3404. For example, in block 3602, process 3600 may begin by transmitting one or more first downlink (DL) PPDUs to a first group of STAs on the primary link. In block 3604, process 3600 continues concurrently with transmitting one or more first DL PPDUs to the first group of STAs on the primary link and transmitting one or more second DL PPDUs to a second group of STAs on a non-primary link.

[0238] Figure 37 A block diagram of an example wireless communication device 3700 according to some implementations is shown. In some implementations, the wireless communication device 3700 is configured to perform... Figure 7A Communication 700, Figure 7B Communication 710 or Figure 8A The communication device 810. The wireless communication device 3700 can be the above reference. Figure 5 The described wireless communication device 500 is an example implementation. For example, the wireless communication device 3700 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem). In some implementations, the wireless communication device 3700 may be used in STAs (such as those described separately). Figure 1 and Figure 6B The device described is one of STA 104 and 604. In some other implementations, the wireless communication device 3700 may be a chip, SoC, chipset, package, or device including at least one antenna (such as...). Figure 6B The STA has an antenna 625. In various implementations, the wireless communication device 3700 may be an example of one or more of the NSTR soft AP MLDs described herein.

[0239] Wireless communication device 3700 includes a receiving component 3710, a communication manager 3720, and a transmitting component 3730. The communication manager 3720 further includes a channel access component 3721, a frame generation component 3722, a link profile component 3723, a link availability component 3724, a parameter update component 3725, and a timing and synchronization component 3726. Parts of one or more of these components may be implemented at least partially in hardware or firmware. In some implementations, at least some of components 3721, 3722, 3723, 3724, 3725, and 3726 are at least partially implemented as stored in memory (such as...). Figure 5 The software in the memory 508. For example, portions of one or more of components 3721, 3722, 3723, 3724, 3725, and 3726 may be implemented as operable by a processor (such as...) Figure 5 The processor 506) executes non-transitory instructions (or "code") to perform the functions or operations of the corresponding components.

[0240] The receiving component 3710 is configured to receive RX signals from other wireless communication devices on one or more wireless channels or links. The communication manager 3720 is configured to control or manage communication with other wireless communication devices. In some implementations, the channel access component 3721 contends for and obtains channel access to the primary link and / or non-primary link associated with the wireless communication device 3700. The frame generation component 3722 generates frames for transmitting discovery information, profile information, operating parameters, updates to operating parameters, link availability, link timing reference, and other suitable information regarding the MLD operating on the primary and non-primary links. The link profile component 3723 generates a complete or partial profile for one or more of the primary and non-primary links. The link availability component 3724 indicates whether the primary and / or non-primary links are available. The parameter update component 3725 determines changes to one or more parameters of the primary and non-primary links and transmits an indication of the parameter update. The timing and synchronization component 3726 generates a timing reference for the non-primary link relative to the primary link.

[0241] Transmission component 3730 is configured to transmit TX signals to one or more other wireless communication devices over a wireless channel. In some implementations, transmission component 3730 may transmit frames that include or indicate discovery information, profile information, operating parameters, updates to operating parameters, link availability, link timing references, and other suitable information about the primary and non-primary links associated with wireless communication device 3700.

[0242] Figure 38 A block diagram of another example wireless communication device 3800 according to some implementations is shown. In some implementations, the wireless communication device 3800 is configured to perform... Figure 8BThe communication device 810. The wireless communication device 3800 can be the above reference. Figure 5 The described wireless communication device 500 is an example implementation. For example, the wireless communication device 3800 may be a chip, SoC, chipset, package, or device including at least one processor and at least one modem (e.g., a Wi-Fi (IEEE 802.11) modem or a cellular modem). In some implementations, the wireless communication device 3800 may be used in STAs (such as those described separately). Figure 1 and Figure 6B The device described is one of STA 104 and 604. In some other implementations, the wireless communication device 3800 may be a chip, SoC, chipset, package, or device including at least one antenna (such as...). Figure 6B The STA (antenna 625). In various implementations, the wireless communication device 3800 may be one or more of the STA MLDs described herein.

[0243] Wireless communication device 3800 includes a receiving component 3810, a communication manager 3820, and a transmitting component 3830. The communication manager 3820 further includes a channel access component 3821, a frame generation component 3822, and a profile request component 3823. A portion of one or more of these components may be implemented at least partially in hardware or firmware. In some implementations, at least some of components 3821, 3822, and 3823 are implemented at least partially as software stored in memory (such as memory 508). For example, a portion of one or more of components 3821, 3822, and 3823 may be implemented as non-transitory instructions (or "code") executable by a processor (such as processor 506) to perform the function or operation of the respective component.

[0244] The receiving component 3810 is configured to receive RX signals from other wireless communication devices on one or more wireless channels or links. The communication manager 3820 is configured to control or manage communication with other wireless communication devices. In some implementations, the channel access component 3821 contends for and obtains channel access to the primary link and / or non-primary link associated with the AP MLD (such as an NSTR soft AP MLD). The frame generation component 3822 generates frames to carry the capabilities and operating parameters of the wireless communication device 3800. The profile request component 3823 generates a request for the AP MLD to provide a complete or partial profile of one or more of the primary and non-primary links.

[0245] Transmission component 3830 is configured to transmit TX signals to one or more other wireless communication devices over a wireless channel. In some implementations, transmission component 3830 may transmit frames that include or indicate capabilities, operating parameters, profile requests, and other suitable information about the primary and secondary links associated with the AP MLD.

[0246] Implementation examples are described in the following numbered clauses:

[0247] 1. A method for wireless communication by a wireless station (STA), comprising:

[0248] Operating as a Non-Simultaneous Transmit-Receive (NSTR) Soft Access Point (AP) Multilink Device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; and

[0249] Frames are transmitted only on the primary link, the frames including a complete profile of the primary link and indicating a complete profile of the non-primary link, the respective complete profiles of the primary link and the non-primary link each including 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 the discovery of the respective link.

[0250] 2. The method according to Clause 1, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

[0251] 3. The method according to any one or more of Clauses 1 to 2, wherein the beacon interval, the SSID, and the TSF value of the non-primary link are inherited from the primary link.

[0252] 4. The method according to any one or more of clauses 1 to 3, wherein the frame includes a frame body, the frame body comprising:

[0253] Multiple fields and elements, said multiple fields and elements carrying the complete profile of the main link; and

[0254] A multi-link (ML) element, the ML element carrying a per-STA profile sub-element indicating the full profile of the non-primary link.

[0255] 5. The method according to Clause 4, wherein the ML element further includes a shared information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the main link.

[0256] 6. The method according to any one or more of Clauses 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 soft AP MLD.

[0257] 7. The method according to any one or more of Clauses 4 to 6, wherein the frame body further includes a Reduced Neighbor Report (RNR) element, the RNR element including a Neighbor AP Information field associated with the non-primary link, the Neighbor AP Information field including a Target Beacon Transmission Time (TBTT) Information field, the TBTT Information field including the Basic Service Set Identifier (BSSID) of the non-primary link and one or more MLD parameters.

[0258] 8. The method according to Clause 7, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-master link.

[0259] 9. The method according to any one or more of Clauses 7 to 8, wherein the neighbor AP information field includes a TBTT information field type configured to indicate that the neighbor AP information field carries information relating only to the non-primary link.

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

[0261] 11. The method according to any one or more of clauses 7 to 10, wherein the length of the TBTT information field indicates whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

[0262] 12. The method according to any one or more of Clauses 7 to 11, wherein the length of the TBTT information field is 9 octets.

[0263] 13. The method according to any one or more of Clauses 7 to 12, wherein the one or more MLD parameters carried in the TBTT information field include a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the non-primary link.

[0264] 14. The method described under Clause 13 further includes:

[0265] Receive an update for at least one of the BSS parameters associated with the non-primary link;

[0266] Based on the received update, increment the value of the Basic Service Set (BSS) Parameter Change Count (BPCC) field, which is included in the Target Beacon Transit Time (TBTT) information field of the Reduced Neighbor Report (RNR) element in another frame;

[0267] Based on the incremented value of the BPCC field, a Key Update Flag (CUF) is set in the Capability Information field of the other frame; and

[0268] The other frame, which indicates the update of the at least one BSS parameter associated with the non-primary link, is transmitted only on the primary link.

[0269] 15. The method according to Clause 13, wherein the BSS parameters include at least one of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

[0270] 16. The method described under any one or more of clauses 1 to 15, further comprising:

[0271] Receive updates to one or more Basic Service Set (BSS) parameters associated with the non-primary link; and

[0272] One or more updated BSS parameters associated with the non-primary link are transmitted only on the primary link.

[0273] 17. The method according to Clause 16, wherein the updated one or more BSS parameters are part of a partial profile of the non-primary link.

[0274] 18. A wireless communication device, comprising:

[0275] At least one modem;

[0276] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0277] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0278] Operating as a Non-Simultaneous Transmit-Receive (NSTR) Soft Access Point (AP) Multilink Device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; and

[0279] Frames are transmitted only on the primary link, the frames including a complete profile of the primary link and indicating a complete profile of the non-primary link, the respective complete profiles of the primary link and the non-primary link each including 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 the discovery of the respective link.

[0280] 19. The wireless communication device according to Clause 18, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

[0281] 20. A wireless communication device according to any one or more of Clauses 18 to 19, wherein the beacon spacing, the SSID, and the TSF value of the non-main link are inherited from the main link.

[0282] 21. A wireless communication device according to any one or more of clauses 18 to 20, wherein the frame includes a frame body, the frame body comprising:

[0283] Multiple fields and elements, said multiple fields and elements carrying the complete profile of the main link; and

[0284] A multi-link (ML) element, the ML element carrying a per-STA profile sub-element indicating the full profile of the non-primary link.

[0285] 22. The wireless communication device according to Clause 21, wherein the ML element further includes a shared information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the main link.

[0286] 23. A wireless communication device according to any one or more of clauses 21 to 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 soft AP MLD.

[0287] 24. A wireless communication device according to any one or more of Clauses 21 to 23, wherein the frame body further includes a Reduced Neighbor Report (RNR) element, the RNR element including a Neighbor AP Information field associated with the non-primary link, the Neighbor AP Information field including a Target Beacon Transmission Time (TBTT) Information field, the TBTT Information field including a Basic Service Set Identifier (BSSID) of the non-primary link and one or more MLD parameters.

[0288] 25. The wireless communication device according to Clause 24, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-master link.

[0289] 26. A wireless communication device according to any one or more of Clauses 24 to 25, wherein the neighbor AP information field includes a TBTT information field type configured to indicate that the neighbor AP information field carries a reserved value relating only to the non-main link.

[0290] 27. A wireless communication device according to any one or more of clauses 24 to 26, wherein the length of the TBTT information field indicates whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

[0291] 28. The wireless communication device according to Clause 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, the BPCC value indicating an update to one or more BSS parameters associated with the non-main link.

[0292] 29. The wireless communication device according to Clause 28, wherein the execution of the processor-readable code is further configured to:

[0293] Receive an update for at least one of the BSS parameters associated with the non-primary link;

[0294] Based on the received update, increment the value of the Basic Service Set (BSS) Parameter Change Count (BPCC) field, which is included in the Target Beacon Transit Time (TBTT) information field of the Reduced Neighbor Report (RNR) element in another frame;

[0295] Based on the incremented value of the BPCC field, a Key Update Flag (CUF) is set in the Capability Information field of the other frame; and

[0296] The other frame, which indicates the update of the at least one BSS parameter associated with the non-primary link, is transmitted only on the primary link.

[0297] 30. A wireless communication device according to any one or more of clauses 18 to 29, wherein the execution of the processor-readable code is further configured to:

[0298] Receive updates to one or more Basic Service Set (BSS) parameters associated with the non-primary link; and

[0299] One or more updated BSS parameters associated with the non-primary link are transmitted only on the primary link.

[0300] 31. A method for wireless communication by a wireless station (STA), comprising:

[0301] Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link;

[0302] It was determined that the non-primary link was unavailable; and

[0303] Only frames carrying an indication of the unavailability of the non-primary link are transmitted on the primary link.

[0304] 32. The method according to Clause 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.

[0305] 33. The method according to any one or more of clauses 31 to 32, wherein the frame includes a per-STA profile sub-element or a reduced neighbor report (RNR) element carrying a No Transmit (DNT) bit set to a value of 1, and wherein the DNT bit set to the value of 1 indicates the unavailability of the non-master link.

[0306] 34. The method according to any one or more of clauses 31 to 33, wherein the frame includes a capability information field carrying a critical update flag (CUF) that is set to a value of 1 based on the unavailability of the non-primary link.

[0307] 35. The method described under any one or more of clauses 31 to 34 further includes:

[0308] Based on the unavailability of the non-primary link, it operates as a single-link device on the primary link.

[0309] 36. The method described under Clause 35 further includes:

[0310] When operating as a single-link device on the primary link, it is determined that the non-primary link is available;

[0311] Based on the availability of the non-primary link, the Do Not Transmit (DNT) bit is reset to the value 0; and

[0312] The reset DNT bit is transmitted only on the main link in another frame, the other frame including a per-STA profile element or a reduced neighbor report (RNR) element carrying the reset DNT bit with the value 0.

[0313] 37. The method described under any one or more of clauses 31 to 36 further includes:

[0314] After transmitting the indication, it is determined that the non-primary link is available;

[0315] Indications regarding the availability of the non-primary link are transmitted only on the primary link; and

[0316] Based on the availability of the non-primary link, it operates as a multi-link device on both the primary link and the non-primary link.

[0317] 38. The method according to any one or more of clauses 31 to 36 further comprises: disabling the non-primary link or placing the non-primary link in a power-saving state based on the unavailability of the non-primary link.

[0318] 39. The method according to Clause 38, wherein disabling the non-primary link includes removing the non-primary link from the multi-link context associated with the NSTR soft AP MLD.

[0319] 40. The method described under clause 39 further includes:

[0320] After removing the non-primary link from the multi-link context, it is determined that the non-primary link is available; and

[0321] Based on the availability of the non-primary link, the non-primary link is added to the multi-link context.

[0322] 41. The method according to Clause 38, wherein disabling the non-primary link includes remapping the Traffic Identifier (TID) from the non-primary link to the primary link.

[0323] 42. The method described under clause 41 further includes:

[0324] After disabling the non-primary link, it was determined that the non-primary link was available; and

[0325] Based on the availability of the non-primary link, the TID is remapped from the primary link to the non-primary link.

[0326] 43. The method described under any one or more of clauses 31 to 42 further includes:

[0327] Receive a Ready to Transmit (RTS) frame from STA MLD on the main link;

[0328] Based on the received RTS frame, a Clear Send (CTS) frame is transmitted to the STA MLD on both the primary link and the non-primary link; and

[0329] One or more uplink (UL) physical layer protocol data units (PPDUs) are received from the STA MLD on the main link and the non-main link.

[0330] 44. The method described under any one or more of clauses 31 to 42 further includes:

[0331] The non-primary link is switched from the second channel to the channel, and the primary link is switched from the first channel to the second channel concurrently.

[0332] 45. The method according to clause 44, wherein the first channel is in one of the 5 GHz band or the 6 GHz band, and the second channel is in the other of the 5 GHz band or the 6 GHz band.

[0333] 46. ​​A wireless communication device, comprising:

[0334] At least one modem;

[0335] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0336] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0337] Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link;

[0338] It was determined that the non-primary link was unavailable; and

[0339] Only frames carrying an indication of the unavailability of the non-primary link are transmitted on the primary link.

[0340] 47. The wireless communication device according to Clause 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.

[0341] 48. A wireless communication device according to any one or more of clauses 46 to 47, wherein the frame includes a per-STA profile sub-element or a reduced neighbor report (RNR) element carrying a non-transmit (DNT) bit set to a value of 1, and wherein the DNT bit set to the value of 1 indicates the unavailability of the non-master link.

[0342] 49. A wireless communication device according to any one or more of Clauses 46 to 47, wherein the frame includes a capability information field carrying a critical update flag (CUF) that is set to a value of 1 based on the unavailability of the non-main link.

[0343] 50. A wireless communication device according to any one or more of clauses 46 to 49, wherein the execution of the processor-readable code is further configured to:

[0344] Based on the unavailability of the non-primary link, it operates as a single-link device on the primary link.

[0345] 51. The wireless communication device according to Clause 50, wherein the execution of the processor-readable code is further configured to:

[0346] When operating as a single-link device on the primary link, it is determined that the non-primary link is available;

[0347] Based on the availability of the non-primary link, the Do Not Transmit (DNT) bit is reset to the value 0; and

[0348] The reset DNT bit is transmitted only on the main link in another frame, the other frame including a per-STA profile element or a reduced neighbor report (RNR) element carrying the reset DNT bit with the value 0.

[0349] 52. The wireless communication device according to any one or more of clauses 46 to 51, wherein the execution of the processor-readable code is further configured to:

[0350] After transmitting the indication, it is determined that the non-primary link is available;

[0351] Indications regarding the availability of the non-primary link are transmitted only on the primary link; and

[0352] Based on the availability of the non-primary link, it operates as a multi-link device on both the primary link and the non-primary link.

[0353] 53. A wireless communication device according to any one or more of clauses 46 to 52, wherein the execution of the processor-readable code is further configured to: disable the non-primary link or place the non-primary link in a power-saving state based on the unavailability of the non-primary link.

[0354] 54. The wireless communication device according to Clause 53, wherein disabling the non-primary link includes removing the non-primary link from the multilink context associated with the NSTR soft AP MLD.

[0355] 55. The wireless communication device according to Clause 54, wherein the execution of the processor-readable code is further configured to:

[0356] After removing the non-primary link from the multi-link context, it is determined that the non-primary link is available; and

[0357] Based on the availability of the non-primary link, the non-primary link is added to the multi-link context.

[0358] 56. The wireless communication device according to Clause 53, wherein disabling the non-primary link includes remapping the Traffic Identifier (TID) from the non-primary link to the primary link.

[0359] 57. The wireless communication device according to Clause 56, wherein the execution of the processor-readable code is further configured to:

[0360] After disabling the non-primary link, it was determined that the non-primary link was available; and

[0361] Based on the availability of the non-primary link, the TID is remapped from the primary link to the non-primary link.

[0362] 58. The wireless communication device according to any one or more of clauses 46 to 57, wherein the execution of the processor-readable code is further configured to:

[0363] Receive a Ready to Transmit (RTS) frame from STA MLD on the main link;

[0364] Based on the received RTS frame, a Clear Send (CTS) frame is transmitted to the STA MLD on both the primary link and the non-primary link; and

[0365] One or more uplink (UL) physical layer protocol data units (PPDUs) are received from the STA MLD on the main link and the non-main link.

[0366] 59. A wireless communication device according to any one or more of clauses 46 to 58, wherein the execution of the processor-readable code is further configured to:

[0367] The non-primary link is switched from the second channel to the first channel concurrently with the primary link being switched from the first channel to the second channel.

[0368] 60. The wireless communication device according to clause 59, wherein the first channel is in one of the 5 GHz band or the 6 GHz band, and the second channel is in the other of the 5 GHz band or the 6 GHz band.

[0369] 61. A method for wireless communication by a wireless station (STA), comprising:

[0370] The first frame is received only on the primary link from the non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and the non-primary link. The first frame includes a complete profile of the primary link and MLD information shared by the primary link and the non-primary link. The complete profile 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 the discovery of the primary link.

[0371] The second frame is transmitted only on the primary link to the NSTR soft AP MLD, and the second frame requests a complete profile of the non-primary link; and

[0372] The third frame, which indicates the complete profile of the non-main link, is received only from the NSTR soft AP MLD on the main link.

[0373] 62. The method according to Clause 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.

[0374] 63. The method according to any one or more of clauses 61 to 62, wherein the first frame includes a frame body carrying the complete profile of the primary link and including a multi-link (ML) element containing MLD common information.

[0375] 64. The method according to Clause 63, wherein 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, an Enhanced Multilink (EML) capability field, and an MLD capability field.

[0376] 65. The method according to Clause 64, wherein the BPCC field indicates an update to one or more BSS parameters associated with the main link.

[0377] 66. The method according to any one or more of clauses 64 to 65, wherein the link information of the non-primary link is not present in the ML element of the first frame.

[0378] 67. The method according to any one or more of clauses 61 to 66, wherein the third frame includes a frame body including a multi-link (ML) element carrying a per-STA profile sub-element indicating the non-primary link.

[0379] 68. The method according to Clause 67, wherein the frame body of the third frame further includes a Reduced Neighbor Report (RNR) element, the RNR element carrying a Neighbor AP Information field associated with the non-primary link, the Neighbor AP Information field carrying a Target Beacon Transmission Time (TBTT) Information field, the TBTT Information field including the Basic Service Set Identifier (BSSID) of the non-primary link and one or more MLD parameters.

[0380] 69. The method according to Clause 68, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-master link.

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

[0382] 71. A wireless communication device, comprising:

[0383] At least one modem;

[0384] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0385] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0386] The first frame is received only on the primary link from the non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and the non-primary link. The first frame includes a complete profile of the primary link and MLD information shared by the primary link and the non-primary link. The complete profile 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 the discovery of the primary link.

[0387] The second frame is transmitted only on the primary link to the NSTR soft AP MLD, and the second frame requests a complete profile of the non-primary link; and

[0388] The third frame, which indicates the complete profile of the non-main link, is received only from the NSTR soft AP MLD on the main link.

[0389] 72. The wireless communication device according to Clause 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.

[0390] 73. A wireless communication device according to any one or more of clauses 71 to 72, wherein the first frame includes a frame body carrying the complete profile of the main link and including a multi-link (ML) element containing MLD common information.

[0391] 74. The wireless communication device according to Clause 73, wherein 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, an Enhanced Multilink (EML) capability field, and an MLD capability field.

[0392] 75. The wireless communication device according to Clause 74, wherein the BPCC field indicates an update to one or more BSS parameters associated with the main link.

[0393] 76. The wireless communication device according to Clause 73, wherein the link information of the non-main link is not present in the ML element of the first frame.

[0394] 77. A wireless communication device according to any one or more of clauses 71 to 76, wherein the third frame includes a frame body that includes a multi-link (ML) element carrying a per-STA profile sub-element indicating the non-primary link.

[0395] 78. The wireless communication device according to Clause 77, wherein the frame body of the third frame further includes a Reduced Neighbor Report (RNR) element, the RNR element carrying a Neighbor AP Information field associated with the non-primary link, the Neighbor AP Information field carrying a Target Beacon Transmission Time (TBTT) Information field, the TBTT Information field including the Basic Service Set Identifier (BSSID) of the non-primary link and one or more MLD parameters.

[0396] 79. The wireless communication device according to Clause 78, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-master link.

[0397] 80. A wireless communication device according to any one or more of clauses 71 to 79, wherein the beacon spacing, SSID, and TSF values ​​of the non-main link are inherited from the main link.

[0398] 81. A method for wireless communication by a wireless station (STA), comprising:

[0399] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links; and

[0400] Frames including one or more timing parameters associated with the main link are transmitted only on the main link, and the non-main link includes one or more timing parameters inherited from the main link.

[0401] 82. The method according to Clause 81, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

[0402] 83. The method according to any one or more of clauses 81 to 82, wherein the one or more timing parameters include at least one of channel handover announcement, silence period or beacon interval.

[0403] 84. The method according to any one or more of clauses 81 to 83, wherein the primary link is associated with the Target Beacon Transmission Time (TBTT), and the non-primary link includes a pseudo BSS aligned with the TBTT of the primary link.

[0404] 85. The method according to any one or more of clauses 81 to 84, wherein the target wait time (TWT) session established on the non-primary link is synchronized with the TWT session established on the primary link.

[0405] 86. The method described under any one or more of clauses 81 to 85 further includes:

[0406] Align the uplink (UL) transmissions from the non-primary link to the NSTR soft AP MLD with the UL transmissions from the primary link to the NSTR soft AP MLD.

[0407] 87. A wireless communication device, comprising:

[0408] At least one modem;

[0409] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0410] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0411] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links; and

[0412] Frames including one or more timing parameters associated with the main link are transmitted only on the main link, and the non-main link includes one or more timing parameters inherited from the main link.

[0413] 88. The wireless communication device according to Clause 87, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

[0414] 89. A wireless communication device according to any one or more of Clauses 87 to 88, wherein the one or more timing parameters include at least one of channel switching announcement, silence period, or beacon interval.

[0415] 90. A wireless communication device according to any one or more of clauses 87 to 89, wherein the primary link is associated with the Target Beacon Transmission Time (TBTT), and the non-primary link includes a pseudo-BSS aligned with the TBTT of the primary link.

[0416] 91. A wireless communication device according to any one or more of clauses 87 to 90, wherein a target wait time (TWT) session established on the non-primary link is synchronized with a TWT session established on the primary link.

[0417] 92. A wireless communication device according to any one or more of clauses 87 to 91, wherein the execution of the processor-readable code is further configured to:

[0418] Align the uplink (UL) transmissions from the non-primary link to the NSTR soft AP MLD with the UL transmissions from the primary link to the NSTR soft AP MLD.

[0419] 93. A method for wireless communication by a wireless station (STA), comprising:

[0420] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links;

[0421] Obtain channel access on the main link;

[0422] The first frame is transmitted to the first associated STA on the main link;

[0423] During the duration of frame transmission on the primary link, the non-primary link is rendered deaf; and

[0424] After the frame transmission on the main link ends, the non-main link is restored from the deaf state.

[0425] 94. The method according to Clause 93, wherein the first frame includes a management frame, a control frame, or a data frame.

[0426] 95. The method described under any one or more of clauses 93 to 95 further comprises:

[0427] Channel access on the non-main link is obtained based on the channel access obtained on the main link; and

[0428] Simultaneously, while transmitting the third frame to the first associated STA on the main link, the second frame is transmitted to the second associated STA on the non-main link.

[0429] 96. The method according to Clause 95, wherein the first associated STA is a conventional device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and the second associated STA is a non-conventional device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0430] 97. The method described under clause 95 further includes:

[0431] The transmission of the second frame on the non-primary link is synchronized with the transmission of the third frame on the primary link.

[0432] 98. The method described under Clause 93 further includes:

[0433] During at least a portion of the channel access obtained on the main link, channel access on the non-main link is obtained; and

[0434] During the transmission of the first frame on the primary link, the second frame is transmitted to one or more second associated STAs on the non-primary link.

[0435] 99. The method according to Clause 98, wherein the first frame is a beacon frame and the second frame is an aggregation transmission to the one or more second associated STAs.

[0436] 100. The method according to Clause 99, wherein the one or more second associated STAs are multiple radio devices operating on the main link and the non-main link.

[0437] 101. A wireless communication device, comprising:

[0438] At least one modem;

[0439] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0440] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0441] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links;

[0442] Obtain channel access on the main link;

[0443] The first frame is transmitted to the first associated STA on the main link;

[0444] During the duration of frame transmission on the primary link, the non-primary link is rendered deaf; and

[0445] After the frame transmission on the main link ends, the non-main link is restored from the deaf state.

[0446] 102. The wireless communication device according to clause 101, wherein the first frame includes a management frame, a control frame, or a data frame.

[0447] 103. The wireless communication device according to any one or more of clauses 101 to 102, wherein the execution of the processor-readable code is further configured to:

[0448] Channel access on the non-main link is obtained based on the channel access obtained on the main link; and

[0449] Simultaneously, while transmitting the third frame to the first associated STA on the main link, the second frame is transmitted to the second associated STA on the non-main link.

[0450] 104. The wireless communication device according to Clause 103, wherein the first associated STA is a conventional device configured to operate according to IEEE 802.11ax or an earlier revision of the 802.11 wireless communication standard family, and the second associated STA is a non-conventional device configured to operate according to IEEE 802.11be or a later revision of the 802.11 wireless communication standard family.

[0451] 105. The wireless communication device according to clause 103, wherein the execution of the processor-readable code is further configured to:

[0452] The transmission of the second frame on the non-primary link is synchronized with the transmission of the third frame on the primary link.

[0453] 106. The wireless communication device according to clause 101, wherein the execution of the processor-readable code is further configured to:

[0454] During at least a portion of the channel access obtained on the main link, channel access on the non-main link is obtained; and

[0455] During the transmission of the first frame on the primary link, the second frame is transmitted to one or more second associated STAs on the non-primary link.

[0456] 107. The wireless communication device according to clause 106, wherein the first frame is a beacon frame and the second frame is an aggregation transmission to the one or more second associated STAs.

[0457] 108. The wireless communication device according to Clause 107, wherein the one or more second associated STAs are multiple radio devices operating on the main link and the non-main link.

[0458] 109. A method for wireless communication by a wireless station (STA), comprising:

[0459] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links;

[0460] Obtain channel access to the main link and the non-main link;

[0461] Establish Coordinated Target Wait Time (TWT) sessions on the primary link and the non-primary link;

[0462] A first trigger frame is transmitted on the main link, the first trigger frame soliciting uplink (UL) transmission from a first group of STAs on the main link; and

[0463] The first trigger frame is transmitted concurrently on the primary link with the transmission of the second trigger frame on the non-primary link, the second trigger frame being transmitted from the second group of STAs on the non-primary link.

[0464] 110. The method described under Clause 109 further includes:

[0465] Based on the first trigger frame, one or more first UL physical layer protocol data units (PPDUs) are received from the first group of STAs on the main link; and

[0466] Based on the second trigger frame, one or more second UL PPDUs are received from the second group of STAs on the non-main link.

[0467] 111. The method described under clause 110 further includes:

[0468] Synchronize one or more TWT service periods on the non-primary link with one or more corresponding TWT service periods on the primary link.

[0469] 112. The method according to Clause 110, wherein the transmission of the one or more second UL PPDUs by the second group of STAs on the main link is time-aligned with the transmission of the one or more first UL PPDUs by the first group of STAs on the main link.

[0470] 113. The method described under clause 110 further includes:

[0471] One or more first downlink (DL) PPDUs are transmitted to the first group of STAs on the main link; and

[0472] Simultaneously, on the primary link, one or more first DLPPDUs are transmitted to the first group of STAs, and on the non-primary link, one or more second DLPPDUs are transmitted to the second group of STAs.

[0473] 114. A wireless communication device, comprising:

[0474] At least one modem;

[0475] At least one processor, the at least one processor being communicatively coupled to the at least one modem; and

[0476] At least one memory, communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being configured, when executed by the at least one processor in conjunction with the at least one modem, to:

[0477] It operates as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD) associated with the primary link and non-primary links;

[0478] Obtain channel access to the main link and the non-main link;

[0479] Establish Coordinated Target Wait Time (TWT) sessions on the primary link and the non-primary link;

[0480] A first trigger frame is transmitted on the main link, the first trigger frame soliciting uplink (UL) transmission from a first group of STAs on the main link; and

[0481] The first trigger frame is transmitted concurrently on the primary link with the transmission of the second trigger frame on the non-primary link, the second trigger frame being transmitted from the second group of STAs on the non-primary link.

[0482] 115. The wireless communication device according to clause 114, wherein the execution of the processor-readable code is further configured to:

[0483] Based on the first trigger frame, one or more first UL physical layer protocol data units (PPDUs) are received from the first group of STAs on the main link; and

[0484] Based on the second trigger frame, one or more second UL PPDUs are received from the second group of STAs on the non-main link.

[0485] 116. The wireless communication device according to Clause 115, wherein the execution of the processor-readable code is further configured to:

[0486] Synchronize one or more TWT service periods on the non-primary link with one or more corresponding TWT service periods on the primary link.

[0487] 117. The wireless communication device according to Clause 115, wherein the transmission of the one or more second UL PPDUs by the second group of STAs on the main link is time-aligned with the transmission of the one or more first UL PPDUs by the first group of STAs on the main link.

[0488] 118. The wireless communication device according to Clause 115, wherein the execution of the processor-readable code is further configured to:

[0489] One or more first downlink (DL) PPDUs are transmitted to the first group of STAs on the main link; and

[0490] Simultaneously, on the primary link, one or more first DLPPDUs are transmitted to the first group of STAs, and on the non-primary link, one or more second DLPPDUs are transmitted to the second group of STAs.

[0491] As used herein, the phrase “at least one of” or “one or more of” refers to any combination of these items, including a single member. For example, “at least one of a, b or c” is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b and c.

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

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

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

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

Claims

1. A method for wireless communication by a wireless station (STA), comprising: Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; as well as Frames are transmitted only on the primary link. Each frame includes one or both of the complete profile of the primary link or the complete profile of the non-primary link. Each complete profile includes at least the 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 the discovery of the corresponding link. The reduced neighbor report (RNR) element includes a neighbor AP information field associated with the non-primary link. The neighbor AP information field includes a target beacon transit time (TBTT) information field. The TBTT information field includes one or both of the basic service set identifier (BSSID) and one or more MLD parameters of the non-primary link, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-primary link.

2. The method of claim 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 claim 1, wherein the beacon interval, the SSID, and the TSF value of the non-primary link are inherited from the primary link.

4. The method of claim 1, wherein the frame includes a frame body, the frame body comprising: Multiple fields and elements, which carry the complete profile of the main link; as well as Multi-link elements.

5. The method of claim 4, wherein the multi-link element further includes a shared information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the primary link.

6. The method of claim 4, wherein one or more bits of the multilink control field or common information field of the multilink element indicate whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

7. The method of claim 1, wherein the neighbor AP information field includes a TBTT information field type that is set to 1 or a reserved value to indicate that the neighbor AP information field carries information only related to the non-primary link.

8. The method of claim 1, wherein the TBTT information field has a length of 9 octets and indicates whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

9. The method of claim 1, wherein the one or more MLD parameters carried in the TBTT information field include a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the non-primary link.

10. The method according to claim 1, further comprising: Identify updates to one or more Basic Service Set (BSS) parameters associated with the non-primary link; as well as One or more updated BSS parameters associated with the non-primary link are transmitted only on the primary link.

11. The method of claim 10, wherein the updated one or more BSS parameters are part of a partial profile of the non-master link.

12. A method for wireless communication by a wireless station (STA), comprising: Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; Frames are transmitted only on the primary link. The frame includes one or both of the full profile of the primary link or the full profile of the non-primary link. Each full profile includes at least the 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 the discovery of the corresponding link. Identify updates to at least one Basic Service Set (BSS) parameter associated with the non-primary link; Based on the update, the value of the BSS parameter change count (BPCC) field in the Target Beacon Transit Time (TBTT) information field, which is included in the Reduced Neighbor Report (RNR) element of another frame, is incremented; Based on the incremented value of the BPCC field, a critical update flag (CUF) is set in the capability information field of the other frame. as well as The other frame, which indicates the update of the at least one BSS parameter associated with the non-primary link, is transmitted only on the primary link.

13. The method of claim 12, wherein the BSS parameters include at least one of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

14. A wireless communication device, comprising: One or more memory units; as well as One or more processors, said one or more processors being coupled to said one or more memories and capable of operating individually or collectively to: Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; as well as Frames are transmitted only on the primary link. Each frame includes one or both of the complete profile of the primary link or the complete profile of the non-primary link. Each complete profile includes at least the 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 the discovery of the corresponding link. The reduced neighbor report (RNR) element includes a neighbor AP information field associated with the non-primary link. The neighbor AP information field includes a target beacon transit time (TBTT) information field. The TBTT information field includes one or both of the basic service set identifier (BSSID) and one or more MLD parameters of the non-primary link, wherein the TBTT offset subfield, short SSID subfield, BSS parameter subfield, and power spectral density (PSD) subfield are not present in the TBTT information field corresponding to the non-primary link.

15. The wireless communication device of claim 14, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame.

16. The wireless communication device of claim 14, wherein the beacon spacing, the SSID, and the TSF value of the profile of the non-main link are inherited from the profile of the main link.

17. The wireless communication device of claim 14, wherein the frame includes a frame body, the frame body comprising: Multiple fields and elements, which carry the complete profile of the main link; as well as Multi-link elements.

18. The wireless communication device of claim 17, wherein the multi-link element further includes a shared information field carrying a Basic Service Set (BSS) Parameter Change Count (BPCC) field, the BPCC field indicating an update to one or more BSS parameters associated with the main link.

19. The wireless communication device of claim 17, wherein one or more bits of the multilink control field or common information field of the multilink element indicate whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

20. The wireless communication device of claim 14, wherein the neighbor AP information field includes a TBTT information field type that is set to 1 or a reserved value to indicate that the neighbor AP information field carries information relating only to the non-main link.

21. The wireless communication device of claim 14, wherein the TBTT information field has a length of 9 octets and indicates whether the frame is transmitted from the first AP of the NSTR soft AP MLD.

22. The wireless communication device of claim 14, wherein the one or more MLD parameters carried in the TBTT information field include a Basic Service Set (BSS) Parameter Change Count (BPCC) value, the BPCC value indicating an update to one or more BSS parameters associated with the non-main link.

23. A wireless communication device, comprising: One or more memory units; as well as One or more processors, said one or more processors being coupled to said one or more memories and capable of operating individually or collectively to: Operating as a non-simultaneous transmit-receive (NSTR) soft access point (AP) multilink device (MLD), the NSTR soft AP MLD includes a first AP associated with the primary link and a second AP associated with a non-primary link; Frames are transmitted only on the primary link. The frame includes one or both of the full profile of the primary link or the full profile of the non-primary link. Each full profile includes at least the 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 the discovery of the corresponding link. Identify updates to at least one Basic Service Set (BSS) parameter associated with the non-primary link; Based on the update, the value of the BSS parameter change count (BPCC) field in the Target Beacon Transit Time (TBTT) information field, which is included in the Reduced Neighbor Report (RNR) element of another frame, is incremented; Based on the incremented value of the BPCC field, a critical update flag (CUF) is set in the capability information field of the other frame. as well as The other frame, which indicates the update of the at least one BSS parameter associated with the non-primary link, is transmitted only on the primary link.

24. The wireless communication device of claim 23, wherein the BSS parameters include at least one of the following: Channel Switching Announcement (CSA) element, Extended Channel Switching Announcement (eCSA) element, Enhanced Distributed Channel Access (EDCA) parameter, Quiet Period element, Direct Sequence Spread Spectrum (DSSS) parameter set, High Throughput (HT) operation element, Very High Throughput (VHT) operation element, High Efficiency (HE) operation element, Extremely High Throughput (EHT) operation element, Wide Bandwidth Channel Switching element, Operation Mode Notification element, Broadcast Target Waiting Time (TWT) element, BSS Color Change Announcement element, Multi-User (MU) EDCA parameter set, Spatial Reuse parameter set, or Uplink (UL) Orthogonal Frequency Division Multiple Access (OFDMA) Random Access (UORA) parameter set.

25. The wireless communication device of claim 23, wherein the execution of the processor-readable code is further configured to: Identify updates to one or more Basic Service Set (BSS) parameters associated with the non-primary link; and One or more updated BSS parameters associated with the non-primary link are transmitted only on the primary link.

26. The wireless communication device of claim 25, wherein the updated one or more BSS parameters are part of a partial profile of the non-main link.

Images