Context updates for multi-link devices

Abstract

A first AP of an Access Point (AP) Multilink Device (MLD) is associated with a first communication link, and one or more secondary APs of the AP MLD are associated with one or more corresponding secondary communication links of the AP MLD. The first AP of the AP MLD generates a frame including a first change sequence field and one or more secondary change sequence fields. The first change sequence field indicates the presence or absence of a critical update associated with the first communication link, and each of the one or more secondary change sequence fields indicates the presence or absence of a critical update associated with a corresponding secondary communication link of the AP MLD. The first AP of the AP MLD sends this frame to the STA of the Station (STA) of the MLD on the first communication link of the AP MLD.

Description

Context updates for multi-link devices This patent application claims priority to U.S. Provisional Patent Application No. 63 / 007,299, filed on April 8, 2020, entitled “INDICATIONS OF CRITICAL UPDATES FOR MULTI-LINK DEVICES”; U.S. Provisional Patent Application No. 63 / 075,816, filed on September 8, 2020, entitled “CONTEXT UPDATES FOR MULTI-LINK DEVICES”; and U.S. Non-Provisional Application No. 17 / 224,979, filed on April 7, 2021, entitled “CONTEXT UPDATES FOR MULTI-LINK DEVICES”, all of which are assigned to the assignee of this application. The disclosures of all prior applications are considered a part of and incorporated by reference into this application. The present disclosure generally relates to wireless communications, and more particularly, to indicating critical updates to communication links associated with multi-link devices (MLDs). A wireless local area network (WLAN) can be formed by one or more access points (APs), which provide a shared wireless communication medium for multiple client devices (also known as stations (STAs)). The fundamental building block of a WLAN, which complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, is the basic service set (BSS), which is 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. To increase data throughput, an AP can communicate with one or more STAs over multiple concurrent communication links. Each communication link can have varying bandwidths, for example, by consolidating multiple 20 MHz-wide channels to form a 40 MHz-wide channel, an 80 MHz-wide channel, or a 160 MHz-wide channel. The AP can establish a BSS over any of the different communication links, and thus, it is desirable to improve communication between the AP and one or more STAs over each of the communication links. The systems, methods, and apparatus of the present disclosure each possess several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein. One innovative aspect of the subject matter described herein can be implemented in a method for wireless communication. The method can be performed by a first access point (AP) multi-link device (MLD). The first AP can be associated with a first communication link, and the AP MLD can include one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD. In some implementations, the method can include generating a frame including a first change sequence field and one or more secondary change sequence fields. The first change sequence field can indicate the presence or absence of a critical update associated with the first communication link of the AP MLD. Each of the one or more secondary change sequence fields can indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. The method can also include transmitting the frame on the first communication link of the AP MLD. The frame can be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a Fast Initial Link Setup (FILS) discovery frame. In some implementations, the method may also include receiving a notification of a critical update for a corresponding secondary AP of the AP MLD. The method may also include incrementing a value of the secondary change sequence field associated with the corresponding secondary AP based on the notification. The first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with the first AP of the AP MLD, and each of the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of the BSS associated with a corresponding secondary AP of the AP MLD. In some implementations, the one or more instruction arguments include at least one of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter sets, contention-free (CF) parameter sets, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. In some implementations, the frame may include a multilink element (MLE) carrying the first change sequence field. In some cases, the MLE may include or indicate one or more command arguments for the first communication link associated with the first AP and the AP MLD. In some cases, the MLE may include one or more per-link profile sub-elements, each per-link profile sub-element carrying a partial or complete set of command arguments for a basic service set (BSS) associated with a corresponding secondary AP of the AP MLD. In some other cases, the one or more secondary change sequence fields are included in one or more corresponding reduced neighbor report (RNR) elements carried in the frame. In some implementations, the method may also include receiving a probe request frame from a wireless STA of a station (STA) MLD. The method may also include sending a response frame from the first AP of the AP MLD to the STA MLD over the first communication link. In some aspects, the response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with one or more corresponding secondary APs of the AP MLD. In some implementations, the method may also include receiving an indication of a critical update for a corresponding secondary AP of the AP MLD. The method may also include sending an unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary AP of the AP MLD. In some aspects, the response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with the one or more corresponding secondary APs of the AP MLD. In one implementation, the method may also include providing an indication of transmission of a complete set of command arguments for the corresponding secondary AP of the AP MLD before sending the unsolicited broadcast probe response frame. In some cases, the indication is sent in a beacon frame over the first communication link. Another innovative aspect of the subject matter described herein can be implemented in a wireless communication device. In some implementations, the wireless communication device can be an access point (AP) multi-link device (MLD). The AP MLD can 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. In some implementations, the memory can store processor-readable code that, when executed by the at least one processor in conjunction with the at least one modem, causes the AP MLD to perform operations including: generating a frame by a first AP of the AP MLD associated with a first communication link of the AP MLD. The AP MLD can also include one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD. The frame can include a first change sequence field and one or more secondary change sequence fields. The first change sequence field can indicate the presence or absence of a critical update associated with the first communication link of the AP MLD. Each of the one or more secondary change sequence fields may indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. The method may also include: sending the frame on the first communication link of the AP MLD. The frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a Fast Initial Link Setup (FILS) discovery frame. In some implementations, execution of the processor-readable code may cause the AP MLD to perform operations, the operations also including: receiving a notification of a critical update for a corresponding secondary AP of the AP MLD from the corresponding secondary AP. Execution of the processor-readable code may cause the AP MLD to perform operations, the operations also including: incrementing a value of a secondary change sequence field associated with the corresponding secondary AP based on the notification. The first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with the first AP of the AP MLD, and each of the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of the BSS associated with a corresponding secondary AP of the AP MLD. In some implementations, the critical update for the corresponding communication link corresponds to a change in one or more command arguments of a BSS associated with the corresponding communication link. In some cases, the one or more command arguments include at least one of: a CSA, an extended CSA, a wideband CSA, an EDCA parameter, a MU EDCA parameter, a quiet time element, a DSSS parameter set, a CF parameter set, an OM parameter, a UORA parameter, a TWT parameter, a BSS color change, a FILS parameter, a SR parameter, a HT operation, a VHT operation, a HE operation, or an EHT operation. In some implementations, the frame may include a multilink element (MLE) carrying the first change sequence field. In some cases, the MLE may include or indicate one or more command arguments for the first communication link associated with the first AP and the AP MLD. In some cases, the MLE may include one or more per-link profile sub-elements, each per-link profile sub-element carrying a partial or complete set of command arguments for a basic service set (BSS) associated with a corresponding secondary AP of the AP MLD. In some other cases, the one or more secondary change sequence fields are included in one or more corresponding reduced neighbor report (RNR) elements carried in the frame. In some implementations, execution of the processor-readable code may cause the AP MLD to perform operations, the operations also including: receiving a probe request frame from a STA MLD. Execution of the processor-readable code may cause the AP MLD to perform operations, the operations also including: sending a response frame from the first AP of the AP MLD to the STA MLD over the first communication link. In some aspects, the response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with the one or more corresponding secondary APs of the AP MLD. In some implementations, execution of the processor-readable code may cause the AP MLD to perform operations, the operations also including: receiving an indication of a critical update for a corresponding secondary AP of the AP MLD. Execution of the processor-readable code may also cause the AP MLD to perform operations, the operations also including: sending an unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary AP of the AP MLD. In some aspects, the response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with the one or more corresponding secondary APs of the AP MLD. In one implementation, the method may also include: providing an indication of transmission of the complete set of command arguments for the corresponding secondary AP of the AP MLD before sending the unsolicited broadcast probe response frame. In some cases, the indication is sent in a beacon frame over the first communication link. Another innovative aspect of the subject matter described herein can be implemented in a method for wireless communication. The method can be performed by a first STA of a STA MLD. The first STA can be associated with a first communication link of the STA MLD, and the STA MLD can include one or more secondary STAs associated with one or more corresponding secondary communication links of the STA MLD. In some implementations, the method can include associating with a first AP of an AP MLD. The method can include receiving a frame from the first AP on the first communication link of the AP MLD. In some cases, the frame can include a first change sequence field and one or more secondary change sequence fields. The first change sequence field can indicate the presence or absence of a critical update associated with the first communication link of the AP MLD. Each of the one or more secondary change sequence fields can indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. In one implementation, the one or more secondary change sequence fields can be included in one or more corresponding RNR elements carried in the frame. In other implementations, the first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with the first AP of the AP MLD, and the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of the BSS associated with the one or more corresponding secondary APs of the AP MLD. In some implementations, the frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a FILS discovery frame. In some cases, the frame may include an MLE carrying the first change sequence field. In some cases, the MLE may include or indicate one or more command arguments for the associated first communication link between the first AP and the AP MLD. In some cases, the MLE may include one or more per-link profile sub-elements, each per-link profile sub-element carrying a partial set of command arguments or a complete set of command arguments for the BSS associated with the corresponding secondary AP of the AP MLD. In some implementations, the method may also include storing, in a STA MLD, the values ​​carried in the first change sequence field and the one or more secondary change sequence fields of the received frame. In some cases, the storing includes incrementing the corresponding change sequence field value in response to the frame indicating a critical update associated with the communication link of the AP MLD corresponding to the corresponding change sequence field value stored in the STA MLD. In some other implementations, the method may also include incrementing the corresponding change sequence field value in response to the frame indicating a critical update associated with the communication link of the AP MLD corresponding to the corresponding change sequence field value stored in the STA MLD. In some implementations, the method may also include: sending a probe request frame over the first communication link. The method may also include: receiving a response frame from the first AP of the AP MLD over the first communication link. The response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with the one or more corresponding secondary APs. In some implementations, the one or more instruction arguments include at least one of: CSA, extended CSA, wideband CSA, EDCA parameters, MU EDCA parameters, quiet time elements, DSSS parameter sets, CF parameter sets, OM parameters, UORA parameters, TWT parameters, BSS color change, FILS parameters, SR parameters, HT operation, VHT operation, HE operation, or EHT operation. Another innovative aspect of the subject matter described herein can be implemented in a wireless communication device. In some implementations, the wireless communication device can be a STA MLD. The STA MLD can 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. In some implementations, the memory can store processor-readable code that, when executed by the at least one processor in conjunction with the at least one modem, causes the STA MLD to perform operations including associating with a first AP of an AP MLD. Execution of the processor-readable code can cause the STA MLD to perform operations including receiving a frame from the first AP on a first communication link of the AP MLD. In some cases, the frame can include a first change sequence field and one or more secondary change sequence fields. The first change sequence field can indicate the presence or absence of a critical update associated with the first communication link of the AP MLD. Each of the one or more secondary change sequence fields can indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. In one implementation, the one or more secondary change sequence fields may be included in one or more corresponding RNR elements carried in the frame. In other implementations, the first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with the first AP of the AP MLD, and the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of the BSS associated with the one or more corresponding secondary APs of the AP MLD. In some implementations, the frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a FILS discovery frame. In some cases, the frame may include an MLE carrying the first change sequence field. In some cases, the MLE may include or indicate one or more command arguments for the associated first communication link between the first AP and the AP MLD. In some cases, the MLE may include one or more per-link profile sub-elements, each per-link profile sub-element carrying a partial set of command arguments or a complete set of command arguments for the BSS associated with the corresponding secondary AP of the AP MLD. In some implementations, execution of the processor-readable code may cause the STA MLD to perform operations, the operations also including: storing, in the STA MLD, the values ​​carried in the first change sequence field and the one or more secondary change sequence fields of the received frame. In some cases, the storing includes: incrementing the corresponding change sequence field value in response to the frame indicating a critical update associated with the communication link of the AP MLD corresponding to the corresponding change sequence field value stored in the STA MLD. In some other implementations, execution of the processor-readable code may cause the STA MLD to perform operations, the operations also including: incrementing the corresponding change sequence field value in response to the frame indicating a critical update associated with the communication link of the AP MLD corresponding to the corresponding change sequence field value stored in the STA MLD. In some implementations, execution of the processor-readable code may cause the STA MLD to perform operations, the operations also including: sending a probe request frame on the first communication link. Execution of the processor-readable code may cause the STA MLD to perform operations, the operations also including: receiving a response frame from the first AP of the AP MLD on the first communication link. The response frame may include a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with the one or more corresponding secondary APs. In some implementations, the one or more instruction arguments include at least one of: CSA, extended CSA, wideband CSA, EDCA parameters, MU EDCA parameters, quiet time elements, DSSS parameter sets, CF parameter sets, OM parameters, UORA parameters, TWT parameters, BSS color change, FILS parameters, SR parameters, HT operation, VHT operation, HE operation, or EHT operation. 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 description, drawings, and claims. It should be noted that the relative dimensions of the following drawings may not be drawn to scale. For the purpose of describing the innovative aspects of the present invention, the following description is directed to certain implementations. However, one of ordinary skill 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 in any device, system, or network capable of sending and receiving radio frequency (RF) signals in accordance with one or more of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, the Bluetooth standard as defined by the Bluetooth Special Interest Group (SIG), the Bluetooth SIG, ... ®The described implementations may also be implemented in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following techniques or methods: 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 implementations may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of the following: wireless personal area networks (WPANs), wireless local area networks (WLANs), wireless wide area networks (WWANs), or Internet of Things (IoT) networks. Generally speaking, various implementations relate to wireless communications over multiple communication links, and more specifically, to establishing a multi-link (ML) context that allows multi-link devices (MLDs), such as access point (AP) MLDs and wireless station (STA) MLDs, to discover and associate with each other on a first communication link and subsequently communicate with each other on the first communication link and one or more other communication links without performing discovery, authentication, or association operations on the other communication links. The ML context may also include a common security context for each communication link associated with the MLD. Furthermore, the ML context may be utilized to establish or tear down block acknowledgment (BA) communication sessions over the multiple communication links and to allow dynamic mapping between transport identifiers (TIDs) and communication links. Implementations of the subject matter disclosed herein allow an MLD to dynamically add, remove, or modify communication links associated with an ML context using a request and response frame exchange over a single communication link. In some implementations, a first MLD and a second MLD may establish an ML context based on an exchange of discovery information, authentication information, and / or association information over the first communication link. The first MLD may send a request to modify a communication link identified in the ML context, and the second MLD may send a response indicating acceptance, rejection, or modification of the request. In some cases, the request may include one or more of: a request to add a new communication link to the ML context; a request to remove or delete a particular communication link from the ML context; or a request to modify one or more communication links identified in the ML context or otherwise associated with the first and second MLDs. FIG1 illustrates a block diagram of an example wireless communication network 100. According to some aspects, wireless communication network 100 may be an example of a wireless local area network (WLAN), such as a Wi-Fi network (and hereinafter referred to as WLAN 100). For example, WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of 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. WLAN 100 may include multiple wireless communication devices, such as an access point (AP) 102 and multiple stations (STAs) 104. Although only one AP 102 is shown, WLAN network 100 may include multiple APs 102. Each of the STAs 104 may also be referred to as a mobile station (MS), a mobile device, a mobile phone, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other possibilities. STA 104 may represent a variety of devices, such as a mobile phone, a personal digital assistant (PDA), other handheld devices, a small notebook computer, a notebook computer, a tablet computer, a laptop computer, a display device (e.g., a TV, a computer monitor, a navigation system, and other devices), a music or other audio or stereo device, a remote control device ("remote device"), a printer, a kitchen or other home appliance, a key fob (e.g., for a passive keyless entry and start (PKES) system), and other possibilities. A single AP 102 and the associated set of STAs 104 may be referred to as a basic service set (BSS) managed by the respective AP 102. FIG1 further illustrates an example coverage area 108 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. A BSS may be identified to users and to other devices via a service set identifier (SSID), which may be the media access control (MAC) address of the AP 102. The AP 102 periodically broadcasts beacon frames (“beacons”) including the BSSID to enable any STA 104 within wireless range of the AP 102 to “associate” or reassociate with the AP 102 to establish or maintain a corresponding communication link 106 (hereinafter also referred to as a “Wi-Fi link”) with the AP 102. For example, the beacon may include an identification of a primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide access to external networks to the various STAs 104 in the WLAN via corresponding communication links 106. To establish a communication link 106 with an AP 102, each of the STAs 104 is configured to perform passive or active scanning operations ("scanning") on frequency channels in one or more frequency bands (e.g., the 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). To perform passive scanning, the STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (measured in time units (TUs), where one TU may be equal to 1024 microseconds (µs)) called target beacon transmission times (TBTTs). To perform active scanning, the STA 104 generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from the AP 102. Each STA 104 may be configured to identify or select an AP 102 with which to associate based on the scanning information obtained via passive or active scanning, and to perform authentication and association operations to establish a communication link 106 with the selected AP 102. The AP 102 assigns an association identifier (AID) to the STA 104 at the end of the association operation, and the AP 102 uses the AID to track the STA 104. As wireless networks become increasingly popular, a STA 104 may have the opportunity to select one of multiple BSSs within the STA's range, or multiple APs 102 that together form an extended service set (ESS) comprising multiple connected BSSs. Extended network stations associated with a WLAN 100 may be connected to a wired or wireless distribution system that allows multiple APs 102 to connect within such an ESS. This allows a STA 104 to be covered by more than one AP 102 and to associate with different APs 102 at different times for different transmissions. Furthermore, after associating with an AP 102, a STA 104 may be configured to periodically scan its surroundings to find a more suitable AP 102 with which to associate. For example, a STA 104 that is moving relative to its associated AP 102 may perform a "roaming" scan to find another AP 102 with more desirable network characteristics, such as a higher received signal strength indicator (RSSI) or reduced traffic load. In some cases, STAs 104 may form a network without an AP 102 or other devices besides the STAs 104 themselves. One example of such a network is an ad hoc network (or wireless ad hoc network). An ad hoc network may alternatively be referred to as a mesh network or a peer-to-peer (P2P) network. In some cases, an ad hoc network may be implemented within a larger wireless network, such as WLAN 100. In such an implementation, while STAs 104 can communicate with each other via AP 102 using communication link 106, STAs 104 may also communicate directly with each other via direct wireless link 110. Furthermore, two STAs 104 may communicate via direct communication link 110 regardless of whether both STAs 104 are associated with and served by the same AP 102. In such an ad hoc system, one or more of the STAs 104 may assume the role that AP 102 plays in a BSS. Such STAs 104 may be referred to as group owners (GOs) and may coordinate transmissions within the ad hoc network. Examples of direct wireless links 110 include Wi-Fi direct connections, connections established via Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other P2P group connections. AP 102 and STA 104 may operate and communicate (via corresponding communication links 106) in accordance with the IEEE 802.11 family of 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. These standards define WLAN radio and baseband protocols for the PHY and media access control (MAC) layers. AP 102 and STA 104 send and receive wireless communications to and from each other in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs) (hereinafter also referred to as "Wi-Fi communications"). The AP 102 and STA 104 in the WLAN 100 can send PPDUs in an unlicensed spectrum, which can be a portion of the spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5.0 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some implementations of the AP 102 and STA 104 described herein can also communicate in other frequency bands, such as the 6.0 GHz band, that can support both licensed and unlicensed communications. The AP 102 and STA 104 can also be configured to communicate in other frequency bands, such as shared licensed bands, where multiple service providers may have licenses to operate in the same or overlapping frequency bands. Each of these frequency bands can include multiple sub-bands or multiple frequency channels. For example, PPDUs compliant with IEEE 802.11n, 802.11ac, and 802.11ax standard amendments can be sent in the 2.4 and 5.0 GHz frequency bands, each of which is divided into multiple 20 MHz channels. Thus, these PPDUs are sent on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel constraining. For example, PPDUs can be sent on physical channels with a bandwidth of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by constraining multiple 20 MHz channels together. Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PLCP Service Data Unit (PSDU). A receiving device can use the information provided in the preamble to decode subsequent data in the PSDU. In instances where the PPDU is sent on a constrained channel, the preamble fields may be replicated and sent in each of multiple component channels. The PHY preamble may include both a legacy portion (or "transmit preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble may be used for packet detection, automatic gain control, and channel estimation, among other purposes. The legacy preamble may also generally be used to maintain compatibility with legacy devices. The format, encoding, and information provided therein of the non-legacy portion of the preamble are based on the specific IEEE 802.11 protocol being used to transmit the payload. Figure 2A illustrates an example protocol data unit (PDU) 200 that can be used for communication between an AP and multiple 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, PHY preamble 202 can include a legacy portion, which itself includes a legacy short training field (L-STF) 206, a legacy long training field (L-LTF) 208, and a legacy signaling field (L-SIG) 210. PHY preamble 202 can also include a non-legacy portion (not shown). L-STF 206 generally enables a receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. L-LTF 208 generally enables a receiving device to perform fine timing and frequency estimation, as well as to estimate the wireless channel. L-SIG 210 generally enables a receiving device to determine the duration of the PDU and use the determined duration to avoid transmissions on the PDU. For example, the L-STF 206, the L-LTF 208, and the L-SIG 210 may be modulated according to a binary phase shift keying (BPSK) modulation scheme. The payload 204 may be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another suitable modulation scheme. The payload 204 may typically carry higher layer data, for example, in the form of a media access control (MAC) protocol data unit (MPDU) or an aggregated MPDU (A-MPDU). FIG2B illustrates an example L-SIG field 210 in the PDU of FIG2A . L-SIG 210 includes a data rate field 212, a reserved bit 214, a length field 216, a parity bit 218, and a tail field 220. Data rate field 212 indicates the data rate (note that the data rate indicated in data rate field 212 may not be the actual data rate of the data carried in payload 204). Length field 216 indicates the length of the packet, for example, in bytes. Parity bit 218 is used to detect bit errors. Tail field 220 includes tail bits used by a receiving device to terminate the operation of a decoder (e.g., a Viterbi decoder). The receiving device uses the data rate and length indicated in data rate field 212 and length field 216 to determine the duration of the packet, for example, in microseconds (µs). FIG3A illustrates another example PDU 300 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 transmission. It can be formatted as a High-Efficiency (HE) WLAN PPDU in accordance with the IEEE 802.11ax amendment to the IEEE 802.11 wireless communication protocol standard. PDU 300 includes a PHY preamble that includes a legacy portion 302 and a non-legacy portion 304. Following the preamble, PDU 300 can also include a PHY payload 306, for example, in the form of a PSDU including a data field 324. The legacy portion 302 of the preamble includes L-STF 308, L-LTF 310, and L-SIG 312. The non-legacy portion 304 includes a repetition of L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, a HE short training field (HE-STF) 320, and one or more HE long training fields (or symbols) (HE-LTF) 322. For OFDMA or MU-MIMO communications, the second portion 304 also includes a second HE signal field (HE-SIG-B) 318, which is encoded separately from HE-SIG-A 316. As with L-STF 308, L-LTF 310, and L-SIG 312, the information in RL-SIG 314 and HE-SIG-A 316 can be duplicated and sent in each of the component 20 MHz channels in situations involving the use of constrained channels. In contrast, the content in the HE-SIG-B 318 may be unique to each 20 MHz channel and targeted to a specific STA 104 . The RL-SIG 314 may indicate to HE-compatible STAs 104 that the PDU 300 is a HE PPDU. The AP 102 may use the HE-SIG-A 316 to identify and inform multiple STAs 104 that the AP has scheduled UL or DL ​​resources for them. For example, the HE-SIG-A 316 may include a resource configuration subfield that indicates the resource configuration for the identified STA 104. The HE-SIG-A 316 may be decoded by each HE-compatible STA 104 served by the AP 102. For MU transmissions, the HE-SIG-A 316 also includes information that each identified STA 104 may use to decode the associated HE-SIG-B 318. For example, the HE-SIG-A 316 may indicate the frame format, including the location and length of the HE-SIG-B 318, the available channel bandwidth, and the modulation and coding scheme (MCS), among other examples. The HE-SIG-A 316 may also include HE WLAN signaling information that may be used by STAs 104 other than the identified STA 104 . The HE-SIG-B 318 may carry STA-specific scheduling information, such as STA-specific (or "user-specific") MCS values ​​and STA-specific RU allocation information. In the context of DL MU-OFDMA, this information enables the corresponding STA 104 to identify and decode the corresponding resource elements (RUs) 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) to multiple STAs 104, indicating 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 using common bits, CRC bits, and tail bits. The user-specific field is assigned to a specific STA 104 and may be used to schedule specific RUs and indicate the schedule to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields containing information for two corresponding STAs to decode their corresponding RU payloads in the data field 324 . FIG3B illustrates another example PPDU 350 that can be used for wireless communication between an AP and one or more STAs. PDU 350 can be used for SU, OFDMA, or MU-MIMO transmission. PDU 350 can be formatted as an Extremely High Throughput (EHT) WLAN PPDU in accordance with the IEEE 802.11be amendment to the IEEE 802.11 wireless communication protocol standard, or it can be formatted as a PPDU compliant with any later (post-EHT) version of a new wireless communication protocol compliant with a future IEEE 802.11 wireless communication protocol standard or other wireless communication standards. PDU 350 includes a PHY preamble that includes a legacy portion 352 and a non-legacy portion 354. PDU 350 can also include a PHY payload 356 following the preamble, for example, in the form of a PSDU including a data field 376. The legacy portion 352 of the preamble includes an L-STF 358, an L-LTF 360, and an L-SIG 362. The non-legacy portion 354 of the preamble includes an RL-SIG 364 and a plurality of signal fields following the RL-SIG 364 that depend on the wireless communication protocol version. For example, the non-legacy portion 354 may include a universal 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 the U-SIG 366 and the EHT-SIG 368 may be configured for a wireless communication protocol version other than EHT and carry version-dependent information for the respective versions. The non-legacy portion 354 also includes an additional short training field 372 (referred to herein as "EHT-STF 372," although it may be configured for wireless communication protocol versions other than EHT and carry version-dependent information therefor) and one or more additional long training fields 374 (referred to herein as "EHT-LTF 374," although they may be configured for wireless communication protocol versions other than EHT and carry version-dependent information therefor). As with the L-STF 358, L-LTF 360, and L-SIG 362, in cases involving the use of constrained channels, the information in the U-SIG 366 and EHT-SIG 368 may be replicated and sent in each of the component 20 MHz channels. In some implementations, in addition to or in lieu of the primary 20 MHz channel, the EHT-SIG 368 may carry different information in one or more non-primary 20 MHz channels than in the primary 20 MHz channel. The EHT-SIG 368 may include one or more jointly coded symbols and may be encoded in a different block than the block in which the U-SIG 366 is encoded. The EHT-SIG 368 may be used by the AP to identify and inform multiple STAs 104 that the AP has scheduled UL or DL ​​resources for them. The EHT-SIG 368 may be decoded by each compatible STA 104 served by the AP 102. The EHT-SIG 368 may generally be used by a receiving device to interpret the bits in the data field 376. For example, the EHT-SIG 368 may include RU allocation information, spatial stream configuration information, and per-user signaling information (such as the MCS), among other examples. The EHT-SIG 368 may also include a cyclic redundancy check (CRC) (e.g., 4 bits) and a tail (e.g., 6 bits), which may be used for a binary convolutional code (BCC). In some implementations, the EHT-SIG 368 may include one or more code blocks, each including a CRC and tail. In some aspects, each of the code blocks can be encoded separately. The EHT-SIG 368 may carry STA-specific scheduling information, such as user-specific MCS values ​​and user-specific RU allocation information. The EHT-SIG 368 can generally be used by a receiving device to interpret the bits in the data field 376. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 376. Each EHT-SIG 368 includes a common field and at least one user-specific field. The common field can indicate RU allocation to multiple STAs 104, indicate RU assignments in the frequency domain, indicate which RUs are allocated for MU-MIMO transmission and which RUs correspond to MU-OFDMA transmission, and the number of users in the allocation, among other examples. The common field can be encoded using common bits, CRC bits, and tail bits. User-specific fields are assigned to a specific STA 104 and can be used to schedule specific RUs and indicate the schedule to other WLAN devices. Each user-specific field can include multiple user block fields. Each user block field may include, for example, two user fields containing information for two corresponding STAs to decode their corresponding RU payloads. The presence of RL-SIG 364 and U-SIG 366 can indicate to an EHT-compliant or later STA 104 that PPDU 350 is an EHT PPDU or a PPDU compliant with any later (post-EHT) version of a new wireless communication protocol that is compliant with future IEEE 802.11 wireless communication protocol standards. For example, U-SIG 366 can be used by a receiving device to interpret bits in EHT-SIG 368 or one or more of data fields 376. FIG4 illustrates an example PPDU 400 that may be used for communication between an AP 102 and multiple STAs 104. As previously described, each PPDU 400 includes a PHY preamble 402 and a PSDU 404. Each PSDU 404 may carry one or more MAC protocol data units (MPDUs). For example, each PSDU 404 may carry an aggregated MPDU (A-MPDU) 408 comprising multiple A-MPDU subframes 406. Each A-MPDU subframe 406 may include a MAC delimiter 410 and a MAC header 412 preceding an accompanying MPDU 414, which includes the data portion ("payload" or "frame body") of the A-MPDU subframe 406. The MPDU 414 may carry one or more MAC service data unit (MSDU) subframes 416. For example, the MPDU 414 may carry an aggregated MSDU (A-MSDU) 418 comprising multiple MSDU subframes 416. Each MSDU subframe 416 includes a corresponding MSDU 420 followed by a subframe header 422 . Referring back to the A-MPDU subframe 406, the MAC header 412 may include multiple fields containing information that defines or indicates characteristics or attributes of the data encapsulated within the frame body 414. The MAC header 412 also includes multiple fields that indicate the address used for the data encapsulated within the frame body 414. For example, the MAC header 412 may include a combination of a source address, a transmitter address, a receiver address, or a destination address. The MAC header 412 may include a frame control field that contains control information. The frame control field specifies the frame type, such as a data frame, a control frame, or a management frame. The MAC header 412 may also include a duration field that indicates the duration extending 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., a block ACK (BA) in the case of an A-MPDU). The duration field is used to reserve the wireless medium for the indicated duration, thereby establishing a NAV. Each A-MPDU subframe 406 may also include a frame check sequence (FCS) field 424 for error detection. For example, the FCS field 416 may include a cyclic redundancy check (CRC). As previously mentioned, AP 102 and STA 104 can support multi-user (MU) communications; that is, concurrent transmissions from one device to each of multiple devices (e.g., multiple simultaneous downlink (DL) communications from AP 102 to corresponding STA 104), or concurrent transmissions from multiple devices to a single device (e.g., multiple simultaneous uplink (UL) transmissions from corresponding STA 104 to AP 102). To support MU transmissions, 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. In the MU-OFDMA scheme, the available spectrum of a wireless channel can be divided into multiple resource elements (RUs), each of which includes multiple different frequency subcarriers ("tones"). The AP 102 can allocate or assign different RUs to different STAs 104 at a given time. The size and distribution of the RUs may be referred to as the RU allocation. In some implementations, RUs may be allocated at 2 MHz intervals, and thus, the smallest RU may include 26 tones, consisting of 24 data tones and 2 pilot tones. Therefore, in a 20 MHz channel, a maximum of 9 RUs (such as a 2 MHz, 26-tone RU) can be allocated (because some tones are reserved for other purposes). Similarly, in a 160 MHz channel, a maximum of 74 RUs can be allocated. Larger RUs of 52, 106, 242, 484, and 996 tones may also be allocated. Adjacent RUs may be separated by a null subcarrier (such as a DC subcarrier), for example, to reduce interference between adjacent RUs, reduce receiver DC offset, and avoid transmit center frequency leakage. For UL MU transmissions, the AP 102 may send a trigger frame to initiate and synchronize UL MU-OFDMA or UL MU-MIMO transmissions from multiple STAs 104 to the AP 102. Thus, such a trigger frame may enable multiple STAs 104 to send UL transmissions concurrently in time to the AP 102. The trigger frame may address one or more STAs 104 via corresponding association identifiers (AIDs) and may assign each AID (and therefore each STA 104) one or more RUs that may be used to send UL transmissions to the AP 102. The AP may also specify one or more random access (RA) RUs that unscheduled STAs 104 may contend for. FIG5 illustrates a block diagram of an example wireless communication device 500. In some implementations, wireless communication device 500 may be an example of a device for use in a STA (such as one of STAs 104 described above with reference to FIG1 ). In some implementations, wireless communication device 500 may be an example of a device for use in an AP (such as AP 102 described above with reference to FIG1 ). Wireless communication device 500 is capable of sending (or outputting for transmission) and receiving wireless communications (e.g., in the form of wireless packets). For example, a wireless communication device may be configured to send 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) in accordance with 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). Wireless communication device 500 may be or include any of the following: a chip, system-on-chip (SoC), chipset, package, or device that includes one or more modems 502 (e.g., Wi-Fi (IEEE 802.11 compliant) modems). In some implementations, one or more modems 502 (collectively, "modems 502") further include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compliant modem). In some implementations, wireless communication device 500 also includes one or more radios 504 (collectively, "radios 504"). In some implementations, wireless communication device 506 also includes one or more processors, processing blocks, or processing elements 506 (collectively, "processors 506") and one or more memory blocks or elements 508 (collectively, "memory 508"). The modem 502 may include intelligent hardware blocks or devices, such as application specific integrated circuits (ASICs), among other possibilities. The modem 502 is typically configured to implement the PHY layer. For example, the modem 502 is configured to modulate packets and output the modulated packets to the radio 504 for transmission over the wireless medium. The modem 502 is similarly configured to obtain modulated packets received by the radio 504 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 502 may also include digital signal processing (DSP) circuitry, automatic gain control (AGC), an encoder, a decoder, a multiplexer, and a demultiplexer. For example, when in transmit mode, data obtained from the processor 506 is provided to an encoder, which encodes the data to provide coded bits. The coded bits are then mapped to points in a modulation constellation (using a selected MCS) to provide modulated symbols. The modulated symbols may then be mapped to N SS spatial streams or N SS The modulated symbols in the corresponding spatial or space-time streams can then be multiplexed, converted via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuitry for Tx windowing and filtering. The digital signal can then be provided to a digital-to-analog converter (DAC). The resulting analog signal can then be provided to a frequency upconverter and ultimately to the radio unit 504. In implementations involving beamforming, the modulated symbols in the corresponding spatial streams are precoded via a directional matrix before being provided to the IFFT block. When in receive mode, a digital signal received from radio unit 504 is provided to the DSP circuitry, which is configured to acquire the received signal, for example, by detecting the presence of a signal and estimating initial timing and frequency offsets. The DSP circuitry is also configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment adjustment (such as correcting for I / Q imbalance), and applying digital gain, to ultimately obtain a narrowband signal. The output of the DSP circuitry can then be fed to an AGC, which is 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 is also coupled to a demodulator, which is configured to extract modulated symbols from the signal and, for example, calculate a log-probability ratio (LLR) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which can be configured to process the LLRs to provide decoded bits. The decoded bits from all spatial streams are then fed to a demultiplexer for demultiplexing.The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 506) for processing, evaluation, or interpretation. The radio unit 504 typically includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which can be combined into one or more transceivers. For example, the RF transmitter and receiver may include various DSP circuits, including at least one power amplifier (PA) and at least one low-noise amplifier (LNA), respectively. The RF transmitter and receiver may in turn be coupled to one or more antennas. For example, in some implementations, the 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 the modem 502 are provided to the radio unit 504, which then transmits the symbols via the coupled antennas. Similarly, symbols received via the antennas are acquired by the radio unit 504, which then provides the symbols to the modem 502. Processor 506 may include an intelligent hardware block or device designed to perform the functions described herein, such as a processing core, processing block, central processing unit (CPU), microprocessor, microcontroller, digital signal processor (DSP), application-specific integrated circuit (ASIC), programmable logic device (PLD) (such as a field-programmable gate array (FPGA)), individual gate or transistor logic, individual hardware components, or any combination thereof. Processor 506 processes information received via radio 504 and modem 502 and processes information to be output via modem 502 and radio 504 for transmission via a wireless medium. For example, processor 506 may implement the control plane and MAC layer, which are 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 encoding and decoding, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, among other operations or techniques. In some implementations, the processor 506 may generally control the data engine 502 to cause the data engine to perform the various operations described above. The memory 504 may include tangible storage media, such as random access memory (RAM) or read-only memory (ROM), or a combination thereof. The memory 504 may also store non-transitory processor or computer-executable software (SW) code containing instructions that, when executed by the processor 506, cause the processor to perform various operations for wireless communications described herein, including the generation, transmission, reception, and interpretation of MPDUs, frames, or packets. For example, various functions of the components disclosed herein or various blocks or steps of the methods, operations, procedures, or algorithms disclosed herein may be implemented as one or more modules of one or more computer programs. FIG6A illustrates a block diagram of an example AP 602. For example, AP 602 may be an example implementation of AP 102 described with reference to FIG1 . AP 602 includes a wireless communication device (WCD) 610. For example, wireless communication device 610 may be an example implementation of wireless communication device 500 described with reference to FIG5 . AP 602 also includes multiple antennas 620 coupled to wireless communication device 610 for transmitting and receiving wireless communications. In some implementations, AP 602 further includes an application processor 630 coupled to wireless communication device 610 and a memory 640 coupled to application processor 630. AP 602 also includes at least one external network interface 650 that enables AP 602 to communicate with a core network or a backhaul network to gain 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). The aforementioned components can communicate with other components directly or indirectly over at least one bus. AP 602 also includes a housing that encloses wireless communication device 610, application processor 630, memory 640, antenna 620, and at least a portion of external network interface 650. FIG6B illustrates a block diagram of an example STA 604. For example, STA 604 may be an example implementation of STA 104 described with reference to FIG1 . STA 604 includes a wireless communication device 615. For example, wireless communication device 615 may be an example implementation of wireless communication device 500 described with reference to FIG5 . STA 604 also includes one or more antennas 625 coupled to wireless communication device 615 for transmitting and receiving wireless communications. STA 604 also includes an application processor 635 coupled to wireless communication device 615 and a memory 645 coupled to application processor 635. In some implementations, STA 604 also includes a user interface (UI) 655 (such as a touchscreen or keyboard) and a display 665, which may be integrated with UI 655 to form a touchscreen display. In some implementations, STA 604 may also include one or more sensors 675, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. STA 604 also includes a housing that encloses wireless communication device 615, application processor 635, memory 645, and at least a portion of antenna 625, UI 655, and display 665. As previously mentioned, various implementations generally relate to multi-link (ML) communication, and more specifically, to establishing ML communication sessions between wireless communication devices. Aspects of the present disclosure provide a single multi-link association (MLA) context for multiple links shared among multiple MLDs. Under certain conditions, such as if congestion on a first link is high, the MLD can switch from communicating on the first link to communicating on a second link. Specifically, the single ML context disclosed herein can be shared between MAC-SAP endpoints of the MLDs, enabling the MLDs to dynamically communicate on any link shared between the MLDs without disassociating or reassociating with each other. For example, in some cases, MLDs associating and authenticating with each other on a link can use the same association and authentication parameters (such as capabilities, command arguments, configuration, encryption keys, and other ML communication parameters) determined for communication on any link. Some implementations more specifically relate to an AP MLD, which includes a first AP associated with a first communication link and one or more secondary APs associated with corresponding secondary communication links. The first AP of the AP MLD generates a frame that includes one or more command arguments for the first communication link, a first change sequence number (CSN) indicating the presence or absence of a critical update for the first communication link of the AP MLD, and one or more secondary CSNs, each indicating the presence or absence of a critical update for the corresponding secondary communication link of the AP MLD. The first AP transmits the frame to STAs of the STA MLD on the first communication link. The first CSN indicates the most recent critical update to the one or more command arguments for the first communication link, and each secondary CSN indicates the most recent critical update to the one or more command arguments for the corresponding secondary communication link. In some implementations, each secondary CSN may be carried in a corresponding per-link profile sub-element of a MLE. In some other implementations, each secondary CSN may be carried in a corresponding neighbor AP information field of a reduced neighbor report (RNR) element. Alternatively, the first CSN and one or more secondary CSNs may be carried in a sequence counter field of a frame or in an information element of a frame. In some other implementations, the frame may also include one or more Do Not Transmit (DNT) indications, where each DNT indication is associated with a corresponding secondary communication link of an AP MLD. In some cases, the frame may also include a DNT indication for a first communication link. Each DNT indication may indicate whether the wireless communication device should avoid transmitting on the corresponding secondary communication link of the AP MLD. In some cases, at least some wireless communication devices may monitor the first communication link instead of the one or more secondary communication links for the DNT indication. In some implementations, the DNT indication for the corresponding secondary communication link may be based on one or more of the following: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of a secondary AP of the AP MLD associated with the corresponding secondary communication link. Certain implementations of the subject matter described herein can be implemented to achieve one or more of the following potential advantages: By using frames sent on a primary communication link to announce one or more of a critical update, a DNT condition, or a command argument for one or more secondary communication links, a STA (such as a STA MLD) can receive one or more of the critical updates, DNT conditions, or command arguments for each secondary communication link without monitoring the secondary communication links, which can allow the STA to save power associated with performing scanning or listening operations on each secondary communication link. FIG7A illustrates a flow chart of an example process 700 for wireless communication that supports communication between MLDs, according to some implementations. The process 700 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 700 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the process 700 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In some implementations, at block 702, the process 700 begins by sending a first packet on a first communication link, the first packet including discovery information for at least the first communication link and a second communication link. At block 704, the process 700 continues by receiving an ML association request from a second wireless communication device on the first communication link based at least in part on the discovery information. At block 706, the process 700 continues by sending a second packet on the first communication link, the second packet including association information for at least the first communication link and the second communication link. At block 708, process 700 continues by associating with the second wireless communications device based at least in part on the association information. In some implementations, associating includes establishing at least one ML communication parameter for communicating with the second wireless communications device over the first and second communications links. The at least one ML communication parameter can be the same for each of the first and second communications links. In some other implementations, associating includes establishing a common security context between a first Media Access Control Service Access Point (MAC-SAP) endpoint of the first wireless communications device and a second MAC-SAP endpoint of the second wireless communications device. Each of the first and second MAC-SAP endpoints can be operable to communicate over the first and second communications links. At block 710, process 700 continues by communicating with the second wireless communications device over the second communications link based on the association with the second wireless communications device over the first communications link. FIG7B illustrates a flow chart of an example procedure 720 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 720 can be performed by a wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 720 can be performed by the wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the procedure 720 can be performed by the wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. 7A , process 720 may be a more detailed implementation of the ML communication operation described in block 710 of process 700. For example, process 720 may begin in block 722 after associating with the second wireless communication device in block 708 of process 700. At block 722, the process 720 continues by establishing a block acknowledgment (BA) communication session with the second wireless communication device, the BA communication session associating at least one transmission identifier (TID) with a first subset of the first communication link, the second communication link, and the third communication link. The BA communication session can be common to each of the first, second, and third communication links. At block 724, the process 720 continues by dynamically reassociating the at least one TID with a second subset of the first, second, and third communication links. At block 726, the process 720 continues by indicating the reassociation in an add block acknowledgment (ADDBA) capability field of a third packet. FIG8A illustrates a flow chart of an example process 800 for wireless communication that supports communication between MLDs, according to some implementations. The process 800 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 800 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the process 800 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In some implementations, at block 802, process 800 begins by receiving a first packet from a second wireless communication device over a first communication link, the first packet including discovery information for at least the first communication link and a second communication link. At block 804, process 800 continues by sending an ML association request over the first communication link based at least in part on the discovery information. At block 806, process 800 continues by receiving a second packet over the first communication link, the second packet including association information for at least the first communication link and the second communication link. In some implementations, a first A-MPDU subframe can be aligned with a code word boundary in a PSDU such that a portion of the first A-MPDU subframe is not encapsulated within the same LDPC code word as a portion of another A-MPDU subframe in the PSDU. At block 808, the process 800 continues by associating with the second wireless communications device based at least in part on the association information. In some implementations, the associating includes establishing at least one ML communication parameter for communicating with the second wireless communications device over the first and second communications links. The at least one ML communication parameter can be the same for each of the first and second communications links. In some other implementations, the associating includes establishing a common security context between a first Media Access Control Service Access Point (MAC-SAP) endpoint of the first wireless communications device and a second MAC-SAP endpoint of the second wireless communications device. Each of the first and second MAC-SAP endpoints can be used for communicating over the first and second communications links. At block 810, the process 800 continues by communicating with the second wireless communications device over the second communications link based on the association with the second wireless communications device over the first communications link. FIG8B illustrates a flow chart of an example process 820 for wireless communication that supports communication between MLDs, according to some implementations. The process 820 can be performed by a wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 820 can be performed by the wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the process 820 can be performed by the wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. 8A , process 820 may be a more detailed implementation of the ML communication operations described in block 810 of process 800. For example, process 820 may begin in block 822 after association with the second wireless communication device in block 808 of process 800. At block 822, the process 820 continues by establishing a block acknowledgment (BA) communication session with the second wireless communication device, the BA communication session associating at least one transmission identifier (TID) with a first subset of the first communication link, the second communication link, and the third communication link. The BA communication session may be common to each of the first, second, and third communication links. At block 824, the process 820 continues by receiving a third packet, the third packet indicating in an add block acknowledgment (ADDBA) capability field that the at least one TID is reassociated with a second subset of the first, second, and third communication links. FIG9 illustrates a flow chart of an example process 900 for wireless communication that supports communication between MLDs, according to some implementations. Process 900 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, process 900 can be performed by a wireless communication device operating as or within an AP, such as one of APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG9A , process 900 is performed by an AP multi-link device (MLD) that includes a first access point (AP) and one or more secondary APs. The first AP can be associated with a first communication link of the AP MLD, and each secondary AP can be associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. At block 902, a first AP of an AP MLD generates a frame comprising one or more command arguments for a first communication link, a first change sequence number (CSN) indicating the presence or absence of a critical update for the first communication link of the AP MLD, and one or more secondary CSNs, each indicating the presence or absence of a critical update for a corresponding secondary communication link of the AP MLD. At block 904, the first AP transmits a frame on the first communication link. The frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a Fast Initial Link Setup (FILS) discovery frame. In some implementations, a first CSN indicates a most recent critical update to one or more command arguments for a first communication link, and each secondary CSN indicates a most recent critical update to one or more command arguments for a corresponding secondary communication link of an AP MLD. In some cases, the first CSN and one or more secondary CSNs may be carried in a sequence counter field of a frame. In other cases, the first CSN and one or more secondary CSNs may be carried in an information element. In some implementations, a frame includes a multilink element (MLE) element that carries one or more secondary CSNs. In some cases, the MLE includes one or more per-link profile sub-elements, each of which carries the corresponding secondary CSN of the one or more secondary CSNs. In some other cases, the one or more per-link profile sub-elements include an information element (IE) that includes the corresponding secondary CSN of the one or more secondary CSNs. In some other cases, the MLE includes a common parameter field that carries the one or more secondary CSNs. In some other implementations, the frame may be a beacon frame including one or more per-link profile elements, each of the one or more per-link profile elements carrying a secondary CSN and a complete set of command arguments for a corresponding secondary communication link in the one or more secondary communication links. In some cases, the beacon frame may include one or more per-link profile elements, each of which carries a secondary CSN and a complete set of command arguments for a corresponding secondary communication link. In some implementations, a frame includes an MLE that carries one or more secondary CSNs. In some cases, the MLE may include one or more per-link profile sub-elements, each of which carries a corresponding secondary CSN for the one or more secondary CSNs. In some cases, each per-link profile sub-element may include an information element (IE) that includes the corresponding secondary CSN. In some other cases, the MLE may include a common parameter field that carries the secondary CSN. In some implementations, a frame may include a Reduced Neighbor Report (RNR) element that carries one or more secondary CSNs. In some cases, the RNR element may include one or more Neighbor AP Information fields, where each Neighbor AP Information field carries a corresponding secondary CSN of one or more secondary CSNs. In some implementations, the critical update may correspond to a change in one or more command arguments of a BSS associated with at least one of the first communication link or the one or more secondary communication links. In some implementations, the one or more instruction arguments may include at least one of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter sets, contention-free (CF) parameter sets, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. In some implementations, the frame may also include one or more Do Not Transmit (DNT) indications, where each DNT indication is associated with a corresponding secondary communication link of an AP MLD. In some cases, the frame may also include a DNT indication for a first communication link. Each DNT indication may indicate whether the wireless communication device should avoid transmitting on the corresponding secondary communication link of the AP MLD. In some cases, at least some wireless communication devices may monitor the first communication link instead of the one or more secondary communication links for the DNT indication. In some implementations, the DNT indication for the corresponding secondary communication link may be based on one or more of the following: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of a secondary AP of the AP MLD associated with the corresponding secondary communication link. In some implementations, a DNT indicator for a first communication link and one or more DNT indicators for one or more corresponding secondary communication links may be carried in a bit image of a frame. In some other implementations, one or more DNT indicators for one or more corresponding secondary communication links may be carried in an MLE of a frame. In some cases, the MLE may include one or more per-link profile sub-elements, each of which carries a DNT indicator for a corresponding secondary communication link. In some other cases, each per-link profile sub-element may also carry a complete set of command arguments for the corresponding secondary communication link. In some implementations, the frame may be a beacon frame including one or more per-link profile elements, where each per-link profile element carries a DNT indicator for a corresponding secondary communication link. In some cases, the per-link profile element in the one or more per-link profile elements may be an information element (IE). In some other cases, the MLE may include a common parameter field that carries one or more DNT indicators for one or more corresponding secondary communication links. In some other implementations, the beacon frame may carry one or more profiles, where each profile carries a complete set of command arguments for a corresponding secondary communication link in the one or more secondary communication links. In some implementations, one or more DNT indicators may be carried in a Reduced Neighbor Report (RNR) element of a frame. In some cases, the RNR element may include one or more neighbor AP information fields, where each neighbor AP information field carries a DNT indicator for a corresponding secondary communication link. FIG10A illustrates a flow chart of an example process 1000 for wireless communication that supports communication between MLDs, according to some implementations. The process 1000 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1000 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10A , the process 1000 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1000 of FIG10A can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1002, a first AP receives a notification of a critical update for a corresponding secondary communication link from one or more secondary APs of an AP MLD associated with the corresponding secondary communication link. At block 1004, the first AP increments a secondary CSN corresponding to the corresponding secondary communication link based on the notification. In some implementations, the critical update for at least one of the first communication link or the one or more secondary communication links may correspond to a change to one or more instruction arguments of a basic service set (BSS) associated with the first communication link or at least one of the one or more secondary communication links. FIG10B illustrates a flow chart of an example process 1010 for wireless communication that supports communication between MLDs, according to some implementations. The process 1010 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1010 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10B , the process 1010 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1010 of FIG10B can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1012, the first AP receives notification of a Do Not Transmit (DNT) condition for the corresponding secondary communication link from a corresponding secondary AP of an AP MLD associated with the corresponding secondary communication link. At block 1014, the first AP asserts a DNT indication corresponding to the corresponding secondary communication link. At block 1014, the first AP broadcasts the asserted DNT indication corresponding to the corresponding secondary communication link on the first communication link. In some implementations, each DNT indication may indicate whether the wireless communication device should avoid transmitting on the corresponding secondary communication link of the AP MLD. In some cases, at least some wireless communication devices may monitor the first communication link instead of one or more secondary communication links for the DNT indication. In some implementations, the DNT indication for the corresponding secondary communication link may be based on one or more of the following: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of a secondary AP of the AP MLD associated with the corresponding secondary communication link. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10C illustrates a flow chart of an example process 1020 for wireless communication that supports communication between MLDs, according to some implementations. The process 1020 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1020 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10C , the process 1020 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1020 of FIG10C can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1022, the first AP receives an indication of a critical update for the corresponding secondary communication link from a corresponding secondary AP of the AP MLD associated with the corresponding secondary communication link. At block 1024, the first AP sends an unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary communication link. In some other implementations, the unsolicited broadcast probe response frame may carry a complete set of command arguments for each of the one or more secondary communication links. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10D illustrates a flow chart of an example process 1030 for wireless communication that supports communication between MLDs, according to some implementations. The process 1030 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1030 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10D , the process 1030 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1030 of FIG10D can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1032, the first AP receives a probe request frame from a wireless STA of a station (STA) MLD. At block 1034, the first AP sends a response frame from the first AP of the AP MLD to the STA MLD over a first communication link. In some implementations, the response frame may carry a complete set of command arguments for the corresponding secondary communication link for which one or more command arguments were updated. In some cases, the request frame may be received by one of the first APs of the AP MLD on the first communication link, or by a corresponding secondary AP of the AP MLD on the corresponding secondary communication link. In some other implementations, the response frame may carry a complete set of command arguments for each of the one or more secondary communication links. In some cases, the request frame may be a broadcast probe request frame. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10E illustrates a flow chart of an example process 1040 for wireless communication that supports communication between MLDs, according to some implementations. Process 1040 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, process 1040 can be performed by a wireless communication device operating as or within an AP, such as one of APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG10E , process 1040 is performed by the AP MLD described with reference to FIG9 . In some implementations, process 1040 of FIG10E can be performed after the AP MLD sends the frame in block 904 of FIG9 . In some implementations, the probe request frame can carry a CSN indicating a recently received critical update for a specified secondary communication link among one or more secondary communication links of the AP MLD. At block 1042, the first AP identifies one or more CSNs for the designated secondary communication link that the STA of STA MLD missed based on the received CSNs. At block 1044, the first AP sends a response frame with an indication of the one or more secondary CSNs for the designated secondary communication link that the STA of STA MLD missed. In some implementations, the response frame may be a unicast probe response frame that carries one or more critical updates for a designated secondary communication link that the STA missed. In some cases, the one or more critical updates missed by the STA may be determined based on a comparison between the received CSN and one or more secondary CSNs missed by the STA. In some implementations, the response frame may be a unicast probe response frame or a broadcast probe response frame that carries a complete set of command arguments for the designated secondary communication link. In some cases, the response frame may be a broadcast probe response frame that carries a complete set of command arguments for each of the designated secondary communication link and other non-designated secondary communication links. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10F illustrates a flow chart of an example process 1050 for wireless communication that supports communication between MLDs, according to some implementations. The process 1050 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1050 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10F , the process 1050 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1050 of FIG10F can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1052, the corresponding secondary AP of the AP MLD may receive a probe request frame from a wireless STA of the station (STA) MLD on a designated secondary communication link. At block 1054, the corresponding secondary AP may send a response frame to the STA MLD on the designated secondary communication link. At block 1056, the first AP may send a response frame to the STA MLD with one or more updated command parameters for the designated secondary communication link. In some implementations, the probe request frame may carry a CSN indicating a recently received critical update for the designated secondary communication link. In some implementations, the command argument set may include one or more of: a channel switch announcement (CSA), an extended CSA, a wideband CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, a quiet time element, a direct sequence spread spectrum (DSSS) parameter set, a contention-free (CF) parameter set, an operation mode (OM) parameter, an uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter, a target latency (TWT) parameter, a basic service set (BSS) color change, a fast initial link setup (FILS) parameter, a spatial reuse (SR) parameter, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10G illustrates a flow chart of an example process 1060 for wireless communication that supports communication between MLDs, according to some implementations. The process 1060 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1060 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10G , the process 1060 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1060 of FIG10G can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1062, the corresponding secondary AP of the AP MLD may receive a probe request frame from a wireless STA of the station (STA) MLD on the designated secondary communication link. At block 1064, the corresponding secondary AP may send a response frame to the STA MLD carrying a complete set of command arguments for the designated secondary communication link. In some implementations, the response frame may be a unicast probe response frame or a beacon frame. In some implementations, the command argument set may include one or more of the following: channel switch announcement (CSA), extended CSA, wideband CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter sets, contention-free (CF) parameter sets, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG10H illustrates a flow chart of an example process 1070 for wireless communication that supports communication between MLDs, according to some implementations. The process 1070 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1070 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. For the example of FIG10H , the process 1070 is performed by the AP MLD described with reference to FIG9 . In some implementations, the process 1070 of FIG10H can be performed after the AP MLD transmits a frame in block 904 of FIG9 . At block 1072, the first AP receives an indication of one or more critical updates for the corresponding secondary communication link from a secondary AP of an AP MLD associated with the corresponding secondary communication link. At block 1074, the first AP sends an unsolicited broadcast probe response frame on the first communication link, the broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary communication link. In some implementations, the transmission of the unsolicited broadcast probe response frame occurs within a time period following the most recent beacon frame transmission by the first AP from the AP MLD. In some cases, the most recent beacon frame transmission by the first AP from the AP MLD includes an indication of the transmission of the unsolicited broadcast probe response frame by the first AP from the AP MLD. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG11 illustrates a flow chart of an example process 1100 for wireless communication that supports communication between MLDs, according to some implementations. The process 1100 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1100 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG11 , the process 1100 is performed by a STA of a STA MLD. At block 1102, a STA MLD associates with a first access point (AP) MLD. The AP MLD includes one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD. At block 1104, the STA MLD receives a frame from the first AP on a first communication link of the AP MLD. The frame includes one or more command arguments for the first communication link, a first change sequence number (CSN) indicating the presence or absence of a critical update for the first communication link of the AP MLD, and one or more secondary CSNs, each of the one or more secondary CSNs indicating the presence or absence of a critical update for a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. In some implementations, the frame may be one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. In some implementations, the critical update may correspond to a change in one or more command arguments of a BSS associated with at least one of the first communication link or the one or more secondary communication links. In some implementations, the one or more instruction arguments may include at least one of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter sets, contention-free (CF) parameter sets, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, BSS color change, FILS parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. In some implementations, the first CSN may indicate a recent critical update to one or more command arguments for the first communication link, and each of the one or more secondary CSNs may indicate a recent critical update to one or more command arguments for the corresponding secondary communication link of the AP MLD. In some cases, the first CSN and the one or more secondary CSNs may be carried in a sequence counter field of a frame. In other cases, the first CSN and the one or more secondary CSNs may be carried in an information element. In some implementations, a frame includes a multilink element (MLE) that carries one or more secondary CSNs. In some cases, the MLE includes one or more per-link profile sub-elements, each of which carries a corresponding secondary CSN from the one or more secondary CSNs. In some other cases, the MLE may include a common parameter field that carries the one or more secondary CSNs. In some implementations, the frame may be a beacon frame including one or more per-link profile elements, each of the one or more per-link profile elements carrying a secondary CSN and a complete set of command parameters for a corresponding secondary communication link of the one or more secondary communication links. In some cases, each of the one or more per-link profile elements may be an information element (IE) including a corresponding secondary CSN of the one or more secondary CSNs. In some other implementations, a frame may include a Multi-Link Attribute (MLA) element, the MLA element including one or more per-link profile sub-elements, each of which carries a secondary CSN and a complete set of command arguments for a corresponding secondary communication link in one or more secondary communication links. In some cases, a frame may include a Reduced Neighbor Report (RNR) element carrying one or more secondary CSNs. In some other cases, the RNR element may include one or more Neighbor AP Information fields, each of which carries a corresponding secondary CSN of one or more secondary CSNs. In some implementations, the frame may be a beacon frame carrying one or more profiles, each of which carries a complete set of command arguments for a corresponding secondary communication link of one or more secondary communication links. In some other implementations, the frame may also include one or more Do Not Transmit (DNT) indications, each of which is associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. In some cases, the frame may also include a DNT indication for the first communication link. Each DNT indication may indicate whether the wireless communication device should refrain from transmitting on the corresponding secondary communication link of the AP MLD. In some cases, at least some wireless communication devices may monitor the first communication link instead of the one or more secondary communication links for the DNT indication. In some implementations, the DNT indication for the corresponding secondary communication link may be based on one or more of the following: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of a secondary AP of the AP MLD associated with the corresponding secondary communication link. FIG12A illustrates a flow chart of an example process 1200 for wireless communication that supports communication between MLDs, according to some implementations. The process 1200 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1200 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12A , the process 1200 is performed by a STA MLD. In some implementations, the process 1200 of FIG12A can be performed after the STA MLD receives a frame in block 1104 of FIG11 . At block 1202, the STA MLD increments a first CSN counter in a STA of the STA MLD based on a first CSN indicating the presence of a critical update for a first communication link for the AP MLD. At block 1204, the STA MLD increments one or more secondary CSN counters in a STA of the STA MLD based on one or more corresponding secondary CSNs indicating the presence of a critical update for one or more corresponding secondary communication links for the AP MLD. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12B illustrates a flow chart of an example process 1210 for wireless communication that supports communication between MLDs, according to some implementations. The process 1210 may be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 1210 may be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12B , the process 1210 is performed by a STA multi-link device (MLD). In some implementations, the process 1210 of FIG12B may be performed after the STA MLD receives the frame in block 1104 of FIG11 . At block 1212 , the STA MLD refrains from transmitting on each secondary communication link for which a corresponding DNT indicates a DNT condition. In some implementations, the frame may also include a DNT indicator for the first communication link. In some cases, the DNT indicator for the first communication link and one or more DNT indicators for one or more corresponding secondary communication links may be carried in the bitmap of the frame. In some implementations, the DNT indication for the corresponding secondary communication link can be based on one or more of the following: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of the secondary AP of the AP MLD associated with the corresponding secondary communication link. In some implementations, each of the one or more DNT indications may indicate whether the wireless communication device should avoid transmitting on the corresponding secondary communication link of the AP MLD. In some cases, the STAs of the STA MLD may monitor the first communication link instead of the one or more secondary communication links for the DNT indication. In some implementations, one or more DNT indicators for one or more corresponding secondary communication links may be carried in a multilink element (MLE) of a frame. In some cases, the MLE may include one or more per-link profile sub-elements, each of which carries a DNT indicator for a corresponding secondary communication link in the one or more secondary communication links. In some other cases, the one or more per-link profile sub-elements may be information elements (IEs). In some cases, the MLE may include a common parameter field that carries the one or more DNT indicators for the one or more corresponding secondary communication links. In some implementations, a frame may include a multi-link element (MLE) including one or more per-link profile sub-elements, wherein each per-link profile sub-element carries a DNT indication and a complete set of command arguments for a corresponding secondary communication link. In some implementations, one or more DNT indicators for one or more corresponding secondary communication links may be carried in a Reduced Neighbor Report (RNR) element of a frame. In some cases, the RNR element may include one or more neighbor AP information fields, where each neighbor AP information field carries a DNT indicator for a corresponding secondary communication link. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12C illustrates a flow chart of an example procedure 1220 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1220 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1220 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12C , the procedure 1200 is performed by a STA multi-link device (MLD). In some implementations, the procedure 1220 of FIG12C can be performed after the STA MLD receives the frame in block 1104 of FIG11 . At block 1222, the STA MLD receives an indication of a do not transmit (DNT) condition for a designated secondary communication link of one or more secondary communication links of the AP MLD from the first AP of the AP MLD on the first communication link. At block 1224, the STA MLD refrains from transmitting on the designated secondary communication link based on receiving the DNT indication. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12D illustrates a flow chart of an example procedure 1230 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1230 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1230 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12D , the procedure 1230 is performed by a STA multi-link device (MLD). In some implementations, the procedure 1230 of FIG12D can be performed after the STA MLD receives a frame in block 1104 of FIG11 . At block 1232 , the STA MLD receives an unsolicited broadcast probe response frame from a first AP of the AP MLD on a first communication link, the unsolicited broadcast probe response frame carrying a complete set of command arguments for a designated secondary communication link of the one or more secondary communication links. In some implementations, the transmission of an unsolicited broadcast probe response frame occurs within a time period following the most recent beacon frame transmission by the first AP from the AP MLD. In some cases, the most recent beacon frame transmission by the first AP from the AP MLD may include an indication of the transmission of an unsolicited broadcast probe response frame by the first AP from the AP MLD. In some implementations, the unsolicited broadcast probe response frame may carry a complete set of instruction arguments for each of one or more secondary communication links. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12E illustrates a flow chart of an example procedure 1240 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1240 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1240 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12E , the procedure 1240 is performed by a STA multi-link device (MLD). In some implementations, the procedure 1240 of FIG12E can be performed after the STA MLD receives a frame in block 1104 of FIG11 . At block 1242 , the STA MLD receives, from a first AP of the AP MLD on a first communication link, an indication of a critical update for a designated secondary communication link of one or more secondary communication links of the AP MLD. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12F illustrates a flow chart of an example procedure 1250 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1250 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1250 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and 6B , respectively. For the example of FIG12F , the procedure 1250 is performed by a STA multi-link device (MLD). In some implementations, the procedure 1250 of FIG12F can be performed after the STA MLD receives an indication of a critical update in block 1242 of FIG12E . At block 1252, the STA MLD sends a probe request frame on the first communication link. At block 1254, the STA MLD receives a response frame from the first AP of the AP MLD on the first communication link. In some implementations, the response frame may carry a complete set of command arguments for a specified secondary communication link. In some implementations, the response frame may carry a complete set of command arguments for each of one or more secondary communication links. In some implementations, the probe request frame may be a broadcast probe request frame. In some implementations, the probe request frame may carry a CSN indicating a recently received critical update for a designated secondary communication link, and the response frame may carry an indication of one or more secondary CSNs for the designated secondary communication link that the STA of the STA MLD missed. In some implementations, the response frame may be a unicast probe response frame that carries one or more critical updates for the designated secondary communication link that the STA missed. In some implementations, the response frame may be a unicast probe response frame or a broadcast probe response frame that carries a complete set of command arguments for the designated secondary communication link. In some implementations, the response frame may be a broadcast probe response frame that carries a complete set of command arguments for each of the designated secondary communication link and other non-designated secondary communication links. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG12G illustrates a flow chart of an example procedure 1260 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1260 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1260 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG12G , the procedure 1260 is performed by a STA multi-link device (MLD). In some implementations, the procedure 1260 of FIG12G can be performed after the STA MLD receives an indication of a critical update in block 1242 of FIG12E . At block 1262, the STA MLD sends a probe request frame on the designated secondary communication link. At block 1264, the STA MLD receives a response frame on the designated secondary communication link from the secondary AP of the AP MLD associated with the designated secondary communication link. In some implementations, the response frame may carry a complete set of command arguments for a specified secondary communication link. In some other implementations, the response frame may carry a complete set of command arguments for each of one or more secondary communication links. In some implementations, the probe request frame may be a broadcast probe request frame. In some implementations, the probe request frame may carry a CSN indicating a recently received critical update for a designated secondary communication link, and the response frame may carry an indication of one or more secondary CSNs for the designated secondary communication link that the STA of the STA MLD missed. In some cases, the response frame may be a unicast probe response frame that carries one or more critical updates for the designated secondary communication link that the STA missed. In some implementations, the response frame may be a unicast probe response frame or a broadcast probe response frame that carries a complete set of command arguments for the designated secondary communication link. In some other implementations, the response frame may be a broadcast probe response frame that carries a complete set of command arguments for each of the designated secondary communication link and other non-designated secondary communication links. In some implementations, the instruction argument set may include one or more of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target latency (TWT) parameters, basic service set (BSS) color change, fast initial link setup (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. FIG13 illustrates a flow chart of an example procedure 1300 for wireless communication that supports communication between MLDs, according to some implementations. The procedure 1300 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 1300 can be performed by a wireless communication device operating as or within a wireless station (STA), such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG13 , the procedure 1300 is performed by a STA MLD that includes at least a first STA. The first STA can be associated with a first communication link of an AP MLD, which can include one or more secondary communication links distinct from the first communication link. In some implementations, the AP MLD includes a first AP associated with the first communication link and one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD. At block 1302, a first STA receives a frame on a first communication link that includes an indication of an update to at least one command argument for a designated secondary communication link of an AP MLD. At block 1304, the STA MLD determines, based on receiving the indication of the update, that the first STA of the STA MLD cannot support the update to the at least one command argument for the designated secondary communication link. At block 1306, the STA MLD removes the designated secondary communication link from the multi-link (ML) context established between the STA MLD and the AP MLD. In some implementations, a designated secondary communication link may be removed from an ML context by sending an action frame to a first AP of an AP MLD over a first communication link. The action frame includes a request to update the ML context by removing the designated secondary communication link from the ML context. In some cases, the action frame may be an ML setup update action frame. In some other cases, the action frame may also include an element including one or more updates to a transmission identifier (TID) mapping associated with the ML context. In some cases, the one or more updates to the transmission identifier (TID) mapping may include remapping the TID from the designated secondary communication link to one or more of the first communication link or another non-designated secondary communication link among the one or more secondary communication links. In some other implementations, the designated secondary communication link may be removed from the ML context by sending an action frame to the first AP of the AP MLD over the first communication link, the action frame including a request to disable the designated secondary communication link. In some other implementations, the designated secondary communication link is removed from the ML context without disassociating from the first AP of the AP MLD. In some cases, the designated secondary communication link is removed from the ML context without tearing down the ML context. In some implementations, the designated secondary communication link may be removed from the ML context by remapping a transmission identifier (TID) from the designated secondary communication link to one or more of the first communication link or other non-designated secondary communication links among the one or more secondary communication links. In some other implementations, the designated secondary communication link may be removed from the ML context by maintaining a sleep or doze state of the STA MLD on the designated secondary communication link. FIG14A illustrates a timing diagram depicting an example multi-link communication 1400 according to some implementations. In the example of FIG14A , MLD communication can be performed between a first wireless communication device ("first device D1") and a second wireless communication device ("second device D2"). Each of devices D1 and D2 can be any suitable wireless communication device, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively, or one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In timing diagram 1400, first device D1 can be a transmitting device, and second device D2 can be a receiving device. Each of first device D1 and second device D2 can be an MLD. For example, first device D1 can be an AP MLD, and second device D2 can be a STA MLD. At time t At 1, first device D1 transmits a first packet 1401 on a first communication link (not shown for simplicity). First packet 1401 includes ML information (such as capabilities and parameters) for at least the first communication link and a second communication link (not shown for simplicity). Although the example of FIG14A is described with respect to the first and second communication links, in some implementations, any number of additional communication links may exist, such as a third, fourth, or fifth communication link. The first and second communication links may operate on different frequency bands or on different channels within the same frequency band. For example, the first communication link may operate on the 2.4 GHz band, the second communication link may operate on the 5 GHz band, and another link (not shown for simplicity) may operate on the 6 GHz band. First packet 1401 may be a beacon frame or any other frame that can be used to transmit ML information. In some implementations, the ML information may include one or more of the following: a first operational class for the first communication link; a first wireless channel for the first communication link; a first BSSID for the first communication link; a second operational class for the second communication link; a second wireless channel for the second communication link; or a second BSSID for the second communication link. In some implementations, some or all of the ML information may be included in the Link Attributes element of first packet 1401 (as further described with respect to Figures 14B and 15 ) or in the Multilink element of first packet 1401 (as further described with respect to Figures 14B , 15 , and 16A-16C ). In some aspects, at least one of the operational class, wireless channel, or BSSID may be different. As a non-limiting example, a pair of APs with the same operational class may communicate on the same wireless channel. However, the pair of APs may be physically separate (non-co-located) and, therefore, may have different MAC addresses (BSSIDs). At time t 1 and t 14B . In some implementations, first device D1 and second device D2 can establish at least one ML communication parameter for communicating over the first and second communication links, as further described with respect to FIG. 14B . Briefly, because first packet 1401 includes ML information (such as ML capabilities, ML command arguments and constraints, and other information) about all links on which first device D1 is operating, aspects of the present disclosure enable a STA MLD (such as second device D2) to discover an AP MLD (such as first device D1) over any link on which the AP MLD has established a BSS. At time t At 3, the second device D2 sends an MLA request 1411 on the first communication link based at least in part on the ML information. The MLA request 1411 can be an association request frame. In some implementations, the MLA request 1411 can include a preference for one or more of the first communication link or the second communication link to be designated as an anchor link, as further described with respect to FIG. 14B and FIG. 15 . In some aspects, a client device (such as the second device D2) can save power by waiting on the anchor link (e.g., waiting for a beacon) when there is no active transmission traffic. At time t 3 and t 4, the first device D1 receives an MLA request 1411 from the second device D2 over the first communication link. In some aspects, the MLA request 1411 can indicate one or more capabilities or security parameters of the second device D2. At time t At 4, the first device D1 sends a second packet 1402 on the first communication link, and the second packet 1402 includes ML information for at least the first communication link and the second communication link. In some implementations, the second packet 1402 can be an association response frame. In some other implementations, the second packet 1402 can be some other appropriate frame. In some aspects, the second packet 1402 can confirm or renegotiate one or more of the second device D2 capabilities for association on multiple links. Therefore, the first device D1 and the second device D2 can establish a common security context that can be applied to multiple links. For example, the first device D1 and the second device D2 can establish a single encryption key that can be applied to each of the first communication link and the second communication link. In some implementations, the first device D1 may assign a different AID to each link. For example, in the second packet 1402, the first device D1 may indicate that the AID for the first communication link is 25 and the AID for the second communication link is 26. In some other implementations, the first device D1 may assign a common AID across all links. At time t 4 and t 5, the second device D2 receives the second packet 1402 from the first device D1 on the first communication link. At 6, the first device D1 associates with the second device D2 based at least in part on the ML information in the second packet 1402. In some implementations, at time t 6 and t 7, the first device D1 and the second device D2 can establish a BA communication period for at least one TID. Finally, at time t At 7 , the first device D1 may communicate with the second device D2 on the first or second communication link based on the association with the second wireless communication device on the first communication link. By exchanging ML information included in first packet 1401, first device D1 and second device D2 can implement various aspects of the present disclosure to facilitate faster discovery of links available for communication between first device D1 and second device D2. Furthermore, by exchanging ML information included in second packet 1422 or MLA request 1431, first device D1 or second device D2 can also implement various aspects of the present disclosure to facilitate faster switching between links and more efficient communication on those links. For example, first device D1 and second device D2 can switch from communicating on a first communication link to communicating on a second communication link without disassociating or reassociating, thereby saving time and resources. Specifically, second device D2 can receive ML information (such as in first packet 1401) for the first communication link, the second communication link, or any link on which first device D1 has established a BSS. Thus, various aspects of the present disclosure enable second device D2 to discover first device D1 on any link on which first device D1 has established a BSS. FIG14B illustrates a timing diagram depicting an example multi-link communication 1420 according to some implementations. In the example of FIG14B , communications can be exchanged between a first wireless communication device ("first device D1") and a second wireless communication device ("second device D2"). Each of devices D1 and D2 can be any suitable wireless communication device, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively, or one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In timing diagram 1420, first device D1 can be a transmitting device, and second device D2 can be a receiving device. Each of devices D1 and D2 can be an MLD. In some implementations, multi-link communication 1420 can be a more detailed example of multi-link communication 1400 shown in FIG14A . At time t At 1, the first device D1 sends a first packet 1421 on a first communication link (not shown for simplicity). As described with respect to FIG. 14A, the first packet 1421 may include ML information for at least the first communication link and a second communication link (not shown for simplicity). Although the example of FIG. 14B is described in terms of the first and second communication links, in some implementations, there may be any number of additional communication links, such as a third, fourth, or fifth communication link. For example, the first packet 1421 may uniquely identify each link based on a limited set of information (a tuple). In some implementations, the tuple may include { }, which may be indicated in a field (such as a 6-octet field) of the first packet 1421, where Indicates the class of operation to be used for the link, Indicates the channel used for the link, and Indicates the BSSID used for the link. The instance operation class can be one of 2.4 GHz spectrum, 5 GHz spectrum, or 6 GHz spectrum. In the example of FIG14B , first packet 1421 is shown as including a Link Attributes element. "Link Attributes Element" is an example name, and in some implementations, the Link Attributes element may have any other name. The Link Attributes element may include specific ML information for one or more links. In some cases, the Link Attributes element may include discovery information such as a first operating class, a first wireless channel, and a first BSSID for a first communication link. In this example, the Link Attributes element is also shown as including an Anchor field. The Anchor field can indicate that the first communication link is an anchor link. For example, if the Anchor bit in the profile for the first communication link in the Link Attributes element is set to 1 or some other suitable value, then the first communication link can be an anchor link. Additionally or alternatively, the Anchor field can indicate that the first communication link is not an anchor link. For example, if the Anchor bit in the profile for the first communication link in the Link Attributes element is set to 0 or some other suitable value, then the first communication link may not be an anchor link. In some other implementations, setting the Anchor bit in the Anchor field to 0 can indicate that the first device D1 has not yet specified an anchor link. First packet 1421 is also shown as including a Multi-Link Element (MLE). "Multi-Link Element" is an example name, and in some implementations, the MLE may have any other name. The MLE may include certain ML information for one or more links other than the first or primary communication link. As an example, the MLE may include ML information for one or more secondary communication links (such as the second and third communication links). For the purposes of this discussion, the first communication link may be referred to as the "first communication link," and each of the one or more other links (such as the second communication link) may be referred to as a "secondary communication link." The MLE may include one or more per-link profile sub-elements, each of which may include ML information specific to a different secondary communication link. As an example, one of the per-link profile sub-elements may include a second operating class, a second wireless channel, and a second BSSID for the second communication link. In some implementations, the per-link profile sub-element for the second communication link may indicate one or more link attributes that differ between the first and second communication links. Example implementations of the MLE are illustrated in Figures 15 and 16A-16C. At time t 1 and t 2, second device D2 receives a first packet 1421 from first device D1 on a first communication link. In some implementations, first device D1 and second device D2 may establish at least one ML communication parameter for communicating on the first communication link based on information included in the link attribute element. Some example ML communication parameters may include, but are not limited to, frequency band, high throughput (HT) capability, very high throughput (VHT) capability, high efficiency (HE) capability, or extremely high throughput (EHT) capability. In some implementations, first device D1 and second device D2 may establish at least one ML communication parameter for communicating on different communication links based on information included in the MLE. For example, first device D1 and second device D2 may establish at least one ML communication parameter for communicating on the second communication link based on information included in the corresponding per-link profile sub-element in the MLE for the second communication link. In some aspects, at least one of the ML communication parameters may be the same for each of the first and second communication links. At time t At 3, the second device D2 sends an MLA request 1431 on the first communication link based at least in part on the ML information included in the first packet 1421. In some implementations, for example, when the anchor field of the first packet 1421 does not yet specify an anchor link, the MLA request 1431 can indicate a preference for one or more of the first communication link or the second communication link to be designated as an anchor link. For example, the second device D2 can indicate its preference for an anchor link by setting the anchor bit to 1 for the preferred anchor link in the MLA request 1431. In some aspects, the second device D2 can indicate more than one preferred anchor link by setting the anchor bit to 1 for each preferred anchor link in the MLA request 1431. At time t 3 and t 4, the first device D1 receives an MLA request 1431 from the second device D2 on the first communication link. At time t At 4, first device D1 sends a second packet 1422 over the first communication link. Second packet 1422 includes ML information for at least the first communication link and the second communication link. In some implementations, if second device D2 indicates a preference for anchor links in MLA request 1431, first device D1 may indicate the designated anchor link for second device D2 by setting the anchor bit to 1 (or some other suitable value) for one of the links in second packet 1422. In some aspects, even if second device D2 indicates a preference for a particular link as the anchor link, first device D1 may designate one or more different links as anchor links. At time t 4 and t 5, the second device D2 receives the second packet 1422 from the first device D1 on the first communication link. Using the ML information in the second packet 1402, the first device D1 and the second device D2 can then, for example, 5 and t 6. In some implementations, the first device D1 and the second device D2 can be associated by establishing a common security context between a first MAC-SAP endpoint of the first wireless communication device and a second MAC-SAP endpoint of the second wireless communication device. In some aspects, each of the first and second MAC-SAP endpoints can be used to communicate on both the first and second communication links. In some aspects, the common security context can include a single encryption key shared by the first MAC-SAP endpoint and the second MAC-SAP endpoint. At time t 6 and t 7, the first device D1 and the second device D2 can jointly establish a common BA communication period for one or more TIDs. Therefore, the first device D1 and the second device D2 can map the MSDU for the one or more TIDs to one or more of the first and second communication links. By establishing a common BA communication period and mapping one or more TIDs, the first device D1 and the second device D2 can implement various aspects of the content of the present case to map (or remap, associate or reassociate) one or more TIDs to multiple links without tearing down the common BA communication period or establishing a new BA communication period. Subsequently, the first device D1 and the second device D2 can communicate on the first communication link or the second communication link according to their respectively mapped TIDs. In some implementations, at time t 3 and t The BA communication period is established during the "MLA establishment" period between 6. At time t After time t 7, one or more link conditions (such as latency) may change, causing the first device D1 to remap one or more TIDs to one or more different links. As a non-limiting example, at time t 6 and t 7, the first device D1 may have initially set the first TID (such as ) is mapped to the first communication link. Therefore, the first device D1 and the second device D2 can be at time t 7 Before exchanging on the first communication link At time t 7After that, the first device D1 can Remap to the second communication link. In some implementations, the first device D1 may indicate in the third packet 1423 In some aspects, the first device D1 may indicate in the ADDBA capability field of the third packet 1423 that the first device D1 is capable of remapping the second device D2. In some implementations, the first device D1 may be configured to remap the 7 and t 8, one or more additional packets are sent between N packets are shown. At time t 7 and t 8, the first device D1 may remap one or more TIDs from one communication link to another communication link. The first device D1 may indicate the remapping to the second device D2 in the third packet 1423. For example, the first device D1 may remap the first TID (such as ) from the first communication link to the second communication link, and indicates the remapping in the third packet 1423. Upon receiving the third packet 1423, the second device D2 can send a packet with The packet is switched to be sent on the second communication link with Since the second device D2 has received information about each of the first and second communication links from the first packet 1421 or the second packet 1422, the second device D2 can receive the information about each of the first and second communication links from the first packet 1421 or the second packet 1422. The communication link is switched to the Communication is performed over the second communication link without disassociating or reassociating with the first device D1, thereby saving time and resources. As another non-limiting example, the first device D1 and the second device D2 may establish a common BA communication period together. In some implementations, the first device D1 may indicate that one or more of the communication links are active or enabled (available for communication), or that one or more of the communication links are inactive or disabled (unavailable for communication). In this example, the first device D1 may indicate that each of the first and second communication links is active, and the third communication link is inactive. For example, when establishing the common BA communication period, the first device D1 may set the first bit corresponding to the first communication link to 1, the second bit corresponding to the second communication link to 1, and the third bit corresponding to the third communication link to 0. Thus, the common BA communication period may Mapped to the first communication link and the second communication link instead of the third communication link. Subsequently, the conditions of one or more links may change. For example, the interference on the third communication link may decrease, and the interference on the second communication link may increase. Therefore, in this example, the first device D1 may send a single signal (such as the third packet 1423) to dynamically map Remap to the first communication link and the third communication link. For example, the third packet 1423 may indicate that the first bit is set to 1, the second bit is set to 0, and the third bit is set to 1. Since the second device D2 has received information about each communication link and established a common BA communication period with the first device D1, the second device D2 can dynamically Communication switching is performed on the first and second communication links to Communicating over the first and third communication links without disassociating or reassociating with the first device D1 and without sending additional communications to the first device D1 saves time and resources. Additionally or alternatively, the first device D1 may use the third packet 1423 to dynamically map one or more other TIDs to any subset of the communication links. As a non-limiting example, the third packet 1423 may dynamically map Mapped to the third communication link, Mapped to the first communication link and the second communication link, 3 is mapped to the fourth communication link, and 6 to all of the first, second, third, and fourth communication links. Additionally or alternatively, the client device can indicate to the first device D1 that the client device is capable of operating on a single link, despite having more than one link enabled. For example, the second device D2 may have a single antenna and, therefore, be capable of operating on a single link. In this example, the first device D1 can dynamically map the TID to the single communication link for communicating with the second device D2. FIG15 illustrates an example frame 1500 including a link attribute element 1510 and a multi-link element (MLE) 1520 that can be used for communication between wireless communication devices. Frame 1500 can be a beacon frame, an association frame, or some other suitable frame. In some aspects, frame 1500 can be an example implementation of the first packet 1401, MLA request 1411, or second packet 1402 described with respect to FIG14A , or an example implementation of the first packet 1421, MLA request 1431, second packet 1422, or third packet 1423 described with respect to FIG14B . In some implementations, frame 1500 can be sent by first device D1 and received by second device D2, or vice versa. For ease of explanation, some information elements of frame 1500 may also be referred to as "fields," "subfields," "elements," or "sub-elements," and for the purposes of this discussion, these information elements may be considered interchangeable. In some implementations, any other suitable terminology may be used to refer to the information elements of frame 1500 . The link attribute element 1510 may include information about the first communication link as described with respect to Figures 14A and 14B. In some implementations, the link attribute element 1510 may include discovery information for the first communication link of the MLD. In some other implementations, the link attribute element 1510 may include discovery information for one or more secondary communication links of the MLD. Link attributes element 1510 is shown as including a plurality of fields, including: element ID field 1551, length field 1552, element ID extension field 1553, control field 1554, operation class field 1555, channel number field 1556, BSSID field 1557, timing synchronization function (TSF) offset field 1558, and beacon interval field 1559. In some implementations, element ID field 1551 can be one octet long and include an identifier for link attributes element 1510. In some aspects, link attributes element 1510 can facilitate establishing a common BA communication period between first device D1 and second device D2, as described with respect to FIG. 14B . In some implementations, length field 1552 can be one octet long and indicate the length of link attributes element 1510. In some implementations, element ID extension field 1553 can be one octet long. In some implementations, the operation class field 1555 can be 0 octets or 1 octet long and indicate the operation class used for the first communication link. In some implementations, the channel number field 1556 can be 0 octets or 1 octet long and indicate the channel number used for the first communication link. In some implementations, BSSID field 1557 can be 0 or 6 octets long and indicates the BSSID associated with the first communication link. In some implementations, TSF Offset field 1558 can be 0 or 2 octets long and indicates the TSF offset timing value for packets sent on the first communication link. In some aspects, a value of 0 in TSF Offset field 1558 and Beacon Interval field 1559 can indicate that first device D1 is not transmitting beacons on the first communication link. In some implementations, Beacon Interval field 1559 can be 0 or 2 octets long and indicates the beacon interval used for beacons sent on the first communication link. In some aspects, the values ​​in TSF Offset field 1558 or Beacon Interval field 1559 can facilitate faster link switching for certain types of non-AP entities (e.g., STA MLDs with a single radio). In some implementations, first device D1 can indicate that beacons will not be transmitted on one or more links. For example, the first device D1 may indicate that it is able to communicate on the second communication link and that the second communication link is dedicated to a data-only channel. In this way, the first device D1 may indicate that the second device D2 may utilize the second communication link, but the first device D1 will not broadcast a beacon on the second communication link. In some implementations, the control field 1554 can be 1 octet (8 bits) long and include multiple sub-elements, or "sub-fields," "fields," or "control information." These sub-elements can include a link ID sub-element 1561 (bits 1 and 2), an active link sub-element 1562 (bit 3), a separate MLA bit map sub-element 1563 (bits 4-7), and an anchor sub-element 1564 (bit 8). In some implementations, the link ID sub-element 1561 can include a unique identifier for the first communication link. In some aspects, the first device D1 can assign the unique identifier. In some implementations, the control field 1554 can exclude the link ID sub-element 1561, or the link ID sub-element 1561 can be included elsewhere in the frame 1500. In some implementations, the active link sub-element 1562 can indicate whether the first communication link is currently enabled. As a non-limiting example, the first device D1 may indicate that it is capable of operating on one or more links, and the first device D1 may provide a channel number and BSSID for each of the one or more links. In some implementations, the active links sub-element 1562 may indicate that the first device D1 is not operating on one or more links. As an example, the first device D1 may indicate that a particular link is disabled so that certain types of devices (such as non-EHT) do not attempt to communicate on the particular link. In some aspects, bits of the active link sub-element 1562 may be reserved for the first communication link. In some implementations, the independent MLA bit map sub-element 1563 may be a bit map indicating a specific (second) link with which the first communication link can perform an independent multi-link association (MLA). In some aspects, the bit positions of the independent MLA bit map sub-element 1563 may correspond to the value of the link ID sub-element 1561. In some aspects, the bit map may be a two-bit link identifier capable of indicating up to four combinations 0-3. For example, if the second bit is enabled (set to 1) for the second communication link, the first communication link can operate independently of the second communication link. In some implementations, anchor sub-element 1564 can indicate whether the first communication link is designated as an anchor link. In some aspects, for auxiliary links, if active link sub-element 1562 is set to 0 for a particular link, anchor sub-element 1564 can be retained and the particular link may not be used as an anchor link. For the example of FIG. 15 , fields 1551-1559 are included in link attribute element 1510. In some implementations, link attribute element 1510 may not include fields 1551-1559 or one or more of sub-elements 1561-1564. In some implementations, link attribute element 1510 may include one or more different information elements. As a non-limiting example, link attribute element 1510 may not include any of the operation class field 1555, channel number field 1556, BSSID field 1557, TSF offset field 1558, or beacon interval field 1559. As another non-limiting example, link attribute element 1510 may include each of the operation class field 1555, channel number field 1556, BSSID field 1557, TSF offset field 1558, and beacon interval field 1559. The MLE 1520 is also shown as including a common attributes sub-element 1525 and one or more per-link profile sub-elements 1530(1)-1530(n). The common attributes sub-element 1525 may include one or more attributes that are common to each communication link associated with the MLD (such as the first device D1 and the second device D2). In some cases, each of the per-link profile sub-elements 1530(1)-1530(n) may include a value for the most recent critical update for the corresponding secondary AP of the AP MLD. In other cases, each of the per-link profile sub-elements 1530(1)-1530(n) may indicate the presence or absence of a critical update associated with the corresponding secondary AP of the AP MLD. In some other implementations (not shown for simplicity), each of the per-link profile sub-elements 1530(1)-1530(n) may include each of the operating class field 1555, the channel number field 1556, the BSSID field 1557, the TSF offset field 1558, and the beacon interval field 1559, as further described with respect to FIG 11. And in some other implementations (not shown for simplicity), each of the per-link profile sub-elements 1530(1)-1530(n) may not include any of the operating class field 1555, the channel number field 1556, the BSSID field 1557, the TSF offset field 1558, or the beacon interval field 1559. FIG16A illustrates an example MLE 1600 that can be used for communication between wireless communication devices. In some aspects, MLE 1600 can be an example implementation of MLE 1520 described with respect to FIG15 . In some implementations, MLE 1520 can be included in a frame (such as frame 1500, a beacon frame, an association request frame, an association response frame, or any other suitable frame) transmitted by first device D1 and received by second device D2 (or vice versa). For ease of explanation, some information elements of MLE 1600 may be referred to as "fields," "subfields," "elements," or "subelements," and for the purposes of this discussion, these information elements may be considered interchangeable. In some implementations, any other suitable terminology may be used to refer to information elements of MLE 1600. MLE 1600 is shown as including a plurality of fields, including an element ID field 1601, a length field 1602, an element ID extension field 1603, a public parameter field 1604, and one or more optional sub-element fields 1605. In some implementations, element ID field 1601 may be one octet long and include an identifier for MLE 1600. In some implementations, length field 1602 may be one octet long and indicate the length of MLE 1600. In some implementations, element ID extension field 1603 may be one octet long. In some implementations, public parameter field 1604 may be one octet long and include common information for each secondary communication link. Although only one optional sub-element field 1605 is shown for simplicity, MLE 1600 may include any suitable number of optional sub-element fields 1605. In some implementations, each of the optional sub-element fields 1605 may correspond to one of the secondary communication links and may include ML information (or "ML attributes") for the corresponding secondary communication link, which is different from the first communication link. To save bits, in some aspects, ML attributes not included in the corresponding MLE 1600 may be assumed to be inherited from the first communication link. As a non-limiting example, a link attribute element (such as link attribute element 1510 in FIG. 15 ) may include the beacon interval for the first communication link, and the optional sub-element field 1605 corresponding to the secondary communication link may not include the beacon interval for the secondary communication link. In this example, the beacon interval for the secondary communication link may be inherited from the beacon interval for the first communication link included in link attribute element 1510. In this manner, one or more information elements in the optional sub-element field 1605 corresponding to the secondary communication link may be excluded or may include different information. In some other implementations, the MLE 1600 may include a single optional sub-element field 1605 that includes ML information for all or a subset of the secondary communication links. Optional sub-element fields 1605 are shown as including a plurality of fields, including a sub-element ID=0 field 1611, a length field 1612, and a data field 1613. In some implementations, sub-element ID=0 field 1611 can be 1 octet long and include an identifier (such as a value between 0 and 255) for the corresponding optional sub-element field 1605. In some aspects, values ​​1-255 can be reserved. In some implementations, the length field 1612 can be 1 octet long and indicate the length of the corresponding optional sub-element field 1605. In some implementations, the data field 1613 can have a variable length and can include ML information for the corresponding secondary communication link. In some implementations, the data field 1613 can be an example implementation of one of the per-link profile sub-elements 1530(1)-1530(n) described with respect to FIG. 15 . 16B illustrates an example data field 1620 that may be used for communication between wireless communication devices. Data field 1620 may be an example implementation of data field 1613 of FIG16A and is shown as including a plurality of fields, including an element ID field 1621, a length field 1622, an element ID extension field 1623, a control field 1624, an operation class field 1625, a channel number field 1626, a BSSID field 1627, a TSF offset field 1628, and a beacon interval field 1629, which may be the same as or similar to the element ID field 1551, length field 1552, element ID extension field 1553, control field 1554, operation class field 1555, channel number field 1556, BSSID field 1557, TSF offset field 1558, and beacon interval field 1559, respectively, described with respect to FIG15 . In some implementations, the control field 1624 can be 1 octet long (8 bits) and include a plurality of sub-elements, including: a link ID sub-element 1641 (bits 1 and 2), an active link sub-element 1642 (bit 3), an independent MLA bit map sub-element 1643 (bits 4-7), and an anchor sub-element 1644 (bit 8), which can be the same as or similar to the link ID sub-element 1561, active link sub-element 1562, independent MLA bit map sub-element 1563, and anchor sub-element 1564, respectively, described with respect to FIG. 15 , except that they include information about the corresponding secondary communication link instead of the primary communication link. In some implementations, one or more information elements may be combined, added, moved (to one or more other information elements), removed, or otherwise modified for MLE 1600. Furthermore, the names shown for the information elements associated with MLE 1600 are example names, and in some implementations, one or more of information elements 1601-1644 may have different names. FIG16C illustrates an example data field 1630 that may be used for communication between wireless communication devices. In some implementations, data field 1630 may be an example implementation of data field 1613 of optional sub-element field 1605 of FIG16A . Data field 1630 is shown as including an element ID field 1631, a length field 1632, and an element ID extension field 1633. Element ID field 1631, length field 1632, and element ID extension field 1633 may be the same or similar to element ID field 1601, length field 1602, and element ID extension field 1603, respectively, except that element ID field 1631, length field 1632, and element ID extension field 1633 may include information about the corresponding secondary communication link instead of MLE 1600. In some aspects, element ID extension field 1633 may be 0 octets or 1 octet long. The data field 1634 may have a variable length and may indicate HT capability, VHT capability, HE capability, EHT capability, MLD capability, or other capabilities. FIG17A illustrates a sequence diagram depicting an example multi-link (ML) communication 1700 according to some implementations. In the example of FIG17A , ML communication 1700 can be performed between a STA of a STA MLD and an AP MLD comprising a first AP (AP1) and a second AP (AP2). AP1 can be associated with a primary communication link of the AP MLD, and AP2 can be associated with a secondary communication link of the AP MLD. In some implementations, AP1 and AP2 can be example implementations of one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively, and the STA can be example implementations of one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. AP1 generates a frame that includes one or more command arguments for a first communication link, a first change sequence number (CSN) or value indicating the presence or absence of a critical update for the first communication link for AP MLD, and one or more secondary CSNs or values, each indicating the presence or absence of a critical update for a corresponding secondary communication link for AP MLD. In some cases, the first CSN or value may be carried in a first change sequence field of the frame, and the one or more secondary CSNs may be carried in one or more corresponding secondary change sequence fields of the frame. In one implementation, a critical update flag or CSN change indicator may be carried in a critical update flag subfield of the frame. AP1 transmits a frame to a STA on the first communication link. In some implementations, the frame may be a beacon frame that includes a first change sequence field carrying a first CSN, one or more second change sequence fields carrying a second CSN, one or more per-link profile subelements carrying one or more command arguments for the first communication link, and a complete set of command arguments for the corresponding secondary communication link. Transmission of such beacon frames may reduce STA power consumption (eg, because the STA does not need to monitor the corresponding secondary communication link), may reduce frame exchange management burden, and may increase the size of the beacon frame. The STA receives the frame and obtains the command argument for the primary communication link, the CSN or value for the primary communication link, and the CSN or value for the secondary communication link. In this way, the STA can determine the current command argument and whether a critical update has already occurred for the primary AP and the associated primary communication link. It can also determine whether a critical update has already occurred for the secondary AP and the associated secondary communication link without monitoring the secondary communication link. AP1 receives a notification of a critical update for a secondary communication link and associated secondary AP from AP2. AP1 increments the secondary CSN or value corresponding to the secondary communication link and associated secondary AP and sends a frame to the STA on the first communication link. In some implementations, the frame may include the updated CSN or value for the secondary communication link and associated secondary AP. In some other implementations, the frame may include a complete set of command arguments for the secondary communication link and associated secondary AP. In some other implementations, the frame may include a complete set of command arguments for each of the secondary communication links associated with the corresponding secondary AP of the AP MLD. The STA may send a probe request frame to AP 1 on the first communication link. In some implementations, the probe request frame may include the most recently received CSN or value for the secondary communication link and the associated secondary AP. AP1 can identify the CSN for the secondary communication link and associated secondary AP that the STA missed (or otherwise incorrectly decoded). AP1 can send a response frame to the STA on the first communication link. In some implementations, the response frame carries the CSN for the secondary communication link and associated secondary AP that the STA missed. In some other implementations, the response frame carries a complete set of command arguments for the secondary communication link and associated secondary AP for which one or more command arguments were updated. In some other implementations, the response frame carries a complete set of command arguments for each secondary communication link associated with the corresponding secondary AP of the AP MLD. In some implementations, the response frame may be a unicast probe response frame that carries one or more critical updates for a designated secondary communication link that the STA missed. In some other implementations, the response frame may be a broadcast probe response frame that carries a complete set of command arguments for each secondary communication link associated with the corresponding secondary AP of the AP MLD. Sending a broadcast probe response frame that carries a complete set of command arguments for all secondary communication links can reduce STA power consumption (e.g., because the STA does not need to monitor any secondary communication links), reduce frame exchange management overhead, and increase the size of the broadcast probe response frame. Additionally or alternatively, AP1 may send an unsolicited broadcast probe response frame to the STA over the first communication link, the unsolicited broadcast probe response frame carrying a complete set of command parameters for the secondary communication link and the associated secondary AP. Sending an unsolicited broadcast probe response frame carrying a complete set of command parameters for the secondary communication link and the associated secondary AP may reduce the STA's power consumption (e.g., because the STA does not need to monitor the secondary communication link), may reduce the frame exchange management burden, and may increase the size of the unsolicited broadcast probe response frame (but not as much as the increase in the aforementioned broadcast probe response frame). FIG17B illustrates a sequence diagram depicting another example multi-link communication 1710 according to some implementations. In the example of FIG17B , multi-link communication 1710 can be performed between STAs of a STA MLD and an AP MLD comprising a first AP (AP1) and a second AP (AP2). AP1 can be associated with a primary communication link of the AP MLD, and AP2 can be associated with a secondary communication link of the AP MLD. In some implementations, AP1 and AP2 can be example implementations of one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively, and the STA can be example implementations of one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. AP1 generates a frame that includes one or more command arguments for a first communication link, a first change sequence number (CSN) or value indicating the presence or absence of a critical update for the first communication link for AP MLD, and one or more secondary CSNs or values, each indicating the presence or absence of a critical update for a corresponding secondary communication link for AP MLD, and transmits the frame to a STA on the first communication link. In some implementations, the frame may be a beacon frame that carries a first CSN in a first change sequence field, a second CSN in a corresponding secondary change sequence field, one or more command arguments for the first communication link in an MLE, and a complete set of command arguments for the corresponding secondary communication link in a corresponding per-link profile sub-element. Transmission of such a beacon frame may reduce STA power consumption (e.g., because the STA does not need to monitor the corresponding secondary communication link), reduce frame exchange management overhead, and increase the size of the beacon frame. The STA receives the frame and obtains the command arguments for the primary communication link, the CSN or value for the primary communication link, and the CSN or value for the secondary communication link. In this way, the STA can determine the current command arguments and whether a critical update has occurred for the primary communication link. It can also determine whether a critical update has occurred for the secondary communication link without monitoring the secondary communication link. AP1 receives a Do Not Transmit (DNT) indication for a secondary communication link from AP2. AP1 asserts the DNT indication for the secondary communication link and transmits a frame on the first communication link. The frame (which may be a unicast frame, a broadcast frame, or an unsolicited probe response frame) includes the asserted DNT indication for the secondary communication link. In some implementations, the DNT indication may be based on one or more of the following: a channel switch notification for the secondary communication link, a quiet time notification for the secondary communication link, or unavailability of a secondary AP of an AP MLD associated with the secondary communication link, and the DNT indication may indicate whether the wireless communication device should avoid transmitting on the secondary communication link of the AP MLD. In some cases, at least some wireless communication devices may monitor the first communication link instead of the secondary communication link for the DNT indication. In some implementations, the frame may be a unicast probe response frame that carries one or more critical updates for a designated secondary communication link that the STA missed. Transmission of such a unicast probe response frame may result in a minimum unicast probe response frame size and may increase frame exchange management overhead (e.g., because an additional frame may be required to carry the instruction arguments for the designated secondary communication link). In some other implementations, the frame may be a broadcast probe response frame that carries a complete set of instruction arguments for the designated secondary communication link. Transmission of such a broadcast probe response frame may increase frame size and reduce frame exchange management overhead. In some other implementations, the frame may be an unsolicited broadcast probe response frame that carries a complete set of instruction arguments for all secondary communication links. Transmission of such an unsolicited broadcast probe response frame may increase frame size and may also reduce frame exchange management overhead (e.g., compared to the aforementioned broadcast probe response frame). In this manner, the STA can determine that a DNT condition exists on the secondary communication link without monitoring the secondary communication link and avoid transmitting on the secondary communication link. In this manner, the STA can receive a DNT condition for the secondary communication link without consuming the power associated with performing a scanning operation on the secondary communication link. The STA can communicate with AP1 on the first communication link. FIG18 illustrates a timing diagram depicting an example multi-link communication 1800 according to some implementations. In the example of FIG18 , multi-link communication 1800 can be performed between a STA MLD and an AP MLD. The AP MLD is shown as including a first AP (AP1) associated with a first communication link (Link1) of the AP MLD and a second AP (AP2) associated with a secondary communication link (Link2) of the AP MLD. The STA MLD is shown as including a first station (STA1) and a second station (STA2). For the example of FIG18 , STA1 is associated with the first communication link (Link1), and STA2 is associated with the secondary communication link (Link2). In some implementations, AP1 and AP2 can be example implementations of one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively, and STA1 and STA2 can be example implementations of one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. Initially, the CSN of AP1 starts at 25, and the CSN of AP2 starts at 45. For the example of Figure 18, STA1 remains in the doze state on Link1. At time t At 0, AP1 sends a beacon frame on Link1 indicating CSN=25 for Link1. The beacon frame also includes an MLE indicating CSN=45 and DNT=0 for Link2. Neither STA1 nor STA2 receives the beacon frame from AP1. At time t At 1, AP2 sends a beacon on Link 2 indicating CSN = 45 for Link 2. The beacon frame also includes an MLE indicating CSN = 25 and DNT = 0 for Link 1. STA 2 receives the beacon frame and obtains CSN = 25 and DNT = 0 for Link 1, and CSN = 45 for Link 2. Based on DNT = 0, STA 2 decides to allow transmission on Link 1. At time t At 2, AP1 sends a beacon frame that includes an ECSA IE with Mode=1 and indicates an incremented CSN=26 for Link1. The beacon frame also includes an MLE indicating CSN=45 and DNT=0 for AP2. Neither STA1 nor STA2 receives a beacon frame from AP1. At time t 3 (which is at time t At TBTT (100 TBTT after 1), AP2 sends a beacon frame on Link2 indicating CSN=45 for Link2. The beacon frame also includes an MLE indicating CSN=26 and DNT=1 for Link1. STA2 receives the beacon frame, obtains CSN=26 and DNT=1 for Link1, and obtains CSN=45 for Link2. Based on DNT=1, STA2 avoids transmitting on Link1. In some implementations, at time t The beacon frame sent at 3 may indicate that AP2 will send a probe response frame including a critical update for Link1. At time t At 4, STA2 sends a probe request frame to AP2 on Link 2. The probe request frame includes the last CSN received by the STA for Link 1, which is CSN=25 (thereby indicating that STA2 missed a critical update on Link 1). At time t At 5, AP2 sends a probe response frame on Link2. The probe response frame includes an MLE indicating an ECSA of Mode=1 for Link1. In some implementations, the probe response frame can be a broadcast probe response frame that includes the complete profile for Link2. STA2 receives the probe response frame, obtains an ECSA of Mode=1 for Link1, and decides not to allow transmission on Link1. At time t At 6, AP1 sends a beacon frame on Link1, which indicates CSN=26 for Link1 and includes MLE, which indicates CSN=45 for Link2 and DNT=0 for Link2. The beacon frame also indicates ECSA mode=1 for Link1. Neither STA1 nor STA2 receives the beacon frame from AP1. At time t At 7, AP2 sends a beacon frame on Link2, which indicates CSN=45 for Link2 and includes an MLE indicating CSN=26 for Link1 and DNT=1 for Link1. STA2 receives the beacon frame, obtains CSN=26 and DNT=1 for Link1, and obtains CSN=45 for Link2. Based on DNT=1, STA2 avoids transmitting on Link1. At time t At 8, AP1 is on the new channel and sends a beacon frame on Link 1. This beacon frame indicates CSN = 26 for Link 1 and includes an MLE, which indicates CSN = 45 and DNT = 0 for Link 2. STA2 receives the beacon frame and obtains CSN = 26 and DNT = 0 for Link 1, and CSN = 45 for Link 2. Based on DNT = 0, STA2 can contend for medium access on Link 1. At time t At 9, AP2 transmits a beacon frame on Link 2, indicating CSN = 45 for Link 2 and including an MLA element indicating CSN = 26 for Link 1 and DNT = 0 for Link 1. STA2 receives the beacon frame, obtains CSN = 26 and DNT = 0 for Link 1, and obtains CSN = 45 for Link 2. Based on DNT = 1, STA2 avoids transmitting on Link 1. For the example in Figure 18, based on the ECSA on L1, at time t DNT for Link 1 is asserted at 2. In other implementations, DNT for Link 1 may be asserted for other reasons or conditions, including (but not limited to) other critical updates to Link 1, the presence of radar signals, the unavailability of AP 1, or some other error associated with AP 1 or Link 1. FIG19 illustrates an example MLE 1900 that can be used for communication between wireless communication devices. In some aspects, MLE 1900 can be an example implementation of MLE 1520 described with respect to FIG15 . In some implementations, MLE 1520 can be included in a frame (such as frame 1500, a beacon frame, an association request frame, an association response frame, or any other suitable frame) transmitted by first device D1 and received by second device D2 (or vice versa). For ease of explanation, some information elements of MLE 1900 may be referred to as "fields," "subfields," "elements," or "subelements," and for the purposes of this discussion, these information elements may be considered interchangeable. In some implementations, any other suitable terminology may be used to refer to information elements of MLE 1900. The MLE 1900 is shown as including a plurality of fields, including an element ID field 1902, a length field 1904, an element ID extension field 1906, a common parameters field 1908, and one or more per-link profile sub-elements 1910(1)–1910(n). In some implementations, the element ID field 1902 can be 1 octet long and include an identifier for the MLE 1900. In some implementations, the length field 1904 can be 1 octet long and indicate the length of the MLE 1900. In some implementations, the element ID extension field 1906 can be 1 octet long. In some implementations, the common parameters field 1908 can be 1 octet long and include common information for each secondary communication link. Each link profile sub-element 1910(1)–1910(n) may have a different length and may carry information including, but not limited to, the following: a CSN for the corresponding secondary communication link, a critical update for the corresponding secondary communication link, a command argument for the corresponding secondary communication link, a partial profile for the corresponding secondary communication link, a DNT indication for the corresponding secondary communication link, discovery information for the corresponding secondary communication link, and capability information for the corresponding secondary communication link. To save bits, in some aspects, attributes, capabilities, command arguments, or other values ​​not included in the corresponding per-link profile sub-element 1910 may be assumed to be inherited from the first communication link. As a non-limiting example, a link attributes element (such as link attributes element 1510 of FIG. 15 ) may include a CSN for the first communication link, and a per-link profile sub-element 1910 corresponding to a secondary communication link may not include a CSN for the secondary communication link. In this example, the CSN for the secondary communication link may be inherited from the CSN for the first communication link included in the link attributes element 1510. In this manner, one or more of the per-link profile sub-elements 1910(1)–1910(n) may be excluded or may include different information. In some other implementations, the MLE 1900 may include a single per-link profile sub-element 1910 that includes information for all or a subset of the secondary communication links. In some implementations, the data field 1916 may include a plurality of sub-elements, including: a link ID sub-element 1932, a critical update field 1934, a DNT field 1936, and one or more elements 1938(1)-1938(n) carrying any appropriate information for the corresponding secondary communication link. In some implementations, one or more information elements or fields may be combined, added, moved (to one or more other information elements), removed, or otherwise modified for MLE 1900. Furthermore, the names shown for information elements or fields associated with MLE 1900 are example names, and in some implementations, one or more of the information elements or fields may have different names. 20 illustrates an example of a simplified neighbor report (RNR) element 2000 that may be used for communication between wireless communication devices. The RNR element 2000 is shown as including an element ID field 2002, a length field 2004, and one or more neighbor AP information fields 2006 (for simplicity, only one neighbor AP information field is shown). In some implementations, each neighbor AP information field 2006 includes a TBTT information header 2011, an operation class field 2012, a channel number field 2013, a TBTT information set field 2014, a critical update field 2015, and a DNT field 2016. The critical update field 2015 may carry an indication of a critical update for the corresponding secondary communication link, and the DNT field 2016 may carry a DNT indication for the corresponding secondary communication link. In some other implementations, the RNR element 2000 may be extended to include a link ID field that stores one or more unique link IDs that can be used to map entries in the neighbor AP information field 2006 to information stored in each link profile sub-element in the MLE. In some implementations, one or more information elements or fields may be combined, added, moved (to one or more other information elements), removed, or otherwise modified for the RNR element 2000. Furthermore, the names shown for the information elements or fields associated with the RNR element 2000 are example names, and in some implementations, one or more of the information elements or fields may have different names. FIG21 illustrates a sequence diagram 2100 depicting another example multi-link communication 2100 according to some implementations. In the example of FIG21 , the ML communication 2100 can be performed between an AP MLD and a STA MLD. In some implementations, the AP MLD can be an example implementation of one of the APs 102 and 602 described above with reference to FIG1 and 6A , respectively, and the STA MLD can be an example implementation of one of the STAs 104 and 604 described above with reference to FIG1 and 6B , respectively. The AP MLD and the STA MLD exchange one or more of discovery information, authentication information, or association information over a first communication link. In some implementations, the first communication link is associated with a first AP of the AP MLD and a first STA of the STA MLD. The AP MLD and the STA MLD establish a multi-link (ML) context based on one or more of the exchanged discovery information, authentication information, or association information. In some implementations, the ML context includes identification of one or more communication links that can be used for communication between the AP MLD and the STA MLD. The AP MLD sends a first frame to the STA MLD on a first communication link. The first frame may include a request to modify the identification of one or more communication links in the ML context. In some implementations, the AP MLD receives the first frame from the STA MLD. The AP MLD receives a second frame from the STA MLD on the first communication link. The second frame may be a response to the first frame and indicate acceptance, rejection, or modification of the request. In some implementations, the AP MLD sends the second frame to the STA MLD. The AP MLD determines whether the second frame indicates acceptance, rejection, or modification of the request included in the first frame. The AP MLD selectively modifies identification of one or more communication links in the ML context based on the determination of whether the second frame indicates acceptance, rejection, or modification of the request. In some implementations, the AP MLD sends a third frame to the STA MLD on the first communication link. In some implementations, the third frame includes a request to add at least one additional communication link to the identifiers of one or more communication links in the ML context. In some implementations, the third frame includes an action frame that includes a link identifier that uniquely identifies the at least one additional communication link. In some implementations, the AP MLD receives the third frame from the STA MLD. In some cases, the AP MLD receives a fourth frame from the STA MLD on the first communication link. The fourth frame may be a response to the third frame and indicate acceptance or rejection of the request in the third frame. If the fourth frame indicates acceptance of the request included in the third frame, the AP MLD adds at least one additional communication link to the identifiers of one or more communication links in the ML context. If the fourth frame indicates rejection of the request included in the third frame, the AP MLD refrains from adding the at least one additional communication link to the identifiers of one or more communication links in the ML context. In some implementations, the AP MLD sends the fourth frame to the STA MLD. In some implementations, the AP MLD sends a fifth frame to the STA MLD on the first communication link. In some implementations, the fifth frame includes a request to delete at least one communication link from the identification of one or more communication links in the ML context. In some implementations, the fifth frame includes an action frame including a link identifier that uniquely identifies the at least one communication link. In some implementations, the AP MLD receives the fifth frame from the STA MLD. In some cases, the AP MLD receives a sixth frame from the STA MLD on the first communication link. The sixth frame may be a response to the fifth frame and indicate acceptance or rejection of the request in the fifth frame. If the sixth frame indicates acceptance of the request included in the fifth frame, the AP MLD deletes the at least one communication link from the identifiers of the one or more communication links in the ML context. If the sixth frame indicates rejection of the request included in the fifth frame, the AP MLD refrains from deleting the at least one communication link from the identifiers of the one or more communication links in the ML context. In some implementations, the AP MLD sends the sixth frame to the STA MLD. In some implementations, the AP MLD sends a seventh frame to the STA MLD on the first communication link. In some implementations, the seventh frame includes a request to change at least one of the identified communication links to a new communication link. In some implementations, the seventh frame includes an action frame that includes a link identifier that uniquely identifies the new communication link. In some implementations, the AP MLD receives the seventh frame from the STA MLD. In some cases, the AP MLD receives an eighth frame from the STA MLD on the first communication link. The eighth frame may be a response to the seventh frame and indicate acceptance or rejection of the request included in the seventh frame. If the eighth frame indicates acceptance of the request included in the seventh frame, the AP MLD changes at least one communication link to a new communication link identified in the ML context. If the eighth frame indicates rejection of the request included in the seventh frame, the AP MLD refrains from changing at least one communication link to the new communication link identified in the ML context. In some implementations, the AP MLD sends the eighth frame to the STA MLD. FIG22 illustrates a flow chart of an example process 2200 for wireless communication that supports modifying a communication link between MLDs, according to some implementations. The process 2200 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 2200 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the process 2200 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In some implementations, at block 2202, the process 2200 begins by exchanging one or more of discovery information, authentication information, or association information between a first AP of the AP MLD and a first wireless STA of the STA MLD over a first communication link associated with the first AP of the AP MLD and associated with a first STA of the STA MLD. At block 2204, the process 2200 continues by establishing a multi-link (ML) context between the AP MLD and the STA MLD based on the one or more of the exchanged discovery information, authentication information, or association information, wherein the ML context includes identification of one or more communication links that can be used for communication between the AP MLD and the STA MLD. At block 2206, the process 2200 continues by sending or receiving a first frame to or from the STA MLD over the first communication link, the first frame including a request to modify identification of one or more communication links in the ML context. At block 2208, the process 2200 continues by receiving or sending a second frame from or to the STA MLD on the first communication link, the second frame being a response to the first frame and indicating acceptance, rejection, or modification of the request. At block 2210, the process 2200 continues by selectively modifying the identification of one or more communication links in the ML context based on whether the second frame indicates acceptance, rejection, or modification of the request. In some implementations, the ML context includes a common security context between a first media access control service access point (MAC-SAP) endpoint of the AP MLD and a second MAC-SAP endpoint of the STA MLD. In some cases, each of the first and second MAC-SAP endpoints is configured to communicate over a communication link identified by the ML context. In some implementations, the first frame is a management frame. In some cases, the management frame is an association request frame, a reassociation request frame, an association response frame, or a reassociation response frame. In some other cases, the management frame is a protected action frame. The protected action frame may indicate one or more of the following: the maximum number of communication links supported by the AP MLD or STA MLD, or the number of currently available communication links associated with the AP MLD. The protected action frame may also include one or more group transient keys (GTKs). In some implementations, the protected action frame includes protected ML information, which includes one or more of the following: a public safety context, block acknowledgement (BA) communication period information, a mapping between a transport identifier (TID) value and a communication link associated with an AP MLD, command arguments for an AP MLD or a STA MLD, or capability information for an AP MLD or a STA MLD. In some cases, the protected ML information is included in one or more fields or information elements (IEs) carried in the protected action frame. FIG23 illustrates a flow chart of an example process for wireless communication that supports modifying a communication link between MLDs, according to some other implementations. The process 2300 can be performed by a first wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 2300 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. In other implementations, the process 2300 can be performed by a wireless communication device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively. In some implementations, at block 2302, the process 2300 begins by sending or receiving a protected action frame to or from a STA MLD, the protected action frame indicating the maximum number of communication links supported by the AP MLD or the STA MLD, or the current number of available communication links associated with the AP MLD. FIG24 illustrates a flow chart of an example process for wireless communication that supports modifying communication links between MLDs, according to some other implementations. Process 2400 may be performed by a first wireless communication device (such as wireless communication device 500 described above with reference to FIG5 ). In some implementations, process 2400 may be performed by a wireless communication device operating as or within a STA (such as STA 104 or 604 described above with reference to FIG1 and FIG6B , respectively). In other implementations, process 2400 may be performed by a wireless communication device operating as or within an AP (such as AP 102 or 602 described above with reference to FIG1 and FIG6A , respectively). In some implementations, operation 2400 may be an implementation of selectively modifying the identification of one or more communication links at block 2210 of operation 2200 in FIG22 . In some other implementations, operation 2400 may be performed after the identification is selectively modified at block 2210 of operation 2200 in FIG22 . In some implementations, at block 2402, the process 2400 begins by determining whether the second frame indicates acceptance or rejection of a request included in the first frame. In some cases, at block 2404, if the second frame indicates acceptance of the request included in the first frame, the process 2400 proceeds by adding at least one additional communication link to an identification of one or more communication links in the ML context based on the second frame indicating acceptance of the request. In some other cases, at block 2406, if the second frame indicates rejection of the request included in the first frame, the process 2400 proceeds by refraining from adding the at least one additional communication link to an identification of one or more communication links in the ML context based on the second frame indicating rejection of the request. In some implementations, the first frame includes a request to add at least one additional communication link to an identification of one or more communication links in the ML context. In some cases, the first frame is an action frame that includes a link identifier that uniquely identifies the at least one additional communication link. In some cases, the action frame also includes one or more of the following: a media access control (MAC) address of a corresponding STA of a STA MLD associated with the at least one additional communication link, or a MAC address of a corresponding AP of an AP MLD associated with the at least one additional communication link. In some implementations, the at least one additional communication link is a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. FIG25 illustrates a flow chart of an example process for wireless communication that supports modifying communication links between MLDs, according to some other implementations. Process 2500 may be performed by a first wireless communication device (such as wireless communication device 500 described above with reference to FIG5 ). In some implementations, process 2500 may be performed by a wireless communication device operating as or within a STA (such as STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively). In other implementations, process 2500 may be performed by a wireless communication device operating as or within an AP (such as APs 102 and 602 described above with reference to FIG1 and FIG6A , respectively). In some implementations, operation 2500 may be an implementation of selectively modifying the identification of one or more communication links at block 2210 of operation 2200 in FIG22 . In some other implementations, operation 2500 may be performed after the identification is selectively modified at block 2210 of operation 2200 in FIG22 . In some implementations, at block 2502, the process 2500 begins by determining whether the second frame indicates acceptance or rejection of a request included in the first frame. In some cases, at block 2504, if the second frame indicates acceptance of the request included in the first frame, the process 2500 proceeds by removing at least one communication link from an identification of one or more communication links in the ML context based on the second frame indicating acceptance of the request. In some other cases, at block 2506, if the second frame indicates rejection of the request included in the first frame, the process 2500 proceeds by refraining from removing at least one communication link from an identification of one or more communication links in the ML context based on the second frame indicating rejection of the request. In some implementations, the first frame includes a request to delete at least one communication link from the identification of one or more communication links in the ML context. In some cases, the first frame is an action frame that includes a link identifier that uniquely identifies the at least one communication link. In some implementations, the action frame also includes one or more of the following: a media access control (MAC) address of a corresponding STA of a STA MLD associated with the at least one communication link, or a MAC address of a corresponding AP of an AP MLD associated with the at least one communication link. In some cases, the at least one communication link is a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. FIG26 illustrates a flow chart of an example process for wireless communication that supports modifying communication links between MLDs, according to some other implementations. Process 2600 may be performed by a first wireless communication device (such as wireless communication device 500 described above with reference to FIG5 ). In some implementations, process 2600 may be performed by a wireless communication device operating as or within a STA (such as STA 104 or 604 described above with reference to FIG1 and FIG6B , respectively). In other implementations, process 2600 may be performed by a wireless communication device operating as or within an AP (such as AP 102 or 602 described above with reference to FIG1 and FIG6A , respectively). In some implementations, operation 2600 may be an implementation of selectively modifying the identification of one or more communication links at block 2210 of operation 2200 in FIG22 . In some other implementations, operation 2600 may be performed after the identification is selectively modified at block 2210 of operation 2200 in FIG22 . In some implementations, at block 2602, the process 2600 begins by determining whether the second frame indicates acceptance or rejection of a request included in the first frame. In some cases, at block 2604, if the second frame indicates acceptance of the request included in the first frame, the process 2600 proceeds by changing at least one communication link to a new communication link identified in the ML context based on the second frame indicating acceptance of the request. In some other cases, at block 2606, if the second frame indicates rejection of the request included in the first frame, the process 2600 proceeds by refraining from changing the at least one communication link identified in the ML context based on the second frame indicating rejection of the request. In some implementations, the first frame includes a request to change at least one of the identified communication links to a new communication link. In some cases, the first frame is an action frame that includes a link identifier that uniquely identifies the new communication link. In some implementations, the action frame also includes one or more of the following: a media access control (MAC) address of a corresponding STA of a STA MLD associated with the new communication link, or a MAC address of a corresponding AP of an AP MLD associated with the new communication link. In some cases, the new communication link includes a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. FIG27 illustrates a flow chart of an example process 2700 for wireless communications that supports indicating a critical update for an MLD, according to some other implementations. Process 2700 can be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG5 . In some implementations, process 2700 can be performed by a wireless communications device operating as or within an AP, such as one of APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG27 , process 2700 is performed by an AP MLD that includes a first AP and one or more secondary APs. The first AP can be associated with a first communication link of the AP MLD, and each secondary AP can be associated with a corresponding secondary communication link from one or more secondary communication links of the AP MLD. At block 2702, a first AP of an AP MLD generates a frame including a first change sequence field and one or more secondary change sequence fields. The first change sequence field may indicate the presence or absence of a critical update associated with a first communication link of the AP MLD. Each of the secondary change sequence fields may indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. At block 2704, the first AP transmits a frame on the first communication link of the AP MLD. The frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a Fast Initial Link Setup (FILS) discovery frame. In some implementations, the frame may include a multilink element (MLE) carrying a first change sequence field. In some cases, the MLE may include one or more command arguments for the primary communication link of the AP MLD. In other cases, the MLE may also include one or more per-link profile sub-elements, each per-link profile sub-element carrying one or more command arguments for a corresponding secondary communication link of the AP MLD. In one implementation, each per-link profile sub-element may carry a partial set of command arguments or a complete set of command arguments for a basic service set (BSS) associated with a corresponding secondary AP of the AP MLD. In other implementations, the one or more secondary change sequence fields may be included in one or more corresponding reduced neighbor report (RNR) elements carried in the frame. In some implementations, the first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with a first AP and an associated first communication link of the AP MLD, and each of the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of a BSS associated with a corresponding secondary AP and an associated secondary communication link of the AP MLD. In some implementations, a critical update for a corresponding communication link corresponds to a change in one or more command arguments of a BSS associated with the corresponding communication link. In some cases, the one or more command arguments may include at least one of the following: CSA, extended CSA, wideband CSA, EDCA parameters, MU EDCA parameters, quiet time element, DSSS parameter set, CF parameter set, OM parameters, UORA parameters, TWT parameters, BSS color change, FILS parameters, SR parameters, HT operation, VHT operation, HE operation, or EHT operation. FIG28 illustrates a flow chart of an example process 2800 for wireless communications that supports indicating a critical update for an MLD, according to some other implementations. The process 2800 can be performed by a wireless communications device, such as the wireless communications device 500 described above with reference to FIG5 . In some implementations, the process 2800 can be performed by a wireless communications device operating as or within an AP, such as one of the APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG28 , the process 2800 is performed by an AP MLD that includes a first AP and one or more secondary APs. In some implementations, the process 2800 can be performed after the AP MLD transmits a frame in block 2704 of FIG27 . At block 2802, a first AP of an AP MLD receives a notification of a critical update for a secondary communication link associated with the corresponding secondary AP from one or more secondary APs of the AP MLD. At block 2804, the first AP of the AP MLD increments a value of a secondary change sequence field associated with the corresponding secondary AP based on the notification. FIG29 illustrates a flow chart of an example process 2900 for wireless communications that supports indicating a critical update for an MLD, according to some other implementations. Process 2900 can be performed by a wireless communications device, such as the wireless communications device 500 described above with reference to FIG5 . In some implementations, process 2900 can be performed by a wireless communications device operating as or within an AP, such as one of APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG29 , process 2900 is performed by an AP MLD that includes a first AP and one or more secondary APs. In some implementations, process 2900 can be performed after the AP MLD transmits a frame in block 2704 of FIG27 . At block 2902, a first AP of an AP MLD receives a probe request frame from a wireless STA of a station (STA) MLD. At block 2904, the first AP of the AP MLD sends a response frame to the STA MLD on a first communication link. The response frame may include a partial set of command arguments or a complete set of command arguments for one or more BSSs associated with one or more corresponding secondary APs of the AP MLD. In some cases, the response frame may include a complete set of command arguments for at least one of the one or more secondary communication links of the AP MLD. In other cases, the response frame may include a partial set of command arguments for one or more of the secondary communication links of the AP MLD. FIG30 illustrates a flow chart of an example process 3000 for wireless communications that supports indicating a critical update for an MLD, according to some other implementations. Process 3000 can be performed by a wireless communications device, such as wireless communications device 500 described above with reference to FIG5 . In some implementations, process 3000 can be performed by a wireless communications device operating as or within an AP, such as one of APs 102 and 602 described above with reference to FIG1 and 6A , respectively. For the example of FIG30 , process 3000 is performed by an AP MLD that includes a first AP and one or more secondary APs. In some implementations, process 3000 can be performed after the AP MLD transmits a frame in block 2704 of FIG27 . At block 3002, a first AP of an AP MLD receives an indication of a critical update for a corresponding secondary AP of the AP MLD. At block 3004, the first AP of the AP MLD transmits an unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary AP of the AP MLD. In some implementations, the first AP of the AP MLD may provide an indication of the transmission of the complete set of command arguments for the corresponding secondary AP of the AP MLD before transmitting the unsolicited broadcast probe response frame. In some cases, the indication may be provided in a management frame, such as, but not limited to, a beacon frame. In this manner, the STA MLD may be informed that the AP MLD will soon transmit a complete set of command arguments for the corresponding secondary AP, and therefore the STA MLD does not need to transmit an ML probe request to request updated command arguments for the corresponding secondary AP. FIG31 illustrates a flow chart of an example procedure 3100 for wireless communication that supports indicating a critical update for an MLD, according to some other implementations. The procedure 3100 can be performed by a wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the procedure 3100 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG31 , the procedure 3100 is performed by a STA MLD that includes a first STA and one or more secondary STAs. At block 3102, a STA MLD associates with a first AP of an AP MLD. The AP MLD also includes one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD. At block 3104, the STA MLD receives a frame from the first AP on the first communication link of the AP MLD. The frame may include a first change sequence field and one or more secondary change sequence fields. The first change sequence field may indicate the presence or absence of a critical update associated with the first communication link of the AP MLD. Each of the secondary change sequence fields may indicate the presence or absence of a critical update associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. The frame may be a beacon frame, a probe response frame, an association response frame, a reassociation response frame, or a FILS discovery frame. In some implementations, the frame may include a multilink element (MLE) carrying a first change sequence field. In some cases, the MLE may include one or more command arguments for the primary communication link of the AP MLD. In other cases, the MLE may also include one or more per-link profile sub-elements, each per-link profile sub-element carrying one or more command arguments for a corresponding secondary communication link of the AP MLD. In one implementation, each per-link profile sub-element may carry a partial set of command arguments or a complete set of command arguments for a basic service set (BSS) associated with a corresponding secondary AP of the AP MLD. In other implementations, the one or more secondary change sequence fields may be included in one or more corresponding reduced neighbor report (RNR) elements carried in the frame. In some implementations, the first change sequence field may indicate a most recent critical update to one or more command arguments of a basic service set (BSS) associated with a first AP and an associated first communication link of the AP MLD, and each of the one or more secondary change sequence fields may indicate a most recent critical update to one or more command arguments of a BSS associated with a corresponding secondary AP and an associated secondary communication link of the AP MLD. In some implementations, a critical update for a corresponding communication link may correspond to a change in one or more command arguments of a BSS associated with the corresponding communication link. In some cases, the one or more command arguments may include at least one of the following: CSA, extended CSA, wideband CSA, EDCA parameters, MU EDCA parameters, quiet time element, DSSS parameter set, CF parameter set, OM parameters, UORA parameters, TWT parameters, BSS color change, FILS parameters, SR parameters, HT operation, VHT operation, HE operation, or EHT operation. FIG32 illustrates a flow chart of an example procedure for wireless communication that supports indicating a critical update for an MLD, according to some other implementations. Procedure 3200 can be performed by a wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, procedure 3200 can be performed by a wireless communication device operating as or within a STA, such as one of STAs 104 and 604 described above with reference to FIG1 and 6B , respectively. For the example of FIG32 , procedure 3200 is performed by a STA MLD comprising a first STA and one or more secondary STAs. In some implementations, procedure 3200 can be performed after the STA MLD receives a frame in block 3104 of FIG31 . At block 3202, the STA MLD stores the values ​​carried in the first change sequence field and one or more secondary change sequence fields of the received frame. In some implementations, storing the values ​​may include incrementing the corresponding change sequence field value stored in the STA MLD in response to the frame indicating a critical update associated with the communication link of the AP MLD corresponding to the corresponding change sequence field value. FIG33 illustrates a flow chart of an example procedure for wireless communication that supports indicating a critical update for an MLD, according to some other implementations. Procedure 3300 can be performed by a wireless communication device, such as wireless communication device 500 described above with reference to FIG5 . In some implementations, procedure 3300 can be performed by a wireless communication device operating as or within a STA, such as STAs 104 and 604 described above with reference to FIG1 and 6B , respectively. For the example of FIG33 , procedure 3300 is performed by a STA MLD comprising a first STA and one or more secondary STAs. In some implementations, procedure 3300 can be performed after the STA MLD receives a frame in block 3104 of FIG31 . At block 3302, the STA MLD increments a first change sequence field value in the STA of the STA MLD based on the first change sequence field indicating the presence of a critical update for the first communication link of the AP MLD. At block 3304, the STA MLD increments one or more secondary change sequence field values ​​in the STA of the STA MLD based on the one or more corresponding secondary change sequence fields indicating the presence of a critical update for one or more corresponding secondary communication links of the AP MLD. FIG34 illustrates a flow chart of an example process 3400 for wireless communication that supports indicating a critical update for an MLD, according to some other implementations. The process 3400 can be performed by a wireless communication device, such as the wireless communication device 500 described above with reference to FIG5 . In some implementations, the process 3400 can be performed by a wireless communication device operating as or within a STA, such as one of the STAs 104 and 604 described above with reference to FIG1 and FIG6B , respectively. For the example of FIG34 , the process 3400 is performed by a STA MLD comprising a first STA and one or more secondary STAs. In some implementations, the process 3400 can be performed after the STA MLD receives a frame in block 3104 of FIG31 . At block 3402, the STA MLD sends a probe request frame to the AP MLD over a first communication link. At block 3404, the STA MLD receives a response frame from the first AP of the AP MLD over the first communication link, the response frame including a partial set of command arguments or a complete set of command arguments for one or more basic service sets (BSSs) associated with one or more corresponding secondary APs. In some cases, the probe request frame may indicate a recently received critical update for at least one secondary AP of the AP MLD. The following numbered clauses describe implementation examples: 1. A method for wireless communication performed by an access point (AP) multi-link device (MLD), comprising: generating, by a first AP of the AP MLD associated with a first communication link of the AP MLD, the AP MLD also including one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD, a frame comprising: one or more command arguments for the first communication link of the AP MLD; a first change sequence number (CSN), the first CSN indicating the presence or absence of a critical update for the first communication link of the AP MLD; and one or more secondary CSNs, each of the one or more secondary CSNs indicating the presence or absence of a critical update for a corresponding secondary communication link of the one or more secondary communication links of the AP MLD; and transmitting the frame over the first communication link of the AP MLD. 2. The method of clause 1, wherein the frame is one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. 3. The method of any one or more of clauses 1-2, further comprising: receiving, by the first AP of the AP MLD, a notification of a critical update for a corresponding one of the one or more secondary communication links of the AP MLD from a secondary AP of the one or more secondary APs of the AP MLD associated with the corresponding one of the one or more secondary communication links of the AP MLD; and incrementing the secondary CSN corresponding to the corresponding secondary communication link based on the notification. 4. The method of any one or more of clauses 1-3, wherein the critical update for at least one of the first communication link or one or more of the secondary communication links corresponds to a change in one or more command arguments of a basic service set (BSS) associated with the corresponding communication link. 5. The method of clause 4, wherein the one or more command arguments include at least one of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time element, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameter, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter, target latency (TWT) parameter, basic service set (BSS) color change, fast initial link setup (FILS) parameter, spatial reuse (SR) parameter, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation.6. The method of any one or more of clauses 1-5, wherein: the first CSN indicates a most recent critical update to the one or more command arguments for the first communication link; and each of the one or more secondary CSNs indicates a most recent critical update to the one or more command arguments for the corresponding secondary communication link of the AP MLD. 7. The method of any one or more of clauses 1-6, wherein the first CSN and the one or more secondary CSNs are carried in a sequence counter field of the frame. 8. The method of any one or more of clauses 1-6, wherein the first CSN and the one or more second CSNs are carried in an information element. 9. The method of any one or more of clauses 1-6, wherein the frame includes a multilink attribute (MLA) element carrying the one or more secondary CSNs. 10. The method of clause 9, wherein the MLA element includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying a corresponding secondary CSN of the one or more secondary CSNs. 11. The method of clause 10, wherein each of the one or more per-link profile sub-elements includes an information element (IE), the IE including the corresponding secondary CSN of the one or more secondary CSNs. 12. The method of clause 9, wherein the MLA element includes a common parameter field carrying the one or more secondary CSNs. 13. The method of clause 1, wherein the frame includes a beacon frame, the beacon frame including one or more per-link profile elements, each of the one or more per-link profile elements carrying the secondary CSN and a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links. 14. The method of clause 1, wherein the frame includes a Reduced Neighbor Report (RNR) element that carries the one or more secondary CSNs. 15. The method of clause 14, wherein the RNR element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields carrying a corresponding secondary CSN of the one or more secondary CSNs. 16. The method of any one or more of clauses 1-15, wherein the frame also includes one or more Do Not Send (DNT) indications, each of the one or more DNT indications being associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. 17. The method of clause 16, wherein the frame also includes a DNT indication for the first communication link. 18. The method of clause 17, wherein the DNT indication for the first communication link and the one or more DNT indications for the one or more corresponding secondary communication links are carried in a bitmap of the frame.19. The method of clause 16, wherein the DNT indication for a secondary communication link in the one or more secondary communication links is based on one or more of: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of the secondary AP of the AP MLD associated with the corresponding secondary communication link. 20. The method of clause 16, wherein each of the one or more DNT indications indicates whether a wireless communication device should refrain from transmitting on the corresponding secondary communication link of the AP MLD. 21. The method of clause 20, wherein at least some of the wireless communication devices monitor the first communication link instead of the one or more secondary communication links for the DNT indication. 22. The method of clause 16, wherein the one or more DNT indications for the one or more corresponding secondary communication links are carried in a multi-link attribute (MLA) element of the frame. 23. The method of clause 22, wherein the MLA element includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying the DNT indicator for the corresponding secondary communication link of the one or more secondary communication links. 24. The method of clause 1, wherein the frame includes a beacon frame, the beacon frame including one or more per-link profile elements, each of the one or more per-link profile elements carrying the DNT indicator for the corresponding secondary communication link of the one or more secondary communication links. 25. The method of clause 24, wherein each of the one or more per-link profile elements includes an information element (IE), the IE including the DNT indicator for the corresponding secondary communication link. 26. The method of clause 23, wherein the MLA element includes a common parameter field, the common parameter field carrying the one or more DNT indicators for the one or more corresponding secondary communication links. 27. The method of clause 16, wherein the frame includes a Multi-Link Attributes (MLA) element, the MLA element including one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying the DNT indicator and a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links. 28. The method of clause 16, wherein the one or more DNT indicators for the one or more corresponding secondary communication links are carried in a Reduced Neighbor Report (RNR) element of the frame. 29. The method of clause 28, wherein the RNR element includes one or more Neighbor AP Information fields, each of the one or more Neighbor AP Information fields carrying the DNT indicator for the corresponding secondary communication link of the one or more secondary communication links.30. The method of any one or more of clauses 1-29, further comprising: receiving, by the first AP of the AP MLD, notification of a Do Not Transmit (DNT) condition for a corresponding one of the one or more secondary APs of the AP MLD associated with the corresponding one of the one or more secondary communication links of the AP MLD; asserting the DNT indication corresponding to the corresponding secondary communication link; and broadcasting the asserted DNT indication corresponding to the corresponding secondary communication link on the first communication link. 31. The method of clause 1, wherein the frame comprises a beacon frame carrying one or more profiles, each of the one or more profiles carrying a complete set of command arguments for a corresponding one of the one or more secondary communication links. 32. The method of any one or more of clauses 1-31, further comprising: receiving, by the first AP of the AP MLD, an indication of a critical update for a corresponding secondary communication link from a corresponding secondary AP of the one or more secondary APs of the AP MLD associated with the corresponding secondary communication link of the AP MLD; and sending, by the first AP of the AP MLD, an unsolicited broadcast probe response frame, the unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary communication link. 33. The method of clause 32, wherein the unsolicited broadcast probe response frame carries the complete set of command arguments for each of the one or more secondary communication links. 34. The method of clause 1, further comprising: receiving a probe request frame from a wireless STA of a station (STA) MLD; and sending a response frame from the first AP of the AP MLD to the STA MLD on the first communication link. 35. The method of clause 34, wherein the response frame carries a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links for which one or more command arguments were updated. 36. The method of any one or more of clauses 34-35, wherein the request frame is received by one of: the first AP of the AP MLD on the first communication link, or a corresponding secondary AP of the one or more secondary APs of the AP MLD on the corresponding secondary communication link. 37. The method of any one or more of clauses 34-36, wherein the response frame carries a complete set of command arguments for each of the one or more secondary communication links. 38. The method of clause 37, wherein the request frame comprises a broadcast probe request frame.39. The method of clause 36, wherein the probe request frame carries a CSN indicating a most recently received critical update for a specified secondary communication link of the one or more secondary communication links of the AP MLD, the method further comprising: identifying one or more CSNs for the specified secondary communication link that the STA of the STA MLD missed based on the received CSN; and sending the response frame with an indication of the one or more secondary CSNs for the specified secondary communication link that the STA of the STA MLD missed. 40. The method of clause 39, wherein the response frame comprises a unicast probe response frame carrying one or more critical updates for the specified secondary communication link that the STA missed. 41. The method of clause 40, wherein the one or more critical updates missed by the STA are determined based on a comparison between the received CSN and the one or more secondary CSNs missed by the STA. 42. The method of clause 39, wherein the response frame comprises one of a unicast probe response frame or a broadcast probe response frame carrying a complete set of command arguments for the designated secondary communication link. 43. The method of clause 42, wherein the response frame comprises a broadcast probe response frame carrying a complete set of command arguments for the designated secondary communication link and each of the other non-designated secondary communication links. 44. The method of clause 1, further comprising: receiving, by a corresponding secondary AP of the one or more secondary APs of the AP MLD associated with a designated one of the one or more secondary communication links of the AP MLD, a probe request frame from a wireless STA of a station (STA) MLD on the designated secondary communication link; and sending, by the corresponding secondary AP, a response frame to the STA MLD. 45. The method of clause 44, wherein the probe request frame carries the CSN indicating the most recently received critical update for the designated secondary communication link, the method further comprising: sending the response frame with the command arguments for the one or more updates for the designated secondary communication link to the STA MLD. 46. The method of clause 1, further comprising: receiving, by a corresponding secondary AP of the one or more secondary APs of the AP MLD associated with a designated one of the one or more secondary communication links of the AP MLD, a probe request frame from a wireless STA of a station (STA) MLD on the designated secondary communication link; and sending, by the corresponding secondary AP, a response frame to the STA MLD on the designated secondary communication link, the response frame carrying the complete set of command arguments for the designated secondary communication link. 47. The method of clause 46, wherein the response frame comprises one of a unicast probe response frame or a beacon frame.48. The method of clause 1, further comprising: receiving, by the first AP of the AP MLD, an indication of one or more critical updates for a corresponding secondary communication link from a secondary AP of the one or more secondary APs of the AP MLD associated with the corresponding secondary communication link; and sending, from the first AP of the AP MLD, an unsolicited broadcast probe response frame on the first communication link, the unsolicited broadcast probe response frame carrying a complete set of command arguments for the corresponding secondary communication link. 49. The method of clause 48, wherein the transmission of the unsolicited broadcast probe response frame occurs within a time period after the most recent beacon frame transmission by the first AP of the AP MLD. 50. The method of clause 49, wherein the most recent beacon frame transmission by the first AP of the AP MLD includes an indication of the transmission of the unsolicited broadcast probe response frame by the first AP of the AP MLD. 51. A method as described in any one or more of clauses 31-50, wherein the command argument set includes one or more of the following: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time element, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameter, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter, target waiting time (TWT) parameter, basic service set (BSS) color change, fast initial link establishment (FILS) parameter, spatial reuse (SR) parameter, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. 52. A wireless communication device comprising: 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 that, when executed by the at least one processor in conjunction with the at least one modem, is configured to perform the method of any one of clauses 1-51.53. A method for wireless communication performed by a wireless STA of a station (STA) multi-link device (MLD), comprising: associating with a first access point (AP) MLD, the AP MLD also including one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD, and receiving a frame from the first AP on the first communication link of the AP MLD, the frame comprising: one or more command arguments for the first communication link; a first change sequence number (CSN), the first CSN indicating the presence or absence of a critical update for the first communication link of the AP MLD; and one or more secondary CSNs, each of the one or more secondary CSNs indicating the presence or absence of a critical update for a corresponding secondary communication link of the one or more secondary communication links of the AP MLD. 54. The method of clause 53, further comprising: incrementing a first CSN counter in the STA of the STA MLD based on the first CSN indicating the presence of the critical update for the first communication link of the AP MLD; and incrementing one or more secondary CSN counters in the STA of the STA MLD based on the one or more corresponding secondary CSNs indicating the presence of the critical update for the one or more corresponding secondary communication links of the AP MLD. 55. The method of any one or more of clauses 53-54, wherein the frame comprises one of a beacon frame, a probe response frame, an association response frame, or a reassociation response frame. 56. The method of any one or more of clauses 53-55, wherein the critical update corresponds to a change in one or more command arguments of a basic service set (BSS) associated with the first communication link or at least one of the one or more secondary communication links. 57. A method according to any one or more of clauses 53-56, wherein the one or more command arguments include at least one of: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time element, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameter, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameter, target waiting time (TWT) parameter, basic service set (BSS) color change, fast initial link establishment (FILS) parameter, spatial reuse (SR) parameter, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation.58. The method of clause 53, wherein: the first CSN indicates a most recent critical update to the one or more command arguments for the first communication link; and each of the one or more secondary CSNs indicates a most recent critical update to the one or more command arguments for the corresponding secondary communication link of the AP MLD. 59. The method of clause 53, wherein the first CSN and the one or more secondary CSNs are carried in a sequence counter field of the frame. 60. The method of clause 53, wherein the first CSN and the one or more secondary CSNs are carried in an information element. 61. The method of clause 53, wherein the frame includes a multilink attribute (MLA) element that carries the one or more secondary CSNs. 62. The method of clause 61, wherein the MLA element includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying a corresponding secondary CSN of the one or more secondary CSNs. 63. The method of clause 53, wherein the frame comprises a beacon frame, the beacon frame comprising one or more per-link profile elements, each of the one or more per-link profile elements carrying the secondary CSN and a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links. 64. The method of clause 63, wherein each of the one or more per-link profile elements comprises an information element (IE), the IE comprising the corresponding secondary CSN of the one or more secondary CSNs. 65. The method of clause 61, wherein the MLA element comprises a common parameter field carrying the one or more secondary CSNs. 66. The method of clause 53, wherein the frame comprises a multi-link attribute (MLA) element, the MLA element comprising one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying the secondary CSN and a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links. 67. The method of clause 53, wherein the frame includes a Reduced Neighbor Report (RNR) element carrying the one or more secondary CSNs. 68. The method of clause 67, wherein the RNR element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields carrying a corresponding secondary CSN of the one or more secondary CSNs. 69. The method of clause 53, wherein the frame includes a beacon frame carrying one or more profiles, each of the one or more profiles carrying a complete set of command arguments for a corresponding secondary communication link of the one or more secondary communication links. 70. The method of clause 53, wherein the frame also includes one or more Do Not Send (DNT) indications, each of the one or more DNT indications being associated with a corresponding secondary communication link of the one or more secondary communication links of the AP MLD.71. The method of clause 70, further comprising: refraining from transmitting on a corresponding one of the one or more secondary communication links of the AP MLD based on a DNT condition indicated by a corresponding one of the one or more DNT indications on a per-secondary communication link basis. 72. The method of clause 70, wherein the frame also includes a DNT indication for the first communication link. 73. The method of clause 72, wherein the DNT indication for the first communication link and the one or more DNT indications for the one or more corresponding secondary communication links are carried in a bitmap of the frame. 74. The method of clause 70, wherein the DNT indication for a corresponding one of the one or more secondary communication links of the AP MLD is based on one or more of: a channel switch notification for the corresponding secondary communication link, a quiet time notification for the corresponding secondary communication link, or unavailability of the secondary AP of the one or more secondary APs of the AP MLD associated with the corresponding secondary communication link. 75. The method of clause 70, wherein each of the one or more DNT indications indicates whether the wireless communication device should avoid transmission on the corresponding secondary communication link of the AP MLD. 76. The method of clause 75, wherein the STA of the STA MLD monitors the first communication link instead of the one or more secondary communication links for the DNT indication. 77. The method of clause 70, wherein the one or more DNT indications for the one or more corresponding secondary communication links are carried in a multilink attributes (MLA) element of the frame. 78. The method of clause 77, wherein the MLA element includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying the DNT indication for the corresponding secondary communication link of the one or more secondary communication links. 79. The method of clause 78, wherein the one or more per-link profile sub-elements include an information element (IE), wherein the IE includes the DNT indication for the corresponding secondary communication link. 80. The method of clause 77, wherein the MLA element includes a common parameter field that carries the one or more DNT indicators for the one or more corresponding secondary communication links. 81. The method of clause 70, wherein the frame includes a Multilink Attributes (MLA) element that includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying the DNT indicator and a complete set of command arguments for a corresponding secondary communication link in the one or more secondary communication links. 82. The method of clause 70, wherein the one or more DNT indicators for the one or more corresponding secondary communication links are carried in a Reduced Neighbor Report (RNR) element of the frame.83. The method of clause 82, wherein the RNR element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields carrying the DNT indication for the corresponding secondary communication link of the one or more secondary communication links. 84. The method of clause 53, further comprising: receiving, from the first AP of the AP MLD on the first communication link, an indication of a Do Not Transmit (DNT) condition for a specified secondary communication link of the one or more secondary communication links of the AP MLD; and refraining from transmitting on the specified secondary communication link based on receiving the DNT indication. 85. The method of clause 53, further comprising: receiving, from the first AP of the AP MLD on the first communication link, an unsolicited broadcast probe response frame, the unsolicited broadcast probe response frame carrying a complete set of command arguments for the specified secondary communication link of the one or more secondary communication links. 86. The method of clause 85, wherein the transmission of the unsolicited broadcast probe response frame occurs within a time period after the most recent beacon frame transmission by the first AP of the AP MLD. 87. The method of clause 86, wherein the most recent beacon frame transmission by the first AP of the AP MLD includes an indication of the transmission of the unsolicited broadcast probe response frame by the first AP of the AP MLD. 88. The method of clause 85, wherein the unsolicited broadcast probe response frame carries the complete set of command arguments for each of the one or more secondary communication links. 89. The method of clause 53, further comprising: receiving, from the first AP of the AP MLD on the first communication link, an indication of a critical update for a specified secondary communication link of the one or more secondary communication links of the AP MLD. 90. The method of clause 89, further comprising: sending a probe request frame on the first communication link; and receiving a response frame from the first AP of the AP MLD on the first communication link. 91. The method of clause 89, further comprising: sending a probe request frame on the designated secondary communication link; and receiving a response frame on the designated secondary communication link from a secondary AP of the one or more secondary APs of the AP MLD associated with the designated secondary communication link. 92. The method of any one or more of clauses 90 or 91, wherein the response frame carries a complete set of command arguments for the designated secondary communication link. 93. The method of any one or more of clauses 90 or 91, wherein the response frame carries a complete set of command arguments for each of the one or more secondary communication links. 94. The method of any one or more of clauses 90 or 91, wherein the probe request frame comprises a broadcast probe request frame.95. The method of any one or more of clauses 90 or 91, wherein the probe request frame carries a CSN indicating a recently received critical update for the designated secondary communication link, and the response frame carries an indication of the one or more secondary CSNs for the designated secondary communication link that the STA missed for the STA MLD. 96. The method of any one or more of clauses 90 or 91, wherein the response frame comprises a unicast probe response frame carrying the one or more critical updates for the designated secondary communication link that the STA missed. 97. The method of any one or more of clauses 90 or 91, wherein the response frame comprises one of a unicast probe response frame or a broadcast probe response frame carrying a complete set of command arguments for the designated secondary communication link. 98. The method of any one or more of clauses 90 or 91, wherein the response frame comprises a broadcast probe response frame carrying a complete set of command arguments for the designated secondary communication link and each of the other non-designated secondary communication links. 99. A method as described in any one or more of clauses 66-98, wherein the command argument set includes one or more of the following: channel switch announcement (CSA), extended CSA, wide bandwidth CSA, enhanced distributed channel access (EDCA) parameters, multi-user (MU) EDCA parameters, quiet time elements, direct sequence spread spectrum (DSSS) parameter set, contention free (CF) parameter set, operation mode (OM) parameters, uplink (UL) orthogonal frequency division multiple access (OFDMA) random access (UORA) parameters, target waiting time (TWT) parameters, basic service set (BSS) color change, fast initial link establishment (FILS) parameters, spatial reuse (SR) parameters, high throughput (HT) operation, very high throughput (VHT) operation, high efficiency (HE) operation, or extremely high throughput (EHT) operation. 100. A wireless communication device comprising: 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 that, when executed by the at least one processor in conjunction with the at least one modem, is configured to perform the method of any of clauses 53-99.101. A method for wireless communication performed by a wireless station (STA) multi-link device (MLD), comprising: receiving, by a first STA of an access point (AP) multi-link device (MLD) associated with a first communication link of the STA MLD, a frame on the first communication link of the AP MLD, the AP MLD also including one or more secondary APs associated with one or more corresponding secondary communication links of the AP MLD, the frame including an indication of an update to at least one command argument for a specified secondary communication link of the one or more secondary communication links; determining, based on receiving the indication of the update, that the first STA of the STA MLD is unable to support the update to the at least one command argument for the specified secondary communication link; and removing the specified secondary communication link from a multi-link (ML) context established between the STA MLD and the AP MLD. 102. The method of clause 101, wherein the specified secondary communication link is removed from the ML context without disassociating from the first AP of the AP MLD. 103. The method of clause 101, wherein the designated secondary communication link is removed from the ML context without tearing down the ML context. 104. The method of clause 101, wherein the update of the at least one command argument for the designated secondary communication comprises one or more of: a change in an operating channel of the designated secondary communication link, a change in a modulation and coding scheme (MCS) used for the designated secondary communication link, or a change in a bandwidth of the designated secondary communication link. 105. The method of clause 101, wherein removing the designated secondary communication link from the ML context comprises: sending an action frame from the first STA of the STA MLD to the first AP of the AP MLD on the first communication link, the action frame comprising a request to update the ML context by removing the designated secondary communication link from the ML context. 106. The method of clause 105, wherein the action frame comprises an ML setup update action frame. 107. The method of clause 105, wherein the action frame also includes an element comprising one or more updates to a transmission identifier (TID) mapping associated with the ML context. 108. The method of clause 107, wherein the one or more updates to the transmission identifier (TID) mapping comprise remapping the TID from the designated secondary communication link to one or more of the first communication link or other non-designated secondary communication links of the one or more secondary communication links. 109. The method of clause 101, wherein removing the designated secondary communication link from the ML context comprises sending an action frame from the first STA of the STA MLD to the first AP of the AP MLD on the first communication link, the action frame comprising a request to disable the designated secondary communication link.110. The method of clause 101, wherein removing the designated secondary communication link from the ML context comprises: remapping a transmission identifier (TID) from the designated secondary communication link to one or more of the first communication link or other non-designated secondary communication links in the one or more secondary communication links. 111. The method of clause 101, wherein removing the designated secondary communication link from the ML context comprises: maintaining a sleep or doze state of the STA MLD on the designated secondary communication link. 112. A method for wireless communication performed by an access point (AP) multi-link device (MLD), comprising: exchanging one or more of discovery information, authentication information, or association information between a first AP of the AP MLD and a first wireless STA of a station (STA) MLD over a first communication link associated with the first AP of the AP MLD and associated with the first wireless STA of the STA MLD; establishing a multi-link (ML) context between the AP MLD and the STA MLD based on the one or more of the exchanged discovery information, authentication information, or association information, wherein the ML context includes identifiers of one or more communication links that can be used for communication between the AP MLD and the STA MLD; sending or receiving a first frame to or from the STA MLD over the first communication link, the first frame including a request to modify the identifiers of the one or more communication links in the ML context; receiving or sending from the STA MLD over the first communication link to the STA MLD The MLD sends a second frame in response to the first frame and indicating acceptance, rejection, or modification of the request; and selectively modifies the identification of the one or more communication links in the ML context based on the second frame indicating acceptance, rejection, or modification of the request. 113. The method of clause 112, wherein the ML context comprises a common security context between a first Media Access Control Service Access Point (MAC-SAP) endpoint of the AP MLD and a second MAC-SAP endpoint of the STA MLD, wherein each of the first MAC-SAP endpoint and the second MAC-SAP endpoint is configured to communicate over the communication link identified by the ML context. 114. The method of clause 112, further comprising: sending or receiving a protected action frame to or from the STA MLD, the protected action frame indicating a maximum number of communication links supported by the AP MLD or the STA MLD, or a currently available number of communication links associated with the AP MLD. 115. The method of clause 112, wherein the first frame comprises a management frame. 116. The method of clause 115, wherein the management frame comprises an association request frame, a reassociation request frame, an association response frame, or a reassociation response frame.117. The method of clause 115, wherein the management frame comprises a protected action frame. 118. The method of clause 117, wherein the protected action frame indicates one or more of the following: the maximum number of communication links supported by the AP MLD or the STA MLD, or the currently available number of communication links associated with the AP MLD. 119. The method of clause 117, wherein the protected action frame also comprises one or more group transient keys (GTKs). 120. The method of clause 117, wherein the protected action frame includes protected ML information, the protected ML information comprising one or more of the following: a public security context, block acknowledgement (BA) communication period information, a mapping between a transport identifier (TID) value and a communication link associated with the AP MLD, command arguments for the AP MLD or the STA MLD, or capability information for the AP MLD or the STA MLD. 121. The method of clause 120, wherein the protected ML information is included in one or more fields or information elements (IEs) carried in the protected action frame. 122. The method of clause 112, wherein the first frame includes a request to add at least one additional communication link to the identification of the one or more communication links in the ML context. 123. The method of clause 122, wherein the first frame includes an action frame, the action frame including a link identifier that uniquely identifies the at least one additional communication link. 124. The method of clause 123, wherein the action frame also includes one or more of the following: a media access control (MAC) address of a corresponding STA of the STA MLD associated with the at least one additional communication link, or a MAC address of a corresponding AP of the AP MLD associated with the at least one additional communication link. 125. The method of clause 123, wherein the at least one additional communication link includes a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. 126. The method of clause 123, wherein selectively modifying the identification comprises: adding the at least one additional communication link to the identification of the one or more communication links in the ML context based on the second frame indicating acceptance of the request. 127. The method of clause 123, wherein selectively modifying the identification comprises: refraining from adding the at least one additional communication link to the identification of the one or more communication links in the ML context based on the second frame indicating rejection of the request. 128. The method of clause 112, wherein the first frame comprises a request to delete at least one communication link from the identification of the one or more communication links in the ML context.129. The method of clause 128, wherein the first frame comprises an action frame, the action frame comprising a link identifier uniquely identifying the at least one communication link. 130. The method of clause 129, wherein the action frame also comprises one or more of the following: a media access control (MAC) address of a corresponding STA of the STA MLD associated with the at least one communication link, or a MAC address of a corresponding AP of the AP MLD associated with the at least one communication link. 131. The method of clause 129, wherein the at least one communication link comprises a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. 132. The method of clause 129, wherein selectively modifying the identification comprises: deleting the at least one communication link from the identification of the one or more communication links in the ML context based on the second frame indicating acceptance of the request. 133. The method of clause 129, wherein selectively modifying the identification comprises: avoiding deleting the at least one communication link from the identification of the one or more communication links in the ML context based on the second frame indicating a rejection of the request. 134. The method of clause 112, wherein the first frame comprises a request to change at least one of the identified communication links to a new communication link. 135. The method of clause 134, wherein the first frame comprises an action frame, the action frame comprising a link identifier that uniquely identifies the new communication link. 136. The method of clause 135, wherein the action frame also comprises one or more of: a media access control (MAC) address of a corresponding STA of the STA MLD associated with the new communication link, or a MAC address of a corresponding AP of the AP MLD associated with the new communication link. 137. The method of clause 134, wherein the new communication link comprises a secondary communication link associated with a second AP of the AP MLD and associated with a second STA of the STA MLD. 138. The method of clause 134, wherein selectively modifying the identification comprises: changing the at least one communication link to the new communication link identified in the ML context based on the second frame indicating acceptance of the request. 139. The method of clause 134, wherein selectively modifying the identification comprises: refraining from changing the at least one communication link identified in the ML context based on the second frame indicating rejection of the request. As used herein, a phrase referring to "at least one of" or "one or more of" a list of items represents any combination of those items, including single members. 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. The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithms 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. The interchangeability of hardware, firmware, and software has been generally described and illustrated in the various illustrative components, blocks, modules, circuits, and procedures described above with respect to functionality. Whether such functionality is implemented using hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system. Various modifications to the implementations described in this disclosure may be readily apparent to those skilled in the art, and the general principles defined herein may 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, and the novel features disclosed herein. In addition, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subgroup combination. Furthermore, although features may be described above as acting in a particular combination and even initially claimed as such, in some cases one or more features from a claimed combination may be removed from that combination, and a claimed combination may be directed to a subgroup combination or a variation of a subgroup combination. Similarly, although operations are illustrated in a specific order in the accompanying drawings, this should not be understood as requiring to perform in the specific order shown or in the order of sequence, or requiring to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically illustrate one or more example programs in the form of a flow chart or a schematic diagram of a flow chart. However, other operations not illustrated can be incorporated into the example programs schematically shown. For example, one or more additional operations can be performed before, after, simultaneously or between any operation in the illustrated operations. In some cases, multiplexing and parallel processing may be advantageous. In addition, the segmentation of each system component in the implementation described above should not be understood as requiring such segmentation in all implementations, and it should be understood that the program components and the system described can usually be integrated together in a single software product, or be encapsulated in multiple software products. 100: Wireless Communication Network 102: Access Point (AP) 104: Station (STA) 106: Communication Link 108: Coverage Area 200: Protocol Data Unit (PDU) 202: PHY Preamble 204: PHY Payload 206: Legacy Short Training Field (L-STF) 208: Legacy Long Training Field (L-LTF) 210: Legacy Signaling Field (L-SIG) 212: Data Rate Field 214: Reserved Bits 216: Length Field 218: Parity Bits 220: Trailer Field 300: PDU 302: Legacy Portion 304: Non-Legacy Portion 306: PHY Payload 308: L-STF 310: L-LTF 312: L-SIG 314: RL-SIG 316: First HE Signal Field (HE-SIG-A) 318: HE-SIG-B 320: HE Short Training Field (HE-STF) 322: HE Long Training Field (or Symbol) 324: Data Field 350: PPDU 352: Legacy Part 352 and 354 354: Non-legacy Part 356: PHY Payload 358: L-STF 360: L-LTF 362: L-SIG 364: RL-SIG 366: U-SIG 368: EHT-SIG 372: Short Training Field 374: EHT-LTF 400: PPDU 402: PHY Preamble 404: PSDU 406: A-MPDU Subframe 408: MPDU (A-MPDU) 410: MAC Delimiter 412: MAC Header 414: MPDU 416: MAC Service Data Unit (MSDU) Subframe 418: MSDU (A-MSDU) 420: MSDU 422: Subframe header 424: Frame check sequence (FCS) field 500: Wireless communication device 502: Modem 504: Radio unit 506: Processor 508: Memory 602: AP 604: STA 610: Wireless communication device (WCD) 615: Wireless communication device 620: Antenna 625: Antenna 630: Application processor 635: Application processor 640: Memory 645: Memory 650: External network interface 655: UI 665: Display 675: Sensor 700: Program 702, 704, 706, 708, 710: Block 720: Program 722, 724, 726: Block 800: Program 802, 804, 806, 808, 810, 820, 822, 824: Block 900: Program 902, 904: Block 1000: Program 1002, 1004, 1010, 1012, 1014, 1016, 1020, 1022, 1024: Block1030: Program 1032, 1034: Block 1040: Program 1042, 1044: Block 1050: Program 1052, 1054, 1056: Block 1060: Program 1062, 1064: Block 1070: Program 1072, 1074: Block 1100: Program 1102, 1104: Block 1200: Program 1202, 1204: Block 1210: Program 1212: Block 1220: Program 1222, 1224: Block 1230: Program 1232: Block 1240: Procedure 1242: Block 1250: Procedure 1252, 1254: Block 1260: Procedure 1262, 1264: Block 1300: Procedure 1302, 1304, 1306: Block 1400: Multi-link Communication 1401: First Packet 1402: Second Packet 1411: MLA Request 1420: Timing Diagram 1421: First Packet 1422: Second Packet 1423: Third Packet 1431: MLA Request 1500: Frame 1510: Link Attribute Element 1520: MLE 1525: Common Attributes Sub-element 1530(1): Per-Link Profile Sub-element 1530(2): Per-Link Profile Sub-element 1530(n): Per-Link Profile Sub-element 1551: Element ID Field 1552: Length Field 1553: Element ID Extension Field 1554: Control Field 1555: Operation Class Field 1556: Channel Number Field 1557: BSSID Field 1558: TSF Offset Field 1559: Beacon Interval Field 1561: Link ID Sub-element 1562: Active Link Sub-element 1563: Independent MLA Bitmap Sub-element 1564: Anchor Sub-element 1600: MLE 1601: Element ID field 1602: Length field 1603: Element ID extension field 1604: Public parameter field 1605: Optional sub-element field 1611: Sub-element ID = 0 field 1612: Length field 1613: Data field 1620: Data field 1621: Element ID field 1622: Length field 1623: Element ID extension field 1624: Control field 1625: Operation type field 1626: Channel number field 1627: BSSID field 1628: TSF offset field 1629: Beacon interval field 1630: Data field 1631: Element ID field 1632: Length field 1633: Element ID extension field 1634: Data field 1641: Link ID 1642: Active Link 1643: Independent MLA Bitmap 1644: Anchor 1700: Multilink (ML) Communication 1710: Multilink Communication 1800: ML Communication 1900: MLE1902: Element ID field 1904: Length field 1906: Element ID extension field 1908: Common parameter field 1910(1): Per-link profile sub-element 1910(2): Per-link profile sub-element 1910(n): Per-link profile sub-element 1912: Sub-element ID 1914: Length 1916: Data 1932: Link ID 1934: Key Update 1936: DNT Field 1938(1): Element 1938(2): Element 1938(n): Element 2000: RNR Element 2002: Element ID Field 2004: Length Field 2006: Neighbor AP Information Field 2011: TBTT Information Header 2012: Operation Class Field 2013: Channel Number Field 2014: TBTT Information Collection Field 2015: Key Update Field 2016: DNT Field 2100: Sequence Diagram 2200: Example Procedure 2202, 2204, 2206, 2208, 2210: Block 2300: Procedure 2302: Block 2400: Program 2402, 2404, 2406: Block 2500: Program 2502, 2504, 2506: Block 2600: Program 2602, 2604, 2606: Block 2700: Program 2702, 2704: Block 2800: Program 2802, 2804: Block 2900: Program 2902, 2904: Block 3000: Program 3002, 3004: Block 3100: Program 3102, 3104: Block 3200: Program 3202: Block 3300: Program 3302, 3304: Block 3400: Program 3402, 3404: Block FIG1 is a schematic diagram illustrating an example wireless communication network. 2A illustrates an example protocol data unit (PDU) that may be used for communication between an access point (AP) and multiple stations (STAs). FIG. 2B illustrates example fields in the PDU of FIG. 2A . FIG. 3A illustrates another example PDU that may be used for communication between an AP and one or more STAs. FIG. 3B illustrates another example PDU that may be used for communication between an AP and one or more STAs. 4 illustrates an example physical layer convergence protocol (PLCP) protocol data unit (PPDU) that may be used for communication between an AP and multiple STAs. FIG5 illustrates a block diagram of an example wireless communication device. 6A illustrates a block diagram of an example access point (AP). FIG6B illustrates a block diagram of an example station (STA). 7A illustrates a flow diagram of an example process for wireless communications that supports communications between multi-link devices (MLDs) according to some implementations. 7B illustrates a flow diagram of an example process for wireless communication that supports communication between MLDs according to some implementations. 8A illustrates a flow chart of an example process for wireless communication that supports communication between MLDs according to some other implementations. 8B illustrates a flow chart of an example process for wireless communication that supports communication between MLDs according to some other implementations. 9 illustrates a flow chart of an example process for wireless communication that supports communication between MLDs according to some other implementations. 10A-10H illustrate flow diagrams of example processes for wireless communication that support communication between MLDs according to some implementations. 11 illustrates a flow chart of an example process for wireless communication that supports communication between MLDs according to some implementations. 12A-12G illustrate flow diagrams of example processes for wireless communications supporting multi-link communications according to some implementations. 13 illustrates a flow chart of an example process for wireless communication that supports communication between MLDs according to some other implementations. 14A illustrates a timing diagram depicting an example multi-link communication supporting communication between MLDs according to some implementations. 14B illustrates a timing diagram depicting an example multi-link communication supporting multi-link communication according to some implementations. FIG15 illustrates an example frame including a link attribute element and a multi-link element (MLE) that may be used for communications between wireless communication devices. FIG. 16A illustrates an example MLE that may be used for communications between wireless communication devices. FIG. 16B illustrates example data fields for the MLE of FIG. 16A . FIG. 16C illustrates another example data field of the MLE of FIG. 16A . 17A illustrates a sequence diagram depicting example multi-link communications according to some implementations. 17B illustrates a sequence diagram depicting another example multi-link communication according to some implementations. 18 illustrates a timing diagram depicting example multi-link communications according to some implementations. FIG. 19 illustrates an example MLE that may be used for communications between wireless communication devices. FIG20 illustrates a simplified neighbor report (RNR) element that may be used for communications between wireless communication devices. 21 illustrates a sequence diagram depicting another example multi-link communication according to some implementations. 22 illustrates a flow diagram of an example process for wireless communications that supports modifying communication links between MLDs according to some other implementations. 23 illustrates a flow diagram of an example process for wireless communications that supports modifying communication links between MLDs according to some other implementations. 24 illustrates a flow diagram of an example process for wireless communications that supports modifying communication links between MLDs according to some other implementations. 25 illustrates a flow diagram of an example process for wireless communications that supports modifying communication links between MLDs according to some other implementations. 26 illustrates a flow diagram of an example process for wireless communications that supports modifying communication links between MLDs according to some other implementations. 27 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 28 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 29 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 30 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 31 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 32 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 33 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. 34 illustrates a flow diagram of an example process for wireless communications supporting indication of a critical update for an MLD according to some other implementations. Like reference numbers and designations in the various drawings indicate like elements. 1700: Multi-link (ML) communication

Claims

1. A non-access point (AP) multi-link device (MLD), comprising: A processing system, including one or more processors and one or more memories storing code, is configured to cause the non-AP MLD to: associate with an AP MLD, the AP MLD including: a first access point (AP) operating on a first communication link of the AP MLD, and one or more auxiliary APs operating on one or more corresponding auxiliary communication links of the AP MLD; and receive a frame from the first AP via the first communication link of the AP MLD, the frame including: A multi-link element includes a first change sequence field indicating the first presence or absence of a critical update of one or more first instruction arguments of a first AP, and a simplified neighbor report element including one or more secondary change sequence fields, each of which is associated with a corresponding secondary AP of the one or more secondary APs and indicates the second presence or absence of a corresponding critical update of one or more corresponding instruction arguments of the corresponding secondary AP of the one or more secondary APs, wherein the value of the first secondary change sequence field associated with the first secondary AP of the one or more secondary APs is incremented relative to a previous value of the first secondary change sequence field to indicate the occurrence of a second critical update of one or more second instruction arguments of the first secondary AP of the one or more secondary APs.

2. The non-AP MLD according to request item 1, wherein the processing system is also configured to cause the non-AP MLD to: associate a first non-AP radio station (STA) of the non-AP MLD with the first AP operating on the first communication link of the AP MLD; and associate one or more second non-AP STAs of the non-AP MLD with one or more secondary APs operating on the one or more corresponding secondary communication links of the AP MLD.

3. According to the non-AP MLD of request item 1, wherein the simplified neighbor report element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields being associated with a corresponding secondary AP of the one or more secondary APs, and each carrying a corresponding secondary change sequence field of the one or more secondary change sequence fields.

4. According to the non-AP MLD of request item 3, each of the one or more neighboring AP information fields includes a corresponding Target Beacon Transmission Time (TBTT) information field.

5. According to the non-AP MLD of request item 1, the frame also includes a critical update flag subfield, which indicates a change to the first change sequence field or one or more of the auxiliary change sequence fields.

6. According to the non-AP MLD of request item 1, wherein the multi-link element also includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying a corresponding partial instruction argument set or a corresponding complete instruction argument set of a corresponding secondary AP of the one or more secondary APs.

7. According to the non-AP MLD of request item 1, wherein the frame is either a beacon frame or a probe response frame.

8. According to the non-AP MLD of request item 1, wherein the non-AP MLD maintains a corresponding recently received change sequence field value for each of the first AP and the one or more auxiliary APs.

9. The non-AP MLD according to request item 8, wherein the processing system is also configured to cause the non-AP MLD to increment the value of the first auxiliary change sequence field of the one or more auxiliary APs maintained at the non-AP MLD, based on the value of the first auxiliary AP that occurred in accordance with the second key update of the one or more second instruction arguments of the first auxiliary AP of the one or more auxiliary APs.

10. According to the non-AP MLD of request item 1, where: The first change sequence field indicates a recent critical update of the one or more first instruction arguments of the first AP; and each of the one or more secondary change sequence fields indicates a corresponding recent critical update of the one or more corresponding instruction arguments of the corresponding secondary AP of the one or more secondary APs.

11. The non-AP MLD according to request item 1, wherein the processing system is also configured to cause the non-AP MLD to send a probe request frame via the first communication link of the AP MLD, wherein the frame received from the first AP is a probe response frame according to the probe request frame, the probe response frame including a corresponding partial set of instruction arguments or a corresponding complete set of instruction arguments for each of the one or more auxiliary APs.

12. The non-AP MLD according to request item 11, wherein the probe request frame includes a recently received critical update of at least one of the one or more auxiliary APs.

13. The non-AP MLD according to request item 1, wherein the processing system is also configured to cause the non-AP MLD to receive a beacon frame from the first secondary AP via a communication link associated with the first secondary AP in accordance with the occurrence of the second key update of the one or more second instruction arguments to the first secondary AP.

14. The non-AP MLD according to request item 1, wherein the processing system is also configured to cause the non-AP MLD to: send a probe request frame via a communication link associated with the first secondary AP based on the occurrence of the second key update of the one or more second instruction arguments of the first secondary AP; and receive a probe response frame from the first secondary AP via the communication link associated with the first secondary AP based on the probe request frame.

15. An access point (AP) multi-link device (MLD), comprising: A first AP operates on a first communication link of the AP MLD; One or more auxiliary APs, operating on one or more corresponding auxiliary communication links of the AP MLD; and a processing system, including one or more processors and one or more memories storing code, the processing system being configured to cause the AP MLD to: associate with a non-AP MLD; And a frame for the non-AP MLD is transmitted via the first communication link of the AP MLD, the frame including: a multi-link element including a first change sequence field indicating a first presence or absence of a critical update of one or more first command arguments of the first AP; and a simplified neighbor report element including one or more secondary change sequence fields, each of the one or more secondary change sequence fields being associated with a corresponding secondary AP of the one or more secondary APs and indicating a second presence or absence of a corresponding critical update of one or more corresponding command arguments of the corresponding secondary AP of the one or more secondary APs, wherein the value of the first secondary change sequence field associated with the first secondary AP of the one or more secondary APs is incremented relative to a previous value of the first secondary change sequence field to indicate the occurrence of a second critical update of one or more second command arguments of the first secondary AP of the one or more secondary APs.

16. The AP MLD according to request item 15, wherein the processing system is also configured to cause the AP MLD to: associate the first AP operating on the first communication link of the AP MLD with a first non-AP radio station (STA) of the non-AP MLD; and associate the one or more secondary APs operating on the one or more corresponding secondary communication links of the AP MLD with one or more second non-AP STAs of the non-AP MLD.

17. The AP MLD according to request item 15, wherein the simplified neighbor report element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields being associated with a corresponding secondary AP of the one or more secondary APs, and each carrying a corresponding secondary change sequence field of the one or more secondary change sequence fields.

18. The AP MLD according to request item 17, wherein each of the one or more neighboring AP information fields includes a corresponding Target Beacon Transmission Time (TBTT) information field.

19. The AP MLD according to request item 15, wherein the frame also includes a critical update flag subfield that indicates a change to the first change sequence field or one or more of the auxiliary change sequence fields.

20. The AP MLD according to request item 15, wherein the multiple link element also includes one or more per-link profile sub-elements, each of the one or more per-link profile sub-elements carrying a corresponding partial instruction argument set or a corresponding complete instruction argument set of a corresponding secondary AP of the one or more secondary APs.

21. The AP MLD according to request item 15, wherein the frame is either a beacon frame or a probe response frame.

22. According to AP MLD of request item 15, where: The first change sequence field indicates a recent critical update of the one or more first instruction arguments of the first AP; and each of the one or more secondary change sequence fields indicates a corresponding recent critical update of the one or more corresponding instruction arguments of the corresponding secondary AP of the one or more secondary APs.

23. The AP MLD according to request item 15, wherein the processing system is also configured to cause the AP MLD to receive a probe request frame from a non-AP radio station (STA) of the non-AP MLD, wherein the frame sent for the non-AP MLD is a probe response frame according to the probe request frame, the probe response frame including a corresponding partial set of command arguments or a corresponding complete set of command arguments for each of the one or more auxiliary APs.

24. AP MLD according to request item 23, wherein the probe request frame includes a recently received critical update for at least one of the one or more auxiliary APs.

25. The AP MLD according to request item 15, wherein the processing system is also configured to cause the AP MLD to send a beacon frame via a communication link associated with the first secondary AP in response to the occurrence of the second key update of the one or more second instruction arguments of the first secondary AP.

26. The AP MLD according to request item 15, wherein the processing system is also configured to cause the AP MLD to: receive a probe request frame via a communication link associated with the first secondary AP based on the occurrence of the second key update of the one or more second instruction arguments of the first secondary AP; and send a probe response frame via the communication link associated with the first secondary AP based on the probe request frame.

27. A method for wireless communication performed by a non-access point (AP) multi-link device (MLD), comprising the following steps: Associated with an AP MLD, the AP MLD comprising: a first AP operating on a first communication link of the AP MLD, and one or more auxiliary APs operating on one or more corresponding auxiliary communication links of the AP MLD; and receiving a frame from the first AP via the first communication link of the AP MLD, the frame comprising: A multi-link element includes a first change sequence field indicating the first presence or absence of a critical update of one or more first instruction arguments of a first AP, and a simplified neighbor report element including one or more secondary change sequence fields, each of which is associated with a corresponding secondary AP of the one or more secondary APs and indicates the second presence or absence of a corresponding critical update of one or more corresponding instruction arguments of the corresponding secondary AP of the one or more secondary APs, wherein the value of the first secondary change sequence field associated with the first secondary AP of the one or more secondary APs is incremented relative to a previous value of the first secondary change sequence field to indicate the occurrence of a second critical update of one or more second instruction arguments of the first secondary AP of the one or more secondary APs.

28. The method as described in claim 27 further includes the following steps: Associating a first non-AP wireless station (STA) of the non-AP MLD with the first AP operating on the first communication link of the AP MLD; And associate one or more second non-AP STAs of the non-AP MLD with one or more secondary APs operating on one or more corresponding secondary communication links of the AP MLD.

29. The method of claim 27, wherein the simplified neighbor report element includes one or more neighbor AP information fields, each of the one or more neighbor AP information fields being associated with a corresponding secondary AP of the one or more secondary APs, and each carrying a corresponding secondary change sequence field of the one or more secondary change sequence fields.

30. A method for wireless communication performed by an access point (AP) multilink device (MLD), the AP MLD including a first AP operating on a first communication link of the AP MLD and one or more secondary APs operating on one or more corresponding secondary communication links of the AP MLD, the method comprising the steps of: Associate with a non-AP MLD; And a frame for the non-AP MLD is transmitted via the first communication link of the AP MLD, the frame including: a multi-link element including a first change sequence field indicating a first presence or absence of a critical update of one or more first command arguments of the first AP; and a simplified neighbor report element including one or more secondary change sequence fields, each of the one or more secondary change sequence fields being associated with a corresponding secondary AP of the one or more secondary APs and indicating a second presence or absence of a corresponding critical update of one or more corresponding command arguments of the corresponding secondary AP of the one or more secondary APs, wherein the value of the first secondary change sequence field associated with the first secondary AP of the one or more secondary APs is incremented relative to a previous value of the first secondary change sequence field to indicate the occurrence of a second critical update of one or more second command arguments of the first secondary AP of the one or more secondary APs.

Images